|
TECHNICAL SPECIFICATIONION
Digital cellular telecommmmunications system (Phase e 2+) (GSM);
Universal Mobile Telelecommunications System ( (UMTS);
LTE;
Telecommmunication management;
Trace Management nt Integration Reference Pointint (IRP);
Solutition o Set (SS) definitions
(3GPP TS 32.4.446 version 13.0.0 Release 13 13)
---------------------- Page: 1 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 1 ETSI TS 132 446 V13.0.0 (2016-03)
Reference
RTS/TSGS-0532446vd00
Keywords
GSM, LTE, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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
The present document can be downloaded from:
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 only prevailing document is the
print of the Portable Document Format (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:
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.
© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI 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
---------------------- Page: 2 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 2 ETSI TS 132 446 V13.0.0 (2016-03)
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 (https://ipr.etsi.org/).
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
.
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
---------------------- Page: 3 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 3 ETSI TS 132 446 V13.0.0 (2016-03)
Contents
Intellectual Property Rights . 2
Foreword . 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 . 8
4 Solution Set definitions . 8
Annex A (normative): CORBA Solution Set . . 9
A.1 Architectural features . 9
A.1.1 Syntax for Distinguished Names . 9
A.1.2 Notification Services . 9
A.1.3 Push and Pull Style . 9
A.1.4 Support multiple notifications in one push operation . 9
A.1.5 Trace Management Notification Interface . 9
A.1.5.1 Method push (M) . 9
A.2 Mapping . 10
A.2.1 Operation and Notification mapping . 10
A.2.2 Operation parameter mapping . 10
A.2.3 Notification parameter mapping . 12
A.3 Solution Set definitions . 18
A.3.1 IDL definition structure . 18
A.3.2 IDL specification (file name "TraceIRPConstDefs.idl") . 19
A.3.3 IDL specification (file name 'TraceIRPSystem.idl') . 23
A.3.4 IDL specification (file name 'TraceIRPNotifications.idl') . 25
Annex B (normative): XML definitions . 27
B.1 Architectural Features . 27
B.1.1 Syntax for Distinguished Names . 27
B.1.2 Notification Services . 27
B.1.3 IOC definitions . 27
B.2 Mapping . 27
B.3 Solution Set definitions . 27
B.3.1 XML definition structure . 27
B.3.2 Graphical Representation . 28
B.3.3 XML Schema 'tMIRPNotif.xsd' . 30
B.3.4 XML Schema 'tMIRPIOCs.xsd' . 32
Annex C (normative): SOAP Solution Set . 37
C.1 Architectural features . 37
C.1.1 Syntax for Distinguished Names . 37
C.1.2 Notification Services . 37
C.1.3 Supported W3C specifications . 37
C.1.4 Prefixes and namespaces . 37
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 4 ETSI TS 132 446 V13.0.0 (2016-03)
C.2 Mapping . 38
C.2.1 Operation and notification mapping . 38
C.2.2 Operation parameter mapping . 38
C.2.3 Notification parameter mapping . 40
C.3 Solution Set definitions . 41
C.3.1 WSDL definition structure . 41
C.3.2 Graphical Representation . 41
C.3.3 WSDL specification 'TraceIRPSystem.wsdl' . 42
Annex D (informative): Change history . 48
History . 49
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 5 ETSI TS 132 446 V13.0.0 (2016-03)
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.446 "Trace Management Integration Reference Point (IRP): Solution Set (SS) definitions".
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 [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
---------------------- Page: 6 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 6 ETSI TS 132 446 V13.0.0 (2016-03)
1 Scope
The present document specifies the Solution Set definitions for the IRP whose semantics are specified in Trace
Management IRP: Information Service (3GPP TS 32.442 [5]). 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 [6].
This Solution Set specification is related to 3GPP TS 32.442 V12. 0.X.
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 TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[3] 3GPP TS 32.102: "Telecommunication management; Architecture".
[4] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept
and definitions".
[5] 3GPP TS 32.442: "Telecommunication management; Trace Management Integration Reference
Point (IRP): Information Service (IS)".
[6] void.
[7] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP):
Requirements".
[8] void.
[9] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[10] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP): Solution Set definitions"
[11] void.
[12] OMG TC Document telecom/98-11-01: "OMG Notification Service".
http://www.omg.org/technology/documents/
[13] 3GPP TS 32.342: "Telecommunication management; File Transfer (FT) Integration Reference
Point (IRP): Information Service (IS)".
[14] W3C REC-xml-20001006: "Extensible Markup Language (XML) 1.0 (Second Edition)".
[15] W3C REC-xmlschema-0-20010502: "XML Schema Part 0: Primer".
[16] W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 7 ETSI TS 132 446 V13.0.0 (2016-03)
[17] W3C REC-xmlschema-2-20010502: "XML Schema Part 2: Datatypes".
[18] void.
[19] void.
[20] void.
[21] W3C SOAP 1.1 specification (http://www.w3.org/TR/2000/NOTE-SOAP-20000508/)
[22] W3C XPath 1.0 specification (http://www.w3.org/TR/1999/REC-xpath-19991116)
[23] W3C WSDL 1.1 specification (http://www.w3.org/TR/2001/NOTE-wsdl-20010315)
[24] W3C SOAP 1.2 specification (http://www.w3.org/TR/soap12-part1/)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1], 3GPP TS 32.101 [2],
3GPP TS 32.102 [3], 3GPP TS 32.150 [4] apply. A term defined in the present document takes precedence over the
definition of the same term, if any, in TR 21.905 [1].
IRP document version number string (or "IRPVersion"): See 3GPP TS 32.311 [7].
IRP: See 3GPP TS 32.101 [2].
IRPAgent: See 3GPP TS 32.102 [3].
IRPManager: See 3GPP TS 32.102 [3].
XML file: file containing an XML document
XML document: composed of the succession of an optional XML declaration followed by a root XML element, see
[14].
XML declaration: it specifies the version of XML being used, see [14].
XML element: has a type, is identified by a name, may have a set of XML attribute specifications and is either
composed of the succession of an XML start-tag followed by the XML content of the XML element followed by an
XML end-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML
elements, see [14].
empty XML element: having an empty XML content; an empty XML element still possibly has a set of XML attribute
specifications; an empty XML element is either composed of the succession of an XML start-tag directly followed by
an XML end-tag, or composed simply of an XML empty-element tag, see [14].
XML content (of an XML element): empty if the XML element is simply composed of an XML empty-element tag;
otherwise the part, possibly empty, of the XML element between its XML start-tag and its XML end-tag, see [14].
XML start-tag: the beginning of a non-empty XML element is marked by an XML start-tag containing the name and
the set of XML attribute specifications of the XML element, see [14].
XML end-tag: the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML
element, see [14].
XML empty-element tag: composed simply of an empty-element tag containing the name and the set of XML attribute
specifications of the XML element, see [14].
XML attribute specification: has a name and a value, see [14].
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 8 ETSI TS 132 446 V13.0.0 (2016-03)
DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this
DTD, see [14].
XML schema: more powerful than a DTD, an XML schema defines structure and content constraints to be respected
by an XML document to conform with this XML schema; through the use of XML namespaces several XML schemas
can be used together by a single XML document; an XML schema is itself also an XML document that shall conform
with the XML schema for XML schemas, see [15], [16] and [17].
XML namespace: enables qualifying element and attribute names used in XML documents by associating them with
namespaces identified by different XML schemas, see [15], [16] and [17].
XML complex type: defined in an XML schema; cannot be directly used in an XML document; can be the concrete
type or the derivation base type for an XML element type or for another XML complex type; ultimately defines
constraints for an XML element on its XML attribute specifications and/or its XML content, see [15], [16] and [17].
XML element type: declared by an XML schema; can be directly used in an XML document; as the concrete type of
an XML element, directly or indirectly defines constraints on its XML attribute specifications and/or its XML content;
can also be the concrete type or the derivation base type for another XML element type, see [15], [16] and [17].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1], in 3GPP TS 32.101 [2],
3GPP TS 32.102 [3], 3GPP TS 32.150 [4], 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].
CM Configuration Management
CORBA Common Object Request Broker Architecture
DN Distinguished Name
EM Element Manager
IDL Interface Definition Language
IRP Integration Reference Point
Itf-N Interface N
IS Information Service
MDT Minimization of Drive Tests
MOC Managed Object Class
NE Network Element
OMG Object Management Group
RLF Radio Link Failure
SS Solution Set
TS Technical Specification
4 Solution Set definitions
This specification defines the following 3GPP Trace Management IRP Solution Set definitions:
Annex A provides the CORBA Solution Set.
Annex B provides the XML definitions.
Annex C provides the SOAP Solution Set.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 9 ETSI TS 132 446 V13.0.0 (2016-03)
Annex A (normative):
CORBA Solution Set
This annex contains the CORBA Solution Set for the IRP whose semantics is specified in Trace Management IRP:
Information Service (3GPP TS 32.442 [5]).
A.1 Architectural features
The overall architectural feature of Trace Management IRP is specified in 3GPP TS 32.442 [5].
A.1.1 Syntax for Distinguished Names
The format of a Distinguished Name is defined in 3GPP TS 32.300 [9].
The version of this IRP is represented as a string (see also clause 3 for versions).
A.1.2 Notification Services
Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.306 [10]).
The contents of the TraceIRP notifications are defined in the present document.
A.1.3 Push and Pull Style
OMG Notification Service defines two styles of interaction. One is called push style. In this style, IRPAgent pushes
notifications to IRPManager as soon as they are available. The other is called pull style. In this style, IRPAgent keeps
the notifications till IRPManager requests for them.
This CORBA SS specifies that support of Push style is Mandatory (M) and that support of Pull style is Optional (O).
A.1.4 Support multiple notifications in one push operation
For efficiency reasons, IRPAgent may send multiple notifications using one single push operation. To pack multiple
notifications into one push operation, IRPAgent may wait and not invoke the push operation as soon as notifications are
available. To avoid IRPAgent to wait for an extended period of time that is objectionable to IRPManager, IRPAgent
shall implement an IRPAgent wide timer configurable by administrator. On expiration of this timer, IRPAgent shall
invoke push if there is at least one notification to be conveyed to IRPManager. This timer is re-started after each push
invocation.
A.1.5 Trace Management Notification Interface
OMG CORBA Notification push operation is used to realise the notification of TraceIRP Notifications. All
the notifications in this interface are implemented using this push_structured_event method.
A.1.5.1 Method push (M)
module CosNotifyComm {
…
Interface SequencePushConsumer : NotifyPublish {
void push_structured_events(
in CosNotification::EventBatch notifications)
raises( CosEventComm::Disconnected);
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 10 ETSI TS 132 446 V13.0.0 (2016-03)
…
}; // SequencePushConsumer
…
}; // CosNotifyComm
NOTE 1: The push_structured_events method takes an input parameter of type EventBatch as defined in the OMG
CosNotification module (OMG Notification Service [12]). This data type is the same as a sequence of
Structured Events. Upon invocation, this parameter will contain a sequence of Structured Events being
delivered to IRPManager by IRPAgent to which it is connected.
NOTE 2: The maximum number of events that will be transmitted within a single invocation of this operation is
controlled by IRPAgent wide configuration parameter.
NOTE 3: The amount of time the supplier (IRPAgent) of a sequence of Structured Events will accumulate
individual events into the sequence before invoking this operation is controlled by IRPAgent wide
configuration parameter as well.
NOTE 4: IRPAgent may push EventBatch with only one Structured Event.
A.2 Mapping
A.2.1 Operation and Notification mapping
TraceIRP: IS 3GPP TS 32.442 [5] defines semantics of operation and notification visible across the TraceIRP.
Table A.2.1 indicates mapping of these operations and notifications to their equivalents defined in this SS.
Table A.2.1: Mapping from IS Operations and Notification to SS equivalents
IS Operations/ notification 3GPP TS 32.442 [5] 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 A.1.5.1) O
notifyTraceSessionLocalActivation push_structured_events (See subclause A.1.5.1) O
A.2.2 Operation parameter mapping
The TraceIRP: IS 3GPP TS 32.442 [5] 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.
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 32.446 version 13.0.0 Release 13 11 ETSI TS 132 446 V13.0.0 (2016-03)
Table A.2.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
jobType TraceIRPConstDefs:: JobType job_type M
areaScope TraceIRPConstDefs::DNSet CM
listOfMeasurements TraceIRPConstDefs:: ListOf Measurements list_of_measurements CM
reportingTrigger TraceIRPConstDefs::ReportingTrigger reporting_trigger CM
reportInterval TraceIRPConstDefs::ReportInterval report_interval CM
reportAmount TraceIRPConstDefs::ReportAmount report_amount CM
eventThreshold TraceIRPConstDefs::EventThreshold event_threshold CM
loggingInterval TraceIRPConstDefs::LoggingInterval logging_interval CM
loggingDuration TraceIRPConstDefs::LoggingDuration logging_duration CM
anonymizationOfMDTData TraceIRPConstDefs: AnonymizationOfMDTData anonymization_Of_MDT_Data CM
measurementQuantity TraceIRPConstDefs::MeasurementQuantity measurement_quantity CM
measurementPeirodLTE TraceIRPConstDefs: MeasurementPeriodLTE measurement_period_lte CM
measurementPeirodUMTS TraceIRPConstDefs: MeasurementPeriodUMTS measurement_period_ umts CM
collectionPeriodRrmUmts TraceIRPConstDefs: CollectionPeriodRrmUmts collection_period_rrm_umts CM
collectionPeriodRrmLte TraceIRPConstDefs: CollectionPeriodRrmLte collection_period_rrm_lte CM
positioningMethod TraceIRPConstDefs: PositioningMethod positioning_method CO
unsupportedList TraceIRPConstDefs: UnsupportedList unsupportedList M
status Return value of type TraceIRPConstDefs::Result M
Exception:
ActivateTraceJob, InvalidTraceDepth, InvalidTraceTarget,
NotUniqueTr
...