Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 38.331  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.2.2.4…   5.3…   5.3.3…   5.3.5…   5.3.5.5…   5.3.5.6…   5.3.5.7…   5.3.5.13…   5.3.5.17…   5.3.6…   5.3.8…   5.3.13…   5.3.14…   5.4…   5.5…   5.5.3…   5.5.4…   5.5.4.15…   5.5.4.23…   5.5.5…   5.5a…   5.7…   5.7.4…   5.7.8…   5.7.12…   5.8…   5.8.9…   5.8.9.2…   5.8.9.8…   5.8.10…   5.8.11…   5.9…   5.10…   6…   6.2.2…   6-2-2-23…   6-2-2-27…   6-2-2-43…   6-2-2-47…   6.3…   6.3.2…   6-3-2-27…   6-3-2-49…   6-3-2-73…   6-3-2-95…   6-3-2-108…   6-3-2-134…   6-3-2-162…   6-3-2-188…   6-3-2-213…   6-3-2-243…   6-3-2-271…   6-3-2-297…   6-3-2-341…   6.3.3…   6-3-3-25…   6-3-3-51…   6.3.4…   6.3.5…   6-3-5-25…   6.3.6…   6.4…   7…   9…   11…   A…   A.4…   B…

 

 –  RACH-ConfigDedicatedp. 965

The IE RACH-ConfigDedicated is used to specify the dedicated random access parameters.
RACH-ConfigDedicated information element
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. 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 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 resource index DMRS_id 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 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.
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. 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 clause 5.1.1 of TS 38.321).
ra-PrioritizationTwoStep
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).
Conditional Presence Explanation
MandatoryThe field is mandatory present.
OccasionsThe field is optionally present, Need S, if the field occasions is present, otherwise it is absent.
2StepCFRAThe field is optionally present for the case of 2-step RA type contention free random access, Need S, otherwise it is absent.
Up

 –  RACH-ConfigGenericp. 969

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
RACH-ConfigGeneric field descriptions
msg1-FDM
The number of PRACH transmission occasions FDMed in one time instance. (see clause 6.3.3.2 of TS 38.211).
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 clause 6.3.3.2 of TS 38.211).
powerRampingStep
Power ramping steps for PRACH (see clause 5.1.3 of TS 38.321).
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 clause 6.3.3.2 of TS 38.211).
prach-ConfigurationIndex
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).
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 clause 6.3.3.2 of TS 38.211).
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 clause 6.3.3.2 of TS 38.211).
preambleReceivedTargetPower
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, ...).
preambleTransMax
Max number of RA preamble transmission performed before declaring a failure (see clauses 5.1.4, 5.1.5 of TS 38.321).
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 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.
zeroCorrelationZoneConfig
N-CS configuration, see Table 6.3.3.1-5 in TS 38.211.
Up

 –  RACH-ConfigGenericTwoStepRAp. 970

The IE RACH-ConfigGenericTwoStepRA is used to specify the 2-step random access type parameters.
RACH-ConfigGenericTwoStepRA information element
RACH-ConfigGenericTwoStepRA field descriptions
msgA-PreamblePowerRampingStep
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.
msgA-PreambleReceivedTargetPower
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.
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 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.
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 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.
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 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.
msgA-ZeroCorrelationZoneConfig
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-ResponseWindow
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.
preambleTransMax
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.
Conditional Presence Explanation
2StepOnlyThe 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.
2StepOnlyNoCFRAThe 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.
NoCFRAThe 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.
NoCFRA2The 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.
Up

 –  RACH-ConfigTwoTAp. 973

 –  RA-Prioritizationp. 974

The IE RA-Prioritization is used to configure prioritized random access.
RA-Prioritization information element
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 clause 5.1.4 of TS 38.321). Value zero corresponds to 0, value dot25 corresponds to 0.25 and so on.
Up

 –  RA-PrioritizationForSlicingp. 975

The IE RA-PrioritizationForSlicing is used to configure prioritized random access for slicing.
RA-PrioritizationForSlicing information element
Up

 –  RadioBearerConfigp. 975

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
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. 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.
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
RBTermChangeThe 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.
RBTermChange1The 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.
PDCPThe 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.
DRBSetupThe field is mandatory present if the corresponding DRB is being setup; otherwise the field is optionally present, need M.
HO-ConnThe 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-toNRIf 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.
DAPSThe 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.
MRBSetupThe field is mandatory present if the corresponding multicast MRB is being setup; otherwise the field is optionally present, need M.
Up

 –  RadioLinkMonitoringConfigp. 979

The IE RadioLinkMonitoringConfig is used to configure radio link monitoring for detection of beam- and/or cell radio link failure. See also clause 5.1.1 of TS 38.321.
RadioLinkMonitoringConfig information element
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 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.
beamFailureInstanceMaxCount
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.
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, 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.
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. 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.
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.
Up

 –  RadioLinkMonitoringRS-Idp. 981

The IE RadioLinkMonitoringRS-Id is used to identify one RadioLinkMonitoringRS.
RadioLinkMonitoringRS-Id information element
Up

 –  RAN-AreaCodep. 982

