Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 32.421  Word version:  19.0.0

Top   Top   Up   Prev   Next
0…   4…   4.2   4.3   5…   6…   A…   A.10… 
6 Requirements for managing MDT  6.1  Business Level Requirements  6.2 Specification level requirements  7 Requirements for managing RRC reports  7.0 General  7.1 Business level requirements  7.2 Specification level requirements 
...

 

6  Requirements for managing MDT |R10|  p. 31

6.1  Business Level Requirements  p. 31

REQ-MDT-CON-1
The Operator shall be able to collect measurements for Network Performance Management purposes from UEs within their network.
REQ-MDT-CON-2
The collected measurements shall be made available in a centralised entity.
REQ-MDT-CON-3
Operator shall be able to select specific set of subscribers for the measurement collection based on IMSI.
REQ-MDT-CON-4
Operator shall be able to select specific set of devices for the measurement collection based on IMEI(SV).
REQ-MDT-CON-5
Operator shall be able to select specific set of devices for the measurement collection based on geographical area.
REQ-MDT-CON-6
Operator shall be able to select specific set of devices for the measurement collection based on device capabilities.
REQ-MDT-CON-7
Operator shall be able to select specific set of subscribers based on IMSI and a geographical area for the measurement collection.
REQ-MDT-CON-8
Operator shall be able to select specific set of devices based on IMEI(SV) and a geographical area for the measurement collection.
REQ-MDT-CON-9
Operator shall be able to configure set of device capabilities and a geographical area for the measurement collection.
REQ-MDT-CON-10
Operator shall be able to select specific set of subscribers based on IMSI and a set of device capabilities and a geographical area for the measurement collection.
REQ-MDT-CON-11
Operator shall be able to select specific set of devices IMEI(SV) and capabilities and a geographical area for the measurement collection.
REQ-MDT-CON-12
Operator shall be able to select set of subscribers based on IMSI and a set of device capabilities for the measurement collection
REQ-MDT-CON-13
Operator shall be able to select specific set of devices IMEI(SV) and capabilities for the measurement collection.
REQ-MDT-CON-14
The operator shall be able to configure the duration of the measurement collection.
REQ-MDT-CON-15
The operator shall be able to configure the UE measurement types and events for collection.
REQ-MDT-CON-16
The operator shall be able to configure the type of UE measurement reporting and log formats i.e. raw measurement results or type of measurement aggregation (e.g. statistical aggregation of raw measurement results, sampling of raw measurement results, etc.)
REQ-MDT-CON-17
The management of MDT shall be independent from the management of SON functionalities
REQ-MDT-CON-18
The management of UE based network performance measurements shall allow the network operator to control whether or not it is possible to link a measurement result and related information (e.g. location information) to the user terminal type ID (i.e. IMEI-TAC).
REQ-MDT-CON-19
An operator that uses more than one PLMN shall be able to activate MDT in each of those PLMN and continue MDT cross its own PLMN IDs.
REQ-MDT-CON-20
The operator shall be able to request collection of positioning information related to UE measurements.
REQ-MDT-CON-21
Operator shall be able to correlate the location information with the MDT UE measurements.
REQ-MDT-CON-22
MDT function shall support RAN sharing scenarios.
REQ-MDT-CON-23
The TCE used to collect MDT data shall be controlled by the same operator, as the operator that the user has given his consent to.
REQ-MDT-CON-24
Operator shall be able to minimize the amount of redundant MDT data.
REQ-MDT-CON-25
For management based MDT data collection, operator shall be able to specify the desired amount of MDT data and the desired number of UEs over period of time.
REQ-MDT-CON-26
The MOP shall be able to select UEs according to the POP intention.
REQ-MDT-CON-27
The recorded Subscriber and Equipment Trace data related to a particular POP shall be delivered to that POP but no other POP.
REQ-MDT-CON-28
The Operator shall be able to collect MBSFN UE measurements.
REQ-MDT-CON-29
The operator shall be able to request collection of sensor information related to UE measurements.
REQ-MDT-CON-30
The operator shall be able to configure MDT for a UE in dual connected mode both on primary and secondary node.
Up

6.2  Specification level requirements  p. 32

6.2.1  Logged MDT and Immediate MDT requirements |R13|  p. 32

