8.2.3 Measurement Configuration Control and Reporting / Handovers

38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.2.3.1 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells

8.2.3.1.1 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / EN-DC

8.2.3.1.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state having completed the radio bearer establishment and performed the inter RAT measurement for NR cell and not detected entering condition for the event B1 is met }

ensure that {

when { UE detects entering condition for the event B1 is not met }

then { UE does not transmit any MeasurementReport }

}

(2)

ensure that {

when { UE detects entering condition for the event B1 is met }

then { UE transmits a MeasurementReport }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state having completed the radio bearer establishment and performed the inter RAT measurement for NR cell and detected entering condition for the event B1 is met }

ensure that {

when { UE detects leaving condition for the event B1 is met }

then { UE does not transmit any MeasurementReport }

}

8.2.3.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.5.1, 5.5.4.1, 5.5.4.7, 5.5.5 and 5.5.5.3. Unless otherwise stated these are Rel-15 requirements.

[TS 36.331, clause 5.5.1]

The UE reports measurement information in accordance with the measurement configuration as provided by E-UTRAN. E-UTRAN provides the measurement configuration applicable for a UE in RRC_CONNECTED by means of dedicated signalling, i.e. using the RRCConnectionReconfiguration or RRCConnectionResume message.

The UE can be requested to perform the following types of measurements:

– Intra-frequency measurements: measurements at the downlink carrier frequency(ies) of the serving cell(s).

– Inter-frequency measurements: measurements at frequencies that differ from any of the downlink carrier frequency(ies) of the serving cell(s).

– Inter-RAT measurements of NR frequencies.

…

The measurement configuration includes the following parameters:

1. Measurement objects: The objects on which the UE shall perform the measurements.

– For intra-frequency and inter-frequency measurements a measurement object is a single E-UTRA carrier frequency. Associated with this carrier frequency, E-UTRAN can configure a list of cell specific offsets, a list of ‘blacklisted’ cells and a list of ‘whitelisted’ cells. Blacklisted cells are not considered in event evaluation or measurement reporting.

– For inter-RAT NR measurements a measurement object is a single NR carrier frequency. Associated with this carrier frequency, E-UTRAN can configure a list of ‘blacklisted’ cells. Blacklisted cells are not considered in event evaluation or measurement reporting.

…

NOTE 1: Some measurements using the above mentioned measurement objects, only concern a single cell, e.g. measurements used to report neighbouring cell system information, PCell UE Rx-Tx time difference, or a pair of cells, e.g. SSTD measurements between the PCell and the PSCell.

2. Reporting configurations: A list of reporting configurations where each reporting configuration consists of the following:

– Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.

– Reporting format: The quantities that the UE includes in the measurement report and associated information (e.g. number of cells to report).

3. Measurement identities: A list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is used as a reference number in the measurement report.

4. Quantity configurations: One quantity configuration is configured per RAT type. The quantity configuration defines the measurement quantities and associated filtering used for all event evaluation and related reporting of that measurement type. One filter can be configured per measurement quantity, except for NR where the network may configure up to 2 sets of quantity configurations each comprising per measurement quantity separate filters for cell and RS index measurement results. The quantity configuration set that applies for a given measurement is indicated within the NR measurement object.

5. Measurement gaps: Periods that the UE may use to perform measurements, i.e. no (UL, DL) transmissions are scheduled.

…

For E-UTRA, the UE measures and reports on the serving cell(s), listed cells, detected cells, transmission resource pools for V2X sidelink communication, and, for RSSI and channel occupancy measurements, the UE measures and reports on any reception on the indicated frequency. For inter-RAT NR, the UE measures and reports on detected cells and, if configured with EN-DC, on NR serving cell(s). For inter-RAT UTRA, the UE measures and reports on listed cells and optionally on cells that are within a range for which reporting is allowed by E-UTRAN. For inter-RAT GERAN, the UE measures and reports on detected cells. For inter-RAT CDMA2000, the UE measures and reports on listed cells. For inter-RAT WLAN, the UE measures and reports on listed cells.

[TS 36.331, clause 5.5.4.1]

If security has been activated successfully, The UE shall:

1> for each measId included in the measIdList within VarMeasConfig:

…

2> else:

…

3> else if the corresponding measObject concerns NR:

4> if the reportSFTD-Meas is set to pSCell in the corresponding reportConfigInterRAT:

5> consider the PSCell to be applicable;

4> else if the reportSFTD-Meas is set to neighborCells in the corresponding reportConfigInterRAT;

5> if cellsForWhichToReportSFTD is configured in the corresponding measObjectNR:6> consider any neighbouring NR cell on the associated frequency that is included in cellsForWhichToReportSFTD to be applicable;

5> else:

6> consider up to 3 strongest neighbouring NR cells detected on the associated frequency to be applicable when the concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

4> else:

5> if the eventB1 or eventB2 is configured in the corresponding reportConfig:

6> consider a serving cell, if any, on the associated NR frequency as neighbouring cell;

5> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;[TS 36.331, clause 5.5.4.7]

The UE shall:

1> for UTRA and CDMA2000, only trigger the event for cells included in the corresponding measurement object;

1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled;

Inequality B1-1 (Entering condition)

Inequality B1-2 (Leaving condition)

The variables in the formula are defined as follows:

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. For CDMA 2000 measurement result, pilotStrength is divided by -2.

Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell (i.e. offsetFreq as defined within the measObject corresponding to the frequency of the neighbour inter-RAT cell).

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).

Thresh is the threshold parameter for this event (i.e. b1-Threshold as defined within reportConfigInterRAT for this event). For CDMA2000, b1-Threshold is divided by -2.

Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.

Ofn, Hys are expressed in dB.

Thresh is expressed in the same unit as Mn.

[TS 36.331, clause 5.5.5]

The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN. The UE shall initiate this procedure only after successful security activation.

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> set the measResultPCell to include the quantities of the PCell;

1> set the measResultServFreqList to include for each E-UTRA SCell that is configured, if any, within measResultSCell the quantities of the concerned SCell, if available according to performance requirements in 36.133 [16], except if purpose for the reportConfig associated with the measId that triggered the measurement reporting is set to reportLocation;

1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

2> for each E-UTRA serving frequency for which measObjectId is referenced in the measIdList, other than the frequency corresponding with the measId that triggered the measurement reporting:

3> set the measResultServFreqList to include within measResultBestNeighCell the physCellId and the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

1> if the triggerType is set to event; and if the corresponding measObject concerns NR; and if eventId is set to eventB1-NR or eventB2-NR; or

1> if the triggerType is set to event; and if eventId is set to eventA3 or eventA4 or eventA5:

2> if purpose for the reportConfig associated with the measId that triggered the measurement reporting is set to a value other than reportLocation:

3> set the measResultServFreqListNR to include for each NR serving frequency that the UE is configured to measure according to TS 38.331 [82], if any, the following:

4> set measResultSCell to include the available results of the NR serving cell, as specified in 5.5.5.2;

4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

5> set measResultBestNeighCell to include the available results, as specified in 5.5.5.2, of the best non-serving cell, ordered based on the quantity determined as specified in 5.5.5.2;

3> for each (serving or neighbouring) cell for which the UE reports results according to the previous, additionally include available beam results according to the following:

4> if maxReportRS-Index is configured, set measResultRS-IndexList to include available results, as specified in 5.5.5.2, of up to maxReportRS-Index beams, ordered based on the quantity determined as specified in 5.5.5.3;

1> if there is at least one applicable neighbouring cell to report:

2> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:

3> if the triggerType is set to event:

4> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;

3> else:

4> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

NOTE 1: The reliability of the report (i.e. the certainty it contains the strongest cells on the concerned frequency) depends on the measurement configuration i.e. the reportInterval. The related performance requirements are specified in TS 36.133 [16].

3> for each cell that is included in the measResultNeighCells, include the physCellId;

3> if the triggerType is set to event; or the purpose is set to reportStrongestCells or to reportStrongestCellsForSON:

4> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

