3GPP TS 37.320 V1.0.0 (2010-08)
`Technical Specification
`3rd Generation Partnership Project;
`Technical Specification Group TSG RAN
`Universal Terrestrial Radio Access (UTRA) and Evolved
`Universal Terrestrial Radio Access (E-UTRA);
`Radio measurement collection for Minimization of Drive Tests
`(MDT);
`Overall description;
`Stage 2
`(Release 10)
`
`The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP..
`The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
`This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
`Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
`
`IPR2022-00459
`Apple EX1010 Page 1
`
`

`

`IPR2022-00459
`Samsung Ex. 1010
`Apple EX1010 Page 2
`
`IPR2022-00459
`Apple EX1010 Page 2
`
`

`

`Keywords
`<keyword[, keyword, …]>
`
`3GPP
`
`Postal address
`
`3GPP support office address
`650 Route des Lucioles - Sophia Antipolis
`Valbonne - FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`
`Internet
`http://www.3gpp.org
`
`Copyright Notification
`
`No part may be reproduced except as authorized by written permission.
`The copyright and the foregoing restriction extend to reproduction in all media.
`
`© 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
`All rights reserved.
`
`IPR2022-00459
`Apple EX1010 Page 3
`
`

`

`Contents
`Foreword............................................................................................................................................................. 5
`Introduction ........................................................................................................................................................ 5
`1
`Scope ........................................................................................................................................................ 6
`2
`References ................................................................................................................................................ 6
`3
`Definitions, symbols and abbreviations ................................................................................................... 6
`3.1
`Definitions ......................................................................................................................................................... 6
`3.2
`Symbols ............................................................................................................................................................. 7
`3.3
`Abbreviations ..................................................................................................................................................... 7
`4
`Main concept and requirements ............................................................................................................... 7
`4.1
`General ............................................................................................................................................................... 7
`5
`Functions and procedures ......................................................................................................................... 8
`5.1
`General procedures ............................................................................................................................................ 8
`5.1.1
`Logged MDT procedures ............................................................................................................................. 8
`5.1.1.1
`Measurement configuration .................................................................................................................... 8
`5.1.1.1.1
`Configuration parameters .................................................................................................................. 9
`5.1.1.1.2
`Configuration effectiveness .............................................................................................................. 9
`5.1.1.2
`Measurement collection ........................................................................................................................ 10
`5.1.1.3
`Measurement reporting ......................................................................................................................... 10
`5.1.1.3.1
`Availability Indicator ...................................................................................................................... 10
`5.1.1.3.2
`Report retrieval ............................................................................................................................... 10
`5.1.1.3.3
`Reporting parameters ...................................................................................................................... 11
`5.1.1.4
`MDT context handling during handover ......................................................................................... 11
`5.1.2
`Immediate MDT procedures ...................................................................................................................... 11
`5.1.2.1
`Measurement configuration ........................................................................................................................ 11
`5.1.2.2
` Measurement reporting ........................................................................................................................ 11
`5.1.2.3
` MDT context handling during handover ............................................................................................. 12
`5.1.3
`MDT Initiation ........................................................................................................................................... 12
`5.1.4
`UE capabilities ........................................................................................................................................... 12
`5.1.5
`UE measurements ....................................................................................................................................... 12
`5.2
`E-UTRAN solutions ........................................................................................................................................ 12
`5.2.1
`RRC_CONNECTED .................................................................................................................................. 12
`Measurements and reporting triggers for Immediate MDT .................................................................. 12
`5.2.1.1
`5.2.1.2
`Enhancement to Radio Link Failure report........................................................................................... 13
`RRC_IDLE ................................................................................................................................................. 13
`5.2.2
`5.3
`UTRAN solutions ............................................................................................................................................ 13
`5.3.1
`UTRA RRC Connected .............................................................................................................................. 13
`5.3.1.1
`Measurements and reporting events for Immediate MDT .................................................................... 13
`5.3.2
`UTRA Idle .................................................................................................................................................. 14
`Annex A (informative): Coverage use cases .................................................................................................... 14
`Annex: Change history ..................................................................................................................................... 15
`
`IPR2022-00459
`Apple EX1010 Page 4
`
`

`

