ETSI TS 132 346-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management File Transfer (FT) Int.pdf

1、 ETSI TS 132 346 V13.0.0 (2016-02) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Solution Set (SS) definitions (3GPP TS 32.346 version 13.0.0 Release 1

2、3) TECHNICAL SPECIFICATION ETSI ETSI TS 132 346 V13.0.0 (2016-02) 1 3GPP TS 32.346 version 13.0.0 Release 13 Reference RTS/TSGS-0532346vd00 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 000

3、17 - 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 el

4、ectronic 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 (

5、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/st

6、atus.asp 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, including photoc

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

8、16. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE a re 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 re

9、gistered and owned by the GSM Association. ETSI ETSI TS 132 346 V13.0.0 (2016-02) 2 3GPP TS 32.346 version 13.0.0 Release 13 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

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

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

12、e, 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 id

13、entities. 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“

14、, “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

15、ETSI TS 132 346 V13.0.0 (2016-02) 3 3GPP TS 32.346 version 13.0.0 Release 13 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 . 7 4 Solution Se

16、t Definitions . 7 Annex A (normative): CORBA Solution Set . 8 A.1 Architectural features . 8 A.1.1 Syntax for Distinguished Names . 8 A.1.2 Notification Services 8 A.1.3 Push and Pull Style 8 A.1.4 Support multiple notifications in one push operation 8 A.1.5 FileTransferIRP Notification Interface 8

17、A.1.5.1 Method push (M) 8 A.2 Mapping . 9 A.2.1 Operation and Notification mapping . 9 A.2.2 Operation parameter mapping 9 A.2.3 Notification parameter mapping 10 A.3 Solution Set definitions 12 A.3.1 IDL definition structure . 12 A.3.2 IDL specification “FileTransferIRPConstDefs.idl“ . 13 A.3.3 IDL

18、 specification “FileTransferIRPSystem.idl“ 14 A.3.4 IDL specification “FileTransferIRPNotifications.idl“ . 15 Annex B (normative): XML Definitions 17 B.1 Architectural Features 17 B.1.1 Syntax for Distinguished Names . 17 B.1.2 Notification Services 17 B.1.3 IOC Definitions . 17 B.2 Mapping . 17 B.3

19、 Solution Set definitions 17 B.3.1 XML definition structure . 17 B.3.2 Graphical Representation . 18 B.3.3 XML Schema fTIRPNotif.xsd 18 B.3.4 XML Schema fTIRPIOCs.xsd 19 Annex C (normative): SOAP Solution Set . 21 C.1 Architectural features . 21 C.1.1 Syntax for Distinguished Names . 21 C.1.2 Notifi

20、cation Services 21 C.1.3 Supported W3C specifications . 21 C.1.4 Prefixes and namespaces . 21 ETSI ETSI TS 132 346 V13.0.0 (2016-02) 4 3GPP TS 32.346 version 13.0.0 Release 13 C.2 Mapping . 22 C.2.1 Operation and notification mapping 22 C.2.2 Operation parameter mapping 22 C.2.2.1 Operation listAvai

21、lableFiles . 22 C.2.2.1.1 Input parameters . 22 C.2.2.1.2 Output parameters 23 C.2.2.1.3 Fault definition . 23 C.2.2.2 Operation fileDownloadIndication . 23 C.2.2.2.1 Input parameters . 23 C.2.2.2.2 Output parameters 23 C.2.2.2.3 Fault definition . 23 C.3 Solution Set definitions 24 C.3.1 WSDL defin

22、ition structure . 24 C.3.2 Graphical Representation . 24 C.3.3 WSDL specification FTRPSystem.wsdl. 24 Annex D (informative): Change history . 26 History 27 ETSI ETSI TS 132 346 V13.0.0 (2016-02) 5 3GPP TS 32.346 version 13.0.0 Release 13 Foreword This Technical Specification (TS) has been produced b

23、y the 3rd 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 o

24、f 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,

25、 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-family covering the 3rd Generation Partnership Project; Technical Specification Group Servic

26、es 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): Information Service (IS)“ 32.346: “File Transfer (FT) Integration Reference Point (IRP

27、): Solution Set (SS) definitions“ 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 3GPP TS 32.102 2. Network

28、 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 anticipated that manag

29、ement functions (e.g. PM, Call Trace, CM) make reuse of capabilities provided by this File Transfer IRP. ETSI ETSI TS 132 346 V13.0.0 (2016-02) 6 3GPP TS 32.346 version 13.0.0 Release 13 1 Scope The present document contains the Solution Sets for the IRP whose semantics are specified in File Transfe

30、r IRP: Information Service (3GPP TS 32.342 15). This Solution Set specification is related to 3GPP TS 32.342 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 (identifi

31、ed 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-specific reference imp

32、licitly 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: “Telecommunication management

33、; File Transfer (FT) Integration Reference 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 Refer

34、ence Point (IRP): Solution Set (SS) definitions“. 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

35、3GPP TS 32.316: “Telecommunication management; 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 Ser

36、vice“. http:/www.omg.org/technology/documents/ 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 specifi

37、cation (http:/www.w3.org/TR/soap12-part1/) 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) d

38、efinitions“. ETSI ETSI TS 132 346 V13.0.0 (2016-02) 7 3GPP TS 32.346 version 13.0.0 Release 13 17 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 doc

39、ument, the terms and definitions given in 3GPP 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

40、following abbreviations apply: CM Configuration Management CORBA Common Object Request Broker Architecture DN Distinguished Name FT File Transfer FTIRP File Transfer IRP IDL Interface Definition Language IRP Integration Reference Point IS Information Service NE Network Element NL Notification Log NR

41、M Network Resource Model OMG Object Management Group PM Performance Management SS Solution Set UML 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:

42、 Annex A provides the CORBA Solution Set. Annex B provides the XML Definitions. Annex C provides the SOAP Solution Set. ETSI ETSI TS 132 346 V13.0.0 (2016-02) 8 3GPP TS 32.346 version 13.0.0 Release 13 Annex A (normative): CORBA Solution Set This annex contains the CORBA Solution Set for the IRP who

43、se semantics is specified in FT IRP: Information Service (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

44、a Distinguished Name is defined in 3GPP TS 32.300 6. 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

45、support FileTransferIRPNotifications notifications 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

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

47、, 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 objectionab

48、le 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 FileTransferIRP Noti

49、fication Interface OMG CORBA Notification push operation is used to realise the notification of FileTransferIRP 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 ETSI TS 132 346 V13.0.0 (2016-02) 9 3GPP TS 32.346 version 13.