Content for  TS 38.331  Word version:  17.4.0

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.

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

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.

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.

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.

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

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.

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 reference location configured with 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.

Reference locations used for condEventD1. 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. 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.

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.

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.

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

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.

SINR is applicable only for CONNECTED mode events.

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

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.

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.

ID used commonly for the MAC logical channel and for the RLC bearer. Value 4 is not configured for DRBs if SRB4 is configured.

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.

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.

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.

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.

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.

Parameter for RLC AM in TS 38.322. Value t1 corresponds to 1 retransmission, value t2 corresponds to 2 retransmissions and so on.

Parameter for RLC AM in TS 38.322. Value kB25 corresponds to 25 kBytes, value kB50 corresponds to 50 kBytes and so on. infinity corresponds to an infinite amount of kBytes.

Parameter for RLC AM in TS 38.322. Value p4 corresponds to 4 PDUs, value p8 corresponds to 8 PDUs and so on. infinity corresponds to an infinite number of PDUs.

Indicates the RLC SN field size, see TS 38.322, in bits. Value size6 means 6 bits, value size12 means 12 bits, value size18 means 18 bits. The value of sn-FieldLength of an RLC entity for the DRB/multicast MRB shall be changed only using reconfiguration with sync. The network configures only value size12 in SN-FieldLengthAM for SRB.

Timer for RLC AM in TS 38.322, in milliseconds. Value ms5 means 5 ms, value ms10 means 10 ms and so on.

Timer for reassembly in TS 38.322, in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-ReassemblyExt-r17 is configured, the UE shall ignore t-Reassembly (without suffix).

Timer for status reporting in TS 38.322, in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-StatusProhibit-v1610 is present, the UE shall ignore t-StatusProhibit (without suffix).

Constants are described in clause 7.3. Value n1 corresponds to 1, value n2 corresponds to 2 and so on.

Timers are described in clause 7.1. Value ms0 corresponds to 0 ms, value ms50 corresponds to 50 ms and so on.