8.6.1 Immediate MDT

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

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

8.6.1.1 Immediate MDT / Reporting / Location information

8.6.1.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA 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 E-UTRA 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.6.1.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.5.3, 5.5.4.1, 5.5.4.3 and 5.5.5.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

…

1> if the RRCConnectionReconfiguration message includes the measConfig:

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

…

[TS 36.331, clause 5.5.4.1]

The UE shall:

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

…

2> else:

3> if the corresponding measObject concerns EUTRA:

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

…

2> if the triggerType is set to ‘event’ 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> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to ‘event’ 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> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to ‘event’ 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> 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 serving cell RSRP being equal to or better than s-Measure or due to the measurement gap not being setup.

…

[TS 36.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;

InequalityA2-1 (Entering condition)

InequalityA2-2 (Leaving condition)

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 the reportConfigEUTRA for this event).

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

Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

[TS 36.331, clause 5.5.5]

…

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 measResultServCell to include the quantities of serving cell;

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

…

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

2> include the locationCoordinates;

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> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.

8.6.1.1.3 Test description

8.6.1.1.3.1 Pre-test conditions

System Simulator:

– 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 36.509 [25] , 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 Generic RB Established (state 3) according to [18].

8.6.1.1.3.2 Test procedure sequence

Table 8.6.1.1.3.2-1 illustrates the downlink power levels to be applied for Cell 1 at various time instants of the test execution. Row marked "T0" denotes the 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.6.1.1.3.2-1: Power levels

	Parameter	Unit	Cell 1	Remark
T0			-70	Power level is such that Ms > Thresh + Hys
T1	Cell-specific RS EPRE	dBm/15kHz	-96	Power level is such that entry condition for event A2 is satisfied Ms + Hys < Thresh
T2			-70	Power level is such that exit condition for event A2 is satisfied Ms > Thresh + Hys
Note: The total tolerance used is the sum of downlink signal level uncertainty (TS 36.508 clause 6.2.2.1) and absolute UE measurement accuracy (TS 36.133 clause 9).

Table 8.6.1.1.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message including measConfig to setup intra LTE measurement and reporting for event A2 with includeLocationInfo configured.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS re-adjusts the cell-specific reference signal level according to row "T1" in table 8.6.1.1.3.2-1.	–	–	–	–
4	Check: Does the UE transmit a MeasurementReport message to report event A2 with the UE locationInfo included?	–>	MeasurementReport	1	P
5	The SS re-adjusts the cell-specific reference signal level according to row "T2" in table 8.6.1.1.3.2-1.	–	–	–	–
6	Wait and ignore MeasurementReport messages for 5 s to allow change of power levels for Cell 1.	–	–	–	–
7	Check: Does the UE attempt to transmit an uplink message within the next 10s?	–		2	F

8.6.1.1.3.3 Specific message contents

Table 8.6.1.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.6.1.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 8.6.1.1.3.3-2: MeasConfig (step 1, Table 8.6.1.1.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1
Information Element	Value/Remark	Comment	Condition
measConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	1 entry
measObjectId[1]	IdMeasObject-f1
measObject[1]	MeasObjectEUTRA-GENERIC(f1)
measObject[1]	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {	1 entry
reportConfigId[1]	IdReportConfig-A2
reportConfig[1]	ReportConfig-A2-H
}
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {	1 entry
measId[1]	1
measObjectId[1]	IdMeasObject-f1
reportConfigId[1]	IdReportConfig-A2
}
measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	1 entry		Band > 64
measObjectEUTRA-v9e0[1] SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
}
}

Condition	Explanation
Band > 64	If band > 64 is selected

