1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommPrinciples an(3GPP TS 32.1TECHNICAL SPECIFICATION132 101 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; and high level requirements .101 version 13.0.0 Release 1316-01) hase 2+); (UMTS); 13) ET
2、SI ETSI TS 132 101 V13.0.0 (2016-01)13GPP TS 32.101 version 13.0.0 Release 13Reference RTS/TSGS-0532101vd00 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 Association but n
3、on 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/or print versions o
4、f 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 kept on a specific
5、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/status.asp If you find errors in t
6、he 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 photocopying and microfilm except as a
7、uthorized 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 2016. All rights reserved. DECTTM,
8、 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 registered and owned by the GSM Asso
9、ciation. ETSI ETSI TS 132 101 V13.0.0 (2016-01)23GPP TS 32.101 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 any, is publicly available for E
10、TSI 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 on the ETSI Web server (https:/
11、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 may be, or may become, essentia
12、l 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 identities. These should be interpreted
13、 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“, “should not“, “may“, “need not“, “w
14、ill“, “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 TS 132 101 V13.0.0 (2016-01)33GP
15、P TS 32.101 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 7g33 Definitions and abbreviations . 10g33.1 Definitions 10g33.2 Abbreviations . 11g34 General . 13g34.1 PLMN Telecom Management 13g34.1.1 Basi
16、c objectives for PLMN management . 13g34.1.2 3GPP reference model 14g34.1.3 3GPP provisioning entities . 14g34.1.4 Management infrastructure of the PLMN . 14g34.2 ITU-T TMN 15g35 Architectural framework 16g35.1 Management reference model and interfaces . 16g35.1.1 Overview 16g35.1.2 Interfaces from
17、Operations Systems to NEs (Type 1 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 editoria
18、l only changes have been incorporated in the document.- ETSI ETSI TS 132 101 V13.0.0 (2016-01)73GPP TS 32.101 version 13.0.0 Release 131 Scope The present document establishes and defines the management principles and high-level requirements for the management of PLMNs. In particular, the present do
19、cument identifies the requirements for: - the upper level of a management system; - the reference model, showing the elements the management system interacts with; - the network operator processes needed to run, operate and maintain a network; - the functional architecture of the management system;
20、- the principles to be applied to management interfaces. The requirements identified in the present document are directed to the further development of management specifications as well as the development of management products. The present document can be seen as guidance for the development of all
21、 other Technical Specification addressing the management of PLMNs. The present document does not provide physical architectures of the management system. These aspects are defined and discussed in more detail in TS 32.102 101. Verbal forms used to indicate requirements in the present document (e.g.
22、“shall“, “should“, “may“) are used in compliance with 3GPP specification Drafting Rules TR 21.801 104. 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 p
23、ublication, 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 document), a non-specific reference implicitly refe
24、rs to the latest version of that document in the same Release as the present document. 1 ITU-T Recommendation M.3010 (2000): “Principles for a telecommunications management network“. 2 3GPP TS 22.101: “Service aspects; Service Principles“. 3 3GPP TS 32.111-1: “Telecommunication management; Fault Man
25、agement; Part 1: 3G fault management requirements“. 4 IETF RFC 959: “File Transfer Protocol (FTP)“; October 1985, J. Postel, J. Reynolds, ISI. (Status: Standard). 5 IETF RFC 783: “Trivial File Transfer Protocol (TFTP)“; rev. 2, June 1981, K.R. Sollins MIT. (Status: Unknown). 6 IETF RFC 1157: “Simple
26、 Network Management Protocol (SNMP)“: May 1990, J. Case, SNMP Research, M. Fedor, Performance Systems International, M. Schoffstall, Performance Systems International, J. Davin, MIT Laboratory for Computer Science. (Status: Standard). 7 IETF RFC 2401: “Security Architecture for the Internet Protocol
27、“; November 1998. (Status: Proposed Standard). ETSI ETSI TS 132 101 V13.0.0 (2016-01)83GPP TS 32.101 version 13.0.0 Release 138 The Object Management Group (OMG) “The Common Object Request Broker: Architecture and Specification“, Revision 2.3, June 1999. http:/www.omg.org/technology/documents/vault.
28、htm#CORBA_IIOP 9 . 12 Void 13 ISO 8571-1 (1988): “Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Management - Part 1: General Introduction“. 14 ISO 8571-2 (1988): “Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Man
29、agement - Part 2: Virtual Filestore Definition“. 15 ISO 8571-3 (1988): “Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Management - Part 3: File Service Definition“. 16 ISO 8571-4 (1988): “Information Processing Systems - Open Systems Interconnection - File
30、 Transfer, Access and Management - Part 4: File Protocol Specification“. 17 ISO/IEC ISP 10607-1 (1995): “Information technology - International Standardized Profiles AFTnn - File Transfer, Access and Management - Part 1: Specification of ACSE, Presentation and Session Protocols for the use by FTAM“.
31、 18 ISO/IEC ISP 10607-2 (1995): “Information technology - International Standardized Profiles AFTnn - File Transfer, Access and Management - Part 2: Definition of Document Types, Constraint sets and Syntaxes“. 19 ISO/IEC ISP 10607-3 (1995): “Information technology - International Standardized Profil
32、es AFTnn - File Transfer, Access and Management - Part 3: AFT 11 - Simple File Transfer Service (Unstructured)“. 20 Void 21 Void 22 ITU-T Recommendation X.25 (1996): “Interface between Data Terminal Equipment (DTE) and Data Circuit Terminating Equipment (DCE) for Terminals operating in the Packet Mo
33、de and connected to Public Data Networks by Dedicated Circuit“. 23 . 42 Void 43 ISO/IEC 7776 (1995): “Information technology - Telecommunications and information exchange between systems - High-level data link control procedures - Description of the X.25 LAPB-compatible DTE data link procedures“. 44
34、 ISO/IEC 8208 (2000): “Information technology - Data communications - X.25 Packet Layer Protocol for Data Terminal Equipment“. 45 ISO/IEC 8878 (1992): “Information technology - Telecommunications and information exchange between systems - Use of X.25 to provide the OSI Connection-mode Network Servic
35、e“. 46 IETF RFC 1006: “ISO Transport on top of the TCP“, Marshall T. Rose, Dwight E. Cass, Northrop Research and Technology Center, May 1987. Status: Standard. 47 IETF RFC 793: “Transmission Control Protocol (TCP)“, September 1981. Status: Standard. 48 IETF RFC 791: “Internet Protocol (IP)“, Septemb
36、er 1981. Status: Standard. 49 ITU-T Recommendation X.680 (2002): “Information Technology-Abstract Syntax Notation One (ASN.1): Specification of Basic Notation“. 50 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 51 3GPP TS 22.115: “Service aspects; Charging and Billing“. ETSI ETSI TS 132 101 V
37、13.0.0 (2016-01)93GPP TS 32.101 version 13.0.0 Release 1352 The Object Management Group (OMG) “The Common Object Request Broker: Architecture and Specification“, Revision 2.1, August 1997. http:/www.omg.org/technology/documents/vault.htm#CORBA_IIOP 53 3GPP TS 32.400-series: “Telecommunication manage
38、ment; Performance Management (PM)“. 54 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 55 3GPP TS 32.240: “Telecommunication management; Charging management; Charging architecture and principles“. 56 3GPP TR 22.121: “Service aspects
39、; The Virtual Home Environment; Stage 1“. 57 3GPP TS 32.140: “Telecommunication management; Subscription Management (SuM) requirements“. 58 3GPP TS 32.141: “Telecommunication management; Subscription Management (SuM) architecture“. 59 to 99 Void 100 TMF GB910: “Telecom Operations Map“; Approved Vers
40、ion 2.1 March 2000, (may be downloaded from http:/www.tmforum.org.). 101 3GPP TS 32.102: “Telecommunication management; Architecture“. 102 ITU-T Recommendation M.3013 (2000): “Considerations for a telecommunications management network“. 103 Void. 104 3GPP TR 21.801: “Specification Drafting Rules“. 1
41、05 TMF GB910B: “Telecom Operations Map Application Note-Mobile Services: Performance Management and Mobile Network Fraud and Roaming Agreement Management“; Public Evaluation Version 1.1, September 2000. (May be downloaded free from http:/www.tmforum.org.) 106 OMA Service Provider Environment Require
42、ments, OMA-RD-OSPE-V1_0-20050614-C, The Open Mobile Alliance (URL:http:/www.openmobilealliance.org/). 107 3GPP TR 32.806: “Telecommunication management; Application guide for use of Integration Reference Points (IRPs) on peer-to-peer (p2p) interface“. 108 W3C SOAP Version 1.1 recommendation (http:/w
43、ww.w3.org/TR/2000/NOTE-SOAP-20000508/). 109 W3C SOAP Version 1.2 recommendation (http:/www.w3.org/TR/soap12-part1/). 110 3GPP TR 32.809: “Telecommunication management; Feasibility study of XML-based (SOAP/HTTP) IRP solution sets“. 111 3GPP TS 32.150: “Telecommunication management; Integration Refere
44、nce Point (IRP) Concept and definitions“. 112 ITU-T Recommendation M.3050.x (2006) series Enhanced Telecom Operations Map (eTOM). 113 ITU-T Recommendation M.3050.1 (2004) Enhanced Telecom Operations Map (eTOM) The business process framework. 114 ITU-T Recommendation M.3050.2 (2004) Enhanced Telecom
45、Operations Map (eTOM) Process decompositions and descriptions. 115 TR-069 Amendment 2, CPE WAN Management Protocol v1.1, Broadband Forum ETSI ETSI TS 132 101 V13.0.0 (2016-01)103GPP TS 32.101 version 13.0.0 Release 13116 WS-I Basic Profile 1.1; http:/www.ws-i.org/Profiles/BasicProfile-1.1.html 117 W
46、3C Web Services Description Language (WSDL) 1.1; http:/www.w3.org/TR/wsdl 118 IETF RFC 6241 Network Configuration Protocol (NETCONF); June 2011. 119 3GPP TS 32.107: Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM). 3 Definitions and abbreviations 3.1 Definitions For the purp
47、oses of the present document, the following definitions apply: Domain Manager (DM): provides element management functions and domain management functions for a sub-network. Inter-working domain managers provide multi vendor and multi technology network management functions. Element Manager (EM): pro
48、vides a package of end-user functions for management of a set of closely related types of network elements. These functions can be divided into two main categories: Element Management Functions and Sub-Network Management Functions. Element Management functions: for management of network elements on
49、an individual basis. These are basically the same functions as supported by the corresponding local terminals. Enterprise Systems: Information Systems that are used in the telecommunication organisation but are not directly or essentially related to the telecommunications aspects (Call Centres, Fraud Detection and Prevention Systems, Invoicing etc). Information Service (IS): Defined in 3GPP TS 32.150 111. Integration Reference Poin