5> if the measObject associated with this measId concerns E-UTRA:

6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfig;

6> sort the included cells in order of decreasing triggerQuantity, i.e. the best cell is included first;

5> if the measObject associated with this measId concerns NR:

6> set the measResultCell to include the quantity(ies) indicated in the reportQuantityCellNR within the concerned reportConfig;

6> if maxReportRS-Index and reportQuantityRS-IndexNR are configured, set measResultRS-IndexList to include results of the best beam and the beams whose quantity is above threshRS-Index defined in the VarMeasConfig for the corresponding measObject, up to maxReportRS-Index beams in total:

7> order beams based on the sorting quantity determined as specified in 5.5.5.3;

7> include ssbIndex;

7> for each included beam:

8> include ssbIndex;

8> if reportRS-IndexResultsNR is configured, for each quantity indicated, include the corresponding measurement result in measResultNeighCells;

6> sort the included cells in order of decreasing sorting quantity determined as specified in 5.5.5.3;

…

[TS 36.331, clause 5.5.5.3]

1> for cells on the frequency associated with the measId that triggered the measurement reporting, if the reportTrigger is set to event, consider the quantity used in bN-ThresholdYNR to be the sorting quantity;

1> for other cases, determine the sorting quantity as follows:

2> consider the following quantities as candidate sorting quantities:

3> for cells on the frequency associated with the measId that triggered the measurement reporting (for a triggerType set to periodical):

4> the quantities defined by reportQuantityCellNR, when used for sorting cells;

4> the quantities defined by reportQuantityRS-IndexNR, when used for sorting beams;

3> for cells, serving or non-serving (i.e. within reportAddNeighMeas), on NR serving frequencies other than the one associated with the measId triggering reporting:

4> the available quantities of available NR measurement results as specified in 5.5.5.2;

2> if there is a single candidate sorting quantity;

3> consider the concerned quantity to be the sorting quantity;

2> else:

3> if RSRP is one of the candidate sorting quantities;

4> consider RSRP to be the sorting quantity;

3> else:

4> consider RSRQ to be the sorting quantity;

8.2.3.1.1.3 Test description

8.2.3.1.1.3.1 Pre-test conditions

System Simulator:

– E-UTRA Cell 1 and NR Cell 1.

UE:

– None.

Preamble:

– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (E-UTRA/EPC) established according to TS 38.508-1 [4].

8.2.3.1.1.3.2 Test procedure sequence

Table 8.2.3.1.3.2-1 and Table 8.2.3.1.3.2-1A illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.3.1.1.3.2-1: Time instances of cell power level and parameter changes for conducted test environment

	Parameter	Unit	E-UTRA Cell 1	NR Cell 1	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-85	–	The power level values are such that entering conditions for event B1 are not satisfied.
T0	SS/PBCH SSS EPRE	dBm/SCS	–	-91
T1	Cell-specific RS EPRE	dBm/15kHz	-85	–	The power level values are such that entering conditions for event B1 are satisfied.
T1	SS/PBCH SSS EPRE	dBm/SCS	–	-79
T2	Cell-specific RS EPRE	dBm/15kHz	-85	–	The power level values are such that leaving conditions for event B1 are satisfied.
T2	SS/PBCH SSS EPRE	dBm/SCS	–	-91

Table 8.2.3.1.1.3.2-1A: Time instances of cell power level and parameter changes for OTA test environment

	Parameter	Unit	E-UTRA Cell 1	NR Cell 1	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-96	–	The power level values are such that entering conditions for event B1 are not satisfied.
T0	SS/PBCH SSS EPRE	dBm/SCS	–	-100
T1	Cell-specific RS EPRE	dBm/15kHz	-96	–	The power level values are such that entering conditions for event B1 are satisfied.
T1	SS/PBCH SSS EPRE	dBm/SCS	–	-82
T2	Cell-specific RS EPRE	dBm/15kHz	-96	–	The power level values are such that leaving conditions for event B1 are satisfied.
T2	SS/PBCH SSS EPRE	dBm/SCS	–	-100

Table 8.2.3.1.1.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration including measConfig to setup inter RAT measurements and reporting for NR Cell 1.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of inter RAT measurements for NR Cell 1.	–>	RRCConnectionReconfigurationComplete	–	–
3	Check: Does the UE transmit a MeasurementReport message on E-UTRA Cell 1 to report the event B1 during the next 10s?	–>	MeasurementReport	1	F
4	The SS changes NR Cell 1 parameters according to the row "T1".	–	–	–	–
5	Check: Does the UE transmit a MeasurementReport message to report the event B1 for NR Cell 1?	–>	MeasurementReport	2	P
6	The SS changes NR Cell 1 parameters according to the row "T2".	–	–	–	–
7	Wait and ignore MeasurementReport messages for 57s if NR Cell 1 is on FR2 frequency else wait for 15 s to allow change of power levels and UE measurements for NR Cell 1.	–	–	–	–
8	Check: Does the UE transmit a MeasurementReport message on E-UTRA Cell 1 to report the event B1 during the next 10s?	–>	MeasurementReport	3	F

8.2.3.1.1.3.3 Specific message contents

Table 8.2.3.1.1.3.3-0: Conditions for specific message contents
in Tables 8.2.3.1.1.3.3-2.

Condition	Explanation
Band > 64	If band > 64 is selected

Table 8.2.3.1.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.3.1.1.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.6.1-8, condition MEAS

Table 8.2.3.1.1.3.3-2: MeasConfig (Table 8.2.3.1.1.3.3-1)

