ETSI TS 132 442 V18.0.0 (2024-05)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Trace Management Integration Reference Point (IRP); Information Service (IS) (3GPP TS 32.442 version 18.0.0 Release 18)

RTS/TSGS-0532442vi00

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 16-May-2024

Standards Content (Sample)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Trace Management Integration Reference Point (IRP);
Information Service (IS)
(3GPP TS 32.442 version 18.0.0 Release 18)

3GPP TS 32.442 version 18.0.0 Release 18 1 ETSI TS 132 442 V18.0.0 (2024-05)

Reference
RTS/TSGS-0532442vi00
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
https://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2024.
All rights reserved.
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 2 ETSI TS 132 442 V18.0.0 (2024-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under https://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 3 ETSI TS 132 442 V18.0.0 (2024-05)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 System Overview . 7
4.1 System context . 7
4.2 Compliance rules . 8
5 Information Object Classes . . 8
5.1 Imported information entities and local labels . 8
5.2 Class diagram . 8
5.2.1 Attributes and relationships . 8
5.2.2 Inheritance . 10
5.3 Information object class definitions . 10
5.3.1 TraceJob . 10
5.3.1.1 Definition . 10
5.3.1.2 Attributes . 12
5.3.1.3 Attribute constraints . 12
5.3.2 TraceRecord . 14
5.3.2.1 Definition . 14
5.3.2.2 Attributes . 14
5.3.3 TraceIRP . 14
5.3.3.1 Definition . 14
5.3.4 ManagedEntity . 14
5.3.4.1 Definition . 14
5.4 Information relationship definitions . 15
5.4.1 relation-traceIRP-traceJob (M) . 15
5.4.1.1 Definition . 15
5.4.1.2 Roles . 15
5.4.2 relation-traceJob-managedEntity (M) . 15
5.4.2.1 Definition . 15
5.4.2.2 Roles . 15
5.4.3 relation-traceJob-traceRecord (M) . 15
5.4.3.1 Definition . 15
5.4.3.2 Roles . 15
5.5 Information attribute definitions . 16
5.5.1 Definition and legal values . 16
6 Interface Definition . 20
6.1 Class diagram representing interfaces . 20
6.2 Generic rules . 20
6.3 TraceIRPManagement (M) . 21
6.3.1 Operation activateTraceJob (M) . 21
6.3.1.1 Definition . 21
6.3.1.2 Input parameters . 22
6.3.1.3 Output parameters . 25
6.3.1.4 Pre-condition . 25
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 4 ETSI TS 132 442 V18.0.0 (2024-05)
6.3.1.5 Post-condition . 26
6.3.1.6 Exceptions . 26
6.3.1.7 Constraints . 26
6.3.2 Operation deactivateTraceJob (M) . 27
6.3.2.1 Definition . 27
6.3.2.2 Input parameters . 27
6.3.2.3 Output parameters . 27
6.3.2.4 Pre-condition . 27
6.3.2.4 Post-condition . 27
6.3.2.6 Exceptions . 28
6.3.3 Operation listTraceJob (M). 28
6.3.3.1 Definition . 28
6.3.3.2 Input parameters . 28
6.3.3.3 Output parameters . 29
6.3.3.4 Pre-condition . 30
6.3.3.5 Post-condition . 30
6.3.3.6 Exceptions . 30
6.3.3.7 Constraints . 30
6.3.4 Operation listActivatedTraceJobs (M) . 31
6.3.4.1 Definition . 31
6.3.4.2 Input parameters . 31
6.3.4.3 Output parameters . 31
6.3.5 Notification notifyTraceRecordingSessionFailure (O) . 31
6.3.5.1 Definition . 31
6.3.5.2 Input parameters . 31
6.3.5.3 Triggering event . 31
6.3.5.3.1 From state . 31
6.3.5.3.2 To state . 32
6.3.6 Notification notifyTraceSessionLocalActivation (M) . 32
6.3.6.1 Definition . 32
6.3.6.2 Input parameters . 32
6.3.6.3 Triggering event . 32
6.3.6.3.1 From state . 32
6.3.6.3.2 To state . 32
6.3.7 Notification notifyTraceSessionIdentities (CM) . 33
6.3.7.1 Definition . 33
6.3.7.2 Input parameters . 33
6.3.7.3 Triggering event . 33
6.3.7.3.1 From state . 33
6.3.7.3.2 To state . 33
6.3.7.4 Constraint . 33
Annex A (informative): Change history . 34
History . 35

ETSI
3GPP TS 32.442 version 18.0.0 Release 18 5 ETSI TS 132 442 V18.0.0 (2024-05)
Foreword
rd
This Technical Specification has been produced by the 3 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
rd
The present document is part of a TS-family covering the 3 Generation Partnership Project; Technical Specification
Group Services and System Aspects; Telecommunication management; as identified below:
32.441 "Trace Management Integration Reference Point (IRP): Requirements".
32.442 "Trace Management Integration Reference Point (IRP): Information Service (IS)".
32.443 "Trace Management Integration Reference Point (IRP): Common Object Request Broker Architecture
(CORBA) Solution Set (SS)".
32.445 "Trace Management Integration Reference Point (IRP): eXtensible Markup Language (XML) file format
definition".
The present document is part of a TS-family which describes the information service necessary for the
Telecommunication Management (TM) of 3G systems. The TM principles and TM architecture are specified in
3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
Trace provides very detailed information on call level for a specific subscriber or MS. This data is an additional
information source to Performance Measurements and allows deeper investigations in problems solving or in case of
optimization.
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 6 ETSI TS 132 442 V18.0.0 (2024-05)
1 Scope
The present document describes the mechanism used for control and configuration of the Trace, Minimization of Drive
Test (MDT) and Radio Link Failure (RLF) reporting functionality through Itf-N. This specification is applicable to
UMTS networks and EPS networks. GSM Trace is outside of the scope of this specification.
The conditions for supporting Network Sharing are stated in 3GPP TS 32.441 [13].
2 References
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] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[2] 3GPP TS 32.102: "Telecommunication management; Architecture".
[3] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept
and definitions".
[4] Void.
[5] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic
network resources Integration Reference Point (IRP); Network Resource Model (NRM)".
[6] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP): Information Service (IS)".
[7] 3GPP TS 32.342: " Telecommunication management; File Transfer (FT) Integration Reference
Point (IRP): Information Service (IS)".
[8] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP)
management: Information Service (IS)".
[9] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace
control and configuration management".
[10] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM
Integration Reference Point (IRP): Information Service (IS)".
[11] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification"
[12] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC); Protocol specification".
[13] 3GPP TS 32.441: "Trace Management Integration Reference Point (IRP): Requirements".
[14] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".