All requirements are valid for Logged MDT and Immediate MDT functionality if not mentioned otherwise:
REQ-MDT-FUN-01
It shall be possible to collect UE measurements based on one or more IMEI(SV) number.
REQ-MDT-FUN-02
It shall be possible to collect UE measurements based on one or more IMSI number.
REQ-MDT-FUN-03
It shall be possible to collect UE measurement logs preceding and following a particular event (e.g. radio link failure).
REQ-MDT-FUN-04
Each UE measurement result shall be linked to a time stamp. Accuracy of time information including absolute time and relative time. The absolute time can refer to the absoluteTimeStamp IE defined in clause 6.2.2 of TS 36.331 for LTE or the absoluteTimeInfo IE in clause 11.3 of TS 25.331 for UMTS. The relative time can refer to the relativeTimeStamp IE defined in clause 6.2.2 of TS 36.331 for LTE or the relativeTimeStamp IE in clause 11.3 of TS 25.331 for UMTS.
REQ-MDT-FUN-05
The solutions for collecting UE measurements for the purpose of minimization of drive tests shall be able to work independently from SON support in the network.
REQ-MDT-FUN-06
It shall be possible to collect UE measurements in one or more cells or TA/RA/LA.
REQ-MDT-FUN-07
It shall be possible to collect UE measurements based on one or more IMSI in one or more cells or TA/RA/LA.
REQ-MDT-FUN-08
It shall be possible to collect UE measurements based on one or more IMEI(SV) in one or more cells or TA/RA/LA.
REQ-MDT-FUN-09
It shall be possible to configure UE measurement types and triggering conditions under which UE measurements would be collected for MDT.
REQ-MDT-FUN-10
Void.
REQ-MDT-FUN-11
It shall be possible to configure the condition of MDT data collection based on certain device capability information in one or more cells or in TA/RA/LA.
REQ-MDT-FUN-12
It shall be possible to configure MDT data collection based on one or more IMSI/SUPI in one or more cells or TA/RA/TA with a set of device capability information.
REQ-MDT-FUN-13
It shall be possible to configure MDT data collection based on one or more IMEI(SV) in one or more cells or TA/RA/TA with a set of device capability information.
REQ-MDT-FUN-14
It shall be possible to configure MDT data collection based on one or more IMEI(SV) with a set of device capability information.
REQ-MDT-FUN-15
It shall be possible to configure MDT data collection based on one or more IMSI/SUPI with a set of device capability information.
REQ-MDT-FUN-16
It shall be possible to activate a Trace Session for MDT data collection (or UE measurement collection for MDT purpose) independently from other mobility related performance measurements and call trace collection.
REQ-MDT-FUN-17
It shall be possible to deactivate MDT data collection by using Trace Reference.
REQ-MDT-FUN-18
It shall be possible to create a combine Trace Session for UE measurement collection and for subscriber and equipment/cell trace.
REQ-MDT-FUN-19
Void.
REQ-MDT-FUN-20
MDT activation shall be supported for a UE belonging to any PLMN within the same MDT PLMN list.
REQ-MDT-FUN-21
MDT data collection shall continue if a user is changing PLMN and the target PLMN within the same MDT PLMN list.
REQ-MDT-FUN-22
It shall be possible to collect positioning data related to UE measurements, which can be either geographical coordinates or raw positioning measurements sufficient to be input for a post processing positioning algorithm.
REQ-MDT-CON-23
It shall be possible for management system to correlate MDT UE measurements with location information.
REQ-MDT-FUN-24
The PLMN where TCE collecting MDT data resides shall match the RPLMN of the UE providing the MDT data.
REQ-MDT-FUN-25
In the case of Management based MDT the MOP shall be able to select UEs according to the POP intention.
REQ-MDT-FUN-26
The recorded Subscriber and Equipment Trace data related to a particular POP shall contain information so that if can be sent to that POP.
REQ-MDT-FUN-27
In case of non-file-based trace reporting, binary encoding shall be used for the transfer of all MDT data from data producer to the data consumer.
REQ-MDT-FUN-28
It shall be possible to configure MDT report type to be used for logged MDT for NR.
REQ-MDT-FUN-29
Management based MDT configuration and signalling based MDT configuration shall be able to coexist in parallel for NR.
REQ-MDT-FUN-30
In case of logged MDT, it shall be possible to collect specific NR neighbour cell measurements on cell level.
REQ-MDT-FUN-31
It shall be possible to continue the actual ongoing process of logging for the UE in RRC INACTIVE state when the logging process for the UE starts in RRC IDLE state in NR.
REQ-MDT-FUN-32
In the case of immediate MDT, the measurement quantities shall be able to handle cell level RSRP/RSRQ/SINR in LTE and NR and beam level BRSRP/BRSRQ/BSINR in NR.
REQ-MDT-FUN-33
In the case of signalling based immediate MDT, configuration shall be able to propagate across RATs for the case of Xn inter-RAT intra-system handover to/from NR.
REQ-MDT-FUN-34
In the case of EN-DC scenario, for immediate MDT, configuration shall be able to be provided for both primary node and secondary node independently.
REQ-MDT-FUN-35
In the case of MR-DC, there is a split DRB in which data shall be sent over both MN and SN. In such a case, the PDCP data volume shall include the data sent over both MN and SN for that DRB.
REQ-MDT-FUN-36
In the case of immediate MDT, it shall be possible to collect the measurement pollution indication so that TCE is able to correlate and filter polluted measurements in NR.
REQ-MDT-FUN-37
In the case of immediate MDT, it shall be possible to configure beam level BRSRP/BRSRQ/BSINR in NR.
REQ-MDT-FUN-38
It shall be possible to collect UE measurements in one or more CAG in case of PNI-NPN networks.
REQ-MDT-FUN-39
It shall be possible to collect UE measurements based on one or more IMSI in one or more CAG in case of PNI-NPN networks.
REQ-MDT-FUN-40
It shall be possible to collect UE measurements based on one or more IMEI(SV) in one or more CAG in case of PNI-NPN networks.
REQ-MDT-FUN-41
It shall be possible to configure the condition of MDT data collection based on device capability information in one or more CAG in case of PNI-NPN networks.
REQ-MDT-FUN-42
It shall be possible to configure MDT data collection based on one or more IMSI/SUPI in one or more CAG in case of PNI-NPN networks with a set of device capability information.
REQ-MDT-FUN-43
It shall be possible to configure MDT data collection based on one or more IMEI(SV) in one or more CAG in case of PNI-NPN networks with a set of device capability information.
Up

