Content for  TS 38.331  Word version:  18.0.0

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 32 entries.

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 clause 5.1.2 of TS 38.321). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination.

Subcarrier spacing of PRACH (see clause 5.3.2 of TS 38.211). Only the following values are applicable depending on the used frequency: 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). 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).

Enables the transform precoder for Msg3 transmission according to clause 6.1.3 of TS 38.214. If the field is absent, the UE disables the transformer precoder (see clause 8.3 of TS 38.213).

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 clause 5.1.1 of TS 38.321). The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

PRACH root sequence index (see clause 6.3.3.1 of TS 38.211). 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:

The initial value for the contention resolution timer (see clause 5.1.5 of TS 38.321). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on.

Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A (see clause 5.1.2 of TS 38.321). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination.

Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see clause 5.1.1a of TS 38.321).

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).

Parameters which apply to configure prioritized CBRA 4-step random access type for slicing.

RACH parameters for both regular random access and beam failure recovery.

Configuration of an unrestricted set or one of two types of restricted sets, see clause 6.3.3.1 of TS 38.211.

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).

The UE selects SUL carrier to perform random access based on this threshold (see clause 5.1.1 of TS 38.321). The value applies to all the BWPs and all RACH configurations.

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.

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.

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.

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.

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.

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:

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.

The UE selects 2-step random access type to perform random access based on this threshold (see clause 5.1.1 of TS 38.321). This field is only present if both 2-step and 4-step RA type are configured for the BWP.

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).

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.

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.

Subcarrier spacing of PRACH (see clause 5.3.2 of TS 38.211). Only the following values are applicable depending on the used frequency: 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) 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).

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.

Max number of MsgA preamble transmissions performed before switching to 4-step random access (see clause 5.1.1 of TS 38.321). 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.

The initial value for the contention resolution timer for fallback RAR in case no 4-step random access type is configured (see clause 5.1.5 of TS 38.321). 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. 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.

Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see clause 5.1.1a of TS 38.321).

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.

Parameters which apply to configure prioritized CBRA 2-step random access type for slicing.

2-step random access type parameters for both regular random access and beam failure recovery.

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 clause 5.1.1 of TS 38.321).

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.

Transport block size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see clause 5.1.1 of TS 38.321).

The ID of a CSI-RS resource defined in the measurement object associated with this serving cell.

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.

The RA preamble index to use in the RA occasions associated with this CSI-RS.

Indicates the MSG1 repetition number used for contention free 4-step random access type in TS 38.321. If this field is absent, the UE performs contention free 4-step random access without MSG1-Repetitions.

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.

Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321. The mask is valid for all SSB resources signalled in ssb-ResourceList.

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.

Number of SSBs per RACH occasion.

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.

Identifies the index of the PUSCH resource used for MSGA CFRA. The PUSCH resource index indicates a valid PUSCH occasion (as specified in clause 8.1A of TS 38.213) 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_id 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.

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

The ID of an SSB transmitted by this serving cell.

PUSCH resource configuration(s) for msgA CFRA.

Max number of MsgA preamble transmissions performed before switching to 4-step type random access (see clause 5.1.1 of TS 38.321). 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.

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.

Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321. The mask is valid for all SSB resources signalled in ssb-ResourceList.

Configuration of contention free random access occasions for CFRA 2-step random access type.

Number of SSBs per RACH occasion for 2-step random access type.

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.

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.

Parameters which apply for prioritized random access procedure to a given target cell (see clause 5.1.1 of TS 38.321).

Parameters which apply for prioritized 2-step random access type procedure to a given target cell (see clause 5.1.1 of TS 38.321).

The number of PRACH transmission occasions FDMed in one time instance. (see clause 6.3.3.2 of TS 38.211).

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 clause 6.3.3.2 of TS 38.211).

Power ramping steps for PRACH (see clause 5.1.3 of TS 38.321). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination.

Frame offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see clause 6.3.3.2 of TS 38.211).

