1、 ETSI TS 132 346 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Solution Set (SS) definitions (3GPP TS 32.346 version 15.0.0 Rel
2、ease 15) TECHNICAL SPECIFICATION ETSI ETSI TS 132 346 V15.0.0 (2018-07)13GPP TS 32.346 version 15.0.0 Release 15Reference RTS/TSGS-0532346vf00 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
3、00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any
4、 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 Forma
5、t (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 https:/portal.etsi.org/TB/ETSID
6、eliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, inc
7、luding 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. ETSI 2018. All rights reserved. DECTT
8、M, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM
9、logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 132 346 V15.0.0 (2018-07)23GPP TS 32.346 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The informa
10、tion 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 ET
11、SI 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 u
12、pdates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated a
13、s being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Speci
14、fication (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 deliverab
15、les. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. 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 interpret
16、ed 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 ETSI TS 132 346 V15.0.0 (2018-07)33GPP TS 32.346 version 15.0.0 Release 15Contents Intellectu
17、al Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Solution Set Definitions . 7g3Annex A (normative): CORBA Solution Set . 8g3A.1 Architectural featur
18、es . 8g3A.1.1 Syntax for Distinguished Names 8g3A.1.2 Notification Services 8g3A.1.3 Push and Pull Style . 8g3A.1.4 Support multiple notifications in one push operation . 8g3A.1.5 FileTransferIRP Notification Interface . 8g3A.1.5.1 Method push (M) 8g3A.2 Mapping . 10g3A.2.1 Operation and Notificatio
19、n mapping 10g3A.2.2 Operation parameter mapping 10g3A.2.3 Notification parameter mapping . 11g3A.3 Solution Set definitions 13g3A.3.1 IDL definition structure 13g3A.3.2 IDL specification “FileTransferIRPConstDefs.idl“ 14g3A.3.3 IDL specification “FileTransferIRPSystem.idl“ . 15g3A.3.4 IDL specificat
20、ion “FileTransferIRPNotifications.idl“ 17g3Annex B (normative): XML Definitions . 19g3B.1 Architectural Features 19g3B.1.1 Syntax for Distinguished Names 19g3B.1.2 Notification Services 19g3B.1.3 IOC Definitions 19g3B.2 Mapping . 19g3B.3 Solution Set definitions 19g3B.3.1 XML definition structure 19
21、g3B.3.2 Graphical Representation . 20g3B.3.3 XML Schema “fTIRPNotif.xsd” 21g3B.3.4 XML Schema “fTIRPIOCs.xsd” 22g3Annex C (normative): SOAP Solution Set . 23g3C.1 Architectural features . 23g3C.1.1 Syntax for Distinguished Names 23g3C.1.2 Notification Services 23g3C.1.3 Supported W3C specifications
22、. 23g3C.1.4 Prefixes and namespaces 23g3C.2 Mapping . 24g3ETSI ETSI TS 132 346 V15.0.0 (2018-07)43GPP TS 32.346 version 15.0.0 Release 15C.2.1 Operation and notification mapping . 24g3C.2.2 Operation parameter mapping 24g3C.2.2.1 Operation listAvailableFiles 24g3C.2.2.1.1 Input parameters 24g3C.2.2.
23、1.2 Output parameters . 25g3C.2.2.1.3 Fault definition 25g3C.2.2.2 Operation fileDownloadIndication . 25g3C.2.2.2.1 Input parameters 25g3C.2.2.2.2 Output parameters . 25g3C.2.2.2.3 Fault definition 25g3C.3 Solution Set definitions 26g3C.3.1 WSDL definition structure . 26g3C.3.2 Graphical Representat
24、ion . 26g3C.3.3 WSDL specification “FTRPSystem.wsdl” . 27g3Annex D (informative): Change history . 30g3History 31g3ETSI ETSI TS 132 346 V15.0.0 (2018-07)53GPP TS 32.346 version 15.0.0 Release 15Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GP
25、P). 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 num
26、ber 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, up
27、dates, 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-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication manag
28、ement, as identified below: 32.341: “File Transfer (FT) Integration Reference Point (IRP): Requirements“ 32.342: “File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“ 32.346: “File Transfer (FT) Integration Reference Point (IRP): Solution Set (SS) definitions“ The present
29、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 3GPP TS 32.102 2. Network Elements (NEs) under management, element mana
30、gers 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 anticipated that management functions (e.g. PM, Call Trace, CM) make
31、 reuse of capabilities provided by this File Transfer IRP. ETSI ETSI TS 132 346 V15.0.0 (2018-07)63GPP TS 32.346 version 15.0.0 Release 151 Scope The present document contains the Solution Sets for the IRP whose semantics are specified in File Transfer IRP: Information Service (3GPP TS 32.342 15). T
32、his Solution Set specification is related to 3GPP TS 32.342 V14.0.X 15. 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, v
33、ersion 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-specific reference implicitly refers to the latest version of
34、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: “Telecommunication management; File Transfer (FT) Integration Referen
35、ce Point (IRP): Requirements “. 4 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements“. 5 3GPP TS 32.306: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) defi
36、nitions“. 6 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 7 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 8 3GPP TS 32.316: “Telecommunication manag
37、ement; Generic Integration Reference Point (IRP) management; Solution Set (SS) definitions“. 9 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 10 OMG TC Document telecom/98-11-01: “OMG Notification Service“. http:/www.omg.org/technology/docu
38、ments/ 11 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 12 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
39、/) 15 3GPP TS 32.342: “Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“. 16 3GPP TS 32.336: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Solution Set (SS) definitions“. ETSI ETSI TS 132 346 V15.0.
40、0 (2018-07)73GPP TS 32.346 version 15.0.0 Release 1517 3GPP TS 32.331: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3
41、GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.150 9, 3GPP TS 32.331 17 and 3GPP TS 32.341 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 Configura
42、tion Management CORBA Common Object Request Broker Architecture DN Distinguished Name FT File TransferFTIRP File Transfer IRP IDL Interface Definition Language IRP Integration Reference Point IS Information Service NE Network ElementNL Notification LogNRM Network Resource Model OMG Object Management
43、 Group PM Performance ManagementSS Solution SetUML Unified Modelling Language WSDL Web Service Description Language XML eXtensible Markup Language 4 Solution Set Definitions This specification defines the following 3GPP FT IRP Solution Set Definitions: Annex A provides the CORBA Solution Set. Annex
44、B provides the XML Definitions. Annex C provides the SOAP Solution Set. ETSI ETSI TS 132 346 V15.0.0 (2018-07)83GPP TS 32.346 version 15.0.0 Release 15Annex A (normative): CORBA Solution Set This annex contains the CORBA Solution Set for the IRP whose semantics is specified in FT IRP: Information Se
45、rvice (3GPP TS 32.342 15). A.1 Architectural features The overall architectural feature of FT IRP is specified in 3GPP TS 32.341 3. This clause specifies features that are specific to the CORBA SS. A.1.1 Syntax for Distinguished Names The syntax of a Distinguished Name is defined in 3GPP TS 32.300 6
46、. A.1.2 Notification Services In implementations of CORBA SS, IRPAgent conveys FT Information to IRPManager via OMG Notification Service (OMG Notification Service 10). A necessary and sufficient sub set of OMG Notification Services shall be used to support FileTransferIRPNotifications notifications
47、as specified in 3GPP TS 32.342 15. 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 t
48、he 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 on
49、e 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 inv