Table 8.6.1.1.3.3-3: ReportConfig-A2-H (step 1, Table 8.6.1.1.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-5 ReportConfigEUTRA-A2(-83)
Information Element	Value/Remark	Comment	Condition
ReportConfigEUTRA ::= SEQUENCE {
triggerType CHOICE {
event SEQUENCE {
hysteresis	6	3 dB
}
}
reportAmount	r1
includeLocationInfo-r10	true
}

Table 8.6.1.1.3.3-4: MeasurementReport (step 4, Table 8.6.1.1.3.2-2)

Derivation path: 36.508 table clause 4.6.1 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 {		Report Cell 1
rsrpResult	(0..97)
rsrqResult	(0..34)
}
measResultNeighCells CHOICE {}	Not present
measResultForECID-r9	Not present
locationInfo-r10 SEQUENCE {
locationCoordinates-r10 CHOICE {
ellipsoid-Point-r10	Any allowed value
ellipsoidPointWithAltitude-r10	Any allowed value
}
}
measResultServFreqList-r10	Not present
}
}
}
}
}

8.6.1.2 Immediate MDT / Reporting / Location information / Request from eNB / Event A2

8.6.1.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A2 with the includeLocationInfo set to true and the obtainLocation set to setup }

ensure that {

when { Serving cell becomes worse than absolute threshold minus hysteresis }

then { UE sends MeasurementReport message with the locationInfo obtained after receiving RRCConnectionReconfiguration message }

}

8.6.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.10.9 and 5.5.5. Unless otherwise stated these are Rel-11 requirements.

[TS 36.331, clause 5.3.10.9]

The UE shall:

…

1> if the received otherConfig includes the obtainLocation:

2> attempt to have detailed location information available for any subsequent measurement report;

NOTE: The UE is requested to attempt to have valid detailed location information available whenever sending a measurement report for which it is configured to include available detailed location information. The UE may not succeed e.g. because the user manually disabled the GPS hardware, due to no/poor satellite coverage. Further details, e.g. regarding when to activate GNSS, are up to UE implementation.

[TS 36.331, clause 5.5.5]

The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN.

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

…

2> include the locationCoordinates;

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

8.6.1.2.3 Test description

8.6.1.2.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

8.6.1.2.3.2 Test procedure sequence

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

Table 8.6.1.2.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-70	The power level value is such that measurement result for Cell 1 satisfies leaving condition for event A2 (Ms – Hys > Thresh).
T1	Cell-specific RS EPRE	dBm/15kHz	-96	The power level value is such that measurement result for Cell 1 satisfies entering condition for event A2 (Ms + Hys < Thresh).

Table 8.6.1.2.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message to setup intra-frequency measurement for event A2 with includeLocationInfo set to true.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS changes Cell 1 power level according to the row "T1" in table 8.6.1.2.3.2-1.	–	–	–	–
4	The UE transmits a MeasurementReport message to report event A2 with locationInfo. (Note 1)	–>	MeasurementReport	–	–
5	The SS changes Cell 1 power level according to the row "T0" in table 8.6.1.2.3.2-1.	–	–	–	–
6	The SS waits 10s.	–	–	–	–
7	The SS transmits an RRCConnectionReconfiguration message to modify intra-frequency measurement for event A2 with includeLocationInfo set to true and obtainLocation set to setup.	<–	RRCConnectionReconfiguration	–	–
8	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
9	The SS waits [60s] to ensure that the UE has detailed location information available. (NOTE 2)	–	–	–	–
10	The SS changes Cell 1 power level according to the row "T1" in table 8.6.1.2.3.2-1.	–	–	–	–
11	Check: Does the UE transmit a MeasurementReport message to report event A2 with locationInfo?	–>	MeasurementReport	1	P
NOTE 1: The UE reports the detailed location information available stored in the UE. This intends to check that detailed location information reported in step 11 is obtained after receiving the RRCConnectionReconfiguration message in step 7. NOTE 2: Depending on UE’s positioning engine used in this test case, any suitable method (e.g. test function Update UE Location Information defined in TS 36.509 [25]) may be used in this step to provide the position to the UE.

8.6.1.2.3.3 Specific message contents

Table 8.6.1.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.6.1.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8 with condition MEAS

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