ETSI
3GPP TS 32.442 version 18.0.0 Release 18 7 ETSI TS 132 442 V18.0.0 (2024-05)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2],
3GPP TS 32.150 [3] and the following apply:
IRPAgent: See 3GPP TS 32.102 [2].
IRPManager: See 3GPP TS 32.102 [2].
MBSFN Area: See 3GPP TS 36.300 [14]
MBSFN Area Reserved Cell: See 3GPP TS 36.300 [14]
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2],
3GPP TS 32.150 [3] and the following apply:
IOC Information Object Class
IRP Integration Reference Point
IS Information Service
MBMS Multimedia Broadcast Multicast Services
MBSFN MBMS over a Single Frequency Network
MDT Minimization of Drive Tests
OMG Object Management Group
RCEF RRC Connection Establisment Failure
RLF Radio Link Failure
UML Unified Modelling Language (OMG)
4 System Overview
4.1 System context
The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 [3] subclause 4.7.
In addition, the set of related IRP(s) relevant to the present IRP is shown in the two diagrams below.

IRPManager IRPAgent
NEs
NM EM
Itf-N
Trace IRP
Figure 4.1.1: System Context A
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 8 ETSI TS 132 442 V18.0.0 (2024-05)

IRPManager IRPAgent
NM NE
Trace IRP
Itf-N
Figure 4.1.2: System Context B
4.2 Compliance rules
For general definitions of compliance rules related to qualifiers (Mandatory/Optional/Conditional) for operations,
notifications and parameters (of operations and notifications) please refer to 3GPP TS 32.150 [3].
5 Information Object Classes
5.1 Imported information entities and local labels
Label reference Local label
3GPP TS 32.622 [5], information object class, Top Top
IRPAgent
3GPP TS 32.622 [5], information object class, IRPAgent
GenericIRP
3GPP TS 32.622 [5], information object class, GenericIRP
NotificationIRP
3GPP TS 32.302 [6], information object class, NotificationIRP
FileTransferIRP
3GPP TS 32.342 [7], information object class, FileTransferIRP
ManagedEntity
3GPP TS 32.602 [10], information object class, ManagedEntity