Derivation Path: TS 36.508 [7], Table 4.6.6-1
Information Element	Value/remark	Comment	Condition
MeasConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF MeasObjectToAddMod {	2 entries
MeasObjectToAddMod[1] SEQUENCE {		entry 1
measObjectId	1
measObject	MeasObjectEUTRA-GENERIC(f1)
	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
}
MeasObjectToAddMod[2] SEQUENCE {		entry 2
measObjectId	2
measObject	MeasObjectNR-GENERIC (NRf1)
}
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod {	1 entry
ReportConfigToAddMod[1] SEQUENCE {		entry 1
reportConfigId	1
reportConfig	ReportConfig1-B1-NR-r15(-85)		FR1
	ReportConfig2-B1-NR-r15(-91 + ∆(NRf1))		FR2
}
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF MeasIdToAddMod {	1 entry
MeasIdToAddMod[1] SEQUENCE {		entry 1
measId	1
measObjectId	2
reportConfigId	1
}
}
quantityConfig	QuantityConfig-DEFAULT
measGapConfig	MeasGapConfig
measObjectToAddModList-v9e0 SEQUENCE (SIZE (1..maxObjectId)) OF MeasObjectToAddMod-v9e0 {	1 entry		Band > 64
MeasObjectToAddMod-v9e0[1] SEQUENCE {		entry 1
measObjectEUTRA-v9e0 SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
}
}
}

Table 8.2.3.1.1.3.3-3: QuantityConfig-DEFAULT (Table 8.2.3.1.1.3.3-2)

Derivation Path: TS 36.508 [7], Table 4.6.6-3A
Information Element	Value/remark	Comment	Condition
QuantityConfig-DEFAULT ::= SEQUENCE {
quantityConfigNRList-r15 SEQUENCE ((SIZE (1..maxQuantSetsNR-r15)) OF QuantityConfigNR-r15 {	1 entry
QuantityConfigNR-r15[1] SEQUENCE {		entry 1
measQuantityCellNR-r15 SEQUENCE {
filterCoeff-RSRP-r15	fc0
filterCoeff-RSRQ-r15	fc0
filterCoefficient-SINR-r13	fc0
}
}
}
}

Table 8.2.3.1.1.3.3-4: MeasObjectNR-GENERIC (NRf1) (Table 8.2.3.1.1.3.3-2)

Derivation Path: TS 36.508 [7], Table 4.6.6-2B
Information Element	Value/remark	Comment	Condition
MeasObjectNR-GENERIC(Freq) ::= SEQUENCE {
carrierFreq-r15	Downlink carrier frequency of NR cell 1
}

Table 8.2.3.1.1.3.3-5: ReportConfig1-B1-NR-r15(-85) (Table 8.2.3.1.1.3.3-2)

Derivation Path: TS 36.508 [7], Table 4.6.6-7AA
Information Element	Value/remark	Comment	Condition
ReportConfig-B1-NR ::= SEQUENCE {
triggerType CHOICE {
reportAmount	infinity
reportQuantityCellNR-r15 SEQUENCE {
ss-rsrp	true
ss-rsrq	true
ss-sinr	true		pc_ss_SINR_Meas
	false
}
}

Table 8.2.3.1.1.3.3-6: MeasurementReport (step 5, Table 8.2.3.1.1.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.6.1-5
Information Element	Value/remark	Comment	Condition
MeasurementReport ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
measurementReport-r8 SEQUENCE {
measResults SEQUENCE {
measId	1
measResultPCell SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
measResultNeighCells CHOICE {
measResultNeighCellListNR-r15 SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultCellNR-r15 {	1 entry
MeasResultCellNR-r15[1] SEQUENCE {		entry 1
pci-r15 [1]	PhysicalCellIdentity of NR Cell 1
measResultCell-r15 [1] SEQUENCE {
rsrpResult-r15	(0..127)
rsrqResult-r15	(0..127)
rs-sinr-Result-r15	(0..127)		pc_ss_SINR_Meas
	Not present
}
measResultRS-IndexList-r15	Not present
cgi-Info-r15	Not present
}
}
}
}
}
}
}
}

Table 8.2.3.1.1.3.3-7: MeasGapConfig(Table 8.2.3.1.1.3.3-2)

Derivation Path: TS 36.331, clause 6.3.5
Information Element	Value/remark	Comment	Condition
MeasGapConfig-GP2 ::= CHOICE {
setup SEQUENCE {
gapOffset CHOICE {
gp1	19	TGRP = 80 ms
}
}
}

Table 8.2.3.1.1.3.3-8: ReportConfig2-B1-NR-r15(-91 + ∆(NRf1)) (Table 8.2.3.1.1.3.3-2)

Derivation Path: TS 36.508 [7], Table 4.6.6-7AA
Information Element	Value/remark	Comment	Condition
ReportConfig-B1-NR ::= SEQUENCE {
triggerType CHOICE {
reportAmount	Infinity
reportQuantityCellNR-r15 SEQUENCE {
ss-rsrp	true
ss-rsrq	true
ss-sinr	true		pc_ss_SINR_Meas
	Not present
}
}
NOTE 1: ∆(NRf1) is derived based on calibration procedure defined in the TS 38.508-1 [4], clause 6.1.3.3

8.2.3.1.2 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / NE-DC

8.2.3.1.2.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state in NE-DC, and, MCG(s) (NR PDCP) and SCG, and performed the inter RAT measurement for E-UTRA cell and not detected entering condition for the event B1 is met }

ensure that {

when { UE detects entering condition for the event B1 is not met }

then { UE does not transmit any MeasurementReport }

}

(2)

with { UE in RRC_CONNECTED state in NE-DC, and, MCG(s) (NR PDCP) and SCG, and having completed the radio bearer establishment and performed the inter RAT measurement for E-UTRA cell and not detected entering condition for the event B1 is met }

ensure that {

when { UE detects entering condition for the event B1 is met }

then { UE transmits a MeasurementReport }

}

(3)

with { UE in RRC_CONNECTED state in NE-DC, and, MCG(s) (NR PDCP) and SCG, and performed the inter RAT measurement for E-UTRA cell and detected entering condition for the event B1 is met }

ensure that {

when { UE detects leaving condition for the event B1 is met }

then { UE does not transmit any MeasurementReport }

}

8.2.3.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.5.1, 5.5.4.1, 5.5.4.7, 5.5.5 and 5.5.5.3. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.5.1]

The network may configure an RRC_CONNECTED UE to perform measurements. The network may configure the UE to report them in accordance with the measurement configuration or perform conditional reconfiguration evaluation in accordance with the conditional reconfiguration. The measurement configuration is provided by means of dedicated signalling i.e. using the RRCReconfiguration or RRCResume.

The network may configure the UE to perform the following types of measurements:

– NR measurements;

– Inter-RAT measurements of E-UTRA frequencies;

– Inter-RAT measurements of UTRA-FDD frequencies;

– NR sidelink measurements of L2 U2N Relay UEs.

The network may configure the UE to report the following measurement information based on SS/PBCH block(s):

– Measurement results per SS/PBCH block;

– Measurement results per cell based on SS/PBCH block(s);

– SS/PBCH block(s) indexes.

The network may configure the UE to report the following measurement information based on CSI-RS resources:

– Measurement results per CSI-RS resource;

– Measurement results per cell based on CSI-RS resource(s);

– CSI-RS resource measurement identifiers.

The network may configure the UE to perform the following types of measurements for NR sidelink and V2X sidelink:

– CBR measurements.

The network may configure the UE to report the following CLI measurement information based on SRS resources:

– Measurement results per SRS resource;

– SRS resource(s) indexes.

The network may configure the UE to report the following CLI measurement information based on CLI-RSSI resources:

– Measurement results per CLI-RSSI resource;

– CLI-RSSI resource(s) indexes.

The network may configure the UE to report the following Rx-Tx time difference measurement information based on CSI-RS for tracking or PRS:

– UE Rx-Tx time difference measurement result.

The measurement configuration includes the following parameters:

1. Measurement objects: A list of objects on which the UE shall perform the measurements.

– For intra-frequency and inter-frequency measurements a measurement object indicates the frequency/time location and subcarrier spacing of reference signals to be measured. Associated with this measurement object, the network may configure a list of cell specific offsets, a list of ‘exclude-listed’ cells and a list of ‘allow-listed’ cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting. Allow-listed cells are the only ones applicable in event evaluation or measurement reporting.

– The measObjectId of the MO which corresponds to each serving cell is indicated by servingCellMO within the serving cell configuration.

– For inter-RAT E-UTRA measurements a measurement object is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell specific offsets and a list of ‘exclude-listed’ cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting.

– For inter-RAT UTRA-FDD measurements a measurement object is a set of cells on a single UTRA-FDD carrier frequency.

– For NR sidelink measurements of L2 U2N Relay UEs, a measurement object is a single NR sidelink frequency to be measured.

– For CBR measurement of NR sidelink communication, a measurement object is a set of transmission resource pool(s) on a single carrier frequency for NR sidelink communication.

– For CLI measurements a measurement object indicates the frequency/time location of SRS resources and/or CLI-RSSI resources, and subcarrier spacing of SRS resources to be measured.

2. Reporting configurations: A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement reporting configuration consists of the following:

– Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.

– RS type: The RS that the UE uses for beam and cell measurement results (SS/PBCH block or CSI-RS).

– Reporting format: The quantities per cell and per beam that the UE includes in the measurement report (e.g. RSRP) and other associated information such as the maximum number of cells and the maximum number beams per cell to report.

In case of conditional reconfiguration, each configuration consists of the following:

– Execution criteria: The criteria the UE uses for conditional reconfiguration execution.

– RS type: The RS that the UE uses for obtaining beam and cell measurement results (SS/PBCH block-based or CSI-RS-based), used for evaluating conditional reconfiguration execution condition.

3. Measurement identities: For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. And up to 2 measurement identities can be linked to one conditional reconfiguration execution condition.

4. Quantity configurations: The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement. For NR measurements, the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam.

5. Measurement gaps: Periods that the UE may use to perform measurements.

Editor Note: It is FFS whether and how the definition of measurement gap should be updated due to pre-configured MG.

A UE in RRC_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to signalling and procedures in this specification. The measurement object list possibly includes NR measurement object(s), CLI measurement object(s), inter-RAT objects, and L2 U2N Relay objects. Similarly, the reporting configuration list includes NR, inter-RAT, and L2 U2N Relay reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration.