Derivation Path: 36.508, Table 4.6.6-1
Information Element	Value/remark	Comment	Condition
MeasConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE{	1 entry
measObjectId[1]	IdMeasObject-f1
measObject[1]	MeasObjectEUTRA-GENERIC(f1)
measObject[1]	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {	1 entry
reportConfigId[1]	IdReportConfig-A2
reportConfig[1]	ReportConfigEUTRA-A2-RECONF
}
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {	1 entry
measId[1]	1
measObjectId[1]	IdMeasObject-f1
reportConfigId[1]	IdReportConfig-A2
}
measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	1 entry		Band > 64
measObjectEUTRA-v9e0[1] SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
}
}

Condition	Explanation
Band > 64	If band > 64 is selected

Table 8.6.1.2.3.3-3: ReportConfigEUTRA-A2-RECONF (Table 8.6.1.2.3.3-2)

Derivation Path: 36.508, Table 4.6.6-5 ReportConfigEUTRA-A2(-83)
Information Element	Value/remark	Comment	Condition
ReportConfigEUTRA ::= SEQUENCE {
triggerType CHOICE {
event SEQUENCE {
hysteresis	6	3dB
}
}
si-RequestForHO-r9	Not present
ue-RxTxTimeDiffPeriodical-r9	Not present
includeLocationInfo-r10	true
reportAddNeighMeas-r10	Not present
}

Table 8.6.1.2.3.3-4: MeasurementReport (steps 4 and 11, Table 8.6.1.2.3.2-2)

Derivation Path: 36.508, 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	Not present
measResultForECID-r9	Not present
locationInfo-r10	Any allowed value
measResultServFreqList-r10	Not present
}
}
}
}
}

Table 8.6.1.2.3.3-5: RRCConnectionReconfiguration (step 7, Table 8.6.1.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8 with condition MEAS
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
lateNonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {
otherConfig-r9 SEQUENCE {
reportProximityConfig-r9	Not present
idc-Config-r11	Not present
powerPrefIndicationConfig-r11	Not present
obtainLocationConfig-r11 SEQUENCE {
obtainLocation-r11	setup
}
}
fullConfig-r9	Not present
nonCriticalExtension	Not present
}
}
}
}
}
}

Table 8.6.1.2.3.3-6: MeasConfig (Table 8.6.1.2.3.3-5)

Derivation Path: 36.508, Table 4.6.6-1
Information Element	Value/remark	Comment	Condition
MeasConfig ::= SEQUENCE {
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {	1 entry
reportConfigId[1]	IdReportConfig-A2
reportConfig[1]	ReportConfigEUTRA-A2-RECONF2
}
}

Table 8.6.1.2.3.3-7: ReportConfigEUTRA-A2-RECONF2 (Table 8.6.1.2.3.3-6)

Derivation Path: 36.508, Table 4.6.6-5 ReportConfigEUTRA-A2(-83)
Information Element	Value/remark	Comment	Condition
ReportConfigEUTRA ::= SEQUENCE {
triggerType CHOICE {
event SEQUENCE {
hysteresis	4	2dB
}
}
si-RequestForHO-r9	Not present
ue-RxTxTimeDiffPeriodical-r9	Not present
includeLocationInfo-r10	true
reportAddNeighMeas-r10	Not present
}

8.6.1.3 Immediate MDT / Measurement / Latency metrics for UL PDCP Packet Delay per QCI

8.6.1.3.1 Test Purpose (TP)

(1)

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

ensure that {

when {UE receives RRCConnectionReconfiguration containing ReportConfigEUTRA IE with ul-DelayConfig IE set to “setup” and triggerType set to “periodical” and purpose set to “reportStrongestCells”}

then {UE sends the RRCConnectionReconfigurationComplete message}

}

(2)

with {UE in RRC_CONNECTED and measurement configured for UL PDCP Packet Delay per QCI and having DRB established with QCI1, QCI2, QCI3 or QCI4}

