ETSI TS 132 443 V9.1.0 (2011-04)

Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Trace Management Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) (3GPP TS 32.443 version 9.1.0 Release 9)

RTS/TSGS-0532443v910

General Information

• Status: Published
• Publication Date: 26-Apr-2011
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Completion
• Due Date: 20-Apr-2011
• Completion Date: 27-Apr-2011

Standards Content (Sample)

Technical Specification
Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Trace Management Integration Reference Point (IRP): Common
Object Request Broker Architecture (CORBA) Solution Set (SS)
(3GPP TS 32.443 version 9.1.0 Release 9)

3GPP TS 32.443 version 9.1.0 Release 9 1 ETSI TS 132 443 V9.1.0 (2011-04)

Reference
RTS/TSGS-0532443v910
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 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
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
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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.

© European Telecommunications Standards Institute 2011.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
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 currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TS 32.443 version 9.1.0 Release 9 2 ETSI TS 132 443 V9.1.0 (2011-04)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, 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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI
3GPP TS 32.443 version 9.1.0 Release 9 3 ETSI TS 132 443 V9.1.0 (2011-04)
Contents
Intellectual Property Rights . 2
Foreword . 2
Foreword . 4
Introduction . 4
1 Scope . 5
2 References . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Architectural features . 6
4.1 Notifications . 6
4.2 Syntax for distinguished names and versions . 6
5 Mapping . 7
5.1 Operation and Notification mapping . 7
5.2 Operation parameter mapping . 7
5.3 Notification parameter mapping . 8
6 TraceIRPNotification Interface . 12
6.1 Method push (M) . 12
Annex A (normative): IDL specifications . . 13
A.1 IDL specification (file name "TraceIRPConstDefs.idl") . 13
A.2 IDL specification (file name 'TraceIRPSystem.idl') . 15
A.3 IDL specification (file name 'TraceIRPNotifications.idl'). 17
Annex B (informative): Change history . 19
History . 20

ETSI
3GPP TS 32.443 version 9.1.0 Release 9 4 ETSI TS 132 443 V9.1.0 (2011-04)
Foreword
rd
This Technical Specification (TS) 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 requirements and information model necessary for the
Telecommunication Management (TM) of 3G systems. The TM principles and TM architecture are specified in
3GPP TS 32.101 [2] and 3GPP TS 32.102 [3].
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.443 version 9.1.0 Release 9 5 ETSI TS 132 443 V9.1.0 (2011-04)
1 Scope
This Solution Set specification is related to 3GPP TS 32.442 [7].
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.441: "Telecommunication management; Trace Integration Reference Point (IRP):
Requirements".
[4] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP):
Requirements".
[5] 3GPP TS 32.303: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP): Common Object Request Broker Architecture
(CORBA) Solution Set (SS)".
[6] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[7] 3GPP TS 32.442: "Telecommunication management; Trace Management Integration Reference
Point (IRP): Information Service (IS)".
[8] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP)
management: Information Service (IS)".
[9] OMG TC Document telecom/98-11-01: "OMG Notification Service".
http://www.omg.org/technology/documents/
[10] 3GPP TS 32.421: "Telecommunication management; Subscriber and Equipment Trace; Concept
and requirements".
ETSI
3GPP TS 32.443 version 9.1.0 Release 9 6 ETSI TS 132 443 V9.1.0 (2011-04)
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.421 [10], 3GPP TS 32.441 [3] and the following apply:
IRP document version number string (or "IRPVersion"): See 3GPP TS 32.311 [4].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CM Configuration Management
CORBA Common Object Request Broker Architecture
DN Distinguished Name
EM Element Manager
IDL Interface Definition Language
IS Information Service
MOC Managed Object Class
NE Network Element
OMG Object Management Group
SS Solution Set
4 Architectural features
The overall architectural feature of TraceIRP is specified in 3GPP TS 32.441 [3].
This clause specifies features that are specific to the CORBA SS.
4.1 Notifications
Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.303 [5]).
The contents of the TraceIRP notifications are defined in the present document.
4.2 Syntax for distinguished names and versions
The format of a Distinguished Name is defined in 3GPP TS 32.300 [6].
The version of this IRP is represented as a string (see also clause 3 for versions).
ETSI
3GPP TS 32.443 version 9.1.0 Release 9 7 ETSI TS 132 443 V9.1.0 (2011-04)
5 Mapping
5.1 Operation and Notification mapping
TraceIRP: IS 3GPP TS 32.442 [7] defines semantics of operation and notification visible across the TraceIRP.
Table 5.1.1 indicates mapping of these operations and notifications to their equivalents defined in this SS.
Table 5.1.1: Mapping from IS Operations and Notification to SS equivalents
IS Operations/ notification 3GPP TS 32.442 [7] SS Method Qualifier
activateTraceJob activate_trace_job M
deactivateTraceJob deactivate_trace_job M
listTraceJob list_trace_job M
listActivatedTraceJob list_activated_trace_job M
notifyTraceRecordingSessionFailure push_structured_events(See subclause 6.1) O
notifyTraceSessionLocalActivation push_structured_events (See subclause 6.1) O