The measurement procedures distinguish the following types of cells:

1. The NR serving cell(s) – these are the SpCell and one or more SCells.

2. Listed cells – these are cells listed within the measurement object(s).

3. Detected cells – these are cells that are not listed within the measurement object(s) but are detected by the UE on the SSB frequency(ies) and subcarrier spacing(s) indicated by the measurement object(s).

For NR measurement object(s), the UE measures and reports on the serving cell(s)/serving Relay UE (for L2 U2N Remote UE), listed cells and/or detected cells. For inter-RAT measurements object(s) of E-UTRA, the UE measures and reports on listed cells and detected cells and, for RSSI and channel occupancy measurements, the UE measures and reports on the configured resources on the indicated frequency. For inter-RAT measurements object(s) of UTRA-FDD, the UE measures and reports on listed cells. For CLI measurement object(s), the UE measures and reports on configured measurement resources (i.e. SRS resources and/or CLI-RSSI resources). For L2 U2N Relay object(s), the UE measures and reports on the serving NR cell(s), as well as the discovered L2 U2N Relay UEs.

Whenever the procedural specification, other than contained in clause 5.5.2, refers to a field it concerns a field included in the VarMeasConfig unless explicitly stated otherwise i.e. only the measurement configuration procedure covers the direct UE action related to the received measConfig.

In NR-DC, the UE may receive two independent measConfig:

– a measConfig, associated with MCG, that is included in the RRCReconfiguration message received via SRB1; and

– a measConfig, associated with SCG, that is included in the RRCReconfiguration message received via SRB3, or, alternatively, included within a RRCReconfiguration message embedded in a RRCReconfiguration message received via SRB1.

In this case, the UE maintains two independent VarMeasConfig and VarMeasReportList, one associated with each measConfig, and independently performs all the procedures in clause 5.5 for each measConfig and the associated VarMeasConfig and VarMeasReportList, unless explicitly stated otherwise.

The configurations related to CBR measurements are only included in the measConfig associated with MCG.

The configurations related to Rx-Tx time difference measurement are only included in the measConfig associated with MCG.

[TS 38.331, clause 5.5.4.1]

If AS security has been activated successfully, the UE shall:

1> for each measId included in the measIdList within VarMeasConfig:

2> if the corresponding reportConfig includes a reportType set to eventTriggered or periodical:

3> if the corresponding measObject concerns NR:

4> if the corresponding reportConfig includes measRSSI-ReportConfig:

5> consider the resource indicated by the rmtc-Config on the associated frequency to be applicable;

4> if the eventA1 or eventA2 is configured in the corresponding reportConfig:

5> consider only the serving cell to be applicable;

4> if the eventA3 or eventA5 is configured in the corresponding reportConfig:

5> if a serving cell is associated with a measObjectNR and neighbours are associated with another measObjectNR, consider any serving cell associated with the other measObjectNR to be a neighbouring cell as well;

4> if corresponding reportConfig includes reportType set to periodical; or

4> for measurement events other than eventA1 or eventA2:

5> if useAllowedCellList is set to true:

6> consider any neighbouring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is included in the allowedCellsToAddModList defined within the VarMeasConfig for this measId;

5> else:

6> consider any neighbouring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is not included in the excludedCellsToAddModList defined within the VarMeasConfig for this measId;

3> else if the corresponding measObject concerns E-UTRA:

4> if eventB1 or eventB2 is configured in the corresponding reportConfig:

5> consider a serving cell, if any, on the associated E-UTRA frequency as neighbour cell;

4> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the excludedCellsToAddModListEUTRAN defined within the VarMeasConfig for this measId;

3> else if the corresponding measObject concerns UTRA-FDD:

4> if eventB1-UTRA-FDD or eventB2-UTRA-FDD is configured in the corresponding reportConfig; or

4> if corresponding reportConfig includes reportType set to periodical:

5> consider a neighbouring cell on the associated frequency to be applicable when the concerned cell is included in the cellsToAddModList defined within the VarMeasConfig for this measId;

3> else if the corresponding measObject concerns L2 U2N Relay UE:

4> if eventY1-Relay is configured in the corresponding reportConfig; or

4> if corresponding reportConfig includes reportType set to periodical:

5> consider any L2 U2N Relay UE detected on the associated frequency to be applicable for this measId;

2> else if the corresponding reportConfig includes a reportType set to reportCGI:

3> consider the cell detected on the associated measObject which has a physical cell identity matching the value of the cellForWhichToReportCGI included in the corresponding reportConfig within the VarMeasConfig to be applicable;

2> else if the corresponding reportConfig includes a reportType set to reportSFTD:

3> if the corresponding measObject concerns NR:

4> if the reportSFTD-Meas is set to true:

5> consider the NR PSCell to be applicable;

4> else if the reportSFTD-NeighMeas is included:

5> if cellsForWhichToReportSFTD is configured in the corresponding reportConfig:

6> consider any NR neighbouring cell detected on the associated measObjectNR which has a physical cell identity that is included in the cellsForWhichToReportSFTD to be applicable;

5> else:

6> consider up to 3 strongest NR neighbouring cells detected based on parameters in the associated measObjectNR to be applicable when the concerned cells are not included in the excludedCellsToAddModList defined within the VarMeasConfig for this measId;

3> else if the corresponding measObject concerns E-UTRA:

4> if the reportSFTD-Meas is set to true:

5> consider the E-UTRA PSCell to be applicable;

2> else if the corresponding reportConfig includes a reportType set to cli-Periodical or cli-EventTriggered:

3> consider all CLI measurement resources included in the corresponding measObject to be applicable;

2> else if the corresponding reportConfig includes a reportType set to rxTxPeriodical:

3> consider all Rx-Tx time difference measurement resources included in the corresponding measObject to be applicable;

2> if the corresponding reportConfig concerns the reporting for NR sidelink communication (i.e. reportConfigNR-SL):

3> consider the transmission resource pools indicated by the tx-PoolMeasToAddModList defined within the VarMeasConfig for this measId to be applicable;

2> if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event):

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

3> if useT312 is set to true in reportConfig for this event:

4> if T310 for the corresponding SpCell is running; and

4> if T312 is not running for corresponding SpCell:

5> start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> else if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells not included in the cellsTriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent cell triggers the event):

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

3> if useT312 is set to true in reportConfig for this event:

4> if T310 for the corresponding SpCell is running; and

4> if T312 is not running for corresponding SpCell:

5> start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> else if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event:

3> remove the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

3> if reportOnLeave is set to true for the corresponding reporting configuration:

4> initiate the measurement reporting procedure, as specified in 5.5.5;

3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:

4> remove the measurement reporting entry within the VarMeasReportList for this measId;

4> stop the periodical reporting timer for this measId, if running;

2> if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable L2 U2N Relay UEs for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first L2 U2N Relay UE triggers the event):

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned L2 U2N Relay UE(s) in the relaysTriggeredList defined within the VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> else if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable L2 U2N Relay UEs not included in the relaysTriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent L2 U2N Relay UE triggers the event):

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned L2 U2N Relay UE(s) in the relaysTriggeredList defined within the VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> else if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the L2 U2N Relay UEs included in the relaysTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event:

3> remove the concerned L2 U2N Relay UE(s) in the relaysTriggeredList defined within the VarMeasReportList for this measId;

3> if reportOnLeave is set to true for the corresponding reporting configuration:

4> initiate the measurement reporting procedure, as specified in 5.5.5;

3> if the relaysTriggeredList defined within the VarMeasReportList for this measId is empty:

4> remove the measurement reporting entry within the VarMeasReportList for this measId;

4> stop the periodical reporting timer for this measId, if running;

2> else if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable transmission resource pools for all measurements taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include an measurement reporting entry for this measId (a first transmission resource pool triggers the event):

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned transmission resource pool(s) in the poolsTriggeredList defined within the VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> else if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable transmission resource pools not included in the poolsTriggeredList for all measurements taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent transmission resource pool triggers the event):

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned transmission resource pool(s) in the poolsTriggeredList defined within the VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> else if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more applicable transmission resource pools included in the poolsTriggeredList defined within the VarMeasReportList for this measId for all measurements taken during timeToTrigger defined within the VarMeasConfig for this event:

