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

1、 ETSI TS 132 341 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); Requirements (3GPP TS 32.341 version 15.0.0 Release 15) TECHNICA

2、L SPECIFICATION ETSI ETSI TS 132 341 V15.0.0 (2018-07)13GPP TS 32.341 version 15.0.0 Release 15Reference RTS/TSGS-0532341vf00 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 00017 - NAF 742 C

3、 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 electronic and/o

4、r 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 (PDF) version k

5、ept 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/ETSIDeliverableStatus.

6、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, including photocopyi

7、ng 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. DECTTM, PLUGTESTSTM, U

8、MTSTMand 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 logo are trademar

9、ks registered and owned by the GSM Association. ETSI ETSI TS 132 341 V15.0.0 (2018-07)23GPP TS 32.341 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 information pertaining t

10、o 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 ETSI Secretariat. L

11、atest 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 updates on the ETS

12、I 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 as being the prope

13、rty 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 Specification (TS) has

14、 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 deliverables. The cross re

15、ference 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 interpreted as described i

16、n 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 341 V15.0.0 (2018-07)33GPP TS 32.341 version 15.0.0 Release 15Contents Intellectual Property Right

17、s 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 File Transfer IRP concept. 6g35 File Transfer IRP requirements 6g35.1 General requirements for File Transfer IRP . 6

18、g35.2 File type requirements 6g35.3 File exchange requirements 7g35.4 File management/maintenance/security requirements 7g36 Overview of IRPs related to File Transfer (FT) 7g3Annex A (informative): Change history . 9g3History 10g3ETSI ETSI TS 132 341 V15.0.0 (2018-07)43GPP TS 32.341 version 15.0.0 R

19、elease 15Foreword 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 contents of the present do

20、cument, 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 approved document under change co

21、ntrol. 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 the 32.34x-series covering the

22、 3rdGeneration Partnership Project; Technical Specification Group Services 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 Se

23、rvice (IS)“ 32.346: “File Transfer (FT) Integration Reference Point (IRP); Solution Set (SS) definitions“ The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realize the functional capabilities over this interface. The basic structu

24、re of the IRPs is defined 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 is addressing how these file are exchanged through Itf-N as well as certai

25、n 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 132 341 V15.0.0 (2018-07)53GPP TS 32.341 version 15.0.0 Release 151 Scope T

26、he present document specifies the overall requirements for the File Transfer Integration Reference Point (FT IRP) as it applies to the Itf-N. 2 References The following documents contain provisions that, through reference in this text, constitute provisions of the present document. - References are

27、either specific (identified by date of publication, edition number, version 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 documen

28、t), a non-specific reference implicitly 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.11

29、1-series: “Telecommunication management; Fault Management; Alarm Integration Reference Point (IRP)“. 4 3GPP TS 32.30x-series: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP)“. 5 3GPP TS 32.33x-series: “Telecommunication management; Notific

30、ation log Integration Reference Point (IRP)“. 6 3GPP TS 32.32x-series: “Telecommunication management; Test management Integration Reference Point (IRP)“. 7 3GPP TS 32.401: “Telecommunication management; Performance Management (PM); Concept and requirements“. 8 3GPP TS 32.41x-series: “Telecommunicati

31、on management; Performance Management (PM) Integration Reference Point (IRP)“. 9 3GPP TS 32.421: “Telecommunication management; Subscriber and equipment trace: Trace concepts and requirements“. 10 3GPP TS 32.61x-series: “Telecommunication management; Configuration Management (CM); Bulk CM Integratio

32、n Reference Point (IRP)“. 11 3GPP TS 32.240: “Telecommunication management; Charging management; Charging architecture and principles“. 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 and 3GPP TS 32.102 2 a

33、pply. ETSI ETSI TS 132 341 V15.0.0 (2018-07)63GPP TS 32.341 version 15.0.0 Release 153.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management EM Element Manager FT File TransferFTP File Transfer Protocol IRP Integration Reference Poin

