3GPP TS 37.320 V10.0.0 (2010-12)
`
`Technical Specification
`
`3rd Generation Partnership Project;
`Technical Specification Group Radio Access Network;
`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)
`
`
`
`
`
`A GLOBAL INITIATIVE
`
`
`
`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.
`
`
`
`Samsung Ex. 1011
`1 of 17
`
`

`

`
`
`
`
`
`
`Keywords
`UTRA, LTE, MDT
`
`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.
`
`
`UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
`3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
`LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
`GSM® and the GSM logo are registered and owned by the GSM Association
`
`Samsung Ex. 1011
`2 of 17
`
`

`

`Contents
`Foreword............................................................................................................................................................. 4
`Introduction ........................................................................................................................................................ 4
`1
`Scope ........................................................................................................................................................ 5
`2
`References ................................................................................................................................................ 5
`3
`Definitions, symbols and abbreviations ................................................................................................... 5
`3.1
`Definitions ......................................................................................................................................................... 5
`3.2
`Symbols ............................................................................................................................................................. 6
`3.3
`Abbreviations ..................................................................................................................................................... 6
`4
`Main concept and requirements ............................................................................................................... 6
`4.1
`General ............................................................................................................................................................... 6
`5
`Functions and procedures ......................................................................................................................... 7
`5.1
`General procedures ............................................................................................................................................ 7
`5.1.1
`Logged MDT procedures ............................................................................................................................. 7
`5.1.1.1
`Measurement configuration .................................................................................................................... 7
`5.1.1.1.1
`Configuration parameters .................................................................................................................. 8
`5.1.1.1.2
`Configuration effectiveness .............................................................................................................. 8
`5.1.1.2
`Measurement collection .......................................................................................................................... 9
`5.1.1.3
`Measurement reporting ........................................................................................................................... 9
`5.1.1.3.1
`Availability Indicator ........................................................................................................................ 9
`5.1.1.3.2
`Report retrieval ............................................................................................................................... 10
`5.1.1.3.3
`Reporting parameters ...................................................................................................................... 10
`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
`5.2.1.1
`Measurements and reporting triggers for Immediate MDT .................................................................. 12
`5.2.1.2
`Enhancement to Radio Link Failure report........................................................................................... 13
`5.2.2
`RRC_IDLE ................................................................................................................................................. 13
`5.3
`UTRAN solutions ............................................................................................................................................ 13
`5.3.1
`UTRA RRC Connected .............................................................................................................................. 13
`5.3.1.1
`Measurements and reporting events for Immediate MDT .................................................................... 14
`5.3.2
`UTRA Idle .................................................................................................................................................. 14
`Coverage use cases ......................................................................................... 15
`Annex A (informative):
`Change history ............................................................................................... 16
`Annex B (informative):
`
`
`Samsung Ex. 1011
`3 of 17
`
`

`

`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.
`
`Samsung Ex. 1011
`4 of 17
`
`

`

`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]
`
`3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
`
`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 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 32.422: “Subscriber and equipment trace; Trace control and configuration management”
`
`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 mode, CELL_PCH and
`URA_PCH states (when UE is in UTRA) 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.
`
`MDT measurements: Measurements determined for MDT.
`MDT PLMN: A PLMN that is the RPLMN for the UE at the point of receiving MDT measurement configuration.
`
`Samsung Ex. 1011
`5 of 17
`
`

`

`Symbols
`3.2
`For the purposes of the present document, the following symbols apply:
`
`<Explanation>
`
`<symbol>
`
`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
`It 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 MDT measurement reports to consist of multiple events and measurements taken over
`time. The time interval for measurement collection and reporting shall be decoupled 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 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.
`
`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.
`
`9. Dependency on TRACE
`The existing subscriber/cell trace functionality will be reused and extended to support MDT. If the MDT is
`
`Samsung Ex. 1011
`6 of 17
`
`

`

`initiated toward to a specific UE (e.g. based on IMSI, IMEI-SV, etc.), the signalling based trace procedure is
`used, otherwise the management based trace procedure (or cell traffic trace procedure) will be used.
`
`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[2]
`and TS 36.133 [3].
`
`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.
`
`Editor’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.
`
`
`
`Samsung Ex. 1011
`7 of 17
`
`

`