ensure that {
when {UE determines that UL PDCP SDUs per QCI are exceeding the configured delay threshold }

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

}

(3)

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

ensure that {

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

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

}

8.6.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.5.3.1, 5.5.4.1, 5.5.5 & TS 36.314, clause 4.2.1.1

[TS 36.331, clause 5.5.3.1]

The UE shall:

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

2> if the purpose for the associated reportConfig is set to reportCGI:

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

3> ignore the measObject;

3> configure the PDCP layer to perform UL PDCP Packet Delay per QCI measurement;

[TS 36.331, clause 5.5.4.1]

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

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

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;

[TS 36.331, clause 5.5.5]

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 uplink PDCP delay results are available:

2> set the ul-PDCP-DelayResultList to include the uplink PDCP delay results available;

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

[TS 36.314, clause 4.2.1.1]

The objective of this measurement performed by UE is to measure Excess Packet Delay Ratio in Layer PDCP for QoS verification of MDT.

Table 4.2.1.1-0: Protocol Layer: RLC, PDCP

Definition

PDCP Packet Delay in the UL per QCI. This measurement refers to packet delay for DRBs, which captures the delay from packet arrival at PDCP upper SAP until the packet starts to be delivered to RLC. The measurement is done separately per QCI.

Detailed Definition:

,where

explanations can be found in the table 4.2.1.1-1 below.

Table 4.2.1.1-1

	Ratio of packets in UL per QCI exceeding the configured delay threshold among the UL PDCP SDUs transmitted.
	Number of PDCP SDUs of a data radio bearer with QCI = ,for which ULdelay exceeded the configured delayThreshold as defined in TS 36.331 [5] during the time period T.
	Number of PDCP SDUs of a data radio bearer with QCI = , for which at least a part of SDU was transmitted during the time period T.
	Queuing delay observed at the UE PDCP layer from packet arrival at PDCP upper SAP until the packet starts to be delivered to RLC, the packet belongs to a data radio bearer with QCI = .
	The point in time when the PDCP SDU i of a data radio bearer with QCI =was delivered to lower layers.
	The point in the time when the PDCP SDU i of a data radio bearer with QCI = arrives at PDCP upper SAP.
	Index of PDCP SDU that arrives at the PDCP upper SAP during time period .
	Time period during which the measurement is performed.

Table 4.2.1.1.1-1: EXCESS DELAY RATIO measurement report mapping (5 –bit value)

