1、 ETSI TS 132 347 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;File Transfer (FT) Integration Reference Point (IRP);SOAP Solution Set (SS)(3GPP TS 32.347 version 9.0.0 R
2、elease 9)ETSI ETSI TS 132 347 V9.0.0 (2010-01)13GPP TS 32.347 version 9.0.0 Release 9Reference RTS/TSGS-0532347v900 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 Associa
3、tion 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 per
4、ceived 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 servi
6、ces: 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
8、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 347 V9.0.0 (2010-01)23GPP TS 32.347 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentially
9、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 n
10、otified 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 (3
12、GPP). 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 f
13、ound under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 347 V9.0.0 (2010-01)33GPP TS 32.347 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2
14、Abbreviations . 6g34 Architectural features . 6g34.1 General . 6g35 Mapping . 7g35.1 Operation and notification mapping . 7g35.2 Operation parameter mapping 8g35.2.1 Operation listAvailableFiles . 8g35.2.1.1 Input parameters 8g35.2.1.2 Output parameters . 8g35.2.1.3 Fault definition 8g35.2.2 Operati
15、on fileDownloadIndication . 8g35.2.2.1 Input parameters 8g35.2.2.2 Output parameters . 9g35.2.2.3 Fault definition 9g3Annex A (normative): WSDL specifications 10g3Annex B (informative): Void . 13g3Annex C (informative): Change history . 14g3History 15g3ETSI ETSI TS 132 347 V9.0.0 (2010-01)43GPP TS 3
16、2.347 version 9.0.0 Release 9Foreword This Technical Specification (TS) 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 approval. Should the TSG modify the conten
17、ts 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 docu
18、ment 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 The present document is part of a TS-fa
19、mily covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below: 32.341: “File Transfer (FT) Integration Reference Point (IRP): Requirements“ 32.342: “File Transfer (FT) Integration Reference Point (IRP
20、): Information Service (IS)“ 32.343: “File Transfer (FT) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“ 32.345: “File Transfer (FT) Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“ 32.347: “File Transfer (FT) In
21、tegration Reference Point (IRP): SOAP Solution Set (SS)“ The present document is part of a TS-family which describe 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 1 and 3G
22、PP TS 32.102 2. Network Elements (NEs) under management, element managers as well as network managers generate various management information stored in file format. This IRP is addressing how these files are exchanged through Itf-N as well as certain aspects of file management and maintenance. It is
23、 anticipated that management functions (e.g. PM, Call Trace, CM) make reuse of capabilities provided by this File Transfer IRP. ETSI ETSI TS 132 347 V9.0.0 (2010-01)53GPP TS 32.347 version 9.0.0 Release 91 Scope The present document specifies the SOAP Solution Set for the IRP whose semantics are spe
24、cified in File Transfer IRP: Information Service (3GPP TS 32.342 4). This Solution Set specification is related to 3GPP TS 32.342 V9.0.X. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are eithe
25、r specific (identified by date of publication, edition number, version number, etc.) 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-sp
26、ecific 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.341: “ Technic
27、al Specification Group Services and System Aspects; Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Requirements “. 4 3GPP TS 32.342: “ Technical Specification Group Services and System Aspects; Telecommunication management; File Transfer (FT) Integration Referenc
28、e Point (IRP): Information Service (IS)“. 5 3GPP TS 32.345: “ Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 6 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requ
29、irements“. 7 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 8 3GPP TS 32.317: “Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP solution set“. 9 3GPP TS 32.150: “Telecommunication
30、 management; Integration Reference Point (IRP) Concept and definitions“. 10 3GPP TS 32.307: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): SOAP solution set“. 11 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 1
31、2 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 13 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 14 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) ETSI ETSI TS 132 347 V9.0.0 (2010-01)63GPP TS 32.347 version 9.0.0 Release 93 Defi
32、nitions 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 9 and 3GPP TS 32.341 3 and the following apply: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 6. 3.2 Ab
33、breviations For the purposes of the present document, the following abbreviations apply: IS Information Service SS Solution SetWSDL Web Service Description Language 4 Architectural features 4.1 General The overall architectural feature of the File Transfer (FT) IRP is specified in 3GPP TS 32.342 4.
34、This clause specifies features that are specific to the SOAP solution set. The SOAP 1.1 specification 11 and WSDL 1.1 specification 13 are supported. The SOAP 1.2 specification 14 is supported optionally. This specification uses “document“ style in WSDL file. This specification uses “literal“ encodi
35、ng style in WSDL file. The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification 12). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex. The FT IRP SOAP SS uses the Notification IRP SOAP SS of 3GPP TS 32.307 10. The IRPAgent shall su
36、pport the push interface model, which means that the IRPAgent sends FT notifications to the IRPManager as soon as new events occur. The IRPManager does not need to check (“pull“) for events. Relevant definitions are imported from the FT IRP XML definitions of 3GPP TS 32.345 5. This specification use
37、s a number of namespace prefixes throughout that are listed in Table 4.1. Table 4.1: Prefixes and Namespaces used in this specification PREFIX NAMESPACE (no prefix) http:/schemas.xmlsoap.org/wsdl/ soap http:/schemas.xmlsoap.org/wsdl/soap/fTIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.
38、347#FTIRPSystem fTIRPData http:/www.3gpp.org/ftp/Specs/archive/32_series/32.347#FTIRPData xfi http:/www.3gpp.org/ftp/specs/archive/32_series/32.345#fTIRPIOCs genericIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.317/schema/32317-810/GenericIRPSystem ntfIRPNtfSystem http:/www.3gpp.org/ft
39、p/Specs/archive/32_series/32.307/schema/32307-810/notification/NotificationIRPNtfSystem ETSI ETSI TS 132 347 V9.0.0 (2010-01)73GPP TS 32.347 version 9.0.0 Release 9The WSDL structure is depicted in Figure 4.1 below, depicting port type, binding and service. The port type contains port type operation
40、s, which again contains input, output and fault messages. The binding contains binding operations, which have the same name as the port type operations. The binding connects to a port inside the service. Figure 4.1: File Transfer IRP SOAP Solution Set WSDL structure 5 Mapping 5.1 Operation and notif
41、ication mapping The FT IRP IS (3GPP TS 32.342 4) defines the operations and their semantics. Table 5.1 maps the operations defined in the FT IRP IS to their equivalent port type and binding operations in this Solution Set (SS). Table 5.1 also maps the notifications of the FT IRP IS, as well as inher
42、ited operations. Table 5.1 also qualifies if an operation is Mandatory (M) or Optional (O). Table 5.1: Mapping from IS Operation to SS Equivalents IS Operation in 3GPP TS 32.342 4 SS: Operation for WSDL port type and WSDL binding SS: Port of FileTransferIRPService Qualifier listAvailableFiles listAv
43、ailableFiles (note 1) FileTransferIRPPort M fileDownloadIndication fileDownloadIndication (note 1) FileTransferIRPPort O notifyFileReady notify (note 2) NotificationIRPNtfPort M notifyFilePreparationError notify (note 2) NotificationIRPNtfPort M getIRPVersion (note 3) See TS 32.317 8 GenericIRPPort
44、M getOperationProfile (note 3) See TS 32.317 8 GenericIRPPort O getNotificationProfile (note 3) See TS 32.317 8 GenericIRPPort O NOTE 1: The operation is under the port type fTIRPSystem:FileTransferIRPPortType and under the binding fTIRPSystem:FileTransferIRPBinding. NOTE 2: The IS equivalent maps t
45、o an XML definition specified in 3GPP TS 32.345 5, 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 10. This binding is linked to a port of the FileTransferIRPSe
46、rvice as indicated in the table above. NOTE 3: The IS operation is inherited from the ManagedGenericIRP IOC specified in 3GPP TS 32.312 7. This inheritance is by the FileTransferIRP IOC of 3GPP TS 32.342 4 inheriting from the ManagedGenericIRP IOC. The corresponding binding is linked to a port of th
47、e FileTransferIRPService as indicated in the table above. ETSI ETSI TS 132 347 V9.0.0 (2010-01)83GPP TS 32.347 version 9.0.0 Release 95.2 Operation parameter mapping The FT IRP IS (3GPP TS 32.342 4) defines semantics of parameters carried in the operations. The tables below show the mapping of these
48、 parameters, as per operation, to their equivalents defined in this SS. 5.2.1 Operation listAvailableFiles 5.2.1.1 Input parameters Table 5.2.1.1: Mapping from IS listAvailableFiles input parameters to SS equivalents IS Operation parameter SS WSDL type sub-element used in corresponding input message
49、 under corresponding port type operation as indicated in Table 5.1 Qualifier managementDataType managementDataType M beginTime beginTime M endTime endTime M 5.2.1.2 Output parameters Table 5.2.1.2: Mapping from IS listAvailableFiles output parameters to SS equivalents IS Operation parameter SS WSDL type sub-element used in corresponding output message under corresponding port type operation as indicated in Table 5.1 Qualifier fileInfoList fileInfoList M status status M 5.2.1.3 Fault