`UE
`
`I
`
`
`
`LoggingConfiguration
`
`(E-)UTRAN
`
`I
`
`Figure 5.1.1.1-1: MDT measurement configuration for Logged MDT
`
`
`
`Network initiates the procedure to UE in RRC Connected by sending LoggingConfiguration message, which is used to
`transfer configuration parameters for Logged MDT. This is unidirectional procedure. A release operation for Logged
`MDT configuration is realized only by configuration replacement in case the other node overwrites the configuration or
`by configuration clearance in case a duration timer stopping or expiration condition is met.
`
`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.
`
`Configuration parameters
`5.1.1.1.1
`The MDT measurement configuration consists of:
`
`- configuration of the triggering of logging events. Only periodic downlink pilot strength measurement trigger is
`supported, for which the logging interval is configurable. The parameter specifies the periodicity for storing
`MDT measurement results. It should be configured in seconds in multiples of the applied IDLE mode DRX, i.e.
`multiples of 1.28s which is either a factor or multiple of the IDLE mode DRX. The UE behaviour is unspecified
`when the UE is configured with a DRX cycle larger than the logging interval.
`
`- configuration of the logging duration. This configuration parameter defines a timer activated at the moment of
`configuration, that continues independent of state changes, RAT or RPLMN change. 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 logging area. A UE will log measurements as long as it is within the configured
`logging area. The scope of the logging 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 8 TAs or 8 LAs or 8 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 MDT PLMN of the UE, i.e. the UE will log
`measurements throughout the MDT PLMN.
`
`
`NOTE: There is no need to introduce a measurement identity for Logged MDT.
`
`NOTE: Additional measurement object parameter such as cell specific offset is not necessary 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 UE state in E-UTRAN, or
`
`in IDLE mode, CELL_PCH and URA_PCH states in UTRAN
`
`Samsung Ex. 1011
`8 of 17
`
`

`

`- until logging duration timer expires or stops
`
`- 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 is valid only in the MDT PLMN. Logged MDT measurements are performed as long as the
`RPLMN is the MDT PLMN. At PLMN change which results in a new RPLMN (RPLMN≠MDT PLMN), the logging is
`suspended, i.e. the MDT configuration and MDT log are kept but measurement results are not logged.
`
`NOTE: The logging duration timer continues.
`
`In case the new RPLMN provides a configuration any previously configured MDT measurements configuration and
`corresponding MDT log are cleared and overwritten without being retrieved.
`
`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 (See TS 36.133 [3]) or
`12 s for UTRA (See TS 25.133 [2]). 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).
`
`The measurement quantity is fixed for logged MDT (i.e. not configurable) and consists of both RSRP and RSRQ for
`EUTRA, both RSCP and Ec/No for UTRA, P-CCPCH RSCP for UTRA 1.28 TDD, and Rxlev for GERAN.
`
`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. The minimum size for Logged MDT UE memory size is [32KB].
`
`Editor’s note: The minimum memory size is tentatively agreed.
`
`5.1.1.3
`
`Measurement reporting
`
`Availability Indicator
`5.1.1.3.1
`A UE configured to perform Logged MDT measurements indicates the availability of Logged MDT measurements, by
`means of a one bit indicator, in RRCConnectionSetupComplete message during connection establishment. Furthermore,
`the indicator (possibly updated) shall be provided within E-UTRAN handover and re-establishment, and UTRAN
`procedures involving the change of SRNC (SRNC relocation), CELL UPDATE and URA UPDATE messages. 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 indicator shall be also provided in UEInformationResponse message during MDT report retrieval in case the UE
`has not transferred the total log in one RRC message in order to indicate the remaining data availability.
`
`The UE will not indicate the availability of MDT measurements in another RAT.
`
`The network may 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.
`
`Samsung Ex. 1011
`9 of 17
`
`

`

