1、 ETSI TS 132 662 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 Information Service (IS) (3GPP TS 32.662 version 14.0.0 Release 14) TECHNICAL
2、 SPECIFICATION ETSI ETSI TS 132 662 V14.0.0 (2017-05)13GPP TS 32.662 version 14.0.0 Release 14Reference RTS/TSGS-0532662ve00 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/or
4、 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 ke
5、pt 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.a
6、spx 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 photocopyin
7、g 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 2017. A
8、ll 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. oneM2M logo is protected for the benefit of it
9、s Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 662 V14.0.0 (2017-05)23GPP TS 32.662 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The
10、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 available from
11、 the ETSI Secretariat. 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 (o
12、r 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 specifications or reports using th
13、eir 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. Modal verbs terminology In the p
14、resent document “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 deliverab
15、les except when used in direct citation. ETSI ETSI TS 132 662 V14.0.0 (2017-05)33GPP TS 32.662 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1
16、Definitions 7g33.2 Abbreviations . 8g34 System overview 9g34.1 System Context 9g34.2 Compliance rules 9g35 Modelling approach 10g36 Information Object Classes (IOCs) 10g36.1 Imported Information entities and local labels . 10g36.2 Class diagram . 10g36.2.1 Attributes and relationships 10g36.2.2 Inhe
17、ritance 10g36.3 Information Object Class Definitions . 11g36.3.1 KernelCmIRP . 11g36.3.1.1 Definition 11g36.3.2 ManagedEntity 11g36.3.2.1 Definition 11g36.4 Information relationship definitions . 11g36.4.1 containment (M) . 11g36.4.1.1 Definition 11g36.4.1.2 Role . 11g36.4.1.3 Constraint 11g37 Inter
18、face Definition 12g37.1 Class diagram . 12g37.2 Generic rules 12g37.3 Interface KernelCmIRPOperations. 13g37.3.1 Operation getNRMIRPVersion (M) 13g37.3.1.1 Definition 13g37.3.1.2 Input parameters 13g37.3.1.3 Output parameters . 13g37.3.1.4 Pre-condition . 13g37.3.1.5 Post-condition . 13g37.3.1.6 Exc
19、eptions . 14g37.4 Interface KernelCmIRPNotifications_1 . 15g37.4.1 notifyObjectCreation (O) 15g37.4.1.1 Definition 15g37.4.1.2 Input Parameters . 15g37.4.1.3 Triggering Event . 16g37.4.1.3.1 From-state 16g37.4.1.3.2 To-state 16g37.5 Interface KernelCmIRPNotifications_2 . 16g37.5.1 notifyObjectDeleti
20、on (O) 16g37.5.1.1 Definition 16g37.5.1.2 Input Parameters . 16g3ETSI ETSI TS 132 662 V14.0.0 (2017-05)43GPP TS 32.662 version 14.0.0 Release 147.5.1.3 Triggering Event . 16g37.5.1.3.1 From-state 16g37.5.1.3.2 To-state 17g37.6 Interface KernelCmIRPNotifications_3 . 17g37.6.1 notifyAttributeValueChan
21、ge (O) 17g37.6.6.1 Definition 17g37.6.6.2 Input Parameters . 17g37.6.6.3 Triggering Event . 17g37.6.6.3.1 From-state 17g37.6.6.3.2 To-state 18g37.7 Interface KernelCmIRPNotifications_4 . 19g37.7.1 notifyCMSynchronizationRecommended (O) 19g37.7.1.1 Definition 19g37.7.1.2 Input Parameters . 20g37.7.1.
22、3 Triggering Event . 20g37.7.1.3.1 From-state 20g37.7.1.3.2 To-state 20g37.8 Interface KernelCmIRPNotifications_5 . 21g37.8.1 notifyStateChange (O) 21g37.8.1.1 Definition 21g37.8.1.2 Input parameters 21g37.8.1.3 Triggering Event . 21g37.8.1.3.1 From-state 21g37.8.1.3.2 To-state 21g3Annex A (normativ
23、e): Notification/Event Types . 22g3Annex B (informative): Change history . 23g3History 24g3ETSI ETSI TS 132 662 V14.0.0 (2017-05)53GPP TS 32.662 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the prese
24、nt 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 release date and an increase in version number as follows: Version x.y.z
25、 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. technical enhancements, corrections, updates, etc. z the third digit
26、 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 System Aspects; Telecommunication management; as identified below: 3
27、2.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 (SS) definitions Configuration Management (CM), in general, provides t
28、he 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 Resources (NRs), and they may be initiated by the operator or by functions i
29、n 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 of Service (QoS). The CM actions are initiated either as single act
30、ions 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 662 V14.0.0 (2017-05)63GPP TS 32.662 version 14.0.0 Release 141 Scope The present document defines Integration Reference Point (IRP) through whi
31、ch an IRPAgent (typically an Element Manager or Network Element) can communicate Configuration Management related information to one or several IRPManagers (typically Network Managers). The function of this Kernel CM IRP Information Service is to define an interface that provides the essential CM se
32、rvices. While it is not expected that the Kernel CM IRP alone will provide adequate CM capability, The Kernel CM IRP is expected to provide the common supporting capability required for other IRPs such as the Basic CM IRP or the Bulk CM IRP, each of which require the Kernel CM IRP. 2 References The
33、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, version number, etc.) or non-specific. - For a specific reference, subsequent revisions d
34、o 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 that document in the same Release as the present document. 1 3GPP TS 32.101: “Telecom
35、munication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 4 3GPP TS 32.312:
36、 “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 5 Void. 6 3GPP TS 32.672: “Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Information Service (IS)“. 7 ITU-T Recommendati
37、on X.710 (1997): “Information technology - Open Systems Interconnection - Common Management Information Service“. 8 ITU-T Recommendation X.721 (1992): “Information technology - Open Systems Interconnection - Structure of Management Information: Definition of management information“. 9 ITU-T Recommen
38、dation X.730 (1992): “Information technology - Open Systems Interconnection - Systems Management: Object Management Function“. 10 ITU-T Recommendation X.733 (1992): “Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function“. 11 - 12 Void. 13 3GPP TS 32.300
39、: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 14 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 15 ITU-T Recommendation X.720: “Information technology - Open Systems Interconn
40、ection - Structure of management information: Management information model“. ETSI ETSI TS 132 662 V14.0.0 (2017-05)73GPP TS 32.662 version 14.0.0 Release 1416 3GPP TS 32.623: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Co
41、mmon Object Request Broker Architecture (CORBA) Solution Set (SS)“. 17 3GPP TS 32.643: “Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 18 3GPP TS 32.642: “Te
42、lecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 19 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 20 3GPP TS 32.311: “Telecommunication man
43、agement; Generic Integration Reference Point (IRP) management: Requirements. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. For terms and definitions not found here, please refer to TS 32.101 1, TS 32.102 2 and TS
44、32.600 14. association: In general it is used to model relationships between Managed Objects. Associations can be implemented in several ways, such as: (1) name bindings, (2) reference attributes, and (3) association objects. This IRP stipulates that containment associations shall be expressed throu
45、gh name bindings, but it does not stipulate the implementation for other types of associations as a general rule. These are specified as separate entities in the object models (UML diagrams). Currently however, all (non-containment) associations are modelled by means of reference attributes of the p
46、articipating MOs. Managed Element (ME): instance of the Managed Object Class G3ManagedElement Managed Object (MO): In the context of the present document, a Managed Object (MO) is a software object that encapsulates the manageable characteristics and behaviour of a particular Network Resource. The M
47、O is instance of a MO class defined in a MIM/NRM. An MO class has attributes that provide information used to characterize the objects that belong to the class. Furthermore, an MO class can have operations that represent the behaviour relevant for that class. An MO class may support notifications th
48、at provide information about an event occurrence within a network resource. Management Information Base (MIB): A MIB is an instance of an NRM and has some values on the defined attributes and associations specific for that instance. In the context of the present document, an MIB consists of: (1) a N
49、ame space (describing the MO containment hierarchy in the MIB through Distinguished Names), (2) a number of Managed Objects with their attributes, and (3) a number of Associations between these MOs. Also note that TMN (ITU-T Recommendation X.710 7) defines a concept of a Management Information Tree (also known as a Naming Tree) that corresponds to the name space (containment hierarchy) portion of this MIB definition. Figure 3.1 depicts the relationships between a Name space and a number of participating MOs (the shown associ
