1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommFile Transfer (FT) I(3GPP TS 32.3TECHNICAL SPECIFICATION132 341 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; ) Integration Reference Point Requirements .341 version 13.0.0 Release 1316-02) ha
2、se 2+); (UMTS); t (IRP); 13) ETSI ETSI TS 132 341 V13.0.0 (2016-02)13GPP TS 32.341 version 13.0.0 Release 13Reference RTS/TSGS-0532341vd00 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 0001
3、7 - 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 ele
4、ctronic 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 (P
5、DF) 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/sta
6、tus.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 photoco
7、pying 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 201
8、6. 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. GSM and the GSM logo are Trade Marks regis
9、tered and owned by the GSM Association. ETSI ETSI TS 132 341 V13.0.0 (2016-02)23GPP TS 32.341 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if a
10、ny, 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 available
11、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 are, or
12、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 identiti
13、es. 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“, “sho
14、uld 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 ETSI T
15、S 132 341 V13.0.0 (2016-02)33GPP TS 32.341 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 File Transfe
16、r IRP concept. 6g35 File Transfer IRP requirements 6g35.1 General requirements for File Transfer IRP . 6g35.2 File type requirements 7g35.3 File exchange requirements 7g35.4 File management/maintenance/security requirements 7g36 Overview of IRPs related to File Transfer (FT) 8g3Annex A (informative)
17、: Change history . 9g3History 10g3ETSI ETSI TS 132 341 V13.0.0 (2016-02)43GPP TS 32.341 version 13.0.0 Release 13Foreword 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 th
18、e 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 presented to TSG for in
19、formation; 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 changes have bee
20、n incorporated in the document. Introduction The present document is part the 32.34x-series covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.341: “File Transfer (FT) Integration Reference
21、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 Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a r
22、elated Name Convention, which realize the functional capabilities over this interface. The basic structure 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 st
23、ored 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, Call Trace, CM) as well as associated IRPs making reuse of capabilities provided by this Fil
24、e Transfer IRP. ETSI ETSI TS 132 341 V13.0.0 (2016-02)53GPP TS 32.341 version 13.0.0 Release 131 Scope The 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 provision
25、s that, 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-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference,
26、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 32.101: “Telecommunication management; Principles and high le
27、vel requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.111-series: “Telecommunication management; Fault Management; Alarm Integration Reference Point (IRP)“. 4 3GPP TS 32.30x-series: “Telecommunication management; Configuration Management (CM); Notification I
28、ntegration Reference Point (IRP)“. 5 3GPP TS 32.33x-series: “Telecommunication management; Notification 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;
29、 Performance Management (PM); Concept and requirements“. 8 3GPP TS 32.41x-series: “Telecommunication 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
30、TS 32.61x-series: “Telecommunication management; Configuration Management (CM); Bulk CM Integration 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 o
31、f the present document, the terms and definitions given in 3GPP TS 32.101 1 and 3GPP TS 32.102 2 apply. ETSI ETSI TS 132 341 V13.0.0 (2016-02)63GPP TS 32.341 version 13.0.0 Release 133.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Manag
32、ement EM Element Manager FT File TransferFTP File Transfer Protocol IRP Integration Reference Point 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 netwo
33、rk managers generate various management information that is stored in files. 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, Call Trace, CM) as well as associate
34、d IRPs making reuse of capabilities provided by this File Transfer IRP. It should be noted that this 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
35、protocol. 5 File Transfer IRP requirements 5.1 General requirements for File Transfer IRP The FT IRP 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 sha
36、ll preserve the encoding of the file during exchange. NOTE 1: Above requirement(s) are considered 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 securit
37、y features that might be added in future versions of the present document. The FT IRP shall 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 Nam
38、e conventions: In the context of this File Transfer IRP an overall applicable file name 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 poss
39、ible 7. This file name convention should address issues with potential Operating System 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 ETSI ETSI TS 132 341 V13.0.0 (2016-02)73GPP TS 32.341 version 13.0.0
40、Release 135.2 File type requirements The FT IRP shall support the exchange and management/maintenance of the following file types: 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
41、 as defined in 5. Charging files as defined in 11. Vendor-specific files 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. invent
42、ory information). 5.3 File exchange requirements The IRP Manager shall 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:
43、 the IRP Manager will always act as the initiator (client) of file 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
44、Preparation Error“, indicating that an error occurred during or 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 requirement
45、s The IRP Manager should be able to request the IRP Agent 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
46、 1 should be supported (e.g. username, password, encryption). 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 expirati
47、on date, which is part of the file name. ETSI ETSI TS 132 341 V13.0.0 (2016-02)83GPP TS 32.341 version 13.0.0 Release 136 Overview 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
48、 purpose of the File Transfer IRP the following IRPs are needed: Notification IRP 4. The 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 IRP for file transfer purposes): Perf
49、ormance 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 exports as defined in 5. Specification changes needed by those IRPs to make reuse of the FT IRP are outside the scope of the present document. ETSI ETSI TS 132 341 V13.0.0 (2016-02)93GPP TS 32.341 version 13.0.0 Release 13Annex A (informative): Change history Change hist