34、t NE Network Element NM Network ManagerPM Performance Management SFTP Secure File Transfer Protocol 4 File Transfer IRP concept Network Elements (NEs) under management, element managers as well as network managers generate various management information that is stored in files. This IRP is addressin

35、g 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. It should be noted that th

36、is File Transfer IRP is not defining a file transfer protocol (applicable file transfer protocols are defined by 3GPP TS 32.101 1) but will make reuse of generic concepts defined by these file transfer protocol. 5 File Transfer IRP requirements 5.1 General requirements for File Transfer IRP The FT I

37、RP shall ensure preservation of file content: - The used file transfer protocol implementation shall preserve the formatting of the file during exchange. - The used file transfer protocol implementation shall preserve the encoding of the file during exchange. NOTE 1: Above requirement(s) are conside

38、red as being satisfied by FTP. The FT IRP shall support the following file transfer protocols: - FTP. - SFTP NOTE 2: SFTP providing initial security capabilities, which may be complemented by additional security features that might be added in future versions of the present document. The FT IRP shal

39、l specify all necessary descriptive file information and parameters, to enable exchange of files between IRPManager and IRPAgent and to ensure respective file management capabilities (such as listing). File Name conventions: - In the context of this File Transfer IRP an overall applicable file name

40、convention should be specified, ensuring the use of meaningful and uniform names of files generated by various IRPs. This convention should reuse the current PM File Naming Conventions to the greatest extent possible 7. - This file name convention should address issues with potential Operating Syste

41、m based changes in file names during or after file exchange (e.g. upper case / lower case). - The file name shall contain the file expiration date 5.2 File type requirements The FT IRP shall support the exchange and management/maintenance of the following file types: ETSI ETSI TS 132 341 V15.0.0 (20

42、18-07)73GPP TS 32.341 version 15.0.0 Release 15- Performance measurement results as defined in 7 and 8. - Test results as defined in 6. - Bulk CM files as defined in 10. - Call trace records as defined in 9. - Notification log as defined in 5. - Charging files as defined in 11. - Vendor-specific fil

43、es containing management information. Subsequently this File Transfer IRP shall consider requirements from management applications listed above. Future 3GPP management information file types shall be supported as well (e.g. inventory information). 5.3 File exchange requirements The IRP Manager shall

44、 be able to: - Upload (read) one or more files from the IRP Agent using FTP or SFTP; - Download (write) one or more files to the IRP Agent using FTP or SFTP, and indicate to the IRP Agent that files have been downloaded. Subsequently: the IRP Manager will always act as the initiator (client) of file

45、 transfer actions, while the IRP Agent shall provide the corresponding server capabilities. This IRP Agent should provide the following notifications to the IRP Manager: - “File Ready“, indicating that a file is ready for upload; - “File Preparation Error“, indicating that an error occurred during o

46、r before file preparation and that no file is being made available related to a specific request; - “File Deleted”, indicating that a file has been made unavailable for access though Itf-N. 5.4 File management/maintenance/security requirements The IRP Manager should be able to request the IRP Agent

47、to: - Provide a list of available files, based on file name and file creation date/time filter criteria. In addition the following requirements should be considered: - Security mechanisms supported by applicable file transfer protocols defined in 1 should be supported (e.g. username, password, encry

48、ption). - File system overload mechanism on IRP Agent side (e.g. automatic deletion of transmitted files, automatic deletion of outdated files, emission of notifications in case of automatic deletion). - File deletion is determined by a file expiration date, which is part of the file name. 6 Overvie

49、w of IRPs related to File Transfer (FT) Itf-N is built up by a number of IRPs. The basic structure of the IRPs is defined in 3GPP TS 32.101 1 and 3GPP TS 32.102 2. For the purpose of the File Transfer IRP the following IRPs are needed: - Notification IRP 4. ETSI ETSI TS 132 341 V15.0.0 (2018-07)83GPP TS 32.341 version 15.0.0 Release 15The following IRP/specifications shall consider using this FT IRP for file transfer purposes (future IRP or IRP capabilities not listed here shall also consider reuse of this FT IR