ETSI TS 132 344-2004 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) Telecommunication management File Transfer (FT) Integra_1.pdf

1、 ETSI TS 132 344 V6.0.0 (2004-12)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);Telecommunication management;File Transfer (FT) Integration Reference Point (IRP):Common Management Information Protocol (CMIP)Solution Set

2、 (SS)(3GPP TS 32.344 version 6.0.0 Release 6)GLOBAL SYSTEM FOR MOBILE COMMUNICATIONSRETSI ETSI TS 132 344 V6.0.0 (2004-12) 1 3GPP TS 32.344 version 6.0.0 Release 6 Reference DTS/TSGS-0532344v600 Keywords GSM, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94

3、42 00 Fax: +33 4 93 65 47 16 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 mo

4、re than one electronic version 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 n

5、etwork 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/status.asp If you find errors in th

6、e present document, please send 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.

7、 European Telecommunications Standards Institute 2004. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Tra

8、de Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 132 344 V6.0.0 (2004-12) 2 3GPP TS 32.344 version 6.0.0 Release 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETS

9、I. 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 is availab

10、le 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 can be given as to the existence of other IPRs not referenced

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

12、s 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 found under http:/webapp.etsi.org/key/queryform.asp . ETSI ETSI

13、TS 132 344 V6.0.0 (2004-12) 3 3GPP TS 32.344 version 6.0.0 Release 6 Contents Intellectual Property Rights2 Foreword.2 Foreword.4 Introduction 4 1 Scope 5 2 References 5 3 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .5 4 Architectural features .6 4.1 Notifications .6 4.2 Synta

14、x for Distinguished Names and Versions 6 5 Mapping .6 5.1 Mapping of Information Object Classes.6 5.2 Mapping of IOC Attributes 6 5.3 Mapping of Operations and Notifications 6 5.3.1 Mapping of Operations .6 5.3.2 Mapping of Notifications7 5.4 Operation parameter mapping 7 5.5 Mapping of Notification

15、 Parameters 8 - 6 GDMO definitions9 - 6.1 Managed Object Classes 9 - 6.1.1 fileTransferIRP .9 - 6.2 Packages.9 - 6.2.1 ftIRPOperationsPackage1.9 - 6.2.2 ftIRPOperationsPackage2.9 - 6.2.3 ftIRPNotificationPackage .10 - 6.3 Actions .10 - 6.3.1 listAvailableFiles(M)10 - 6.3.2 fileDownloadIndication(M)

16、11 - 6.4 Notifications .11 - 6.4.1 notifyFileReady (M) .11 - 6.4.2 notifyFilePreparationError (O) .12 - 7 ASN.1 definitions for the FT IRP 12 Annex A (informative): List of assigned Object Identifiers16 Annex B (informative): Change history .17 History 18 ETSI ETSI TS 132 344 V6.0.0 (2004-12) 4 3GPP

17、 TS 32.344 version 6.0.0 Release 6 Foreword 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

18、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 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approve

19、d 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 changes have been incorporated in the document. Introduction The present document is part of a

20、 TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: TS 32.341 “File Transfer (FT) Integration Reference Point (IRP): Requirements“; TS 32.342 “File Transfer (FT) Integration Reference

21、 Point (IRP): Information Service (IS)“; TS 32.343 “File Transfer (FT) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. TS 32.344 “File Transfer (FT) Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set

22、(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 3GPP TS 32.102 2. Network Elements (NEs) under manag

23、ement, element managers as well as network managers generate various management information stored in file format. This IRP 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

24、, Call Trace, CM) as well as associated IRPs use the capabilities provided by this File Transfer IRP. ETSI ETSI TS 132 344 V6.0.0 (2004-12) 5 3GPP TS 32.344 version 6.0.0 Release 6 1 Scope The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the IRP

25、whose semantics is specified in File Transfer IRP: Information Service 7. 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

26、ersion number, etc.) or 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 t

27、hat 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 Referenc

28、e Point (IRP): Requirements“. 4 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management: Requirements“. 5 3GPP TS 32.304: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Management Inform

29、ation Protocol (CMIP) Solution 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

30、32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management: Information Service (IS)“. 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.341 3 an

31、d 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: ASN.1 Abstract Syntax Notation.1 CM Configuration ManagementETSI ETSI TS 132 344 V6.0.0 (2004-12) 6 3GPP T

32、S 32.344 version 6.0.0 Release 6 CMIP Common Management Information Protocol DN Distinguished Name FT File Transfer GDMO Guidelines for the Definition of Managed Objects IS Information Service NE Network Element PM Performance Management SS Solution Set 4 Architectural features The overall architect

33、ural feature of FileTransferIRP is specified in 3GPP TS 32.341 3. This clause specifies features that are specific to the CMIP SS. 4.1 Notifications Notifications are sent according to the Notification IRP: CMIP SS (see 3GPP TS 32.304 ?). The contents of the FileTransferIRP notifications are defined

34、 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 Mapping of Information Object Classes For the FT IRP CMIP So