Reported value	Measured quantity value	Unit
EXCESS DELAY RATIO_00	0 < EXCESS DELAY RATIO  0,079	%
EXCESS DELAY RATIO_01	0,079 < EXCESS DELAY RATIO  0,100	%
EXCESS DELAY RATIO_02	0,100 < EXCESS DELAY RATIO 0,126	%
EXCESS DELAY RATIO_03	0,126 < EXCESS DELAY RATIO  0,158	%
EXCESS DELAY RATIO_04	0,158 < EXCESS DELAY RATIO  0,199	%
EXCESS DELAY RATIO_05	0,199 < EXCESS DELAY RATIO  0,251	%
EXCESS DELAY RATIO_06	0,251 < EXCESS DELAY RATIO  0,316	%
EXCESS DELAY RATIO_07	0,316 < EXCESS DELAY RATIO  0,398	%
EXCESS DELAY RATIO_08	0,398 < EXCESS DELAY RATIO  0,501	%
EXCESS DELAY RATIO_09	0,501 < EXCESS DELAY RATIO  0,631	%
EXCESS DELAY RATIO_10	0,631 < EXCESS DELAY RATIO  0,794	%
EXCESS DELAY RATIO_11	0,794 < EXCESS DELAY RATIO  1,000	%
EXCESS DELAY RATIO_12	1,000 < EXCESS DELAY RATIO  1,259	%
EXCESS DELAY RATIO_13	1,259 < EXCESS DELAY RATIO 1,585	%
EXCESS DELAY RATIO_14	1,585 < EXCESS DELAY RATIO 1,995	%
EXCESS DELAY RATIO_15	1,995 < EXCESS DELAY RATIO 2,511	%
EXCESS DELAY RATIO_16	2,511 < EXCESS DELAY RATIO 3,161	%
EXCESS DELAY RATIO_17	3,161 < EXCESS DELAY RATIO 3,980	%
EXCESS DELAY RATIO_18	3,980 < EXCESS DELAY RATIO 5,011	%
EXCESS DELAY RATIO_19	5,011 < EXCESS DELAY RATIO 6,309	%
EXCESS DELAY RATIO_20	6,309 < EXCESS DELAY RATIO 7,943	%
EXCESS DELAY RATIO_21	7,943 < EXCESS DELAY RATIO 10,00	%
EXCESS DELAY RATIO_22	10,00 < EXCESS DELAY RATIO 12,589	%
EXCESS DELAY RATIO_23	12,589 < EXCESS DELAY RATIO 15,849	%
EXCESS DELAY RATIO_24	15,849 < EXCESS DELAY RATIO 19,953	%
EXCESS DELAY RATIO_25	19,953 < EXCESS DELAY RATIO 25,119	%
EXCESS DELAY RATIO_26	25,119 < EXCESS DELAY RATIO 31,623	%
EXCESS DELAY RATIO_27	31,623 < EXCESS DELAY RATIO 39,811	%
EXCESS DELAY RATIO_28	39,811 < EXCESS DELAY RATIO 50,119	%
EXCESS DELAY RATIO_29	50,119 < EXCESS DELAY RATIO 63,096	%
EXCESS DELAY RATIO_30	63,096 < EXCESS DELAY RATIO 79,433	%
EXCESS DELAY RATIO_31	79,433 < EXCESS DELAY RATIO 100	%

8.6.1.3.3 Test description

8.6.1.3.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

– None

Preamble:

– The UE is in state Registered, Idle Mode (State 2) according to [18].

8.6.1.3.3.2 Test procedure sequence

Table 8.6.1.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS performs the generic procedure to get UE in Loopback Activated (state 4) with condition UE TEST LOOP MODE B with a Reference default EPS bearer context #1 and Reference dedicated EPS bearer context #1 and Reference default EPS bearer #2 and Reference dedicated EPS bearer context #3 according to [18] on Cell A	–	–	–	–
1	The SS transmits an RRCConnectionReconfiguration message including MeasConfig to setup UL-DelayConfig	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message	–>	RRCConnectionReconfigurationComplete	1	P
3	The SS transmits an IP Packet on the data radio bearer associated with the dedicated EPS bearer contex #1	–	–	–	–
4	The SS transmits an IP Packet on the data radio bearer associated with the dedicated EPS bearer contex #3	–	–	–	–
5	SS provides sufficient UL grants to ensure UE can loopback IP packets without delay and waits for duration indicated in the IE reportInterval	–	–	–	–
–	EXCEPTION: In parallel to the event described in step 6 UE transmits IP packets on the data radio bearers associated with the dedicated EPS bearer contexts #1 and #3.	–	–	–	–
6	Check: Does the UE transmit a MeasurementReport message containing UL-PDCP-DelayResultList for QCI 1 and/or QCI 2	–>	MeasurementReport	2	F
7	The SS transmits an IP Packet on the data radio bearer associated with the dedicated EPS bearer contex #1
8	The SS transmits an IP Packet on the data radio bearer associated with the dedicated EPS bearer contex #3
9	SS doesn’t provide UL grants to the UE for the duration indicated by IE delayThreshold-r13 and waits for duration indicated in the IE reportInterval (Note 1)
–	EXCEPTION: In parallel to the event described in step 10 UE transmits IP packets on the data radio bearers associated with the dedicated EPS bearer contexts #1 and #3.	–	–	–	–
10	Check: Does the UE transmit a MeasurementReport message containing UL-PDCP-DelayResultList for QCI 1 and QCI 2	–>	MeasurementReport	2	P
11	The SS transmits an RRCConnectionReconfiguration message including MeasConfig to release the UL-DelayConfig measurement	<–	RRCConnectionReconfiguration	–	–
12	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete
13	The SS transmits an IP Packet on the data radio bearer associated with the dedicated EPS bearer contex #1	–	–	–	–
14	The SS transmits an IP Packet on the data radio bearer associated with the dedicated EPS bearer contex #3	–	–	–	–
15	SS doesn’t provide UL grants to the UE for the duration indicated by IE delayThreshold-r13 and waits for duration indicated in the IE reportInterval (Note 1)	–	–	–	–
–	EXCEPTION: In parallel to the event described in step 16 UE transmits IP packets on the data radio bearers associated with the dedicated EPS bearer contexts #1 and #3.	–	–	–	–
16	Check: Does the UE transmit a MeasurementReport message containing UL-PDCP-DelayResultList for QCI 1 and QCI 2	–>	MeasurementReport	3	F
Note 1: dsr-TransMax shall be set to 64 to ensure UE doesn’t initiate PRACH preamble before delayThreshold-r13 (ms750) expires.