3> remove the concerned transmission resource pool(s) in the poolsTriggeredList defined within the VarMeasReportList for this measId;

3> if the poolsTriggeredList defined within the VarMeasReportList for this measId is empty:

4> remove the measurement reporting entry within the VarMeasReportList for this measId;

4> stop the periodical reporting timer for this measId, if running

2> else if the reportType is set to eventTriggered and if the eventId is set to eventD1 and if the entering condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled during timeToTrigger defined within the VarMeasConfig for this event:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

NOTE 1: Void.

2> if reportType is set to periodical and if a (first) measurement result is available:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> if the corresponding reportConfig includes measRSSI-ReportConfig:

4> initiate the measurement reporting procedure as specified in 5.5.5 immediately when RSSI sample values are reported by the physical layer after the first L1 measurement duration;

3> else if the corresponding reportConfig includes the ul-DelayValueConfig:

4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity;

3> else if the corresponding reportConfig includes the ul-ExcessDelayConfig:

4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity(ies) according to the configured threshold per DRB identity(ies);

3> else if the reportAmount exceeds 1:

4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell or for the serving L2 U2N Relay UE (if the UE is a L2 U2N Remote UE);

3> else (i.e. the reportAmount is equal to 1):

4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell and for the strongest cell among the applicable cells, or for the NR SpCell and for the strongest L2 U2N Relay UEs among the applicable L2 U2N Relay UEs; or initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the serving L2 U2N Relay UE and for the strongest cell among the applicable cells (if the UE is a L2 U2N Remote UE);

2> if, in case the corresponding reportConfig concerns the reporting for NR sidelink communication, reportType is set to periodical and if a (first) measurement result is available:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell and CBR measurement results become available;

2> if the reportType is set to cli-EventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable CLI measurement resources for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first CLI measurement resource triggers the event):

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned CLI measurement resource(s) in the cli-TriggeredList defined within the VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> else if the reportType is set to cli-EventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more CLI measurement resources not included in the cli-TriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent CLI measurement resource triggers the event):

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned CLI measurement resource(s) in the cli-TriggeredList defined within the VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> else if the reportType is set to cli-EventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the CLI measurement resources included in the cli-TriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event:

3> remove the concerned CLI measurement resource(s) in the cli-TriggeredList defined within the VarMeasReportList for this measId;

3> if reportOnLeave is set to true for the corresponding reporting configuration:

4> initiate the measurement reporting procedure, as specified in 5.5.5;

3> if the cli-TriggeredList defined within the VarMeasReportList for this measId is empty:

4> remove the measurement reporting entry within the VarMeasReportList for this measId;

4> stop the periodical reporting timer for this measId, if running;

2> if reportType is set to cli-Periodical and if a (first) measurement result is available:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for at least one CLI measurement resource;

2> if reportType is set to rxTxPeriodical and if a (first) measurement result is available:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> upon expiry of the periodical reporting timer for this measId:

3> initiate the measurement reporting procedure, as specified in 5.5.5.

2> if the corresponding reportConfig includes a reportType is set to reportSFTD:

3> if the corresponding measObject concerns NR:

4> if the drx-SFTD-NeighMeas is included:

5> if the quantity to be reported becomes available for each requested pair of PCell and NR cell:

6> stop timer T322;

6> initiate the measurement reporting procedure, as specified in 5.5.5;

4> else

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for each requested pair of PCell and NR cell or the maximal measurement reporting delay as specified in TS 38.133 [14];

3> else if the corresponding measObject concerns E-UTRA:

4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the pair of PCell and E-UTRA PSCell or the maximal measurement reporting delay as specified in TS 38.133 [14];

2> if reportType is set to reportCGI:

3> if the UE acquired the SIB1 or SystemInformationBlockType1 for the requested cell; or

3> if the UE detects that the requested NR cell is not transmitting SIB1 (see TS 38.213 [13], clause 13):

4> stop timer T321;

4> include a measurement reporting entry within the VarMeasReportList for this measId;

4> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

4> initiate the measurement reporting procedure, as specified in 5.5.5;

2> upon the expiry of T321 for this measId:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5.

2> upon the expiry of T322 for this measId:

3> initiate the measurement reporting procedure, as specified in 5.5.5.

[TS 38.331, clause 5.5.4. 8]

The UE shall:

1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled.

Inequality B1-1 (Entering condition)

Mn + Ofn + Ocn – Hys > Thresh

Inequality B1-2 (Leaving condition)

Mn + Ofn + Ocn + Hys < Thresh

The variables in the formula are defined as follows:

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.

Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra-Q-OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the neighbour inter-RAT cell, utra-FDD-Q-OffsetRange as defined within the measObjectUTRA-FDD corresponding to the frequency of the neighbour inter-RAT cell).

Ocn is the cell specific offset of the inter-RAT neighbour cell (i.e. cellIndividualOffset as defined within the measObjectEUTRA corresponding to the neighbour inter-RAT cell), and set to zero if not configured for the neighbour cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).

Thresh is the threshold parameter for this event (i.e. b1-ThresholdEUTRA as defined within reportConfigInterRAT for this event, b1-ThresholdUTRA-FDD as defined for UTRA-FDD within reportConfigInterRAT for this event).

Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.

Ofn, Ocn, Hys are expressed in dB.

Thresh is expressed in the same unit as Mn.

[TS 38.331, clause 5.5.5]

Figure 5.5.5-1: Measurement reporting

The purpose of this procedure is to transfer measurement results from the UE to the network. The UE shall initiate this procedure only after successful security activation.

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> set the measResultServingCell within measResultServingMOList to include, for each NR serving cell that is configured with servingCellMO, RSRP, RSRQ and the available SINR, derived based on the rsType if indicated in the associated reportConfig, otherwise based on SSB if available, otherwise based on CSI-RS;

1> set the measResultServingCell within measResultServingMOList to include for each NR serving cell that is configured with servingCellMO, if any, the servCellId;

1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRsIndexes and maxNrofRSIndexesToReport:

2> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2;

…

1> if there is at least one applicable neighbouring cell to report:

2> if the reportType is set to eventTriggered or periodical:

3> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:

4> if the reportType is set to eventTriggered:

5> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;

…

4> for each cell that is included in the measResultNeighCells, include the physCellId;

4> if the reportType is set to eventTriggered or periodical:

5> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

6> if the measObject associated with this measId concerns NR:

7> if rsType in the associated reportConfig is set to ssb:

8> set resultsSSB-Cell within the measResult to include the SS/PBCH block based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first:

9> if reportQuantityRsIndexesand maxNrofRSIndexesToReport are configured, include beam measurement information as described in 5.5.5.2;

…

6> if the measObject associated with this measId concerns E-UTRA:

7> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfigInterRAT in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;

…

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

…

1> if the UE is configured with EN-DC:

2> if SRB3 is configured:

3> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;

2> else:

3> submit the MeasurementReport message via the EUTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10].

1> else:

2> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.

8.2.3.1.2.3 Test description

8.2.3.1.2.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell and E-UTRA Cell 1 is the PSCell.

UE:

– None.

Preamble:

– The UE is in state NE-DC RRC_CONNECTED using generic procedure parameter Connectivity (NE-DC) according to TS 38.508-1 [4], Table 4.5.4.2-6.

8.2.3.1.2.3.2 Test procedure sequence

Table 8.2.3.1.2.3.2-1 and Table 8.2.3.1.2.3.2-2 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.3.1.2.3.2-1: Time instances of cell power level and parameter changes for FR1

	Parameter	Unit	E-UTRA Cell 1	NR Cell 1	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-93	–	The power level values are such that entering conditions for event B1 are not satisfied.
