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

《ETSI TS 132 346-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management File Transfer (F.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 346-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management File Transfer (F.pdf（32页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 346 V14.0.0 (2017-04) 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 14.0.0 Rel

2、ease 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 346 V14.0.0 (2017-04)13GPP TS 32.346 version 14.0.0 Release 14Reference RTS/TSGS-0532346ve00 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. European Telecommunications Standards

8、 Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for

9、 the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 346 V14.0.0 (2017-04)23GPP TS 32.346 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been decl

10、ared 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 notified to ETSI in respect of ETSI standards“, which

11、 is available from the ETSI 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

12、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 (3GPP). The present document may refer to technical specifications o

13、r 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 found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs te

14、rminology In the present document “shall“, “shall not“, “should“, “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

15、 in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 346 V14.0.0 (2017-04)33GPP TS 32.346 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 6g3Introduction 6g31 Scope 7g32 References 7g33 Definitions and abbre

16、viations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Solution Set Definitions . 8g3Annex A (normative): CORBA Solution Set . 9g3A.1 Architectural features . 9g3A.1.1 Syntax for Distinguished Names 9g3A.1.2 Notification Services 9g3A.1.3 Push and Pull Style . 9g3A.1.4 Support multiple notificati

17、ons in one push operation . 9g3A.1.5 FileTransferIRP Notification Interface . 9g3A.1.5.1 Method push (M) 9g3A.2 Mapping . 11g3A.2.1 Operation and Notification mapping 11g3A.2.2 Operation parameter mapping 11g3A.2.3 Notification parameter mapping . 12g3A.3 Solution Set definitions 14g3A.3.1 IDL defin

18、ition structure 14g3A.3.2 IDL specification “FileTransferIRPConstDefs.idl“ 15g3A.3.3 IDL specification “FileTransferIRPSystem.idl“ . 16g3A.3.4 IDL specification “FileTransferIRPNotifications.idl“ 18g3Annex B (normative): XML Definitions 20g3B.1 Architectural Features 20g3B.1.1 Syntax for Distinguish

19、ed Names 20g3B.1.2 Notification Services 20g3B.1.3 IOC Definitions 20g3B.2 Mapping . 20g3B.3 Solution Set definitions 20g3B.3.1 XML definition structure 20g3B.3.2 Graphical Representation . 21g3B.3.3 XML Schema “fTIRPNotif.xsd” 22g3B.3.4 XML Schema “fTIRPIOCs.xsd” 23g3Annex C (normative): SOAP Solut

20、ion Set . 24g3C.1 Architectural features . 24g3C.1.1 Syntax for Distinguished Names 24g3C.1.2 Notification Services 24g3C.1.3 Supported W3C specifications . 24g3C.1.4 Prefixes and namespaces 24g3ETSI ETSI TS 132 346 V14.0.0 (2017-04)43GPP TS 32.346 version 14.0.0 Release 14C.2 Mapping . 25g3C.2.1 Op

21、eration and notification mapping . 25g3C.2.2 Operation parameter mapping 25g3C.2.2.1 Operation listAvailableFiles 25g3C.2.2.1.1 Input parameters 25g3C.2.2.1.2 Output parameters . 26g3C.2.2.1.3 Fault definition 26g3C.2.2.2 Operation fileDownloadIndication . 26g3C.2.2.2.1 Input parameters 26g3C.2.2.2.

22、2 Output parameters . 26g3C.2.2.2.3 Fault definition 26g3C.3 Solution Set definitions 27g3C.3.1 WSDL definition structure . 27g3C.3.2 Graphical Representation . 27g3C.3.3 WSDL specification “FTRPSystem.wsdl” . 28g3Annex D (informative): Change history . 31g3History 32g3ETSI ETSI TS 132 346 V14.0.0 (

23、2017-04)53GPP TS 32.346 version 14.0.0 Release 14ETSI ETSI TS 132 346 V14.0.0 (2017-04)63GPP TS 32.346 version 14.0.0 Release 14Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing

24、 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 number as follows: Version x.y.z where: x the first digit: 1 presente

25、d 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, updates, etc. z the third digit is incremented when editorial only c

26、hanges 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 management, as identified below: 32.341: “File Transfer (FT) Integratio

27、n 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 document is part of a TS-family which describe the requirements an

28、d 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 managers as well as network managers generate various management infor

29、mation 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 reuse of capabilities provided by this File Transfer IRP. ETSI ET

30、SI TS 132 346 V14.0.0 (2017-04)73GPP TS 32.346 version 14.0.0 Release 141 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). This Solution Set specification is related to 3GPP TS 32.342 V13.0.

31、X. 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.) non-specific. - For a specific reference, subseq

32、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 TS

33、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 Reference Point (IRP): Requirements “. 4 3GPP TS 32.311: “Telecommunication

34、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) definitions“. 6 3GPP TS 32.300: “Telecommunication management; Configurat

35、ion 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 management; Generic Integration Reference Point (IRP) management; Solution

36、 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/documents/ 11 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-S

37、OAP-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/) 15 3GPP TS 32.342: “Telecommunication management; File Transfer (F

38、T) 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 V14.0.0 (2017-04)83GPP TS 32.346 version 14.0.0 Release 1417 3GPP TS 32.331

39、: “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 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.150 9, 3GPP TS 32.331 1

40、7 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 Configuration Management CORBA Common Object Request Broker Architecture DN Di

41、stinguished 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 Group PM Performance ManagementSS Solution SetUML Unified Modelling

42、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 B provides the XML Definitions. Annex C provides the SOAP Solution Se

43、t. ETSI ETSI TS 132 346 V14.0.0 (2017-04)93GPP TS 32.346 version 14.0.0 Release 14Annex A (normative): CORBA Solution Set This annex contains the CORBA Solution Set for the IRP whose semantics is specified in FT IRP: Information Service (3GPP TS 32.342 15). A.1 Architectural features The overall arc

44、hitectural 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. A.1.2 Notification Services In implementations of CORBA SS, IRPAgen

45、t 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 as specified in 3GPP TS 32.342 15. A.1.3 Push and Pull Style OMG Noti

46、fication 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 the notifications till IRPManager requests for them. This CORBA SS spe

47、cifies 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 one single push operation. To pack multiple notifications into one push

48、 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 t

49、imer, 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 Notification 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_str