8.6.1.3.3.3 Specific message contents

Table 8.6.1.3.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.6.1.3.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1, Table 4.6.1-8 RRCConnectionReconfiguration
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier-DL
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
measConfig	MeasConfig-DEFAULT
}
}
}
}

Table 8.6.1.3.3.3-2: MeasConfig (step 1, Table 8.6.1.3.3.2-1)

Derivation Path: TS 36.508, clause 4.6.6 Table 4.6.6-1
Information Element	Value/remark	Comment	Condition
MeasConfig-DEFAULT ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	1 entry
measObjectId[1]	IdMeasObject-f1
measObject[1]	MeasObjectEUTRA-GENERIC(f1)		Band > 64
measObject[1]	MeasObjectEUTRA-GENERIC(maxEARFCN)
}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE{
reportConfigId[1]	IdReportConfig- PERIODICAL-CSI-RS
reportConfig[1]	reportConfigEUTRA- PERIODICAL-CSI-RS
}
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE{	1 entry
measId[1]	1
measObjectId[1]	IdMeasObject-f1
reportConfigId[1]	IdReportConfig- PERIODICAL-CSI-RS
measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	1 entry		Band > 64
measObjectEUTRA-v9e0[1] SEQUENCE {
carrierFreq-v9e0[1]	Same downlink EARFCN as used for f1
}
}
}

Table 8.6.1.3.3.3-3: reportConfigEUTRA- PERIODICAL-CSI-RS (step 1, Table 8.6.1.3.3.2-1)

Derivation path: TS 36.508 clause 4.6.6 table 4.6.6-12 ReportConfigEUTRA-PERIODICAL-CSI-RS
Information Element	Value/Remark	Comment	Condition
ReportConfigEUTRA ::= SEQUENCE {
triggerType CHOICE {
periodical SEQUENCE {
purpose	reportStrongestCells
}
}
triggerQuantity	rsrp
reportQuantity	both
maxReportCells	1
reportInterval	ms5120
reportAmount	r64
si-RequestForHO-r9	Not Present
ue-RxTxTimeDiffPeriodical-r9	Not Present
includeLocationInfo-r10	Not Present
reportAddNeighMeas-r10	Not Present
alternativeTimeToTrigger-r12	Not Present
useT312-r12	Not Present
usePSCell-r12	Not Present
aN-Threshold1-v1250	Not Present
a5-Threshold2-v1250	Not Present
reportStrongestCSI-RSs-r12	Not Present
reportCRS-Meas-r12	false
triggerQuantityCSI-RS-r12	false
reportSSTD-Meas-r13	Not Present
rs-sinr-Config-r13	Not Present
useWhiteCellList-r13	Not Present
measRSSI-ReportConfig-r13	Not Present
includeMultiBandInfo-r13	Not Present
ul-DelayConfig-r13 CHOICE {
setup SEQUENCE {
delayThreshold-r13	ms750
}
}
}