5.2 Class diagram
5.2.1 Attributes and relationships
This clause introduces the set of Information Object Classes (IOCs) that encapsulate information within the
IRPAgent. The intent is to identify the information required for the TraceIRP implementation of its operations and
notification emission. This clause provides the overview of all support object classes in UML. Subsequent clauses
provide more detailed specification of various aspects of these support object classes.
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 9 ETSI TS 132 442 V18.0.0 (2024-05)

<>
ManagedGenericIRP
(f rom TS 32.312)
<>
TraceRecord
<>
TraceIRP
+thetraceRecord
0.0.nn
+thetraceJob
relation-traceJob-traceRecord
relation-traceIRP-traceJob
+thetraceJob
+thetraceIRP
0.0.nn
<>
+themanagedEntity
<>
+thetraceJob
ManagedEntity
TraceJob
(f rom TS 32.602)
relation-traceJob-managedEntity
11 1.1.nn
Figure 5.2.1: Information Object Class (IOC) UML diagram

ETSI
3GPP TS 32.442 version 18.0.0 Release 18 10 ETSI TS 132 442 V18.0.0 (2024-05)
5.2.2 Inheritance
<>
Top
(f rom TS 32.622)
<>
TraceRecord
<>
TraceJob
<>
ManagedGenericIRP
(f rom TS 32.312)
<>
TraceIRP
Figure 5.2.2: Information Object Class Inheritance UML Diagram
5.3 Information object class definitions
5.3.1 TraceJob
5.3.1.1 Definition
It represents a task that controls the Trace Sessions and collects the trace data (i.e. collects the TraceRecord of
multiple ManagedEntity instances). The TraceReference is a unique ID, which identifies the Trace Session
that has been created by the TraceJob and activated to one or multiple ManagedEntity instance(s).
It represents also the task that controls the UE based network performance measurements.
When a TraceJob is created the following attributes cannot be modified via the Itf-N:
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 11 ETSI TS 132 442 V18.0.0 (2024-05)
- TraceReference
- ListOfInterfaces
- ListofNeTypes
- TraceDepth
- TraceTarget
- TriggeringEvent
- JobType
- areaScope
- ListOfMeasurements
- ReportingTrigger
- ReportInterval
- ReportAmount
- EventThreshold
- LoggingInterval
- LoggingDuration
- IPAddressOfTCE
- AnonymizationofMDTData
- MeasurementPeriodLTE
- MeasurementPeriodUMTS
- CollectionPeriodRrmUmts
- CollectionPeriodRrmLte
- PositioningMethod
- MeasurementQuantity
- PLMNTarget
- MBSFNAreaList
If for any reason the TraceIRP determines that a Trace Session has been activated in its ManagedEntity(ies) the
TraceIRP shall emit the "noitfyTraceSessionLocalActivation" notification to the subscribed
IRPManagers to inform the active Trace Sessions. The IRPManagers can decide whether they deactivate the Trace
Session or keep the Trace Session active. (E.g. if the TraceReference is colliding with an existing TraceJob’s
TraceReference, the IRPManager may decide to immediately deactivate the Trace Session in that
ManagedEntity.)
The TraceJob shall use its information to activate and configure Trace Session(s) in the requested ManagedEntity
instance(s). When the TraceIRP determines that there are available TraceRecord files, it shall emit a notification
to all subscribed IRPManagers informing the availability of the files. The method and the notification of the available
files is described in the File Transfer IRP (3GPP TS 32.342 [7]).
If a TraceJob receives an indication from one of its ManagedEntity that starting a Trace Recording Session is
failed for any reason, the "notifyTraceRecordingSessionFailure" notification may be emitted to inform
all subscribed IRPManagers that there was a Trace Recording Session that was not started in the ManagedEntity.
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 12 ETSI TS 132 442 V18.0.0 (2024-05)
5.3.1.2 Attributes
Support
Attribute name Qualifier
traceReference M
listOfInterfaces
O
listOfNeTypes
CM
traceDepth
CM
traceTarget
M
triggeringEvent CM
traceCollectionEntityAddress M
jobType
M
listOfMeasurements
CM
reportingTrigger
CM
reportInterval
CM
reportAmount
CM
eventThreshold CM
loggingInterval CM
loggingDuration
CM
areaScope
CM
anonymizationOfMDTData
CM
measurementPeriodLTE
CM
measurementPeriodUMTS
CM
collectionPeriodRrmUmts CM
collectionPeriodRrmLte
CM
positioningMethod
CM
measurementQuantity
CM
pLMNTarget
CM
mBSFNAreaList
CM
5.3.1.3 Attribute constraints
The listOfNeTypes attributes shall be present only for Signalling Based Activation.
The traceTarget shall be public ID in case of a Management Based Activation is done to an ScscfFunction.
The TraceTarget shall be cell only in case of the UTRAN cell traffic trace function.
The TraceTarget shall be E-UtranCell only in case of E-UTRAN cell traffic trace function.The
traceTarget shall be either IMSI or IMEI(SV) if the Trace Session is activated to any of the following
ManagedEntity(ies):
- HssFunction
- MscServerFunction
- SgsnFunction
- GgsnFunction
- BmscFunction
- RncFunction
- MmeFunction
The traceTarget shall be IMSI if the Trace Session is activated to a ManagedEntity playing a role of
ServinGWFunction.
In case of subscription based MDT, the traceTarget attribute shall be able to carry (IMSI or IMEI(SV)), the
areaScope attribute shall be able to carry a list of (cell or EUtranCell or TA/LA/RA).
In case of area based Immediate MDT, the traceTarget attribute shall be null value, the areaScope attribute
shall carry a list of (Utrancell or E-UtranCell).
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 13 ETSI TS 132 442 V18.0.0 (2024-05)
In case of area based Logged MDT, the traceTarget attribute shall carry an eNodeBs or a RNC. The Logged
MDT should be initiated on the specified eNodeB/RNC in TraceTarget. The areaScope attribute shall carry
a list of (Utrancell or E-UtranCell or TA/LA/RA).
In case of RLF reporting, or RCEF reporting, the traceTarget attribute shall be null value, the areaScope
attribute shall carry one or list of eNBs.
- traceTarget: This attribute shall be present if Trace or MDT RLF or RCEF reporting is supported.
- areaScope: This attribute shall be present if MDT is supported.
- triggeringEvent: This attribute shall be present only if Trace is supported.
- listOfMeasurements: This attribute shall be present only if MDT is supported and the JobType
attribute is set to ImmediateMDT.
- reportingTrigger: This attribute shall be present only if MDT is supported and the JobType attribute
is set to ImmediateMDT and the ListOfMeasurements attribute is configured for M1 (for both UMTS
and LTE) or M2 (only for UMTS).
- reportInterval: This attribute shall be present only if MDT is supported and the JobType attribute is
set to ImmediateMDT and the ReportingTrigger is configured for PeriodicMeasurements
- reportAmount: This attribute shall be present only if MDT is supported and the JobType attribute is set to
ImmediateMDT and the ReportingTrigger attribute is configured for PeriodicMeasurements.
- eventThreshold: This attribute shall be present only if MDT is supported and the JobType attribute is
set to ImmediateMDT and the ReportTrigger attribute is configured for A2EventReporting in
LTE or 1F/1IEventReporting in UMTS.
- loggingInterval: This attribute shall be present only if MDT is supported and the JobType attribute is
set to LoggedMDT or Logged MBSFN MDT.
- loggingDuration: This attribute shall be present only if MDT is supported
and the JobType attribute is set to LoggedMDT or Logged MBSFN MDT.
- anonymizationOfMDTData: This attribute shall be present only if MDT is supported and the
mdtAreaScope attribute is present.
- measurementPeriodLTE: This attribute shall be present only if MDT is supported and the JobType
attribute is set to Immediate MDT or combine Trace and Immediate MDT and the
listOfMeasurements parameter for LTE has either M4 or M5 measurement set.
- measurementPeriodUMTS: This attribute shall be present only if MDT is supported and the JobType
attribute is set to Immediate MDT or combine Trace and Immediate MDT and the
listOfMeasurements parameter for UMTS has M6 or M7 measurements set.
- collectionPeriodRrmUmts: This attribute shall be present only if MDT is supported and the JobType
attribute is set to Immediate MDT or combine Trace and Immediate MDT and the
listOfMeasurements parameter has any of M3, M4, M5 measurement set in case of UMTS.
- collectionPeriodRrmLte: This attribute shall be present only if MDT is supported and the JobType
attribute is set to Immediate MDT or combine Trace and Immediate MDT and the
listOfMeasurements parameter has any of M2, M3 measurement set in case of LTE.
- positioningMethod: This attribute shall be present only if MDT is supported and the JobType
attribute is set to Immediate MDT or combine Trace and Immediate MDT.
- measurementQuantity: This attribute shall be present only if MDT is supported and the JobType
attribute is set to Immediate MDT or combined Trace and Immediate MDT and the
reportingTrigger parameter is set to event 1F.
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 14 ETSI TS 132 442 V18.0.0 (2024-05)
- pLMNTarget: This attribute shall be present for management based activation when several PLMNs are
suppored in the RAN.
- mBSFNAreaList: This attribute shall be present only if Logged MBSFN MDT is supported and the
JobType attribute is set to Logged MBSFN MDT. This is applicable only for eUTRAN.
5.3.2 TraceRecord
5.3.2.1 Definition
TraceRecord is the representation of the files containing the logged information from the Trace Recording Sessions.
5.3.2.2 Attributes
Attribute name Visibility Support Qualifier Read Qualifier Write Qualifier
fileName + M M -
5.3.3 TraceIRP
5.3.3.1 Definition
TraceIRPis the representation of the trace management capabilities specified by the present document. This IOC
inherits from ManagedGenericIRP IOC specified in 3GPP TS 32.312 [8].
5.3.4 ManagedEntity
5.3.4.1 Definition
In case of Signalling Based Activation the ManagedEntity represents the role that can be played by an instance of
one of the following IOCs:
- HssFunction
- MscServerFunction
- SgsnFunction
- MmeFunction
In case of Management Based Activation the ManagedEntity represents the role that can be played by an instance of
the following IOCs:
- HssFunction
- MscServerFunction
- SgsnFunction
- GgsnFunction
- BmscFunction
- RncFunction
- CscfFunction
- MmeFunction
- ServingGWFunction
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 15 ETSI TS 132 442 V18.0.0 (2024-05)
In case of Cell Traffic Trace the ManagedEntity represents the role that can be played by an instance of the
following IOCs:
- UtranCell
- E-UtranCell
5.4 Information relationship definitions
5.4.1 relation-traceIRP-traceJob (M)
5.4.1.1 Definition
This represents the relationship between TraceIRP and the TraceJob.
5.4.1.2 Roles
Name Definition
theTraceIRP
It represents the TraceIRP
theTraceJobList
It represents the TraceJobList