`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. UE Information procedure defined in TS 25.331 [4] and TS
`36.331 [5] 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.
`
`Transport of Logged MDT reports in multiple RRC messages is supported. With every request, the network may
`receive a part of the total UE log. To indicate the reported data is a segment, the UE should include data availability
`indicator as specified in 5.1.1.3.1. In multiple RRC transmissions for segmented logged MDT reporting, FIFO order is
`followed, i.e. the UE should provide oldest available measurement entries in earliest message. There is no requirement
`specified on the size of particular reporting parts. However, each reported part should be “self-decodable”, i.e.
`interpretable even in case all the other parts are lost.
`
`Logged MDT measurements can be retrieved only if RPLMN is MDT PLMN. The UE shall send an empty report when
`retrieval is attempted in other cases.
`
`
`Reporting parameters
`5.1.1.3.3
`The logged measurement report consists of measurement results for the serving cell (the measurement quantity),
`available UE measurements performed in idle for intra-frequency/inter-frequency/inter-RAT, time stamp and location
`information.
`
`The number of neighbouring cells to be logged is limited by a fixed upper limit per frequency for each category below.
`The UE should log the measurement results for the neighbouring cells, if available, up to:
`
`-
`
`-
`
`-
`
`-
`
`-
`
`6 for intra-frequency neighbouring cells
`
`3 for inter-frequency neighbouring cells
`
`3 for GERAN neighbouring cells
`
`3 for UTRAN (if non-serving) neighbouring cells
`
`3 for E-UTRAN (if non-serving) neighbouring cells
`
`The measurement reports for neighbour cells consist of:
`
`-
`
`Physical cell identity of the logged cell
`
`- Carrier frequency (for inter-frequency and inter-RAT neighbours)
`
`- RSRP and RSRQ for EUTRA
`
`- RSCP and Ec/No for UTRA,
`P-CCPCH RSCP for UTRA 1.28 TDD, and
`- Rxlev for GERAN
`
`-
`
`For any logged cell (serving or neighbour), latest available measurement made for cell reselection purposes is included
`in the log only once, while measurements are performed in accordance with requirements defined in TS 25.133 [2] and
`TS 36.133 [3].
`
`While logging neighbour cells measurements, the UE shall determine a fixed number of best cells based on the
`measurement quantity used for ranking during cell reselection per frequency or RAT.
`
`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. In the log, the time stamp indicates the point in time when periodic logging timer expires.
`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
`
`Samsung Ex. 1011
`10 of 17
`
`

`

`when Logged MDT is configured to the UE. The UE echoes back this absolute reference time. The time format for
`logged MDT report is: YY-MM-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 or Cell-Id of the serving cell when the measurement was taken is always included in E-UTRAN or
`UTRAN respectively
`
`- Detailed location information (e.g. GNSS location information) is included if available in the UE when the
`measurement was taken. If detailed location information is available the reporting shall consist of latitude and
`longitude. Depending on availability, altitude may be also additionally included. UE tags available detailed
`location information only once with upcoming measurement sample, and then the detailed location
`information is discarded, i.e. the validity of detailed location information is implicitly assumed to be one
`logging interval.
`
`-
`
`if detailed 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
`
`Depending on location information, measurement log/report consists of:
`
`-
`
`-
`
`time information, RF measurements, RF fingerprints, or
`
`time information, RF measurements, detailed location information (e.g. GNSS location information)
`
`MDT context handling during handover
`5.1.1.4
`For Logged MDT in IDLE, CELL_PCH and URA_PCH, 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 with some extensions 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 is not able to force UE to provide accurate location information.
`
` Measurement reporting
`5.1.2.2
`For Immediate MDT, measurement results should provide 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.
`Since ECGI or Cell-Id of the serving cell when the measurement was taken is always known in E-UTRAN or UTRAN
`respectively, thus, the Immediate MDT measurements are tagged by the UE with location data in the following manner:
`
`- Detailed location information (e.g. GNSS location information) is included if available in the UE when the
`measurement was taken. If detailed location information is available the reporting shall consist of latitude and
`longitude. Depending on availability, altitude may be also additionally included. The UE should include the
`available detailed location information only once. For both event based and periodic reporting (see 5.2.1.1), the
`detailed location information can only be included if the report is transmitted within the validity time after the
`detailed location information was obtained.
`
`Editor’s note: It is FFS if the validity time is configurable or specified in standard.
`
`-
`
`if detailed 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
`
`Samsung Ex. 1011
`11 of 17
`
`

`

`NOTE: RF fingerprint information is provided as a part of neighbor cells measurement results
`
`Normal RRC signalling in (E-)UTRA procedures are enhanced to support this.
`
` MDT context handling during handover
`5.1.2.3
`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