35、lution Set the Information Object Classes (IOC) and the Interfaces defined in 3GPP TS 32.342 7 are mapped onto Managed Object Classes (MOC) as given in Table 1. These MOC include all the Attributes, Actions and Notifications necessary to model file transfer management as described in 3GPP TS 32.342

36、7. Table 1: Mapping of Information Object Classes IS IOC CMIP SS MOC FileTransferIRP fileTransferIRP 5.2 Mapping of IOC Attributes 5.3 Mapping of Operations and Notifications FileTransferIRP: IS 3GPP TS 32.342 7 defines the semantics of operations and notifications visible across the FileTransferIRP

37、. Clause 5.3.1 and 5.3.2 describe the mapping of FileTransferIRP: IS operations and notifications onto their equivalents defined in this SS. 5.3.1 Mapping of Operations Table 2 maps the Interface/Operations defined in the IS of the file transfer IRP onto their equivalents in the CMIP SS. These are q

38、ualified as Mandatory (M) or Optional (O). ETSI ETSI TS 132 344 V6.0.0 (2004-12) 7 3GPP TS 32.344 version 6.0.0 Release 6 Table 2: Mapping of Operations IS Interface Qualifier IS Operation CMIP SS Equivalent Qualifier FileTransferIRPOperations_1 Interface M listAvailableFiles CMISE M-ACTION service,

39、 action type: listAvailableFiles M FileTransferIRPOperations_2 Interface M fileDownloadIndication CMISE M-ACTION service, action type: fileDownloadIndication O GenericIRPVersionOperation M getIRPVersion CMISE M-ACTION service, action type: getIRPVersion M getNotificationProfile CMISE M-ACTION servic

40、e, action type: getNotificationProfile M GenericIRPProfileOperation O getOperationProfile CMISE M-ACTION service, action type: getOperationProfile M NOTE: The Interfaces GenericIRPVersionOperation and GenericIRPProfileOperation are inherited from 3GPP TS 32.314 8. 5.3.2 Mapping of Notifications Tabl

41、e 3 maps the Interface/Notifications defined in the IS of the file transfer IRP onto their equivalents in the CMIP SS. These are qualified as Mandatory (M) or Optional (O). Table 3: Mapping of IS Notification IS Notification CMIP SS Equivalent Qualifier notifyFileReady notifyFileReady M notifyFilePr

42、eparationError notifyFilePreparationError M 5.4 Operation parameter mapping The FileTransferIRP: IS 3GPP TS 32.342 7 defines semantics of parameters carried in operations across the FileTransferIRP. The following tables indicate the mapping of these parameters, as per operation, to their equivalents

43、 defined in this SS. Table 5: Parameter mapping of the operation listAvailableFiles IS Operation parameter IN/ OUT CMIP SS Equivalent Qualifier managementDataType IN M-ACTION parameter Action information: (ListAvailableFilesInfo): managementDataType M beginTime INM-ACTION parameter Action informatio

44、n: (ListAvailableFilesInfo): beginTime M endTime IN M-ACTION parameter Action information: (ListAvailableFilesInfo): endTime M fileInfoList OUTM-ACTION parameter Action Reply: (ListAvailableFilesReply): fileInfoList M status OUT M-ACTION parameter Action Reply: (ListAvailableFilesReply): status M Ta

45、ble 6: Parameter mapping of the operation fileDownloadIndication IS Operation parameter IN/ OUT CMIP SS Equivalent Qualifier fileInfoList IN M-ACTION parameter Action information: (FileDownloadIndicationInfo): FileInfoList M status OUT M-ACTION parameter Action Reply: (FileDownloadIndicationReply):

46、ErrorCauses M ETSI ETSI TS 132 344 V6.0.0 (2004-12) 8 3GPP TS 32.344 version 6.0.0 Release 6 5.5 Mapping of Notification Parameters In the CMIP Solution Set notifications emitted by an Agent are reported to the Managers by means of the CMISE “M-EVENT-REPORT“ service primitive, which again is impleme

47、nted by means of the “m-EventReport OPERATION“ (see ITU-T Recommendations X.710 and X.711 ). The argument of the m-EventReport OPERATION is defined in ITU-T Recommendation X.711 as follows: EventReportArgument := SEQUENCE managedObjectClass ObjectClass, managedObjectInstance ObjectInstance, eventTim

48、e 5 IMPLICIT GeneralizedTime OPTIONAL, eventType EventTypeId, eventInfo 8 ANY DEFINED BY eventType OPTIONAL where eventInfo has to be further specified for each notification by means of specific GDMO/ASN.1 definitions. For the notifications defined in 3GPP TS 32. 342 7 all parameters are mapped onto

49、 their CMIP SS equivalents as shown in the following tables. Most parameters are mapped to the M-EVENT report parameter Event information. The Event information parameter is described by the ASN.1 definitions given in this document. Table 7: Parameter mapping of the notification notifyFileReady IS Parameter Qualifier CMIP SS Equivalent objectClass M M-EVENT-REPORT parameter “Managed object class“ objectInstance M M-EVENT-REPORT parameter “Managed object instance“ noti