1、 ETSI TS 132 661 V14.0.0 (2017-05) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Kernel CM Requirements (3GPP TS 32.661 version 14.0.0 Release 14) TECHNICAL SPECIFICATI
2、ON ETSI ETSI TS 132 661 V14.0.0 (2017-05)13GPP TS 32.661 version 14.0.0 Release 14Reference RTS/TSGS-0532661ve00 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
3、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/or print versi
4、ons 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 kept on a spec
5、ific 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.aspx If you f
6、ind 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 photocopying and microf
7、ilm 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 2017. All rights re
8、served. 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. oneM2M logo is protected for the benefit of its Members GS
9、M and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 661 V14.0.0 (2017-05)23GPP TS 32.661 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
10、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 available from the ETSI Se
11、cretariat. Latest 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 update
12、s 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 specifications or reports using their 3GPP ide
13、ntities, 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. Modal verbs terminology In the present docum
14、ent “shall“, “shall not“, “should“, “should 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 w
15、hen used in direct citation. ETSI ETSI TS 132 661 V14.0.0 (2017-05)33GPP TS 32.661 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions
16、5g33.3 Abbreviations . 6g34 Requirements 8g34.1 General Requirements 8g34.2 Kernel CM Requirements . 8g3Annex A (informative): Change history . 9g3History 10g3ETSI ETSI TS 132 661 V14.0.0 (2017-05)43GPP TS 32.661 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the
17、 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 document, it will be re-released by the TSG with an identifying change of rele
18、ase 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 control. y the second digit is incremented for all changes of substance, i.e.
19、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 TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and
20、System Aspects; Telecommunication management; as identified below: 32.661 Configuration Management (CM); Kernel CM Requirements 32.662 Configuration Management (CM); Kernel CM Information Service (IS) 32.666: Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (S
21、S) definitions Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resource
22、s (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs. CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality
23、 of Service (QoS). The CM actions are initiated either as single actions on single NEs of the 3G network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs. ETSI ETSI TS 132 661 V14.0.0 (2017-05)53GPP TS 32.661 version 14.0.0 Release 141 Scope The pr
24、esent document defines, in addition to the requirements defined in 1, 2 and 3, the requirements for the present IRP: Kernel Configuration Management IRP. It is the intent of Kernel Configuration Management to provide an IRP that contains the configuration management functionality that is basic and m
25、inimal. It is the functionality that is common to and required by both Basic CM and Bulk CM. While neither the Basic CM IRP nor Bulk CM IRP requires the other, they each require the Kernel CM IRP. 2 References The following documents contain provisions which, through reference in this text, constitu
26、te 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, the latest version applies. In the case of
27、 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 level requirements“. 2 3GPP TS 32.102: “Tele
28、communication management; Architecture“. 3 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 4 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP):
29、Network Resource Model (NRM)“. 5 3GPP TS 32.632: “Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 6 3GPP TS 32.642: “Telecommunication management; Configuration Management (CM): UTRAN network resour
30、ces Integration Reference Point (IRP): Network Resource Model (NRM)“. 7 3GPP TS 32.652: “Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 8 3GPP TS 32.662: “Telecommunication management; Configurati
31、on Management (CM); Kernel CM Information Service (IS)“. 9 3GPP TS 32.742: “Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) Interface Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. 3 Definitions and abbreviat
32、ions 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: data: any information or set of information required to give software or equipment or combinations thereof a specific state of functionality ETSI ETSI TS 132 661 V14.0.0 (2017-05)63GPP TS 32.661
33、 version 14.0.0 Release 14Element Manager (EM): provides a package of end-user functions for management of a set of closely related types of Network Elements (NEs). These functions can be divided into two main categories: Element Management Functions for management of NEs on an individual basis. The
34、se are basically the same functions as supported by the corresponding local terminals. Sub-Network Management Functions that are related to a network model for a set of NEs constituting a clearly defined sub-network, which may include relations between the NEs. This model enables additional function
35、s on the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisioning). IRP: See 3GPP TS 32.101 1. IRP Information Model: See 3GPP TS 32.101 1. IRP Information Service: See 3GPP TS 32.101 1. IRP Solution Set: See 3GPP
36、 TS 32.101 1. Managed Object (MO): abstract entity, which may be accessed through an open interface between two or more systems, and representing a Network Resource (NR) for the purpose of management. The Managed Object (MO) is an instance of a Managed Object Class (MOC) as defined in a Management I
37、nformation Model (MIM). The MIM does not define how the MO or NR is implemented; only what can be seen in the interface. Managed Object Class (MOC): description of all the common characteristics for a number of MOs, such as their attributes, operations, notifications and behaviour Managed Object Ins
38、tance (MOI): instance of a MOC, which is the same as a MO as described above Management Information Base (MIB): set of existing managed objects in a management domain, together with their attributes, constitutes that management domains MIB. The MIB may be distributed over several OS/NEs. Management
39、Information Model (MIM): also referred to as NRM see the definition below. There is a slight difference between the meaning of MIM and NRM the term MIM is generic and can be used to denote any type of management model, while NRM denotes the model of the actual managed telecommunications Network Reso
40、urces (NRs). Network Element (NE): discrete telecommunications entity, which can be, managed over a specific interface e.g. the RNC Network Manager (NM): provides a package of end-user functions with the responsibility for the management of a network, mainly as supported by the EM(s) but it may also
41、 involve direct access to the NEs. All communication with the network is based on open and well-standardised interfaces supporting management of multi-vendor and multi-technology NEs. Network Resource (NR): component of a NE, which can be identified as a discrete separate entity and is in an object
42、oriented environment for the purpose of management represented by an abstract entity called Managed Object (MO) Network Resource Model (NRM): model representing the actual managed telecommunications Network Resources (NRs) that a System is providing through the subject IRP. An NRM describes Managed
43、Object Classes (MOC), their associations, attributes and operations. The NRM is also referred to as “MIM“ (see above) which originates from the ITU-T TMN. Object Management Group (OMG): See http:/www.omg.org. Operations System (OS): indicates a generic management system, independent of its location
44、level within the management hierarchy 3.3 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management EM Element Manager FM Fault ManagementETSI ETSI TS 132 661 V14.0.0 (2017-05)73GPP TS 32.661 version 14.0.0 Release 14IRP Integration Refere
45、nce Point IS Information Service (see 3GPP TS 32.101 1) ITU-T International Telecommunication Union, Telecommunication Standardisation Sector MIB Management Information Base MIM Management Information Model MOC Managed Object Class MOI Managed Object Instance NE Network Element NM Network ManagerNR
46、Network Resource NRM Network Resource Model OMG Object Management Group OS Operations System PM Performance Management TM Telecom ManagementUML Unified Modelling Language (OMG) UMTS Universal Mobile Telecommunications System ETSI ETSI TS 132 661 V14.0.0 (2017-05)83GPP TS 32.661 version 14.0.0 Releas
47、e 144 Requirements 4.1 General Requirements This requirements specification defines requirements for the IS for this IRP. As such, capabilities specified here as being required in the IS are not necessarily required in the product implementation. That which is required in the product implementation
48、will be specified in the IS itself. The following general and high-level requirements apply for the present IRP: A. IRP-related requirements in 3GPP TS 32.101 1. B. IRP-related requirements in 3GPP TS 32.102 2. C. IRP-related requirements in 3GPP TS 32.600 3. In addition to the above, the following
49、more specific requirements apply: 1. The IS defined by this IRP shall enable an NM to operate on (access) any NRMs defined in any NRM IRPs, such as those defined in 4, 5, 6, 7 and 8. 2. The IS defined by this IRP shall as far as possible be independent of any specific definitions of MOCs, attributes etc. in the NRMs referred to in item 1. 4.2 Kernel CM Requirements The IS defined by this IRP shall include the following operations that may be invoked by the IRP Manager to retrieve management information from the IRPAgent:
