8.1.6 SON and MDT support for NR

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

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

8.1.6.1 Intra NR MDT

8.1.6.1.1 Immediate MDT

8.1.6.1.1.1 Immediate MDT / Measurement reporting / Location information

8.1.6.1.1.1.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and measurement with event A2 configured with includeLocationInfo included in the reportConfig }

ensure that {

when { Entry condition for event A2 is met and detailed location information that has not been reported is available }

then { UE sends MeasurementReport message with locationInfo included }

}

(2)

with { UE in RRC_CONNECTED state and measurement configured for event A2 }

ensure that {

when { Exit condition for event A2 is met }

then { UE stops sending MeasurementReport message }

}

8.1.6.1.1.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.5.3, 5.5.4.1, 5.5.4.3, 5.5.5.1.

[TS 38.331, clause 5.3.5.3]

The UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO or CPC):

…

1> if the RRCReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

…

[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 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 useWhiteCellList 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 whiteCellsToAddModList 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 blackCellsToAddModList defined within the VarMeasConfig for this measId;

…

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

…

[TS 38.331, clause 5.5.4.3]

The UE shall:

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

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

1> for this measurement, consider the serving cell indicated by the measObjectNR associated to this event.

Inequality A2-1 (Entering condition)

Ms + Hys < Thresh

Inequality A2-2 (Leaving condition)

Ms – Hys > Thresh

The variables in the formula are defined as follows:

Ms is the measurement result of the serving cell, not taking into account any offsets.

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

Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within reportConfigNR for this event).

Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

[TS 38.331, clause 5.5.5.1]

…

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> if there is at least one applicable neighbouring cell to report:

…

1> if the includeCommonLocationInfo is configured in the corresponding reportConfig for this measId and detailed location information that has not been reported is available, set the content of commonLocationInfo of the locationInfo as follows:

2> include the locationTimestamp;

2> include the locationCoordinate, if available;

2> include the velocityEstimate, if available;

2> include the locationError, if available;

2> include the locationSource, if available;

2> if available, include the gnss-TOD-msec,

…

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 numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

1> else:

2> if the reportType is set to periodical or cli-Periodical:

3> remove the entry within the VarMeasReportList for this measId;

3> remove this measId from the measIdList within VarMeasConfig;

8.1.6.1.1.1.3 Test description

8.1.6.1.1.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1

Preamble:

– The UE’s positioning engine (e.g. standalone GNSS receiver) should be provided with any necessary stimulus to allow it to provide the position. This shall be done by use of the test function Update UE Location Information defined in TS 38.509 [6], if supported by the UE according to pc_UpdateUE_LocationInformation. Otherwise, or in addition any other suitable method may also be used.

– The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.

8.1.6.1.1.1.3.2 Test procedure sequence

Table 8.1.6.1.1.1.3.2-1 and Table 8.1.6.1.1.1.3.2-1a illustrate the downlink power levels to be applied for NR Cell 1 at various time instants of the test execution. Row marked "T0" denotes the initial conditions after the preamble, while rows 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.1.6.1.1.1.3.2-1: Time instances of cell power level and parameter changes for FR1

	Parameter	Unit	NR Cell 1	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	-78	Power level is such that Ms > Thresh + Hys
T1	SS/PBCH SSS EPRE	dBm/SCS	-98	Power level is such that entry condition for event A2 is satisfied Ms + Hys < Thresh
T2	SS/PBCH SSS EPRE	dBm/SCS	-78	Power level is such that exit condition for event A2 is satisfied Ms – Hys > Thresh

Table 8.1.6.1.1.1.3.2-1a: Time instances of cell power level and parameter changes for FR2

	Parameter	Unit	NR Cell 1	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	-82	Power level is such that Ms > Thresh + Hys
T1	SS/PBCH SSS EPRE	dBm/SCS	-96	Power level is such that entry condition for event A2 is satisfied Ms + Hys < Thresh
T2	SS/PBCH SSS EPRE	dBm/SCS	-82	Power level is such that exit condition for event A2 is satisfied Ms – Hys > Thresh

Table 8.1.6.1.1.1.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCReconfiguration message including measConfig to setup intra NR measurement and reporting for event A2 with includeLocationInfo configured.	<–	NR RRC: RRCReconfiguration	–	–
2	The UE transmits an RRCReconfigurationComplete message.	–>	NR RRC: RRCReconfigurationComplete	–	–
3	SS re-adjusts the SS/PBCH EPRE level according to row "T1" in Table 8.1.6.1.1.1.3.2-1 or Table 8.1.6.1.1.1.3.2-1a.	–	–	–	–
4	Check: Does the UE transmit a MeasurementReport message to report event A2 with the UE commonLocationInfo included?	–>	NR RRC: MeasurementReport	1	P
5	SS re-adjusts the SS/PBCH EPRE level according to row "T2" in Table 8.1.6.1.1.1.3.2-1 or Table 8.1.6.1.1.1.3.2-1a.	–	–	–	–
6	Wait and ignore MeasurementReport messages for 5 s to allow change of power levels for NR Cell 1.	–	–	–	–
7	Check: Does the UE attempt to transmit MeasurementReport message within the next 10s??	–		2	F

8.1.6.1.1.1.3.3 Specific message contents

Table 8.1.6.1.1.1.3.3-1: RRCReconfiguration (step 1 Table 8.1.6.1.1.1.3.2-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR_MEAS

Table 8.1.6.1.1.1.3.3-2: MeasConfig (Table 8.1.6.1.1.1.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.. maxNrofObjectId)) OF MeasObjectToAddMod {	1 entry
MeasObjectToAddMod[1] SEQUENCE {		entry 1
measObjectId	1
measObject CHOICE {
measObjectNR	MeasObjectNR(57)	Thres=57(-100dBm ≤ SS-RSRP<-99dBm)
}
}
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod {	1 entry
ReportConfigToAddMod[1] SEQUENCE {		entry 1
reportConfigId	1
reportConfig	ReportConfigNR-EventA2
}
}
measIdToAddModList SEQUENCE (SIZE (1.. maxNrofMeasId)) OF MeasIdToAddMod {	1 entry
MeasIdToAddMod[1] SEQUENCE {		entry 1
measId	1
measObjectId	1
reportConfigId	1
}
}
}

Table 8.1.6.1.1.1.3.3-3: ReportConfigNR-EventA2 (Table 8.1.6.1.1.1.3.3-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-142 with condition EVENT_A2
Information Element	Value/remark	Comment	Condition
ReportConfigNR::= SEQUENCE {
reportType CHOICE {
eventTriggered SEQUENCE {
eventId CHOICE {
eventA2 SEQUENCE {			EVENT_A2
a2-Threshold CHOICE {
rsrp	69	-88dBm ≤ SS-RSRP<-87dBm	FR1/FR2
}
hysteresis	0	0 dB	FR1/FR2
}
}
reportAmount	r1
includeCommonLocationInfo-r16	True
}
}
}

Table 8.1.6.1.1.1.3.3-4: MeasurementReport (steps 4, Table 8.1.6.1.1.1.3.2-2)

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 4
measResultServingMOList SEQUENCE {	1 entry
servCellId	ServCellIndex of NR Cell 1
measResultServingCell SEQUENCE {
physCellId	Physical CellID of the NR Cell 1
measResult SEQUENCE {
cellResults SEQUENCE {
resultsSSB-Cell SEQUENCE {
rsrp	(0..127)
rsrq	(0..127)
sinr	Not present
	(0..127)		pc_ss_SINR_Meas
}
}
}
}
}
locationInfo-r16 SEQUENCE {
commonLocationInfo-r16 SEQUENCE {
gnss-TOD-msec-r16	Any allowed value
locationTimestamp-r16	Any allowed value
locationCoordinate-r16	Any allowed value
locationError-r16	Not checked
locationSource-r16	Any allowed value
velocityEstimate-r16	Any allowed value
}
}
}
}
}
}

8.1.6.1.1.2 Immediate MDT / Measurement / Latency metrics for UL PDCP Packet Delay per DRB

8.1.6.1.1.2.1 Test Purpose (TP)

(1)

with {UE supporting UL PDCP Packet Delay per DRB measurement and in RRC_CONNECTED state}

ensure that {

when {UE receives RRCReconfiguration containing ReportConfigNR IE with ul-DelayValueConfig IE set to “setup”}

then {UE sends the RRCReconfigurationComplete message}

}

(2)

with {UE in RRC_CONNECTED and measurement configured for UL PDCP Packet Delay per DRB and having DRBs established}

ensure that {
when {UE determines that UL PDCP SDUs per DRB}

then {UE sends the MeasurementReport message with ul-PDCP-DelayResultList for corresponding DRB}

}

(3)

with { UE in RRC_CONNECTED and measurement configured for UL PDCP Packet Delay per DRB}

ensure that {

when {UE receives RRCReconfiguration containing ReportConfigNR IE with ul-DelayConfig IE set to “release”)

then {UE stops monitoring the UL PDCP Packet Delay per DRB}

}

8.1.6.1.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.5.3.1, 5.5.4.1, 5.5.5.1 & TS 38.314, clause 4.3.1.1

[TS 38.331, clause 5.5.3.1]

…

The UE shall:

…

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

…

2> if the ul-DelayValueConfig is configured for the associated reportConfig:

3> ignore the measObject;

3> for each of the configured DRBs, configure the PDCP layer to perform corresponding average UL PDCP packet delay measurement per DRB;

…

[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 the ul-DelayValueConfig:

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

…

[TS 38.331, clause 5.5.5.1]

…

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

…

1> if average uplink PDCP delay values are available:

2> set the ul-PDCP-DelayValueResultList to include the corresponding average uplink PDCP delay values;

…

[TS 38.314, clause 4.3.1.1]

The objective of this measurement performed by UE is to measure Packet Delay in Layer PDCP for QoS verification of MDT or for the QoS monitoring as defined in TS 23.501.

Protocol Layer: PDCP

Table 4.3.1.1-1: Definition for UL PDCP Packet Average Delay per DRB per UE

Definition

PDCP Packet Delay in the UL per DRB. This measurement refers to PDCP queuing delay for DRBs in the UE, which captures the delay from packet arrival at PDCP upper SAP until the UL grant to transmit the packet is available, which has included the delay the UE gets resources granted (from sending SR/RACH to get the first grant). The measurement is done separately per DRB.

Detailed Definition:

where

explanations can be found in the table 4.3.1.1-2 below.

NOTE: UE measures UL PDCP queueing delay at DRB level. It is up to gNB to convert DRB level delay to QoS level delay with the assumption that all QoS flows mapped to the same DRB get the same QoS treatment, and it is up to gNB to calculate QoS level delay if multiple DRBs mapped with the same QoS.

Table 4.3.1.1-2: Parameter description for UL PDCP Packet Average Delay per DRB per UE

	PDCP average delay in the UL per DRB, averaged during time period 𝑇. Unit: 0.1 ms. PDCP average delay in the UL per DRB is 1s if the actual value is larger than 1s.
	The point in time when the UL PDCP SDU i arrivals at PDCP upper SAP.
	The point in time when the UL MAC PDU k including the first part of UL PDCP SDU i is scheduled for transmission.
	A UL PDCP SDU that is received by the PDCP during time period 𝑇.
	Total number of UL PDCP SDUs received during time period 𝑇.
	Time Period during which the measurement is performed
	The identity of the measured DRB.

8.1.6.1.1.2.3 Test description

8.1.6.1.1.2.3.1 Pre-test conditions

System Simulator:

– NR Cell 1

UE:

– None

Preamble:

– The UE is in 5GS state 3N-A with one PDU session active according to TS 38.508-1 [4], clause 4.4A.3 Table 4.4A.3-1.and using the message condition UE TEST LOOP MODE A active. 3 DRBs are configured where DRB#j1 is defined as default DRB.

8.1.6.1.1.2.3.2 Test procedure sequence

Table 8.1.6.1.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCReconfiguration message including MeasConfig to setup ul-DelayValueConfig	<–	NR RRC: RRCReconfiguration	–	–
2	The UE transmits an RRCReconfigurationComplete message	–>	NR RRC: RRCReconfigurationComplete	1	P
	EXCEPTION: In parallel with steps 3-9, parallel behaviour defined in table 8.1.6.1.1.2.3.2-3 is executed to receive periodic measurement report.
3	The SS transmits UL grant to the UE at every 5ms in PDCCH occasion
4	The SS transmits an IP Packet on the data radio bearer associated with the dedicated 5GC bearer context #2
5	The UE loop backs the IP packet received in step 4 on DRB#j+1
5A	Check: Does the UE transmit a MeasurementReport message containing UL-PDCP-DelayValueResult with averageDelay set to non zero value for DRB#j+1 and DRB# j+2?	–>	NR RRC: MeasurementReport	2	P
6	The SS transmits an IP Packet on the data radio bearer associated with the dedicated 5GC bearer context #3
7	The UE loop backs the IP packet received in step 6 on DRB# j+2
8	Check: Does the UE transmit a MeasurementReport message containing UL-PDCP-DelayValueResult for DRB# j+1 and with with averageDelay set to non zero value DRB# j+2?2 and DRB#3?	–>	MeasurementReport	2	P
9	The SS transmits an RRCReconfiguration message including MeasConfig to release the ul-DelayValueConfig measurement	<–	NR RRC: RRCReconfiguration	–	–
10	The UE transmits an RRCReconfigurationComplete message.	–>	NR RRC: RRCReconfigurationComplete
–	EXCEPTION: In parallel with steps 11-14, parallel behaviour defined in table 8.1.6.1.1.2.3.2-2 is executed.	–	–	–	–
11	The SS transmits an IP Packet on the data radio bearer associated with the dedicated 5GC bearer context #2
12	The UE loop backs the IP packet received in step 11 on DRB# j+1
13	The SS transmits an IP Packet on the data radio bearer associated with the dedicated 5GC bearer context #3
14	The UE loop backs the IP packet received in step 13 on DRB#j+2
15	Void	–	–	–	–

Table 8.1.6.1.1.2.3.2-2: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

Check: Does the UE transmit a

MeasurementReport message containing UL-PDCP-DelayValueResult?

–>

MeasurementReport

Table 8.1.6.1.1.2.3.2-3: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmit a

MeasurementReport message

–>

MeasurementReport

–

8.1.6.1.1.2.3.3 Specific message contents

Table 8.1.6.1.1.2.3.3-1: RRCReconfiguration (step 1 and 9, Table 8.1.6.1.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR_MEAS

Table 8.1.6.1.1.2.3.3-2: MeasConfig (Table 8.1.6.1.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.. maxNrofObjectId)) OF MeasObjectToAddMod {	1 entry
MeasObjectToAddMod[1] SEQUENCE {		entry 1
measObjectId	1
measObject CHOICE {
measObjectNR	MeasObjectNR(57)	Thres=57(-100dBm ≤ SS-RSRP<-99dBm)
}
}
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod {	1 entry
ReportConfigToAddMod[1] SEQUENCE {		entry 1
reportConfigId	1
reportConfig	ReportConfigNR- PERIODICAL
}
}
measIdToAddModList SEQUENCE (SIZE (1.. maxNrofMeasId)) OF MeasIdToAddMod {	1 entry
MeasIdToAddMod[1] SEQUENCE {		entry 1
measId	1
measObjectId	1
reportConfigId	1
}
}
}

Table 8.1.6.1.1.2.3.3-3: ReportConfigNR- PERIODICAL (Table 8.1.6.1.1.2.3.3-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-142 with condition PERIODICAL, MDT_DELAY
Information Element	Value/remark	Comment	Condition
ReportConfigNR::= SEQUENCE {
reportType CHOICE {
periodical SEQUENCE {
ul-DelayValueConfig-r16 CHOICE {
setup SEQUENCE {			Step1
delay-DRBlist SEQUENCE (SIZE(1..maxDRB)) OF DRB-Identity {	2 entries
DRB-Identity[1]	j+1	entry 1
DRB-Identity[2]	j+2	entry 2
}
}
Release	NULL		Step9
}
}
}
}

Table 8.1.6.1.1.2.3.3-4: MeasurementReport (steps 5A and 8, Table 8.1.6.1.1.2.3.2-1 and step 1, Table 8.1.6.1.1.2.3.2-2)

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
measResultServingMOList SEQUENCE {	1 entry
servCellId	ServCellIndex of NR Cell 1
measResultServingCell SEQUENCE {
physCellId	Physical CellID of the NR Cell 1
measResult SEQUENCE {
cellResults SEQUENCE {
resultsSSB-Cell SEQUENCE {
rsrp	(0..127)
rsrq	(0..127)
sinr	Not checked
}
}
}
}
}
ul-PDCP-DelayValueResultList-r16 SEQUENCE (SIZE (1..maxDRB)) OF UL-PDCP-DelayValueResult-r16{	2 entries	Step 5A, Table 8.1.6.1.1.2.3.2-1
drb-Id-r16[1]	j+1	entry 1
averageDelay-r16[1]	Any value other than 0
drb-Id-r16[2]	j+2	entry 2
averageDelay-r16[2]	0
}
ul-PDCP-DelayValueResultList-r16 SEQUENCE (SIZE (1..maxDRB)) OF UL-PDCP-DelayValueResult-r16{	2 entries	Step8, Table 8.1.6.1.1.2.3.2-1
drb-Id-r16[1]	j+1	entry 1
averageDelay-r16[1]	0
drb-Id-r16[2]	j+2	entry 2
averageDelay-r16[2]	Any value other than 0
}
ul-PDCP-DelayValueResultList-r16	Present	Step 1, Table 8.1.6.1.1.2.3.2-2
}
}
}
}

Table 8.1.6.1.1.2.3.3-5: RRCReconfiguration (Preamble, Table 8.1.6.1.1.2.3.3-1)

Derivation Path: TS 38.508-1 [4], table 4.6.1-13 with condition NR
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	RadioBearerConfig-3DRBs
nonCriticalExtension SEQUENCE {
masterCellGroup	CellGroupConfig-3DRBs	OCTET STRING (CONTAINING CellGroupConfig)
}
}
}
}

Table 8.1.6.1.1.2.3.3-6: RadioBearerConfig-3DRBs (Table 8.1.6.1.1.2.3.3-4)

Derivation Path: TS 38.508-1 [4], table 4.6.3-132 and condition SRB2 and DRB1
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod {	3 entries
DRB-ToAddMod[1] SEQUENCE {		entry 1
cnAssociation CHOICE {
sdap-Config::= SEQUENCE {
pdu-Session	PDU session ID	Same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
defaultDRB	true
mappedQoS-FlowsToAdd SEQUENCE {
QFI	1
}
}
}
drb-Identity	DRB-Identity with Condition DRBj	j is the ID of the DRB established during the preamble which is allocated according to internal TTCN mapping
}
}
DRB-ToAddMod[2] SEQUENCE		entry 2
cnAssociation CHOICE {
sdap-Config SEQUENCE {
pdu-Session	PDU session ID	Same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
defaultDRB	false
mappedQoS-FlowsToAdd SEQUENCE {
QFI	5
}
}
}
drb-Identity	DRB-Identity with Condition DRBj+1
}
}
DRB-ToAddMod[3] SEQUENCE		entry 3
cnAssociation CHOICE {
sdap-Config SEQUENCE {
pdu-Session	PDU session ID	Same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
defaultDRB	false
mappedQoS-FlowsToAdd SEQUENCE {
QFI	2
}
}
}
drb-Identity	DRB-Identity with Condition DRBj+2
}
}
}
}

Table 8.1.6.1.1.2.3.3-7: CellGroupConfig-3DRBs (Table 8.1.6.1.1.2.3.3-4)

Derivation Path: TS 38.508-1 [4], table 4.6.3-19 and condition SRB2_DRB1
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig {	4 entries
RLC-BearerConfig[1]	RLC-BearerConfig with condition SRB2	entry 1
RLC-BearerConfig[2]	RLC-BearerConfig with conditions AM and DRBj	entry 2
RLC-BearerConfig[3]	RLC-BearerConfig with conditions AM and DRBj+1	entry 3
RLC-BearerConfig[3]	RLC-BearerConfig with conditions AM and DRBj+2	entry 4
}
}

Table 8.1.6.1.1.2.3.3-8: PDU SESSION ESTABLISHMENT ACCEPT (Preamble) (Table 8.1.6.1.1.2.3.3-1)

Derivation Path: TS 38.508-1, table 4.7.2-2
Information Element	Value/remark	Comment	Condition
PDU session ID	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
Authorized QoS rules	3 entries
QoS rule [1]	Reference QoS rule #1 as defined in Table 4.8.2.1-1.	QFI=1
QoS rule [2]	Reference QoS rule #4 as defined in Table 4.8.2.1-4 except DQR bit set to ‘0’B.	QFI=2
QoS rule [3]	Reference QoS rule #5 as defined in Table 4.8.2.1-5.	QFI=5
Mapped EPS Bearer contexts	Not Present
Authorized QoS flow descriptions	3 entries
QoS flow [1]	Reference QoS flow #1 as defined in Table8.1.5.4.1.3.3-7.	QFI=1
QoS flow [2]	Reference QoS flow #2 as defined in Table8.1.5.4.1.3.3-8.	QFI=2
QoS flow [3]	Reference QoS flow #3 as defined in Table 4.8.2.3-3.	QFI=5

8.1.6.1.2 Logged MDT

8.1.6.1.2.1 Logged MDT / RRC_IDLE / Logging and reporting / Intra-frequency measurement

8.1.6.1.2.1.1 Test Purpose (TP)

(1)

with { UE in NR RRC_IDLE state camping normally on an NR cell where logged measurement is configured without areaConfiguration and the UE is able to detect an NR intra-frequency cell }

ensure that {

when { T330 is running }

then { UE is logging serving cell idle mode measurements and Intra-frequency neighbouring cell measurements }

}

(2)

with { UE in NR RRC_IDLE state and UE has one or more logged Intra-frequency neighbouring cell measurement entries stored in VarLogMeasReport }

ensure that {

when { receiving RRCSetup message }

then { UE includes the logMeasAvailable IE in the RRCSetupComplete message }

}

(3)

with { UE in NR RRC_CONNECTED state and UE has one or more logged Intra-frequency neighbouring cell measurement entries stored in VarLogMeasReport }

ensure that {

when { receiving UEInformationRequest message }

then { UE transmits UEInformationResponse messages with absoluteTimeStamp set equal to the value configured when the logged measurement configuration was received and a relativeTimeStamp for each logged measurement indicating the elapsed time since the logged measurement configuration was received }

}

(4)

with { UE in NR RRC_CONNECTED state and UE has one or more logged Intra-frequency neighbouring cell measurement entries stored in VarLogMeasReport }

ensure that {

when { receiving UEInformationRequest message }

then { UE transmits UEInformationResponse messages with traceReference, traceRecordingSessionRef and tce-Id being set to same values as configured when the logged measurement configuration was received }

}

8.1.6.1.2.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331, clauses 5.3.3.4, 5 5.5a.1.3, 5.5a.3.2, 5.7.10.3 and 6.2.2. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.3.3.4]

The UE shall perform the following actions upon reception of the RRCSetup:

…

set the content of RRCSetupComplete message as follows:

…

2> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailable in the RRCSetupComplete message;

2> if the UE has Bluetooth logged measurements available and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailableBT in the RRCSetupComplete message;

2> if the UE has WLAN logged measurements available and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailableWLAN in the RRCSetupComplete message;

…

[TS 38.331, clause 5.5a.1.3]

Upon receiving the LoggedMeasurementConfiguration message the UE shall:

1> discard the logged measurement configuration as well as the logged measurement information as specified in 5.5a.2;

1> store the received loggingDuration, reportType and areaConfiguration, if included, in VarLogMeasConfig;

1> if the LoggedMeasurementConfiguration message includes plmn-IdentityList:

2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN as well as the PLMNs included in plmn-IdentityList;

1> else:

2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN;

1> store the received absoluteTimeInfo, traceReference, traceRecordingSessionRef, and tce-Id in VarLogMeasReport;

1> store the received bt-NameList, if included, in VarLogMeasConfig;

1> store the received wlan-Namelist, if included, in VarLogMeasConfig;

1> store the received sensor-Namelist, if included, in VarLogMeasConfig;

1> start timer T330 with the timer value set to the loggingDuration;

[TS 38.331, clause5.5a.3.2]

While T330 is running, the UE shall:

1> perform the logging in accordance with the following:

2> if the reportType is set to periodical in the VarLogMeasConfig:

3> if the UE is camping normally on an NR cell and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport and, if the cell is part of the area indicated by areaConfiguration if configured in VarLogMeasConfig:

4> perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig;

2> else if the reportType is set to eventTriggered, and eventType is set to outOfCoverage:

3> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the UE is in any cell selection state;

3> perform the logging immediately upon transitioning from the any cell selection state to the camped normally state;

2> else if the reportType is set to eventTriggered and eventType is set to eventL1:

4> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the conditions indicated by the eventL1 are met;

2> when performing the logging:

3> set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged measurement configuration was received;

3> if detailed location information became available during the last logging interval, set the content of the locationInfo as in 5.3.3.7:

3> if the UE is in any cell selection state (as specified in TS 38.304 [20]):

4> set anyCellSelectionDetected to indicate the detection of no suitable or no acceptable cell found;

4> set the servCellIdentity to indicate global cell identity of the last logged cell that the UE was camping on;

4> set the measResultServingCell to include the quantities of the last logged cell the UE was camping on;

3> else:

4> set the servCellIdentity to indicate global cell identity of the cell the UE is camping on;

4> set the measResultServingCell to include the quantities of the cell the UE is camping on;

4> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements that became available during the last logging interval for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies per RAT and according to the following:

5> for each neighbour cell included, include the optional fields that are available;

NOTE: The UE includes the latest results of the available measurements as used for cell reselection evaluation in RRC_IDLE or RRC_INACTIVE, which are performed in accordance with the performance requirements as specified in TS 38.133 [14].

2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in 5.5a.1.4.

[TS 38.331, clause 5.7.10.3]

Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:

…

1> if the logMeasReportReq is present and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

2> if VarLogMeasReport includes one or more logged measurement entries, set the contents of the logMeasReport in the UEInformationResponse message as follows:

3> include the absoluteTimeStamp and set it to the value of absoluteTimeInfo in the VarLogMeasReport;

3> include the traceReference and set it to the value of traceReference in the VarLogMeasReport;

3> include the traceRecordingSessionRef and set it to the value of traceRecordingSessionRef in the VarLogMeasReport;

3> include the tce-Id and set it to the value of tce-Id in the VarLogMeasReport;

3> include the logMeasInfoList and set it to include one or more entries from VarLogMeasReport starting from the entries logged first;

3> if the VarLogMeasReport includes one or more additional logged measurement entries that are not included in the logMeasInfoList within the UEInformationResponse message:

4> include the logMeasAvailable;

3> if the VarLogMeasReport includes one or more additional logged Bluetooth measurement entries that are not included in the logMeasInfoList within the UEInformationResponse message:

4> include the logMeasAvailableBT;

3> if the VarLogMeasReport includes one or more additional logged WLAN measurement entries that are not included in the logMeasInfoList within the UEInformationResponse message:

4> include the logMeasAvailableWLAN;

…

1> if the logMeasReport is included in the UEInformationResponse:

2> submit the UEInformationResponse message to lower layers for transmission via SRB2;

2> discard the logged measurement entries included in the logMeasInfoList from VarLogMeasReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1> else:

2> submit the UEInformationResponse message to lower layers for transmission via SRB1.

[TS 38.331, clause 6.2.2]

– LoggedMeasurementConfiguration

The LoggedMeasurementConfiguration message is used to perform logging of measurement results while in RRC_IDLE or RRC_INACTIVE. It is used to transfer the logged measurement configuration for network performance optimisation.

Signalling radio bearer: SRB1

RLC-SAP: AM

Logical channel: DCCH

Direction: Network to UE

LoggedMeasurementConfiguration message

— ASN1START

— TAG-LOGGEDMEASUREMENTCONFIGURATION-START

LoggedMeasurementConfiguration-r16 ::= SEQUENCE {

criticalExtensions CHOICE {

loggedMeasurementConfiguration-r16 LoggedMeasurementConfiguration-r16-IEs,

criticalExtensionsFuture SEQUENCE {}

}

LoggedMeasurementConfiguration-r16-IEs ::= SEQUENCE {

traceReference-r16 TraceReference-r16,

traceRecordingSessionRef-r16 OCTET STRING (SIZE (2)),

tce-Id-r16 OCTET STRING (SIZE (1)),

absoluteTimeInfo-r16 AbsoluteTimeInfo-r16,

areaConfiguration-r16 AreaConfiguration-r16 OPTIONAL, –Need R

plmn-IdentityList-r16 PLMN-IdentityList2-r16 OPTIONAL, –Need R

bt-NameList-r16 SetupRelease {BT-NameList-r16} OPTIONAL, –Need M

wlan-NameList-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, –Need M

sensor-NameList-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, –Need M

loggingDuration-r16 LoggingDuration-r16,

reportType CHOICE {

periodical LoggedPeriodicalReportConfig-r16,

eventTriggered LoggedEventTriggerConfig-r16,

…

lateNonCriticalExtension OCTET STRING OPTIONAL,

nonCriticalExtension SEQUENCE {} OPTIONAL

}

LoggedPeriodicalReportConfig-r16 ::= SEQUENCE {

loggingInterval-r16 LoggingInterval-r16,

…

}

LoggedEventTriggerConfig-r16 ::= SEQUENCE {

eventType-r16 EventType-r16,

loggingInterval-r16 LoggingInterval-r16,

…

}

EventType-r16 ::= CHOICE {

outOfCoverage NULL,

eventL1 SEQUENCE {

l1-Threshold MeasTriggerQuantity,

hysteresis Hysteresis,

timeToTrigger TimeToTrigger

…

}

— TAG-LOGGEDMEASUREMENTCONFIGURATION-STOP

— ASN1STOP

LoggedMeasurementConfiguration field descriptions

absoluteTimeInfo

Indicates the absolute time in the current cell.

areaConfiguration

Used to restrict the area in which the UE performs measurement logging to cells broadcasting either one of the included cell identities or one of the included tracking area codes/ frequencies.

eventType

The value outOfCoverage indicates the UE to perform logging of measurements when the UE enters any cell selection state, and the value eventL1 indicates the UE to perform logging of measurements when the triggering condition (similar as event A2 as specified in 5.5.4.3) as configured in the event is met for the camping cell in camped normally state.

plmn-IdentityList

Indicates a set of PLMNs defining when the UE performs measurement logging as well as the associated status indication and information retrieval i.e. the UE performs these actions when the RPLMN is part of this set of PLMNs.

tce-Id

Parameter Trace Collection Entity Id: See TS 32.422 [52].

traceRecordingSessionRef

Parameter Trace Recording Session Reference: See TS 32.422 [52].

reportType

Parameter configures the type of MDT configuration, specifically Periodic MDT conifguraiton or Event Triggerd MDT configuration.

8.1.6.1.2.1.3 Test description

8.1.6.1.2.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 and NR Cell 11.

– System information combination NR-2 as defined in TS 38.508-1[4] clause 4.4.3.1.2 is used in NR cells.

UE:

– None.

Preamble:

– The UE is in state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.

8.1.6.1.2.1.3.2 Test procedure sequence

Table 8.1.6.1.2.1.3.2-1/2 illustrate the downlink power levels and other changing parameters to be applied for the cell at various time instants of the test execution. The configuration "T0" indicates the initial conditions. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.1.6.1.2.1.3.2-1: Time instances of cell power level for FR1

Parameter

Unit

NR Cell 1

NR Cell 11

Remark

SS/PBCH

SSS EPRE

dBm/SCS

-78

-85

NR Cell 1 becomes the highest ranked cell.

SS/PBCH

SSS EPRE

dBm/SCS

-85

-78

NR Cell 11 becomes the highest ranked cell.

Table 8.1.6.1.2.1.3.2-2: Time instances of cell power level for FR2

Parameter

Unit

NR Cell 1

NR Cell 11

Remark

SS/PBCH

SSS EPRE

dBm/SCS

-82

-91

NR Cell 1 becomes the highest ranked cell.

SS/PBCH

SSS EPRE

dBm/SCS

-91

-82

NR Cell 11 becomes the highest ranked cell.

Table 8.1.6.1.2.1.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits a LoggedMeasurementConfiguration message to configure the UE to perform logging of measurement results while in RRC_IDLE.	<–	LoggedMeasurementConfiguration	–	–
2	The SS transmits an RRCRelease message.	<–	NR RRC:RRCRelease	–	–
3	Wait 5s to allow UE to activate logging.	–	–	–	–
4	The SS changes NR Cell 1 and NR Cell 11 levels according to the row "T1" in table 8.1.6.1.2.1.3.2-1/2. (Note 1)	–	–	–	–
5	The UE transmits an RRCSetupRequest message on NR Cell 11 to initiate a tracking area update procedure.	–>	NR RRC: RRCSetupRequest	–	–
6	SS transmits an RRCSetup message.	<–	NR RRC: RRCSetup	–	–
7	Check: Does the UE include the IE logMeasAvailable in the RRCSetupComplete message?	–>	NR RRC: RRCSetupComplete 5GMM: REGISTRATION REQUEST	2	P
8-10	Steps 4 to 6a1 of generic test procedure in TS 38.508-1[4] Table 4.9.5.2.2-1 are performed on NR Cell 11. NOTE: The UE performs a REGISTRATION procedure update the registration of the actual tracking area and the RRC connection is released.	–	–	–	–
11-18	Steps 1 to 8 of the generic radio bearer establishment procedure in TS 38.508-1 [4], Table4.5.4.2-3 are executed to successfully complete the service request procedure on NR Cell 11.	–	–	–	–
19	The SS transmits a UEInformationRequest message on NR Cell 11.	<–	UEInformationRequest	–	–
20	Check: Does the UE transmit a UEInformationResponse message with the IEs absoluteTimeStamp, traceReference, traceRecordingSessionRef and tce-Id set to same value as received in the LoggedMeasurementConfiguration message in step 1; and a LogMeasInfoList with at least two entries with serving cell idle mode measurements and where in at least one of the entries the IE measResultListNR include a neighbouring cell measurement of NR Cell 11; and where the relativeTimeStamp is increased between the subsequent LogMeasInfoList entries by at least the value of configured loggingInterval in the received LoggedMeasurementConfiguration message in step 1.	–>	UEInformationResponse	1, 3, 4	P
Note 1: The change of power levels is to trigger a cell re-selection procedure to make sure that the UE is logging neighbouring cell measurements (logging interval=2.56 seconds) of Cell NR 11 while t-Reselection timer is running (7 seconds).

8.1.6.1.2.1.3.3 Specific message contents

Table 8.1.6.1.2.1.3.3-1: SIB2 for NR cell 1 (preamble)

Derivation Path: TS 38.508-1 [4], table 4.6.2-1
Information Element	Value/remark	Comment	Condition
SIB2 ::= SEQUENCE {
intraFreqCellReselectionInfo SEQUENCE {
t-ReselectionNR	7	seconds
}
}

Table 8.1.6.1.2.1.3.3-2: LoggedMeasurementConfiguration (step 1, Table 8.1.6.1.2.1.3.2-3)

Derivation path: TS 38.508-1 [4], table 4.6.1-5AA with condition PERIODICAL

Table 8.1.6.1.2.1.3.3-3: RRCSetupComplete (steps 7 and 14, Table 8.1.6.1.2.1.3.2-3)

Derivation path: TS 38.508-1 [4], table 4.6.1-22
Information Element	Value/remark	Comment	Condition
RRCSetupComplete ::= SEQUENCE {
criticalExtensions CHOICE {
rrcSetupComplete SEQUENCE {
nonCriticalExtension SEQUENCE {
ue-MeasurementsAvailable-r16	UE-MeasurementsAvailable-r16 with condition LOG
}
}
}
}

Table 8.1.6.1.2.1.3.3-4: UEInformationRequest (step 19, Table 8.1.6.1.2.1.3.2-3)

Derivation path: TS 38.508-1 [4], table 4.6.1-32A with condition LOG

Table 8.1.6.1.2.1.3.3-5: UEInformationResponse (step 20, Table 8.1.6.1.2.1.3.2-3)

Derivation path: TS 38.508-1 [4], table 4.6.1-32B
Information Element	Value/remark	Comment	Condition
UEInformationResponse-r16 ::= SEQUENCE {
criticalExtensions CHOICE {
ueInformationResponse-r16 SEQUENCE {
logMeasReport-r16 SEQUENCE {
absoluteTimeStamp-r16	Same value as sent by SS in LoggedMeasurementConfiguration in step 1
traceReference-r16 SEQUENCE {
plmn-Identity-r16 SEQUENCE {
mcc SEQUENCE (SIZE (3)) OF MCC-NMC-Digit	Same value as sent by SS in LoggedMeasurementConfiguration in step 1
mnc SEQUENCE (SIZE (2..3)) OF MCC-NMC-Digit	Same value as sent by SS in LoggedMeasurementConfiguration in step 1
}
traceId-r16	Same value as sent by SS in LoggedMeasurementConfiguration in step 1
}
traceRecordingSessionRef-r16	Same value as sent by SS in LoggedMeasurementConfiguration in step 1
tce-Id-r16	Same value as sent by SS in LoggedMeasurementConfiguration in step 1
logMeasInfoList-r16 SEQUENCE (SIZE (1..maxLogMeasReport-r16)) OF LogMeasInfo-r16 SEQUENCE {	At least 2 entries where at least one entry complies to entry with index ‘x’ below. SS records the relativeTimeStamp value for each entry
LogMeasInfo-r16[x] SEQUENCE {		entry x
locationInfo-r16	Not checked
relativeTimeStamp-r16	SS record the value
servCellIdentity-r16	Same as NR Cell 1
measResultServCell-16 SEQUENCE {
resultsSSB-Cell-r16	MeasQuantityResults of NR Cell 1
resultsSSB SEQUENCE {
best-ssb-Index	Not checked
best-ssb-Results	Not checked
numberOfGoodSSB	Not checked
}
}
measResultNeighCells-r16 SEQUENCE {
measResultNeighCellListNR SEQUENCE (SIZE (1..maxFreq)) OF MeasResultLogging2NR-r16 SEQUENCE {	1 entry
carrierFreq-r16	Same as NR Cell 11
measResultListLoggingNR -r16 SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultLoggingNR-r16 SEQUENCE {	1 entry
MeasResultLoggingNR-r16[1] SEQUENCE {		entry 1
physCellId-r16	Same as NR Cell 11
resultsSSB-Cell-r16	MeasQuantityResults of NR Cell 11
numberOfGoodSSB-r16	Not checked
}
}
}
}
measResultNeighCellListEUTRA	Not present
}
anyCellSelectionDetected-r16	Not present
}
}
logMeasAvailable-r16	Not present
}
}
}
}

8.1.6.1.2.2 Logged MDT / RRC_INACTIVE / Logging and reporting / Inter-frequency measurement

8.1.6.1.2.2.1 Test Purpose (TP)

(1)

with { UE in NR RRC_INACTIVE state camping normally on an NR cell where logged measurement is configured without areaConfiguration and the UE is able to detect an NR inter-frequency cell }

ensure that {

when { T330 is running }

then { UE is logging serving cell measurements and Inter-frequency neighbouring cell measurements }

}

(2)

with { UE in NR RRC_INACTIVE state and has sent RRCResumeRequest message and UE has one or more logged Inter-frequency neighbouring cell measurement entries stored in VarLogMeasReport }

ensure that {

when { receiving RRCResume message }

then { UE includes the logMeasAvailable IE in the RRCResumeComplete message }

}

(3)

with { UE in NR RRC_CONNECTED state and UE has one or more logged Inter-frequency neighbouring cell measurement entries stored in VarLogMeasReport }

ensure that {

when { receiving UEInformationRequest message }

then { UE transmits UEInformationResponse messages with a logMeasReport with Inter-frequency neighbouring cell measurements }

}

(4)

with { UE in NR RRC_CONNECTED state and UE has one or more logged Inter-frequency neighbouring cell measurement entries stored in VarLogMeasReport }

ensure that {

when { receiving UEInformationRequest message and the UE has not transferred the total log in the UEInformationResponse message }

then { UE transmits UEInformationResponse messages with the logMeasAvailable IE }

}

8.1.6.1.2.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331, clauses 5.3.13.4, 5 5.5a.1.3, 5.5a.3.2, 5.7.10.3 and 6.2.2. Unless otherwise stated these are Rel-16 requirements. [TS 38.331, clause 5.3.13.4]

The UE shall:

1> stop timer T319;

1> stop timer T380, if running;

…

1> set the content of the of RRCResumeComplete message as follows:

2> if the upper layer provides NAS PDU, set the dedicatedNAS-Message to include the information received from upper layers;

…

2> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailable in the RRCResumeComplete message;

2> if the UE has Bluetooth logged measurements available and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailableBT in the RRCResumeComplete message;

2> if the UE has WLAN logged measurements available and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailableWLAN in the RRCResumeComplete message;