The IE RAN-AreaCode is used to identify a RAN area within the scope of a tracking area.
RAN-AreaCode information element

 –  RateMatchPatternp. 982

The IE RateMatchPattern is used to configure one rate matching pattern for PDSCH, see clause 5.1.4.1 of TS 38.214.
RateMatchPattern information element
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 clause 5.1.4.1 of TS 38.214).
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 clause 5.1.4.1 of TS 38.214).
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 clause 5.1.4.1 of TS 38.214):
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 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.
Conditional Presence Explanation
CellLevelThe 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 or RedCap-specific initial BWP (if configured) for RedCap UEs.
Up

 –  RateMatchPatternIdp. 984

The IE RateMatchPatternId identifies one RateMatchPattern (see clause 5.1.4.1 of TS 38.214).
RateMatchPatternId information element
Up

 –  RateMatchPatternLTE-CRSp. 985

The IE RateMatchPatternLTE-CRS is used to configure a pattern to rate match around LTE CRS. See clause 5.1.4.2 of TS 38.214.
RateMatchPatternLTE-CRS information element
RateMatchPatternLTE-CRS field descriptions
carrierBandwidthDL
BW of the LTE carrier in number of PRBs (see clause 5.1.4.2 of TS 38.214).
carrierFreqDL
Center of the LTE carrier (see clause 5.1.4.2 of TS 38.214).
mbsfn-SubframeConfigList
LTE MBSFN subframe configuration (see clause 5.1.4.2 of TS 38.214).
nrofCRS-Ports
Number of LTE CRS antenna port to rate-match around (see clause 5.1.4.2 of TS 38.214).
v-Shift
Shifting value v-shift in LTE to rate match around LTE CRS (see clause 5.1.4.2 of TS 38.214).
Up

 –  ReferenceConfigurationp. 986

 –  ReferenceLocationp. 986

The IE ReferenceLocation contains location information used as a reference location. The value of the field is same as Ellipsoid-Point defined in TS 37.355. The first/leftmost bit of the first octet contains the most significant bit.
ReferenceLocation information element
Up

 –  ReferenceTimeInfop. 986

The IE ReferenceTimeInfo contains timing information for 5G internal system clock used for, e.g., time stamping, see clause 5.27.1.2 of TS 23.501.
ReferenceTimeInfo information element
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
RefTimeThe field is mandatory present if referenceTimeInfo is included in DLInformationTransfer message; otherwise the field is absent.
Up

 –  RejectWaitTimep. 988

The IE RejectWaitTime is used to provide the value in seconds for timer T302.
RejectWaitTime information element
Up

 –  RepetitionSchemeConfigp. 988

The IE RepetitionSchemeConfig is used to configure the UE with repetition schemes as specified in clause 5.1 of TS 38.214.
RepetitionSchemeConfig information element
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. 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.
Up

 –  ReportConfigIdp. 989

The IE ReportConfigId is used to identify a measurement reporting configuration.
ReportConfigId information element

 –  ReportConfigInterRATp. 989

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

 –  ReportConfigNRp. 995

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
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 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, as specified in clause 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 clause 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 clause 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 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.
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 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.
useAllowedCellList
Indicates whether only the cells included in the allow-list of the associated measObject are applicable as specified in clause 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.
Up

 –  ReportConfigNR-SLp. 1009

The IE ReportConfigNR-SL specifies criteria for triggering of a CBR measurement reporting event for NR sidelink communication/ discovery. 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/ discovery is above a threshold;
Event C2:
CBR of NR sidelink communication/ discovery is below a threshold;
ReportConfigNR-SL information element
ReportConfigNR-SL field descriptions
reportType
Type of the configured CBR measurement report for NR sidelink communication/ discovery.
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.
Up

 –  ReportConfigToAddModListp. 1011

The IE ReportConfigToAddModList concerns a list of reporting configurations to add or modify.
ReportConfigToAddModList information element
Up

 –  ReportIntervalp. 1012

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) when reportType is set to either eventTriggered, periodical, cli-EventTriggered or cli-Periodical. 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
Up

 –  ReselectionThresholdp. 1012

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

 –  ReselectionThresholdQp. 1012

The IE ReselectionThresholdQ is used to indicate a quality level threshold for cell reselection. Actual value of threshold = field value [dB].
ReselectionThresholdQ information element

 –  ResumeCausep. 1013

The IE ResumeCause is used to indicate the resume cause in RRCResumeRequest, RRCResumeRequest1 and UEAssistanceInformation.
ResumeCause information element
Up

 –  RLC-BearerConfigp. 1013

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
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-SetupThis field is mandatory present upon creation of a new logical channel for a DRB or a multicast MRB or SRB4. This field is optionally present, Need S, upon creation of a new logical channel for an SRB except SRB4. It is optionally present, Need M, otherwise.
LCH-SetupModMRBThis 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-SetupOnlyThis 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-SetupOnlyMRBThis 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.
Up

Up   Top   ToC