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

1、 ETSI TS 132 447 V9.0.0 (2010-04)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Trace Management Integration Reference Point (IRP):SOAP Solution Set (SS) (3GPP TS 32.447 version 9.0.0 Re

2、lease 9)ETSI ETSI TS 132 447 V9.0.0 (2010-04)13GPP TS 32.447 version 9.0.0 Release 9Reference DTS/TSGS-0532447v900 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 Associat

3、ion 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 or in print. In any case of existing or perc

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

5、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 servic

6、es: 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 2010. All rights reserved.

7、 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. LTE is a Trade Mark of ETSI currently being r

8、egistered 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 447 V9.0.0 (2010-04)23GPP TS 32.447 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentially e

9、ssential 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 no

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

11、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 (3G

12、PP). 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 fo

13、und under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 447 V9.0.0 (2010-04)33GPP TS 32.447 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 A

14、bbreviations . 6g34 Architectural features . 6g34.1 General . 6g35 Mapping . 7g35.1 Operation and notification mapping . 7g35.2 Operation parameter mapping 7g35.3 Notification parameter mapping . 8g3Annex A (normative): WSDL specifications 9g3Annex B (informative): Change history . 14g3History 15g3E

15、TSI ETSI TS 132 447 V9.0.0 (2010-04)43GPP TS 32.447 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG a

16、pproval. 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;

17、 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. Introductio

18、n 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 Point (IRP): Requirements“. 32.442 “Trace Managem

19、ent 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

20、 definition“. 32.447 “Trace Management Integration Reference Point (IRP): SOAP Solution Set (SS)“. 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 specifie

21、d 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 ETSI TS

22、132 447 V9.0.0 (2010-04)53GPP TS 32.447 version 9.0.0 Release 91 Scope The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Trace Management IRP: Information Service (3GPP TS 32.442 5). This Solution Set specification is related to 3GPP TS 32.442 V9.0.X.

23、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, subseq

24、uent 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

25、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 defin

26、itions“. 5 3GPP TS 32.442: “Telecommunication management; Trace Management Integration Reference Point (IRP): Information Service (IS)“. 6 3GPP TS 32.445: “ Trace Management Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition“. 7 W3C SOAP 1.1 specification (htt

27、p:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 8 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 9 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 10 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 11 3GPP TS 32.307: “Telecommunication ma

28、nagement; Configuration Management (CM); Notification Integration Reference Point (IRP): SOAP solution set“. 12 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“ 3 Definitions and abbreviations 3.1 Definitions For the purpo

29、ses 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. ETSI ETSI TS 132 447 V9.0.0 (2010-04)63GPP TS

30、 32.447 version 9.0.0 Release 93.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

31、 the same abbreviation, if any, in TR 21.905 1. 4 Architectural features 4.1 General The overall architectural feature of the Trace Management IRP is specified in 3GPP TS 32.442 4. This clause specifies features that are specific to the SOAP solution set. The SOAP 1.1 specification 7 and WSDL 1.1 sp

32、ecification 9 are supported. The SOAP 1.2 specification 10 is supported optionally. This specification uses “document“ style in WSDL file. This specification uses “literal“ encoding style in WSDL file. The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification 8). IRPA

33、gents may throw a FilterComplexityLimit fault when a given filter is too complex. The Trace Management IRP SOAP SS uses the Notification IRP SOAP SS of 3GPP TS 32.307 11. The IRPAgent shall support the push interface model, which means that the IRPAgent sends trace management notifications to the IR

34、PManager as soon as new events occur. The IRPManager does not need to check (“pull“) for events. Relevant definitions are imported from the Trace Management IRP XML definitions of 3GPP TS 32.445 6. This specification uses a number of namespace prefixes throughout that are listed in Table 4.1. 1. Tab

35、le 4.1.1: Prefixes and Namespaces used in this specification PREFIX NAMESPACE (no prefix) http:/schemas.xmlsoap.org/wsdl/ soap http:/schemas.xmlsoap.org/wsdl/soap/traceRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.447#TraceIRPSystem traceIRPData http:/www.3gpp.org/ftp/Specs/archive/32_s

