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

1、 ETSI TS 132 343 V9.0.0 (2010-02)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;File Transfer (FT) Integration Reference Point (IRP);Common Object Request Broker Architecture (CORBA)Solu

2、tion Set (SS) (3GPP TS 32.343 version 9.0.0 Release 9)ETSI ETSI TS 132 343 V9.0.0 (2010-02)13GPP TS 32.343 version 9.0.0 Release 9Reference RTS/TSGS-0532343v900 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

3、Siret N 348 623 562 00017 - NAF 742 C Association 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 versio

4、n or in print. In any case of existing or perceived 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 Secr

5、etariat. 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/status.asp If you find errors in the present document, please se

6、nd your comment to one of the following services: 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

7、Standards Institute 2010. All rights reserved. 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.

8、 LTE is a Trade Mark of ETSI currently being 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 343 V9.0.0 (2010-02)23GPP TS 32.343 version 9.0.0 Release 9Intellectual P

9、roperty Rights IPRs essential or potentially 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)

10、; Essential, or potentially Essential, IPRs notified 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 searche

11、s, 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 are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced

12、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 deliverables. The cross reference between

13、 GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 343 V9.0.0 (2010-02)33GPP TS 32.343 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions a

14、nd abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Architectural features . 6g34.1 Notifications . 6g34.2 Syntax for Distinguished Names and Versions 6g35 Mapping . 6g35.1 Operation and Notification mapping 6g35.2 Operation parameter mapping 7g35.3 Notification parameter mapping . 8g3

15、6 FileTransferIRP Notification Interface. 11g36.1 Method push (M) 11g3Annex A (normative): IDL specifications 12g3A.1 IDL specification (file name “FileTransferIRPConstDefs.idl“) . 12g3A.2 IDL specification (file name “FileTransferIRPSystem.idl“) 14g3A.3 IDL specification (file name “FileTransferIRP

16、Notifications.idl“) . 16g3Annex B (informative): Change history . 18g3History 19g3ETSI ETSI TS 132 343 V9.0.0 (2010-02)43GPP TS 32.343 version 9.0.0 Release 9Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present docu

17、ment 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 number as follows: Version x.y.z where:

18、 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, updates, etc. z the third digit is inc

19、remented when editorial only changes have been incorporated in the document. Introduction The present document is part a TS-family covering the 3rdGeneration Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.341: “Fi

20、le Transfer (FT) Integration Reference Point (IRP): Requirements“ 32.342: “File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“ 32.343: “File Transfer (FT) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“ 32.345: “File

21、 Transfer (FT) Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“ 32.347: “File Transfer (FT) Integration Reference Point (IRP): SOAP Solution Set (SS)“ The present document is part of a set of TSs which describe the requirements and information model necessary for the

22、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 information stored in file format. This IRP

23、 is addressing how these file are exchanged through Itf-N as well as certain aspects of file management and maintenance. It is anticipated that all management functions (e.g. PM, Call Trace, CM) as well as associated IRPs making reuse of capabilities provided by this File Transfer IRP. ETSI ETSI TS

24、132 343 V9.0.0 (2010-02)53GPP TS 32.343 version 9.0.0 Release 91 Scope The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in File Transfer IRP: Information Service 3GPP TS 32.342 7. This Solution Set specifi

25、cation 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 either specific (identified by date of publication, edition number, version number, etc.) or non-sp

26、ecific. 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 that document in the same Relea

27、se 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 Reference Point (IRP): Requirements“.

28、4 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management: Requirements“. 5 3GPP TS 32.303: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solu

29、tion Set (SS)“. 6 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 7 3GPP TS 32.342: “Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“. 8 3GPP TS 32.312: “Telecommunication

30、 management; Generic Integration Reference Point (IRP) management: Information Service (IS)“. 9 OMG TC Document telecom/98-11-01: “OMG Notification Service“. http:/www.omg.org/technology/documents/ 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms an

31、d definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.341 3 and the following apply: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 4. ETSI ETSI TS 132 343 V9.0.0 (2010-02)63GPP TS 32.343 version 9.0.0 Release 93.2 Abbreviations For the purposes of the prese

32、nt document, the following abbreviations apply: CM Configuration Management CORBA Common Object Request Broker Architecture DN Distinguished Name FT File TransferIDL Interface Definition Language IS Information ServiceNE Network Element OMG Object Management Group PM Performance ManagementSS Solutio

33、n Set4 Architectural features The overall architectural feature of FileTransferIRP is specified in 3GPP TS 32.341 3. This clause specifies features that are specific to the CORBA SS. 4.1 Notifications Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.303 5). The cont

