ETSI TS 132 602-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Ma.pdf

1、 ETSI TS 132 602 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) (3GPP TS 32.602 ve

2、rsion 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 602 V14.0.0 (2017-04)13GPP TS 32.602 version 14.0.0 Release 14Reference RTS/TSGS-0532602ve00 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 Sire

3、t N 348 623 562 00017 - 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. Th

4、e content of any electronic 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 Portabl

5、e Document Format (PDF) 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 https:/portal.e

6、tsi.org/TB/ETSIDeliverableStatus.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

7、 mechanical, including photocopying 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 Telecommunic

8、ations Standards Institute 2017. 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. oneM2M logo

9、is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 602 V14.0.0 (2017-04)23GPP TS 32.602 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document ma

10、y have been declared to ETSI. The 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 s

11、tandards“, which is available from 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 no

12、t referenced in ETSI SR 000 314 (or 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

13、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 reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp

14、. 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 in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“

15、 are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 602 V14.0.0 (2017-04)33GPP TS 32.602 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Defin

16、itions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 System overview 9g34.1 System Context 9g34.2 Compliance rules 10g35 Modelling approach 10g36 Model 10g36.1 Imported information entities and local labels . 10g36.2 Class diagram . 11g36.2.1 Relationships. 11g36.2.2 Inheritance

17、 11g36.3 Class Definitions . 11g36.3.1 BasicCmIRP 11g36.3.1.1 Definition 11g36.3.2 ManagedEntity . 11g36.3.2.1 Definition 11g36.4 Information relationship definitions . 12g36.4.1 Void 12g37 Interface Definition 12g37.1 Class diagram . 12g37.2 Generic rules 12g37.3 Interface PassiveCmIRPOperations#1

18、. 13g37.3.1 getMoAttributes (M) . 13g37.3.1.1 Definition 13g37.3.1.2 Input Parameters . 13g37.3.1.3 Output Parameters. 14g37.3.1.4 Pre-condition . 14g37.3.1.5 Post-condition . 14g37.3.1.6 Exceptions . 15g37.4 Interface PassiveCmIRPOperations#2 . 15g37.4.1 getContainment (O) 15g37.4.1.1 Definition 15

19、g37.4.1.2 Input Parameters . 15g37.4.1.3 Output Parameters. 16g37.4.1.4 Pre-condition . 16g37.4.1.5 Post-condition . 16g37.4.1.6 Exceptions . 17g37.5 Interface BasicCmIRPOperations . 17g37.5.1 cancelOperation (O) 17g37.5.1.1 Definition 17g37.5.1.2 Input Parameters . 17g37.5.1.3 Output Parameters. 17

20、g37.5.1.4 Pre-condition . 18g3ETSI ETSI TS 132 602 V14.0.0 (2017-04)43GPP TS 32.602 version 14.0.0 Release 147.5.1.5 Post-condition . 18g37.5.1.6 Exceptions . 18g37.6 Interface ActiveCmIRPOperations . 19g37.6.1 createMO (O) . 19g37.6.1.1 Definition 19g37.6.1.2 Input Parameters . 19g37.6.1.3 Output P

21、arameters. 20g37.6.1.4 Pre-condition . 20g37.6.1.5 Post-condition . 20g37.6.1.6 Exceptions . 21g37.6.2 deleteMO (O) . 22g37.6.2.1 Definition 22g37.6.2.2 Input Parameters . 22g37.6.2.3 Output Parameters. 22g37.6.2.4 Pre-condition . 22g37.6.2.5 Post-condition . 23g37.6.2.6 Exceptions . 23g37.6.3 setMO

22、Attributes (O) 23g37.6.3.1 Definition 23g37.6.3.2 Input Parameters . 24g37.6.3.3 Output Parameters. 26g37.6.3.4 Pre-condition . 26g37.6.3.5 Post-condition . 26g37.6.3.6 Exceptions . 27g3Annex A (informative): Change history . 28g3History 29g3ETSI ETSI TS 132 602 V14.0.0 (2017-04)53GPP TS 32.602 vers

23、ion 14.0.0 Release 14Foreword This Technical Specification 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 pre

24、sent 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 information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under ch

25、ange 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 been incorporated in the document. Introduction The present document is part of a TS-family covering

26、 the 3rdGeneration Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.601: “Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements“ 32.602: “Configuration Management (CM); Basic CM Int

27、egration Reference Point (IRP): Information Service (IS)“ 32.606: “Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions“ Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of

28、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 in the Operations Systems (OSs) or NEs. CM actions may be requested as part

29、 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 actions on single NEs of the 3G network, or as part of a complex procedure in

30、volving actions on many resources/objects in one or several NEs. ETSI ETSI TS 132 602 V14.0.0 (2017-04)63GPP TS 32.602 version 14.0.0 Release 141 Scope The present document defines a component of an Integration Reference Point (IRP) through which an IRPAgent (typically an Element Manager or Network

31、Element) can communicate basic Configuration Management related information to one or several IRPManagers (typically Network Managers). The function of this Basic CM IRP Information Service is to define an interface for the retrieval and modification of Configuration Management Information. This Bas

32、ic CM IRP IS is aligned with ITU-T M.3700 15 in that ITU-T M.3700 is a subset of the Basic CM IRP IS in terms of the definitions of operations for the retrieval and modification of Configuration Management Information. 2 References The following documents contain provisions, which, through reference

33、 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, the latest version

34、applies. 1 3GPP TS 32.101: “Telecommunication 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): Informati

35、on Service (IS)“. 4 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 5 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 6 3GPP TS 32.600: “Telecommunicati

36、on management; Configuration Management (CM); Concept and high-level requirements“. 7 ITU-T Recommendation X.710 (1997): “Common Management Information Service“. 8 ITU-T Recommendation X.721 (02/92): “Information Technology - Open Systems Interconnection Structure of Management Information: Definiti

37、on of Management Information“. 9 ITU-T Recommendation X.730 (01/92): “Information Technology - Open Systems Interconnection Systems Management: Object Management Function“. 10 ITU-T Recommendation X.733 (02/92): “Information Technology - Open Systems Interconnection - Alarm Reporting Function“. 11 3

38、GPP TS 32.662: “Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS)“. 12 ITU-T Recommendation X.720: “Information technology - Open Systems Interconnection - Structure of management information: Management information model“. 13 3GPP TS 32.622: “Telecommun