5.4.2 relation-traceJob-managedEntity (M)
5.4.2.1 Definition
This represents the relationship between TraceJob and the ManagedEntity.
5.4.2.2 Roles
Name Definition
theManagedEntity
The ManagedEntity, when playing this role, represents the actual network resource instance,
where a Trace Session is activated.
theTraceJob
It represents the TraceJob
5.4.3 relation-traceJob-traceRecord (M)
5.4.3.1 Definition
This represents the relationship between TraceJob and the TraceRecord.
5.4.3.2 Roles
Name Definition
theTraceJob
It represents the TraceJob
theTraceRecord
It represnts the TraceRecord.
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 16 ETSI TS 132 442 V18.0.0 (2024-05)
5.5 Information attribute definitions
5.5.1 Definition and legal values
ETSI
3GPP TS 32.442 version 18.0.0 Release 18 17 ETSI TS 132 442 V18.0.0 (2024-05)
Attribute Name Definition Legal Values
anonymizationOfMDTData
It specifies the level of anonymization for an area See 3GPP TS 32.422 [9]
based MDT.
areaScope
It specifies MDT area scope when activates an List of cells/TA/LA/RA for
MDT job. subscription based MDT or
For RLF and RCEF reporting it specifies the eNB or area based Logged MDT.
list of eNBs where the RLF or RCEF reports should
List of cells for area
be collected.
based
Immediate MDT.
Cell, TA, LA, RA are
mutually
exclusive.
One or list of eNBs for RLF
and RCEFreporting
collectionPeriodRrmLte
It specifies the collection period for collecting RRM See 3GPP TS 32.422 [9]
configured measurement samples for M2, M3 in
LTE. The attribute is applicable only for Immediate
MDT. In case this attribute is not used, it carries a
null semantic.
collectionPeriodRrmUmts It specifies the collection period for collecting RRM See 3GPP TS 32.422 [9]
configured measurement samples for M3, M4, M5
in UMTS. The attribute is applicable only for
Immediate MDT. In case this attribute is not used, it
carries a null semantic.
eventThreshold It specifies the threshold which should trigger See 3GPP TS 32.422 [9] ,
the reporting in case A2 event reporting in 3GPP TS 25.331 [11] ,
LTE or 1F/1l event in UMTS. The attribute is 3GPP TS 36.331 [12]
applicable only for Immediate MDT and
when reportingTrigger is configured for A2
event in LTE or 1F event or 1l event in
UMTS. In case this attribute is not used, it
carries a null semantic.
jobType It specifies the MDT mode and it specifies also
See 3GPP TS 32.422 [9]
whether the TraceJob represents only MDT,
Logged MBSFN MDT, Trace or a combined Trace
and MDT job. The attribute is applicable for Trace,
MDT, RCEF and RLF reporting.
listOfInterfaces
It specifies the interfaces that need to be traced in See 3GPP TS 32.422 [9]
the given ManagedEntityFunction.The attribute
is applicable only for Trace. In case this attribute
is not used, it carries a null semantic.
listOfMeasurements It specifies the UE measurements that shall be See 3GPP TS 32.422 [9]
collected in an Immediate MDT job. The attribute is
applicable only for Immediate MDT. In case this
attribute is not used, it carries a null semantic.
listOfNETypes See 3GPP TS 32.422 [9]
It specifies in which type of ManagedFunction the
trace should be activated. The attribute is
applicable only for Trace with Signalling Based
Trace activation. In case this attribute is not used, it
carries a null semantic.
loggingDuration It specifies how long the MDT configuration is valid See 3GPP TS 32.422 [9]
at the UE in case of Logged MDT. The attribute is
applicable only for Logged MDT and Logged
MBSFN MDT. In case this attribute is not used, it
carries a null semantic.
loggingInterval It specifies the periodicty for Logged MDT. The See 3GPP TS 32.422 [9],
attribute is applicable only for Logged MDT and 3GPP TS 25.331 [11] , 3GPP
Logged MBSFN MDT. In case this attribute is not TS 36.331 [12]
used, it carries a null semantic.
measurementPeriodLTE It specifies the measurement period for the Data See 3GPP TS 32.422 [9]
Volume and Scheduled IP throughput
mea
...