6.3.2 Radio resource control information elements

38.3313GPPNRProtocol specificationRadio Resource Control (RRC)Release 17TS

– AdditionalSpectrumEmission

The IE AdditionalSpectrumEmission is used to indicate emission requirements to be fulfilled by the UE (see TS 38.101-1 [15], clause 6.2.3, and TS 38.101-2 [39], clause 6.2.3).

AdditionalSpectrumEmission information element

— ASN1START

— TAG-ADDITIONALSPECTRUMEMISSION-START

AdditionalSpectrumEmission ::= INTEGER (0..7)

— TAG-ADDITIONALSPECTRUMEMISSION-STOP

— ASN1STOP

– Alpha

The IE Alpha defines possible values of a the pathloss compensation coefficient for uplink power control. Value alpha0 corresponds to the value 0, Value alpha04 corresponds to the value 0.4, Value alpha05 corresponds to the value 0.5 and so on. Value alpha1 corresponds to value 1. See also clause 7.1 of TS 38.213 [13].

— ASN1START

— TAG-ALPHA-START

Alpha ::= ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1}

— TAG-ALPHA-STOP

— ASN1STOP

– AMF-Identifier

The IE AMF-Identifier (AMFI) comprises of an AMF Region ID, an AMF Set ID and an AMF Pointer as specified in TS 23.003 [21], clause 2.10.1.

AMF-Identifier information element

— ASN1START

— TAG-AMF-IDENTIFIER-START

AMF-Identifier ::= BIT STRING (SIZE (24))

— TAG-AMF-IDENTIFIER-STOP

— ASN1STOP

– ARFCN-ValueEUTRA

The IE ARFCN-ValueEUTRA is used to indicate the ARFCN applicable for a downlink, uplink or bi-directional (TDD) E-UTRA carrier frequency, as defined in TS 36.101 [22].

ARFCN-ValueEUTRA information element

— ASN1START

— TAG-ARFCN-VALUEEUTRA-START

ARFCN-ValueEUTRA ::= INTEGER (0..maxEARFCN)

— TAG-ARFCN-VALUEEUTRA-STOP

— ASN1STOP

– ARFCN-ValueNR

The IE ARFCN-ValueNR is used to indicate the ARFCN applicable for a downlink, uplink or bi-directional (TDD) NR global frequency raster, as defined in TS 38.101-1 [15] and TS 38.101-2 [39], clause 5.4.2.

— ASN1START

— TAG-ARFCN-VALUENR-START

ARFCN-ValueNR ::= INTEGER (0..maxNARFCN)

— TAG-ARFCN-VALUENR-STOP

— ASN1STOP

– ARFCN-ValueUTRA-FDD

The IE ARFCN-ValueUTRA-FDD is used to indicate the ARFCN applicable for a downlink (Nd, FDD) UTRA-FDD carrier frequency, as defined in TS 25.331 [45].

ARFCN-ValueUTRA-FDD information element

— ASN1START

— TAG-ARFCN-ValueUTRA-FDD-START

ARFCN-ValueUTRA-FDD-r16 ::= INTEGER (0..16383)

— TAG-ARFCN-ValueUTRA-FDD-STOP

— ASN1STOP

– AvailabilityCombinationsPerCell

The IE AvailabilityCombinationsPerCell is used to configure the AvailabilityCombinations applicable for a cell of the IAB DU (see TS 38.213 [13], clause 14). Note that the IE AvailabilityCombinationsPerCellIndex can only be configured up to 511.

AvailabilityCombinationsPerCell information element

— ASN1START

— TAG-AVAILABILITYCOMBINATIONSPERCELL-START

AvailabilityCombinationsPerCell-r16 ::= SEQUENCE {

availabilityCombinationsPerCellIndex-r16 AvailabilityCombinationsPerCellIndex-r16,

iab-DU-CellIdentity-r16 CellIdentity,

positionInDCI-AI-r16 INTEGER(0..maxAI-DCI-PayloadSize-1-r16) OPTIONAL, — Need M

availabilityCombinations-r16 SEQUENCE (SIZE (1..maxNrofAvailabilityCombinationsPerSet-r16)) OF AvailabilityCombination-r16,

…,

[[

availabilityCombinationsRB-Groups-r17 SEQUENCE (SIZE (1..maxNrofAvailabilityCombinationsPerSet-r16)) OF AvailabilityCombinationRB-Groups-r17 OPTIONAL — Need M

]],

[[

positionInDCI-AI-RBGroups-v1720 INTEGER(0..maxAI-DCI-PayloadSize-1-r16) OPTIONAL — Need M

]]

}

AvailabilityCombinationsPerCellIndex-r16 ::= INTEGER(0..maxNrofDUCells-r16)

AvailabilityCombination-r16 ::= SEQUENCE {

availabilityCombinationId-r16 AvailabilityCombinationId-r16,

resourceAvailability-r16 SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7)

}

AvailabilityCombinationId-r16 ::= INTEGER (0..maxNrofAvailabilityCombinationsPerSet-1-r16)

AvailabilityCombinationRB-Groups-r17 ::= SEQUENCE {

availabilityCombinationId-r17 AvailabilityCombinationId-r16,

rb-SetGroups-r17 SEQUENCE (SIZE (1..maxNrofRB-SetGroups-r17)) OF RB-SetGroup-r17 OPTIONAL, — Need R

resourceAvailability-r17 SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7) OPTIONAL — Need R

}

RB-SetGroup-r17 ::= SEQUENCE {

resourceAvailability-r17 SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7) OPTIONAL, — Need R

rb-Sets-r17 SEQUENCE (SIZE (1..maxNrofRB-Sets-r17)) OF INTEGER (0..7) OPTIONAL — Need R

}

— TAG-AVAILABILITYCOMBINATIONSPERCELL-STOP

— ASN1STOP

AvailabilityCombination field descriptions

availabilityCombinationId This ID is used in the DCI Format 2_5 payload to dynamically select this AvailabilityCombination, see TS 38.213 [13], clause 14.

resourceAvailability Indicates the resource availability of soft symbols for a set of consecutive slots in the time domain. The meaning of this field is described in TS 38.213 [13], Table 14.3. If included in RB-SetGroup within AvailabilityCombinationRB-Groups-r17, it indicates the availability of soft resources for an RB set group. If included in AvailabilityCombinationRB-Groups-r17 when the rb-SetGroups is not configured, it indicates the availability of soft resources in one or multiple slots for all RB sets of a DU cell.

AvailabilityCombinationsPerCell field descriptions

iab-DU-CellIdentity The ID of the IAB-DU cell for which the availabilityCombinations are applicable.

positionInDCI-AI The (starting) position (bit) of the AvailabilityCombinationId for the indicated IAB-DU cell (iab-DU-CellIdentity) within the DCI payload. If positionInDCI-AI-RBGroups is not configured, it applies to the availabilityCombinationId included in availabilityCombinations and in availabilityCombinationsRBGroups. If positionInDCI-AI-RBGroups is configured, it applies to the availabilityCombinationId included in availabilityCombinations.

positionInDCI-AI-RBGroups The (starting) position (bit) of the availabilityCombinationId associated to the availabilityCombinationsRBGroups for the indicated IAB-DU cell (iab-DU-CellIdentity) within the DCI payload.

AvailabilityCombinationRB-Groups field descriptions

rb-SetGroups Indicates the RB set groups configured for the availability combination. Each group includes consecutive RB sets.

rb-Sets Indicates the one or more RB set indexes associated to one or more RB sets configured for one RB set group.

– AvailabilityIndicator

The IE AvailabilityIndicator is used to configure monitoring a PDCCH for Availability Indicators (AI).

AvailabilityIndicator information element

— ASN1START

— TAG-AVAILABILITYINDICATOR-START

AvailabilityIndicator-r16 ::= SEQUENCE {

ai-RNTI-r16 AI-RNTI-r16,

dci-PayloadSizeAI-r16 INTEGER (1..maxAI-DCI-PayloadSize-r16),

availableCombToAddModList-r16 SEQUENCE (SIZE(1..maxNrofDUCells-r16)) OF AvailabilityCombinationsPerCell-r16 OPTIONAL, — Need N

availableCombToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofDUCells-r16)) OF AvailabilityCombinationsPerCellIndex-r16 OPTIONAL, — Need N

…

}

AI-RNTI-r16 ::= RNTI-Value

— TAG-AVAILABILITYINDICATOR-STOP

— ASN1STOP

AvailabilityIndicator field descriptions

ai-RNTI Used by an IAB-MT for detection of DCI format 2_5 indicating AvailabilityCombinationId for an IAB-DU’s cells.

availableCombToAddModList A list of availabilityCombinations to add for the IAB-DU’s cells. (see TS 38.213 [13], clause 14).

availableCombToReleaseList A list of availabilityCombinations to release for the IAB-DU’s cells. (see TS 38.213 [13], clause 14).

dci-PayloadSizeAI Total length of the DCI payload scrambled with ai-RNTI (see TS 38.213 [13]).

– BAP-RoutingID

The IE BAP-RoutingID is used for IAB-node to configure the BAP Routing ID.

BAP-RoutingID information element

— ASN1START

— TAG-BAPROUTINGID-START

BAP-RoutingID-r16::= SEQUENCE{

bap-Address-r16 BIT STRING (SIZE (10)),

bap-PathId-r16 BIT STRING (SIZE (10))

}

— TAG-BAPROUTINGID-STOP

— ASN1STOP

BAP-RoutingID field descriptions

bap-Address The ID of a destination IAB-node or IAB-donor-DU used in the BAP header.

bap-PathId The ID of a path used in the BAP header.

– BeamFailureRecoveryConfig

The IE BeamFailureRecoveryConfig is used to configure the UE with RACH resources and candidate beams for beam failure recovery in case of beam failure detection. See also TS 38.321 [3], clause 5.1.1.

BeamFailureRecoveryConfig information element

— ASN1START

— TAG-BEAMFAILURERECOVERYCONFIG-START

BeamFailureRecoveryConfig ::= SEQUENCE {

rootSequenceIndex-BFR INTEGER (0..137) OPTIONAL, — Need M

rach-ConfigBFR RACH-ConfigGeneric OPTIONAL, — Need M

rsrp-ThresholdSSB RSRP-Range OPTIONAL, — Need M

candidateBeamRSList SEQUENCE (SIZE(1..maxNrofCandidateBeams)) OF PRACH-ResourceDedicatedBFR OPTIONAL, — Need M

ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two,

four, eight, sixteen} OPTIONAL, — Need M

ra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL, — Need M

recoverySearchSpaceId SearchSpaceId OPTIONAL, — Need R

ra-Prioritization RA-Prioritization OPTIONAL, — Need R

beamFailureRecoveryTimer ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, ms150, ms200} OPTIONAL, — Need M

…,

[[

msg1-SubcarrierSpacing SubcarrierSpacing OPTIONAL — Need M

]],

[[

ra-PrioritizationTwoStep-r16 RA-Prioritization OPTIONAL, — Need R

candidateBeamRSListExt-v1610 SetupRelease{ CandidateBeamRSListExt-r16 } OPTIONAL — Need M

]],

[[

spCell-BFR-CBRA-r16 ENUMERATED {true} OPTIONAL — Need R

]]

}

PRACH-ResourceDedicatedBFR ::= CHOICE {

ssb BFR-SSB-Resource,

csi-RS BFR-CSIRS-Resource

}

BFR-SSB-Resource ::= SEQUENCE {

ssb SSB-Index,

ra-PreambleIndex INTEGER (0..63),

…

}

BFR-CSIRS-Resource ::= SEQUENCE {

csi-RS NZP-CSI-RS-ResourceId,

ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1) OPTIONAL, — Need R

ra-PreambleIndex INTEGER (0..63) OPTIONAL, — Need R

…

}

CandidateBeamRSListExt-r16::= SEQUENCE (SIZE(1.. maxNrofCandidateBeamsExt-r16)) OF PRACH-ResourceDedicatedBFR

— TAG-BEAMFAILURERECOVERYCONFIG-STOP

— ASN1STOP

BeamFailureRecoveryConfig field descriptions

beamFailureRecoveryTimer Timer for beam failure recovery timer. Upon expiration of the timer the UE does not use CFRA for BFR. Value in ms. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on.

candidateBeamRSList, candidateBeamRSListExt-v1610 Set of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery and the associated RA parameters. This set includes all elements of candidateBeamRSList (without suffix) and all elements of candidateBeamRSListExt-v1610. The UE maintains candidateBeamRSList and candidateBeamRSListExt-v1610 separately: Receiving candidateBeamRSListExt-v1610 set to release releases only the entries that were configured by candidateBeamRSListExt-v1610, and receiving candidateBeamRSListExt-v1610 set to setup replaces only the entries that were configured by candidateBeamRSListExt-v1610 with the newly signalled entries. The network configures these reference signals to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig is provided.

msg1-SubcarrierSpacing Subcarrier spacing for contention free beam failure recovery (see TS 38.211 [16], clause 5.3.2). Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz

rsrp-ThresholdSSB L1-RSRP threshold used for determining whether a candidate beam may be used by the UE to attempt contention free random access to recover from beam failure (see TS 38.213 [13], clause 6).

ra-prioritization Parameters which apply for prioritized random access procedure for BFR (see TS 38.321 [3], clause 5.1.1).

ra-PrioritizationTwoStep Parameters which apply for prioritized 2-step random access procedure for BFR (see TS 38.321 [3], clause 5.1.1).

ra-ssb-OccasionMaskIndex Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources.

rach-ConfigBFR Configuration of random access parameters for BFR.

recoverySearchSpaceId Search space to use for BFR RAR. The network configures this search space to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig is provided. The CORESET associated with the recovery search space cannot be associated with another search space. Network always configures the UE with a value for this field when contention free random access resources for BFR are configured.

rootSequenceIndex-BFR PRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1) for beam failure recovery.

spCell-BFR-CBRA Indicates that UE is configured to send BFR MAC CE for SpCell BFR as specified in TS38.321 [3].

ssb-perRACH-Occasion Number of SSBs per RACH occasion for CF-BFR, see TS 38.213 [13], clause 8.1.

BFR-CSIRS-Resource field descriptions

csi-RS The ID of a NZP-CSI-RS-Resource configured in the CSI-MeasConfig of this serving cell. This reference signal determines a candidate beam for beam failure recovery (BFR).

ra-OccasionList RA occasions that the UE shall use when performing BFR upon selecting the candidate beam identified by this CSI-RS. The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot and Third, in increasing order of indexes for PRACH slots. If the field is absent the UE uses the RA occasion associated with the SSB that is QCLed with this CSI-RS.

ra-PreambleIndex The RA preamble index to use in the RA occasions associated with this CSI-RS. If the field is absent, the UE uses the preamble index associated with the SSB that is QCLed with this CSI-RS.

BFR-SSB-Resource field descriptions

ra-PreambleIndex The preamble index that the UE shall use when performing BFR upon selecting the candidate beams identified by this SSB.

ssb The ID of an SSB transmitted by this serving cell. It determines a candidate beam for beam failure recovery (BFR).

– BeamFailureRecoveryRSConfig

The IE BeamFailureRecoveryRSConfig is used to configure the UE with candidate beams for beam failure recovery in case of beam failure detection. See also TS 38.321 [3], clause 5.17.

BeamFailureRecoveryRSConfig information element

— ASN1START

— TAG-BEAMFAILURERECOVERYRSCONFIG-START

BeamFailureRecoveryRSConfig-r16 ::= SEQUENCE {

rsrp-ThresholdBFR-r16 RSRP-Range OPTIONAL, — Need M

candidateBeamRS-List-r16 SEQUENCE (SIZE(1..maxNrofCandidateBeams-r16)) OF CandidateBeamRS-r16 OPTIONAL, — Need M

…,

[[

candidateBeamRS-List2-r17 SEQUENCE (SIZE(1..maxNrofCandidateBeams-r16)) OF CandidateBeamRS-r16 OPTIONAL — Need R

]]

}

— TAG-BEAMFAILURERECOVERYRSCONFIG-STOP

— ASN1STOP

BeamFailureRecoveryRSConfig field descriptions

candidateBeamRS-List A list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery. The network always configures this parameter in every instance of this IE.

candidateBeamRS-List2 A list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery.

rsrp-ThresholdBFR L1-RSRP threshold used for determining whether a candidate beam may be included by the UE in BFR MAC CE (see TS 38.213 [13], clause 6). The network always configures this parameter in every instance of this IE.

– BetaOffsets

The IE BetaOffsets is used to configure beta-offset values, see TS 38.213 [13], clause 9.3.

BetaOffsets information element

— ASN1START

— TAG-BETAOFFSETS-START

BetaOffsets ::= SEQUENCE {

betaOffsetACK-Index1 INTEGER(0..31) OPTIONAL, — Need S

betaOffsetACK-Index2 INTEGER(0..31) OPTIONAL, — Need S

betaOffsetACK-Index3 INTEGER(0..31) OPTIONAL, — Need S

betaOffsetCSI-Part1-Index1 INTEGER(0..31) OPTIONAL, — Need S

betaOffsetCSI-Part1-Index2 INTEGER(0..31) OPTIONAL, — Need S

betaOffsetCSI-Part2-Index1 INTEGER(0..31) OPTIONAL, — Need S

betaOffsetCSI-Part2-Index2 INTEGER(0..31) OPTIONAL — Need S

}

— TAG-BETAOFFSETS-STOP

— ASN1STOP

BetaOffsets field descriptions

betaOffsetACK-Index1 Up to 2 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11.

betaOffsetACK-Index2 Up to 11 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11.

betaOffsetACK-Index3 Above 11 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11.

betaOffsetCSI-Part1-Index1 Up to 11 bits of CSI part 1 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13.

betaOffsetCSI-Part1-Index2 Above 11 bits of CSI part 1 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13.

betaOffsetCSI-Part2-Index1 Up to 11 bits of CSI part 2 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13.

betaOffsetCSI-Part2-Index2 Above 11 bits of CSI part 2 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13.

– BetaOffsetsCrossPri

The IE BetaOffsetsCrossPri is used to configure beta-offset values for cross-priority HARQ-ACK multiplexing on PUSCH.

BetaOffsetsCrossPri information element

— ASN1START

— TAG-BETAOFFSETSCROSSPRI-START

BetaOffsetsCrossPri-r17 ::= SEQUENCE (SIZE(3)) OF INTEGER(0..31)

— TAG-BETAOFFSETSCROSSPRI-STOP

— ASN1STOP

– BH-LogicalChannelIdentity

The IE BH-LogicalChannelIdentity is used to identify a logical channel between an IAB-node and its parent IAB-node or IAB-donor-DU.

BH-LogicalChannelIdentity information element

— ASN1START

— TAG-BHLOGICALCHANNELIDENTITY-START

BH-LogicalChannelIdentity-r16 ::= CHOICE {

bh-LogicalChannelIdentity-r16 LogicalChannelIdentity,

bh-LogicalChannelIdentityExt-r16 BH-LogicalChannelIdentity-Ext-r16

}

— TAG-BHLOGICALCHANNELIDENTITY-STOP

— ASN1STOP

BH-LogicalChannelIdentity field descriptions

bh-LogicalChannelIdentity ID used for the MAC logical channel.

bh-LogicalChannelIdentityExt ID used for the MAC logical channel.

– BH-LogicalChannelIdentity-Ext

The IE BH-LogicalChannelIdentity-Ext is used to identify a logical channel between an IAB-node and its parent node.

BH-LogicalChannelIdentity-Ext information element

— ASN1START

— TAG-BHLOGICALCHANNELIDENTITYEXT-START

BH-LogicalChannelIdentity-Ext-r16 ::= INTEGER (320.. maxLC-ID-Iab-r16)

— TAG-BHLOGICALCHANNELIDENTITYEXT-STOP

— ASN1STOP

– BH-RLC-ChannelConfig

The IE BH-RLC-ChannelConfig is used to configure an RLC entity, a corresponding logical channel in MAC for BH RLC channel between IAB-node and its parent node.

BH-RLC-ChannelConfig information element

— ASN1START

— TAG-BHRLCCHANNELCONFIG-START

BH-RLC-ChannelConfig-r16::= SEQUENCE {

bh-LogicalChannelIdentity-r16 BH-LogicalChannelIdentity-r16 OPTIONAL, — Cond LCH-SetupOnly

bh-RLC-ChannelID-r16 BH-RLC-ChannelID-r16,

reestablishRLC-r16 ENUMERATED {true} OPTIONAL, — Need N

rlc-Config-r16 RLC-Config OPTIONAL, — Cond LCH-Setup

mac-LogicalChannelConfig-r16 LogicalChannelConfig OPTIONAL, — Cond LCH-Setup

…

}

— TAG-BHRLCCHANNELCONFIG-STOP

— ASN1STOP

BH-RLC-ChannelConfig field descriptions

bh-LogicalChannelIdentity Indicates the logical channel id for BH RLC channel of the IAB-node.

bh-RLC-ChannelID Indicates the BH RLC channel in the link between IAB-MT of the IAB-node and IAB-DU of the parent IAB-node or IAB-donor-DU.

reestablishRLC Indicates that RLC should be re-established.

rlc-Config Determines the RLC mode (UM, AM) and provides corresponding parameters.

Conditional Presence	Explanation
LCH-Setup	This field is mandatory present upon creation of a new logical channel for a BH RLC channel. It is optionally present, Need M, otherwise.
LCH-SetupOnly	This field is mandatory present upon creation of a new logical channel for a BH RLC channel. It is absent, Need M otherwise.

– BH-RLC-ChannelID

The IE BH-RLC-ChannelID is used to identify a BH RLC channel in the link between IAB-MT of the IAB-node and IAB-DU of the parent IAB-node or IAB-donor-DU.

BH-RLC-ChannelID information element

— ASN1START

— TAG-BHRLCCHANNELID-START

BH-RLC-ChannelID-r16 ::= BIT STRING (SIZE (16))

— TAG-BHRLCCHANNELID-STOP

— ASN1STOP

– BSR-Config

The IE BSR-Config is used to configure buffer status reporting.

BSR-Config information element

— ASN1START

— TAG-BSR-CONFIG-START

BSR-Config ::= SEQUENCE {

periodicBSR-Timer ENUMERATED { sf1, sf5, sf10, sf16, sf20, sf32, sf40, sf64,

sf80, sf128, sf160, sf320, sf640, sf1280, sf2560, infinity },

retxBSR-Timer ENUMERATED { sf10, sf20, sf40, sf80, sf160, sf320, sf640, sf1280, sf2560,

sf5120, sf10240, spare5, spare4, spare3, spare2, spare1},

logicalChannelSR-DelayTimer ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, — Need R

…

}

— TAG-BSR-CONFIG-STOP

— ASN1STOP

BSR-Config field descriptions

logicalChannelSR-DelayTimer Value in number of subframes. Value sf20 corresponds to 20 subframes, sf40 corresponds to 40 subframes, and so on.

periodicBSR-Timer Value in number of subframes. Value sf1 corresponds to 1 subframe, value sf5 corresponds to 5 subframes and so on.

retxBSR-Timer Value in number of subframes. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes and so on.

– BWP

The IE BWP is used to configure generic parameters of a bandwidth part as defined in TS 38.211 [16], clause 4.5, and TS 38.213 [13], clause 12.

For each serving cell the network configures at least an initial downlink bandwidth part and one (if the serving cell is configured with an uplink) or two (if using supplementary uplink (SUL)) initial uplink bandwidth parts. Furthermore, the network may configure additional uplink and downlink bandwidth parts for a serving cell.

The uplink and downlink bandwidth part configurations are divided into common and dedicated parameters.

BWP information element

— ASN1START

— TAG-BWP-START

BWP ::= SEQUENCE {

locationAndBandwidth INTEGER (0..37949),

subcarrierSpacing SubcarrierSpacing,

cyclicPrefix ENUMERATED { extended } OPTIONAL — Need R

}

— TAG-BWP-STOP

— ASN1STOP

BWP field descriptions

cyclicPrefix Indicates whether to use the extended cyclic prefix for this bandwidth part. If not set, the UE uses the normal cyclic prefix. Normal CP is supported for all subcarrier spacings and slot formats. Extended CP is supported only for 60 kHz subcarrier spacing. (see TS 38.211 [16], clause 4.2). Except for SUL, the network ensures the same cyclic prefix length is used in active DL BWP and active UL BWP within a serving cell.

locationAndBandwidth Frequency domain location and bandwidth of this bandwidth part. The value of the field shall be interpreted as resource indicator value (RIV) as defined TS 38.214 [19] with assumptions as described in TS 38.213 [13], clause 12, i.e. setting =275. The first PRB is a PRB determined by subcarrierSpacing of this BWP and offsetToCarrier (configured in SCS-SpecificCarrier contained within FrequencyInfoDL / FrequencyInfoUL / FrequencyInfoUL-SIB / FrequencyInfoDL-SIB within ServingCellConfigCommon / ServingCellConfigCommonSIB) corresponding to this subcarrier spacing. In case of TDD, a BWP-pair (UL BWP and DL BWP with the same bwp-Id) must have the same center frequency (see TS 38.213 [13], clause 12)

subcarrierSpacing Subcarrier spacing to be used in this BWP for all channels and reference signals unless explicitly configured elsewhere. Corresponds to subcarrier spacing according to TS 38.211 [16], table 4.2-1. The value kHz15 corresponds to µ=0, value kHz30 corresponds to µ=1, and so on. Only the following values are applicable depending on the used frequency: FR1: 15, 30, or 60 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz For the initial DL BWP and operation in licensed spectrum this field has the same value as the field subCarrierSpacingCommon in MIB of the same serving cell. Except for SUL, the network ensures the same subcarrier spacing is used in active DL BWP and active UL BWP within a serving cell. For the initial DL BWP and operation with shared spectrum channel access, the value of this field corresponds to the subcarrier spacing of the SSB associated to the initial DL BWP.

– BWP-Downlink

The IE BWP-Downlink is used to configure an additional downlink bandwidth part (not for the initial BWP).

BWP-Downlink information element

— ASN1START

— TAG-BWP-DOWNLINK-START

BWP-Downlink ::= SEQUENCE {

bwp-Id BWP-Id,

bwp-Common BWP-DownlinkCommon OPTIONAL, — Cond SetupOtherBWP

bwp-Dedicated BWP-DownlinkDedicated OPTIONAL, — Cond SetupOtherBWP

…

}

— TAG-BWP-DOWNLINK-STOP

— ASN1STOP

BWP-Downlink field descriptions

bwp-Id An identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP.

Conditional Presence	Explanation
SetupOtherBWP	The field is mandatory present upon configuration of a new DL BWP. The field is optionally present, Need M, otherwise.

– BWP-DownlinkCommon

The IE BWP-DownlinkCommon is used to configure the common parameters of a downlink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signalling.

BWP-DownlinkCommon information element

— ASN1START

— TAG-BWP-DOWNLINKCOMMON-START

BWP-DownlinkCommon ::= SEQUENCE {

genericParameters BWP,

pdcch-ConfigCommon SetupRelease { PDCCH-ConfigCommon } OPTIONAL, — Need M

pdsch-ConfigCommon SetupRelease { PDSCH-ConfigCommon } OPTIONAL, — Need M

…

}

— TAG-BWP-DOWNLINKCOMMON-STOP

— ASN1STOP

BWP-DownlinkCommon field descriptions

pdcch-ConfigCommon Cell specific parameters for the PDCCH of this BWP. This field is absent for a dormant BWP.

pdsch-ConfigCommon Cell specific parameters for the PDSCH of this BWP.

– BWP-DownlinkDedicated

The IE BWP-DownlinkDedicated is used to configure the dedicated (UE specific) parameters of a downlink BWP.

BWP-DownlinkDedicated information element

— ASN1START

— TAG-BWP-DOWNLINKDEDICATED-START

BWP-DownlinkDedicated ::= SEQUENCE {

pdcch-Config SetupRelease { PDCCH-Config } OPTIONAL, — Need M

pdsch-Config SetupRelease { PDSCH-Config } OPTIONAL, — Need M

sps-Config SetupRelease { SPS-Config } OPTIONAL, — Need M

radioLinkMonitoringConfig SetupRelease { RadioLinkMonitoringConfig } OPTIONAL, — Need M

…,

[[

sps-ConfigToAddModList-r16 SPS-ConfigToAddModList-r16 OPTIONAL, — Need N

sps-ConfigToReleaseList-r16 SPS-ConfigToReleaseList-r16 OPTIONAL, — Need N

sps-ConfigDeactivationStateList-r16 SPS-ConfigDeactivationStateList-r16 OPTIONAL, — Need R

beamFailureRecoverySCellConfig-r16 SetupRelease {BeamFailureRecoveryRSConfig-r16} OPTIONAL, — Cond SCellOnly

sl-PDCCH-Config-r16 SetupRelease { PDCCH-Config } OPTIONAL, — Need M

sl-V2X-PDCCH-Config-r16 SetupRelease { PDCCH-Config } OPTIONAL — Need M

]],

[[

preConfGapStatus-r17 BIT STRING (SIZE (maxNrofGapId-r17)) OPTIONAL, — Cond PreConfigMG

beamFailureRecoverySpCellConfig-r17 SetupRelease { BeamFailureRecoveryRSConfig-r16} OPTIONAL, — Cond SpCellOnly

harq-FeedbackEnablingforSPSactive-r17 BOOLEAN OPTIONAL, — Need R

cfr-ConfigMulticast-r17 SetupRelease { CFR-ConfigMulticast-r17 } OPTIONAL, — Need M

dl-PPW-PreConfigToAddModList-r17 DL-PPW-PreConfigToAddModList-r17 OPTIONAL, — Need N

dl-PPW-PreConfigToReleaseList-r17 DL-PPW-PreConfigToReleaseList-r17 OPTIONAL, — Need N

nonCellDefiningSSB-r17 NonCellDefiningSSB-r17 OPTIONAL, — Need R

servingCellMO-r17 MeasObjectId OPTIONAL — Cond MeasObject-NCDSSB

]]

}

SPS-ConfigToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-Config

SPS-ConfigToReleaseList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-ConfigIndex-r16

SPS-ConfigDeactivationState-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-ConfigIndex-r16

SPS-ConfigDeactivationStateList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-DeactivationState)) OF SPS-ConfigDeactivationState-r16

DL-PPW-PreConfigToAddModList-r17 ::= SEQUENCE (SIZE (1..maxNrofPPW-Config-r17)) OF DL-PPW-PreConfig-r17

DL-PPW-PreConfigToReleaseList-r17 ::= SEQUENCE (SIZE (1..maxNrofPPW-Config-r17)) OF DL-PPW-ID-r17

— TAG-BWP-DOWNLINKDEDICATED-STOP

— ASN1STOP

BWP-DownlinkDedicated field descriptions

beamFailureRecoverySCellConfig Configuration of candidate RS for beam failure recovery on SCells.

beamFailureRecoverySpCellConfig Configuration of candidate RS for beam failure recovery on the SpCell. This field can only be configured when beamfailure is configured in RadioLinkMonitoringConfig.

cfr-ConfigMulticast UE specific common frequency resource configuration for MBS multicast for one dedicated BWP. This field can be configured within at most one serving cell.

dl-PPW-PreConfigToAddModList Indicates a list of DL-PRS processing window configurations to be added or modified for the dedicated DL BWP.

dl-PPW-PreConfigToReleaseList Indicates a list of DL-PRS processing window configurations to be released for the dedicated DL BWP.

harq-FeedbackEnablingforSPSactive If enabled, UE reports ACK/NACK for the first SPS PDSCH after activation, regardless of if HARQ feedback is enabled or disabled corresponding to the first SPS PDSCH after activation. Otherwise, UE follows configuration of HARQ feedback enabled/disabled corresponding to the first SPS PDSCH after activation.

nonCellDefiningSSB If configured, the RedCap UE operating in this BWP uses this SSB for the purposes for which it would otherwise have used the cell-defining SSB of the serving cell (e.g. obtaining sync, measurements, RLM). Furthermore, other parts of the BWP configuration that refer to an SSB (e.g. the "SSB" configured in the QCL-Info IE; the "ssb-Index" configured in the RadioLinkMonitoringRS; CFRA-SSB-Resource; PRACH-ResourceDedicatedBFR) refer implicitily to this NCD-SSB. The NCD-SSB has the same values for the properties (e.g., ssb-PositionsInBurst, PCI, ssb-periodicity, ssb-PBCH-BlockPower) of the corresponding CD-SSB apart from the values of the properties configured in the NonCellDefiningSSB-r17 IE.

pdcch-Config UE specific PDCCH configuration for one BWP.

pdsch-Config UE specific PDSCH configuration for one BWP.

preConfGapStatus Indicates whether the pre-configured measurement gaps (i.e. the gaps configured with preConfigInd) are activated or deactivated upon the switch to this BWP. If this field is configured, the UE shall apply network-controlled mechanism for activation and deactivation of the pre-configured measurement gaps, otherwise the UE shall apply the autonomous activation/deactivation mechanism, as specified in TS 38.133 [14]. The first/leftmost bit corresponds to the measurement gap with gap ID 1, the second bit corresponds to measurement gap with gap ID 2, and so on. Value 0 indicates that the corresponding pre-configured measurement gap is deactivated while value 1 indicates that the corresponding pre-configured measurement gap is activated. The UE shall ignore the bit if the corresponding measurement gap is not a pre-configured measurement gap.

servingCellMO measObjectId of the MeasObjectNR in MeasConfig which is associated to the serving cell. For this MeasObjectNR, the following relationship applies between this MeasObjectNR and nonCellDefiningSSB in BWP-DownlinkDedicated of the associated downlink BWP: if ssbFrequency is configured, its value is the same as the absoluteFrequencySSB in the nonCellDefiningSSB. If the field is present in a downlink BWP and the BWP is activated, the RedCap UE uses this measurement object for serving cell measurements, otherwise, the RedCap UE uses the servingCellMO in ServingCellConfig IE.

sps-Config UE specific SPS (Semi-Persistent Scheduling) configuration for one BWP. Except for reconfiguration with sync, the NW does not reconfigure sps-Config when there is an active configured downlink assignment (see TS 38.321 [3]). However, the NW may release the sps-Config at any time. Network can only configure SPS in one BWP using either this field or sps-ConfigToAddModList.

sps-ConfigDeactivationStateList Indicates a list of the deactivation states in which each state can be mapped to a single or multiple SPS configurations to be deactivated, see clause 10.2 in TS 38.213 [13]. If a state is mapped to multiple SPS configurations, each of these SPS configurations is configured with the same harq-CodebookID.

sps-ConfigToAddModList Indicates a list of one or more DL SPS configurations to be added or modified in one BWP. Except for reconfiguration with sync, the NW does not reconfigure a SPS configuration when it is active (see TS 38.321 [3]).

sps-ConfigToReleaseList Indicates a list of one or more DL SPS configurations to be released. The NW may release a SPS configuration at any time.

radioLinkMonitoringConfig UE specific configuration of radio link monitoring for detecting cell- and beam radio link failure occasions. The maximum number of failure detection resources should be limited up to 8 for both cell and beam radio link failure detection. For SCells, only periodic 1-port CSI-RS can be configured in IE RadioLinkMonitoringConfig.

sl-PDCCH-Config Indicates the UE specific PDCCH configurations for receiving the SL grants (via SL-RNTI or SL-CS-RNTI) for NR sidelink communication/discovery.

sl-V2X-PDCCH-Config Indicates the UE specific PDCCH configurations for receiving SL grants (i.e. sidelink SPS) for V2X sidelink communication.

Conditional Presence	Explanation
MeasObject-NCD-SSB	This field is optionally present Need S if the UE is a RedCap UE and nonCellDefiningSSB is configured in this DL BWP. It is absent otherwise.
PreConfigMG	The field is optionally present, Need R, if there is at least one per UE gap configured with preConfigInd or there is at least one per FR gap of the same FR which the BWP belongs to and configured with preConfigInd. It is absent, Need R, otherwise.
ScellOnly	The field is optionally present, Need M, in the BWP-DownlinkDedicated of an Scell. It is absent otherwise.
SpCellOnly	The field is optionally present, Need M, in the BWP-DownlinkDedicated of an Spcell. It is absent otherwise.

– BWP-Id

The IE BWP-Id is used to refer to Bandwidth Parts (BWP). The initial BWP (including RedCap-specific initial BWP, if configured) is referred to by BWP-Id 0. The other BWPs are referred to by BWP-Id 1 to maxNrofBWPs.

BWP-Id information element

— ASN1START

— TAG-BWP-ID-START

BWP-Id ::= INTEGER (0..maxNrofBWPs)

— TAG-BWP-ID-STOP

— ASN1STOP

– BWP-Uplink

The IE BWP-Uplink is used to configure an additional uplink bandwidth part (not for the initial BWP).

BWP-Uplink information element

— ASN1START

— TAG-BWP-UPLINK-START

BWP-Uplink ::= SEQUENCE {

bwp-Id BWP-Id,

bwp-Common BWP-UplinkCommon OPTIONAL, — Cond SetupOtherBWP

bwp-Dedicated BWP-UplinkDedicated OPTIONAL, — Cond SetupOtherBWP

…

}

— TAG-BWP-UPLINK-STOP

— ASN1STOP

BWP-Uplink field descriptions

bwp-Id An identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP.

Conditional Presence	Explanation
SetupOtherBWP	The field is mandatory present upon configuration of a new UL BWP. The field is optionally present, Need M, otherwise.

– BWP-UplinkCommon

The IE BWP-UplinkCommon is used to configure the common parameters of an uplink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signalling.

BWP-UplinkCommon information element

— ASN1START

— TAG-BWP-UPLINKCOMMON-START

BWP-UplinkCommon ::= SEQUENCE {

genericParameters BWP,

rach-ConfigCommon SetupRelease { RACH-ConfigCommon } OPTIONAL, — Need M

pusch-ConfigCommon SetupRelease { PUSCH-ConfigCommon } OPTIONAL, — Need M

pucch-ConfigCommon SetupRelease { PUCCH-ConfigCommon } OPTIONAL, — Need M

…,

[[

rach-ConfigCommonIAB-r16 SetupRelease { RACH-ConfigCommon } OPTIONAL, — Need M

useInterlacePUCCH-PUSCH-r16 ENUMERATED {enabled} OPTIONAL, — Need R

msgA-ConfigCommon-r16 SetupRelease { MsgA-ConfigCommon-r16 } OPTIONAL — Cond SpCellOnly2

]],

[[

enableRA-PrioritizationForSlicing-r17 BOOLEAN OPTIONAL, — Cond RA-PrioSliceAI

additionalRACH-ConfigList-r17 SetupRelease { AdditionalRACH-ConfigList-r17 } OPTIONAL, — Cond SpCellOnly2

rsrp-ThresholdMsg3-r17 RSRP-Range OPTIONAL, — Need R

numberOfMsg3-RepetitionsList-r17 SEQUENCE (SIZE (4)) OF NumberOfMsg3-Repetitions-r17 OPTIONAL, — Cond Msg3Rep

mcs-Msg3-Repetitions-r17 SEQUENCE (SIZE (8)) OF INTEGER (0..31) OPTIONAL — Cond Msg3Rep

]]

}

AdditionalRACH-ConfigList-r17 ::= SEQUENCE (SIZE(1..maxAdditionalRACH-r17)) OF AdditionalRACH-Config-r17

AdditionalRACH-Config-r17 ::= SEQUENCE {

rach-ConfigCommon-r17 RACH-ConfigCommon OPTIONAL, — Need R

msgA-ConfigCommon-r17 MsgA-ConfigCommon-r16 OPTIONAL, — Need R

…

}

NumberOfMsg3-Repetitions-r17::= ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16}

— TAG-BWP-UPLINKCOMMON-STOP

— ASN1STOP

BWP-UplinkCommon field descriptions

additionalRACH-ConfigList List of feature or feature combination-specific RACH configurations, i.e. the RACH configurations configured in addition to the one configured by rach-ConfigCommon and by msgA-ConfigCommon. The network associates all possible preambles of an additional RACH configuration to a feature or feature combination. The network does not configure this list to have more than 16 entries.

enableRA-PrioritizationForSlicing Indicates whether or not the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep should override the ra-PrioritizationForAccessIdentity. The field is applicable only when the UE is configured by upper layers with both NSAG and Access Identity 1 or 2. If value TRUE is configured, the UE should only apply the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep. If value FALSE is configured, the UE should only apply ra-PrioritizationForAccessIdentity. If the field is absent, whether to use ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep or ra-PrioritizationForAccessIdentity is up to UE implementation.

mcs-Msg3-Repetitions Configuration of eight candidate MCS indexes for PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. Only the first 4 configured or default MCS indexes are used for PUSCH transmission scheduled by RAR UL grant. This field is only applicable when the UE selects Random Access resources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon, the UE shall apply the values {0, 1, 2, 3, 4, 5, 6, 7} (see TS 38.214 [19], clause 6.1.4).

msgA-ConfigCommon Configuration of the cell specific PRACH and PUSCH resource parameters for transmission of MsgA in 2-step random access type procedure. The NW can configure msgA-ConfigCommon only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial BL BWP

numberOfMsg3-RepetitionsList The number of repetitions for PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. This field is only applicable when the UE selects Random Access resources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon, the UE shall apply the values {n1, n2, n3, n4} (see TS 38.214 [19], clause 6.1.2.1).

pucch-ConfigCommon Cell specific parameters for the PUCCH of this BWP.

pusch-ConfigCommon Cell specific parameters for the PUSCH of this BWP.

rach-ConfigCommon Configuration of cell specific random access parameters which the UE uses for contention based and contention free random access as well as for contention based beam failure recovery in this BWP. The NW configures SSB-based RA (and hence RACH-ConfigCommon) only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial DL BWP or for RedCap UEs DL BWPs associated with nonCellDefiningSSB or the RedCap-specific initial downlink BWP. The network configures rach-ConfigCommon, whenever it configures contention free random access (for reconfiguration with sync or for beam failure recovery).

rach-ConfigCommonIAB Configuration of cell specific random access parameters for the IAB-MT. The IAB specific IAB RACH configuration is used by IAB-MT, if configured.

rsrp-ThresholdMsg3 Threshold used by the UE for determining whether to select resources indicating Msg3 repetition in this BWP, as specified in TS 38.321 [3]. The field is mandatory if both set(s) of Random Access resources with MSG3 repetition indication and set(s) of Random Access resources without MSG3 repetition indication are configured in the BWP. It is absent otherwise.

useInterlacePUCCH-PUSCH If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for cell-specific PUSCH, e.g., PUSCH scheduled by RAR UL grant (see TS 38.213 [13] clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0 and 1 for cell-specific PUCCH (see TS 38.213 [13], clause 9.2.1).

Conditional Presence	Explanation
Msg3Rep	This field is optionally present, Need S, if the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon. It is absent otherwise.
RA-PrioSliceAI	The field is optionally present in SIB1, Need R, if both parameters ra-PrioritizationForAccessIdentity and the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep are present in SIB1. It is absent otherwise.
SpCellOnly2	The field is optionally present, Need M, in the BWP-UplinkCommon of an SpCell. It is absent otherwise.

– BWP-UplinkDedicated

The IE BWP-UplinkDedicated is used to configure the dedicated (UE specific) parameters of an uplink BWP.

BWP-UplinkDedicated information element

— ASN1START

— TAG-BWP-UPLINKDEDICATED-START

BWP-UplinkDedicated ::= SEQUENCE {

pucch-Config SetupRelease { PUCCH-Config } OPTIONAL, — Need M

pusch-Config SetupRelease { PUSCH-Config } OPTIONAL, — Need M

configuredGrantConfig SetupRelease { ConfiguredGrantConfig } OPTIONAL, — Need M

srs-Config SetupRelease { SRS-Config } OPTIONAL, — Need M

beamFailureRecoveryConfig SetupRelease { BeamFailureRecoveryConfig } OPTIONAL, — Cond SpCellOnly

…,

[[

sl-PUCCH-Config-r16 SetupRelease { PUCCH-Config } OPTIONAL, — Need M

cp-ExtensionC2-r16 INTEGER (1..28) OPTIONAL, — Need R

cp-ExtensionC3-r16 INTEGER (1..28) OPTIONAL, — Need R

useInterlacePUCCH-PUSCH-r16 ENUMERATED {enabled} OPTIONAL, — Need R

pucch-ConfigurationList-r16 SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL, — Need M

lbt-FailureRecoveryConfig-r16 SetupRelease { LBT-FailureRecoveryConfig-r16 } OPTIONAL, — Need M

configuredGrantConfigToAddModList-r16 ConfiguredGrantConfigToAddModList-r16 OPTIONAL, — Need N

configuredGrantConfigToReleaseList-r16 ConfiguredGrantConfigToReleaseList-r16 OPTIONAL, — Need N

configuredGrantConfigType2DeactivationStateList-r16 ConfiguredGrantConfigType2DeactivationStateList-r16 OPTIONAL — Need R

]],

[[

ul-TCI-StateList-r17 CHOICE {

explicitlist SEQUENCE {

ul-TCI-ToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-State-r17 OPTIONAL, — Need N

ul-TCI-ToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-State-Id-r17 OPTIONAL — Need N

},

unifiedTCI-StateRef-r17 ServingCellAndBWP-Id-r17

} OPTIONAL, — Need R

ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, — Cond NoTCI-PC

pucch-ConfigurationListMulticast1-r17 SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL, — Need M

pucch-ConfigurationListMulticast2-r17 SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL — Need M

]],

[[

pucch-ConfigMulticast1-r17 SetupRelease { PUCCH-Config } OPTIONAL, — Need M

pucch-ConfigMulticast2-r17 SetupRelease { PUCCH-Config } OPTIONAL — Need M

]]

}

ConfiguredGrantConfigToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfig

ConfiguredGrantConfigToReleaseList-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfigIndex-r16

ConfiguredGrantConfigType2DeactivationState-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfigIndex-r16

ConfiguredGrantConfigType2DeactivationStateList-r16 ::=

SEQUENCE (SIZE (1..maxNrofCG-Type2DeactivationState)) OF ConfiguredGrantConfigType2DeactivationState-r16

— TAG-BWP-UPLINKDEDICATED-STOP

— ASN1STOP

BWP-UplinkDedicated field descriptions

beamFailureRecoveryConfig Configuration of beam failure recovery. If supplementaryUplink is present, the field is present only in one of the uplink carriers, either UL or SUL.

configuredGrantConfig A Configured-Grant of type1 or type2. It may be configured for UL or SUL but in case of type1 not for both at a time. Except for reconfiguration with sync, the NW does not reconfigure configuredGrantConfig when there is an active configured uplink grant Type 2 (see TS 38.321 [3]). However, the NW may release the configuredGrantConfig at any time. Network can only configure configured grant in one BWP using either this field or configuredGrantConfigToAddModList.

configuredGrantConfigToAddModList Indicates a list of one or more configured grant configurations to be added or modified for one BWP. Except for reconfiguration with sync, the NW does not reconfigure a Type 2 configured grant configuration when it is active (see TS 38.321 [3]). The network configures multiple CG configurations for one BWP with either all configurations or no configuration configured with cg-RetransmissionTimer-r16.

configuredGrantConfigToReleaseList Indicates a list of one or more UL Configured Grant configurations to be released. The NW may release a configured grant configuration at any time.

configuredGrantConfigType2DeactivationStateList Indicates a list of the deactivation states in which each state can be mapped to a single or multiple Configured Grant type 2 configurations to be deactivated when the corresponding deactivation DCI is received, see clause 7.3.1 in TS 38.212 [17] and clause 10.2 in TS 38.213 [13].

cp-ExtensionC2, cp-ExtensionC3 Configures the cyclic prefix (CP) extension (see TS 38.211 [16], clause 5.3.1). For 15 kHz SCS, {1..28} are valid for both cp-ExtensionC2 and cp-ExtensionC3. For 30 kHz SCS, {1..28} are valid for cp-ExtensionC2 and {2..28} are valid for cp-ExtensionC3. For 60 kHz SCS, {2..28} are valid for cp-ExtensionC2 and {3..28} are valid for cp-ExtensionC3.

lbt-FailureRecoveryConfig Configures parameters used for detection of consistent uplink LBT failures for operation with shared spectrum channel access, as specified in TS 38.321 [3].

pucch-Config PUCCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL, the network configures PUCCH only on the BWPs of one of the uplinks (normal UL or SUL). The network configures PUCCH-Config at least on non-initial BWP(s) for SpCell and PUCCH SCell. If supported by the UE, the network may configure at most one additional SCell of a cell group with PUCCH-Config (i.e. PUCCH SCell). If PUCCH cell switching is supported by the UE, the network may configure two TDD serving cells with PUCCH-Config within each PUCCH group. For supporting PUCCH cell switching in the PUCCH group with the SpCell, the TDD SpCell and one TDD SCell shall have PUCCH-Config on their normal UL. For supporting PUCCH cell switching in the PUCCH group with only SCells, two TDD SCells shall have PUCCH-Config on their normal UL. In (NG)EN-DC and NE-DC, the NW configures at most one serving cell per frequency range with PUCCH. In (NG)EN-DC and NE-DC, if two PUCCH groups are configured, the serving cells of the NR PUCCH group in FR2 use the same numerology. For NR-DC, the maximum number of PUCCH groups in each cell group is one, and only the same numerology is supported for the cell group with carriers only in FR2. The NW may configure PUCCH for a BWP when setting up the BWP. The network may also add/remove the pucch-Config in an RRCReconfiguration with reconfigurationWithSync (for SpCell or PUCCH SCell) or with SCell release and add (for PUCCH SCell) to move the PUCCH between the UL and SUL carrier of one serving cell. In other cases, only modifications of a previously configured pucch-Config are allowed. If one (S)UL BWP of a serving cell is configured with PUCCH, all other (S)UL BWPs must be configured with PUCCH, too.

pucch-ConfigurationList PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks (see TS 38.213 [13], clause 9.1). Different PUCCH Resource IDs are configured in different PUCCH-Config within the pucch-ConfigurationList if configured.

pucch-ConfigurationListMulticast1 PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks for MBS multicast (see TS 38.213, clause 9).

pucch-ConfigurationListMulticast2 PUCCH configurations for two simultaneously constructed NACK-only feedback for MBS multicast (see TS 38.213, clause 9).

pusch-Config PUSCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL and if it has a PUSCH-Config for both UL and SUL, an UL/SUL indicator field in DCI indicates which of the two to use. See TS 38.212 [17], clause 7.3.1.

pucch-ConfigMulticast1 PUCCH configuration for the HARQ-ACK codebook for MBS multicast when multicast feedback is not configured with a priority value (see TS 38.213 [13], clause 9). If the field is not configured, pucch-Config applies.

pucch-ConfigMulticast2 PUCCH configuration for the NACK-only feedback for MBS multicast when multicast feedback is not configured with a priority value (see TS 38.213 [13], clause 9). If the field is not configured, pucch-Config applies.

sl-PUCCH-Config Indicates the UE specific PUCCH configurations used for the HARQ-ACK feedback reporting for NR sidelink communication.

srs-Config Uplink sounding reference signal configuration.

ul-powerControl Configures power control parameters for PUCCH, PUSCH and SRS when UE is configured with unifiedTCI-StateType for this serving cell.

ul-TCI-StateList Indicates the applicable UL TCI states for PUCCH, PUSCH and SRS.

ul-TCI-ToAddModList Indicates a list of UL TCI states.

unifiedTCI-StateRef Provides the serving cell and UL BWP where UL TCI states applicable to this UL BWP are defined.

useInterlacePUCCH-PUSCH If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for PUSCH (see TS 38.213 [13], clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0, 1, 2, and 3 for PUCCH (see TS 38.213 [13], clause 9.2.1).

Conditional Presence	Explanation
NoTCI-PC	The field is optionally present, Need R, if unifiedTCI-StateType is configured for this serving cell and ul-powerControl is not configured for any UL TCI state or joint TCI state of this serving cell. Otherwise it is absent, Need R
SpCellOnly	The field is optionally present, Need M, in the BWP-UplinkDedicated of an SpCell. It is absent otherwise.

NOTE 1: In case of RRCReconfiguration with reconfigurationWithSync, the UE performs a MAC reset, which involves releasing the PUCCH-CSI/SRS/SR configuration in accordance with clause 5.3.12 and TS 38.321 [3], clauses 5.12 and 5.2. Hence, for these parts of the dedicated radio resource configuration, delta signalling is not supported in the message when reconfigurationWithSync is included.

– CandidateBeamRS

The IE CandidateBeamRS inlcudes candidate beams for beam failure recovery in case of beam failure detection. See also TS 38.321 [3], clause 5.17.

CandidateBeamRS information element

— ASN1START

— TAG-CANDIDATEBEAMRS-START

CandidateBeamRS-r16 ::= SEQUENCE {

candidateBeamConfig-r16 CHOICE {

ssb-r16 SSB-Index,

csi-RS-r16 NZP-CSI-RS-ResourceId

},

servingCellId ServCellIndex OPTIONAL — Need R

}

— TAG-CANDIDATEBEAMRS-STOP

— ASN1STOP

CandidateBeamRS field descriptions

candidateBeamConfig Indicates the resource (i.e. SSB or CSI-RS) defining this beam resource.

servingCellId If the field is absent, the RS belongs to the serving cell in which BeamFailureRecoveryRSConfig is configured.

– CellAccessRelatedInfo

The IE CellAccessRelatedInfo indicates cell access related information for this cell.

CellAccessRelatedInfo information element

— ASN1START

— TAG-CELLACCESSRELATEDINFO-START

CellAccessRelatedInfo ::= SEQUENCE {

plmn-IdentityInfoList PLMN-IdentityInfoList,

cellReservedForOtherUse ENUMERATED {true} OPTIONAL, — Need R

…,

[[

cellReservedForFutureUse-r16 ENUMERATED {true} OPTIONAL, — Need R

npn-IdentityInfoList-r16 NPN-IdentityInfoList-r16 OPTIONAL — Need R

]],

[[

snpn-AccessInfoList-r17 SEQUENCE (SIZE (1..maxNPN-r16)) OF SNPN-AccessInfo-r17 OPTIONAL — Need R

]]

}

SNPN-AccessInfo-r17 ::= SEQUENCE {

extCH-Supported-r17 ENUMERATED {true} OPTIONAL, — Need R

extCH-WithoutConfigAllowed-r17 ENUMERATED {true} OPTIONAL, — Need R

onboardingEnabled-r17 ENUMERATED {true} OPTIONAL, — Need R

imsEmergencySupportForSNPN-r17 ENUMERATED {true} OPTIONAL — Need R

}

— TAG-CELLACCESSRELATEDINFO-STOP

— ASN1STOP

CellAccessRelatedInfo field descriptions

cellReservedForFutureUse Indicates whether the cell is reserved, as defined in 38.304 [20] for future use. The field is applicable to all PLMNs and NPNs. This field is ignored by IAB-MT.

cellReservedForOtherUse Indicates whether the cell is reserved, as defined in 38.304 [20]. The field is applicable to all PLMNs. This field is ignored by IAB-MT for cell barring determination, but still considered by NPN capable IAB-MT for determination of an NPN-only cell.

npn-IdentityInfoList The npn-IdentityInfoList is used to configure a set of NPN-IdentityInfo elements. Each of those elements contains a list of one or more NPN Identities and additional information associated with those NPNs. The total number of PLMNs (identified by a PLMN identity in plmn -IdentityList), PNI-NPNs (identified by a PLMN identity and a CAG-ID), and SNPNs (identified by a PLMN identity and a NID) together in the PLMN-IdentityInfoList and NPN-IdentityInfoList does not exceed 12, except for the NPN-only cells. A PNI-NPN and SNPN can be included only once, and in only one entry of the NPN-IdentityInfoList. In case of NPN-only cells the PLMN-IdentityList contains a single element that does not count to the limit of 12 and the cellIdentity of the first entry of the PLMN-IdentityInfoList is set to the same value as the cellIdentity-r16 of the first entry of the NPN-IdentityInfoList. The NPN index is defined as B+c1+c2+…+c(n-1)+d1+d2+…+d(m-1)+e(i) for the NPN identity included in the n-th entry of NPN-IdentityInfoList and in the m-th entry of npn-Identitylist within that NPN-IdentityInfoList entry, and the i-th entry of its corresponding NPN-Identity, where – B is the index used for the last PLMN in the PLMN-IdentittyInfoList; in NPN-only cells B is considered 0; – c(j) is the number of NPN index values used in the j-th NPN-IdentityInfoList entry; – d(k) is the number of NPN index values used in the k-th npn-IdentityList entry within the n-th NPN-IdentityInfoList entry; – e(i) is – i if the n-th entry of NPN-IdentityInfoList entry is for SNPN(s); – 1 if the n-th entry of NPN-IdentityInfoList entry is for PNI-NPN(s).

plmn-IdentityInfoList The plmn-IdentityInfoList is used to configure a set of PLMN-IdentityInfo elements. Each of those elements contains a list of one or more PLMN Identities and additional information associated with those PLMNs. A PLMN-identity can be included only once, and in only one entry of the PLMN-IdentityInfoList. The PLMN index is defined as b1+b2+…+b(n-1)+i for the PLMN included at the n-th entry of PLMN-IdentityInfoList and the i-th entry of its corresponding PLMN-IdentityInfo, where b(j) is the number of PLMN-Identity entries in each PLMN-IdentityInfo, respectively.

snpn-AccessInfoList This list provides access related information for each SNPN in npn-IdentityInfoList, see TS 23.501 [32]. The n-th entry of the list contains the access related information of the n-th SNPN in npn-IdentityInfoList.

SNPN-AccessInfo field descriptions

extCH-Supported Indicates whether the SNPN supports access using credentials from a Credentials Holder as specified in TS 23.501 [32].

extCH-WithoutConfigAllowed Indicates whether the SNPN allows registration attempts with credentials from a Credentials Holder from UEs that are not explicitly configured to select the SNPN as specified in TS 23.501 [32].

imsEmergencySupportForSNPN Indicates whether the SNPN supports IMS emergency bearer services for UEs in limited service mode in the cell. If absent, IMS emergency call is not supported by the SNPN in the cell for UEs in limited service mode.

onboardingEnabled Indicates whether the onboarding SNPN allows registration for onboarding in the cell as specified in TS 23.501 [32].

– CellAccessRelatedInfo-EUTRA-5GC

The IE CellAccessRelatedInfo-EUTRA-5GC indicates cell access related information for an LTE cell connected to 5GC.

CellAccessRelatedInfo-EUTRA-5GC information element

— ASN1START

— TAG-CELLACCESSRELATEDINFOEUTRA-5GC-START

CellAccessRelatedInfo-EUTRA-5GC ::= SEQUENCE {

plmn-IdentityList-eutra-5gc PLMN-IdentityList-EUTRA-5GC,

trackingAreaCode-eutra-5gc TrackingAreaCode,

ranac-5gc RAN-AreaCode OPTIONAL,

cellIdentity-eutra-5gc CellIdentity-EUTRA-5GC

}

PLMN-IdentityList-EUTRA-5GC::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity-EUTRA-5GC

PLMN-Identity-EUTRA-5GC ::= CHOICE {

plmn-Identity-EUTRA-5GC PLMN-Identity,

plmn-index INTEGER (1..maxPLMN)

}

CellIdentity-EUTRA-5GC ::= CHOICE {

cellIdentity-EUTRA BIT STRING (SIZE (28)),

cellId-index INTEGER (1..maxPLMN)

}

— TAG-CELLACCESSRELATEDINFOEUTRA-5GC-STOP

— ASN1STOP

– CellAccessRelatedInfo-EUTRA-EPC

The IE CellAccessRelatedInfo-EUTRA-EPC indicates cell access related information for an LTE cell connected to EPC.

CellAccessRelatedInfo-EUTRA-EPC information element

— ASN1START

— TAG-CELLACCESSRELATEDINFOEUTRA-EPC-START

CellAccessRelatedInfo-EUTRA-EPC ::= SEQUENCE {

plmn-IdentityList-eutra-epc PLMN-IdentityList-EUTRA-EPC,

trackingAreaCode-eutra-epc BIT STRING (SIZE (16)),

cellIdentity-eutra-epc BIT STRING (SIZE (28))

}

PLMN-IdentityList-EUTRA-EPC::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity

— TAG-CELLACCESSRELATEDINFOEUTRA-EPC-STOP

— ASN1STOP

– CellGroupConfig

The CellGroupConfig IE is used to configure a master cell group (MCG) or secondary cell group (SCG). A cell group comprises of one MAC entity, a set of logical channels with associated RLC entities and of a primary cell (SpCell) and one or more secondary cells (SCells).

CellGroupConfig information element

— ASN1START

— TAG-CELLGROUPCONFIG-START

— Configuration of one Cell-Group:

CellGroupConfig ::= SEQUENCE {

cellGroupId CellGroupId,

rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig OPTIONAL, — Need N

rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity OPTIONAL, — Need N

mac-CellGroupConfig MAC-CellGroupConfig OPTIONAL, — Need M

physicalCellGroupConfig PhysicalCellGroupConfig OPTIONAL, — Need M

spCellConfig SpCellConfig OPTIONAL, — Need M

sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig OPTIONAL, — Need N

sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex OPTIONAL, — Need N

…,

[[

reportUplinkTxDirectCurrent ENUMERATED {true} OPTIONAL — Cond BWP-Reconfig

]],

[[

bap-Address-r16 BIT STRING (SIZE (10)) OPTIONAL, — Need M

bh-RLC-ChannelToAddModList-r16 SEQUENCE (SIZE(1..maxBH-RLC-ChannelID-r16)) OF BH-RLC-ChannelConfig-r16 OPTIONAL, — Need N

bh-RLC-ChannelToReleaseList-r16 SEQUENCE (SIZE(1..maxBH-RLC-ChannelID-r16)) OF BH-RLC-ChannelID-r16 OPTIONAL, — Need N

f1c-TransferPath-r16 ENUMERATED {lte, nr, both} OPTIONAL, — Need M

simultaneousTCI-UpdateList1-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, — Need R

simultaneousTCI-UpdateList2-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, — Need R

simultaneousSpatial-UpdatedList1-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, — Need R

simultaneousSpatial-UpdatedList2-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, — Need R

uplinkTxSwitchingOption-r16 ENUMERATED {switchedUL, dualUL} OPTIONAL, — Need R

uplinkTxSwitchingPowerBoosting-r16 ENUMERATED {enabled} OPTIONAL — Need R

]],

[[

reportUplinkTxDirectCurrentTwoCarrier-r16 ENUMERATED {true} OPTIONAL — Need N

]],

[[

f1c-TransferPathNRDC-r17 ENUMERATED {mcg, scg, both} OPTIONAL, — Need M

uplinkTxSwitching-2T-Mode-r17 ENUMERATED {enabled} OPTIONAL, — Cond 2Tx

uplinkTxSwitching-DualUL-TxState-r17 ENUMERATED {oneT, twoT} OPTIONAL, — Cond 2Tx

uu-RelayRLC-ChannelToAddModList-r17 SEQUENCE (SIZE(1..maxUu-RelayRLC-ChannelID-r17)) OF Uu-RelayRLC-ChannelConfig-r17

OPTIONAL, — Need N

uu-RelayRLC-ChannelToReleaseList-r17 SEQUENCE (SIZE(1..maxUu-RelayRLC-ChannelID-r17)) OF Uu-RelayRLC-ChannelID-r17

OPTIONAL, — Need N

simultaneousU-TCI-UpdateList1-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, — Need R

simultaneousU-TCI-UpdateList2-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, — Need R

simultaneousU-TCI-UpdateList3-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, — Need R

simultaneousU-TCI-UpdateList4-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, — Need R

rlc-BearerToReleaseListExt-r17 SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentityExt-r17 OPTIONAL, — Need N

iab-ResourceConfigToAddModList-r17 SEQUENCE (SIZE(1..maxNrofIABResourceConfig-r17)) OF IAB-ResourceConfig-r17 OPTIONAL, — Need N

iab-ResourceConfigToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofIABResourceConfig-r17)) OF IAB-ResourceConfigID-r17 OPTIONAL — Need N

]],

[[

reportUplinkTxDirectCurrentMoreCarrier-r17 ReportUplinkTxDirectCurrentMoreCarrier-r17 OPTIONAL — Need N

]]

}

— Serving cell specific MAC and PHY parameters for a SpCell:

SpCellConfig ::= SEQUENCE {

servCellIndex ServCellIndex OPTIONAL, — Cond SCG

reconfigurationWithSync ReconfigurationWithSync OPTIONAL, — Cond ReconfWithSync

rlf-TimersAndConstants SetupRelease { RLF-TimersAndConstants } OPTIONAL, — Need M

rlmInSyncOutOfSyncThreshold ENUMERATED {n1} OPTIONAL, — Need S

spCellConfigDedicated ServingCellConfig OPTIONAL, — Need M

…,

[[

lowMobilityEvaluationConnected-r17 SEQUENCE {

s-SearchDeltaP-Connected-r17 ENUMERATED {dB3, dB6, dB9, dB12, dB15, spare3, spare2, spare1},

t-SearchDeltaP-Connected-r17 ENUMERATED {s5, s10, s20, s30, s60, s120, s180, s240, s300, spare7, spare6, spare5,

spare4, spare3, spare2, spare1}

} OPTIONAL, — Need R

goodServingCellEvaluationRLM-r17 GoodServingCellEvaluation-r17 OPTIONAL, — Need R

goodServingCellEvaluationBFD-r17 GoodServingCellEvaluation-r17 OPTIONAL, — Need R

deactivatedSCG-Config-r17 SetupRelease { DeactivatedSCG-Config-r17 } OPTIONAL — Cond SCG-Opt

]]

}

ReconfigurationWithSync ::= SEQUENCE {

spCellConfigCommon ServingCellConfigCommon OPTIONAL, — Need M

newUE-Identity RNTI-Value,

t304 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000},

rach-ConfigDedicated CHOICE {

uplink RACH-ConfigDedicated,

supplementaryUplink RACH-ConfigDedicated

} OPTIONAL, — Need N

…,

[[

smtc SSB-MTC OPTIONAL — Need S

]],

[[

daps-UplinkPowerConfig-r16 DAPS-UplinkPowerConfig-r16 OPTIONAL — Need N

]],

[[

sl-PathSwitchConfig-r17 SL-PathSwitchConfig-r17 OPTIONAL — Cond DirectToIndirect-PathSwitch

]]

}

DAPS-UplinkPowerConfig-r16 ::= SEQUENCE {

p-DAPS-Source-r16 P-Max,

p-DAPS-Target-r16 P-Max,

uplinkPowerSharingDAPS-Mode-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic }

}

SCellConfig ::= SEQUENCE {

sCellIndex SCellIndex,

sCellConfigCommon ServingCellConfigCommon OPTIONAL, — Cond SCellAdd

sCellConfigDedicated ServingCellConfig OPTIONAL, — Cond SCellAddMod

…,

[[

smtc SSB-MTC OPTIONAL — Need S

]],

[[

sCellState-r16 ENUMERATED {activated} OPTIONAL, — Cond SCellAddSync

secondaryDRX-GroupConfig-r16 ENUMERATED {true} OPTIONAL — Cond DRX-Config2

]],

[[

preConfGapStatus-r17 BIT STRING (SIZE (maxNrofGapId-r17)) OPTIONAL, — Cond PreConfigMG

goodServingCellEvaluationBFD-r17 GoodServingCellEvaluation-r17 OPTIONAL, — Need R

sCellSIB20-r17 SetupRelease { SCellSIB20-r17 } OPTIONAL — Need M

]]

}

SCellSIB20-r17 ::= OCTET STRING (CONTAINING SystemInformation)

DeactivatedSCG-Config-r17 ::= SEQUENCE {

bfd-and-RLM BOOLEAN,

…

}

GoodServingCellEvaluation-r17 ::= SEQUENCE {

offset-r17 ENUMERATED {db2, db4, db6, db8} OPTIONAL — Need S

}

SL-PathSwitchConfig-r17 ::= SEQUENCE {

targetRelayUE-Identity-r17 SL-SourceIdentity-r17,

t420-r17 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000},

…

}

IAB-ResourceConfig-r17 ::= SEQUENCE {

iab-ResourceConfigID-r17 IAB-ResourceConfigID-r17,

slotList-r17 SEQUENCE (SIZE (1..5120)) OF INTEGER (0..5119) OPTIONAL, — Need M

periodicitySlotList-r17 ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ms20, ms40, ms80, ms160} OPTIONAL, — Need M

slotListSubcarrierSpacing-r17 SubcarrierSpacing OPTIONAL, — Need M

…

}

IAB-ResourceConfigID-r17 ::= INTEGER(0..maxNrofIABResourceConfig-1-r17)

ReportUplinkTxDirectCurrentMoreCarrier-r17 ::= SEQUENCE (SIZE(1.. maxSimultaneousBands)) OF IntraBandCC-CombinationReqList-r17

IntraBandCC-CombinationReqList-r17::= SEQUENCE {

servCellIndexList-r17 SEQUENCE (SIZE(1.. maxNrofServingCells)) OF ServCellIndex,

cc-CombinationList-r17 SEQUENCE (SIZE(1.. maxNrofReqComDC-Location-r17)) OF IntraBandCC-Combination-r17

}

IntraBandCC-Combination-r17::= SEQUENCE (SIZE(1.. maxNrofServingCells)) OF CC-State-r17

CC-State-r17::= SEQUENCE {

dlCarrier-r17 CarrierState-r17 OPTIONAL,

ulCarrier-r17 CarrierState-r17 OPTIONAL

}

CarrierState-r17::= CHOICE {

deActivated-r17 NULL,

activeBWP-r17 INTEGER (0..maxNrofBWPs)

}

— TAG-CELLGROUPCONFIG-STOP

— ASN1STOP

CC-State field descriptions

dlCarrier Indicates DL carrier activation state for this carrier and the related active BWP Index, if activated.

ulCarrier Indicates UL carrier activation state for this carrier and the related active BWP Index, if activated.

CellGroupConfig field descriptions

bap-Address BAP address of the parent node in cell group.

bh-RLC-ChannelToAddModList Configuration of the backhaul RLC entities and the corresponding MAC Logical Channels to be added and modified.

bh-RLC-ChannelToReleaseList List of the backhaul RLC entities and the corresponding MAC Logical Channels to be released.

f1c-TransferPath The F1-C transfer path that an EN-DC IAB-MT should use for transferring F1-C packets to the IAB-donor-CU. If IAB-MT is configured with lte, IAB-MT can only use LTE leg for F1-C transfer. If IAB-MT is configured with nr, IAB-MT can only use NR leg for F1-C transfer. If IAB-MT is configured with both, it is up to IAB-MT to select an LTE leg or a NR leg for F1-C transfer. If the field is not configured, the IAB node uses the NR leg as the default one.

f1c-TransferPathNRDC The F1-C transfer path that an NR-DC IAB-MT should use for transferring F1-C packets to the IAB-donor-CU. If IAB-MT is configured with mcg, IAB-MT can only use the MCG for F1-C transfer. If IAB-MT is configured with scg, IAB-MT can only use the SCG for F1-C transfer. If IAB-MT is configured with both, it is up to IAB-MT to select the MCG or the SCG for F1-C transfer.

mac-CellGroupConfig MAC parameters applicable for the entire cell group.

rlc-BearerToAddModList Configuration of the MAC Logical Channel, the corresponding RLC entities and association with radio bearers.

reportUplinkTxDirectCurrent Enables reporting of uplink and supplementary uplink Direct Current location information upon BWP configuration and reconfiguration. This field is only present when the BWP configuration is modified or any serving cell is added or removed. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. If UE is configured with SUL carrier, UE reports both UL and SUL Direct Current locations.

reportUplinkTxDirectCurrentMoreCarrier Enables reporting of uplink Direct Current location information when the UE is configured with intra-band CA. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. The UE only report the uplink Direct Current location information that are related to the indicated cc-CombinationList. The network does not include carriers which locate in DL only spectrum described in TS 38.101-2 [39] clause 5.3A.4 and defined by Fsd according to Table 5.3A.4-3 in FR2 in the IntraBandCC-CombinationReqList. I.e. DL-only carrier in FR2 frequency spectrum is not used to calculate the default DC location.

reportUplinkTxDirectCurrentTwoCarrier Enables reporting of uplink Direct Current location information when the UE is configured with uplink intra-band CA with two carriers. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message.

rlc-BearerToReleaseListExt List of the RLC entities and the corresponding MAC Logical Channels to be released for multicast MRBs.

rlmInSyncOutOfSyncThreshold BLER threshold pair index for IS/OOS indication generation, see TS 38.133 [14], table 8.1.1-1. n1 corresponds to the value 1. When the field is absent, the UE applies the value 0. Whenever this is reconfigured, UE resets N310 and N311, and stops T310, if running. Network does not include this field.

sCellSIB20 This field is used to transfer SIB20 of the SCell in order to allow the UE for MBS broadcast reception on SCell. The network configures this field only for a single SCell at a time.

sCellState Indicates whether the SCell shall be considered to be in activated state upon SCell configuration. If the field is included for an SCell configured with TRS for fast activation of the SCell, such TRS is not used for the corresponding SCell.

sCellToAddModList List of secondary serving cells (SCells) to be added or modified.

sCellToReleaseList List of secondary serving cells (SCells) to be released.

secondaryDRX-GroupConfig The field is used to indicate whether the SCell belongs to the secondary DRX group. All serving cells in the secondary DRX group shall belong to one Frequency Range and all serving cells in the legacy DRX group shall belong to another Frequency Range.

simultaneousSpatial-UpdatedList1, simultaneousSpatial-UpdatedList2 List of serving cells which can be updated simultaneously for spatial relation with a MAC CE. The simultaneousSpatial-UpdatedList1 and simultaneousSpatial-UpdatedList2 shall not contain same serving cells. Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists.

simultaneousTCI-UpdateList1, simultaneousTCI-UpdateList2 List of serving cells which can be updated simultaneously for TCI relation with a MAC CE. The simultaneousTCI-UpdateList1 and simultaneousTCI-UpdateList2 shall not contain same serving cells. Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists.

simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4 List of serving cells for which the Unified TCI States Activation/Deactivation MAC CE applies simultaneously, as specified in TS 38.321 [3] clause 6.1.3.47. The different lists shall not contain same serving cells. Network only configures in these lists serving cells that are configured with unifiedTCI-StateType.

spCellConfig Parameters for the SpCell of this cell group (PCell of MCG or PSCell of SCG).

uplinkTxSwitchingOption Indicates which option is configured for dynamic UL Tx switching for inter-band UL CA or (NG)EN-DC. The field is set to switchedUL if network configures option 1 as specified in TS 38.214 [19], or dualUL if network configures option 2 as specified in TS 38.214 [19]. Network always configures UE with a value for this field in inter-band UL CA case and (NG)EN-DC case where UE supports dynamic UL Tx switching.

uplinkTxSwitchingPowerBoosting Indicates whether the UE is allowed to enable 3dB boosting on the maximum output power for transmission on carrier2 under the operation state in which 2-port transmission can be supported on carrier2 for inter-band UL CA case with dynamic UL Tx switching as defined in TS 38.101-1 [15]. Network can only configure this field for dynamic UL Tx switching in inter-band UL CA case with power Class 3 as defined in TS 38.101-1 [15].

uplinkTxSwitching-2T-Mode Indicates 2Tx-2Tx switching mode is configured for inter-band UL CA or SUL, in which the switching gap duration for a triggered uplink switching (as specified in TS 38.214 [19]) is equal to the switching time capability value reported for the switching mode. If this field is absent and uplinkTxSwitching is configured, it is interpreted that 1Tx-2Tx UL Tx switching is configured as specified in TS 38.214 [19]. In this case, there is one uplink (or one uplink band in case of intra-band) configured with uplinkTxSwitching, on which the maximum number of antenna ports among all configured P-SRS/A-SRS and activated SP-SRS resources should be 1 and non-codebook based UL MIMO is not configured.

uplinkTxSwitching-DualUL-TxState Indicates the state of Tx chains if the state of Tx chains after the UL Tx switching is not unique (as specified in TS 38.214 [19]) in case of 2Tx-2Tx switching is configured and uplinkTxSwitchingOption is set to dualUL. Value oneT indicates 1Tx is assumed to be supported on the carriers on each band, value twoT indicates 2Tx is assumed to be supported on that carrier.

uu-RelayRLC-ChannelToAddModList List of the Uu RLC entities and the corresponding MAC Logical Channels to be added or modified.

uu-RelayRLC-ChannelToReleaseList List of the Uu RLC entities and the corresponding MAC Logical Channels to be released.

DeactivatedSCG-Config field descriptions

bfd-and-RLM If the field is set to true, the UE shall perform RLM and BFD on the PSCell when the SCG is deactivated and the network ensures that beamFailure is not configured in the radioLinkMonitoringConfig of the DL BWP of the PSCell in which the UE performs BFD. If set to false, the UE is not required to perform RLM and BFD on the PSCell when the SCG is deactivated.

DAPS-UplinkPowerConfig field descriptions

p-DAPS-Source The maximum total transmit power to be used by the UE in the source cell group during DAPS handover.

p-DAPS-Target The maximum total transmit power to be used by the UE in the target cell group during DAPS handover.

uplinkPowerSharingDAPS-Mode Indicates the uplink power sharing mode that the UE uses in DAPS handover (see TS 38.213 [13]).

GoodServingCellEvaluation field descriptions

offset The parameter "X" (dB) for the good serving cell quality criterion in RRC_CONNECTED, for a cell operating in FR1 and FR2, respectively. If this field is absent, the UE applies the (default) value of 0 dB for "X".

IAB-ResourceConfig field descriptions

iab-ResourceConfigID This ID is used to indicate the specific resource configuration addressed by the MAC CEs specified in TS 38.321 [3].

periodicitySlotList Indicates the periodicity in ms of the list of slot indexes indicated in slotList.

slotList Indicates the list of slot indexes to which the information indicated in the specific MAC CE applies to, as specified in TS 38.321 [3]. The values of the entries in the slotList are strictly less than the value of the periodicitySlotList.

slotListSubcarrierSpacing Subcarrier spacing used as reference for the slotList configuration. Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 60 or 120 kHz FR2-2: 120 or 480 kHz

ReconfigurationWithSync field descriptions

rach-ConfigDedicated Random access configuration to be used for the reconfiguration with sync (e.g. handover). The UE performs the RA according to these parameters in the firstActiveUplinkBWP (see UplinkConfig).

smtc The SSB periodicity/offset/duration configuration of target cell for NR PSCell change and NR PCell change. The network sets the periodicityAndOffset to indicate the same periodicity as ssb-periodicityServingCell in spCellConfigCommon or sets to the same periodicity as ssb-Periodicity-r17 in nonCellDefiningSSB-r17 if the first active DL BWP included in this RRC message is configured with nonCellDefiningSSB-r17 for RedCap. For case of NR PCell change, the smtc is based on the timing reference of (source) PCell. For case of NR PSCell change, it is based on the timing reference of source PSCell. If both this field and targetCellSMTC-SCG are absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message. For a RedCap UE, if the first active DL BWP included in this RRC message is configured with nonCellDefiningSSB-r17, this field corresponds to the NCD-SSB indicated by nonCellDefiningSSB-r17, otherwise, this field corresponds to the CD-SSB indicated by absoluteFrequencySSB in frequencyInfoDL.

ReportUplinkTxDirectCurrentMoreCarrier field descriptions

IntraBandCC-Combination Indicates carriers states and BWPs indexes in a CC combination, each carrier in this combination correspondes an entry in servCellIndexList with same order. This field shall have same size with servCellIndexList.

IntraBandCC-CombinationReqList Indicates the list of the requested carriers/BWPs combinations for an intra-band CA component.

servCellIndexList indicates the list of cell index for an intra-band CA component.

SCellConfig field descriptions

goodServingCellEvaluationBFD Indicates the criterion for a UE to detect the good serving cell quality for BFD relaxation in an SCell in RRC_CONNECTED. This field is always configured when the network enables BFD relaxation for the UE in this SCell.

preConfGapStatus Indicates whether the pre-configured measurement gaps (i.e. the gaps configured with preConfigInd) are activated or deactivated while this SCell is deactivated. If this field is configured, the UE shall apply network-controlled mechanism for activation and deactivation of the pre-configured measurement gaps, otherwise the UE shall apply the autonomous activation/deactivation mechanism, as specified in TS 38.133 [14]. The first/leftmost bit corresponds to the measurement gap with gap ID 1, the second bit corresponds to measurement gap with gap ID 2, and so on. Value 0 indicates that the corresponding pre-configured measurement gap is deactivated while value 1 indicates that the corresponding pre-configured measurement gap is activated. The UE shall ignore the bit if the corresponding measurement gap is not a pre-configured measurement gap.

smtc The SSB periodicity/offset/duration configuration of target cell for NR SCell addition. The network sets the periodicityAndOffset to indicate the same periodicity as ssb-periodicityServingCell in sCellConfigCommon. The smtc is based on the timing of the SpCell of associated cell group. In case of inter-RAT handover to NR, the timing reference is the NR PCell. In case of intra-NR PCell change (standalone NR) or NR PSCell change (EN-DC), the timing reference is the target SpCell. If the field is absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message.

SpCellConfig field descriptions

deactivated-SCG-Config Configuration applicable when the SCG is deactivated. The network always configures this field before or when indicating that the SCG is deactivated in an RRCReconfiguration, RRCResume, E-UTRA RRCConnectionReconfiguration or E-UTRA RRCConnectionResume message.

goodServingCellEvaluationBFD Indicates the criterion for a UE to detect the good serving cell quality for BFD relaxation in the SpCell in RRC_CONNECTED. The field is always configured when the network enables BFD relaxation for the UE in this SpCell.

goodServingCellEvaluationRLM Indicates the criterion for a UE to detect the good serving cell quality for RLM relaxation in the SpCell in RRC_CONNECTED. The field is always configured when the network enables RLM relaxation for the UE in this SpCell.

lowMobilityEvaluationConnected Indicates the criterion for a UE to detect low mobility in RRC_CONNECTED in an SpCell. The s-SearchDeltaP-Connected is the parameter "SSearchDeltaP-connected". Value dB3 corresponds to 3 dB, dB6 corresponds to 6 dB and so on. The t-SearchDeltaP-Connected is the parameter "TSearchDeltaP-Connected". Value s5 means 5 seconds, value s10 means 10 seconds and so on. Low mobility criterion is configured in NR PCell for the case of NR SA/ NR CA/ NE-DC/NR-DC, and in the NR PSCell for the case of EN-DC.

reconfigurationWithSync Parameters for the synchronous reconfiguration to the target SpCell.

rlf-TimersAndConstants Timers and constants for detecting and triggering cell-level radio link failure. For the SCG, rlf-TimersAndConstants can only be set to setup and is always included at SCG addition.

servCellIndex Serving cell ID of a PSCell. The PCell of the Master Cell Group uses ID = 0.

SL-PathSwitchConfig field descriptions

targetRelayUE-Identity Indicates the L2 source ID of the target L2 U2N Relay UE during path switch.

T420 Indicates the timer value of T420 to be used during path switch.

Conditional Presence	Explanation
2Tx	The field is optionally present, Need R, if uplinkTxSwitching is configured; otherwise it is absent, Need R.
BWP-Reconfig	The field is optionally present, Need N, if the BWPs are reconfigured or if serving cells are added or removed. Otherwise it is absent.
DirectToIndirect-PathSwitch	The field is mandatory present for the L2 U2N remote UE at path switch to the target L2 U2N Relay UE. It is absent otherwise.
DRX-Config2	The field is optionally present, Need N, if drx-ConfigSecondaryGroup is configured. It is absent otherwise.
PreConfigMG	The field is optionally present, Need R, if there is at least one per UE gap configured with preConfigInd or there is at least one per FR gap of the same FR which the SCell belongs to and configured with preConfigInd. It is absent, Need R, otherwise.
ReconfWithSync	The field is mandatory present in the RRCReconfiguration message: – in each configured CellGroupConfig for which the SpCell changes, – in the masterCellGroup: – at change of AS security key derived from KgNB, – in an RRCReconfiguration message contained in a DLInformationTransferMRDC message, – path switch of L2 U2N remote UE to the target PCell, – path switch of L2 U2N remote UE to the target L2 U2N Relay UE, – in the secondaryCellGroup at: – PSCell addition, – SCG resume with NR-DC or (NG)EN-DC, – update of required SI for PSCell, – change of AS security key derived from S-KgNB in NR-DC while the UE is configured with at least one radio bearer with keyToUse set to secondary and that is not released by this RRCReconfiguration message, – MN handover in (NG)EN-DC. Otherwise, it is optionally present, need M. The field is absent in the masterCellGroup in RRCResume and RRCSetup messages and is absent in the masterCellGroup in RRCReconfiguration messages if source configuration is not released during DAPS handover.
SCellAdd	The field is mandatory present upon SCell addition; otherwise it is absent, Need M.
SCellAddMod	The field is mandatory present upon SCell addition; otherwise it is optionally present, need M.
SCellAddSync	The field is optionally present, Need N, in the masterCellGroup and, if the SCG is not indicated as deactivated, in the secondaryCellGroup in case of SCell addition, reconfiguration with sync, and resuming an RRC connection. It is absent otherwise.
SCG	The field is mandatory present in an SpCellConfig for the PSCell. It is absent otherwise.
SCG-Opt	The field is optionally present, Need M, in an SpCellConfig for the PSCell. It is absent otherwise.

NOTE: In case of change of AS security key derived from S-K_gNB/S-K_eNB, if reconfigurationWithSync is not included in the masterCellGroup, the network releases all existing MCG RLC bearers associated with a radio bearer with keyToUse set to secondary. In case of change of AS security key derived from K_gNB/K_eNB, if reconfigurationWithSync is not included in the secondaryCellGroup, the network releases all existing SCG RLC bearers associated with a radio bearer with keyToUse set to primary.

– CellGroupId

The IE CellGroupId is used to identify a cell group. Value 0 identifies the master cell group. Other values identify secondary cell groups. In this version of the specification only values 0 and 1 are supported.

CellGroupId information element

— ASN1START

— TAG-CELLGROUPID-START

CellGroupId ::= INTEGER (0.. maxSecondaryCellGroups)

— TAG-CELLGROUPID-STOP

— ASN1STOP

– CellIdentity

The IE CellIdentity is used to unambiguously identify a cell within a PLMN/SNPN.

CellIdentity information element

— ASN1START

— TAG-CELLIDENTITY-START

CellIdentity ::= BIT STRING (SIZE (36))

— TAG-CELLIDENTITY-STOP

— ASN1STOP

– CellReselectionPriority

The IE CellReselectionPriority concerns the absolute priority of the concerned carrier frequency, as used by the cell reselection procedure. Corresponds to parameter "priority" in TS 38.304 [20]. Value 0 means lowest priority. The UE behaviour for the case the field is absent, if applicable, is specified in TS 38.304 [20].

CellReselectionPriority information element

— ASN1START

— TAG-CELLRESELECTIONPRIORITY-START

CellReselectionPriority ::= INTEGER (0..7)

— TAG-CELLRESELECTIONPRIORITY-STOP

— ASN1STOP

– CellReselectionSubPriority

The IE CellReselectionSubPriority indicates a fractional value to be added to the value of cellReselectionPriority to obtain the absolute priority of the concerned carrier frequency for E-UTRA and NR. Value oDot2 corresponds to 0.2, value oDot4 corresponds to 0.4 and so on.

CellReselectionSubPriority information element

— ASN1START

— TAG-CELLRESELECTIONSUBPRIORITY-START

CellReselectionSubPriority ::= ENUMERATED {oDot2, oDot4, oDot6, oDot8}

— TAG-CELLRESELECTIONSUBPRIORITY-STOP

— ASN1STOP

– CFR-ConfigMulticast

The IE CFR-ConfigMulticast indicates UE specific common frequency resource configuration for multicast for one dedicated BWP.

CFR-ConfigMulticast information element

— ASN1START

— TAG-CFR-CONFIGMULTICAST-START

CFR-ConfigMulticast-r17::= SEQUENCE {

locationAndBandwidthMulticast-r17 INTEGER (0..37949) OPTIONAL, — Need S

pdcch-ConfigMulticast-r17 PDCCH-Config OPTIONAL, — Need M

pdsch-ConfigMulticast-r17 PDSCH-Config OPTIONAL, — Need M

sps-ConfigMulticastToAddModList-r17 SPS-ConfigMulticastToAddModList-r17 OPTIONAL, — Need N

sps-ConfigMulticastToReleaseList-r17 SPS-ConfigMulticastToReleaseList-r17 OPTIONAL — Need N

}

SPS-ConfigMulticastToAddModList-r17 ::= SEQUENCE (SIZE (1..8)) OF SPS-Config

SPS-ConfigMulticastToReleaseList-r17 ::= SEQUENCE (SIZE (1..8)) OF SPS-ConfigIndex-r16

— TAG-CFR-CONFIGMULTICAST-STOP

— ASN1STOP

CFR-ConfigMulticast field descriptions
locationAndBandwidthMulticast Frequency domain location and bandwidth for MBS multicast. The value of the field shall be interpreted as resource indicator value (RIV) as defined TS 38.214 [19] with assumptions as described in TS 38.213 [13], clause 12, i.e. setting N^size_BWP=275. The first PRB is a PRB determined by subcarrierSpacing of the associated BWP and offsetToCarrier corresponding to this subcarrier spacing. If not configured, the UE applies the value of locationAndBandwidth of the DL BWP in which the cfr-ConfigMulticast is configured.
pdcch-ConfigMulticast UE specific group-common PDCCH configuration for MBS multicast for one CFR.
pdsch-ConfigMulticast UE specific group-common PDSCH configuration for MBS multicast for one CFR.
sps-ConfigMulticastToAddModList Indicates a list of one or more DL SPS configurations for MBS multicast.
sps-ConfigMulticastToReleaseList Indicates a list of one or more DL SPS configurations to be released. The NW may release a SPS configuration at any time.

– CGI-InfoEUTRA

The IE CGI-InfoEUTRA indicates EUTRA cell access related information, which is reported by the UE as part of E-UTRA report CGI procedure.

CGI-InfoEUTRA information element

— ASN1START

— TAG-CGI-INFOEUTRA-START

CGI-InfoEUTRA ::= SEQUENCE {

cgi-info-EPC SEQUENCE {

cgi-info-EPC-legacy CellAccessRelatedInfo-EUTRA-EPC,

cgi-info-EPC-list SEQUENCE (SIZE (1..maxPLMN)) OF CellAccessRelatedInfo-EUTRA-EPC OPTIONAL

} OPTIONAL,

cgi-info-5GC SEQUENCE (SIZE (1..maxPLMN)) OF CellAccessRelatedInfo-EUTRA-5GC OPTIONAL,

freqBandIndicator FreqBandIndicatorEUTRA,

multiBandInfoList MultiBandInfoListEUTRA OPTIONAL,

freqBandIndicatorPriority ENUMERATED {true} OPTIONAL

}

— TAG-CGI-INFOEUTRA-STOP

— ASN1STOP

– CGI-InfoEUTRALogging

The IE CGI-InfoEUTRALogging indicates EUTRA cell related information, which is reported by the UE as part of RLF reporting procedure.

CGI-InfoEUTRALogging information element

— ASN1START

— TAG-CGI-INFOEUTRALOGGING-START

CGI-InfoEUTRALogging ::= SEQUENCE {

plmn-Identity-eutra-5gc PLMN-Identity OPTIONAL,

trackingAreaCode-eutra-5gc TrackingAreaCode OPTIONAL,

cellIdentity-eutra-5gc BIT STRING (SIZE (28)) OPTIONAL,

plmn-Identity-eutra-epc PLMN-Identity OPTIONAL,

trackingAreaCode-eutra-epc BIT STRING (SIZE (16)) OPTIONAL,

cellIdentity-eutra-epc BIT STRING (SIZE (28)) OPTIONAL

}

— TAG-CGI-INFOEUTRALOGGING-STOP

— ASN1STOP

CGI-InfoEUTRALogging field descriptions

cellIdentity-eutra-epc, cellIdentity-eutra-5GC Unambiguously identify a cell within the context of the PLMN. It belongs the first PLMN entry of plmn-IdentityList (when connected to EPC) or of plmn-IdentityList-r15 (when connected to 5GC) in SystemInformationBlockType1.

plmn-Identity-eutra-epc, plmn-Identity-eutra-5GC Identifies the PLMN of the cell for the reported cellIdentity: the first PLMN entry of plmn-IdentityList (when connected to EPC) or of plmn-IdentityList-r15 (when connected to 5GC) in SystemInformationBlockType1 that contained the reported cellIdentity.

trackingAreaCode-eutra-epc, trackingAreaCode-eutra-5gc Indicates Tracking Area Code to which the cell indicated by cellIdentity-eutra-epc, cellIdentity-eutra-5GC belongs.

– CGI-InfoNR

The IE CGI-InfoNR indicates cell access related information, which is reported by the UE as part of report CGI procedure.

CGI-InfoNR information element

— ASN1START

— TAG-CGI-INFO-NR-START

CGI-InfoNR ::= SEQUENCE {

plmn-IdentityInfoList PLMN-IdentityInfoList OPTIONAL,

frequencyBandList MultiFrequencyBandListNR OPTIONAL,

noSIB1 SEQUENCE {

ssb-SubcarrierOffset INTEGER (0..15),

pdcch-ConfigSIB1 PDCCH-ConfigSIB1

} OPTIONAL,

…,

[[

npn-IdentityInfoList-r16 NPN-IdentityInfoList-r16 OPTIONAL

]],

[[

cellReservedForOtherUse-r16 ENUMERATED {true} OPTIONAL

]]

}

— TAG-CGI-INFO-NR-STOP

— ASN1STOP

CGI-InfoNR field descriptions
noSIB1 Contains ssb-SubcarrierOffset and pdcch-ConfigSIB1 fields acquired by the UE from MIB of the cell for which report CGI procedure was requested by the network in case SIB1 was not broadcast by the cell.
cellReservedForOtherUse Contains cellReservedForOtherUse field acquired by the UE that supports nr-CGI-Reporting-NPN from SIB1 of the cell for which report CGI procedure was requested by the network.

– CGI-Info-Logging

The IE CGI-Info-Logging indicates the NR Cell Global Identifier (NCGI) for logging purposes (e.g. RLF report), the globally unique identity, and the TAC information of a cell in NR.

CGI-Info-Logging information element

— ASN1START

— TAG-CGI-INFO-LOGGING-START

CGI-Info-Logging-r16 ::= SEQUENCE {

plmn-Identity-r16 PLMN-Identity,

cellIdentity-r16 CellIdentity,

trackingAreaCode-r16 TrackingAreaCode OPTIONAL

}

— TAG-CGI-INFO-LOGGING-STOP

— ASN1STOP

CGI-Info-Logging field descriptions

cellIdentity Unambiguously identify a cell within the context of the PLMN. It belongs the first PLMN-IdentityInfo IE of PLMN-IdentityInfoList in SIB1.

plmn-Identity Identifies the PLMN of the cell for the reported cellIdentity: the first PLMN entry of plmn-IdentityList (in SIB1) in the instance of PLMN-IdentityInfoList that contained the reported cellIdentity.

trackingAreaCode Indicates Tracking Area Code to which the cell indicated by cellIdentity field belongs.

– CLI-RSSI-Range

The IE CLI-RSSI-Range specifies the value range used in CLI-RSSI measurements and thresholds. The integer value for CLI-RSSI measurements is according to Table 10.1.22.2.2-1 in TS 38.133 [14].

CLI-RSSI-Range information element

— ASN1START

— TAG-CLI-RSSI-RANGE-START

CLI-RSSI-Range-r16 ::= INTEGER(0..76)

— TAG-CLI-RSSI-RANGE-STOP

— ASN1STOP

– CodebookConfig

The IE CodebookConfig is used to configure codebooks of Type-I and Type-II (see TS 38.214 [19], clause 5.2.2.2)

CodebookConfig information element

— ASN1START

— TAG-CODEBOOKCONFIG-START

CodebookConfig ::= SEQUENCE {

codebookType CHOICE {

type1 SEQUENCE {

subType CHOICE {

typeI-SinglePanel SEQUENCE {

nrOfAntennaPorts CHOICE {

two SEQUENCE {

twoTX-CodebookSubsetRestriction BIT STRING (SIZE (6))

},

moreThanTwo SEQUENCE {

n1-n2 CHOICE {

two-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (8)),

two-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (64)),

four-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (16)),

three-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (96)),

six-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (24)),

four-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (128)),

eight-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (32)),

four-three-TypeI-SinglePanel-Restriction BIT STRING (SIZE (192)),

six-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (192)),

twelve-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (48)),

four-four-TypeI-SinglePanel-Restriction BIT STRING (SIZE (256)),

eight-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (256)),

sixteen-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (64))

},

typeI-SinglePanel-codebookSubsetRestriction-i2 BIT STRING (SIZE (16)) OPTIONAL — Need R

}

},

typeI-SinglePanel-ri-Restriction BIT STRING (SIZE (8))

},

typeI-MultiPanel SEQUENCE {

ng-n1-n2 CHOICE {

two-two-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (8)),

two-four-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (16)),

four-two-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (8)),

two-two-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (64)),

two-eight-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (32)),

four-four-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (16)),

two-four-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (128)),

four-two-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (64))

},

ri-Restriction BIT STRING (SIZE (4))

}

},

codebookMode INTEGER (1..2)

},

type2 SEQUENCE {

subType CHOICE {

typeII SEQUENCE {

n1-n2-codebookSubsetRestriction CHOICE {

two-one BIT STRING (SIZE (16)),

two-two BIT STRING (SIZE (43)),

four-one BIT STRING (SIZE (32)),

three-two BIT STRING (SIZE (59)),

six-one BIT STRING (SIZE (48)),

four-two BIT STRING (SIZE (75)),

eight-one BIT STRING (SIZE (64)),

four-three BIT STRING (SIZE (107)),

six-two BIT STRING (SIZE (107)),

twelve-one BIT STRING (SIZE (96)),

four-four BIT STRING (SIZE (139)),

eight-two BIT STRING (SIZE (139)),

sixteen-one BIT STRING (SIZE (128))

},

typeII-RI-Restriction BIT STRING (SIZE (2))

},

typeII-PortSelection SEQUENCE {

portSelectionSamplingSize ENUMERATED {n1, n2, n3, n4} OPTIONAL, — Need R

typeII-PortSelectionRI-Restriction BIT STRING (SIZE (2))

}

},

phaseAlphabetSize ENUMERATED {n4, n8},

subbandAmplitude BOOLEAN,

numberOfBeams ENUMERATED {two, three, four}

}

}

}

CodebookConfig-r16 ::= SEQUENCE {

codebookType CHOICE {

type2 SEQUENCE {

subType CHOICE {

typeII-r16 SEQUENCE {

n1-n2-codebookSubsetRestriction-r16 CHOICE {

two-one BIT STRING (SIZE (16)),

two-two BIT STRING (SIZE (43)),

four-one BIT STRING (SIZE (32)),

three-two BIT STRING (SIZE (59)),

six-one BIT STRING (SIZE (48)),

four-two BIT STRING (SIZE (75)),

eight-one BIT STRING (SIZE (64)),

four-three BIT STRING (SIZE (107)),

six-two BIT STRING (SIZE (107)),

twelve-one BIT STRING (SIZE (96)),

four-four BIT STRING (SIZE (139)),

eight-two BIT STRING (SIZE (139)),

sixteen-one BIT STRING (SIZE (128))

},

typeII-RI-Restriction-r16 BIT STRING (SIZE(4))

},

typeII-PortSelection-r16 SEQUENCE {

portSelectionSamplingSize-r16 ENUMERATED {n1, n2, n3, n4},

typeII-PortSelectionRI-Restriction-r16 BIT STRING (SIZE (4))

}

},

numberOfPMI-SubbandsPerCQI-Subband-r16 INTEGER (1..2),

paramCombination-r16 INTEGER (1..8)

}

}

}

CodebookConfig-r17 ::= SEQUENCE {

codebookType CHOICE {

type1 SEQUENCE {

typeI-SinglePanel-Group1-r17 SEQUENCE {

nrOfAntennaPorts CHOICE {

two SEQUENCE {

twoTX-CodebookSubsetRestriction1-r17 BIT STRING (SIZE (6))

},

moreThanTwo SEQUENCE {

n1-n2 CHOICE {

two-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (8)),

two-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (64)),

four-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (16)),

three-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (96)),

six-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (24)),

four-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (128)),

eight-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (32)),

four-three-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (192)),

six-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (192)),

twelve-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (48)),

four-four-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (256)),

eight-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (256)),

sixteen-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (64))

}

}

}

} OPTIONAL, — Need R

typeI-SinglePanel-Group2-r17 SEQUENCE {

nrOfAntennaPorts CHOICE {

two SEQUENCE {

twoTX-CodebookSubsetRestriction2-r17 BIT STRING (SIZE (6))

},

moreThanTwo SEQUENCE {

n1-n2 CHOICE {

two-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (8)),

two-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (64)),

four-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (16)),

three-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (96)),

six-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (24)),

four-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (128)),

eight-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (32)),

four-three-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (192)),

six-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (192)),

twelve-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (48)),

four-four-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (256)),

eight-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (256)),

sixteen-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (64))

}

}

}

} OPTIONAL, — Need R

typeI-SinglePanel-ri-RestrictionSTRP-r17 BIT STRING (SIZE (8)) OPTIONAL, — Need R

typeI-SinglePanel-ri-RestrictionSDM-r17 BIT STRING (SIZE (4)) OPTIONAL — Need R

},

type2 SEQUENCE {

typeII-PortSelection-r17 SEQUENCE {

paramCombination-r17 INTEGER (1..8),

valueOfN-r17 ENUMERATED {n2, n4} OPTIONAL, — Need R

numberOfPMI-SubbandsPerCQI-Subband-r17 INTEGER(1..2) OPTIONAL, — Need R

typeII-PortSelectionRI-Restriction-r17 BIT STRING (SIZE (4))

}

}

}

}

— TAG-CODEBOOKCONFIG-STOP

— ASN1STOP

CodebookConfig field descriptions

codebookMode CodebookMode as specified in TS 38.214 [19], clause 5.2.2.2.2.

codebookType CodebookType including possibly sub-types and the corresponding parameters for each (see TS 38.214 [19], clause 5.2.2.2).

n1-n2-codebookSubsetRestriction Number of antenna ports in first (n1) and second (n2) dimension and codebook subset restriction (see TS 38.214 [19] clause 5.2.2.2.3). Number of bits for codebook subset restriction is CEIL(log2(nchoosek(O1*O2,4)))+8*n1*n2 where nchoosek(a,b) = a!/(b!(a-b)!).

n1-n2 Number of antenna ports in first (n1) and second (n2) dimension and codebook subset restriction (see TS 38.214 [19] clause 5.2.2.2.1).

ng-n1-n2 Codebook subset restriction for Type I Multi-panel codebook (see TS 38.214 [19], clause 5.2.2.2.2).

numberOfBeams Number of beams, L, used for linear combination.

numberOfPMI-SubbandsPerCQI-Subband Field indicates how PMI subbands are defined per CQI subband according to TS 38.214 [19], clause 5.2.2.2.5, and 5.2.2.2.7.

paramCombination Field describes supported parameter combination (M, , ) as specified in TS 38.214.

phaseAlphabetSize The size of the PSK alphabet, QPSK or 8-PSK.

portSelectionSamplingSize The size of the port selection codebook (parameter d), see TS 38.214 [19] clause 5.2.2.2.6.

ri-Restriction Restriction for RI for TypeI-MultiPanel-RI-Restriction (see TS 38.214 [19], clause 5.2.2.2.2).

subbandAmplitude If subband amplitude reporting is activated (true).

twoTX-CodebookSubsetRestriction Codebook subset restriction for 2TX codebook (see TS 38.214 [19] clause 5.2.2.2.1).

typeI-SinglePanel-codebookSubsetRestriction-i2 i2 codebook subset restriction for Type I Single-panel codebook used when reportQuantity is CRI/Ri/i1/CQI (see TS 38.214 [19] clause 5.2.2.2.1).

typeI-SinglePanel-ri-Restriction Restriction for RI for TypeI-SinglePanel-RI-Restriction (see TS 38.214 [19], clause 5.2.2.2.1).

typeI-SinglePanel-Group1, typeI-SinglePanel-Group2 Configures codebooks for CSI calculation when UE is configured with two CMR Groups with CMRGroupingAndPairing in the NZP-CSI-RS-ResourceSet associated with the CSI-ReportConfig. Network configures the same number of ports for both codebooks.

typeI-SinglePanel-ri-RestrictionSDM, typeI-SinglePanel-ri-RestrictionSTRP Restriction for RI for N Resource Pairs when two CMR Groups are configured with CMRGroupingAndPairing in the NZP-CSI-RS-ResourceSet associated with the CSI-ReportConfig (see TS 38.214 [19], clause 5.2.1.4.2).

typeII-PortSelectionRI-Restriction Restriction for RI for TypeII-PortSelection-RI-Restriction (see TS 38.214 [19], clauses 5.2.2.2.4 and 5.2.2.2.6).

typeII-RI-Restriction Restriction for RI for TypeII-RI-Restriction (see TS 38.214 [19], clauses 5.2.2.2.3 and 5.2.2.2.5).

valueOfN Field provides the value of parameter N as specified in TS 38.214 [19], clause 5.2.2.2.7. The field is present only when M=2 set by paramCombination, see TS 38.214 [19].

– CommonLocationInfo

The IE CommonLocationInfo is used to transfer detailed location information available at the UE to correlate measurements and UE position information.

CommonLocationInfo information element

— ASN1START

— TAG-COMMONLOCATIONINFO-START

CommonLocationInfo-r16 ::= SEQUENCE {

gnss-TOD-msec-r16 OCTET STRING OPTIONAL,

locationTimestamp-r16 OCTET STRING OPTIONAL,

locationCoordinate-r16 OCTET STRING OPTIONAL,

locationError-r16 OCTET STRING OPTIONAL,

locationSource-r16 OCTET STRING OPTIONAL,

velocityEstimate-r16 OCTET STRING OPTIONAL

}

— TAG-COMMONLOCATIONINFO-STOP

— ASN1STOP

CommonLocationInfo field descriptions

gnss-TOD-msec Parameter type gnss-TOD-msec defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.

locationTimeStamp Parameter type DisplacementTimeStamp defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.

locationCoordinate Parameter type LocationCoordinates defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.

locationError Parameter LocationError defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.

locationSource Parameter LocationSource defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.

velocityEstimate Parameter type Velocity defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.

– CondReconfigId

The IE CondReconfigId is used to identify a CHO, CPA or CPC configuration.

CondReconfigId information element

— ASN1START

— TAG-CONDRECONFIGID-START

CondReconfigId-r16 ::= INTEGER (1.. maxNrofCondCells-r16)

— TAG-CONDRECONFIGID-STOP

— ASN1STOP

– CondReconfigToAddModList

The IE CondReconfigToAddModList concerns a list of conditional reconfigurations to add or modify, with for each entry the condReconfigId and the associated condExecutionCond/condExecutionCondSCG and condRRCReconfig.

CondReconfigToAddModList information element

— ASN1START

— TAG-CONDRECONFIGTOADDMODLIST-START

CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16

CondReconfigToAddMod-r16 ::= SEQUENCE {

condReconfigId-r16 CondReconfigId-r16,

condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, — Need M

condRRCReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, — Cond condReconfigAdd

…,

[[

condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL — Need M

]]

}

CondReconfigExecCondSCG-r17 ::= SEQUENCE (SIZE (1..2)) OF MeasId

— TAG-CONDRECONFIGTOADDMODLIST-STOP

— ASN1STOP

CondReconfigToAddMod field descriptions
condExecutionCond The execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for CHO, CPA, intra-SN CPC without MN involvement or MN initiated inter-SN CPC. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject. For CHO, if network configures condEventD1 or condEventT1 for a candidate cell network configures a second triggering event condEventA3, condEventA4 or condEventA5 for the same candidate cell. Network does not configure both condEventD1 and condEventT1 for the same candidate cell.
condExecutionCondSCG Contains execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for SN initiated inter-SN CPC. The Meas Ids refer to the measConfig associated with the SCG. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject. For each condReconfigId, the network always configures either condExecutionCond or condExecutionCondSCG (not both).
condRRCReconfig The RRCReconfiguration message to be applied when the condition(s) are fulfilled. The RRCReconfiguration message contained in condRRCReconfig cannot contain the field conditionalReconfiguration or the field daps-Config.

Conditional Presence	Explanation
condReconfigAdd	The field is mandatory present when a condReconfigId is being added. Otherwise the field is optional, need M.

– ConditionalReconfiguration

The IE ConditionalReconfiguration is used to add, modify and release the configuration of conditional reconfiguration.

ConditionalReconfiguration information element

— ASN1START

— TAG-CONDITIONALRECONFIGURATION-START

ConditionalReconfiguration-r16 ::= SEQUENCE {

attemptCondReconfig-r16 ENUMERATED {true} OPTIONAL, — Cond CHO

condReconfigToRemoveList-r16 CondReconfigToRemoveList-r16 OPTIONAL, — Need N

condReconfigToAddModList-r16 CondReconfigToAddModList-r16 OPTIONAL, — Need N

…

}

CondReconfigToRemoveList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigId-r16

— TAG-CONDITIONALRECONFIGURATION-STOP

— ASN1STOP

ConditionalReconfiguration field descriptions
attemptCondReconfig If present, the UE shall perform conditional reconfiguration if selected cell is a target candidate cell and it is the first cell selection after failure as described in clause 5.3.7.3.
condReconfigToAddModList List of the configuration of candidate SpCells to be added or modified for CHO, CPA or CPC.
condReconfigToRemoveList List of the configuration of candidate SpCells to be removed.

Conditional Presence	Explanation
CHO	The field is optional present, Need R, if the UE is configured with at least a candidate SpCell for CHO. Otherwise the field is not present.

– ConfiguredGrantConfig

The IE ConfiguredGrantConfig is used to configure uplink transmission without dynamic grant according to two possible schemes. The actual uplink grant may either be configured via RRC (type1) or provided via the PDCCH (addressed to CS-RNTI) (type2). Multiple Configured Grant configurations may be configured in one BWP of a serving cell.

ConfiguredGrantConfig information element

— ASN1START

— TAG-CONFIGUREDGRANTCONFIG-START

ConfiguredGrantConfig ::= SEQUENCE {

frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, — Need S

cg-DMRS-Configuration DMRS-UplinkConfig,

mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, — Need S

mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, — Need S

uci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH } OPTIONAL, — Need M

resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch },

rbg-Size ENUMERATED {config2} OPTIONAL, — Need S

powerControlLoopToUse ENUMERATED {n0, n1},

p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,

transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, — Need S

nrofHARQ-Processes INTEGER(1..16),

repK ENUMERATED {n1, n2, n4, n8},

repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, — Need R

periodicity ENUMERATED {

sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,

sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,

sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,

sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,

sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,

sym1280x12, sym2560x12

},

configuredGrantTimer INTEGER (1..64) OPTIONAL, — Need R

rrc-ConfiguredUplinkGrant SEQUENCE {

timeDomainOffset INTEGER (0..5119),

timeDomainAllocation INTEGER (0..15),

frequencyDomainAllocation BIT STRING (SIZE(18)),

antennaPort INTEGER (0..31),

dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, — Need R

precodingAndNumberOfLayers INTEGER (0..63),

srs-ResourceIndicator INTEGER (0..15) OPTIONAL, — Need R

mcsAndTBS INTEGER (0..31),

frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, — Need R

pathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),

…,

[[

pusch-RepTypeIndicator-r16 ENUMERATED {pusch-RepTypeA,pusch-RepTypeB} OPTIONAL, — Need M

frequencyHoppingPUSCH-RepTypeB-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, — Cond RepTypeB

timeReferenceSFN-r16 ENUMERATED {sfn512} OPTIONAL — Need S

]],

[[

pathlossReferenceIndex2-r17 INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1) OPTIONAL, — Need R

srs-ResourceIndicator2-r17 INTEGER (0..15) OPTIONAL, — Need R

precodingAndNumberOfLayers2-r17 INTEGER (0..63) OPTIONAL, — Need R

timeDomainAllocation-v1710 INTEGER (16..63) OPTIONAL, — Need M

timeDomainOffset-r17 INTEGER (0..40959) OPTIONAL, — Need R

cg-SDT-Configuration-r17 CG-SDT-Configuration-r17 OPTIONAL — Need M

]]

} OPTIONAL, — Need R

…,

[[

cg-RetransmissionTimer-r16 INTEGER (1..64) OPTIONAL, — Need R

cg-minDFI-Delay-r16 ENUMERATED

{sym7, sym1x14, sym2x14, sym3x14, sym4x14, sym5x14, sym6x14, sym7x14, sym8x14,

sym9x14, sym10x14, sym11x14, sym12x14, sym13x14, sym14x14,sym15x14, sym16x14

} OPTIONAL, — Need R

cg-nrofPUSCH-InSlot-r16 INTEGER (1..7) OPTIONAL, — Need R

cg-nrofSlots-r16 INTEGER (1..40) OPTIONAL, — Need R

cg-StartingOffsets-r16 CG-StartingOffsets-r16 OPTIONAL, — Need R

cg-UCI-Multiplexing-r16 ENUMERATED {enabled} OPTIONAL, — Need R

cg-COT-SharingOffset-r16 INTEGER (1..39) OPTIONAL, — Need R

betaOffsetCG-UCI-r16 INTEGER (0..31) OPTIONAL, — Need R

cg-COT-SharingList-r16 SEQUENCE (SIZE (1..1709)) OF CG-COT-Sharing-r16 OPTIONAL, — Need R

harq-ProcID-Offset-r16 INTEGER (0..15) OPTIONAL, — Need M

harq-ProcID-Offset2-r16 INTEGER (0..15) OPTIONAL, — Need M

configuredGrantConfigIndex-r16 ConfiguredGrantConfigIndex-r16 OPTIONAL, — Cond CG-List

configuredGrantConfigIndexMAC-r16 ConfiguredGrantConfigIndexMAC-r16 OPTIONAL, — Cond CG-IndexMAC

periodicityExt-r16 INTEGER (1..5120) OPTIONAL, — Need R

startingFromRV0-r16 ENUMERATED {on, off} OPTIONAL, — Need R

phy-PriorityIndex-r16 ENUMERATED {p0, p1} OPTIONAL, — Need R

autonomousTx-r16 ENUMERATED {enabled} OPTIONAL — Cond LCH-BasedPrioritization

]],

[[

cg-betaOffsetsCrossPri0-r17 SetupRelease { BetaOffsetsCrossPriSelCG-r17 } OPTIONAL, — Need M

cg-betaOffsetsCrossPri1-r17 SetupRelease { BetaOffsetsCrossPriSelCG-r17 } OPTIONAL, — Need M

mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, — Cond SRSsets

sequenceOffsetForRV-r17 INTEGER (0..3) OPTIONAL, — Need R

p0-PUSCH-Alpha2-r17 P0-PUSCH-AlphaSetId OPTIONAL, — Need R

powerControlLoopToUse2-r17 ENUMERATED {n0, n1} OPTIONAL, — Need R

cg-COT-SharingList-r17 SEQUENCE (SIZE (1..50722)) OF CG-COT-Sharing-r17 OPTIONAL, — Need R

periodicityExt-r17 INTEGER (1..40960) OPTIONAL, — Need R

repK-v1710 ENUMERATED {n12, n16, n24, n32} OPTIONAL, — Need R

nrofHARQ-Processes-v1700 INTEGER(17..32) OPTIONAL, — Need M

harq-ProcID-Offset2-v1700 INTEGER (16..31) OPTIONAL, — Need R

configuredGrantTimer-v1700 INTEGER(33..288) OPTIONAL, — Need R

cg-minDFI-Delay-v1710 INTEGER (238..3584) OPTIONAL — Need R

]]

}

CG-UCI-OnPUSCH ::= CHOICE {

dynamic SEQUENCE (SIZE (1..4)) OF BetaOffsets,

semiStatic BetaOffsets

}

CG-COT-Sharing-r16 ::= CHOICE {

noCOT-Sharing-r16 NULL,

cot-Sharing-r16 SEQUENCE {

duration-r16 INTEGER (1..39),

offset-r16 INTEGER (1..39),

channelAccessPriority-r16 INTEGER (1..4)

}

}

CG-COT-Sharing-r17 ::= CHOICE {

noCOT-Sharing-r17 NULL,

cot-Sharing-r17 SEQUENCE {

duration-r17 INTEGER (1..319),

offset-r17 INTEGER (1..319)

}

}

CG-StartingOffsets-r16 ::= SEQUENCE {

cg-StartingFullBW-InsideCOT-r16 SEQUENCE (SIZE (1..7)) OF INTEGER (0..6) OPTIONAL, — Need R

cg-StartingFullBW-OutsideCOT-r16 SEQUENCE (SIZE (1..7)) OF INTEGER (0..6) OPTIONAL, — Need R

cg-StartingPartialBW-InsideCOT-r16 INTEGER (0..6) OPTIONAL, — Need R

cg-StartingPartialBW-OutsideCOT-r16 INTEGER (0..6) OPTIONAL — Need R

}

BetaOffsetsCrossPriSelCG-r17 ::= CHOICE {

dynamic-r17 SEQUENCE (SIZE (1..4)) OF BetaOffsetsCrossPri-r17,

semiStatic-r17 BetaOffsetsCrossPri-r17

}

CG-SDT-Configuration-r17 ::= SEQUENCE {

cg-SDT-RetransmissionTimer INTEGER (1..64) OPTIONAL, — Need R

sdt-SSB-Subset-r17 CHOICE {

shortBitmap-r17 BIT STRING (SIZE (4)),

mediumBitmap-r17 BIT STRING (SIZE (8)),

longBitmap-r17 BIT STRING (SIZE (64))

} OPTIONAL, — Need S

sdt-SSB-PerCG-PUSCH-r17 ENUMERATED {oneEighth, oneFourth, half, one, two, four, eight, sixteen} OPTIONAL, — Need M

sdt-P0-PUSCH-r17 INTEGER (-16..15) OPTIONAL, — Need M

sdt-Alpha-r17 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, — Need M

sdt-DMRS-Ports-r17 CHOICE {

dmrsType1-r17 BIT STRING (SIZE (8)),

dmrsType2-r17 BIT STRING (SIZE (12))

} OPTIONAL, — Need M

sdt-NrofDMRS-Sequences-r17 INTEGER (1..2) OPTIONAL — Need M

}

— TAG-CONFIGUREDGRANTCONFIG-STOP

— ASN1STOP

ConfiguredGrantConfig field descriptions

antennaPort Indicates the antenna port(s) to be used for this configuration, and the maximum bitwidth is 5. See TS 38.214 [19], clause 6.1.2, and TS 38.212 [17], clause 7.3.1. The UE ignores this field in case of CG-SDT.

autonomousTx If this field is present, the Configured Grant configuration is configured with autonomous transmission, see TS 38.321 [3].

betaOffsetCG-UCI Beta offset for CG-UCI in CG-PUSCH, see TS 38.213 [13], clause 9.3

cg-betaOffsetsCrossPri0, cg-betaOffsetsCrossPri1 Selection between and configuration of dynamic and semi-static beta-offset for multiplexing HARQ-ACK in CG-PUSCH with different priorities. The field cg-betaOffsetsCrossPri0 indicates multiplexing LP HARQ-ACK in HP CG-PUSCH. This field is configured only if phy-PriorityIndex-r16 is configured with value p1. The field cg-betaOffsetsCrossPri1 indicates multiplexing HP HARQ-ACK in LP CG-PUSCH. This field is configured only if phy-PriorityIndex-r16 is configured with value p0.

cg-COT-SharingList Indicates a table for COT sharing combinations (see 37.213 [48], clause 4.1.3). One row of the table can be set to noCOT-Sharing to indicate that there is no channel occupancy sharing. If the cg-RetransmissionTimer-r16 is configured and the UE operates as an initiating device in semi-static channel access mode (see TS 37.213 [48], clause 4.3), then cg-COT-SharingList-r16 is configured.

cg-COT-SharingOffset Indicates the offset from the end of the slot where the COT sharing indication in UCI is enabled where the offset in symbols is equal to 14*n, where n is the signaled value for cg-COT-SharingOffset. Applicable when ul-toDL-COT-SharingED-Threshold-r16 is not configured (see 37.213 [48], clause 4.1.3).

cg-DMRS-Configuration DMRS configuration (see TS 38.214 [19], clause 6.1.2.3).

cg-minDFI-Delay Indicates the minimum duration (in unit of symbols) from the ending symbol of the PUSCH to the starting symbol of the PDCCH containing the downlink feedback indication (DFI) carrying HARQ-ACK for this PUSCH. The HARQ-ACK received before this minimum duration is not considered as valid for this PUSCH (see TS 38.213 [13], clause 10.5). The following minimum duration values are supported, depending on the configured subcarrier spacing [symbols]: 15 kHz: 7, m*14, where m = {1, 2, 3, 4} 30 kHz: 7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8} 60 kHz: 7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16} 120 kHz: 7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32} 480 kHz: m*14, where m = {2, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64, 68, 72, 76, 80, 84, 88, 92, 96, 100, 104, 108, 112, 116, 120, 124, 128} 960 kHz: m*14, where m = {4, 8, 16, 24, 32, 40, 48, 56, 64, 72, 80, 88, 96, 104, 112, 120, 128, 136, 144, 152, 160, 168, 176, 184, 192, 200, 208, 216, 224, 232, 240, 248, 256}

cg-nrofPUSCH-InSlot Indicates the number of consecutive PUSCH configured to CG within a slot where the SLIV indicating the first PUSCH and additional PUSCH appended with the same length (see TS 38.214 [19], clause 6.1.2.3). The network can only configure this field if cg-RetransmissionTimer is configured.

cg-nrofSlots Indicates the number of allocated slots in a configured grant periodicity following the time instance of configured grant offset (see TS 38.214 [19], clause 6.1.2.3). The network can only configure this field if cg-RetransmissionTimer is configured.

cg-RetransmissionTimer Indicates the initial value of the configured retransmission timer (see TS 38.321 [3]) in multiples of periodicity. The value of cg-RetransmissionTimer is always less than or equal to the value of configuredGrantTimer. This field is always configured together with harq-ProcID-Offset. This field is not configured for operation in licensed spectrum or simultaneously with harq-ProcID-Offset2.

cg-StartingOffsets This field is not applicable for a UE which is allowed to operate as an initiating device in semi-static channel access mode, i.e., not applicable for a UE configured with UE FFP parameters (e.g. period, offset) regardless whether the UE would initiate its own COT or would share gNB’s COT.

cg-UCI-Multiplexing If present, this field indicates that in the case of PUCCH overlapping with CG-PUSCH(s) within a PUCCH group, the CG-UCI and HARQ-ACK are jointly encoded (see TS 38.213 [13], clause 9).

configuredGrantConfigIndex Indicates the index of the Configured Grant configurations within the BWP.

configuredGrantConfigIndexMAC Indicates the index of the Configured Grant configurations within the MAC entity.

configuredGrantTimer Indicates the initial value of the configured grant timer (see TS 38.321 [3]) in multiples of periodicity. When cg-RetransmissonTimer is configured, if HARQ processes are shared among different configured grants on the same BWP, configuredGrantTimer * periodicity is set to the same value for the configurations that share HARQ processes on this BWP. The value of the extension configuredGrantTimer is 2 times the configured value.

dmrs-SeqInitialization The network configures this field if transformPrecoder is disabled or when the value of sdt-NrofDMRS-Sequences is set to 1. Otherwise, the field is absent.

frequencyDomainAllocation Indicates the frequency domain resource allocation, see TS 38.214 [19], clause 6.1.2, and TS 38.212 [17], clause 7.3.1).

frequencyHopping The value intraSlot enables ‘Intra-slot frequency hopping’ and the value interSlot enables ‘Inter-slot frequency hopping’. If the field is absent, frequency hopping is not configured. The field frequencyHopping applies to configured grant for ‘pusch-RepTypeA’ (see TS 38.214 [19], clause 6.3.1).

frequencyHoppingOffset Frequency hopping offset used when frequency hopping is enabled (see TS 38.214 [19], clause 6.1.2 and clause 6.3).

frequencyHoppingPUSCH-RepTypeB Indicates the frequency hopping scheme for Type 1 CG when pusch-RepTypeIndicator is set to ‘pusch-RepTypeB’ (see TS 38.214 [19], clause 6.1). The value interRepetition enables ‘Inter-repetition frequency hopping’, and the value interSlot enables ‘Inter-slot frequency hopping’. If the field is absent, the frequency hopping is not enabled for Type 1 CG.

harq-ProcID-Offset For operation with shared spectrum channel access configured with cg-RetransmissionTimer-r16, this configures the range of HARQ process IDs which can be used for this configured grant where the UE can select a HARQ process ID within [harq-procID-offset, .., (harq-procID-offset + nrofHARQ-Processes – 1)].

harq-ProcID-Offset2 Indicates the offset used in deriving the HARQ process IDs, see TS 38.321 [3], clause 5.4.1. This field is not configured together with cg-RetransmissionTimer-r16. If the field harq-ProcID-Offset2-v1700 is present, the UE shall ignore the harq-ProcID-Offset2-r16.

mappingPattern Indicates whether the UE should follow Cyclical mapping pattern or Sequential mapping pattern when two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage ‘codebook’ or ‘noncodebook’ for PUSCH transmission with a Type 1 configured grant and/or a Type 2 configured grant as described in clause 6.1.2.3 of TS 38.214 [19]

mcs-Table Indicates the MCS table the UE shall use for PUSCH without transform precoding. If the field is absent the UE applies the value qam64.

mcs-TableTransformPrecoder Indicates the MCS table the UE shall use for PUSCH with transform precoding. If the field is absent the UE applies the value qam64.

mcsAndTBS The modulation order, target code rate and TB size (see TS 38.214 [19], clause 6.1.2). The NW does not configure the values 28~31 in this version of the specification.

nrofHARQ-Processes The number of HARQ processes configured. It applies for both Type 1 and Type 2. See TS 38.321 [3], clause 5.4.1. If the UE is configured with nrofHARQ-Processes-v1700, the UE shall ignore nrofHARQ-Processes (without suffix).

pathlossReferenceIndex Indicates the reference signal index used as PUSCH pathloss reference (see TS 38.213 [13], clause 7.1.1). In case of CG-SDT, the UE does not use this field.

pathlossReferenceIndex2 Indicates the reference signal used as PUSCH pathloss reference for the second SRS resource set. When this field is present, pathlossReferenceIndex indicates the reference signal used as PUSCH pathloss reference for the first SRS resource set

p0-PUSCH-Alpha Index of the P0-PUSCH-AlphaSet to be used for this configuration.

p0-PUSCH-Alpha2 Index of the P0-PUSCH-AlphaSet to be used for second SRS resource set. If this field is present, the p0-PUSCH-Alpha provides index for the P0-PUSCH-AlphaSet to be used for first SRS resource set.

periodicity Periodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321 [3], clause 5.8.2). The following periodicities are supported depending on the configured subcarrier spacing [symbols]: 15 kHz: 2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 320, 640} 30 kHz: 2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 640, 1280} 60 kHz with normal CP 2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1280, 2560} 60 kHz with ECP: 2, 6, n*12, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1280, 2560} 120 kHz: 2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1024, 1280, 2560, 5120} 480 and 960 kHz: n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1024, 1280, 2560, 5120} In case of SDT, the network does not configure periodicity values less than 5ms.

periodicityExt This field is used to calculate the periodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321 [3], clause 5,8.2). If this field is present, the field periodicity is ignored. The following periodicites are supported depending on the configured subcarrier spacing [symbols]: 15 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 640. 30 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 1280. 60 kHz with normal CP: periodicityExt*14, where periodicityExt has a value between 1 and 2560. 60 kHz with ECP: periodicityExt*12, where periodicityExt has a value between 1 and 2560. 120 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 5120. 480 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 20480. 960 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 40960. In case of SDT, the network does not configure periodicity values less than 5ms.

phy-PriorityIndex Indicates the PHY priority of CG PUSCH at least for PHY-layer collision handling. Value p0 indicates low priority and value p1 indicates high priority. The network does not configure this for CG-SDT.

powerControlLoopToUse Closed control loop to apply (see TS 38.213 [13], clause 7.1.1).

powerControlLoopToUse2 Closed control loop to apply to second SRS resource set (see TS 38.213 [13], clause 7.1.1). If this field is present, the powerControlLoopToUse applies to the first SRS resource set.

precodingAndNumberOfLayers Indicates the precoding and number of layers (see TS 38.212 [17], clause 7.3.1.1.2, and TS 38.214 [19], clause 6.1.2.3). In case of CG-SDT, network sets this field to 1.

precodingAndNumberOfLayers2 Indicates the precoding and number of layers for the second SRS resource set. When this field is present, precodingAndNumberOfLayers indicated the precoding and number of layers for the first SRS resource set.

pusch-RepTypeIndicator Indicates whether UE follows the behavior for PUSCH repetition type A or the behavior for PUSCH repetition type B for each Type 1 configured grant configuration. The value pusch-RepTypeA enables the ‘PUSCH repetition type A’ and the value pusch-RepTypeB enables the ‘PUSCH repetition type B’ (see TS 38.214 [19], clause 6.1.2.3). The value pusch-RepTypeB is not configured simultaneously with cg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16. The network does not configure this field if cg-RetransmissionTimer-r16 is configured for CG operation with shared spectrum channel access.

rbg-Size Selection between configuration 1 and configuration 2 for RBG size for PUSCH. The UE does not apply this field if resourceAllocation is set to resourceAllocationType1. Otherwise, the UE applies the value config1 when the field is absent. Note: rbg-Size is used when the transformPrecoder parameter is disabled.

repK-RV The redundancy version (RV) sequence to use. See TS 38.214 [19], clause 6.1.2. The network configures this field if repetitions are used, i.e., if repK is set to n2, n4 or n8. This field is not configured when cg-RetransmissionTimer is configured. Otherwise, the field is absent.

repK Number of repetitions K, see TS 38.214 [19]. If the field repK-v1710 is present, the UE shall ignore the repK (without suffix).

resourceAllocation Configuration of resource allocation type 0 and resource allocation type 1. For Type 1 UL data transmission without grant, resourceAllocation should be resourceAllocationType0 or resourceAllocationType1.

rrc-ConfiguredUplinkGrant Configuration for "configured grant" transmission with fully RRC-configured UL grant (Type1). If this field is absent the UE uses UL grant configured by DCI addressed to CS-RNTI (Type2).

sequenceOffsetForRV Configures the RV offset for the starting RV for the first repetition (first actual repetition in PUSCH repetition Type B) towards the second ‘SRS resource set’ for PUSCH configured in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage ‘codebook’ or ‘noncodebook’.

srs-ResourceIndicator Indicates the SRS resource to be used. The network does not configure this for CG-SDT.

srs-ResourceIndicator2 Indicates the SRS resource to be used for the second SRS resource set. When this field is present, the srs-ResourceIndicator is used for the first SRS resource set.

startingFromRV0 This field is used to determine the initial transmission occasion of a transport block for a given RV sequence, see TS 38.214 [19], clause 6.1.2.3.1. The network does not configure this field if cg-RetransmissionTimer-r16 is configured for CG operation.

timeDomainAllocation, timeDomainAllocation-v1710 Indicates a combination of start symbol and length and PUSCH mapping type, see TS 38.214 [19], clause 6.1.2 and TS 38.212 [17], clause 7.3.1. If the field timeDomainAllocation-v1710 is present, the UE shall ignore timeDomainAllocation field (without suffix).

timeDomainOffset Offset related to the reference SFN indicated by timeReferenceSFN, see TS 38.321 [3], clause 5.8.2. timeDomainOffset-r17 is only applicable to 480 kHz and 960 kHz. If timeDomainOffset-r17 is present, the UE shall ignore timeDomainOffset (without suffix).

timeReferenceSFN Indicates SFN used for determination of the offset of a resource in time domain. The UE uses the closest SFN with the indicated number preceding the reception of the configured grant configuration, see TS 38.321 [3], clause 5.8.2. If the field timeReferenceSFN is not present, the reference SFN is 0.

transformPrecoder Enables or disables transform precoding for type1 and type2. If the field is absent, the UE enables or disables transform precoding in accordance with the field msg3-transformPrecoder in RACH-ConfigCommon from rach-ConfigCommon included directly within BWP configuration (i.e., not included in additionalRACH-ConfigList), see TS 38.214 [19], clause 6.1.3.

uci-OnPUSCH Selection between and configuration of dynamic and semi-static beta-offset. For Type 1 UL data transmission without grant, uci-OnPUSCH should be set to semiStatic. The network does not configure this for CG-SDT.

CG-COT-Sharing field descriptions

channelAccessPriority Indicates the Channel Access Priority Class that the gNB can assume when sharing the UE initiated COT (see 37.213 [48], clause 4.1.3).

duration Indicates the number of DL transmission slots within UE initiated COT (see 37.213 [48], clause 4.1.3).

offset Indicates the number of DL transmission slots from the end of the slot where CG-UCI is detected after which COT sharing can be used (see 37.213 [48], clause 4.1.3).

CG-StartingOffsets field descriptions

cg-StartingFullBW-InsideCOT A set of configured grant PUSCH transmission starting offsets which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation includes all interlaces in the allocated RB set(s) and the CG PUSCH resource is inside gNB COT (see TS 38.214 [19], clause 6.1.2.3).

cg-StartingFullBW-OutsideCOT A set of configured grant PUSCH transmission starting offset indices (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation includes all interlaces in the allocated RB set(s) and the CG PUSCH resource is outside gNB COT (see TS 38.214 [19], clause 6.1.2.3).

cg-StartingPartialBW-InsideCOT A set of configured grant PUSCH transmission starting offset index (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation does not include all interlaces in the allocated RB set(s) and the CG PUSCH resource is inside gNB COT (see TS 38.214 [19], clause 6.1.2.3).

cg-StartingPartialBW-OutsideCOT A set of configured grant PUSCH transmission starting offset index (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation does not include all interlaces in the allocated RB set(s) and the CG PUSCH resource is outside gNB COT (see TS 38.214 [19], clause 6.1.2.3).

CG-SDT-Configuration field descriptions

cg-SDT-RetransmissionTimer Indicates the initial value of the configured grant retransmission timer used for the initial transmission of CG-SDT with CCCH message (see TS 38.321 [3]) in multiples of periodicity.

sdt-DMRS-Ports Indicates the set of DMRS ports for SSB to PUSCH mapping (see TS 38.213 [13]).

sdt-NrofDMRS-Sequences Indicates the number of DMRS sequences for SSB to PUSCH mapping (see TS 38.213 [13]).

sdt-SSB-Subset Indicates SSB subset for SSB to CG PUSCH mapping within one CG configuration. If this field is absent, UE assumes the SSB set includes all actually transmitted SSBs configured by SIB1.

sdt-SSB-PerCG-PUSCH The number of SSBs per CG PUSCH (see TS 38.213 [13]). Value one corresponds to 1 SSBs per CG PUSCH, value two corresponds to 2 SSBs per CG PUSCH and so on.

sdt-P0-PUSCH Indicates P0 value for PUSCH for CG SDT in steps of 1dB (see TS 38.213 [13]). When this field is configured, the UE ignores the p0-PUSCH-Alpha.

sdt-Alpha Indicates alpha value for PUSCH for CG SDT. alpha0 indicates value 0 is used alpha04 indicates value 4 is used and so on (see TS 38.213 [13]). When this field is configured, the UE ignores the p0-PUSCH-Alpha.

Conditional Presence	Explanation
LCH-BasedPrioritization	This field is optionally present, Need R, if lch-BasedPrioritization is configured in the MAC entity. It is absent otherwise.
RepTypeB	The field is optionally present if pusch-RepTypeIndicator is set to pusch-RepTypeB, Need S, and absent otherwise.
CG-List	The field is mandatory present when included in configuredGrantConfigToAddModList-r16, otherwise the field is absent.
CG-IndexMAC	The field is mandatory present if at least one configured grant is configured by configuredGrantConfigToAddModList-r16 in any BWP of this MAC entity, otherwise it is optionally present, need R.
SRSsets	This field is mandatory present when UE is configured with two SRS sets configured in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage codebook or non-codebook. Otherwise it is absent, Need R

– ConfiguredGrantConfigIndex

The IE ConfiguredGrantConfigIndex is used to indicate the index of one of multiple UL Configured Grant configurations in one BWP.

ConfiguredGrantConfigIndex information element

— ASN1START

— TAG-CONFIGUREDGRANTCONFIGINDEX-START

ConfiguredGrantConfigIndex-r16 ::= INTEGER (0.. maxNrofConfiguredGrantConfig-1-r16)

— TAG-CONFIGUREDGRANTCONFIGINDEX-STOP

— ASN1STOP

– ConfiguredGrantConfigIndexMAC

The IE ConfiguredGrantConfigIndexMAC is used to indicate the unique Configured Grant configurations index per MAC entity.

ConfiguredGrantConfigIndexMAC information element

— ASN1START

— TAG-CONFIGUREDGRANTCONFIGINDEXMAC-START

ConfiguredGrantConfigIndexMAC-r16 ::= INTEGER (0.. maxNrofConfiguredGrantConfigMAC-1-r16)

— TAG-CONFIGUREDGRANTCONFIGINDEXMAC-STOP

— ASN1STOP

– ConnEstFailureControl

The IE ConnEstFailureControl is used to configure parameters for connection establishment failure control.

ConnEstFailureControl information element

— ASN1START

— TAG-CONNESTFAILURECONTROL-START

ConnEstFailureControl ::= SEQUENCE {

connEstFailCount ENUMERATED {n1, n2, n3, n4},

connEstFailOffsetValidity ENUMERATED {s30, s60, s120, s240, s300, s420, s600, s900},

connEstFailOffset INTEGER (0..15) OPTIONAL — Need S

}

— TAG-CONNESTFAILURECONTROL-STOP

— ASN1STOP

ConnEstFailureControl field descriptions

connEstFailCount Number of times that the UE detects T300 expiry on the same cell before applying connEstFailOffset.

connEstFailOffset Parameter "Qoffsettemp" in TS 38.304 [20]. If the field is absent, the value of infinity shall be used for "Qoffsettemp".

connEstFailOffsetValidity Amount of time that the UE applies connEstFailOffset before removing the offset from evaluation of the cell. Value s30 corresponds to 30 seconds, value s60 corresponds to 60 seconds, and so on.

– ControlResourceSet

The IE ControlResourceSet is used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information (see TS 38.213 [13], clause 10.1). For the UE not supporting multipleCORESET in FR1, in order to receive MBS multicast in CFR within the UE’s active BWP, if a CORESET is not configured within the PDCCH-ConfigMulticast, the CORESET other than CORESET0 configured within the UE’s active BWP for scheduling unicast can be used for scheduling MBS multicast, and the CORESET is expected to be included completely within the CFR and the parameters configured in the CORESET are expected to be supported by the UE for MBS multicast.

ControlResourceSet information element

— ASN1START

— TAG-CONTROLRESOURCESET-START

ControlResourceSet ::= SEQUENCE {

controlResourceSetId ControlResourceSetId,

frequencyDomainResources BIT STRING (SIZE (45)),

duration INTEGER (1..maxCoReSetDuration),

cce-REG-MappingType CHOICE {

interleaved SEQUENCE {

reg-BundleSize ENUMERATED {n2, n3, n6},

interleaverSize ENUMERATED {n2, n3, n6},

shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL — Need S

},

nonInterleaved NULL

},

precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs},

tci-StatesPDCCH-ToAddList SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, — Cond NotSIB-initialBWP

tci-StatesPDCCH-ToReleaseList SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, — Cond NotSIB-initialBWP

tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, — Need S

pdcch-DMRS-ScramblingID INTEGER (0..65535) OPTIONAL, — Need S

…,

[[

rb-Offset-r16 INTEGER (0..5) OPTIONAL, — Need S

tci-PresentDCI-1-2-r16 INTEGER (1..3) OPTIONAL, — Need S

coresetPoolIndex-r16 INTEGER (0..1) OPTIONAL, — Need S

controlResourceSetId-v1610 ControlResourceSetId-v1610 OPTIONAL — Need S

]],

[[

followUnifiedTCIstate-r17 ENUMERATED {enabled} OPTIONAL — Need R

]]

}

— TAG-CONTROLRESOURCESET-STOP

— ASN1STOP

ControlResourceSet field descriptions

cce-REG-MappingType Mapping of Control Channel Elements (CCE) to Resource Element Groups (REG) (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2).

controlResourceSetId Identifies the instance of the ControlResourceSet IE. Value 0 identifies the common CORESET configured in MIB and in ServingCellConfigCommon (controlResourceSetZero) and is hence not used here in the ControlResourceSet IE. Other values identify CORESETs configured by dedicated signalling or in SIB1 or SIB20. The controlResourceSetId is unique among the BWPs of a serving cell. If the field controlResourceSetId-v1610 is present, the UE shall ignore the controlResourceSetId field (without suffix).

coresetPoolIndex The index of the CORESET pool for this CORESET as specified in TS 38.213 [13] (clauses 9 and 10) and TS 38.214 [19] (clauses 5.1 and 6.1). If the field is absent, the UE applies the value 0.

duration Contiguous time duration of the CORESET in number of symbols (see TS 38.211 [16], clause 7.3.2.2).

followUnifiedTCIstate When set to enabled, for PDCCH reception on this CORESET, the UE applies the "indicated" DL only TCI or joint TCI as specified in TS 38.214 [19], clause 5.1.5.

frequencyDomainResources Frequency domain resources for the CORESET. Each bit corresponds a group of 6 RBs, with grouping starting from the first RB group in the BWP or MBS CFR where the CORESET is configured. When at least one search space is configured with freqMonitorLocation-r16, only the first bits are valid (see TS 38.213 [13], clause 10.1). The first (left-most / most significant) bit corresponds to the first RB group in the BWP or MBS CFR where the CORESET is configured, and so on. A bit that is set to 1 indicates that this RB group belongs to the frequency domain resource of this CORESET. Bits corresponding to a group of RBs not fully contained in the bandwidth part within which the CORESET is configured are set to zero (see TS 38.211 [16], clause 7.3.2.2).

interleaverSize Interleaver-size (see TS 38.211 [16], clause 7.3.2.2).

pdcch-DMRS-ScramblingID PDCCH DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.3.1). When the field is absent the UE applies the value of the physCellId configured for this serving cell.

precoderGranularity Precoder granularity in frequency domain (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2).

rb-Offset Indicates the RB level offset in units of RB from the first RB of the first 6RB group to the first RB of BWP (see 38.213 [13], clause 10.1).

reg-BundleSize Resource Element Groups (REGs) can be bundled to create REG bundles. This parameter defines the size of such bundles (see TS 38.211 [16], clause 7.3.2.2).

shiftIndex When the field is absent the UE applies the value of the physCellIdconfigured for this serving cell (see TS 38.211 [16], clause 7.3.2.2).

tci-PresentInDCI This field indicates if TCI field is present or absent in DCI format 1_1 and DCI format 4_2. When the field is absent the UE considers the TCI to be absent/disabled. In case of cross carrier scheduling, the network sets this field to enabled for the ControlResourceSet used for cross carrier scheduling in DCI format 1_1 in the scheduling cell if enableDefaultBeamForCCS is not configured (see TS 38.214 [19], clause 5.1.5).

tci-PresentDCI-1-2 Configures the number of bits for "Transmission configuration indicator" in DCI format 1_2. When the field is absent the UE applies the value of 0 bit for the "Transmission configuration indicator" in DCI format 1_2 (see TS 38.212, clause 7.3.1 and TS 38.214, clause 5.1.5). In case of cross carrier scheduling, the network configures this field for the ControlResourceSet used for cross carrier scheduling in DCI format 1_2 in the scheduling cell if enableDefaultBeamForCCS is not configured (see TS 38.214 [19], clause 5.1.5).

tci-StatesPDCCH-ToAddList A subset of the TCI states defined in pdsch-Config included in the BWP-DownlinkDedicated corresponding to the serving cell and to the DL BWP to which the ControlResourceSet belong to. They are used for providing QCL relationships between the DL RS(s) in one RS Set (TCI-State) and the PDCCH DMRS ports (see TS 38.213 [13], clause 6.). The network configures at most maxNrofTCI-StatesPDCCH entries. The QCL relationships defined herein do not apply to MBS broadcast.

Conditional Presence	Explanation
NotSIB-initialBWP	The field is absent in SIB1/SIB20 and in the PDCCH-ConfigCommon of the initial BWP in ServingCellConfigCommon, if SIB1/SIB20 is broadcasted. Otherwise, it is optionally present, Need N.

– ControlResourceSetId

The ControlResourceSetId IE concerns a short identity, used to identify a control resource set within a serving cell. The ControlResourceSetId = 0 identifies the ControlResourceSet#0 configured via PBCH (MIB) and in controlResourceSetZero (ServingCellConfigCommon). The ID space is used across the BWPs and MBS CFRs of a Serving Cell.

ControlResourceSetId information element

— ASN1START

— TAG-CONTROLRESOURCESETID-START

ControlResourceSetId ::= INTEGER (0..maxNrofControlResourceSets-1)

ControlResourceSetId-r16 ::= INTEGER (0..maxNrofControlResourceSets-1-r16)

ControlResourceSetId-v1610 ::= INTEGER (maxNrofControlResourceSets..maxNrofControlResourceSets-1-r16)

— TAG-CONTROLRESOURCESETID-STOP

— ASN1STOP

– ControlResourceSetZero

The IE ControlResourceSetZero is used to configure CORESET#0 of the initial BWP (see TS 38.213 [13], clause 13).

ControlResourceSetZero information element

— ASN1START

— TAG-CONTROLRESOURCESETZERO-START

ControlResourceSetZero ::= INTEGER (0..15)

— TAG-CONTROLRESOURCESETZERO-STOP

— ASN1STOP

– CrossCarrierSchedulingConfig

The IE CrossCarrierSchedulingConfig is used to specify the configuration when the cross-carrier scheduling is used in a cell.

CrossCarrierSchedulingConfig information element

— ASN1START

— TAG-CROSSCARRIERSCHEDULINGCONFIG-START

CrossCarrierSchedulingConfig ::= SEQUENCE {

schedulingCellInfo CHOICE {

own SEQUENCE { — Cross carrier scheduling: scheduling cell

cif-Presence BOOLEAN

},

other SEQUENCE { — Cross carrier scheduling: scheduled cell

schedulingCellId ServCellIndex,

cif-InSchedulingCell INTEGER (1..7)

}

},

…,

[[

carrierIndicatorSize-r16 SEQUENCE {

carrierIndicatorSizeDCI-1-2-r16 INTEGER (0..3),

carrierIndicatorSizeDCI-0-2-r16 INTEGER (0..3)

} OPTIONAL, — Cond CIF-PRESENCE

enableDefaultBeamForCCS-r16 ENUMERATED {enabled} OPTIONAL — Need S

]],

[[

ccs-BlindDetectionSplit-r17 ENUMERATED {oneSeventh, threeFourteenth, twoSeventh, threeSeventh,

oneHalf, fourSeventh, fiveSeventh, spare1} OPTIONAL — Need R

]]

}

— TAG-CROSSCARRIERSCHEDULINGCONFIG-STOP

— ASN1STOP

CrossCarrierSchedulingConfig field descriptions
carrierIndicatorSizeDCI-0-2, carrierIndicatorSizeDCI-1-2 Configures the number of bits for the field of carrier indicator in PDCCH DCI format 0_2/1_2. The field carrierIndicatorSizeDCI-0-2 refers to DCI format 0_2 and the field carrierIndicatorSizeDCI-1-2 refers to DCI format 1_2, respectively (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 10.1).
ccs-BlindDetectionSplit Indicates the share of blind detection candidates and non-overlapping CCEs for PDCCH monitoring on an SpCell and an SCell when cross-carrier scheduling is configured from the SCell for the SpCell (see TS 38.213 [13], clause 10.1.1). The network only configures this field when it sets the field other for an SpCell, i.e., when it configures cross-carrier scheduling of the SpCell by a PDCCH on an Scell.
cif-Presence The field is used to indicate whether carrier indicator field is present (value true) or not (value false) in PDCCH DCI formats, see TS 38.213 [13]. If cif-Presence is set to true, the CIF value indicating a grant or assignment for this cell is 0.
cif-InSchedulingCell The field indicates the CIF value used in the scheduling cell to indicate a grant or assignment applicable for this cell, see TS 38.213 [13]. If configured for an SpCell, the non-fallback DCI formats on the SpCell include same number of CIF bits as the corresponding non-fallback DCI formats on the scheduling cell, and the CIF bits are considered reserved.
enableDefaultBeamForCCS This field indicates whether default beam selection for cross-carrier scheduled PDSCH is enabled, see TS 38.214 [19]. If not present, the default beam selection behaviour is not applied, i.e. Rel-15 behaviour is applied. This field can only be configured in the cross-scheduled SCell or SpCell.
other Parameters for cross-carrier scheduling. If configured for an SpCell, the SpCell can be scheduled by the PDCCH on another SCell as well as by the PDCCH on the SpCell. If configured for an SCell, the SCell is scheduled by a PDDCH on another cell.
own Parameters for self-scheduling, i.e., a serving cell is scheduled by its own PDCCH.
schedulingCellId If configured for an SpCell, this field indicates which SCell, in addition to the SpCell, signals the downlink allocations and uplink grants, if applicable, for the concerned SpCell. If configured for an Scell, this field indicates which cell signals the downlink allocations and uplink grants, if applicable, for the concerned SCell. In case the UE is configured with DC, the scheduling cell is part of the same cell group (i.e. MCG or SCG) as the scheduled cell. In case the UE is configured with two PUCCH groups, the scheduling cell and the scheduled cell are within the same PUCCH group. If drx-ConfigSecondaryGroup is configured in the MAC-CellGroupConfig associated with this serving cell, the scheduling cell and the scheduled cell belong to the same Frequency Range. In addition, the serving cell with an aperiodic CSI trigger and the PUSCH resource scheduled for the report are on the same carrier and serving cell, but the cell for which CSI is reported may belong to the same or a different Frequency Range. The network should not trigger a CSI request for a serving cell in the other Frequency Range when that serving cell is outside Active Time.

Conditional Presence	Explanation
CIF-PRESENCE	The field is mandatory present if the cif-Presence is set to true. The field is absent otherwise.

– CSI-AperiodicTriggerStateList

The CSI-AperiodicTriggerStateList IE is used to configure the UE with a list of aperiodic trigger states. Each codepoint of the DCI field "CSI request" is associated with one trigger state (see TS 38.321 [3], clause 6.1.3.13). Upon reception of the value associated with a trigger state, the UE will perform measurement of CSI-RS, CSI-IM and/or SSB (reference signals) and aperiodic reporting on L1 according to all entries in the associatedReportConfigInfoList for that trigger state.

CSI-AperiodicTriggerStateList information element

— ASN1START

— TAG-CSI-APERIODICTRIGGERSTATELIST-START

CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState

CSI-AperiodicTriggerState ::= SEQUENCE {

associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo,

…,

[[

ap-CSI-MultiplexingMode-r17 ENUMERATED {enabled} OPTIONAL — Need R

]]

}

CSI-AssociatedReportConfigInfo ::= SEQUENCE {

reportConfigId CSI-ReportConfigId,

resourcesForChannel CHOICE {

nzp-CSI-RS SEQUENCE {

resourceSet INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig),

qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId

OPTIONAL — Cond Aperiodic

},

csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig)

},

csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig) OPTIONAL, — Cond CSI-IM-ForInterference

nzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, — Cond NZP-CSI-RS-ForInterference

…,

[[

resourcesForChannel2-r17 CHOICE {

nzp-CSI-RS2-r17 SEQUENCE {

resourceSet2-r17 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig),

qcl-info2-r17 SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId

OPTIONAL — Cond Aperiodic

},

csi-SSB-ResourceSet2-r17 INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfigExt)

} OPTIONAL, — Cond NoUnifiedTCI

csi-SSB-ResourceSetExt INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfigExt) OPTIONAL — Need R

]]

}

— TAG-CSI-APERIODICTRIGGERSTATELIST-STOP

— ASN1STOP

CSI-AssociatedReportConfigInfo field descriptions

ap-CSI-MultiplexingMode Indicates if the behavior of transmitting aperiodic CSI on the first PUSCH repetitions corresponding to two SRS resource sets configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage ‘codebook‘ or ‘noncodebook‘ is enabled or not.

csi-IM-ResourcesForInterference CSI-IM-ResourceSet for interference measurement. Entry number in csi-IM-ResourceSetList in the CSI-ResourceConfig indicated by csi-IM-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on). The indicated CSI-IM-ResourceSet should have exactly the same number of resources like the NZP-CSI-RS-ResourceSet indicated in resourceSet within nzp-CSI-RS.

csi-SSB-ResourceSet, csi-SSB-ResourceSet2 CSI-SSB-ResourceSet for channel measurements. Entry number in csi-SSB-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on).

nzp-CSI-RS-ResourcesForInterference NZP-CSI-RS-ResourceSet for interference measurement. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by nzp-CSI-RS-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on).

qcl-info, qcl-info2 List of references to TCI-States for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by resourceSet within nzp-CSI-RS. Each TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resourcesForChannelMeasurement (in the CSI-ReportConfig indicated by reportConfigId above) belong to. First entry in qcl-info corresponds to first entry in nzp-CSI-RS-Resources of that NZP-CSI-RS-ResourceSet, second entry in qcl-info corresponds to second entry in nzp-CSI-RS-Resources, and so on (see TS 38.214 [19], clause 5.2.1.5.1). When this field is absent for aperiodic CSI RS, the UE shall use QCL information included in the "indicated" DL only/Joint TCI state as specified in TS 38.214

reportConfigId The reportConfigId of one of the CSI-ReportConfigToAddMod configured in CSI-MeasConfig

resourcesForChannel2 Configures reference signals for channel measurement corresponding to the second resource set for L1-RSRP measurement as configured in IE CSI-ResourceConfig when nrofReportedGroups-r17 is configured in IE CSI-ReportConfig. If this is present, network configures csi-SSB-ResourceSetExt instead of csi-SSB-ResourceSet and the UE ignores csi-SSB-ResourceSet in resourcesForChannel, and the resourcesForChannel configures the reference signals for channel measurement corresponding to the first resource set for L1-RSRP measurement (see TS 38.214 [19], clause 5.2.1.4).

resourceSet NZP-CSI-RS-ResourceSet for channel measurements. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on).

Conditional Presence	Explanation
Aperiodic	The field is mandatory present if the NZP-CSI-RS-Resources in the associated resourceSet have the resourceType aperiodic. The field is absent otherwise.
CSI-IM-ForInterference	This field is mandatory present if the CSI-ReportConfig identified by reportConfigId is configured with csi-IM-ResourcesForInterference; otherwise it is absent.
NZP-CSI-RS-ForInterference	This field is mandatory present if the CSI-ReportConfig identified by reportConfigId is configured with nzp-CSI-RS-ResourcesForInterference; otherwise it is absent.
NoUnifiedTCI	This field is absent, Need R, if unifiedTCI-StateType is configured for the serving cell in which the CSI-AperiodicTriggerStateList is included. It is optionally present, Need R, otherwise.

– CSI-FrequencyOccupation

The IE CSI-FrequencyOccupation is used to configure the frequency domain occupation of a channel state information measurement resource (e.g. NZP-CSI-RS-Resource, CSI-IM-Resource).

CSI-FrequencyOccupation information element

— ASN1START

— TAG-CSI-FREQUENCYOCCUPATION-START

CSI-FrequencyOccupation ::= SEQUENCE {

startingRB INTEGER (0..maxNrofPhysicalResourceBlocks-1),

nrofRBs INTEGER (24..maxNrofPhysicalResourceBlocksPlus1),

…

}

— TAG-CSI-FREQUENCYOCCUPATION-STOP

— ASN1STOP

CSI-FrequencyOccupation field descriptions

nrofRBs Number of PRBs across which this CSI resource spans. Only multiples of 4 are allowed. The smallest configurable number is the minimum of 24 and the width of the associated BWP. If the configured value is larger than the width of the corresponding BWP, the UE shall assume that the actual CSI-RS bandwidth is equal to the width of the BWP.

startingRB PRB where this CSI resource starts in relation to common resource block #0 (CRB#0) on the common resource block grid. Only multiples of 4 are allowed (0, 4, …)

– CSI-IM-Resource

The IE CSI-IM-Resource is used to configure one CSI Interference Management (IM) resource.

CSI-IM-Resource information element

— ASN1START

— TAG-CSI-IM-RESOURCE-START

CSI-IM-Resource ::= SEQUENCE {

csi-IM-ResourceId CSI-IM-ResourceId,

csi-IM-ResourceElementPattern CHOICE {

pattern0 SEQUENCE {

subcarrierLocation-p0 ENUMERATED { s0, s2, s4, s6, s8, s10 },

symbolLocation-p0 INTEGER (0..12)

},

pattern1 SEQUENCE {

subcarrierLocation-p1 ENUMERATED { s0, s4, s8 },

symbolLocation-p1 INTEGER (0..13)

}

} OPTIONAL, — Need M

freqBand CSI-FrequencyOccupation OPTIONAL, — Need M

periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, — Cond PeriodicOrSemiPersistent

…

}

— TAG-CSI-IM-RESOURCE-STOP

— ASN1STOP

CSI-IM-Resource field descriptions

csi-IM-ResourceElementPattern The resource element pattern (Pattern0 (2,2) or Pattern1 (4,1)) with corresponding parameters (see TS 38.214 [19], clause 5.2.2.4)

freqBand Frequency-occupancy of CSI-IM (see TS 38.214 [19], clause 5.2.2.4)

periodicityAndOffset Periodicity and slot offset for periodic/semi-persistent CSI-IM. Network always configures the UE with a value for this field for periodic and semi-persistent CSI-IM-Resources (as indicated in CSI-ResourceConfig). A change of configuration between periodic or semi-persistent and aperiodic for a CSI-IM-Resource is not supported without a release and add.

subcarrierLocation-p0 OFDM subcarrier occupancy of the CSI-IM resource for Pattern0 (see TS 38.214 [19], clause 5.2.2.4)

subcarrierLocation-p1 OFDM subcarrier occupancy of the CSI-IM resource for Pattern1 (see TS 38.214 [19], clause 5.2.2.4)

symbolLocation-p0 OFDM symbol location of the CSI-IM resource for Pattern0 (see TS 38.214 [19], clause 5.2.2.4)

symbolLocation-p1 OFDM symbol location of the CSI-IM resource for Pattern1 (see TS 38.214 [19], clause 5.2.2.4)

Conditional Presence	Explanation
PeriodicOrSemiPersistent	The field is optionally present, Need M, for periodic and semi-persistent CSI-IM-Resources (as indicated in CSI-ResourceConfig). The field is absent otherwise.

– CSI-IM-ResourceId

The IE CSI-IM-ResourceId is used to identify one CSI-IM-Resource.

CSI-IM-ResourceId information element

— ASN1START

— TAG-CSI-IM-RESOURCEID-START

CSI-IM-ResourceId ::= INTEGER (0..maxNrofCSI-IM-Resources-1)

— TAG-CSI-IM-RESOURCEID-STOP

— ASN1STOP

– CSI-IM-ResourceSet

The IE CSI-IM-ResourceSet is used to configure a set of one or more CSI Interference Management (IM) resources (their IDs) and set-specific parameters.

CSI-IM-ResourceSet information element

— ASN1START

— TAG-CSI-IM-RESOURCESET-START

CSI-IM-ResourceSet ::= SEQUENCE {

csi-IM-ResourceSetId CSI-IM-ResourceSetId,

csi-IM-Resources SEQUENCE (SIZE(1..maxNrofCSI-IM-ResourcesPerSet)) OF CSI-IM-ResourceId,

…

}

— TAG-CSI-IM-RESOURCESET-STOP

— ASN1STOP

CSI-IM-ResourceSet field descriptions

csi-IM-Resources CSI-IM-Resources associated with this CSI-IM-ResourceSet (see TS 38.214 [19], clause 5.2).

– CSI-IM-ResourceSetId

The IE CSI-IM-ResourceSetId is used to identify CSI-IM-ResourceSets.

CSI-IM-ResourceSetId information element

— ASN1START

— TAG-CSI-IM-RESOURCESETID-START

CSI-IM-ResourceSetId ::= INTEGER (0..maxNrofCSI-IM-ResourceSets-1)

— TAG-CSI-IM-RESOURCESETID-STOP

— ASN1STOP

– CSI-MeasConfig

The IE CSI-MeasConfig is used to configure CSI-RS (reference signals) belonging to the serving cell in which CSI-MeasConfig is included, channel state information reports to be transmitted on PUCCH on the serving cell in which CSI-MeasConfig is included and channel state information reports on PUSCH triggered by DCI received on the serving cell in which CSI-MeasConfig is included. See also TS 38.214 [19], clause 5.2.

CSI-MeasConfig information element

— ASN1START

— TAG-CSI-MEASCONFIG-START

CSI-MeasConfig ::= SEQUENCE {

nzp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, — Need N

nzp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, — Need N

nzp-CSI-RS-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet

OPTIONAL, — Need N

nzp-CSI-RS-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId

OPTIONAL, — Need N

csi-IM-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-Resource OPTIONAL, — Need N

csi-IM-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-ResourceId OPTIONAL, — Need N

csi-IM-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSet OPTIONAL, — Need N

csi-IM-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSetId OPTIONAL, — Need N

csi-SSB-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSet OPTIONAL, — Need N

csi-SSB-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSetId OPTIONAL, — Need N

csi-ResourceConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig

OPTIONAL, — Need N

csi-ResourceConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfigId

OPTIONAL, — Need N

csi-ReportConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfig OPTIONAL, — Need N

csi-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfigId

OPTIONAL, — Need N

reportTriggerSize INTEGER (0..6) OPTIONAL, — Need M

aperiodicTriggerStateList SetupRelease { CSI-AperiodicTriggerStateList } OPTIONAL, — Need M

semiPersistentOnPUSCH-TriggerStateList SetupRelease { CSI-SemiPersistentOnPUSCH-TriggerStateList } OPTIONAL, — Need M

…,

[[

reportTriggerSizeDCI-0-2-r16 INTEGER (0..6) OPTIONAL — Need R

]],

[[

sCellActivationRS-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-Config-r17 OPTIONAL, — Need N

sCellActivationRS-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-ConfigId-r17 OPTIONAL — Need N

]]

}

— TAG-CSI-MEASCONFIG-STOP

— ASN1STOP

CSI-MeasConfig field descriptions

aperiodicTriggerStateList Contains trigger states for dynamically selecting one or more aperiodic and semi-persistent reporting configurations and/or triggering one or more aperiodic CSI-RS resource sets for channel and/or interference measurement (see TS 38.214 [19], clause 5.2.1).

csi-IM-ResourceSetToAddModList Pool of CSI-IM-ResourceSet which can be referred to from CSI-ResourceConfig or from MAC CEs.

csi-IM-ResourceToAddModList Pool of CSI-IM-Resource which can be referred to from CSI-IM-ResourceSet.

csi-ReportConfigToAddModList Configured CSI report settings as specified in TS 38.214 [19] clause 5.2.1.1.

csi-ResourceConfigToAddModList Configured CSI resource settings as specified in TS 38.214 [19] clause 5.2.1.2.

csi-SSB-ResourceSetToAddModList Pool of CSI-SSB-ResourceSet which can be referred to from CSI-ResourceConfig.

nzp-CSI-RS-ResourceSetToAddModList Pool of NZP-CSI-RS-ResourceSet which can be referred to from CSI-ResourceConfig or from MAC CEs.

nzp-CSI-RS-ResourceToAddModList Pool of NZP-CSI-RS-Resource which can be referred to from NZP-CSI-RS-ResourceSet.

reportTriggerSize, reportTriggerSizeDCI-0-2 Size of CSI request field in DCI (bits) (see TS 38.214 [19], clause 5.2.1.5.1). The field reportTriggerSize applies to DCI format 0_1 and the field reportTriggerSizeDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 5.2.1.5.1).

scellActivationRS-ConfigToAddModList Configured RS for fast SCell activation as specified in TS 38.214 [19] clause x.y.z.

– CSI-ReportConfig

The IE CSI-ReportConfig is used to configure a periodic or semi-persistent report sent on PUCCH on the cell in which the CSI-ReportConfig is included, or to configure a semi-persistent or aperiodic report sent on PUSCH triggered by DCI received on the cell in which the CSI-ReportConfig is included (in this case, the cell on which the report is sent is determined by the received DCI). See TS 38.214 [19], clause 5.2.1.

CSI-ReportConfig information element

— ASN1START

— TAG-CSI-REPORTCONFIG-START

CSI-ReportConfig ::= SEQUENCE {

reportConfigId CSI-ReportConfigId,

carrier ServCellIndex OPTIONAL, — Need S

resourcesForChannelMeasurement CSI-ResourceConfigId,

csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, — Need R

nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, — Need R

reportConfigType CHOICE {

periodic SEQUENCE {

reportSlotConfig CSI-ReportPeriodicityAndOffset,

pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource

},

semiPersistentOnPUCCH SEQUENCE {

reportSlotConfig CSI-ReportPeriodicityAndOffset,

pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource

},

semiPersistentOnPUSCH SEQUENCE {

reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},

reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),

p0alpha P0-PUSCH-AlphaSetId

},

aperiodic SEQUENCE {

reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)

}

},

reportQuantity CHOICE {

none NULL,

cri-RI-PMI-CQI NULL,

cri-RI-i1 NULL,

cri-RI-i1-CQI SEQUENCE {

pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL — Need S

},

cri-RI-CQI NULL,

cri-RSRP NULL,

ssb-Index-RSRP NULL,

cri-RI-LI-PMI-CQI NULL

},

reportFreqConfiguration SEQUENCE {

cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI } OPTIONAL, — Need R

pmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI } OPTIONAL, — Need R

csi-ReportingBand CHOICE {

subbands3 BIT STRING(SIZE(3)),

subbands4 BIT STRING(SIZE(4)),

subbands5 BIT STRING(SIZE(5)),

subbands6 BIT STRING(SIZE(6)),

subbands7 BIT STRING(SIZE(7)),

subbands8 BIT STRING(SIZE(8)),

subbands9 BIT STRING(SIZE(9)),

subbands10 BIT STRING(SIZE(10)),

subbands11 BIT STRING(SIZE(11)),

subbands12 BIT STRING(SIZE(12)),

subbands13 BIT STRING(SIZE(13)),

subbands14 BIT STRING(SIZE(14)),

subbands15 BIT STRING(SIZE(15)),

subbands16 BIT STRING(SIZE(16)),

subbands17 BIT STRING(SIZE(17)),

subbands18 BIT STRING(SIZE(18)),

…,

subbands19-v1530 BIT STRING(SIZE(19))

} OPTIONAL — Need S

} OPTIONAL, — Need R

timeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured},

timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured},

codebookConfig CodebookConfig OPTIONAL, — Need R

dummy ENUMERATED {n1, n2} OPTIONAL, — Need R

groupBasedBeamReporting CHOICE {

enabled NULL,

disabled SEQUENCE {

nrofReportedRS ENUMERATED {n1, n2, n3, n4} OPTIONAL — Need S

}

},

cqi-Table ENUMERATED {table1, table2, table3, table4-r17} OPTIONAL, — Need R

subbandSize ENUMERATED {value1, value2},

non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, — Need R

…,

[[

semiPersistentOnPUSCH-v1530 SEQUENCE {

reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16}

} OPTIONAL — Need R

]],

[[

semiPersistentOnPUSCH-v1610 SEQUENCE {

reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, — Need R

reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL — Need R

} OPTIONAL, — Need R

aperiodic-v1610 SEQUENCE {

reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, — Need R

reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL — Need R

} OPTIONAL, — Need R

reportQuantity-r16 CHOICE {

cri-SINR-r16 NULL,

ssb-Index-SINR-r16 NULL

} OPTIONAL, — Need R

codebookConfig-r16 CodebookConfig-r16 OPTIONAL — Need R

]],

[[

cqi-BitsPerSubband-r17 ENUMERATED {bits4} OPTIONAL, — Need R

groupBasedBeamReporting-v1710 SEQUENCE {

nrofReportedGroups-r17 ENUMERATED {n1, n2, n3, n4}

} OPTIONAL, — Need R

codebookConfig-r17 CodebookConfig-r17 OPTIONAL, — Need R

sharedCMR-r17 ENUMERATED {enable} OPTIONAL, — Need R

csi-ReportMode-r17 ENUMERATED {mode1, mode2} OPTIONAL, — Need R

numberOfSingleTRP-CSI-Mode1-r17 ENUMERATED {n0, n1, n2} OPTIONAL, — Need R

reportQuantity-r17 CHOICE {

cri-RSRP-Index-r17 NULL,

ssb-Index-RSRP-Index-r17 NULL,

cri-SINR-Index-r17 NULL,

ssb-Index-SINR-Index-r17 NULL

} OPTIONAL — Need R

]],

[[

semiPersistentOnPUSCH-v1720 SEQUENCE {

reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, — Need R

reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, — Need R

reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL — Need R

} OPTIONAL, — Need R

aperiodic-v1720 SEQUENCE {

reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, — Need R

reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, — Need R

reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL — Need R

} OPTIONAL — Need R

]]

}

CSI-ReportPeriodicityAndOffset ::= CHOICE {

slots4 INTEGER(0..3),

slots5 INTEGER(0..4),

slots8 INTEGER(0..7),

slots10 INTEGER(0..9),

slots16 INTEGER(0..15),

slots20 INTEGER(0..19),

slots40 INTEGER(0..39),

slots80 INTEGER(0..79),

slots160 INTEGER(0..159),

slots320 INTEGER(0..319)

}

PUCCH-CSI-Resource ::= SEQUENCE {

uplinkBandwidthPartId BWP-Id,

pucch-Resource PUCCH-ResourceId

}

PortIndexFor8Ranks ::= CHOICE {

portIndex8 SEQUENCE{

rank1-8 PortIndex8 OPTIONAL, — Need R

rank2-8 SEQUENCE(SIZE(2)) OF PortIndex8 OPTIONAL, — Need R

rank3-8 SEQUENCE(SIZE(3)) OF PortIndex8 OPTIONAL, — Need R

rank4-8 SEQUENCE(SIZE(4)) OF PortIndex8 OPTIONAL, — Need R

rank5-8 SEQUENCE(SIZE(5)) OF PortIndex8 OPTIONAL, — Need R

rank6-8 SEQUENCE(SIZE(6)) OF PortIndex8 OPTIONAL, — Need R

rank7-8 SEQUENCE(SIZE(7)) OF PortIndex8 OPTIONAL, — Need R

rank8-8 SEQUENCE(SIZE(8)) OF PortIndex8 OPTIONAL — Need R

},

portIndex4 SEQUENCE{

rank1-4 PortIndex4 OPTIONAL, — Need R

rank2-4 SEQUENCE(SIZE(2)) OF PortIndex4 OPTIONAL, — Need R

rank3-4 SEQUENCE(SIZE(3)) OF PortIndex4 OPTIONAL, — Need R

rank4-4 SEQUENCE(SIZE(4)) OF PortIndex4 OPTIONAL — Need R

},

portIndex2 SEQUENCE{

rank1-2 PortIndex2 OPTIONAL, — Need R

rank2-2 SEQUENCE(SIZE(2)) OF PortIndex2 OPTIONAL — Need R

},

portIndex1 NULL

}

PortIndex8::= INTEGER (0..7)

PortIndex4::= INTEGER (0..3)

PortIndex2::= INTEGER (0..1)

— TAG-CSI-REPORTCONFIG-STOP

— ASN1STOP

CSI-ReportConfig field descriptions

carrier Indicates in which serving cell the CSI-ResourceConfig indicated below are to be found. If the field is absent, the resources are on the same serving cell as this report configuration.

codebookConfig Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network can only configure one of codebookConfig, codebookConfig-r16 or codebookConfig-r17 to a UE.

cqi-BitsPerSubband This field can only be present if cqi-FormatIndicator is set to subbandCQI. If the field is configured with bits4, the UE uses 4-bit sub-band CQI. If the field is not present and cqi-FormatIndicator is set to subbandCQI, the UE uses 2-bit sub-band differential CQI.

cqi-FormatIndicator Indicates whether the UE shall report a single (wideband) or multiple (subband) CQI (see TS 38.214 [19], clause 5.2.1.4).

cqi-Table Which CQI table to use for CQI calculation (see TS 38.214 [19], clause 5.2.2.1). For a RedCap UE, CQI table 2 is only supported if the UE indicates support of 256QAM for PDSCH.

csi-IM-ResourcesForInterference CSI IM resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only CSI-IM resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.

csi-ReportingBand Indicates a contiguous or non-contiguous subset of subbands in the bandwidth part which CSI shall be reported for. Each bit in the bit-string represents one subband. The right-most bit in the bit string represents the lowest subband in the BWP. The choice determines the number of subbands (subbands3 for 3 subbands, subbands4 for 4 subbands, and so on) (see TS 38.214 [19], clause 5.2.1.4). This field is absent if there are less than 24 PRBs (no sub band) and present otherwise (see TS 38.214 [19], clause 5.2.1.4).

csi-ReportMode Configures the CSI report modes Mode1 or Mode 2 (see TS 38.214 [19], clause 5.2.1.4.2)

dummy This field is not used in the specification. If received it shall be ignored by the UE.

groupBasedBeamReporting Turning on/off group beam based reporting (see TS 38.214 [19], clause 5.2.1.4). If groupBasedBeamReporting (without suffix) is set to disabled, groupBasedBeamReporting-v1710 is absent.

non-PMI-PortIndication Port indication for RI/CQI calculation. For each CSI-RS resource in the linked ResourceConfig for channel measurement, a port indication for each rank R, indicating which R ports to use. Applicable only for non-PMI feedback (see TS 38.214 [19], clause 5.2.1.4.2). The first entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the CSI-ResourceConfig whose CSI-ResourceConfigId is indicated in a CSI-MeasId together with the above CSI-ReportConfigId; the second entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the second entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig, and so on until the NZP-CSI-RS-Resource indicated by the last entry in nzp-CSI-RS-Resources in the in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig. Then the next entry corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the second entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig and so on.

nrofReportedGroups Number of reported resource groups per CSI-report. Value n1 means one resource group, n2 means 2 resource groups, and so on. If nrofReportedGroups is configured, the UE ignores groupBasedBeamReporting (without suffix).

nrofReportedRS The number (N) of measured RS resources to be reported per report setting in a non-group-based report. N <= N_max, where N_max is either 2 or 4 depending on UE capability. (see TS 38.214 [19], clause 5.2.1.4) When the field is absent the UE applies the value 1.

numberOfSingleTRP-CSI-Mode1 Configures the number of reported X CSIs when csi-ReportMode is set to ‘Mode 1’ as described in TS 38.214 [19], clause 5.2.1.4.2. The field is present only if csi-ReportMode configures Mode 1.

nzp-CSI-RS-ResourcesForInterference NZP CSI RS resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.

p0alpha Index of the p0-alpha set determining the power control for this CSI report transmission (see TS 38.214 [19], clause 6.2.1.2).

pdsch-BundleSizeForCSI PRB bundling size to assume for CQI calculation when reportQuantity is CRI/RI/i1/CQI. If the field is absent, the UE assumes that no PRB bundling is applied (see TS 38.214 [19], clause 5.2.1.4.2).

pmi-FormatIndicator Indicates whether the UE shall report a single (wideband) or multiple (subband) PMI. (see TS 38.214 [19], clause 5.2.1.4).

pucch-CSI-ResourceList Indicates which PUCCH resource to use for reporting on PUCCH.

reportConfigType Time domain behavior of reporting configuration.

reportFreqConfiguration Reporting configuration in the frequency domain. (see TS 38.214 [19], clause 5.2.1.4).

reportQuantity The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16 is present, UE shall ignore reportQuantity (without suffix).

reportSlotConfig Periodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix).

reportSlotOffsetList, reportSlotOffsetListDCI-0-1, reportSlotOffsetListDCI-0-2 Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17, reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz.

resourcesForChannelMeasurement Resources for channel measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources and/or SSB resources. This CSI-ReportConfig is associated with the DL BWP indicated by bwp-Id in that CSI-ResourceConfig.

sharedCMR Enables sharing of channel measurement resources between different CSI measurement hypotheses when (1) csi-ReportMode is set to ‘Mode1’ and numberOfSingleTRP-CSI-Mode1 is set to 1 or 2; or (2) csi-ReportMode is set to ‘Mode2’ (see TS 38.214 [19], clause 5.2.1.4.2).

subbandSize Indicates one out of two possible BWP-dependent values for the subband size as indicated in TS 38.214 [19], table 5.2.1.4-2 . If csi-ReportingBand is absent, the UE shall ignore this field.

timeRestrictionForChannelMeasurements Time domain measurement restriction for the channel (signal) measurements (see TS 38.214 [19], clause 5.2.1.1).

timeRestrictionForInterferenceMeasurements Time domain measurement restriction for interference measurements (see TS 38.214 [19], clause 5.2.1.1).

PortIndexFor8Ranks field descriptions

portIndex8 Port-Index configuration for up to rank 8. If present, the network configures port indexes for at least one of the ranks.

portIndex4 Port-Index configuration for up to rank 4. If present, the network configures port indexes for at least one of the ranks.

portIndex2 Port-Index configuration for up to rank 2. If present, the network configures port indexes for at least one of the ranks.

portIndex1 Port-Index configuration for rank 1.

PUCCH-CSI-Resource field descriptions

pucch-Resource PUCCH resource for the associated uplink BWP. Only PUCCH-Resource of format 2, 3 and 4 is supported. The actual PUCCH-Resource is configured in PUCCH-Config and referred to by its ID. When two PUCCH-Config are configured within PUCCH-ConfigurationList, PUCCH-ResourceId in a PUCCH-CSI-Resource refers to a PUCCH-Resource in the PUCCH-Config used for HARQ-ACK with low priority.

– CSI-ReportConfigId

The IE CSI-ReportConfigId is used to identify one CSI-ReportConfig.

CSI-ReportConfigId information element

— ASN1START

— TAG-CSI-REPORTCONFIGID-START

CSI-ReportConfigId ::= INTEGER (0..maxNrofCSI-ReportConfigurations-1)

— TAG-CSI-REPORTCONFIGID-STOP

— ASN1STOP

– CSI-ResourceConfig

The IE CSI-ResourceConfig defines a group of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet and/or CSI-SSB-ResourceSet.

CSI-ResourceConfig information element

— ASN1START

— TAG-CSI-RESOURCECONFIG-START

CSI-ResourceConfig ::= SEQUENCE {

csi-ResourceConfigId CSI-ResourceConfigId,

csi-RS-ResourceSetList CHOICE {

nzp-CSI-RS-SSB SEQUENCE {

nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId

OPTIONAL, — Need R

csi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL — Need R

},

csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId

},

bwp-Id BWP-Id,

resourceType ENUMERATED { aperiodic, semiPersistent, periodic },

…,

[[

csi-SSB-ResourceSetListExt-r17 CSI-SSB-ResourceSetId OPTIONAL — Need R

]]

}

— TAG-CSI-RESOURCECONFIG-STOP

— ASN1STOP

CSI-ResourceConfig field descriptions

bwp-Id The DL BWP which the CSI-RS associated with this CSI-ResourceConfig are located in (see TS 38.214 [19], clause 5.2.1.2.

csi-IM-ResourceSetList List of references to CSI-IM resources used for CSI measurement and reporting in a CSI-RS resource set. Contains up to maxNrofCSI-IM-ResourceSetsPerConfig resource sets if resourceType is ‘aperiodic’ and 1 otherwise (see TS 38.214 [19], clause 5.2.1.2).

csi-ResourceConfigId Used in CSI-ReportConfig to refer to an instance of CSI-ResourceConfig.

csi-SSB-ResourceSetList, csi-SSB-ResourceSetListExt List of references to SSB resources used for CSI measurement and reporting in a CSI-RS resource set (see TS 38.214 [19], clause 5.2.1.2). If groupBasedBeamReporting-v1710 is configured in the IE CSI-ReportConfig that indicates this CSI-ResourceConfig as resourceForChannelMeasurement, the network configures 2 resource sets, which may be two NZP CSI-RS resource sets, two CSI SSB resource sets or one NZP CSI-RS resource set and one CSI-SSB resource set (see TS 38.214 [19], clause 5.2.1.2 and 5.2.1.4.2). In this case, in TS 38.212 [17] Table 6.3.1.1.2-8B: – if the list has one CSI-SSB resource set, this resource set is indicated by a resource set indicator set to 1, while the resource set indicator of the NZP CSI-RS resource set is 0; – if the list has two CSI-SSB resource sets, the first resource set is indicated by a resource set indicator set to 0 and the second resource set by a resource set indicator set to 1.

nzp-CSI-RS-ResourceSetList List of references to NZP CSI-RS resources used for beam measurement and reporting in a CSI-RS resource set. Contains up to maxNrofNZP-CSI-RS-ResourceSetsPerConfig resource sets if resourceType is ‘aperiodic’. Otherwise, contains 1 resource set when groupBasedBeamReporting-v1710 is not configured in IE CSI-ReportConfig. If groupBasedBeamReporting-v1710 is configured and resourceType is set to ‘periodic’ or ‘semipersistent’, then the network configures 2 resource sets, which may be two NZP CSI-RS resource sets, two CSI SSB resource sets or one NZP CSI-RS resource set and one CSI-SSB resource set (see TS 38.214 [19], clause 5.2.1.2 and 5.2.1.4.2). In this case, in TS 38.212 [17] Table 6.3.1.1.2-8B, the following applies: – if the list has one NZP CSI-RS resource set, this resource set is indicated by a resource set indicator set to 0; – if the list has two NZP CSI-RS resource sets, the first resource set is indicated by a resource set indicator set to 0 and the second resource set by a resource set indicator set to 1.

resourceType Time domain behavior of resource configuration (see TS 38.214 [19], clause 5.2.1.2). It does not apply to resources provided in the csi-SSB-ResourceSetList.

– CSI-ResourceConfigId

The IE CSI-ResourceConfigId is used to identify a CSI-ResourceConfig.

CSI-ResourceConfigId information element

— ASN1START

— TAG-CSI-RESOURCECONFIGID-START

CSI-ResourceConfigId ::= INTEGER (0..maxNrofCSI-ResourceConfigurations-1)

— TAG-CSI-RESOURCECONFIGID-STOP

— ASN1STOP

– CSI-ResourcePeriodicityAndOffset

The IE CSI-ResourcePeriodicityAndOffset is used to configure a periodicity and a corresponding offset for periodic and semi-persistent CSI resources, and for periodic and semi-persistent reporting on PUCCH. both, the periodicity and the offset are given in number of slots. The periodicity value slots4 corresponds to 4 slots, value slots5 corresponds to 5 slots, and so on.

CSI-ResourcePeriodicityAndOffset information element

— ASN1START

— TAG-CSI-RESOURCEPERIODICITYANDOFFSET-START

CSI-ResourcePeriodicityAndOffset ::= CHOICE {

slots4 INTEGER (0..3),

slots5 INTEGER (0..4),

slots8 INTEGER (0..7),

slots10 INTEGER (0..9),

slots16 INTEGER (0..15),

slots20 INTEGER (0..19),

slots32 INTEGER (0..31),

slots40 INTEGER (0..39),

slots64 INTEGER (0..63),

slots80 INTEGER (0..79),

slots160 INTEGER (0..159),

slots320 INTEGER (0..319),

slots640 INTEGER (0..639)

}

— TAG-CSI-RESOURCEPERIODICITYANDOFFSET-STOP

— ASN1STOP

– CSI-RS-ResourceConfigMobility

The IE CSI-RS-ResourceConfigMobility is used to configure CSI-RS based RRM measurements.

CSI-RS-ResourceConfigMobility information element

— ASN1START

— TAG-CSI-RS-RESOURCECONFIGMOBILITY-START

CSI-RS-ResourceConfigMobility ::= SEQUENCE {

subcarrierSpacing SubcarrierSpacing,

csi-RS-CellList-Mobility SEQUENCE (SIZE (1..maxNrofCSI-RS-CellsRRM)) OF CSI-RS-CellMobility,

…,

[[

refServCellIndex ServCellIndex OPTIONAL — Need S

]]

}

CSI-RS-CellMobility ::= SEQUENCE {

cellId PhysCellId,

csi-rs-MeasurementBW SEQUENCE {

nrofPRBs ENUMERATED { size24, size48, size96, size192, size264},

startPRB INTEGER(0..2169)

},

density ENUMERATED {d1,d3} OPTIONAL, — Need R

csi-rs-ResourceList-Mobility SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesRRM)) OF CSI-RS-Resource-Mobility

}

CSI-RS-Resource-Mobility ::= SEQUENCE {

csi-RS-Index CSI-RS-Index,

slotConfig CHOICE {

ms4 INTEGER (0..31),

ms5 INTEGER (0..39),

ms10 INTEGER (0..79),

ms20 INTEGER (0..159),

ms40 INTEGER (0..319)

},

associatedSSB SEQUENCE {

ssb-Index SSB-Index,

isQuasiColocated BOOLEAN

} OPTIONAL, — Need R

frequencyDomainAllocation CHOICE {

row1 BIT STRING (SIZE (4)),

row2 BIT STRING (SIZE (12))

},

firstOFDMSymbolInTimeDomain INTEGER (0..13),

sequenceGenerationConfig INTEGER (0..1023),

…,

[[

slotConfig-r17 CHOICE {

ms4 INTEGER (0..255),

ms5 INTEGER (0..319),

ms10 INTEGER (0..639),

ms20 INTEGER (0..1279),

ms40 INTEGER (0..2559)

} OPTIONAL — Need R

]]

}

CSI-RS-Index ::= INTEGER (0..maxNrofCSI-RS-ResourcesRRM-1)

— TAG-CSI-RS-RESOURCECONFIGMOBILITY-STOP

— ASN1STOP

CSI-RS-CellMobility field descriptions

csi-rs-ResourceList-Mobility List of CSI-RS resources for mobility. The maximum number of CSI-RS resources that can be configured per measObjectNR depends on the configuration of associatedSSB and the support of increasedNumberofCSIRSPerMO capability (see TS 38.214 [19], clause 5.1.6.1.3).

density Frequency domain density for the 1-port CSI-RS for L3 mobility. See TS 38.211 [16], clause 7.4.1.

nrofPRBs Allowed size of the measurement BW in PRBs. See TS 38.211 [16], clause 7.4.1.

startPRB Starting PRB index of the measurement bandwidth. See TS 38.211 [16], clause 7.4.1.

CSI-RS-ResourceConfigMobility field descriptions

csi-RS-CellList-Mobility List of cells for CSI-RS based RRM measurements.

refServCellIndex Indicates the serving cell providing the timing reference for CSI-RS resources without associatedSSB. The field may be present only if there is at least one CSI-RS resource configured without associatedSSB. If this field is absent, the UE shall use the timing of the PCell for measurements on the CSI-RS resources without associatedSSB. The CSI-RS resources and the serving cell indicated by refServCellIndex for timing reference should be located in the same band.

subcarrierSpacing Subcarrier spacing of CSI-RS. Only the following values are applicable depending on the used frequency: FR1: 15, 30, or 60 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz

CSI-RS-Resource-Mobility field descriptions

associatedSSB If this field is present, the UE may base the timing of the CSI-RS resource indicated in CSI-RS-Resource-Mobility on the timing of the cell indicated by the cellId in the CSI-RS-CellMobility. In this case, the UE is not required to monitor that CSI-RS resource if the UE cannot detect the SS/PBCH block indicated by this associatedSSB and cellId. If this field is absent, the UE shall base the timing of the CSI-RS resource indicated in CSI-RS-Resource-Mobility on the timing of the serving cell indicated by refServCellIndex. In this case, the UE is required to measure the CSI-RS resource even if SS/PBCH block(s) with cellId in the CSI-RS-CellMobility are not detected. CSI-RS resources with and without associatedSSB may be configured in accordance with the rules in TS 38.214 [19], clause 5.1.6.1.3.

csi-RS-Index CSI-RS resource index associated to the CSI-RS resource to be measured (and used for reporting).

firstOFDMSymbolInTimeDomain Time domain allocation within a physical resource block. The field indicates the first OFDM symbol in the PRB used for CSI-RS, see TS 38.211 [16], clause 7.4.1.5.3. Value 2 is supported only when dmrs-TypeA-Position equals pos3.

frequencyDomainAllocation Frequency domain allocation within a physical resource block in accordance with TS 38.211 [16], clause 7.4.1.5.3 including table 7.4.1.5.2-1. The number of bits that may be set to one depend on the chosen row in that table.

isQuasiColocated Indicates that the CSI-RS resource is quasi co-located with the associated SS/PBCH block, see TS 38.214 [19], clause 5.1.6.1.3.

sequenceGenerationConfig Scrambling ID for CSI-RS (see TS 38.211 [16], clause 7.4.1.5.2).

slotConfig Indicates the CSI-RS periodicity (in milliseconds) and for each periodicity the offset (in number of slots). When subcarrierSpacing is set to kHz15, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 3/4/9/19/39 slots. When subcarrierSpacing is set to kHz30, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 7/9/19/39/79 slots. When subcarrierSpacing is set to kHz60, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 15/19/39/79/159 slots. When subcarrierSpacing is set kHz120, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 31/39/79/159/319 slots. When subcarrierSpacing is set to kHz480, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 127/159/319/639/1279 slots. When subcarrierSpacing is set to kHz960, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 255/319/639/1279/2559 slots. If slotConfig-r17 is present, UE shall ignore the slotConfig (without suffix).

– CSI-RS-ResourceMapping

The IE CSI-RS-ResourceMapping is used to configure the resource element mapping of a CSI-RS resource in time- and frequency domain.

CSI-RS-ResourceMapping information element

— ASN1START

— TAG-CSI-RS-RESOURCEMAPPING-START

CSI-RS-ResourceMapping ::= SEQUENCE {

frequencyDomainAllocation CHOICE {

row1 BIT STRING (SIZE (4)),

row2 BIT STRING (SIZE (12)),

row4 BIT STRING (SIZE (3)),

other BIT STRING (SIZE (6))

},

nrofPorts ENUMERATED {p1,p2,p4,p8,p12,p16,p24,p32},

firstOFDMSymbolInTimeDomain INTEGER (0..13),

firstOFDMSymbolInTimeDomain2 INTEGER (2..12) OPTIONAL, — Need R

cdm-Type ENUMERATED {noCDM, fd-CDM2, cdm4-FD2-TD2, cdm8-FD2-TD4},

density CHOICE {

dot5 ENUMERATED {evenPRBs, oddPRBs},

one NULL,

three NULL,

spare NULL

},

freqBand CSI-FrequencyOccupation,

…

}

— TAG-CSI-RS-RESOURCEMAPPING-STOP

— ASN1STOP

CSI-RS-ResourceMapping field descriptions

cdm-Type CDM type (see TS 38.214 [19], clause 5.2.2.3.1).

density Density of CSI-RS resource measured in RE/port/PRB (see TS 38.211 [16], clause 7.4.1.5.3). Values 0.5 (dot5), 1 (one) and 3 (three) are allowed for X=1, values 0.5 (dot5) and 1 (one) are allowed for X=2, 16, 24 and 32, value 1 (one) is allowed for X=4, 8, 12. For density = 1/2, includes 1-bit indication for RB level comb offset indicating whether odd or even RBs are occupied by CSI-RS.

firstOFDMSymbolInTimeDomain2 Time domain allocation within a physical resource block. See TS 38.211 [16], clause 7.4.1.5.3.

firstOFDMSymbolInTimeDomain Time domain allocation within a physical resource block. The field indicates the first OFDM symbol in the PRB used for CSI-RS. See TS 38.211 [16], clause 7.4.1.5.3. Value 2 is supported only when dmrs-TypeA-Position equals pos3.

freqBand Wideband or partial band CSI-RS, (see TS 38.214 [19], clause 5.2.2.3.1).

frequencyDomainAllocation Frequency domain allocation within a physical resource block in accordance with TS 38.211 [16], clause 7.4.1.5.3. The applicable row number in table 7.4.1.5.3-1 is determined by the frequencyDomainAllocation for rows 1, 2 and 4, and for other rows by matching the values in the column Ports, Density and CDMtype in table 7.4.1.5.3-1 with the values of nrofPorts, cdm-Type and density below and, when more than one row has the 3 values matching, by selecting the row where the column (k bar, l bar) in table 7.4.1.5.3-1 has indexes for k ranging from 0 to 2*n-1 where n is the number of bits set to 1 in frequencyDomainAllocation.

nrofPorts Number of ports (see TS 38.214 [19], clause 5.2.2.3.1).

– CSI-SemiPersistentOnPUSCH-TriggerStateList

The CSI-SemiPersistentOnPUSCH-TriggerStateList IE is used to configure the UE with list of trigger states for semi-persistent reporting of channel state information on L1. See also TS 38.214 [19], clause 5.2.

CSI-SemiPersistentOnPUSCH-TriggerStateList information element

— ASN1START

— TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-START

CSI-SemiPersistentOnPUSCH-TriggerStateList ::= SEQUENCE(SIZE (1..maxNrOfSemiPersistentPUSCH-Triggers)) OF CSI-SemiPersistentOnPUSCH-TriggerState

CSI-SemiPersistentOnPUSCH-TriggerState ::= SEQUENCE {

associatedReportConfigInfo CSI-ReportConfigId,

…,

[[

sp-CSI-MultiplexingMode-r17 ENUMERATED {enabled} OPTIONAL — Need R

]]

}

— TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STOP

— ASN1STOP

CSI-SemiPersistentOnPUSCH-TriggerStateList field descriptions

sp-CSI-MultiplexingMode Indicates if the behavior of transmitting SP-CSI on the first PUSCH repetitions coresponding to two SRS resource sets configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage ‘codebook’ or ‘noncodebook’ is enabled or not.

– CSI-SSB-ResourceSet

The IE CSI-SSB-ResourceSet is used to configure one SS/PBCH block resource set which refers to SS/PBCH as indicated in ServingCellConfigCommon and ServingCellConfig.

CSI-SSB-ResourceSet information element

— ASN1START

— TAG-CSI-SSB-RESOURCESET-START

CSI-SSB-ResourceSet ::= SEQUENCE {

csi-SSB-ResourceSetId CSI-SSB-ResourceSetId,

csi-SSB-ResourceList SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF SSB-Index,

…,

[[

servingAdditionalPCIList-r17 SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF ServingAdditionalPCIIndex-r17 OPTIONAL — Need R

]]

}

ServingAdditionalPCIIndex-r17 ::= INTEGER(0..maxNrofAdditionalPCI-r17)

— TAG-CSI-SSB-RESOURCESET-STOP

— ASN1STOP

CSI-SSB-ResourceSet field descriptions

servingAdditionalPCIList Indicates the physical cell IDs (PCI) of the SSBs in the csi-SSB-ResourceList. If present, the list has the same number of entries as csi-SSB-ResourceList. The first entry of the list indicates the value of the PCI for the first entry of csi-SSB-ResourceList, the second entry of this list indicates the value of the PCI for the second entry of csi-SSB-ResourceList, and so on. For each entry, the following applies: – If the value is zero, the PCI is the PCI of the serving cell in which this CSI-SSB-ResourceSet is defined; – otherwise, the value is additionalPCIIndex-r17 of an SSB-MTC-AdditionalPCI-r17 configured using the additionalPCI-ToAddModList-r17 in ServingCellConfig, and the PCI is the additionalPCI-r17 in this SSB-MTC-AdditionalPCI-r17.

– CSI-SSB-ResourceSetId

The IE CSI-SSB-ResourceSetId is used to identify one SS/PBCH block resource set.

CSI-SSB-ResourceId information element

— ASN1START

— TAG-CSI-SSB-RESOURCESETID-START

CSI-SSB-ResourceSetId ::= INTEGER (0..maxNrofCSI-SSB-ResourceSets-1)

— TAG-CSI-SSB-RESOURCESETID-STOP

— ASN1STOP

– DedicatedNAS-Message

The IE DedicatedNAS-Message is used to transfer UE specific NAS layer information between the 5GC CN and the UE. The RRC layer is transparent for this information.

DedicatedNAS-Message information element

— ASN1START

— TAG-DEDICATED-NAS-MESSAGE-START

DedicatedNAS-Message ::= OCTET STRING

— TAG-DEDICATED-NAS-MESSAGE-STOP

— ASN1STOP

– DL-PPW-PreConfig

The IE DL-PPW-PreConfig provides configuration for a measurement window where a UE is expected to measure the DL PRS, if it is inside the active DL BWP and with the same numerology as the active DL BWP. Based upon the indication received in the configuration, the UE identifies whether the DL PRS priority is higher than that of the other DL signals or channels and accordingly determines, for example, the UE is expected to measure the DL PRS and is not expected to receive other DL signals and channels.

DL-PPW-PreConfig information element

— ASN1START

— TAG-DL-PPW-PRECONFIG-START

DL-PPW-PreConfig-r17 ::= SEQUENCE {

dl-PPW-ID-r17 DL-PPW-ID-r17,

dl-PPW-Periodicity-and-StartSlot-r17 DL-PPW-Periodicity-and-StartSlot-r17,

length-r17 INTEGER (1..160),

type-r17 ENUMERATED {type1A, type1B, type2} OPTIONAL, — Cond MultiType

priority-r17 ENUMERATED {st1, st2, st3} OPTIONAL — Cond MultiState

}

DL-PPW-ID-r17 ::= INTEGER (0..maxNrofPPW-ID-1-r17)

DL-PPW-Periodicity-and-StartSlot-r17 ::= CHOICE {

scs15-r17 CHOICE {

n4-r17 INTEGER (0..3),

n5-r17 INTEGER (0..4),

n8-r17 INTEGER (0..7),

n10-r17 INTEGER (0..9),

n16-r17 INTEGER (0..15),

n20-r17 INTEGER (0..19),

n32-r17 INTEGER (0..31),

n40-r17 INTEGER (0..39),

n64-r17 INTEGER (0..63),

n80-r17 INTEGER (0..79),

n160-r17 INTEGER (0..159),

n320-r17 INTEGER (0..319),

n640-r17 INTEGER (0..639),

n1280-r17 INTEGER (0..1279),

n2560-r17 INTEGER (0..2559),

n5120-r17 INTEGER (0..5119),

n10240-r17 INTEGER (0..10239),

…

},

scs30-r17 CHOICE {

n8-r17 INTEGER (0..7),

n10-r17 INTEGER (0..9),

n16-r17 INTEGER (0..15),

n20-r17 INTEGER (0..19),

n32-r17 INTEGER (0..31),

n40-r17 INTEGER (0..39),

n64-r17 INTEGER (0..63),

n80-r17 INTEGER (0..79),

n128-r17 INTEGER (0..127),

n160-r17 INTEGER (0..159),

n320-r17 INTEGER (0..319),

n640-r17 INTEGER (0..639),

n1280-r17 INTEGER (0..1279),

n2560-r17 INTEGER (0..2559),

n5120-r17 INTEGER (0..5119),

n10240-r17 INTEGER (0..10239),

n20480-r17 INTEGER (0..20479),

…

},

scs60-r17 CHOICE {

n16-r17 INTEGER (0..15),

n20-r17 INTEGER (0..19),

n32-r17 INTEGER (0..31),

n40-r17 INTEGER (0..39),

n64-r17 INTEGER (0..63),

n80-r17 INTEGER (0..79),

n128-r17 INTEGER (0..127),

n160-r17 INTEGER (0..159),

n256-r17 INTEGER (0..255),

n320-r17 INTEGER (0..319),

n640-r17 INTEGER (0..639),

n1280-r17 INTEGER (0..1279),

n2560-r17 INTEGER (0..2559),

n5120-r17 INTEGER (0..5119),

n10240-r17 INTEGER (0..10239),

n20480-r17 INTEGER (0..20479),

n40960-r17 INTEGER (0..40959),

…

},

scs120-r17 CHOICE {

n32-r17 INTEGER (0..31),

n40-r17 INTEGER (0..39),

n64-r17 INTEGER (0..63),

n80-r17 INTEGER (0..79),

n128-r17 INTEGER (0..127),

n160-r17 INTEGER (0..159),

n256-r17 INTEGER (0..255),

n320-r17 INTEGER (0..319),

n512-r17 INTEGER (0..511),

n640-r17 INTEGER (0..639),

n1280-r17 INTEGER (0..1279),

n2560-r17 INTEGER (0..2559),

n5120-r17 INTEGER (0..5119),

n10240-r17 INTEGER (0..10239),

n20480-r17 INTEGER (0..20479),

n40960-r17 INTEGER (0..40959),

n81920-r17 INTEGER (0..81919),

…

},

…

}

— TAG-DL-PPW-PRECONFIG-STOP

— ASN1STOP

DL-PPW-PreConfig field descriptions
dl-PPW-ID Indicates the pre-configured ID for DL-PRS processing window configuration.
length Indicates the length of DL-PRS processing window in slots. Value 1 indicates length of one slot, value 2 indicates length of two slots and so on.
periodicity Indicates the periodicity of the DL-PRS processing window.
priority Indicates the priority between PDCCH/PDSCH/CSI-RS and PRS as specified in TS 38.214 [19].
type Indicates the DL-PRS processing window type as specified in TS 38.214 [19].

Conditional Presence	Explanation
MultiType	The field is mandatory present when the UE reports its capability on supporting multiple processing types, otherwise it is absent.
MultiState	The field is mandatory present when the UE reports its capability on supporting option 1 or option 2 for the configured type, otherwise it is absent

– DMRS-BundlingPUCCH-Config

The IE DMRS-BundlingPUCCH-Config-r17 is used to configure DMRS bundling for PUCCH.

DMRS-BundlingPUCCH-Config information element

— ASN1START

— TAG-DMRS-BUNDLINGPUCCH-CONFIG-START

DMRS-BundlingPUCCH-Config-r17 ::= SEQUENCE {

pucch-DMRS-Bundling-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pucch-TimeDomainWindowLength-r17 INTEGER (2..8) OPTIONAL, — Need S

pucch-WindowRestart-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pucch-FrequencyHoppingInterval-r17 ENUMERATED {s2, s4, s5, s10} OPTIONAL, — Need S

…

}

— TAG-DMRS-BUNDLINGPUCCH-CONFIG-STOP

— ASN1STOP

DMRS-BundlingPUCCH-Config field descriptions

pucch-DMRS-Bundling Indicates whether DMRS bundling and time domain window for PUCCH are jointly enabled.

pucch-FrequencyHoppingInterval Configures the number of consecutive slots for the UE to perform inter-slot frequency hopping with inter-slot bundling for PUCCH. When both inter-frequency hopping and DMRS bundling are enabled for PUCCH repetitions, the UE is expected to be configured with at least one pucch-FrequencyHoppingInterval-r17 and pucch-TimeDomainWindowLength-r17. When DMRS bundling for PUCCH is enabled by pucch-DMRS-Bundling-r17, PUCCH frequency hopping interval is only determined by the configuration of PUCCH hopping interval if PUCCH hopping interval is configured. If the field is absent, the number of consecutive slots for the UE to perform inter-slot PUCCH frequency hopping is indicated by pucch-TimeDomainWindowLength-r17.

pucch-TimeDomainWindowLength Configures the length of a nominal time domain window in slots for DMRS bundling for PUCCH. The value shall not exceed the maximum duration for DMRS bundling for PUCCH as specified in TS 38.306 [26]. If this field is absent, the UE shall apply the default value that is the minimum value in the unit of consecutive slots of the time duration for the transmission of all PUCCH repetitions and the maximum duration for DMRS bundling for PUCCH as specified in TS 38.306 [26].

pucch-WindowRestart Indicates whether UE bundles PUCCH DMRS remaining in a nominal time domain window after event(s) triggered by DCI or MAC CE that violate power consistency and phase continuity requirements is enabled (see TS 38.214 [19], clause 6.1.7). NOTE: Events, which are triggered by DCI or MAC CE, but regarded as semi-static events, e.g. frequency hopping, UL beam switching for multi-TRP operation, or other if defined, are excluded.

– DMRS-BundlingPUSCH-Config

The IE DMRS-BundlingPUSCH-Config-r17 is used to configure DMRS bundling for PUSCH.

DMRS-BundlingPUSCH-Config information element

— ASN1START

— TAG-DMRS-BUNDLINGPUSCH-CONFIG-START

DMRS-BundlingPUSCH-Config-r17 ::= SEQUENCE {

pusch-DMRS-Bundling-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pusch-TimeDomainWindowLength-r17 INTEGER (2..32) OPTIONAL, — Need S

pusch-WindowRestart-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pusch-FrequencyHoppingInterval-r17 ENUMERATED {s2, s4, s5, s6, s8, s10, s12, s14, s16, s20} OPTIONAL, — Need S

…

}

— TAG-DMRS-BUNDLINGPUSCH-CONFIG-STOP

— ASN1STOP

DMRS-BundlingPUSCH-Config field descriptions

pusch-DMRS-Bundling Indicates whether DMRS bundling and time domain window for PUSCH are jointly enabled.

pusch-FrequencyHoppingInterval Configures the number of consecutive slots for the UE to perform inter-slot frequency hopping with inter-slot bundling for PUSCH. When both inter-frequency hopping and DMRS bundling are enabled for PUSCH repetitions, the UE is expected to be configured with at least one pusch-FrequencyHoppingInterval-r17 and pusch-TimeDomainWindowLength-r17. This parameter is shared for both DG-PUSCH and CG-PUSCH. When DMRS bundling for PUSCH is enabled by pusch-DMRS-Bundling-r17, PUSCH frequency hopping interval is only determined by the configuration of PUSCH hopping interval if PUSCH hopping interval is configured. If the field is absent, the number of consecutive slots for the UE to perform inter-slot PUSCH frequency hopping is indicated by pusch-TimeDomainWindowLength-r17. Note: For unpaired spectrum, the UE is not expected to be configured the value of s6, s8, s12, s14 and s16.

pusch-TimeDomainWindowLength Configures the length of a nominal time domain window in number of consecutive slots for DMRS bundling for PUSCH. The value shall not exceed the maximum duration for DMRS bundling for PUSCH as specified in TS 38.306 [26]. For PUSCH repetition type A/B, if this field is absent, the UE shall apply the default value that is the minimum value in the unit of consecutive slots of the time duration for the transmission of all PUSCH repetitions and the maximum duration for DMRS bundling for PUSCH as specified in TS 38.306 [26]. For TBoMS, if this field is absent, the UE shall apply the default value that is the minimum value in the unit of consecutive slots of the duration of TBoMS transmission (including repetition of TBoMS) and the maximum duration for DMRS bundling for PUSCH as specified in TS 38.306 [26].

pusch-WindowRestart Indicates whether UE bundles PUSCH DMRS remaining in a nominal time domain window after event(s) triggered by DCI or MAC CE that violate power consistency and phase continuity requirements is enabled (see TS 38.214 [19], clause 6.1.7). NOTE: Events, which are triggered by DCI or MAC CE, but regarded as semi-static events, e.g. frequency hopping, UL beam switching for multi-TRP operation, or other if defined, are excluded.

– DMRS-DownlinkConfig

The IE DMRS-DownlinkConfig is used to configure downlink demodulation reference signals for PDSCH.

DMRS-DownlinkConfig information element

— ASN1START

— TAG-DMRS-DOWNLINKCONFIG-START

DMRS-DownlinkConfig ::= SEQUENCE {

dmrs-Type ENUMERATED {type2} OPTIONAL, — Need S

dmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, — Need S

maxLength ENUMERATED {len2} OPTIONAL, — Need S

scramblingID0 INTEGER (0..65535) OPTIONAL, — Need S

scramblingID1 INTEGER (0..65535) OPTIONAL, — Need S

phaseTrackingRS SetupRelease { PTRS-DownlinkConfig } OPTIONAL, — Need M

…,

[[

dmrs-Downlink-r16 ENUMERATED {enabled} OPTIONAL — Need R

]]

}

— TAG-DMRS-DOWNLINKCONFIG-STOP

— ASN1STOP

DMRS-DownlinkConfig field descriptions

dmrs-AdditionalPosition Position for additional DM-RS in DL, see Tables 7.4.1.1.2-3 and 7.4.1.1.2-4 in TS 38.211 [16]. If the field is absent, the UE applies the value pos2. See also clause 7.4.1.1.2 for additional constraints on how the network may set this field depending on the setting of other fields.

dmrs-Downlink This field indicates whether low PAPR DMRS is used, as specified in TS38.211 [16], clause 7.4.1.1.1.

dmrs-Type Selection of the DMRS type to be used for DL (see TS 38.211 [16], clause 7.4.1.1.1). If the field is absent, the UE uses DMRS type 1.

maxLength The maximum number of OFDM symbols for DL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1. If set to len2, the UE determines the actual number of DM-RS symbols by the associated DCI. (see TS 38.211 [16], clause 7.4.1.1.2).

phaseTrackingRS Configures downlink PTRS. If the field is not configured, the UE assumes that downlink PTRS are absent. See TS 38.214 [19] clause 5.1.6.3.

scramblingID0 DL DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.1.1). When the field is absent the UE applies the value physCellId configured for this serving cell.

scramblingID1 DL DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.1.1). When the field is absent the UE applies the value physCellId configured for this serving cell.

– DMRS-UplinkConfig

The IE DMRS-UplinkConfig is used to configure uplink demodulation reference signals for PUSCH.

DMRS-UplinkConfig information element

— ASN1START

— TAG-DMRS-UPLINKCONFIG-START

DMRS-UplinkConfig ::= SEQUENCE {

dmrs-Type ENUMERATED {type2} OPTIONAL, — Need S

dmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, — Need S

phaseTrackingRS SetupRelease { PTRS-UplinkConfig } OPTIONAL, — Need M

maxLength ENUMERATED {len2} OPTIONAL, — Need S

transformPrecodingDisabled SEQUENCE {

scramblingID0 INTEGER (0..65535) OPTIONAL, — Need S

scramblingID1 INTEGER (0..65535) OPTIONAL, — Need S

…,

[[

dmrs-Uplink-r16 ENUMERATED {enabled} OPTIONAL — Need R

]]

} OPTIONAL, — Need R

transformPrecodingEnabled SEQUENCE {

nPUSCH-Identity INTEGER(0..1007) OPTIONAL, — Need S

sequenceGroupHopping ENUMERATED {disabled} OPTIONAL, — Need S

sequenceHopping ENUMERATED {enabled} OPTIONAL, — Need S

…,

[[

dmrs-UplinkTransformPrecoding-r16 SetupRelease {DMRS-UplinkTransformPrecoding-r16} OPTIONAL — Need M

]]

} OPTIONAL, — Need R

…

}

DMRS-UplinkTransformPrecoding-r16 ::= SEQUENCE {

pi2BPSK-ScramblingID0 INTEGER(0..65535) OPTIONAL, — Need S

pi2BPSK-ScramblingID1 INTEGER(0..65535) OPTIONAL — Need S

}

— TAG-DMRS-UPLINKCONFIG-STOP

— ASN1STOP

DMRS-UplinkConfig field descriptions

dmrs-AdditionalPosition Position for additional DM-RS in UL (see TS 38.211 [16], clause 6.4.1.1.3). If the field is absent, the UE applies the value pos2. See also clause 6.4.1.1.3 for additional constraints on how the network may set this field depending on the setting of other fields.

dmrs-Type Selection of the DMRS type to be used for UL (see TS 38.211 [16], clause 6.4.1.1.3) If the field is absent, the UE uses DMRS type 1.

dmrs-Uplink This field indicates whether low PAPR DMRS is used, as specified in TS38.211 [16], clause 6.4.1.1.1.1.

dmrs-UplinkTransformPrecoding This field indicates whether low PAPR DMRS is used for PUSCH with pi/2 BPSK modulation, as specified in TS38.211 [16], clause 6.4.1.1.1.2. The network configures this field only if tp-pi2BPSK is configured in PUSCH-Config.

maxLength The maximum number of OFDM symbols for UL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1. If set to len2, the UE determines the actual number of DM-RS symbols by the associated DCI. (see TS 38.211 [16], clause 6.4.1.1.3).

nPUSCH-Identity Parameter: N_ID^(PUSCH) for DFT-s-OFDM DMRS. If the value is absent or released, the UE uses the value Physical cell ID (physCellId). See TS 38.211 [16].

phaseTrackingRS Configures uplink PTRS (see TS 38.211 [16]).

pi2BPSK-ScramblingID0, pi2BPSK-ScramblingID1 UL DMRS scrambling initialization for pi/2 BPSK DMRS for PUSCH (see TS 38.211 [16], Clause 6.4.1.1.2). When the field is absent the UE applies the value Physical cell ID (physCellId) of the serving cell.

scramblingID0 UL DMRS scrambling initialization for CP-OFDM (see TS 38.211 [16], clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID (physCellId).

scramblingID1 UL DMRS scrambling initialization for CP-OFDM. (see TS 38.211 [16], clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID (physCellId).

sequenceGroupHopping For DMRS transmission with transform precoder the NW may configure group hopping by the cell-specific parameter groupHoppingEnabledTransformPrecoding in PUSCH-ConfigCommon. In this case, the NW may include this UE specific field to disable group hopping for PUSCH transmission except for Msg3, i.e., to override the configuration in PUSCH-ConfigCommon (see TS 38.211 [16]). If the field is absent, the UE uses the same hopping mode as for Msg3.

sequenceHopping Determines if sequence hopping is enabled for DMRS transmission with transform precoder for PUSCH transmission other than Msg3 (sequence hopping is always disabled for Msg3). If the field is absent, the UE uses the same hopping mode as for msg3. The network does not configure simultaneous group hopping and sequence hopping. See TS 38.211 [16], clause 6.4.1.1.1.2.

transformPrecodingDisabled DMRS related parameters for Cyclic Prefix OFDM.

transformPrecodingEnabled DMRS related parameters for DFT-s-OFDM (Transform Precoding).

– DownlinkConfigCommon

The IE DownlinkConfigCommon provides common downlink parameters of a cell.

DownlinkConfigCommon information element

— ASN1START

— TAG-DOWNLINKCONFIGCOMMON-START

DownlinkConfigCommon ::= SEQUENCE {

frequencyInfoDL FrequencyInfoDL OPTIONAL, — Cond InterFreqHOAndServCellAdd

initialDownlinkBWP BWP-DownlinkCommon OPTIONAL, — Cond ServCellAdd

…,

[[

initialDownlinkBWP-RedCap-r17 BWP-DownlinkCommon OPTIONAL — Need R

]]

}

— TAG-DOWNLINKCONFIGCOMMON-STOP

— ASN1STOP

DownlinkConfigCommon field descriptions

frequencyInfoDL Basic parameters of a downlink carrier and transmission thereon.

initialDownlinkBWP The initial downlink BWP configuration for a serving cell. The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain.

initialDownlinkBWP-RedCap If present, RedCap UEs use this DL BWP instead of initialDownlinkBWP. If absent, RedCap UEs use initialDownlinkBWP provided that it does not exceed the RedCap UE maximum bandwidth (see also clause 5.2.2.4.2).

Conditional Presence	Explanation
InterFreqHOAndServCellAdd	This field is mandatory present for inter-frequency handover, and upon serving cell (PSCell/SCell) addition. Otherwise, the field is optionally present, Need M.
ServCellAdd	This field is mandatory present upon serving cell addition (for PSCell and SCell) and upon handover from E-UTRA to NR. It is optionally present, Need M otherwise.

– DownlinkConfigCommonSIB

The IE DownlinkConfigCommonSIB provides common downlink parameters of a cell.

DownlinkConfigCommonSIB information element

— ASN1START

— TAG-DOWNLINKCONFIGCOMMONSIB-START

DownlinkConfigCommonSIB ::= SEQUENCE {

frequencyInfoDL FrequencyInfoDL-SIB,

initialDownlinkBWP BWP-DownlinkCommon,

bcch-Config BCCH-Config,

pcch-Config PCCH-Config,

…,

[[

pei-Config-r17 PEI-Config-r17 OPTIONAL, — Need R

initialDownlinkBWP-RedCap-r17 BWP-DownlinkCommon OPTIONAL — Need R

]]

}

BCCH-Config ::= SEQUENCE {

modificationPeriodCoeff ENUMERATED {n2, n4, n8, n16},

…

}

PCCH-Config ::= SEQUENCE {

defaultPagingCycle PagingCycle,

nAndPagingFrameOffset CHOICE {

oneT NULL,

halfT INTEGER (0..1),

quarterT INTEGER (0..3),

oneEighthT INTEGER (0..7),

oneSixteenthT INTEGER (0..15)

},

ns ENUMERATED {four, two, one},

firstPDCCH-MonitoringOccasionOfPO CHOICE {

sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139),

sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279),

sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559),

sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119),

sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239),

sCS480KHZoneT-SCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479),

sCS480KHZhalfT-SCS120KHZoneEighthT-SCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959),

sCS480KHZquarterT-SCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919)

} OPTIONAL, — Need R

…,

[[

nrofPDCCH-MonitoringOccasionPerSSB-InPO-r16 INTEGER (2..4) OPTIONAL — Cond SharedSpectrum2

]],

[[

ranPagingInIdlePO-r17 ENUMERATED {true} OPTIONAL, — Need R

firstPDCCH-MonitoringOccasionOfPO-v1710 CHOICE {

sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839),

sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..71679)

} OPTIONAL — Need R

]]

}

PEI-Config-r17 ::= SEQUENCE {

po-NumPerPEI-r17 ENUMERATED {po1, po2, po4, po8},

payloadSizeDCI-2-7-r17 INTEGER (1..maxDCI-2-7-Size-r17),

pei-FrameOffset-r17 INTEGER (0..16),

subgroupConfig-r17 SubgroupConfig-r17,

lastUsedCellOnly-r17 ENUMERATED {true} OPTIONAL, — Need R

…

}

SubgroupConfig-r17 ::= SEQUENCE {

subgroupsNumPerPO-r17 INTEGER (1.. maxNrofPagingSubgroups-r17),

subgroupsNumForUEID-r17 INTEGER (1.. maxNrofPagingSubgroups-r17) OPTIONAL, — Need S

…

}

— TAG-DOWNLINKCONFIGCOMMONSIB-STOP

— ASN1STOP

DownlinkConfigCommonSIB field descriptions

bcch-Config The modification period related configuration.

frequencyInfoDL-SIB Basic parameters of a downlink carrier and transmission thereon.

initialDownlinkBWP The initial downlink BWP configuration for a PCell. The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain. The UE applies the locationAndBandwidth upon reception of this field (e.g. to determine the frequency position of signals described in relation to this locationAndBandwidth) but it keeps CORESET#0 until after reception of RRCSetup/RRCResume/RRCReestablishment.

initialDownlinkBWP-RedCap If present, RedCap UEs use this DL BWP instead of initialDownlinkBWP. If the locationAndBandwidth of this BWP contains the entire CORESET#0, the UE applies the locationAndBandwidth upon reception of this field (e.g. to determine the frequency position of signals described in relation to this locationAndBandwidth) but it keeps CORESET#0 until after reception of RRCSetup/RRCResume/RRCReestablishment. Otherwise, i.e., if the locationAndBandwidth of this BWP does not contain the entire CORESET#0, the UE uses this BWP for receiving DL messages during initial access (Msg2, MsgB, Msg4) and after initial access. If absent, RedCap UEs use initialDownlinkBWP provided that it does not exceed the RedCap UE maximum bandwidth (see also clause 5.2.2.4.2).

lastUsedCellOnly When present, the field indicates that the UE monitors PEI only if the latest received RRCRelease without noLastCellUpdate is from this cell. A PEI-capable UE stores its last used cell information.

nrofPDCCH-MonitoringOccasionPerSSB-InPO The number of PDCCH monitoring occasions corresponding to an SSB within a Paging Occasion, see TS 38.304 [20], clause 7.1.

pcch-Config The paging related configuration.

pei-Config The PEI related configuration.

subgroupConfig The paging subgroup related configuration.

BCCH-Config field descriptions

modificationPeriodCoeff Actual modification period, expressed in number of radio frames m = modificationPeriodCoeff * defaultPagingCycle, see clause 5.2.2.2.2. n2 corresponds to value 2, n4 corresponds to value 4, and so on.

PCCH-Config field descriptions

defaultPagingCycle Default paging cycle, used to derive ‘T’ in TS 38.304 [20]. Value rf32 corresponds to 32 radio frames, value rf64 corresponds to 64 radio frames and so on.

firstPDCCH-MonitoringOccasionOfPO Points out the first PDCCH monitoring occasion for paging of each PO of the PF, see TS 38.304 [20].

nAndPagingFrameOffset Used to derive the number of total paging frames in T (corresponding to parameter N in TS 38.304 [20]) and paging frame offset (corresponding to parameter PF_offset in TS 38.304 [20]). A value of oneSixteenthT corresponds to T / 16, a value of oneEighthT corresponds to T / 8, and so on. If pagingSearchSpace is set to zero and if SS/PBCH block and CORESET multiplexing pattern is 2 or 3 (as specified in TS 38.213 [13]): – for ssb-periodicityServingCell of 5 or 10 ms, N can be set to one of {oneT, halfT, quarterT, oneEighthT, oneSixteenthT} – for ssb-periodicityServingCell of 20 ms, N can be set to one of {halfT, quarterT, oneEighthT, oneSixteenthT} – for ssb-periodicityServingCell of 40 ms, N can be set to one of {quarterT, oneEighthT, oneSixteenthT} – for ssb-periodicityServingCell of 80 ms, N can be set to one of {oneEighthT, oneSixteenthT} – for ssb-periodicityServingCell of 160 ms, N can be set to oneSixteenthT If pagingSearchSpace is set to zero and if SS/PBCH block and CORESET multiplexing pattern is 1 (as specified in TS 38.213 [13]), N can be set to one of {halfT, quarterT, oneEighthT, oneSixteenthT} If pagingSearchSpace is not set to zero, N can be configured to one of {oneT, halfT, quarterT, oneEighthT, oneSixteenthT}

ns Number of paging occasions per paging frame.

ranPagingInIdlePO Indicates that the network supports to send RAN paging in PO that corresponds to the i_s as determined by UE in RRC_IDLE state, see TS38.304 [20].

PEI-Config field descriptions

payloadSizeDCI-2-7 Payload size of PEI DCI, i.e., DCI format 2_7. The size is no larger than the payload size of paging DCI which has maximum of 41 bits and 43 bits for licensed and unlicensed spectrums, respectively.

pei-FrameOffset Offset, in number of frames from the start of a reference frame for PEI-O to the start of a first paging frame of the paging frames associated with the PEI-O, see TS 38.213 [13], clause 10.4A.

po-NumPerPEI The number of PO(s) associated with one PEI monitoring occasion. It is a factor of the total PO number in a paging cycle, i.e N x Ns, as specified in TS 38.304 [20]. The maximum number of PF associated with one PEI monitoring occasion is 2. The number of PO mapping to one PEI should be multiple of Ns when po-NumPerPEI is larger than Ns.

SubgroupConfig field descriptions

subgroupsNumPerPO Total number of subgroups per Paging Occasion (PO) for UE to read subgroups indication from physical-layer signaling. The field represents the sum of CN-assigned and UEID-based subgroups supported by the network. When PEI-Config is configured, there is always at least one subgroup (UEID-based subgroup or CN-assigned subgroup) configured.

subgroupsNumForUEID Number of subgroups per Paging Occasion (PO) for UE to read subgroups indication from physical-layer signaling, for UEID-based subgrouping method. When present, the field is set to an integer smaller than or equal to subgroupsNumPerPO. subgroupsNumPerPO equals to subgroupsNumForUEID when the network does not support CN-assigned subgrouping. The field is absent when the network only supports CN-assigned subgrouping. Both this field and subgroupsNumPerPO are equal to 1 when the network does not support subgrouping.

Conditional Presence	Explanation
SharedSpectrum2	The field is optional present, Need R, if this cell operates with shared spectrum channel access. Otherwise, it is absent, Need R.

– DownlinkPreemption

The IE DownlinkPreemption is used to configure the UE to monitor PDCCH for the INT-RNTI (interruption).

DownlinkPreemption information element

— ASN1START

— TAG-DOWNLINKPREEMPTION-START

DownlinkPreemption ::= SEQUENCE {

int-RNTI RNTI-Value,

timeFrequencySet ENUMERATED {set0, set1},

dci-PayloadSize INTEGER (0..maxINT-DCI-PayloadSize),

int-ConfigurationPerServingCell SEQUENCE (SIZE (1..maxNrofServingCells)) OF INT-ConfigurationPerServingCell,

…

}

INT-ConfigurationPerServingCell ::= SEQUENCE {

servingCellId ServCellIndex,

positionInDCI INTEGER (0..maxINT-DCI-PayloadSize-1)

}

— TAG-DOWNLINKPREEMPTION-STOP

— ASN1STOP

DownlinkPreemption field descriptions

dci-PayloadSize Total length of the DCI payload scrambled with INT-RNTI (see TS 38.213 [13], clause 11.2).

int-ConfigurationPerServingCell Indicates (per serving cell) the position of the 14 bit INT values inside the DCI payload (see TS 38.213 [13], clause 11.2).

int-RNTI RNTI used for indication pre-emption in DL (see TS 38.213 [13], clause 10).

timeFrequencySet Set selection for DL-preemption indication (see TS 38.213 [13], clause 11.2) The set determines how the UE interprets the DL preemption DCI payload.

INT-ConfigurationPerServingCell field descriptions

positionInDCI Starting position (in number of bit) of the 14 bit INT value applicable for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2). Must be multiples of 14 (bit).

– DRB-Identity

The IE DRB-Identity is used to identify a DRB used by a UE.

DRB-Identity information element

— ASN1START

— TAG-DRB-IDENTITY-START

DRB-Identity ::= INTEGER (1..32)

— TAG-DRB-IDENTITY-STOP

— ASN1STOP

– DRX-Config

The IE DRX-Config is used to configure DRX related parameters.

DRX-Config information element

— ASN1START

— TAG-DRX-CONFIG-START

DRX-Config ::= SEQUENCE {

drx-onDurationTimer CHOICE {

subMilliSeconds INTEGER (1..31),

milliSeconds ENUMERATED {

ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60,

ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200,

ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }

},

drx-InactivityTimer ENUMERATED {

ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80,

ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8,

spare7, spare6, spare5, spare4, spare3, spare2, spare1},

drx-HARQ-RTT-TimerDL INTEGER (0..56),

drx-HARQ-RTT-TimerUL INTEGER (0..56),

drx-RetransmissionTimerDL ENUMERATED {

sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128,

sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9,

spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1},

drx-RetransmissionTimerUL ENUMERATED {

sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128,

sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9,

spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 },

drx-LongCycleStartOffset CHOICE {

ms10 INTEGER(0..9),

ms20 INTEGER(0..19),

ms32 INTEGER(0..31),

ms40 INTEGER(0..39),

ms60 INTEGER(0..59),

ms64 INTEGER(0..63),

ms70 INTEGER(0..69),

ms80 INTEGER(0..79),

ms128 INTEGER(0..127),

ms160 INTEGER(0..159),

ms256 INTEGER(0..255),

ms320 INTEGER(0..319),

ms512 INTEGER(0..511),

ms640 INTEGER(0..639),

ms1024 INTEGER(0..1023),

ms1280 INTEGER(0..1279),

ms2048 INTEGER(0..2047),

ms2560 INTEGER(0..2559),

ms5120 INTEGER(0..5119),

ms10240 INTEGER(0..10239)

},

shortDRX SEQUENCE {

drx-ShortCycle ENUMERATED {

ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32,

ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9,

spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 },

drx-ShortCycleTimer INTEGER (1..16)

} OPTIONAL, — Need R

drx-SlotOffset INTEGER (0..31)

}

DRX-ConfigExt-v1700 ::= SEQUENCE {

drx-HARQ-RTT-TimerDL-r17 INTEGER (0..448),

drx-HARQ-RTT-TimerUL-r17 INTEGER (0..448)

}

— TAG-DRX-CONFIG-STOP

— ASN1STOP

DRX-Config field descriptions

drx-HARQ-RTT-TimerDL Value in number of symbols of the BWP where the transport block was received. drx-HARQ-RTT-TimerDL-r17 is only applicable for SCS 480 kHz and 960 kHz. If configured, the UE shall ignore drx-HARQ-RTT-TimerDL (without suffix) for SCS 480 kHz and 960 kHz.

drx-HARQ-RTT-TimerUL Value in number of symbols of the BWP where the transport block was transmitted. drx-HARQ-RTT-TimerUL-r17 is only applicable for SCS 480 kHz and 960 kHz. If configured, the UE shall ignore drx-HARQ-RTT-TimerUL (without suffix) for SCS 480 kHz and 960 kHz.

drx-InactivityTimer Value in multiple integers of 1 ms. ms0 corresponds to 0, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on.

drx-LongCycleStartOffset drx-LongCycle in ms and drx-StartOffset in multiples of 1 ms. If drx-ShortCycle is configured, the value of drx-LongCycle shall be a multiple of the drx-ShortCycle value.

drx-onDurationTimer Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on.

drx-RetransmissionTimerDL Value in number of slot lengths of the BWP where the transport block was received. value sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on.

drx-RetransmissionTimerUL Value in number of slot lengths of the BWP where the transport block was transmitted. sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on.

drx-ShortCycleTimer Value in multiples of drx-ShortCycle. A value of 1 corresponds to drx-ShortCycle, a value of 2 corresponds to 2 * drx-ShortCycle and so on.

drx-ShortCycle Value in ms. ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on.

drx-SlotOffset Value in 1/32 ms. Value 0 corresponds to 0 ms, value 1 corresponds to 1/32 ms, value 2 corresponds to 2/32 ms, and so on.

– DRX-ConfigSecondaryGroup

The IE DRX-ConfigSecondaryGroup is used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3].

DRX-ConfigSecondaryGroup information element

— ASN1START

— TAG-DRX-CONFIGSECONDARYGROUP-START

DRX-ConfigSecondaryGroup-r16 ::= SEQUENCE {

drx-onDurationTimer-r16 CHOICE {

subMilliSeconds INTEGER (1..31),

milliSeconds ENUMERATED {

ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60,

ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200,

ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }

},

drx-InactivityTimer-r16 ENUMERATED {

ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80,

ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8,

spare7, spare6, spare5, spare4, spare3, spare2, spare1}

}

— TAG-DRX-CONFIGSECONDARYGROUP-STOP

— ASN1STOP

DRX-ConfigSecondaryGroup field descriptions

drx-InactivityTimer Value in multiple integers of 1 ms. ms0 corresponds to 0 ms, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on, as specified in TS 38.321 [3]. The network configures a drx-InactivityTimer value for the second DRX group that is smaller than the drx-InactivityTimer configured for the default DRX group in IE DRX-Config.

drx-onDurationTimer Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSeconds). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on, as specified in TS 38.321 [3]. The network configures a drx-onDurationTimer value for the second DRX group that is smaller than the drx-onDurationTimer configured for the default DRX group in IE DRX-Config.

– DRX-ConfigSL

The IE DRX-ConfigSL is used to configure additional DRX parameters for the UE performing sidelink operation with resource allocation mode 1, as specified in TS 38.321 [3].

DRX-ConfigSL information element

— ASN1START

— TAG-DRX-CONFIGSL-START

DRX-ConfigSL-r17 ::= SEQUENCE {

drx-HARQ-RTT-TimerSL-r17 INTEGER (0..56),

drx-RetransmissionTimerSL-r17 ENUMERATED {sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128,

sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8,

spare7, spare6, spare5, spare4, spare3, spare2, spare1}

}

— TAG-DRX-CONFIGSL-STOP

— ASN1STOP

DRX-ConfigSL field descriptions

drx-HARQ-RTT-TimerSL Value in number of symbols of the BWP where the PDCCH was transmitted.

drx-RetransmissionTimerSL Value in number of slot lengths of the BWP where the PDCCH was transmitted. sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on.

– EphemerisInfo

The IE EphemerisInfo provides satellite ephemeris. Ephemeris may be expressed either in format of position and velocity state vector or in format of orbital parameters.

EphemerisInfo information element

— ASN1START

— TAG-EPHEMERISINFO-START

EphemerisInfo-r17 ::= CHOICE {

positionVelocity-r17 PositionVelocity-r17,

orbital-r17 Orbital-r17

}

PositionVelocity-r17 ::= SEQUENCE {

positionX-r17 PositionStateVector-r17,

positionY-r17 PositionStateVector-r17,

positionZ-r17 PositionStateVector-r17,

velocityVX-r17 VelocityStateVector-r17,

velocityVY-r17 VelocityStateVector-r17,

velocityVZ-r17 VelocityStateVector-r17

}

Orbital-r17 ::= SEQUENCE {

semiMajorAxis-r17 INTEGER (0..8589934591),

eccentricity-r17 INTEGER (0..1048575),

periapsis-r17 INTEGER (0..268435455),

longitude-r17 INTEGER (0..268435455),

inclination-r17 INTEGER (-67108864..67108863),

meanAnomaly-r17 INTEGER (0..268435455)

}

PositionStateVector-r17 ::= INTEGER (-33554432..33554431)

VelocityStateVector-r17 ::= INTEGER (-131072..131071)

— TAG-EPHEMERISINFO-STOP

— ASN1STOP

EphemerisInfo field descriptions

eccentricity Satellite orbital parameter: eccentricity e, see NIMA TR 8350.2 [71]. Unit is radian. Step of 1.431 * 10-8. Actual value = field value * (1.431 * 10-8).

inclination Satellite orbital parameter: inclination i, see NIMA TR 8350.2 [71]. Unit is radian. Step of 2.341* 10-8 rad. Actual value = field value * (2.341* 10-8).

longitude Satellite orbital parameter: longitude of ascending node Ω, see NIMA TR 8350.2 [71]. Unit is radian. Step of 2.341* 10-8 rad. Actual value = field value * (2.341* 10-8).

meanAnomaly Satellite orbital parameter: Mean anomaly M at epoch time, see NIMA TR 8350.2 [71]. Unit is radian. Step of 2.341* 10-8 rad. Actual value = field value * (2.341* 10-8).

periapsis Satellite orbital parameter: argument of periapsis ω, see NIMA TR 8350.2 [71]. Unit is radian. Step of 2.341* 10-8 rad. Actual value = field value * (2.341* 10-8).

positionX, positionY, positionZ X, Y, Z coordinate of satellite position state vector in ECEF. Unit is meter. Step of 1.3 m. Actual value = field value * 1.3.

semiMajorAxis Satellite orbital parameter: semi major axis α, see NIMA TR 8350.2 [71]. Unit is meter. Step of 4.249 * 10-3 m. Actual value = 6500000 + field value * (4.249 * 10-3).

velocityVX, velocityVY, velocityVZ X, Y, Z coordinate of satellite velocity state vector in ECEF. Unit is meter/second. Step of 0.06 m/s. Actual value = field value * 0.06.

– FeatureCombination

The IE FeatureCombination indicates a feature or a combination of features to be associated with a set of Random Access resources (i.e. an instance of FeatureCombinationPreambles).

FeatureCombination information element

— ASN1START

— TAG-FEATURECOMBINATION-START

FeatureCombination-r17 ::= SEQUENCE {

redCap-r17 ENUMERATED {true} OPTIONAL, — Need R

smallData-r17 ENUMERATED {true} OPTIONAL, — Need R

nsag-r17 NSAG-List-r17 OPTIONAL, — Need R

msg3-Repetitions-r17 ENUMERATED {true} OPTIONAL, — Need R

spare4 ENUMERATED {true} OPTIONAL, — Need R

spare3 ENUMERATED {true} OPTIONAL, — Need R

spare2 ENUMERATED {true} OPTIONAL, — Need R

spare1 ENUMERATED {true} OPTIONAL — Need R

}

NSAG-List-r17 ::= SEQUENCE (SIZE (1.. maxSliceInfo-r17)) OF NSAG-ID-r17

— TAG-FEATURECOMBINATION-STOP

— ASN1STOP

FeatureCombination field descriptions

redCap If present, this field indicates that RedCap is part of this feature combination.

smallData If present, this field indicates that Small Data is part of this feature combination.

nsag If present, this field indicates NSAG(s) that are part of this feature combination.

msg3-Repetitions If present, this field indicates that signalling of msg3 repetition is part of this feature combination. This field is not configured in a set of preambles that is configured with 2-step random-access type.

– FeatureCombinationPreambles

The IE FeatureCombinationPreambles associates a set of preambles with a feature combination. For parameters which can be provided in this IE, the UE applies this field value when performing Random Access using a preamble in this featureCombinationPreambles, otherwise the UE applies the corresponding value as determined by applicable Need Code, e.g. Need S. On a specific BWP, there can be at most one set of preambles associated with a given feature combination per RA Type (i.e. 4-step RACH or 2-step RACH).

FeatureCombinationPreambles information element

— ASN1START

— TAG-FEATURECOMBINATIONPREAMBLES-START

FeatureCombinationPreambles-r17 ::= SEQUENCE {

featureCombination-r17 FeatureCombination-r17,

startPreambleForThisPartition-r17 INTEGER (0..63),

numberOfPreamblesPerSSB-ForThisPartition-r17 INTEGER (1..64),

ssb-SharedRO-MaskIndex-r17 INTEGER (1..15) OPTIONAL, — Need S

groupBconfigured-r17 SEQUENCE {

ra-SizeGroupA-r17 ENUMERATED {b56, b144, b208, b256, b282, b480, b640,

b800, b1000, b72, spare6, spare5,spare4, spare3, spare2, spare1},

messagePowerOffsetGroupB-r17 ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18},

numberOfRA-PreamblesGroupA-r17 INTEGER (1..64)

} OPTIONAL, — Need R

separateMsgA-PUSCH-Config-r17 MsgA-PUSCH-Config-r16 OPTIONAL, — Cond MsgAConfigCommon

msgA-RSRP-Threshold-r17 RSRP-Range OPTIONAL, — Need R

rsrp-ThresholdSSB-r17 RSRP-Range OPTIONAL, — Need R

deltaPreamble-r17 INTEGER (-1..6) OPTIONAL, — Need R

…

}

— TAG-FEATURECOMBINATIONPREAMBLES-STOP

— ASN1STOP

FeatureCombinationPreambles field descriptions

deltaPreamble Power offset between msg3 or msgA-PUSCH and RACH preamble transmission. If configured, this parameter overrides msg3-DeltaPreamble or msgA-DeltaPreamble, Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1). If msgA-DeltaPreamble is configured in separateMsgA-PUSCH-Config-r17, this field is absent.

featureCombination Indicates which combination of features that the preambles indicated by this IE are associated with. The UE ignores a RACH resource defined by this FeatureCombinationPreambles if any feature within the featureCombination is not supported by the UE or if any of the spare fields within the featureCombination is set to true.

messagePowerOffsetGroupB Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to –infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on (see TS 38.321 [3], clause 5.1.2).

msgA-RSRP-Threshold The UE selects 2-step random access type to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). This field is only present if both 2-step and 4-step RA type are configured for the concerned feature combination in the BWP. If configured, this parameter overrides msgA-RSRP-Threshold-r16. If absent, the UE applies msgA-RSRP-Threshold-r16, if configured

numberOfPreamblesPerSSB-ForThisPartition It determines how many consecutive preambles are associated to the Feature Combination starting from the starting preamble(s) per SSB.

numberOfRA-PreamblesGroupA It determines how many consecutive preambles per SSB are associated to Group A starting from the starting preamble(s). The remaining preambles associated to the Feature Combination are associated to Group B

ra-SizeGroupA Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see TS 38.321 [3], clause 5.1.2). If this feature combination preambles are associated to a RACH-ConfigCommon-twostepRA, this field correspond to ra-MsgA-SizeGroupA, otherwise it corresponds to ra-Msg3SizeGroupA.

rsrp-ThresholdSSB L1-RSRP threshold used for determining whether a candidate beam may be used by the UE. If this parameter is included in FeatureCombinationPreambles which is included in RACH-ConfigCommonTwoStepRA, it corresponds to msgA-RSRP-ThresholdSSB, as defined in TS 38.321 [3]. If this parameter is included in FeatureCombinationPreambles which is included in RACH-ConfigCommon, it it corresponds to rsrp-ThresholdSSB, as defined in TS 38.321 [3].

separateMsgA-PUSCH-Config If present it specifies how the 2-step RACH preambles identified by this FeatureCombinationPreambles are mapped to a PUSCH slot separate from the one defined in MsgA-ConfigCommon-r16. If the field is absent, the UE should apply the corresponding parameter in the RACH-ConfigCommonTwoStepRA of the BWP which includes the FeatureCombinationPreambles IE.

ssb-SharedRO-MaskIndex Mask index (see TS 38.321 [3]). Indicates a subset of ROs where preambles are allocated for this feature combination. If this field is configured within FeatureCombinationPreambles which is included in RACH-ConfigCommonTwoStepRA, it indicates a subset of ROs configured within this RACH-ConfigCommonTwoStepRA. This field is configured when there is more than one RO per SSB. If the field is absent, all ROs configured in RACH-ConfigCommon or RACH-ConfigCommonTwoStepRA containing this FeatureCombinationPreambles are shared.

startPreambleForThisPartition It defines the first preamble associated with the Feature Combination. If the UE is provided with a number N of SSB block indexes associated with one PRACH occasion, and N<1, the first preamble in each PRACH occasion is the one having the same index as indicated by this field. If N>=1, N blocks of preambles associated with the Feature Combination are defined, each having start index + startPreambleForThisPartition, where n refers to SSB block index (see TS 38.213 [13], clause 8.1).

Conditional Presence	Explanation
MsgAConfigCommon	The field is optionally present, Need S, if FeatureCombinationPreambles is included in RACH-ConfigCommonTwoStepRA. Otherwise, it is absent. If the field is absent in FeatureCombinationPreambles included in RACH-ConfigCommonTwoStepRA, the UE applies MsgA-PUSCH-Config included in the corresponding MsgA-ConfigCommon.

– FilterCoefficient

The IE FilterCoefficient specifies the measurement filtering coefficient. Value fc0 corresponds to k = 0, fc1 corresponds to k = 1, and so on.

FilterCoefficient information element

— ASN1START

— TAG-FILTERCOEFFICIENT-START

FilterCoefficient ::= ENUMERATED { fc0, fc1, fc2, fc3, fc4, fc5, fc6, fc7, fc8, fc9, fc11, fc13, fc15, fc17, fc19, spare1, …}

— TAG-FILTERCOEFFICIENT-STOP

— ASN1STOP

– FreqBandIndicatorNR

The IE FreqBandIndicatorNR is used to convey an NR frequency band number as defined in TS 38.101-1 [15] and TS 38.101-2 [39].

FreqBandIndicatorNR information element

— ASN1START

— TAG-FREQBANDINDICATORNR-START

FreqBandIndicatorNR ::= INTEGER (1..1024)

— TAG-FREQBANDINDICATORNR-STOP

— ASN1STOP

– FreqPriorityListDedicatedSlicing

The IE FreqPriorityListDedicatedSlicing provides dedicated cell reselection priorities for slicing in RRCRelease.

FreqPriorityListDedicatedSlicing information element

— ASN1START

— TAG-FREQPRIORITYLISTDEDICATEDSLICING-START

FreqPriorityListDedicatedSlicing-r17 ::= SEQUENCE (SIZE (1.. maxFreq)) OF FreqPriorityDedicatedSlicing-r17

FreqPriorityDedicatedSlicing-r17 ::= SEQUENCE {

dl-ExplicitCarrierFreq-r17 ARFCN-ValueNR,

sliceInfoListDedicated-r17 SliceInfoListDedicated-r17 OPTIONAL — Cond Mandatory

}

SliceInfoListDedicated-r17 ::= SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF SliceInfoDedicated-r17

SliceInfoDedicated-r17 ::= SEQUENCE {

nsag-IdentityInfo-r17 NSAG-IdentityInfo-r17,

nsag-CellReselectionPriority-r17 CellReselectionPriority OPTIONAL, — Need R

nsag-CellReselectionSubPriority-r17 CellReselectionSubPriority OPTIONAL — Need R

}

— TAG-FREQPRIORITYLISTDEDICATEDSLICING-STOP

— ASN1STOP

FreqPriorityDedicatedSlicing field descriptions
dl-ExplicitCarrierFreq Indicates the downlink carrier frequency to which SliceInfoListDedicated is associated.

Conditional Presence	Explanation
Mandatory	The field is mandatory present.

– FreqPriorityListSlicing

The IE FreqPriorityListSlicing indicates cell reselection priorities for slicing in SIB16.

FreqPriorityListSlicing information element

— ASN1START

— TAG-FREQPRIORITYLISTSLICING-START

FreqPriorityListSlicing-r17 ::= SEQUENCE (SIZE (1..maxFreqPlus1)) OF FreqPrioritySlicing-r17

FreqPrioritySlicing-r17 ::= SEQUENCE {

dl-ImplicitCarrierFreq-r17 INTEGER (0..maxFreq),

sliceInfoList-r17 SliceInfoList-r17 OPTIONAL — Cond Mandatory

}

SliceInfoList-r17 ::= SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF SliceInfo-r17

SliceInfo-r17 ::= SEQUENCE {

nsag-IdentityInfo-r17 NSAG-IdentityInfo-r17,

nsag-CellReselectionPriority-r17 CellReselectionPriority OPTIONAL, — Need R

nsag-CellReselectionSubPriority-r17 CellReselectionSubPriority OPTIONAL, — Need R

sliceCellListNR-r17 CHOICE {

sliceAllowedCellListNR-r17 SliceCellListNR-r17,

sliceExcludedCellListNR-r17 SliceCellListNR-r17

} OPTIONAL — Need R

}

SliceCellListNR-r17 ::= SEQUENCE (SIZE (1..maxCellSlice-r17)) OF PCI-Range

— TAG-FREQPRIORITYLISTSLICING-STOP

— ASN1STOP

FreqPriorityListSlicing field descriptions
dl-ImplicitCarrierFreq Indicates the downlink carrier frequency to which sliceInfoList is associated with. The frequency is signalled implicitly, value 0 corresponds to the serving frequency, value 1 corresponds to the first frequency indicated by the InterFreqCarrierFreqList in SIB4, and value 2 coresponds to the second frequency indicated by the InterFreqCarrierFreqList in SIB4, and so on.

SliceInfo field descriptions
sliceAllowedCellListNR List of allow-listed cells for slicing. If present, the cells listed in this list support the corresponding nsag-frequency pair, and the cells not listed in this list do not support the corresponding nsag-frequency pair, according to TS 38.304 [20], clause 5.2.4.11.
sliceCellListNR Contains either the list of allow-listed or exclude-listed cells for slicing. If absent, it implies all the cells support the corresponding nsag-frequency pair, according to 38.304 [20], clause 5.2.4.11.
sliceExcludedCellListNR List of exclude-listed cells for slicing. If present, the cells listed in this list do not support the corresponding nsag-frequency pair, and the cells not listed in this list support the corresponding nsag-frequency pair, according to TS 38.304 [20], clause 5.2.4.11.

Conditional Presence	Explanation
Mandatory	The field is mandatory present.

– FrequencyInfoDL

The IE FrequencyInfoDL provides basic parameters of a downlink carrier and transmission thereon.

FrequencyInfoDL information element

— ASN1START

— TAG-FREQUENCYINFODL-START

FrequencyInfoDL ::= SEQUENCE {

absoluteFrequencySSB ARFCN-ValueNR OPTIONAL, — Cond SpCellAdd

frequencyBandList MultiFrequencyBandListNR,

absoluteFrequencyPointA ARFCN-ValueNR,

scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier,

…

}

— TAG-FREQUENCYINFODL-STOP

— ASN1STOP

FrequencyInfoDL field descriptions

absoluteFrequencyPointA Absolute frequency position of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A (see TS 38.211 [16], clause 4.4.4.2). Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList.

absoluteFrequencySSB Frequency of the SSB to be used for this serving cell. SSB related parameters (e.g. SSB index) provided for a serving cell refer to this SSB frequency unless mentioned otherwise. The cell-defining SSB of the PCell is always on the sync raster. Frequencies are considered to be on the sync raster if they are also identifiable with a GSCN value (see TS 38.101-1 [15]). If the field is absent, the SSB related parameters should be absent, e.g. ssb-PositionsInBurst, ssb-periodicityServingCell and subcarrierSpacing in ServingCellConfigCommon IE. If the field is absent, the UE obtains timing reference from the SpCell or an SCell if applicable as described in TS 38.213 [13], clause 4.1. This is only supported in case the SCell for which the UE obtains the timing reference is in the same frequency band as the cell (i.e. the SpCell or the SCell, respectively) from which the UE obtains the timing reference. For cells supporting RedCap, if FrequencyInfoDL is included in the ReconfigurationWithSync, this field corresponds to the cell-defining SSB.

frequencyBandList List containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported.

scs-SpecificCarrierList A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see TS 38.211 [16], clause 5.3).

Conditional Presence	Explanation
SpCellAdd	The field is mandatory present if this FrequencyInfoDL is for SpCell. Otherwise the field is optionally present, Need S.

– FrequencyInfoDL-SIB

The IE FrequencyInfoDL-SIB provides basic parameters of a downlink carrier and transmission thereon.

FrequencyInfoDL-SIB information element

— ASN1START

— TAG-FREQUENCYINFODL-SIB-START

FrequencyInfoDL-SIB ::= SEQUENCE {

frequencyBandList MultiFrequencyBandListNR-SIB,

offsetToPointA INTEGER (0..2199),

scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier

}

— TAG-FREQUENCYINFODL-SIB-STOP

— ASN1STOP

FrequencyInfoDL-SIB field descriptions

offsetToPointA Represents the offset to Point A as defined in TS 38.211 [16], clause 4.4.4.2.

frequencyBandList List of one or multiple frequency bands to which this carrier(s) belongs.

scs-SpecificCarrierList A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see TS 38.211 [16], clause 5.3). The network configures this for all SCSs that are used in DL BWPs in this serving cell.

– FrequencyInfoUL

The IE FrequencyInfoUL provides basic parameters of an uplink carrier and transmission thereon.

FrequencyInfoUL information element

— ASN1START

— TAG-FREQUENCYINFOUL-START

FrequencyInfoUL ::= SEQUENCE {

frequencyBandList MultiFrequencyBandListNR OPTIONAL, — Cond FDD-OrSUL

absoluteFrequencyPointA ARFCN-ValueNR OPTIONAL, — Cond FDD-OrSUL

scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier,

additionalSpectrumEmission AdditionalSpectrumEmission OPTIONAL, — Need S

p-Max P-Max OPTIONAL, — Need S

frequencyShift7p5khz ENUMERATED {true} OPTIONAL, — Cond FDD-TDD-OrSUL-Optional

…

}

— TAG-FREQUENCYINFOUL-STOP

— ASN1STOP

FrequencyInfoUL field descriptions

absoluteFrequencyPointA Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see TS 38.211 [16], clause 4.4.4.2).

additionalSpectrumEmission The additional spectrum emission requirements to be applied by the UE on this uplink. If the field is absent, the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1 [15], table 6.2.3.1-1A, and TS 38.101-2 [39], table 6.2.3.1-2). Network configures the same value in additionalSpectrumEmission for all uplink carrier(s) of the same band with UL configured, except for additionalSpectrumEmission value corresponding to NS_55/NS_57. If NS_55/NS_57 (see TS 38.101-1 [15], table 6.2.3.1-1) is applicable for at least one uplink carrier, the network may configure either NS_55/NS_57 or NS_01 for these uplink carriers, and NS_01 for the remaining uplink carrier(s) of band n77. The additionalSpectrumEmission is applicable for all uplink carriers of the same band with UL configured.

frequencyBandList List containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported.

frequencyShift7p5khz Enable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled.

p-Max Maximum transmit power allowed in this serving cell. The maximum transmit power that the UE may use on this serving cell may be additionally limited by p-NR-FR1 (configured for the cell group) and by p-UE-FR1 (configured total for all serving cells operating on FR1). If absent, the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. Value in dBm. This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63].

scs-SpecificCarrierList A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see TS 38.211 [16], clause 5.3).

Conditional Presence	Explanation
FDD-OrSUL	The field is mandatory present if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL) or if this FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R, otherwise (if this FrequencyInfoUL is for an unpaired UL (TDD).
FDD-TDD-OrSUL-Optional	The field is optionally present, Need R, if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL), or if this FrequencyInfoUL is for an unpaired UL (TDD) in certain bands (as defined in clause 5.4.2.1 of TS 38.101-1 and in clause 5.4.2.1 of TS 38.104 [12]), or if this FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R, otherwise.

– FrequencyInfoUL-SIB

The IE FrequencyInfoUL-SIB provides basic parameters of an uplink carrier and transmission thereon.

FrequencyInfoUL-SIB information element

— ASN1START

— TAG-FREQUENCYINFOUL-SIB-START

FrequencyInfoUL-SIB ::= SEQUENCE {

frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, — Cond FDD-OrSUL

absoluteFrequencyPointA ARFCN-ValueNR OPTIONAL, — Cond FDD-OrSUL

scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier,

p-Max P-Max OPTIONAL, — Need S

frequencyShift7p5khz ENUMERATED {true} OPTIONAL, — Cond FDD-TDD-OrSUL-Optional

…

}

— TAG-FREQUENCYINFOUL-SIB-STOP

— ASN1STOP

FrequencyInfoUL-SIB field descriptions

absoluteFrequencyPointA Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see TS 38.211 [16], clause 4.4.4.2).

frequencyBandList Provides the frequency band indicator and a list of additionalPmax and additionalSpectrumEmission values as defined in TS 38.101-1 [15], table 6.2.3.1-1, and TS 38.101-2 [39], table 6.2.3.1-2. The UE shall apply the first listed band which it supports in the frequencyBandList field.

frequencyShift7p5khz Enable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled.

p-Max Value in dBm applicable for the cell. If absent the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63].

scs-SpecificCarrierList A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see TS 38.211 [16], clause 5.3). The network configures this for all SCSs that are used in UL BWPs configured in this serving cell.

Conditional Presence	Explanation
FDD-OrSUL	The field is mandatory present if this FrequencyInfoUL-SIB is for the paired UL for a DL (defined in a FrequencyInfoDL-SIB) or if this FrequencyInfoUL-SIB is for a supplementary uplink (SUL). It is absent otherwise (if this FrequencyInfoUL-SIB is for an unpaired UL (TDD).
FDD-TDD-OrSUL-Optional	The field is optionally present, Need R, if this FrequencyInfoUL-SIB is for the paired UL for a DL (defined in a FrequencyInfoDL-SIB), or if this FrequencyInfoUL-SIB is for an unpaired UL (TDD) in certain bands (as defined in clause 5.4.2.1 of TS 38.101-1 and in clause 5.4.2.1 of TS 38.104 [12]), or if this FrequencyInfoUL-SIB is for a supplementary uplink (SUL). It is absent otherwise.

– GapPriority

The IE GapPriority is used to identify the priority of a gap configuration.

GapPriority information element

— ASN1START

— TAG-GAPPRIORITY-START

GapPriority-r17 ::= INTEGER (1..maxNrOfGapPri-r17)

— TAG-GAPPRIORITY-STOP

— ASN1STOP

– HighSpeedConfig

The IE HighSpeedConfig is used to configure parameters for high speed scenarios.

HighSpeedConfig information element

— ASN1START

— TAG-HIGHSPEEDCONFIG-START

HighSpeedConfig-r16 ::= SEQUENCE {

highSpeedMeasFlag-r16 ENUMERATED {true} OPTIONAL, — Need R

highSpeedDemodFlag-r16 ENUMERATED {true} OPTIONAL, — Need R

…

}

HighSpeedConfig-v1700 ::= SEQUENCE {

highSpeedMeasCA-Scell-r17 ENUMERATED {true} OPTIONAL, — Need R

highSpeedMeasInterFreq-r17 ENUMERATED {true} OPTIONAL, — Need R

highSpeedDemodCA-Scell-r17 ENUMERATED {true} OPTIONAL, — Need R

…

}

HighSpeedConfigFR2-r17 ::= SEQUENCE {

highSpeedMeasFlagFR2-r17 ENUMERATED {set1, set2} OPTIONAL, — Need R

highSpeedDeploymentTypeFR2-r17 ENUMERATED {unidirectional, bidirectional} OPTIONAL, — Need R

highSpeedLargeOneStepUL-TimingFR2-r17 ENUMERATED {true} OPTIONAL, — Need R

…

}

— TAG-HIGHSPEEDCONFIG-STOP

— ASN1STOP

HighSpeedConfig field descriptions
HighSpeedDemodCA-Scell If the field is present and UE supports demodulationEnhancementCA-r17, the UE shall apply the enhanced demodulation processing for HST-SFN joint transmission scheme with velocity up to 500km/h as specified in TS 38.101-4 [59]. This parameter only applies to SCell.
highSpeedDemodFlag If the field is present and UE supports demodulationEnhancement-r16, the UE shall apply the enhanced demodulation processing for HST-SFN joint transmission scheme with velocity up to 500km/h as specified in TS 38.101-4 [59]. This parameter only applies to SpCell.
highSpeedDeploymentTypeFR2 If the field is present, and field value is unidirectional, the UE shall assume uni-directional deployment or if field value is birectional the UE shall assume bidirectional deployment for FR2 up to 350km/h as specified in TS 38.133 [14].
highSpeedLargeOneSteptUL-TimingFR2 If the field is present, large one step UE autonomous uplink transmit timing adjustment for FR2 up to 350km/h as specified in TS 38.133 [14] is enabled.
highSpeedMeasCA-Scell If the field is present and UE supports measurementEnhancementCA-r17, the UE shall apply the enhanced RRM requirements to SCell for carrier aggregation to support high speed up to 500 km/h as specified in TS 38.133 [14]. This parameter only applies to SCell.
highSpeedMeasFlag If the field is present and UE supports measurementEnhancement-r16, the UE shall apply the enhanced intra-NR and inter-RAT EUTRAN RRM requirements to support high speed up to 500 km/h as specified in TS 38.133 [14]. If the field is present and UE supports intraNR-MeasurementEnhancement-r16, the UE shall apply enhanced intra-NR RRM requirement to support high speed up to 500 km/h as specified in TS 38.133 [14]. If the field is present and UE supports interRAT-MeasurementEnhancement-r16, the UE shall apply enhanced inter-RAT EUTRAN RRM requirement to support high speed up to 500 km/h as specified in TS 38.133 [14]. This parameter only applies to SpCell.
highSpeedMeasFlagFR2 If the field is present, the UE shall apply enhanced intra-NR RRM requirement set one to support high speed up to 350 km/h for FR2 as specified in TS 38.133 [14], if the field value is set1 or RRM requirement set two if the field value is set2.
highSpeedMeasInterFreq If the field is present and UE supports measurementEnhancementInterFreq-r17, the UE shall apply the enhanced RRM requirements for inter-frequency measurement in RRC_CONNECTED to support high speed up to 500 km/h as specified in TS 38.133 [14].

– Hysteresis

The IE Hysteresis is a parameter used within the entry and leave condition of an event triggered reporting condition. The actual value is field value * 0.5 dB.

Hysteresis information element

— ASN1START

— TAG-HYSTERESIS-START

Hysteresis ::= INTEGER (0..30)

— TAG-HYSTERESIS-STOP

— ASN1STOP

– HysteresisLocation

The IE HysteresisLocation is a parameter used within entry and leave condition of a location based event triggered reporting condition. The actual value is field value * 10 meters.

HysteresisLocation information element

— ASN1START

— TAG-HYSTERESISLOCATION-START

HysteresisLocation-r17 ::= INTEGER (0..32768)

— TAG-HYSTERESISLOCATION-STOP

— ASN1STOP

– InvalidSymbolPattern

The IE InvalidSymbolPattern is used to configure one invalid symbol pattern for PUSCH transmission repetition type B applicable for both DCI format 0_1 and 0_2, see TS 38.214 [19], clause 6.1.

InvalidSymbolPattern information element

— ASN1START

— TAG-INVALIDSYMBOLPATTERN-START

InvalidSymbolPattern-r16 ::= SEQUENCE {

symbols-r16 CHOICE {

oneSlot BIT STRING (SIZE (14)),

twoSlots BIT STRING (SIZE (28))

},

periodicityAndPattern-r16 CHOICE {

n2 BIT STRING (SIZE (2)),

n4 BIT STRING (SIZE (4)),

n5 BIT STRING (SIZE (5)),

n8 BIT STRING (SIZE (8)),

n10 BIT STRING (SIZE (10)),

n20 BIT STRING (SIZE (20)),

n40 BIT STRING (SIZE (40))

} OPTIONAL, — Need M

…

}

— TAG-INVALIDSYMBOLPATTERN-STOP

— ASN1STOP

InvalidSymbolPattern field descriptions

periodicityAndPattern A time domain repetition pattern at which the pattern defined by symbols recurs. This slot pattern repeats itself continuously. When the field is not configured, the UE uses the value n1 (see TS 38.214 [19], clause 6.1).

symbols A symbol level bitmap in time domain (see TS 38.214[19], clause 6.1). For oneSlot, if ECP is configured, the first 12 bits represent the symbols within the slot and the last two bits within the bitstring are ignored by the UE; Otherwise, the 14 bits represent the symbols within the slot. For twoSlots, if ECP is configured, the first 12 bits represent the symbols within the first slot and the next 12 bits represent the symbols in the second slot and the last four bits within the bit string are ignored by the UE; Otherwise, the first 14 bits represent the symbols within the first slot and the next 14 bits represent the symbols in the second slot. For the bits representing symbols in a slot, the most significant bit of the bit string represents the first symbol in the slot and the second most significant bit represents the second symbol in the slot and so on. This pattern recurs (in time domain) with the configured periodicityAndPattern.

– I-RNTI-Value

The IE I-RNTI-Value is used to identify the suspended UE context of a UE in RRC_INACTIVE.

I-RNTI-Value information element

— ASN1START

— TAG-I-RNTI-VALUE-START

I-RNTI-Value ::= BIT STRING (SIZE(40))

— TAG-I-RNTI-VALUE-STOP

— ASN1STOP

– LBT-FailureRecoveryConfig

The IE LBT-FailureRecoveryConfig-r16 is used to configure the parameters used for detection of consistent uplink LBT failures for operation with shared spectrum channel access, as specified in TS 38.321 [3].

LBT-FailureRecoveryConfig information element

— ASN1START

— TAG-LBT-FAILURERECOVERYCONFIG-START

LBT-FailureRecoveryConfig-r16 ::= SEQUENCE {

lbt-FailureInstanceMaxCount-r16 ENUMERATED {n4, n8, n16, n32, n64, n128},

lbt-FailureDetectionTimer-r16 ENUMERATED {ms10, ms20, ms40, ms80, ms160, ms320},

…

}

— TAG-LBT-FAILURERECOVERYCONFIG-STOP

— ASN1STOP

LBT-FailureRecoveryConfig field descriptions

lbt-FailureDetectionTimer Timer for consistent uplink LBT failure detection (see TS 38.321 [3]). Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on.

lbt-FailureInstanceMaxCount This field determines after how many LBT failure indications received from the physical layer the UE triggers uplink LBT failure recovery (see TS 38.321 [3]). Value n4 corresponds to 4, value n8 corresponds to 8, and so on.

– LocationInfo

The IE LocationInfo is used to transfer available detailed location information, Bluetooth, WLAN and sensor available measurement results at the UE.

LocationInfo information element

— ASN1START

— TAG-LOCATIONINFO-START

LocationInfo-r16 ::= SEQUENCE {

commonLocationInfo-r16 CommonLocationInfo-r16 OPTIONAL,

bt-LocationInfo-r16 LogMeasResultListBT-r16 OPTIONAL,

wlan-LocationInfo-r16 LogMeasResultListWLAN-r16 OPTIONAL,

sensor-LocationInfo-r16 Sensor-LocationInfo-r16 OPTIONAL,

…

}

— TAG-LOCATIONINFO-STOP

— ASN1STOP

– LocationMeasurementInfo

The IE LocationMeasurementInfo defines the information sent by the UE to the network to assist with the configuration of measurement gaps for location related measurements.

LocationMeasurementInfo information element

— ASN1START

— TAG-LOCATIONMEASUREMENTINFO-START

LocationMeasurementInfo ::= CHOICE {

eutra-RSTD EUTRA-RSTD-InfoList,

…,

eutra-FineTimingDetection NULL,

nr-PRS-Measurement-r16 NR-PRS-MeasurementInfoList-r16

}

EUTRA-RSTD-InfoList ::= SEQUENCE (SIZE (1..maxInterRAT-RSTD-Freq)) OF EUTRA-RSTD-Info

EUTRA-RSTD-Info ::= SEQUENCE {

carrierFreq ARFCN-ValueEUTRA,

measPRS-Offset INTEGER (0..39),

…

}

NR-PRS-MeasurementInfoList-r16 ::= SEQUENCE (SIZE (1..maxFreqLayers)) OF NR-PRS-MeasurementInfo-r16

NR-PRS-MeasurementInfo-r16 ::= SEQUENCE {

dl-PRS-PointA-r16 ARFCN-ValueNR,

nr-MeasPRS-RepetitionAndOffset-r16 CHOICE {

ms20-r16 INTEGER (0..19),

ms40-r16 INTEGER (0..39),

ms80-r16 INTEGER (0..79),

ms160-r16 INTEGER (0..159),

…

},

nr-MeasPRS-length-r16 ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20},

…

}

— TAG-LOCATIONMEASUREMENTINFO-STOP

— ASN1STOP

LocationMeasurementInfo field descriptions
carrierFreq The EARFCN value of the carrier received from upper layers for which the UE needs to perform the inter-RAT RSTD measurements.
measPRS-Offset Indicates the requested gap offset for performing RSTD measurements towards E-UTRA. It is the smallest subframe offset from the beginning of subframe 0 of SFN=0 of the serving cell of the requested gap for measuring PRS positioning occasions in the carrier frequency carrierFreq for which the UE needs to perform the inter-RAT RSTD measurements. The PRS positioning occasion information is received from upper layers. The value of measPRS-Offset is obtained by mapping the starting subframe of the PRS positioning occasion in the measured cell onto the corresponding subframe in the serving cell and is calculated as the serving cell’s number of subframes from SFN=0 mod 40. The UE shall take into account any additional time required by the UE to start PRS measurements on the other carrier when it does this mapping for determining the measPRS-Offset. NOTE: Figure 6.2.2-1 in TS 36.331[10] illustrates the measPRS-Offset field.
dl-PRS-PointA The ARFCN value of the carrier received from upper layers for which the UE needs to perform the NR DL-PRS measurements.
nr-MeasPRS-RepetitionAndOffset Indicates the gap periodicity in ms and offset in number of subframes of the requested measurement gap for performing NR DL-PRS measurements.
nr-MeasPRS-length Indicates measurement gap length in ms of the requested measurement gap for performing NR DL-PRS measurements. The measurement gap length is according to in Table 9.1.2-1 in TS 38.133 [14].

– LogicalChannelConfig

The IE LogicalChannelConfig is used to configure the logical channel parameters.

LogicalChannelConfig information element

— ASN1START

— TAG-LOGICALCHANNELCONFIG-START

LogicalChannelConfig ::= SEQUENCE {

ul-SpecificParameters SEQUENCE {

priority INTEGER (1..16),

prioritisedBitRate ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, kBps512,

kBps1024, kBps2048, kBps4096, kBps8192, kBps16384, kBps32768, kBps65536, infinity},

bucketSizeDuration ENUMERATED {ms5, ms10, ms20, ms50, ms100, ms150, ms300, ms500, ms1000,

spare7, spare6, spare5, spare4, spare3,spare2, spare1},

allowedServingCells SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex

OPTIONAL, — Cond PDCP-CADuplication

allowedSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SubcarrierSpacing OPTIONAL, — Need R

maxPUSCH-Duration ENUMERATED {ms0p02, ms0p04, ms0p0625, ms0p125, ms0p25, ms0p5, ms0p01-v1700, spare1}

OPTIONAL, — Need R

configuredGrantType1Allowed ENUMERATED {true} OPTIONAL, — Need R

logicalChannelGroup INTEGER (0..maxLCG-ID) OPTIONAL, — Need R

schedulingRequestID SchedulingRequestId OPTIONAL, — Need R

logicalChannelSR-Mask BOOLEAN,

logicalChannelSR-DelayTimerApplied BOOLEAN,

…,

bitRateQueryProhibitTimer ENUMERATED {s0, s0dot4, s0dot8, s1dot6, s3, s6, s12, s30} OPTIONAL, — Need R

[[

allowedCG-List-r16 SEQUENCE (SIZE (0.. maxNrofConfiguredGrantConfigMAC-1-r16)) OF ConfiguredGrantConfigIndexMAC-r16

OPTIONAL, — Need S

allowedPHY-PriorityIndex-r16 ENUMERATED {p0, p1} OPTIONAL — Need S

]],

[[

logicalChannelGroupIAB-Ext-r17 INTEGER (0..maxLCG-ID-IAB-r17) OPTIONAL, — Need R

allowedHARQ-mode-r17 ENUMERATED {harqModeA, harqModeB} OPTIONAL — Need R

]]

} OPTIONAL, — Cond UL

…,

[[

channelAccessPriority-r16 INTEGER (1..4) OPTIONAL, — Need R

bitRateMultiplier-r16 ENUMERATED {x40, x70, x100, x200} OPTIONAL — Need R

]]

}

— TAG-LOGICALCHANNELCONFIG-STOP

— ASN1STOP

LogicalChannelConfig field descriptions

allowedCG-List This restriction applies only when the UL grant is a configured grant. If present, UL MAC SDUs from this logical channel can only be mapped to the indicated configured grant configuration. If the size of the sequence is zero, then UL MAC SDUs from this logical channel cannot be mapped to any configured grant configurations. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any configured grant configurations. If the field configuredGrantType1Allowed is present, only those configured grant type 1 configuration indicated in this sequence are allowed for use by this logical channel; otherwise, this sequence shall not include any configured grant type 1 configuration. Corresponds to "allowedCG-List" as specified in TS 38.321 [3].

allowedHARQ-mode Indicates the allowed HARQ mode of a HARQ process mapped to this logical channel. If the parameter is absent, there is no restriction for HARQ mode for the mapping. This field applies to SRB1, SRB2 and DRBs.

allowedPHY-PriorityIndex This restriction applies only when the UL grant is a dynamic grant. If the field is present and the dynamic grant has a PHY-priority index, UL MAC SDUs from this logical channel can only be mapped to the dynamic grants indicating PHY-priority index equal to the values configured by this field. If the field is present and the dynamic grant does not have a PHY-priority index, UL MAC SDUs from this logical channel can only be mapped to this dynamic grant if the value of the field is p0, see TS 38.213 [13], clause 9. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any dynamic grants. Corresponds to "allowedPHY-PriorityIndex" as specified in TS 38.321 [3].

allowedSCS-List If present, UL MAC SDUs from this logical channel can only be mapped to the indicated numerology. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured numerology. Corresponds to ‘allowedSCS-List’ as specified in TS 38.321 [3]. Only the following values are applicable depending on the used frequency: FR1: 15, 30, or 60 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz

allowedServingCells If present, UL MAC SDUs from this logical channel can only be mapped to the serving cells indicated in this list. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured serving cell of this cell group. Corresponds to ‘allowedServingCells’ in TS 38.321 [3].

bitRateMultiplier Bit rate multiplier for recommended bit rate MAC CE as specified in TS 38.321 [3]. Value x40 indicates bit rate multiplier 40, value x70 indicates bit rate multiplier 70 and so on.

bitRateQueryProhibitTimer The timer is used for bit rate recommendation query in TS 38.321 [3], in seconds. Value s0 means 0 s, s0dot4 means 0.4 s and so on.

bucketSizeDuration Value in ms. ms5 corresponds to 5 ms, value ms10 corresponds to 10 ms, and so on.

channelAccessPriority Indicates the Channel Access Priority Class (CAPC), as specified in TS 38.300 [2], to be used on uplink transmissions for operation with shared spectrum channel access. The network configures this field only for SRB2 and DRBs.

configuredGrantType1Allowed If present, or if the capability lcp-Restriction as specified in TS 38.306 [26] is not supported, UL MAC SDUs from this logical channel can be transmitted on a configured grant type 1. Otherwise, UL MAC SDUs from this logical channel cannot be transmitted on a configured grant type 1. Corresponds to ‘configuredGrantType1Allowed’ in TS 38.321 [3].

logicalChannelGroup, logicalChannelGroupIAB-Ext ID of the logical channel group, as specified in TS 38.321 [3], which the logical channel belongs to. The logicalChannelGroupIAB-Ext is only applicable to the IAB-MT. When logicalChannelGroupIAB-Ext is configured, logicalChannelGroup shall be ignored.

logicalChannelSR-Mask Controls SR triggering when a configured uplink grant of type1 or type2 is configured. true indicates that SR masking is configured for this logical channel as specified in TS 38.321 [3].

logicalChannelSR-DelayTimerApplied Indicates whether to apply the delay timer for SR transmission for this logical channel. Set to false if logicalChannelSR-DelayTimer is not included in BSR-Config.

maxPUSCH-Duration If present, UL MAC SDUs from this logical channel can only be transmitted using uplink grants that result in a PUSCH duration shorter than or equal to the duration indicated by this field. Otherwise, UL MAC SDUs from this logical channel can be transmitted using an uplink grant resulting in any PUSCH duration. Corresponds to "maxPUSCH-Duration" in TS 38.321 [3]. The PUSCH duration is calculated based on the same length of all symbols, and the shortest length applies if the symbol lengths are different.

priority Logical channel priority, as specified in TS 38.321 [3].

prioritisedBitRate Value in kiloBytes/s. Value kBps0 corresponds to 0 kiloBytes/s, value kBps8 corresponds to 8 kiloBytes/s, value kBps16 corresponds to 16 kiloBytes/s, and so on. For SRBs, the value can only be set to infinity.

schedulingRequestId If present, it indicates the scheduling request configuration applicable for this logical channel, as specified in TS 38.321 [3].

Conditional Presence	Explanation
PDCP-CADuplication	The field is mandatory present if the DRB/SRB associated with this logical channel is configured with PDCP CA duplication in UL in the cell group in which this IE is included (i.e. the PDCP entity is associated with multiple RLC entities belonging to this cell group). Otherwise the field is optionally present, need R.
UL	The field is mandatory present for a logical channel with uplink if it serves DRB. It is optionally present, Need R, for a logical channel with uplink if it serves an SRB. Otherwise it is absent.

– LogicalChannelIdentity

The IE LogicalChannelIdentity is used to identify one logical channel (LogicalChannelConfig) and the corresponding RLC bearer (RLC-BearerConfig) or BH RLC channel (BH-RLC-ChannelConfig) or Uu Relay RLC channel (Uu-RelayRLC-ChannelConfig) or PC5 Relay RLC channel (SL-RLC-ChannelConfig).

LogicalChannelIdentity information element

— ASN1START

— TAG-LOGICALCHANNELIDENTITY-START

LogicalChannelIdentity ::= INTEGER (1..maxLC-ID)

— TAG-LOGICALCHANNELIDENTITY-STOP

— ASN1STOP

– LTE-NeighCellsCRS-AssistInfoList

The IE LTE-NeighCellsCRS-AssistInfoList-r17 is used to provide configuration information of neighbour LTE cells to assist the UE to perform CRS interference mitigation (CRS-IM) in scenarios with overlapping spectrum for LTE and NR.

LTE-NeighCellsCRS-AssistInfoList information element

— ASN1START

— TAG-LTE-NEIGHCELLSCRS-ASSISTINFOLIST-START

LTE-NeighCellsCRS-AssistInfoList-r17 ::= SEQUENCE (SIZE (1..maxNrofCRS-IM-InterfCell-r17)) OF LTE-NeighCellsCRS-AssistInfo-r17

LTE-NeighCellsCRS-AssistInfo-r17 ::= SEQUENCE {

neighCarrierBandwidthDL-r17 ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1} OPTIONAL, — Cond CRS-IM

neighCarrierFreqDL-r17 INTEGER (0..16383) OPTIONAL, — Need S

neighCellId-r17 EUTRA-PhysCellId OPTIONAL, — Need S

neighCRS-muting-r17 ENUMERATED {enabled} OPTIONAL, — Need R

neighMBSFN-SubframeConfigList-r17 EUTRA-MBSFN-SubframeConfigList OPTIONAL, — Need S

neighNrofCRS-Ports-r17 ENUMERATED {n1, n2, n4} OPTIONAL, — Need S

neighV-Shift-r17 ENUMERATED {n0, n1, n2, n3, n4, n5} OPTIONAL — Cond NotCellID

}

— TAG-LTE-NEIGHCELLSCRS-ASSISTINFOLIST-STOP

— ASN1STOP

LTE-NeighCellsCRS-AssistInfo field descriptions

neighCarrierBandwidthDL Indicates the channel bandwidth of the neighbour LTE cell in number of PRBs. If the field is absent, the UE applies the value of carrierBandwidthDL indicated in RateMatchPatternLTE-CRS for this serving cell, if configured.

neighCarrierFreqDL Indicates the downlink centre frequency of the neighbour LTE cell. If the field is absent, the UE applies the value of carrierFreqDL indicated in RateMatchPatternLTE-CRS for this serving cell, if configured.

neighCellId Indicates the physical cell ID of the neighbour LTE cell for which the other fields within the same LTE-NeighCellsCRS-AssistInfo apply. If the IE LTE-NeighCellsCRS-AssistInfoList contains multiple list entries, either this field or neighV-Shift is included in each instance. If the IE LTE-NeighCellsCRS-AssistInfoList contains multiple list entries, the entry with neighV-Shift is only used for neighbour LTE cells for which neighCellId is not provided (i.e. the entry with neighCellId takes precedence over the entry with neighV-Shift, if provided). If the IE LTE-NeighCellsCRS-AssistInfoList contains one list entry with neither this field nor neighV-Shift, the information within the entry applies to all neighbour LTE cells.

neighCRS-muting Indicates whether the CRS interference mitigation is enabled in the neighbour LTE cell, as specified in TS 36.133 [40], clause 3.6.1.1.

neighMBSFN-SubframeConfigList Indicates the MBSFN subframe configuration of the neighbour LTE cell. If RateMatchPatternLTE-CRS is configured for this serving cell and the field is absent, the UE applies the value of mbsfn-SubframeConfigList indicated in RateMatchPatternLTE-CRS for this serving cell if configured; otherwise, if the field is absent, the UE assumes MBSFN is not configured in the neighbour LTE cell.

neighNrofCRS-Ports Indicates the CRS antenna ports number of the neighbour LTE cell. If the field is absent, the UE applies the value of nrofCRS-Ports indicated in RateMatchPatternLTE-CRS for this serving cell, if configured. If RateMatchPatternLTE-CRS is not configured for this serving cell and the field is absent, the UE applies the default value n4.

neighV-Shift Indicates the shifting value v-shift of neighbour LTE cells for which the other fields within the same LTE-NeighCellsCRS-AssistInfo apply.

Conditional Presence	Explanation
CRS-IM	For the serving cell with 15kHz SCS, this field is mandatory present for the UE supporting the capability of crs-IM-nonDSS-NWA-15kHzSCS-r17, but not supporting crs-IM-nonDSS-15kHzSCS-r17, if RateMatchPatternLTE-CRS is not configured for this serving cell. Otherwise it is optionally present, Need S if RateMatchPatternLTE-CRS is configured for this serving cell; Need M otherwise. For the serving cell with 30kHz SCS, this field is mandatory present for the UE supporting the capability of crs-IM-nonDSS-NWA-30kHzSCS-r17, but not supporting crs-IM-nonDSS-30kHzSCS-r17, if RateMatchPatternLTE-CRS is not configured for this serving cell. Otherwise it is optionally present, Need S if RateMatchPatternLTE-CRS is configured for this serving cell; Need M otherwise.
NotCellID	If the field neighCellId is present, this field shall be absent; otherwise, it is optionally present if the IE LTE-NeighCellsCRS-AssistInfoList contains one list entry, Need S, or it is mandatory present if the IE LTE-NeighCellsCRS-AssistInfoList contains multiple list entries.

– MAC-CellGroupConfig

The IE MAC-CellGroupConfig is used to configure MAC parameters for a cell group, including DRX.

MAC-CellGroupConfig information element

— ASN1START

— TAG-MAC-CELLGROUPCONFIG-START

MAC-CellGroupConfig ::= SEQUENCE {

drx-Config SetupRelease { DRX-Config } OPTIONAL, — Need M

schedulingRequestConfig SchedulingRequestConfig OPTIONAL, — Need M

bsr-Config BSR-Config OPTIONAL, — Need M

tag-Config TAG-Config OPTIONAL, — Need M

phr-Config SetupRelease { PHR-Config } OPTIONAL, — Need M

skipUplinkTxDynamic BOOLEAN,

…,

[[

csi-Mask BOOLEAN OPTIONAL, — Need M

dataInactivityTimer SetupRelease { DataInactivityTimer } OPTIONAL — Cond MCG-Only

]],

[[

usePreBSR-r16 ENUMERATED {true} OPTIONAL, — Need R

schedulingRequestID-LBT-SCell-r16 SchedulingRequestId OPTIONAL, — Need R

lch-BasedPrioritization-r16 ENUMERATED {enabled} OPTIONAL, — Need R

schedulingRequestID-BFR-SCell-r16 SchedulingRequestId OPTIONAL, — Need R

drx-ConfigSecondaryGroup-r16 SetupRelease { DRX-ConfigSecondaryGroup-r16 } OPTIONAL — Need M

]],

[[

enhancedSkipUplinkTxDynamic-r16 ENUMERATED {true} OPTIONAL, — Need R

enhancedSkipUplinkTxConfigured-r16 ENUMERATED {true} OPTIONAL — Need R

]],

[[

intraCG-Prioritization-r17 ENUMERATED {enabled} OPTIONAL, — Cond LCH-PrioWithReTxTimer

drx-ConfigSL-r17 SetupRelease { DRX-ConfigSL-r17 } OPTIONAL, — Need M

drx-ConfigExt-v1700 SetupRelease { DRX-ConfigExt-v1700 } OPTIONAL, — Need M

schedulingRequestID-BFR-r17 SchedulingRequestId OPTIONAL, — Need R

schedulingRequestID-BFR2-r17 SchedulingRequestId OPTIONAL, — Need R

schedulingRequestConfig-v1700 SchedulingRequestConfig-v1700 OPTIONAL, — Need M

tar-Config-r17 SetupRelease { TAR-Config-r17 } OPTIONAL, — Need M

g-RNTI-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxG-RNTI-r17)) OF MBS-RNTI-SpecificConfig-r17 OPTIONAL, — Need N

g-RNTI-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxG-RNTI-r17)) OF MBS-RNTI-SpecificConfigId-r17 OPTIONAL, — Need N

g-CS-RNTI-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxG-CS-RNTI-r17)) OF MBS-RNTI-SpecificConfig-r17 OPTIONAL, — Need N

g-CS-RNTI-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxG-CS-RNTI-r17)) OF MBS-RNTI-SpecificConfigId-r17 OPTIONAL, — Need N

allowCSI-SRS-Tx-MulticastDRX-Active-r17 BOOLEAN OPTIONAL — Need M

]],

[[

schedulingRequestID-PosMG-Request-r17 SchedulingRequestId OPTIONAL, — Need R

drx-LastTransmissionUL-r17 ENUMERATED {enabled} OPTIONAL — Need R

]]

}

DataInactivityTimer ::= ENUMERATED {s1, s2, s3, s5, s7, s10, s15, s20, s40, s50, s60, s80, s100, s120, s150, s180}

MBS-RNTI-SpecificConfig-r17 ::= SEQUENCE {

mbs-RNTI-SpecificConfigId-r17 MBS-RNTI-SpecificConfigId-r17,

groupCommon-RNTI-r17 CHOICE {

g-RNTI RNTI-Value,

g-CS-RNTI RNTI-Value

},

drx-ConfigPTM-r17 SetupRelease { DRX-ConfigPTM-r17 } OPTIONAL, — Need M

harq-FeedbackEnablerMulticast-r17 ENUMERATED {dci-enabler, enabled} OPTIONAL, — Need S

harq-FeedbackOptionMulticast-r17 ENUMERATED {ack-nack, nack-only} OPTIONAL, — Cond HARQFeedback

pdsch-AggregationFactor-r17 ENUMERATED {n2, n4, n8} OPTIONAL — Cond G-RNTI

}

MBS-RNTI-SpecificConfigId-r17 ::= INTEGER (0..maxG-RNTI-1-r17)

— TAG-MAC-CELLGROUPCONFIG-STOP

— ASN1STOP

MAC-CellGroupConfig field descriptions

allowCSI-SRS-Tx-MulticastDRX-Active Used to control the CSI/SRS transmission during MBS multicast DRX ActiveTime, see TS 38.321 [3].

csi-Mask If set to true, the UE limits CSI reports to the on-duration period of the DRX cycle, see TS 38.321 [3].

dataInactivityTimer Releases the RRC connection upon data inactivity as specified in clause 5.3.8.5 and in TS 38.321 [3]. Value s1 corresponds to 1 second, value s2 corresponds to 2 seconds, and so on.

drx-Config, drx-ConfigExt Used to configure DRX as specified in TS 38.321 [3]. Network only configures drx-ConfigExt when drx-Config is configured.

drx-ConfigSecondaryGroup Used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3]. The network does not configure secondary DRX group with DCP simultaneously nor secondary DRX group with a dormant BWP simultaneously.

drx-ConfigSL Used to configure additional DRX parameters for the UE performing sidelink operation with resource allocation mode 1, as specified in TS 38.321 [3]. Network only configures this field if sl-ScheduledConfig is configured and drx-Config is configured.

drx-LastTransmissionUL If this field is present, the start of the drx-HARQ-RTT-TimerUL is after the last transmission within a bundle, see TS 38.321 [3].

g-RNTI-ConfigToAddModList List of G-RNTI configurations to add or modify. Up to 8 G-RNTIs can be configured in total in this release based on the UE capability.

g-RNTI-ConfigToReleaseList List of G-RNTI configurations to release.

g-CS-RNTI-ConfigToAddModList List of G-CS-RNTI configurations to add or modify. Up to 8 G-CS-RNTIs can be configured in total in this release based on the UE capability.

g-CS-RNTI-ConfigToReleaseList List of G-CS-RNTI configurations to release.

intraCG-Prioritization Used to enable HARQ process ID selection based on LCH-priority for one CG as specified in TS 38.321 [3].

lch-BasedPrioritization If this field is present, the corresponding MAC entity of the UE is configured with prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority, see TS 38.321 [3]. The network does not configure lch-BasedPrioritization with enhancedSkipUplinkTxDynamic simultaneously nor lch-BasedPrioritization with enhancedSkipUplinkTxConfigured simultaneously.

schedulingRequestID-BFR-SCell Indicates the scheduling request configuration applicable for BFR on SCell, as specified in TS 38.321 [3].

schedulingRequestID-BFR-r17 Indicates the scheduling request configuration (SchedulingRequestConfig) that the UE shall use upon detecting a beam failure on the detection resources configured in schedulingRequestID-BFR of a serving cell while beam failure is not detected on resources configured in failureDetectionSet2 of the same serving cell.

schedulingRequestID-BFR2-r17 Indicates the scheduling request configuration (SchedulingRequestConfig) that the UE shall use upon detecting a beam failure on the detection resources configured in schedulingRequestID-BFR2 of a serving cell while beam failure is not detected on resources configured in failureDetectionSet1 of the same serving cell.

schedulingRequestID-LBT-SCell Indicates the scheduling request configuration applicable for consistent uplink LBT recovery on SCell, as specified in TS 38.321 [3].

schedulingRequestID-PosMG-Request Indicates the scheduling request configuration applicable for Positioning Measurement Gap Activation/Deactivation Request, as specified in TS 38.321 [3].

skipUplinkTxDynamic, enhancedSkipUplinkTxDynamic, enhancedSkipUplinkTxConfigured If set to true, the UE skips UL transmissions as described in TS 38.321 [3]. If the UE is configured with enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured with value true, REPETITION_NUMBER (as specified in TS 38.321 [3], clause 5.4.2.1) of the corresponding PUSCH transmission of the uplink grant shall be equal to 1.

tag-Config The field is used to configure parameters for a time-alignment group. The field is not present if any DAPS bearer is configured.

usePreBSR If set to true, the MAC entity of the IAB-MT may use the Pre-emptive BSR, see TS 38.321 [3].

MBS-RNTI-SpecificConfig field descriptions

drx-ConfigPTM Used to configure DRX for PTM transmission as specified in TS 38.321 [3].

g-CS-RNTI Used to scramble the SPS group-common PDSCH and activation/deactivation of SPS group-common PDSCH for one or more MBS multicast services.

g-RNTI Used to scramble the scheduling and transmission of PTM for one or more MBS multicast services.

groupCommon-RNTI Used to configure g-RNTI or g-CS-RNTI.

harq-FeedbackEnablerMulticast Indicates whether the UE shall provide HARQ feedback for MBS multicast. Value dci-enabler means that whether the UE shall provide HARQ feedback for MBS multicast is indicated by DCI. Value enabled means the UE shall always provide HARQ feedback for MBS multicast. When the field is absent, the value "disabled" is used as defined in TS 38.213 [3].

harq-FeedbackOptionMulticast Indicates the feedback mode for MBS multicast dynamically scheduled PDSCH or SPS PDSCH.

mbs-RNTI-SpecificConfigId An identifier of the RNTI specific configuration for MBS multicast.

pdsch-AggregationFactor Number of repetitions for dynamically scheduled MBS multicast data (see TS 38.214 [19], clause 5.1.2.1). When the field is absent and groupCommon-RNTI is set to g-RNTI, the UE applies the value 1.

Conditional Presence	Explanation
G-RNTI	This field is optionally present, Need S, if groupCommon-RNTI is set to g-RNTI. The field is absent when groupCommon-RNTI is set to g-CS-RNTI.
HARQFeedback	The field is mandatory present when harq-FeedbackEnablerMulticast is present. It is absent otherwise.
MCG-Only	This field is optionally present, Need M, for the MAC-CellGroupConfig of the MCG. It is absent otherwise.
LCH-PrioWithReTxTimer	This field is optionally present, Need R, if lch-BasedPrioritization-r16 is configured in this MAC entity and cg-RetransmissionTimer-r16 is configured for any configured grant configuration associated with this MAC entity. It is absent otherwise, Need R.

– MeasConfig

The IE MeasConfig specifies measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps.

MeasConfig information element

— ASN1START

— TAG-MEASCONFIG-START

MeasConfig ::= SEQUENCE {

measObjectToRemoveList MeasObjectToRemoveList OPTIONAL, — Need N

measObjectToAddModList MeasObjectToAddModList OPTIONAL, — Need N

reportConfigToRemoveList ReportConfigToRemoveList OPTIONAL, — Need N

reportConfigToAddModList ReportConfigToAddModList OPTIONAL, — Need N

measIdToRemoveList MeasIdToRemoveList OPTIONAL, — Need N

measIdToAddModList MeasIdToAddModList OPTIONAL, — Need N

s-MeasureConfig CHOICE {

ssb-RSRP RSRP-Range,

csi-RSRP RSRP-Range

} OPTIONAL, — Need M

quantityConfig QuantityConfig OPTIONAL, — Need M

measGapConfig MeasGapConfig OPTIONAL, — Need M

measGapSharingConfig MeasGapSharingConfig OPTIONAL, — Need M

…,

[[

interFrequencyConfig-NoGap-r16 ENUMERATED {true} OPTIONAL — Need R

]]

}

MeasObjectToRemoveList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectId

MeasIdToRemoveList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId

ReportConfigToRemoveList ::= SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigId

— TAG-MEASCONFIG-STOP

— ASN1STOP

MeasConfig field descriptions
interFrequencyConfig-NoGap-r16 If the field is set to true, UE is configured to perform SSB based inter-frequency measurement without measurement gaps when the inter-frequency SSB is completely contained in the active DL BWP of the UE, as specified in TS 38.133 [14], clause 9.3. Otherwise, the SSB based inter-frequency measurement is performed within measurement gaps. In NR-DC, the field can only be configured in the measConfig associated with MCG, and when configured, it applies to all the inter-frequency measurements configured by MN and SN.
measGapConfig Used to setup and release measurement gaps in NR.
measIdToAddModList List of measurement identities to add and/or modify.
measIdToRemoveList List of measurement identities to remove.
measObjectToAddModList List of measurement objects to add and/or modify.
measObjectToRemoveList List of measurement objects to remove.
reportConfigToAddModList List of measurement reporting configurations to add and/or modify.
reportConfigToRemoveList List of measurement reporting configurations to remove.
s-MeasureConfig Threshold for NR SpCell RSRP measurement controlling when the UE is required to perform measurements on non-serving cells. Choice of ssb-RSRP corresponds to cell RSRP based on SS/PBCH block and choice of csi-RSRP corresponds to cell RSRP of CSI-RS.
measGapSharingConfig Specifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing.

– MeasGapConfig

The IE MeasGapConfig specifies the measurement gap configuration and controls setup/release of measurement gaps.

MeasGapConfig information element

— ASN1START

— TAG-MEASGAPCONFIG-START

MeasGapConfig ::= SEQUENCE {

gapFR2 SetupRelease { GapConfig } OPTIONAL, — Need M

…,

[[

gapFR1 SetupRelease { GapConfig } OPTIONAL, — Need M

gapUE SetupRelease { GapConfig } OPTIONAL — Need M

]],

[[

gapToAddModList-r17 SEQUENCE (SIZE (1..maxNrofGapId-r17)) OF GapConfig-r17 OPTIONAL, — Need N

gapToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofGapId-r17)) OF MeasGapId-r17 OPTIONAL, — Need N

posMeasGapPreConfigToAddModList-r17 PosMeasGapPreConfigToAddModList-r17 OPTIONAL, — Need N

posMeasGapPreConfigToReleaseList-r17 PosMeasGapPreConfigToReleaseList-r17 OPTIONAL — Need N

]]

}

GapConfig ::= SEQUENCE {

gapOffset INTEGER (0..159),

mgl ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6},

mgrp ENUMERATED {ms20, ms40, ms80, ms160},

mgta ENUMERATED {ms0, ms0dot25, ms0dot5},

…,

[[

refServCellIndicator ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL — Cond NEDCorNRDC

]],

[[

refFR2ServCellAsyncCA-r16 ServCellIndex OPTIONAL, — Cond AsyncCA

mgl-r16 ENUMERATED {ms10, ms20} OPTIONAL — Cond PRS

]]

}

GapConfig-r17 ::= SEQUENCE {

measGapId-r17 MeasGapId-r17,

gapType-r17 ENUMERATED {perUE, perFR1, perFR2},

gapOffset-r17 INTEGER (0..159),

mgl-r17 ENUMERATED {ms1, ms1dot5, ms2, ms3, ms3dot5, ms4, ms5, ms5dot5, ms6, ms10, ms20},

mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160},

mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot75},

refServCellIndicator-r17 ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL, — Cond NEDCorNRDC

refFR2-ServCellAsyncCA-r17 ServCellIndex OPTIONAL, — Cond AsyncCA

preConfigInd-r17 ENUMERATED {true} OPTIONAL, — Need R

ncsgInd-r17 ENUMERATED {true} OPTIONAL, — Need R

gapAssociationPRS-r17 ENUMERATED {true} OPTIONAL, — Need R

gapSharing-r17 MeasGapSharingScheme OPTIONAL, — Need R

gapPriority-r17 GapPriority-r17 OPTIONAL, — Need R

…

}

PosMeasGapPreConfigToAddModList-r17 ::= SEQUENCE (SIZE (1..maxNrofPreConfigPosGapId-r17)) OF PosGapConfig-r17

PosMeasGapPreConfigToReleaseList-r17 ::= SEQUENCE (SIZE (1..maxNrofPreConfigPosGapId-r17)) OF MeasPosPreConfigGapId-r17

PosGapConfig-r17 ::= SEQUENCE {

measPosPreConfigGapId-r17 MeasPosPreConfigGapId-r17,

gapOffset-r17 INTEGER (0..159),

mgl-r17 ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20},

mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160},

mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5},

gapType-r17 ENUMERATED {perUE, perFR1, perFR2},

…

}

MeasPosPreConfigGapId-r17 ::= INTEGER (1..maxNrofPreConfigPosGapId-r17)

— TAG-MEASGAPCONFIG-STOP

— ASN1STOP

MeasGapConfig field descriptions

gapAssociationPRS Indicates that PRS measurement is associated with this measurement gap. The network only includes this field for one per UE gap. If concurrent gap (i.e. one of the gap combination as defined in Table 9.1.8-1 in TS 38.133 [14]) is configured and no gap is configured with this field, the PRS measurement is associated with the gap configured via gapUE, if available.

gapFR1 Indicates measurement gap configuration that applies to FR1 only. In (NG)EN-DC, gapFR1 cannot be set up by NR RRC (i.e. only LTE RRC can configure FR1 measurement gap). In NE-DC, gapFR1 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR1 gap). In NR-DC, gapFR1 can only be set up in the measConfig associated with MCG. gapFR1 can not be configured together with gapUE. The applicability of the FR1 measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14].

gapFR2 Indicates measurement gap configuration applies to FR2 only. In (NG)EN-DC or NE-DC, gapFR2 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR2 gap). In NR-DC, gapFR2 can only be set up in the measConfig associated with MCG. gapFR2 cannot be configured together with gapUE. The applicability of the FR2 measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14].

gapOffset Value gapOffset is the gap offset of the gap pattern with MGRP indicated in the field mgrp. The value range is from 0 to mgrp-1. If ncsgInd-r17 is present, this offset value refers to the starting point of VIL1 (the visible interruption length before the ML).

gapPriority Indicates the priority of this measurement gap (see TS 38.133 [14], clause FFS). Value 1 indicates highest priority, value 2 indicates second level priority, and so on.

gapSharing Indicates the measurement gap sharing scheme that applies to this GapConfig. For applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on.

gapToAddModList A list of of measurement gap configuration to be added or modified. If more than one measurement gap is configured (i.e. concurrent measurement gap as specified in TS 38.133[14], clause 9.1.8), the maximum number of configured measurement gap is limited by the gap combinations defined in Table 9.1.8-1 in TS 38.133 [14]. The network configures at most one NCSG or pre-configured measurement gap for a given gap type. In this version of the specification, the network configures this field only in NR standalone. This field is used only for a UE that supports pre-configured measurement gap, concurrent measurement gap, or NCSG. In this version of the specification, the network does not configure concurrent measurement gap together with MUSIM gap or preconfigured measurement gap for positioning.

gapToReleaseList A list of measurement gap configuration to be released.

gapType Indicates the type of this measurement gap. Value perUE indicates that it is a per UE measurement gap, value perFR1 indicates that it is an FR1 measurement gap, and value perFR2 indicates that it is an FR2 measurement gap.

gapUE Indicates measurement gap configuration that applies to all frequencies (FR1 and FR2). In (NG)EN-DC, gapUE cannot be set up by NR RRC (i.e. only LTE RRC can configure per UE measurement gap). In NE-DC, gapUE can only be set up by NR RRC (i.e. LTE RRC cannot configure per UE gap). In NR-DC, gapUE can only be set up in the measConfig associated with MCG. If gapUE is configured, then neither gapFR1 nor gapFR2 can be configured. The applicability of the per UE measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14].

measGapId The ID of this measurement gap configuration.

mgl Value mgl is the measurement gap length in ms of the measurement gap. If ncsgInd-r17 is not present, the measurement gap length is according to in Table 9.1.2-1 in TS 38.133 [14]. If ncsgInd-r17 is present, this field indicates the measurement length (ML) in NCSG pattern and is configured according to Table 9.1.9.3-1 in TS 38.133 [14]. Value ms1dot5 corresponds to 1.5 ms, ms3 corresponds to 3 ms and so on. If mgl-r16 is present, UE shall ignore the mgl (without suffix). Value ms1, ms2, and ms5 can only be configured if ncsgInd is present.

mgrp Value mgrp is measurement gap repetition period in (ms) of the measurement gap. The measurement gap repetition period is according to Table 9.1.2-1 in TS 38.133 [14].

mgta Value mgta is the measurement gap timing advance in ms. The applicability of the measurement gap timing advance is according to clause 9.1.2 of TS 38.133 [14], or according to clause 9.1.9 of TS 38.133 [14] if ncsgInd is present. Value ms0 corresponds to 0 ms, ms0dot25 corresponds to 0.25 ms, ms0dot5 corresponds to 0.5 ms and ms0dot75 corresponds to 0.75 ms. For FR2, the network only configures 0 ms and 0.25 ms if ncsgInd is not present. If ncsgInd is present, the network only configures 0ms for per-UE NCSG and FR1 NCSG and only configures 0ms or 0.75ms for FR2 NCSG. Value ms0dot75 can only be configured if ncsgInd is present.

ncsgInd Indicates that the measurement gap is a NCSG as specified in 38.133 [14].

posMeasGapPreConfigToAddModList List of preconfigured measurement gap for positioning to add and/or modify. All the gaps configured are associated with the measurement of PRS for RSTD, UE-RxTx Time Difference, PRS-RSRP and PRS-RSRPP as defined in TS 38.215 [9]. In this version of the specification, the network does not configure preconfigured measurement gap for positioning together with concurrent measurement gap or MUSIM gap.

posMeasGapPreConfigToReleaseList List of preconfigured measurement gap for positioning to release.

preConfigInd Indicates whether the measurement gap is a pre-configured measurement gap.

refFR2ServCellAsyncCA Indicates the FR2 serving cell identifier whose SFN and subframe is used for FR2 gap calculation for this gap pattern with asynchronous CA involving FR2 carrier(s).

refServCellIndicator Indicates the serving cell whose SFN and subframe are used for gap calculation for this gap pattern. Value pCell corresponds to the PCell, pSCell corresponds to the PSCell, and mcg-FR2 corresponds to a serving cell on FR2 frequency in MCG.

Conditional Presence	Explanation
AsyncCA	This field is mandatory present when configuring FR2 gap pattern to UE in: – (NG)EN-DC or NR SA with asynchronous CA involving FR2 carrier(s); – NE-DC or NR-DC with asynchronous CA involving FR2 carrier(s), if the field refServCellIndicator is set to mcg-FR2. In case the gap pattern to UE in NE-DC and NR-DC is already configured and the serving cell used for the gap calculation corresponds to a serving cell on FR2 frequency in MCG, then the field is optionally present, need M. Otherwise, it is absent, Need R.
NEDCorNRDC	This field is mandatory present when configuring gap pattern to UE in NE-DC or NR-DC. In case the gap pattern to UE in NE-DC and NR-DC is already configured, then the field is absent, need M. Otherwise, it is absent.
PRS	This field is optionally present, Need R, when configuring gap pattern to UE for measurements of DL-PRS configured via LPP (TS 37.355 [49]). Otherwise, it is absent.

– MeasGapId

The IE MeasGapId used to identify a per UE or per FR measurement gap configuration.

MeasGapId information element

— ASN1START

— TAG-MEASGAPID-START

MeasGapId-r17 ::= INTEGER (1..maxNrofGapId-r17)

— TAG-MEASGAPID-STOP

— ASN1STOP

– MeasGapSharingConfig

The IE MeasGapSharingConfig specifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing.

MeasGapSharingConfig information element

— ASN1START

— TAG-MEASGAPSHARINGCONFIG-START

MeasGapSharingConfig ::= SEQUENCE {

gapSharingFR2 SetupRelease { MeasGapSharingScheme } OPTIONAL, — Need M

…,

[[

gapSharingFR1 SetupRelease { MeasGapSharingScheme } OPTIONAL, –Need M

gapSharingUE SetupRelease { MeasGapSharingScheme } OPTIONAL –Need M

]]

}

MeasGapSharingScheme::= ENUMERATED {scheme00, scheme01, scheme10, scheme11}

— TAG-MEASGAPSHARINGCONFIG-STOP

— ASN1STOP

MeasGapSharingConfig field descriptions

gapSharingFR1 Indicates the measurement gap sharing scheme that applies to the gap set via gapFR1. In (NG)EN-DC, gapSharingFR1 cannot be set up by NR RRC (i.e. only LTE RRC can configure FR1 gap sharing). In NE-DC, gapSharingFR1 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR1 gap sharing). In NR-DC, gapSharingFR1 can only be set up in the measConfig associated with MCG. gapSharingFR1 can not be configured together with gapSharingUE. For the applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on.

gapSharingFR2 Indicates the measurement gap sharing scheme that applies to the gap set via gapFR2. In (NG)EN-DC or NE-DC, gapSharingFR2 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR2 gap sharing). In NR-DC, gapSharingFR2 can only be set up by MCG in the measConfig associated with MCG. gapSharingFR2 cannot be configured together with gapSharingUE. For applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on.

gapSharingUE Indicates the measurement gap sharing scheme that applies to the gap set via gapUE. In (NG)EN-DC, gapSharingUE cannot be set up by NR RRC (i.e. only LTE RRC can configure per UE gap sharing). In NE-DC, gapSharingUE can only be set up by NR RRC (i.e. LTE RRC cannot configure per UE gap sharing). In NR-DC, gapSharingUE can only be set up in the measConfig associated with MCG. If gapSharingUE is configured, then neither gapSharingFR1 nor gapSharingFR2 can be configured. For the applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on.

– MeasId

The IE MeasId is used to identify a measurement configuration, i.e., linking of a measurement object and a reporting configuration.

MeasId information element

— ASN1START

— TAG-MEASID-START

MeasId ::= INTEGER (1..maxNrofMeasId)

— TAG-MEASID-STOP

— ASN1STOP

– MeasIdleConfig

The IE MeasIdleConfig is used to convey information to UE about measurements requested to be done while in RRC_IDLE or RRC_INACTIVE.

MeasIdleConfig information element

— ASN1START

— TAG-MEASIDLECONFIG-START

MeasIdleConfigSIB-r16 ::= SEQUENCE {

measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, — Need S

measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, — Need S

…

}

MeasIdleConfigDedicated-r16 ::= SEQUENCE {

measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, — Need N

measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, — Need N

measIdleDuration-r16 ENUMERATED{sec10, sec30, sec60, sec120, sec180, sec240, sec300, spare},

validityAreaList-r16 ValidityAreaList-r16 OPTIONAL, — Need N

…

}

ValidityAreaList-r16 ::= SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF ValidityArea-r16

ValidityArea-r16 ::= SEQUENCE {

carrierFreq-r16 ARFCN-ValueNR,

validityCellList-r16 ValidityCellList OPTIONAL — Need N

}

ValidityCellList ::= SEQUENCE (SIZE (1.. maxCellMeasIdle-r16)) OF PCI-Range

MeasIdleCarrierNR-r16 ::= SEQUENCE {

carrierFreq-r16 ARFCN-ValueNR,

ssbSubcarrierSpacing-r16 SubcarrierSpacing,

frequencyBandList MultiFrequencyBandListNR OPTIONAL, — Need R

measCellListNR-r16 CellListNR-r16 OPTIONAL, — Need R

reportQuantities-r16 ENUMERATED {rsrp, rsrq, both},

qualityThreshold-r16 SEQUENCE {

idleRSRP-Threshold-NR-r16 RSRP-Range OPTIONAL, — Need R

idleRSRQ-Threshold-NR-r16 RSRQ-Range OPTIONAL — Need R

} OPTIONAL, — Need R

ssb-MeasConfig-r16 SEQUENCE {

nrofSS-BlocksToAverage-r16 INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, — Need S

absThreshSS-BlocksConsolidation-r16 ThresholdNR OPTIONAL, — Need S

smtc-r16 SSB-MTC OPTIONAL, — Need S

ssb-ToMeasure-r16 SSB-ToMeasure OPTIONAL, — Need S

deriveSSB-IndexFromCell-r16 BOOLEAN,

ss-RSSI-Measurement-r16 SS-RSSI-Measurement OPTIONAL — Need S

} OPTIONAL, — Need S

beamMeasConfigIdle-r16 BeamMeasConfigIdle-NR-r16 OPTIONAL, — Need R

…

}

MeasIdleCarrierEUTRA-r16 ::= SEQUENCE {

carrierFreqEUTRA-r16 ARFCN-ValueEUTRA,

allowedMeasBandwidth-r16 EUTRA-AllowedMeasBandwidth,

measCellListEUTRA-r16 CellListEUTRA-r16 OPTIONAL, — Need R

reportQuantitiesEUTRA-r16 ENUMERATED {rsrp, rsrq, both},

qualityThresholdEUTRA-r16 SEQUENCE {

idleRSRP-Threshold-EUTRA-r16 RSRP-RangeEUTRA OPTIONAL, — Need R

idleRSRQ-Threshold-EUTRA-r16 RSRQ-RangeEUTRA-r16 OPTIONAL — Need R

} OPTIONAL, — Need S

…

}

CellListNR-r16 ::= SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF PCI-Range

CellListEUTRA-r16 ::= SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF EUTRA-PhysCellIdRange

BeamMeasConfigIdle-NR-r16 ::= SEQUENCE {

reportQuantityRS-Indexes-r16 ENUMERATED {rsrp, rsrq, both},

maxNrofRS-IndexesToReport-r16 INTEGER (1.. maxNrofIndexesToReport),

includeBeamMeasurements-r16 BOOLEAN

}

RSRQ-RangeEUTRA-r16 ::= INTEGER (-30..46)

— TAG-MEASIDLECONFIG-STOP

— ASN1STOP

MeasIdleConfig field descriptions

absThreshSS-BlocksConsolidation Threshold for consolidation of L1 measurements per RS index.

beamMeasConfigIdle Indicates the beam level measurement configuration.

carrierFreq Indicates the NR carrier frequency to be used for measurements during RRC_IDLE or RRC_INACTIVE.

carrierFreqEUTRA Indicates the E-UTRA carrier frequency to be used for measurements during RRC_IDLE or RRC_INACTIVE.

deriveSSB-IndexFromCell This field indicates whether the UE may use the timing of any detected cell on that frequency to derive the SSB index of all neighbour cells on that frequency. If this field is set to true, the UE assumes SFN and frame boundary alignment across cells on the neighbor frequency as specified in TS 38.133 [14].

frequencyBandList Indicates the list of frequency bands for which the NR idle/inactive measurement parameters apply. The UE shall select the first listed band which it supports in the frequencyBandList field to represent the NR neighbour carrier frequency.

includeBeamMeasurements Indicates whether or not the UE shall include beam measurements in the NR idle/inactive measurement results.

maxNrofRS-IndexesToReport Max number of beam indices to include in the idle/inactive measurement result.

measCellListEUTRA Indicates the list of E-UTRA cells which the UE is requested to measure and report for idle/inactive measurements.

measCellListNR Indicates the list of NR cells which the UE is requested to measure and report for idle/inactive measurements.

measIdleCarrierListEUTRA Indicates the E-UTRA carriers to be measured during RRC_IDLE or RRC_INACTIVE.

measIdleCarrierListNR Indicates the NR carriers to be measured during RRC_IDLE or RRC_INACTIVE.

measIdleDuration Indicates the duration for performing idle/inactive measurements while in RRC_IDLE or RRC_INACTIVE. Value sec10 correspond to 10 seconds, value sec30 to 30 seconds and so on.

nrofSS-BlocksToAverage Number of SS blocks to average for cell measurement derivation.

qualityThreshold Indicates the quality thresholds for reporting the measured cells for idle/inactive NR measurements.

qualityThresholdEUTRA Indicates the quality thresholds for reporting the measured cells for idle/inactive E-UTRA measurements.

reportQuantities Indicates which measurement quantities UE is requested to report in the idle/inactive measurement report.

reportQuantitiesEUTRA Indicates which E-UTRA measurement quantities the UE is requested to report in the idle/inactive measurement report.

reportQuantityRS-Indexes Indicates which measurement information per beam index the UE shall include in the NR idle/inactive measurement results.

smtc Indicates the measurement timing configuration for inter-frequency measurement. If this field is absent in VarMeasIdleConfig, the UE assumes that SSB periodicity is 5 ms in this frequency.

ssbSubcarrierSpacing Indicates subcarrier spacing of SSB. Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 120 or 240 kHz FR2-2: 120, 480, or 960 kHz

ssb-ToMeasure The set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). When the field is absent in VarMeasIdleConfig, the UE measures on all SS-blocks.

ss-RSSI-Measurement Indicates the SSB-based RSSI measurement configuration. If the field is absent in VarMeasIdleConfig, the UE behaviour is defined in TS 38.215 [89], clause 5.1.3.

validityAreaList Indicates the list of frequencies and optionally, for each frequency, a list of cells within which the UE is required to perform measurements while in RRC_IDLE and RRC_INACTIVE.

– MeasIdToAddModList

The IE MeasIdToAddModList concerns a list of measurement identities to add or modify, with for each entry the measId, the associated measObjectId and the associated reportConfigId.

MeasIdToAddModList information element

— ASN1START

— TAG-MEASIDTOADDMODLIST-START

MeasIdToAddModList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod

MeasIdToAddMod ::= SEQUENCE {

measId MeasId,

measObjectId MeasObjectId,

reportConfigId ReportConfigId

}

— TAG-MEASIDTOADDMODLIST-STOP

— ASN1STOP

– MeasObjectCLI

The IE MeasObjectCLI specifies information applicable for SRS-RSRP measurements and/or CLI-RSSI measurements.

MeasObjectCLI information element

— ASN1START

— TAG-MEASOBJECTCLI-START

MeasObjectCLI-r16 ::= SEQUENCE {

cli-ResourceConfig-r16 CLI-ResourceConfig-r16,

…

}

CLI-ResourceConfig-r16 ::= SEQUENCE {

srs-ResourceConfig-r16 SetupRelease { SRS-ResourceListConfigCLI-r16 } OPTIONAL, — Need M

rssi-ResourceConfig-r16 SetupRelease { RSSI-ResourceListConfigCLI-r16 } OPTIONAL — Need M

}

SRS-ResourceListConfigCLI-r16 ::= SEQUENCE (SIZE (1.. maxNrofCLI-SRS-Resources-r16)) OF SRS-ResourceConfigCLI-r16

RSSI-ResourceListConfigCLI-r16 ::= SEQUENCE (SIZE (1.. maxNrofCLI-RSSI-Resources-r16)) OF RSSI-ResourceConfigCLI-r16

SRS-ResourceConfigCLI-r16 ::= SEQUENCE {

srs-Resource-r16 SRS-Resource,

srs-SCS-r16 SubcarrierSpacing,

refServCellIndex-r16 ServCellIndex OPTIONAL, — Need S

refBWP-r16 BWP-Id,

…

}

RSSI-ResourceConfigCLI-r16 ::= SEQUENCE {

rssi-ResourceId-r16 RSSI-ResourceId-r16,

rssi-SCS-r16 SubcarrierSpacing,

startPRB-r16 INTEGER (0..2169),

nrofPRBs-r16 INTEGER (4..maxNrofPhysicalResourceBlocksPlus1),

startPosition-r16 INTEGER (0..13),

nrofSymbols-r16 INTEGER (1..14),

rssi-PeriodicityAndOffset-r16 RSSI-PeriodicityAndOffset-r16,

refServCellIndex-r16 ServCellIndex OPTIONAL, — Need S

…

}

RSSI-ResourceId-r16 ::= INTEGER (0.. maxNrofCLI-RSSI-Resources-1-r16)

RSSI-PeriodicityAndOffset-r16 ::= CHOICE {

sl10 INTEGER(0..9),

sl20 INTEGER(0..19),

sl40 INTEGER(0..39),

sl80 INTEGER(0..79),

sl160 INTEGER(0..159),

sl320 INTEGER(0..319),

s1640 INTEGER(0..639),

…

}

— TAG-MEASOBJECTCLI-STOP

— ASN1STOP

CLI-ResourceConfig field descriptions

srs-ResourceConfig SRS resources to be used for CLI measurements.

rssi-ResourceConfig CLI-RSSI resources to be used for CLI measurements.

MeasObjectCLI field descriptions

cli-ResourceConfig SRS and/or CLI-RSSI resource configuration for CLI measurement.

SRS-ResourceConfigCLI field descriptions

refBWP DL BWP id that is used to derive the reference point of the SRS resource (see TS 38.211[16], clause 6.4.1.4.3)

refServCellIndex The index of the reference serving cell that the refBWP belongs to. If this field is absent, the reference serving cell is PCell.

srs-SCS Subcarrier spacing for SRS. Only the following values are applicable depending on the used frequency: FR1: 15, 30, or 60 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz

RSSI-ResourceConfigCLI field descriptions

nrofPRBs Allowed size of the measurement BW. Only multiples of 4 are allowed. The smallest configurable number is the minimum of 4 and the width of the active DL BWP. If the configured value is larger than the width of the active DL BWP, the UE shall assume that the actual CLI-RSSI resource bandwidth is within the active DL BWP.

nrofSymbols Within a slot that is configured for CLI-RSSI measurement (see slotConfiguration), the UE measures the RSSI from startPosition to startPosition + nrofSymbols – 1. The configured CLI-RSSI resource does not exceed the slot boundary of the reference SCS. If the SCS of configured DL BWP(s) is larger than the reference SCS, network configures startPosition and nrofSymbols such that the configured CLI-RSSI resource not to exceed the slot boundary corresponding to the configured BWP SCS. If the reference SCS is larger than SCS of configured DL BWP(s), network ensures startPosition and nrofSymbols are integer multiple of reference SCS divided by configured BWP SCS.

refServCellIndex The index of the reference serving cell. Frequency reference point of the RSSI resource is subcarrier 0 of CRB0 of the reference serving cell. If this field is absent, the reference serving cell is PCell.

rssi-PeriodicityAndOffset Periodicity and slot offset for this CLI-RSSI resource. All values are in "number of slots". Value sl1 corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots.

rssi-SCS Reference subcarrier spacing for CLI-RSSI measurement. Only the following values are applicable depending on the used frequency: FR1: 15, 30, or 60 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz UE performs CLI-RSSI measurement with the SCS of the active bandwidth part within the configured CLI-RSSI resource in the active BWP regardless of the reference SCS of the measurement resource.

startPosition OFDM symbol location of the CLI-RSSI resource within a slot.

startPRB Starting PRB index of the measurement bandwidth. For the case where the reference subcarrier spacing is smaller than subcarrier spacing of active DL BWP(s), network configures startPRB and nrofPRBs are as a multiple of active BW SCS divided by reference SCS.

– MeasObjectEUTRA

The IE MeasObjectEUTRA specifies information applicable for E‑UTRA cells.

MeasObjectEUTRA information element

— ASN1START

— TAG-MEASOBJECTEUTRA-START

MeasObjectEUTRA::= SEQUENCE {

carrierFreq ARFCN-ValueEUTRA,

allowedMeasBandwidth EUTRA-AllowedMeasBandwidth,

cellsToRemoveListEUTRAN EUTRA-CellIndexList OPTIONAL, — Need N

cellsToAddModListEUTRAN SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-Cell OPTIONAL, — Need N

excludedCellsToRemoveListEUTRAN EUTRA-CellIndexList OPTIONAL, — Need N

excludedCellsToAddModListEUTRAN SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-ExcludedCell OPTIONAL, — Need N

eutra-PresenceAntennaPort1 EUTRA-PresenceAntennaPort1,

eutra-Q-OffsetRange EUTRA-Q-OffsetRange OPTIONAL, — Need R

widebandRSRQ-Meas BOOLEAN,

…,

[[

associatedMeasGap-r17 MeasGapId-r17 OPTIONAL — Need R

]]

}

EUTRA-CellIndexList ::= SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-CellIndex

EUTRA-CellIndex ::= INTEGER (1..maxCellMeasEUTRA)

EUTRA-Cell ::= SEQUENCE {

cellIndexEUTRA EUTRA-CellIndex,

physCellId EUTRA-PhysCellId,

cellIndividualOffset EUTRA-Q-OffsetRange

}

EUTRA-ExcludedCell ::= SEQUENCE {

cellIndexEUTRA EUTRA-CellIndex,

physCellIdRange EUTRA-PhysCellIdRange

}

— TAG-MEASOBJECTEUTRA-STOP

— ASN1STOP

EUTRAN-ExcludedCell field descriptions

cellIndexEUTRA Entry index in the cell list.

physicalCellIdRange Physical cell identity or a range of physical cell identities.

EUTRAN-Cell field descriptions

physicalCellId Physical cell identity of a cell in the cell list.

cellIndividualOffset Cell individual offset applicable to a specific cell. Value dB-24 corresponds to -24 dB, dB-22 corresponds to -22 dB and so on.

MeasObjectEUTRA field descriptions

allowedMeasBandwidth The maximum allowed measurement bandwidth on a carrier frequency as defined by the parameter Transmission Bandwidth Configuration "NRB" TS 36.104 [33].

associatedMeasGap Indicates the associated measurement gap for measuring this EUTRA frequency. If this field is absent, the associated meaurment gap is the gap configured via gapFR1 or gapUE.

carrierFreq Identifies E‑UTRA carrier frequency for which this configuration is valid. Network does not configure more than one MeasObjectEUTRA for the same physical frequency, regardless of the E-ARFCN used to indicate this.

cellsToAddModListEUTRAN List of cells to add/ modify in the cell list.

cellsToRemoveListEUTRAN List of cells to remove from the cell list.

eutra-PresenceAntennaPort1 When set to true, the UE may assume that at least two cell-specific antenna ports are used in all neighbouring cells.

eutra-Q-OffsetRange Used to indicate a cell, or frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, value dB-22 corresponds to -22 dB and so on.

excludedCellsToAddModListEUTRAN List of cells to add/ modify in the exclude-list of cells.

excludedCellsToRemoveListEUTRAN List of cells to remove from the exclude-list of cells.

widebandRSRQ-Meas If set to true, the UE shall, when performing RSRQ measurements, use a wider bandwidth in accordance with TS 36.133 [40]. The network may set the field to true if the measurement bandwidth indicated by allowedMeasBandwidth is 50 resource blocks or larger; otherwise the network sets this field to false.

– MeasObjectId

The IE MeasObjectId used to identify a measurement object configuration.

MeasObjectId information element

— ASN1START

— TAG-MEASOBJECTID-START

MeasObjectId ::= INTEGER (1..maxNrofObjectId)

— TAG-MEASOBJECTID-STOP

— ASN1STOP

– MeasObjectNR

The IE MeasObjectNR specifies information applicable for SS/PBCH block(s) intra/inter-frequency measurements and/or CSI-RS intra/inter-frequency measurements.

MeasObjectNR information element

— ASN1START

— TAG-MEASOBJECTNR-START

MeasObjectNR ::= SEQUENCE {

ssbFrequency ARFCN-ValueNR OPTIONAL, — Cond SSBorAssociatedSSB

ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, — Cond SSBorAssociatedSSB

smtc1 SSB-MTC OPTIONAL, — Cond SSBorAssociatedSSB

smtc2 SSB-MTC2 OPTIONAL, — Cond IntraFreqConnected

refFreqCSI-RS ARFCN-ValueNR OPTIONAL, — Cond CSI-RS

referenceSignalConfig ReferenceSignalConfig,

absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, — Need R

absThreshCSI-RS-Consolidation ThresholdNR OPTIONAL, — Need R

nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, — Need R

nrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS-ResourcesToAverage) OPTIONAL, — Need R

quantityConfigIndex INTEGER (1..maxNrofQuantityConfig),

offsetMO Q-OffsetRangeList,

cellsToRemoveList PCI-List OPTIONAL, — Need N

cellsToAddModList CellsToAddModList OPTIONAL, — Need N

excludedCellsToRemoveList PCI-RangeIndexList OPTIONAL, — Need N

excludedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, — Need N

allowedCellsToRemoveList PCI-RangeIndexList OPTIONAL, — Need N

allowedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, — Need N

…,

[[

freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, — Need R

measCycleSCell ENUMERATED {sf160, sf256, sf320, sf512, sf640, sf1024, sf1280} OPTIONAL — Need R

]],

[[

smtc3list-r16 SSB-MTC3List-r16 OPTIONAL, — Need R

rmtc-Config-r16 SetupRelease {RMTC-Config-r16} OPTIONAL, — Need M

t312-r16 SetupRelease { T312-r16 } OPTIONAL — Need M

]],

[[

associatedMeasGapSSB-r17 MeasGapId-r17 OPTIONAL, — Need R

associatedMeasGapCSIRS-r17 MeasGapId-r17 OPTIONAL, — Need R

smtc4list-r17 SSB-MTC4List-r17 OPTIONAL, — Need R

measCyclePSCell-r17 ENUMERATED {ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, spare1}

OPTIONAL, — Cond SCG

cellsToAddModListExt-v1710 CellsToAddModListExt-v1710 OPTIONAL — Need N

]],

[[

associatedMeasGapSSB2-v1720 MeasGapId-r17 OPTIONAL, — Cond AssociatedGapSSB

associatedMeasGapCSIRS2-v1720 MeasGapId-r17 OPTIONAL — Cond AssociatedGapCSIRS

]]

}

SSB-MTC3List-r16::= SEQUENCE (SIZE(1..4)) OF SSB-MTC3-r16

SSB-MTC4List-r17::= SEQUENCE (SIZE(1..3)) OF SSB-MTC4-r17

T312-r16 ::= ENUMERATED { ms0, ms50, ms100, ms200, ms300, ms400, ms500, ms1000}

ReferenceSignalConfig::= SEQUENCE {

ssb-ConfigMobility SSB-ConfigMobility OPTIONAL, — Need M

csi-rs-ResourceConfigMobility SetupRelease { CSI-RS-ResourceConfigMobility } OPTIONAL — Need M

}

SSB-ConfigMobility::= SEQUENCE {

ssb-ToMeasure SetupRelease { SSB-ToMeasure } OPTIONAL, — Need M

deriveSSB-IndexFromCell BOOLEAN,

ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, — Need M

…,

[[

ssb-PositionQCL-Common-r16 SSB-PositionQCL-Relation-r16 OPTIONAL, — Cond SharedSpectrum

ssb-PositionQCL-CellsToAddModList-r16 SSB-PositionQCL-CellsToAddModList-r16 OPTIONAL, — Need N

ssb-PositionQCL-CellsToRemoveList-r16 PCI-List OPTIONAL — Need N

]],

[[

deriveSSB-IndexFromCellInter-r17 ServCellIndex OPTIONAL, — Need R

ssb-PositionQCL-Common-r17 SSB-PositionQCL-Relation-r17 OPTIONAL, — Cond SharedSpectrum2

ssb-PositionQCL-Cells-r17 SetupRelease {SSB-PositionQCL-CellList-r17} OPTIONAL — Need M

]]

}

Q-OffsetRangeList ::= SEQUENCE {

rsrpOffsetSSB Q-OffsetRange DEFAULT dB0,

rsrqOffsetSSB Q-OffsetRange DEFAULT dB0,

sinrOffsetSSB Q-OffsetRange DEFAULT dB0,

rsrpOffsetCSI-RS Q-OffsetRange DEFAULT dB0,

rsrqOffsetCSI-RS Q-OffsetRange DEFAULT dB0,

sinrOffsetCSI-RS Q-OffsetRange DEFAULT dB0

}

ThresholdNR ::= SEQUENCE{

thresholdRSRP RSRP-Range OPTIONAL, — Need R

thresholdRSRQ RSRQ-Range OPTIONAL, — Need R

thresholdSINR SINR-Range OPTIONAL — Need R

}

CellsToAddModList ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddMod

CellsToAddModListExt-v1710 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddModExt-v1710

CellsToAddMod ::= SEQUENCE {

physCellId PhysCellId,

cellIndividualOffset Q-OffsetRangeList

}

CellsToAddModExt-v1710 ::= SEQUENCE {

ntn-PolarizationDL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL, — Need R

ntn-PolarizationUL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL — Need R

}

RMTC-Config-r16 ::= SEQUENCE {

rmtc-Periodicity-r16 ENUMERATED {ms40, ms80, ms160, ms320, ms640},

rmtc-SubframeOffset-r16 INTEGER(0..639) OPTIONAL, — Need M

measDurationSymbols-r16 ENUMERATED {sym1, sym14or12, sym28or24, sym42or36, sym70or60},

rmtc-Frequency-r16 ARFCN-ValueNR,

ref-SCS-CP-r16 ENUMERATED {kHz15, kHz30, kHz60-NCP, kHz60-ECP},

…,

[[

rmtc-Bandwidth-r17 ENUMERATED {mhz100, mhz400, mhz800, mhz1600, mhz2000} OPTIONAL, — Need R

measDurationSymbols-v1700 ENUMERATED {sym140, sym560, sym1120} OPTIONAL, — Need R

ref-SCS-CP-v1700 ENUMERATED {kHz120, kHz480, kHz960} OPTIONAL, — Need R

tci-StateInfo-r17 SEQUENCE {

tci-StateId-r17 TCI-StateId,

ref-ServCellId-r17 ServCellIndex OPTIONAL — Need R

} OPTIONAL — Need R

]],

[[

ref-BWPId-r17 BWP-Id OPTIONAL — Need R

]]

}

SSB-PositionQCL-CellsToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF SSB-PositionQCL-CellsToAddMod-r16

SSB-PositionQCL-CellsToAddMod-r16 ::= SEQUENCE {

physCellId-r16 PhysCellId,

ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16

}

SSB-PositionQCL-CellList-r17 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF SSB-PositionQCL-Cell-r17

SSB-PositionQCL-Cell-r17 ::= SEQUENCE {

physCellId-r17 PhysCellId,

ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17

}

— TAG-MEASOBJECTNR-STOP

— ASN1STOP

CellsToAddMod field descriptions

cellIndividualOffset Cell individual offsets applicable to a specific cell.

physCellId Physical cell identity of a cell in the cell list.

MeasObjectNR field descriptions

absThreshCSI-RS-Consolidation Absolute threshold for the consolidation of measurement results per CSI-RS resource(s) from L1 filter(s). The field is used for the derivation of cell measurement results as described in 5.5.3.3 and the reporting of beam measurement information per CSI-RS resource as described in 5.5.5.2.

absThreshSS-BlocksConsolidation Absolute threshold for the consolidation of measurement results per SS/PBCH block(s) from L1 filter(s). The field is used for the derivation of cell measurement results as described in 5.5.3.3 and the reporting of beam measurement information per SS/PBCH block index as described in 5.5.5.2.

allowedCellsToAddModList List of cells to add/modify in the allow-list of cells. It applies only to SSB resources.

allowedCellsToRemoveList List of cells to remove from the allow-list of cells.

associatedMeasGapSSB Indicates the associated measurement gap for SSB measuring identified by ssb-ConfigMobility in this measurement object. When multiple MeasObjectNR with the same SSB frequency are configured, the network configures the same measurement gap ID in this field for each MeasObjectNR. If this field is absent, the associated measurement gap is the gap configured via gapFR1, gapFR2, or gapUE.

associatedMeasGapSSB2 Indicates the associated additional measurement gap for SSB measuring identified by ssb-ConfigMobility in this measurement object for NTN deployments. When multiple MeasObjectNR with the same SSB frequency are configured, the network configures the same measurement gap ID in this field for each MeasObjectNR. If this field is absent, the associated measurement gap is the gap indicated by associatedMeasGapSSB.

associatedMeasGapCSIRS Indicates the associated measurement gap for CSI-RS measuring identified by csi-rs-ResourceConfigMobility in this measurement object. If this field is absent, the associated measurement gap is the gap configured via gapFR1, gapFR2, or gapUE.

associatedMeasGapCSIRS2 Indicates the associated additional measurement gap for CSI-RS measuring identified by csi-rs-ResourceConfigMobility in this measurement object for NTN deployments. If this field is absent, the associated measurement gap is the gap indicated by associatedMeasGapCSIRS.

cellsToAddModList List of cells to add/modify in the cell list.

cellsToRemoveList List of cells to remove from the cell list.

excludedCellsToAddModList List of cells to add/modify in the exclude-list of cells. It applies only to SSB resources.

excludedCellsToRemoveList List of cells to remove from the exclude-list of cells.

freqBandIndicatorNR The frequency band in which the SSB and/or CSI-RS indicated in this MeasObjectNR are located and according to which the UE shall perform the RRM measurements. This field is always provided when the network configures measurements with this MeasObjectNR.

measCyclePSCell The parameter is used only when the PSCell is configured on the frequency indicated by the measObjectNR and the SCG is deactivated, see TS 38.133 [14]. The field may also be configured when the PSCell is not configured on that frequency. Value ms160 corresponds to 160 ms, value ms256 corresponds to 256 ms and so on.

measCycleSCell The parameter is used only when an SCell is configured on the frequency indicated by the measObjectNR and is in deactivated state, see TS 38.133 [14]. gNB configures the parameter whenever an SCell is configured on the frequency indicated by the measObjectNR, but the field may also be signalled when an SCell is not configured. Value sf160 corresponds to 160 sub-frames, value sf256 corresponds to 256 sub-frames and so on.

nrofCSInrofCSI-RS-ResourcesToAverage Indicates the maximum number of measurement results per beam based on CSI-RS resources to be averaged. The same value applies for each detected cell associated with this MeasObjectNR.

nrofSS-BlocksToAverage Indicates the maximum number of measurement results per beam based on SS/PBCH blocks to be averaged. The same value applies for each detected cell associated with this MeasObject.

ntn-PolarizationDL If present, this parameter indicates polarization information for downlink transmission on service link: including Right hand, Left hand circular polarizations (RHCP, LHCP) and Linear polarization.

ntn-PolarizationUL If present, this parameter indicates polarization information for uplink transmission on service link. If not present and ntn-PolarizationDL is present, UE assumes the same polarization for UL and DL.

offsetMO Offset values applicable to all measured cells with reference signal(s) indicated in this MeasObjectNR.

quantityConfigIndex Indicates the n-th element of quantityConfigNR-List provided in MeasConfig.

referenceSignalConfig RS configuration for SS/PBCH block and CSI-RS.

refFreqCSI-RS Point A which is used for mapping of CSI-RS to physical resources according to TS 38.211 [16] clause 7.4.1.5.3.

smtc1 Primary measurement timing configuration. (see clause 5.5.2.10).

smtc2 Secondary measurement timing configuration for SS corresponding to this MeasObjectNR with PCI listed in pci-List. For these SS, the periodicity is indicated by periodicity in smtc2 and the timing offset is equal to the offset indicated in periodicityAndOffset modulo periodicity. periodicity in smtc2 can only be set to a value strictly shorter than the periodicity indicated by periodicityAndOffset in smtc1 (e.g. if periodicityAndOffset indicates sf10, periodicity can only be set of sf5, if periodicityAndOffset indicates sf5, smtc2 cannot be configured).

smtc3list Measurement timing configuration list for SS corresponding to IAB-MT. This is used for the IAB-node’s discovery of other IAB-nodes and the IAB-Donor-DUs.

smtc4list Measurement timing configuration list for NTN deployments, see clause 5.5.2.10.

ssbFrequency Indicates the frequency of the SS associated to this MeasObjectNR. For operation with shared spectrum channel access, this field is a k*30 kHz shift from the sync raster where k = 0,1,2, and so on if the reportType within the corresponding ReportConfigNR is set to reportCGI (see TS 38.211 [16], clause 7.4.3.1). Frequencies are considered to be on the sync raster if they are also identifiable with a GSCN value (see TS 38.101-1 [15]).

ssb-PositionQCL-Common Indicates the QCL relationship between SS/PBCH blocks for all measured cells as specified in TS 38.213 [13], clause 4.1.

ssbSubcarrierSpacing Subcarrier spacing of SSB. Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 120 or 240 kHz FR2-2: 120, 480, or 960 kHz

t312 The value of timer T312. Value ms0 represents 0 ms, ms50 represents 50 ms and so on.

ReferenceSignalConfig field descriptions

csi-rs-ResourceConfigMobility CSI-RS resources to be used for CSI-RS based RRM measurements.

ssb-ConfigMobility SSB configuration for mobility (nominal SSBs, timing configuration).

RMTC-Config field descriptions

measDurationSymbols Number of consecutive symbols for which the Physical Layer reports samples of RSSI (see TS 38.215 [9], clause 5.1.21). Value sym1 corresponds to one symbol, sym14or12 corresponds to 14 symbols of the reference numerology for NCP and 12 symbols for ECP, and so on. If measDurationSymbols-v1700 is signalled, the UE ignores measDurationSymbols-r16.

ref-BWPId Indicates the reference BWP for the TCI state indicated in tci-StateInfo. Network includes this field if tci-StateInfo is present.

ref-SCS-CP Indicates a reference subcarrier spacing and cyclic prefix to be used for RSSI measurements (see TS 38.215 [9]). Value kHz15 corresponds to 15kHz, kHz30 corresponds to 30 kHz, value kHz60-NCP corresponds to 60 kHz using normal cyclic prefix (NCP), and kHz60-ECP corresponds to 60 kHz using extended cyclic prefix (ECP). If ref-SCS-CP-v1700 is signalled, the UE ignores ref-SCS-CP-r16.

ref-ServCellId Indicates the reference serving cell index for the TCI state. Network includes this field if tci-StateInfo is present.

rmtc-Bandwidth Indicates the bandwidth for the RSSI measurement (see TS 38. 215 [9], clause 5.1.21).

rmtc-Frequency Indicates the center frequency of the measured bandwidth for a frequency which operates with shared spectrum channel access (see TS 38. 215 [9], clause 5.1.21).

rmtc-Periodicity Indicates the RSSI measurement timing configuration (RMTC) periodicity (see TS 38.215 [9], clause 5.1.21).

rmtc-SubframeOffset Indicates the RSSI measurement timing configuration (RMTC) subframe offset for this frequency (see TS 38.215 [9], clause 5.1.21). For inter-frequency measurements, this field is optional present and if it is not configured, the UE chooses a random value as rmtc-SubframeOffset for measDurationSymbols which shall be selected to be between 0 and the configured rmtc-Periodicity with equal probability.

tci-StateId Indicates the TCI state to be used for RSSI measurements. This field is only applicable for shared spectrum channel access in FR2-2.

SSB-ConfigMobility field descriptions

deriveSSB-IndexFromCell If this field is set to true, UE assumes SFN and frame boundary alignment across cells on the same frequency carrier as specified in TS 38.133 [14]. Hence, if the UE is configured with a serving cell for which (absoluteFrequencySSB, subcarrierSpacing) in ServingCellConfigCommon is equal to (ssbFrequency, ssbSubcarrierSpacing) in this MeasObjectNR, this field indicates whether the UE can utilize the timing of this serving cell to derive the index of SS block transmitted by neighbour cell. Otherwise, this field indicates whether the UE may use the timing of any detected cell on that target frequency to derive the SSB index of all neighbour cells on that frequency.

deriveSSB-IndexFromCellInter If this field is present, UE assumes SFN and frame boundary alignment between the reference serving cell indicated by ServCellIndex and all neighbour cells in this MeasObjectNR as specified in TS 38.133 [14]. This field also indicates that the UE can utilize the timing of the reference serving cell indicated by ServCellIndex to derive the index of SS block transmitted by all inter-frequency neighbour cells on the frequency indicated by the MeasObjectNR. When this field is included, the network should set deriveSSB-IndexFromCell to true.

ssb-ToMeasure The set of SS blocks to be measured within the SMTC measurement duration. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not to be measured while value 1 indicates that the corresponding SS/PBCH block is to be measured (see TS 38.215 [9]). When the field is not configured the UE measures on all SS blocks. Regardless of the value of this field, SS/PBCH blocks outside of the applicable smtc are not to be measured. See TS 38.215 [9] clause 5.1.1.

SSB-PositionQCL-CellsToAddMod field descriptions

physCellId Physical cell identity of a cell in the cell list.

ssb-PositionQCL Indicates the QCL relation between SS/PBCH blocks for a specific cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the value signalled by ssb-PositionQCL-Common.

Conditional Presence	Explanation
AssociatedGapCSIRS	This field is optionally present, Need R if associatedMeasGapCSIRS is configured, otherwise, it is absent.
AssociatedGapSSB	This field is optionally present, Need R if associatedMeasGapSSB is configured, otherwise, it is absent.
CSI-RS	This field is mandatory present if csi-rs-ResourceConfigMobility is configured, otherwise, it is absent.
IntraFreqConnected	This field is optionally present, Need R if the UE is configured with a serving cell for which (absoluteFrequencySSB, subcarrierSpacing) in ServingCellConfigCommon is equal to (ssbFrequency, ssbSubcarrierSpacing) in this MeasObjectNR, otherwise, it is absent.
SCG	This field is optionallly present, Need R, in the measConfig associated with the SCG. It is absent in the measConfig associated with the MCG.
SharedSpectrum	This field is mandatory present if this MeasObject is for a frequency which operates with shared spectrum channel access in FR1. Otherwise, it is absent, Need R.
SharedSpectrum2	This field is optionally present if this MeasObject is for a frequency which operates with shared spectrum channel access in FR2-2, Need R. Otherwise, it is absent, Need R.
SSBorAssociatedSSB	This field is mandatory present if ssb-ConfigMobility is configured or associatedSSB is configured in at least one cell. Otherwise, it is absent, Need R.

– MeasObjectNR-SL

The IE MeasObjectNR-SL concerns a measurement object including a list of transmission resource pool(s) for which CBR measurement is performed for NR sidelink communication/discovery.

MeasObjectNR-SL information element

— ASN1START

— TAG-MEASOBJECTNR-SL-START

MeasObjectNR-SL-r16 ::= SEQUENCE {

tx-PoolMeasToRemoveList-r16 Tx-PoolMeasList-r16 OPTIONAL, — Need N

tx-PoolMeasToAddModList-r16 Tx-PoolMeasList-r16 OPTIONAL — Need N

}

Tx-PoolMeasList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-PoolToMeasureNR-r16)) OF SL-ResourcePoolID-r16

— TAG-MEASOBJECTNR-SL-STOP

— ASN1STOP

– MeasObjectRxTxDiff

The IE MeasObjectRxTxDiff is used to configure the measurement object for UE Rx-Tx time difference measurement.

MeasObjectRxTxDiff information element

— ASN1START

— TAG-MEASOBJECTRXTXDIFF-START

MeasObjectRxTxDiff-r17 ::= SEQUENCE {

dl-Ref-r17 CHOICE {

prs-Ref-r17 NULL,

csi-RS-Ref-r17 NULL,

…

} OPTIONAL, — Need R

…

}

— TAG-MEASOBJECTRXTXDIFF-STOP

— ASN1STOP

MeasObjectRxTxDiff field descriptions

dl-Ref configures the DL references signals to measure Rx-Tx time difference. prs-Ref-r17 indicates PRS is chosen, and csi-RS-Ref-r17 indicates that CSI-RS for tracking is chosen. Only one PRS resource set is configured by the network. Only one NZP-CSI-RS-ResourceSet can be configured with pdc-Info-r17 set to true and it is used for UE Rx-Tx time difference measurement. Only reference signals from the PCell of the MCG can be configured by the network.

– MeasObjectToAddModList

The IE MeasObjectToAddModList concerns a list of measurement objects to add or modify.

MeasObjectToAddModList information element

— ASN1START

— TAG-MEASOBJECTTOADDMODLIST-START

MeasObjectToAddModList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectToAddMod

MeasObjectToAddMod ::= SEQUENCE {

measObjectId MeasObjectId,

measObject CHOICE {

measObjectNR MeasObjectNR,

…,

measObjectEUTRA MeasObjectEUTRA,

measObjectUTRA-FDD-r16 MeasObjectUTRA-FDD-r16,

measObjectNR-SL-r16 MeasObjectNR-SL-r16,

measObjectCLI-r16 MeasObjectCLI-r16,

measObjectRxTxDiff-r17 MeasObjectRxTxDiff-r17,

measObjectRelay-r17 SL-MeasObject-r16

}

}

— TAG-MEASOBJECTTOADDMODLIST-STOP

— ASN1STOP

– MeasObjectUTRA-FDD

The IE MeasObjectUTRA-FDD specifies information applicable for inter-RAT UTRA-FDD neighbouring cells.

MeasObjectUTRA-FDD information element

— ASN1START

— TAG-MEASOBJECTUTRA-FDD-START

MeasObjectUTRA-FDD-r16 ::= SEQUENCE {

carrierFreq-r16 ARFCN-ValueUTRA-FDD-r16,

utra-FDD-Q-OffsetRange-r16 UTRA-FDD-Q-OffsetRange-r16 OPTIONAL, — Need R

cellsToRemoveList-r16 UTRA-FDD-CellIndexList-r16 OPTIONAL, — Need N

cellsToAddModList-r16 CellsToAddModListUTRA-FDD-r16 OPTIONAL, — Need N

…

}

CellsToAddModListUTRA-FDD-r16 ::= SEQUENCE (SIZE (1..maxCellMeasUTRA-FDD-r16)) OF CellsToAddModUTRA-FDD-r16

CellsToAddModUTRA-FDD-r16 ::= SEQUENCE {

cellIndexUTRA-FDD-r16 UTRA-FDD-CellIndex-r16,

physCellId-r16 PhysCellIdUTRA-FDD-r16

}

UTRA-FDD-CellIndexList-r16 ::= SEQUENCE (SIZE (1..maxCellMeasUTRA-FDD-r16)) OF UTRA-FDD-CellIndex-r16

UTRA-FDD-CellIndex-r16 ::= INTEGER (1..maxCellMeasUTRA-FDD-r16)

— TAG-MEASOBJECTUTRA-FDD-STOP

— ASN1STOP

MeasObjectUTRA-FDD field descriptions
carrierFreq Identifies UTRA-FDD carrier frequency for which this configuration is valid. NR does not configure more than one measurement object for the same physical frequency regardless of the ARFCN used to indicate this.
cellIndexUTRA-FDD Entry index in the neighbouring cell list.
cellsToAddModList List of UTRA-FDD cells to add/modify in the neighbouring cell list.
cellsToRemoveList List of cells to remove from the neighbouring cell list.
utra–FDD-Q-OffsetRange Used to indicate a frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB.

– MeasResultCellListSFTD-NR

The IE MeasResultCellListSFTD-NR consists of SFN and radio frame boundary difference between the PCell and an NR cell as specified in TS 38.215 [9] and TS 38.133 [14].

MeasResultCellListSFTD-NR information element

— ASN1START

— TAG-MEASRESULTCELLLISTSFTD-NR-START

MeasResultCellListSFTD-NR ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF MeasResultCellSFTD-NR

MeasResultCellSFTD-NR ::= SEQUENCE {

physCellId PhysCellId,

sfn-OffsetResult INTEGER (0..1023),

frameBoundaryOffsetResult INTEGER (-30720..30719),

rsrp-Result RSRP-Range OPTIONAL

}

— TAG-MEASRESULTCELLLISTSFTD-NR-STOP

— ASN1STOP

MeasResultCellSFTD-NR field descriptions
sfn-OffsetResult Indicates the SFN difference between the PCell and the NR cell as an integer value according to TS 38.215 [9].
frameBoundaryOffsetResult Indicates the frame boundary difference between the PCell and the NR cell as an integer value according to TS 38.215 [9].

– MeasResultCellListSFTD-EUTRA

The IE MeasResultCellListSFTD-EUTRA consists of SFN and radio frame boundary difference between the PCell and an E-UTRA PSCell.

MeasResultCellListSFTD-EUTRA information element

— ASN1START

— TAG-MEASRESULTCELLLISTSFTD-EUTRA-START

MeasResultCellListSFTD-EUTRA ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF MeasResultSFTD-EUTRA

MeasResultSFTD-EUTRA ::= SEQUENCE {

eutra-PhysCellId EUTRA-PhysCellId,

sfn-OffsetResult INTEGER (0..1023),

frameBoundaryOffsetResult INTEGER (-30720..30719),

rsrp-Result RSRP-Range OPTIONAL

}

— TAG-MEASRESULTCELLLISTSFTD-EUTRA-STOP

— ASN1STOP

MeasResultSFTD-EUTRA field descriptions
eutra-PhysCellId Identifies the physical cell identity of the E-UTRA cell for which the reporting is being performed.
sfn-OffsetResult Indicates the SFN difference between the PCell and the E-UTRA cell as an integer value according to TS 38.215 [9].
frameBoundaryOffsetResult Indicates the frame boundary difference between the PCell and the E-UTRA cell as an integer value according to TS 38.215 [9].

– MeasResults

The IE MeasResults covers measured results for intra-frequency, inter-frequency, inter-RAT mobility and measured results for NR sidelink communication/discovery.

MeasResults information element

— ASN1START

— TAG-MEASRESULTS-START

MeasResults ::= SEQUENCE {

measId MeasId,

measResultServingMOList MeasResultServMOList,

measResultNeighCells CHOICE {

measResultListNR MeasResultListNR,

…,

measResultListEUTRA MeasResultListEUTRA,

measResultListUTRA-FDD-r16 MeasResultListUTRA-FDD-r16,

sl-MeasResultsCandRelay-r17 OCTET STRING — Contains PC5 SL-MeasResultListRelay-r17

} OPTIONAL,

…,

[[

measResultServFreqListEUTRA-SCG MeasResultServFreqListEUTRA-SCG OPTIONAL,

measResultServFreqListNR-SCG MeasResultServFreqListNR-SCG OPTIONAL,

measResultSFTD-EUTRA MeasResultSFTD-EUTRA OPTIONAL,

measResultSFTD-NR MeasResultCellSFTD-NR OPTIONAL

]],

[[

measResultCellListSFTD-NR MeasResultCellListSFTD-NR OPTIONAL

]],

[[

measResultForRSSI-r16 MeasResultForRSSI-r16 OPTIONAL,

locationInfo-r16 LocationInfo-r16 OPTIONAL,

ul-PDCP-DelayValueResultList-r16 UL-PDCP-DelayValueResultList-r16 OPTIONAL,

measResultsSL-r16 MeasResultsSL-r16 OPTIONAL,

measResultCLI-r16 MeasResultCLI-r16 OPTIONAL

]],

[[

measResultRxTxTimeDiff-r17 MeasResultRxTxTimeDiff-r17 OPTIONAL,

sl-MeasResultServingRelay-r17 OCTET STRING OPTIONAL,

— Contains PC5 SL-MeasResultRelay-r17

ul-PDCP-ExcessDelayResultList-r17 UL-PDCP-ExcessDelayResultList-r17 OPTIONAL,

coarseLocationInfo-r17 OCTET STRING OPTIONAL

]]

}

MeasResultServMOList ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResultServMO

MeasResultServMO ::= SEQUENCE {

servCellId ServCellIndex,

measResultServingCell MeasResultNR,

measResultBestNeighCell MeasResultNR OPTIONAL,

…

}

MeasResultListNR ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultNR

MeasResultNR ::= SEQUENCE {

physCellId PhysCellId OPTIONAL,

measResult SEQUENCE {

cellResults SEQUENCE{

resultsSSB-Cell MeasQuantityResults OPTIONAL,

resultsCSI-RS-Cell MeasQuantityResults OPTIONAL

},

rsIndexResults SEQUENCE{

resultsSSB-Indexes ResultsPerSSB-IndexList OPTIONAL,

resultsCSI-RS-Indexes ResultsPerCSI-RS-IndexList OPTIONAL

} OPTIONAL

},

…,

[[

cgi-Info CGI-InfoNR OPTIONAL

]] ,

[[

choCandidate-r17 ENUMERATED {true} OPTIONAL,

choConfig-r17 SEQUENCE (SIZE (1..2)) OF CondTriggerConfig-r16 OPTIONAL,

triggeredEvent-r17 SEQUENCE {

timeBetweenEvents-r17 TimeBetweenEvent-r17 OPTIONAL,

firstTriggeredEvent ENUMERATED {condFirstEvent, condSecondEvent} OPTIONAL

} OPTIONAL

]]

}

MeasResultListEUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultEUTRA

MeasResultEUTRA ::= SEQUENCE {

eutra-PhysCellId PhysCellId,

measResult MeasQuantityResultsEUTRA,

cgi-Info CGI-InfoEUTRA OPTIONAL,

…

}

MultiBandInfoListEUTRA ::= SEQUENCE (SIZE (1..maxMultiBands)) OF FreqBandIndicatorEUTRA

MeasQuantityResults ::= SEQUENCE {

rsrp RSRP-Range OPTIONAL,

rsrq RSRQ-Range OPTIONAL,

sinr SINR-Range OPTIONAL

}

MeasQuantityResultsEUTRA ::= SEQUENCE {

rsrp RSRP-RangeEUTRA OPTIONAL,

rsrq RSRQ-RangeEUTRA OPTIONAL,

sinr SINR-RangeEUTRA OPTIONAL

}

ResultsPerSSB-IndexList::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2)) OF ResultsPerSSB-Index

ResultsPerSSB-Index ::= SEQUENCE {

ssb-Index SSB-Index,

ssb-Results MeasQuantityResults OPTIONAL

}

ResultsPerCSI-RS-IndexList::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2)) OF ResultsPerCSI-RS-Index

ResultsPerCSI-RS-Index ::= SEQUENCE {

csi-RS-Index CSI-RS-Index,

csi-RS-Results MeasQuantityResults OPTIONAL

}

MeasResultServFreqListEUTRA-SCG ::= SEQUENCE (SIZE (1..maxNrofServingCellsEUTRA)) OF MeasResult2EUTRA

MeasResultServFreqListNR-SCG ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResult2NR

MeasResultListUTRA-FDD-r16 ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultUTRA-FDD-r16

MeasResultUTRA-FDD-r16 ::= SEQUENCE {

physCellId-r16 PhysCellIdUTRA-FDD-r16,

measResult-r16 SEQUENCE {

utra-FDD-RSCP-r16 INTEGER (-5..91) OPTIONAL,

utra-FDD-EcN0-r16 INTEGER (0..49) OPTIONAL

}

}

MeasResultForRSSI-r16 ::= SEQUENCE {

rssi-Result-r16 RSSI-Range-r16,

channelOccupancy-r16 INTEGER (0..100)

}

MeasResultCLI-r16 ::= SEQUENCE {

measResultListSRS-RSRP-r16 MeasResultListSRS-RSRP-r16 OPTIONAL,

measResultListCLI-RSSI-r16 MeasResultListCLI-RSSI-r16 OPTIONAL

}

MeasResultListSRS-RSRP-r16 ::= SEQUENCE (SIZE (1.. maxCLI-Report-r16)) OF MeasResultSRS-RSRP-r16

MeasResultSRS-RSRP-r16 ::= SEQUENCE {

srs-ResourceId-r16 SRS-ResourceId,

srs-RSRP-Result-r16 SRS-RSRP-Range-r16

}

MeasResultListCLI-RSSI-r16 ::= SEQUENCE (SIZE (1.. maxCLI-Report-r16)) OF MeasResultCLI-RSSI-r16

MeasResultCLI-RSSI-r16 ::= SEQUENCE {

rssi-ResourceId-r16 RSSI-ResourceId-r16,

cli-RSSI-Result-r16 CLI-RSSI-Range-r16

}

UL-PDCP-DelayValueResultList-r16 ::= SEQUENCE (SIZE (1..maxDRB)) OF UL-PDCP-DelayValueResult-r16

UL-PDCP-DelayValueResult-r16 ::= SEQUENCE {

drb-Id-r16 DRB-Identity,

averageDelay-r16 INTEGER (0..10000),

…

}

UL-PDCP-ExcessDelayResultList-r17 ::= SEQUENCE (SIZE (1..maxDRB)) OF UL-PDCP-ExcessDelayResult-r17

UL-PDCP-ExcessDelayResult-r17 ::= SEQUENCE {

drb-Id-r17 DRB-Identity,

excessDelay-r17 INTEGER (0..31),

…

}

TimeBetweenEvent-r17 ::= INTEGER (0..1023)

— TAG-MEASRESULTS-STOP

— ASN1STOP

MeasResultEUTRA field descriptions

eutra-PhysCellId Identifies the physical cell identity of the E-UTRA cell for which the reporting is being performed. The UE reports a value in the range 0..503, other values are reserved.

MeasResultNR field descriptions

averageDelay Indicates average delay for the packets during the reporting period, as specified in TS 38.314 [53]. Value 0 corresponds to 0 millisecond, value 1 corresponds to 0.1 millisecond, value 2 corresponds to 0.2 millisecond, and so on.

cellResults Cell level measurement results.

choCandidate This field indicates whether the associated cell is a candidate target cell for conditional handover. This field may be included only in the SuccessHO-Report within UEInformationResponse message.

choConfig If the associated cell is a candidate target cell for conditional handover, this field indicates the conditional handover execution condition for each measId within condTriggerConfig associated to the cell. This field may be included only in the rlf-report within UEInformationResponse message.

drb-Id Indicates DRB value for which uplink PDCP delay ratio or value is provided, according to TS 38.314 [53].

firstTriggeredEvent This field is set to condFirstEvent if the execution condition associated to the first entry of choConfig was fulfilled first in time. This field is set to condSecondEvent if the execution condition associated to the second entry of choConfig was fulfilled first in time. This field may be included only in rlf-report within UEInformationResponse message.

locationInfo Positioning related information and measurements.

physCellId The physical cell identity of the NR cell for which the reporting is being performed.

resultsSSB-Cell Cell level measurement results based on SS/PBCH related measurements.

resultsSSB-Indexes Beam level measurement results based on SS/PBCH related measurements.

resultsCSI-RS-Cell Cell level measurement results based on CSI-RS related measurements.

resultsCSI-RS-Indexes Beam level measurement results based on CSI-RS related measurements.

rsIndexResults Beam level measurement results.

timeBetweenEvents Indicates the time elapsed between fulfilling the conditional execution conditions included in choConfig. Value in milliseconds. The maximum value 1023 means 1023ms or longer. This field may be included only in the reports associated to UEInformationResponse message, e.g., rlf-Report.

MeasResultUTRA-FDD field descriptions

physCellId The physical cell identity of the UTRA-FDD cell for which the reporting is being performed.

utra-FDD-EcN0 According to CPICH_Ec/No in TS 25.133 [46] for FDD.

utra-FDD-RSCP According to CPICH_RSCP in TS 25.133 [46] for FDD.

MeasResults field descriptions
coarseLocationInfo This field indicates the coarse location information reported by the UE. This field is coded as the Ellipsoid-Point defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. The least significant bits of degreesLatitude and degreesLongitude are set to 0 to meet the accuracy requirement corresponds to a granularity of approximately 2 km. It is up to UE implementation how many LSBs are set to 0 to meet the accuracy requirement
excessDelay Indicates the ratio of packets in UL per DRB exceeding the configured delay threshold among the UL PDCP SDUs, according to the UL PDCP Excess Packet Delay per DRB mapping table, as defined in TS 38.314 [53], Table 4.3.1.e-1.
measId Identifies the measurement identity for which the reporting is being performed.
measQuantityResults The value sinr is not included when it is used for LogMeasReport-r16.
measResultCellListSFTD-NR SFTD measurement results between the PCell and the NR neighbour cell(s) in NR standalone.
measResultCLI CLI measurement results.
measResultEUTRA Measured results of an E-UTRA cell.
measResultForRSSI Includes measured RSSI result in dBm (see TS 38.215 [9]) and channelOccupancy which is the percentage of samples when the RSSI was above the configured channelOccupancyThreshold for the associated reportConfig.
measResultListEUTRA List of measured results for the maximum number of reported best cells for an E-UTRA measurement identity.
measResultListNR List of measured results for the maximum number of reported best cells for an NR measurement identity.
measResultListUTRA-FDD List of measured results for the maximum number of reported best cells for a UTRA-FDD measurement identity.
measResultNR Measured results of an NR cell.
measResultServFreqListEUTRA-SCG Measured results of the E-UTRA SCG serving frequencies: the measurement result of PSCell and each SCell, if any, and of the best neighbouring cell on each E-UTRA SCG serving frequency.
measResultServFreqListNR-SCG Measured results of the NR SCG serving frequencies: the measurement result of PSCell and each SCell, if any, and of the best neighbouring cell on each NR SCG serving frequency.
measResultServingMOList Measured results of measured cells with reference signals indicated in the serving cell measurement objects including measurement results of SpCell, configured SCell(s) and best neighbouring cell within measured cells with reference signals indicated in on each serving cell measurement object. If the sending of the MeasurementReport message is triggered by a measurement configured by the field sl-ConfigDedicatedForNR received within an E-UTRA RRCConnectionReconfiguration message (i.e. CBR measurements), this field is not applicable and its contents is ignored by the network.
measResultSFTD-EUTRA SFTD measurement results between the PCell and the E-UTRA PScell in NE-DC.
measResultSFTD-NR SFTD measurement results between the PCell and the NR PScell in NR-DC.
measResultsSL CBR measurements results for NR sidelink communication/discovery.
measResultUTRA-FDD Measured result of a UTRA-FDD cell.
sl-MeasResultsCandRelay Measurement result(s) of candiate L2 U2N relay UE(s).
sl-MeasResultsServingRelay Measurement result of serving L2 U2N relay UE.

– MeasResult2EUTRA

The IE MeasResult2EUTRA contains measurements on E-UTRA frequencies.

MeasResult2EUTRA information element

— ASN1START

— TAG-MEASRESULT2EUTRA-START

MeasResult2EUTRA ::= SEQUENCE {

carrierFreq ARFCN-ValueEUTRA,

measResultServingCell MeasResultEUTRA OPTIONAL,

measResultBestNeighCell MeasResultEUTRA OPTIONAL,

…

}

— TAG-MEASRESULT2EUTRA-STOP

— ASN1STOP

– MeasResult2NR

The IE MeasResult2NR contains measurements on NR frequencies.

MeasResult2NR information element

— ASN1START

— TAG-MEASRESULT2NR-START

MeasResult2NR ::= SEQUENCE {

ssbFrequency ARFCN-ValueNR OPTIONAL,

refFreqCSI-RS ARFCN-ValueNR OPTIONAL,

measResultServingCell MeasResultNR OPTIONAL,

measResultNeighCellListNR MeasResultListNR OPTIONAL,

…

}

— TAG-MEASRESULT2NR-STOP

— ASN1STOP

– MeasResultIdleEUTRA

The IE MeasResultIdleEUTRA covers the E-UTRA measurement results performed in RRC_IDLE and RRC_INACTIVE.

MeasResultIdleEUTRA information element

— ASN1START

— TAG-MEASRESULTIDLEEUTRA-START

MeasResultIdleEUTRA-r16 ::= SEQUENCE {

measResultsPerCarrierListIdleEUTRA-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleEUTRA-r16,

…

}

MeasResultsPerCarrierIdleEUTRA-r16 ::= SEQUENCE {

carrierFreqEUTRA-r16 ARFCN-ValueEUTRA,

measResultsPerCellListIdleEUTRA-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleEUTRA-r16,

…

}

MeasResultsPerCellIdleEUTRA-r16 ::= SEQUENCE {

eutra-PhysCellId-r16 EUTRA-PhysCellId,

measIdleResultEUTRA-r16 SEQUENCE {

rsrp-ResultEUTRA-r16 RSRP-RangeEUTRA OPTIONAL,

rsrq-ResultEUTRA-r16 RSRQ-RangeEUTRA-r16 OPTIONAL

},

…

}

— TAG-MEASRESULTIDLEEUTRA-STOP

— ASN1STOP

MeasResultIdleEUTRA field descriptions

carrierFreqEUTRA Indicates the E-UTRA carrier frequency.

eutra-PhysCellId Indicates the physical cell identity of an E-UTRA cell.

measIdleResultEUTRA Idle/inactive measurement results for an E-UTRA cell.

measResultsPerCarrierListIdleEUTRA List of idle/inactive measured results for the maximum number of reported E-UTRA carriers.

measResultsPerCellListIdleEUTRA List of idle/inactive measured results for the maximum number of reported best cells for a given E-UTRA carrier.

– MeasResultIdleNR

The IE MeasResultIdleNR covers the NR measurement results performed in RRC_IDLE and RRC_INACTIVE.

MeasResultIdleNR information element

— ASN1START

— TAG-MEASRESULTIDLENR-START

MeasResultIdleNR-r16 ::= SEQUENCE {

measResultServingCell-r16 SEQUENCE {

rsrp-Result-r16 RSRP-Range OPTIONAL,

rsrq-Result-r16 RSRQ-Range OPTIONAL,

resultsSSB-Indexes-r16 ResultsPerSSB-IndexList-r16 OPTIONAL

},

measResultsPerCarrierListIdleNR-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleNR-r16 OPTIONAL,

…

}

MeasResultsPerCarrierIdleNR-r16 ::= SEQUENCE {

carrierFreq-r16 ARFCN-ValueNR,

measResultsPerCellListIdleNR-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleNR-r16,

…

}

MeasResultsPerCellIdleNR-r16 ::= SEQUENCE {

physCellId-r16 PhysCellId,

measIdleResultNR-r16 SEQUENCE {

rsrp-Result-r16 RSRP-Range OPTIONAL,

rsrq-Result-r16 RSRQ-Range OPTIONAL,

resultsSSB-Indexes-r16 ResultsPerSSB-IndexList-r16 OPTIONAL

},

…

}

ResultsPerSSB-IndexList-r16 ::= SEQUENCE (SIZE (1.. maxNrofIndexesToReport)) OF ResultsPerSSB-IndexIdle-r16

ResultsPerSSB-IndexIdle-r16 ::= SEQUENCE {

ssb-Index-r16 SSB-Index,

ssb-Results-r16 SEQUENCE {

ssb-RSRP-Result-r16 RSRP-Range OPTIONAL,

ssb-RSRQ-Result-r16 RSRQ-Range OPTIONAL

} OPTIONAL

}

— TAG-MEASRESULTIDLENR-STOP

— ASN1STOP

MeasResultIdleNR field descriptions

carrierFreq Indicates the NR carrier frequency.

measIdleResultNR Idle/inactive measurement results for an NR cell (optionally including beam level measurements).

measResultServingCell Measured results of the serving cell (i.e., PCell) from idle/inactive measurements.

measResultsPerCellListIdleNR List of idle/inactive measured results for the maximum number of reported best cells for a given NR carrier.

resultsSSB-Indexes Beam level measurement results (indexes and optionally, beam measurements).

– MeasResultRxTxTimeDiff

The IE MeasResultRxTxTimeDiff is used to provide Rx-Tx time difference measurement result.

MeasResultRxTxTimeDiff information element

— ASN1START

— TAG-MEASRESULTRXTXTIMEDIFF-START

MeasResultRxTxTimeDiff-r17 ::= SEQUENCE {

rxTxTimeDiff-ue-r17 RxTxTimeDiff-r17 OPTIONAL,

…

}

— TAG-MEASRESULTRXTXTIMEDIFF-STOP

— ASN1STOP

MeasResultRxTxTimeDiff field descriptions

rxTxTimeDiff-ue indicates the Rx-Tx Time difference measurement at the UE (see clause 5.1.30, TS 38.215 [9]).

– MeasResultSCG-Failure

The IE MeasResultSCG-Failure is used to provide information regarding failures detected by the UE in (NG)EN-DC and NR-DC.

MeasResultSCG-Failure information element

— ASN1START

— TAG-MEASRESULTSCG-FAILURE-START

MeasResultSCG-Failure ::= SEQUENCE {

measResultPerMOList MeasResultList2NR,

…,

[[

locationInfo-r16 LocationInfo-r16 OPTIONAL

]]

}

MeasResultList2NR ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2NR

— TAG-MEASRESULTSCG-FAILURE-STOP

— ASN1STOP

– MeasResultsSL

The IE MeasResultsSL covers measured results for NR sidelink communication/discovery.

MeasResultsSL information element

— ASN1START

— TAG-MEASRESULTSSL-START

MeasResultsSL-r16 ::= SEQUENCE {

measResultsListSL-r16 CHOICE {

measResultNR-SL-r16 MeasResultNR-SL-r16,

…

},

…

}

MeasResultNR-SL-r16 ::= SEQUENCE {

measResultListCBR-NR-r16 SEQUENCE (SIZE (1.. maxNrofSL-PoolToMeasureNR-r16)) OF MeasResultCBR-NR-r16,

…

}

MeasResultCBR-NR-r16 ::= SEQUENCE {

sl-poolReportIdentity-r16 SL-ResourcePoolID-r16,

sl-CBR-ResultsNR-r16 SL-CBR-r16,

…

}

— TAG-MEASRESULTSSL-STOP

— ASN1STOP

MeasResultsSL field descriptions
measResultNR-SL Include the measured results for NR sidelink communication/discovery.

MeasResultNR-SL field descriptions

measResultListCBR-NR CBR measurement results for NR sidelink communication/discovery.

sl-poolReportIdentity The identity of the transmission resource pool which is corresponding to the sl-ResourcePoolID configured in a resource pool for NR sidelink communication/discovery.

– MeasTriggerQuantityEUTRA

The IE MeasTriggerQuantityEUTRA is used to configure the trigger quantity and reporting range for E-UTRA measurements. The RSRP, RSRQ and SINR ranges correspond to RSRP-Range, RSRQ-Range and RS-SINR-Range in TS 36.331 [10], respectively.

MeasTriggerQuantityEUTRA information element

— ASN1START

— TAG-MEASTRIGGERQUANTITYEUTRA-START

MeasTriggerQuantityEUTRA::= CHOICE {

rsrp RSRP-RangeEUTRA,

rsrq RSRQ-RangeEUTRA,

sinr SINR-RangeEUTRA

}

RSRP-RangeEUTRA ::= INTEGER (0..97)

RSRQ-RangeEUTRA ::= INTEGER (0..34)

SINR-RangeEUTRA ::= INTEGER (0..127)

— TAG-MEASTRIGGERQUANTITYEUTRA-STOP

— ASN1STOP

– MobilityStateParameters

The IE MobilityStateParameters contains parameters to determine UE mobility state.

MobilityStateParameters information element

— ASN1START

— TAG-MOBILITYSTATEPARAMETERS-START

MobilityStateParameters ::= SEQUENCE{

t-Evaluation ENUMERATED {

s30, s60, s120, s180, s240, spare3, spare2, spare1},

t-HystNormal ENUMERATED {

s30, s60, s120, s180, s240, spare3, spare2, spare1},

n-CellChangeMedium INTEGER (1..16),

n-CellChangeHigh INTEGER (1..16)

}

— TAG-MOBILITYSTATEPARAMETERS-STOP

— ASN1STOP

MobilityStateParameters field descriptions
n-CellChangeHigh The number of cell changes to enter high mobility state. Corresponds to NCR_H in TS 38.304 [20].
n-CellChangeMedium The number of cell changes to enter medium mobility state. Corresponds to NCR_M in TS 38.304 [20].
t-Evaluation The duration for evaluating criteria to enter mobility states. Corresponds to TCRmax in TS 38.304 [20]. Value in seconds, s30 corresponds to 30 s and so on.
t-HystNormal The additional duration for evaluating criteria to enter normal mobility state. Corresponds to TCRmaxHyst in TS 38.304 [20]. Value in seconds, value s30 corresponds to 30 seconds and so on.

– MRB-Identity

The IE MRB-Identity is used to identify a multicast MRB used by a UE.

MRB-Identity information element

— ASN1START

— TAG-MRB-IDENTITY-START

MRB-Identity-r17 ::= INTEGER (1..512)

— TAG-MRB-IDENTITY-STOP

— ASN1STOP

– MsgA-ConfigCommon

The IE MsgA-ConfigCommon is used to configure the PRACH and PUSCH resource for transmission of MsgA in 2-step random access type procedure.

— ASN1START

— TAG-MSGACONFIGCOMMON-START

MsgA-ConfigCommon-r16 ::= SEQUENCE {

rach-ConfigCommonTwoStepRA-r16 RACH-ConfigCommonTwoStepRA-r16,

msgA-PUSCH-Config-r16 MsgA-PUSCH-Config-r16 OPTIONAL –Cond InitialBWPConfig

}

— TAG-MSGACONFIGCOMMON-STOP

— ASN1STOP

MsgA-ConfigCommon field descriptions
msgA-PUSCH-Config Configuration of cell-specific MsgA PUSCH parameters which the UE uses for contention-based MsgA PUSCH transmission of this BWP. If the field is not configured for the selected UL BWP, the UE shall use the MsgA PUSCH configuration of initial UL BWP.
rach-ConfigCommonTwoStepRA Configuration of cell specific random access parameters which the UE uses for contention based and contention free 2-step random access type procedure as well as for 2-step RA type contention based beam failure recovery in this BWP.

Conditional Presence	Explanation
InitialBWPConfig	The field is mandatory present when MsgA-ConfigCommon is configured for the initial uplink BWP, or when MsgA-ConfigCommon is configured for a non-initial uplink BWP and MsgA-ConfigCommon is not configured for the initial uplink BWP, otherwise the field is optionally present, Need S.

– MsgA-PUSCH-Config

The IE MsgA-PUSCH-Config is used to specify the PUSCH allocation for MsgA in 2-step random access type procedure.

MsgA-PUSCH-Config information element

— ASN1START

— TAG-MSGA-PUSCH-CONFIG-START

MsgA-PUSCH-Config-r16 ::= SEQUENCE {

msgA-PUSCH-ResourceGroupA-r16 MsgA-PUSCH-Resource-r16 OPTIONAL, — Cond InitialBWPConfig

msgA-PUSCH-ResourceGroupB-r16 MsgA-PUSCH-Resource-r16 OPTIONAL, — Cond GroupBConfigured

msgA-TransformPrecoder-r16 ENUMERATED {enabled, disabled} OPTIONAL, — Need R

msgA-DataScramblingIndex-r16 INTEGER (0..1023) OPTIONAL, — Need S

msgA-DeltaPreamble-r16 INTEGER (-1..6) OPTIONAL — Need R

}

MsgA-PUSCH-Resource-r16 ::= SEQUENCE {

msgA-MCS-r16 INTEGER (0..15),

nrofSlotsMsgA-PUSCH-r16 INTEGER (1..4),

nrofMsgA-PO-PerSlot-r16 ENUMERATED {one, two, three, six},

msgA-PUSCH-TimeDomainOffset-r16 INTEGER (1..32),

msgA-PUSCH-TimeDomainAllocation-r16 INTEGER (1..maxNrofUL-Allocations) OPTIONAL, — Need S

startSymbolAndLengthMsgA-PO-r16 INTEGER (0..127) OPTIONAL, — Need S

mappingTypeMsgA-PUSCH-r16 ENUMERATED {typeA, typeB} OPTIONAL, — Need S

guardPeriodMsgA-PUSCH-r16 INTEGER (0..3) OPTIONAL, — Need R

guardBandMsgA-PUSCH-r16 INTEGER (0..1),

frequencyStartMsgA-PUSCH-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1),

nrofPRBs-PerMsgA-PO-r16 INTEGER (1..32),

nrofMsgA-PO-FDM-r16 ENUMERATED {one, two, four, eight},

msgA-IntraSlotFrequencyHopping-r16 ENUMERATED {enabled} OPTIONAL, — Need R

msgA-HoppingBits-r16 BIT STRING (SIZE(2)) OPTIONAL, — Cond FreqHopConfigured

msgA-DMRS-Config-r16 MsgA-DMRS-Config-r16,

nrofDMRS-Sequences-r16 INTEGER (1..2),

msgA-Alpha-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06,

alpha07, alpha08, alpha09, alpha1} OPTIONAL, — Need S

interlaceIndexFirstPO-MsgA-PUSCH-r16 INTEGER (1..10) OPTIONAL, — Need R

nrofInterlacesPerMsgA-PO-r16 INTEGER (1..10) OPTIONAL, — Need R

…

}

MsgA-DMRS-Config-r16 ::= SEQUENCE {

msgA-DMRS-AdditionalPosition-r16 ENUMERATED {pos0, pos1, pos3} OPTIONAL, — Need S

msgA-MaxLength-r16 ENUMERATED {len2} OPTIONAL, — Need S

msgA-PUSCH-DMRS-CDM-Group-r16 INTEGER (0..1) OPTIONAL, — Need S

msgA-PUSCH-NrofPorts-r16 INTEGER (0..1) OPTIONAL, — Need S

msgA-ScramblingID0-r16 INTEGER (0..65535) OPTIONAL, — Need S

msgA-ScramblingID1-r16 INTEGER (0..65535) OPTIONAL — Need S

}

— TAG-MSGA-PUSCH-CONFIG-STOP

— ASN1STOP

MsgA-PUSCH-Config field descriptions

msgA-DataScramblingIndex Identifier used to initiate data scrambling (c_init) for msgA PUSCH. If the field is absent the UE applies the value Physical cell ID (physCellID).

msgA-DeltaPreamble Power offset of msgA PUSCH relative to the preamble received target power. Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1).

msgA-PUSCH-ResourceGroupA MsgA PUSCH resources that the UE shall use when performing MsgA transmission using preambles group A. If field is not configured for the selected UL BWP, the UE shall use the MsgA PUSCH configuration for group A of initial UL BWP.

msgA-PUSCH-ResourceGroupB MsgA PUSCH resources that the UE shall use when performing MsgA transmission using preambles group B.

msgA-TransformPrecoder Enables or disables the transform precoder for MsgA transmission (see clause 6.1.3 of TS 38.214 [19]).

MsgA-PUSCH-Resource field descriptions

guardBandMsgA-PUSCH PRB-level guard band between FDMed PUSCH occasions (see TS 38.213 [13], clause 8.1A). If interlaced PUSCH is configured, value 0 is applied.

guardPeriodMsgA-PUSCH Guard period between PUSCH occasions in the unit of symbols (see TS 38.213 [13], clause 8.1A).

frequencyStartMsgA-PUSCH Offset of lowest PUSCH occasion in frequency domain with respect to PRB 0 (see TS 38.213 [13], clause 8.1A).

interlaceIndexFirstPO-MsgA-PUSCH Interlace index of the first PUSCH occasion in frequency domain if interlaced PUSCH is configured. For 30kHz SCS only the integers 1, 2, 3, 4, 5 are applicable (see TS 38.213 [13], clause 8.1A).

mappingTypeMsgA-PUSCH PUSCH mapping type A or B. If the field is absent, the UE shall use the parameter msgA-PUSCH-TimeDomainAllocation (see TS 38.213 [13], clause 8.1A).

msgA-Alpha Dedicated alpha value for MsgA PUSCH. If the field is absent, the UE shall use the value of msg3-Alpha if configured, else UE applies value 1 (see TS 38.213 [13], clause 7.1.1).

msgA-DMRS-Config DMRS configuration for msgA PUSCH (see TS 38.213 [13], clause 8.1A and TS 38.214 [19] clause 6.2.2).

msgA-HoppingBits Value of hopping bits to indicate which frequency offset to be used for second hop. See Table 8.3-1 in TS 38.213 [13].

msgA-IntraSlotFrequencyHopping Intra-slot frequency hopping per PUSCH occasion (see TS 38.213 [13], clause 8.1A).

msgA-MCS Indicates the MCS index for msgA PUSCH from the Table 6.1.4.1-1 for DFT-s-OFDM and Table 5.1.3.1-1 for CP-OFDM in TS 38.214 [19].

msgA-PUSCH-TimeDomainAllocation Indicates a combination of start symbol and length and PUSCH mapping type from the TDRA table (PUSCH-TimeDomainResourceAllocationList if provided in PUSCH-ConfigCommon, or else the default Table 6.1.2.1.1-2 in 38.214 [19] is used if pusch-TimeDomainAllocationList is not provided in PUSCH-ConfigCommon). The parameter K2 in the table is not used for msgA PUSCH. The network configures one of msgA-PUSCH-TimeDomainAllocation and startSymbolAndLengthMsgA-PO, but not both. If the field is absent, the UE shall use the value of startSymbolAndLenghtMsgA-PO.

msgA-PUSCH-TimeDomainOffset A single time offset with respect to the start of each PRACH slot (with at least one valid RO), counted as the number of slots (based on the numerology of active UL BWP). See TS 38.213 [13], clause 8.1A.

nrofDMRS-Sequences Number of DMRS sequences for MsgA PUSCH for CP-OFDM. In case of single PUSCH configuration or if the DMRS symbols of multiple configurations are not overlapped, if the DMRS resources configured in one PUSCH occasion is no larger than 8 (for len2) or 4 (for len1), then only DMRS port is configured.

nrofInterlacesPerMsgA-PO Number of consecutive interlaces per PUSCH occasion if interlaced PUSCH is configured. For 30kHz SCS only the integers 1, 2, 3, 4, 5 are applicable (see TS 38.213 [13], clause 8.1A).

nrofMsgA-PO-FDM The number of msgA PUSCH occasions FDMed in one time instance (see TS 38.213 [13], clause 8.1A).

nrofMsgA-PO-PerSlot Number of time domain PUSCH occasions in each slot. PUSCH occasions including guard period are contiguous in time domain within a slot (see TS 38.213 [13], clause 8.1A).

nrofPRBs-PerMsgA-PO Number of PRBs per PUSCH occasion (see TS 38.213 [13], clause 8.1A).

nrofSlotsMsgA-PUSCH Number of slots (in active UL BWP numerology) containing one or multiple PUSCH occasions, each slot has the same time domain resource allocation (see TS 38.213 [13], clause 8.1A).

startSymbolAndLengthMsgA-PO An index giving valid combinations of start symbol, length and mapping type as start and length indicator (SLIV) for the first msgA PUSCH occasion, for RRC_CONNECTED UEs in non-initial BWP as described in TS 38.214 [19] clause 6.1.2. The network configures the field so that the allocation does not cross the slot boundary. The number of occupied symbols excludes the guard period. If the field is absent, the UE shall use the value in msgA-PUSCH-TimeDomainAllocation (see TS 38.213 [13], clause 8.1A). The network configures one of msgA-PUSCH-TimeDomainAllocation and startSymbolAndLengthMsgA-PO, but not both. If the field is absent, the UE shall use the value of msgA-PUSCH-TimeDomainAllocation.

MsgA-DMRS-Config field descriptions

msgA-DMRS-AdditionalPosition Indicates the position for additional DM-RS. If the field is absent, the UE applies value pos2.

msgA-MaxLength indicates single-symbol or double-symbol DMRS. If the field is absent, the UE applies value len1.

msgA-PUSCH-DMRS-CDM-Group 1-bit indication of indices of CDM group(s). If the field is absent, then both CDM groups are used.

msgA-PUSCH-NrofPorts 0 indicates 1 port per CDM group, 1 indicates 2 ports per CDM group. If the field is absent then 4 ports per CDM group are used (see TS 38.213 [13], clause 8.1A).

msgA-ScramblingID0 UL DMRS scrambling initialization for CP-OFDM. If the field is absent the UE applies the value Physical cell ID (physCellID).

msgA-ScramblingID1 UL DMRS scrambling initialization for CP-OFDM. If the field is absent the UE applies the value Physical cell ID (physCellID).

Conditional Presence	Explanation
FreqHopConfigured	This field is mandatory present when the field msgA-IntraSlotFrequencyHopping is configured. Otherwise, the field is absent.
GroupBConfigured	The field is mandatory present if groupB-ConfiguredTwoStepRA is configured in RACH-ConfigCommonTwoStepRA, otherwise the field is absent.
InitialBWPConfig	The field is mandatory present when MsgA-ConfigCommon is configured for the initial uplink BWP, or when MsgA-ConfigCommon is configured for a non-initial uplink BWP and MsgA-ConfigCommon is not configured for the initial uplink BWP, otherwise the field is optionally present, Need S.

– MultiFrequencyBandListNR

The IE MultiFrequencyBandListNR is used to configure a list of one or multiple NR frequency bands.

MultiFrequencyBandListNR information element

— ASN1START

— TAG-MULTIFREQUENCYBANDLISTNR-START

MultiFrequencyBandListNR ::= SEQUENCE (SIZE (1..maxNrofMultiBands)) OF FreqBandIndicatorNR

— TAG-MULTIFREQUENCYBANDLISTNR-STOP

— ASN1STOP

– MultiFrequencyBandListNR-SIB

The IE MultiFrequencyBandListNR-SIB indicates the list of frequency bands, for which cell (re-)selection parameters are common, and a list of additionalPmax and additionalSpectrumEmission.

MultiFrequencyBandListNR-SIB information element

— ASN1START

— TAG-MULTIFREQUENCYBANDLISTNR-SIB-START

MultiFrequencyBandListNR-SIB ::= SEQUENCE (SIZE (1.. maxNrofMultiBands)) OF NR-MultiBandInfo

NR-MultiBandInfo ::= SEQUENCE {

freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, — Cond OptULNotSIB2

nr-NS-PmaxList NR-NS-PmaxList OPTIONAL — Need S

}

— TAG-MULTIFREQUENCYBANDLISTNR-SIB-STOP

— ASN1STOP

NR-MultiBandInfo field descriptions

freqBandIndicatorNR Provides an NR frequency band number as defined in TS 38.101-1 [15] and TS 38.101-2 [39], table 5.2-1.

nr-NS-PmaxList Provides a list of additionalPmax and additionalSpectrumEmission values. If the field is absent the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1 [15] table 6.2.3.1-1A , and TS 38.101-2 [39], table 6.2.3.1-2). This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63].

Conditional Presence	Explanation
OptULNotSIB2	The field is absent for SIB2 and is mandatory present in SIB4 and frequencyInfoDL-SIB. Otherwise, if the field is absent in frequencyInfoUL-SIB in UplinkConfigCommonSIB, the UE will use the frequency band indicated in frequencyInfoDL-SIB in DownlinkConfigCommonSIB.

– MUSIM-GapConfig

The IE MUSIM-GapConfig specifies the MUSIM gap configuration and controls setup/release of MUSIM gaps.

MUSIM-GapConfig information element

— ASN1START

— TAG-MUSIM-GAPCONFIG-START

MUSIM-GapConfig-r17 ::= SEQUENCE {

musim-GapToReleaseList-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-GapId-r17 OPTIONAL, — Need N

musim-GapToAddModList-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-Gap-r17 OPTIONAL, — Need N

musim-AperiodicGap-r17 MUSIM-GapInfo-r17 OPTIONAL, — Need N

…

}

MUSIM-Gap-r17 ::= SEQUENCE {

musim-GapId-r17 MUSIM-GapId-r17,

musim-GapInfo-r17 MUSIM-GapInfo-r17

}

— TAG-MUSIM-GAPCONFIG-STOP

— ASN1STOP

MUSIM-GapConfig field descriptions
musim-AperiodicGap Indicates the MUSIM aperiodic gap as specified in TS 38.133 [14] clause 9.1.10.
musim-GapInfo Indicates the values for musim-GapLength, musim-GapRepetitionAndOffset, starting-SFN, and startingSubframe. If UE indicates the musim-Starting-SFN-AndSubframe when requesting aperiodic gap the network can only configure the aperiodic gap with the same start point or no aperiodic gap. If the field musim-Starting-SFN-AndSubframe is absent for aperiodic gap, network can configure any timing as the starting point for aperiodic gap or configure no aperiodic gap. When network provides periodic gap, network always signals the musim-GapLength and musim-GapRepetitionAndOffset as indicated by the UE’s preferred MUSIM gap configuration.
musim-GapToAddModList List of MUSIM periodic gap patterns to add or modify.
musim-GapToReleaseList List of MUSIM periodic gap patterns to release.

– MUSIM-GapId

The IE MUSIM-GapId is used to identify UE periodic MUSIM gap(s) to add, modify or release.

MUSIM-GapId information element

— ASN1START

— TAG-MUSIM-GAPID-START

MUSIM-GapId-r17 ::= INTEGER (0..2)

— TAG-MUSIM-GAPID-STOP

— ASN1STOP

– MUSIM-GapInfo

The IE MUSIM-GapInfo is used to indicate MUSIM gap parameters.

MUSIM-GapInfo information element

— ASN1START

— TAG-MUSIM-GAPINFO-START

MUSIM-GapInfo-r17 ::= SEQUENCE {

musim-Starting-SFN-AndSubframe-r17 MUSIM-Starting-SFN-AndSubframe-r17 OPTIONAL, — Cond aperiodic

musim-GapLength-r17 ENUMERATED {ms3, ms4, ms6, ms10, ms20} OPTIONAL, — Cond gapSetup

musim-GapRepetitionAndOffset-r17 CHOICE {

ms20-r17 INTEGER (0..19),

ms40-r17 INTEGER (0..39),

ms80-r17 INTEGER (0..79),

ms160-r17 INTEGER (0..159),

ms320-r17 INTEGER (0..319),

ms640-r17 INTEGER (0..639),

ms1280-r17 INTEGER (0..1279),

ms2560-r17 INTEGER (0..2559),

ms5120-r17 INTEGER (0..5119),

…

} OPTIONAL — Cond periodic

}

MUSIM-Starting-SFN-AndSubframe-r17 ::= SEQUENCE {

starting-SFN-r17 INTEGER (0..1023),

startingSubframe-r17 INTEGER (0..9)

}

— TAG-MUSIM-GAPINFO-STOP

— ASN1STOP

MUSIM-GapInfo field descriptions
musim-GapLength Indicates the length of the UE’s MUSIM gap as specified in TS 38.133 [14] clause 9.1.10. This field is mandatory present for both periodic gap and aperiodic gap preference indication.
musim-GapRepetitionAndOffset Indicates the gap repetition period in ms and gap offset in number of subframes for the periodic MUSIM gap as specified in TS 38.133 [14] clause 9.1.10. This field is mandatory present for the periodic MUSIM gap indication.
musim-Starting-SFN-AndSubframe Indicates gap starting position for the aperiodic MUSIM gap. This field is optionally present for the aperiodic MUSIM gap indication.
starting-SFN Indicates gap starting SFN number for the aperiodic MUSIM gap preference.
startingSubframe Indicates gap starting subframe number for the aperiodic MUSIM gap.

Conditional Presence	Explanation
aperiodic	This field is mandatory present in case of aperiodic MUSIM gap configuration. Otherwise it is absent.
gapSetup	The field is mandatory present upon configuration of a new MUSIM gap. The field is optionally present, Need M, otherwise.
periodic	This field is mandatory present in case of periodic MUSIM gap configuration. Otherwise it is absent.

– NeedForGapsConfigNR

The IE NeedForGapsConfigNR contains configuration related to the reporting of measurement gap requirement information.

NeedForGapsConfigNR information element

— ASN1START

— TAG-NeedForGapsConfigNR-START

NeedForGapsConfigNR-r16 ::= SEQUENCE {

requestedTargetBandFilterNR-r16 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL — Need R

}

— TAG-NeedForGapsConfigNR-STOP

— ASN1STOP

NeedForGapsConfigNR field descriptions

requestedTargetBandFilterNR Indicates the target NR bands that the UE is requested to report the gap requirement information.

– NeedForGapsInfoNR

The IE NeedForGapsInfoNR indicates whether measurement gap is required for the UE to perform SSB based measurements on an NR target band while NR-DC or NE-DC is not configured.

NeedForGapsInfoNR information element

— ASN1START

— TAG-NeedForGapsInfoNR-START

NeedForGapsInfoNR-r16 ::= SEQUENCE {

intraFreq-needForGap-r16 NeedForGapsIntraFreqList-r16,

interFreq-needForGap-r16 NeedForGapsBandListNR-r16

}

NeedForGapsIntraFreqList-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF NeedForGapsIntraFreq-r16

NeedForGapsBandListNR-r16 ::= SEQUENCE (SIZE (1..maxBands)) OF NeedForGapsNR-r16

NeedForGapsIntraFreq-r16 ::= SEQUENCE {

servCellId-r16 ServCellIndex,

gapIndicationIntra-r16 ENUMERATED {gap, no-gap}

}

NeedForGapsNR-r16 ::= SEQUENCE {

bandNR-r16 FreqBandIndicatorNR,

gapIndication-r16 ENUMERATED {gap, no-gap}

}

— TAG-NeedForGapsInfoNR-STOP

— ASN1STOP

NeedForGapsInfoNR field descriptions

intraFreq-needForGap Indicates the measurement gap requirement information for NR intra-frequency measurement.

interFreq-needForGap Indicates the measurement gap requirement information for NR inter-frequency measurement.

NeedForGapsIntraFreq field descriptions

servCellId Indicates the serving cell which contains the target SSB (associated with the initial DL BWP) to be measured.

gapIndicationIntra Indicates whether measurement gap is required for the UE to perform intra-frequency SSB based measurements on the concerned serving cell. Value gap indicates that a measurement gap is needed if any of the UE configured BWPs do not contain the frequency domain resources of the SSB associated to the initial DL BWP. Value no-gap indicates a measurement gap is not needed to measure the SSB associated to the initial DL BWP for all configured BWPs, no matter the SSB is within the configured BWP or not.

NeedForGapsNR field descriptions

bandNR Indicates the NR target band to be measured.

gapIndication Indicates whether measurement gap is required for the UE to perform SSB based measurements on the concerned NR target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the RRCReconfiguration or RRCResume message that triggers this response. Value gap indicates that a measurement gap is needed, value no-gap indicates a measurement gap is not needed.

– NeedForGapNCSG-ConfigEUTRA

The IE NeedForGapNCSG-ConfigEUTRA contains configuration related to the reporting of measurement gap and NCSG requirement information.

NeedForGapNCSG-ConfigEUTRA information element

— ASN1START

— TAG-NeedForGapNCSG-ConfigEUTRA-START

NeedForGapNCSG-ConfigEUTRA-r17 ::= SEQUENCE {

requestedTargetBandFilterNCSG-EUTRA-r17 SEQUENCE (SIZE (1..maxBandsEUTRA)) OF FreqBandIndicatorEUTRA OPTIONAL — Need R

}

— TAG-NeedForGapNCSG-ConfigEUTRA-STOP

— ASN1STOP

NeedForGapNCSG-ConfigEUTRA field descriptions

requestedTargetBandFilterNCSG-EUTRA Indicates the target E-UTRA bands that the UE is requested to report the measurement gap and NCSG requirement information.

– NeedForGapNCSG-ConfigNR

The IE NeedForGapNCSG-ConfigNR contains configuration related to the reporting of measurement gap and NCSG requirement information.

NeedForGapNCSG-ConfigNR information element

— ASN1START

— TAG-NEEDFORGAPNCSG-CONFIGNR-START

NeedForGapNCSG-ConfigNR-r17 ::= SEQUENCE {

requestedTargetBandFilterNCSG-NR-r17 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL — Need R

}

— TAG-NEEDFORGAPNCSG-CONFIGNR-STOP

— ASN1STOP

NeedForGapNCSG-ConfigNR field descriptions

requestedTargetBandFilterNCSG-NR Indicates the target NR bands that the UE is requested to report the measurement gap and NCSG requirement information.

– NeedForGapNCSG-InfoEUTRA

The IE NeedForGapNCSG-InfoEUTRA indicates whether measurement gap or NCSG is required for the UE to perform measurements on an E‑UTRA target band while NR-DC or NE-DC is not configured.

NeedForGapNCSG-InfoEUTRA information element

— ASN1START

— TAG-NEEDFORGAPNCSG-INFOEUTRA-START

NeedForGapNCSG-InfoEUTRA-r17 ::= SEQUENCE {

needForNCSG-EUTRA-r17 SEQUENCE (SIZE (1..maxBandsEUTRA)) OF NeedForNCSG-EUTRA-r17

}

NeedForNCSG-EUTRA-r17 ::= SEQUENCE {

bandEUTRA-r17 FreqBandIndicatorEUTRA,

gapIndication-r17 ENUMERATED {gap, ncsg, nogap-noncsg}

}

— TAG-NEEDFORGAPNCSG-INFOEUTRA-STOP

— ASN1STOP

NeedForGapNCSG-InfoEUTRA field descriptions

needForNCSG-EUTRA Indicates the measurement gap and NCSG requirement information for E-UTRA measurement.

NeedForNCSG-EUTRA field descriptions

bandEUTRA Indicates the E‑UTRA target band to be measured.

gapIndication Indicates whether measurement gap or NCSG is required for the UE to perform measurements on the concerned E‑UTRA target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the RRCReconfiguration message or RRCResume message that triggers this response. Value gap indicates that a measurement gap is needed, value ncsg indicates that NCSG is needed, value nogap-noncsg indicates neither a measurement gap nor a NCSG is needed.

– NeedForGapNCSG-InfoNR

The IE NeedForGapNCSG-InfoNR indicates whether measurement gap or NCSG is required for the UE to perform SSB based measurements on an NR target band while NR-DC or NE-DC is not configured.

NeedForGapNCSG-InfoNR information element

— ASN1START

— TAG-NEEDFORGAPNCSG-INFONR-START

NeedForGapNCSG-InfoNR-r17 ::= SEQUENCE {

intraFreq-needForNCSG-r17 NeedForNCSG-IntraFreqList-r17,

interFreq-needForNCSG-r17 NeedForNCSG-BandListNR-r17

}

NeedForNCSG-IntraFreqList-r17 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF NeedForNCSG-IntraFreq-r17

NeedForNCSG-BandListNR-r17 ::= SEQUENCE (SIZE (1..maxBands)) OF NeedForNCSG-NR-r17

NeedForNCSG-IntraFreq-r17 ::= SEQUENCE {

servCellId-r17 ServCellIndex,

gapIndicationIntra-r17 ENUMERATED {gap, ncsg, nogap-noncsg}

}

NeedForNCSG-NR-r17 ::= SEQUENCE {

bandNR-r17 FreqBandIndicatorNR,

gapIndication-r17 ENUMERATED {gap, ncsg, nogap-noncsg}

}

— TAG-NEEDFORGAPNCSG-INFONR-STOP

— ASN1STOP

NeedForGapNCSG-InfoNR field descriptions

intraFreq-needForNCSG Indicates the measurement gap and NCSG requirement information for NR intra-frequency measurement.

interFreq-needForNCSG Indicates the measurement gap and NCSG requirement information for NR inter-frequency measurement.

NeedForNCSG-IntraFreq field descriptions

servCellId Indicates the serving cell which contains the target SSB (associated with the initial DL BWP) to be measured.

gapIndicationIntra Indicates whether measurement gap or NCSG is required for the UE to perform intra-frequency SSB based measurements on the concerned serving cell. Value gap indicates that a measurement gap is needed if any of the UE configured BWPs do not contain the frequency domain resources of the SSB associated to the initial DL BWP. Value ncsg indicates that a NCSG is needed if any of the UE configured BWPs do not contain the frequency domain resources of the SSB associated to the initial DL BWP. Value nogap-noncsg indicates that neither a measurement gap nor a NCSG is needed to measure the SSB associated to the initial DL BWP for all configured BWPs, no matter the SSB is within the configured BWP or not.

NeedForNCSG-NR field descriptions

bandNR Indicates the NR target band to be measured.

gapIndication Indicates whether measurement gap or NCSG is required for the UE to perform SSB based measurements on the concerned NR target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the RRCReconfiguration or RRCResume message that triggers this response. Value gap indicates that a measurement gap is needed, value ncsg indicates that a NCSG is needed, and value nogap-noncsg indicates neither a measurement gap nor a NCSG is needed.

– NextHopChainingCount

The IE NextHopChainingCount is used to update the K_gNB key and corresponds to parameter NCC: See TS 33.501 [11].

NextHopChainingCount information element

— ASN1START

— TAG-NEXTHOPCHAININGCOUNT-START

NextHopChainingCount ::= INTEGER (0..7)

— TAG-NEXTHOPCHAININGCOUNT-STOP

— ASN1STOP

– NG-5G-S-TMSI

The IE NG-5G-S-TMSI contains a 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI), a temporary UE identity provided by the 5GC which uniquely identifies the UE within the tracking area, see TS 23.003 [21].

NG-5G-S-TMSI information element

— ASN1START

— TAG-NG-5G-S-TMSI-START

NG-5G-S-TMSI ::= BIT STRING (SIZE (48))

— TAG-NG-5G-S-TMSI-STOP

— ASN1STOP

– NonCellDefiningSSB

The IE NonCellDefiningSSB is used to configure a non-cell-defining SSB to be used while the UE operates in a RedCap-specific initial BWP or dedicated BWP.

NonCellDefiningSSB information element

— ASN1START

— TAG-NONCELLDEFININGSSB-START

NonCellDefiningSSB-r17 ::= SEQUENCE {

absoluteFrequencySSB-r17 ARFCN-ValueNR,

ssb-Periodicity-r17 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 } OPTIONAL, — Need S

ssb-TimeOffset-r17 ENUMERATED { ms5, ms10, ms15, ms20, ms40, ms80, spare2, spare1 } OPTIONAL, — Need S

…

}

— TAG-NONCELLDEFININGSSB-STOP

— ASN1STOP

NonCellDefiningSSB field descriptions

absoluteFrequencySSB Frequency of the non-cell-defining SSB. The network configures this field so that the SSB is within the bandwidth of the BWP configured in BWP-DownlinkCommon.

ssb-Periodicity The periodicity of this Non-Cell-Defining SSB. The network configures only periodicities that are larger than the periodicity of serving cell’s CD-SSB. If the field is absent, the UE applies the SSB periodicity of the cell-defining SSB (ssb-periodicityServingCell configured in ServingCellConfigCommon).

ssb-TimeOffset The time offset between CD-SSB of the serving cell and this Non-Cell Defining SSB. Value ms5 means the first burst of Non-Cell Defining SSB is transmitted 5ms later than the first burst of CD-SSB transmitted after the first symbol of SFN=0 of the serving cell, value ms10 means the first burst of Non-Cell Defining SSB is transmitted 10ms later than the first burst of CD-SSB transmitted after the first symbol in SFN=0 of the serving cell, and so on. If the field is absent, RedCap UE considers that the time offset between the first burst of CD-SSB transmitted in the serving cell and the first burst of this Non-Cell Defining SSB transmitted is zero.

– NPN-Identity

The IE NPN-Identity includes either a list of CAG-IDs or a list of NIDs per PLMN Identity. Further information regarding how to set the IE is specified in TS 23.003 [21].

NPN-Identity information element

— ASN1START

— TAG-NPN-IDENTITY-START

NPN-Identity-r16 ::= CHOICE {

pni-npn-r16 SEQUENCE {

plmn-Identity-r16 PLMN-Identity,

cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16

},

snpn-r16 SEQUENCE {

plmn-Identity-r16 PLMN-Identity,

nid-List-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16

}

}

CAG-IdentityInfo-r16 ::= SEQUENCE {

cag-Identity-r16 BIT STRING (SIZE (32)),

manualCAGselectionAllowed-r16 ENUMERATED {true} OPTIONAL — Need R

}

NID-r16 ::= BIT STRING (SIZE (44))

— TAG-NPN-IDENTITY-STOP

— ASN1STOP

NPN-Identity field descriptions

cag-Identity A CAG-ID as specified in TS 23.003 [21]. The PLMN ID and a CAG ID in the NPN-Identity identifies a PNI-NPN.

cag-IdentityList The cag-IdentityList contains one or more CAG IDs. All CAG IDs associated to the same PLMN ID are listed in the same cag-IdentityList entry.

manualCAGselectionAllowed The manualCAGselectionAllowed indicates that the CAG ID can be selected manually even if it is outside the UE’s allowed CAG list.

NID A NID as specified in TS 23.003 [21]. The PLMN ID and a NID in the NPN-Identity identifies a SNPN.

nid-List The nid-List contains one or more NID.

– NPN-IdentityInfoList

The IE NPN-IdentityInfoList includes a list of NPN identity information.

NPN-IdentityInfoList information element

— ASN1START

— TAG-NPN-IDENTITYINFOLIST-START

NPN-IdentityInfoList-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-IdentityInfo-r16

NPN-IdentityInfo-r16 ::= SEQUENCE {

npn-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-Identity-r16,

trackingAreaCode-r16 TrackingAreaCode,

ranac-r16 RAN-AreaCode OPTIONAL, — Need R

cellIdentity-r16 CellIdentity,

cellReservedForOperatorUse-r16 ENUMERATED {reserved, notReserved},

iab-Support-r16 ENUMERATED {true} OPTIONAL, — Need S

…,

[[

gNB-ID-Length-r17 INTEGER (22..32) OPTIONAL — Need R

]]

}

— TAG-NPN-IDENTITYINFOLIST-STOP

— ASN1STOP

NPN-IdentityInfoList field descriptions

iab-Support This field combines both the support of IAB and the cell status for IAB. If the field is present, the cell supports IAB and the cell is also considered as a candidate for cell (re)selection for IAB-nodes; if the field is absent, the cell does not support IAB and/or the cell is barred for IAB-node.

gNB-ID-Length Indicates the length of the gNB ID out of the 36-bit long cellIdentity.

NPN-IdentityInfo The NPN-IdentityInfo contains one or more NPN identities and additional information associated with those NPNs. Only the same type of NPNs (either SNPNs or PNI-NPNs) can be listed in a NPN-IdentityInfo element.

npn-IdentityList The npn-IdentityList contains one or more NPN Identity elements.

trackingAreaCode Indicates the Tracking Area Code to which the cell indicated by cellIdentity field belongs.

ranac Indicates the RAN Area Code to which the cell indicated by cellIdentity field belongs.

cellReservedForOperatorUse Indicates whether the cell is reserved for operator use (for the NPN(s) identified in the npn-IdentityList) as defined in TS 38.304 [20]. This field is ignored by NPN capable IAB-MT.

– NR-DL-PRS-PDC-Info

The IE NR-DL-PRS-PDC-Info defines downlink PRS configuration for PDC.

NR-DL-PRS-PDC-Info information element

— ASN1START

— TAG-NR-DL-PRS-PDC-INFO-START

NR-DL-PRS-PDC-Info-r17 ::= SEQUENCE {

nr-DL-PRS-PDC-ResourceSet-r17 NR-DL-PRS-PDC-ResourceSet-r17 OPTIONAL, — Need R

…

}

NR-DL-PRS-PDC-ResourceSet-r17 ::= SEQUENCE {

periodicityAndOffset-r17 NR-DL-PRS-Periodicity-and-ResourceSetSlotOffset-r17,

numSymbols-r17 ENUMERATED {n2, n4, n6, n12, spare4, spare3, spare2, spare1},

dl-PRS-ResourceBandwidth-r17 INTEGER (1..63),

dl-PRS-StartPRB-r17 INTEGER (0..2176),

resourceList-r17 SEQUENCE (SIZE (1..maxNrofPRS-ResourcesPerSet-r17)) OF NR-DL-PRS-Resource-r17,

repFactorAndTimeGap-r17 RepFactorAndTimeGap-r17 OPTIONAL, — Need S

…

}

NR-DL-PRS-Periodicity-and-ResourceSetSlotOffset-r17 ::= CHOICE {

scs15-r17 CHOICE {

n4-r17 INTEGER (0..3),

n5-r17 INTEGER (0..4),

n8-r17 INTEGER (0..7),

n10-r17 INTEGER (0..9),

n16-r17 INTEGER (0..15),

n20-r17 INTEGER (0..19),

n32-r17 INTEGER (0..31),

n40-r17 INTEGER (0..39),

n64-r17 INTEGER (0..63),

n80-r17 INTEGER (0..79),

n160-r17 INTEGER (0..159),

n320-r17 INTEGER (0..319),

n640-r17 INTEGER (0..639),

n1280-r17 INTEGER (0..1279),

n2560-r17 INTEGER (0..2559),

n5120-r17 INTEGER (0..5119),

n10240-r17 INTEGER (0..10239),

…

},

scs30-r17 CHOICE {

n8-r17 INTEGER (0..7),

n10-r17 INTEGER (0..9),

n16-r17 INTEGER (0..15),

n20-r17 INTEGER (0..19),

n32-r17 INTEGER (0..31),

n40-r17 INTEGER (0..39),

n64-r17 INTEGER (0..63),

n80-r17 INTEGER (0..79),

n128-r17 INTEGER (0..127),

n160-r17 INTEGER (0..159),

n320-r17 INTEGER (0..319),

n640-r17 INTEGER (0..639),

n1280-r17 INTEGER (0..1279),

n2560-r17 INTEGER (0..2559),

n5120-r17 INTEGER (0..5119),

n10240-r17 INTEGER (0..10239),

n20480-r17 INTEGER (0..20479),

…

},

scs60-r17 CHOICE {

n16-r17 INTEGER (0..15),

n20-r17 INTEGER (0..19),

n32-r17 INTEGER (0..31),

n40-r17 INTEGER (0..39),

n64-r17 INTEGER (0..63),

n80-r17 INTEGER (0..79),

n128-r17 INTEGER (0..127),

n160-r17 INTEGER (0..159),

n256-r17 INTEGER (0..255),

n320-r17 INTEGER (0..319),

n640-r17 INTEGER (0..639),

n1280-r17 INTEGER (0..1279),

n2560-r17 INTEGER (0..2559),

n5120-r17 INTEGER (0..5119),

n10240-r17 INTEGER (0..10239),

n20480-r17 INTEGER (0..20479),

n40960-r17 INTEGER (0..40959),

…

},

scs120-r17 CHOICE {

n32-r17 INTEGER (0..31),

n40-r17 INTEGER (0..39),

n64-r17 INTEGER (0..63),

n80-r17 INTEGER (0..79),

n128-r17 INTEGER (0..127),

n160-r17 INTEGER (0..159),

n256-r17 INTEGER (0..255),

n320-r17 INTEGER (0..319),

n512-r17 INTEGER (0..511),

n640-r17 INTEGER (0..639),

n1280-r17 INTEGER (0..1279),

n2560-r17 INTEGER (0..2559),

n5120-r17 INTEGER (0..5119),

n10240-r17 INTEGER (0..10239),

n20480-r17 INTEGER (0..20479),

n40960-r17 INTEGER (0..40959),

n81920-r17 INTEGER (0..81919),

…

},

…

}

NR-DL-PRS-Resource-r17 ::= SEQUENCE {

nr-DL-PRS-ResourceID-r17 NR-DL-PRS-ResourceID-r17,

dl-PRS-SequenceID-r17 INTEGER (0..4095),

dl-PRS-CombSizeN-AndReOffset-r17 CHOICE {

n2-r17 INTEGER (0..1),

n4-r17 INTEGER (0..3),

n6-r17 INTEGER (0..5),

n12-r17 INTEGER (0..11),

…

},

dl-PRS-ResourceSlotOffset-r17 INTEGER (0..maxNrofPRS-ResourceOffsetValue-1-r17),

dl-PRS-ResourceSymbolOffset-r17 INTEGER (0..12),

dl-PRS-QCL-Info-r17 DL-PRS-QCL-Info-r17 OPTIONAL, — Need N

…

}

DL-PRS-QCL-Info-r17 ::= CHOICE {

ssb-r17 SEQUENCE {

ssb-Index-r17 INTEGER (0..63),

rs-Type-r17 ENUMERATED {typeC, typeD, typeC-plus-typeD},

…

},

dl-PRS-r17 SEQUENCE {

qcl-DL-PRS-ResourceID-r17 NR-DL-PRS-ResourceID-r17,

…

},

…

}

NR-DL-PRS-ResourceID-r17 ::= INTEGER (0..maxNrofPRS-ResourcesPerSet-1-r17)

RepFactorAndTimeGap-r17 ::= SEQUENCE {

repetitionFactor-r17 ENUMERATED {n2, n4, n6, n8, n16, n32, spare2, spare1},

timeGap-r17 ENUMERATED {s1, s2, s4, s8, s16, s32, spare2, spare1}

}

— TAG-NR-DL-PRS-PDC-INFO-STOP

— ASN1STOP

NR-DL-PRS-PDC-ResourceSet field descriptions

dl-PRS-ResourceBandwidth This field specifies the number of PRBs allocated for all the DL-PRS Resource (allocated DL-PRS bandwidth) in multiples of 4 PRBs in this resource set. All DL-PRS Resources of the DL-PRS-PDC Resource Set have the same bandwidth. Integer value 1 corresponds to 24 PRBs, value 2 corresponds to 28 PRBs, value 3 corresponds to 32 PRBs and so on.

dl-PRS-StartPRB This field specifies the start PRB index defined as offset with respect to subcarrier 0 in common resource block 0 for the DL-PRS Resource. All DL-PRS Resources of the DL-PRS-PDC Resource Set have the same value of dl-PRS-StartPRB.

numSymbols This field specifies the number of symbols per DL-PRS Resource within a slot.

periodicityAndOffset This field specifies the periodicity of DL-PRS allocation in slots and the slot offset with respect to SFN #0 slot #0 in the PCell where the DL-PRS-PDC Resource Set is configured (i.e., slot where the first DL-PRS Resource of DL-PRS-PDC Resource Set occurs).

repFactorAndTimeGap If this field is absent, the value for repetitionFactor is 1 (i.e., no resource repetition).

RepFactorAndTimeGap field descriptions

repetitionFactor This field specifies how many times each DL-PRS Resource is repeated for a single instance of the DL-PRS Resource Set. It is applied to all resources of the DL-PRS Resource Set. Enumerated values n2, n4, n6, n8, n16, n32 correspond to 2, 4, 6, 8, 16, 32 resource repetitions, respectively.

timeGap This field specifies the offset in units of slots between two repeated instances of a DL-PRS Resource corresponding to the same DL-PRS Resource ID within a single instance of the DL-PRS Resource Set. The time duration spanned by one DL-PRS Resource Set containing repeated DL-PRS Resources should not exceed the periodicity configured by periodicityAndOffset.

– NR-NS-PmaxList

The IE NR-NS-PmaxList is used to configure a list of additionalPmax and additionalSpectrumEmission, as defined in TS 38.101-1 [15], table 6.2.3.1-1A, and TS 38.101-2 [39], table 6.2.3.1-2, for a given frequency band.

NR-NS-PmaxList information element

— ASN1START

— TAG-NR-NS-PMAXLIST-START

NR-NS-PmaxList ::= SEQUENCE (SIZE (1..maxNR-NS-Pmax)) OF NR-NS-PmaxValue

NR-NS-PmaxValue ::= SEQUENCE {

additionalPmax P-Max OPTIONAL, — Need N

additionalSpectrumEmission AdditionalSpectrumEmission

}

— TAG-NR-NS-PMAXLIST-STOP

— ASN1STOP

– NSAG-ID

The IE NSAG-ID is used to identify an NSAG (TS 23.501 [32]) for slice-based cell reselection or slice-based random access.

NSAG-ID information element

— ASN1START

— TAG-NSAG-ID-START

NSAG-ID-r17 ::= BIT STRING (SIZE (8))

— TAG-NSAG-ID-STOP

— ASN1STOP

– NSAG-IdentityInfo

The IE NSAG-IdentityInfo is used to identify an NSAG (TS 23.501 [32]) for slice-based cell reselection.

NSAG-IdentityInfo information element

— ASN1START

— TAG-NSAG-IDENTITYINFO-START

NSAG-IdentityInfo-r17 ::= SEQUENCE {

nsag-ID-r17 NSAG-ID-r17,

trackingAreaCode-r17 TrackingAreaCode OPTIONAL — Need R

}

— TAG-NSAG-IDENTITYINFO-STOP

— ASN1STOP

NSAG-IdentityInfo field descriptions
trackingAreaCode If absent, UE assumes the trackingAreaCode of the serving cell.

– NTN-Config

The IE NTN-Config provides parameters needed for the UE to access NR via NTN access.

NTN-Config information element

— ASN1START

— TAG-NTN-CONFIG-START

NTN-Config-r17 ::= SEQUENCE {

epochTime-r17 EpochTime-r17 OPTIONAL, — Need R

ntn-UlSyncValidityDuration-r17 ENUMERATED{ s5, s10, s15, s20, s25, s30, s35,

s40, s45, s50, s55, s60, s120, s180, s240, s900} OPTIONAL, — Cond SIB19

cellSpecificKoffset-r17 INTEGER(1..1023) OPTIONAL, — Need R

kmac-r17 INTEGER(1..512) OPTIONAL, — Need R

ta-Info-r17 TA-Info-r17 OPTIONAL, — Need R

ntn-PolarizationDL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL, — Need R

ntn-PolarizationUL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL, — Need R

ephemerisInfo-r17 EphemerisInfo-r17 OPTIONAL, — Need R

ta-Report-r17 ENUMERATED {enabled} OPTIONAL, — Need R

…

}

EpochTime-r17 ::= SEQUENCE {

sfn-r17 INTEGER(0..1023),

subFrameNR-r17 INTEGER(0..9)

}

TA-Info-r17 ::= SEQUENCE {

ta-Common-r17 INTEGER(0..66485757),

ta-CommonDrift-r17 INTEGER(-257303..257303) OPTIONAL, — Need R

ta-CommonDriftVariant-r17 INTEGER(0..28949) OPTIONAL — Need R

}

— TAG-NTN-CONFIG-STOP

— ASN1STOP

NTN-Config field descriptions

EphemerisInfo This field provides satellite ephemeris either in format of position and velocity state vector or in format of orbital parameters. This field is excluded when determining changes in system information, i.e. changes to ephemerisInfo should neither result in system information change notifications nor in a modification of valueTag in SIB1.

epochTime Indicate the epoch time for the NTN assistance information. When explicitly provided through SIB, or through dedicated signaling, EpochTime is the starting time of a DL sub-frame, indicated by a SFN and a sub-frame number signaled together with the assistance information. The reference point for epoch time of the serving satellite ephemeris and Common TA parameters is the uplink time synchronization reference point. If this field is absent, the epoch time is the end of SI window where this SIB19 is scheduled. This field is mandatory present when provided in dedicated configuration. If this field is absent in ntn-Config provided via NTN-NeighCellConfig the UE uses epoch time from the serving satellite ephemeris, otherwise the field is based on the timing of the serving cell, i.e. the SFN and sub-frame number indicated in this field refers to the SFN and sub-frame of the serving cell. In case of handover, this field is based on the timing of the target cell, i.e. the SFN and sub-frame number indicated in this field refers to the SFN and sub-frame of the target cell. This field is excluded when determining changes in system information, i.e. changes to epochTime should neither result in system information change notifications nor in a modification of valueTag in SIB1.

cellSpecificKoffset Scheduling offset used for the timing relationships that are modified for NTN [see TS 38.211]. The unit of the field K_offset is number of slots for a given subcarrier spacing of 15 kHz. If the field is absent UE assumes value 0.

kmac Scheduling offset provided by network if downlink and uplink frame timing are not aligned at gNB. It is needed for UE action and assumption on downlink configuration indicated by a MAC CE command in PDSCH [see TS 38.2xy]. If the field is absent UE assumes value 0. For the reference subcarrier spacing value for the unit of K_mac in FR1, a value of 15 kHz is used. The unit of K_mac is number of slots for a given subcarrier spacing.

ntn-PolarizationDL If present, this parameter indicates polarization information for downlink transmission on service link: including Right hand, Left hand circular polarizations (RHCP, LHCP) and Linear polarization.

ntn-PolarizationUL If present, this parameter indicates Polarization information for Uplink service link. If not present and ntn-PolarizationDL is present, UE assumes the same polarization for UL and DL.

ntn-UlSyncValidityDuration A validity duration configured by the network for assistance information (i.e. Serving and/or neighbour satellite ephemeris and Common TA parameters) which indicates the maximum time during which the UE can apply assistance information without having acquired new assistance information. The unit of ntn-UlSyncValidityDuration is second. Value s5 corresponds to 5 s, value s10 indicate 10 s and so on. This parameter applies to both connected and idle mode UEs. If this field is absent in ntn-Config provided via NTN-NeighCellConfig, the UE uses validity duration from the serving cell assistance information. This field is excluded when determining changes in system information, i.e. changes of ntn-UlSyncValidityDuration should neither result in system information change notifications nor in a modification of valueTag in SIB1. ntn-UlSyncValidityDuration is only updated when at least one of epochTime, ta-Info, ephemerisInfo is updated.

ta-Common Network-controlled common timing advanced value and it may include any timing offset considered necessary by the network. ta-Common with value of 0 is supported. The granularity of ta-Common is 4.072 × 10^(-3) μs. Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-Common should neither result in system information change notifications nor in a modification of valueTag in SIB1.

ta-CommonDrift Indicate drift rate of the common TA. The granularity of ta-CommonDrift is 0.2 × 10^(-3) μs⁄s Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-CommonDrift should neither result in system information change notifications nor in a modification of valueTag in SIB1.

ta-CommonDriftVariant Indicate drift rate variation of the common TA. The granularity of ta-CommonDriftVariation is 0.2×10^(-4) μs⁄s^2. Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-CommonDriftVariant should neither result in system information change notifications nor in a modification of valueTag in SIB1.

ta-Report When this field is included in SIB19, it indicates reporting of timing advanced is enabled during Random Access due to RRC connection establishment or RRC connection resume, and during RRC connection reestablishment.. When this field is included in ServingCellConfigCommon within dedicated signalling, it indicates TA reporting is enabled during Random Access due to reconfiguration with sync (see TS 38.321 [3], clause 5.4.8).

Conditional Presence	Explanation
SIB19	The field is mandatory present for the serving cell in SIB19. The field is optionally present, Need R, otherwise.

– NZP-CSI-RS-Resource

The IE NZP-CSI-RS-Resource is used to configure Non-Zero-Power (NZP) CSI-RS transmitted in the cell where the IE is included, which the UE may be configured to measure on (see TS 38.214 [19], clause 5.2.2.3.1). A change of configuration between periodic, semi-persistent or aperiodic for an NZP-CSI-RS-Resource is not supported without a release and add.

NZP-CSI-RS-Resource information element

— ASN1START

— TAG-NZP-CSI-RS-RESOURCE-START

NZP-CSI-RS-Resource ::= SEQUENCE {

nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId,

resourceMapping CSI-RS-ResourceMapping,

powerControlOffset INTEGER (-8..15),

powerControlOffsetSS ENUMERATED{db-3, db0, db3, db6} OPTIONAL, — Need R

scramblingID ScramblingId,

periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, — Cond PeriodicOrSemiPersistent

qcl-InfoPeriodicCSI-RS TCI-StateId OPTIONAL, — Cond Periodic

…

}

— TAG-NZP-CSI-RS-RESOURCE-STOP

— ASN1STOP

NZP-CSI-RS-Resource field descriptions

periodicityAndOffset Periodicity and slot offset sl1 corresponds to a periodicity of 1 slot, sl2 to a periodicity of two slots, and so on. The corresponding offset is also given in number of slots (see TS 38.214 [19], clause 5.2.2.3.1). Network always configures the UE with a value for this field for periodic and semi-persistent NZP-CSI-RS-Resource (as indicated in CSI-ResourceConfig).

powerControlOffset Power offset of PDSCH RE to NZP CSI-RS RE. Value in dB (see TS 38.214 [19], clauses 5.2.2.3.1 and 4.1).

powerControlOffsetSS Power offset of NZP CSI-RS RE to SSS RE. Value in dB (see TS 38.214 [19], clause 5.2.2.3.1).

qcl-InfoPeriodicCSI-RS For a target periodic CSI-RS, contains a reference to one TCI-State in TCI-States for providing the QCL source and QCL type. For periodic CSI-RS, the source can be SSB or another periodic-CSI-RS. Refers to the TCI-State or DLorJoint-TCIState which has this value for tci-StateId and is defined in tci-StatesToAddModList or in dl-OrJoint-TCI-State-ToAddModList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resource belongs to (see TS 38.214 [19], clause 5.2.2.3.1).

resourceMapping OFDM symbol location(s) in a slot and subcarrier occupancy in a PRB of the CSI-RS resource.

scramblingID Scrambling ID (see TS 38.214 [19], clause 5.2.2.3.1).

Conditional Presence	Explanation
Periodic	The field is optionally present, Need M, for periodic NZP-CSI-RS-Resources (as indicated in CSI-ResourceConfig). The field is absent otherwise.
PeriodicOrSemiPersistent	The field is optionally present, Need M, for periodic and semi-persistent NZP-CSI-RS-Resources (as indicated in CSI-ResourceConfig). The field is absent otherwise.

– NZP-CSI-RS-ResourceId

The IE NZP-CSI-RS-ResourceId is used to identify one NZP-CSI-RS-Resource.

NZP-CSI-RS-ResourceId information element

— ASN1START

— TAG-NZP-CSI-RS-RESOURCEID-START

NZP-CSI-RS-ResourceId ::= INTEGER (0..maxNrofNZP-CSI-RS-Resources-1)

— TAG-NZP-CSI-RS-RESOURCEID-STOP

— ASN1STOP

– NZP-CSI-RS-ResourceSet

The IE NZP-CSI-RS-ResourceSet is a set of Non-Zero-Power (NZP) CSI-RS resources (their IDs) and set-specific parameters.

NZP-CSI-RS-ResourceSet information element

— ASN1START

— TAG-NZP-CSI-RS-RESOURCESET-START

NZP-CSI-RS-ResourceSet ::= SEQUENCE {

nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId,

nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId,

repetition ENUMERATED { on, off } OPTIONAL, — Need S

aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, — Need S

trs-Info ENUMERATED {true} OPTIONAL, — Need R

…,

[[

aperiodicTriggeringOffset-r16 INTEGER(0..31) OPTIONAL — Need S

]],

[[

pdc-Info-r17 ENUMERATED {true} OPTIONAL, — Need R

cmrGroupingAndPairing-r17 CMRGroupingAndPairing-r17 OPTIONAL, — Need R

aperiodicTriggeringOffset-r17 INTEGER (0..124) OPTIONAL, — Need S

aperiodicTriggeringOffsetL2-r17 INTEGER(0..31) OPTIONAL — Need R

]]

}

CMRGroupingAndPairing-r17 ::= SEQUENCE {

nrofResourcesGroup1-r17 INTEGER (1..7),

pair1OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL, — Need R

pair2OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL — Need R

}

NZP-CSI-RS-Pairing-r17 ::= SEQUENCE {

nzp-CSI-RS-ResourceId1-r17 INTEGER (1..7),

nzp-CSI-RS-ResourceId2-r17 INTEGER (1..7)

}

— TAG-NZP-CSI-RS-RESOURCESET-STOP

— ASN1STOP

NZP-CSI-RS-ResourceSet field descriptions

aperiodicTriggeringOffset, aperiodicTriggeringOffset-r16, aperiodicTriggeringOffset-r17 Offset X between the slot containing the DCI that triggers a set of aperiodic NZP CSI-RS resources and the slot in which the CSI-RS resource set is transmitted. For aperiodicTriggeringOffset, the value 0 corresponds to 0 slots, value 1 corresponds to 1 slot, value 2 corresponds to 2 slots, value 3 corresponds to 3 slots, value 4 corresponds to 4 slots, value 5 corresponds to 16 slots, value 6 corresponds to 24 slots. For aperiodicTriggeringOffset-r16 and aperiodicTriggeringOffset-r17, the value indicates the number of slots. aperiodicTriggeringOffset-r17 is applicable to SCS 480 kHz and 960 kHz, and only the values of integer multiples of 4 are valid, i.e. 0, 4, 8, and so on. The network configures only one of the fields. When neither field is included, the UE applies the value 0.

aperiodicTriggeringOffsetL2 Indicates triggering offset of aperiodic NZP CSI-RS resources used for fast activation of the SCell (see clause 5.2.1.5.3 of TS 38.214 [19]), when the NZP CSI-RS resources are activated by the MAC CE (see clause 5.9 of TS 38.321 [3]). The value indicates the number of slots.

cmrGroupingAndPairing Configures CMR groups and pairs. The first nrofResourcesGroup1 resources in the NZP-CSI-RS resource set belong to Group 1 and the remaining resources in the NZP-CSI-RS resource set belong to Group 2. nrofResourcesGroup1 is and the number of remaining resources in the NZP-CSI-RS resource set belonging to Group 2 is as specified in TS 38.214 clause 5.2.1.4.1. Maximum total number in Group 1 and Group 2 is 8 (see TS 38.214 [19], clauses 5.2.1.4.1 and 5.2.1.4.2).

pair1OfNZP-CSI-RS, pair2OfNZP-CSI-RS A pair of NZP CSI-RS resources. In one pair, one resource shall belong to group 1 and the other resource shall belong to group 2 as configured by nrofResourcesGroup1 and nrofResourcesGroup2. (see TS 38.214 [19], clause xx).

nzp-CSI-RS-Resources NZP-CSI-RS-Resources associated with this NZP-CSI-RS resource set (see TS 38.214 [19], clause 5.2). For CSI, there are at most 8 NZP CSI RS resources per resource set.

nzp-CSI-RS-ResourceId1, nzp-CSI-RS-ResourceId2 The nzp-CSI-RS-ResourceId1-r17 represents the index of the NZP CSI-RS resource in Resource Group 1, and nzp-CSI-RS-ResourceId2-r17 represents the index of the NZP CSI-RS resource in Resource Group 2.

pdc-Info Indicates that this NZP-CSI-RS-ResourceSet, if configured also with trs-Info, is used for propagation delay compensation. The field can be present only if trs-info is present. The field can be present in only one NZP-CSI-RS-ResourceSet. If network configures this field for an NZP-CSI-RS-ResourceSet, the UE measures the UE Rx-Tx time difference based on resources configured in this resource set.

repetition Indicates whether repetition is on/off. If the field is set to off or if the field is absent, the UE may not assume that the NZP-CSI-RS resources within the resource set are transmitted with the same downlink spatial domain transmission filter (see TS 38.214 [19], clauses 5.2.2.3.1 and 5.1.6.1.2). It can only be configured for CSI-RS resource sets which are associated with CSI-ReportConfig with report of L1 RSRP, L1 SINR or "no report".

trs-Info Indicates that the antenna port for all NZP-CSI-RS resources in the CSI-RS resource set is same. If the field is absent or released the UE applies the value false (see TS 38.214 [19], clause 5.2.2.3.1).

– NZP-CSI-RS-ResourceSetId

The IE NZP-CSI-RS-ResourceSetId is used to identify one NZP-CSI-RS-ResourceSet.

NZP-CSI-RS-ResourceSetId information element

— ASN1START

— TAG-NZP-CSI-RS-RESOURCESETID-START

NZP-CSI-RS-ResourceSetId ::= INTEGER (0..maxNrofNZP-CSI-RS-ResourceSets-1)

— TAG-NZP-CSI-RS-RESOURCESETID-STOP

— ASN1STOP

– P-Max

The IE P-Max is used to limit the UE’s uplink transmission power on a carrier frequency, in TS 38.101-1 [15] and is used to calculate the parameter Pcompensation defined in TS 38.304 [20].

P-Max information element

— ASN1START

— TAG-P-MAX-START

P-Max ::= INTEGER (-30..33)

— TAG-P-MAX-STOP

— ASN1STOP

– PCI-ARFCN-EUTRA

The IE PCI-ARFCN-EUTRA is used to encode EUTRA PCI and ARFCN.

PCI-ARFCN-EUTRA information element

— ASN1START

— TAG-PCIARFCNEUTRA-START

PCI-ARFCN-EUTRA-r16 ::= SEQUENCE {

physCellId-r16 EUTRA-PhysCellId,

carrierFreq-r16 ARFCN-ValueEUTRA

}

— TAG-PCIARFCNEUTRA-STOP

— ASN1STOP

– PCI-ARFCN-NR

The IE PCI-ARFCN-NR is used to encode NR PCI and ARFCN.

PCI-ARFCN-NR information element

— ASN1START

— TAG-PCIARFCNNR-START

PCI-ARFCN-NR-r16 ::= SEQUENCE {

physCellId-r16 PhysCellId,

carrierFreq-r16 ARFCN-ValueNR

}

— TAG-PCIARFCNNR-STOP

— ASN1STOP

– PCI-List

The IE PCI-List concerns a list of physical cell identities, which may be used for different purposes.

PCI-List information element

— ASN1START

— TAG-PCI-LIST-START

PCI-List ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF PhysCellId

— TAG-PCI-LIST-STOP

— ASN1STOP

– PCI-Range

The IE PCI-Range is used to encode either a single or a range of physical cell identities. The range is encoded by using a start value and by indicating the number of consecutive physical cell identities (including start) in the range. For fields comprising multiple occurrences of PCI-Range, the Network may configure overlapping ranges of physical cell identities.

PCI-Range information element

— ASN1START

— TAG-PCI-RANGE-START

PCI-Range ::= SEQUENCE {

start PhysCellId,

range ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n84,

n96, n128, n168, n252, n504, n1008,spare1} OPTIONAL — Need S

}

— TAG-PCI-RANGE-STOP

— ASN1STOP

PCI-Range field descriptions
range Indicates the number of physical cell identities in the range (including start). Value n4 corresponds with 4, value n8 corresponds with 8 and so on. The UE shall apply value 1 in case the field is absent, in which case only the physical cell identity value indicated by start applies.
start Indicates the lowest physical cell identity in the range.

– PCI-RangeElement

The IE PCI-RangeElement is used to define a PCI-Range as part of a list (e.g. AddMod list).

PCI-RangeElement information element

— ASN1START

— TAG-PCI-RANGEELEMENT-START

PCI-RangeElement ::= SEQUENCE {

pci-RangeIndex PCI-RangeIndex,

pci-Range PCI-Range

}

— TAG-PCI-RANGEELEMENT-STOP

— ASN1STOP

PCI-RangeElement field descriptions

pci-Range Physical cell identity or a range of physical cell identities.

– PCI-RangeIndex

The IE PCI-RangeIndex identifies a physical cell id range, which may be used for different purposes.

PCI-RangeIndex information element

— ASN1START

— TAG-PCI-RANGEINDEX-START

PCI-RangeIndex ::= INTEGER (1..maxNrofPCI-Ranges)

— TAG-PCI-RANGEINDEX-STOP

— ASN1STOP

– PCI-RangeIndexList

The IE PCI-RangeIndexList concerns a list of indexes of physical cell id ranges, which may be used for different purposes.

PCI-RangeIndexList information element

— ASN1START

— TAG-PCI-RANGEINDEXLIST-START

PCI-RangeIndexList ::= SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeIndex

— TAG-PCI-RANGEINDEXLIST-STOP

— ASN1STOP

– PDCCH-Config

The IE PDCCH-Config is used to configure UE specific PDCCH parameters or MBS multicast PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. If this IE is used for the scheduled SCell in case of cross carrier scheduling, the fields other than searchSpacesToAddModList and searchSpacesToReleaseList are absent. If the IE is used for a dormant BWP, the fields other than controlResourceSetToAddModList and controlResourceSetToReleaseList are absent. If this IE is used for MBS CFR, the field downlinkPreemptiom,tpc-PUSCH, tpc-SRS, uplinkCancellation, monitoringCapabilityConfig, and searchSpaceSwitchConfig are absent.

PDCCH-Config information element

— ASN1START

— TAG-PDCCH-CONFIG-START

PDCCH-Config ::= SEQUENCE {

controlResourceSetToAddModList SEQUENCE(SIZE (1..3)) OF ControlResourceSet OPTIONAL, — Need N

controlResourceSetToReleaseList SEQUENCE(SIZE (1..3)) OF ControlResourceSetId OPTIONAL, — Need N

searchSpacesToAddModList SEQUENCE(SIZE (1..10)) OF SearchSpace OPTIONAL, — Need N

searchSpacesToReleaseList SEQUENCE(SIZE (1..10)) OF SearchSpaceId OPTIONAL, — Need N

downlinkPreemption SetupRelease { DownlinkPreemption } OPTIONAL, — Need M

tpc-PUSCH SetupRelease { PUSCH-TPC-CommandConfig } OPTIONAL, — Need M

tpc-PUCCH SetupRelease { PUCCH-TPC-CommandConfig } OPTIONAL, — Need M

tpc-SRS SetupRelease { SRS-TPC-CommandConfig} OPTIONAL, — Need M

…,

[[

controlResourceSetToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..2)) OF ControlResourceSet OPTIONAL, — Need N

controlResourceSetToReleaseListSizeExt-r16 SEQUENCE (SIZE (1..5)) OF ControlResourceSetId-r16 OPTIONAL, — Need N

searchSpacesToAddModListExt-r16 SEQUENCE(SIZE (1..10)) OF SearchSpaceExt-r16 OPTIONAL, — Need N

uplinkCancellation-r16 SetupRelease { UplinkCancellation-r16 } OPTIONAL, — Need M

monitoringCapabilityConfig-r16 ENUMERATED { r15monitoringcapability,r16monitoringcapability } OPTIONAL, — Need M

searchSpaceSwitchConfig-r16 SearchSpaceSwitchConfig-r16 OPTIONAL — Need R

]],

[[

searchSpacesToAddModListExt-v1700 SEQUENCE(SIZE (1..10)) OF SearchSpaceExt-v1700 OPTIONAL, — Need N

monitoringCapabilityConfig-v1710 ENUMERATED { r17monitoringcapability } OPTIONAL, — Need M

searchSpaceSwitchConfig-r17 SearchSpaceSwitchConfig-r17 OPTIONAL, — Need R

pdcch-SkippingDurationList-r17 SEQUENCE(SIZE (1..3)) OF SCS-SpecificDuration-r17 OPTIONAL — Need R

]]

}

SearchSpaceSwitchConfig-r16 ::= SEQUENCE {

cellGroupsForSwitchList-r16 SEQUENCE(SIZE (1..4)) OF CellGroupForSwitch-r16 OPTIONAL, — Need R

searchSpaceSwitchDelay-r16 INTEGER (10..52) OPTIONAL — Need R

}

SearchSpaceSwitchConfig-r17 ::= SEQUENCE {

searchSpaceSwitchTimer-r17 SCS-SpecificDuration-r17 OPTIONAL, — Need R

searchSpaceSwitchDelay-r17 INTEGER (10..52) OPTIONAL — Need R

}

CellGroupForSwitch-r16 ::= SEQUENCE(SIZE (1..16)) OF ServCellIndex

SCS-SpecificDuration-r17 ::= INTEGER (1..166)

— TAG-PDCCH-CONFIG-STOP

— ASN1STOP

PDCCH-Config field descriptions

controlResourceSetToAddModList, controlResourceSetToAddModListSizeExt List of UE specifically configured Control Resource Sets (CORESETs) to be used by the UE. The network restrictions on configuration of CORESETs per DL BWP are specified in TS 38.213 [13], clause 10.1 and TS 38.306 [26]. The UE shall consider entries in controlResourceSetToAddModList and in controlResourceSetToAddModListSizeExt as a single list, i.e. an entry created using controlResourceSetToAddModList can be modified using controlResourceSetToAddModListSizeExt (or deleted using controlResourceSetToReleaseListSizeExt) and vice-versa. In case network reconfigures control resource set with the same ControlResourceSetId as used for commonControlResourceSet or commonControlResourceSetExt configured via PDCCH-ConfigCommon or via SIB20, the configuration from PDCCH-Config always takes precedence and should not be updated by the UE based on servingCellConfigCommon or based on SIB20.

controlResourceSetToReleaseList, controlResourceSetToReleaseListSizeExt List of UE specifically configured Control Resource Sets (CORESETs) to be released by the UE. This field only applies to CORESETs configured by controlResourceSetToAddModList or controlResourceSetToAddModListSizeExt and does not release the field commonControlResourceSet configured by PDCCH-ConfigCommon and commonControlResourceSetExt configured by SIB20.

downlinkPreemption Configuration of downlink preemption indications to be monitored in this cell (see TS 38.213 [13], clause 11.2).

monitoringCapabilityConfig Configures either Rel-15 PDCCH monitoring capability, Rel-16 PDCCH monitoring capability or Rel-17 PDCCH monitoring capability for PDCCH monitoring on a serving cell (see TS 38.213 [13], clause 10.1). Value r15monitoringcapability enables the Rel-15 monitoring capability, and value r16monitoringcapability enables the Rel-16 PDCCH monitoring capability. r17monitoringcapability enables the Rel-17 PDCCH multi-slot monitoring capability. For 480 and 960 kHz SCS, only value r17monitoringcapability is applicable.

pdcch-SkippingDurationList Provides one or more values to derive the skipping duration in unit of slots, as specified in TS 38.213 [13], clause 10.4. The DCI which schedules data indicates which of the values is to be applied (see TS 38.213 [13], clause 10.4). For the 15kHz SCS, for each entry, only the first 26 values are valid and correspond to {1, 2, 3, …, 20, 30, 40, 50, 60, 80, 100}. For the 30kHz SCS, for each entry, only the first 46 values are valid and correspond to {1, 2, 3, …, 40, 60, 80, 100, 120, 160, 200}. For the 60kHz SCS, for each entry, only the first 86 values are valid and correspond to {1, 2, 3, …, 80, 120, 160, 200, 240, 320, 400}. For the 120kHz SCS, for each entry, the 166 values correspond to {1, 2, 3, …, 160, 240, 320, 400, 480, 640, 800}. For the 480kHz SCS, for each entry, the 166 values correspond to {4, 8, 12, …, 640, 960, 1280, 1600, 1920, 2560, 3200}. For the 960kHz SCS, for each entry, the 166 values correspond to {8, 16, 24, …, 1280, 1920, 2560, 3200, 3840, 5120, 6400}.

searchSpacesToAddModList, searchSpacesToAddModListExt List of UE specifically configured Search Spaces or MBS multicast Search Spaces. The network configures at most 10 Search Spaces per BWP per cell (including UE-specific and common Search Spaces). If the network includes searchSpaceToAddModListExt, it includes the same number of entries, and listed in the same order, as in searchSpacesToAddModList in each of them.

searchSpaceSwitchConfig Configuration to control the UE behavior to switch from search space group X back to search space group 0, as specified in clause 10 of TS 38.213 [13]. The network only configures either searchSpaceSwitchConfig-r16 or searchSpaceSwitchConfig-r17 for a UE.

tpc-PUCCH Enable and configure reception of group TPC commands for PUCCH.

tpc-PUSCH Enable and configure reception of group TPC commands for PUSCH.

tpc-SRS Enable and configure reception of group TPC commands for SRS.

uplinkCancellation Configuration of uplink cancellation indications to be monitored in this cell (see TS 38.213 [13], clause 11.2A).

SearchSpaceSwitchConfig field descriptions

cellGroupsForSwitchList The list of serving cells which are bundled for the search space group switching purpose (see TS 38.213 [13], clause 10.4). A serving cell can belong to only one CellGroupForSwitch. The network configures the same list for all BWPs of serving cells in the same CellGroupForSwitch.

searchSpaceSwitchDelay Indicates the value to be applied by a UE for Search Space Set Group switching; corresponds to the P value in TS 38.213 [13], clause 10.4. The network configures the same value for all BWPs of serving cells in the same CellGroupForSwitch. For 120/480/960 kHz SCS, only values 40,41, … 52 are valid and the actual value = field value * SCS/120 kHz i.e. field value 40 corresponds to 40 with 120 kHz SCS, 160 with 480 kHz SCS and 320 with 960 kHz SCS, and so on.

searchSpaceSwitchTimer Timer (in unit of slots) to control the UE behavior to switch from search space group X back to search space group 0, as specified in clause 10 of TS 38.213 [13]. For the 15kHz SCS, only the first 26 values are valid and correspond to {1, 2, 3, …, 20, 30, 40, 50, 60, 80, 100}. For the 30kHz SCS, only the first 46 values are valid and correspond to {1, 2, 3, …, 40, 60, 80, 100, 120, 160, 200}. For the 60kHz SCS, only the first 86 values are valid and correspond to {1, 2, 3, …, 80, 120, 160, 200, 240, 320, 400}. For the 120kHz SCS, the 166 values correspond to {1, 2, 3, …, 160, 240, 320, 400, 480, 640, 800}. For the 480kHz SCS, the 166 values correspond to {4, 8, 12, …, 640, 960, 1280, 1600, 1920, 2560, 3200}. For the 960kHz SCS, the 166 values correspond to {8, 16, 24, …, 1280, 1920, 2560, 3200, 3840, 5120, 6400}.

– PDCCH-ConfigCommon

The IE PDCCH-ConfigCommon is used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signalling.

PDCCH-ConfigCommon information element

— ASN1START

— TAG-PDCCH-CONFIGCOMMON-START

PDCCH-ConfigCommon ::= SEQUENCE {

controlResourceSetZero ControlResourceSetZero OPTIONAL, — Cond InitialBWP-Only

commonControlResourceSet ControlResourceSet OPTIONAL, — Need R

searchSpaceZero SearchSpaceZero OPTIONAL, — Cond InitialBWP-Only

commonSearchSpaceList SEQUENCE (SIZE(1..4)) OF SearchSpace OPTIONAL, — Need R

searchSpaceSIB1 SearchSpaceId OPTIONAL, — Need S

searchSpaceOtherSystemInformation SearchSpaceId OPTIONAL, — Need S

pagingSearchSpace SearchSpaceId OPTIONAL, — Need S

ra-SearchSpace SearchSpaceId OPTIONAL, — Need S

…,

[[

firstPDCCH-MonitoringOccasionOfPO CHOICE {

sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139),

sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279),

sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559),

sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119),

sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239),

sCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479),

sCS120KHZoneEighthT-SCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959),

sCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919)

} OPTIONAL — Cond OtherBWP

]],

[[

commonSearchSpaceListExt-r16 SEQUENCE (SIZE(1..4)) OF SearchSpaceExt-r16 OPTIONAL — Need R

]],

[[

sdt-SearchSpace-r17 CHOICE {

newSearchSpace SearchSpace,

existingSearchSpace SearchSpaceId

} OPTIONAL, — Need R

searchSpaceMCCH-r17 SearchSpaceId OPTIONAL, — Need R

searchSpaceMTCH-r17 SearchSpaceId OPTIONAL, — Need S

commonSearchSpaceListExt2-r17 SEQUENCE (SIZE(1..4)) OF SearchSpaceExt-v1700 OPTIONAL, — Need R

firstPDCCH-MonitoringOccasionOfPO-v1710 CHOICE {

sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839),

sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..71679)

} OPTIONAL, — Need R

pei-ConfigBWP-r17 SEQUENCE {

pei-SearchSpace-r17 SearchSpaceId,

firstPDCCH-MonitoringOccasionOfPEI-O-r17 CHOICE {

sCS15KHZoneT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..139),

sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..279),

sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..559),

sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..1119),

sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..2239),

sCS480KHZoneT-SCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..4479),

sCS480KHZhalfT-SCS120KHZoneEighthT-SCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..8959),

sCS480KHZquarterT-SCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..17919),

sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..35839),

sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..71679)

}

} OPTIONAL — Cond InitialBWP-Paging

]],

[[

followUnifiedTCIstate-v1720 ENUMERATED {enabled} OPTIONAL — Need R

]]

}

— TAG-PDCCH-CONFIGCOMMON-STOP

— ASN1STOP

PDCCH-ConfigCommon field descriptions

commonControlResourceSet An additional common control resource set which may be configured and used for any common or UE-specific search space. If the network configures this field, it uses a ControlResourceSetId other than 0 for this ControlResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is contained in the bandwidth of CORESET#0. If the RedCap-specific initial downlink BWP does not contain the entire CORESET#0, the network configures the commonControlResourceSet in SIB1 for RedCap so that it is not contained in the bandwidth of CORESET#0.

commonSearchSpaceList, commonSearchSpaceListExt A list of additional common search spaces. If the network configures this field, it uses the SearchSpaceIds other than 0. If the field is included, it replaces any previous list, i.e. all the entries of the list are replaced and each of the SearchSpace entries is considered to be newly created and the conditions and Need codes for setup of the entry apply. If the network includes commonSearchSpaceListExt, it includes the same number of entries, and listed in the same order, as in commonSearchSpaceList.

controlResourceSetZero Parameters of the common CORESET#0 which can be used in any common or UE-specific search spaces. The values are interpreted like the corresponding bits in MIB pdcch-ConfigSIB1. Even though this field is only configured in the initial BWP (BWP#0) controlResourceSetZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions defined in TS 38.213 [13], clause 10 are satisfied.

firstPDCCH-MonitoringOccasionOfPEI-O Offset, in number of symbols, from the start of the reference frame for PEI-O to the start of the first PDCCH monitoring occasion of PEI-O on this BWP, see TS 38.213 [13], clause 10.4A. For the case po-NumPerPEI is smaller than Ns, UE applies the (floor(i_s/po-NumPerPEI)+1)-th value out of (N_s/po-NumPerPEI) configured values in firstPDCCH-MonitoringOccasionOfPEI-O for the symbol-level offset. When po-NumPerPEI is one or multiple of Ns, UE applies the first configured value in firstPDCCH-MonitoringOccasionOfPEI-O for the symbol-level offset.

firstPDCCH-MonitoringOccasionOfPO Indicates the first PDCCH monitoring occasion of each PO of the PF on this BWP, see TS 38.304 [20]. The field sCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT, sCS120KHZoneEighthT-SCS60KHZoneSixteenthT and sCS120KHZoneSixteenthT can be applied for SCS 480kHz, corresponding to sCS480KHZoneT-SCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT, sCS480KHZhalfT-SCS120KHZoneEighthT-SCS60KHZoneSixteenthT and sCS480KHZquarterT-SCS120KHZoneSixteenthT in IE DownlinkConfigCommonSIB respectively.

followUnifiedTCIstate When set to enabled, for PDCCH reception in CORESET #0, the UE applies the "indicated" DL only TCI or joint TCI as specified in TS 38.214 clause 5.1.5.

pagingSearchSpace ID of the search space for paging (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive paging in this BWP (see TS 38.213 [13], clause 10). This field is absent for the RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0. In that case, a RedCap UE shall monitor paging in the initial DL BWP that includes CORESET#0

pei-ConfigBWP Provides the configuration for PEI reception in this BWP. If the field is absent, the UE does not receive PEI in this BWP.

pei-SearchSpace ID of dedicated search space for PEI. It can be configured to one of up to 4 common SS sets configured by commonSearchSpaceList with SearchSpaceId > 0. The CCE aggregation levels and maximum number of PDCCH candidates per CCE aggregation level follows Table 10.1-1 of TS38.213 [13]. SearchSpaceId = 0 can be configured for the case of SS/PBCH block and CORESET multiplexing pattern 2 or 3.

ra-SearchSpace ID of the Search space for random access procedure (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive RAR in this BWP. This field is mandatory present in the DL BWP(s) if the conditions described in TS 38.321 [3], clause 5.15 are met.

sdt-SearchSpace Common search space for CG-SDT and RA-SDT (see TS 38.213 [13]). If an existingSearchSpace is used, the network only signals the search space ID of the ra-SearchSpace.

searchSpaceMCCH ID of the search space for MCCH. If the field is absent, the UE does not receive MCCH in this BWP (see TS 38.213 [13], clause 10). This field is absent for the RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0.

searchSpaceMTCH ID of the search space for MTCH of MBS broadcast. If the field is absent, the UE applies searchSpaceMCCH also for MTCH, (see TS 38.213 [13], clause 10). This field is absent for the RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0.

searchSpaceOtherSystemInformation ID of the Search space for other system information, i.e., SIB2 and beyond (see TS 38.213 [13], clause 10.1) If the field is absent, the UE does not receive other system information in this BWP. This field is absent for the RedCap-specific initial DL BWP, if it does not include CD-SSB and the entire CORESET#0.

searchSpaceSIB1 ID of the search space for SIB1 message. In the initial DL BWP of the UE′s PCell, the network sets this field to 0. If the field is absent, the UE does not receive SIB1 in this BWP. (see TS 38.213 [13], clause 10). This field is absent for the RedCap-specific initial DL BWP, if it does not include CD-SSB and the entire CORESET#0.

searchSpaceZero Parameters of the common SearchSpace#0. The values are interpreted like the corresponding bits in MIB pdcch-ConfigSIB1. Even though this field is only configured in the initial BWP (BWP#0), searchSpaceZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions described in TS 38.213 [13], clause 10, are satisfied.

Conditional Presence	Explanation
InitialBWP-Only	If SIB1 is broadcast the field is mandatory present in the PDCCH-ConfigCommon of the initial BWP (BWP#0) in ServingCellConfigCommon except it is the RedCap-specific initial BWP not including CD-SSB and the entire CORESET#0; it is absent in other BWPs and when sent in system information. If SIB1 is not broadcast and there is an SSB associated to the cell, the field is optionally present, Need M, in the PDCCH-ConfigCommon of the initial BWP (BWP#0) in ServingCellConfigCommon (still with the same setting for all UEs). In other cases, the field is absent.
OtherBWP	This field is optionally present, Need R, if this BWP is not the initialDownlinkBWP and pagingSearchSpace is configured in this BWP. Otherwise this field is absent.
InitialBWP-Paging	This field is optionally present, Need R, if this BWP is the initialDownlinkBWP or initialDownlinkBWP-RedCap including CD-SSB and the entire CORESET#0, and pei-Config is configured in DownlinkConfigCommonSIB. Otherwise, this field is absent.

– PDCCH-ConfigSIB1

The IE PDCCH-ConfigSIB1 is used to configure CORESET#0 and search space#0.

PDCCH-ConfigSIB1 information element

— ASN1START

— TAG-PDCCH-CONFIGSIB1-START

PDCCH-ConfigSIB1 ::= SEQUENCE {

controlResourceSetZero ControlResourceSetZero,

searchSpaceZero SearchSpaceZero

}

— TAG-PDCCH-CONFIGSIB1-STOP

— ASN1STOP

PDCCH-ConfigSIB1 field descriptions

controlResourceSetZero Determines a common ControlResourceSet (CORESET) with ID #0, see TS 38.213 [13], clause 13.

searchSpaceZero Determines a common search space with ID #0, see TS 38.213 [13], clause 13.

– PDCCH-ServingCellConfig

The IE PDCCH-ServingCellConfig is used to configure UE specific PDCCH parameters applicable across all bandwidth parts of a serving cell.

PDCCH-ServingCellConfig information element

— ASN1START

— TAG-PDCCH-SERVINGCELLCONFIG-START

PDCCH-ServingCellConfig ::= SEQUENCE {

slotFormatIndicator SetupRelease { SlotFormatIndicator } OPTIONAL, — Need M

…,

[[

availabilityIndicator-r16 SetupRelease {AvailabilityIndicator-r16} OPTIONAL, — Need M

searchSpaceSwitchTimer-r16 INTEGER (1..80) OPTIONAL — Need R

]],

[[

searchSpaceSwitchTimer-v1710 INTEGER (81..1280) OPTIONAL — Need R

]]

}

— TAG-PDCCH-SERVINGCELLCONFIG-STOP

— ASN1STOP

PDCCH-ServingCellConfig field descriptions

availabilityIndicator Use to configure monitoring a PDCCH for Availability Indicators (AI).

searchSpaceSwitchTimer The value of the timer in slots for monitoring PDCCH in the active DL BWP of the serving cell before moving to the default search space group (see TS 38.213 [13], clause 10.4). For 15 kHz SCS, {1..20} are valid. For 30 kHz SCS, {1..40} are valid. For 60kHz SCS, {1..80} are valid. For 120 kHz SCS, {1..160} are valid. For 480 kHz SCS, {1..640} are valid. For 960 kHz SCS, {1..1280} are valid. The network configures the same value for all serving cells in the same CellGroupForSwitch.

slotFormatIndicator Configuration of Slot-Format-Indicators to be monitored in the correspondingly configured PDCCHs of this serving cell.

– PDCP-Config

The IE PDCP-Config is used to set the configurable PDCP parameters for signalling, MBS multicast and data radio bearers.

PDCP-Config information element

— ASN1START

— TAG-PDCP-CONFIG-START

PDCP-Config ::= SEQUENCE {

drb SEQUENCE {

discardTimer ENUMERATED {ms10, ms20, ms30, ms40, ms50, ms60, ms75, ms100, ms150, ms200,

ms250, ms300, ms500, ms750, ms1500, infinity} OPTIONAL, — Cond Setup

pdcp-SN-SizeUL ENUMERATED {len12bits, len18bits} OPTIONAL, — Cond Setup1

pdcp-SN-SizeDL ENUMERATED {len12bits, len18bits} OPTIONAL, — Cond Setup2

headerCompression CHOICE {

notUsed NULL,

rohc SEQUENCE {

maxCID INTEGER (1..16383) DEFAULT 15,

profiles SEQUENCE {

profile0x0001 BOOLEAN,

profile0x0002 BOOLEAN,

profile0x0003 BOOLEAN,

profile0x0004 BOOLEAN,

profile0x0006 BOOLEAN,

profile0x0101 BOOLEAN,

profile0x0102 BOOLEAN,

profile0x0103 BOOLEAN,

profile0x0104 BOOLEAN

},

drb-ContinueROHC ENUMERATED { true } OPTIONAL — Need N

},

uplinkOnlyROHC SEQUENCE {

maxCID INTEGER (1..16383) DEFAULT 15,

profiles SEQUENCE {

profile0x0006 BOOLEAN

},

drb-ContinueROHC ENUMERATED { true } OPTIONAL — Need N

},

…

},

integrityProtection ENUMERATED { enabled } OPTIONAL, — Cond ConnectedTo5GC1

statusReportRequired ENUMERATED { true } OPTIONAL, — Cond Rlc-AM-UM

outOfOrderDelivery ENUMERATED { true } OPTIONAL — Need R

} OPTIONAL, — Cond DRB

moreThanOneRLC SEQUENCE {

primaryPath SEQUENCE {

cellGroup CellGroupId OPTIONAL, — Need R

logicalChannel LogicalChannelIdentity OPTIONAL — Need R

},

ul-DataSplitThreshold UL-DataSplitThreshold OPTIONAL, — Cond SplitBearer

pdcp-Duplication BOOLEAN OPTIONAL — Need R

} OPTIONAL, — Cond MoreThanOneRLC

t-Reordering ENUMERATED {

ms0, ms1, ms2, ms4, ms5, ms8, ms10, ms15, ms20, ms30, ms40,

ms50, ms60, ms80, ms100, ms120, ms140, ms160, ms180, ms200, ms220,

ms240, ms260, ms280, ms300, ms500, ms750, ms1000, ms1250,

ms1500, ms1750, ms2000, ms2250, ms2500, ms2750,

ms3000, spare28, spare27, spare26, spare25, spare24,

spare23, spare22, spare21, spare20,

spare19, spare18, spare17, spare16, spare15, spare14,

spare13, spare12, spare11, spare10, spare09,

spare08, spare07, spare06, spare05, spare04, spare03,

spare02, spare01 } OPTIONAL, — Need S

…,

[[

cipheringDisabled ENUMERATED {true} OPTIONAL — Cond ConnectedTo5GC

]],

[[

discardTimerExt-r16 SetupRelease { DiscardTimerExt-r16 } OPTIONAL, — Cond DRB2

moreThanTwoRLC-DRB-r16 SEQUENCE {

splitSecondaryPath-r16 LogicalChannelIdentity OPTIONAL, — Cond SplitBearer2

duplicationState-r16 SEQUENCE (SIZE (3)) OF BOOLEAN OPTIONAL — Need S

} OPTIONAL, — Cond MoreThanTwoRLC-DRB

ethernetHeaderCompression-r16 SetupRelease { EthernetHeaderCompression-r16 } OPTIONAL — Need M

]],

[[

survivalTimeStateSupport-r17 ENUMERATED {true} OPTIONAL, — Cond Drb-Duplication

uplinkDataCompression-r17 SetupRelease { UplinkDataCompression-r17 } OPTIONAL, — Cond Rlc-AM

discardTimerExt2-r17 SetupRelease { DiscardTimerExt2-r17 } OPTIONAL, — Need M

initialRX-DELIV-r17 BIT STRING (SIZE (32)) OPTIONAL — Cond MRB-Initialization

]]

}

EthernetHeaderCompression-r16 ::= SEQUENCE {

ehc-Common-r16 SEQUENCE {

ehc-CID-Length-r16 ENUMERATED { bits7, bits15 },

…

},

ehc-Downlink-r16 SEQUENCE {

drb-ContinueEHC-DL-r16 ENUMERATED { true } OPTIONAL, — Need N

…

} OPTIONAL, — Need M

ehc-Uplink-r16 SEQUENCE {

maxCID-EHC-UL-r16 INTEGER (1..32767),

drb-ContinueEHC-UL-r16 ENUMERATED { true } OPTIONAL, — Need N

…

} OPTIONAL — Need M

}

UL-DataSplitThreshold ::= ENUMERATED {

b0, b100, b200, b400, b800, b1600, b3200, b6400, b12800, b25600, b51200, b102400, b204800,

b409600, b819200, b1228800, b1638400, b2457600, b3276800, b4096000, b4915200, b5734400,

b6553600, infinity, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}

DiscardTimerExt-r16 ::= ENUMERATED {ms0dot5, ms1, ms2, ms4, ms6, ms8, spare2, spare1}

DiscardTimerExt2-r17 ::= ENUMERATED {ms2000, spare3, spare2, spare1}

UplinkDataCompression-r17 ::= CHOICE {

newSetup SEQUENCE {

bufferSize-r17 ENUMERATED {kbyte2, kbyte4, kbyte8, spare1},

dictionary-r17 ENUMERATED {sip-SDP, operator} OPTIONAL — Need N

},

drb-ContinueUDC NULL

}

— TAG-PDCP-CONFIG-STOP

— ASN1STOP

PDCP-Config field descriptions
cipheringDisabled If included, ciphering is disabled for this DRB regardless of which ciphering algorithm is configured for the SRB/DRBs. The field may only be included if the UE is connected to 5GC. Otherwise the field is absent. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up.
discardTimer Value in ms of discardTimer specified in TS 38.323 [5]. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms and so on. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.
discardTimerExt Value in ms of discardTimer specified in TS 38.323 [5]. Value ms0dot5 corresponds to 0.5 ms, value ms1 corresponds to 1ms and so on. If this field is present, the field discardTimer is ignored and discardTimerExt is used instead.
discardTimerExt2 Value in ms of discardTimerExt specified in TS 38.323 [5]. Value ms2000 corresponds to 2000 ms. If this field is present, the field discardTimer and discardTimerExt are ignored and discardTimerExt2 is used instead.
drb-ContinueROHC Indicates whether the PDCP entity continues or resets the ROHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. This field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. The network does not include the field if the bearer is configured as DAPS bearer. This field can be configured for both DRB and multicast MRB.
duplicationState This field indicates the uplink PDCP duplication state for the associated RLC entities at the time of receiving this IE. If set to true, the PDCP duplication state is activated for the associated RLC entity. The index for the indication is determined by ascending order of logical channel ID of all RLC entities other than the primary RLC entity indicated by primaryPath in the order of MCG and SCG, as in clause 6.1.3.32 of TS 38.321 [3]. If the number of associated RLC entities other than the primary RLC entity is two, UE ignores the value in the largest index of this field. If the field is absent, the PDCP duplication states are deactivated for all associated RLC entities.
ethernetHeaderCompression This fields configures Ethernet Header Compression. This field can only be configured for a bi-directional DRB or a bi-directional multicast MRB. The network reconfigures ethernetHeaderCompression only upon reconfiguration involving PDCP re-establishment and with neither drb-ContinueEHC-DL nor drb-ContinueEHC-UL configured. Network only configures this field when uplinkDataCompression is not configured.
headerCompression If rohc is configured, the UE shall apply the configured ROHC profile(s) in both uplink and downlink. If uplinkOnlyROHC is configured, the UE shall apply the configured ROHC profile(s) in uplink (there is no header compression in downlink). ROHC can be configured for any bearer type. ROHC and EHC can be both configured simultaneously for a DRB or a multicast MRB. The network reconfigures headerCompression only upon reconfiguration involving PDCP re-establishment or involving PDCP entity reconfiguration to configure DAPS bearer(s), and without any drb-ContinueROHC. Network configures headerCompression to notUsed when outOfOrderDelivery is configured. Network only configures this field when uplinkDataCompression is not configured.
initialRX-DELIV Indicates the initial value of RX_DELIV during PDCP window initialization for multicast MRB as specified in TS 38.323 [5].
integrityProtection Indicates whether or not integrity protection is configured for this radio bearer. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up.
maxCID Indicates the value of the MAX_CID parameter as specified in TS 38.323 [5]. The total value of MAX_CIDs across all bearers for the UE should be less than or equal to the value of maxNumberROHC-ContextSessions parameter as indicated by the UE.
moreThanOneRLC This field configures UL data transmission when more than one RLC entity is associated with the PDCP entity. This field is not present if the bearer is configured as DAPS bearer.
moreThanTwoRLC-DRB This field configures UL data transmission when more than two RLC entities are associated with the PDCP entity for DRBs.
outOfOrderDelivery Indicates whether or not outOfOrderDelivery specified in TS 38.323 [5] is configured. This field should be either always present or always absent, after the radio bearer is established.
pdcp-Duplication Indicates whether or not uplink duplication status at the time of receiving this IE is configured and activated as specified in TS 38.323 [5]. The presence of this field indicates that duplication is configured. PDCP duplication is not configured for CA packet duplication of LTE RLC bearer. The value of this field, when the field is present, indicates the state of the duplication at the time of receiving this IE. If set to true, duplication is activated. The value of this field is always true, when configured for a SRB. For PDCP entity with more than two associated RLC entities for UL transmission, this field is always present. If the field moreThanTwoRLC-DRB is present, the value of this field is ignored and the state of the duplication is indicated by duplicationState. For PDCP entity with more than two associated RLC entities, only NR RLC bearer is supported.
pdcp-SN-SizeDL PDCP sequence number size for downlink, 12 or 18 bits, as specified in TS 38.323 [5]. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.
pdcp-SN-SizeUL PDCP sequence number size for uplink, 12 or 18 bits, as specified in TS 38.323 [5]. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.
primaryPath Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323 [5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs, except for the split SRB2 of the IAB-MT, and, when the SCG is deactivated, for DRBs. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW always indicates logicalChannel if CA based PDCP duplication is configured in the cell group indicated by cellGroup of this field.
splitSecondaryPath Indicates the LCID of the split secondary RLC entity as specified in TS 38.323 [5] for fallback to split bearer operation when UL data transmission with more than two RLC entities is associated with the PDCP entity. This RLC entity belongs to a cell group that is different from the cell group indicated by cellGroup in the field primaryPath.
statusReportRequired For AM DRBs, AM MRBs and DAPS UM DRBs, indicates whether the DRB or the multicast MRB is configured to send a PDCP status report in the uplink, as specified in TS 38.323 [5]. For DAPS AM DRBs, it also indicates whether the DRB is configured to send a second PDCP status report in the uplink, as specified in TS 38.323 [5].
survivalTimeStateSupport Indicates whether the DRB associated with this PDCP entity has survival time state support. If this field is configured to be true, all associated RLC entities are activated for PDCP duplication upon reception of a retransmission grant addressed to CS-RNTI, as specified in TS 38.321 [3].
t-Reordering Value in ms of t-Reordering specified in TS 38.323 [5]. Value ms0 corresponds to 0 ms, value ms20 corresponds to 20 ms, value ms40 corresponds to 40 ms, and so on. When the field is absent the UE applies the value infinity. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.
ul-DataSplitThreshold Parameter specified in TS 38.323 [5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting splitDRB-withUL-Both-MCG-SCG and when the SCG is deactivated. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied.
uplinkDataCompression Indicates the UDC configuration that the UE shall apply. Network does not configure uplinkDataCompression for a DRB, if headerCompression or ethernetHeaderCompression is already configured or outOfOrderDelivery or DAPS is configured for the DRB. The maximum number of DRBs where uplinkDataCompression can be applied is two. The network reconfigures uplinkDataCompression only upon reconfiguration involving PDCP re-establishment. If the field is set to drb-ContinueUDC, the PDCP entity continues the uplink data compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is set to drb-ContinueUDC only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated.

EthernetHeaderCompression field descriptions

drb-ContinueEHC-DL Indicates whether the PDCP entity continues or resets the downlink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated.

drb-ContinueEHC-UL Indicates whether the PDCP entity continues or resets the uplink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated.

ehc-CID-Length Indicates the length of the CID field for EHC packet. The value bits7 indicates the length is 7 bits, and the value bits15 indicates the length is 15 bits. Once the field ethernetHeaderCompression-r16 is configured for a DRB or a multicast MRB, the value of the field ehc-CID-Length for this DRB or multicast MRB is not reconfigured to a different value.

ehc-Common Indicates the configurations that apply for both downlink and uplink.

ehc-Downlink Indicates the configurations that apply for only downlink. If the field is configured, then Ethernet header compression is configured for downlink. Otherwise, it is not configured for downlink.

ehc-Uplink Indicates the configurations that apply for only uplink. If the field is configured, then Ethernet header compression is configured for uplnik. Otherwise, it is not configured for uplink.

maxCID-EHC-UL Indicates the value of the MAX_CID_EHC_UL parameter as specified in TS 38.323 [5]. The total value of MAX_CID_EHC_UL across all bearers for the UE should be less than or equal to the value of maxNumberEHC-Contexts parameter as indicated by the UE.

UplinkDataCompression field descriptions

bufferSize This field indicates the buffer size applied for UDC as specified in TS 38.323 [5]. Value kbyte2 means 2048 bytes, kbyte4 means 4096 bytes and so on.

dictionary This field indicates which pre-defined dictionary is used for UDC as specified in TS 38.323 [5]. The value sip-SDP means that UE shall prefill the buffer with standard dictionary for SIP and SDP defined in TS 38.323 [5], and the value operator means that UE shall prefill the buffer with operator-defined dictionary.

Conditional presence	Explanation
DRB	This field is mandatory present when the corresponding DRB/multicast MRB is being set up, absent for SRBs. Otherwise this field is optionally present, need M.
DRB2	This field is optionally present in case of DRB, need M. Otherwise, it is absent for SRBs and MRBs.
Drb-Duplication	For SRBs, this field is absent. For DRBs, this field is absent if duplication is not configured. Otherwise, this field is optional, need R.
MoreThanOneRLC	This field is mandatory present upon RRC reconfiguration with setup of a PDCP entity for a radio bearer with more than one associated logical channel and upon RRC reconfiguration with the association of additional logical channels to the PDCP entity. The field is also mandatory present in case the field moreThanTwoRLC-DRB is included in PDCP-Config. Upon RRC reconfiguration when a PDCP entity is associated with multiple logical channels, this field is optionally present need M. Otherwise, this field is absent. Need R.
MoreThanTwoRLC-DRB	For SRBs, this field is absent. For DRBs, this field is mandatory present upon RRC reconfiguration with setup of a PDCP entity for a radio bearer with more than two associated logical channels and upon RRC reconfiguration with the association of one or more additional logical channel(s) to the PDCP entity so that the PDCP entity has more than two associated logical channels. Upon RRC reconfiguration when a PDCP entity is associated with more than two logical channels, this field is optionally present, Need M. Otherwise, the field is absent, Need R.
Rlc-AM	For RLC AM, the field is optionally present, need M. Otherwise, the field is absent.
Rlc-AM-UM	In case of DRB, for RLC UM (if the UE supports DAPS handover) or RLC AM, the field is optionally present, need R. In case of multicast MRB, if multicast MRB is associated with at least one RLC AM entity, the field is optionally present, need R. Otherwise, the field is absent.
Setup	The field is mandatory present in case of SRB or DRB setup. Otherwise the field is optionally present, need M.
SplitBearer	The field is absent for SRBs. Otherwise, the field is optional present, need M, in case of radio bearer with more than one associated RLC mapped to different cell groups.
SplitBearer2	The field is mandatory present, in case of a split bearer. Otherwise the field is absent.
ConnectedTo5GC	The field is optionally present, need R, if the UE is connected to 5GC. Otherwise the field is absent.
ConnectedTo5GC1	The field is optionally present, need R, if the UE is connected to NR/5GC or if the UE supports user plane integrity protection when connected to E-UTRA/EPC (as specified in TS 33.401 [30]). Otherwise the field is absent.
Setup1	This field is mandatory present in case of SRB and DRB setup for RLC-AM and RLC-UM. Otherwise, this field is absent, Need M.
Setup2	This field is mandatory present in case for radio bearer setup for RLC-AM and RLC-UM. Otherwise, this field is absent, Need M.
MRB-Initialization	This field is mandatory present in case of multicast MRB setup and PDCP re-establishment for UM multicast MRB. Otherwise, this field is absent, Need N.

– PDSCH-Config

The PDSCH-Config IE is used to configure the UE specific PDSCH parameters. If this IE is used for MBS CFR, the following fields shall be absent: tci-StatesToAddModList, tci-StatesToReleaseList, zp-CSI-RS-ResourceToAddModList, minimumSchedulingOffsetK0, antennaPortsFieldPresenceDCI-1-2, aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2, aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2, dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2, dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2, dmrs-SequenceInitializationDCI-1-2, harq-ProcessNumberSizeDCI-1-2, mcs-TableDCI-1-2, numberOfBitsForRV-DCI-1-2, pdsch-AggregationFactor, pdsch-TimeDomainAllocationListDCI-1-2, prb-BundlingTypeDCI-1-2, priorityIndicatorDCI-1-2, rateMatchPatternGroup1DCI-1-2, rateMatchPatternGroup2DCI-1-2, resourceAllocationType1GranularityDCI-1-2, vrb-ToPRB-InterleaverDCI-1-2, referenceOfSLIVDCI-1-2, resourceAllocationDCI-1-2, dataScramblingIdentityPDSCH2-r16, repetitionSchemeConfig.

PDSCH-Config information element

— ASN1START

— TAG-PDSCH-CONFIG-START

PDSCH-Config ::= SEQUENCE {

dataScramblingIdentityPDSCH INTEGER (0..1023) OPTIONAL, — Need S

dmrs-DownlinkForPDSCH-MappingTypeA SetupRelease { DMRS-DownlinkConfig } OPTIONAL, — Need M

dmrs-DownlinkForPDSCH-MappingTypeB SetupRelease { DMRS-DownlinkConfig } OPTIONAL, — Need M

tci-StatesToAddModList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State OPTIONAL, — Need N

tci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-StateId OPTIONAL, — Need N

vrb-ToPRB-Interleaver ENUMERATED {n2, n4} OPTIONAL, — Need S

resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},

pdsch-TimeDomainAllocationList SetupRelease { PDSCH-TimeDomainResourceAllocationList } OPTIONAL, — Need M

pdsch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, — Need S

rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, — Need N

rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, — Need N

rateMatchPatternGroup1 RateMatchPatternGroup OPTIONAL, — Need R

rateMatchPatternGroup2 RateMatchPatternGroup OPTIONAL, — Need R

rbg-Size ENUMERATED {config1, config2},

mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, — Need S

maxNrofCodeWordsScheduledByDCI ENUMERATED {n1, n2} OPTIONAL, — Need R

prb-BundlingType CHOICE {

staticBundling SEQUENCE {

bundleSize ENUMERATED { n4, wideband } OPTIONAL — Need S

},

dynamicBundling SEQUENCE {

bundleSizeSet1 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, — Need S

bundleSizeSet2 ENUMERATED { n4, wideband } OPTIONAL — Need S

}

},

zp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-Resource

OPTIONAL, — Need N

zp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-ResourceId

OPTIONAL, — Need N

aperiodic-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet

OPTIONAL, — Need N

aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId

OPTIONAL, — Need N

sp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet

OPTIONAL, — Need N

sp-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId

OPTIONAL, — Need N

p-ZP-CSI-RS-ResourceSet SetupRelease { ZP-CSI-RS-ResourceSet }

OPTIONAL, — Need M

…,

[[

maxMIMO-Layers-r16 SetupRelease { MaxMIMO-LayersDL-r16 } OPTIONAL, — Need M

minimumSchedulingOffsetK0-r16 SetupRelease { MinSchedulingOffsetK0-Values-r16 } OPTIONAL, — Need M

— Start of the parameters for DCI format 1_2 introduced in V16.1.0

antennaPortsFieldPresenceDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, — Need S

aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet

OPTIONAL, — Need N

aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId

OPTIONAL, — Need N

dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, — Need M

dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, — Need M

dmrs-SequenceInitializationDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, — Need S

harq-ProcessNumberSizeDCI-1-2-r16 INTEGER (0..4) OPTIONAL, — Need R

mcs-TableDCI-1-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, — Need S

numberOfBitsForRV-DCI-1-2-r16 INTEGER (0..2) OPTIONAL, — Need R

pdsch-TimeDomainAllocationListDCI-1-2-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 }

OPTIONAL, — Need M

prb-BundlingTypeDCI-1-2-r16 CHOICE {

staticBundling-r16 SEQUENCE {

bundleSize-r16 ENUMERATED { n4, wideband } OPTIONAL — Need S

},

dynamicBundling-r16 SEQUENCE {

bundleSizeSet1-r16 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, — Need S

bundleSizeSet2-r16 ENUMERATED { n4, wideband } OPTIONAL — Need S

}

} OPTIONAL, — Need R

priorityIndicatorDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, — Need S

rateMatchPatternGroup1DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, — Need R

rateMatchPatternGroup2DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, — Need R

resourceAllocationType1GranularityDCI-1-2-r16 ENUMERATED {n2,n4,n8,n16} OPTIONAL, — Need S

vrb-ToPRB-InterleaverDCI-1-2-r16 ENUMERATED {n2, n4} OPTIONAL, — Need S

referenceOfSLIVDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, — Need S

resourceAllocationDCI-1-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch}

OPTIONAL, — Need M

— End of the parameters for DCI format 1_2 introduced in V16.1.0

priorityIndicatorDCI-1-1-r16 ENUMERATED {enabled} OPTIONAL, — Need S

dataScramblingIdentityPDSCH2-r16 INTEGER (0..1023) OPTIONAL, — Need R

pdsch-TimeDomainAllocationList-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, — Need M

repetitionSchemeConfig-r16 SetupRelease { RepetitionSchemeConfig-r16} OPTIONAL — Need M

]],

[[

repetitionSchemeConfig-v1630 SetupRelease { RepetitionSchemeConfig-v1630} OPTIONAL — Need M

]],

[[

pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pdsch-HARQ-ACK-EnhType3DCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pdsch-HARQ-ACK-EnhType3DCI-Field-1-2-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pdsch-HARQ-ACK-RetxDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pucch-sSCellDynDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, — Need R

dl-OrJoint-TCIStateList-r17 CHOICE {

explicitlist SEQUENCE {

dl-OrJoint-TCI-State-ToAddModList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-State

OPTIONAL, — Need N

dl-OrJoint-TCI-State-ToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-StateId

OPTIONAL — Need N

},

unifiedTCI-StateRef-r17 ServingCellAndBWP-Id-r17

} OPTIONAL, — Need R

beamAppTime-r17 ENUMERATED {n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336, spare2,

spare1} OPTIONAL, — Need R

pdsch-TimeDomainAllocationListForMultiPDSCH-r17 SetupRelease { MultiPDSCH-TDRA-List-r17 } OPTIONAL, — Need M

dmrs-FD-OCC-DisabledForRank1-PDSCH-r17 ENUMERATED {true} OPTIONAL, — Need R

minimumSchedulingOffsetK0-r17 SetupRelease { MinSchedulingOffsetK0-Values-r17 } OPTIONAL, — Need M

harq-ProcessNumberSizeDCI-1-2-v1700 INTEGER (0..5) OPTIONAL, — Need R

harq-ProcessNumberSizeDCI-1-1-r17 INTEGER (5) OPTIONAL, — Need R

mcs-Table-r17 ENUMERATED {qam1024} OPTIONAL, — Need R

mcs-TableDCI-1-2-r17 ENUMERATED {qam1024} OPTIONAL, — Need R

xOverheadMulticast-r17 ENUMERATED {xOh6, xOh12, xOh18} OPTIONAL, — Need S

priorityIndicatorDCI-4-2-r17 ENUMERATED {enabled} OPTIONAL, — Need S

sizeDCI-4-2-r17 INTEGER (20..maxDCI-4-2-Size-r17) OPTIONAL — Need R

]]

}

RateMatchPatternGroup ::= SEQUENCE (SIZE (1..maxNrofRateMatchPatternsPerGroup)) OF CHOICE {

cellLevel RateMatchPatternId,

bwpLevel RateMatchPatternId

}

MinSchedulingOffsetK0-Values-r16 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK0-SchedulingOffset-r16)

MinSchedulingOffsetK0-Values-r17 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK0-SchedulingOffset-r17)

MaxMIMO-LayersDL-r16 ::= INTEGER (1..8)

— TAG-PDSCH-CONFIG-STOP

— ASN1STOP

PDSCH-Config field descriptions

antennaPortsFieldPresenceDCI-1-2 Configure the presence of "Antenna ports" field in DCI format 1_2. When the field is configured, then the "Antenna ports" field is present in DCI format 1_2. Otherwise, the field size is set to 0 for DCI format 1_2 (See TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 nor dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 is configured, this field is absent.

aperiodic-ZP-CSI-RS-ResourceSetsToAddModList, aperiodic-ZP-CSI-RS-ResourceSetsToAddModListDCI-1-2 AddMod/Release lists for configuring aperiodically triggered zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList). The network configures the UE with at most 3 aperiodic ZP-CSI-RS-ResourceSets and it uses only the ZP-CSI-RS-ResourceSetId 1 to 3. The network triggers a set by indicating its ZP-CSI-RS-ResourceSetId in the DCI payload. The DCI codepoint ’01’ triggers the resource set with ZP-CSI-RS-ResourceSetId 1, the DCI codepoint ’10’ triggers the resource set with ZP-CSI-RS-ResourceSetId 2, and the DCI codepoint ’11’ triggers the resource set with ZP-CSI-RS-ResourceSetId 3 (see TS 38.214 [19], clause 5.1.4.2). The field aperiodic-ZP-CSI-RS-ResourceSetsToAddModList applies to DCI format 1_1 and the field aperiodic-ZP-CSI-RS-ResourceSetsToAddModListDCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.2 and TS 38.212 [17] clause 7.3.1).

beamAppTime Indicates the first slot to apply the unified TCI indicated by DCI as specified in TS 38.214 Clause 5.1.5. The value n1 means 1 symbol, n2 two symbols and so on. The first slot is at least Y symbols indicated by beamAppTime parameter after the last symbol of the acknowledgment of the joint or separate DL/UL beam indication. The same value shall be configured for all serving cells in any one of the simultaneousU-TCI-UpdateListN configured in IE CellGroupConfig based on the smallest SCS of the active BWP.

dataScramblingIdentityPDSCH, dataScramblingIdentityPDSCH2 Identifier(s) used to initialize data scrambling (c_init) for PDSCH as specified in TS 38.211 [16], clause 7.3.1.1. The dataScramblingIdentityPDSCH2 is configured if coresetPoolIndex is configured with 1 for at least one CORESET in the same BWP.

dl-OrJoint-TCI-State-ToAddModList A list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports (see TS 38.214 [19], clause 5.1.5).

dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 DMRS configuration for PDSCH transmissions using PDSCH mapping type A (chosen dynamically via PDSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeA applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1).

dmrs-DownlinkForPDSCH-MappingTypeB, dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 DMRS configuration for PDSCH transmissions using PDSCH mapping type B (chosen dynamically via PDSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeB applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1).

dmrs-FD-OCC-DisabledForRank1-PDSCH If configured, the UE may assume that the set of remaining orthogonal antenna ports, which are within the same code division multiplexing (CDM) group and have different frequency domain orthogonal cover codes (FD-OCC), are not associated with the PDSCH of another UE (see TS 38.214 [19], clause 5.1.6.2). It is applicable for PDSCH SCS of 480 and 960 kHz when rank 1 PDSCH with type-1 or type-2 DMRS is scheduled.

dmrs-SequenceInitializationDCI-1_2 Configure whether the field "DMRS Sequence Initialization" is present or not in DCI format 1_2 If the field is absent, then the UE applies the value of 0 bit for the field "DMRS Sequence Initialization" in DCI format 1_2. If the field is present, then the UE applies the value of 1 bit as in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1).

harq-ProcessNumberSizeDCI-1-2 Configure the number of bits for the field "HARQ process number" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1).

maxMIMO-Layers Indicates the maximum number of MIMO layers to be used for PDSCH in this DL BWP. If not configured, the UE uses the maxMIMO-Layers configuration in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs, when the UE operates in this BWP. The value of maxMIMO-Layers for a DL BWP shall be smaller than or equal to the value of maxMIMO-Layers configured in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs. For MBS multicast, indicates the maximum number of MIMO layers to be used for group-common PDSCH of MBS multicast in this CFR. If not configured for CFR, the UE applies value 1. The value of maxMIMO-Layers for a CFR shall be smaller than or equal to the value of maxMIMO-Layers configured in PDSCH-ServingCellConfig IE of the serving cell to which this CFR belongs.

maxNrofCodeWordsScheduledByDCI Maximum number of code words that a single DCI may schedule. This changes the number of MCS/RV/NDI bits in the DCI message from 1 to 2.

mcs-Table Indicates which MCS table the UE shall use for PDSCH for DCI formats 1_0 and 1_1 (see TS 38.214 [19], clause 5.1.3.1). If all fields are absent the UE applies the value 64QAM. If the field mcs-Table-r17 is present for DCI format 1_1, the network does not configure the field mcs-Table (without suffix). For a RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH.

mcs-TableDCI-1-2 Indicates which MCS table the UE shall use for PDSCH for DCI format 1_2 (see TS 38.214 [19], clause 5.1.3.1). If all fields are absent the UE applies the value 64QAM. If the field mcs-TableDCI-1-2-r17 is present, the network does not configure the field mcs-TableDCI-1-2-r16. For a RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH.

minimumSchedulingOffsetK0 List of minimum K0 values. Minimum K0 parameter denotes minimum applicable value(s) for the TDRA table for PDSCH and for A-CSI RS triggering Offset(s) (see TS 38.214 [19], clause 5.3.1).

numberOfBitsForRV-DCI-1-2 Configures the number of bits for "Redundancy version" in the DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.1).

pdsch-AggregationFactor Number of repetitions for data (see TS 38.214 [19], clause 5.1.2.1). When the field is absent in PDSCH-Config which is not used for MBS CFR, the UE applies the value 1.

pdsch-HARQ-ACK-EnhType3DCI-1-2 When configured, enhanced Type 3 HARQ-ACK codebook triggering by DCI format 1_2 is enabled.

pdsch-HARQ-ACK-EnhType3DCI-Field-1-2 Enables the enhanced Type 3 codebook through a new DCI field to indicate the enhanced Type 3 HARQ-ACK codebook in DCI format 1_2 if the more than one enhanced Type 3 HARQ-ACK codebook is configured for the primary PUCCH cell group.

pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2 When configured, DCI format 1_2 can request the UE to report A/N for all HARQ processes and all component carriers configured in the PUCCH group (see TS 38.212 [17], clause 7.3.1).

pdsch-HARQ-ACK-RetxDCI-1-2 When configured, DCI format 1_2 can request the UE to perform a HARQ-ACK re-transmission on a PUCCH resource (see TS 38.213 [13], clause 9.1.5).

pdsch-TimeDomainAllocationList, pdsch-TimeDomainAllocationListDCI-1-2, pdsch-TimeDomainAllocationListForMultiPDSCH List of time-domain configurations for timing of DL assignment to DL data. The field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0 and DCI format 1_1 (see table 5.1.2.1.1-1 in TS 38.214 [19]), and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2 is configured, it applies to DCI format 1_2 (see table 5.1.2.1.1-1A in TS 38.214 [19]). The field pdsch-TimeDomainAllocationListForMultiPDSCH applies to DCI format 1_1. The network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config.

prb-BundlingType, prb-BundlingTypeDCI-1-2 Indicates the PRB bundle type and bundle size(s) (see TS 38.214 [19], clause 5.1.2.3). If dynamic is chosen, the actual bundleSizeSet1 or bundleSizeSet2 to use is indicated via DCI. Constraints on bundleSize(Set) setting depending on vrb-ToPRB-Interleaver and rbg-Size settings are described in TS 38.214 [19], clause 5.1.2.3. If a bundleSize(Set) value is absent, the UE applies the value n2. The field prb-BundlingType applies to DCI format 1_1, and the field prb-BundlingTypeDCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.3).

priorityIndicatorDCI-1-1, priorityIndicatorDCI-1-2, priorityIndicatorDCI-4-2 Configure the presence of "priority indicator" in DCI format 1_1/1_2/4_2. When the field is absent in the IE, then 0 bit for "priority indicator" in DCI format 1_1/1_2/4_2. The field priorityIndicatorDCI-1-1 applies to DCI format 1_1, the field priorityIndicatorDCI-1-2 applies to DCI format 1_2 and the field priorityIndicatorDCI-4-2 applies to DCI format 4_2, respectively (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9).

pucch-sSCellDynDCI-1-2 When configured, PUCCH cell switching based on dynamic indication in DCI format 1_2 is enabled (see TS 38.213 [13], clause 9.A).

p-ZP-CSI-RS-ResourceSet A set of periodically occurring ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList). The network uses the ZP-CSI-RS-ResourceSetId=0 for this set. If p-ZP-CSI-RS-ResourceSet is configured in both PDSCH-Config for MBS CFR and PDSCH-Config for the assoicated BWP, it is subject to UE capability whether the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config for MBS CFR can be different from the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config for the assoicated BWP.

rateMatchPatternGroup1, rateMatchPatternGroup1DCI-1-2 The IDs of a first group of RateMatchPatterns defined in PDSCH-Config->rateMatchPatternToAddModList (BWP level) or in ServingCellConfig ->rateMatchPatternToAddModList (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup1 applies to DCI format 1_1, and the field rateMatchPatternGroup1DCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1).

rateMatchPatternGroup2, rateMatchPatternGroup2DCI-1-2 The IDs of a second group of RateMatchPatterns defined in PDSCH-Config->rateMatchPatternToAddModList (BWP level) or in ServingCellConfig ->rateMatchPatternToAddModList (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup2 applies to DCI format 1_1, and the field rateMatchPatternGroup2DCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1).

rateMatchPatternToAddModList Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns (see TS 38.214 [19], clause 5.1.4.1). If a RateMatchPattern with the same RateMatchPatternId is configured in both MBS CFR and its associated BWP, the entire RateMatchPattern configuration, including the set of RBs/REs indicated by the patterns for the rate matching around, shall be the same and they are counted as a single rate match pattern in the total configured rate match patterns as defined in TS 38.214 [19].

rbg-Size Selection between config 1 and config 2 for RBG size for PDSCH. The UE ignores this field if resourceAllocation is set to resourceAllocationType1 (see TS 38.214 [19], clause 5.1.2.2.1).

referenceOfSLIVDCI-1-2 Enable using the starting symbol of the PDCCH monitoring occasion in which the DL assignment is detected as the reference of the SLIV for DCI format 1_2. When the RRC parameter enables the utilization of the new reference, the new reference is applied for TDRA entries with K0=0. For other entries (if any) in the same TDRA table, the reference is slot boundary as in Rel-15. PDSCH mapping type A is not supported with the new reference. The new reference of SLIV is not configured for a serving cell configured to be scheduled by cross-carrier scheduling on a scheduling cell with different numerology (see TS 38.212 [17] clause 7.3.1 and TS 38.214 [19] clause 5.1.2.1).

repetitionSchemeConfig Configure the UE with repetition schemes. The network does not configure repetitionSchemeConfig-r16 and repetitionSchemeConfig-v1630 simultaneously to setup in the same PDSCH-Config.

resourceAllocation, resourceAllocationDCI-1-2 Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 5.1.2.2). The field resourceAllocation applies to DCI format 1_1, and the field resourceAllocationDCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.2.2).

resourceAllocationType1GranularityDCI-1-2 Configure the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 1_2. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 5.1.2.2.2).

sizeDCI-4-2 Indicates the size of DCI format 4-2 (see TS 38.213 [13], clause 10.1).

sp-ZP-CSI-RS-ResourceSetsToAddModList AddMod/Release lists for configuring semi-persistent zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList) (see TS 38.214 [19], clause 5.1.4.2).

tci-StatesToAddModList A list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports (see TS 38.214 [19], clause 5.1.5).

unifiedTCI-StateRef Provides the serving cell and BWP where the configuration for dl-OrJoint-TCI-State-ToAddModList-r17 in this IE for this serving cell and BWP. When this field is present, dl-OrJoint-TCI-State-ToAddModList and dl-OrJoint-TCI-State-ToReleaseList are not present.

vrb-ToPRB-Interleaver, vrb-ToPRB-InterleaverDCI-1-2 Interleaving unit configurable between 2 and 4 PRBs (see TS 38.211 [16], clause 7.3.1.6). When the field is absent, the UE performs non-interleaved VRB-to-PRB mapping.

xOverheadMulticast Accounts for an overhead from CSI-RS, CORESET etc. If the field is absent, the UE applies value xOh0 (see TS 38.214 [19]).

zp-CSI-RS-ResourceToAddModList A list of Zero-Power (ZP) CSI-RS resources used for PDSCH rate-matching. Each resource in this list may be referred to from only one type of resource set, i.e., aperiodic, semi-persistent or periodic (see TS 38.214 [19]).

– PDSCH-ConfigCommon

The IE PDSCH-ConfigCommon is used to configure cell specific PDSCH parameters.

PDSCH-ConfigCommon information element

— ASN1START

— TAG-PDSCH-CONFIGCOMMON-START

PDSCH-ConfigCommon ::= SEQUENCE {

pdsch-TimeDomainAllocationList PDSCH-TimeDomainResourceAllocationList OPTIONAL, — Need R

…

}

— TAG-PDSCH-CONFIGCOMMON-STOP

— ASN1STOP

PDSCH-ConfigCommon field descriptions

pdsch-TimeDomainAllocationList List of time-domain configurations for timing of DL assignment to DL data (see table 5.1.2.1.1-1 in TS 38.214 [19]).

– PDSCH-ServingCellConfig

The IE PDSCH-ServingCellConfig is used to configure UE specific PDSCH parameters that are common across the UE’s BWPs of one serving cell.

PDSCH-ServingCellConfig information element

— ASN1START

— TAG-PDSCH-SERVINGCELLCONFIG-START

PDSCH-ServingCellConfig ::= SEQUENCE {

codeBlockGroupTransmission SetupRelease { PDSCH-CodeBlockGroupTransmission } OPTIONAL, — Need M

xOverhead ENUMERATED { xOh6, xOh12, xOh18 } OPTIONAL, — Need S

nrofHARQ-ProcessesForPDSCH ENUMERATED {n2, n4, n6, n10, n12, n16} OPTIONAL, — Need S

pucch-Cell ServCellIndex OPTIONAL, — Cond SCellAddOnly

…,

[[

maxMIMO-Layers INTEGER (1..8) OPTIONAL, — Need M

processingType2Enabled BOOLEAN OPTIONAL — Need M

]],

[[

pdsch-CodeBlockGroupTransmissionList-r16 SetupRelease { PDSCH-CodeBlockGroupTransmissionList-r16 } OPTIONAL — Need M

]],

[[

downlinkHARQ-FeedbackDisabled-r17 SetupRelease { DownlinkHARQ-FeedbackDisabled-r17 } OPTIONAL, — Need M

nrofHARQ-ProcessesForPDSCH-v1700 ENUMERATED {n32} OPTIONAL — Need R

]]

}

PDSCH-CodeBlockGroupTransmission ::= SEQUENCE {

maxCodeBlockGroupsPerTransportBlock ENUMERATED {n2, n4, n6, n8},

codeBlockGroupFlushIndicator BOOLEAN,

…

}

PDSCH-CodeBlockGroupTransmissionList-r16 ::= SEQUENCE (SIZE (1..2)) OF PDSCH-CodeBlockGroupTransmission

DownlinkHARQ-FeedbackDisabled-r17 ::= BIT STRING (SIZE (32))

— TAG-PDSCH-SERVINGCELLCONFIG-STOP

— ASN1STOP

PDSCH-CodeBlockGroupTransmission field descriptions

codeBlockGroupFlushIndicator Indicates whether CBGFI for CBG based (re)transmission in DL is enabled (true). (see TS 38.212 [17], clause 7.3.1.2.2).

maxCodeBlockGroupsPerTransportBlock Maximum number of code-block-groups (CBGs) per TB. In case of multiple CW, the maximum CBG is 4 (see TS 38.213 [13], clause 9.1.1).

PDSCH-ServingCellConfig field descriptions

codeBlockGroupTransmission Enables and configures code-block-group (CBG) based transmission (see TS 38.213 [13], clause 9.1.1). Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. The network does not configure this field if – the SCS is 480 or 960 kHz – Type-1 HARQ-ACK codebook is configured and pdsch-TimeDomainAllocationListForMultiPDSCH-r17 for this serving cell contains pdsch-AllocationList with multiple entries (multiple PDSCH) – Type-2 HARQ-ACK codebook is configured and pdsch-TimeDomainAllocationListForMultiPDSCH-r17 for any cell in the same PUCCH cell group associated with this serving cell contains pdsch-AllocationList with multiple entries (multiple PDSCH)

downlinkHARQ-FeedbackDisabled Used to disable the DL HARQ feedback, sent in the uplink, per HARQ process ID. The first/leftmost bit corresponds to HARQ process ID 0, the next bit to HARQ process ID 1 and so on. Bits corresponding to HARQ process IDs that are not configured shall be ignored. The bit(s) set to one identify HARQ processes with disabled DL HARQ feedback and the bit(s) set to zero identify HARQ processes with enabled DL HARQ feedback.

maxMIMO-Layers Indicates the maximum number of MIMO layers to be used for PDSCH in all BWPs of this serving cell. (see TS 38.212 [17], clause 5.4.2.1).

nrofHARQ-ProcessesForPDSCH The number of HARQ processes to be used on the PDSCH of a serving cell. Value n2 corresponds to 2 HARQ processes, value n4 to 4 HARQ processes, and so on. If both nrofHARQ-ProcessesForPDSCH and nrofHARQ-ProcessesForPDSCH-v1700 are absent, the UE uses 8 HARQ processes (see TS 38.214 [19], clause 5.1).

pdsch-CodeBlockGroupTransmissionList A list of configurations for up to two simultaneously constructed HARQ-ACK codebooks (see TS 38.213 [13], clause 9.3).

processingType2Enabled Enables configuration of advanced processing time capability 2 for PDSCH (see 38.214 [19], clause 5.3).

pucch-Cell The ID of the serving cell (of the same cell group) to use for PUCCH. If the field is absent, the UE sends the HARQ feedback on the PUCCH of the SpCell of this cell group, or on this serving cell if it is a PUCCH SCell.

xOverhead Accounts for overhead from CSI-RS, CORESET, etc. If the field is absent, the UE applies value xOh0 (see TS 38.214 [19], clause 5.1.3.2).

Conditional Presence	Explanation
SCellAddOnly	It is optionally present, Need S, for (non-PUCCH) SCells when adding a new SCell. The field is absent, Need M, when reconfiguring SCells. The field is also absent for the SpCells as well as for a PUCCH SCell.

– PDSCH-TimeDomainResourceAllocationList

The IE PDSCH-TimeDomainResourceAllocation is used to configure a time domain relation between PDCCH and PDSCH. The PDSCH-TimeDomainResourceAllocationList contains one or more of such PDSCH-TimeDomainResourceAllocations. The network indicates in the DL assignment which of the configured time domain allocations the UE shall apply for that DL assignment. The UE determines the bit width of the DCI field based on the number of entries in the PDSCH-TimeDomainResourceAllocationList. Value 0 in the DCI field refers to the first element in this list, value 1 in the DCI field refers to the second element in this list, and so on.

PDSCH-TimeDomainResourceAllocationList information element

— ASN1START

— TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation

PDSCH-TimeDomainResourceAllocation ::= SEQUENCE {

k0 INTEGER(0..32) OPTIONAL, — Need S

mappingType ENUMERATED {typeA, typeB},

startSymbolAndLength INTEGER (0..127)

}

PDSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation-r16

PDSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE {

k0-r16 INTEGER(0..32) OPTIONAL, — Need S

mappingType-r16 ENUMERATED {typeA, typeB},

startSymbolAndLength-r16 INTEGER (0..127),

repetitionNumber-r16 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL, — Cond Formats1-0and1-1

…,

[[

k0-v1710 INTEGER(33..128) OPTIONAL — Need S

]]

}

MultiPDSCH-TDRA-List-r17 ::= SEQUENCE (SIZE(1.. maxNrofDL-Allocations)) OF MultiPDSCH-TDRA-r17

MultiPDSCH-TDRA-r17 ::= SEQUENCE {

pdsch-TDRA-List-r17 SEQUENCE (SIZE(1..maxNrofMultiplePDSCHs-r17)) OF PDSCH-TimeDomainResourceAllocation-r16,

…

}

— TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

— ASN1STOP

PDSCH-TimeDomainResourceAllocation field descriptions

k0 Slot offset between DCI and its scheduled PDSCH (see TS 38.214 [19], clause 5.1.2.1). k0-v1710 is only applicable for PDSCH SCS of 480 kHz and 960 kHz. When the field is absent the UE applies the value 0.

mappingType PDSCH mapping type (see TS 38.214 [19], clause 5.3).

repetitionNumber Indicates the number of PDSCH transmission occasions for slot-based repetition scheme in IE RepetitionSchemeConfig. The parameter is used as specified in 38.214 [19].

startSymbolAndLength An index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary (see TS 38.214 [19], clause 5.1.2.1).

MultiPDSCH-TimeDomainResourceAllocation field descriptions

pdsch-TDRA-List One or multiple PDSCHs which can be in consecutive or non-consecutive slots (see TS 38.214 [19], clause 5.1.2.1).

Conditional Presence	Explanation
Formats1-0and1-1	In pdsch-TimeDomainAllocationListDCI-1-2, pdsch-TimeDomainAllocationListForMultiPDSCH, and SIB20, this field is absent. Otherwise, in pdsch-TimeDomainResourceAllocationList-r16 and pdsch-TimeDomainResourceAllocationList-r17, this field is optionally present, Need R.

– PHR-Config

The IE PHR-Config is used to configure parameters for power headroom reporting.

PHR-Config information element

— ASN1START

— TAG-PHR-CONFIG-START

PHR-Config ::= SEQUENCE {

phr-PeriodicTimer ENUMERATED {sf10, sf20, sf50, sf100, sf200,sf500, sf1000, infinity},

phr-ProhibitTimer ENUMERATED {sf0, sf10, sf20, sf50, sf100,sf200, sf500, sf1000},

phr-Tx-PowerFactorChange ENUMERATED {dB1, dB3, dB6, infinity},

multiplePHR BOOLEAN,

dummy BOOLEAN,

phr-Type2OtherCell BOOLEAN,

phr-ModeOtherCG ENUMERATED {real, virtual},

…,

[[

mpe-Reporting-FR2-r16 SetupRelease { MPE-Config-FR2-r16 } OPTIONAL — Need M

]],

[[

mpe-Reporting-FR2-r17 SetupRelease { MPE-Config-FR2-r17 } OPTIONAL, — Need M

twoPHRMode-r17 ENUMERATED {enabled} OPTIONAL — Need R

]]

}

MPE-Config-FR2-r16 ::= SEQUENCE {

mpe-ProhibitTimer-r16 ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200, sf500, sf1000},

mpe-Threshold-r16 ENUMERATED {dB3, dB6, dB9, dB12}

}

MPE-Config-FR2-r17 ::= SEQUENCE {

mpe-ProhibitTimer-r17 ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200, sf500, sf1000},

mpe-Threshold-r17 ENUMERATED {dB3, dB6, dB9, dB12},

numberOfN-r17 INTEGER(1..4),

…

}

— TAG-PHR-CONFIG-STOP

— ASN1STOP

PHR-Config field descriptions

dummy This field is not used in this version of the specification and the UE ignores the received value.

mpe-ProhibitTimer Value in number of subframes for MPE reporting, as specified in TS 38.321 [3]. Value sf10 corresponds to 10 subframes, and so on.

mpe-Reporting-FR2 Indicates whether the UE shall report MPE P-MPR in the PHR MAC control element, as specified in TS 38.321 [3].

mpe-Threshold Value of the P-MPR threshold in dB for reporting MPE P-MPR when FR2 is configured, as specified in TS 38.321 [3]. The same value applies for each serving cell (although the associated functionality is performed independently for each cell).

multiplePHR Indicates if power headroom shall be reported using the Single Entry PHR MAC control element or Multiple Entry PHR MAC control element defined in TS 38.321 [3]. True means to use Multiple Entry PHR MAC control element and False means to use the Single Entry PHR MAC control element defined in TS 38.321 [3]. The network configures this field to true for MR-DC and UL CA for NR, and to false in all other cases.

numberOfN Number of reported P-MPR values in a PHR MAC CE.

phr-ModeOtherCG Indicates the mode (i.e. real or virtual) used for the PHR of the activated cells that are part of the other Cell Group (i.e. MCG or SCG), when DC is configured. If the UE is configured with only one cell group (no DC), it ignores the field.

phr-PeriodicTimer Value in number of subframes for PHR reporting as specified in TS 38.321 [3]. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on.

phr-ProhibitTimer Value in number of subframes for PHR reporting as specified in TS 38.321 [3]. Value sf0 corresponds to 0 subframe, value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on.

phr-Tx-PowerFactorChange Value in dB for PHR reporting as specified in TS 38.321 [3]. Value dB1 corresponds to 1 dB, dB3 corresponds to 3 dB and so on. The same value applies for each serving cell (although the associated functionality is performed independently for each cell).

phr-Type2OtherCell If set to true, the UE shall report a PHR type 2 for the SpCell of the other MAC entity. See TS 38.321 [3], clause 5.4.6. Network sets this field to false if the UE is not configured with an E-UTRA MAC entity.

twoPHRMode Indicates if the power headroom shall be reported as two PHRs (each PHR associated with a SRS resource set) is enabled or not.

– PhysCellId

The PhysCellId identifies the physical cell identity (PCI).

PhysCellId information element

— ASN1START

— TAG-PHYSCELLID-START

PhysCellId ::= INTEGER (0..1007)

— TAG-PHYSCELLID-STOP

— ASN1STOP

– PhysicalCellGroupConfig

The IE PhysicalCellGroupConfig is used to configure cell-group specific L1 parameters.

PhysicalCellGroupConfig information element

— ASN1START

— TAG-PHYSICALCELLGROUPCONFIG-START

PhysicalCellGroupConfig ::= SEQUENCE {

harq-ACK-SpatialBundlingPUCCH ENUMERATED {true} OPTIONAL, — Need S

harq-ACK-SpatialBundlingPUSCH ENUMERATED {true} OPTIONAL, — Need S

p-NR-FR1 P-Max OPTIONAL, — Need R

pdsch-HARQ-ACK-Codebook ENUMERATED {semiStatic, dynamic},

tpc-SRS-RNTI RNTI-Value OPTIONAL, — Need R

tpc-PUCCH-RNTI RNTI-Value OPTIONAL, — Need R

tpc-PUSCH-RNTI RNTI-Value OPTIONAL, — Need R

sp-CSI-RNTI RNTI-Value OPTIONAL, — Need R

cs-RNTI SetupRelease { RNTI-Value } OPTIONAL, — Need M

…,

[[

mcs-C-RNTI RNTI-Value OPTIONAL, — Need R

p-UE-FR1 P-Max OPTIONAL — Cond MCG-Only

]],

[[

xScale ENUMERATED {dB0, dB6, spare2, spare1} OPTIONAL — Cond SCG-Only

]],

[[

pdcch-BlindDetection SetupRelease { PDCCH-BlindDetection } OPTIONAL — Need M

]],

[[

dcp-Config-r16 SetupRelease { DCP-Config-r16 } OPTIONAL, — Need M

harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup-r16 ENUMERATED {enabled, disabled} OPTIONAL, — Cond twoPUCCHgroup

harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup-r16 ENUMERATED {enabled, disabled} OPTIONAL, — Cond twoPUCCHgroup

pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16 ENUMERATED {semiStatic, dynamic} OPTIONAL, — Cond twoPUCCHgroup

p-NR-FR2-r16 P-Max OPTIONAL, — Need R

p-UE-FR2-r16 P-Max OPTIONAL, — Cond MCG-Only

nrdc-PCmode-FR1-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, — Cond MCG-Only

nrdc-PCmode-FR2-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, — Cond MCG-Only

pdsch-HARQ-ACK-Codebook-r16 ENUMERATED {enhancedDynamic} OPTIONAL, — Need R

nfi-TotalDAI-Included-r16 ENUMERATED {true} OPTIONAL, — Need R

ul-TotalDAI-Included-r16 ENUMERATED {true} OPTIONAL, — Need R

pdsch-HARQ-ACK-OneShotFeedback-r16 ENUMERATED {true} OPTIONAL, — Need R

pdsch-HARQ-ACK-OneShotFeedbackNDI-r16 ENUMERATED {true} OPTIONAL, — Need R

pdsch-HARQ-ACK-OneShotFeedbackCBG-r16 ENUMERATED {true} OPTIONAL, — Need R

downlinkAssignmentIndexDCI-0-2-r16 ENUMERATED { enabled } OPTIONAL, — Need S

downlinkAssignmentIndexDCI-1-2-r16 ENUMERATED {n1, n2, n4} OPTIONAL, — Need S

pdsch-HARQ-ACK-CodebookList-r16 SetupRelease {PDSCH-HARQ-ACK-CodebookList-r16} OPTIONAL, — Need M

ackNackFeedbackMode-r16 ENUMERATED {joint, separate} OPTIONAL, — Need R

pdcch-BlindDetectionCA-CombIndicator-r16 SetupRelease { PDCCH-BlindDetectionCA-CombIndicator-r16 } OPTIONAL, — Need M

pdcch-BlindDetection2-r16 SetupRelease { PDCCH-BlindDetection2-r16 } OPTIONAL, — Need M

pdcch-BlindDetection3-r16 SetupRelease { PDCCH-BlindDetection3-r16 } OPTIONAL, — Need M

bdFactorR-r16 ENUMERATED {n1} OPTIONAL — Need R

]],

[[

— start of enhanced Type3 feedback

pdsch-HARQ-ACK-EnhType3ToAddModList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3-r17

OPTIONAL, — Need N

pdsch-HARQ-ACK-EnhType3ToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3Index-r17

OPTIONAL, — Need N

pdsch-HARQ-ACK-EnhType3SecondaryToAddModList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3-r17

OPTIONAL, — Need N

pdsch-HARQ-ACK-EnhType3SecondaryToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3Index-r17

OPTIONAL, — Need N

pdsch-HARQ-ACK-EnhType3DCI-FieldSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, — Cond twoPUCCHgroup

pdsch-HARQ-ACK-EnhType3DCI-Field-r17 ENUMERATED {enabled} OPTIONAL, — Need R

— end of enhanced Type3 feedback

— start of triggering of HARQ-ACK re-transmission on a PUCCH resource

pdsch-HARQ-ACK-Retx-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, — Cond twoPUCCHgroup

— end of triggering of HARQ-ACK re-transmission on a PUCCH resource

— start of PUCCH Cell switching

pucch-sSCell-r17 SCellIndex OPTIONAL, — Need R

pucch-sSCellSecondaryPUCCHgroup-r17 SCellIndex OPTIONAL, — Cond twoPUCCHgroup

pucch-sSCellDyn-r17 ENUMERATED {enabled} OPTIONAL, — Need R

pucch-sSCellDynSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, — Cond twoPUCCHgroup

pucch-sSCellPattern-r17 SEQUENCE (SIZE(1..maxNrofSlots)) OF INTEGER (0..1) OPTIONAL, — Need R

pucch-sSCellPatternSecondaryPUCCHgroup-r17 SEQUENCE (SIZE(1..maxNrofSlots)) OF INTEGER (0..1) OPTIONAL, — Cond twoPUCCHgroup

— end of PUCCH Cell switching

uci-MuxWithDiffPrio-r17 ENUMERATED {enabled} OPTIONAL, — Need R

uci-MuxWithDiffPrioSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, — Cond twoPUCCHgroup

simultaneousPUCCH-PUSCH-r17 ENUMERATED {enabled} OPTIONAL, — Need R

simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, — Cond twoPUCCHgroup

prioLowDG-HighCG-r17 ENUMERATED {enabled} OPTIONAL, — Need R

prioHighDG-LowCG-r17 ENUMERATED {enabled} OPTIONAL, — Need R

twoQCLTypeDforPDCCHRepetition-r17 ENUMERATED {enabled} OPTIONAL, — Need R

multicastConfig-r17 SetupRelease { MulticastConfig-r17 } OPTIONAL, — Need M

pdcch-BlindDetectionCA-CombIndicator-r17 SetupRelease { PDCCH-BlindDetectionCA-CombIndicator-r17 } OPTIONAL — Need M

]],

[[

simultaneousSR-PUSCH-diffPUCCH-Groups-r17 ENUMERATED {enabled} OPTIONAL — Cond twoPUCCHgroup

]]

}

PDSCH-HARQ-ACK-EnhType3-r17 ::= SEQUENCE {

pdsch-HARQ-ACK-EnhType3Index-r17 PDSCH-HARQ-ACK-EnhType3Index-r17,

applicable-r17 CHOICE {

perCC SEQUENCE (SIZE (1..maxNrofServingCells)) OF INTEGER (0..1),

perHARQ SEQUENCE (SIZE (1..maxNrofServingCells)) OF BIT STRING (SIZE (16))

},

pdsch-HARQ-ACK-EnhType3NDI-r17 ENUMERATED {true} OPTIONAL, — Need R

pdsch-HARQ-ACK-EnhType3CBG-r17 ENUMERATED {true} OPTIONAL, — Need S

…

}

PDSCH-HARQ-ACK-EnhType3Index-r17 ::= INTEGER (0..maxNrofEnhType3HARQ-ACK-1-r17)

PDCCH-BlindDetection ::= INTEGER (1..15)

DCP-Config-r16 ::= SEQUENCE {

ps-RNTI-r16 RNTI-Value,

ps-Offset-r16 INTEGER (1..120),

sizeDCI-2-6-r16 INTEGER (1..maxDCI-2-6-Size-r16),

ps-PositionDCI-2-6-r16 INTEGER (0..maxDCI-2-6-Size-1-r16),

ps-WakeUp-r16 ENUMERATED {true} OPTIONAL, — Need S

ps-TransmitPeriodicL1-RSRP-r16 ENUMERATED {true} OPTIONAL, — Need S

ps-TransmitOtherPeriodicCSI-r16 ENUMERATED {true} OPTIONAL — Need S

}

PDSCH-HARQ-ACK-CodebookList-r16 ::= SEQUENCE (SIZE (1..2)) OF ENUMERATED {semiStatic, dynamic}

PDCCH-BlindDetectionCA-CombIndicator-r16 ::= SEQUENCE {

pdcch-BlindDetectionCA1-r16 INTEGER (1..15),

pdcch-BlindDetectionCA2-r16 INTEGER (1..15)

}

PDCCH-BlindDetection2-r16 ::= INTEGER (1..15)

PDCCH-BlindDetection3-r16 ::= INTEGER (1..15)

MulticastConfig-r17 ::= SEQUENCE {

pdsch-HARQ-ACK-CodebookListMulticast-r17 SetupRelease { PDSCH-HARQ-ACK-CodebookList-r16} OPTIONAL, — Need M

type1-Codebook-GenerationMode-r17 ENUMERATED { mode1, mode2} OPTIONAL — Need M

}

PDCCH-BlindDetectionCA-CombIndicator-r17 ::= SEQUENCE {

pdcch-BlindDetectionCA1-r17 INTEGER (1..15) OPTIONAL, — Need R

pdcch-BlindDetectionCA2-r17 INTEGER (1..15) OPTIONAL, — Need R

pdcch-BlindDetectionCA3-r17 INTEGER (1..15)

}

— TAG-PHYSICALCELLGROUPCONFIG-STOP

— ASN1STOP

PhysicalCellGroupConfig field descriptions

ackNackFeedbackMode Indicates which among the joint and separate ACK/NACK feedback modes to use within a slot as specified in TS 38.213 [13] (clause 9).

bdFactorR Parameter for determining and distributing the maximum numbers of BD/CCE for mPDCCH based mPDSCH transmission as specified in TS 38.213 [13] Clause 10.1.

cs-RNTI RNTI value for downlink SPS (see SPS-Config) and uplink configured grant (see ConfiguredGrantConfig).

downlinkAssignmentIndexDCI-0-2 Indicates if "Downlink assignment index" is present or absent in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is absent, then 0 bit for "Downlink assignment index" in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is present, then the bitwidth of "Downlink assignment index" in DCI format 0_2 is defined in the same was as that in DCI format 0_1 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.1).

downlinkAssignmentIndexDCI-1-2 Configures the number of bits for "Downlink assignment index" in DCI format 1_2. If the field is absent, then 0 bit for "Downlink assignment index" in DCI format 1_2. Note that 1 bit and 2 bits are applied if only one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic. 4 bits is applied if more than one serving cell are configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook is set to dynamic (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.1).

harq-ACK-SpatialBundlingPUCCH Enables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUCCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUCCH HARQ ACKs for the primary PUCCH group is disabled (see TS 38.213 [13], clause 9.1.2.1). If the field harq-ACK SpatialBundlingPUCCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUCCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.

harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup Indicates whether spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see TS 38.213 [13], clause 9.1.2.1). When the field is absent, the use of spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUCCH. See TS 38.213 [13], clause 9.1.2.1. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.

harq-ACK-SpatialBundlingPUSCH Enables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUSCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUSCH HARQ ACKs for the primary PUCCH group is disabled (see TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2). If the field harq-ACK SpatialBundlingPUSCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUSCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.

harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup Indicates whether spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2). When the field is absent, the use of spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUSCH. See TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.

mcs-C-RNTI RNTI to indicate use of qam64LowSE for grant-based transmissions. When the mcs–C-RNTI is configured, RNTI scrambling of DCI CRC is used to choose the corresponding MCS table.

nfi-TotalDAI-Included Indicates whether the NFI and total DAI fields of the non-scheduled PDSCH group is included in the non-fallback DL grant DCI (see TS 38.212 [17], clause 7.3.1). The network configures this only when enhanced dynamic codebook is configured (pdsch-HARQ-ACK-Codebook is set to enhancedDynamic).

nrdc-PCmode-FR1 Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 1 (FR1) (see TS 38.213 [13], clause 7.6).

nrdc-PCmode-FR2 Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 2 (FR2) (see TS 38.213 [13], clause 7.6).

pdcch-BlindDetection, pdcch-BlindDetection2, pdcch-BlindDetection3 Indicates the reference number of cells for PDCCH blind detection for the CG. Network configures the field for each CG when the UE is in NR DC and sets the value in accordance with the constraints specified in TS 38.213 [13]. The network configures pdcch-BlindDetection only if the UE is in NR-DC. The network configures pdcch-BlindDetection2 only if the UE is in NR-DC with at least one downlink cell using Rel-16 PDCCH monitoring capability. The network configures pdcch-BlindDetection3 only if the UE is in NR-DC with at least one downlink cell using Rel-15 PDCCH monitoring capability.

pdcch-BlindDetectionCA-CombIndicator Configure one combination of pdcch-BlindDetectionCA1 (for R15) and pdcch-BlindDetectionCA2 (for R16) for UE to use for scaling PDCCH monitoring capability if the number of serving cells configured to a UE is larger than the reported capability, and if UE reports more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 as UE capability. The combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2) configured by pdcch-BlindDetectionCACombIndicator is from the more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 reported by UE (see TS 38.213 [13], clause 10). pdcch-BlindDetectionCA-CombIndicator-r17 is used to configure one combination of pdcch-BlindDetectionCA1 (for R15), pdcch-BlindDetectionCA2 (for R16) and pdcch-BlindDetectionCA3 (for R17) for UE to use for scaling PDCCH monitoring capability if the number of serving cells configured to a UE is larger than the reported capability, and if UE reports more than one combination of pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2 and pdcch-BlindDetectionCA3 as UE capability. The combination of pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2 and pdcch-BlindDetectionCA3 configured by pdcch-BlindDetectionCACombIndicator-r17 is from the more than one combination of pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2 and pdcch-BlindDetectionCA3 reported by UE (see TS 38.213 [13], clause 10). pdcch-BlindDetectionCA-CombIndicator-r16 and pdcch-BlindDetectionCA-CombIndicator-r17 are not configured simultaneously.

p-NR-FR1 The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 1 (FR1). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-UE-FR1 (configured total for all serving cells operating on FR1).

p-NR-FR2 The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 2 (FR2). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-UE-FR2 (configured total for all serving cells operating on FR2). This field is only used in NR-DC. A UE does not expect to be configured with this parameter in this release of the specification.

prioLowDG-HighCG Enable PHY prioritization for the case where low-priority dynamic grant-PUSCH collides with high-priority configured grant-PUSCH on a BWP of a serving cell (see TS 38.213 [13], clause 9), when the UE has generated transport blocks for both DG-PUSCH and CG-PUSCH as described in TS 38.321 [3].

prioHighDG-LowCG Enable PHY prioritization for the case where high-priority dynamic grant PUSCH collides with low-priority configured grant PUSCH on a BWP of a serving cell (see TS 38.213 [13], clause 9), when the UE has generated transport blocks for both DG-PUSCH and CG-PUSCH as described in TS 38.321 [3].

ps-RNTI RNTI value for scrambling CRC of DCI format 2-6 used for power saving (see TS 38.213 [13], clause 10.1).

ps-Offset The start of the search-time of DCI format 2-6 with CRC scrambled by PS-RNTI relative to the start of the drx-onDurationTimer of Long DRX (see TS 38.213 [13], clause 10.3). Value in multiples of 0.125ms (milliseconds). 1 corresponds to 0.125 ms, 2 corresponds to 0.25 ms, 3 corresponds to 0.375 ms and so on.

ps-WakeUp Indicates the UE to wake-up if DCI format 2-6 is not detected outside active time (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not wake-up if DCI format 2-6 is not detected outside active time.

ps-PositionDCI-2-6 Starting position of UE wakeup and SCell dormancy indication in DCI format 2-6 (see TS 38.213 [13], clause 10.3).

ps-TransmitPeriodicL1-RSRP Indicates the UE to transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start.

ps-TransmitOtherPeriodicCSI Indicates the UE to transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start.

p-UE-FR1 The maximum total transmit power to be used by the UE across all serving cells in frequency range 1 (FR1) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-NR-FR1 (configured for the cell group).

p-UE-FR2 The maximum total transmit power to be used by the UE across all serving cells in frequency range 2 (FR2) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-NR-FR2 (configured for the cell group). A UE does not expect to be configured with this parameter in this release of the specification.

pdsch-HARQ-ACK-Codebook The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to both CA and none CA operation (see TS 38.213 [13], clauses 9.1.2 and 9.1.3). If pdsch-HARQ-ACK-Codebook-r16 is signalled, UE shall ignore the pdsch-HARQ-ACK-Codebook (without suffix). For the HARQ-ACK for sidelink, if pdsch-HARQ-ACK-Codebook-r16 is signalled, the UE uses pdsch-HARQ-ACK-Codebook (without suffix) and ignores pdsch-HARQ-ACK-Codebook-r16. If the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary PUCCH group. Otherwise, this field is applied to the cell group (i.e. for all the cells within the cell group). For the HARQ-ACK for sidelink, if the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary and secondary PUCCH group and the UE ignores pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup.

pdsch-HARQ-ACK-CodebookList A list of configurations for one or two HARQ-ACK codebooks. Each configuration in the list is defined in the same way as pdsch-HARQ-ACK-Codebook (see TS 38.212 [17], clause 7.3.1.2.2 and TS 38.213 [13], clauses 7.2.1, 9.1.2, 9.1.3 and 9.2.1). If this field is present, the field pdsch-HARQ-ACK-Codebook is ignored. If this field is present, the value of this field is applied for primary PUCCH group and for secondary PUCCH group (if configured). For the HARQ-ACK for sidelink, the UE uses pdsch-HARQ-ACK-Codebook and ignores pdsch-HARQ-ACK-CodebookList if this field is present.

pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to CA operation (see TS 38.213 [13], clauses 9.1.2 and 9.1.3). It is configured for secondary PUCCH group.

pdsch-HARQ-ACK-EnhType3DCI-Field, pdsch-HARQ-ACK-EnhType3DCI-FieldSecondaryPUCCHgroup Indicates the enhanced Type 3 codebook through a new DCI field to indicate the enhanced Type 3 HARQ-ACK codebook in the primary PUCCH group if the more than one enhanced Type 3 HARQ-ACK codebook is configured for the primary PUCCH group, or in the secondary PUCCH group if the more than one enhanced Type 3 HARQ-ACK code is configured for the secondary PUCCH group, respectively.

pdsch-HARQ-ACK-EnhType3ToAddModList, pdsch-HARQ-ACK-EnhType3SecondaryToAddModList Configure the list of enhanced Type 3 HARQ-ACK codebooks for the primary PUCCH group and the secondary PUCCH group, respectively. When configured, DCI_format 1_1 can request the UE to report A/N for one of the configured enhanced Type 3 HARQ-ACK codebooks in the corresponding PUCCH group (see TS 38.213 [13], clause 9.1.4). The network can configure pdsch-HARQ-ACK-EnhType3SecondaryToAddModList only if secondary PUCCH group is configured.

pdsch-HARQ-ACK-OneShotFeedback When configured, the DCI_format 1_1 can request the UE to report A/N for all HARQ processes and all CCs configured in the PUCCH group (see TS 38.212 [17], clause 7.3.1).

pdsch-HARQ-ACK-OneShotFeedbackCBG When configured, the DCI_format 1_1 can request the UE to include CBG level A/N for each CC with CBG level transmission configured. When not configured, the UE will report TB level A/N even if CBG level transmission is configured for a CC. The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured.

pdsch-HARQ-ACK-OneShotFeedbackNDI When configured, the DCI_format 1_1 can request the UE to include NDI for each A/N reported. The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured.

pdsch-HARQ-ACK-Retx, pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup When configured, the DCI format 1_1 can request the UE to perform a HARQ-ACK re-transmission on a PUCCH resource in the primary PUCCH group and the secondary PUCCH group, respectively (see TS 38.213 [13], clause 9.1.5).

pucch-sSCell, pucch-sSCellSecondaryPUCCHgroup indictates the alternative PUCCH cells for PUCCH cell switching in the primary and the secondary PUCCH group, respectively. For the primary PUCCH group, it is configured for cells on top of SpCell. For the secondary PUCCH group, it is configured for cell on top of the PUCCH SCell.

pucch-sSCellDyn, pucch-sSCellDynsecondaryPUCCHgroup When configured, PUCCH cell switching based on dynamic indication in DCI format 1_1 is enabled (see TS 38.213 [13], clause 9.A, clause 9.1.5), respectively for the primary PUCCH group and the secondary PUCCH group.

pucch-sSCellPattern, pucch-sSCellPatternSecondaryPUCCHgroup When configured, the UE applies the semi-static PUCCH cell switching (see TS 38.213 [13], clause 9.A) using the time domain pattern of applicable PUCCH cells indicated by this field, respectively for the primary PUCCH group and the secondary PUCCH group.

simultaneousPUCCH-PUSCH, simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup Enables simultaneous PUCCH and PUSCH transmissions with different priorities for the primary PUCCH group and the secondary PUCCH group, respectively.

simultaneousSR-PUSCH-diffPUCCH-Groups Enables simultaneous SR and PUSCH transmissions in different PUCCH groups (see TS 38.321 [3], clause 5.4.1, clause 5.4.4).

sizeDCI-2-6 Size of DCI format 2-6 (see TS 38.213 [13], clause 10.3).

sp-CSI-RNTI RNTI for Semi-Persistent CSI reporting on PUSCH (see CSI-ReportConfig) (see TS 38.214 [19], clause 5.2.1.5.2). Network always configures the UE with a value for this field when at least one CSI-ReportConfig with reportConfigType set to semiPersistentOnPUSCH is configured.

tpc-PUCCH-RNTI RNTI used for PUCCH TPC commands on DCI (see TS 38.213 [13], clause 10.1).

tpc-PUSCH-RNTI RNTI used for PUSCH TPC commands on DCI (see TS 38.213 [13], clause 10.1).

tpc-SRS-RNTI RNTI used for SRS TPC commands on DCI (see TS 38.213 [13], clause 10.1).

twoQCLTypeDforPDCCHRepetition Indicates whether a UE is expected UE to identify and monitor two QCL-TypeD properties for multiple overlapping CORESETs in the case of PDCCH repetition.

uci-MuxWithDiffPrio, uci-MuxWithDiffPrio-secondaryPUCCHgroup When configured, enables multiplexing a high-priority (HP) HARQ-ACK UCI and a low-priority (LP) HARQ-ACK UCI into a PUCCH or PUSCH for the primary PUCCH group and the secondary PUCCH group, respectively.

ul-TotalDAI-Included Indicates whether the total DAI fields of the additional PDSCH group is included in the non-fallback UL grant DCI (see TS 38.212 [17], clause 7.3.1). The network configures this only when enhanced dynamic codebook is configured (pdsch-HARQ-ACK-Codebook is set to enhancedDynamic).

xScale The UE is allowed to drop NR only if the power scaling applied to NR results in a difference between scaled and unscaled NR UL of more than xScale dB (see TS 38.213 [13]). If the value is not configured for dynamic power sharing, the UE assumes default value of 6 dB.

MulticastConfig field descriptions

pdsch-HARQ-ACK-CodebookListMulticast A list of configurations for one or two HARQ-ACK codebooks for MBS multicast. Each configuration in the list is defined in the same way as pdsch-HARQ-ACK-Codebook (see TS 38.212 [17], clause 7.3.1.2.2 and TS 38.213 [13], clauses 7.2.1, 9.1.2, 9.1.3 and 9.2.1). If this field is present, the field pdsch-HARQ-ACK-Codebook is ignored. If this field is present, the value of this field is applied for primary PUCCH group and for secondary PUCCH group (if configured).

type1-Codebook-Generation-Mode Indicates the mode of Type-1 HARQ-ACK codebook generation. Mode 1 is based on the k1 values that are in the intersection of K1 set for unicast and K1 set for multicast. Mode 2 is based on the k1 values that in the union of K1 set for unicast and K1 set for multicast.

PDSCH-HARQ-ACK-EnhType3 field descriptions

pdsch-HARQ-ACK-EnhType3CBG When configured, the DCI_format 1_1 or DCI format 1_2 can request the UE to include CBG level A/N for each CC with CBG level transmission configured of the enhanced Type 3 HARQ-ACK codebook. When not configured, the UE will report TB level A/N even if CBG level transmission is configured for a CC.

pdsch-HARQ-ACK-EnhType3NDI When configured, the DCI_format 1_1 or DCI format 1_2 can request the UE to include NDI for each A/N reported of the enhanced Type 3 HARQ-ACK codebook.

perCC Configures enhanced Type 3 HARQ-ACK codebook using per CC configuration.

perHARQ Configures enhanced Type 3 HARQ-ACK codebook using per HARQ process and CC configuration.

Conditional Presence	Explanation
MCG-Only	This field is optionally present, Need R, in the PhysicalCellGroupConfig of the MCG. It is absent otherwise.
SCG-Only	This field is optionally present, Need S, in the PhysicalCellGroupConfig of the SCG in (NG)EN-DC as defined in TS 38.213 [13]. It is absent otherwise.
twoPUCCHgroup	This field is optionally present, Need R, if secondary PUCCH group is configured. It is absent otherwise, Need R.

– PLMN-Identity

The IE PLMN-Identity identifies a Public Land Mobile Network. Further information regarding how to set the IE is specified in TS 23.003 [21].

PLMN-Identity information element

— ASN1START

— TAG-PLMN-IDENTITY-START

PLMN-Identity ::= SEQUENCE {

mcc MCC OPTIONAL, — Cond MCC

mnc MNC

}

MCC ::= SEQUENCE (SIZE (3)) OF MCC-MNC-Digit

MNC ::= SEQUENCE (SIZE (2..3)) OF MCC-MNC-Digit

MCC-MNC-Digit ::= INTEGER (0..9)

— TAG-PLMN-IDENTITY-STOP

— ASN1STOP

PLMN-Identity field descriptions

mcc The first element contains the first MCC digit, the second element the second MCC digit and so on. If the field is absent, it takes the same value as the mcc of the immediately preceding IE PLMN-Identity. See TS 23.003 [21].

mnc The first element contains the first MNC digit, the second element the second MNC digit and so on. See TS 23.003 [21].

Conditional Presence	Explanation
MCC	This field is mandatory present when PLMN-Identity is not used in a list or if it is the first entry of PLMN-Identity in a list. Otherwise it is optionally present, Need S.

– PLMN-IdentityInfoList

The IE PLMN-IdentityInfoList includes a list of PLMN identity information.

PLMN-IdentityInfoList information element

— ASN1START

— TAG-PLMN-IDENTITYINFOLIST-START

PLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-IdentityInfo

PLMN-IdentityInfo ::= SEQUENCE {

plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity,

trackingAreaCode TrackingAreaCode OPTIONAL, — Need R

ranac RAN-AreaCode OPTIONAL, — Need R

cellIdentity CellIdentity,

cellReservedForOperatorUse ENUMERATED {reserved, notReserved},

…,

[[

iab-Support-r16 ENUMERATED {true} OPTIONAL — Need S

]],

[[

trackingAreaList-r17 SEQUENCE (SIZE (1..maxTAC-r17)) OF TrackingAreaCode OPTIONAL, — Need R

gNB-ID-Length-r17 INTEGER (22..32) OPTIONAL — Need R

]]

}

— TAG-PLMN-IDENTITYINFOLIST-STOP

— ASN1STOP

PLMN-IdentityInfo field descriptions

cellReservedForOperatorUse Indicates whether the cell is reserved for operator use (per PLMN), as defined in TS 38.304 [20]. This field is ignored by IAB-MT.

gNB-ID-Length Indicates the length of the gNB ID out of the 36-bit long cellIdentity.

iab-Support This field combines both the support of IAB and the cell status for IAB. If the field is present, the cell supports IAB and the cell is also considered as a candidate for cell (re)selection for IAB-node; if the field is absent, the cell does not support IAB and/or the cell is barred for IAB-node.

trackingAreaCode Indicates Tracking Area Code to which the cell indicated by cellIdentity field belongs. The absence of the field indicates that the cell only supports PSCell/SCell functionality (per PLMN) or is an NTN cell.

trackingAreaList List of Tracking Areas to which the cell indicated by cellIdentity field belongs. If this field is present, network does not configure trackingAreaCode. Total number of different TACs across different PLMN-IdentityInfos shall not exceed maxTAC.

– PLMN-IdentityList2

Includes a list of PLMN identities.

PLMN-IdentityList2 information element

— ASN1START

— TAG-PLMNIDENTITYLIST2-START

PLMN-IdentityList2-r16 ::= SEQUENCE (SIZE (1..16)) OF PLMN-Identity

— TAG-PLMNIDENTITYLIST2-STOP

— ASN1STOP

– PRB-Id

The IE PRB-Id identifies a Physical Resource Block (PRB) position within a carrier.

PRB-Id information element

— ASN1START

— TAG-PRB-ID-START

PRB-Id ::= INTEGER (0..maxNrofPhysicalResourceBlocks-1)

— TAG-PRB-ID-STOP

— ASN1STOP

– PTRS-DownlinkConfig

The IE PTRS-DownlinkConfig is used to configure downlink phase tracking reference signals (PTRS) (see TS 38.214 [19] clause 5.1.6.3)

PTRS-DownlinkConfig information element

— ASN1START

— TAG-PTRS-DOWNLINKCONFIG-START

PTRS-DownlinkConfig ::= SEQUENCE {

frequencyDensity SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, — Need S

timeDensity SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, — Need S

epre-Ratio INTEGER (0..3) OPTIONAL, — Need S

resourceElementOffset ENUMERATED { offset01, offset10, offset11 } OPTIONAL, — Need S

…,

[[

maxNrofPorts-r16 ENUMERATED {n1, n2} OPTIONAL — Need R

]]

}

— TAG-PTRS-DOWNLINKCONFIG-STOP

— ASN1STOP

PTRS-DownlinkConfig field descriptions

epre-Ratio EPRE ratio between PTRS and PDSCH. Value 0 corresponds to the codepoint "00" in table 4.1-2. Value 1 corresponds to codepoint "01", and so on. If the field is not provided, the UE applies value 0 (see TS 38.214 [19], clause 4.1).

frequencyDensity Presence and frequency density of DL PT-RS as a function of Scheduled BW. If the field is absent, the UE uses K_PT-RS = 2 (see TS 38.214 [19], clause 5.1.6.3, table 5.1.6.3-2).

maxNrofPorts The maximum number of DL PTRS ports specified in TS 38.214 [19] (clause 5.1.6.3). 2 PT-RS ports can only be configured for a DL BWP that is configured, as specified in TS 38.214 [19] clause 5.1, with a mode where a single PDSCH has association between the DM-RS ports and the TCI states as defined in TS 38.214 [19] clause 5.1.6.2.

resourceElementOffset Indicates the subcarrier offset for DL PTRS. If the field is absent, the UE applies the value offset00 (see TS 38.211 [16], clause 7.4.1.2.2).

timeDensity Presence and time density of DL PT-RS as a function of MCS. The value 29 is only applicable for MCS Table 5.1.3.1-1 (TS 38.214 [19]). If the field is absent, the UE uses L_PT-RS = 1 (see TS 38.214 [19], clause 5.1.6.3, table 5.1.6.3-1).

– PTRS-UplinkConfig

The IE PTRS-UplinkConfig is used to configure uplink Phase-Tracking-Reference-Signals (PTRS).

PTRS-UplinkConfig information element

— ASN1START

— TAG-PTRS-UPLINKCONFIG-START

PTRS-UplinkConfig ::= SEQUENCE {

transformPrecoderDisabled SEQUENCE {

frequencyDensity SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, — Need S

timeDensity SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, — Need S

maxNrofPorts ENUMERATED {n1, n2},

resourceElementOffset ENUMERATED {offset01, offset10, offset11 } OPTIONAL, — Need S

ptrs-Power ENUMERATED {p00, p01, p10, p11}

} OPTIONAL, — Need R

transformPrecoderEnabled SEQUENCE {

sampleDensity SEQUENCE (SIZE (5)) OF INTEGER (1..276),

timeDensityTransformPrecoding ENUMERATED {d2} OPTIONAL — Need S

} OPTIONAL, — Need R

…

}

— TAG-PTRS-UPLINKCONFIG-STOP

— ASN1STOP

PTRS-UplinkConfig field descriptions

frequencyDensity Presence and frequency density of UL PT-RS for CP-OFDM waveform as a function of scheduled BW If the field is absent, the UE uses K_PT-RS = 2 (see TS 38.214 [19], clause 6.1).

maxNrofPorts The maximum number of UL PTRS ports for CP-OFDM (see TS 38.214 [19], clause 6.2.3.1).

ptrs-Power UL PTRS power boosting factor per PTRS port (see TS 38.214 [19], clause 6.1, table 6.2.3.1.3).

resourceElementOffset Indicates the subcarrier offset for UL PTRS for CP-OFDM. If the field is absent, the UE applies the value offset00 (see TS 38.211 [16], clause 6.4.1.2.2).

sampleDensity Sample density of PT-RS for DFT-s-OFDM, pre-DFT, indicating a set of thresholds T={NRBn, n=0,1,2,3,4}, that indicates dependency between presence of PT-RS and scheduled BW and the values of X and K the UE should use depending on the scheduled BW, see TS 38.214 [19], clause 6.1, table 6.2.3.2-1.

timeDensity Presence and time density of UL PT-RS for CP-OFDM waveform as a function of MCS If the field is absent, the UE uses L_PT-RS = 1 (see TS 38.214 [19], clause 6.1).

timeDensityTransformPrecoding Time density (OFDM symbol level) of PT-RS for DFT-s-OFDM. If the field is absent, the UE applies value d1 (see TS 38.214 [19], clause 6.1).

transformPrecoderDisabled Configuration of UL PTRS without transform precoder (with CP-OFDM).

transformPrecoderEnabled Configuration of UL PTRS with transform precoder (DFT-S-OFDM).

– PUCCH-Config

The IE PUCCH-Config is used to configure UE specific PUCCH parameters (per BWP).

PUCCH-Config information element

— ASN1START

— TAG-PUCCH-CONFIG-START

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

]]

}

PUCCH-FormatConfig ::= SEQUENCE {

interslotFrequencyHopping ENUMERATED {enabled} OPTIONAL, — Need R

additionalDMRS ENUMERATED {true} OPTIONAL, — Need R

maxCodeRate PUCCH-MaxCodeRate OPTIONAL, — Need R

nrofSlots ENUMERATED {n2,n4,n8} OPTIONAL, — Need S

pi2BPSK ENUMERATED {enabled} OPTIONAL, — Need R

simultaneousHARQ-ACK-CSI ENUMERATED {true} OPTIONAL — Need R

}

PUCCH-FormatConfigExt-r17 ::= SEQUENCE {

maxCodeRateLP-r17 PUCCH-MaxCodeRate OPTIONAL, — Need R

…

}

PUCCH-MaxCodeRate ::= ENUMERATED {zeroDot08, zeroDot15, zeroDot25, zeroDot35, zeroDot45, zeroDot60, zeroDot80}

— A set with one or more PUCCH resources

PUCCH-ResourceSet ::= SEQUENCE {

pucch-ResourceSetId PUCCH-ResourceSetId,

resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId,

maxPayloadSize INTEGER (4..256) OPTIONAL — Need R

}

PUCCH-ResourceSetId ::= INTEGER (0..maxNrofPUCCH-ResourceSets-1)

PUCCH-Resource ::= SEQUENCE {

pucch-ResourceId PUCCH-ResourceId,

startingPRB PRB-Id,

intraSlotFrequencyHopping ENUMERATED { enabled } OPTIONAL, — Need R

secondHopPRB PRB-Id OPTIONAL, — Need R

format CHOICE {

format0 PUCCH-format0,

format1 PUCCH-format1,

format2 PUCCH-format2,

format3 PUCCH-format3,

format4 PUCCH-format4

}

}

PUCCH-ResourceExt-v1610 ::= SEQUENCE {

interlaceAllocation-r16 SEQUENCE {

rb-SetIndex-r16 INTEGER (0..4),

interlace0-r16 CHOICE {

scs15 INTEGER (0..9),

scs30 INTEGER (0..4)

}

} OPTIONAL, –Need R

format-v1610 CHOICE {

interlace1-v1610 INTEGER (0..9),

occ-v1610 SEQUENCE {

occ-Length-v1610 ENUMERATED {n2,n4} OPTIONAL, — Need M

occ-Index-v1610 ENUMERATED {n0,n1,n2,n3} OPTIONAL — Need M

}

} OPTIONAL, — Need R

…,

[[

formatExt-v1700 SEQUENCE {

nrofPRBs-r17 INTEGER (1..16)

} OPTIONAL, — Need R

pucch-RepetitionNrofSlots-r17 ENUMERATED { n1,n2,n4,n8 } OPTIONAL — Need R

]]

}

PUCCH-ResourceId ::= INTEGER (0..maxNrofPUCCH-Resources-1)

PUCCH-format0 ::= SEQUENCE {

initialCyclicShift INTEGER(0..11),

nrofSymbols INTEGER (1..2),

startingSymbolIndex INTEGER(0..13)

}

PUCCH-format1 ::= SEQUENCE {

initialCyclicShift INTEGER(0..11),

nrofSymbols INTEGER (4..14),

startingSymbolIndex INTEGER(0..10),

timeDomainOCC INTEGER(0..6)

}

PUCCH-format2 ::= SEQUENCE {

nrofPRBs INTEGER (1..16),

nrofSymbols INTEGER (1..2),

startingSymbolIndex INTEGER(0..13)

}

PUCCH-format3 ::= SEQUENCE {

nrofPRBs INTEGER (1..16),

nrofSymbols INTEGER (4..14),

startingSymbolIndex INTEGER(0..10)

}

PUCCH-format4 ::= SEQUENCE {

nrofSymbols INTEGER (4..14),

occ-Length ENUMERATED {n2,n4},

occ-Index ENUMERATED {n0,n1,n2,n3},

startingSymbolIndex INTEGER(0..10)

}

PUCCH-ResourceGroup-r16 ::= SEQUENCE {

pucch-ResourceGroupId-r16 PUCCH-ResourceGroupId-r16,

resourcePerGroupList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerGroup-r16)) OF PUCCH-ResourceId

}

PUCCH-ResourceGroupId-r16 ::= INTEGER (0..maxNrofPUCCH-ResourceGroups-1-r16)

DL-DataToUL-ACK-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..15)

DL-DataToUL-ACK-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..127)

DL-DataToUL-ACK-v1700 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (16..31)

DL-DataToUL-ACK-DCI-1-2-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..15)

DL-DataToUL-ACK-DCI-1-2-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..127)

UL-AccessConfigListDCI-1-1-r16 ::= SEQUENCE (SIZE (1..16)) OF INTEGER (0..15)

UL-AccessConfigListDCI-1-2-r17 ::= SEQUENCE (SIZE (1..16)) OF INTEGER (0..15)

UL-AccessConfigListDCI-1-1-r17 ::= SEQUENCE (SIZE (1..3)) OF INTEGER (0..2)

DL-DataToUL-ACK-MulticastDCI-Format4-1-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..15)

— TAG-PUCCH-CONFIG-STOP

— ASN1STOP

PUCCH-Config field descriptions

dl-DataToUL-ACK, dl-DataToUL-ACK-DCI-1-2 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 up to 71 GHz. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 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.

dl-DataToUL-ACK-MulticastDCI-Format4-1 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).

dmrs-BundlingPUCCH-Config 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.

dmrs-UplinkTransformPrecodingPUCCH This field is used for PUCCH formats 3 and 4 according to TS 38.211, Clause 6.4.1.3.3.1.

format0 Parameters that are common for all PUCCH resources of format 0.

format1 Parameters that are common for all PUCCH resources of format 1.

format2 Parameters that are common for all PUCCH resources of format 2.

format3 Parameters that are common for all PUCCH resources of format 3.

format4 Parameters that are common for all PUCCH resources of format 4.

mappingPattern 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).

numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2 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).

powerControlSetInfoToAddModList 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.

pucch-PowerControl Configures power control parameters PUCCH transmission. This field is not configured if unifiedTCI-StateType is configured for the serving cell.

resourceGroupToAddModList, resourceGroupToReleaseList Lists for adding and releasing groups of PUCCH resources that can be updated simultaneously for spatial relations with a MAC CE.

resourceSetToAddModList, resourceSetToReleaseList Lists for adding and releasing PUCCH resource sets (see TS 38.213 [13], clause 9.2).

resourceToAddModList, resourceToAddModListExt, resourceToReleaseList 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.

secondTPCFieldDCI-1-1, secondTPCFieldDCI-1-2 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.

spatialRelationInfoToAddModList, spatialRelationInfoToAddModListSizeExt , spatialRelationInfoToAddModListExt 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.

spatialRelationInfoToReleaseList, spatialRelationInfoToReleaseListSizeExt, spatialRelationInfoToReleaseListExt Lists of spatial relation configurations between a reference RS and PUCCH to be released by the UE.

sps-PUCCH-AN-List 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.

sps-PUCCH-AN-ListMulticast The field is used to configure the list of PUCCH resources per HARQ ACK codebook for MBS multicast.

subslotLengthForPUCCH 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.

ul-AccessConfigListDCI-1-1, ul-AccessConfigListDCI-1-2 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).

PUCCH-format3 field descriptions

nrofPRBs The supported values are 1,2,3,4,5,6,8,9,10,12,15 and 16. The UE shall ignore this field when formatExt is configured.

PUCCH-FormatConfig, PUCCH-FormatConfigExt field descriptions

additionalDMRS If the field is present, the UE enables 2 DMRS symbols per hop of a PUCCH Format 3 or 4 if both hops are more than X symbols when FH is enabled (X=4). And it enables 4 DMRS symbols for a PUCCH Format 3 or 4 with more than 2X+1 symbols when FH is disabled (X=4). The field is not applicable for format 0, 1 and 2. See TS 38.213 [13], clause 9.2.2.

interslotFrequencyHopping If the field is present, the UE enables inter-slot frequency hopping when PUCCH Format 0, 1, 3 or 4 is repeated over multiple slots. For long PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. The field is not applicable for format 2. See TS 38.213 [13], clause 9.2.6.

maxCodeRate Max coding rate to determine how to feedback UCI on PUCCH for format 2, 3 or 4. The field is not applicable for format 0 and 1. See TS 38.213 [13], clause 9.2.5.

maxCodeRateLP Max coding rate to determine how to feedback UCI on PUCCH for format 2, 3 or 4. The field is not applicable for format 0 and 1. This field configures additional max code rate in the second entry of PUCCH-ConfigurationList-r16 for multiplexing low-priority (LP) HARQ-ACK and high-priority (HP) UCI in a PUCCH as described Clause 9.2.5.3 of TS 38.213 [13]. The field is absent for the first entry of PUCCH-ConfigurationList-r16.

nrofSlots Number of slots with the same PUCCH. When the field is absent the UE applies the value n1. The field is not applicable for format 2. See TS 38.213 [13], clause 9.2.6.

pi2BPSK If the field is present, the UE uses pi/2 BPSK for UCI symbols instead of QPSK for PUCCH. The field is not applicable for format 0, 1 and 2. See TS 38.213 [13], clause 9.2.5.

rb-SetIndex Indicates the RB set where PUCCH resource is allocated.

simultaneousHARQ-ACK-CSI If the field is present, the UE uses simultaneous transmission of CSI and HARQ-ACK feedback with or without SR with PUCCH Format 2, 3 or 4. See TS 38.213 [13], clause 9.2.5. When the field is absent the UE applies the value off. The field is not applicable for format 0 and 1.

PUCCH-Resource, PUCCH-ResourceExt field descriptions

format, formatExt Selection of the PUCCH format (format 0 – 4) and format-specific parameters, see TS 38.213 [13], clause 9.2. format0 and format1 are only allowed for a resource in a first PUCCH resource set. format2, format3 and format4 are only allowed for a resource in non-first PUCCH resource set. The network can only configure formatExt-v1610 when format is set to format2 or format3. The network only configures formatExt-v17xx when format is set to format0, format1 or format4.

interlace0 This is the only interlace of interlaced PUCCH Format 0 and 1 and the first interlace for interlaced PUCCH Format 2 and 3.

interlace1 A second interlace, in addition to interlace 0, as specified in TS 38.213 [13], clause 9.2.1. For 15kHz SCS, values {0..9} are applicable; for 30kHz SCS, values {0..4} are applicable. For 15kHz SCS, the values of interlace1 shall satisfy interlace1=mod(interlace0+X,10) where X=1, -1, or 5.

intraSlotFrequencyHopping Enabling intra-slot frequency hopping, applicable for all types of PUCCH formats. For long PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. See TS 38.213 [13], clause 9.2.1.

nrofPRBs Indicates the number of PRBs used per PUCCH resource for the PUCCH format, see TS 38.213 [13], clause 9.2.1. This field is applicable for PUCCH format0, format1, and format4 in FR2-2. The supported values for format4 are 1,2,3,4,5,6,8,9,10,12,15 and 16.

occ-Index Indicates the orthogonal cover code index (see TS 38.213 [13], clause 9.2.1). This field is applicable when useInterlacePUCCH-PUSCH-16 is configured.

occ-Length Indicates the orthogonal cover code length (see TS 38.213 [13], clause 9.2.1). This field is applicable when useInterlacePUCCH-PUSCH-16 is configured.

pucch-RepetitionNrofSlots Configuration of PUCCH repetition factor per PUCCH resource with associated scheduling DCI corresponding to Rel-17 dynamic PUCCH repetition. For a PUCCH resource, if both the field pucch-RepetitionNrofSlots and the field nrofSlots are present, the field nrofSlots is ignored and apply the value of pucch-RepetitionNrofSlots corresponding to Rel-17 dynamic PUCCH repetition. If this field is absent in a PUCCH resource with associated scheduling DCI, the UE applies the value of field nrofSlots.

pucch-ResourceId Identifier of the PUCCH resource.

secondHopPRB Index of first PRB after frequency hopping of PUCCH. This value is applicable for intra-slot frequency hopping (see TS 38.213 [13], clause 9.2.1) or inter-slot frequency hopping (see TS 38.213 [13], clause 9.2.6).

PUCCH-ResourceSet field descriptions

maxPayloadSize Maximum number of UCI information bits that the UE may transmit using this PUCCH resource set (see TS 38.213 [13], clause 9.2.1). In a PUCCH occurrence, the UE chooses the first of its PUCCH-ResourceSet which supports the number of bits that the UE wants to transmit. The field is absent in the first set (Set0) and in the last configured set since the UE derives the maximum number of UCI information bits as specified in TS 38.213 [13], clause 9.2.1. This field can take integer values that are multiples of 4.

resourceList PUCCH resources of format0 and format1 are only allowed in the first PUCCH resource set, i.e., in a PUCCH-ResourceSet with pucch-ResourceSetId = 0. This set may contain between 1 and 32 resources. PUCCH resources of format2, format3 and format4 are only allowed in a PUCCH-ResourceSet with pucch-ResourceSetId > 0. If present, these sets contain between 1 and 8 resources each. The UE chooses a PUCCH-Resource from this list as specified in TS 38.213 [13], clause 9.2.3. Note that this list contains only a list of resource IDs. The actual resources are configured in PUCCH-Config.

Conditional Presence	Explanation
PI2-BPSK	The field is optionally present, Need R, if format3 and/or format4 are configured and pi2BPSK is configured in each of them. It is absent, Need R otherwise.

– PUCCH-ConfigCommon

The IE PUCCH-ConfigCommon is used to configure the cell specific PUCCH parameters.

PUCCH-ConfigCommon information element

— ASN1START

— TAG-PUCCH-CONFIGCOMMON-START

PUCCH-ConfigCommon ::= SEQUENCE {

pucch-ResourceCommon INTEGER (0..15) OPTIONAL, — Cond InitialBWP-Only

pucch-GroupHopping ENUMERATED { neither, enable, disable },

hoppingId INTEGER (0..1023) OPTIONAL, — Need R

p0-nominal INTEGER (-202..24) OPTIONAL, — Need R

…,

[[

nrofPRBs INTEGER (1..16) OPTIONAL, — Need R

intra-SlotFH-r17 ENUMERATED {fromLowerEdge, fromUpperEdge} OPTIONAL, — Need R

pucch-ResourceCommonRedCap-r17 INTEGER (0..15) OPTIONAL, — Cond InitialBWP-RedCap

additionalPRBOffset-r17 ENUMERATED {n2, n3, n4, n6, n8, n9, n10, n12} OPTIONAL — Need S

]]

}

— TAG-PUCCH-CONFIGCOMMON-STOP

— ASN1STOP

PUCCH-ConfigCommon field descriptions

additionalPRBOffset When intra-slot PUCCH frequency hopping within RedCap-specific initial UL BWP is disabled, each common PUCCH resource is mapped to a single PRB on one side of the UL BWP. This parameter determines an additional PRB offset in the PRB mapping for the PUCCH resource. If the field is not configured, the UE shall assume an additional PRB offset of zero.

hoppingId Cell-specific scrambling ID for group hopping and sequence hopping if enabled, see TS 38.211 [16], clause 6.3.2.2.

intra-SlotFH-r17 In case a separate initial UL BWP is configured for RedCap UEs, the presence of this parameter indicates whether intra-slot PUCCH frequency hopping within the separate initial UL BWP in the common PUCCH resource is enabled for RedCap UEs. If this field is absent, intra-slot PUCCH frequency hopping within RedCap-specific initial UL BWP is enabled. If this field is present, intra-slot PUCCH frequency hopping within RedCap-specific initial UL BWP is disabled and each PUCCH resource is mapped to a single PRB on one side of the UL BWP and this parameter determines whether the PRB index in the PRB mapping is counted in increasing order from the lower edge or in decreasing order from the upper edge of the UL BWP.

nrofPRBs Indicates the number of PRBs used per PUCCH resource for PUCCH format 0 and format 1 in FR2-2, see TS 38.213 [13], clause 9.2.1.

p0-nominal Power control parameter P0 for PUCCH transmissions. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.2).

pucch-GroupHopping Configuration of group- and sequence hopping for all the PUCCH formats 0, 1, 3 and 4. Value neither implies neither group or sequence hopping is enabled. Value enable enables group hopping and disables sequence hopping. Value disable disables group hopping and enables sequence hopping (see TS 38.211 [16], clause 6.3.2.2).

pucch-ResourceCommon An entry into a 16-row table where each row configures a set of cell-specific PUCCH resources/parameters. The UE uses those PUCCH resources until it is provided with a dedicated PUCCH-Config (e.g. during initial access) on the initial uplink BWP. Once the network provides a dedicated PUCCH-Config for that bandwidth part the UE applies that one instead of the one provided in this field (see TS 38.213 [13], clause 9.2).

pucch-ResourceCommonRedCap An entry into a 16-row table where each row configures a set of cell-specific PUCCH resources/parameters for RedCap UEs. The UE uses those PUCCH resources until it is provided with a dedicated PUCCH-Config (e.g. during initial access) on the initial uplink BWP. Once the network provides a dedicated PUCCH-Config for that bandwidth part the UE applies that one instead of the one provided in this field (see TS 38.213 [13], clause 9.2).

Conditional Presence	Explanation
InitialBWP-Only	The field is mandatory present in the PUCCH-ConfigCommon of the initial BWP (BWP#0) in SIB1. It is absent in other BWPs including the RedCap-specific initial uplink BWP, if configured.
InitialBWP-RedCap	The field is mandatory present in the PUCCH-ConfigCommon of the RedCap-specific initial BWP. It is absent in other BWPs. It is optional present, Need R, in the PUCCH-ConfigCommon of the initial BWP configured by initialUplinkBWP.

– PUCCH-ConfigurationList

The IE PUCCH-ConfigurationList is used to configure UE specific PUCCH parameters (per BWP) for two simultaneously constructed HARQ-ACK codebooks. See TS 38.213 [13], clause 9.1.

PUCCH-ConfigurationList information element

— ASN1START

— TAG-PUCCH-CONFIGURATIONLIST-START

PUCCH-ConfigurationList-r16 ::= SEQUENCE (SIZE (1..2)) OF PUCCH-Config

— TAG-PUCCH-CONFIGURATIONLIST-STOP

— ASN1STOP

– PUCCH-PathlossReferenceRS-Id

The IE PUCCH-PathlossReferenceRS-Id is an ID for a reference signal (RS) configured as PUCCH pathloss reference (see TS 38.213 [13], clause 7.2).

PUCCH-PathlossReferenceRS-Id information element

— ASN1START

— TAG-PUCCH-PATHLOSSREFERENCERS-ID-START

PUCCH-PathlossReferenceRS-Id ::= INTEGER (0..maxNrofPUCCH-PathlossReferenceRSs-1)

PUCCH-PathlossReferenceRS-Id-v1610 ::= INTEGER (maxNrofPUCCH-PathlossReferenceRSs..maxNrofPUCCH-PathlossReferenceRSs-1-r16)

PUCCH-PathlossReferenceRS-Id-r17 ::= INTEGER (0..maxNrofPUCCH-PathlossReferenceRSs-1-r17)

— TAG-PUCCH-PATHLOSSREFERENCERS-ID-STOP

— ASN1STOP

– PUCCH-PowerControl

The IE PUCCH-PowerControl is used to configure UE-specific parameters for the power control of PUCCH.

PUCCH-PowerControl information element

— ASN1START

— TAG-PUCCH-POWERCONTROL-START

PUCCH-PowerControl ::= SEQUENCE {

deltaF-PUCCH-f0 INTEGER (-16..15) OPTIONAL, — Need R

deltaF-PUCCH-f1 INTEGER (-16..15) OPTIONAL, — Need R

deltaF-PUCCH-f2 INTEGER (-16..15) OPTIONAL, — Need R

deltaF-PUCCH-f3 INTEGER (-16..15) OPTIONAL, — Need R

deltaF-PUCCH-f4 INTEGER (-16..15) OPTIONAL, — Need R

p0-Set SEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH OPTIONAL, — Need M

pathlossReferenceRSs SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS

OPTIONAL, — Need M

twoPUCCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, — Need S

…,

[[

pathlossReferenceRSs-v1610 SetupRelease { PathlossReferenceRSs-v1610 } OPTIONAL — Need M

]]

}

P0-PUCCH ::= SEQUENCE {

p0-PUCCH-Id P0-PUCCH-Id,

p0-PUCCH-Value INTEGER (-16..15)

}

P0-PUCCH-Id ::= INTEGER (1..8)

PathlossReferenceRSs-v1610 ::= SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSsDiff-r16)) OF PUCCH-PathlossReferenceRS-r16

PUCCH-PathlossReferenceRS ::= SEQUENCE {

pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id,

referenceSignal CHOICE {

ssb-Index SSB-Index,

csi-RS-Index NZP-CSI-RS-ResourceId

}

}

PUCCH-PathlossReferenceRS-r16 ::= SEQUENCE {

pucch-PathlossReferenceRS-Id-r16 PUCCH-PathlossReferenceRS-Id-v1610,

referenceSignal-r16 CHOICE {

ssb-Index-r16 SSB-Index,

csi-RS-Index-r16 NZP-CSI-RS-ResourceId

}

}

PUCCH-PowerControlSetInfo-r17 ::= SEQUENCE {

pucch-PowerControlSetInfoId-r17 PUCCH-PowerControlSetInfoId-r17,

p0-PUCCH-Id-r17 P0-PUCCH-Id,

pucch-ClosedLoopIndex-r17 ENUMERATED { i0, i1 },

pucch-PathlossReferenceRS-Id-r17 PUCCH-PathlossReferenceRS-Id-r17

}

PUCCH-PowerControlSetInfoId-r17 ::= INTEGER (1.. maxNrofPowerControlSetInfos-r17)

— TAG-PUCCH-POWERCONTROL-STOP

— ASN1STOP

P0-PUCCH field descriptions

p0-PUCCH-Value P0 value for PUCCH with 1dB step size.

PUCCH-PowerControl field descriptions

deltaF-PUCCH-f0 deltaF for PUCCH format 0 with 1dB step size (see TS 38.213 [13], clause 7.2).

deltaF-PUCCH-f1 deltaF for PUCCH format 1 with 1dB step size (see TS 38.213 [13], clause 7.2).

deltaF-PUCCH-f2 deltaF for PUCCH format 2 with 1dB step size (see TS 38.213 [13], clause 7.2).

deltaF-PUCCH-f3 deltaF for PUCCH format 3 with 1dB step size (see TS 38.213 [13], clause 7.2).

deltaF-PUCCH-f4 deltaF for PUCCH format 4 with 1dB step size (see TS 38.213 [13], clause 7.2).

p0-Set A set with dedicated P0 values for PUCCH, i.e., {P01, P02,… } (see TS 38.213 [13], clause 7.2).

pathlossReferenceRSs, pathlossReferenceRSs-v1610 A set of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for PUCCH pathloss estimation. Up to maxNrofPUCCH-PathlossReference-RSs may be configured. If the field is not configured, the UE uses the SSB as reference signal (see TS 38.213 [13], clause 7.2). The set includes Reference Signals indicated in pathlossReferenceRSs (without suffix) and in pathlossReferenceRSs-v1610. The UE maintains pathlossReferenceRSs and pathlossReferenceRSs-v1610 separately: Receiving pathlossReferenceRSs-v1610 set to release releases only the entries that were configured by pathlossReferenceRSs-v1610, and receiving pathlossReferenceRSs-v1610 set to setup replaces only the entries that were configured by pathlossReferenceRSs-v1610 with the newly signalled entries.

twoPUCCH-PC-AdjustmentStates Number of PUCCH power control adjustment states maintained by the UE (i.e., g(i)). If the field is present (n2) the UE maintains two power control states (i.e., g(i,0) and g(i,1)). If the field is absent, it maintains one power control state (i.e., g(i,0)) (see TS 38.213 [13], clause 7.2).

– PUCCH-SpatialRelationInfo

The IE PUCCH-SpatialRelationInfo is used to configure the spatial setting for PUCCH transmission and the parameters for PUCCH power control, see TS 38.213, [13], clause 9.2.2.

PUCCH-SpatialRelationInfo information element

— ASN1START

— TAG-PUCCH-SPATIALRELATIONINFO-START

PUCCH-SpatialRelationInfo ::= SEQUENCE {

pucch-SpatialRelationInfoId PUCCH-SpatialRelationInfoId,

servingCellId ServCellIndex OPTIONAL, — Need S

referenceSignal CHOICE {

ssb-Index SSB-Index,

csi-RS-Index NZP-CSI-RS-ResourceId,

srs PUCCH-SRS

},

pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id,

p0-PUCCH-Id P0-PUCCH-Id,

closedLoopIndex ENUMERATED { i0, i1 }

}

PUCCH-SpatialRelationInfoExt-r16 ::= SEQUENCE {

pucch-SpatialRelationInfoId-v1610 PUCCH-SpatialRelationInfoId-v1610 OPTIONAL, — Need S

pucch-PathlossReferenceRS-Id-v1610 PUCCH-PathlossReferenceRS-Id-v1610 OPTIONAL, –Need R

…

}

PUCCH-SRS ::= SEQUENCE {

resource SRS-ResourceId,

uplinkBWP BWP-Id

}

— TAG-PUCCH-SPATIALRELATIONINFO-STOP

— ASN1STOP

PUCCH-SpatialRelationInfo field descriptions

pucch-PathLossReferenceRS-Id When pucch-PathLossReferenceRS-Id-v1610 is configured, the UE shall ignore pucch-PathLossReferenceRS-Id (without suffix).

pucch-SpatialRelationInfoId When pucch-SpatialRelationInfoId-v1610 is configured, the UE shall ignore pucch-SpatialRelationInfoId (without suffix). If pucch-SpatialRelationInfoId-v1610 is absent, the UE shall use the pucch-SpatialRelationInfoId (without suffix).

servingCellId If the field is absent, the UE applies the ServCellId of the serving cell in which this PUCCH-SpatialRelationInfo is configured

– PUCCH-SpatialRelationInfo-Id

The IE PUCCH-SpatialRelationInfo-Id is used to identify a PUCCH-SpatialRelationInfo

PUCCH-SpatialRelationInfo-Id information element

— ASN1START

— TAG-PUCCH-SPATIALRELATIONINFO-START

PUCCH-SpatialRelationInfoId ::= INTEGER (1..maxNrofSpatialRelationInfos)

PUCCH-SpatialRelationInfoId-r16 ::= INTEGER (1..maxNrofSpatialRelationInfos-r16)

PUCCH-SpatialRelationInfoId-v1610::= INTEGER (maxNrofSpatialRelationInfos-plus-1..maxNrofSpatialRelationInfos-r16)

— TAG-PUCCH-SPATIALRELATIONINFO-STOP

— ASN1STOP

– PUCCH-TPC-CommandConfig

The IE PUCCH-TPC-CommandConfig is used to configure the UE for extracting TPC commands for PUCCH from a group-TPC messages on DCI.

PUCCH-TPC-CommandConfig information element

— ASN1START

— TAG-PUCCH-TPC-COMMANDCONFIG-START

PUCCH-TPC-CommandConfig ::= SEQUENCE {

tpc-IndexPCell INTEGER (1..15) OPTIONAL, — Cond PDCCH-OfSpcell

tpc-IndexPUCCH-SCell INTEGER (1..15) OPTIONAL, — Cond PDCCH-ofSpCellOrPUCCH-SCell

…,

[[

tpc-IndexPUCCH-sSCell-r17 INTEGER (1..15) OPTIONAL, — Need R

tpc-IndexPUCCH-sScellSecondaryPUCCHgroup-r17 INTEGER (1..15) OPTIONAL — Cond twoPUCCHgroup

]]

}

— TAG-PUCCH-TPC-COMMANDCONFIG-STOP

— ASN1STOP

PUCCH-TPC-CommandConfig field descriptions

tpc-IndexPCell An index determining the position of the first bit of TPC command (applicable to the SpCell) inside the DCI format 2-2 payload.

tpc-IndexPUCCH-SCell An index determining the position of the first bit of TPC command (applicable to the PUCCH SCell) inside the DCI format 2-2 payload.

tpc-IndexPUCCH-sSCell, tpc-IndexPUCCH-sSCellSecondaryPUCCHgroup An index determining the position of the first bit of TPC command (applicable to the alternative PUCCH cell for PUCCH cell switching) inside the DCI format 2-2 payload, for the primary PUCCH group and the secondary PUCCH group respectively.

Conditional Presence	Explanation
PDCCH-OfSpcell	The field is mandatory present if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the SpCell. Otherwise, the field is absent, Need R.
PDCCH-ofSpCellOrPUCCH-SCell	The field is mandatory present if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the PUCCH-SCell. The field is optionally present, need R, if the UE is configured with a PUCCH SCell in this cell group and if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the SpCell. Otherwise, the field is absent, Need R.
twoPUCCHgroup	This field is optionally present, Need R, if secondary PUCCH group is configured. It is absent otherwise.

– PUSCH-Config

The IE PUSCH-Config is used to configure the UE specific PUSCH parameters applicable to a particular BWP.

PUSCH-Config information element

— ASN1START

— TAG-PUSCH-CONFIG-START

PUSCH-Config ::= SEQUENCE {

dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, — Need S

txConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, — Need S

dmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig } OPTIONAL, — Need M

dmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig } OPTIONAL, — Need M

pusch-PowerControl PUSCH-PowerControl OPTIONAL, — Need M

frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, — Need S

frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1)

OPTIONAL, — Need M

resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},

pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList } OPTIONAL, — Need M

pusch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, — Need S

mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, — Need S

mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, — Need S

transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, — Need S

codebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}

OPTIONAL, — Cond codebookBased

maxRank INTEGER (1..4) OPTIONAL, — Cond codebookBased

rbg-Size ENUMERATED { config2} OPTIONAL, — Need S

uci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, — Need M

tp-pi2BPSK ENUMERATED {enabled} OPTIONAL, — Need S

…,

[[

minimumSchedulingOffsetK2-r16 SetupRelease { MinSchedulingOffsetK2-Values-r16 } OPTIONAL, — Need M

ul-AccessConfigListDCI-0-1-r16 SetupRelease { UL-AccessConfigListDCI-0-1-r16 } OPTIONAL, — Need M

— Start of the parameters for DCI format 0_2 introduced in V16.1.0

harq-ProcessNumberSizeDCI-0-2-r16 INTEGER (0..4) OPTIONAL, — Need R

dmrs-SequenceInitializationDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, — Need S

numberOfBitsForRV-DCI-0-2-r16 INTEGER (0..2) OPTIONAL, — Need R

antennaPortsFieldPresenceDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, — Need S

dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, — Need M

dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, — Need M

frequencyHoppingDCI-0-2-r16 CHOICE {

pusch-RepTypeA ENUMERATED {intraSlot, interSlot},

pusch-RepTypeB ENUMERATED {interRepetition, interSlot}

} OPTIONAL, — Need S

frequencyHoppingOffsetListsDCI-0-2-r16 SetupRelease { FrequencyHoppingOffsetListsDCI-0-2-r16} OPTIONAL, — Need M

codebookSubsetDCI-0-2-r16 ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}

OPTIONAL, — Cond codebookBased

invalidSymbolPatternIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, — Need S

maxRankDCI-0-2-r16 INTEGER (1..4) OPTIONAL, — Cond codebookBased

mcs-TableDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, — Need S

mcs-TableTransformPrecoderDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, — Need S

priorityIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, — Need S

pusch-RepTypeIndicatorDCI-0-2-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, — Need R

resourceAllocationDCI-0-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch}

OPTIONAL, — Need M

resourceAllocationType1GranularityDCI-0-2-r16 ENUMERATED { n2,n4,n8,n16 } OPTIONAL, — Need S

uci-OnPUSCH-ListDCI-0-2-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-2-r16} OPTIONAL, — Need M

pusch-TimeDomainAllocationListDCI-0-2-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 }

OPTIONAL, — Need M

— End of the parameters for DCI format 0_2 introduced in V16.1.0

— Start of the parameters for DCI format 0_1 introduced in V16.1.0

pusch-TimeDomainAllocationListDCI-0-1-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 }

OPTIONAL, — Need M

invalidSymbolPatternIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, — Need S

priorityIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, — Need S

pusch-RepTypeIndicatorDCI-0-1-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, — Need R

frequencyHoppingDCI-0-1-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, — Cond RepTypeB

uci-OnPUSCH-ListDCI-0-1-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-1-r16 } OPTIONAL, — Need M

— End of the parameters for DCI format 0_1 introduced in V16.1.0

invalidSymbolPattern-r16 InvalidSymbolPattern-r16 OPTIONAL, — Need S

pusch-PowerControl-v1610 SetupRelease {PUSCH-PowerControl-v1610} OPTIONAL, — Need M

ul-FullPowerTransmission-r16 ENUMERATED {fullpower, fullpowerMode1, fullpowerMode2} OPTIONAL, — Need R

pusch-TimeDomainAllocationListForMultiPUSCH-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 }

OPTIONAL, — Need M

numberOfInvalidSymbolsForDL-UL-Switching-r16 INTEGER (1..4) OPTIONAL — Cond RepTypeB2

]],

[[

ul-AccessConfigListDCI-0-2-r17 SetupRelease { UL-AccessConfigListDCI-0-2-r17 } OPTIONAL, — Need M

betaOffsetsCrossPri0-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, — Need M

betaOffsetsCrossPri1-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, — Need M

betaOffsetsCrossPri0DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, — Need M

betaOffsetsCrossPri1DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, — Need M

mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, — Cond SRSsets

secondTPCFieldDCI-0-1-r17 ENUMERATED {enabled} OPTIONAL, — Need R

secondTPCFieldDCI-0-2-r17 ENUMERATED {enabled} OPTIONAL, — Need R

sequenceOffsetForRV-r17 INTEGER (0..3) OPTIONAL, — Need R

ul-AccessConfigListDCI-0-1-r17 SetupRelease { UL-AccessConfigListDCI-0-1-r17 } OPTIONAL, — Need M

minimumSchedulingOffsetK2-r17 SetupRelease { MinSchedulingOffsetK2-Values-r17 } OPTIONAL, — Need M

availableSlotCounting-r17 ENUMERATED { enabled } OPTIONAL, — Need S

dmrs-BundlingPUSCH-Config-r17 SetupRelease { DMRS-BundlingPUSCH-Config-r17 } OPTIONAL, — Need M

harq-ProcessNumberSizeDCI-0-2-v1700 INTEGER (5) OPTIONAL, — Need R

harq-ProcessNumberSizeDCI-0-1-r17 INTEGER (5) OPTIONAL, — Need R

mpe-ResourcePoolToAddModList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-Resource-r17 OPTIONAL, — Need N

mpe-ResourcePoolToReleaseList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-ResourceId-r17 OPTIONAL — Need N

]]

}

UCI-OnPUSCH ::= SEQUENCE {

betaOffsets CHOICE {

dynamic SEQUENCE (SIZE (4)) OF BetaOffsets,

semiStatic BetaOffsets

} OPTIONAL, — Need M

scaling ENUMERATED { f0p5, f0p65, f0p8, f1 }

}

MinSchedulingOffsetK2-Values-r16 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK2-SchedulingOffset-r16)

MinSchedulingOffsetK2-Values-r17 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK2-SchedulingOffset-r17)

UCI-OnPUSCH-DCI-0-2-r16 ::= SEQUENCE {

betaOffsetsDCI-0-2-r16 CHOICE {

dynamicDCI-0-2-r16 CHOICE {

oneBit-r16 SEQUENCE (SIZE (2)) OF BetaOffsets,

twoBits-r16 SEQUENCE (SIZE (4)) OF BetaOffsets

},

semiStaticDCI-0-2-r16 BetaOffsets

} OPTIONAL, — Need M

scalingDCI-0-2-r16 ENUMERATED { f0p5, f0p65, f0p8, f1 }

}

FrequencyHoppingOffsetListsDCI-0-2-r16 ::= SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1)

UCI-OnPUSCH-ListDCI-0-2-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH-DCI-0-2-r16

UCI-OnPUSCH-ListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH

UL-AccessConfigListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..64)) OF INTEGER (0..63)

UL-AccessConfigListDCI-0-1-r17 ::= SEQUENCE (SIZE (1..3)) OF INTEGER (0..2)

UL-AccessConfigListDCI-0-2-r17 ::= SEQUENCE (SIZE (1..64)) OF INTEGER (0..63)

BetaOffsetsCrossPriSel-r17 ::= CHOICE {

dynamic-r17 SEQUENCE (SIZE (4)) OF BetaOffsetsCrossPri-r17,

semiStatic-r17 BetaOffsetsCrossPri-r17

}

BetaOffsetsCrossPriSelDCI-0-2-r17 ::= CHOICE {

dynamicDCI-0-2-r17 CHOICE {

oneBit-r17 SEQUENCE (SIZE (2)) OF BetaOffsetsCrossPri-r17,

twoBits-r17 SEQUENCE (SIZE (4)) OF BetaOffsetsCrossPri-r17

},

semiStaticDCI-0-2-r17 BetaOffsetsCrossPri-r17

}

MPE-Resource-r17 ::= SEQUENCE {

mpe-ResourceId-r17 MPE-ResourceId-r17,

cell-r17 ServCellIndex OPTIONAL, — Need R

additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, — Need R

mpe-ReferenceSignal-r17 CHOICE {

csi-RS-Resource-r17 NZP-CSI-RS-ResourceId,

ssb-Resource-r17 SSB-Index

}

}

MPE-ResourceId-r17 ::= INTEGER (1..maxMPE-Resources-r17)

— TAG-PUSCH-CONFIG-STOP

— ASN1STOP

PUSCH-Config field descriptions

antennaPortsFieldPresenceDCI-0-2 Configure the presence of "Antenna ports" field in DCI format 0_2. When the field is configured, then the "Antenna ports" field is present in DCI format 0_2. Otherwise, the field size is set to 0 for DCI format 0_2 (See TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 nor dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 is configured, this field is absent.

availableSlotCounting Indicate whether PUSCH repetitions counted on the basis of available slots is enabled. If the field is absent, PUSCH repetitions counted on the basis of available slots is disabled.

betaOffsetsCrossPri0, betaOffsetsCrossPri1, betaOffsetsCrossPri0DCI-0-2, betaOffsetsCrossPri1DCI-0-2 Selection between and configuration of dynamic and semi-static beta-offset for multiplexing HARQ-ACK on dynamically scheduled PUSCH with different priorities, see TS 38.213 [13], clause 9.3. The field betaOffsetsCrossPrio0 indicates multiplexing low priority (LP) HARQ-ACK on dynamically scheduled high priority (HP) PUSCH. The field betaOffsetsCrossPrio1 indicates multiplexing HP HARQ-ACK on dynamically scheduled LP PUSCH. The field betaOffsetsCrossPrio0DCI-0-2 indicates multiplexing LP HARQ-ACK on dynamically scheduled HP PUSCH by DCI format 0_2. The field betaOffsetsCrossPrio1DCI-0-2 indicates multiplexing HP HARQ-ACK on dynamically scheduled LP PUSCH by DCI format 0_2.

codebookSubset, codebookSubsetDCI-0-2 Subset of PMIs addressed by TPMI, where PMIs are those supported by UEs with maximum coherence capabilities (see TS 38.214 [19], clause 6.1.1.1). The field codebookSubset applies to DCI format 0_1 and the field codebookSubsetDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1).

dataScramblingIdentityPUSCH Identifier used to initialise data scrambling (c_init) for PUSCH. If the field is absent, the UE applies the physical cell ID. (see TS 38.211 [16], clause 6.3.1.1).

dmrs-BundlingPUSCH-Config Configure the parameters for DMRS bundling for PUSCH (see TS 38.214 [19], clause 6.1.7).

dmrs-SequenceInitializationDCI-0-2 Configure whether the field "DMRS Sequence Initialization" is present or not in DCI format 0_2. If the field is absent, then 0 bit for the field "DMRS Sequence Initialization" in DCI format 0_2. If the field is present, then the number of bits is determined in the same way as DCI format 0_1 (see TS 38.212 [17], clause 7.3.1).

dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 DMRS configuration for PUSCH transmissions using PUSCH mapping type A (chosen dynamically via PUSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeA applies to DCI format 0_1 and the field dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).

dmrs-UplinkForPUSCH-MappingTypeB, dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 DMRS configuration for PUSCH transmissions using PUSCH mapping type B (chosen dynamically via PUSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeB applies to DCI format 0_1 and the field dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).

frequencyHopping The value intraSlot enables ‘Intra-slot frequency hopping’ and the value interSlot enables ‘Inter-slot frequency hopping’. If the field is absent, frequency hopping is not configured for ‘pusch-RepTypeA’ (see TS 38.214 [19], clause 6.3). The field frequencyHopping applies to DCI format 0_0 and 0_1 for ‘pusch-RepTypeA’.

frequencyHoppingDCI-0-1 Indicates the frequency hopping scheme for DCI format 0_1 when pusch-RepTypeIndicatorDCI-0-1 is set to ‘pusch-RepTypeB’, The value interRepetition enables ‘Inter-repetition frequency hopping’, and the value interSlot enables ‘Inter-slot frequency hopping’. If the field is absent, frequency hopping is not configured for DCI format 0_1 (see TS 38.214 [19], clause 6.1).

frequencyHoppingDCI-0-2 Indicate the frequency hopping scheme for DCI format 0_2. The value intraSlot enables ‘intra-slot frequency hopping’, and the value interRepetition enables ‘Inter-repetition frequency hopping’, and the value interSlot enables ‘Inter-slot frequency hopping’. When pusch-RepTypeIndicatorDCI-0-2 is set to ‘pusch-RepTypeA‘, the frequency hopping scheme can be chosen between ‘intra-slot frequency hopping and ‘inter-slot frequency hopping’ if enabled. When pusch-RepTypeIndicatorDCI-0-2 is set to ‘pusch-RepTypeB’, the frequency hopping scheme can be chosen between ‘inter-repetition frequency hopping’ and ‘inter-slot frequency hopping’ if enabled. If the field is absent, frequency hopping is not configured for DCI format 0_2 for ‘pusch-RepTypeB’ (see TS 38.214 [19], clause 6.3).

frequencyHoppingOffsetLists, frequencyHoppingOffsetListsDCI-0-2 Set of frequency hopping offsets used when frequency hopping is enabled for granted transmission (not msg3) and type 2 configured grant activation (see TS 38.214 [19], clause 6.3). The field frequencyHoppingOffsetLists applies to DCI format 0_0 and DCI format 0_1 and the field frequencyHoppingOffsetListsDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.3).

harq-ProcessNumberSizeDCI-0-2 Configure the number of bits for the field "HARQ process number" in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).

invalidSymbolPattern Indicates one pattern for invalid symbols for PUSCH transmission repetition type B applicable to both DCI format 0_1 and 0_2. If InvalidSymbolPattern is not configured, semi-static flexible symbols are used for PUSCH. Segmentation occurs only around semi-static DL symbols (see TS 38.214 [19] clause 6.1).

invalidSymbolPatternIndicatorDCI-0-1, invalidSymbolPatternIndicatorDCI-0-2 Indicates the presence of an additional bit in the DCI format 0_1/0_2. If invalidSymbolPattern is absent, then both invalidSymbolPatternIndicatorDCI-0-1 and invalidSymbolPatternIndicatorDCI-0-2 are absent. The field invalidSymbolPatternIndicatorDCI-0-1 applies to the DCI format 0_1 and the field invalidSymbolPatternIndicatorDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19] clause 6.1). If the field is absent, the UE behaviour is specified in TS 38.214 [19], clause 6.1.2.1.

mappingPattern Indicates whether the UE should follow Cyclical mapping pattern or Sequential mapping pattern for when two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage ‘codebook’ or ‘noncodebook’ for PUSCH transmission and the PUSCH transmission occasions are associated with both SRS resource sets.

maxRank, maxRankDCI-0-2 Subset of PMIs addressed by TRIs from 1 to ULmaxRank (see TS 38.214 [19], clause 6.1.1.1). The field maxRank applies to DCI format 0_1 and the field maxRankDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1).

mcs-Table, mcs-TableFormat0-2 Indicates which MCS table the UE shall use for PUSCH without transform precoder (see TS 38.214 [19], clause 6.1.4.1). If the field is absent the UE applies the value 64QAM. The field mcs-Table applies to DCI format 0_0 and DCI format 0_1 and the field mcs-TableDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.4.1).

mcs-TableTransformPrecoder, mcs-TableTransformPrecoderDCI-0-2 Indicates which MCS table the UE shall use for PUSCH with transform precoding (see TS 38.214 [19], clause 6.1.4.1) If the field is absent the UE applies the value 64QAM. The field mcs-TableTransformPrecoder applies to DCI format 0_0 and DCI format 0_1 and the field mcs-TableTransformPrecoderDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.4.1).

minimumSchedulingOffsetK2 List of minimum K2 values. Minimum K2 parameter denotes minimum applicable value(s) for the Time domain resource assignment table for PUSCH (see TS 38.214 [19], clause 6.1.2.1).

mpe-ResourcePoolToAddModList List of SSB/CSI-RS resources for P-MPR reporting. Each resource is configured with serving cell index where the resource is configured for the UE. The additionalPCI is configured only if the resource is SSB. For each resource, if neither cell nor additionalPCI is present, the SSB/CSI-RS resource is from the serving cell where the PUSCH-Config is configured.

numberOfBitsRV-DCI-0-2 Configures the number of bits for "Redundancy version" in the DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 6.1.2.1).

numberOfInvalidSymbolsForDL-UL-Switching Indicates the number of symbols after the last semi-static DL symbol that are invalid symbols for PUSCH repetition Type B. If it is absent, no symbol is explicitly defined for DL-to-UL switching (see TS 38.214 [19], clause 6.1).

priorityIndicatorDCI-0-1, priorityIndicatorDCI-0-2 Configures the presence of "priority indicator" in DCI format 0_1/0_2. When the field is absent in the IE, then the UE shall apply 0 bit for "Priority indicator" in DCI format 0_1/0_2. The field priorityIndicatorDCI-0-1 applies to DCI format 0_1 and the field priorityIndicatorDCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17] clause 7.3.1 and TS 38.213 [13] clause 9).

pusch-AggregationFactor Number of repetitions for data (see TS 38.214 [19], clause 6.1.2.1). If the field is absent the UE applies the value 1.

pusch-PowerControl Configures power control parameters PUSCH transmission. This field is not configured if unifiedTCI-StateType is configured for the serving cell.

pusch-RepTypeIndicatorDCI-0-1, pusch-RepTypeIndicatorDCI-0-2 Indicates whether UE follows the behavior for "PUSCH repetition type A" or the behavior for "PUSCH repetition type B" for the PUSCH scheduled by DCI format 0_1/0_2 and for Type 2 CG associated with the activating DCI format 0_1/0_2.The value pusch-RepTypeA enables the ‘PUSCH repetition type A’ and the value pusch-RepTypeB enables the ‘PUSCH repetition type B’. The field pusch-RepTypeIndicatorDCI-0-1 applies to DCI format 0_1 and the field pusch-RepTypeIndicatorDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1).

pusch-TimeDomainAllocationList List of time domain allocations for timing of UL assignment to UL data (see TS 38.214 [19], table 6.1.2.1.1-1). The field pusch-TimeDomainAllocationList applies to DCI formats 0_0 or DCI format 0_1 when the field pusch-TimeDomainAllocationListDCI-0-1 is not configured (see TS 38.214 [19], table 6.1.2.1.1-1 and table 6.1.2.1.1-1A). The network does not configure the pusch-TimeDomainAllocationList (without suffix) simultaneously with the pusch-TimeDomainAllocationListDCI-0-2-r16 or pusch-TimeDomainAllocationListDCI-0-1-r16 or pusch-TimeDomainAllocationListForMultiPUSCH-r16.

pusch-TimeDomainAllocationListDCI-0-1 Configuration of the time domain resource allocation (TDRA) table for DCI format 0_1 (see TS 38.214 [19], clause 6.1, table 6.1.2.1.1-1A).

pusch-TimeDomainAllocationListDCI-0-2 Configuration of the time domain resource allocation (TDRA) table for DCI format 0_2 (see TS 38.214 [19], clause 6.1.2, table 6.1.2.1.1-1B).

pusch-TimeDomainAllocationListForMultiPUSCH Configuration of the time domain resource allocation (TDRA) table for multiple PUSCH (see TS 38.214 [19], clause 6.1.2). The network configures at most 16 rows in this TDRA table in PUSCH-TimeDomainResourceAllocationList-r16 configured by this field. This field is not configured simultaneously with pusch-AggregationFactor.

rbg-Size Selection between configuration 1 and configuration 2 for RBG size for PUSCH. The UE does not apply this field if resourceAllocation is set to resourceAllocationType1. Otherwise, the UE applies the value config1 when the field is absent (see TS 38.214 [19], clause 6.1.2.2.1).

resourceAllocation, resourceAllocationDCI-0-2 Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 6.1.2). The field resourceAllocation applies to DCI format 0_1 and the field resourceAllocationDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2).

resourceAllocationType1GranularityDCI-0-2 Configures the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 0_2. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 6.1.2.2.2).

secondTPCFieldDCI-0-1, secondTPCFieldDCI-0-2 A second TPC field can be configured via RRC for DCI-0-1 and DCI-0-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,

sequenceOffsetForRV Configures the RV offset for the starting RV for the first repetition (first actual repetition in PUSCH repetition Type B) towards the second ‘SRS resource set’ for PUSCH configured in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage ‘codebook’ or ‘noncodebook’.

tp-pi2BPSK Enables pi/2-BPSK modulation with transform precoding if the field is present and disables it otherwise.

transformPrecoder The UE specific selection of transformer precoder for PUSCH (see TS 38.214 [19], clause 6.1.3). When the field is absent the UE applies the value of the field msg3-transformPrecoder from rach-ConfigCommon included directly within BWP configuration (i.e., not included in additionalRACH-ConfigList).

txConfig Whether UE uses codebook based or non-codebook based transmission (see TS 38.214 [19], clause 6.1.1). If the field is absent, the UE transmits PUSCH on one antenna port, see TS 38.214 [19], clause 6.1.1.

uci-OnPUSCH-ListDCI-0-1, uci-OnPUSCH-ListDCI-0-2 Configuration for up to 2 HARQ-ACK codebooks specific to DCI format 0_1/0_2. The field uci-OnPUSCH-ListDCI-0-1 applies to DCI format 0_1 and the field uci-OnPUSCH-ListDCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9.3).

ul-AccessConfigListDCI-0-1, ul-AccessConfigListDCI-0-2 List of the combinations of cyclic prefix extension, channel access priority class (CAPC), and UL channel access type (see TS 38.212 [17], clause 7.3.1) applicable for DCI format 0_1 and DCI format 0_2, respectively. The fields ul-AccessConfigListDCI-0-1-r16 and ul-AccessConfigListDCI-0-2-r17 are only applicable for FR1 (see TS 38.212 [17], Table 7.3.1.1.2-35). The field ul-AccessConfigListDCI-0-1-r17 only contains a list of UL channel access types and is only applicable for FR2-2 (see TS 38.212 [17], Table 7.3.1.1.2-35A).

ul-FullPowerTransmission Configures the UE with UL full power transmission mode as specified in TS 38.213. This field is not configured if ul-powerControl is configured in the BWP-UplinkDedicated in which the PUCCH-Config is included.

UCI-OnPUSCH field descriptions

betaOffsets Selection between and configuration of dynamic and semi-static beta-offset for DCI formats other than DCI format 0_2. If the field is not configured, the UE applies the value ‘semiStatic’ (see TS 38.213 [13], clause 9.3).

scaling Indicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI formats other than DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on. The value configured herein is applicable for PUSCH with configured grant (see TS 38.212 [17], clause 6.3).

UCI-OnPUSCH-DCI-0-2 field descriptions

betaOffsetsDCI-0-2 Configuration of beta-offset for DCI format 0_2. If semiStaticDCI-0-2 is chosen, the UE shall apply the value of 0 bit for the field of beta offset indicator in DCI format 0_2. If dynamicDCI-0-2 is chosen, the UE shall apply the value of 1 bit or 2 bits for the field of beta offset indicator in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9.3).

dynamicDCI-0-2 Indicates the UE applies the value ‘dynamic’ for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.3).

semiStaticDCI-0-2 Indicates the UE applies the value ‘semiStatic’ for DCI format 0_2. (see TS 38.212 [17], clause 7.3.1 and see TS 38.213 [13], clause 9.3).

scalingDCI-0-2 Indicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on (see TS 38.212 [17], clause 6.3).

Conditional Presence	Explanation
codebookBased	The field is mandatory present if txConfig is set to codebook and absent otherwise.
RepTypeB	The field is optionally present, Need S, if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeB. It is absent otherwise.
RepTypeB2	The field is optionally present, Need S, if pusch-RepTypeIndicatorDCI-0-1 or pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB. It is absent otherwise.
SRSsets	This field is mandatory present when UE is configured with two SRS sets in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage codebook or non-codebook.

– PUSCH-ConfigCommon

The IE PUSCH-ConfigCommon is used to configure the cell specific PUSCH parameters.

PUSCH-ConfigCommon information element

— ASN1START

— TAG-PUSCH-CONFIGCOMMON-START

PUSCH-ConfigCommon ::= SEQUENCE {

groupHoppingEnabledTransformPrecoding ENUMERATED {enabled} OPTIONAL, — Need R

pusch-TimeDomainAllocationList PUSCH-TimeDomainResourceAllocationList OPTIONAL, — Need R

msg3-DeltaPreamble INTEGER (-1..6) OPTIONAL, — Need R

p0-NominalWithGrant INTEGER (-202..24) OPTIONAL, — Need R

…

}

— TAG-PUSCH-CONFIGCOMMON-STOP

— ASN1STOP

PUSCH-ConfigCommon field descriptions

groupHoppingEnabledTransformPrecoding For DMRS transmission with transform precoder, the NW may configure group hopping by this cell-specific parameter, see TS 38.211 [16], clause 6.4.1.1.1.2.

msg3-DeltaPreamble Power offset between msg3 and RACH preamble transmission. Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1)

p0-NominalWithGrant P0 value for PUSCH with grant (except msg3). Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.1) This field is cell specific

pusch-TimeDomainAllocationList List of time domain allocations for timing of UL assignment to UL data (see TS 38.214 [19], table 6.1.2.1.1-1).

– PUSCH-PowerControl

The IE PUSCH-PowerControl is used to configure UE specific power control parameter for PUSCH.

PUSCH-PowerControl information element

— ASN1START

— TAG-PUSCH-POWERCONTROL-START

PUSCH-PowerControl ::= SEQUENCE {

tpc-Accumulation ENUMERATED { disabled } OPTIONAL, — Need S

msg3-Alpha Alpha OPTIONAL, — Need S

p0-NominalWithoutGrant INTEGER (-202..24) OPTIONAL, — Need M

p0-AlphaSets SEQUENCE (SIZE (1..maxNrofP0-PUSCH-AlphaSets)) OF P0-PUSCH-AlphaSet OPTIONAL, — Need M

pathlossReferenceRSToAddModList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS

OPTIONAL, — Need N

pathlossReferenceRSToReleaseList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS-Id

OPTIONAL, — Need N

twoPUSCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, — Need S

deltaMCS ENUMERATED {enabled} OPTIONAL, — Need S

sri-PUSCH-MappingToAddModList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControl

OPTIONAL, — Need N

sri-PUSCH-MappingToReleaseList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControlId

OPTIONAL — Need N

}

P0-PUSCH-AlphaSet ::= SEQUENCE {

p0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId,

p0 INTEGER (-16..15) OPTIONAL, — Need S

alpha Alpha OPTIONAL — Need S

}

P0-PUSCH-AlphaSetId ::= INTEGER (0..maxNrofP0-PUSCH-AlphaSets-1)

PUSCH-PathlossReferenceRS ::= SEQUENCE {

pusch-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id,

referenceSignal CHOICE {

ssb-Index SSB-Index,

csi-RS-Index NZP-CSI-RS-ResourceId

}

}

PUSCH-PathlossReferenceRS-r16 ::= SEQUENCE {

pusch-PathlossReferenceRS-Id-r16 PUSCH-PathlossReferenceRS-Id-v1610,

referenceSignal-r16 CHOICE {

ssb-Index-r16 SSB-Index,

csi-RS-Index-r16 NZP-CSI-RS-ResourceId

}

}

PUSCH-PathlossReferenceRS-v1710 ::= SEQUENCE {

pusch-PathlossReferenceRS-Id-r17 PUSCH-PathlossReferenceRS-Id-r17,

additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL — Need R

}

PUSCH-PathlossReferenceRS-Id ::= INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1)

PUSCH-PathlossReferenceRS-Id-v1610 ::= INTEGER (maxNrofPUSCH-PathlossReferenceRSs..maxNrofPUSCH-PathlossReferenceRSs-1-r16)

PUSCH-PathlossReferenceRS-Id-r17 ::= INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1-r16)

SRI-PUSCH-PowerControl ::= SEQUENCE {

sri-PUSCH-PowerControlId SRI-PUSCH-PowerControlId,

sri-PUSCH-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id,

sri-P0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId,

sri-PUSCH-ClosedLoopIndex ENUMERATED { i0, i1 }

}

SRI-PUSCH-PowerControlId ::= INTEGER (0..maxNrofSRI-PUSCH-Mappings-1)

PUSCH-PowerControl-v1610 ::= SEQUENCE {

pathlossReferenceRSToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSsDiff-r16)) OF PUSCH-PathlossReferenceRS-r16

OPTIONAL, — Need N

pathlossReferenceRSToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSsDiff-r16)) OF PUSCH-PathlossReferenceRS-Id-v1610

OPTIONAL, — Need N

p0-PUSCH-SetList-r16 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF P0-PUSCH-Set-r16 OPTIONAL, — Need R

olpc-ParameterSet SEQUENCE {

olpc-ParameterSetDCI-0-1-r16 INTEGER (1..2) OPTIONAL, — Need R

olpc-ParameterSetDCI-0-2-r16 INTEGER (1..2) OPTIONAL — Need R

} OPTIONAL, — Need M

…,

[[

sri-PUSCH-MappingToAddModList2-r17 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControl

OPTIONAL, — Need N

sri-PUSCH-MappingToReleaseList2-r17 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControlId OPTIONAL, — Need N

p0-PUSCH-SetList2-r17 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF P0-PUSCH-Set-r16 OPTIONAL, — Need R

pathlossReferenceRSToAddModListExt-v1710 SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs-r16)) OF PUSCH-PathlossReferenceRS-v1710 OPTIONAL — Need N

]]

}

P0-PUSCH-Set-r16 ::= SEQUENCE {

p0-PUSCH-SetId-r16 P0-PUSCH-SetId-r16,

p0-List-r16 SEQUENCE (SIZE (1..maxNrofP0-PUSCH-Set-r16)) OF P0-PUSCH-r16 OPTIONAL, — Need R

…

}

P0-PUSCH-SetId-r16 ::= INTEGER (0..maxNrofSRI-PUSCH-Mappings-1)

P0-PUSCH-r16 ::= INTEGER (-16..15)

— TAG-PUSCH-POWERCONTROL-STOP

— ASN1STOP

P0-PUSCH-AlphaSet field descriptions

alpha alpha value for PUSCH with grant (except msg3) (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 1.

p0 P0 value for PUSCH with grant (except msg3) in steps of 1dB (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 0.

P0-PUSCH-Set field descriptions

p0-List Configuration of {p0-PUSCH, p0-PUSCH} sets for PUSCH. If SRI is present in the DCI, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and both olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 are configured to be 1 bit, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and if any of olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 is configured to be 2 bits, then two p0-PUSCH values can be configured in P0-PUSCH-Set (see TS 38.213 [13] clause 7 and TS 38.212 [17] clause 7.3.1).

p0-PUSCH-SetId Configure the index of a p0-PUSCH-Set (see TS 38.213 [13] clause 7 and TS 38.212 [17] clause 7.3.1).

PUSCH-PowerControl field descriptions

deltaMCS Indicates whether to apply delta MCS. When the field is absent, the UE applies Ks = 0 in delta_TFC formula for PUSCH (see TS 38.213 [13], clause 7.1).

msg3-Alpha Dedicated alpha value for msg3 PUSCH (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 1.

olpc-ParameterSetDCI-0-1, olpc-ParameterSetDCI-0-2 Configures the number of bits for Open-loop power control parameter set indication for DCI format 0_1/0_2 in case SRI is not configured in the DCI. 2 bits is applicable only if SRI is not present in the DCI format 0_1. The field olpc-ParameterSetDCI-0-1 applies to DCI format 0_1 and the field olpc-ParameterSetDCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11).

p0-AlphaSets Configuration {p0-pusch, alpha} sets for PUSCH (except msg3 and msgA PUSCH), i.e., { {p0,alpha,index1}, {p0,alpha,index2},…} (see TS 38.213 [13], clause 7.1). When no set is configured, the UE uses the P0-nominal for msg3/msgA PUSCH, P0-UE is set to 0 and alpha is set according to either msg3-Alpha or msgA-Alpha (see TS 38.213 [13], clause 7.1).

p0-NominalWithoutGrant P0 value for UL grant-free/SPS based PUSCH. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.1).

p0-PUSCH-SetList Configure one additional P0-PUSCH-Set per SRI. If present, the one bit or 2 bits in the DCI is used to dynamically indicate among the P0 value from the existing P0-PUSCH-AlphaSet and the P0 value(s) from the P0-PUSCH-Set (See TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 17).

p0-PUSCH-SetList2 For indicating per-TRP OLPC set in DCI format 0_1/0_2 with the legacy field, a second p0-PUSCH-SetList-r16 is used. When this field is present the p0-PUSCH-SetList corresponds to the first SRS resource set (see TS 38.213).

pathlossReferenceRSToAddModList, pathlossReferenceRSToAddModListSizeExt, pathlossReferenceRSToAddModListExt A set of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for PUSCH path loss estimation. The set consists of Reference Signals configured using pathLossReferenceRSToAddModList and Reference Signals configured using pathlossReferenceRSToAddModListSizeExt. Up to maxNrofPUSCH-PathlossReferenceRSs may be configured (see TS 38.213 [13], clause 7.1). When pathlossReferenceRSToAddModListExt is included, its number of entries is the number of entries of pathlossReferenceRSToAddModList plus the number of entries of pathlossReferenceRSToAddModListSizeExt-v1610 and its n-th entry corresponds to the n-th entry of the concatenated list made of pathlossReferenceRSToAddModList and pathlossReferenceRSToAddModListSizeExt-v1610. Network configures the additionalPCI only when reference signal is SSB.

pathlossReferenceRSToReleaseList, pathlossReferenceRSToReleaseListSizeExt Lists of reference signals for PUSCH path loss estimation to be released by the UE.

sri-PUSCH-MappingToAddModList A list of SRI-PUSCH-PowerControl elements among which one is selected by the SRI field in DCI (see TS 38.213 [13], clause 7.1).

sri-PUSCH-MappingToAddModList2 A list of SRI-PUSCH-PowerControl elements for second SRS-resource set, among which one is selected by the SRI field in DCI (see TS 38.213 [13], clause 7.1). When this field is present the sri-PUSCH-MappingToAddModList corresponds to the first SRS resource set for PUSCH.

tpc-Accumulation If enabled, UE applies TPC commands via accumulation. If not enabled, UE applies the TPC command without accumulation. If the field is absent, TPC accumulation is enabled (see TS 38.213 [13], clause 7.1).

twoPUSCH-PC-AdjustmentStates Number of PUSCH power control adjustment states maintained by the UE (i.e., fc(i)). If the field is present (n2) the UE maintains two power control states (i.e., fc(i,0) and fc(i,1)). If the field is absent, it maintains one power control state (i.e., fc(i,0)) (see TS 38.213 [13], clause 7.1).

SRI-PUSCH-PowerControl field descriptions

sri-P0-PUSCH-AlphaSetId The ID of a P0-PUSCH-AlphaSet as configured in p0-AlphaSets in PUSCH-PowerControl.

sri-PUSCH-ClosedLoopIndex The index of the closed power control loop associated with this SRI-PUSCH-PowerControl.

sri-PUSCH-PathlossReferenceRS-Id The ID of PUSCH-PathlossReferenceRS as configured in the pathlossReferenceRSToAddModList in PUSCH-PowerControl.

sri-PUSCH-PowerControlId The ID of this SRI-PUSCH-PowerControl configuration. It is used as the codepoint (payload) in the SRI DCI field.

– PUSCH-ServingCellConfig

The IE PUSCH-ServingCellConfig is used to configure UE specific PUSCH parameters that are common across the UE’s BWPs of one serving cell.

PUSCH-ServingCellConfig information element

— ASN1START

— TAG-PUSCH-SERVINGCELLCONFIG-START

PUSCH-ServingCellConfig ::= SEQUENCE {

codeBlockGroupTransmission SetupRelease { PUSCH-CodeBlockGroupTransmission } OPTIONAL, — Need M

rateMatching ENUMERATED {limitedBufferRM} OPTIONAL, — Need S

xOverhead ENUMERATED {xoh6, xoh12, xoh18} OPTIONAL, — Need S

…,

[[

maxMIMO-Layers INTEGER (1..4) OPTIONAL, — Need M

processingType2Enabled BOOLEAN OPTIONAL — Need M

]],

[[

maxMIMO-LayersDCI-0-2-r16 SetupRelease { MaxMIMO-LayersDCI-0-2-r16} OPTIONAL — Need M

]],

[[

nrofHARQ-ProcessesForPUSCH-r17 ENUMERATED {n32} OPTIONAL, — Need R

uplinkHARQ-mode-r17 SetupRelease { UplinkHARQ-mode-r17} OPTIONAL — Need M

]]

}

PUSCH-CodeBlockGroupTransmission ::= SEQUENCE {

maxCodeBlockGroupsPerTransportBlock ENUMERATED {n2, n4, n6, n8},

…

}

MaxMIMO-LayersDCI-0-2-r16 ::= INTEGER (1..4)

UplinkHARQ-mode-r17 ::= BIT STRING (SIZE (32))

— TAG-PUSCH-SERVINGCELLCONFIG-STOP

— ASN1STOP

PUSCH-CodeBlockGroupTransmission field descriptions

maxCodeBlockGroupsPerTransportBlock Maximum number of code-block-groups (CBGs) per TB (see TS 38.213 [13], clause 9.1).

PUSCH-ServingCellConfig field descriptions

codeBlockGroupTransmission Enables and configures code-block-group (CBG) based transmission (see TS 38.214 [19], clause 5.1.5). The network does not configure this field if the SCS is 480 or 960 kHz.

maxMIMO-Layers Indicates the maximum MIMO layer to be used for PUSCH in all BWPs of the corresponding UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRank to the same value. The field maxMIMO-Layers refers to DCI format 0_1.

nrofHARQ-ProcessesForPUSCH The number of HARQ processes to be used on the PUSCH of a serving cell. Value n32 corresponds to 32 HARQ processes. If the field is absent, the UE uses 16 HARQ processes (see TS 38.214 [19], clause 6.1).

processingType2Enabled Enables configuration of advanced processing time capability 2 for PUSCH (see 38.214 [19], clause 6.4).

rateMatching Enables LBRM (Limited buffer rate-matching). When the field is absent the UE applies FBRM (Full buffer rate-matchingLBRM) (see TS 38.212 [17], clause 5.4.2).

xOverhead If the field is absent, the UE applies the value ‘xoh0’ (see TS 38.214 [19], clause 5.1.3.2).

maxMIMO-LayersDCI-0-2 Indicates the maximum MIMO layer to be used for PUSCH for DCI format 0_2 in all BWPs of the corresponding UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRankDCI-0-2 to the same value.

uplinkHARQ-mode Used to set the HARQ mode per HARQ process ID, see TS 38.321 [3]. The first/leftmost bit corresponds to HARQ process ID 0, the next bit to HARQ process ID 1 and so on. Bits corresponding to HARQ process IDs that are not configured shall be ignored. A bit set to one identifies a HARQ process with HARQmodeA and a bit set to zero identifies a HARQ process with HARQ modeB. This field applies for SRBs and DRBs.

– PUSCH-TimeDomainResourceAllocationList

The IE PUSCH-TimeDomainResourceAllocation is used to configure a time domain relation between PDCCH and PUSCH. PUSCH-TimeDomainResourceAllocationList contains one or more of such PUSCH-TimeDomainResourceAllocations. The network indicates in the UL grant which of the configured time domain allocations the UE shall apply for that UL grant. The UE determines the bit width of the DCI field based on the number of entries in the PUSCH-TimeDomainResourceAllocationList. Value 0 in the DCI field refers to the first element in this list, value 1 in the DCI field refers to the second element in this list, and so on.

PUSCH-TimeDomainResourceAllocation information element

— ASN1START

— TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START

PUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocation

PUSCH-TimeDomainResourceAllocation ::= SEQUENCE {

k2 INTEGER(0..32) OPTIONAL, — Need S

mappingType ENUMERATED {typeA, typeB},

startSymbolAndLength INTEGER (0..127)

}

PUSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations-r16)) OF PUSCH-TimeDomainResourceAllocation-r16

PUSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE {

k2-r16 INTEGER(0..32) OPTIONAL, — Need S

puschAllocationList-r16 SEQUENCE (SIZE(1..maxNrofMultiplePUSCHs-r16)) OF PUSCH-Allocation-r16,

…

}

PUSCH-Allocation-r16 ::= SEQUENCE {

mappingType-r16 ENUMERATED {typeA, typeB} OPTIONAL, — Cond NotFormat01-02-Or-TypeA

startSymbolAndLength-r16 INTEGER (0..127) OPTIONAL, — Cond NotFormat01-02-Or-TypeA

startSymbol-r16 INTEGER (0..13) OPTIONAL, — Cond RepTypeB

length-r16 INTEGER (1..14) OPTIONAL, — Cond RepTypeB

numberOfRepetitions-r16 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} OPTIONAL, — Cond Format01-02

…,

[[

numberOfRepetitionsExt-r17 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16, n20, n24, n28, n32, spare4, spare3, spare2,

spare1} OPTIONAL, — Cond Format01-02-For-TypeA

numberOfSlotsTBoMS-r17 ENUMERATED {n1, n2, n4, n8, spare4, spare3, spare2, spare1} OPTIONAL, — Need R

extendedK2-r17 INTEGER (0..128) OPTIONAL — Cond MultiPUSCH

]]

}

— TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP

— ASN1STOP

PUSCH-TimeDomainResourceAllocationList field descriptions

extendedK2 Corresponds to L1 parameter ‘K2’ (see TS 38.214 [19], clause 6.1.2.1) configurable per PUSCH allocation. Only values {0..32} are applicable for PUSCH SCS of 120 kHz. When the field is absent for the first PUSCH if multiple PUSCH are configured per PDCCH, or when the field is absent and only one PUSCH is configured per PDCCH, the UE applies the value 1 when PUSCH SCS is 15/30 kHz; the value 2 when PUSCH SCS is 60 kHz, the value 3 when PUSCH SCS is 120 kHz, the value 11 when PUSCH SCS is 480 kHz, and the value 21 when PUSCH SCS is 960 kHz.

k2 Corresponds to L1 parameter ‘K2’ (see TS 38.214 [19], clause 6.1.2.1). When the field is absent the UE applies the value 1 when PUSCH SCS is 15/30 kHz; the value 2 when PUSCH SCS is 60 kHz, and the value 3 when PUSCH SCS is 120 kHz. k2 is absent/ignored if extendedK2 is present.

length Indicates the length allocated for PUSCH for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1).

mappingType Mapping type (see TS 38.214 [19], clause 6.1.2.1).

numberOfRepetitions Number of repetitions for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1). When numberOfSlotsTBoMS-r17 is set to 2, 4 or 8 (i.e. TB processing over multi-slot (TBoMS) PUSCH is enabled), it indicates the number of repetitions of a single TBoMS.

numberOfRepetitionsExt Number of repetitions for DCI format 0_1/0_2 if pusch-RepTypeIndicatorDCI-0-1/pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeA (see TS 38.214 [19], clause 6.1.2.1). If this field is present, the field numberOfRepeitions-r16 is ignored for PUSCH repetition Type A.

numberOfSlotsTBoMS Number of slots allocated for TB processing over multi-slot PUSCH for DCI format 0_1/0_2. If a number of repetitions K is configured by numberOfRepetitions or numberOfRepetitionsExt, the network configures numberOfSlotsTBoMS (N) and K such that N*K ≤ 32 (see TS 38.214 [19], clause 6.1.2.1).

puschAllocationList The field puschAllocationList-r16 indicates one or multiple PUSCH continuous in time domain which share a common k2 (see TS 38.214 [19], clause 6.1.2.1). The field pusch-AllocationList-r17 configures one or multiple PUSCH that may be in consecutive or non-consecutive slots (see TS 38.214 [19], clause 6.1.2.1). The puschAllocationList-r16 only has one element in pusch-TimeDomainAllocationListDCI-0-1-r16 and in pusch-TimeDomainAllocationListDCI-0-2-r16.

startSymbol Indicates the index of start symbol for PUSCH for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1).

startSymbolAndLength An index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary. (see TS 38.214 [19], clause 6.1.2.1).

Conditional Presence	Explanation
Format01-02	In pusch-TimeDomainAllocationListForMultiPUSCH-r16 and pusch-TimeDomainAllocationListForMultiPUSCH-r17, the field is absent. In pusch-TimeDomainAllocationListDCI-0-1 and in pusch-TimeDomainAllocationListDCI-0-2, the field is mandatory present.
Format01-02-For-TypeA	In pusch-TimeDomainAllocationListForMultiPUSCH-r16, the field is absent. In pusch-TimeDomainAllocationListDCI-0-1, the field is optionally present if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeA, Need R. It is absent otherwise, Need R. In pusch-TimeDomainAllocationListDCI-0-2, the field is optionally present if pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeA, Need R. It is absent otherwise, Need R.
NotFormat01-02-Or-TypeA	In pusch-TimeDomainAllocationListForMultiPUSCH-r16 and pusch-TimeDomainAllocationListForMultiPUSCH-r17, the field is mandatory present. In pusch-TimeDomainAllocationListDCI-0-1, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeA. It is absent otherwise, Need R. In pusch-TimeDomainAllocationListDCI-0-2, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeA. It is absent otherwise, Need R.
RepTypeB	In pusch-TimeDomainAllocationListForMultiPUSCH-r16 and pusch-TimeDomainAllocationListForMultiPUSCH-r17, the field is absent. In pusch-TimeDomainAllocationListDCI-0-1, the field is optionally present if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeB, Need R. It is absent otherwise, Need R. In pusch-TimeDomainAllocationListDCI-0-2, the field is optionally present if pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB, Need R. It is absent otherwise, Need R.
MultiPUSCH	In case size of puschAllocationList is higher than 1, the field extendedK2(n) corresponding to k2 of the n-th PUSCH, n>1, is mandatory present. Otherwise, it is optionally present, Need S.

– PUSCH-TPC-CommandConfig

The IE PUSCH-TPC-CommandConfig is used to configure the UE for extracting TPC commands for PUSCH from a group-TPC messages on DCI.

PUSCH-TPC-CommandConfig information element

— ASN1START

— TAG-PUSCH-TPC-COMMANDCONFIG-START

PUSCH-TPC-CommandConfig ::= SEQUENCE {

tpc-Index INTEGER (1..15) OPTIONAL, — Cond SUL

tpc-IndexSUL INTEGER (1..15) OPTIONAL, — Cond SUL-Only

targetCell ServCellIndex OPTIONAL, — Need S

…

}

— TAG-PUSCH-TPC-COMMANDCONFIG-STOP

— ASN1STOP

PUSCH-TPC-CommandConfig field descriptions

targetCell The serving cell to which the acquired power control commands are applicable. If the value is absent, the UE applies the TPC commands to the serving cell on which the command has been received.

tpc-Index An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload.

tpc-IndexSUL An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload.

Conditional Presence	Explanation
SUL-Only	The field is optionally present, Need R, if supplementaryUplink is configured within ServingCellConfig. It is absent otherwise.
SUL	The field is optionally present, Need R, if supplementaryUplink is configured within ServingCellConfig. It is mandatory present otherwise.

– Q-OffsetRange

The IE Q-OffsetRange is used to indicate a cell, beam or measurement object specific offset to be applied when evaluating candidates for cell re-selection or when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, dB-22 corresponds to -22 dB and so on.

Q-OffsetRange information element

— ASN1START

— TAG-Q-OFFSETRANGE-START

Q-OffsetRange ::= ENUMERATED {

dB-24, dB-22, dB-20, dB-18, dB-16, dB-14,

dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3,

dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5,

dB6, dB8, dB10, dB12, dB14, dB16, dB18,

dB20, dB22, dB24}

— TAG-Q-OFFSETRANGE-STOP

— ASN1STOP

– Q-QualMin

The IE Q-QualMin is used to indicate for cell selection/ re-selection the required minimum received RSRQ level in the (NR) cell. Corresponds to parameter Q_qualmin in TS 38.304 [20]. Actual value Q_qualmin = field value [dB].

Q-QualMin information element

— ASN1START

— TAG-Q-QUALMIN-START

Q-QualMin ::= INTEGER (-43..-12)

— TAG-Q-QUALMIN-STOP

— ASN1STOP

– Q-RxLevMin

The IE Q-RxLevMin is used to indicate for cell selection/ re-selection the required minimum received RSRP level in the (NR) cell. Corresponds to parameter Q_rxlevmin in TS 38.304 [20]. Actual value Q_rxlevmin = field value * 2 [dBm].

Q-RxLevMin information element

— ASN1START

— TAG-Q-RXLEVMIN-START

Q-RxLevMin ::= INTEGER (-70..-22)

— TAG-Q-RXLEVMIN-STOP

— ASN1STOP

– QuantityConfig

The IE QuantityConfig specifies the measurement quantities and layer 3 filtering coefficients for NR and inter-RAT measurements.

QuantityConfig information element

— ASN1START

— TAG-QUANTITYCONFIG-START

QuantityConfig ::= SEQUENCE {

quantityConfigNR-List SEQUENCE (SIZE (1..maxNrofQuantityConfig)) OF QuantityConfigNR OPTIONAL, — Need M

…,

[[

quantityConfigEUTRA FilterConfig OPTIONAL — Need M

]],

[[

quantityConfigUTRA-FDD-r16 QuantityConfigUTRA-FDD-r16 OPTIONAL, — Need M

quantityConfigCLI-r16 FilterConfigCLI-r16 OPTIONAL — Need M

]]

}

QuantityConfigNR::= SEQUENCE {

quantityConfigCell QuantityConfigRS,

quantityConfigRS-Index QuantityConfigRS OPTIONAL — Need M

}

QuantityConfigRS ::= SEQUENCE {

ssb-FilterConfig FilterConfig,

csi-RS-FilterConfig FilterConfig

}

FilterConfig ::= SEQUENCE {

filterCoefficientRSRP FilterCoefficient DEFAULT fc4,

filterCoefficientRSRQ FilterCoefficient DEFAULT fc4,

filterCoefficientRS-SINR FilterCoefficient DEFAULT fc4

}

FilterConfigCLI-r16 ::= SEQUENCE {

filterCoefficientSRS-RSRP-r16 FilterCoefficient DEFAULT fc4,

filterCoefficientCLI-RSSI-r16 FilterCoefficient DEFAULT fc4

}

QuantityConfigUTRA-FDD-r16 ::= SEQUENCE {

filterCoefficientRSCP-r16 FilterCoefficient DEFAULT fc4,

filterCoefficientEcNO-r16 FilterCoefficient DEFAULT fc4

}

— TAG-QUANTITYCONFIG-STOP

— ASN1STOP

QuantityConfigNR field descriptions

quantityConfigCell Specifies L3 filter configurations for cell measurement results for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR).

quantityConfigRS-Index Specifies L3 filter configurations for measurement results per RS index for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR).

QuantityConfigRS field descriptions

csi-RS-FilterConfig CSI-RS based L3 filter configurations: Specifies L3 filter configurations for CSI-RSRP, CSI-RSRQ and CSI-SINR measurement results from the L1 filter(s), as defined in TS 38.215 [9].

ssb-FilterConfig SS Block based L3 filter configurations: Specifies L3 filter configurations for SS-RSRP, SS-RSRQ and SS-SINR measurement results from the L1 filter(s), as defined in TS 38.215 [9].

QuantityConfigUTRA-FDD field descriptions

filterCoefficientRSCP Specifies L3 filter coefficient for FDD UTRAN CPICH_RSCP measuement results from L1 filter.

filterCoefficientEcN0 Specifies L3 filter coefficient for FDD UTRAN CPICH_EcN0 measuement results from L1 filter.

– RACH-ConfigCommon

The IE RACH-ConfigCommon is used to specify the cell specific random-access parameters.

RACH-ConfigCommon information element

— ASN1START

— TAG-RACH-CONFIGCOMMON-START

RACH-ConfigCommon ::= SEQUENCE {

rach-ConfigGeneric RACH-ConfigGeneric,

totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL, — Need S

ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE {

oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32},

four INTEGER (1..16),

eight INTEGER (1..8),

sixteen INTEGER (1..4)

} OPTIONAL, — Need M

groupBconfigured SEQUENCE {

ra-Msg3SizeGroupA ENUMERATED {b56, b144, b208, b256, b282, b480, b640,

b800, b1000, b72, spare6, spare5,spare4, spare3, spare2, spare1},

messagePowerOffsetGroupB ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18},

numberOfRA-PreamblesGroupA INTEGER (1..64)

} OPTIONAL, — Need R

ra-ContentionResolutionTimer ENUMERATED { sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64},

rsrp-ThresholdSSB RSRP-Range OPTIONAL, — Need R

rsrp-ThresholdSSB-SUL RSRP-Range OPTIONAL, — Cond SUL

prach-RootSequenceIndex CHOICE {

l839 INTEGER (0..837),

l139 INTEGER (0..137)

},

msg1-SubcarrierSpacing SubcarrierSpacing OPTIONAL, — Cond L139

restrictedSetConfig ENUMERATED {unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB},

msg3-transformPrecoder ENUMERATED {enabled} OPTIONAL, — Need R

…,

[[

ra-PrioritizationForAccessIdentity-r16 SEQUENCE {

ra-Prioritization-r16 RA-Prioritization,

ra-PrioritizationForAI-r16 BIT STRING (SIZE (2))

} OPTIONAL, — Cond InitialBWP-Only

prach-RootSequenceIndex-r16 CHOICE {

l571 INTEGER (0..569),

l1151 INTEGER (0..1149)

} OPTIONAL — Need R

]],

[[

ra-PrioritizationForSlicing-r17 RA-PrioritizationForSlicing-r17 OPTIONAL, — Cond InitialBWP-Only

featureCombinationPreamblesList-r17 SEQUENCE (SIZE(1..maxFeatureCombPreamblesPerRACHResource-r17)) OF FeatureCombinationPreambles-r17 OPTIONAL — Cond AdditionalRACH-AndRedCap

]]

}

— TAG-RACH-CONFIGCOMMON-STOP

— ASN1STOP

RACH-ConfigCommon field descriptions

featureCombinationPreamblesList Specifies a series of preamble partitions each associated to a combination of features and 4-step RA. The network does not configure this list to have more than 16 entries.

messagePowerOffsetGroupB Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to –infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on. (see TS 38.321 [3], clause 5.1.2)

msg1-SubcarrierSpacing Subcarrier spacing of PRACH (see TS 38.211 [16], clause 5.3.2). Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz If absent, the UE applies the SCS as derived from the prach-ConfigurationIndex in RACH-ConfigGeneric (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211 [16]). The value also applies to contention free random access (RACH-ConfigDedicated), to SI-request and to contention-based beam failure recovery (CB-BFR). But it does not apply for contention free beam failure recovery (CF-BFR) (see BeamFailureRecoveryConfig).

msg3-transformPrecoder Enables the transform precoder for Msg3 transmission according to clause 6.1.3 of TS 38.214 [19]. If the field is absent, the UE disables the transformer precoder (see TS 38.213 [13], clause 8.3).

numberOfRA-PreamblesGroupA The number of CB preambles per SSB in group A. This determines implicitly the number of CB preambles per SSB available in group B. (see TS 38.321 [3], clause 5.1.1). The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

prach-RootSequenceIndex PRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1). The value range depends on whether L=839 or L=139 or L=571 or L=1151. The length of the root sequence corresponding with the index indicated in this IE should be consistent with the one indicated in prach-ConfigurationIndex in the RACH-ConfigDedicated (if configured). If prach-RootSequenceIndex-r16 is signalled, UE shall ignore the prach-RootSequenceIndex (without suffix). For FR2-2, only the following values are applicable depending on the used subcarrier spacing: 120 kHz: L=139, L=571, and L=1151 480 kHz: L=139, and L=571 960 kHz: L=139

ra-ContentionResolutionTimer The initial value for the contention resolution timer (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on.

ra-Msg3SizeGroupA Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see TS 38.321 [3], clause 5.1.2).

ra-Prioritization Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a).

ra-PrioritizationForAI Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 indicates that the field ra-Prioritization-r16 applies otherwise the field does not apply (see TS 23.501 [32]).

ra-PrioritizationForSlicing Parameters which apply to configure prioritized CBRA 4-step random access type for slicing.

rach-ConfigGeneric RACH parameters for both regular random access and beam failure recovery.

restrictedSetConfig Configuration of an unrestricted set or one of two types of restricted sets, see TS 38.211 [16], clause 6.3.3.1.

rsrp-ThresholdSSB UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213 [13]).

rsrp-ThresholdSSB-SUL The UE selects SUL carrier to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). The value applies to all the BWPs and all RACH configurations.

ssb-perRACH-OccasionAndCB-PreamblesPerSSB The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEighth corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion). See TS 38.213 [13].

totalNumberOfRA-Preambles Total number of preambles used for contention based and contention free 4-step or 2-step random access in the RACH resources defined in RACH-ConfigCommon, excluding preambles used for other purposes (e.g. for SI request). If the field is absent, all 64 preambles are available for RA. The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, i.e. it should be a multiple of the number of SSBs per RACH occasion.

Conditional Presence	Explanation
AdditionalRACH-AndRedCap	The field is mandatory present if the RACH-ConfigCommon is included in initialUplinkBWP-RedCap or in an AdditionalRACH-Config. Otherwise, it is optional, Need R.
InitialBWP-Only	This field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise, the field is absent.
L139	The field is mandatory present if prach-RootSequenceIndex L=139, otherwise the field is absent, Need S.
SUL	The field is mandatory present in rach-ConfigCommon in initialUplinkBWP if supplementaryUplink is configured in ServingCellConfigCommonSIB or if supplementaryUplinkConfig is configured in ServingCellConfigCommon; otherwise, the field is absent. This field is not configured in additionalRACH-Config.

– RACH-ConfigCommonTwoStepRA

The IE RACH-ConfigCommonTwoStepRA is used to specify cell specific 2-step random-access type parameters.

RACH-ConfigCommonTwoStepRA information element

— ASN1START

— TAG-RACH-CONFIGCOMMONTWOSTEPRA-START

RACH-ConfigCommonTwoStepRA-r16 ::= SEQUENCE {

rach-ConfigGenericTwoStepRA-r16 RACH-ConfigGenericTwoStepRA-r16,

msgA-TotalNumberOfRA-Preambles-r16 INTEGER (1..63) OPTIONAL, — Need S

msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB-r16 CHOICE {

oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32},

four INTEGER (1..16),

eight INTEGER (1..8),

sixteen INTEGER (1..4)

} OPTIONAL, — Cond 2StepOnly

msgA-CB-PreamblesPerSSB-PerSharedRO-r16 INTEGER (1..60) OPTIONAL, — Cond SharedRO

msgA-SSB-SharedRO-MaskIndex-r16 INTEGER (1..15) OPTIONAL, — Need S

groupB-ConfiguredTwoStepRA-r16 GroupB-ConfiguredTwoStepRA-r16 OPTIONAL, — Need S

msgA-PRACH-RootSequenceIndex-r16 CHOICE {

l839 INTEGER (0..837),

l139 INTEGER (0..137),

l571 INTEGER (0..569),

l1151 INTEGER (0..1149)

} OPTIONAL, — Cond 2StepOnly

msgA-TransMax-r16 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, — Need R

msgA-RSRP-Threshold-r16 RSRP-Range OPTIONAL, — Cond 2Step4Step

msgA-RSRP-ThresholdSSB-r16 RSRP-Range OPTIONAL, — Need R

msgA-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, — Cond 2StepOnlyL139

msgA-RestrictedSetConfig-r16 ENUMERATED {unrestrictedSet, restrictedSetTypeA,

restrictedSetTypeB} OPTIONAL, — Cond 2StepOnly

ra-PrioritizationForAccessIdentityTwoStep-r16 SEQUENCE {

ra-Prioritization-r16 RA-Prioritization,

ra-PrioritizationForAI-r16 BIT STRING (SIZE (2))

} OPTIONAL, — Cond InitialBWP-Only

ra-ContentionResolutionTimer-r16 ENUMERATED {sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64} OPTIONAL, — Cond 2StepOnly

…,

[[

ra-PrioritizationForSlicingTwoStep-r17 RA-PrioritizationForSlicing-r17 OPTIONAL, — Cond InitialBWP-Only

featureCombinationPreamblesList-r17 SEQUENCE (SIZE(1..maxFeatureCombPreamblesPerRACHResource-r17)) OF FeatureCombinationPreambles-r17 OPTIONAL — Cond AdditionalRACH-AndRedCap

]]

}

GroupB-ConfiguredTwoStepRA-r16 ::= SEQUENCE {

ra-MsgA-SizeGroupA ENUMERATED {b56, b144, b208, b256, b282, b480, b640, b800,

b1000, b72, spare6, spare5, spare4, spare3, spare2, spare1},

messagePowerOffsetGroupB ENUMERATED {minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18},

numberOfRA-PreamblesGroupA INTEGER (1..64)

}

— TAG-RACH-CONFIGCOMMONTWOSTEPRA-STOP

— ASN1STOP

RACH-ConfigCommonTwoStepRA field descriptions

featureCombinationPreamblesList Specifies a series of preamble partitions each associated to a combination of features and 2-step RA. The network does not configure this list to have more than 16 entries.

groupB-ConfiguredTwoStepRA Preamble grouping for 2-step random access type. If the field is absent then there is only one preamble group configured and only one msgA PUSCH configuration.

msgA-CB-PreamblesPerSSB-PerSharedRO Number of contention-based preambles used for 2-step RA type from the non-CBRA 4-step type preambles associated with each SSB for RO shared with 4-step type RA. The number of preambles for 2-step RA type shall not exceed the number of preambles per SSB minus the number of contention-based preambles per SSB for 4-step type RA. The possible value range for this parameter needs to be aligned with value range for the configured SSBs per RACH occasion in ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. The field is only applicable for the case of shared ROs with 4-step type random access.

msgA-PRACH-RootSequenceIndex PRACH root sequence index. If the field is not configured in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e., not within AdditionalRACH-Config), the UE applies the value in field prach-RootSequenceIndex in RACH-ConfigCommon in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE applies the corresponding value of prach-RootSequenceIndex in RACH-ConfigCommon in the same AdditionalRACH-Config. When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access. For FR2-2, only the following values are applicable depending on the used subcarrier spacing: 120 kHz: L=139, L=571, and L=1151 480 kHz: L=139, and L=571 960 kHz: L=139

msgA-RestrictedSetConfig Configuration of an unrestricted set or one of two types of restricted sets for 2-step random access type preamble. If the field is not configured in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config), the UE applies the value in field restrictedSetConfig in RACH-ConfigCommon in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE applies the value of restrictedSetConfig in RACH-ConfigCommon in the same AdditionalRACH-Config. When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access.

msgA-RSRP-Threshold The UE selects 2-step random access type to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). This field is only present if both 2-step and 4-step RA type are configured for the BWP.

msgA-RSRP-ThresholdSSB UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213 [13]).

msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEight corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion). If the field is not configured in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config) and both 2-step and 4-step are configured for the BWP, the UE applies the value in the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. If the field is not configured in AdditionalRACH-Config and both 2-step and 4-step are configured in AdditionalRACH-Config, the UE applies the value in the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon in the same AdditionalRACH-Config. The field is not present when RACH occasions are shared between 2-step and 4-step type random access in the BWP.

msgA-SSB-SharedRO-MaskIndex Indicates the subset of 4-step type ROs shared with 2-step random access type for each SSB. This field is configured when there is more than one RO per SSB. If the field is absent, and 4-step and 2-step has shared ROs, then all ROs are shared.

msgA-SubcarrierSpacing Subcarrier spacing of PRACH (see TS 38.211 [16], clause 5.3.2). Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz. If the field is absent, the UE applies the SCS as derived from the msgA-PRACH-ConfigurationIndex in RACH-ConfigGenericTwoStepRA (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211 [16]) in case of 2-step only BWP, otherwise the UE applies the same SCS as Msg1 derived from RACH-ConfigCommon. The value also applies to contention free 2-step random access type (RACH-ConfigDedicated).

msgA-TotalNumberOfRA-Preambles Indicates the total number of preambles used for contention-based and contention-free 2-step random access type when ROs for 2-step are not shared with 4-step. If the field is absent, and 2-step and 4-step does not have shared ROs, all 64 preambles are available for 2-step random access type.

msgA-TransMax Max number of MsgA preamble transmissions performed before switching to 4-step random access (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when 2-step and 4-step RA type are configured and switching to 4-step type RA is supported. If the field is absent, switching from 2-step RA type to 4-step RA type is not allowed.

ra-ContentionResolutionTimer The initial value for the contention resolution timer for fallback RAR in case no 4-step random access type is configured (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on. If both 2-step and 4-step random access type resources are configured on the BWP, then this field is absent.

ra-Prioritization Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a).

ra-PrioritizationForAI Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 for an Access Identity indicates that the field ra-Prioritization-r16 applies, otherwise the field does not apply.

ra-PrioritizationForSlicingTwoStep Parameters which apply to configure prioritized CBRA 2-step random access type for slicing.

rach-ConfigGenericTwoStepRA 2-step random access type parameters for both regular random access and beam failure recovery.

GroupB-ConfiguredTwoStepRA field descriptions

messagePowerOffsetGroupB Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to –infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on. (see TS 38.321 [3], clause 5.1.1).

numberOfRA-PreamblesGroupA The number of CB preambles per SSB in group A for idle/inactive or connected mode. The setting of the number of preambles for each group should be consistent with msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB or msgA-CB-PreamblesPerSSB-PerSharedRO if configured.

ra-MsgA-SizeGroupA Transport block size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see TS 38.321 [3], clause 5.1.1).

Conditional Presence	Explanation
2Step4Step	The field is mandatory present if both 2-step random access type and 4-step random access type are configured in the BWP, otherwise the field is not present. The field is mandatory present in msgA-ConfigCommon field in AdditionalRACH-Config if both 2-step random access type and 4-step random access type are configured for the same feature combination in the BWP.
2StepOnlyL139	The field is mandatory present if msgA-PRACH-RootSequenceIndex L=139 and no 4-step random access type is configured, otherwise the field is absent, Need S.
2StepOnly	The field is mandatory present in msgA-ConfigCommon field in BWP-UplinkCommon if rach-ConfigCommon field is absent in this BWP-UplinkCommon, otherwise the field is optionally present in msgA-ConfigCommon field in BWP-UplinkCommon, Need S. The field is mandatory present in msgA-ConfigCommon field in AdditionalRACH-Config if rach-ConfigCommon field is absent in this AdditionalRACH-Config, otherwise the field is optionally present in msgA-ConfigCommon field in AdditionalRACH-Config, Need S.
AdditionalRACH-AndRedCap	The field is mandatory present if the RACH-ConfigCommon is included in initialUplinkBWP-RedCap or in an AdditionalRACH-Config. Otherwise, it is optional, Need R.
InitialBWP-Only	This field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise, the field is absent.
SharedRO	The field is mandatory present if the 2-step random access type occasions are shared with 4-step random access type, otherwise the field is not present.

– RACH-ConfigDedicated

The IE RACH-ConfigDedicated is used to specify the dedicated random access parameters.

RACH-ConfigDedicated information element

— ASN1START

— TAG-RACH-CONFIGDEDICATED-START

RACH-ConfigDedicated ::= SEQUENCE {

cfra CFRA OPTIONAL, — Need S

ra-Prioritization RA-Prioritization OPTIONAL, — Need N

…,

[[

ra-PrioritizationTwoStep-r16 RA-Prioritization OPTIONAL, — Need N

cfra-TwoStep-r16 CFRA-TwoStep-r16 OPTIONAL — Need S

]]

}

CFRA ::= SEQUENCE {

occasions SEQUENCE {

rach-ConfigGeneric RACH-ConfigGeneric,

ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen}

OPTIONAL — Cond Mandatory

} OPTIONAL, — Need S

resources CHOICE {

ssb SEQUENCE {

ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource,

ra-ssb-OccasionMaskIndex INTEGER (0..15)

},

csirs SEQUENCE {

csirs-ResourceList SEQUENCE (SIZE(1..maxRA-CSIRS-Resources)) OF CFRA-CSIRS-Resource,

rsrp-ThresholdCSI-RS RSRP-Range

}

},

…,

[[

totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL — Cond Occasions

]]

}

CFRA-TwoStep-r16 ::= SEQUENCE {

occasionsTwoStepRA-r16 SEQUENCE {

rach-ConfigGenericTwoStepRA-r16 RACH-ConfigGenericTwoStepRA-r16,

ssb-PerRACH-OccasionTwoStepRA-r16 ENUMERATED {oneEighth, oneFourth, oneHalf, one,

two, four, eight, sixteen}

} OPTIONAL, — Need S

msgA-CFRA-PUSCH-r16 MsgA-PUSCH-Resource-r16,

msgA-TransMax-r16 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, — Need S

resourcesTwoStep-r16 SEQUENCE {

ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource,

ra-ssb-OccasionMaskIndex INTEGER (0..15)

},

…

}

CFRA-SSB-Resource ::= SEQUENCE {

ssb SSB-Index,

ra-PreambleIndex INTEGER (0..63),

…,

[[

msgA-PUSCH-Resource-Index-r16 INTEGER (0..3071) OPTIONAL — Cond 2StepCFRA

]]

}

CFRA-CSIRS-Resource ::= SEQUENCE {

csi-RS CSI-RS-Index,

ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1),

ra-PreambleIndex INTEGER (0..63),

…

}

— TAG-RACH-CONFIGDEDICATED-STOP

— ASN1STOP

CFRA-CSIRS-Resource field descriptions

csi-RS The ID of a CSI-RS resource defined in the measurement object associated with this serving cell.

ra-OccasionList RA occasions that the UE shall use when performing CF-RA upon selecting the candidate beam identified by this CSI-RS. The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot and Third, in increasing order of indexes for PRACH slots.

ra-PreambleIndex The RA preamble index to use in the RA occasions associated with this CSI-RS.

CFRA field descriptions

occasions RA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommon in the first active UL BWP.

ra-ssb-OccasionMaskIndex Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources signalled in ssb-ResourceList.

rach-ConfigGeneric Configuration of contention free random access occasions for CFRA. The UE shall ignore preambleReceivedTargetPower, preambleTransMax, powerRampingStep, ra-ResponseWindow signaled within this field and use the corresponding values provided in RACH-ConfigCommon.

ssb-perRACH-Occasion Number of SSBs per RACH occasion.

totalNumberOfRA-Preambles Total number of preambles used for contention free random access in the RACH resources defined in CFRA, excluding preambles used for other purposes (e.g. for SI request). If the field is absent but the field occasions is present, the UE may assume all the 64 preambles are for RA. The setting should be consistent with the setting of ssb-perRACH-Occasion, if present, i.e. it should be a multiple of the number of SSBs per RACH occasion.

CFRA-SSB-Resource field descriptions

msgA-PUSCH-Resource-Index Identifies the index of the PUSCH resource used for MSGA CFRA. The PUSCH resource index indicates a valid PUSCH occasion (as specified in TS 38.213 [13], clause 8.1A) and the associated DMRS resources corresponding to a PRACH slot. The PUSCH resource indexes are sequentially numbered and are mapped to valid PUSCH occasions corresponding to a PRACH slot which are ordered, first, in increasing order of frequency resource indexes for frequency multiplexed PUSCH occasions; second, in increasing order of DMRS resource indexes within a PUSCH occasion, where a DMRS resource index is determined first in an ascending order of a DMRS port index and then in an ascending order of a DMRS sequence index, third in increasing order of time resource indexes for time multiplexed PUSCH occasions within a PUSCH slot and fourth, in increasing order of indexes for PUSCH slots. For the case of contention free 2-step random access type, if this field is absent, the UE shall use the value 0.

ra-PreambleIndex The preamble index that the UE shall use when performing CF-RA upon selecting the candidate beams identified by this SSB.

ssb The ID of an SSB transmitted by this serving cell.

CFRA-TwoStep field descriptions

msgA-CFRA-PUSCH PUSCH resource configuration(s) for msgA CFRA.

msgA-TransMax Max number of MsgA preamble transmissions performed before switching to 4-step type random access (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when 2-step and 4-step RA type are configured and switching to 4-step type RA is supported. If the field is absent in cfra-TwoStep, switching from 2-step RA type to 4-step RA type is not allowed.

occasionsTwoStepRA RA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommonTwoStepRA in the first active UL BWP.

ra-SSB-OccasionMaskIndex Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources signalled in ssb-ResourceList.

rach-ConfigGenericTwoStepRA Configuration of contention free random access occasions for CFRA 2-step random access type.

ssb-PerRACH-OccasionTwoStep Number of SSBs per RACH occasion for 2-step random access type.

RACH-ConfigDedicated field descriptions

cfra Parameters for contention free random access to a given target cell. If this field and cfra-TwoStep are absent, the UE performs contention based random access.

cfra-TwoStep Parameters for contention free 2-step random access type to a given target cell. Network ensures that cfra and cfra-TwoStep are not configured at the same time. If this field and cfra are absent, the UE performs contention based random access. This field may only be present if msgA-ConfigCommon is configured on the BWP.

ra-prioritization Parameters which apply for prioritized random access procedure to a given target cell (see TS 38.321 [3], clause 5.1.1).

ra-PrioritizationTwoStep Parameters which apply for prioritized 2-step random access type procedure to a given target cell (see TS 38.321 [3], clause 5.1.1).

Conditional Presence	Explanation
Mandatory	The field is mandatory present.
Occasions	The field is optionally present, Need S, if the field occasions is present, otherwise it is absent.
2StepCFRA	The field is optionally present for the case of 2-step RA type contention free random access, Need S, otherwise it is absent.

– RACH-ConfigGeneric

The IE RACH-ConfigGeneric is used to specify the random-access parameters both for regular random access as well as for beam failure recovery.

RACH-ConfigGeneric information element

— ASN1START

— TAG-RACH-CONFIGGENERIC-START

RACH-ConfigGeneric ::= SEQUENCE {

prach-ConfigurationIndex INTEGER (0..255),

msg1-FDM ENUMERATED {one, two, four, eight},

msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1),

zeroCorrelationZoneConfig INTEGER(0..15),

preambleReceivedTargetPower INTEGER (-202..-60),

preambleTransMax ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200},

powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6},

ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80},

…,

[[

prach-ConfigurationPeriodScaling-IAB-r16 ENUMERATED {scf1,scf2,scf4,scf8,scf16,scf32,scf64} OPTIONAL, — Need R

prach-ConfigurationFrameOffset-IAB-r16 INTEGER (0..63) OPTIONAL, — Need R

prach-ConfigurationSOffset-IAB-r16 INTEGER (0..39) OPTIONAL, — Need R

ra-ResponseWindow-v1610 ENUMERATED { sl60, sl160} OPTIONAL, — Need R

prach-ConfigurationIndex-v1610 INTEGER (256..262) OPTIONAL — Need R

]],

[[

ra-ResponseWindow-v1700 ENUMERATED {sl240, sl320, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL — Need R

]]

}

— TAG-RACH-CONFIGGENERIC-STOP

— ASN1STOP

RACH-ConfigGeneric field descriptions

msg1-FDM The number of PRACH transmission occasions FDMed in one time instance. (see TS 38.211 [16], clause 6.3.3.2).

msg1-FrequencyStart Offset of lowest PRACH transmission occasion in frequency domain with respective to PRB 0. The value is configured so that the corresponding RACH resource is entirely within the bandwidth of the UL BWP. (see TS 38.211 [16], clause 6.3.3.2).

powerRampingStep Power ramping steps for PRACH (see TS 38.321 [3],5.1.3).

prach-ConfigurationFrameOffset-IAB Frame offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see TS 38.211 [16], clause 6.3.3.2).

prach-ConfigurationIndex PRACH configuration index. For prach-ConfigurationIndex configured under beamFailureRecoveryConfig, the prach-ConfigurationIndex can only correspond to the short preamble format, (see TS 38.211 [16], clause 6.3.3.2). If the field prach-ConfigurationIndex-v1610 is present, the UE shall ignore the value provided in prach-ConfigurationIndex (without suffix).

prach-ConfigurationPeriodScaling-IAB Scaling factor to extend the periodicity of the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. Value scf1 corresponds to scaling factor of 1 and so on. (see TS 38.211 [16], clause 6.3.3.2).

prach-ConfigurationSOffset-IAB Subframe/Slot offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see TS 38.211 [16], clause 6.3.3.2).

preambleReceivedTargetPower The target power level at the network receiver side (see TS 38.213 [13], clause 7.4, TS 38.321 [3], clauses 5.1.2, 5.1.3). Only multiples of 2 dBm may be chosen (e.g. -202, -200, -198, …).

preambleTransMax Max number of RA preamble transmission performed before declaring a failure (see TS 38.321 [3], clauses 5.1.4, 5.1.5).

ra-ResponseWindow Msg2 (RAR) window length in number of slots. The network configures a value lower than or equal to 10 ms when Msg2 is transmitted in licensed spectrum and a value lower than or equal to 40 ms when Msg2 is transmitted with shared spectrum channel access (see TS 38.321 [3], clause 5.1.4). UE ignores the field if included in SCellConfig. If ra-ResponseWindow-v1610 or ra-ResponseWindow-v1700 is signalled, UE shall ignore the ra-ResponseWindow (without suffix). The field ra-ResponseWindow-v1700 is applicable to SCS 480 kHz and SCS 960 kHz.

zeroCorrelationZoneConfig N-CS configuration, see Table 6.3.3.1-5 in TS 38.211 [16].

– RACH-ConfigGenericTwoStepRA

The IE RACH-ConfigGenericTwoStepRA is used to specify the 2-step random access type parameters.

RACH-ConfigGenericTwoStepRA information element

— ASN1START

— TAG-RACH-CONFIGGENERICTWOSTEPRA-START

RACH-ConfigGenericTwoStepRA-r16 ::= SEQUENCE {

msgA-PRACH-ConfigurationIndex-r16 INTEGER (0..262) OPTIONAL, — Cond 2StepOnly

msgA-RO-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, — Cond 2StepOnly

msgA-RO-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, — Cond 2StepOnly

msgA-ZeroCorrelationZoneConfig-r16 INTEGER (0..15) OPTIONAL, — Cond 2StepOnly

msgA-PreamblePowerRampingStep-r16 ENUMERATED {dB0, dB2, dB4, dB6} OPTIONAL, — Cond 2StepOnlyNoCFRA

msgA-PreambleReceivedTargetPower-r16 INTEGER (-202..-60) OPTIONAL, — Cond 2StepOnlyNoCFRA

msgB-ResponseWindow-r16 ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80, sl160, sl320}

OPTIONAL, — Cond NoCFRA

preambleTransMax-r16 ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200} OPTIONAL, — Cond 2StepOnlyNoCFRA

…,

[[

msgB-ResponseWindow-v1700 ENUMERATED {sl240, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL — Cond NoCFRA2

]]

}

— TAG-RACH-CONFIGGENERICTWOSTEPRA-STOP

— ASN1STOP

RACH-ConfigGenericTwoStepRA field descriptions

msgA-PreamblePowerRampingStep Power ramping steps for msgA PRACH. If the field is absent, UE shall use the value of powerRampingStep in RACH-ConfigGeneric in the configured BWP (see TS 38.321 [3], 5.1.3). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and then the UE uses the value of msgA-PreamblePowerRampingStep in RACH-ConfigGenericTwoStepRA configured for CBRA.

msgA-PreambleReceivedTargetPower The target power level at the network receiver side (see TS 38.213 [13], clause 7.1.1 and TS 38.321 [3], clause 5.1.1). Only multiples of 2 dBm may be chosen (e.g -202, -200, -198, …). If the field is absent, UE shall use the value of preambleReceivedTargetPower in RACH-ConfigGeneric in the configured BWP. This field may only be present if no 4-step type RA is configured in the BWP. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and then the UE uses the value of msgA-PreambleReceivedTargetPower in RACH-ConfigGenericTwoStepRA configured for CBRA.

msgA-PRACH-ConfigurationIndex Cell-specific PRACH configuration index for 2-step RA type. If the field is absent in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config), the UE shall use the value of corresponding 4-step random access parameter in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the corresponding value in RACH-ConfigCommon in the same AdditionalRACH-Config. If the value is in the range of 256 to 262, the field prach-ConfigurationIndex-v1610 should be considered configured (see TS 38.211 [16], clause 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.

msgA-RO-FDM The number of msgA PRACH transmission occasions Frequency-Division Multiplexed in one time instance. If the field is absent in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config), UE shall use value of msg1-FDM in RACH-ConfigGeneric in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the value of msg1-FDM in RACH-ConfigCommon in the same AdditionalRACH-Config (see TS 38.211 [16], clause 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.

msgA-RO-FrequencyStart Offset of lowest PRACH transmissions occasion in frequency domain with respect to PRB 0. If the field is absent in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config), UE shall use value of msg1-FrequencyStart in RACH-ConfigGeneric in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the value of msg1-FrequencyStart in RACH-ConfigCommon in the same AdditionalRACH-Config (see TS 38.211 [16], clauses 5.3.2 and 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.

msgA-ZeroCorrelationZoneConfig N-CS configuration for msgA preamble, see Table 6.3.3.1-5 in TS 38.211 [16]. If the field is absent, UE shall use value zeroCorrelationZoneConfig in RACH-ConfigGeneric in the configured BWP. This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.

msgB-ResponseWindow MsgB monitoring window length in number of slots. The network configures a value lower than or equal to 40ms (see TS 38.321 [3], clause 5.1.1). The network does not configure msgB-ResponseWindow-r16 simultaneously with msgB-ResponseWindow-v1700, and if both fields are absent, the UE uses the value of msgB-ResponseWindow in RACH-ConfigGenericTwoStepRA configured for CBRA.

preambleTransMax Max number of RA preamble transmission performed before declaring a failure (see TS 38.321 [3], clauses 5.1.4, 5.1.5). If the field is absent, UE shall use the value of preambleTransMax in RACH-ConfigGeneric in the configured BWP. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and then the UE uses the value of preambleTransMax in RACH-ConfigGenericTwoStepRA configured for CBRA.

Conditional Presence	Explanation
2StepOnly	The field is mandatory present in msgA-ConfigCommon field in BWP-UplinkCommon if rach-ConfigCommon field is absent in this BWP-UplinkCommon, otherwise the field is optionally present in msgA-ConfigCommon field in BWP-UplinkCommon, Need S. The field is mandatory present in msgA-ConfigCommon in AdditionalRACH-Config if rach-ConfigCommon field is absent in this AdditionalRACH-Config, otherwise the field is optionally present in msgA-ConfigCommon field in AdditionalRACH-Config, Need S.
2StepOnlyNoCFRA	The field is mandatory present if RACH-ConfigGenericTwoStepRA is included in the RACH-ConfigCommonTwoStepRA and there are no 4-step random access configurations configured in the BWP (i.e only 2-step random access type configured in the BWP), otherwise (i.e. 4-step random access configuration also exists in the BWP) the field is optionally present, Need S. When RACH-ConfigGenericTwoStepRA is included in the RACH-ConfigDedicated, this field is absent.
NoCFRA	The field is mandatory present if msgB-ResponseWindow-r17 is absent and RACH-ConfigGenericTwoStepRA is not included in CFRA-TwoStep in RACH-ConfigDedicated, otherwise the field is absent, Need S.
NoCFRA2	The field is mandatory present if msgB-ResponseWindow-r16 is absent and RACH-ConfigGenericTwoStepRA is not included in CFRA-TwoStep in RACH-ConfigDedicated, otherwise the field is absent, Need S.

– RA-Prioritization

The IE RA-Prioritization is used to configure prioritized random access.

RA-Prioritization information element

— ASN1START

— TAG-RA-PRIORITIZATION-START

RA-Prioritization ::= SEQUENCE {

powerRampingStepHighPriority ENUMERATED {dB0, dB2, dB4, dB6},

scalingFactorBI ENUMERATED {zero, dot25, dot5, dot75} OPTIONAL, — Need R

…

}

— TAG-RA-PRIORITIZATION-STOP

— ASN1STOP

RA-Prioritization field descriptions

powerRampingStepHighPrioritiy Power ramping step applied for prioritized random access procedure.

scalingFactorBI Scaling factor for the backoff indicator (BI) for the prioritized random access procedure. (see TS 38.321 [3], clause 5.1.4). Value zero corresponds to 0, value dot25 corresponds to 0.25 and so on.

– RA-PrioritizationForSlicing

The IE RA-PrioritizationForSlicing is used to configure prioritized random access for slicing.

RA-PrioritizationForSlicing information element

— ASN1START

— TAG-RA-PRIORITIZATIONFORSLICING-START

RA-PrioritizationForSlicing-r17 ::= SEQUENCE {

ra-PrioritizationSliceInfoList-r17 RA-PrioritizationSliceInfoList-r17,

…

}

RA-PrioritizationSliceInfoList-r17 ::= SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF RA-PrioritizationSliceInfo-r17

RA-PrioritizationSliceInfo-r17 ::= SEQUENCE {

nsag-ID-List-r17 SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF NSAG-ID-r17,

ra-Prioritization-r17 RA-Prioritization,

…

}

— TAG-RA-PRIORITIZATIONFORSLICING-STOP

— ASN1STOP

– RadioBearerConfig

The IE RadioBearerConfig is used to add, modify and release signalling, multicast MRBs and/or data radio bearers. Specifically, this IE carries the parameters for PDCP and, if applicable, SDAP entities for the radio bearers.

RadioBearerConfig information element

— ASN1START

— TAG-RADIOBEARERCONFIG-START

RadioBearerConfig ::= SEQUENCE {

srb-ToAddModList SRB-ToAddModList OPTIONAL, — Cond HO-Conn

srb3-ToRelease ENUMERATED{true} OPTIONAL, — Need N

drb-ToAddModList DRB-ToAddModList OPTIONAL, — Cond HO-toNR

drb-ToReleaseList DRB-ToReleaseList OPTIONAL, — Need N

securityConfig SecurityConfig OPTIONAL, — Need M

…,

[[

mrb-ToAddModList-r17 MRB-ToAddModList-r17 OPTIONAL, — Need N

mrb-ToReleaseList-r17 MRB-ToReleaseList-r17 OPTIONAL, — Need N

srb4-ToAddMod-r17 SRB-ToAddMod OPTIONAL, — Need N

srb4-ToRelease-r17 ENUMERATED{true} OPTIONAL — Need N

]]

}

SRB-ToAddModList ::= SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod

SRB-ToAddMod ::= SEQUENCE {

srb-Identity SRB-Identity,

reestablishPDCP ENUMERATED{true} OPTIONAL, — Need N

discardOnPDCP ENUMERATED{true} OPTIONAL, — Need N

pdcp-Config PDCP-Config OPTIONAL, — Cond PDCP

…,

[[

srb-Identity-v1700 SRB-Identity-v1700 OPTIONAL — Need M

]]

}

DRB-ToAddModList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod

DRB-ToAddMod ::= SEQUENCE {

cnAssociation CHOICE {

eps-BearerIdentity INTEGER (0..15),

sdap-Config SDAP-Config

} OPTIONAL, — Cond DRBSetup

drb-Identity DRB-Identity,

reestablishPDCP ENUMERATED{true} OPTIONAL, — Need N

recoverPDCP ENUMERATED{true} OPTIONAL, — Need N

pdcp-Config PDCP-Config OPTIONAL, — Cond PDCP

…,

[[

daps-Config-r16 ENUMERATED{true} OPTIONAL — Cond DAPS

]]

}

DRB-ToReleaseList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity

SecurityConfig ::= SEQUENCE {

securityAlgorithmConfig SecurityAlgorithmConfig OPTIONAL, — Cond RBTermChange1

keyToUse ENUMERATED{master, secondary} OPTIONAL, — Cond RBTermChange

…

}

MRB-ToAddModList-r17 ::= SEQUENCE (SIZE (1..maxMRB-r17)) OF MRB-ToAddMod-r17

MRB-ToAddMod-r17 ::= SEQUENCE {

mbs-SessionId-r17 TMGI-r17 OPTIONAL, — Cond MRBSetup

mrb-Identity-r17 MRB-Identity-r17,

mrb-IdentityNew-r17 MRB-Identity-r17 OPTIONAL, — Need N

reestablishPDCP-r17 ENUMERATED{true} OPTIONAL, — Need N

recoverPDCP-r17 ENUMERATED{true} OPTIONAL, — Need N

pdcp-Config-r17 PDCP-Config OPTIONAL, — Cond PDCP

…

}

MRB-ToReleaseList-r17 ::= SEQUENCE (SIZE (1..maxMRB-r17)) OF MRB-Identity-r17

— TAG-RADIOBEARERCONFIG-STOP

— ASN1STOP

DRB-ToAddMod and MRB-ToAddMod field descriptions

cnAssociation Indicates if the bearer is associated with the eps-bearerIdentity (when connected to EPC) or sdap-Config (when connected to 5GC).

daps-Config Indicates that the bearer is configured as DAPS bearer.

drb-Identity In case of DC, the DRB identity is unique within the scope of the UE, i.e. an MCG DRB cannot use the same value as a split DRB. For a split DRB the same identity is used for the MCG and SCG parts of the configuration.

eps-BearerIdentity The EPS bearer ID determines the EPS bearer.

mbs-SessionId Indicates which multicast MBS session the bearer is associated with.

mrb-Identity Identification of the multicast MRB.

mrb-IdentityNew New identity of the multicast MRB when mrb-Identity needs to be changed, e.g. as a result of a handover.

reestablishPDCP Indicates that PDCP should be re-established. Network sets this to true whenever the security key used for this radio bearer changes. Key change could for example be due to termination point change for the bearer, reconfiguration with sync, resuming an RRC connection, or the first reconfiguration after reestablishment. It is also applicable for LTE procedures when NR PDCP is configured. Network doesn’t include this field for DRB if the bearer is configured as DAPS bearer.

recoverPDCP Indicates that PDCP should perform recovery according to TS 38.323 [5]. Network doesn’t include this field if the bearer is configured as DAPS bearer.

sdap-Config The SDAP configuration determines how to map QoS flows to DRBs when NR or E-UTRA connects to the 5GC and presence/absence of UL/DL SDAP headers.

RadioBearerConfig field descriptions

securityConfig Indicates the security algorithm and key to use for the signalling and data radio bearers configured with the list in this IE RadioBearerConfig. When the field is not included after AS security has been activated, the UE shall continue to use the currently configured keyToUse and security algorithm for the radio bearers reconfigured with the lists in this IE RadioBearerConfig. The field is not included when configuring SRB1 before AS security is activated.

srb3-ToRelease Release SRB3. SRB3 release can only be done over SRB1 and only at SCG release and reconfiguration with sync.

SecurityConfig field descriptions

keyToUse Indicates if the bearers configured with the list in this IE RadioBearerConfig are using the master key or the secondary key for deriving ciphering and/or integrity protection keys. For MR-DC, network should not configure SRB1 and SRB2 with secondary key and SRB3 with the master key. When the field is not included, the UE shall continue to use the currently configured keyToUse for the radio bearers reconfigured with the lists in this IE RadioBearerConfig.

securityAlgorithmConfig Indicates the security algorithm for the signalling and data radio bearers configured with the list in this IE RadioBearerConfig. When the field is not included, the UE shall continue to use the currently configured security algorithm for the radio bearers reconfigured with the lists in this IE RadioBearerConfig.

SRB-ToAddMod field descriptions

discardOnPDCP Indicates that PDCP should discard stored SDU and PDU according to TS 38.323 [5].

reestablishPDCP Indicates that PDCP should be re-established. Network sets this to true whenever the security key used for this radio bearer changes. Key change could for example be due to reconfiguration with sync, for SRB2 when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR. For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR, the network does not set this field to true. For LTE SRBs using NR PDCP, it could be for handover, RRC connection reestablishment or resume. Network doesn’t include this field if any DAPS bearer is configured.

srb-Identity, srb-Identity-v1700 Value 1 is applicable for SRB1 only. Value 2 is applicable for SRB2 only. Value 3 is applicable for SRB3 only. Value 4 is applicable for SRB4 only. If srb-Identity-v1700 is received for an SRB, the UE shall ignore srb-Identity (i.e. without suffix) for this SRB.

Conditional Presence	Explanation
RBTermChange	The field is mandatory present in case of: – set up of signalling and data radio bearer, – change of termination point for the radio bearer between MN and SN. It is optionally present otherwise, Need S.
RBTermChange1	The field is mandatory present in case of: – set up of signalling and data radio bearer, – change of termination point for the radio bearer between MN and SN, – handover from E-UTRA/EPC or E-UTRA/5GC to NR, – handover from NR or E-UTRA/EPC to E-UTRA/5GC if the UE supports NGEN-DC. It is optionally present otherwise, Need S.
PDCP	The field is mandatory present if the corresponding DRB/multicast MRB is being setup or corresponding DRB/multicast MRB is reconfigured with NR PDCP or corresponding SRB associated with two RLC entities is being setup or if the number of RLC bearers associated with the DRB/multicast MRB or SRB is changed. The field is optionally present, Need S, if the corresponding SRB associated with one RLC entity is being setup or corresponding SRB is reconfigured with NR PDCP; otherwise the field is optionally present, need M.
DRBSetup	The field is mandatory present if the corresponding DRB is being setup; otherwise the field is optionally present, need M.
HO-Conn	The field is mandatory present – in case of inter-system handover from E-UTRA/EPC to E-UTRA/5GC or NR, – or when the fullConfig is included in the RRCReconfiguration message and NE-DC/NR-DC is not configured, – or in case of RRCSetup. Otherwise the field is optionally present, need N. Upon RRCSetup, only SRB1 can be present.
HO-toNR	If mrb-ToAddModList is not included, the field is mandatory present – in case of inter-system handover from E-UTRA/EPC to E-UTRA/5GC or NR, – or when the fullConfig is included in the RRCReconfiguration message and NE-DC/NR-DC is not configured. In case of RRCSetup, the field is absent; otherwise the field is optionally present, need N.
DAPS	The field is optionally present, need N, in case masterCellGroup includes ReconfigurationWithSync, SCell(s) and SCG are not configured, multi-DCI/single-DCI based multi-TRP are not configured in any DL BWP, supplementaryUplink is not configured, ethernetHeaderCompression is not configured for the DRB, conditionalReconfiguration is not configured, and NR sidelink and V2X sidelink are not configured. Otherwise the field is absent.
MRBSetup	The field is mandatory present if the corresponding multicast MRB is being setup; otherwise the field is optionally present, need M.

– RadioLinkMonitoringConfig

The IE RadioLinkMonitoringConfig is used to configure radio link monitoring for detection of beam- and/or cell radio link failure. See also TS 38.321 [3], clause 5.1.1.

RadioLinkMonitoringConfig information element

— ASN1START

— TAG-RADIOLINKMONITORINGCONFIG-START

RadioLinkMonitoringConfig ::= SEQUENCE {

failureDetectionResourcesToAddModList SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS

OPTIONAL, — Need N

failureDetectionResourcesToReleaseList SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS-Id

OPTIONAL, — Need N

beamFailureInstanceMaxCount ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10} OPTIONAL, — Need R

beamFailureDetectionTimer ENUMERATED {pbfd1, pbfd2, pbfd3, pbfd4, pbfd5, pbfd6, pbfd8, pbfd10} OPTIONAL, — Need R

…,

[[

beamfailure-r17 BeamFailureDetection-r17 OPTIONAL — Need R

]]

}

BeamFailureDetection-r17 ::= SEQUENCE {

failureDetectionSet1-r17 BeamFailureDetectionSet-r17 OPTIONAL, — Need R

failureDetectionSet2-r17 BeamFailureDetectionSet-r17 OPTIONAL, — Need R

additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL — Need R

}

RadioLinkMonitoringRS ::= SEQUENCE {

radioLinkMonitoringRS-Id RadioLinkMonitoringRS-Id,

purpose ENUMERATED {beamFailure, rlf, both},

detectionResource CHOICE {

ssb-Index SSB-Index,

csi-RS-Index NZP-CSI-RS-ResourceId

},

…

}

BeamFailureDetectionSet-r17 ::= SEQUENCE {

bfdResourcesToAddModList-r17 SEQUENCE (SIZE(1..maxNrofBFDResourcePerSet-r17)) OF BeamLinkMonitoringRS-r17

OPTIONAL, — Need N

bfdResourcesToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofBFDResourcePerSet-r17)) OF BeamLinkMonitoringRS-Id-r17

OPTIONAL, — Need N

beamFailureInstanceMaxCount-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10} OPTIONAL, — Need R

beamFailureDetectionTimer-r17 ENUMERATED {pbfd1, pbfd2, pbfd3, pbfd4, pbfd5, pbfd6, pbfd8, pbfd10} OPTIONAL, — Need R

…

}

BeamLinkMonitoringRS-r17 ::= SEQUENCE {

beamLinkMonitoringRS-Id-r17 BeamLinkMonitoringRS-Id-r17,

detectionResource-r17 CHOICE {

ssb-Index SSB-Index,

csi-RS-Index NZP-CSI-RS-ResourceId

},

…

}

BeamLinkMonitoringRS-Id-r17 ::= INTEGER (0..maxNrofFailureDetectionResources-1-r17)

— TAG-RADIOLINKMONITORINGCONFIG-STOP

— ASN1STOP

RadioLinkMonitoringConfig field descriptions

additionalPCI Indicates the physical cell IDs (PCI) of the SSBs in the failureDetectionSet2. If candidateBeamRS-List2 is configured in IE BeamFailureRecoveryRSConfig the field indicates the physical cell IDs (PCI) of the SSBs in the candidateBeamRS-List2.

beamFailureDetectionTimer Timer for beam failure detection (see TS 38.321 [3], clause 5.17). See also the BeamFailureRecoveryConfig IE. Value in number of "Qout,LR reporting periods of Beam Failure Detection" Reference Signal (see TS 38.213 [13], clause 6). Value pbfd1 corresponds to 1 Qout,LR reporting period of Beam Failure Detection Reference Signal, value pbfd2 corresponds to 2 Qout,LR reporting periods of Beam Failure Detection Reference Signal and so on.

beamFailureInstanceMaxCount This field determines after how many beam failure events the UE triggers beam failure recovery (see TS 38.321 [3], clause 5.17). Value n1 corresponds to 1 beam failure instance, value n2 corresponds to 2 beam failure instances and so on.

failureDetectionResourcesToAddModList A list of reference signals for detecting beam failure and/or cell level radio link failure (RLF). The limits of the reference signals that the network can configure are specified in TS 38.213 [13], table 5-1. The network configures at most two detectionResources per BWP for the purpose beamFailure or both. If no RSs are provided for the purpose of beam failure detection, the UE performs beam monitoring based on the activated TCI-State for PDCCH as described in TS 38.213 [13], clause 6. If no RSs are provided in this list for the purpose of RLF detection, the UE performs Cell-RLM based on the activated TCI-State of PDCCH as described in TS 38.213 [13], clause 5. The network ensures that the UE has a suitable set of reference signals for performing cell-RLM. If failureDetectionSet1-r17 and failureDetectionSet2-r17 are present, the purpose of RadioLinkMonitoringRS in failureDetectionResourcesToAddModList only can be set to rlf.

failureDetectionSet1, failureDetectionSet2 Configures parameters for beamfailure detection towards beam failure detection resources configured in the set. If additional PCIs are configured using additionalPCI-ToAddModList for the serving cell, each RS in one set can be associated only with one PCI. Network always configures the failureDetectionSet1 and failureDetectionSet2 together. When a failureDetectionSetN is present, after the reconfiguration, the UE shall consider all the reference signals for this failure detection set as activated if at most maxBFD-RS-resourcesPerSetPerBWP-r17 reference signals are configured for each failure detection set, otherwise the UE shall considered all the reference signals in this failure detection set as deactivated.

RadioLinkMonitoringRS field descriptions

detectionResource A reference signal that the UE shall use for radio link monitoring or beam failure detection (depending on the indicated purpose). Only periodic 1-port CSI-RS can be configured on SCell for beam failure detection purpose.

purpose Determines whether the UE shall monitor the associated reference signal for the purpose of cell- and/or beam failure detection. For SCell, network only configures the value to beamFailure.

– RadioLinkMonitoringRS-Id

The IE RadioLinkMonitoringRS-Id is used to identify one RadioLinkMonitoringRS.

RadioLinkMonitoringRS-Id information element

— ASN1START

— TAG-RADIOLINKMONITORINGRS-ID-START

RadioLinkMonitoringRS-Id ::= INTEGER (0..maxNrofFailureDetectionResources-1)

— TAG-RADIOLINKMONITORINGRS-ID-STOP

— ASN1STOP

– RAN-AreaCode

The IE RAN-AreaCode is used to identify a RAN area within the scope of a tracking area.

RAN-AreaCode information element

— ASN1START

— TAG-RAN-AREACODE-START

RAN-AreaCode ::= INTEGER (0..255)

— TAG-RAN-AREACODE-STOP

— ASN1STOP

– RateMatchPattern

The IE RateMatchPattern is used to configure one rate matching pattern for PDSCH, see TS 38.214 [19], clause 5.1.4.1.

RateMatchPattern information element

— ASN1START

— TAG-RATEMATCHPATTERN-START

RateMatchPattern ::= SEQUENCE {

rateMatchPatternId RateMatchPatternId,

patternType CHOICE {

bitmaps SEQUENCE {

resourceBlocks BIT STRING (SIZE (275)),

symbolsInResourceBlock CHOICE {

oneSlot BIT STRING (SIZE (14)),

twoSlots BIT STRING (SIZE (28))

},

periodicityAndPattern CHOICE {

n2 BIT STRING (SIZE (2)),

n4 BIT STRING (SIZE (4)),

n5 BIT STRING (SIZE (5)),

n8 BIT STRING (SIZE (8)),

n10 BIT STRING (SIZE (10)),

n20 BIT STRING (SIZE (20)),

n40 BIT STRING (SIZE (40))

} OPTIONAL, — Need S

…

},

controlResourceSet ControlResourceSetId

},

subcarrierSpacing SubcarrierSpacing OPTIONAL, — Cond CellLevel

dummy ENUMERATED { dynamic, semiStatic },

…,

[[

controlResourceSet-r16 ControlResourceSetId-r16 OPTIONAL — Need R

]]

}

— TAG-RATEMATCHPATTERN-STOP

— ASN1STOP

RateMatchPattern field descriptions

bitmaps Indicates rate matching pattern by a pair of bitmaps resourceBlocks and symbolsInResourceBlock to define the rate match pattern within one or two slots, and a third bitmap periodicityAndPattern to define the repetition pattern with which the pattern defined by the above bitmap pair occurs.

controlResourceSet This ControlResourceSet is used as a PDSCH rate matching pattern, i.e., PDSCH reception rate matches around it. In frequency domain, the resource is determined by the frequency domain resource of the CORESET with the corresponding CORESET ID. Time domain resource is determined by the parameters of the associated search space of the CORESET. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix).

periodicityAndPattern A time domain repetition pattern at which the pattern defined by symbolsInResourceBlock and resourceBlocks recurs. This slot pattern repeats itself continuously. Absence of this field indicates the value n1 (see TS 38.214 [19], clause 5.1.4.1).

resourceBlocks A resource block level bitmap in the frequency domain. A bit in the bitmap set to 1 indicates that the UE shall apply rate matching in the corresponding resource block in accordance with the symbolsInResourceBlock bitmap. If used as cell-level rate matching pattern, the bitmap identifies "common resource blocks (CRB)". If used for MBS broadcast CFR, the bitmap identifies "physical resource blocks" inside the MBS broadcast CFR. If used as BWP-level rate matching pattern, the bitmap identifies "physical resource blocks" inside the BWP or MBS multicast CFR. The first/ leftmost bit corresponds to resource block 0, and so on (see TS 38.214 [19], clause 5.1.4.1).

subcarrierSpacing The SubcarrierSpacing for this resource pattern. If the field is absent, the UE applies the SCS of the associated BWP. The value kHz15 corresponds to µ=0, the value kHz30 corresponds to µ=1, and so on. Only the following values are applicable depending on the used frequency (see TS 38.214 [19], clause 5.1.4.1): FR1: 15, 30 or 60 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz

symbolsInResourceBlock A symbol level bitmap in time domain. It indicates with a bit set to true that the UE shall rate match around the corresponding symbol. This pattern recurs (in time domain) with the configured periodicityAndPattern (see TS 38.214 [19], clause 5.1.4.1). For oneSlot, if ECP is configured, the first 12 bits represent the symbols within the slot and the last two bits within the bitstring are ignored by the UE; Otherwise, the 14 bits represent the symbols within the slot. For twoSlots, if ECP is configured, the first 12 bits represent the symbols within the first slot and the next 12 bits represent the symbols in the second slot and the last four bits within the bit string are ignored by the UE; Otherwise, the first 14 bits represent the symbols within the first slot and the next 14 bits represent the symbols in the second slot. For the bits representing symbols in a slot, the most significant bit of the bit string represents the first symbol in the slot and the second most significant bit represents the second symbol in the slot and so on.

Conditional Presence	Explanation
CellLevel	The field is mandatory present if the RateMatchPattern is defined on cell level. The field is absent when the RateMatchPattern is defined on BWP level or defined for MBS broadcast CFR. If the RateMatchPattern is defined on BWP level, the UE applies the SCS of the BWP and if RateMatchPattern is defined for MBS broadcast CFR, the UE applies the SCS of the initial BWP.

– RateMatchPatternId

The IE RateMatchPatternId identifies one RateMatchMattern (see TS 38.214 [19], clause 5.1.4.2).

RateMatchPatternId information element

— ASN1START

— TAG-RATEMATCHPATTERNID-START

RateMatchPatternId ::= INTEGER (0..maxNrofRateMatchPatterns-1)

— TAG-RATEMATCHPATTERNID-STOP

— ASN1STOP

– RateMatchPatternLTE-CRS

The IE RateMatchPatternLTE-CRS is used to configure a pattern to rate match around LTE CRS. See TS 38.214 [19], clause 5.1.4.2.

RateMatchPatternLTE-CRS information element

— ASN1START

— TAG-RATEMATCHPATTERNLTE-CRS-START

RateMatchPatternLTE-CRS ::= SEQUENCE {

carrierFreqDL INTEGER (0..16383),

carrierBandwidthDL ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1},

mbsfn-SubframeConfigList EUTRA-MBSFN-SubframeConfigList OPTIONAL, — Need M

nrofCRS-Ports ENUMERATED {n1, n2, n4},

v-Shift ENUMERATED {n0, n1, n2, n3, n4, n5}

}

LTE-CRS-PatternList-r16 ::= SEQUENCE (SIZE (1..maxLTE-CRS-Patterns-r16)) OF RateMatchPatternLTE-CRS

— TAG-RATEMATCHPATTERNLTE-CRS-STOP

— ASN1STOP

RateMatchPatternLTE-CRS field descriptions

carrierBandwidthDL BW of the LTE carrier in number of PRBs (see TS 38.214 [19], clause 5.1.4.2).

carrierFreqDL Center of the LTE carrier (see TS 38.214 [19], clause 5.1.4.2).

mbsfn-SubframeConfigList LTE MBSFN subframe configuration (see TS 38.214 [19], clause 5.1.4.2).

nrofCRS-Ports Number of LTE CRS antenna port to rate-match around (see TS 38.214 [19], clause 5.1.4.2).

v-Shift Shifting value v-shift in LTE to rate match around LTE CRS (see TS 38.214 [19], clause 5.1.4.2).

– ReferenceLocation

The IE ReferenceLocation contains location information used as a reference location. The value of the field is same as Ellipsoid-Point defined in TS37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.

ReferenceLocation information element

— ASN1START

— TAG-REFERENCELOCATION-START

ReferenceLocation-r17 ::= OCTET STRING

— TAG-REFERENCELOCATION-STOP

— ASN1STOP

– ReferenceTimeInfo

The IE ReferenceTimeInfo contains timing information for 5G internal system clock used for, e.g., time stamping, see TS 23.501 [32], clause 5.27.1.2.

ReferenceTimeInfo information element

— ASN1START

— TAG-REFERENCETIMEINFO-START

ReferenceTimeInfo-r16 ::= SEQUENCE {

time-r16 ReferenceTime-r16,

uncertainty-r16 INTEGER (0..32767) OPTIONAL, — Need S

timeInfoType-r16 ENUMERATED {localClock} OPTIONAL, — Need S

referenceSFN-r16 INTEGER (0..1023) OPTIONAL — Cond RefTime

}

ReferenceTime-r16 ::= SEQUENCE {

refDays-r16 INTEGER (0..72999),

refSeconds-r16 INTEGER (0..86399),

refMilliSeconds-r16 INTEGER (0..999),

refTenNanoSeconds-r16 INTEGER (0..99999)

}

— TAG-REFERENCETIMEINFO-STOP

— ASN1STOP

ReferenceTimeInfo field descriptions

referenceSFN This field indicates the reference SFN corresponding to the reference time information. If referenceTimeInfo field is received in DLInformationTransfer message, this field indicates the SFN of PCell.

time This field indicates time reference with 10ns granularity. If included in DLInformationTransfer and if UE-side TA PDC is de-activated, the indicated time may not be referenced at the network, i.e., gNB may pre-compensate for RF propagation delay. If included in DLInformationTransfer and if UE is requested to transmit UE Rx-Tx time difference measurement, the indicated time may not be referenced at the network, i.e., gNB may pre-compensate for RF propagation delay. Otherwise, the indicated time is referenced at the network, i.e., without compensating for RF propagation delay. The indicated time in 10ns unit from the origin is refDays*86400*1000*100000 + refSeconds*1000*100000 + refMilliSeconds*100000 + refTenNanoSeconds. The refDays field specifies the sequential number of days (with day count starting at 0) from the origin of the time field. If the referenceTimeInfo field is received in DLInformationTransfer message, the time field indicates the time at the ending boundary of the system frame indicated by referenceSFN. The UE considers this frame (indicated by referenceSFN) to be the frame which is nearest to the frame where the message is received (which can be either in the past or in the future). If the referenceTimeInfo field is received in SIB9, the time field indicates the time at the SFN boundary at or immediately after the ending boundary of the SI-window in which SIB9 is transmitted. If referenceTimeInfo field is received in SIB9, this field is excluded when determining changes in system information, i.e. changes of time should neither result in system information change notifications nor in a modification of valueTag in SIB1.

timeInfoType If timeInfoType is not included, the time indicates the GPS time and the origin of the time field is 00:00:00 on Gregorian calendar date 6 January, 1980 (start of GPS time). If timeInfoType is set to localClock, the origin of the time is unspecified.

uncertainty This field indicates the uncertainty of the reference time information provided by the time field. The uncertainty is 25ns multiplied by this field. If this field is absent, the uncertainty is unspecified.

Conditional Presence	Explanation
RefTime	The field is mandatory present if referenceTimeInfo is included in DLInformationTransfer message; otherwise the field is absent.

– RejectWaitTime

The IE RejectWaitTime is used to provide the value in seconds for timer T302.

RejectWaitTime information element

— ASN1START

— TAG-REJECTWAITTIME-START

RejectWaitTime ::= INTEGER (1..16)

— TAG-REJECTWAITTIME-STOP

— ASN1STOP

– RepetitionSchemeConfig

The IE RepetitionSchemeConfig is used to configure the UE with repetition schemes as specified in TS 38.214 [19] clause 5.1.

RepetitionSchemeConfig information element

— ASN1START

— TAG-REPETITIONSCHEMECONFIG-START

RepetitionSchemeConfig-r16 ::= CHOICE {

fdm-TDM-r16 SetupRelease { FDM-TDM-r16 },

slotBased-r16 SetupRelease { SlotBased-r16 }

}

RepetitionSchemeConfig-v1630 ::= SEQUENCE {

slotBased-v1630 SetupRelease { SlotBased-v1630 }

}

FDM-TDM-r16 ::= SEQUENCE {

repetitionScheme-r16 ENUMERATED {fdmSchemeA, fdmSchemeB,tdmSchemeA },

startingSymbolOffsetK-r16 INTEGER (0..7) OPTIONAL — Need R

}

SlotBased-r16 ::= SEQUENCE {

tciMapping-r16 ENUMERATED {cyclicMapping, sequentialMapping},

sequenceOffsetForRV-r16 INTEGER (1..3)

}

SlotBased-v1630 ::= SEQUENCE {

tciMapping-r16 ENUMERATED {cyclicMapping, sequentialMapping},

sequenceOffsetForRV-r16 INTEGER (0)

}

— TAG-REPETITIONSCHEMECONFIG-STOP

— ASN1STOP

RepetitionSchemeConfig field descriptions

fdm-TDM Configures UE with a repetition scheme among fdmSchemeA, fdmSchemeB and tdmSchemeA as specified in clause 5.1 of TS 38.214 [19]. The network does not set this field to release. Upon reception of this field in RepetitionSchemeConfig-r16, the UE shall release slotBased if previously configured in the same instance of RepetitionSchemeConfig-r16.

sequenceOffsetForRV For slot-based repetition scheme, selected RV sequence is applied to transmission occasions associated to the first TCI state. The RV sequence associated to the second TCI state is determined by a RV offset from that selected RV sequence.

slotBased Configures UE with slot-based repetition scheme. Network always configures this field when the parameter repetitionNumber is present in IE PDSCH-TimeDomainResourceAllocationList. The network does not set this field to release. Upon reception of this field in RepetitionSchemeConfig-r16, the UE shall release fdm-TDM if previously configured in the same instance of RepetitionSchemeConfig-r16.

startingSymbolOffsetK The starting symbol of the second transmission occasion has K symbol offset relative to the last symbol of the first transmission occasion. When UE is configured with tdmSchemeA, the parameter startingSymbolOffsetK is present, otherwise absent.

tciMapping Enables TCI state mapping method to PDSCH transmission occasions.

– ReportConfigId

The IE ReportConfigId is used to identify a measurement reporting configuration.

ReportConfigId information element

— ASN1START

— TAG-REPORTCONFIGID-START

ReportConfigId ::= INTEGER (1..maxReportConfigId)

— TAG-REPORTCONFIGID-STOP

— ASN1STOP

– ReportConfigInterRAT

The IE ReportConfigInterRAT specifies criteria for triggering of an inter-RAT measurement reporting event, or an L2 U2N relay measurement reporting event. The inter-RAT measurement reporting events for E-UTRA and UTRA-FDD are labelled BN with N equal to 1, 2 and so on. The measurement reporting events for L2 U2N relay UE are labelled YN with N equal to 1, 2 and so on.

Event B1: Neighbour becomes better than absolute threshold;

Event B2: PCell becomes worse than absolute threshold1 AND Neighbour becomes better than another absolute threshold2;

Event Y1: PCell becomes worse than absolute threshold1 AND candidate L2 U2N Relay UE becomes better than another absolute threshold2;

Event Y2: Candidate L2 U2N Relay UE becomes better than absolute threshold;

ReportConfigInterRAT information element

— ASN1START

— TAG-REPORTCONFIGINTERRAT-START

ReportConfigInterRAT ::= SEQUENCE {

reportType CHOICE {

periodical PeriodicalReportConfigInterRAT,

eventTriggered EventTriggerConfigInterRAT,

reportCGI ReportCGI-EUTRA,

…,

reportSFTD ReportSFTD-EUTRA

}

}

ReportCGI-EUTRA ::= SEQUENCE {

cellForWhichToReportCGI EUTRA-PhysCellId,

…,

[[

useAutonomousGaps-r16 ENUMERATED {setup} OPTIONAL — Need R

]]

}

ReportSFTD-EUTRA ::= SEQUENCE {

reportSFTD-Meas BOOLEAN,

reportRSRP BOOLEAN,

…

}

EventTriggerConfigInterRAT ::= SEQUENCE {

eventId CHOICE {

eventB1 SEQUENCE {

b1-ThresholdEUTRA MeasTriggerQuantityEUTRA,

reportOnLeave BOOLEAN,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger,

…

},

eventB2 SEQUENCE {

b2-Threshold1 MeasTriggerQuantity,

b2-Threshold2EUTRA MeasTriggerQuantityEUTRA,

reportOnLeave BOOLEAN,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger,

…

},

…,

[[

eventB1-UTRA-FDD-r16 SEQUENCE {

b1-ThresholdUTRA-FDD-r16 MeasTriggerQuantityUTRA-FDD-r16,

reportOnLeave-r16 BOOLEAN,

hysteresis-r16 Hysteresis,

timeToTrigger-r16 TimeToTrigger,

…

},

eventB2-UTRA-FDD-r16 SEQUENCE {

b2-Threshold1-r16 MeasTriggerQuantity,

b2-Threshold2UTRA-FDD-r16 MeasTriggerQuantityUTRA-FDD-r16,

reportOnLeave-r16 BOOLEAN,

hysteresis-r16 Hysteresis,

timeToTrigger-r16 TimeToTrigger,

…

}

]],

[[

eventY1-Relay-r17 SEQUENCE {

y1-Threshold1-r17 MeasTriggerQuantity,

y1-Threshold2-Relay-r17 SL-MeasTriggerQuantity-r16,

reportOnLeave-r17 BOOLEAN,

hysteresis-r17 Hysteresis,

timeToTrigger-r17 TimeToTrigger,

…

},

eventY2-Relay-r17 SEQUENCE {

y2-Threshold-Relay-r17 SL-MeasTriggerQuantity-r16,

reportOnLeave-r17 BOOLEAN,

hysteresis-r17 Hysteresis,

timeToTrigger-r17 TimeToTrigger,

…

}

]]

},

rsType NR-RS-Type,

reportInterval ReportInterval,

reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

reportQuantity MeasReportQuantity,

maxReportCells INTEGER (1..maxCellReport),

…,

[[

reportQuantityUTRA-FDD-r16 MeasReportQuantityUTRA-FDD-r16 OPTIONAL — Need R

]],

[[

includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, — Need R

includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, — Need M

includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, — Need M

includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL — Need M

]],

[[

reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL — Need R

]]}

PeriodicalReportConfigInterRAT ::= SEQUENCE {

reportInterval ReportInterval,

reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

reportQuantity MeasReportQuantity,

maxReportCells INTEGER (1..maxCellReport),

…,

[[

reportQuantityUTRA-FDD-r16 MeasReportQuantityUTRA-FDD-r16 OPTIONAL — Need R

]],

[[

includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, — Need R

includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, — Need M

includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, — Need M

includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL — Need M

]],

[[

reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL — Need R

]]

}

MeasTriggerQuantityUTRA-FDD-r16 ::= CHOICE{

utra-FDD-RSCP-r16 INTEGER (-5..91),

utra-FDD-EcN0-r16 INTEGER (0..49)

}

MeasReportQuantityUTRA-FDD-r16 ::= SEQUENCE {

cpich-RSCP BOOLEAN,

cpich-EcN0 BOOLEAN

}

— TAG-REPORTCONFIGINTERRAT-STOP

— ASN1STOP

ReportConfigInterRAT field descriptions

reportType Type of the configured measurement report. In (NG)EN-DC, and NR-DC, network does not configure report of type ReportCGI-EUTRA for SCG.

ReportCGI-EUTRA field descriptions

useAutonomousGaps Indicates whether or not the UE is allowed to use autonomous gaps in acquiring system information from the E-UTRAN neighbour cell. When the field is included, the UE applies the corresponding value for T321.

EventTriggerConfigInterRAT field descriptions

b2-Threshold1 NR threshold to be used in inter RAT measurement report triggering condition for event B2.

bN-ThresholdEUTRA E-UTRA threshold value associated with the selected trigger quantity (RSRP, RSRQ, SINR) to be used in inter RAT measurement report triggering condition for event number bN. In the same eventB2, the network configures the same CHOICE name (rsrp, rsrq or sinr) for the MeasTriggerQuantity of the b2-Threshold1 and for the MeasTriggerQuantityEUTRA of the b2-Threshold2EUTRA.

eventId Choice of inter RAT event triggered reporting criteria.

maxReportCells Max number of non-serving cells/candidate L2 U2N Relay UEs to include in the measurement report.

reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types

reportOnLeave Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList, as specified in 5.5.4.1.

reportQuantity, reportQuantityUTRA-FDD The cell measurement quantities to be included in the measurement report. If the field eventB1-UTRA-FDD or eventB2-UTRA-FDD is present, the UE shall ignore the value(s) provided in reportQuantity.

reportQuantityRelay The L2 U2N Relay UE measurement quantity to be included in measuremet report.

timeToTrigger Time during which specific criteria for the event needs to be met in order to trigger a measurement report.

bN-ThresholdUTRA-FDD UTRA-FDD threshold value associated with the selected trigger quantity (RSCP, EcN0) to be used in inter RAT measurement report triggering condition for event number bN. utra-FDD-RSCP corresponds to CPICH_RSCP in TS 25.133 [46] for FDD. utra-FDD-EcN0 corresponds to CPICH_Ec/No in TS 25.133 [46] for FDD. For utra-FDD-RSCP: The actual value is field value – 115 dBm. For utra-FDD-EcN0: The actual value is (field value – 49)/2 dB.

y1-Threshold1 NR threshold to be used in measurement report triggering condition for event Y1.

yN-Threshold2-Relay L2 U2N Relay threshold value associated with the selected trigger quantity (i.e. RSRP) to be used in measurement report triggering condition for event number YN.

PeriodicalReportConfigInterRAT field descriptions

maxReportCells Max number of non-serving cells/candidate L2 U2N Relay UEs to include in the measurement report.

reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types

reportQuantity, reportQuantityUTRA-FDD The cell measurement quantities to be included in the measurement report. If the field reportQuantityUTRA-FDD is present, the UE shall ignore the value(s) provided in reportQuantity.

– ReportConfigNR

The IE ReportConfigNR specifies criteria for triggering of an NR measurement reporting event or of a CHO, CPA or CPC event or of an L2 U2N relay measurement reporting event. For events labelled AN with N equal to 1, 2 and so on, measurement reporting events and CHO, CPA or CPC events are based on cell measurement results, which can either be derived based on SS/PBCH block or CSI-RS.

Event A1: Serving becomes better than absolute threshold;

Event A2: Serving becomes worse than absolute threshold;

Event A3: Neighbour becomes amount of offset better than PCell/PSCell;

Event A4: Neighbour becomes better than absolute threshold;

Event A5: PCell/PSCell becomes worse than absolute threshold1 AND Neighbour/SCell becomes better than another absolute threshold2;

Event A6: Neighbour becomes amount of offset better than SCell;

Event D1: Distance between UE and a reference location referenceLocation1 becomes larger than configured threshold distanceThreshFromReference1 and distance between UE and a reference location referenceLocation2 becomes shorter than configured threshold distanceThreshFromReference2;

CondEvent A3: Conditional reconfiguration candidate becomes amount of offset better than PCell/PSCell;

CondEvent A4: Conditional reconfiguration candidate becomes better than absolute threshold;

CondEvent A5: PCell/PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2;

CondEvent D1: Distance between UE and a reference location referenceLocation1 becomes larger than configured threshold distanceThreshFromReference1 and distance between UE and a reference location referenceLocation2 of conditional reconfiguration candidate becomes shorter than configured threshold distanceThreshFromReference2;

CondEvent T1: Time measured at UE becomes more than configured threshold t1-Threshold but is less than t1-Threshold + duration;

Event X1: Serving L2 U2N Relay UE becomes worse than absolute threshold1 AND NR Cell becomes better than another absolute threshold2;

Event X2: Serving L2 U2N Relay UE becomes worse than absolute threshold;

For event I1, measurement reporting event is based on CLI measurement results, which can either be derived based on SRS-RSRP or CLI-RSSI.

Event I1: Interference becomes higher than absolute threshold.

ReportConfigNR information element

— ASN1START

— TAG-REPORTCONFIGNR-START

ReportConfigNR ::= SEQUENCE {

reportType CHOICE {

periodical PeriodicalReportConfig,

eventTriggered EventTriggerConfig,

…,

reportCGI ReportCGI,

reportSFTD ReportSFTD-NR,

condTriggerConfig-r16 CondTriggerConfig-r16,

cli-Periodical-r16 CLI-PeriodicalReportConfig-r16,

cli-EventTriggered-r16 CLI-EventTriggerConfig-r16,

rxTxPeriodical-r17 RxTxPeriodical-r17

}

}

ReportCGI ::= SEQUENCE {

cellForWhichToReportCGI PhysCellId,

…,

[[

useAutonomousGaps-r16 ENUMERATED {setup} OPTIONAL — Need R

]]

}

ReportSFTD-NR ::= SEQUENCE {

reportSFTD-Meas BOOLEAN,

reportRSRP BOOLEAN,

…,

[[

reportSFTD-NeighMeas ENUMERATED {true} OPTIONAL, — Need R

drx-SFTD-NeighMeas ENUMERATED {true} OPTIONAL, — Need R

cellsForWhichToReportSFTD SEQUENCE (SIZE (1..maxCellSFTD)) OF PhysCellId OPTIONAL — Need R

]]

}

CondTriggerConfig-r16 ::= SEQUENCE {

condEventId CHOICE {

condEventA3 SEQUENCE {

a3-Offset MeasTriggerQuantityOffset,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger

},

condEventA5 SEQUENCE {

a5-Threshold1 MeasTriggerQuantity,

a5-Threshold2 MeasTriggerQuantity,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger

},

…,

condEventA4-r17 SEQUENCE {

a4-Threshold-r17 MeasTriggerQuantity,

hysteresis-r17 Hysteresis,

timeToTrigger-r17 TimeToTrigger

},

condEventD1-r17 SEQUENCE {

distanceThreshFromReference1-r17 INTEGER(0.. 65525),

distanceThreshFromReference2-r17 INTEGER(0.. 65525),

referenceLocation1-r17 ReferenceLocation-r17,

referenceLocation2-r17 ReferenceLocation-r17,

hysteresisLocation-r17 HysteresisLocation-r17,

timeToTrigger-r17 TimeToTrigger

},

condEventT1-r17 SEQUENCE {

t1-Threshold-r17 INTEGER (0..549755813887),

duration-r17 INTEGER (1..6000)

}

},

rsType-r16 NR-RS-Type,

…

}

EventTriggerConfig::= SEQUENCE {

eventId CHOICE {

eventA1 SEQUENCE {

a1-Threshold MeasTriggerQuantity,

reportOnLeave BOOLEAN,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger

},

eventA2 SEQUENCE {

a2-Threshold MeasTriggerQuantity,

reportOnLeave BOOLEAN,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger

},

eventA3 SEQUENCE {

a3-Offset MeasTriggerQuantityOffset,

reportOnLeave BOOLEAN,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger,

useAllowedCellList BOOLEAN

},

eventA4 SEQUENCE {

a4-Threshold MeasTriggerQuantity,

reportOnLeave BOOLEAN,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger,

useAllowedCellList BOOLEAN

},

eventA5 SEQUENCE {

a5-Threshold1 MeasTriggerQuantity,

a5-Threshold2 MeasTriggerQuantity,

reportOnLeave BOOLEAN,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger,

useAllowedCellList BOOLEAN

},

eventA6 SEQUENCE {

a6-Offset MeasTriggerQuantityOffset,

reportOnLeave BOOLEAN,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger,

useAllowedCellList BOOLEAN

},

…,

[[

eventX1-r17 SEQUENCE {

x1-Threshold1-Relay-r17 SL-MeasTriggerQuantity-r16,

x1-Threshold2-r17 MeasTriggerQuantity,

reportOnLeave-r17 BOOLEAN,

hysteresis-r17 Hysteresis,

timeToTrigger-r17 TimeToTrigger,

useAllowedCellList-r17 BOOLEAN

},

eventX2-r17 SEQUENCE {

x2-Threshold-Relay-r17 SL-MeasTriggerQuantity-r16,

reportOnLeave-r17 BOOLEAN,

hysteresis-r17 Hysteresis,

timeToTrigger-r17 TimeToTrigger

},

eventD1-r17 SEQUENCE {

distanceThreshFromReference1-r17 INTEGER(1.. 65525),

distanceThreshFromReference2-r17 INTEGER(1.. 65525),

referenceLocation1-r17 ReferenceLocation-r17,

referenceLocation2-r17 ReferenceLocation-r17,

reportOnLeave-r17 BOOLEAN,

hysteresisLocation-r17 HysteresisLocation-r17,

timeToTrigger-r17 TimeToTrigger

}

]]

},

rsType NR-RS-Type,

reportInterval ReportInterval,

reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

reportQuantityCell MeasReportQuantity,

maxReportCells INTEGER (1..maxCellReport),

reportQuantityRS-Indexes MeasReportQuantity OPTIONAL, — Need R

maxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport) OPTIONAL, — Need R

includeBeamMeasurements BOOLEAN,

reportAddNeighMeas ENUMERATED {setup} OPTIONAL, — Need R

…,

[[

measRSSI-ReportConfig-r16 MeasRSSI-ReportConfig-r16 OPTIONAL, — Need R

useT312-r16 BOOLEAN OPTIONAL, — Need M

includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, — Need R

includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, — Need M

includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, — Need M

includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL — Need M

]],

[[

coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, — Need R

reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL — Need R

]]

}

PeriodicalReportConfig ::= SEQUENCE {

rsType NR-RS-Type,

reportInterval ReportInterval,

reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

reportQuantityCell MeasReportQuantity,

maxReportCells INTEGER (1..maxCellReport),

reportQuantityRS-Indexes MeasReportQuantity OPTIONAL, — Need R

maxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport) OPTIONAL, — Need R

includeBeamMeasurements BOOLEAN,

useAllowedCellList BOOLEAN,

…,

[[

measRSSI-ReportConfig-r16 MeasRSSI-ReportConfig-r16 OPTIONAL, — Need R

includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, — Need R

includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, — Need M

includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, — Need M

includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, — Need M

ul-DelayValueConfig-r16 SetupRelease { UL-DelayValueConfig-r16 } OPTIONAL, — Need M

reportAddNeighMeas-r16 ENUMERATED {setup} OPTIONAL — Need R

]],

[[

ul-ExcessDelayConfig-r17 SetupRelease { UL-ExcessDelayConfig-r17 } OPTIONAL, — Need M

coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, — Need R

reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL — Need R

]]

}

NR-RS-Type ::= ENUMERATED {ssb, csi-rs}

MeasTriggerQuantity ::= CHOICE {

rsrp RSRP-Range,

rsrq RSRQ-Range,

sinr SINR-Range

}

MeasTriggerQuantityOffset ::= CHOICE {

rsrp INTEGER (-30..30),

rsrq INTEGER (-30..30),

sinr INTEGER (-30..30)

}

MeasReportQuantity ::= SEQUENCE {

rsrp BOOLEAN,

rsrq BOOLEAN,

sinr BOOLEAN

}

MeasRSSI-ReportConfig-r16 ::= SEQUENCE {

channelOccupancyThreshold-r16 RSSI-Range-r16 OPTIONAL — Need R

}

CLI-EventTriggerConfig-r16 ::= SEQUENCE {

eventId-r16 CHOICE {

eventI1-r16 SEQUENCE {

i1-Threshold-r16 MeasTriggerQuantityCLI-r16,

reportOnLeave-r16 BOOLEAN,

hysteresis-r16 Hysteresis,

timeToTrigger-r16 TimeToTrigger

},

…

},

reportInterval-r16 ReportInterval,

reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

maxReportCLI-r16 INTEGER (1..maxCLI-Report-r16),

…

}

CLI-PeriodicalReportConfig-r16 ::= SEQUENCE {

reportInterval-r16 ReportInterval,

reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

reportQuantityCLI-r16 MeasReportQuantityCLI-r16,

maxReportCLI-r16 INTEGER (1..maxCLI-Report-r16),

…

}

RxTxPeriodical-r17 ::= SEQUENCE {

rxTxReportInterval-r17 RxTxReportInterval-r17 OPTIONAL, — Need R

reportAmount-r17 ENUMERATED {r1, infinity, spare6, spare5, spare4, spare3, spare2, spare1},

…

}

RxTxReportInterval-r17 ::= ENUMERATED {ms80,ms120,ms160,ms240,ms320,ms480,ms640,ms1024,ms1280,ms2048,ms2560,ms5120,spare4,spare3,spare2,spare1}

MeasTriggerQuantityCLI-r16 ::= CHOICE {

srs-RSRP-r16 SRS-RSRP-Range-r16,

cli-RSSI-r16 CLI-RSSI-Range-r16

}

MeasReportQuantityCLI-r16 ::= ENUMERATED {srs-rsrp, cli-rssi}

— TAG-REPORTCONFIGNR-STOP

— ASN1STOP

CondTriggerConfig field descriptions

a3-Offset Offset value(s) to be used in NR conditional reconfiguration triggering condition for cond event a3. The actual value is field value * 0.5 dB.

a4-Threshold Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR conditional reconfiguration triggering condition for cond event a4.

a5-Threshold1/ a5-Threshold2 Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR conditional reconfiguration triggering condition for cond event a5. In the same condeventA5, the network configures the same quantity for the MeasTriggerQuantity of the a5-Threshold1 and for the MeasTriggerQuantity of the a5-Threshold2.

condEventId Choice of NR conditional reconfiguration event triggered criteria.

distanceThreshFromReference1, distanceThreshFromReference2 Distance from a reference location configured with referenceLocation1 or referenceLocation2. Each step represents 50m.

duration This field is used for defining the leaving condition T1-2 for conditional HO event condEventT1. Each step represents 100ms.

referenceLocation1, referenceLocation2 Reference locations used for condEventD1. The referenceLocation1 is associated to serving cell and referenceLocation2 is associated to candidate target cell.

t1-Threshold The field counts the number of UTC seconds in 10 ms units since 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900).

timeToTrigger Time during which specific criteria for the event needs to be met in order to execute the conditional reconfiguration evaluation.

ReportConfigNR field descriptions

reportType Type of the configured measurement report. In MR-DC, network does not configure report of type reportCGI using SRB3. The condTriggerConfig is used for CHO, CPA or CPC configuration.

ReportCGI field descriptions

useAutonomousGaps Indicates whether or not the UE is allowed to use autonomous gaps in acquiring system information from the NR neighbour cell. When the field is included, the UE applies the corresponding value for T321.

EventTriggerConfig field descriptions

a3-Offset/a6-Offset Offset value(s) to be used in NR measurement report triggering condition for event a3/a6. The actual value is field value * 0.5 dB.

aN-ThresholdM Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR measurement report triggering condition for event number aN. If multiple thresholds are defined for event number aN, the thresholds are differentiated by M. The network configures aN-Threshold1 only for events A1, A2, A4, A5 and a5-Threshold2 only for event A5. In the same eventA5, the network configures the same quantity for the MeasTriggerQuantity of the a5-Threshold1 and for the MeasTriggerQuantity of the a5-Threshold2.

channelOccupancyThreshold RSSI threshold which is used for channel occupancy evaluation.

coarseLocationRequest This field is used to request UE to report coarse location information.

distanceThreshFromReference1, distanceThreshFromReference2 Threshold value associated to the distance from a reference location configured with referenceLocation1 or referenceLocation2. Each step represents 50m.

eventId Choice of NR event triggered reporting criteria.

maxNrofRS-IndexesToReport Max number of RS indexes to include in the measurement report for A1-A6 events.

maxReportCells Max number of non-serving cells to include in the measurement report.

referenceLocation1, referenceLocation2 Reference locations used for eventD1. The referenceLocation1 is associated to serving cell and referenceLocation2 is associated to neighbour cell.

reportAddNeighMeas Indicates that the UE shall include the best neighbour cells per serving frequency.

reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types.

reportOnLeave Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList, as specified in 5.5.4.1. Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met if configured in eventD1, as specified in 5.5.4.1.

reportQuantityCell The cell measurement quantities to be included in the measurement report.

reportQuantityRS-Indexes Indicates which measurement information per RS index the UE shall include in the measurement report.

timeToTrigger Time during which specific criteria for the event needs to be met in order to trigger a measurement report.

useAllowedCellList Indicates whether only the cells included in the allow-list of the associated measObject are applicable as specified in 5.5.4.1.

useT312 If value TRUE is configured, the UE shall use the timer T312 with the value t312 as specified in the corresponding measObjectNR. If value FALSE is configured, the timer T312 is considered as disabled. Network configures value TRUE only if reportType is set to eventTriggered.

xN-ThresholdM Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR measurement report triggering condition for event xN. If multiple thresholds are defined for event number xN, the thresholds are differentiated by M. x1-Threshold1 and x2-Threshold indicates the threshold value for the serving L2 U2N Relay UE, x1-Threshold2 indicates the threshold value for the NR Cells.

CLI-EventTriggerConfig field descriptions

i1-Threshold Threshold value associated to the selected trigger quantity (e.g. SRS-RSRP, CLI-RSSI) to be used in CLI measurement report triggering condition for event i1.

eventId Choice of CLI event triggered reporting criteria.

maxReportCLI Max number of CLI measurement resource to include in the measurement report.

reportAmount Number of measurement reports.

reportOnLeave Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList, as specified in 5.5.4.1.

timeToTrigger Time during which specific criteria for the event needs to be met in order to trigger a measurement report.

CLI-PeriodicalReportConfig field descriptions

maxReportCLI Max number of CLI measurement resource to include in the measurement report.

reportAmount Number of measurement reports.

reportQuantityCLI The CLI measurement quantities to be included in the measurement report.

PeriodicalReportConfig field descriptions

coarseLocationRequest This field is used to request UE to report coarse location information.

maxNrofRS-IndexesToReport Max number of RS indexes to include in the measurement report.

maxReportCells Max number of non-serving cells to include in the measurement report.

reportAddNeighMeas Indicates that the UE shall include the best neighbour cells per serving frequency.

reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types

reportQuantityCell The cell measurement quantities to be included in the measurement report.

reportQuantityRS-Indexes Indicates which measurement information per RS index the UE shall include in the measurement report.

ul-DelayValueConfig If the field is present, the UE shall perform the actual UL PDCP Packet Average Delay measurement per DRB as specified in TS 38.314 [53] and the UE shall ignore the fields reportQuantityCell and maxReportCells. The applicable values for the corresponding reportInterval are (one of the) {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1,min6, min12, min30}. The reportInterval indicates the periodicity for performing and reporting of UL PDCP Packet Average Delay per DRB measurement as specified in TS 38.314 [53].

ul-ExcessDelayConfig If the field is present, the UE shall perform the actual UL PDCP Excess Packet Delay per DRB measurement as specified in TS 38.314 [53] and the UE shall ignore the fields reportQuantityCell and maxReportCells. The applicable values for the corresponding reportInterval are (one of the) {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1,min6, min12, min30}. The reportInterval indicates the periodicity for performing and reporting of UL PDCP Excess Packet Delay per DRB measurement as specified in TS 38.314 [53].

useAllowedCellList Indicates whether only the cells included in the allow-list of the associated measObject are applicable as specified in 5.5.4.1.

ReportSFTD-NR field descriptions

cellForWhichToReportSFTD Indicates the target NR neighbour cells for SFTD measurement between PCell and NR neighbour cells.

drx-SFTD-NeighMeas Indicates that the UE shall use available idle periods (i.e. DRX off periods) for the SFTD measurement in NR standalone. The network only includes drx-SFTD-NeighMeas field when reprtSFTD-NeighMeas is set to true.

reportSFTD-Meas Indicates whether UE is required to perform SFTD measurement between PCell and NR PSCell in NR-DC.

reportSFTD-NeighMeas Indicates whether UE is required to perform SFTD measurement between PCell and NR neighbour cells in NR standalone. The network does not include this field if reportSFTD-Meas is set to true.

reportRSRP Indicates whether UE is required to include RSRP result of NR PSCell or NR neighbour cells in SFTD measurement result, derived based on SSB. If it is set to true, the network should ensure that ssb-ConfigMobility is included in the measurement object for NR PSCell or NR neighbour cells.

RxTxPeriodical field descriptions

reportAmount This field indicates the number of UE Rx-Tx time difference measurement reports. If configured to r1, the network does not configure rxTxReportInterval and only one measurement is reported. If configured to infinity, UE periodically reports measurements according to the periodicity configured by rxTxReportInterval.

rxTxReportInterval This field indicates the measurement reporting periodicity of UE Rx-Tx time difference.

other field descriptions

MeasTriggerQuantity SINR is applicable only for CONNECTED mode events.

– ReportConfigNR-SL

The IE ReportConfigNR-SL specifies criteria for triggering of a CBR measurement reporting event for NR sidelink communication. Measurement reporting events are based on CBR measurement results on the corresponding transmission resource pools. These events are labelled CN with N equal to 1 and 2.

Event C1: CBR of NR sidelink communication becomes better than absolute threshold;

Event C2: CBR of NR sidelink communication becomes worse than absolute threshold;

ReportConfigNR-SL information element

— ASN1START

— TAG-REPORTCONFIGNR-SL-START

ReportConfigNR-SL-r16 ::= SEQUENCE {

reportType-r16 CHOICE {

periodical-r16 PeriodicalReportConfigNR-SL-r16,

eventTriggered-r16 EventTriggerConfigNR-SL-r16

}

}

EventTriggerConfigNR-SL-r16::= SEQUENCE {

eventId-r16 CHOICE {

eventC1 SEQUENCE {

c1-Threshold-r16 SL-CBR-r16,

hysteresis-r16 Hysteresis,

timeToTrigger-r16 TimeToTrigger

},

eventC2-r16 SEQUENCE {

c2-Threshold-r16 SL-CBR-r16,

hysteresis-r16 Hysteresis,

timeToTrigger-r16 TimeToTrigger

},

…

},

reportInterval-r16 ReportInterval,

reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

reportQuantity-r16 MeasReportQuantity-r16,

…

}

PeriodicalReportConfigNR-SL-r16 ::= SEQUENCE {

reportInterval-r16 ReportInterval,

reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

reportQuantity-r16 MeasReportQuantity-r16,

…

}

MeasReportQuantity-r16 ::= SEQUENCE {

cbr-r16 BOOLEAN,

…

}

— TAG-REPORTCONFIGNR-SL-STOP

— ASN1STOP

ReportConfigNR-SL field descriptions

reportType Type of the configured CBR measurement report for NR sidelink communication.

EventTriggerConfigNR-SL field descriptions

cN-Threshold Threshold used for events C1 and C2 specified in clauses 5.5.4.11 and 5.5.4.12, respectively.

eventId Choice of NR event triggered reporting criteria.

reportAmoun Number of measurement reports applicable for eventTriggered as well as for periodical report types.

reportQuantity The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result.

timeToTrigger Time during which specific criteria for the event needs to be met in order to trigger a measurement report.

PeriodicalReportConfigNR-SL field descriptions

reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types.

reportQuantity The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result.

– ReportConfigToAddModList

The IE ReportConfigToAddModList concerns a list of reporting configurations to add or modify.

ReportConfigToAddModList information element

— ASN1START

— TAG-REPORTCONFIGTOADDMODLIST-START

ReportConfigToAddModList ::= SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod

ReportConfigToAddMod ::= SEQUENCE {

reportConfigId ReportConfigId,

reportConfig CHOICE {

reportConfigNR ReportConfigNR,

…,

reportConfigInterRAT ReportConfigInterRAT,

reportConfigNR-SL-r16 ReportConfigNR-SL-r16

}

}

— TAG-REPORTCONFIGTOADDMODLIST-STOP

— ASN1STOP

– ReportInterval

The IE ReportInterval indicates the interval between periodical reports. The ReportInterval is applicable if the UE performs periodical reporting (i.e. when reportAmount exceeds 1), for triggerTypeevent as well as for triggerTypeperiodical. Value ms120 corresponds to 120 ms, value ms240 corresponds to 240 ms and so on, while value min1 corresponds to 1 min, min6 corresponds to 6 min and so on.

ReportInterval information element

— ASN1START

— TAG-REPORTINTERVAL-START

ReportInterval ::= ENUMERATED {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960,

min1,min6, min12, min30 }

— TAG-REPORTINTERVAL-STOP

— ASN1STOP

– ReselectionThreshold

The IE ReselectionThreshold is used to indicate an Rx level threshold for cell reselection. Actual value of threshold = field value * 2 [dB].

ReselectionThreshold information element

— ASN1START

— TAG-RESELECTIONTHRESHOLD-START

ReselectionThreshold ::= INTEGER (0..31)

— TAG-RESELECTIONTHRESHOLD-STOP

— ASN1STOP

– ReselectionThresholdQ

The IE ReselectionThresholdQ is used to indicate a quality level threshold for cell reselection. Actual value of threshold = field value [dB].

ReselectionThresholdQ information element

— ASN1START

— TAG-RESELECTIONTHRESHOLDQ-START

ReselectionThresholdQ ::= INTEGER (0..31)

— TAG-RESELECTIONTHRESHOLDQ-STOP

— ASN1STOP

– ResumeCause

The IE ResumeCause is used to indicate the resume cause in RRCResumeRequest and RRCResumeRequest1.

ResumeCause information element

— ASN1START

— TAG-RESUMECAUSE-START

ResumeCause ::= ENUMERATED {emergency, highPriorityAccess, mt-Access, mo-Signalling,

mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps-PriorityAccess,

mcs-PriorityAccess, spare1, spare2, spare3, spare4, spare5 }

— TAG-RESUMECAUSE-STOP

— ASN1STOP

– RLC-BearerConfig

The IE RLC-BearerConfig is used to configure an RLC entity, a corresponding logical channel in MAC and the linking to a PDCP entity (served radio bearer).

RLC-BearerConfig information element

— ASN1START

— TAG-RLC-BEARERCONFIG-START

RLC-BearerConfig ::= SEQUENCE {

logicalChannelIdentity LogicalChannelIdentity,

servedRadioBearer CHOICE {

srb-Identity SRB-Identity,

drb-Identity DRB-Identity

} OPTIONAL, — Cond LCH-SetupOnly

reestablishRLC ENUMERATED {true} OPTIONAL, — Need N

rlc-Config RLC-Config OPTIONAL, — Cond LCH-Setup

mac-LogicalChannelConfig LogicalChannelConfig OPTIONAL, — Cond LCH-Setup

…,

[[

rlc-Config-v1610 RLC-Config-v1610 OPTIONAL — Need R

]],

[[

rlc-Config-v1700 RLC-Config-v1700 OPTIONAL, — Need R

logicalChannelIdentityExt-r17 LogicalChannelIdentityExt-r17 OPTIONAL, — Cond LCH-SetupModMRB

multicastRLC-BearerConfig-r17 MulticastRLC-BearerConfig-r17 OPTIONAL, — Cond LCH-SetupOnlyMRB

servedRadioBearerSRB4-r17 SRB-Identity-v1700 OPTIONAL — Need N

]]

}

MulticastRLC-BearerConfig-r17 ::= SEQUENCE {

servedMBS-RadioBearer-r17 MRB-Identity-r17,

isPTM-Entity-r17 ENUMERATED {true} OPTIONAL — NEED S

}

LogicalChannelIdentityExt-r17 ::= INTEGER (320..65855)

— TAG-RLC-BEARERCONFIG-STOP

— ASN1STOP

RLC-BearerConfig field descriptions

isPTM-Entity If configured, indicates that the RLC entity is used for PTM reception. When the field is absent the RLC entity is used for PTP transmission/reception.

logicalChannelIdentity ID used commonly for the MAC logical channel and for the RLC bearer. Value 4 is not configured for DRBs if SRB4 is configured.

logicalChannelIdentityExt Extended logical channel ID used commonly for the MAC logical channel and for the RLC bearer for PTM reception. If this field is configured, the UE shall ignore logicalChannelIdentity.

reestablishRLC Indicates that RLC should be re-established. Network sets this to true at least whenever the security key used for the radio bearer associated with this RLC entity changes. For SRB2, multicast MRBs and DRBs, unless full configuration is used, it is also set to true during the resumption of the RRC connection or the first reconfiguration after reestablishment. For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment, the network does not set this field to true.

rlc-Config Determines the RLC mode (UM, AM) and provides corresponding parameters. RLC mode reconfiguration can only be performed by DRB/multicast MRB release/addition or full configuration. The network may configure rlc-Config-v1610 only when rlc-Config (without suffix) is set to am.

servedMBS-RadioBearer Associates the RLC Bearer with a multicast MRB. The UE shall deliver DL RLC SDUs received via the RLC entity of this RLC bearer to the PDCP entity of the servedMBS-RadioBearer.

servedRadioBearer, servedRadioBearerSRB4 Associates the RLC Bearer with an SRB or a DRB. The UE shall deliver DL RLC SDUs received via the RLC entity of this RLC bearer to the PDCP entity of the servedRadioBearer. Furthermore, the UE shall advertise and deliver uplink PDCP PDUs of the uplink PDCP entity of the servedRadioBearer to the uplink RLC entity of this RLC bearer unless the uplink scheduling restrictions (moreThanOneRLC in PDCP-Config and the restrictions in LogicalChannelConfig) forbid it to do so.

Conditional Presence	Explanation
LCH-Setup	This field is mandatory present upon creation of a new logical channel for a DRB or a multicast MRB. This field is optionally present, Need S, upon creation of a new logical channel for an SRB. It is optionally present, Need M, otherwise.
LCH-SetupModMRB	This field is optionally present upon creation of a new logical channel for PTM reception for a multicast MRB. If this field is included upon creation of a new logical channel for PTM reception for a multicast MRB, it shall be present when modifying this logical channel. The field is absent for logical channels configured for an SRB and a DRB.
LCH-SetupOnly	This field is mandatory present upon creation of a new logical channel for a DRB or an SRB (servedRadioBearer). It is absent, Need M otherwise.
LCH-SetupOnlyMRB	This field is mandatory present upon creation of a new logical channel for a multicast MRB and upon modification of MRB-Identity of the served MRB. It is absent, Need M otherwise.

– RLC-Config

The IE RLC-Config is used to specify the RLC configuration of SRBs, multicast MRBs and DRBs.

RLC-Config information element

— ASN1START

— TAG-RLC-CONFIG-START

RLC-Config ::= CHOICE {

am SEQUENCE {

ul-AM-RLC UL-AM-RLC,

dl-AM-RLC DL-AM-RLC

},

um-Bi-Directional SEQUENCE {

ul-UM-RLC UL-UM-RLC,

dl-UM-RLC DL-UM-RLC

},

um-Uni-Directional-UL SEQUENCE {

ul-UM-RLC UL-UM-RLC

},

um-Uni-Directional-DL SEQUENCE {

dl-UM-RLC DL-UM-RLC

},

…

}

UL-AM-RLC ::= SEQUENCE {

sn-FieldLength SN-FieldLengthAM OPTIONAL, — Cond Reestab

t-PollRetransmit T-PollRetransmit,

pollPDU PollPDU,

pollByte PollByte,

maxRetxThreshold ENUMERATED { t1, t2, t3, t4, t6, t8, t16, t32 }

}

DL-AM-RLC ::= SEQUENCE {

sn-FieldLength SN-FieldLengthAM OPTIONAL, — Cond Reestab

t-Reassembly T-Reassembly,

t-StatusProhibit T-StatusProhibit

}

UL-UM-RLC ::= SEQUENCE {

sn-FieldLength SN-FieldLengthUM OPTIONAL — Cond Reestab

}

DL-UM-RLC ::= SEQUENCE {

sn-FieldLength SN-FieldLengthUM OPTIONAL, — Cond Reestab

t-Reassembly T-Reassembly

}

T-PollRetransmit ::= ENUMERATED {

ms5, ms10, ms15, ms20, ms25, ms30, ms35,

ms40, ms45, ms50, ms55, ms60, ms65, ms70,

ms75, ms80, ms85, ms90, ms95, ms100, ms105,

ms110, ms115, ms120, ms125, ms130, ms135,

ms140, ms145, ms150, ms155, ms160, ms165,

ms170, ms175, ms180, ms185, ms190, ms195,

ms200, ms205, ms210, ms215, ms220, ms225,

ms230, ms235, ms240, ms245, ms250, ms300,

ms350, ms400, ms450, ms500, ms800, ms1000,

ms2000, ms4000, ms1-v1610, ms2-v1610, ms3-v1610,

ms4-v1610, spare1}

PollPDU ::= ENUMERATED {

p4, p8, p16, p32, p64, p128, p256, p512, p1024, p2048, p4096, p6144, p8192, p12288, p16384,p20480,

p24576, p28672, p32768, p40960, p49152, p57344, p65536, infinity, spare8, spare7, spare6, spare5, spare4,

spare3, spare2, spare1}

PollByte ::= ENUMERATED {

kB1, kB2, kB5, kB8, kB10, kB15, kB25, kB50, kB75,

kB100, kB125, kB250, kB375, kB500, kB750, kB1000,

kB1250, kB1500, kB2000, kB3000, kB4000, kB4500,

kB5000, kB5500, kB6000, kB6500, kB7000, kB7500,

mB8, mB9, mB10, mB11, mB12, mB13, mB14, mB15,

mB16, mB17, mB18, mB20, mB25, mB30, mB40, infinity,

spare20, spare19, spare18, spare17, spare16,

spare15, spare14, spare13, spare12, spare11,

spare10, spare9, spare8, spare7, spare6, spare5,

spare4, spare3, spare2, spare1}

T-Reassembly ::= ENUMERATED {

ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35,

ms40, ms45, ms50, ms55, ms60, ms65, ms70,

ms75, ms80, ms85, ms90, ms95, ms100, ms110,

ms120, ms130, ms140, ms150, ms160, ms170,

ms180, ms190, ms200, spare1}

T-StatusProhibit ::= ENUMERATED {

ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35,

ms40, ms45, ms50, ms55, ms60, ms65, ms70,

ms75, ms80, ms85, ms90, ms95, ms100, ms105,

ms110, ms115, ms120, ms125, ms130, ms135,

ms140, ms145, ms150, ms155, ms160, ms165,

ms170, ms175, ms180, ms185, ms190, ms195,

ms200, ms205, ms210, ms215, ms220, ms225,

ms230, ms235, ms240, ms245, ms250, ms300,

ms350, ms400, ms450, ms500, ms800, ms1000,

ms1200, ms1600, ms2000, ms2400, spare2, spare1}

SN-FieldLengthUM ::= ENUMERATED {size6, size12}

SN-FieldLengthAM ::= ENUMERATED {size12, size18}

RLC-Config-v1610 ::= SEQUENCE {

dl-AM-RLC-v1610 DL-AM-RLC-v1610

}

RLC-Config-v1700 ::= SEQUENCE {

dl-AM-RLC-v1700 DL-AM-RLC-v1700,

dl-UM-RLC-v1700 DL-UM-RLC-v1700

}

DL-AM-RLC-v1610 ::= SEQUENCE {

t-StatusProhibit-v1610 T-StatusProhibit-v1610 OPTIONAL, — Need N

…

}

DL-AM-RLC-v1700 ::= SEQUENCE {

t-ReassemblyExt-r17 T-ReassemblyExt-r17 OPTIONAL — Need N

}

DL-UM-RLC-v1700 ::= SEQUENCE {

t-ReassemblyExt-r17 T-ReassemblyExt-r17 OPTIONAL — Need N

}

T-StatusProhibit-v1610 ::= ENUMERATED { ms1, ms2, ms3, ms4, spare4, spare3, spare2, spare1}

T-ReassemblyExt-r17 ::= ENUMERATED {ms210, ms220, ms340, ms350, ms550, ms1100, ms1650, ms2200}

— TAG-RLC-CONFIG-STOP

— ASN1STOP

RLC-Config field descriptions
maxRetxThreshold Parameter for RLC AM in TS 38.322 [4]. Value t1 corresponds to 1 retransmission, value t2 corresponds to 2 retransmissions and so on.
pollByte Parameter for RLC AM in TS 38.322 [4]. Value kB25 corresponds to 25 kBytes, value kB50 corresponds to 50 kBytes and so on. infinity corresponds to an infinite amount of kBytes.
pollPDU Parameter for RLC AM in TS 38.322 [4]. Value p4 corresponds to 4 PDUs, value p8 corresponds to 8 PDUs and so on. infinity corresponds to an infinite number of PDUs.
sn-FieldLength Indicates the RLC SN field size, see TS 38.322 [4], in bits. Value size6 means 6 bits, value size12 means 12 bits, value size18 means 18 bits. The value of sn-FieldLength of an RLC entity for the DRB/multicast MRB shall be changed only using reconfiguration with sync. The network configures only value size12 in SN-FieldLengthAM for SRB.
t-PollRetransmit Timer for RLC AM in TS 38.322 [4], in milliseconds. Value ms5 means 5 ms, value ms10 means 10 ms and so on.
t-Reassembly, t-ReassemblyExt Timer for reassembly in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-ReassemblyExt-r17 is configured, the UE shall ignore t-Reassembly (without suffix).
t-StatusProhibit Timer for status reporting in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-StatusProhibit-v1610 is present, the UE shall ignore t-StatusProhibit (without suffix).

Conditional Presence	Explanation
Reestab	The field is mandatory present at RLC bearer setup. It is optionally present, need M, at RLC re-establishment. Otherwise it is absent. Need M.

– RLF-TimersAndConstants

The IE RLF-TimersAndConstants is used to configure UE specific timers and constants.

RLF-TimersAndConstants information element

— ASN1START

— TAG-RLF-TIMERSANDCONSTANTS-START

RLF-TimersAndConstants ::= SEQUENCE {

t310 ENUMERATED {ms0, ms50, ms100, ms200, ms500, ms1000, ms2000, ms4000, ms6000},

n310 ENUMERATED {n1, n2, n3, n4, n6, n8, n10, n20},

n311 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10},

…,

[[

t311 ENUMERATED {ms1000, ms3000, ms5000, ms10000, ms15000, ms20000, ms30000}

]]

}

— TAG-RLF-TIMERSANDCONSTANTS-STOP

— ASN1STOP

RLF-TimersAndConstants field descriptions
n3xy Constants are described in clause 7.3. Value n1 corresponds to 1, value n2 corresponds to 2 and so on.
t3xy Timers are described in clause 7.1. Value ms0 corresponds to 0 ms, value ms50 corresponds to 50 ms and so on.

– RNTI-Value

The IE RNTI-Value represents a Radio Network Temporary Identity.

RNTI-Value information element

— ASN1START

— TAG-RNTI-VALUE-START

RNTI-Value ::= INTEGER (0..65535)

— TAG-RNTI-VALUE-STOP

— ASN1STOP

– RSRP-Range

The IE RSRP-Range specifies the value range used in RSRP measurements and thresholds. For measurements, integer value for RSRP measurements is according to Table 10.1.6.1-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value – 156) dBm, except for the IE value 127, in which case the actual value is infinity.

RSRP-Range information element

— ASN1START

— TAG-RSRP-RANGE-START

RSRP-Range ::= INTEGER(0..127)

— TAG-RSRP-RANGE-STOP

— ASN1STOP

– RSRQ-Range

The IE RSRQ-Range specifies the value range used in RSRQ measurements and thresholds. For measurements, integer value for RSRQ measurements is according to Table 10.1.11.1-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value – 87) / 2 dB.

RSRQ-Range information element

— ASN1START

— TAG-RSRQ-RANGE-START

RSRQ-Range ::= INTEGER(0..127)

— TAG-RSRQ-RANGE-STOP

— ASN1STOP

– RSSI-Range

The IE RSSI-Range specifies the value range used in RSSI measurements and thresholds for NR operation with shared spectrum channel access. The integer value for RSSI measurements is according to Table 10.1.34.3-1 in TS 38.133 [14].

RSSI-Range information element

— ASN1START

— TAG-RSSI-RANGE-START

RSSI-Range-r16 ::= INTEGER(0..76)

— TAG-RSSI-RANGE-STOP

— ASN1STOP

– RxTxTimeDiff

The IE RxTxTimeDiff contains the Rx-Tx time difference measurement at either the UE or the gNB.

RxTxTimeDiff information element

— ASN1START

— TAG-RXTXTIMEDIFF-START

RxTxTimeDiff-r17 ::= SEQUENCE {

result-k5-r17 INTEGER (0..61565) OPTIONAL, — Need N

…

}

— TAG-RXTXTIMEDIFF-STOP

— ASN1STOP

RxTxTimeDiff field descriptions

result-k5 This field indicates the Rx-Tx time difference measurement, see TS 38.215 [9], clause 10.1.25.3.1 of TS 38.133 [14] for UE Rx-Tx time difference and clause 13.2.1 of TS 38.133 [14] for gNB Rx-Tx time difference.

– SCellActivationRS-Config

The IE SCellActivationRS-Config is used to configure a Reference Signal for fast activation of the SCell where the IE is included (see TS 38.214 [19], clause 5.2.1.5.3. Usage of an SCellActivationRS-Config is indicated by including its scellActivationRS-Id in the Enhanced SCell activation MAC CE (see TS 38.321 [3] clause 6.1.3.55).

SCellActivationRS-Config information element

— ASN1START

— TAG-SCELLACTIVATIONRS-CONFIG-START

SCellActivationRS-Config-r17 ::= SEQUENCE {

scellActivationRS-Id-r17 SCellActivationRS-ConfigId-r17,

resourceSet-r17 NZP-CSI-RS-ResourceSetId,

gapBetweenBursts-r17 INTEGER (2..31) OPTIONAL, — Need R

qcl-Info-r17 TCI-StateId,

…

}

— TAG-SCELLACTIVATIONRS-CONFIG-STOP

— ASN1STOP

SCellActivationRS-Config field descriptions

gapBetweenBursts When this field is present, there are two bursts and it indicates the gap between the two bursts in number of slots. When this field is absent, there is a single burst.

qcl-Info Reference to TCI-State for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by resourceSet (see TS 38.214 [19], clause 5.1.6.1.1.1). TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink of this serving cell indicated by firstActiveDownlinkBWP-Id in the ServingCellConfig in which this IE is included.

resourceSet nzp-CSI-ResourceSetId of the NZP-CSI-RS-ResourceSet of this serving cell used as resource configuration for one or two bursts for SCell activation. This NZP-CSI-RS-ResourceSet consists of four NZP CSI-RS resources in two consecutive slots with two NZP CSI-RS resources in each slot (see TS 38.214 [19], clause 5.1.6.1.1.1). The CSI-RS associated with this NZP-CSI-RS-ResourceSet are located in the BWP addressed by firstActiveDownlinkBWP-Id.

– SCellActivationRS-ConfigId

The IE SCellActivationRS-ConfigId is used to identify one SCellActivationRS-Config.

SCellActivationRS-ConfigId information element

— ASN1START

— TAG-SCELLACTIVATIONRS-CONFIGID-START

SCellActivationRS-ConfigId-r17 ::= INTEGER (1.. maxNrofSCellActRS-r17)

— TAG-SCELLACTIVATIONRS-CONFIGID-STOP

— ASN1STOP

– SCellIndex

The IE SCellIndex concerns a short identity, used to identify an SCell. The value range is shared across the Cell Groups.

SCellIndex information element

— ASN1START

— TAG-SCELLINDEX-START

SCellIndex ::= INTEGER (1..31)

— TAG-SCELLINDEX-STOP

— ASN1STOP

– SchedulingRequestConfig

The IE SchedulingRequestConfig is used to configure the parameters, for the dedicated scheduling request (SR) resources.

SchedulingRequestConfig information element

— ASN1START

— TAG-SCHEDULINGREQUESTCONFIG-START

SchedulingRequestConfig ::= SEQUENCE {

schedulingRequestToAddModList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddMod

OPTIONAL, — Need N

schedulingRequestToReleaseList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestId

OPTIONAL — Need N

}

SchedulingRequestToAddMod ::= SEQUENCE {

schedulingRequestId SchedulingRequestId,

sr-ProhibitTimer ENUMERATED {ms1, ms2, ms4, ms8, ms16, ms32, ms64, ms128} OPTIONAL, — Need S

sr-TransMax ENUMERATED { n4, n8, n16, n32, n64, spare3, spare2, spare1}

}

SchedulingRequestConfig-v1700 ::= SEQUENCE {

schedulingRequestToAddModListExt-v1700 SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddModExt-v1700

OPTIONAL — Need N

}

SchedulingRequestToAddModExt-v1700 ::= SEQUENCE {

sr-ProhibitTimer-v1700 ENUMERATED { ms192, ms256, ms320, ms384, ms448, ms512, ms576, ms640, ms1082, spare7, spare6, spare5, spare4, spare3, spare2, spare1}

OPTIONAL — Need R

}

— TAG-SCHEDULINGREQUESTCONFIG-STOP

— ASN1STOP

SchedulingRequestConfig field descriptions

schedulingRequestToAddModList, schedulingRequestToAddModListExt List of Scheduling Request configurations to add or modify. If schedulingRequestToAddModListExt is configured, it contains the same number of entries, and in the same order, as schedulingRequestToAddModList.

schedulingRequestToReleaseList List of Scheduling Request configurations to release.

SchedulingRequestToAddMod field descriptions

schedulingRequestId Used to modify a SR configuration and to indicate, in LogicalChannelConfig, the SR configuration to which a logical channel is mapped and to indicate, in SchedulingRequestresourceConfig, the SR configuration for which a scheduling request resource is used.

sr-ProhibitTimer Timer for SR transmission on PUCCH in TS 38.321 [3]. Value is in ms. Value ms1 corresponds to 1ms, value ms2 corresponds to 2ms, and so on. If sr-ProhibitTimer-v1700 is configured, UE shall ignore sr-ProhibitTimer (without suffix). If both sr-ProhibitTimer (without suffix) and sr-ProhibitTimer-v1700 are absent, the UE applies the value 0.

sr-TransMax Maximum number of SR transmissions as described in TS 38.321 [3]. Value n4 corresponds to 4, value n8 corresponds to 8, and so on.

– SchedulingRequestId

The IE SchedulingRequestId is used to identify a Scheduling Request instance in the MAC layer.

SchedulingRequestId information element

— ASN1START

— TAG-SCHEDULINGREQUESTID-START

SchedulingRequestId ::= INTEGER (0..7)

— TAG-SCHEDULINGREQUESTID-STOP

— ASN1STOP

– SchedulingRequestResourceConfig

The IE SchedulingRequestResourceConfig determines physical layer resources on PUCCH where the UE may send the dedicated scheduling request (D-SR) (see TS 38.213 [13], clause 9.2.4).

SchedulingRequestResourceConfig information element

— ASN1START

— TAG-SCHEDULINGREQUESTRESOURCECONFIG-START

SchedulingRequestResourceConfig ::= SEQUENCE {

schedulingRequestResourceId SchedulingRequestResourceId,

schedulingRequestID SchedulingRequestId,

periodicityAndOffset CHOICE {

sym2 NULL,

sym6or7 NULL,

sl1 NULL, — Recurs in every slot

sl2 INTEGER (0..1),

sl4 INTEGER (0..3),

sl5 INTEGER (0..4),

sl8 INTEGER (0..7),

sl10 INTEGER (0..9),

sl16 INTEGER (0..15),

sl20 INTEGER (0..19),

sl40 INTEGER (0..39),

sl80 INTEGER (0..79),

sl160 INTEGER (0..159),

sl320 INTEGER (0..319),

sl640 INTEGER (0..639)

} OPTIONAL, — Need M

resource PUCCH-ResourceId OPTIONAL — Need M

}

SchedulingRequestResourceConfigExt-v1610 ::= SEQUENCE {

phy-PriorityIndex-r16 ENUMERATED {p0, p1} OPTIONAL, — Need M

…

}

SchedulingRequestResourceConfigExt-v1700 ::= SEQUENCE {

periodicityAndOffset-r17 CHOICE {

sl1280 INTEGER (0..1279),

sl2560 INTEGER (0..2559),

sl5120 INTEGER (0..5119)

} OPTIONAL — Need M

}

— TAG-SCHEDULINGREQUESTRESOURCECONFIG-STOP

— ASN1STOP

SchedulingRequestResourceConfig field descriptions

periodicityAndOffset SR periodicity and offset in number of symbols or slots (see TS 38.213 [13], clause 9.2.4) The following periodicities may be configured depending on the chosen subcarrier spacing: SCS = 15 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 5sl, 8sl, 10sl, 16sl, 20sl, 40sl, 80sl SCS = 30 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 8sl, 10sl, 16sl, 20sl, 40sl, 80sl, 160sl SCS = 60 kHz: 2sym, 7sym/6sym, 1sl, 2sl, 4sl, 8sl, 16sl, 20sl, 40sl, 80sl, 160sl, 320sl SCS = 120 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 8sl, 16sl, 40sl, 80sl, 160sl, 320sl, 640sl SCS = 480 kHz: 1sl, 2sl, 4sl, 8sl, 16sl, 40sl, 80sl, 160sl, 320sl, 640sl, 1280sl, 2560sl SCS = 960 kHz: 1sl, 2sl, 4sl, 8sl, 16sl, 40sl, 80sl, 160sl, 320sl, 640sl, 1280sl, 2560sl, 5120sl sym6or7 corresponds to 6 symbols if extended cyclic prefix and a SCS of 60 kHz are configured, otherwise it corresponds to 7 symbols. For periodicities 2sym, 7sym and sl1 the UE assumes an offset of 0 slots. If periodicityAndOffset-r17 is present, any previously configured periodicityAndOffset (without suffix) is released, and vice versa.

phy-PriorityIndex Indicates whether this scheduling request resource is high or low priority in PHY prioritization/multiplexing handling (see TS 38.213 [13], clause 9.2.4). Value p0 indicates low priority and value p1 indicates high priority.

resource ID of the PUCCH resource in which the UE shall send the scheduling request. The actual PUCCH-Resource is configured in PUCCH-Config of the same UL BWP and serving cell as this SchedulingRequestResourceConfig. The network configures a PUCCH-Resource of PUCCH-format0 or PUCCH-format1 (other formats not supported) (see TS 38.213 [13], clause 9.2.4)

schedulingRequestID The ID of the SchedulingRequestConfig that uses this scheduling request resource.

– SchedulingRequestResourceId

The IE SchedulingRequestResourceId is used to identify scheduling request resources on PUCCH.

SchedulingRequestResourceId information element

— ASN1START

— TAG-SCHEDULINGREQUESTRESOURCEID-START

SchedulingRequestResourceId ::= INTEGER (1..maxNrofSR-Resources)

— TAG-SCHEDULINGREQUESTRESOURCEID-STOP

— ASN1STOP

– ScramblingId

The IE ScramblingID is used for scrambling channels and reference signals.

ScramblingId information element

— ASN1START

— TAG-SCRAMBLINGID-START

ScramblingId ::= INTEGER(0..1023)

— TAG-SCRAMBLINGID-STOP

— ASN1STOP

– SCS-SpecificCarrier

The IE SCS-SpecificCarrier provides parameters determining the location and width of the actual carrier or the carrier bandwidth. It is defined specifically for a numerology (subcarrier spacing (SCS)) and in relation (frequency offset) to Point A.

SCS-SpecificCarrier information element

— ASN1START

— TAG-SCS-SPECIFICCARRIER-START

SCS-SpecificCarrier ::= SEQUENCE {

offsetToCarrier INTEGER (0..2199),

subcarrierSpacing SubcarrierSpacing,

carrierBandwidth INTEGER (1..maxNrofPhysicalResourceBlocks),

…,

[[

txDirectCurrentLocation INTEGER (0..4095) OPTIONAL — Need S

]]

}

— TAG-SCS-SPECIFICCARRIER-STOP

— ASN1STOP

SCS-SpecificCarrier field descriptions

carrierBandwidth Width of this carrier in number of PRBs (using the subcarrierSpacing defined for this carrier) (see TS 38.211 [16], clause 4.4.2).

offsetToCarrier Offset in frequency domain between Point A (lowest subcarrier of common RB 0) and the lowest usable subcarrier on this carrier in number of PRBs (using the subcarrierSpacing defined for this carrier). The maximum value corresponds to 275*8-1. See TS 38.211 [16], clause 4.4.2.

txDirectCurrentLocation Indicates the downlink Tx Direct Current location for the carrier. A value in the range 0..3299 indicates the subcarrier index within the carrier. The values in the value range 3301..4095 are reserved and ignored by the UE. If this field is absent for downlink within ServingCellConfigCommon and ServingCellConfigCommonSIB, the UE assumes the default value of 3300 (i.e. "Outside the carrier"). (see TS 38.211 [16], clause 4.4.2). Network does not configure this field via ServingCellConfig or for uplink carriers.

subcarrierSpacing Subcarrier spacing of this carrier. It is used to convert the offsetToCarrier into an actual frequency. Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz

– SDAP-Config

The IE SDAP-Config is used to set the configurable SDAP parameters for a data radio bearer. All configured instances of SDAP-Config with the same value of pdu-Session correspond to the same SDAP entity as specified in TS 37.324 [24].

SDAP-Config information element

— ASN1START

— TAG-SDAP-CONFIG-START

SDAP-Config ::= SEQUENCE {

pdu-Session PDU-SessionID,

sdap-HeaderDL ENUMERATED {present, absent},

sdap-HeaderUL ENUMERATED {present, absent},

defaultDRB BOOLEAN,

mappedQoS-FlowsToAdd SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI OPTIONAL, — Need N

mappedQoS-FlowsToRelease SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI OPTIONAL, — Need N

…

}

QFI ::= INTEGER (0..maxQFI)

PDU-SessionID ::= INTEGER (0..255)

— TAG-SDAP-CONFIG-STOP

— ASN1STOP

SDAP-Config field descriptions

defaultDRB Indicates whether or not this is the default DRB for this PDU session. Among all configured instances of SDAP-Config with the same value of pdu-Session, this field shall be set to true in at most one instance of SDAP-Config and to false in all other instances.

mappedQoS-FlowsToAdd Indicates the list of QFIs of UL QoS flows of the PDU session to be additionally mapped to this DRB. A QFI value can be included at most once in all configured instances of SDAP-Config with the same value of pdu-Session. For QoS flow remapping, the QFI value of the remapped QoS flow is only included in mappedQoS-FlowsToAdd in sdap-Config corresponding to the new DRB and not included in mappedQoS-FlowsToRelease in sdap-Config corresponding to the old DRB.

mappedQoS-FlowsToRelease Indicates the list of QFIs of QoS flows of the PDU session to be released from existing QoS flow to DRB mapping of this DRB.

pdu-Session Identity of the PDU session whose QoS flows are mapped to the DRB.

sdap-HeaderUL Indicates whether or not a SDAP header is present for UL data on this DRB. The field cannot be changed after a DRB is established. The network sets this field to present if the field defaultDRB is set to true.

sdap-HeaderDL Indicates whether or not a SDAP header is present for DL data on this DRB. The field cannot be changed after a DRB is established.

– SearchSpace

The IE SearchSpace defines how/where to search for PDCCH candidates. Each search space is associated with one ControlResourceSet. For a scheduled SCell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent (regardless of their presence conditions). For a scheduled SpCell in the case of the cross carrier scheduling, if the search space is linked to another search space in the scheduling SCell, all the optional fields of this search space in the scheduled SpCell are absent (regardless of their presence conditions) except for nrofCandidates.

SearchSpace information element

— ASN1START

— TAG-SEARCHSPACE-START

SearchSpace ::= SEQUENCE {

searchSpaceId SearchSpaceId,

controlResourceSetId ControlResourceSetId OPTIONAL, — Cond SetupOnly

monitoringSlotPeriodicityAndOffset CHOICE {

sl1 NULL,

sl2 INTEGER (0..1),

sl4 INTEGER (0..3),

sl5 INTEGER (0..4),

sl8 INTEGER (0..7),

sl10 INTEGER (0..9),

sl16 INTEGER (0..15),

sl20 INTEGER (0..19),

sl40 INTEGER (0..39),

sl80 INTEGER (0..79),

sl160 INTEGER (0..159),

sl320 INTEGER (0..319),

sl640 INTEGER (0..639),

sl1280 INTEGER (0..1279),

sl2560 INTEGER (0..2559)

} OPTIONAL, — Cond Setup4

duration INTEGER (2..2559) OPTIONAL, — Need S

monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL, — Cond Setup

nrofCandidates SEQUENCE {

aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},

aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},

aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},

aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},

aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}

} OPTIONAL, — Cond Setup

searchSpaceType CHOICE {

common SEQUENCE {

dci-Format0-0-AndFormat1-0 SEQUENCE {

…

} OPTIONAL, — Need R

dci-Format2-0 SEQUENCE {

nrofCandidates-SFI SEQUENCE {

aggregationLevel1 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel2 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel4 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel8 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel16 ENUMERATED {n1, n2} OPTIONAL — Need R

},

…

} OPTIONAL, — Need R

dci-Format2-1 SEQUENCE {

…

} OPTIONAL, — Need R

dci-Format2-2 SEQUENCE {

…

} OPTIONAL, — Need R

dci-Format2-3 SEQUENCE {

dummy1 ENUMERATED {sl1, sl2, sl4, sl5, sl8, sl10, sl16, sl20} OPTIONAL, — Cond Setup

dummy2 ENUMERATED {n1, n2},

…

} OPTIONAL — Need R

},

ue-Specific SEQUENCE {

dci-Formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1},

…,

[[

dci-Formats-MT-r16 ENUMERATED {formats2-5} OPTIONAL, — Need R

dci-FormatsSL-r16 ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1, formats3-0, formats3-1,

formats3-0-And-3-1} OPTIONAL, — Need R

dci-FormatsExt-r16 ENUMERATED {formats0-2-And-1-2, formats0-1-And-1-1And-0-2-And-1-2}

OPTIONAL — Need R

]]

}

} OPTIONAL — Cond Setup2

}

SearchSpaceExt-r16 ::= SEQUENCE {

controlResourceSetId-r16 ControlResourceSetId-r16 OPTIONAL, — Cond SetupOnly2

searchSpaceType-r16 SEQUENCE {

common-r16 SEQUENCE {

dci-Format2-4-r16 SEQUENCE {

nrofCandidates-CI-r16 SEQUENCE {

aggregationLevel1-r16 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel2-r16 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel4-r16 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel8-r16 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel16-r16 ENUMERATED {n1, n2} OPTIONAL — Need R

},

…

} OPTIONAL, — Need R

dci-Format2-5-r16 SEQUENCE {

nrofCandidates-IAB-r16 SEQUENCE {

aggregationLevel1-r16 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel2-r16 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel4-r16 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel8-r16 ENUMERATED {n1, n2} OPTIONAL, — Need R

aggregationLevel16-r16 ENUMERATED {n1, n2} OPTIONAL — Need R

},

…

} OPTIONAL, — Need R

dci-Format2-6-r16 SEQUENCE {

…

} OPTIONAL, — Need R

…

}

} OPTIONAL, — Cond Setup3

searchSpaceGroupIdList-r16 SEQUENCE (SIZE (1.. 2)) OF INTEGER (0..1) OPTIONAL, — Need R

freqMonitorLocations-r16 BIT STRING (SIZE (5)) OPTIONAL — Need R

}

SearchSpaceExt-v1700 ::= SEQUENCE {

monitoringSlotPeriodicityAndOffset-v1710 CHOICE {

sl32 INTEGER (0..31),

sl64 INTEGER (0..63),

sl128 INTEGER (0..127),

sl5120 INTEGER (0..5119),

sl10240 INTEGER (0..10239),

sl20480 INTEGER (0..20479)

} OPTIONAL, — Cond Setup5

monitoringSlotsWithinSlotGroup-r17 CHOICE {

slotGroupLength4-r17 BIT STRING (SIZE (4)),

slotGroupLength8-r17 BIT STRING (SIZE (8))

} OPTIONAL, — Need R

duration-r17 INTEGER (4..20476) OPTIONAL, — Need R

searchSpaceType-r17 SEQUENCE{

common-r17 SEQUENCE {

dci-Format4-0-r17 SEQUENCE {

…

} OPTIONAL, — Need R

dci-Format4-1-r17 SEQUENCE {

…

} OPTIONAL, — Need R

dci-Format4-2-r17 SEQUENCE {

…

} OPTIONAL, — Need R

dci-Format4-1-AndFormat4-2-r17 SEQUENCE {

…

} OPTIONAL, — Need R

dci-Format2-7-r17 SEQUENCE {

nrofCandidates-PEI-r17 SEQUENCE {

aggregationLevel4-r17 ENUMERATED {n0, n1, n2, n3, n4} OPTIONAL, — Need R

aggregationLevel8-r17 ENUMERATED {n0, n1, n2} OPTIONAL, — Need R

aggregationLevel16-r17 ENUMERATED {n0, n1} OPTIONAL — Need R

},

…

} OPTIONAL — Need R

}

} OPTIONAL, — Need R

searchSpaceGroupIdList-r17 SEQUENCE (SIZE (1.. 3)) OF INTEGER (0.. maxNrofSearchSpaceGroups-1-r17) OPTIONAL, — Cond DedicatedOnly

searchSpaceLinkingId-r17 INTEGER (0..maxNrofSearchSpacesLinks-1-r17) OPTIONAL — Cond DedicatedOnly

}

— TAG-SEARCHSPACE-STOP

— ASN1STOP

SearchSpace field descriptions

common Configures this search space as common search space (CSS) and DCI formats to monitor.

controlResourceSetId The CORESET applicable for this SearchSpace. Value 0 identifies the common CORESET#0 configured in MIB and in ServingCellConfigCommon. Values 1..maxNrofControlResourceSets-1 identify CORESETs configured in System Information or by dedicated signalling. The CORESETs with non-zero controlResourceSetId are configured in the same BWP as this SearchSpace except commonControlResourceSetExt which is configured by SIB20. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix).

dummy1, dummy2 This field is not used in the specification. If received it shall be ignored by the UE.

dci-Format0-0-AndFormat1-0 If configured, the UE monitors the DCI formats 0_0 and 1_0 according to TS 38.213 [13], clause 10.1.

dci-Format2-0 If configured, UE monitors the DCI format 2_0 according to TS 38.213 [13], clause 10.1, 11.1.1.

dci-Format2-1 If configured, UE monitors the DCI format 2_1 according to TS 38.213 [13], clause 10.1, 11.2.

dci-Format2-2 If configured, UE monitors the DCI format 2_2 according to TS 38.213 [13], clause 10.1, 11.3.

dci-Format2-3 If configured, UE monitors the DCI format 2_3 according to TS 38.213 [13], clause 10.1, 11.4

dci-Format2-4 If configured, UE monitors the DCI format 2_4 according to TS 38.213 [13], clause 11.2A.

dci-Format2-5 If configured, IAB-MT monitors the DCI format 2_5 according to TS 38.213 [13], clause 14.

dci-Format2-6 If configured, UE monitors the DCI format 2_6 according to TS 38.213 [13], clause 10.1, 10.3. DCI format 2_6 can only be configured on the SpCell.

dci-Format2-7 If configured, UE monitors the DCI format 2_7 according to TS 38.213 [13], clause 10.1, 10.4A.

dci-Format4-0 If configured, the UE monitors the DCI format 4_0 with CRC scrambled by MCCH-RNTI/G-RNTI according to TS 38.213 [13], clause [10.1].

dci-Format4-1-AndFormat4-2 If configured, the UE monitors the DCI format 4_1 and 4_2 with CRC scrambled by G-RNTI/G-CS-RNTI according to TS 38.213 [13], clause [11.1].

dci-Format4-1 If configured, the UE monitors the DCI format 4_1 with CRC scrambled by G-RNTI/G-CS-RNTI according to TS 38.213 [13], clause [10.1].

dci-Format4-2 If configured, the UE monitors the DCI format 4_2 with CRC scrambled by G-RNTI/G-CS-RNTI according to TS 38.213 [13], clause [10.1].

dci-Formats Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.

dci-FormatsExt If this field is present, the field dci-Formats is ignored and dci-FormatsExt is used instead to indicate whether the UE monitors in this USS for DCI format 0_2 and 1_2 or formats 0_1 and 1_1 and 0_2 and 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 10.1). This field is not configured for operation with shared spectrum channel access in this release.

dci-Formats-MT Indicates whether the IAB-MT monitors the DCI formats 2-5 according to TS 38.213 [13], clause 14.

dci-FormatsSL Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1 or for format 3-0 or for format 3-1 or for formats 3-0 and 3-1. If this field is present, the field dci-Formats is ignored and dci-FormatsSL is used.

duration Number of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset. If the field is absent, the UE applies the value 1 slot, except for DCI format 2_0. The UE ignores this field for DCI format 2_0. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset). For SCS 480 kHz and SCS 960 kHz, duration-r17 is used, and the configured duration is restricted to be an integer multiple of L slots and smaller than periodicity, where L is the configured length of the bitmap monitoringSlotsWithinSlotGroup-r17. If duration-r17 is absent, the UE assumes the duration in slots is equal to L. The maximum valid duration is periodicity-L. For IAB-MT, duration indicates number of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset. If the field is absent, the IAB-MT applies the value 1 slot, except for DCI format 2_0 and DCI format 2_5. The IAB-MT ignores this field for DCI format 2_0 and DCI format 2_5. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset).

freqMonitorLocations Defines an association of the search space to multiple monitoring locations in the frequency domain and indicates whether the pattern configured in the associated CORESET is replicated to a specific RB set, see TS 38.213, clause 10.1. Each bit in the bitmap corresponds to one RB set, and the leftmost (most significant) bit corresponds to RB set 0 in the BWP. A bit set to 1 indicates that a frequency domain resource allocation replicated from the pattern configured in the associated CORESET is mapped to the RB set.

monitoringSlotPeriodicityAndOffset Slots for PDCCH Monitoring configured as periodicity and offset. For SCS 15, 30, 60, and 120 kHz and if the UE is configured to monitor: – DCI format 2_1, only the values ‘sl1’, ‘sl2’ or ‘sl4’ are applicable. – DCI format 2_0, only the values ′sl1′, ′sl2′, ′sl4′, ′sl5′, ′sl8′, ′sl10′, ′sl16′, and ′sl20′ are applicable (see TS 38.213 [13], clause 10). – DCI format 2_4, only the values ‘sl1’, ‘sl2’, ‘sl4’, ‘sl5’, ‘sl8’ and ‘sl10’ are applicable. For SCS 480 kHz and if the UE is configured to monitor: – DCI format 2_0, only the values ‘sl4’, ‘sl8’, ‘sl16’, ‘sl20’, ‘sl32’, ‘sl40’, ‘sl64’, and ‘sl80’ are applicable. – DCI format 2_1, only the values ′sl4′, ′sl8′, and ′sl16′ are applicable. – DCI format 2_4, only the values ‘sl4’, ‘sl8’, ‘sl16’, ‘sl20’, ‘sl32’, ‘sl40’ are applicable. For SCS 960 kHz and if the UE is configured to monitor: – DCI format 2_0, only the values ‘sl4’, ‘sl8’, ‘sl16’, ‘sl20’, ‘sl32’, ‘sl40’, ‘sl64’, and ‘sl80’ are applicable. – DCI format 2_1, only the values ′sl4′, ′sl8′, and ′sl16′ are applicable. – DCI format 2_4, only the values ‘sl8’, ‘sl16’, ‘sl32’, ‘sl40’, ‘sl64’, ‘sl80’ are applicable. For SCS 480 kHz and SCS 960 kHz, and the configured periodicity and offset are restricted to be an integer multiple of L slots, where L is the configured length of the bitmap provided by monitoringSlotsWithinSlotGroup-r17, i.e. for a given periodicity, the offset has a range of {0, L, 2*L, …, L*FLOOR(1/L*(periodicity-1))}. For IAB-MT, If the IAB-MT is configured to monitor DCI format 2_1, only the values ‘sl1’, ‘sl2’ or ‘sl4’ are applicable. If the IAB-MT is configured to monitor DCI format 2_0 or DCI format 2_5, only the values ′sl1′, ′sl2′, ′sl4′, ′sl5′, ′sl8′, ′sl10′, ′sl16′, and ′sl20′ are applicable (see TS 38.213, clause 10). If monitoringSlotPeriodicityAndOffset-r17 is present, any previously configured monitoringSlotPeriodicityAndOffset is released, and if monitoringSlotPeriodicityAndOffset is present, any previously configured monitoringSlotPeriodicityAndOffset-r17 is released.

monitoringSlotsWithinSlotGroup Indicates which slot(s) within a slot group are configured for multi-slot PDCCH monitoring. The first (leftmost, most significant) bit represents the first slot in the slot group, the second bit represents the second slot in the slot group, and so on. A bit set to ‘1’ indicates that the corresponding slot is configured for multi-slot PDCCH monitoring (see TS 38.213 [13], clause 10). The number of slots for multi-slot PDCCH monitoring is configured according to clause 10 in TS 38.213 [13].

monitoringSymbolsWithinSlot The first symbol(s) for PDCCH monitoring in the slots configured for (multi-slot) PDCCH monitoring (see monitoringSlotPeriodicityAndOffset and duration). The most significant (left) bit represents the first OFDM in a slot, and the second most significant (left) bit represents the second OFDM symbol in a slot and so on. The bit(s) set to one identify the first OFDM symbol(s) of the control resource set within a slot. If the cyclic prefix of the BWP is set to extended CP, the last two bits within the bit string shall be ignored by the UE or IAB-MT. For DCI format 2_0, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol. See TS 38.213 [13], clause 10. For IAB-MT: For DCI format 2_0 or DCI format 2_5, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol. See TS 38.213 [13], clause 10.

nrofCandidates-CI The number of PDCCH candidates specifically for format 2-4 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see TS 38.213 [13], clause 10.1).

nrofCandidates-PEI The number of PDCCH candidates specifically for format 2-7 for the configured aggregation level.

nrofCandidates-SFI The number of PDCCH candidates specifically for format 2-0 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see TS 38.213 [13], clause 11.1.1). For a search space configured with freqMonitorLocations-r16, only value ′n1′ is valid.

nrofCandidates Number of PDCCH candidates per aggregation level. The number of candidates and aggregation levels configured here applies to all formats unless a particular value is specified or a format-specific value is provided (see inside searchSpaceType). If configured in the SearchSpace of a cross carrier scheduled cell, this field determines the number of candidates and aggregation levels to be used on the linked scheduling cell (see TS 38.213 [13], clause 10).

searchSpaceGroupIdList-r16, searchSpaceGroupIdList-r17 List of search space group IDs which the search space is associated with. The network configures at most 2 search space groups per BWP where the group ID is either 0 or 1 if searchSpaceGroupIdList-r16 is included. The network configures at most 3 search space groups per BWP where the group ID is either 0, 1 or 2 if searchSpaceGroupIdList-r17 is included. And if searchSpaceGroupIdList-r17 is included, searchSpaceGroupIdList-r16 is ignored.

searchSpaceId Identity of the search space. SearchSpaceId = 0 identifies the searchSpaceZero configured via PBCH (MIB) or ServingCellConfigCommon and may hence not be used in the SearchSpace IE. The searchSpaceId is unique among the BWPs of a Serving Cell. In case of cross carrier scheduling, search spaces with the same searchSpaceId in scheduled cell and scheduling cell are linked to each other. The UE applies the search space for the scheduled cell only if the DL BWPs in which the linked search spaces are configured in scheduling cell and scheduled cell are both active. For an IAB-MT, the search space defines how/where to search for PDCCH candidates for an IAB-MT where each search space is associated with one ControlResearchSet and for a scheduled cell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent.

SearchSpaceLinkingId This parameter is used to link two search spaces of same type in the same BWP. If two search spaces have the same SearchSpaceLinkingId UE assumes these search spaces are linked to PDCCH repetition REF. When PDCCH repetition is monitored in two linked search space (SS) sets, the UE does not expect a third monitored SS set to be linked with any of the two linked SS sets. The two linked SS sets have the same SS set type (USS/CSS). The two linked SS sets have the same DCI formats to monitor. For intra-slot PDCCH repetition: The two SS sets should have the same periodicity and offset (monitoringSlotPeriodicityAndOffset), and the same duration. For linking monitoring occasions across the two SS sets that exist in the same slot: The two SS sets have the same number of monitoring occasions within a slot and n-th monitoring occasion of one SS set is linked to n-th monitoring occasion of the other SS set. The following SS sets cannot be linked with another SS set for PDCCH repetition: SS set 0, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, searchSpaceBroadcast, peiSearchSpace, and sdt-SearchSpace. SS set configured by recoverySearchSpaceId cannot be linked to another SS set for PDCCH repetition. When a scheduled serving cell is configured to be cross-carrier scheduled by a scheduling serving cell, two PDCCH candidates (with the same AL and candidate index associated with the scheduled serving cell) are linked only if the corresponding two SS sets in the scheduling serving cell are linked and two SS sets in the scheduled serving cell with the same SS set IDs are also linked.

searchSpaceType Indicates whether this is a common search space (present) or a UE specific search space as well as DCI formats to monitor for.

ue-Specific Configures this search space as UE specific search space (USS). The UE monitors the DCI format with CRC scrambled by C-RNTI, CS-RNTI (if configured), and SP-CSI-RNTI (if configured)

Conditional Presence	Explanation
DedicatedOnly	In PDCCH-Config, the field is optionally present, Need R. Otherwise it is absent, Need R.
Setup	This field is mandatory present upon creation of a new SearchSpace. It is optionally present, Need M, otherwise.
Setup2	This field is mandatory present when a new SearchSpace is set up, if the same SearchSpace ID is not included in searchSpacesToAddModListExt-r16 of the parent IE with the field searchSpaceType-r16 or searchSpaceType-r17 included. Otherwise it is optionally present, Need M.
Setup3	This field is mandatory present when a new SearchSpace is set up, if the same SearchSpace ID is not included in searchSpacesToAddModListExt (without suffix) of the parent IE with the field searchSpaceType (without suffix) included. Otherwise it is optionally present, Need M.
Setup4	This field is mandatory present upon creation of a new SearchSpace if monitoringSlotPeriodicityAndOffset-r17 is not included. It is optionally present, Need M, otherwise.
Setup5	This field is mandatory present upon creation of a new SearchSpace if monitoringSlotPeriodicityAndOffset (without suffix) is not included. It is optionally present, Need M, otherwise.
SetupOnly	This field is mandatory present upon creation of a new SearchSpace. It is absent, Need M, otherwise.
SetupOnly2	In PDCCH-Config, the field is optionally present upon creation of a new SearchSpace and absent, Need M upon reconfiguration of an existing SearchSpace. In PDCCH-ConfigCommon, the field is absent.

– SearchSpaceId

The IE SearchSpaceId is used to identify Search Spaces. The ID space is used across the BWPs of a Serving Cell. The search space with the SearchSpaceId = 0 identifies the search space configured via PBCH (MIB) and in ServingCellConfigCommon (searchSpaceZero). The number of Search Spaces per BWP is limited to 10 including the common and UE specific Search Spaces.

SearchSpaceId information element

— ASN1START

— TAG-SEARCHSPACEID-START

SearchSpaceId ::= INTEGER (0..maxNrofSearchSpaces-1)

— TAG-SEARCHSPACEID-STOP

— ASN1STOP

– SearchSpaceZero

The IE SearchSpaceZero is used to configure SearchSpace#0 of the initial BWP (see TS 38.213 [13], clause 13).

SearchSpaceZero information element

— ASN1START

— TAG-SEARCHSPACEZERO-START

SearchSpaceZero ::= INTEGER (0..15)

— TAG-SEARCHSPACEZERO-STOP

— ASN1STOP

– SecurityAlgorithmConfig

The IE SecurityAlgorithmConfig is used to configure AS integrity protection algorithm and AS ciphering algorithm for SRBs and DRBs.

SecurityAlgorithmConfig information element

— ASN1START

— TAG-SECURITYALGORITHMCONFIG-START

SecurityAlgorithmConfig ::= SEQUENCE {

cipheringAlgorithm CipheringAlgorithm,

integrityProtAlgorithm IntegrityProtAlgorithm OPTIONAL, — Need R

…

}

IntegrityProtAlgorithm ::= ENUMERATED {

nia0, nia1, nia2, nia3, spare4, spare3,

spare2, spare1, …}

CipheringAlgorithm ::= ENUMERATED {

nea0, nea1, nea2, nea3, spare4, spare3,

spare2, spare1, …}

— TAG-SECURITYALGORITHMCONFIG-STOP

— ASN1STOP

SecurityAlgorithmConfig field descriptions
cipheringAlgorithm Indicates the ciphering algorithm to be used for SRBs and DRBs, as specified in TS 33.501 [11]. The algorithms nea0–nea3 are identical to the LTE algorithms eea0-3. The algorithms configured for all bearers using master key shall be the same, and the algorithms configured for all bearers using secondary key, if any, shall be the same. If UE is connected to E-UTRA/EPC, this field indicates the ciphering algorithm to be used for RBs configured with NR PDCP, as specified in TS 33.501 [11].
integrityProtAlgorithm Indicates the integrity protection algorithm to be used for SRBs and DRBs, as specified in TS 33.501 [11]. The algorithms nia0-nia3 are identical to the E-UTRA algorithms eia0-3. The algorithms configured for all bearers using master key shall be the same and the algorithms configured for all bearers using secondary key, if any, shall be the same. The network does not configure nia0 except for unauthenticated emergency sessions for unauthenticated UEs in LSM (limited service mode). If UE is connected to E-UTRA/EPC, this field indicates the integrity protection algorithm to be used for SRBs configured with NR PDCP as specified in TS 33.501 [11], and DRBs configured with integrity protection as specified in TS 33.401 [30]. The network does not configure nia0 for SRB3.

– SemiStaticChannelAccessConfig

The IE SemiStaticChannelAccessConfig is used to configure channel access parameters when the network is operating in semi-static channel access mode (see clause 4.3 TS 37.213 [48].

SemiStaticChannelAccessConfig information element

— ASN1START

— TAG-SEMISTATICCHANNELACCESSCONFIG-START

SemiStaticChannelAccessConfig-r16 ::= SEQUENCE {

period ENUMERATED {ms1, ms2, ms2dot5, ms4, ms5, ms10}

}

— TAG-SEMISTATICCHANNELACCESSCONFIG-STOP

— ASN1STOP

SemiStaticChannelAccessConfig field descriptions

period Indicates the periodicity of the semi-static channel access mode (see TS 37.213 [48], clause 4.3). Value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, value ms2dot5 corresponds to 2.5 ms, and so on.

– SemiStaticChannelAccessConfigUE

The IE SemiStaticChannelAccessConfigUE is used to configure channel access parameters for UE initiated semi-static channel access.

SemiStaticChannelAccessConfigUE information element

— ASN1START

— TAG-SEMISTATICCHANNELACCESSCONFIGUE-START

SemiStaticChannelAccessConfigUE-r17 ::= SEQUENCE {

periodUE-r17 ENUMERATED {ms1, ms2, ms2dot5, ms4, ms5, ms10, spare2, spare1},

offsetUE-r17 INTEGER (0..559)

}

— TAG-SEMISTATICCHANNELACCESSCONFIGUE-STOP

— ASN1STOP

SemiStaticChannelAccessConfigUE field descriptions

periodUE Indicates the period of a channel occupancy that the UE can initiate as described in TS 37.213 [48], clause 4.3. Value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, value ms2dot5 corresponds to 2.5 ms, and so on.

offsetUE Indicates the number of symbols from the beginning of the even indexed radio frame to the start of the first period within that radio frame that the UE can initiate a channel occupancy (see TS 37.213 [48], clause 4.3), based on the smallest SCS among the configured SCSs in the serving cell. The offset duration indicated by this field is less than the period duration indicated by periodUE. The maximum value is 139, 279 and 559 for 15, 30 and 60 kHz subcarrier spacing, respectively.

– Sensor-LocationInfo

The IE Sensor-LocationInfo is used by the UE to provide sensor information.

Sensor-LocationInfo information element

— ASN1START

— TAG-SENSORLOCATIONINFO-START

Sensor-LocationInfo-r16 ::= SEQUENCE {

sensor-MeasurementInformation-r16 OCTET STRING OPTIONAL,

sensor-MotionInformation-r16 OCTET STRING OPTIONAL,

…

}

— TAG-SENSORLOCATIONINFO-STOP

— ASN1STOP

Sensor-LocationInfo field descriptions

sensor-MeasurementInformation This field provides barometric pressure measurements as Sensor-MeasurementInformation defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.

sensor-MotionInformation This field provides motion sensor measurements as Sensor-MotionInformation defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.

– ServingCellAndBWP-Id

The IE ServingCellAndBWP-Id is used to indicate a serving cell and an uplink or a downlink BWP.

ServingCellAndBWP-Id information element

— ASN1START

— TAG-SERVINGCELLANDBWP-ID-START

ServingCellAndBWP-Id-r17 ::= SEQUENCE {

servingcell-r17 ServCellIndex,

bwp-r17 BWP-Id

}

— TAG-SERVINGCELLANDBWP-ID-STOP

— ASN1STOP

– ServCellIndex

The IE ServCellIndex concerns a short identity, used to uniquely identify a serving cell (i.e. the PCell, the PSCell or an SCell) across the cell groups. Value 0 applies for the PCell, while the SCellIndex that has previously been assigned applies for SCells.

ServCellIndex information element

— ASN1START

— TAG-SERVCELLINDEX-START

ServCellIndex ::= INTEGER (0..maxNrofServingCells-1)

— TAG-SERVCELLINDEX-STOP

— ASN1STOP

– ServingCellConfig

The IE ServingCellConfig is used to configure (add or modify) the UE with a serving cell, which may be the SpCell or an SCell of an MCG or SCG. The parameters herein are mostly UE specific but partly also cell specific (e.g. in additionally configured bandwidth parts). Reconfiguration between a PUCCH and PUCCHless SCell is only supported using an SCell release and add.

ServingCellConfig information element

— ASN1START

— TAG-SERVINGCELLCONFIG-START

ServingCellConfig ::= SEQUENCE {

tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated OPTIONAL, — Cond TDD

initialDownlinkBWP BWP-DownlinkDedicated OPTIONAL, — Need M

downlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, — Need N

downlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink OPTIONAL, — Need N

firstActiveDownlinkBWP-Id BWP-Id OPTIONAL, — Cond SyncAndCellAdd

bwp-InactivityTimer ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30,

ms40,ms50, ms60, ms80,ms100, ms200,ms300, ms500,

ms750, ms1280, ms1920, ms2560, spare10, spare9, spare8,

spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, –Need R

defaultDownlinkBWP-Id BWP-Id OPTIONAL, — Need S

uplinkConfig UplinkConfig OPTIONAL, — Need M

supplementaryUplink UplinkConfig OPTIONAL, — Need M

pdcch-ServingCellConfig SetupRelease { PDCCH-ServingCellConfig } OPTIONAL, — Need M

pdsch-ServingCellConfig SetupRelease { PDSCH-ServingCellConfig } OPTIONAL, — Need M

csi-MeasConfig SetupRelease { CSI-MeasConfig } OPTIONAL, — Need M

sCellDeactivationTimer ENUMERATED {ms20, ms40, ms80, ms160, ms200, ms240,

ms320, ms400, ms480, ms520, ms640, ms720,

ms840, ms1280, spare2,spare1} OPTIONAL, — Cond ServingCellWithoutPUCCH

crossCarrierSchedulingConfig CrossCarrierSchedulingConfig OPTIONAL, — Need M

tag-Id TAG-Id,

dummy1 ENUMERATED {enabled} OPTIONAL, — Need R

pathlossReferenceLinking ENUMERATED {spCell, sCell} OPTIONAL, — Cond SCellOnly

servingCellMO MeasObjectId OPTIONAL, — Cond MeasObject

…,

[[

lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, — Need M

rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, — Need N

rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, — Need N

downlinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL — Need S

]],

[[

supplementaryUplinkRelease-r16 ENUMERATED {true} OPTIONAL, — Need N

tdd-UL-DL-ConfigurationDedicated-IAB-MT-r16 TDD-UL-DL-ConfigDedicated-IAB-MT-r16 OPTIONAL, — Cond TDD_IAB

dormantBWP-Config-r16 SetupRelease { DormantBWP-Config-r16 } OPTIONAL, — Need M

ca-SlotOffset-r16 CHOICE {

refSCS15kHz INTEGER (-2..2),

refSCS30KHz INTEGER (-5..5),

refSCS60KHz INTEGER (-10..10),

refSCS120KHz INTEGER (-20..20)

} OPTIONAL, — Cond AsyncCA

dummy2 SetupRelease { DummyJ } OPTIONAL, — Need M

intraCellGuardBandsDL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, — Need S

intraCellGuardBandsUL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, — Need S

csi-RS-ValidationWithDCI-r16 ENUMERATED {enabled} OPTIONAL, — Need R

lte-CRS-PatternList1-r16 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, — Need M

lte-CRS-PatternList2-r16 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, — Need M

crs-RateMatch-PerCORESETPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, — Need R

enableTwoDefaultTCI-States-r16 ENUMERATED {enabled} OPTIONAL, — Need R

enableDefaultTCI-StatePerCoresetPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, — Need R

enableBeamSwitchTiming-r16 ENUMERATED {true} OPTIONAL, — Need R

cbg-TxDiffTBsProcessingType1-r16 ENUMERATED {enabled} OPTIONAL, — Need R

cbg-TxDiffTBsProcessingType2-r16 ENUMERATED {enabled} OPTIONAL — Need R

]],

[[

directionalCollisionHandling-r16 ENUMERATED {enabled} OPTIONAL, — Need R

channelAccessConfig-r16 SetupRelease { ChannelAccessConfig-r16 } OPTIONAL — Need M

]],

[[

nr-dl-PRS-PDC-Info-r17 SetupRelease {NR-DL-PRS-PDC-Info-r17} OPTIONAL, — Need M

semiStaticChannelAccessConfigUE-r17 SetupRelease {SemiStaticChannelAccessConfigUE-r17} OPTIONAL, — Need M

mimoParam-r17 SetupRelease {MIMOParam-r17} OPTIONAL, — Need M

channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, — Need R

timeDomainHARQ-BundlingType1-r17 ENUMERATED {enabled} OPTIONAL, — Need R

nrofHARQ-BundlingGroups-r17 ENUMERATED {n1, n2, n4} OPTIONAL, — Need R

fdmed-ReceptionMulticast-r17 ENUMERATED {true} OPTIONAL, — Need R

moreThanOneNackOnlyMode-r17 ENUMERATED {mode2} OPTIONAL, — Need S

tci-ActivatedConfig-r17 TCI-ActivatedConfig-r17 OPTIONAL, — Cond TCI_ActivatedConfig

directionalCollisionHandling-DC-r17 ENUMERATED {enabled} OPTIONAL, — Need R

lte-NeighCellsCRS-AssistInfoList-r17 SetupRelease { LTE-NeighCellsCRS-AssistInfoList-r17 } OPTIONAL — Need M

]],

[[

lte-NeighCellsCRS-Assumptions-r17 ENUMERATED {false} OPTIONAL — Need R

]]

}

UplinkConfig ::= SEQUENCE {

initialUplinkBWP BWP-UplinkDedicated OPTIONAL, — Need M

uplinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, — Need N

uplinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Uplink OPTIONAL, — Need N

firstActiveUplinkBWP-Id BWP-Id OPTIONAL, — Cond SyncAndCellAdd

pusch-ServingCellConfig SetupRelease { PUSCH-ServingCellConfig } OPTIONAL, — Need M

carrierSwitching SetupRelease { SRS-CarrierSwitching } OPTIONAL, — Need M

…,

[[

powerBoostPi2BPSK BOOLEAN OPTIONAL, — Need M

uplinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL — Need S

]],

[[

enablePL-RS-UpdateForPUSCH-SRS-r16 ENUMERATED {enabled} OPTIONAL, — Need R

enableDefaultBeamPL-ForPUSCH0-0-r16 ENUMERATED {enabled} OPTIONAL, — Need R

enableDefaultBeamPL-ForPUCCH-r16 ENUMERATED {enabled} OPTIONAL, — Need R

enableDefaultBeamPL-ForSRS-r16 ENUMERATED {enabled} OPTIONAL, — Need R

uplinkTxSwitching-r16 SetupRelease { UplinkTxSwitching-r16 } OPTIONAL, — Need M

mpr-PowerBoost-FR2-r16 ENUMERATED {true} OPTIONAL — Need R

]]

}

DummyJ ::= SEQUENCE {

maxEnergyDetectionThreshold-r16 INTEGER(-85..-52),

energyDetectionThresholdOffset-r16 INTEGER (-20..-13),

ul-toDL-COT-SharingED-Threshold-r16 INTEGER (-85..-52) OPTIONAL, — Need R

absenceOfAnyOtherTechnology-r16 ENUMERATED {true} OPTIONAL — Need R

}

ChannelAccessConfig-r16 ::= SEQUENCE {

energyDetectionConfig-r16 CHOICE {

maxEnergyDetectionThreshold-r16 INTEGER (-85..-52),

energyDetectionThresholdOffset-r16 INTEGER (-13..20)

} OPTIONAL, — Need R

ul-toDL-COT-SharingED-Threshold-r16 INTEGER (-85..-52) OPTIONAL, — Need R

absenceOfAnyOtherTechnology-r16 ENUMERATED {true} OPTIONAL — Need R

}

IntraCellGuardBandsPerSCS-r16 ::= SEQUENCE {

guardBandSCS-r16 SubcarrierSpacing,

intraCellGuardBands-r16 SEQUENCE (SIZE (1..4)) OF GuardBand-r16

}

GuardBand-r16 ::= SEQUENCE {

startCRB-r16 INTEGER (0..274),

nrofCRBs-r16 INTEGER (0..15)

}

DormancyGroupID-r16 ::= INTEGER (0..4)

DormantBWP-Config-r16::= SEQUENCE {

dormantBWP-Id-r16 BWP-Id OPTIONAL, — Need M

withinActiveTimeConfig-r16 SetupRelease { WithinActiveTimeConfig-r16 } OPTIONAL, — Need M

outsideActiveTimeConfig-r16 SetupRelease { OutsideActiveTimeConfig-r16 } OPTIONAL — Need M

}

WithinActiveTimeConfig-r16 ::= SEQUENCE {

firstWithinActiveTimeBWP-Id-r16 BWP-Id OPTIONAL, — Need M

dormancyGroupWithinActiveTime-r16 DormancyGroupID-r16 OPTIONAL — Need R

}

OutsideActiveTimeConfig-r16 ::= SEQUENCE {

firstOutsideActiveTimeBWP-Id-r16 BWP-Id OPTIONAL, — Need M

dormancyGroupOutsideActiveTime-r16 DormancyGroupID-r16 OPTIONAL — Need R

}

UplinkTxSwitching-r16 ::= SEQUENCE {

uplinkTxSwitchingPeriodLocation-r16 BOOLEAN,

uplinkTxSwitchingCarrier-r16 ENUMERATED {carrier1, carrier2}

}

MIMOParam-r17 ::= SEQUENCE {

additionalPCI-ToAddModList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17 OPTIONAL, — Need N

additionalPCI-ToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF AdditionalPCIIndex-r17 OPTIONAL, — Need N

unifiedTCI-StateType-r17 ENUMERATED {separate, joint} OPTIONAL, — Need R

uplink-PowerControlToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF Uplink-powerControl-r17 OPTIONAL, — Need N

uplink-PowerControlToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF Uplink-powerControlId-r17 OPTIONAL, — Need N

sfnSchemePDCCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL, — Need R

sfnSchemePDSCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL — Need R

}

— TAG-SERVINGCELLCONFIG-STOP

— ASN1STOP

ChannelAccessConfig field descriptions

absenceOfAnyOtherTechnology Presence of this field indicates absence on a long term basis (e.g. by level of regulation) of any other technology sharing the carrier; absence of this field indicates the potential presence of any other technology sharing the carrier, as specified in TS 37.213 [48] clauses 4.2.1 and 4.2.3.

energyDetectionConfig Indicates whether to use the maxEnergyDetectionThreshold or the energyDetectionThresholdOffset (see TS 37.213 [48], clause 4.2.3).

energyDetectionThresholdOffset Indicates the offset to the default maximum energy detection threshold value. Unit in dB. Value -13 corresponds to -13dB, value -12 corresponds to -12dB, and so on (i.e. in steps of 1dB) as specified in TS 37.213 [48], clause 4.2.3.

maxEnergyDetectionThreshold Indicates the absolute maximum energy detection threshold value. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm) as specified in TS 37.213 [48], clause 4.2.3.

ul-toDL-COT-SharingED-Threshold Maximum energy detection threshold that the UE should use to share channel occupancy with gNB for DL transmission as specified in TS 37.213 [48], clause 4.1.3 for downlink channel access and clause 4.2.3 for uplink channel access. This field is not applicable in semi-static channel access mode.

ServingCellConfig field descriptions

additionalPCI-ToAddModList List of information for the additional SSB with different PCI than the serving cell PCI. The additional SSBs with different PCIs are not used for measurement event evaluation.

bwp-InactivityTimer The duration in ms after which the UE falls back to the default Bandwidth Part (see TS 38.321 [3], clause 5.15). When the network releases the timer configuration, the UE stops the timer without switching to the default BWP.

ca-SlotOffset Slot offset between the primary cell (PCell/PSCell) and the SCell in unaligned frame boundary with slot alignment and partial SFN alignment inter-band CA. Based on this field, the UE determines the time offset of the SCell as specified in clause 4.5 of TS 38.211 [16]. The granularity of this field is determined by the reference SCS for the slot offset (i.e. the maximum of PCell/PSCell lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB and this serving cell’s lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB). The Network configures at most single non-zero offset duration in ms (independent on SCS) among CCs in the unaligned CA configuration. If the field is absent, the UE applies the value of 0. The slot offset value can only be changed with SCell release and add.

cbg-TxDiffTBsProcessingType1, cbg-TxDiffTBsProcessingType2 Indicates whether processing types 1 and 2 based CBG based operation is enabled according to Rel-16 UE capabilities.

channelAccessConfig List of parameters used for access procedures of operation with shared spectrum channel access (see TS 37.213 [48).

channelAccessMode2 If present, this field indicates that the UE shall apply channel access mode procedures for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4 for FR2-2. If absent, the UE does not apply these channel access procedures. Overwrites the corresponding field in ServingCellConfigCommon or ServingCellConfigCommonSIB for this serving cell.

crossCarrierSchedulingConfig Indicates whether this serving cell is cross-carrier scheduled by another serving cell or whether it cross-carrier schedules another serving cell. If the field other is configured for an SpCell (i.e., the SpCell is cross-carrier scheduled by another serving cell), the SpCell can be additionally scheduled by the PDCCH on the SpCell.

crs-RateMatch-PerCORESETPoolIndex Indicates how UE performs rate matching when both lte-CRS-PatternList1-r16 and lte-CRS-PatternList2-r16 are configured as specified in TS 38.214 [19], clause 5.1.4.2.

csi-RS-ValidationWithDCI Indicates how the UE performs periodic and semi-persistent CSI-RS reception in a slot. The presence of this field indicates that the UE uses DCI detection to validate whether to receive CSI-RS (see TS 38.213 [13], clause 11.1).

defaultDownlinkBWP-Id The initial bandwidth part is referred to by BWP-Id = 0. ID of the downlink bandwidth part to be used upon expiry of the BWP inactivity timer. This field is UE specific. When the field is absent the UE uses the initial BWP as default BWP. (see TS 38.213 [13], clause 12 and TS 38.321 [3], clause 5.15).

directionalCollisionHandling Indicates that this serving cell is using directional collision handling between a reference and other cell(s) for half-duplex operation in TDD CA with same SCS as specified in TS 38.213 [13], clause 11.1. The half-duplex operation only applies within the same frequency range and cell group. The network only configures this field for TDD serving cells that are using the same SCS.

directionalCollisionHandling-DC For the IAB-MT, it indicates that this serving cell is using directional collision handling between a reference and other cell(s) for half-duplex operation in TDD NR-DC with same SCS within same cell group or cross different cell groups.

dormantBWP-Config The dormant BWP configuration for an SCell. This field can be configured only for a (non-PUCCH) SCell.

downlinkBWP-ToAddModList List of additional downlink bandwidth parts to be added or modified. (see TS 38.213 [13], clause 12).

downlinkBWP-ToReleaseList List of additional downlink bandwidth parts to be released. (see TS 38.213 [13], clause 12).

downlinkChannelBW-PerSCS-List A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in DownlinkConfigCommon / DownlinkConfigCommonSIB. Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1 [15] and TS 38.101-2 [39].

dummy1, dummy 2 This field is not used in the specification. If received it shall be ignored by the UE.

enableBeamSwitchTiming Indicates the aperiodic CSI-RS triggering with beam switching triggering behaviour as defined in clause 5.2.1.5.1 of TS 38.214 [19].

enableDefaultTCI-StatePerCoresetPoolIndex Presence of this field indicates the UE shall follow the release 16 behavior of default TCI state per CORESETPoolindex when the UE is configured by higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in ControlResourceSet is enabled.

enableTwoDefaultTCI-States Presence of this field indicates the UE shall follow the release 16 behavior of two default TCI states for PDSCH when at least one TCI codepoint is mapped to two TCI states is enabled

fdmed-ReceptionMulticast Indicates the Type-1 HARQ codebook generation as specified in TS 38.213 [13], clause 9.1.2.1.

firstActiveDownlinkBWP-Id If configured for an SpCell, this field contains the ID of the DL BWP to be activated or to be used for RLM, BFD and measurements if included in an RRCReconfiguration message contained in an NR or E-UTRA RRC message indicating that the SCG is deactivated, upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch. If the field is absent for the PSCell at SCG deactivation, the UE considers the previously activated DL BWP as the BWP to be used for RLM, BFD and measurements. If the field is absent for the PSCell at SCG activation, the DL BWP to be activated is the DL BWP previously to be used for RLM, BFD and measurements. If configured for an SCell, this field contains the ID of the downlink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BWP-Id = 0. Upon reconfiguration with reconfigurationWithSync, the network sets the firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id to the same value.

initialDownlinkBWP The dedicated (UE-specific) configuration for the initial downlink bandwidth-part (i.e., DL BWP#0). If any of the optional IEs are configured within this IE, the UE considers the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1

intraCellGuardBandsDL-List, intraCellGuardBandsUL-List List of intra-cell guard bands in a serving cell for operation with shared spectrum channel access. If not configured, the guard bands are defined according to 38.101-1 [15], see TS 38.214 [19], clause 7. For operation in licensed spectrum, this field is absent, and no UE action is required.

lte-CRS-PatternList1 A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH. The LTE CRS patterns in this list shall be non-overlapping in frequency. The network does not configure this field and lte-CRS-ToMatchAround simultaneously.

lte-CRS-PatternList2 A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH scheduled with a DCI detected on a CORESET with CORESETPoolIndex configured with 1. This list is configured only if CORESETPoolIndex configured with 1. The first LTE CRS pattern in this list shall be fully overlapping in frequency with the first LTE CRS pattern in lte-CRS-PatternList1, The second LTE CRS pattern in this list shall be fully overlapping in frequency with the second LTE CRS pattern in lte-CRS-PatternList1, and so on. Network configures this field only if the field lte-CRS-ToMatchAround is not configured and there is at least one ControlResourceSet in one DL BWP of this serving cell with coresetPoolIndex set to 1.

lte-CRS-ToMatchAround Parameters to determine an LTE CRS pattern that the UE shall rate match around.

lte-NeighCellsCRS-AssistInfoList A list of LTE neighbour cells configuration information which is used to assist the UE to perform CRS interference mitigation (CRS-IM) in scenarios with overlapping spectrum for LTE and NR (see TS 38.101-4 [59]). If the field is included, it replaces any previous list, i.e. all the entries of the list are replaced and each of the LTE-NeighCellsCRS-AssistInfo entries is considered to be newly created and the conditions and Need codes for setup of the entry apply.

lte-NeighCellsCRS-Assumptions If the field is not configured, the following default network configuration assumptions are valid for all LTE neighbour cells for the purpose of CRS interference mitigation (CRS-IM) in scenarios with overlapping spectrum for LTE and NR (see TS 38.101-4 [59]). – The CRS port number is the same as the one indicated in RateMatchPatternLTE-CRS if configured for the serving cell. – The CRS port number is 4 if RateMatchPatternLTE-CRS is not configured for the serving cell. – The channel bandwidth and centre frequency are the same as the ones indicated in RateMatchPatternLTE-CRS if configured for the serving cell. – The MBSFN configuration is the same as the one indicated in RateMatchPatternLTE-CRS if configured for the serving cell. – Network-based CRS interference mitigation (i.e., CRS muting), as in crs-IntfMitigConfig specified in TS 36.331 [10], is not enabled. If the field is configured (i.e. false) and LTE-NeighCellsCRS-AssistInfoList is configured, the configuration provided in LTE-NeighCellsCRS-AssistInfoList overrides the default network configuration assumptions. If the field is configured (i.e. false) and LTE-NeighCellsCRS-AssistInfoList is not configured, it is up to the UE implementation whether to apply CRS-IM operation.

nr-dl-PRS-PDC-Info Configures the DL PRS for propagation delay compensation. When configured, the UE measures the UE Rx-Tx time difference based on the reference signals configured in this field.

nrofHARQ-BundlingGroups Indicates the number of HARQ bundling groups for type2 HARQ-ACK codebook.

pathlossReferenceLinking Indicates whether UE shall apply as pathloss reference either the downlink of SpCell (PCell for MCG or PSCell for SCG) or of SCell that corresponds with this uplink (see TS 38.213 [13], clause 7).

pdsch-ServingCellConfig PDSCH related parameters that are not BWP-specific.

rateMatchPatternToAddModList Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology. See TS 38.214 [19], clause 5.1.4.1. If a RateMatchPattern with the same RateMatchPatternId is configured in both ServingCellConfig/ServingCellConfigCommon and in SIB20/MCCH, the entire RateMatchPattern configuration shall be the same, including the set of RBs/REs indicated by the patterns for the rate matching around, and they are counted as a single rate match pattern in the total configured rate match patterns as defined in TS 38.214 [19].

sCellDeactivationTimer SCell deactivation timer in TS 38.321 [3]. If the field is absent, the UE applies the value infinity.

sfnSchemePDCCH This parameter is used to configure SFN scheme for PDCCH: sfnSchemeA or sfnSchemeB as specified (see TS 38.214 [19], clause 5.1). If network includes both sfnSchemePDCCH and sfnSchemePDSCH, same value shall be configured.

sfnSchemePDSCH This parameter is used to configure SFN scheme for PDSCH: sfnSchemeA or sfnSchemeB as specified (see TS 38.214 [19], clause 5.1). If network includes both sfnSchemePDCCH and sfnSchemePDSCH, same value shall be configured.

semiStaticChannelAccessConfigUE When this field is configured and when channelAccessMode-r16 (see IE ServingCellConfigCommon and IE ServingCellConfigCommonSIB) is configured to semiStatic, the UE operates in semi-static channel access mode and can initiate a channel occupancy periodically (see TS 37.213 [48], Clause 4.3). The period can be configured independently from period configured in SemiStaticChannelAccessConfig-r16 if the UE indicates the corresponding capability. Otherwise, the periodicity configured by periodUE-r17 is an integer multiple of or an integter factor of the periodicity indicated by period in SemiStaticChannelAccessConfig-r16.

servingCellMO measObjectId of the MeasObjectNR in MeasConfig which is associated to the serving cell. For this MeasObjectNR, the following relationship applies between this MeasObjectNR and frequencyInfoDL in ServingCellConfigCommon of the serving cell: if ssbFrequency is configured, its value is the same as the absoluteFrequencySSB and if csi-rs-ResourceConfigMobility is configured, the value of its subcarrierSpacing is present in one entry of the scs-SpecificCarrierList, csi-RS-CellListMobility includes an entry corresponding to the serving cell (with cellId equal to physCellId in ServingCellConfigCommon) and the frequency range indicated by the csi-rs-MeasurementBW of the entry in csi-RS-CellListMobility is included in the frequency range indicated by in the entry of the scs-SpecificCarrierList.

supplementaryUplink Network may configure this field only when supplementaryUplinkConfig is configured in ServingCellConfigCommon or supplementaryUplink is configured in ServingCellConfigCommonSIB.

supplementaryUplinkRelease If this field is included, the UE shall release the uplink configuration configured by supplementaryUplink. The network only includes either supplementaryUplinkRelease or supplementaryUplink at a time.

tag-Id Timing Advance Group ID, as specified in TS 38.321 [3], which this cell belongs to.

tci-ActivatedConfig If configured for an SCell, or if configured for the PSCell when the SCG is being activated upon the reception of the containing message, the UE shall consider the TCI states provided in this field as the activated TCI states for PDCCH/PDSCH reception on this serving cell. If configured for the PSCell when the SCG is indicated as deactivated in the containing message: – the UE shall consider the TCI states provided in this field as the TCI states to be activated for PDCCH/PDSCH reception upon a later SCG activation in which tci-ActivatedConfig is absent – if bfd-and-RLM is configured and no RS is configured in RadioLinkMonitoringConfig for RLM, respectively for BFD, the UE shall use the TCI states provided in this field for PDCCH as RS for RLM, respectively for BFD. When this field is absent for the PSCell and the SCG is being deactivated: – the UE shall consider the previously activated TCI states as the TCI states to be activated for PDCCH/PDSCH reception upon a later SCG activation in which tci-ActivatedConfig is absent – if bfd-and-RLM is configured and no RS is configured in RadioLinkMonitoringConfig for RLM, respectively for BFD, the UE shall use the previously activated TCI states for PDCCH as RS for RLM, respectively for BFD.

tdd-UL-DL-ConfigurationDedicated-IAB-MT Resource configuration per IAB-MT D/U/F overrides all symbols (with a limitation that effectively only flexible symbols can be overwritten in Rel-16) per slot over the number of slots as provided by TDD-UL-DL ConfigurationCommon.

unifiedTCI-StateType Indicates the unified TCI state type the UE is configured for this serving cell. The value separate means this serving cell is configured with dl-OrJoint-TCI-ToAddModList for DL TCI state and ul-TCI-ToAddModList for UL TCI state. The value joint means this serving cell is configured with dl-OrJoint-TCI-ToAddModList for joint TCI state for UL and DL operation. The network does not configure the field in a serving cell that is configured with more than one value for the coresetPoolIndex.

uplinkConfig Network may configure this field only when uplinkConfigCommon is configured in ServingCellConfigCommon or ServingCellConfigCommonSIB. Addition or release of this field can only be done upon SCell addition or release (respectively).

uplink-PowerControlToAddModList Configures UL power control parameters for PUSCH, PUCCH and SRS when field unifiedTCI-StateType is configured for this serving cell.

UplinkConfig field descriptions

carrierSwitching Includes parameters for configuration of carrier based SRS switching (see TS 38.214 [19], clause 6.2.1.3.

enableDefaultBeamPL-ForPUSCH0-0, enableDefaultBeamPL-ForPUCCH, enableDefaultBeamPL-ForSRS When the parameter is present, UE derives the spatial relation and the corresponding pathloss reference Rs as specified in 38.213, clauses 7.1.1, 7.2.1, 7.3.1 and 9.2.2. The network only configures these parameters for FR2.

enablePL-RS-UpdateForPUSCH-SRS When this parameter is present, the Rel-16 feature of MAC CE based pathloss RS updates for PUSCH/SRS is enabled. Network only configures this parameter when the UE is configured with sri-PUSCH-PowerControl. If this field is not configured, network configures at most 4 pathloss RS resources for PUSCH/PUCCH/SRS transmissions per BWP, not including pathloss RS resources for SRS transmissions for positioning. (See TS 38.213 [13], clause 7).

firstActiveUplinkBWP-Id If configured for an SpCell, this field contains the ID of the UL BWP to be activated upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch. If configured for an SCell, this field contains the ID of the uplink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BandiwdthPartId = 0.

initialUplinkBWP The dedicated (UE-specific) configuration for the initial uplink bandwidth-part (i.e. UL BWP#0). If any of the optional IEs are configured within this IE as part of the IE uplinkConfig, the UE considers the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1

moreThanOneNackOnlyMode Indicates the mode of supporting more than one NACK-only feedback in the same PUCCH transmission. Mode 1 means UE multiplexing the HARQ-ACK bits by transforming NACK-only into ACK/NACK HARQ bits. Mode 2 means UE transmitting a specific sequence or a PUCCH transmission corresponding to the combination of more than one NACK-only HARQ feedback. If multicast CFR is not configured, this field is not included. Otherwise, if the field is absent, UE uses mode 1 for multicast CFR.

mpr-PowerBoost-FR2 Indicates whether UE is allowed to boost uplink transmission power by suspending in-band emission (IBE) requirements as specified in TS 38.101-2 [39]. Network only configures this field for FR2 serving cells.

powerBoostPi2BPSK If this field is set to true, the UE determines the maximum output power for PUCCH/PUSCH transmissions that use pi/2 BPSK modulation according to TS 38.101-1 [15], clause 6.2.4.

pusch-ServingCellConfig PUSCH related parameters that are not BWP-specific.

uplinkBWP-ToAddModList The additional bandwidth parts for uplink to be added or modified. In case of TDD uplink- and downlink BWP with the same bandwidthPartId are considered as a BWP pair and must have the same center frequency.

uplinkBWP-ToReleaseList The additional bandwidth parts for uplink to be released.

uplinkChannelBW-PerSCS-List A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in UplinkConfigCommon / UplinkConfigCommonSIB. Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1 [15] and TS 38.101-2 [39].

uplinkTxSwitchingPeriodLocation Indicates whether the location of UL Tx switching period is configured in this uplink carrier in case of inter-band UL CA, SUL, or (NG)EN-DC, as specified in TS 38.101-1 [15] and TS 38.101-3 [34]. In case of (NG)EN-DC, network always configures this field to TRUE for NR carrier (i.e. with (NG)EN-DC, the UL switching period always occurs on the NR carrier). In case of inter-band UL CA or SUL, for dynamic uplink Tx switching between 2 bands with 2 uplink carriers or 3 uplink carriers as defined in TS 38.101-1 [15], network configures this field to TRUE for the uplink carrier(s) on one band and configures this field to FALSE for the uplink carrier(s) on the other band. This field is set to the same value for the carriers on the same band.

uplinkTxSwitchingCarrier Indicates that the configured carrier is carrier1 or carrier2 for dynamic uplink Tx switching, as defined in TS 38.101-1 [15] and TS 38.101-3 [34]. In case of (NG)EN-DC, network always configures the NR carrier as carrier 2. In case of inter-band UL CA or SUL, for dynamic uplink Tx switching between 2 bands with 2 uplink carriers or 3 uplink carriers as defined in TS 38.101-1 [15], network configures the uplink carrier(s) on one band as carrier1 and the uplink carrier(s) on the other band as carrier2. This field is set to the same value for the carriers on the same band.

DormantBWP-Config field descriptions

dormancyGroupWithinActiveTime This field contains the ID of an SCell group for Dormancy within active time, to which this SCell belongs. The use of the Dormancy within active time SCell groups is specified in TS 38.213 [13].

dormancyGroupOutsideActiveTime This field contains the ID of an SCell group for Dormancy outside active time, to which this SCell belongs. The use of the Dormancy outside active time SCell groups is specified in TS 38.213 [13].

dormantBWP-Id This field contains the ID of the downlink bandwidth part to be used as dormant BWP. If this field is configured, its value is different from defaultDownlinkBWP-Id, and at least one of the withinActiveTimeConfig and outsideActiveTimeConfig should be configured.

firstOutsideActiveTimeBWP-Id This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy outside active time.

firstWithinActiveTimeBWP-Id This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy within active time.

outsideActiveTimeConfig This field contains the configuration to be used for SCell dormancy outside active time, as specified in TS 38.213 [13]. The field can only be configured when the cell group the SCell belongs to is configured with dcp-Config.

withinActiveTimeConfig This field contains the configuration to be used for SCell dormancy within active time, as specified in TS 38.213 [13].

GuardBand field descriptions

startCRB Indicates the starting RB of the guard band.

nrofCRB Indicates the length of the guard band in RBs. When set to 0, zero-size guard band is used.

NOTE 1: If the dedicated part of initial UL/DL BWP configuration is absent, the initial BWP can be used but with some limitations. For example, changing to another BWP requires RRCReconfiguration since DCI format 1_0 doesn’t support DCI-based switching.

Conditional Presence	Explanation
AsyncCA	This field is mandatory present for SCells whose slot offset between the SpCell is not 0. Otherwise it is absent, Need S.
MeasObject	This field is mandatory present for the SpCell if the UE has a measConfig, and it is optionally present, Need M, for SCells. For RedCap UEs, this field is optionally present, Need M.
SCellOnly	This field is optionally present, Need R, for SCells. It is absent otherwise.
ServingCellWithoutPUCCH	This field is optionally present, Need S, for SCells except PUCCH SCells. It is absent otherwise.
SyncAndCellAdd	This field is mandatory present for a SpCell upon reconfiguration with reconfigurationWithSync and upon RRCSetup/RRCResume. The field is optionally present for an SpCell, Need N, upon reconfiguration without reconfigurationWithSync. The field is mandatory present for an SCell upon addition, and absent for SCell in other cases, Need M.
TCI_ActivatedConfig	This field is optional Need N for SCells if sCellState is configured, otherwise it is absent. This field is optional Need S for the PSCell when the SCG is indicated as deactivated or is being activated, otherwise it is absent. This field is absent for the PCell.
TDD	This field is optionally present, Need R, for TDD cells. It is absent otherwise.
TDD_IAB	For IAB-MT, this field is optionally present, Need R, for TDD cells. It is absent otherwise.

– ServingCellConfigCommon

The IE ServingCellConfigCommon is used to configure cell specific parameters of a UE’s serving cell. The IE contains parameters which a UE would typically acquire from SSB, MIB or SIBs when accessing the cell from IDLE. With this IE, the network provides this information in dedicated signalling when configuring a UE with a SCells or with an additional cell group (SCG). It also provides it for SpCells (MCG and SCG) upon reconfiguration with sync.

ServingCellConfigCommon information element

— ASN1START

— TAG-SERVINGCELLCONFIGCOMMON-START

ServingCellConfigCommon ::= SEQUENCE {

physCellId PhysCellId OPTIONAL, — Cond HOAndServCellAdd,

downlinkConfigCommon DownlinkConfigCommon OPTIONAL, — Cond HOAndServCellAdd

uplinkConfigCommon UplinkConfigCommon OPTIONAL, — Need M

supplementaryUplinkConfig UplinkConfigCommon OPTIONAL, — Need S

n-TimingAdvanceOffset ENUMERATED { n0, n25600, n39936 } OPTIONAL, — Need S

ssb-PositionsInBurst CHOICE {

shortBitmap BIT STRING (SIZE (4)),

mediumBitmap BIT STRING (SIZE (8)),

longBitmap BIT STRING (SIZE (64))

} OPTIONAL, — Cond AbsFreqSSB

ssb-periodicityServingCell ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 } OPTIONAL, — Need S

dmrs-TypeA-Position ENUMERATED {pos2, pos3},

lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, — Need M

rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, — Need N

rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, — Need N

ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, — Cond HOAndServCellWithSSB

tdd-UL-DL-ConfigurationCommon TDD-UL-DL-ConfigCommon OPTIONAL, — Cond TDD

ss-PBCH-BlockPower INTEGER (-60..50),

…,

[[

channelAccessMode-r16 CHOICE {

dynamic NULL,

semiStatic SemiStaticChannelAccessConfig-r16

} OPTIONAL, — Cond SharedSpectrum

discoveryBurstWindowLength-r16 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5} OPTIONAL, — Need R

ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16 OPTIONAL, — Cond SharedSpectrum

highSpeedConfig-r16 HighSpeedConfig-r16 OPTIONAL — Need R

]],

[[

highSpeedConfig-v1700 HighSpeedConfig-v1700 OPTIONAL, — Need R

channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, — Cond SharedSpectrum2

discoveryBurstWindowLength-r17 ENUMERATED {ms0dot125, ms0dot25, ms0dot5, ms0dot75, ms1, ms1dot25} OPTIONAL, — Need R

ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17 OPTIONAL, — Cond SharedSpectrum2

highSpeedConfigFR2-r17 HighSpeedConfigFR2-r17 OPTIONAL, — Need R

uplinkConfigCommon-v1700 UplinkConfigCommon-v1700 OPTIONAL, — Need R

ntn-Config-r17 NTN-Config-r17 OPTIONAL — Need R

]],

[[

featurePriorities-r17 SEQUENCE {

redCapPriority-r17 FeaturePriority-r17 OPTIONAL, — Need R

slicingPriority-r17 FeaturePriority-r17 OPTIONAL, — Need R

msg3-Repetitions-Priority-r17 FeaturePriority-r17 OPTIONAL, — Need R

sdt-Priority-r17 FeaturePriority-r17 OPTIONAL — Need R

} OPTIONAL — Need R

]]

}

— TAG-SERVINGCELLCONFIGCOMMON-STOP

— ASN1STOP

ServingCellConfigCommon field descriptions

channelAccessMode If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213 [48]. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 in TS 37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedures in TS 37.213, with the exception of clause 4.3 of TS 37.213.

channelAccessMode2 If present (‘enabled’), the UE shall apply channel access mode procedures for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4 for FR2-2. If absent, the UE shall not apply any channel access procedure.

dmrs-TypeA-Position Position of (first) DM-RS for downlink (see TS 38.211 [16], clause 7.4.1.1.1) and uplink (TS 38.211 [16], clause 6.4.1.1.3).

downlinkConfigCommon The common downlink configuration of the serving cell, including the frequency information configuration and the initial downlink BWP common configuration. The parameters provided herein should match the parameters configured by MIB and SIB1 (if provided) of the serving cell, with the exception of controlResourceSetZero and searchSpaceZero which can be configured in ServingCellConfigCommon even if MIB indicates that they are absent.

discoveryBurstWindowLength Indicates the window length of the discovery burst in ms (see TS 37.213 [48]). The field discoveryBurstWindowLength-r17 is applicable to SCS 480 kHz and SCS 960 kHz.

featurePriorities Indicates priorities for features, such as RedCap, Slicing, SDT and MSG3-Repetitions for Coverage Enhancements. These priorities are used to determine which FeatureCombinationPreambles the UE shall use when a feature maps to more than one FeatureCombinationPreambles, as specified in TS 38.321 [3]. A lower value means a higher priority. The network does not signal the same priority for more than one feature. The network signals a priority for all feature that map to at least one FeatureCombinationPreambles.

longBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1.

lte-CRS-ToMatchAround Parameters to determine an LTE CRS pattern that the UE shall rate match around.

mediumBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1.

n-TimingAdvanceOffset The N_TA-Offset to be applied for all uplink transmissions on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133 [14], table 7.1.2-2.

rateMatchPatternToAddModList Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology (see TS 38.214 [19], clause 5.1.4.1). If a RateMatchPattern with the same RateMatchPatternId is configured in both ServingCellConfig/ServingCellConfigCommon and in SIB20/MCCH, the entire RateMatchPattern configuration, including the set of RBs/REs indicated by the patterns for the rate matching around, shall be the same and they are counted as a single rate match pattern in the total configured rate match patterns as defined in TS 38.214 [19].

shortBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1.

ss-PBCH-BlockPower Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7.

ssb-periodicityServingCell The SSB periodicity in ms for the rate matching purpose. If the field is absent, the UE applies the value ms5. (see TS 38.213 [13], clause 4.1)

ssb-PositionQCL Indicates the QCL relation between SSB positions for this serving cell as specified in TS 38.213 [13], clause 4.1.

ssb-PositionsInBurst For operation in licensed spectrum, indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB. For operation with shared spectrum channel access, the UE assumes that one or more SS/PBCH blocks indicated by ssb-PositionsInBurst may be transmitted within the discovery burst transmission window and have candidate SS/PBCH blocks indexes corresponding to SS/PBCH block indexes provided by ssb-PositionsInBurst (see TS 38.213 [13], clause 4.1). If the k-th bit of ssb-PositionsInBurst is set to 1, the UE assumes that one or more SS/PBCH blocks within the discovery burst transmission window with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k – 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL and the number of actually transmitted SS/PBCH blocks is not larger than the number of 1’s in the bitmap. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB. For operation with shared spectrum channel access in FR1, only mediumBitmap is used, and for FR2-2, longBitmap is used.

ssbSubcarrierSpacing Subcarrier spacing of SSB. Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 120 or 240 kHz FR2-2: 120, 480, or 960 kHz

supplementaryUplinkConfig The network configures this field only if uplinkConfigCommon is configured. If this field is absent, the UE shall release the supplementaryUplinkConfig and the supplementaryUplink configured in ServingCellConfig of this serving cell, if configured.

tdd-UL-DL-ConfigurationCommon A cell-specific TDD UL/DL configuration, see TS 38.213 [13], clause 11.1.

Conditional Presence	Explanation
AbsFreqSSB	The field is absent when absoluteFrequencySSB in frequencyInfoDL is absent, otherwise the field is mandatory present.
HOAndServCellAdd	This field is mandatory present upon SpCell change (including path switch between a serving cell and a L2 U2N Relay UE) and upon serving cell (PSCell/SCell) addition. Otherwise, the field is absent.
HOAndServCellWithSSB	This field is mandatory present upon SpCell change and upon serving cell (SCell with SSB or PSCell) addition. Otherwise, the field is absent.
SharedSpectrum	This field is mandatory present if this cell operates with shared spectrum channel access in FR1. Otherwise, it is absent, Need R.
SharedSpectrum2	This field is optionally present if this cell operates with shared spectrum channel access in FR2-2, Need R. Otherwise, it is absent, Need R.
TDD	The field is optionally present, Need R, for TDD cells; otherwise it is absent.

– ServingCellConfigCommonSIB

The IE ServingCellConfigCommonSIB is used to configure cell specific parameters of a UE’s serving cell in SIB1.

ServingCellConfigCommonSIB information element

— ASN1START

— TAG-SERVINGCELLCONFIGCOMMONSIB-START

ServingCellConfigCommonSIB ::= SEQUENCE {

downlinkConfigCommon DownlinkConfigCommonSIB,

uplinkConfigCommon UplinkConfigCommonSIB OPTIONAL, — Need R

supplementaryUplink UplinkConfigCommonSIB OPTIONAL, — Need R

n-TimingAdvanceOffset ENUMERATED { n0, n25600, n39936 } OPTIONAL, — Need S

ssb-PositionsInBurst SEQUENCE {

inOneGroup BIT STRING (SIZE (8)),

groupPresence BIT STRING (SIZE (8)) OPTIONAL — Cond FR2-Only

},

ssb-PeriodicityServingCell ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160},

tdd-UL-DL-ConfigurationCommon TDD-UL-DL-ConfigCommon OPTIONAL, — Cond TDD

ss-PBCH-BlockPower INTEGER (-60..50),

…,

[[

channelAccessMode-r16 CHOICE {

dynamic NULL,

semiStatic SemiStaticChannelAccessConfig-r16

} OPTIONAL, — Cond SharedSpectrum

discoveryBurstWindowLength-r16 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5} OPTIONAL, — Need R

highSpeedConfig-r16 HighSpeedConfig-r16 OPTIONAL — Need R

]],

[[

channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, — Cond SharedSpectrum2

discoveryBurstWindowLength-v1700 ENUMERATED {ms0dot125, ms0dot25, ms0dot5, ms0dot75, ms1, ms1dot25} OPTIONAL, — Need R

highSpeedConfigFR2-r17 HighSpeedConfigFR2-r17 OPTIONAL, — Need R

uplinkConfigCommon-v1700 UplinkConfigCommonSIB-v1700 OPTIONAL — Need R

]]

}

— TAG-SERVINGCELLCONFIGCOMMONSIB-STOP

— ASN1STOP

ServingCellConfigCommonSIB field descriptions

channelAccessMode If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213 [48]. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 in TS 37.213. If the field is configured as "dynamic"t, the UE shall apply the channel access procedures in TS 37.213, with the exception of clause 4.3 of TS 37.213.

channelAccessMode2 If present (‘enabled’), this field indicates that the UE shall apply channel access mode procedures for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4 for FR2-2. If absent, the UE shall not apply any channel access procedure.

discoveryBurstWindowLength Indicates the window length of the discovery burst in ms (see TS 37.213 [48]). The field discoveryBurstWindowLength-v1700 is applicable to SCS 480 kHz and SCS 960 kHz.

groupPresence This field is present when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to the SS/PBCH index 0-7, the second bit corresponds to SS/PBCH block 8-15, and so on. Value 0 in the bitmap indicates that the SSBs according to inOneGroup are absent. Value 1 indicates that the SS/PBCH blocks are transmitted in accordance with inOneGroup.

inOneGroup When maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1, only the 4 leftmost bits are valid; the UE ignores the 4 rightmost bits. When maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1, all 8 bits are valid. The first/ leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. When maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1, all 8 bit are valid; The first/ leftmost bit corresponds to the first SS/PBCH block index in the group (i.e., to SSB index 0, 8, and so on); the second bit corresponds to the second SS/PBCH block index in the group (i.e., to SSB index 1, 9, and so on), and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted.

n-TimingAdvanceOffset The N_TA-Offset to be applied for random access on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133 [14], table 7.1.2-2.

ssb-PositionsInBurst Time domain positions of the transmitted SS-blocks in an SS-burst as defined in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access in FR1, only inOneGroup is used and the UE interprets this field same as mediumBitmap in ServingCellConfigCommon. The UE assumes that a bit in inOneGroup at position k > is 0, where is obtained from MIB as specified in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access in FR2-2, the m-th bit in groupPresence is set to 0 for m > /8, where is obtained from MIB as specified in TS 38.213 [13], clause 4.1.

ss-PBCH-BlockPower Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7.

Conditional Presence	Explanation
FR2-Only	This field is mandatory present for an FR2 carrier frequency. It is absent otherwise and UE releases any configured value.
SharedSpectrum	This field is mandatory present if this cell operates with shared spectrum channel access in FR1. Otherwise, it is absent, Need R.
SharedSpectrum2	This field is optionally present if this cell operates with shared spectrum channel access in FR2-2, Need R. Otherwise, it is absent, Need R.
TDD	The field is optionally present, Need R, for TDD cells; otherwise it is absent.

– ShortI-RNTI-Value

The IE ShortI-RNTI-Value is used to identify the suspended UE context of a UE in RRC_INACTIVE using fewer bits compared to I-RNTI-Value.

ShortI-RNTI-Value information element

— ASN1START

— TAG-SHORTI-RNTI-VALUE-START

ShortI-RNTI-Value ::= BIT STRING (SIZE(24))

— TAG-SHORTI-RNTI-VALUE-STOP

— ASN1STOP

– ShortMAC-I

The IE ShortMAC-I is used to identify and verify the UE at RRC connection re-establishment. The 16 least significant bits of the MAC-I calculated using the AS security configuration of the source PCell, as specified in 5.3.7.4.

ShortMAC-I information element

— ASN1START

— TAG-SHORTMAC-I-START

ShortMAC-I ::= BIT STRING (SIZE (16))

— TAG-SHORTMAC-I-STOP

— ASN1STOP

– SINR-Range

The IE SINR-Range specifies the value range used in SINR measurements and thresholds. For measurements, integer value for SINR measurements is according to Table 10.1.16.1-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value – 46) / 2 dB.

SINR-Range information element

— ASN1START

— TAG-SINR-RANGE-START

SINR-Range ::= INTEGER(0..127)

— TAG-SINR-RANGE-STOP

— ASN1STOP

– SI-RequestConfig

The IE SI-RequestConfig contains configuration for Msg1 based SI request.

SI-RequestConfig information element

— ASN1START

— TAG-SI-REQUESTCONFIG-START

SI-RequestConfig ::= SEQUENCE {

rach-OccasionsSI SEQUENCE {

rach-ConfigSI RACH-ConfigGeneric,

ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen}

} OPTIONAL, — Need R

si-RequestPeriod ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, — Need R

si-RequestResources SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResources

}

SI-RequestResources ::= SEQUENCE {

ra-PreambleStartIndex INTEGER (0..63),

ra-AssociationPeriodIndex INTEGER (0..15) OPTIONAL, — Need R

ra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL — Need R

}

— TAG-SI-REQUESTCONFIG-STOP

— ASN1STOP

SI-RequestConfig field descriptions

rach-OccasionsSI Configuration of dedicated RACH Occasions for SI. If the field is absent, the UE uses the corresponding parameters configured in rach-ConfigCommon of the initial uplink BWP.

si-RequestPeriod Periodicity of the SI-Request configuration in number of association periods.

si-RequestResources If there is only one entry in the list, the configuration is used for all SI messages for which si-BroadcastStatus is set to notBroadcasting. Otherwise the 1st entry in the list corresponds to the first SI message in schedulingInfoList for which si-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message in schedulingInfoList for which si-BroadcastStatus is set to notBroadcasting and so on. Change of si-RequestResources should not result in system information change notification.

SI-RequestResources field descriptions

ra-AssociationPeriodIndex Index of the association period in the si-RequestPeriod in which the UE can send the SI request for SI message(s) corresponding to this SI-RequestResources, using the preambles indicated by ra-PreambleStartIndex and rach occasions indicated by ra-ssb-OccasionMaskIndex.

ra-PreambleStartIndex If N SSBs are associated with a RACH occasion, where N > = 1, for the i-th SSB (i=0, …, N-1) the preamble with preamble index = ra-PreambleStartIndex + i is used for SI request; For N < 1, the preamble with preamble index = ra-PreambleStartIndex is used for SI request.

– SI-SchedulingInfo

The IE SI-SchedulingInfo contains information needed for acquisition of SI messages.

SI-SchedulingInfo information element

— ASN1START

— TAG-SI-SCHEDULINGINFO-START

SI-SchedulingInfo ::= SEQUENCE {

schedulingInfoList SEQUENCE (SIZE (1..maxSI-Message)) OF SchedulingInfo,

si-WindowLength ENUMERATED {s5, s10, s20, s40, s80, s160, s320, s640, s1280, s2560-v1710, s5120-v1710 },

si-RequestConfig SI-RequestConfig OPTIONAL, — Cond MSG-1

si-RequestConfigSUL SI-RequestConfig OPTIONAL, — Cond SUL-MSG-1

systemInformationAreaID BIT STRING (SIZE (24)) OPTIONAL, — Need R

…

}

SchedulingInfo ::= SEQUENCE {

si-BroadcastStatus ENUMERATED {broadcasting, notBroadcasting},

si-Periodicity ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512},

sib-MappingInfo SIB-Mapping

}

SI-SchedulingInfo-v1700 ::= SEQUENCE {

schedulingInfoList2-r17 SEQUENCE (SIZE (1..maxSI-Message)) OF SchedulingInfo2-r17,

si-RequestConfigRedCap-r17 SI-RequestConfig OPTIONAL — Cond REDCAP-MSG-1

}

SchedulingInfo2-r17 ::= SEQUENCE {

si-BroadcastStatus-r17 ENUMERATED {broadcasting, notBroadcasting},

si-WindowPosition-r17 INTEGER (1..256),

si-Periodicity-r17 ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512},

sib-MappingInfo-r17 SIB-Mapping-v1700

}

SIB-Mapping ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo

SIB-Mapping-v1700 ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo-v1700

SIB-TypeInfo ::= SEQUENCE {

type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9,

sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610,

sibType14-v1610, spare3, spare2, spare1,… },

valueTag INTEGER (0..31) OPTIONAL, — Cond SIB-TYPE

areaScope ENUMERATED {true} OPTIONAL — Need S

}

SIB-TypeInfo-v1700 ::= SEQUENCE {

sibType-r17 CHOICE {

type1-r17 ENUMERATED {sibType15, sibType16, sibType17, sibType18, sibType19, sibType20, sibType21,

spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1,…},

type2-r17 SEQUENCE {

posSibType-r17 ENUMERATED {posSibType1-9, posSibType1-10, posSibType2-24, posSibType2-25,

posSibType6-4, posSibType6-5, posSibType6-6, spare9, spare8, spare7, spare6,

spare5, spare4, spare3, spare2, spare1,…},

encrypted-r17 ENUMERATED { true } OPTIONAL, — Need R

gnss-id-r17 GNSS-ID-r16 OPTIONAL, — Need R

sbas-id-r17 SBAS-ID-r16 OPTIONAL — Need R

}

},

valueTag-r17 INTEGER (0..31) OPTIONAL, — Cond NonPosSIB

areaScope-r17 ENUMERATED {true} OPTIONAL — Need S

}

— TAG-SI-SCHEDULINGINFO-STOP

— ASN1STOP

SchedulingInfo field descriptions

areaScope Indicates that a SIB is area specific. If the field is absent, the SIB is cell specific.

si-BroadcastStatus Indicates if the SI message is being broadcasted or not. Change of si-BroadcastStatus should not result in system information change notifications in Short Message transmitted with P-RNTI over DCI (see clause 6.5). The value of the indication is valid until the end of the BCCH modification period when set to broadcasting. When SIB19 is scheduled, the si-BroadcastStatus for the mapped SIB19 is set to broadcasting.

si-Periodicity Periodicity of the SI-message in radio frames. Value rf8 corresponds to 8 radio frames, value rf16 corresponds to 16 radio frames, and so on.

SI-SchedulingInfo field descriptions

si-RequestConfig Configuration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting.

si-RequestConfigRedCap Configuration of Msg1 resources for initialUplinkBWP-RedCap that the RedCap UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting.

si-RequestConfigSUL Configuration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting.

si-WindowLength The length of the SI scheduling window. Value s5 corresponds to 5 slots, value s10 corresponds to 10 slots and so on. The network always configures si-WindowLength to be shorter than or equal to the si-Periodicity. The values s2560-v1710 and s5120-v1710 are only applicable for SCS 480 kHz.

systemInformationAreaID Indicates the system information area that the cell belongs to, if any. Any SIB with areaScope within the SI is considered to belong to this systemInformationAreaID. The systemInformationAreaID is unique within a PLMN/SNPN.

SchedulingInfo2 field descriptions

encrypted The presence of this field indicates that the pos-sib-type is encrypted as specified in TS 37.355 [49].

gnss-id The presence of this field indicates that the positioning SIB type is for a specific GNSS. Indicates a specific GNSS (see also TS 37.355 [49])

posSibType The posSIBs as defined in TS 37.355 [49] mapped to SI for scheduling using schedulingInfoList2.

sbas-id The presence of this field indicates that the positioning SIB type is for a specific SBAS. Indicates a specific SBAS (see also TS 37.355 [49]).

si-WindowPosition This field indicates the SI window position of the associated SI-message. The network provides si-WindowPosition in an ascending order, i.e. si-WindowPosition in the subsequent entry in schedulingInfoList2 has always value higher than in the previous entry of schedulingInfoList2. The network configures this field in a way that ensures that SI messages scheduled by schedulingInfoList and/or posSchedulingInfoList do not overlap with SI messages scheduled by schedulingInfoList2.

sib-MappingInfo Indicates which SIBs or posSIBs are contained in the SI message.

type1, type2 The SIBs/posSIBs mapped to SI for scheduling using schedulingInfoList2.

Conditional presence	Explanation
MSG-1	The field is optionally present, Need R, if si-BroadcastStatus is set to notBroadcasting for any SI-message included in SchedulingInfo. It is absent otherwise.
SIB-TYPE	The field is mandatory present if the SIB type is different from SIB6, SIB7 or SIB8. For SIB6, SIB7 and SIB8 it is absent.
NonPosSIB	The field is mandatory present if the SIB type is type1. For type2 it is absent.
SUL-MSG-1	The field is optionally present, Need R, if supplementaryUplink is configured in ServingCellConfigCommonSIB and if si-BroadcastStatus is set to notBroadcasting for any SI-message included in SchedulingInfo. It is absent otherwise.
REDCAP-MSG-1	The field is optionally present, Need R, if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if si-BroadcastStatus is set to notBroadcasting for any SI-message included in SchedulingInfo. It is absent otherwise.

– SK-Counter

The IE SK-Counter is a counter used upon initial configuration of SN security for NR-DC and NE-DC, as well as upon refresh of S-K_gNB or S-K_eNB based on the current or newly derived K_gNB during RRC Resume or RRC Reconfiguration, as defined in TS 33.501 [11].

— ASN1START

— TAG-SKCOUNTER-START

SK-Counter ::= INTEGER (0..65535)

— TAG-SKCOUNTER-STOP

— ASN1STOP

– SlotFormatCombinationsPerCell

The IE SlotFormatCombinationsPerCell is used to configure the SlotFormatCombinations applicable for one serving cell (see TS 38.213 [13], clause 11.1.1).

SlotFormatCombinationsPerCell information element

— ASN1START

— TAG-SLOTFORMATCOMBINATIONSPERCELL-START

SlotFormatCombinationsPerCell ::= SEQUENCE {

servingCellId ServCellIndex,

subcarrierSpacing SubcarrierSpacing,

subcarrierSpacing2 SubcarrierSpacing OPTIONAL, — Need R

slotFormatCombinations SEQUENCE (SIZE (1..maxNrofSlotFormatCombinationsPerSet)) OF SlotFormatCombination

OPTIONAL, — Need M

positionInDCI INTEGER(0..maxSFI-DCI-PayloadSize-1) OPTIONAL, — Need M

…,

[[

enableConfiguredUL-r16 ENUMERATED {enabled} OPTIONAL — Need R

]]

}

SlotFormatCombination ::= SEQUENCE {

slotFormatCombinationId SlotFormatCombinationId,

slotFormats SEQUENCE (SIZE (1..maxNrofSlotFormatsPerCombination)) OF INTEGER (0..255)

}

SlotFormatCombinationId ::= INTEGER (0..maxNrofSlotFormatCombinationsPerSet-1)

— TAG-SLOTFORMATCOMBINATIONSPERCELL-STOP

— ASN1STOP

SlotFormatCombination field descriptions

slotFormatCombinationId This ID is used in the DCI payload to dynamically select this SlotFormatCombination (see TS 38.213 [13], clause 11.1.1).

slotFormats Slot formats that occur in consecutive slots in time domain order as listed here (see TS 38.213 [13], clause 11.1.1 and TS 38.213 [13], clause 14 for IAB-MT).

SlotFormatCombinationsPerCell field descriptions

enableConfiguredUL If configured, the UE is allowed to transmit uplink signals/channels (SRS, PUCCH, CG-PUSCH) in the set of symbols of the slot when the UE does not detect a DCI format 2_0 providing a slot format for the set of symbols (see TS 38.213 [13], 11.1.1). This field is applicable only if cg-RetransmissionTimer-r16 is configured.

positionInDCI The (starting) position (bit) of the slotFormatCombinationId (SFI-Index) for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.1.1).

servingCellId The ID of the serving cell for which the slotFormatCombinations are applicable.

slotFormatCombinations A list with SlotFormatCombinations. Each SlotFormatCombination comprises of one or more SlotFormats (see TS 38.211 [16], clause 4.3.2). The total number of slotFormats in the slotFormatCombinations list does not exceed 512.

subcarrierSpacing2 Reference subcarrier spacing for a Slot Format Combination on an FDD or SUL cell (see TS 38.213 [13], clause 11.1.1). For FDD, subcarrierSpacing (SFI-scs) is the reference SCS for DL BWP and subcarrierSpacing2 (SFI-scs2) is the reference SCS for UL BWP. For SUL, subcarrierSpacing (SFI-scs) is the reference SCS for non-SUL carrier and subcarrierSpacing2 (SFI-scs2) is the reference SCS for SUL carrier. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications.

subcarrierSpacing Reference subcarrier spacing for this Slot Format Combination. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications (see TS 38.213 [13], clause 11.1.1).

– SlotFormatIndicator

The IE SlotFormatIndicator is used to configure monitoring a Group-Common-PDCCH for Slot-Format-Indicators (SFI).

SlotFormatIndicator information element

— ASN1START

— TAG-SLOTFORMATINDICATOR-START

SlotFormatIndicator ::= SEQUENCE {

sfi-RNTI RNTI-Value,

dci-PayloadSize INTEGER (1..maxSFI-DCI-PayloadSize),

slotFormatCombToAddModList SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF SlotFormatCombinationsPerCell

OPTIONAL, — Need N

slotFormatCombToReleaseList SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL, — Need N

…,

[[

availableRB-SetsToAddModList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF AvailableRB-SetsPerCell-r16 OPTIONAL, — Need N

availableRB-SetsToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL, — Need N

switchTriggerToAddModList-r16 SEQUENCE (SIZE(1..4)) OF SearchSpaceSwitchTrigger-r16 OPTIONAL, — Need N

switchTriggerToReleaseList-r16 SEQUENCE (SIZE(1..4)) OF ServCellIndex OPTIONAL, — Need N

co-DurationsPerCellToAddModList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF CO-DurationsPerCell-r16 OPTIONAL, — Need N

co-DurationsPerCellToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL — Need N

]],

[[

switchTriggerToAddModListSizeExt-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroupMinus4-r16)) OF

SearchSpaceSwitchTrigger-r16 OPTIONAL, — Need N

switchTriggerToReleaseListSizeExt-r16 SEQUENCE (SIZE(1.. maxNrofAggregatedCellsPerCellGroupMinus4-r16)) OF

ServCellIndex OPTIONAL — Need N

]],

[[

co-DurationsPerCellToAddModList-r17 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF CO-DurationsPerCell-r17 OPTIONAL — Need N

]]

}

CO-DurationsPerCell-r16 ::= SEQUENCE {

servingCellId-r16 ServCellIndex,

positionInDCI-r16 INTEGER(0..maxSFI-DCI-PayloadSize-1),

subcarrierSpacing-r16 SubcarrierSpacing,

co-DurationList-r16 SEQUENCE (SIZE(1..64)) OF CO-Duration-r16

}

CO-DurationsPerCell-r17 ::= SEQUENCE {

servingCellId-r17 ServCellIndex,

positionInDCI-r17 INTEGER(0..maxSFI-DCI-PayloadSize-1),

subcarrierSpacing-r17 SubcarrierSpacing,

co-DurationList-r17 SEQUENCE (SIZE(1..64)) OF CO-Duration-r17

}

CO-Duration-r16 ::= INTEGER (0..1120)

CO-Duration-r17 ::= INTEGER (0..4480)

AvailableRB-SetsPerCell-r16 ::= SEQUENCE {

servingCellId-r16 ServCellIndex,

positionInDCI-r16 INTEGER(0..maxSFI-DCI-PayloadSize-1)

}

SearchSpaceSwitchTrigger-r16 ::= SEQUENCE {

servingCellId-r16 ServCellIndex,

positionInDCI-r16 INTEGER(0..maxSFI-DCI-PayloadSize-1)

}

— TAG-SLOTFORMATINDICATOR-STOP

— ASN1STOP

SlotFormatIndicator field descriptions

availableRB-SetsToAddModList A list of AvailableRB-SetsPerCell objects (see TS 38.213 [13], clause 11.1.1).

co-DurationsPerCellToAddModList A list of CO-DurationPerCell objects. If not configured, the UE uses the slot format indicator (SFI), if available, to determine the channel occupancy duration (see TS 38.213 [13], clause 11.1.1).

dci-PayloadSize Total length of the DCI payload scrambled with SFI-RNTI (see TS 38.213 [13], clause 11.1.1).

sfi-RNTI RNTI used for SFI on the given cell (see TS 38.213 [13], clause 11.1.1).

slotFormatCombToAddModList A list of SlotFormatCombinations for the UE’s serving cells (see TS 38.213 [13], clause 11.1.1).

switchTriggerToAddModList, switchTriggerToAddModListSizeExt A list of SearchSpaceSwitchTrigger objects. Each SearchSpaceSwitchTrigger object provides position in DCI of the bit field indicating search space switching flag for a serving cell or, if cellGroupsForSwitchList is configured, group of serving cells (see TS 38.213 [13], clause 10.4). If cellGroupsForSwitchList is configured, only one of the cells belonging to the same cell group is added/modified, and the configuration applies to all cells belonging to the cellGroupsForSwitchList (see TS 38.213 [13], clause 10.4). The network configures more than 4 SearchSpaceSwitchTrigger objects only if cellGroupsForSwitchList is not configured. The UE shall consider entries in switchTriggerToAddModList and in switchTriggerToAddModListSizeExt as a single list, i.e. an entry created using switchTriggerToAddModList can be modifed using switchTriggerToAddModListSizeExt and vice-versa.

switchTriggerToReleaseModList, switchTriggerToReleaseListSizeExt A list of SearchSpaceSwitchTriggers to be released. If cellGroupsForSwitchList is configured, the SearchSpaceSwitchTrigger is released for all serving cells belonging to the same CellGroupForSwitch. The UE shall consider entries in switchTriggerToReleaseList and in switchTriggerToReleaseListSizeExt as a single list, i.e. an entry created using switchTriggerToAddModList or switchTriggerToAddModListSizeExt can be deleted using switchTriggerToReleaseList or switchTriggerToReleaseListSizeExt.

AvailableRB-SetsPerCell field descriptions

positionInDCI The (starting) position of the bits within DCI payload indicating the availability of the RB sets of a serving cell (see TS 38.213 [13], clause 11.1.1).

servingCelIId The ID of the serving cell for which the configuration is applicable.

CO-DurationsPerCell field descriptions

co-DurationList A list of Channel Occupancy duration in symbols. The maximum duration that can be configured for the following SCS 120 kHz: 560. 480 kHz: 2240. 960 kHz: 4480.

positionInDCI Position in DCI of the bit field indicating Channel Occupancy duration for UE’s serving cells (see TS 38.213 [13], clause 11.1.1).

servingCelIId The ID of the serving cell for which the configuration is applicable.

subcarrierSpacing Reference subcarrier spacing for the list of Channel Occupancy durations (see TS 38.213 [13], clause 11.1.1).

SearchSpaceSwitchTrigger field descriptions

positionInDCI The position of the bit within DCI payload containing a search space switching flag (see TS 38.213 [13], clause 11.1.1).

servingCellId The ID of the serving cell for which the configuration is applicable or the group of serving cells as indicated by CellGroupsForSwitch-r16 containing this servingCellId.

– S-NSSAI

The IE S-NSSAI (Single Network Slice Selection Assistance Information) identifies a Network Slice end to end and comprises a slice/service type and a slice differentiator, see TS 23.003 [21].

S-NSSAI information element

— ASN1START

— TAG-S-NSSAI-START

S-NSSAI ::= CHOICE{

sst BIT STRING (SIZE (8)),

sst-SD BIT STRING (SIZE (32))

}

— TAG-S-NSSAI-STOP

— ASN1STOP

S-NSSAI field descriptions

sst Indicates the S-NSSAI consisting of Slice/Service Type, see TS 23.003 [21].

sst-SD Indicates the S-NSSAI consisting of Slice/Service Type and Slice Differentiator, see TS 23.003 [21].

– SpeedStateScaleFactors

The IE SpeedStateScaleFactors concerns factors, to be applied when the UE is in medium or high speed state, used for scaling a mobility control related parameter.

SpeedStateScaleFactors information element

— ASN1START

— TAG-SPEEDSTATESCALEFACTORS-START

SpeedStateScaleFactors ::= SEQUENCE {

sf-Medium ENUMERATED {oDot25, oDot5, oDot75, lDot0},

sf-High ENUMERATED {oDot25, oDot5, oDot75, lDot0}

}

— TAG-SPEEDSTATESCALEFACTORS-STOP

— ASN1STOP

SpeedStateScaleFactors field descriptions
sf-High The concerned mobility control related parameter is multiplied with this factor if the UE is in High Mobility state as defined in TS 38.304 [20]. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, oDot75 corresponds to 0.75 and so on.
sf-Medium The concerned mobility control related parameter is multiplied with this factor if the UE is in Medium Mobility state as defined in TS 38.304 [20]. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, value oDot75 corresponds to 0.75, and so on.

– SPS-Config

The IE SPS-Config is used to configure downlink semi-persistent transmission. Multiple Downlink SPS configurations may be configured in one BWP of a serving cell.

SPS-Config information element

— ASN1START

— TAG-SPS-CONFIG-START

SPS-Config ::= SEQUENCE {

periodicity ENUMERATED {ms10, ms20, ms32, ms40, ms64, ms80, ms128, ms160, ms320, ms640,

spare6, spare5, spare4, spare3, spare2, spare1},

nrofHARQ-Processes INTEGER (1..8),

n1PUCCH-AN PUCCH-ResourceId OPTIONAL, — Need M

mcs-Table ENUMERATED {qam64LowSE} OPTIONAL, — Need S

…,

[[

sps-ConfigIndex-r16 SPS-ConfigIndex-r16 OPTIONAL, — Cond SPS-List

harq-ProcID-Offset-r16 INTEGER (0..15) OPTIONAL, — Need R

periodicityExt-r16 INTEGER (1..5120) OPTIONAL, — Need R

harq-CodebookID-r16 INTEGER (1..2) OPTIONAL, — Need R

pdsch-AggregationFactor-r16 ENUMERATED {n1, n2, n4, n8 } OPTIONAL — Need S

]],

[[

sps-HARQ-Deferral-r17 INTEGER (1..32) OPTIONAL, — Need R

n1PUCCH-AN-PUCCHsSCell-r17 PUCCH-ResourceId OPTIONAL, — Need R

periodicityExt-r17 INTEGER (1..40960) OPTIONAL, — Need R

nrofHARQ-Processes-v1710 INTEGER(9..32) OPTIONAL, — Need R

harq-ProcID-Offset-v1700 INTEGER (16..31) OPTIONAL — Need R

]]

}

— TAG-SPS-CONFIG-STOP

— ASN1STOP

SPS-Config field descriptions

harq-CodebookID Indicates the HARQ-ACK codebook index for the corresponding HARQ-ACK codebook for SPS PDSCH and ACK for SPS PDSCH release.

harq-ProcID-Offset Indicates the offset used in deriving the HARQ process IDs, see TS 38.321 [3], clause 5.3.1.

mcs-Table Indicates the MCS table the UE shall use for DL SPS (see TS 38.214 [19],clause 5.1.3.1. If present, the UE shall use the MCS table of low-SE 64QAM table indicated in Table 5.1.3.1-3 of TS 38.214 [19]. If this field is absent and field mcs-table in PDSCH-Config is set to ‘qam256’ and the activating DCI is of format 1_1, the UE applies the 256QAM table indicated in Table 5.1.3.1-2 of TS 38.214 [19]. If this field is absent and the field mcs-Table-r17 in PDSCH-Config is set to ‘qam1024’ and the activating DCI is format 1_1, the UE applies the 1024QAM table indicated in Table 5.1.3.1-4 of TS 38.214 [19]. Otherwise, the UE applies the non-low-SE 64QAM table indicated in Table 5.1.3.1-1 of TS 38.214 [19].

n1PUCCH-AN HARQ resource for PUCCH for DL SPS. The network configures the resource either as format0 or format1. The actual PUCCH-Resource is configured in PUCCH-Config and referred to by its ID. See TS 38.213 [13], clause 9.2.3.

n1PUCCH-AN-PUCCHsSCell HARQ resource for PUCCH on PUCCH switching SCell (sSCell) for DL SPS. The network configures the resource either as format 0 or format 1. The actual PUCCH-Resource is configured in PUCCH-Config of the PUCCH sSCell and referred to by its ID. See TS 38.213 [13], clause 9.2.3.

nrofHARQ-Processes Number of configured HARQ processes for SPS DL (see TS 38.321 [3], clause 5.8.1). If UE is configured with nrofHARQ-Processes-v1710 UE shall ignore nrofHARQ-Processes (without suffix).

pdsch-AggregationFactor Number of repetitions for SPS PDSCH (see TS 38.214 [19], clause 5.1.2.1). When the field is absent, the UE applies PDSCH aggregation factor of PDSCH-Config.

periodicity Periodicity for DL SPS (see TS 38.214 [19] and TS 38.321 [3], clause 5.8.1).

periodicityExt This field is used to calculate the periodicity for DL SPS (see TS 38.214 [19] and see TS 38.321 [3], clause 5,8.1). If this field is present, the field periodicity is ignored. The following periodicities are supported depending on the configured subcarrier spacing [ms]: 15 kHz: periodicityExt, where periodicityExt has a value between 1 and 640. 30 kHz: 0.5 x periodicityExt, where periodicityExt has a value between 1 and 1280. 60 kHz with normal CP. 0.25 x periodicityExt, where periodicityExt has a value between 1 and 2560. 60 kHz with ECP: 0.25 x periodicityExt, where periodicityExt has a value between 1 and 2560. 120 kHz: 0.125 x periodicityExt, where periodicityExt has a value between 1 and 5120. 480 kHz: 0.0625 x periodicityExt, where periodicityExt has a value between 1 and 20480. 960 kHz: 0.03125 x periodicityExt, where periodicityExt has a value between 1 and 40960. periodicityExt-r17 is only applicable for SCS 480 kHz and 960 kHz.

sps-ConfigIndex Indicates the index of one of multiple SPS configurations.

sps-HARQ-Deferral Indicates the maximum number of slots or subslots the transmission of DL SPS HARQ-ACK in a slot or subslot can be deferred (see TS 38.213 [13], clause 9.2.5.4).

Conditional Presence	Explanation
SPS-List	The field is mandatory present when included in sps-ConfigToAddModList-r16, otherwise the field is absent.

– SPS-ConfigIndex

The IE SPS-ConfigIndex is used to indicate the index of one of multiple DL SPS configurations in one BWP.

SPS-ConfigIndex information element

— ASN1START

— TAG-SPS-CONFIGINDEX-START

SPS-ConfigIndex-r16 ::= INTEGER (0.. maxNrofSPS-Config-1-r16)

— TAG-SPS-CONFIGINDEX-STOP

— ASN1STOP

– SPS-PUCCH-AN

The IE SPS-PUCCH-AN is used to indicate a PUCCH resource for HARQ ACK and configure the corresponding maximum payload size for the PUCCH resource.

SPS-PUCCH-AN information element

— ASN1START

— TAG-SPS-PUCCH-AN-START

SPS-PUCCH-AN-r16 ::= SEQUENCE {

sps-PUCCH-AN-ResourceID-r16 PUCCH-ResourceId,

maxPayloadSize-r16 INTEGER (4..256) OPTIONAL — Need R

}

— TAG-SPS-PUCCH-AN-STOP

— ASN1STOP

SPS-PUCCH-AN field descriptions

maxPayloadSize Indicates the maximum payload size for the corresponding PUCCH resource ID.

sps-PUCCH-AN-ResourceID Indicates the PUCCH resource ID

– SPS-PUCCH-AN-List

The IE SPS-PUCCH-AN-List is used to configure the list of PUCCH resources per HARQ ACK codebook

SPS-PUCCH-AN-List information element

— ASN1START

— TAG-SPS-PUCCH-AN-LIST-START

SPS-PUCCH-AN-List-r16 ::= SEQUENCE (SIZE(1..4)) OF SPS-PUCCH-AN-r16

— TAG-SPS-PUCCH-AN-LIST-STOP

— ASN1STOP

– SRB-Identity

The IE SRB-Identity is used to identify a Signalling Radio Bearer (SRB) used by a UE.

SRB-Identity information element

— ASN1START

— TAG-SRB-IDENTITY-START

SRB-Identity ::= INTEGER (1..3)

SRB-Identity-v1700 ::= INTEGER (4)

— TAG-SRB-IDENTITY-STOP

— ASN1STOP

– SRS-CarrierSwitching

The IE SRS-CarrierSwitching is used to configure for SRS carrier switching when PUSCH is not configured and independent SRS power control from that of PUSCH.

SRS-CarrierSwitching information element

— ASN1START

— TAG-SRS-CARRIERSWITCHING-START

SRS-CarrierSwitching ::= SEQUENCE {

srs-SwitchFromServCellIndex INTEGER (0..31) OPTIONAL, — Need M

srs-SwitchFromCarrier ENUMERATED {sUL, nUL},

srs-TPC-PDCCH-Group CHOICE {

typeA SEQUENCE (SIZE (1..32)) OF SRS-TPC-PDCCH-Config,

typeB SRS-TPC-PDCCH-Config

} OPTIONAL, — Need M

monitoringCells SEQUENCE (SIZE (1..maxNrofServingCells)) OF ServCellIndex OPTIONAL, — Need M

…

}

SRS-TPC-PDCCH-Config ::= SEQUENCE {

srs-CC-SetIndexlist SEQUENCE (SIZE(1..4)) OF SRS-CC-SetIndex OPTIONAL — Need M

}

SRS-CC-SetIndex ::= SEQUENCE {

cc-SetIndex INTEGER (0..3) OPTIONAL, — Need M

cc-IndexInOneCC-Set INTEGER (0..7) OPTIONAL — Need M

}

— TAG-SRS-CARRIERSWITCHING-STOP

— ASN1STOP

SRS-CC-SetIndex field descriptions

cc-IndexInOneCC-Set Indicates the CC index in one CC set for Type A (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA.

cc-SetIndex Indicates the CC set index for Type A associated (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA. The network does not configure this field to 3 in this release of specification.

SRS-CarrierSwitching field descriptions

monitoringCells A set of serving cells for monitoring PDCCH conveying SRS DCI format with CRC scrambled by TPC-SRS-RNTI (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.3).

srs-SwitchFromServCellIndex Indicates the serving cell whose UL transmission may be interrupted during SRS transmission on a PUSCH-less SCell. During SRS transmission on a PUSCH-less SCell, the UE may temporarily suspend the UL transmission on a serving cell with PUSCH in the same CG to allow the PUSCH-less SCell to transmit SRS. (see TS 38.214 [19], clause 6.2.1.3).

srs-TPC-PDCCH-Group Network configures the UE with either typeA-SRS-TPC-PDCCH-Group or typeB-SRS-TPC-PDCCH-Group, if any.

typeA Type A trigger configuration for SRS transmission on a PUSCH-less SCell (see TS 38.213 [13], clause 11.4). In this release, the network configures at most one entry (the first entry) of typeA, and the first entry corresponds to the serving cell in which the SRS-CarrierSwitching field is configured. SRS carrier switching to SUL carrier is not supported in this version of the specification.

typeB Type B trigger configuration for SRS transmission on a PUSCH-less SCell (see TS 38.213 [13], clause 11.4).

SRS-TPC-PDCCH-Config field descriptions

srs-CC-SetIndexlist A list of pairs of [cc-SetIndex; cc-IndexInOneCC-Set] (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network does not configure this field for typeB.

– SRS-Config

The IE SRS-Config is used to configure sounding reference signal transmissions. The configuration defines a list of SRS-Resources, a list of SRS-PosResources, a list of SRS-PosResourceSets and a list of SRS-ResourceSets. Each resource set defines a set of SRS-Resources or SRS-PosResources. The network triggers the transmission of the set of SRS-Resources or SRS-PosResources using a configured aperiodicSRS-ResourceTrigger (L1 DCI). The network does not configure SRS specific power control parameters, alpha, p0 or pathlossReferenceRS if unifiedTCI-StateType is configured for the serving cell.

SRS-Config information element

— ASN1START

— TAG-SRS-CONFIG-START

SRS-Config ::= SEQUENCE {

srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, — Need N

srs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, — Need N

srs-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, — Need N

srs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, — Need N

tpc-Accumulation ENUMERATED {disabled} OPTIONAL, — Need S

…,

[[

srs-RequestDCI-1-2-r16 INTEGER (1..2) OPTIONAL, — Need S

srs-RequestDCI-0-2-r16 INTEGER (1..2) OPTIONAL, — Need S

srs-ResourceSetToAddModListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, — Need N

srs-ResourceSetToReleaseListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, — Need N

srs-PosResourceSetToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16

OPTIONAL, — Need N

srs-PosResourceSetToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSet-r16 OPTIONAL,– Need N

srs-PosResourceToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16 OPTIONAL,– Need N

srs-PosResourceToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResource-r16 OPTIONAL — Need N

]]

}

SRS-ResourceSet ::= SEQUENCE {

srs-ResourceSetId SRS-ResourceSetId,

srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, — Cond Setup

resourceType CHOICE {

aperiodic SEQUENCE {

aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1),

csi-RS NZP-CSI-RS-ResourceId OPTIONAL, — Cond NonCodebook

slotOffset INTEGER (1..32) OPTIONAL, — Need S

…,

[[

aperiodicSRS-ResourceTriggerList SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2))

OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL — Need M

]]

},

semi-persistent SEQUENCE {

associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, — Cond NonCodebook

…

},

periodic SEQUENCE {

associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, — Cond NonCodebook

…

}

},

usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching},

alpha Alpha OPTIONAL, — Need S

p0 INTEGER (-202..24) OPTIONAL, — Cond Setup

pathlossReferenceRS PathlossReferenceRS-Config OPTIONAL, — Need M

srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, — Need S

…,

[[

pathlossReferenceRSList-r16 SetupRelease { PathlossReferenceRSList-r16} OPTIONAL — Need M

]],

[[

usagePDC-r17 ENUMERATED {true} OPTIONAL, — Need R

availableSlotOffsetList-r17 SEQUENCE (SIZE(1..4)) OF AvailableSlotOffset-r17 OPTIONAL, — Need R

followUnifiedTCIstateSRS-r17 ENUMERATED {enabled} OPTIONAL — Need R

]]

}

AvailableSlotOffset-r17 ::= INTEGER (0..7)

PathlossReferenceRS-Config ::= CHOICE {

ssb-Index SSB-Index,

csi-RS-Index NZP-CSI-RS-ResourceId

}

PathlossReferenceRSList-r16 ::= SEQUENCE (SIZE (1..maxNrofSRS-PathlossReferenceRS-r16)) OF PathlossReferenceRS-r16

PathlossReferenceRS-r16 ::= SEQUENCE {

srs-PathlossReferenceRS-Id-r16 SRS-PathlossReferenceRS-Id-r16,

pathlossReferenceRS-r16 PathlossReferenceRS-Config

}

SRS-PathlossReferenceRS-Id-r16 ::= INTEGER (0..maxNrofSRS-PathlossReferenceRS-1-r16)

SRS-PosResourceSet-r16 ::= SEQUENCE {

srs-PosResourceSetId-r16 SRS-PosResourceSetId-r16,

srs-PosResourceIdList-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-PosResourceId-r16

OPTIONAL, — Cond Setup

resourceType-r16 CHOICE {

aperiodic-r16 SEQUENCE {

aperiodicSRS-ResourceTriggerList-r16 SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-1))

OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL, — Need M

…

},

semi-persistent-r16 SEQUENCE {

…

},

periodic-r16 SEQUENCE {

…

}

},

alpha-r16 Alpha OPTIONAL, — Need S

p0-r16 INTEGER (-202..24) OPTIONAL, — Cond Setup

pathlossReferenceRS-Pos-r16 CHOICE {

ssb-IndexServing-r16 SSB-Index,

ssb-Ncell-r16 SSB-InfoNcell-r16,

dl-PRS-r16 DL-PRS-Info-r16

} OPTIONAL, — Need M

…

}

SRS-ResourceSetId ::= INTEGER (0..maxNrofSRS-ResourceSets-1)

SRS-PosResourceSetId-r16 ::= INTEGER (0..maxNrofSRS-PosResourceSets-1-r16)

SRS-Resource ::= SEQUENCE {

srs-ResourceId SRS-ResourceId,

nrofSRS-Ports ENUMERATED {port1, ports2, ports4},

ptrs-PortIndex ENUMERATED {n0, n1 } OPTIONAL, — Need R

transmissionComb CHOICE {

n2 SEQUENCE {

combOffset-n2 INTEGER (0..1),

cyclicShift-n2 INTEGER (0..7)

},

n4 SEQUENCE {

combOffset-n4 INTEGER (0..3),

cyclicShift-n4 INTEGER (0..11)

}

},

resourceMapping SEQUENCE {

startPosition INTEGER (0..5),

nrofSymbols ENUMERATED {n1, n2, n4},

repetitionFactor ENUMERATED {n1, n2, n4}

},

freqDomainPosition INTEGER (0..67),

freqDomainShift INTEGER (0..268),

freqHopping SEQUENCE {

c-SRS INTEGER (0..63),

b-SRS INTEGER (0..3),

b-hop INTEGER (0..3)

},

groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping },

resourceType CHOICE {

aperiodic SEQUENCE {

…

},

semi-persistent SEQUENCE {

periodicityAndOffset-sp SRS-PeriodicityAndOffset,

…

},

periodic SEQUENCE {

periodicityAndOffset-p SRS-PeriodicityAndOffset,

…

}

},

sequenceId INTEGER (0..1023),

spatialRelationInfo SRS-SpatialRelationInfo OPTIONAL, — Need R

…,

[[

resourceMapping-r16 SEQUENCE {

startPosition-r16 INTEGER (0..13),

nrofSymbols-r16 ENUMERATED {n1, n2, n4},

repetitionFactor-r16 ENUMERATED {n1, n2, n4}

} OPTIONAL — Need R

]],

[[

spatialRelationInfo-PDC-r17 SetupRelease { SpatialRelationInfo-PDC-r17 } OPTIONAL, — Need M

resourceMapping-r17 SEQUENCE {

startPosition-r17 INTEGER (0..13),

nrofSymbols-r17 ENUMERATED {n1, n2, n4, n8, n10, n12, n14},

repetitionFactor-r17 ENUMERATED {n1, n2, n4, n5, n6, n7, n8, n10, n12, n14}

} OPTIONAL, — Need R

partialFreqSounding-r17 SEQUENCE {

startRBIndexFScaling-r17 CHOICE{

startRBIndexAndFreqScalingFactor2-r17 INTEGER (0..1),

startRBIndexAndFreqScalingFactor4-r17 INTEGER (0..3)

},

enableStartRBHopping-r17 ENUMERATED {enable} OPTIONAL — Need R

} OPTIONAL, — Need R

transmissionComb-n8-r17 SEQUENCE {

combOffset-n8-r17 INTEGER (0..7),

cyclicShift-n8-r17 INTEGER (0..5)

} OPTIONAL, — Need R

srs-TCIState-r17 CHOICE {

srs-UL-TCIState-r17 TCI-UL-State-Id-r17,

srs-DLorJoint-TCIState-r17 TCI-StateId

} OPTIONAL — Need R

]]

}

SRS-PosResource-r16::= SEQUENCE {

srs-PosResourceId-r16 SRS-PosResourceId-r16,

transmissionComb-r16 CHOICE {

n2-r16 SEQUENCE {

combOffset-n2-r16 INTEGER (0..1),

cyclicShift-n2-r16 INTEGER (0..7)

},

n4-r16 SEQUENCE {

combOffset-n4-r16 INTEGER (0..3),

cyclicShift-n4-r16 INTEGER (0..11)

},

n8-r16 SEQUENCE {

combOffset-n8-r16 INTEGER (0..7),

cyclicShift-n8-r16 INTEGER (0..5)

},

…

},

resourceMapping-r16 SEQUENCE {

startPosition-r16 INTEGER (0..13),

nrofSymbols-r16 ENUMERATED {n1, n2, n4, n8, n12}

},

freqDomainShift-r16 INTEGER (0..268),

freqHopping-r16 SEQUENCE {

c-SRS-r16 INTEGER (0..63),

…

},

groupOrSequenceHopping-r16 ENUMERATED { neither, groupHopping, sequenceHopping },

resourceType-r16 CHOICE {

aperiodic-r16 SEQUENCE {

slotOffset-r16 INTEGER (1..32) OPTIONAL, — Need S

…

},

semi-persistent-r16 SEQUENCE {

periodicityAndOffset-sp-r16 SRS-PeriodicityAndOffset-r16,

…,

[[

periodicityAndOffset-sp-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL — Need R

]]

},

periodic-r16 SEQUENCE {

periodicityAndOffset-p-r16 SRS-PeriodicityAndOffset-r16,

…,

[[

periodicityAndOffset-p-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL — Need R

]]

}

},

sequenceId-r16 INTEGER (0..65535),

spatialRelationInfoPos-r16 SRS-SpatialRelationInfoPos-r16 OPTIONAL, — Need R

…

}

SRS-SpatialRelationInfo ::= SEQUENCE {

servingCellId ServCellIndex OPTIONAL, — Need S

referenceSignal CHOICE {

ssb-Index SSB-Index,

csi-RS-Index NZP-CSI-RS-ResourceId,

srs SEQUENCE {

resourceId SRS-ResourceId,

uplinkBWP BWP-Id

}

}

}

SRS-SpatialRelationInfoPos-r16 ::= CHOICE {

servingRS-r16 SEQUENCE {

servingCellId ServCellIndex OPTIONAL, — Need S

referenceSignal-r16 CHOICE {

ssb-IndexServing-r16 SSB-Index,

csi-RS-IndexServing-r16 NZP-CSI-RS-ResourceId,

srs-SpatialRelation-r16 SEQUENCE {

resourceSelection-r16 CHOICE {

srs-ResourceId-r16 SRS-ResourceId,

srs-PosResourceId-r16 SRS-PosResourceId-r16

},

uplinkBWP-r16 BWP-Id

}

}

},

ssb-Ncell-r16 SSB-InfoNcell-r16,

dl-PRS-r16 DL-PRS-Info-r16

}

SSB-Configuration-r16 ::= SEQUENCE {

ssb-Freq-r16 ARFCN-ValueNR,

halfFrameIndex-r16 ENUMERATED {zero, one},

ssbSubcarrierSpacing-r16 SubcarrierSpacing,

ssb-Periodicity-r16 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2,spare1 } OPTIONAL, — Need S

sfn0-Offset-r16 SEQUENCE {

sfn-Offset-r16 INTEGER (0..1023),

integerSubframeOffset-r16 INTEGER (0..9) OPTIONAL — Need R

} OPTIONAL, — Need R

sfn-SSB-Offset-r16 INTEGER (0..15),

ss-PBCH-BlockPower-r16 INTEGER (-60..50) OPTIONAL — Cond Pathloss

}

SSB-InfoNcell-r16 ::= SEQUENCE {

physicalCellId-r16 PhysCellId,

ssb-IndexNcell-r16 SSB-Index OPTIONAL, — Need S

ssb-Configuration-r16 SSB-Configuration-r16 OPTIONAL — Need S

}

DL-PRS-Info-r16 ::= SEQUENCE {

dl-PRS-ID-r16 INTEGER (0..255),

dl-PRS-ResourceSetId-r16 INTEGER (0..7),

dl-PRS-ResourceId-r16 INTEGER (0..63) OPTIONAL — Need S

}

SRS-ResourceId ::= INTEGER (0..maxNrofSRS-Resources-1)

SRS-PosResourceId-r16 ::= INTEGER (0..maxNrofSRS-PosResources-1-r16)

SRS-PeriodicityAndOffset ::= CHOICE {

sl1 NULL,

sl2 INTEGER(0..1),

sl4 INTEGER(0..3),

sl5 INTEGER(0..4),

sl8 INTEGER(0..7),

sl10 INTEGER(0..9),

sl16 INTEGER(0..15),

sl20 INTEGER(0..19),

sl32 INTEGER(0..31),

sl40 INTEGER(0..39),

sl64 INTEGER(0..63),

sl80 INTEGER(0..79),

sl160 INTEGER(0..159),

sl320 INTEGER(0..319),

sl640 INTEGER(0..639),

sl1280 INTEGER(0..1279),

sl2560 INTEGER(0..2559)

}

SRS-PeriodicityAndOffset-r16 ::= CHOICE {

sl1 NULL,

sl2 INTEGER(0..1),

sl4 INTEGER(0..3),

sl5 INTEGER(0..4),

sl8 INTEGER(0..7),

sl10 INTEGER(0..9),

sl16 INTEGER(0..15),

sl20 INTEGER(0..19),

sl32 INTEGER(0..31),

sl40 INTEGER(0..39),

sl64 INTEGER(0..63),

sl80 INTEGER(0..79),

sl160 INTEGER(0..159),

sl320 INTEGER(0..319),

sl640 INTEGER(0..639),

sl1280 INTEGER(0..1279),

sl2560 INTEGER(0..2559),

sl5120 INTEGER(0..5119),

sl10240 INTEGER(0..10239),

sl40960 INTEGER(0..40959),

sl81920 INTEGER(0..81919),

…

}

SRS-PeriodicityAndOffsetExt-r16 ::= CHOICE {

sl128 INTEGER(0..127),

sl256 INTEGER(0..255),

sl512 INTEGER(0..511),

sl20480 INTEGER(0..20479)

}

SpatialRelationInfo-PDC-r17 ::= SEQUENCE {

referenceSignal CHOICE {

ssb-Index SSB-Index,

csi-RS-Index NZP-CSI-RS-ResourceId,

dl-PRS-PDC NR-DL-PRS-ResourceID-r17,

srs SEQUENCE {

resourceId SRS-ResourceId,

uplinkBWP BWP-Id

},

…

},

…

}

— TAG-SRS-CONFIG-STOP

— ASN1STOP

SRS-Config field descriptions

tpc-Accumulation If the field is absent, UE applies TPC commands via accumulation. If disabled, UE applies the TPC command without accumulation (this applies to SRS when a separate closed loop is configured for SRS) (see TS 38.213 [13], clause 7.3).

SRS-Resource, SRS-PosResource field descriptions

cyclicShift-n2 Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1).

cyclicShift-n4 Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1).

enableStartRBHopping When this RRC parameter is configured, start RB location hopping is enabled for partial frequency sounding in different SRS frequency hopping periods for periodic/semi-persistent/aperiodic SRS as described in Clause 6.4.1.4 in TS 38.211.

freqHopping Includes parameters capturing SRS frequency hopping (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, the network always configures this field such that b-hop > b-SRS.

groupOrSequenceHopping Parameter(s) for configuring group or sequence hopping (see TS 38.211 [16], clause 6.4.1.4.2). For CLI SRS-RSRP measurement, the network always configures this parameter to ‘neither’.

nrofSRS-Ports Number of ports. For CLI SRS-RSRP measurement, the network always configures this parameter to ‘port1’.

periodicityAndOffset-p, periodicityAndOffset-p-Ext Periodicity and slot offset for this SRS resource. All values are in "number of slots". Value sl1 corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity sl1 the offset is 0 slots (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, sl1280 and sl2560 cannot be configured. For SRS-PosResource, values sl20480, sl40960 and sl81920 cannot be configured for SCS=15kHz, values sl40960 and sl81920 cannot be configured for SCS=30kHz, and value sl81920 cannot be configured for SCS=60kHz. When periodicityAndOffset-p-Ext is present, periodicityAndOffset-p shall be ignored by the UE.

periodicityAndOffset-sp, periodicityAndOffset-sp-Ext Periodicity and slot offset for this SRS resource. All values are in "number of slots". Value sl1 corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity sl1 the offset is 0 slots (see TS 38.214 [19], clause 6.2.1). For SRS-PosResource, values sl20480, sl40960 and sl81920 cannot be configured for SCS=15kHz, values sl40960 and sl81920 cannot be configured for SCS=30kHz, and value sl81920 cannot be configured for SCS=60kHz. When periodicityAndOffset-sp-Ext is present, periodicityAndOffset-sp shall be ignored by the UE.

ptrs-PortIndex The PTRS port index for this SRS resource for non-codebook based UL MIMO. This is only applicable when the corresponding PTRS-UplinkConfig is set to CP-OFDM. The ptrs-PortIndex configured here must be smaller than the maxNrofPorts configured in the PTRS-UplinkConfig (see TS 38.214 [19], clause 6.2.3.1). This parameter is not applicable to CLI SRS-RSRP measurement.

resourceMapping OFDM symbol location of the SRS resource within a slot including nrofSymbols (number of OFDM symbols), startPosition (value 0 refers to the last symbol, value 1 refers to the second last symbol, and so on) and repetitionFactor (see TS 38.214 [19], clause 6.2.1 and TS 38.211 [16], clause 6.4.1.4). The configured SRS resource does not exceed the slot boundary. If resourceMapping-r16 is signalled, UE shall ignore the resourceMapping (without suffix). If resourceMapping-r17 is signalled, UE shall ignore the resourceMapping (without suffix) and only the values of nrofSymbols which are integer multiples of the configured repetitionFactor can be configured. For CLI SRS-RSRP measurement, the network always configures nrofSymbols and repetitionFactor to ‘n1’.

resourceType Periodicity and offset for semi-persistent and periodic SRS resource (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, only ‘periodic’ is applicable for resourceType.

sequenceId Sequence ID used to initialize pseudo random group and sequence hopping (see TS 38.214 [19], clause 6.2.1).

servingCellId The serving Cell ID of the source SSB, CSI-RS, or SRS for the spatial relation of the target SRS resource. If this field is absent the SSB, the CSI-RS, or the SRS is from the same serving cell where the SRS is configured.

spatialRelationInfo Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS (see TS 38.214 [19], clause 6.2.1). This parameter is not applicable to CLI SRS-RSRP measurement.

spatialRelationInfo-PDC Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS/DL-PRS-PDC (see TS 38.214 [19], clause 6.2.1). The field is present in case of resourceType=periodic and usagePDC-r17=true in the SRS-ResourceSet, otherwise the field is absent.

spatialRelationInfoPos Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS/DL-PRS (see TS 38.214 [19], clause 6.2.1). If the IE srs-ResourceId-Ext is present, the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 63. Otherwise the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 31.

srs-RequestDCI-0-2 Indicate the number of bits for "SRS request"in DCI format 0_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 0_2 is applied. If the parameter srs-RequestDCI-0-2 is configured to value 1, 1 bit is used to indicate one of the first two rows of Table 7.3.1.1.2-24 in TS 38.212 [17] for triggered aperiodic SRS resource set. If the value 2 is configured, 2 bits are used to indicate one of the rows of Table 7.3.1.1.2-24 in TS 38.212 [17]. When UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication.

srs-RequestDCI-1-2 Indicate the number of bits for "SRS request" in DCI format 1_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 1_2 is applied. When the UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication (see TS 38.214 [19], clause 6.1.1.2).

srs-ResourceSetToAddModListDCI-0-2 List of SRS resource set to be added or modified for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).

srs-ResourceSetToReleaseListDCI-0-2 List of SRS resource set to be released for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).

srs-TCIState Configuration of either a UL TCI state or a joint TCI state for the SRS resource. This field is absent when the SRS resource is in a SRS-ResourceSet configured with followUnifiedTCIstateSRS-r17 or when the field unifiedTCI-StateType is not configured to the serving cell which the SRS resource is located in.

startRBIndexAndFreqScalingFactor Configures the UE with the startRBIndex and freqScalingFactor for partial frequency sounding as described in Clause 6.4.1.4 in TS 38.211. The startRBIndexForFScaling2 gives the startRBIndex when freqScalingFactor is 2 and the startRBIndexForFScaling4 gives the startRBIndex when FreqScalingFactor is 4

transmissionComb, transmissionComb-n8 Comb value (2 or 4 or 8) and comb offset (0..combValue-1) (see TS 38.214 [19], clause 6.2.1).

SRS-ResourceSet, SRS-PosResourceSet field descriptions

alpha alpha value for SRS power control (see TS 38.213 [13], clause 7.3). When the field is absent the UE applies the value 1.

aperiodicSRS-ResourceTriggerList An additional list of DCI "code points" upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6). When the field is not included during a reconfiguration of SRS-ResourceSet of resourceType set to aperiodic, UE maintains this value based on the Need M; that is, this list is not considered as an extension of aperiodicSRS-ResourceTrigger for purpose of applying the general rule for extended list in clause 6.1.3.

aperiodicSRS-ResourceTrigger The DCI "code point" upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6).

associatedCSI-RS ID of CSI-RS resource associated with this SRS resource set in non-codebook based operation (see TS 38.214 [19], clause 6.1.1.2).

availableSlotOffset Indicates the number of available slots from slot n+k to the slot where the aperiodic SRS resource set is transmitted, where slot n is the slot with the triggering DCI, and k is the legacy triggering offset (slotOffset, not based on availabel slot) as described in clause 6.2.1 of TS 38.214.

csi-RS ID of CSI-RS resource associated with this SRS resource set. (see TS 38.214 [19], clause 6.1.1.2).

csi-RS-IndexServingcell Indicates CSI-RS index belonging to a serving cell

followUnifiedTCIstateSRS When set to enabled, for SRS resource Set, the UE applies the "indicated" UL only TCI or joint TCI as specified in TS 38.214 clause 5.1.5. This parameter may be configured for aperiodic SRS for BM or SRS of any time-domain behavior for codebook, non-codebook, and antenna switching.

p0 P0 value for SRS power control. The value is in dBm. Only even values (step size 2) are allowed (see TS 38.213 [13], clause 7.3).

pathlossReferenceRS A reference signal (e.g. a CSI-RS config or a SS block) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3).

pathlossReferenceRS-Pos A reference signal (e.g. a SS block or a DL-PRS config) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3).

pathlossReferenceRSList Multiple candidate pathloss reference RS(s) for SRS power control, where one candidate RS can be mapped to SRS Resource Set via MAC CE (clause 6.1.3.27 in TS 38.321 [3]). The network can only configure this field if pathlossReferenceRS is not configured in the same SRS-ResourceSet.

resourceSelection Indicates whether the configured SRS spatial relation resource is a SRS-Resource or SRS-PosResource.

resourceType Time domain behavior of SRS resource configuration, see TS 38.214 [19], clause 6.2.1. The network configures SRS resources in the same resource set with the same time domain behavior on periodic, aperiodic and semi-persistent SRS. The aperiodic SRS is not applicable for the UE in RRC_INACTIVE.

slotOffset An offset in number of slots between the triggering DCI and the actual transmission of this SRS-ResourceSet. If the field is absent the UE applies no offset (value 0).

srs-PowerControlAdjustmentStates Indicates whether hsrs,c(i) = fc(i,1) or hsrs,c(i) = fc(i,2) (if twoPUSCH-PC-AdjustmentStates are configured) or separate close loop is configured for SRS. This parameter is applicable only for Uls on which UE also transmits PUSCH. If absent or release, the UE applies the value sameAs-Fci1 (see TS 38.213 [13], clause 7.3).

srs-ResourceIdList, srs-PosResourceIdList The IDs of the SRS-Resources/SRS-PosResource used in this SRS-ResourceSet/SRS-PosResourceSet. If this SRS-ResourceSet is configured with usage set to codebook, the srs-ResourceIdList contains at most 2 entries. If this SRS-ResourceSet is configured with usage set to nonCodebook, the srs-ResourceIdList contains at most 4 entries.

srs-ResourceSetId, srs-PosResourceSetId The ID of this resource set. It is unique in the context of the BWP in which the parent SRS-Config is defined.

ssb-IndexSevingcell Indicates SSB index belonging to a serving cell

ssb-NCell This field indicates a SSB configuration from neighboring cell

usage Indicates if the SRS resource set is used for beam management, codebook based or non-codebook based transmission or antenna switching. See TS 38.214 [19], clause 6.2.1. Reconfiguration between codebook based and non-codebook based transmission is not supported.

usagePDC If configured, it indicates that this SRS resource set is used for propagation delay compensation. The field can be present in only one SRS-ResourceSet.

SSB-InfoNCell field descriptions

physicalCellId This field specifies the physical cell ID of the neighbour cell for which SSB configuration is provided.

ssb-IndexNcell This field specifies the index of the SSB for a neighbour cell. See TS 38.213 [13]. If this field is absent, the UE determines the ssb-IndexNcell of the physicalCellId based on its SSB measurement from the cell.

ssb-Configuration This field specifies the full configuration of the SSB. If this field is absent, the UE obtains the configuration for the SSB from nr-SSB-Config received as part of DL-PRS assistance data in LPP, see TS 37.355 [49], by looking up the corresponding SSB configuration using the field physicalCellId.

DL-PRS-Info field descriptions

dl-PRS-ID This field specifies the UE specific TRP ID (see TS 37.355 [49]) for which PRS configuration is provided.

dl-PRS-ResourceSetId This field specifies the PRS-ResourceSet ID of a PRS resourceSet.

dl-PRS-ResourceId This field specifies the PRS-Resource ID of a PRS resource. If this field is absent, the UE determines the dl-PRS-ResourceID based on its PRS measurement from the TRP (see TS 37.355 [49]) and DL-PRS Resource Set.

SSB-Configuration field descriptions

halfFrameIndex Indicates whether SSB is in the first half or the second half of the frame. Value zero indicates the first half and value 1 indicates the second half.

integerSubframeOffset Indicates the subframe boundary offset of the cell in which SSB is transmited.

sfn0-Offset Indiactes the time offset of the SFN0 slot 0 for the cell with respect to SFN0 slot 0 of serving cell.

sfn-Offset Specifies the SFN offset between the cell in which SSB is transmited and serving cell. The offset corresponds to the number of full radio frames counted from the beginning of a radio frame #0 of serving cell to the beginning of the closest subsequent radio frame #0 of the cell in which SSB is transmitted.

sfn-SSB-Offset Indicates the SFN offset of the transmitted SSB relative to the start of the SSB period. Value 0 indicates that the SSB is transmitted in the first system frame, value 1 indicates that SSB is transmitted in the second system frame and so on. The network configures this field according to the field ssb-Periodicity such that the indicated system frame does not exceed the configured SSB periodicity.

ssb-Freq Indicates the frequency of the SSB.

ss-PBCH-BlockPower Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7.

ssb-Periodicity Indicates the periodicity of the SSB. If the field is absent, the UE applies the value ms5. (see TS 38.213 [13], clause 4.1)

ssbSubcarrierSpacing Subcarrier spacing of SSB. Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 120 or 240 kHz FR2-2: 120, 480, or 960 kHz

Conditional Presence	Explanation
Setup	This field is mandatory present upon configuration of SRS-ResourceSet or SRS-Resource and optionally present, Need M, otherwise.
NonCodebook	This field is optionally present, Need M, in case of non-codebook based transmission, otherwise the field is absent.
Pathloss	The field is mandatory present if the IE SSB-InfoNcell is included in pathlossReferenceRS-Pos; otherwise it is optionally present, Need R

– SRS-RSRP-Range

The IE SRS-RSRP-Range specifies the value range used in SRS-RSRP measurements and thresholds. The integer value for SRS-RSRP measurements is according to Table 10.1.22.1.2-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value –140) dBm, except for the IE value 98, in which case the actual value is infinity.

SRS-RSRP-Range information element

— ASN1START

— TAG-SRS-RSRP-RANGE-START

SRS-RSRP-Range-r16 ::= INTEGER(0..98)

— TAG-SRS-RSRP-RANGE-STOP

— ASN1STOP

– SRS-TPC-CommandConfig

The IE SRS-TPC-CommandConfig is used to configure the UE for extracting TPC commands for SRS from a group-TPC messages on DCI

SRS-TPC-CommandConfig information element

— ASN1START

— TAG-SRS-TPC-COMMANDCONFIG-START

SRS-TPC-CommandConfig ::= SEQUENCE {

startingBitOfFormat2-3 INTEGER (1..31) OPTIONAL, — Need R

fieldTypeFormat2-3 INTEGER (0..1) OPTIONAL, — Need R

…,

[[

startingBitOfFormat2-3SUL INTEGER (1..31) OPTIONAL — Need R

]]

}

— TAG-SRS-TPC-COMMANDCONFIG-STOP

— ASN1STOP

SRS-TPC-CommandConfig field descriptions

fieldTypeFormat2-3 The type of a field within the group DCI with SRS request fields (optional), which indicates how many bits in the field are for SRS request (0 or 2). Note that for Type A, there is a common SRS request field for all SCells in the set, but each SCell has its own TPC command bits. See TS 38.212 [17] clause 7.3.1 and , TS 38.213 [13], clause 11.3.

startingBitOfFormat2-3 The starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands. The value 1 of the field corresponds to the first/left most bit of format2-3. The value 2 of the field corresponds to the second bit format2-3, and so on (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11.3).

startingBitOfFormat2-3SUL The starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands for SUL carrier (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11.3).

– SSB-Index

The IE SSB-Index identifies an SS-Block within an SS-Burst. See TS 38.213 [13], clause 4.1.

SSB-Index information element

— ASN1START

— TAG-SSB-INDEX-START

SSB-Index ::= INTEGER (0..maxNrofSSBs-1)

— TAG-SSB-INDEX-STOP

— ASN1STOP

– SSB-MTC

The IE SSB-MTC is used to configure measurement timing configurations, i.e., timing occasions at which the UE measures SSBs.

SSB-MTC information element

— ASN1START

— TAG-SSB-MTC-START

SSB-MTC ::= SEQUENCE {

periodicityAndOffset CHOICE {

sf5 INTEGER (0..4),

sf10 INTEGER (0..9),

sf20 INTEGER (0..19),

sf40 INTEGER (0..39),

sf80 INTEGER (0..79),

sf160 INTEGER (0..159)

},

duration ENUMERATED { sf1, sf2, sf3, sf4, sf5 }

}

SSB-MTC2 ::= SEQUENCE {

pci-List SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, — Need M

periodicity ENUMERATED {sf5, sf10, sf20, sf40, sf80, spare3, spare2, spare1}

}

SSB-MTC2-LP-r16 ::= SEQUENCE {

pci-List SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, — Need R

periodicity ENUMERATED {sf10, sf20, sf40, sf80, sf160, spare3, spare2, spare1}

}

SSB-MTC3-r16 ::= SEQUENCE {

periodicityAndOffset-r16 CHOICE {

sf5-r16 INTEGER (0..4),

sf10-r16 INTEGER (0..9),

sf20-r16 INTEGER (0..19),

sf40-r16 INTEGER (0..39),

sf80-r16 INTEGER (0..79),

sf160-r16 INTEGER (0..159),

sf320-r16 INTEGER (0..319),

sf640-r16 INTEGER (0..639),

sf1280-r16 INTEGER (0..1279)

},

duration-r16 ENUMERATED {sf1, sf2, sf3, sf4, sf5},

pci-List-r16 SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, — Need M

ssb-ToMeasure-r16 SetupRelease { SSB-ToMeasure } OPTIONAL — Need M

}

SSB-MTC4-r17 ::= SEQUENCE {

pci-List-r17 SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, — Need M

offset-r17 INTEGER (0..159)

}

SSB-MTC-AdditionalPCI-r17 ::= SEQUENCE {

additionalPCIIndex-r17 AdditionalPCIIndex-r17,

additionalPCI-r17 PhysCellId,

periodicity-r17 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 },

ssb-PositionsInBurst-r17 CHOICE {

shortBitmap BIT STRING (SIZE (4)),

mediumBitmap BIT STRING (SIZE (8)),

longBitmap BIT STRING (SIZE (64))

},

ss-PBCH-BlockPower-r17 INTEGER (-60..50)

}

AdditionalPCIIndex-r17 ::= INTEGER(1..maxNrofAdditionalPCI-r17)

— TAG-SSB-MTC-STOP

— ASN1STOP

SSB-MTC field descriptions

duration Duration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see TS 38.213 [13], clause 4.1).

periodicityAndOffset Periodicity and offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Periodicity and offset are given in number of subframes.

SSB-MTC2 field descriptions

pci-List PCIs that follow this SMTC.

SSB-MTC3 field descriptions

duration Duration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see TS 38.213 [13], clause 4.1).

pci-List PCIs that follow this SMTC, used for IAB-node discovery.

periodicityAndOffset Periodicity and offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Periodicity and offset are given in number of subframes.

ssb-ToMeasure The set of SS blocks to be measured within the SMTC measurement duration. The first/leftmost bit corresponds to SS block index 0, the second bit corresponds to SS block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS block is not to be measured while value 1 indicates that the corresponding SS block is to be measured (see TS 38.215 [9]). When the field is not configured the IAB-MT measures on all SS blocks. Regardless of the value of this field, SS blocks outside of the applicable smtc are not to be measured. See TS 38.215 [9] clause 5.1.1.

SSB-MTC4 field descriptions

pci-List PCIs that follow this SMTC.

offset Offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Offset is given in number of subframes.

SSB-MTC-AdditionalPCI field descriptions

additionalPCI PCI of the additional SSB different from serving cell PCI.

periodicity Periodicity of the SS/PBCH blocks, see 5.5.2.10. Periodicity is given in number of subframes.

ssb-PositionsInBurst Indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted.

ss-PBCH-BlockPower Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7.

– SSB-PositionQCL-Relation

The IE SSB-PositionQCL-Relation is used to indicate the QCL relationship between SSB positions on the frequency indicated by ssbFrequency (see TS 38.213 [13], clause 4.1) for operation with shared spectrum channel access. Value n1 corresponds to 1, value n2 corresponds to 2 and so on.

SSB-PositionQCL-Relation information element

— ASN1START

— TAG-SSB-POSITIONQCL-RELATION-START

SSB-PositionQCL-Relation-r16 ::= ENUMERATED {n1,n2,n4,n8}

SSB-PositionQCL-Relation-r17 ::= ENUMERATED {n32, n64}

— TAG-SSB-POSITIONQCL-RELATION-STOP

— ASN1STOP

– SSB-ToMeasure

The IE SSB-ToMeasure is used to configure a pattern of SSBs. For operation with shared spectrum channel access in FR1, only mediumBitmap is used, and for FR2-2, longBitmap is used.

SSB-ToMeasure information element

— ASN1START

— TAG-SSB-TOMEASURE-START

SSB-ToMeasure ::= CHOICE {

shortBitmap BIT STRING (SIZE (4)),

mediumBitmap BIT STRING (SIZE (8)),

longBitmap BIT STRING (SIZE (64))

}

— TAG-SSB-TOMEASURE-STOP

— ASN1STOP

SSB-ToMeasure field descriptions

longBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access in FR2-2, if the k-th bit is set to 1, the UE assumes that one or more SS/PBCH blocks within the SMTC measurement duration with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to (k– 1) may be transmitted; if the k-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted.

mediumBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access, if the k-th bit is set to 1, the UE assumes that one or more SS/PBCH blocks within the SMTC measurement duration with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k – 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL-Common and the number of actually transmitted SS/PBCH blocks is not larger than the number of 1’s in the bitmap. If ssb-PositionQCL is configured with a value smaller than ssb-PositionQCL-Common, only the leftmost K bits (K = ssb-PositionQCL) are applicable for the corresponding cell.

shortBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1.

– SS-RSSI-Measurement

The IE SS-RSSI-Measurement is used to configure RSSI measurements based on synchronization reference signals.

SS-RSSI-Measurement information element

— ASN1START

— TAG-SS-RSSI-MEASUREMENT-START

SS-RSSI-Measurement ::= SEQUENCE {

measurementSlots BIT STRING (SIZE (1..80)),

endSymbol INTEGER(0..3)

}

— TAG-SS-RSSI-MEASUREMENT-STOP

— ASN1STOP

SS-RSSI-Measurement field descriptions

endSymbol Within a slot that is configured for RSSI measurements (see measurementSlots) the UE measures the RSSI from symbol 0 to symbol endSymbol. This field identifies the entry in Table 5.1.3-1 in TS 38.215 [9], which determines the actual end symbol.

measurementSlots Indicates the slots in which the UE can perform RSSI measurements. The length of the BIT STRING is equal to the number of slots in the configured SMTC window (determined by the duration and by the subcarrierSpacing). The first (left-most / most significant) bit in the bitmap corresponds to the first slot in the SMTC window, the second bit in the bitmap corresponds to the second slot in the SMTC window, and so on. The UE measures in slots for which the corresponding bit in the bitmap is set to 1. In case this field is configured for a SCell with ca-SlotOffset-r16, the bits in the bitmap corresponds to the slots that are fully contained in the SMTC window.

– SubcarrierSpacing

The IE SubcarrierSpacing determines the subcarrier spacing. Restrictions applicable for certain frequencies, channels or signals are clarified in the fields that use this IE.

SubcarrierSpacing information element

— ASN1START

— TAG-SUBCARRIERSPACING-START

SubcarrierSpacing ::= ENUMERATED {kHz15, kHz30, kHz60, kHz120, kHz240, kHz480-v1700, kHz960-v1700, spare1}

— TAG-SUBCARRIERSPACING-STOP

— ASN1STOP

– TAG-Config

The IE TAG-Config is used to configure parameters for a time-alignment group.

TAG-Config information element

— ASN1START

— TAG-TAG-CONFIG-START

TAG-Config ::= SEQUENCE {

tag-ToReleaseList SEQUENCE (SIZE (1..maxNrofTAGs)) OF TAG-Id OPTIONAL, — Need N

tag-ToAddModList SEQUENCE (SIZE (1..maxNrofTAGs)) OF TAG OPTIONAL — Need N

}

TAG ::= SEQUENCE {

tag-Id TAG-Id,

timeAlignmentTimer TimeAlignmentTimer,

…

}

TAG-Id ::= INTEGER (0..maxNrofTAGs-1)

— TAG-TAG-CONFIG-STOP

— ASN1STOP

TAG field descriptions

tag-Id Indicates the TAG of the SpCell or an SCell, see TS 38.321 [3]. Uniquely identifies the TAG within the scope of a Cell Group (i.e. MCG or SCG).

timeAlignmentTimer The timeAlignmentTimer for TAG with ID tag-Id, as specified in TS 38.321 [3].

– TAR-Config

The IE TAR-Config is used to configure Timing Advance reporting in non-terrestrial networks.

TAR-Config information element

— ASN1START

— TAG-TAR-CONFIG-START

TAR-Config-r17 ::= SEQUENCE {

offsetThresholdTA-r17 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5, ms6 ,ms7, ms8, ms9, ms10, ms11, ms12,

ms13, ms14, ms15, spare13, spare12, spare11, spare10, spare9, spare8, spare7,

spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, — Need R

timingAdvanceSR-r17 ENUMERATED {enabled} OPTIONAL, — Need R

…

}

— TAG-TAR-CONFIG-STOP

— ASN1STOP

TAR-Config field descriptions

offsetThresholdTA Offset for TA reporting as specified in TS 38.321 [3]. Network only configures this parameter for MCG.

timingAdvanceSR Used to configure whether a Timing Advance report may trigger a Scheduling Request as specified in TS 38.321 [3].

– TCI-ActivatedConfig

The IE TCI-ActivatedConfig is used to provides activated TCI states for PDSCH and/or PDCCH of the PSCell or of an SCell.

TCI-ActivatedConfig information element

— ASN1START

— TAG-TCI-ACTIVATEDCONFIG-START

TCI-ActivatedConfig-r17 ::= SEQUENCE {

pdcch-TCI-r17 SEQUENCE (SIZE (1..5)) OF TCI-StateId,

pdsch-TCI-r17 BIT STRING (SIZE (1..maxNrofTCI-States))

}

— TAG-TCI-ACTIVATEDCONFIG-STOP

— ASN1STOP

TCI-ActivatedConfig field descriptions

pdcch-TCI Indicates the TCI state for PDCCH for each configured CORESET of the DL BWP to be activated at SCell activation, to be activated for the PSCell at SCG activation and/or to be used for BFD, RLM and measurements while the SCG is deactivated. The list includes exactly as many entries as CORESETs configured in this BWP, ordered by increasing values of ControlResourceSet-Id, i.e. the first entry indicates the TCI state for the configured CORESET with the lowest ControlResourceset-Id value, the second value indicates the TCI states for the configured CORESET with the second lowest ControlResourceset-Id value, and so on.

pdsch-TCI Indicates TCI states for PDSCH reception at SCell addition/activation or of the PSCell at SCG activation. This field indicates activated TCI state(s) for this BWP ordered by increasing values of TCI-StateId, i.e. the first bit indicates the activation state of the TCI state with the lowest TCI-StateId value, the second value indicates the activation status of the TCI state with the second lowest TCI-State-Id value, and so on. A bit set to 0 indicates that the corresponding TCI state is deactivated, a bit set to 1 indicates that the TCI state is activated.

– TCI-State

The IE TCI-State associates one or two DL reference signals with a corresponding quasi-colocation (QCL) type.

TCI-State information element

— ASN1START

— TAG-TCI-STATE-START

TCI-State ::= SEQUENCE {

tci-StateId TCI-StateId,

qcl-Type1 QCL-Info,

qcl-Type2 QCL-Info OPTIONAL, — Need R

…,

[[

additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, — Need R

pathlossReferenceRS-Id-r17 PUSCH-PathlossReferenceRS-Id-r17 OPTIONAL, — Cond JointTCI

ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL — Cond JointTCI

]]

}

QCL-Info ::= SEQUENCE {

cell ServCellIndex OPTIONAL, — Need R

bwp-Id BWP-Id OPTIONAL, — Cond CSI-RS-Indicated

referenceSignal CHOICE {

csi-rs NZP-CSI-RS-ResourceId,

ssb SSB-Index

},

qcl-Type ENUMERATED {typeA, typeB, typeC, typeD},

…

}

— TAG-TCI-STATE-STOP

— ASN1STOP

QCL-Info field descriptions

bwp-Id The DL BWP which the RS is located in.

cell The UE’s serving cell in which the referenceSignal is configured. If the field is absent, it applies to the serving cell in which the TCI-State is applied. The RS can be located on a serving cell other than the serving cell in which the TCI-State is configured only if the qcl-Type is configured as typeC or typeD. See TS 38.214 [19] clause 5.1.5.

referenceSignal Reference signal with which quasi-collocation information is provided as specified in TS 38.214 [19] clause 5.1.5.

qcl-Type QCL type as specified in TS 38.214 [19] clause 5.1.5.

TCI-State field descriptions

additionalPCI Indicates the physical cell IDs (PCI) of the SSBs when referenceSignal is configured as SSB for both QCL-Type1 and QCL-Type2. In case the cell is present, the additionalPCI refers to a PCI value configured in the list configured using additionalPCI-ToAddModList in the serving cell indicated by the field cell. Otherwise, it refers to a PCI value configured in a list additionalPCI-ToAddModList configured in the serving cell where the TCI-State is applied.When this field is present the cell for qcl-Type1 and qcl-Type2 is configured with same value, if present.

pathlossReferenceRS-Id The ID of the reference Signal (e.g. a CSI-RS config or a SS block) used for PUSCH path loss estimation.

qcl-Type1, qcl-Type2 QCL information for the TCI state as specified in TS 38.214 [19] clause 5.1.5.

tci-StateId ID number of the TCI state.

ul-PowerControl Configures power control parameters for PUCCH, PUSCH and SRS for this TCI state. The field is present here only if ul-powerControl is not configured in any BWP-Uplink-Dedicated of this serving cell.

Conditional Presence	Explanation
CSI-RS-Indicated	This field is mandatory present if csi-rs is included, absent otherwise
JointTCI	This field is optionally present, Need R,if this serving cell is configured with unifiedTCI-StateType set to ‘joint‘. It is absent, Need R, otherwise.

– TCI-StateId

The IE TCI-StateId is used to identify one TCI-State configuration.

TCI-StateId information element

— ASN1START

— TAG-TCI-STATEID-START

TCI-StateId ::= INTEGER (0..maxNrofTCI-States-1)

— TAG-TCI-STATEID-STOP

— ASN1STOP

– TCI-UL-State

The IE TCI-UL-State indicates the TCI state information for UL transmission.

TCI-UL-State information element

— ASN1START

— TAG-TCI-UL-STATE-START

TCI-UL-State-r17 ::= SEQUENCE {

tci-UL-State-Id-r17 TCI-UL-State-Id-r17,

servingCellId-r17 ServCellIndex OPTIONAL, — Need R

bwp-Id-r17 BWP-Id OPTIONAL, — Cond CSI-RSorSRS-Indicated

referenceSignal-r17 CHOICE {

ssb-Index-r17 SSB-Index,

csi-RS-Index-r17 NZP-CSI-RS-ResourceId,

srs-r17 SRS-ResourceId

},

additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, — Need R

ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, — Need R

pathlossReferenceRS-Id-r17 PUSCH-PathlossReferenceRS-Id-r17 OPTIONAL, — Need R

…

}

— TAG-TCI-UL-STATE-STOP

— ASN1STOP

TCI-UL-State field descriptions

additionalPCI Indicates the physical cell IDs (PCI) of the SSBs when referenceSignal is configured as SSB. In case the servingCellId is present, the additionalPCI refers to a PCI value configured in the list configured using additionalPCI-ToAddModList in the serving cell indicated by the field servingCellId. Otherwise, it refers to a PCI value configured in the list configured using additionalPCI-ToAddModList in the serving cell where the ul-TCI-StateList is applied.

bwp-Id The DL BWP which the CSI-RS is located in or UL BWP where the SRS is located in.

servingCellId The UE’s serving cell in which the referenceSignal is configured. If the field is absent, it applies to the serving cell in which the TCI-UL-State is applied.

pathlossReferenceRS-Id The ID of the reference Signal (e.g. a CSI-RS config or a SS block) used for PUSCH path loss estimation.

ul-powerControl Configures power control parameters for PUCCH, PUSCH and SRS for this TCI state. The field is present here only if ul-powerControl is not configured in any BWP-Uplink-Dedicated of this serving cell.

Conditional Presence	Explanation
CSI-RSorSRS-Indicated	This field is mandatory present if referenceSignal is set to csi-RS-index or to srs, absent otherwise

– TCI-UL-StateId

The IE TCI-UL-StateId is used to identify one TCI-UL-State configuration.

TCI-UL-StateId information element

— ASN1START

— TAG-TCI-UL-STATEID-START

TCI-UL-State-Id-r17 ::= INTEGER (0..maxUL-TCI-1-r17)

— TAG-TCI-UL-STATEID-STOP

— ASN1STOP

– TDD-UL-DL-ConfigCommon

The IE TDD-UL-DL-ConfigCommon determines the cell specific Uplink/Downlink TDD configuration.

TDD-UL-DL-ConfigCommon information element

— ASN1START

— TAG-TDD-UL-DL-CONFIGCOMMON-START

TDD-UL-DL-ConfigCommon ::= SEQUENCE {

referenceSubcarrierSpacing SubcarrierSpacing,

pattern1 TDD-UL-DL-Pattern,

pattern2 TDD-UL-DL-Pattern OPTIONAL, — Need R

…

}

TDD-UL-DL-Pattern ::= SEQUENCE {

dl-UL-TransmissionPeriodicity ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10},

nrofDownlinkSlots INTEGER (0..maxNrofSlots),

nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1),

nrofUplinkSlots INTEGER (0..maxNrofSlots),

nrofUplinkSymbols INTEGER (0..maxNrofSymbols-1),

…,

[[

dl-UL-TransmissionPeriodicity-v1530 ENUMERATED {ms3, ms4} OPTIONAL — Need R

]]

}

— TAG-TDD-UL-DL-CONFIGCOMMON-STOP

— ASN1STOP

TDD-UL-DL-ConfigCommon field descriptions

referenceSubcarrierSpacing Reference SCS used to determine the time domain boundaries in the UL-DL pattern which must be common across all subcarrier specific carriers, i.e., independent of the actual subcarrier spacing using for data transmission. Only the following values are applicable depending on the used frequency: FR1: 15, 30, or 60 kHz FR2-1: 60 or 120 kHz FR2-2: 120, 480, or 960 kHz The network configures a not larger than any SCS of configured BWPs for the serving cell. The network or SL-PreconfigGeneral configures a not larger than the SCS of (pre-)configured SL BWP.See TS 38.213 [13], clause 11.1.

TDD-UL-DL-Pattern field descriptions

dl-UL-TransmissionPeriodicity Periodicity of the DL-UL pattern, see TS 38.213 [13], clause 11.1. If the dl-UL-TransmissionPeriodicity-v1530 is signalled, UE shall ignore the dl-UL-TransmissionPeriodicity (without suffix).

nrofDownlinkSlots Number of consecutive full DL slots at the beginning of each DL-UL pattern, see TS 38.213 [13], clause 11.1. In this release, the maximum value for this field is 80.

nrofDownlinkSymbols Number of consecutive DL symbols in the beginning of the slot following the last full DL slot (as derived from nrofDownlinkSlots). The value 0 indicates that there is no partial-downlink slot. (see TS 38.213 [13], clause 11.1).

nrofUplinkSlots Number of consecutive full UL slots at the end of each DL-UL pattern, see TS 38.213 [13], clause 11.1. In this release, the maximum value for this field is 80.

nrofUplinkSymbols Number of consecutive UL symbols in the end of the slot preceding the first full UL slot (as derived from nrofUplinkSlots). The value 0 indicates that there is no partial-uplink slot. (see TS 38.213 [13], clause 11.1).

– TDD-UL-DL-ConfigDedicated

The IE TDD-UL-DL-ConfigDedicated determines the UE-specific Uplink/Downlink TDD configuration.

TDD-UL-DL-ConfigDedicated information element

— ASN1START

— TAG-TDD-UL-DL-CONFIGDEDICATED-START

TDD-UL-DL-ConfigDedicated ::= SEQUENCE {

slotSpecificConfigurationsToAddModList SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig OPTIONAL, — Need N

slotSpecificConfigurationsToReleaseList SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, — Need N

…

}

TDD-UL-DL-ConfigDedicated-IAB-MT-r16::= SEQUENCE {

slotSpecificConfigurationsToAddModList-IAB-MT-r16 SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig-IAB-MT-r16 OPTIONAL, — Need N

slotSpecificConfigurationsToReleaseList-IAB-MT-r16 SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, — Need N

…

}

TDD-UL-DL-SlotConfig ::= SEQUENCE {

slotIndex TDD-UL-DL-SlotIndex,

symbols CHOICE {

allDownlink NULL,

allUplink NULL,

explicit SEQUENCE {

nrofDownlinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL, — Need S

nrofUplinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL — Need S

}

}

}

TDD-UL-DL-SlotConfig-IAB-MT-r16::= SEQUENCE {

slotIndex-r16 TDD-UL-DL-SlotIndex,

symbols-IAB-MT-r16 CHOICE {

allDownlink-r16 NULL,

allUplink-r16 NULL,

explicit-r16 SEQUENCE {

nrofDownlinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, — Need S

nrofUplinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL — Need S

},

explicit-IAB-MT-r16 SEQUENCE {

nrofDownlinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, — Need S

nrofUplinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL — Need S

}

}

}

TDD-UL-DL-SlotIndex ::= INTEGER (0..maxNrofSlots-1)

— TAG-TDD-UL-DL-CONFIGDEDICATED-STOP

— ASN1STOP

TDD-UL-DL-ConfigDedicated field descriptions

slotSpecificConfigurationsToAddModList The slotSpecificConfigurationToAddModList allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon, see TS 38.213 [13], clause 11.1.

TDD-UL-DL-ConfigDedicated-IAB-MT field descriptions

slotSpecificConfigurationsToAddModList-IAB-MT The slotSpecificConfigurationToAddModList-IAB-MT allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon with a limitation that effectively only flexible symbols can be overwritten in Rel-16.

slotSpecificConfigurationsToReleaseList-IAB-MT The slotSpecificConfigurationsToReleaseList-IAB-MT allows release of a set of slot configuration previously add with slotSpecificConfigurationToAddModList-IAB-MT.

TDD-UL-DL-SlotConfig field descriptions

nrofDownlinkSymbols Number of consecutive DL symbols in the beginning of the slot identified by slotIndex. If the field is absent the UE assumes that there are no leading DL symbols. (see TS 38.213 [13], clause 11.1).

nrofUplinkSymbols Number of consecutive UL symbols in the end of the slot identified by slotIndex. If the field is absent the UE assumes that there are no trailing UL symbols. (see TS 38.213 [13], clause 11.1).

slotIndex Identifies a slot within a slot configuration period given in tdd-UL-DL-configurationCommon, see TS 38.213 [13], clause 11.1.

symbols The direction (downlink or uplink) for the symbols in this slot. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively.

TDD-UL-DL-SlotConfig-IAB-MT field descriptions

symbols-IAB-MT The symbols-IAB-MT is used to configure an IAB-MT with the SlotConfig applicable for one serving cell. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively; value explicit-IAB-MT indicates explicitly how many symbols in the beginning and end of this slot are allocated to uplink and downlink, respectively.

– TrackingAreaCode

The IE TrackingAreaCode is used to identify a tracking area within the scope of a PLMN/SNPN, see TS 24.501 [23].

TrackingAreaCode information element

— ASN1START

— TAG-TRACKINGAREACODE-START

TrackingAreaCode ::= BIT STRING (SIZE (24))

— TAG-TRACKINGAREACODE-STOP

— ASN1STOP

– T-Reselection

The IE T-Reselection concerns the cell reselection timer Treselection_RAT for NR and E-UTRA. Value in seconds. For value 0, behaviour as specified in 7.1.2 applies.

T-Reselection information element

— ASN1START

— TAG-TRESELECTION-START

T-Reselection ::= INTEGER (0..7)

— TAG-TRESELECTION-STOP

— ASN1STOP

– TimeAlignmentTimer

The IE TimeAlignmentTimer is used to configure the time alignment timer as specified in TS 38.321 [3]. The values are in ms.

TimeAlignmentTimer information element

— ASN1START

— TAG-TIMEALIGNMENTTIMER-START

TimeAlignmentTimer ::= ENUMERATED {ms500, ms750, ms1280, ms1920, ms2560, ms5120, ms10240, infinity}

— TAG-TIMEALIGNMENTTIMER-STOP

— ASN1STOP

– TimeToTrigger

The IE TimeToTrigger specifies the value range used for time to trigger parameter, which concerns the time during which specific criteria for the event needs to be met in order to trigger a measurement report. Value ms0 corresponds to 0 ms and behaviour as specified in 7.1.2 applies, value ms40 corresponds to 40 ms, and so on.

TimeToTrigger information element

— ASN1START

— TAG-TIMETOTRIGGER-START

TimeToTrigger ::= ENUMERATED {

ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256,

ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560,

ms5120}

— TAG-TIMETOTRIGGER-STOP

— ASN1STOP

– UAC-BarringInfoSetIndex

The IE UAC-BarringInfoSetIndex provides the index of the entry in uac-BarringInfoSetList. Value 1 corresponds to the first entry in uac-BarringInfoSetList, value 2 corresponds to the second entry in this list and so on. An index value referring to an entry not included in uac-BarringInfoSetList indicates no barring.

UAC-BarringInfoSetIndex information element

— ASN1START

— TAG-UAC-BARRINGINFOSETINDEX-START

UAC-BarringInfoSetIndex ::= INTEGER (1..maxBarringInfoSet)

— TAG-UAC-BARRINGINFOSETINDEX-STOP

— ASN1STOP

– UAC-BarringInfoSetList

The IE UAC-BarringInfoSetList provides a list of access control parameter sets. An access category can be configured with access parameters according to one of the sets.

UAC-BarringInfoSetList information element

— ASN1START

— TAG-UAC-BARRINGINFOSETLIST-START

UAC-BarringInfoSetList ::= SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet

UAC-BarringInfoSetList-v1700 ::= SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet-v1700

UAC-BarringInfoSet ::= SEQUENCE {

uac-BarringFactor ENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40,

p50, p60, p70, p75, p80, p85, p90, p95},

uac-BarringTime ENUMERATED {s4, s8, s16, s32, s64, s128, s256, s512},

uac-BarringForAccessIdentity BIT STRING (SIZE(7))

}

UAC-BarringInfoSet-v1700 ::= SEQUENCE {

uac-BarringFactorForAI3-r17 ENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40, p50, p60, p70, p75, p80, p85, p90, p95}

OPTIONAL — Need S

}

— TAG-UAC-BARRINGINFOSETLIST-STOP

— ASN1STOP

UAC-BarringInfoSetList field descriptions

uac-BarringInfoSetList List of access control parameter sets. Each access category can be configured with access parameters corresponding to a particular set by uac-barringInfoSetIndex. Association of an access category with an index that has no corresponding entry in the uac-BarringInfoSetList is valid configuration and indicates no barring.

uac-BarringForAccessIdentity Indicates whether access attempt is allowed for each Access Identity. The leftmost bit, bit 0 in the bit string corresponds to Access Identity 1, bit 1 in the bit string corresponds to Access Identity 2, bit 2 in the bit string corresponds to Access Identity 11, bit 3 in the bit string corresponds to Access Identity 12, bit 4 in the bit string corresponds to Access Identity 13, bit 5 in the bit string corresponds to Access Identity 14, and bit 6 in the bit string corresponds to Access Identity 15. Value 0 means that access attempt is allowed for the corresponding access identity.

uac-BarringFactor Represents the probability that access attempt would be allowed during access barring check.

uac-BarringFactorForAI3 Barring factor applicable for Access Identity 3. Represents the probability that access attempt would be allowed during access barring check. If absent, the UE considers the access attempt as allowed.

uac-BarringTime The average time in seconds before a new access attempt is to be performed after an access attempt was barred at access barring check for the same access category, see 5.3.14.5.

– UAC-BarringPerCatList

The IE UAC-BarringPerCatList provides access control parameters for a list of access categories.

UAC-BarringPerCatList information element

— ASN1START

— TAG-UAC-BARRINGPERCATLIST-START

UAC-BarringPerCatList ::= SEQUENCE (SIZE (1..maxAccessCat-1)) OF UAC-BarringPerCat

UAC-BarringPerCat ::= SEQUENCE {

accessCategory INTEGER (1..maxAccessCat-1),

uac-barringInfoSetIndex UAC-BarringInfoSetIndex

}

— TAG-UAC-BARRINGPERCATLIST-STOP

— ASN1STOP

UAC-BarringPerCatList field descriptions

accessCategory The Access Category according to TS 22.261 [25].

– UAC-BarringPerPLMN-List

The IE UAC-BarringPerPLMN-List provides access category specific access control parameters, which are configured per PLMN/SNPN.

UAC-BarringPerPLMN-List information element

— ASN1START

— TAG-UAC-BARRINGPERPLMN-LIST-START

UAC-BarringPerPLMN-List ::= SEQUENCE (SIZE (1.. maxPLMN)) OF UAC-BarringPerPLMN

UAC-BarringPerPLMN ::= SEQUENCE {

plmn-IdentityIndex INTEGER (1..maxPLMN),

uac-ACBarringListType CHOICE{

uac-ImplicitACBarringList SEQUENCE (SIZE(maxAccessCat-1)) OF UAC-BarringInfoSetIndex,

uac-ExplicitACBarringList UAC-BarringPerCatList

} OPTIONAL — Need S

}

— TAG-UAC-BARRINGPERPLMN-LIST-STOP

— ASN1STOP

UAC-BarringPerPLMN-List field descriptions

uac-ACBarringListType Access control parameters for each access category valid only for a specific PLMN or SNPN. UE behaviour upon absence of this field is specified in clause 5.3.14.2.

plmn-IdentityIndex Index of the PLMN or SNPN across the plmn-IdentityInfoList and npn-IdentityInfoList fields included in SIB1.

– UE-TimersAndConstants

The IE UE-TimersAndConstants contains timers and constants used by the UE in RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE.

UE-TimersAndConstants information element

— ASN1START

— TAG-UE-TIMERSANDCONSTANTS-START

UE-TimersAndConstants ::= SEQUENCE {

t300 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000},

t301 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000},

t310 ENUMERATED {ms0, ms50, ms100, ms200, ms500, ms1000, ms2000},

n310 ENUMERATED {n1, n2, n3, n4, n6, n8, n10, n20},

t311 ENUMERATED {ms1000, ms3000, ms5000, ms10000, ms15000, ms20000, ms30000},

n311 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10},

t319 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000},

…

}

— TAG-UE-TIMERSANDCONSTANTS-STOP

— ASN1STOP

– UE-TimersAndConstantsRemoteUE

The IE UE-TimersAndConstantsRemoteUE contains timers and constants used by the L2 U2N Remote UE in RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE.

UE-TimersAndConstantsRemoteUE information element

— ASN1START

— TAG-UE-TIMERSANDCONSTANTSREMOTEUE-START

UE-TimersAndConstantsRemoteUE-r17 ::= SEQUENCE {

t300-RemoteUE-r17 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, — Need S

t301-RemoteUE-r17 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, — Need S

t319-RemoteUE-r17 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, — Need S

…

}

— TAG-UE-TIMERSANDCONSTANTSREMOTEUE-STOP

— ASN1STOP

UE-TimersAndConstantsRemoteUE field descriptions

t300-RemoteUE Indicates the timer value of T300 used by L2 U2N Remote UE. If the field is absent, the timer value indicated in t300 applies to L2 U2N Remote UE.

t301-RemoteUE Indicates the timer value of T301 used by L2 U2N Remote UE. If the field is absent, the timer value indicated in t301 applies to L2 U2N Remote UE.

t319-RemoteUE Indicates the timer value of T319 used by L2 U2N Remote UE. If the field is absent, the timer value indicated in t319 applies to L2 U2N Remote UE.

– UL-DelayValueConfig

The IE UL-DelayValueConfig specifies the configuration of the UL PDCP Packet Delay value per DRB measurement specified in TS 38.314 [53].

UL-DelayValueConfig information element

— ASN1START

— TAG-ULDELAYVALUECONFIG-START

UL-DelayValueConfig-r16 ::= SEQUENCE {

delay-DRBlist-r16 SEQUENCE (SIZE(1..maxDRB)) OF DRB-Identity

}

— TAG-ULDELAYVALUECONFIG-STOP

— ASN1STOP

UL-DelayValueConfig field descriptions
delay-DRBlist Indicates the DRB IDs used by UE to provide results of UL PDCP Packet Delay value per DRB measurement as specified in TS 38.314 [53].

– UL-ExcessDelayConfig

The IE UL-ExcessDelayConfig IE specifies the configuration of the UL PDCP Excess Packet Delay per DRB measurement specified in TS 38.314 [53].

UL-ExcessDelayConfig information element

— ASN1START

— TAG-ULEXCESSDELAYCONFIG-START

UL-ExcessDelayConfig-r17 ::= SEQUENCE {

excessDelay-DRBlist-r17 SEQUENCE (SIZE(1..maxDRB)) OF ExcessDelay-DRB-IdentityInfo-r17

}

ExcessDelay-DRB-IdentityInfo-r17 ::= SEQUENCE {

drb-IdentityList SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity,

delayThreshold ENUMERATED {ms0dot25, ms0dot5, ms1, ms2, ms4, ms5, ms10, ms20, ms30, ms40, ms50, ms60, ms70,

ms80, ms90, ms100, ms150, ms300, ms500}

}

— TAG-ULEXCESSDELAYCONFIG-STOP

— ASN1STOP

UL-ExcessDelayConfig field descriptions
drb-IdentityList Indicates the DRB IDs used by UE to provide results of UL PDCP Excess Packet Delay per DRB measurement as specified in TS 38.314 [53].
delayThreshold Indicates the delay threshold for the DRB IDs indicated in DRB-IdentityList. Value ms0dot25 corresponds to 0.25ms, ms0dot5 corresponds to 0.5ms, ms1 corresponds to 1ms and so on.

– UL-GapFR2-Config

The IE UL-GapFR2-Config specifies the FR2 uplink gap configuration.

UL-GapFR2-Config information element

— ASN1START

— TAG-UL-GAPFR2-CONFIG-START

UL-GapFR2-Config-r17 ::= SEQUENCE {

gapOffset-r17 INTEGER (0..159),

ugl-r17 ENUMERATED {ms0dot125, ms0dot25, ms0dot5, ms1},

ugrp-r17 ENUMERATED {ms5, ms20, ms40, ms160},

refFR2-ServCellAsyncCA-r17 ServCellIndex OPTIONAL — Cond AsyncCA

}

— TAG-UL-GAPFR2-CONFIG-STOP

— ASN1STOP

UL-GapFR2-Config field descriptions
gapOffset Value gapOffset is the gap offset of the FR2 UL gap pattern with UGRP indicated in the field ugrp. The value range is from 0 to ugrp-1.
refFR2-ServCellAsyncCA Indicates the FR2 serving cell identifier whose SFN and subframe is used for FR2 UL gap calculation for this gap pattern with asynchronous CA involving FR2 carrier(s).
ugl Value ugl is the gap length in ms of the FR2 UL gap. The FR2 UL gap length is according to in Table 9.1.7 in TS 38.133 [14]. Value ms0dot125 corresponds to 0.125 ms, ms0dot25 corresponds to 0.25 ms and so on.
ugrp Value ugrp is the gap repetition period in (ms) of the FR2 UL gap. The FR2 UL gap repetition period is according to Table 9.1.7 in TS 38.133 [14].

Conditional Presence	Explanation
AsyncCA	This field is mandatory present when configuring FR2 UL gap pattern to UE in: – (NG)EN-DC, NR SA, NE-DC or NR-DC without FR2-FR2 band combination, with asynchronous CA involving FR2 carriers.

– UplinkCancellation

The IE UplinkCancellation is used to configure the UE to monitor PDCCH for the CI-RNTI.

UplinkCancellation information element

— ASN1START

— TAG-UPLINKCANCELLATION-START

UplinkCancellation-r16 ::= SEQUENCE {

ci-RNTI-r16 RNTI-Value,

dci-PayloadSizeForCI-r16 INTEGER (0..maxCI-DCI-PayloadSize-r16),

ci-ConfigurationPerServingCell-r16 SEQUENCE (SIZE (1..maxNrofServingCells)) OF CI-ConfigurationPerServingCell-r16,

…

}

CI-ConfigurationPerServingCell-r16 ::= SEQUENCE {

servingCellId ServCellIndex,

positionInDCI-r16 INTEGER (0..maxCI-DCI-PayloadSize-1-r16),

positionInDCI-ForSUL-r16 INTEGER (0..maxCI-DCI-PayloadSize-1-r16) OPTIONAL, — Cond SUL-Only

ci-PayloadSize-r16 ENUMERATED {n1, n2, n4, n5, n7, n8, n10, n14, n16, n20, n28, n32, n35, n42, n56, n112},

timeFrequencyRegion-r16 SEQUENCE {

timeDurationForCI-r16 ENUMERATED {n2, n4, n7, n14} OPTIONAL, — Cond SymbolPeriodicity

timeGranularityForCI-r16 ENUMERATED {n1, n2, n4, n7, n14, n28},

frequencyRegionForCI-r16 INTEGER (0..37949),

deltaOffset-r16 INTEGER (0..2),

…

},

uplinkCancellationPriority-v1610 ENUMERATED {enabled} OPTIONAL — Need S

}

— TAG-UPLINKCANCELLATION-STOP

— ASN1STOP

UplinkCancellation field descriptions

ci-ConfigurationPerServingCell Indicates (per serving cell) the position of the ci-PaylaodSize bit CI values inside the DCI payload (see TS 38.213 [13], clause 11.2A).

ci-RNTI RNTI used for indication cancellation in UL (see TS 38.212 [17] clause 7.3.1 and TS 38.213 [13], clause 11.2A).

dci-PayloadSizeForCI Total length of the DCI payload scrambled with CI-RNTI (see TS 38.213 [13], clause 11.2A).

CI-ConfigurationPerServingCell field descriptions

ci-PayloadSize Configures the field size for each UL cancelation indicator of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A).

deltaOffset Configures the additional offset from the end of a PDCCH reception where the UE detects the DCI format 2_4 and the first symbol of the T_"CI" symbols, in the unit of OFDM symbols (see TS 38.213 [13], clause 11.2A).

frequencyRegionForCI Configures the reference frequency region where a detected UL CI is applicable (see TS 38.213 [13], clause 11.2A). It is defined in the same way as locationAndBandwidth.

positionInDCI Starting position (in number of bit) of the ci-PayloadSize bit CI value applicable for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2A).

positionInDCI-ForSUL Starting position (in number of bit) of the ci-PayloadSize bit CI value applicable for SUL of this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2A).

timeDurationForCI Configures the duration of the reference time region in symbols where a detected UL CI is applicable of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). If the field is absent, i.e., the configured UL CI monitoring periodicity indicated by monitoringSlotPeriodicityAndOffset for DCI format 2_4 is larger than 1 slot or 1 slot with only one monitoring occasion, the UE applies the value of the configured UL CI monitoring periodicity,

timeFrequencyRegion Configures the reference time and frequency region where a detected UL CI is applicable of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A).

timeGranularityForCI Configures the number of partitions within the time region of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A).

uplinkCancellationPriority Configures uplink cancellation behavior if both UL CI and intra-UE priority indicator are configured for a given UE. If the field is present, then UL CI is only applicable to the UL transmissions indicated/configured as low priority level. If the field is absent, UL CI is applicable to UL transmission irrespective of its priority level (see TS 38.213 [13], clause 11.2A).

Conditional Presence	Explanation
SUL-Only	The field is optionally present, Need R, if supplementaryUplink is configured in ServingCellConfig. It is absent otherwise.
SymbolPeriodicity	This field is mandatory present if the configured UL CI monitoring periodicity indicated by monitoringSlotPeriodicityAndOffset for DCI format 2_4 is 1 slot with more than one monitoring occasion, otherwise absent.

– UplinkConfigCommon

The IE UplinkConfigCommon provides common uplink parameters of a cell.

UplinkConfigCommon information element

— ASN1START

— TAG-UPLINKCONFIGCOMMON-START

UplinkConfigCommon ::= SEQUENCE {

frequencyInfoUL FrequencyInfoUL OPTIONAL, — Cond InterFreqHOAndServCellAdd

initialUplinkBWP BWP-UplinkCommon OPTIONAL, — Cond ServCellAdd

dummy TimeAlignmentTimer

}

UplinkConfigCommon-v1700 ::= SEQUENCE {

initialUplinkBWP-RedCap-r17 BWP-UplinkCommon OPTIONAL — Need R

}

— TAG-UPLINKCONFIGCOMMON-STOP

— ASN1STOP

UplinkConfigCommon field descriptions

frequencyInfoUL Absolute uplink frequency configuration and subcarrier specific virtual carriers.

initialUplinkBWP The initial uplink BWP configuration for a serving cell (see TS 38.213 [13], clause 12).

initialUplinkBWP-RedCap If present, RedCap UEs use this UL BWP instead of initialUplinkBWP. If absent, RedCap UEs use initialUplinkBWP provided that it does not exceed the RedCap UE maximum bandwidth (see also clause 5.2.2.4.2).

Conditional Presence	Explanation
InterFreqHOAndServCellAdd	This field is mandatory present for inter-frequency handover and upon serving cell (PSCell/SCell) addition. Otherwise, the field is optionally present, Need M.
ServCellAdd	This field is mandatory present upon serving cell addition (for PSCell and SCell) and upon handover from E-UTRA to NR. It is optionally present, Need M otherwise.

– UplinkConfigCommonSIB

The IE UplinkConfigCommonSIB provides common uplink parameters of a cell.

UplinkConfigCommonSIB information element

— ASN1START

— TAG-UPLINKCONFIGCOMMONSIB-START

UplinkConfigCommonSIB ::= SEQUENCE {

frequencyInfoUL FrequencyInfoUL-SIB,

initialUplinkBWP BWP-UplinkCommon,

timeAlignmentTimerCommon TimeAlignmentTimer

}

UplinkConfigCommonSIB-v1700 ::= SEQUENCE {

initialUplinkBWP-RedCap-r17 BWP-UplinkCommon OPTIONAL — Need R

}

— TAG-UPLINKCONFIGCOMMONSIB-STOP

— ASN1STOP

UplinkConfigCommonSIB field descriptions

frequencyInfoUL Absolute uplink frequency configuration and subcarrier specific virtual carriers.

InitialUplinkBWP The initial uplink BWP configuration for a PCell (see TS 38.213 [13], clause 12).

initialUplinkBWP-RedCap If present, RedCap UEs use this UL BWP instead of initialUplinkBWP. If absent, RedCap UEs use initialUplinkBWP provided that it does not exceed the RedCap UE maximum bandwidth (see also clause 5.2.2.4.2).

– Uplink-PowerControl

The IE Uplink-PowerControl is used to configure UE specific power control parameter for PUSCH, PUCCH and SRS.

Uplink-PowerControl information element

— ASN1START

— TAG-UPLINK-POWERCONTROL-START

Uplink-powerControl-r17 ::= SEQUENCE {

ul-powercontrolId-r17 Uplink-powerControlId-r17,

p0AlphaSetforPUSCH-r17 P0AlphaSet-r17 OPTIONAL, — Need R

p0AlphaSetforPUCCH-r17 P0AlphaSet-r17 OPTIONAL, — Need R

p0AlphaSetforSRS-r17 P0AlphaSet-r17 OPTIONAL — Need R

}

P0AlphaSet-r17 ::= SEQUENCE {

p0-r17 INTEGER (-16..15) OPTIONAL, — Need R

alpha-r17 Alpha OPTIONAL, — Need S

closedLoopIndex-r17 ENUMERATED { i0, i1 }

}

Uplink-powerControlId-r17 ::= INTEGER(1.. maxUL-TCI-r17)

— TAG-UPLINK-POWERCONTROL-STOP

— ASN1STOP

Uplink-PowerControl field descriptions

p0AlphaSetforPUSCH, p0AlphaSetforPUCCH, p0AlphaSetforSRS Configures power control parameters for PUSCH, PUCCH and SRS (see TS 38.213 [13], clause 7.2). When the field alpha is absent in p0AlphaSetforPUSCH, the UE applies the value 1 for PUSCH power control. When the field alpha is absent in p0AlphaSetforSRS, the UE applies the value 1 for SRS power control. In p0AlphaSetForPUCCH, the field alpha is absent (not used).

– Uu-RelayRLC-ChannelConfig

The IE Uu-RelayRLC-ChannelConfig is used to configure an RLC entity, a corresponding logical channel in MAC for Uu Relay RLC channel between L2 U2N Relay UE and network.

Uu-RelayRLC-ChannelConfig information element

— ASN1START

— TAG-UURELAYRLCCHANNELCONFIG-START

Uu-RelayRLC-ChannelConfig-r17::= SEQUENCE {

uu-LogicalChannelIdentity-r17 LogicalChannelIdentity OPTIONAL, — Cond RelayLCH-SetupOnly

uu-RelayRLC-ChannelID-r17 Uu-RelayRLC-ChannelID-r17,

reestablishRLC-r17 ENUMERATED {true} OPTIONAL, — Need N

rlc-Config-r17 RLC-Config OPTIONAL, — Cond RelayLCH-Setup

mac-LogicalChannelConfig-r17 LogicalChannelConfig OPTIONAL, — Cond RelayLCH-Setup

…

}

— TAG-UURELAYRLCCHANNELCONFIG-STOP

— ASN1STOP

Uu-RelayRLC-ChannelConfig field descriptions

uu-LogicalChannelIdentity Indicates the logical channel id for Uu Relay RLC channel of the L2 U2N Relay UE.

uu-RelayRLC-ChannelID Indicates the Uu Relay RLC channel in the link between L2 U2N Relay UE and network.

reestablishRLC Indicates that RLC should be re-established.

rlc-Config Determines the RLC mode (UM, AM) and provides corresponding parameters.

Conditional Presence	Explanation
RelayLCH-Setup	This field is mandatory present upon creation of a new logical channel for a Uu Relay RLC channel. It is optionally present, Need M, otherwise.
RelayLCH-SetupOnly	This field is mandatory present upon creation of a new logical channel for a Uu Relay RLC channel. It is absent otherwise.

– Uu-RelayRLC-ChannelID

The IE Uu-RelayRLC-ChannelID is used to identify a Uu Relay RLC channel in the link between L2 U2N Relay UE and network.

Uu-RelayRLC-ChannelID information element

— ASN1START

— TAG-UURELAYRLCCHANNELID-START

Uu-RelayRLC-ChannelID-r17 ::= INTEGER (1..maxLC-ID)

— TAG-UURELAYRLCCHANNELID-STOP

— ASN1STOP

– UplinkTxDirectCurrentList

The IE UplinkTxDirectCurrentList indicates the Tx Direct Current locations per serving cell for each configured UL BWP in the serving cell, based on the BWP numerology and the associated carrier bandwidth.

UplinkTxDirectCurrentList information element

— ASN1START

— TAG-UPLINKTXDIRECTCURRENTLIST-START

UplinkTxDirectCurrentList ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF UplinkTxDirectCurrentCell

UplinkTxDirectCurrentCell ::= SEQUENCE {

servCellIndex ServCellIndex,

uplinkDirectCurrentBWP SEQUENCE (SIZE (1..maxNrofBWPs)) OF UplinkTxDirectCurrentBWP,

…,

[[

uplinkDirectCurrentBWP-SUL SEQUENCE (SIZE (1..maxNrofBWPs)) OF UplinkTxDirectCurrentBWP OPTIONAL

]]

}

UplinkTxDirectCurrentBWP ::= SEQUENCE {

bwp-Id BWP-Id,

shift7dot5kHz BOOLEAN,

txDirectCurrentLocation INTEGER (0..3301)

}

— TAG-UPLINKTXDIRECTCURRENTLIST-STOP

— ASN1STOP

UplinkTxDirectCurrentBWP field descriptions

bwp-Id The BWP-Id of the corresponding uplink BWP.

shift7dot5kHz Indicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true. Otherwise 7.5 kHz shift is not applied.

txDirectCurrentLocation The uplink Tx Direct Current location for the carrier. Only values in the value range of this field between 0 and 3299, which indicate the subcarrier index within the carrier corresponding to the numerology of the corresponding uplink BWP and value 3300, which indicates "Outside the carrier" and value 3301, which indicates "Undetermined position within the carrier" are used in this version of the specification.

UplinkTxDirectCurrentCell field descriptions

servCellIndex The serving cell ID of the serving cell corresponding to the uplinkDirectCurrentBWP.

uplinkDirectCurrentBWP The Tx Direct Current locations for all the uplink BWPs configured at the corresponding serving cell.

uplinkDirectCurrentBWP-SUL The Tx Direct Current locations for all the supplementary uplink BWPs configured at the corresponding serving cell.

– UplinkTxDirectCurrentMoreCarrierList

The IE UplinkTxDirectCurrentMoreCarrierList indicates the Tx Direct Current locations for intra-band CA including one, two or more uplink carriers. The UE does not report the uplink Direct Current location information for SUL carrier(s).

UplinkTxDirectCurrentMoreCarrierList information element

— ASN1START

— TAG-UPLINKTXDIRECTCURRENTMORECARRIERLIST-START

UplinkTxDirectCurrentMoreCarrierList-r17 ::= SEQUENCE (SIZE (1..maxNrofCC-Group-r17)) OF CC-Group-r17

CC-Group-r17 ::= SEQUENCE {

servCellIndexLower-r17 ServCellIndex,

servCellIndexHigher-r17 ServCellIndex OPTIONAL,

defaultDC-Location-r17 DefaultDC-Location-r17,

offsetToDefault-r17 CHOICE{

offsetValue OffsetValue-r17,

offsetlist SEQUENCE (SIZE(1..maxNrofReqComDC-Location-r17)) OF OffsetValue-r17

} OPTIONAL

}

OffsetValue-r17::= SEQUENCE {

offsetValue-r17 INTEGER (-20000.. 20000),

shift7dot5kHz-r17 BOOLEAN

}

DefaultDC-Location-r17 ::= CHOICE {

ul FrequencyComponent-r17,

dl FrequencyComponent-r17,

ulAndDL FrequencyComponent-r17

}

FrequencyComponent-r17 ::= ENUMERATED {activeCarrier,configuredCarrier,activeBWP,configuredBWP}

— TAG-UPLINKTXDIRECTCURRENTMORECARRIERLIST-STOP

— ASN1STOP

UplinkTxDirectCurrentMoreCarrierList and CC-Group field descriptions

CC-Group The contiguous carriers sharing the same PA in an intra-band UL CA configuration. The UE shall report only one DC location for an intra-band CC combination with one active uplink carrier in case DefaultDCLoactionOption is set to activeCarrier or activeBWP.

defaultDCLocationOption Indicates the defatul DC location derivation option. The default Tx Direct Current is located at the mathematical center of the UE bandwidth, i.e. between the lower edge of lowest frequency component and the upper edge of highest frequency component as indicated by FrequencyComponent in the associated CC-Group, where the lowest frequency component and the highest frequency component may be the same, as indicated by FrequencyComponent, rounded to the subcarrier grid defined for the component carrier on which the Tx Direct Current is located. If the mathematical center of the UE bandwidth lands on frequencies where there is no subcarrier grid defined, the subcarrier grid of the nearest lower frequency component carrier shall be extended to cover the frequency of the mathematical default Direct Current location.

OffsetToDefault Indicates the DC location offset to the defatul DC location derived from defaultDCLocationOption. The lowest SCS in the CC group is used as the offset granularity. Value 0 respresents no offset. offsetValue is used in case DefaultDCLocationOption is set to configuredCarrier or configuredBWP. offsetlist is used in case DefaultDCLocationOption is set to activeCarrier or activeBWP. Each entity in this list corresponds to the entry in carriers combination in IntraBandCC-CombinationReqList of the intra-band CA component. For each CC group, the UE shall include the same number of entries, and listed in the same order as in CC-CombinationList. If DefaultDCLocationOption is set the activeCarrier, same offsetValue is signalled for all requested carriers combinations with same active carriers states(regardless of the active BPW index).

servCellIndexHigher Indicates the serving cell index of the highest edge of the CC-Group. If asbsent, there is only one carrier in this group indicated by servCellIndexLower.

servCellIndexLower Indicates the serving cell index of the lowest edge of the CC-Group.

shift7dot5kHz Indicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true, otherwise 7.5 kHz shift is not applied.

DefaultDCLocationOption field descriptions

dl Indicates that the default DC location is derived based on the DL frequencies of the frequency component.

ul Indicates that the default DC location is derived based on the UL frequencies of the frequency component.

ulAndDL Indicates that the default DC location is derived based on the edge most frequencies among any DL and UL frequency components.

– UplinkTxDirectCurrentTwoCarrierList

The IE UplinkTxDirectCurrentTwoCarrierList indicates the Tx Direct Current locations when uplink intra-band CA with two carriers is configured, based on the configured carriers and BWP numerology and the associated carrier bandwidth of the carriers. The UE does not report the uplink Direct Current location information for SUL carrier(s).

UplinkTxDirectCurrentTwoCarrierList information element

— ASN1START

— TAG-UPLINKTXDIRECTCURRENTTWOCARRIERLIST-START

UplinkTxDirectCurrentTwoCarrierList-r16 ::= SEQUENCE (SIZE (1..maxNrofTxDC-TwoCarrier-r16)) OF UplinkTxDirectCurrentTwoCarrier-r16

UplinkTxDirectCurrentTwoCarrier-r16 ::= SEQUENCE {

carrierOneInfo-r16 UplinkTxDirectCurrentCarrierInfo-r16,

carrierTwoInfo-r16 UplinkTxDirectCurrentCarrierInfo-r16,

singlePA-TxDirectCurrent-r16 UplinkTxDirectCurrentTwoCarrierInfo-r16,

secondPA-TxDirectCurrent-r16 UplinkTxDirectCurrentTwoCarrierInfo-r16 OPTIONAL

}

UplinkTxDirectCurrentCarrierInfo-r16 ::= SEQUENCE {

servCellIndex-r16 ServCellIndex,

servCellInfo-r16 CHOICE {

bwp-Id-r16 BWP-Id,

deactivatedCarrier-r16 ENUMERATED {deactivated}

}

}

UplinkTxDirectCurrentTwoCarrierInfo-r16 ::= SEQUENCE {

referenceCarrierIndex-r16 ServCellIndex,

shift7dot5kHz-r16 BOOLEAN,

txDirectCurrentLocation-r16 INTEGER (0..3301)

}

— TAG-UPLINKTXDIRECTCURRENTTWOCARRIERLIST-STOP

— ASN1STOP

UplinkTxDirectCurrentTwoCarrierInfo field descriptions

referenceCarrierIndex The serving cell ID of the carrier which is to be used as the reference for interpreting the Tx Direction Current location as reported using txDirectCurrentLocation-r16. The numerology of the uplink BWP ID reported with bwp-Id-r16 for this serving cell is the numerology used for interpreting the reported subcarrier location.

shift7dot5kHz Indicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true. Otherwise 7.5 kHz shift is not applied.

txDirectCurrentLocation The uplink Tx Direct Current location for the two carrier uplink CA with the serving cells reported using carrierOneInfo-r16 and carrierTwoInfo-r16. Values in the range of this field between 0 and 3299 indicate the subcarrier index of the uplink Tx Direct Current location with the subcarrier taken from the serving cell with ID referenceCarrierIndex and the numerology of the corresponding uplink BWP reported for this serving cell. Value 3300 indicates "Outside the carrier" and value 3301 indicates "Undetermined position within the carrier".

UplinkTxDirectCurrentCarrierInfo field descriptions

bwp-Id The BWP ID of the serving cell which is part of the two carrier uplink carrier aggregation. The UE shall not report this field if the serving cell is reported as deactivated using deactivatedCarrier-r16.

deactivatedCarrier For the reported uplink Tx Direct Current location(s) corresponding to singlePA-TxDirectCurrent-r16, indicates whether the carrier is deactivated or not for this serving cell. If the carrier refers to the PCell, the UE shall not set this field to deactivated.

servCellIndex The serving cell ID of the serving cell which is part of the two carrier uplink carrier aggregation.

UplinkTxDirectCurrentTwoCarrier field descriptions

carrierOneInfo The serving cell ID and BWP ID of the first carrier of the uplink carrier aggregation for which the uplink Tx Direct Current location(s) are being reported.

carrierTwoInfo The serving cell ID and BWP ID of the second carrier of the uplink carrier aggregation for which the uplink Tx Direct Current location(s) are being reported.

singlePA-TxDirectCurrent The uplink Tx Direct Current location for the UE which support single PA for this uplink carrier aggregation. For the UEs which support dual PA for this uplink carrier aggregation, this field is for reporting the uplink Tx Direct Current location of the first PA.

secondPA-TxDirectCurrent The uplink Tx Direct Current location used by the UE with the second PA for the UEs which support dual PA for this uplink carrier aggregation. This field shall be absent for the UplinkTxDirectCurrentTwoCarrier entity where deactivatedCarrier of carrierOneInfo or carrierTwoInfo is set to deactivated.

– ZP-CSI-RS-Resource

The IE ZP-CSI-RS-Resource is used to configure a Zero-Power (ZP) CSI-RS resource (see TS 38.214 [19], clause 5.1.4.2). Reconfiguration of a ZP-CSI-RS-Resource between periodic or semi-persistent and aperiodic is not supported.

ZP-CSI-RS-Resource information element

— ASN1START

— TAG-ZP-CSI-RS-RESOURCE-START

ZP-CSI-RS-Resource ::= SEQUENCE {

zp-CSI-RS-ResourceId ZP-CSI-RS-ResourceId,

resourceMapping CSI-RS-ResourceMapping,

periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, –Cond PeriodicOrSemiPersistent

…

}

ZP-CSI-RS-ResourceId ::= INTEGER (0..maxNrofZP-CSI-RS-Resources-1)

— TAG-ZP-CSI-RS-RESOURCE-STOP

— ASN1STOP

ZP-CSI-RS-Resource field descriptions

periodicityAndOffset Periodicity and slot offset for periodic/semi-persistent ZP-CSI-RS (see TS 38.214 [19], clause 5.1.4.2). Network always configures the UE with a value for this field for periodic and semi-persistent ZP-CSI-RS resource (as indicated in PDSCH-Config).

resourceMapping OFDM symbol and subcarrier occupancy of the ZP-CSI-RS resource within a slot.

zp-CSI-RS-ResourceId ZP CSI-RS resource configuration ID (see TS 38.214 [19], clause 5.1.4.2).

Conditional Presence	Explanation
PeriodicOrSemiPersistent	The field is optionally present, Need M, for periodic and semi-persistent ZP-CSI-RS-Resources (as indicated in PDSCH-Config). The field is absent otherwise.

– ZP-CSI-RS-ResourceSet

The IE ZP-CSI-RS-ResourceSet refers to a set of ZP-CSI-RS-Resources using their ZP-CSI-RS-ResourceIds.

ZP-CSI-RS-ResourceSet information element

— ASN1START

— TAG-ZP-CSI-RS-RESOURCESET-START

ZP-CSI-RS-ResourceSet ::= SEQUENCE {

zp-CSI-RS-ResourceSetId ZP-CSI-RS-ResourceSetId,

zp-CSI-RS-ResourceIdList SEQUENCE (SIZE(1..maxNrofZP-CSI-RS-ResourcesPerSet)) OF ZP-CSI-RS-ResourceId,

…

}

— TAG-ZP-CSI-RS-RESOURCESET-STOP

— ASN1STOP

ZP-CSI-RS-ResourceSet field descriptions

zp-CSI-RS-ResourceIdList The list of ZP-CSI-RS-ResourceId identifying the ZP-CSI-RS-Resource elements belonging to this set.

– ZP-CSI-RS-ResourceSetId

The IE ZP-CSI-RS-ResourceSetId identifies a ZP-CSI-RS-ResourceSet.

ZP-CSI-RS-ResourceSetId information element

— ASN1START

— TAG-ZP-CSI-RS-RESOURCESETID-START

ZP-CSI-RS-ResourceSetId ::= INTEGER (0..maxNrofZP-CSI-RS-ResourceSets-1)

— TAG-ZP-CSI-RS-RESOURCESETID-STOP

— ASN1STOP