T0	SS/PBCH SSS EPRE	dBm/SCS	–	-85
T1	Cell-specific RS EPRE	dBm/15kHz	-73	–	The power level values are such that entering conditions for event B1 are satisfied.
T1	SS/PBCH SSS EPRE	dBm/SCS	–	-85
T2	Cell-specific RS EPRE	dBm/15kHz	-93	–	The power level values are such that leaving conditions for event B1 are satisfied.
T2	SS/PBCH SSS EPRE	dBm/SCS	–	-85

Table 8.2.3.1.2.3.2-2: Time instances of cell power level and parameter changes for FR2

	Parameter	Unit	E-UTRA Cell 1	NR Cell 1	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-93	–	The power level values are such that entering conditions for event B1 are not satisfied.
T0	SS/PBCH SSS EPRE	dBm/SCS	–	-82
T1	Cell-specific RS EPRE	dBm/15kHz	-73	–	The power level values are such that entering conditions for event B1 are satisfied.
T1	SS/PBCH SSS EPRE	dBm/SCS	–	-82
T2	Cell-specific RS EPRE	dBm/15kHz	-93	–	The power level values are such that leaving conditions for event B1 are satisfied.
T2	SS/PBCH SSS EPRE	dBm/SCS	–	-82

Table 8.2.3.1.2.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCReconfiguration including measConfig to setup inter RAT measurements and reporting for E-UTRA Cell 1.	<–	RRCReconfiguration	–	–
2	The UE transmits an RRCReconfigurationComplete message to confirm the setup of inter RAT measurements for E-UTRA Cell 1.	–>	RRCReconfigurationComplete	–	–
3	Check: Does the UE transmit a MeasurementReport message on NR Cell 1 to report the event B1 during the next 10s?	–>	MeasurementReport	1	F
4	The SS changes E-UTRA Cell 1 parameters according to the row "T1".	–	–	–	–
5	Check: Does the UE transmit a MeasurementReport message to report the event B1 for E-UTRA Cell 1?	–>	MeasurementReport	2	P
6	The SS changes E-UTRA Cell 1 parameters according to the row "T2".	–	–	–	–
7	Wait and ignore MeasurementReport messages for 15 s to allow change of power levels and UE measurements for E-UTRA Cell 1.	–	–	–	–
8	Check: Does the UE transmit a MeasurementReport message on NR Cell 1 to report the event B1 during the next 10s?	–>	MeasurementReport	3	F

8.2.3.1.2.3.3 Specific message contents