PRACH configuration index. For prach-ConfigurationIndex configured under beamFailureRecoveryConfig, the prach-ConfigurationIndex can only correspond to the short preamble format, (see clause 6.3.3.2 of TS 38.211). If the field prach-ConfigurationIndex-v1610 is present, the UE shall ignore the value provided in prach-ConfigurationIndex (without suffix).

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 clause 6.3.3.2 of TS 38.211).

Subframe/Slot offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see clause 6.3.3.2 of TS 38.211).

The target power level at the network receiver side (see clause 7.4 of TS 38.213, clauses 5.1.2, 5.1.3 of TS 38.321). Only multiples of 2 dBm may be chosen (e.g. -202, -200, -198, ...). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination.

Max number of RA preamble transmission performed before declaring a failure (see clauses 5.1.4, 5.1.5 of TS 38.321).

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 clause 5.1.4 of TS 38.321). 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.

N-CS configuration, see Table 6.3.3.1-5 in TS 38.211.

Power ramping steps for msgA PRACH. 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 field is absent in other cases, UE shall use the value of powerRampingStep in RACH-ConfigGeneric in the configured BWP (see clause 5.1.3 of TS 38.321). 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.

The target power level at the network receiver side (see clause 7.1.1 of TS 38.213, and clause 5.1.1 of TS 38.321). 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.

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 clause 6.3.3.2 of TS 38.211). 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 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 clause 6.3.3.2 of TS 38.211). 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.

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 clauses 5.3.2 and 6.3.3.2 of TS 38.211). 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.

N-CS configuration for msgA preamble, see Table 6.3.3.1-5 in TS 38.211. 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 field is absent in other cases, 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 monitoring window length in number of slots. The network configures a value lower than or equal to 40ms (see clause 5.1.1 of TS 38.321). 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.

Max number of RA preamble transmission performed before declaring a failure (see clauses 5.1.4, 5.1.5 of TS 38.321). 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 field is absent in other cases, 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.

Subcarrier spacing of PRACH when prach-RootSequenceIndex has value set to l139 (see clause 5.3.2 of TS 38.211).

PRACH root sequence index (see clause 6.3.3.1 of TS 38.211). The value range depends on whether L=839 or L=139. If prach-RootSequenceIndex-r18 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

RACH parameters for for contention free random access occasions for CFRA.

Number of SSBs per RACH occasion.

Power ramping step applied for prioritized random access procedure.

Scaling factor for the backoff indicator (BI) for the prioritized random access procedure. (see clause 5.1.4 of TS 38.321). Value zero corresponds to 0, value dot25 corresponds to 0.25 and so on.

Indicates if the bearer is associated with the eps-bearerIdentity (when connected to EPC) or sdap-Config (when connected to 5GC).

Indicates that the bearer is configured as DAPS bearer.

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/indirect path of the configuration.

The EPS bearer ID determines the EPS bearer.

Indicates which multicast MBS session the bearer is associated with.

Identification of the multicast MRB.

New identity of the multicast MRB when mrb-Identity needs to be changed, e.g. as a result of a handover.

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 or if the RadioBearerConfig IE is part of an RRCReconfiguration message within the LTM-Config IE.

Indicates that PDCP should perform recovery according to TS 38.323. Network doesn't include this field if the bearer is configured as DAPS bearer or if the RadioBearerConfig IE is part of an RRCReconfiguration message within the LTM-Config IE.

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.

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.

Release SRB3. SRB3 release can only be done over SRB1 and only at SCG release and reconfiguration with sync.

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.

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.

Indicates that PDCP should discard stored SDU and PDU according to TS 38.323.

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 or if the RadioBearerConfig IE is part of an RRCReconfiguration message within the LTM-Config IE.

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.

Timer for beam failure detection (see clause 5.17 of TS 38.321). See also the BeamFailureRecoveryConfig IE. Value in number of "Qout,LR reporting periods of Beam Failure Detection" Reference Signal (see clause 6 of TS 38.213). 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.