34、ents of the FileTransferIRP notifications are defined in the present document. 4.2 Syntax for Distinguished Names and Versions The format of a Distinguished Name is defined in 3GPP TS 32.300 6. The version of this IRP is represented as a string (see also clause 3 for versions). 5 Mapping 5.1 Operati

35、on and Notification mapping FileTransferIRP: IS 3GPP TS 32.342 7 defines semantics of operation and notification visible across the FileTransferIRP. Table 1 indicates mapping of these operations and notifications to their equivalents defined in this SS. Table 1: Mapping from IS Operations and Notifi

36、cation to SS equivalents IS Operations/ notification 3GPP TS 32.342 7 SS Method Qualifier listAvailableFiles list_available_files MfileDownloadIndication file_download_indication OgetIRPVersion (see note) get_file_transfer_irp_versions M getOperationProfile (see note) get_file_transfer_irp_operation

37、s_profile O getNotificationProfile (see note) get_file_transfer_irp_notifications_profile O notifyFileReady push_structured_events (see subclause 6.1) M notifyFilePreparationError push_structured_events (see subclause 6.1) M NOTE: This operation is of ManagedGenericIRP IOC specified in 3GPP TS 32.31

38、2 8. The FileTransferIRP IOC of 3GPP TS 32.342 7 inherits from it. ETSI ETSI TS 132 343 V9.0.0 (2010-02)73GPP TS 32.343 version 9.0.0 Release 95.2 Operation parameter mapping The FileTransferIRP: IS 3GPP TS 32.342 7 defines semantics of parameters carried in operations across the FileTransferIRP. Th

39、e following tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS. Table 2: Mapping from IS listAvailableFiles parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier managementDataType short management_data_type M beginT

40、ime FileTransferIRPConstDefs:UTCTime begin_time MendTime FileTransferIRPConstDefs:UTCTime end_time MfileInfoList FileTransferIRPConstDefs:FileInfoList file_info_list M status Return value of type FileTransferIRPConstDefs:Result Exception: ListAvailableFiles, InvalidTimes, ManagedGenericIRPSystem:Inv

41、alidParameter M Table 3: Mapping from IS fileDownloadIndication parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier fileInfoList FileTransferIRPConstDefs:FileInfoList file_info_list Mstatus Return value of type FileTransferIRPConstDefs:Result Exception: FileDownloadIndi

42、cation, InvalidFileInfoList, ManagedGenericIRPSystem:OperationNotSupported M Table 4: Mapping from IS getIRPVersion parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier versionNumberSet Return value of type ManagedGenericIRPConstDefs:VersionNumberSet M status Exception:

43、GetFileTransferIRPVersions M Table 5: Mapping from IS getOperationProfile parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier iRPVersion ManagedGenericIRPConstDefs:VersionNumber irp_version MoperationNameProfile, operationParameterProfile Return value of type ManagedGen

44、ericIRPConstDefs:MethodList M status Exception: GetFileTransferIRPOperationsProfile, ManagedGenericIRPSystem:OperationNotSupported, ManagedGenericIRPSystem:InvalidParameter M Table 6: Mapping from IS getNotificationProfile parameters to SS equivalents IS Operation parameter SS Method parameter Quali

45、fier iRPVersion ManagedGenericIRPConstDefs:VersionNumber irp_version MnotificationNameProfile, notificationParameterProfile Return value of type ManagedGenericIRPConstDefs:MethodList M status Exception: GetFileTransferIRPNotificationsProfile, ManagedGenericIRPSystem:OperationNotSupported, ManagedGen

46、ericIRPSystem:InvalidParameter M ETSI ETSI TS 132 343 V9.0.0 (2010-02)83GPP TS 32.343 version 9.0.0 Release 95.3 Notification parameter mapping The FileTransferIRP: IS 3GPP TS 32.342 7 defines semantics of parameters carried in notifications. The following table indicates the mapping of these parame

47、ters to their OMG CORBA Structured Event (defined in OMG Notification Service 9) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service 9, is: Header Fixed Header domain_name type_name event_name Variable Header Body filterable_body_fields remaining_body The

48、 following tables list all OMG Structured Event attributes in the second column. The first column identifies the FileTransferIRP: IS 3GPP TS 32.342 7 defined notification parameters. ETSI ETSI TS 132 343 V9.0.0 (2010-02)93GPP TS 32.343 version 9.0.0 Release 9Table 7: Mapping for notifyFileReady IS P

49、arameters OMG CORBA Structured Event attribute Qualifier Comment There is no corresponding IS attribute. domain_name M It carries the IRP document version number string. See subclause 3.1. It indicates the syntax and semantics of the Structured Event as defined by the present document. notificationType type_name M This is the ET_FILE_READY of module of FileTransferIRPNotifDefs. There is no corresponding IS attribute. event_name M It carries no information. There is no corresponding IS attribute. V