39、ication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. ETSI ETSI TS 132 602 V14.0.0 (2017-04)73GPP TS 32.602 version 14.0.0 Release 1414 3GPP TS 32.150: “Telecommunication management; Integration Reference Point

40、(IRP) Concept and definitions“. 15 ITU-T M.3700 (01/2010): “Telecommunication Management, Including TMN and Network Maintenance; Integrated services digital networks; Common management services Object management Protocol neutral requirements and analysis” 3 Definitions and abbreviations 3.1 Definiti

41、ons For the purposes of the present document, the following terms and definitions apply. For terms and definitions not found here, please refer to 3GPP TS 32.101 1, 3GPP TS 32.102 2 and 3GPP TS 32.600 6. Association: In general it is used to model relationships between Managed Objects. Associations

42、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 through name bindings, but it does not stipulate the implementation for other types of associations as a general

43、 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 participating MOs. Managed Element (ME): An instance of the Managed Object Class G3ManagedElement. Managed O

44、bject (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 MO is instance of a MO class defined in a MIM/NRM. An MO class has attributes that provide information u

45、sed 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 that provide information about an event occurrence within a network resource. Management Information Base

46、 (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 Name space (describing the MO containment hierarchy in the MIB through Distinguished Names), (2) a numbe

47、r 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

48、 MIB definition. Figure 3.1 depicts the relationships between a Name space and a number of participating MOs (the shown association is of a non-containment type) MONamespace (containment hierarhy)AssociationMIBFigure 3.1: Relationships between a Name space and a number of participating MOs ETSI ETSI

49、 TS 132 602 V14.0.0 (2017-04)83GPP TS 32.602 version 14.0.0 Release 14Management Information Model (MIM): Also referred to as NRM see the definition below. Name space: A name space is a collection of names. The IRP name convention (see 3GPP TS 32.300 5) restricts the name space to a hierarchical containment structure, including its simplest form - the one-level, flat name space. All Managed Objects in a MIB shall be included in the corresponding name space and the MIB/name space shall only support a strict hierarchical c