This field determines after how many beam failure events the UE triggers beam failure recovery (see clause 5.17 of TS 38.321). Value n1 corresponds to 1 beam failure instance, value n2 corresponds to 2 beam failure instances and so on.

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, 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 clause 6 of TS 38.213. 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 clause 5 of TS 38.213. 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.

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. failureDetectionSetN is present if and only if candidateBeamRS-List2-r17 is configured. 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 consider all the reference signals in this failure detection set as deactivated. If bfdResourcesToAddModList-r17 in failureDetectionSetN is not present, the UE determines the RS(es) in each failureDetectionSetN as described in clause 6 of TS 38.213.

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.

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.

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.

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).

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 clause 5.1.4.1 of TS 38.214).

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 clause 5.1.4.1 of TS 38.214).

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 clause 5.1.4.1 of TS 38.214):

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 clause 5.1.4.1 of TS 38.214). 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.

BW of the LTE carrier in number of PRBs (see clause 5.1.4.2 of TS 38.214).

Center of the LTE carrier (see clause 5.1.4.2 of TS 38.214).

LTE MBSFN subframe configuration (see clause 5.1.4.2 of TS 38.214).

Number of LTE CRS antenna port to rate-match around (see clause 5.1.4.2 of TS 38.214).

Shifting value v-shift in LTE to rate match around LTE CRS (see clause 5.1.4.2 of TS 38.214).

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.

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. In an NTN cell, the indicated time is referenced at the uplink time synchronization reference point (RP), i.e., UE should take into account the propagation delay between UE and RP when determining the UTC time at the UE. 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.

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.

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.

Configures UE with a repetition scheme among fdmSchemeA, fdmSchemeB and tdmSchemeA as specified in clause 5.1 of TS 38.214. 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.

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.

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.

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.

Enables TCI state mapping method to PDSCH transmission occasions.

Type of the configured measurement report. In (NG)EN-DC, and NR-DC, network does not configure report of type ReportCGI-EUTRA for SCG.

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.

NR threshold to be used in inter RAT measurement report triggering condition for event B2.

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.

Choice of inter RAT event triggered reporting criteria.

Max number of non-serving cells/candidate L2 U2N Relay UEs to include in the measurement report.

Number of measurement reports applicable for eventTriggered as well as for periodical report types

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 clause 5.5.4.1.

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.

The L2 U2N Relay UE measurement quantity to be included in measuremet report.

Time during which specific criteria for the event needs to be met in order to trigger a measurement report.

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 for FDD. utra-FDD-EcN0 corresponds to CPICH_Ec/No in TS 25.133 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.

NR threshold to be used in measurement report triggering condition for event Y1.

L2 U2N Relay threshold value associated with the selected trigger quantity (i.e. RSRP) to be used in measurement report triggering condition for event Y1.

L2 U2N Relay threshold value associated with the selected trigger quantity (i.e. RSRP) to be used in measurement report triggering condition for event Y2.

L2 U2N Relay threshold value associated with the selected trigger quantity (i.e. SL-RSRP and/or SD-RSRP) to be used in measurement report triggering condition for serving Relay UE in event Z1. If the field sd-RSRP is not included, the UE considers it to be equal to sl-RSRP.

L2 U2N Relay threshold value associated with the selected trigger quantity (i.e. SD-RSRP) to be used in measurement report triggering condition for candidate Relay UE in event Z1.

Max number of non-serving cells/candidate L2 U2N Relay UEs to include in the measurement report.

Number of measurement reports applicable for eventTriggered as well as for periodical report types

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.

Cell individual offsets applicable to a specific measurement event.

Physical cell identity of a cell in the cell list.

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.

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.

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.

Choice of NR conditional reconfiguration event triggered criteria.

Distance from a fixed reference location configured with referenceLocation1 or referenceLocation2 or a moving reference location determined by the UE based on referenceLocation1 or referenceLocation2. Each step represents 50m.

This field is used for defining the leaving condition T1-2 for conditional HO event condEventT1. Each step represents 100ms.

Indicates the event is a NES-specific CHO event and the event is only considered to be satisfied if indication from lower layers is received indicating the applicability of NES-specific CHO event and the related entry condition(s) is fulfilled. This field can only be configured for condEventA3, condEventA4 or condEventA5.