Table 8.2.3.1.2.3.3-1: RRCReconfiguration (step 1 Table 8.2.3.1.2.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with conditions NR_MEAS and NE-DC

Table 8.2.3.1.2.3.3-2: MeasConfig (Table 8.2.3.1.2.3.3-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-69
Information Element	Value/remark	Comment	Condition
MeasConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod {	2 entries
MeasObjectToAddMod[1] SEQUENCE {		entry 1
measObjectId	1	MeasObjectIdNR-f1
measObject CHOICE {
measObjectNR SEQUENCE {
ssbFrequency	ssbFrequency IE equals the ARFCN for NR Cell 1
absThreshSS-BlocksConsolidation	Not present
}
}
}
MeasObjectToAddMod[2] SEQUENCE {		entry 2
measObjectId	2	MeasObjectIdE-UTRA-f1
measObject CHOICE {
measObjectEUTRA SEQUENCE {
carrierFreq	ARFCN-ValueEUTRA for E-UTRA Cell 1
}
}
}
}
reportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod {	1 entry
ReportConfigToAddMod[1] SEQUENCE {		entry 1
reportConfigId	1
reportConfig CHOICE {
reportConfigInterRAT	ReportConfigInterRAT-EventB1	Table 8.2.3.1.2.3.3-3
}
}
}
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod {	1 entry
MeasIdToAddMod[1] SEQUENCE {		entry 1
measId	1
measObjectId	2
reportConfigId	1
}
}
quantityConfig	QuantityConfig with condition INTER-RAT
measGapConfig	MeasGapConfig
}

Table 8.2.3.1.2.3.3-3: ReportConfigInterRAT-EventB1 (Table 8.2.3.1.2.3.3-2)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-141 with condition EVENT_B1
Information Element	Value/remark	Comment	Condition
ReportConfigNR ::= SEQUENCE {
reportType CHOICE {
eventTriggered SEQUENCE {
eventId CHOICE {
eventB1 SEQUENCE {
b1-ThresholdEUTRA SEQUENCE {
rsrp	61	-80dBm
}
}
}
reportAmount	r1
}
}
}

Table 8.2.3.1.2.3.3-4: QuantityConfig with condition INTER-RAT (Table 8.2.3.1.2.3.3-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-127 with condition INTER-RAT

Table 8.2.3.1.2.3.3-5: MeasurementReport (step 5, Table 8.2.3.1.2.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-5A
Information Element	Value/remark	Comment	Condition
MeasurementReport ::= SEQUENCE {
criticalExtensions CHOICE {
measurementReport SEQUENCE {
measResults SEQUENCE {
measId	1		Step 5
measResultServingMOList SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResultServMO {	1 entry	Report NR Cell 1
MeasResultServMO[1] SEQUENCE {		entry 1
servCellId	ServCellIndex of NR Cell 1
measResultServingCell SEQUENCE {
physCellId	Physical layer cell identity of NR Cell 1
measResult SEQUENCE {
cellResults SEQUENCE {
resultsSSB-Cell SEQUENCE {
rsrp	(0..127)
rsrq	(0..127)
sinr	Not present
	Not checked		pc_ss_SINR_Meas
}
}
}
}
}
}
measResultNeighCells CHOICE {
measResultListEUTRA SEQUENCE (SIZE (1.. maxCellReport)) OF MeasResultEUTRA {	1 entry	Report E-UTRA neighbour cell
MeasResultEUTRA[1] SEQUENCE {		entry 1
eutra-PhysCellId	Physical layer cell identity of E-UTRA Cell 1		Step 5
measResult SEQUENCE {
rsrp	(0..97)
rsrq	(0..34)
sinr	Not present
}
cgi-Info	Not present
}
}
}
}
}
}

8.2.3.2 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / RSRQ based measurements

8.2.3.2.1 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / RSRQ based measurements / EN-DC

8.2.3.2.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state having completed the radio bearer establishment and performed the inter RAT measurement for NR cell, configured b1-Threshold set to threshold-RSRQ and not detected entering condition for the event B1 is met }

ensure that {

when { UE detects entering condition for the event B1 is not met }

then { UE does not transmit any MeasurementReport }

}

(2)

ensure that {

when { UE detects entering condition for the event B1 is met }

then { UE transmits a MeasurementReport }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state having completed the radio bearer establishment and performed the inter RAT measurement for NR cell, configured b1-Threshold set to threshold-RSRQ and detected entering condition for the event B1 is met }

ensure that {

when { UE detects leaving condition for the event B1 is met }

then { UE does not transmit any MeasurementReport }

}

8.2.3.2.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.5.1, 5.5.4.1, 5.5.4.7, 5.5.5.1 and 5.5.5.3. Unless otherwise stated these are Rel-15 requirements.

[TS 36.331, clause 5.5.1]

The UE can be requested to perform the following types of measurements:

– Intra-frequency measurements: measurements at the downlink carrier frequency(ies) of the serving cell(s).

– Inter-frequency measurements: measurements at frequencies that differ from any of the downlink carrier frequency(ies) of the serving cell(s).

– Inter-RAT measurements of NR frequencies.

…

The measurement configuration includes the following parameters:

1. Measurement objects: The objects on which the UE shall perform the measurements.

…

2. Reporting configurations: A list of reporting configurations where each reporting configuration consists of the following:

– Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.

– Reporting format: The quantities that the UE includes in the measurement report and associated information (e.g. number of cells to report).

4. Quantity configurations: One quantity configuration is configured per RAT type. The quantity configuration defines the measurement quantities and associated filtering used for all event evaluation and related reporting of that measurement type. One filter can be configured per measurement quantity, except for NR where the network may configure up to 2 sets of quantity configurations each comprising per measurement quantity seperate filters for cell and RS index measurement results. The quantity configuration set that applies for a given measurement is indicated within the NR measurement object.

5. Measurement gaps: Periods that the UE may use to perform measurements, i.e. no (UL, DL) transmissions are scheduled.

E-UTRAN only configures a single measurement object for a given frequency (except for WLAN and except for CBR measurements), i.e. it is not possible to configure two or more measurement objects for the same frequency with different associated parameters, e.g. different offsets and/ or blacklists. E-UTRAN may configure multiple instances of the same event e.g. by configuring two reporting configurations with different thresholds.

The UE maintains a single measurement object list, a single reporting configuration list, and a single measurement identities list. The measurement object list includes measurement objects, that are specified per RAT type, possibly including intra-frequency object(s) (i.e. the object(s) corresponding to the serving frequency(ies)), inter-frequency object(s) and inter-RAT objects. Similarly, the reporting configuration list includes E-UTRA and inter-RAT reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration.

[TS 36.331, clause 5.5.4.1]

If security has been activated successfully, the UE shall:

1> for each measId included in the measIdList within VarMeasConfig:

…

2> else:

…

3> else if the corresponding measObject concerns NR:

4> if the reportSFTD-Meas is set to pSCell in the corresponding reportConfigInterRAT:

5> consider the PSCell to be applicable;

4> else if the reportSFTD-Meas is set to neighborCells in the corresponding reportConfigInterRAT:

5> if cellsForWhichToReportSFTD is configured in the corresponding measObjectNR:

6> consider any neighbouring NR cell on the associated frequency that is included in cellsForWhichToReportSFTD to be applicable;

5> else:

6> consider up to 3 strongest neighbouring NR cells detected on the associated frequency to be applicable when the concerned cells are not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

…

2> else if the purpose is included and set to reportStrongestCells, reportStrongestCellsForSON, reportLocation sidelink or sensing sidelink and if a (first) measurement result is available:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> if the purpose is set to reportStrongestCells and reportStrongestCSI-RSs is not included:

4> if the triggerType is set to periodical and the corresponding reportConfig includes the ul-DelayConfig:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided by lower layers;

…

4> else if the reportAmount exceeds 1:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the PCell;

4> else (i.e. the reportAmount is equal to 1):

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the PCell and for the strongest cell among the applicable cells, or becomes available for the pair of PCell and the PSCell in case of SSTD measurements, or becomes available for each requested pair of PCell and NR cell or the maximal measurement reporting delay as specified in TS 38.133 [84, 8.17.2.3] in case of SFTD measurements;

…

3> else:

4> initiate the measurement reporting procedure, as specified in 5.5.5, when it has determined the strongest cells on the associated frequency;

2> upon expiry of the periodical reporting timer for this measId:

3> initiate the measurement reporting procedure, as specified in 5.5.5;

…

NOTE 2: The UE does not stop the periodical reporting with triggerType set to event or to periodical while the corresponding measurement is not performed due to the PCell RSRP being equal to or better than s-Measure or due to the measurement gap not being setup.

NOTE 3: If the UE is configured with DRX, the UE may delay the measurement reporting for event triggered and periodical triggered measurements until the Active Time, which is defined in TS 36.321 [6].

[TS 36.331, clause 5.5.4.7]

The UE shall:

1> for UTRA and CDMA2000, only trigger the event for cells included in the corresponding measurement object;

1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled;

Inequality B1-1 (Entering condition)

Inequality B1-2 (Leaving condition)

The variables in the formula are defined as follows:

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. For CDMA 2000 measurement result, pilotStrength is divided by -2.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).

Thresh is the threshold parameter for this event (i.e. b1-Threshold as defined within reportConfigInterRAT for this event). For CDMA2000, b1-Threshold is divided by -2.

Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.

Ofn, Hys are expressed in dB.

Thresh is expressed in the same unit as Mn.

[TS 36.331, clause 5.5.5.1]

Figure 5.5.5.1-1: Measurement reporting

The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN. The UE shall initiate this procedure only after successful security activation.

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> set the measResultPCell to include the quantities of the PCell;

1> set the measResultServFreqList to include for each E-UTRA SCell that is configured, if any, within measResultSCell the quantities of the concerned SCell, if available according to performance requirements in [16], except if purpose for the reportConfig associated with the measId that triggered the measurement reporting is set to reportLocation;

1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

2> for each E-UTRA serving frequency for which measObjectId is referenced in the measIdList, other than the frequency corresponding with the measId that triggered the measurement reporting:

3> set the measResultServFreqList to include within measResultBestNeighCell the physCellId and the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

1> if the triggerType is set to event; and if the corresponding measObject concerns NR; and if eventId is set to eventB1 or eventB2; or

1> if the triggerType is set to event; and if eventId is set to eventA3 or eventA4 or eventA5:

2> if purpose for the reportConfig associated with the measId that triggered the measurement reporting is set to a value other than reportLocation:

3> set the measResultServFreqListNR to include for each NR serving frequency, if any, the following:

4> set measResultSCell to include the available results of the NR serving cell, as specified in 5.5.5.2;

4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

5> set measResultBestNeighCell to include the available results, as specified in 5.5.5.2, of the best non-serving cell, ordered based on the quantity determined as specified in 5.5.5.3;

5> for each (serving or neighbouring) cell for which the UE reports results according to the previous, additionally include available beam results according to the following:

6> if maxReportRS-Index is configured, set measResultCellRS-Index to include available results, as specified in 5.5.5.2, of up to maxReportRS-Index beams, ordered based on the quantity determined as specified in 5.5.5.3;

1> if there is at least one applicable neighbouring cell to report:

2> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:

3> if the triggerType is set to event:

4> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;

3> else:

4> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

3> for each cell that is included in the measResultNeighCells, include the physCellId;

3> if the triggerType is set to event; or the purpose is set to reportStrongestCells or to reportStrongestCellsForSON:

4> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

5> if the measObject associated with this measId concerns E-UTRA:

6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfig in order of decreasing triggerQuantity, i.e. the best cell is included first;

5> if the measObject associated with this measId concerns NR:

6> set the measResultCell to include the quantity(ies) indicated in the reportQuantityCellNR within the concerned reportConfig in order of decreasing quantity according to bN-ThresholdYNR, i.e. the best cell is included first;

6> if maxReportRS-Index and reportQuantityRS-IndexNR are configured, set measResultCellRS-Index to include results of the best beam and the beams whose quantity is above threshRS-Index defined in the VarMeasConfig for the corresponding measObject, up to maxReportRS-Index beams in total, and in order of decreasing quantity, same as used for cell reporting, and as follows:

7> order beams based on the sorting quantity determined as specified in 5.5.5.2;

7> include ssbIndex;

7> if reportRS-IndexResultsNR is configured, for each quantity indicated, include the corresponding measurement result;

[TS 36.331, clause 5.5.5.3]

When configured to report the best cells or beams, the UE shall determine the quantity that is used to order and select as follows:

1> consider the quantities the UE reports as candidate sorting quantities i.e. as follows:

2> for NR cells for which measurement reporting is triggered (i.e. NR cells included in cellsTriggered):

3> the quantities defined by reportQuantityCellNR, when used for sorting cells;

3> the quantities defined by reportQuantityRS-IndexNR, when used for sorting beams;

2> for cells on NR serving frequencies:

3> the available quanties of available NR measurement results as specified in 5.5.5.2;

1> if reportType is set to eventTriggered; and if eventId is set to eventB1 or eventB2:

2> consider the trigger quantity to be the sorting quantity;

1> if reportType is set to periodical:

2> if there is a single candidate sorting quantity;

3> consider the concerned quantity to be the sorting quantity;

2> else:

3> if RSRP is one of the candidate sorting quantityies;

4> consider RSRP to be the sorting quantity;

3> else:

4> consider RSRQ to be the sorting quantity;

8.2.3.2.1.3 Test description

8.2.3.2.1.3.1 Pre-test conditions

System Simulator:

– E-UTRA Cell 1 and NR Cell 1.

– NR Cell 1 is configured to operate in FR1 bands as defined in TS 38.508-1 [4] clause 6.2.3.

UE:

– None.

Preamble:

– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (E-UTRA/EPC) established according to TS 38.508-1 [4], clause 4.5.4.

8.2.3.2.1.3.2 Test procedure sequence

Table 8.2.3.2.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.3.2.1.3.2-1: Time instances of cell power level and parameter changes for conducted test environment

	Parameter	Unit	E-UTRA Cell 1	NR Cell 1	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-85	–	The power level values are such that entering conditions for event B1 are not satisfied.
	SS/PBCH SSS EPRE	dBm/SCS	–	-91
	SS-RSRQ	dB	–	-16.24
	Noc	dBm/SCS	–	-87
T1	Cell-specific RS EPRE	dBm/15kHz	-85	–	The power level values are such that entering conditions for event B1 are satisfied.
	SS/PBCH SSS EPRE	dBm/SCS	–	-85
	SS-RSRQ	dB	–	-12.91
	Noc	dBm/SCS	–	-87
T2	Cell-specific RS EPRE	dBm/15kHz	-85	–	The power level values are such that leaving conditions for event B1 are satisfied.
	SS/PBCH SSS EPRE	dBm/SCS	–	-91
	SS-RSRQ	dB	–	-16.24
	Noc	dBm/SCS	–	-87

Table 8.2.3.2.1.3.2-1A: Void

Table 8.2.3.2.1.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration including measConfig to setup inter RAT measurements and reporting for NR Cell 1.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of inter RAT measurements for NR Cell 1.	–>	RRCConnectionReconfigurationComplete	–	–
3	Check: Does the UE transmit a MeasurementReport message on E-UTRA Cell 1 to report the event B1 during the next 10s?	–>	MeasurementReport	1	F
4	The SS changes E-UTRA Cell 1 and NR Cell 1 parameters according to the row "T1".	–	–	–	–
5	Check: Does the UE transmit a MeasurementReport message to report the event B1 for NR Cell 1?	–>	MeasurementReport	2	P
6	The SS changes E-UTRA Cell 1 and NR Cell 1 parameters according to the row "T2".	–	–	–	–
7	Wait and ignore MeasurementReport messages for 15 s to allow change of power levels and UE measurements for NR Cell 1.	–	–	–	–
8	Check: Does the UE transmit a MeasurementReport message on E-UTRA Cell 1 to report the event B1 during the next 10s?	–>	MeasurementReport	3	F

8.2.3.2.1.3.3 Specific message contents

Table 8.2.3.2.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.3.2.1.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.6.1-8, condition MEAS

Table 8.2.3.2.1.3.3-2: MeasConfig (Table 8.2.3.2.1.3.3-1)

Derivation Path: TS 36.508 [7], Table 4.6.6-1
Information Element	Value/remark	Comment	Condition
MeasConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF MeasObjectToAddMod {	2 entries
MeasObjectToAddMod[1] SEQUENCE {		entry 1
measObjectId	IdMeasObject-f1
measObject	MeasObjectEUTRA-GENERIC(f1)
	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
}
MeasObjectToAddMod[2] SEQUENCE {		entry 2
measObjectId	IdMeasObject-NRf1
measObject	MeasObjectNR-GENERIC (NRf1)
}
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod {	1 entry
ReportConfigToAddMod[1] SEQUENCE {		entry 1
reportConfigId	IdReportConfig-B1-NR
reportConfig	ReportConfig-B1-NR-r15
}
}
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF MeasIdToAddMod {	1 entry
MeasIdToAddMod[1] SEQUENCE {		entry 1
measId	1
measObjectId	IdMeasObject-NRf1
reportConfigId	IdReportConfig-B1-NR
}
}
quantityConfig	QuantityConfig-DEFAULT
measGapConfig	MeasGapConfig
}

Table 8.2.3.2.1.3.3-3: QuantityConfig-DEFAULT (Table 8.2.3.2.1.3.3-2)

Derivation Path: TS 36.508 [7], Table 4.6.6-3A
Information Element	Value/remark	Comment	Condition
QuantityConfig-DEFAULT ::= SEQUENCE {
quantityConfigNRList-r15 SEQUENCE ((SIZE (1..maxQuantSetsNR-r15)) OF QuantityConfigNR-r15 {	1 entry
QuantityConfigNR-r15[1] SEQUENCE {		entry 1
measQuantityCellNR-r15 SEQUENCE {
filterCoeff-RSRP-r15	fc4
filterCoeff-RSRQ-r15	fc4
}
}
}
}

Table 8.2.3.2.1.3.3-4: MeasObjectNR-GENERIC (NRf1) (Table 8.2.3.2.1.3.3-2)

Derivation Path: TS 36.508 [7], Table 4.6.6-2B
Information Element	Value/remark	Comment	Condition
MeasObjectNR-GENERIC(Freq) ::= SEQUENCE {
carrierFreq-r15	Downlink carrier frequency of NR cell 1
}

Table 8.2.3.2.1.3.3-5: ReportConfig-B1-NR-r15 (Table 8.2.3.2.1.3.3-2)

Derivation Path: TS 36.508 [7], Table 4.6.6-7AA
Information Element	Value/remark	Comment	Condition
ReportConfig-B1-NR ::= SEQUENCE {
triggerType CHOICE {
event SEQUENCE {
eventId CHOICE {
eventB1-NR-r15 SEQUENCE{
b1-ThresholdNR-r15 CHOICE {
nr-RSRQ-r15	58
}
}
}
}
reportAmount	infinity
reportQuantityCellNR-r15 SEQUENCE {
ss-rsrq	true
}

Table 8.2.3.2.1.3.3-6: MeasurementReport (step 5, Table 8.2.3.2.1.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.6.1-5
Information Element	Value/remark	Comment	Condition
MeasurementReport ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
measurementReport-r8 SEQUENCE {
measResults SEQUENCE {
measId	1
measResultPCell SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
measResultNeighCells CHOICE {
measResultNeighCellListNR-r15 SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultCellNR-r15 {	1 entry
MeasResultCellNR-r15[1] SEQUENCE {		entry 1
pci-r15	PhysicalCellIdentity of NR Cell 1
measResultCell-r15 SEQUENCE {
rsrqResult-r15	(0..127)
}
}
}
}
}
}
}
}
}

Table 8.2.3.2.1.3.3-7: MeasGapConfig(Table 8.2.3.2.1.3.3-2)

Derivation Path: TS 36.331, clause 6.3.5
Information Element	Value/remark	Comment	Condition
MeasGapConfig-GP2 ::= CHOICE {
setup SEQUENCE {
gapOffset CHOICE {
gp1	19	TGRP = 80 ms
}
}
}

8.2.3.2.2 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / NE-DC

8.2.3.2.2.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state in NE-DC, and, MCG(s) (NR PDCP) and SCG, and performed the inter RAT measurement for E-UTRA cell and not detected entering condition for the event B1 is met }

ensure that {

when { UE detects entering condition for the event B1 is not met }

then { UE does not transmit any MeasurementReport }

}

(2)

with { UE in RRC_CONNECTED state in NE-DC, and, MCG(s) (NR PDCP) and SCG, and having completed the radio bearer establishment and performed the inter RAT measurement for E-UTRA cell and configured b1-Threshold set to threshold-RSRQ and not detected entering condition for the event B1 is met }

ensure that {

when { UE detects entering condition for the event B1 is met }

then { UE transmits a MeasurementReport }

}

(3)

with { UE in RRC_CONNECTED state in NE-DC, and, MCG(s) (NR PDCP) and SCG, and performed the inter RAT measurement for E-UTRA cell and configured b1-Threshold set to threshold-RSRQ and detected entering condition for the event B1 is met}

ensure that {

when { UE detects leaving condition for the event B1 is met }

then { UE does not transmit any MeasurementReport }

}

8.2.3.2.2.2 Conformance requirements