36、eries/32.447#TraceIRPData xti http:/www.3gpp.org/ftp/specs/archive/32_series/32.445#tMIRPIOCs xn http:/www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrmgenericIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.317/schema/32317-810/GenericIRPSystem ntfIRPNtfSystem http:/www.3gpp.org

37、/ftp/Specs/archive/32_series/32.307/schema/32307-810/ notification/NotificationIRPNtfSystem The WSDL structure is depicted in Figure 4.1.1 below, depicting port type, binding and service. The port type contains port type operations, which again contains input, output and fault messages. The binding

38、contains binding operations, which have the same name as the port type operations. The binding connects to a port inside the service. ETSI ETSI TS 132 447 V9.0.0 (2010-04)73GPP TS 32.447 version 9.0.0 Release 9TraceIRPService NotificationIRPNtfPort GenericIRPPort TraceIRPManagementPort Port Types Bi

39、ndings Services GenericIRPBinding (from 32.317) NotificationIRPNtf (from 32.307) TraceIRPManagement activateTraceJob deactivateTraceJob listTraceJob listActivatedTraceJobs TraceIRPManagement activateTraceJob deactivateTraceJob listTraceJob listActivatedTraceJobs Figure 4.1.1: Trace Management IRP SO

40、AP Solution Set WSDL structure 5 Mapping 5.1 Operation and notification mapping The Trace Management IRP IS (3GPP TS 32.442 5) defines semantics of operation and notification visible across the Itf-N. Table 5.1.1 indicates mapping of these operations and notifications to their equivalents defined in

41、 this SS. Table 5.1.1: Mapping from IS Operation to SS Equivalents IS Operations in 3GPP TS 32.442 5 SS Operations SS Port Qualifier activateTraceJob activateTraceJob TraceIRPManagementPort MdeactivateTraceJob deactivateTraceJob TraceIRPManagementPort MlistTraceJob listTraceJob TraceIRPManagementPor

42、t MlistActivatedTraceJobs listActivatedTraceJobs TraceIRPManagementPort O notifyTraceRecordingSessionFailure notify (note 1) NotificationIRPNtfPort OnotifyTraceSessionLocalActivation notify (note 1) NotificationIRPNtfPort M NOTE 1: The IS equivalent maps to an XML definition specified in 3GPP TS 32.

43、445 6, and this being an input parameter to the operation notify under the port type ntfIRPNtfSystem:NotificationIRPNtf and under the binding ntfIRPNtfSystem:NotificationIRPNtf of 3GPP TS 32.307 11. 5.2 Operation parameter mapping The Trace Management IRP IS (3GPP TS 32.442 5) defines semantics of p

44、arameters carried in the operations. The tables below show 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 iOCInstan

45、ce MlistOfInterfaces listOfInterfaces O listOfNeTypes listOfNeTypes CMtraceDepth traceDepth MtraceReference traceReference M traceTarget traceTarget MtriggeringEvent triggeringEvent CO traceCollectionEntityAddress traceCollectionEntityAddress CM unsupportedList unsupportedList Mstatus status METSI E

46、TSI TS 132 447 V9.0.0 (2010-04)83GPP TS 32.447 version 9.0.0 Release 9Table 5.2.2: Mapping from IS deactivateTraceJob parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier traceReference traceReference MtraceTarget traceTarget MtraceRecordingSessionReference traceRecordin

47、gSessionReference CM status status MTable 5.2.3: Mapping from IS listTraceJob parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier traceReference traceReference MiOCInstance iOCInstance MlistOfInterfaces listOfInterfaces O traceDepth traceDepth MtraceRecordingSessionRefe

48、rence traceRecordingSessionReference CM traceTarget traceTarget MtriggeringEvent triggeringEvent OtraceCollectionEntityAddress traceCollectionEntityAddress CM status status MTable 5.2.4: Mapping from IS listTraceJobs parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier t

49、raceReferenceList traceReferenceList M status status M5.3 Notification parameter mapping The Trace Management IRP IS (3GPP TS 32.442 5) defines semantics of parameters carried in notifications. The following tables indicate the mapping of these parameters to their SS equivalents. Table 5.3.1: Mapping for notifyTraceRecordingSessionFailure IS Parameters Parameters Qualifier Comment objectClass objectClass MobjectInstance objectInstance M eventTime eventTime M notificationType notificationTy