5.2 Operation parameter mapping
The TraceIRP: IS 3GPP TS 32.442 [7] defines semantics of parameters carried in operations across the TraceIRP. The
following tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS.
Table 5.2.1: Mapping from IS activateTraceJob parameters to SS equivalents
IS Operation parameter SS Method parameter Qualifier
iocInstance KernelCmConstDefs::DN moInstance M
listOfInterfaces TraceIRPConstDefs::ListOfInterfaces list_of_interfaces O
listOfNeTypes TraceIRPConstDefs::ListOfNeTypes list_of_ne_types CM
traceDepth TraceIRPConstDefs::TraceDepth trace_depth M
traceReference TraceIRPConstDefs::TraceReference trace_reference M
traceTarget TraceIRPConstDefs::TraceTarget trace_target M
triggeringEvent TraceIRPConstDefs:: TriggeringEvent triggering_event CO
traceCollectionEntityAddress TraceIRPConstDefs::TraceCollectionEntityAddress CM
trace_collection_entity_address
unsupportedList TraceIRPConstDefs:: UnsupportedList unsupportedList M
status Return value of type TraceIRPConstDefs::Result M
Exception:
ActivateTraceJob, InvalidTraceDepth, InvalidTraceTarget,
NotUniqueTraceReference
ManagedGenericIRPSystem::InvalidParameter,
ManagedGenericIRPSystem::ParameterNotSupported

Table 5.2.2: Mapping from IS deactivateTraceJob parameters to SS equivalents
IS Operation parameter SS Method parameter Qualifier
traceReference TraceIRPConstDefs:: TraceReference trace_reference M
traceTarget TraceIRPConstDefs::TraceTarget trace_target M
status Return value of type TraceIRPConstDefs::Result M
Exception:
DeactivateTraceJob, NotUniqueTraceReference
traceRecordingSessionReference TraceIRPConstDefs::TraceRecordingSessionReference CM
trace_recording_session_reference

ETSI
3GPP TS 32.443 version 9.1.0 Release 9 8 ETSI TS 132 443 V9.1.0 (2011-04)
Table 5.2.3: Mapping from IS listTraceJob parameters to SS equivalents
IS Operation parameter SS Method parameter Qualifier
traceReference TraceIRPConstDefs::TraceReference trace_reference M
status Return value of type TraceIRPConstDefs::Result M
Exception:
ListTraceJob, NotUniqueTraceReference
iocInstance KernelCmConstDefs::DN moInstance M
listOfInterfaces TraceIRPConstDefs::ListOfInterfaces list_of_interfaces O
traceDepth TraceIRPConstDefs::TraceDepth trace_depth M
traceRecordingSessionReference TraceIRPConstDefs::TraceRecordingSessionReference CM
trace_recording_session_reference
traceTarget TraceIRPConstDefs::TraceTarget trace_target M
triggeringEvent TraceIRPConstDefs::TriggeringEvent triggering_event O
traceCollectionEntityAddress TraceIRPConstDefs::TraceCollectionEntityAddress CM
trace_collection_entity_address