`Foreword
`This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
`
`The contents of the present document are subject to continuing work within the TSG and may change following formal
`TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
`identifying change of release date and an increase in version number as follows:
`
`Version x.y.z
`
`where:
`
`x
`
`the first digit:
`
`1 presented to TSG for information;
`
`2 presented to TSG for approval;
`
`3 or greater indicates TSG approved document under change control.
`
`y
`
`the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
`updates, etc.
`
`z
`
`the third digit is incremented when editorial only changes have been incorporated in the document.
`
`Introduction
`Using drive tests for network optimization purposes is costly and causes also additional CO2 emissions, so it is desirable
`to develop automated solutions, including involving UEs in the field, in 3GPP to reduce the operator costs for network
`deployment and operation. The studies done as part of the study item phase have shown that it is beneficial to collect
`UE measurements to enable a more efficient network optimisation and it is feasible to use control plane solutions to
`acquire the information from devices. This information, together with information available in the radio access network
`can be used for Coverage Optimization purposes.
`
`IPR2022-00459
`Apple EX1010 Page 5
`
`

`

`Scope
`1
`The present document provides an overview and overall description of the minimization of drive tests functionality.
`
`The document describes functions and procedures to support autonomous collection of UE measurements using Control
`Plane architecture for both UTRAN and E-UTRAN. Details of the signalling procedures for single-RAT operation are
`specified in the appropriate radio interface protocol specification.
`
`NOTE: The focus in on conventional macro cellular network deployments. It is presently not envisioned that
`H(e)NB deployments and MBMS will be supported by the MDT functionality.
`
`References
`2
`The following documents contain provisions which, through reference in this text, constitute provisions of the present
`document.
`
`- References are either specific (identified by date of publication, edition number, version number, etc.) or
`non-specific.
`
`- For a specific reference, subsequent revisions do not apply.
`
`- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
`a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
`Release as the present document.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`[8]
`
`[9]
`
`[x]
`
`3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
`
`3GPP TR 36.805 (V2.0.0): “Study on Minimization of drive-test in Next Generation Networks”
`
`3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification"
`
`3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
`Control (RRC); Protocol specification".
`
`3GPP TS 25.133: “Requirements for support of radio resource management (FDD)”
`
`3GPP TS 36.133: “Requirements for support of radio resource management (FDD)”
`
`3GPP TS 32.422: “Subscriber and equipment trace; Trace control and configuration management”
`
`3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell
`reselection in connected mode".
`
`3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
`procedures in idle mode".…
`
`<doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>".
`
`3
`
`Definitions, symbols and abbreviations
`
`Definitions
`3.1
`For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply.
`Immediate MDT: MDT functionality involving measurement performance by UE in CONNECTED state and
`reporting of the measurements to eNB/RNC available at the time of reporting condition.
`
`Logged MDT: MDT functionality involving measurement performance by UE in IDLE state at points in time when
`configured conditions are satisfied, its storage in measurement log for reporting to eNB/RNC at a later point in time.
`
`IPR2022-00459
`Apple EX1010 Page 6
`
`

`

`MDT measurements: Measurements determined for MDT.
`
`Symbols
`3.2
`For the purposes of the present document, the following symbols apply:
`
`<symbol>
`
`<Explanation>
`
`Abbreviations
`3.3
`For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
`abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
`TR 21.905 [1].
`
`MDT
`
`Minimization of Drive-Tests
`
`4
`
`Main concept and requirements
`
`General
`4.1
`The general principles and requirements guiding the definition of functions for Minimization of drive tests are the
`following:
`
`1) MDT Reporting mode
`There are two modes of reporting for the MDT measurements: non-real-time or immediate reporting.
`A UE in IDLE mode of operation is configured with Logged MDT. I.e. after having initiated Logged MDT the UE
`will not support immediate reporting but instead will apply specific non-real time reporting triggers.
`A UE in CONNECTED mode is configured with Immediate MDT that implies immediate reporting.
`
`2) UE measurement configuration
`The operator shall be able to configure MDT measurements for the UE logging purpose independently from the
`network configurations for normal RRM purposes.
`
`3) UE measurement collection and reporting
`It should be possible for measurement logs to consist of multiple events and measurements taken over time. The
`time interval for measurement collection and reporting shall be separately configurable in order to limit the impact
`on the UE battery consumption and network signalling load. It shall be possible to collect measurements logs
`preceding a particular event (e.g. radio link failure).
`
`4) Geographical scope of measurement logging
`It shall be possible for the operator to configure the geographical area where the defined set of measurements shall
`be collected. Some measurements might run independent of any geographically defined area.
`
`5) Location information
`The measurements shall be linked to available location information and/or other information or measurements that
`can be used to derive location information.
`
`6) Time information
`The measurements in measurement logs shall be linked to a time stamp.
`
`7) Device type information
`The terminal used for MDT shall be able to indicate a set of terminal capabilities which allows the network to
`carefully select the right terminals for specific MDT measurements.
`
`Editor’s note: It is FFS if existing UE capability reporting is sufficient.
`
`IPR2022-00459
`Apple EX1010 Page 7
`
`

