ETSI TS 132 443-2011 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Trace Management Integ_1.pdf

1、 ETSI TS 132 443 V8.2.0 (2011-05)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)Soluti

2、on Set (SS) (3GPP TS 32.443 version 8.2.0 Release 8)ETSI ETSI TS 132 443 V8.2.0 (2011-05)13GPP TS 32.443 version 8.2.0 Release 8Reference RTS/TSGS-0532443v820 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 Si

3、ret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture 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

4、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 Secret

5、ariat. 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

6、 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 St

7、andards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. L

8、TE 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 ETSI TS 132 443 V8.2.0 (2011-05)23GPP TS 32.443 version 8.2.0 Release 8Intellectual Pro

9、perty 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);

10、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,

11、 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

12、 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 G

13、SM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 443 V8.2.0 (2011-05)33GPP TS 32.443 version 8.2.0 Release 8Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and

14、 abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Architectural features . 6g34.1 Notifications . 6g34.2 Syntax for distinguished names and versions . 6g35 Mapping . 7g35.1 Operation and Notification mapping 7g35.2 Operation parameter mapping 7g35.3 Notification parameter mapping . 8g3

15、6 TraceIRPNotification Interface 12g36.1 Method push (M) 12g3Annex A (normative): IDL specifications 13g3A.1 IDL specification (file name “TraceIRPConstDefs.idl“) 13g3A.2 IDL specification (file name TraceIRPSystem.idl) . 15g3A.3 IDL specification (file name TraceIRPNotifications.idl) 17g3Annex B (i

16、nformative): Change history 19g3History 20g3ETSI ETSI TS 132 443 V8.2.0 (2011-05)43GPP TS 32.443 version 8.2.0 Release 8Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work wi

17、thin 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

18、 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 h

19、ave been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.441 “Trace Management Integration Reference

20、 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 (

21、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

22、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 ETSI TS 132 443 V8.2.0 (2011

23、-05)53GPP TS 32.443 version 8.2.0 Release 81 Scope This Solution Set specification is related to 3GPP TS 32.442 V8.0.0. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identi

24、fied 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 referenc

25、e 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 manag

26、ement; 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): Co

27、mmon 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 S

28、ervice (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; Su

29、bscriber and Equipment Trace; Concept and requirements“. ETSI ETSI TS 132 443 V8.2.0 (2011-05)63GPP TS 32.443 version 8.2.0 Release 83 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 T

30、S 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 Architectur

31、e DN Distinguished Name EM Element ManagerIDL Interface Definition Language IS Information ServiceMOC 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 clau

32、se 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 fo

33、rmat 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 ETSI TS 132 443 V8.2.0 (2011-05)73GPP TS 32.443 version 8.2.0 Release 85 Mapping 5.1 Operation and Notification mapping TraceIRP: IS 3GPP TS 32.442 7

34、 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

35、.442 7 SS Method Qualifier activateTraceJob activate_trace_job MdeactivateTraceJob deactivate_trace_job MlistTraceJob list_trace_job MlistActivatedTraceJob list_activated_trace_job M notifyTraceRecordingSessionFailure push_structured_events(See subclause 6.1) OnotifyTraceSessionLocalActivation push_

36、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 S

37、S. Table 5.2.1: Mapping from IS activateTraceJob parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier iocInstance KernelCmConstDefs:DN moInstance MlistOfInterfaces TraceIRPConstDefs:ListOfInterfaces list_of_interfaces O listOfNeTypes TraceIRPConstDefs:ListOfNeTypes list_

38、of_ne_types CMtraceDepth TraceIRPConstDefs:TraceDepth trace_depth M traceReference TraceIRPConstDefs:TraceReference trace_reference MtraceTarget TraceIRPConstDefs:TraceTarget trace_target M triggeringEvent TraceIRPConstDefs: TriggeringEvent triggering_event CO traceCollectionEntityAddress TraceIRPCo

39、nstDefs:TraceCollectionEntityAddress trace_collection_entity_address CM unsupportedList TraceIRPConstDefs: UnsupportedList unsupportedList M status Return value of type TraceIRPConstDefs:Result Exception: ActivateTraceJob, InvalidTraceDepth, InvalidTraceTarget, NotUniqueTraceReference ManagedGeneric

40、IRPSystem:InvalidParameter, ManagedGenericIRPSystem:ParameterNotSupported M 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 TraceIRPConstDe

41、fs:TraceTarget trace_target Mstatus Return value of type TraceIRPConstDefs:Result Exception: DeactivateTraceJob, NotUniqueTraceReference M traceRecordingSessionReference TraceIRPConstDefs:TraceRecordingSessionReference trace_recording_session_reference CM ETSI ETSI TS 132 443 V8.2.0 (2011-05)83GPP T

42、S 32.443 version 8.2.0 Release 8Table 5.2.3: Mapping from IS listTraceJob parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier traceReference TraceIRPConstDefs:TraceReference trace_reference Mstatus Return value of type TraceIRPConstDefs:Result Exception: ListTraceJob, N

43、otUniqueTraceReference M iocInstance KernelCmConstDefs:DN moInstance M listOfInterfaces TraceIRPConstDefs:ListOfInterfaces list_of_interfaces OtraceDepth raceIRPConstDefs:TraceDepth trace_depth MtraceRecordingSessionReference TraceIRPConstDefs:TraceRecordingSessionReference trace_recording_session_r

44、eference CM traceTarget TraceIRPConstDefs:TraceTarget trace_target MtriggeringEvent TraceIRPConstDefs:TriggeringEvent triggering_event O traceCollectionEntityAddress TraceIRPConstDefs:TraceCollectionEntityAddress trace_collection_entity_address CM Table 5.2.4: Mapping from IS listActivatedTraceJobs

45、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 semant

46、ics 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 H

47、eader 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 ETSI TS 132 443 V8

48、.2.0 (2011-05)93GPP TS 32.443 version 8.2.0 Release 8Table 5.3.1: Mapping for notifyTraceRecordingSessionFailure IS Parameters OMG CORBA Structured Event attribute Qualifier Comment There is no corresponding IS attribute. domain_name M It carries the IRP document version number string. See subclause

49、 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 attribute. event_name M It carries no information. There is no corresponding IS attribute. Variable Header objectClass, objectInstance One NV pair of filterable_body_fields M NV stands for name-value pair. Order arrangement of NV pairs is not significant. The name