Table 5.2.4: Mapping from IS listActivatedTraceJobs parameters to SS equivalents
IS Operation parameter SS Method parameter Qualifier
traceReferenceList TraceMIRPConstDefs::TraceReferenceList trace_reference_list M
status Return value of type TraceIRPConstDefs::Result M

5.3 Notification parameter mapping
The TraceIRP: IS 3GPP TS 32.442 [7] defines semantics of parameters carried in notifications. The following table
indicates the mapping of these parameters to their OMG CORBA Structured Event (defined in OMG Notification
Service [9]) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service [9],
is:
Header
Fixed Header
domain_name
type_name
event_name
Variable Header
Body
filterable_body_fields
remaining_body
The following tables list all OMG Structured Event attributes in the second column. The first column identifies the
TraceIRP: IS 3GPP TS 32.442 [7] defined notification parameters.
ETSI
3GPP TS 32.443 version 9.1.0 Release 9 9 ETSI TS 132 443 V9.1.0 (2011-04)
Table 5.3.1: Mapping for notifyTraceRecordingSessionFailure
IS Parameters OMG CORBA Qualifier Comment
Structured Event
attribute
There is no corresponding IS domain_name M It carries the IRP document version number string. See
attribute. subclause 3.1.
It indicates the syntax and semantics of the Structured
Event as defined by the present document.
notificationType type_name M This is constant string
"notifyTraceRecordingSessionFailure".
There is no corresponding IS event_name M It carries no information.
attribute.
There is no corresponding IS Variable Header
attribute.
objectClass, objectInstance One NV pair of M NV stands for name-value pair. Order arrangement of NV
filterable_body_fields pairs is not significant. The name of NV-pair is always
encoded in string.
Name of this NV pair is the
MANAGED_OBJECT_INSTANCE of interface
AttributeNameValue of module NotificationIRPConstDefs.

Value of NV pair is a string. See corresponding table in
Notification IRP: CORBA SS (3GPP TS 32.303 [5]).
notificationId One NV pair of M Name of NV pair is the NOTIFICATION_ID of interface
remaining_body AttributeNameValue of module NotificationIRPConstDefs.

Value of NV pair is a long. See corresponding table in
Notification IRP: CORBA SS (3GPP TS 32.303 [5]).
eventTime One NV pair of M Name of NV pair is the EVENT_TIME of interface
filterable_body_fields AttributeNameValue of module NotificationIRPConstDefs.

Value of NV pair is IRPTime. See corresponding table in
Notification IRP: CORBA SS (3GPP TS 32.303 [5]).
systemDN One NV pair of M Name of NV pair is the SYSTEM_DN of interface
filterable_body_fields AttributeNameValue of module NotificationIRPConstDefs.

Value of NV pair is a string. See corresponding table in
Notification IRP: CORBA SS (3GPP TS 32.303 [5]).
traceRecordingSessionReference One NV pair of O Name of NV pair is the
remaining_body TRACE_RECORDING_SESSION_REFERENCE of
TraceIRPNotifications::notifyTraceRecordingSessionFailure.

Value of NV pair is TraceRecordingSessionReference of
module TraceIRPConstDefs.
traceReference One NV pair of M Name of NV pair is the TRACE_REFERENCE of
filterable_body_fields TraceIRPNotifications::notifyTraceRecordingSessionFailure.

Value of NV pair is TraceReference of module
TraceIRPConstDefs.
reason One NV pair of O Name of NV pair is the REASON of
remaining_body traceIRPNotifications:: notifyTraceRecordingSessionFailure.

Value of NV pair is a string.
ETS
...