`

`8) Dependency on SON
`The solutions for MDT shall be able to work independently from SON support in the network. Relation between
`measurements/solution for MDT and UE side SON functions shall be established in a way that re-use of functions
`is achieved where possible.
`
`The solutions for MDT shall take into account the following constraints:
`
`1) UE measurements
`The UE measurement logging mechanism is an optional feature. In order to limit the impact on UE power
`consumption and processing, the UE measurement logging should as much as possible rely on the measurements
`that are available in the UE according to radio resource management enforced by the access network.
`
`2) Location information
`The availability of location information is subject to UE capability and/or UE implementation. Solutions requiring
`location information shall take into account power consumption of the UE due to the need to run its positioning
`components.
`
`5
`
`Functions and procedures
`
`5.1
`
`General procedures
`
`5.1.1
`Logged MDT procedures
`Support of Logged MDT complies with the principles for idle mode measurements in the UE specified in TS 25.133[5]
`and TS 36.133 [6].
`
`NOTE: It should be noted the established principles may result in different logged information in different UEs and
`less information about neighbour cells.
`
`Further, measurement logging is differentiated based on UE states in idle mode i.e. camped normally, any cell selection
`or camped on any cell. The UE shall perform measurement logging in “camped normally” state. In “any cell selection”
`and “camped on any cell” state the UE is not required to perform MDT measurement logging (including time and
`location information).
`
`For Logged MDT, configuration, measurement collection and reporting of the concerning measurement will always be
`done in cells of the same RAT type.
`
`Eitor’s note: It is FFS if extension across RATs should be possible.
`
`There is no need to align the specification of procedural aspects of idle mode measurements with those of the connected
`mode measurements.
`
`Measurement configuration
`5.1.1.1
`Logged MDT measurements are configured with a separate MDT Measurement Configuration procedure, as shown in
`Figure 5.1.1.1-1.
`
`IPR2022-00459
`Apple EX1010 Page 8
`
`

`

`UE
`
`(E-)UTRAN
`
`IdleMDTConfiguration
`
`Figure 5.1.1.1-1: MDT measurement configuration for Logged MDT
`
`Network initiates the procedure to UE in RRC Connected by sending IdleMDTConfiguration message, which is used to
`transfer configuration parameters for Logged MDT to be performed in idle mode. This is unidirectional procedure and
`there is no need to introduce a failure message or a confirmed message.
`A single sequence is used to specify the object, the reporting configuration as well as the quantity configuration, i.e.
`there is no need to use any sub-structuring logged MDT configuration.
`
`5.1.1.1.1
`Configuration parameters
`The MDT measurement configuration consists of:
`
`-
`
`configuration of the measurements to be logged, i.e. the measurement object (frequency). The measurement
`quantity is fixed for logged MDT and consists of both RSRP and RSRQ for EUTRA, both RSCP and Ec/No for
`UTRA and Rxlev for GERAN.
`
`NOTE: Additional measurement object parameter such as cell specific offset is not necessary for Logged MDT
`
`-
`
`-
`
`-
`
`-
`
`configuration of the triggering of logging events. Periodic downlink pilot strength measurement trigger is
`supported, for which the measurement interval (in multiples of the applied IDLE mode DRX cycle) can be
`configured.
`
`Editor’s note: It is FFS whether remaining measurements indentified in Study Item will be supported in the
`current release
`
`configuration of the total duration of logging. The timer is activated at the moment of configuration. When the
`timer expires the logging is stopped and the configuration is cleared.
`
`network absolute time stamp to be used as a time reference to UE
`
`(optionally) configuration of a measurements area. A UE will collect measurements as long as it is within the
`configured measurement area. The scope of the measurement area may consist of one of:
`a list of 32 global cell identities. If this list is configured, the UE will only log measurements when
`•
`camping in any of these cells
`a list of TAs or LAs or RAs. If this list is configured, the UE will only log measurements when camping
`in any cell belonging to the preconfigured TA/LA/RAs.
`If no area scope is configured, the configuration is valid in the entire RPLMN of the UE, i.e. the UE will log
`measurements throughout the RPLMN.
`
`•
`
`NOTE: There is no need to introduce a measurement identity for Logged MDT.
`
`Configuration effectiveness
`5.1.1.1.2
`The configuration is provided in a cell by dedicated control while UE is in CONNECTED and implies:
`
`- measurement configuration is valid in IDLE
`
`IPR2022-00459
`Apple EX1010 Page 9
`
`

`