6.2.2  Logged MBSFN MDT requirements |R13|  p. 34

Requirements in clause 6.2.1 that apply to MBSFN MDT are as follows:
REQ-MDT-FUN-01
REQ-MDT-FUN-02
REQ-MDT-FUN-03
REQ-MDT-FUN-04
REQ-MDT-FUN-05
REQ-MDT-FUN-06
REQ-MDT-FUN-07
REQ-MDT-FUN-08
REQ-MDT-FUN-09
REQ-MDT-FUN-11
REQ-MDT-FUN-12
REQ-MDT-FUN-13
REQ-MDT-FUN-14
REQ-MDT-FUN-15
REQ-MDT-FUN-20
REQ-MDT-FUN-21
REQ-MDT-FUN-24
REQ-MDT-FUN-25
REQ-MDT-MBSFN-FUN-1
It shall be possible to activate a Session for Logged MBSFN MDT data collection independently from other mobility related performance measurements and call trace collection.
REQ-MDT-MBSFN-FUN-2
It shall be possible to configure MBSFN MDT data collection based on certain device capability information in specific MBSFN area(s).
REQ-MDT-MBSFN-FUN-3
It shall be possible to deactivate Logged MBSFN MDT data collection by using Trace Reference.
REQ-MDT-MBSFN-FUN-4
It shall not be possible to combine Logged MBSFN MDT session with any other trace sessions.
Up

7  Requirements for managing RRC reports |R11|  p. 36

7.0  General |R19|  p. 36

The term RRC reports is used for the RLF, RCEF, RA, SHR, SPR, MHI and VisitedCellInfoList reports for NG-RAN. A NG-RAN node can configure the UE so these reports are generated when specific triggers occur. The UE will notify the NG-RAN node when the reports are available, and the NG-RAN node can subsequently retrieve the reports.

7.1  Business level requirements  p. 36

REQ-RLF-CON-1
The Operator shall be able to collect RLF and RCEF reports from eNBs within their network.
REQ-RLF-CON-2
The collected reports shall be made available in a centralised entity.
REQ-RLF-CON-3
The Operator shall be able to select certain areas for collecting reports.
REQ-RLF-CON-4
The Operator shall be able to collect RLF and RCEF reports from NG-RAN nodes within their network. The Operator shall be able to collect RRC reports from NG-RAN nodes within their network.

7.2  Specification level requirements  p. 36

REQ-RLF-FUN-01
It shall be possible to collect RLF and RCEF reports in one or more eNodeBs.
REQ-RLF-FUN-02
It shall be possible to activate a Trace Session for reports data collection independently from other Trace jobs.
REQ-RLF-FUN-03
It shall be possible to collect reports in one or more NG-RAN nodes.
REQ-RLF-FUN-04
In case of non-file-based trace reporting, binary encoding or GPB shall be used for the transfer of all reports data from data producer to the data consumer.
REQ-RLF-FUN-05
It shall be possible to collect neighbour cell measurements for RLF and RCEF reports in one or more eNodeBs and NG-RAN nodes. It shall be possible to collect neighbour cell measurements for RRC reports in one or more NG-RAN nodes.
REQ-RLF-FUN-06
It shall be possible to collect SCGF information for RLF reports in one or more RAN nodes in the case of MR-DC scenario.
Up

Up   Top   ToC