Table 8.6.1.3.3.3-3A: SchedulingRequest-Configuration (RRCConnectionReconfiguration, step 1 table 8.6.1.3.3.2-1)

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Configuration ::= CHOICE {
setup SEQUENCE {
dsr-TransMax	n64	Max value allowed
}
}

Table 8.6.1.3.3.3-4: MeasurementReport (step 10, Table 8.6.1.3.3.2-1)

Derivation Path: 36.508, 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 {}	Not present
measResultForECID-r9	Not present
locationInfo-r10	Not present
measResultServFreqList-r10	Not present
measId-v1250	Not present
measResultPCell-v1250	Not present
measResultCSI-RS-List-r12	Not present
measResultForRSSI-r13	Not present
measResultServFreqListExt-r13	Not present
measResultSSTD-r13	Not present
measResultPCell-v1310	Not present
ul-PDCP-DelayResultList-r13 SEQUENCE (SIZE (1..maxQCI-r13)) OF SEQUENCE {	2 entries
qci-Id-r13[1]	qci1
excessDelay-r13[1]	31
qci-Id-r13[2]	qci2
excessDelay-r13[2]	31
}
}
}
}
}
}
}

Table 8.6.1.3.3.3-5: RRCConnectionReconfiguration (step 11, Table 8.6.1.3.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1, Table 4.6.1-8 RRCConnectionReconfiguration
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier-DL
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
measConfig	MeasConfig-DEFAULT
}
}
}
}

Table 8.6.1.3.3.3-6: MeasConfig (step 11, Table 8.6.1.3.3.2-1)

Derivation Path: TS 36.508, clause 4.6.6 Table 4.6.6-1
Information Element	Value/remark	Comment	Condition
MeasConfig-DEFAULT ::= SEQUENCE {
measObjectToAddModList SEQUENCE {}	Not Present
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE{
reportConfigId[1]	IdReportConfig- PERIODICAL-CSI-RS
reportConfig[1]	reportConfigEUTRA- PERIODICAL-CSI-RS
}
measIdToAddModList SEQUENCE {}	Not Present
}

Table 8.6.1.3.3.3-7: reportConfigEUTRA- PERIODICAL-CSI-RS (step 11, Table 8.6.1.3.3.2-1)

Derivation path: TS 36.508 clause 4.6.6 table 4.6.6-12 ReportConfigEUTRA-PERIODICAL-CSI-RS
Information Element	Value/Remark	Comment	Condition
ReportConfigEUTRA ::= SEQUENCE {
triggerType CHOICE {
periodical SEQUENCE {
purpose	reportStrongestCells
}
}
triggerQuantity	rsrp
reportQuantity	both
maxReportCells	1
reportInterval	ms10240
reportAmount	r1
si-RequestForHO-r9	Not Present
ue-RxTxTimeDiffPeriodical-r9	Not Present
includeLocationInfo-r10	Not Present
reportAddNeighMeas-r10	Not Present
alternativeTimeToTrigger-r12	Not Present
useT312-r12	Not Present
usePSCell-r12	Not Present
aN-Threshold1-v1250	Not Present
a5-Threshold2-v1250	Not Present
reportStrongestCSI-RSs-r12	Not Present
reportCRS-Meas-r12	false
triggerQuantityCSI-RS-r12	false
reportSSTD-Meas-r13	Not Present
rs-sinr-Config-r13	Not Present
useWhiteCellList-r13	Not Present
measRSSI-ReportConfig-r13	Not Present
includeMultiBandInfo-r13	Not Present
ul-DelayConfig-r13 CHOICE {
release	NULL
}
}