Reference locations used for condEventD1 and condEventD2. The referenceLocation1 is associated to serving cell and referenceLocation2 is associated to candidate target cell.

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).

Time during which specific criteria for the event needs to be met in order to execute the conditional reconfiguration evaluation.

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.

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.

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.

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. In the same eventA5, eventA5H1, eventA5H2, the network configures the same quantity for the MeasTriggerQuantity of the a5-Threshold1 and for the MeasTriggerQuantity of the a5-Threshold2.

RSSI threshold which is used for channel occupancy evaluation.

This field is used to request UE to report coarse location information.

Threshold value associated to the distance from a reference location configured with referenceLocation1 or referenceLocation2. Each step represents 50m.

Choice of NR event triggered reporting criteria.

This field is used to request UE to report altitude information.

Max number of RS indexes to include in the measurement report for A1-A6 events.

Max number of non-serving cells to include in the measurement report.

Indicates the number of cells detected that are required to fulfill an event for a measurement report to be triggered. This field is applicable only for the events concerning neighbor cells, i.e. eventA3, eventA4, eventA5, eventA3H1, eventA3H2, eventA4H1, eventA4H2, eventA5H1, eventA5H2.

Reference locations used for eventD1. The referenceLocation1 is associated to serving cell and referenceLocation2 is associated to neighbour cell.

Indicates that the UE shall include the best neighbour cells per serving frequency.

Number of measurement reports applicable for eventTriggered as well as for periodical report types.

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 clause 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, eventH1, eventH2 as specified in clause 5.5.4.1.

The cell measurement quantities to be included in the measurement report.

Indicates which measurement information per RS index the UE shall include in the measurement report.

Indicates when multiple events of the same type satisfy the entering condition(s), whether to consider only the event with the smallest value between the altitude of the UE and the configured altitude threshold.

Time during which specific criteria for the event needs to be met in order to trigger a measurement report.

Indicates whether only the cells included in the allow-list of the associated measObject are applicable as specified in clause 5.5.4.1.

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.

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.

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.

Choice of CLI event triggered reporting criteria.

Max number of CLI measurement resource to include in the measurement report.

Number of measurement reports.

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 clause 5.5.4.1.

Time during which specific criteria for the event needs to be met in order to trigger a measurement report.

Max number of CLI measurement resource to include in the measurement report.

Number of measurement reports.

The CLI measurement quantities to be included in the measurement report.

This field is used to request UE to report coarse location information.

Max number of RS indexes to include in the measurement report.

Max number of non-serving cells to include in the measurement report.

Indicates that the UE shall include the best neighbour cells per serving frequency.

Number of measurement reports applicable for eventTriggered as well as for periodical report types

The cell measurement quantities to be included in the measurement report.

Indicates which measurement information per RS index the UE shall include in the measurement report.

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 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.

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 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.

Indicates whether only the cells included in the allow-list of the associated measObject are applicable as specified in clause 5.5.4.1.

Indicates the target NR neighbour cells for SFTD measurement between PCell and NR neighbour cells.

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.

Indicates whether UE is required to perform SFTD measurement between PCell and NR PSCell in NR-DC.

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.

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.

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.

This field indicates the measurement reporting periodicity of UE Rx-Tx time difference.

Indicates which RS is used to provide the measurement result. Only value ssb can be set in this release.

Indicates which measurement information per RS index is used to sort the reported measurement results and is included in the measurement report.

Max number of RS indexes to include in the measurement report.

Indicates whether to include the measurement result per RS index in the measurement report.

Cell individual offsets applicable to a specific measurement event.

Physical cell identity of a cell in the cell list.

SINR is applicable only for CONNECTED mode events.

Type of the configured CBR measurement report for NR sidelink communication/ discovery.

Threshold used for events C1 and C2 specified in clauses 5.5.4.11 and 5.5.4.12, respectively.

Choice of NR event triggered reporting criteria.

Number of measurement reports applicable for eventTriggered as well as for periodical report types.

The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result.

Time during which specific criteria for the event needs to be met in order to trigger a measurement report.

Number of measurement reports applicable for eventTriggered as well as for periodical report types.

The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result.