`- measurement configuration and logs are maintained when the UE is in IDLE, i.e. during multiple IDLE
`periods interrupted by IDLE->CONNECTED->IDLE state transitions
`
`- measurement configuration and logs are maintained when the UE is in IDLE in that RAT, i.e. during multiple
`IDLE periods interrupted by UE presence in another RAT
`
`There is only one RAT-specific configuration for Logged MDT in the UE. When the network provides a configuration,
`any previously configured MDT measurements configuration will be entirely replaced by the new one. Moreover,
`logged measurements corresponding to the previous configuration will be cleared at the same time. It is left up to the
`network to retrieve any relevant data before providing a new configuration.
`
`NOTE: The network may have to do inter-RAT coordination
`
`MDT configuration and corresponding measurement log shall be cleared by the UE at any PLMN change (irrespective
`of the Equivalent PLMN list).
`
`Editor’s note: The behaviour in shared network environment is FFS.
`
`Measurement collection
`5.1.1.2
`In “camp normally” state, a UE shall perform logging as per the configuration. This state includes a period between cell
`selection criteria not being met and UE entering “any cell selection” state, i.e. 10 s for E-UTRA [6] or 12 s for UTRA
`[5]. In “any cell selection” or “camped on any cell” state, the periodic logging stops. However, it should be noted that
`time stamp information and duration timer continue normally. When the UE re-enters “camped normally” state and the
`duration timer has not expired, the periodic logging is restarted based on new DRX and logging resumes automatically
`(with a leap in time stamp).
`
`UE collects MDT measurements and continue logging according to Logged MDT configuration until UE memory
`reserved for MDT is exceeded. Once log volume exceeds the suitable UE memory, the UE stops logging, stops the
`duration timer and starts the 48 hour timer.
`
`Editor’s note: The size of MDT memory is FFS.
`
`5.1.1.3
`
`Measurement reporting
`
`Availability Indicator
`5.1.1.3.1
`A UE configured to perform Logged MDT measurements in IDLE indicates the availability of MDT measurements, by
`means of a one bit indicator, in RRCConnectionSetupComplete message during connection establishment. Furthermore,
`the indicator (possibly updated) can be provided within E-UTRAN handover and re-establishment, and UTRAN
`procedures SRNC (SRNC relocation involving the change of).The UE includes the indication in one of these messages
`at every transition to RRC Connected mode even though the logging period has not ended, upon connection to RAT,
`which configured the UE to perform Logged MDT measurements. The UE will not indicate the availability of MDT
`measurements in another RAT.
`The network can decide to retrieve the logged measurements based on this indication. In case logged MDT
`measurements are retrieved before the completion of the pre-defined logging duration, the reported measurement results
`are deleted, but MDT measurement logging will continue according to ongoing Logged MDT configuration.
`In case the network will not retrieve logged MDT measurements, UE should store non-retrieved measurements for 48
`hours from the moment the duration timer for logging expired. There is no requirement to store non-retrieved data
`beyond 48 hours. In addition, all related MDT configuration and logging shall be removed by the UE at switch off.
`
`Report retrieval
`5.1.1.3.2
`For Logged MDT the measurement reporting is triggered by on-demand mechanism, i.e. the UE is asked by the network
`to send the collected measurement logs via RRC signalling. In E-UTRAN, UE Information procedure defined in [4] is
`used to request UE to send the collected measurement logs. The reporting may occur in different cells than which the
`measurement configuration is signalled.
`
`IPR2022-00459
`Apple EX1010 Page 10
`
`

`

`Reporting parameters
`5.1.1.3.3
`The logged measurement report consists of measurement results for the serving cell (the measurement object and the
`measurement quantity), time stamp and location information. Available UE measurements performed in idle for intra-
`frequency/inter-frequency/inter-RAT can be reported.
`
`Editor’s note: It is FFS whether the configuration should be able to restrict the amount of reporting from neighbours.
`
`The measurement report is self contained, i.e. the RAN node is able to interpret the Logged MDT reporting results even
`if it does not have access to the logged MDT measurement configuration.
`
`For each MDT measurement the UE includes a relative time stamp. The base unit for time information in the logged
`MDT reports is the second. The time stamp is counted in seconds from the moment the MDT configuration is received
`at the UE, relative to the absolute time stamp received within the configuration. The absolute time stamp is the current
`network time at the point when Logged MDT is configured to the UE. The UE echoes back this absolute reference time.
`The time format for logged MDT report is: DD HH-MM-SS.
`
`Location information is based on available location information in the UE. Thus, the Logged MDT measurements are
`tagged by the UE with location data in the following manner:
`
`-
`
`-
`
`-
`
`ECGI of the serving cell when the measurement was taken is always included
`
`GNSS location information is included if available in the UE when the measurement was taken. If GNSS
`location information is available the reporting shall consist of latitude and longitude. Depending on
`availability, altitude may be also additionally included.
`
`if GNSS location information is not available when the measurement was taken, the UE includes RF
`fingerprint information consisting of: PCI/PSC + RSRP/CPICH RSCP for up to 6 intra-frequency neighbour
`cells
`
`Editor’s note: It is FFS when GNSS location information is considered available for the logged measurement, e.g.
`the acceptable time lag.
`
`MDT context handling during handover
`5.1.1.4
`For Logged MDT in IDLE, no need is identified to transfer an MDT context (any related configuration information
`about measurement and reporting) between (e)NBs/RNCs. In addition, MDT context is assumed to be released in the
`RAN nodes when the UE is in IDLE.
`
`5.1.2
`
`Immediate MDT procedures
`
`5.1.2.1 Measurement configuration
`For Immediate MDT, the configuration is based on the existing RRC measurement procedures for configuration and
`reporting, potentially with some extensions, e.g. for location information.
`
`NOTE: No extensions related to time stamping are expected for Immediate MDT i.e. time stamping is expected to
`be provided by eNB/RNC.
`
`With respect to positioning configuration, the network will not be able to force UE to provide accurate location
`information.
`5.1.2.2 Measurement reporting
`For Immediate MDT, measurement results should be tagged with available location information in the same way as for
`Logged MDT in Idle mode specified in 5.1.1.3.3. I.e. location information is based on available location information in
`the UE. Thus, the Immediate MDT measurements are tagged by the UE with location data in the following manner:
`
`-
`
`ECGI of the serving cell when the measurement was taken is always included
`
`IPR2022-00459
`Apple EX1010 Page 11
`
`

`

`-
`
`-
`
`GNSS location information is included if available in the UE when the measurement was taken. If GNSS
`location information is available the reporting shall consist of latitude and longitude. Depending on
`availability, altitude may be also additionally included.
`
`if GNSS location information is not available when the measurement was taken, the UE includes RF
`fingerprint information consisting of: PCI/PSC + RSRP/CPICH RSCP for up to 6 intra-frequency neighbour
`cells
`
`Normal RRC signalling in (E-)UTRA procedures are enhanced to support this.
`5.1.2.3 MDT context handling during handover
`The measurements configured in the UE for Immediate MDT should fully comply with the transferring and
`reconfiguration principles for the current measurements configured in the UE for RRM purpose during handover
`(including conformance with Rel-8 and Rel-9).
`
`In addition, MDT configuration handling during handover depends on MDT initiation from OAM defined in section
`5.1.3:
`
`- The MDT configuration configured by management based trace function will not propagate during handover.
`
`- The MDT configuration received by signalling based trace messages for a specific UE will propagate during
`handover.
`
`5.1.3 MDT Initiation
`There are two cases that RAN should initiate a MDT measurements collection task. One is that the MDT task is
`initiated towards a region (limited by a cell list or a TA list) by the cell traffic trace, i.e. management based trace
`function from OAM. The other is that the MDT task is initiated towards a specific UE by the S1 signaling trace
`activation messages from CN nodes, i.e. the Initial Context Setup message and the Trace Start message in E-UTRAN,
`the CN Invoke Trace message in UTRAN. The detailed procedures to transfer the MDT configurations to RAN are
`specified in [7].
`
`UE capabilities
`5.1.4
`MDT relevant UE capabilities are component of radio access UE capabilities. Thus the procedures used for handling
`UE radio capabilities over (E-)UTRAN apply.
`
`5.1.5
`
`UE measurements
`
`5.2
`
`E-UTRAN solutions
`
`RRC_CONNECTED
`5.2.1
`UE in RRC Connected does not support Logged MDT in this release of the specification. In order to support Immediate
`MDT, the existing RRC measurement configuration and reporting procedures apply. Some extensions are required to
`carry out location information reporting.
`5.2.1.1
`Measurements and reporting triggers for Immediate MDT
`Measurements to be performed for Immediate MDT purposes involve E-UTRAN reporting triggers and criteria utilized
`for RRM. In particular, the following measurements shall be supported for Immediate MDT performance:
`
`Measurements:
`- M1: RSRP and RSRQ measurement by UE
`- M2: Power Headroom (PH) measurement by UE
`
`- M3: Uplink signal strength/SINR measurement by eNB
`
`IPR2022-00459
`Apple EX1010 Page 12
`
`

`

`RRC reporting triggers:
`
`-
`
`-
`
`-
`
`Periodic
`
`For M1:
`o
`Serving cell becomes worse than threshold; event A2
`o
`o Radio Link Failure
`For M2:
`o N/A
`NOTE: PHR is carried by MAC signalling. Thus, the existing mechanism of PHR transmission applies.
`
`For M3:
`o N/A
`
`Enhancement to Radio Link Failure report
`5.2.1.2
`Upon Radio Link Failure detection in the UE, RLFreport defined in [4] also includes available location information on
`where RLF occurred, i.e. if GNSS location information is available the reported location information in RLFreport
`consist of:
`
`-Latitude, longitude (mandatory)
`
`-Altitude (conditional on availability)
`
`-Velocity (conditional on availability)
`
`-Direction (conditional on availability).
`
`Editor’s note: It remains FFS whether additional enhancements for RLF report (e.g. IDLE survival, separate small
`buffer) are introduced as part of Immediate MDT.
`
`RRC_IDLE
`5.2.2
`For UE in RRC idle state Logged MDT procedures as described in 5.1.1 apply.
`
`Logged MDT measurements retrieval is carried on Signalling Radio Bearer SRB2.
`
`5.3
`
`UTRAN solutions
`
`UTRA RRC Connected
`5.3.1
`In CELL_PCH and URA_PCH states UE supports Logged MDT. In CELL_DCH state UE supports Immediate MDT.
`In CELL_FACH state MDT is not supported in the current release.
`
`Editor’s note: It is FFS whether additional details should be specified (e.g. for CELL_FACH entrance at Cell
`Update).
`
`Measurements and reporting events for Immediate MDT
`5.3.1.1
`The solutions for Immediate MDT in UTRAN are only applicable for UEs in CELL_DCH state. Measurements to be
`performed for Immediate MDT purposes involve normal UTRAN reporting triggers and criteria utilized for controlling
`the RRC connection. In particular, the following measurements shall be supported for Immediate MDT performance:
`
`Measurements:
`
`- M1: CPICH RSCP and CPICH Ec/No measurement by UE
`
`IPR2022-00459
`Apple EX1010 Page 13
`
`

`

`- M2: Uplink signal strength/SINR measurement by NodeB
`
`RRC reporting triggers:
`
`Periodic
`
`Primary CPICH becomes worse than an absolute threshold; event 1F
`
`-
`
`-
`
`For M1:
`o
`o
`For M2:
`o N/A
`UTRA Idle
`5.3.2
`For UEs in UTRA Idle state Logged MDT procedures as described in 5.1.1 apply.
`
`Logged MDT measurements retrieval is carried on Signalling Radio Bearer SRB4.
`
`Annex A (informative): Coverage use cases
`The MDT data reported from UEs may be used to monitor and detect coverage problems in the network. Some
`examples of use cases of coverage problem monitoring and detection are described in the following:
`‐ Coverage hole: A coverage hole is an area where the signal level SNR (or SINR) of both serving and allowed
`neighbor cells is below the level needed to maintain basic service (SRB & DL common channels), i.e. coverage
`of PDCCH. Coverage holes are usually caused by physical obstructions such as new buildings, hills, or by
`unsuitable antenna parameters, or just inadequate RF