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

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

2、sion 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 612 V14.0.0 (2017-04)13GPP TS 32.612 version 14.0.0 Release 14Reference RTS/TSGS-0532612ve00 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

3、 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. The

4、 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 Portable

5、 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.et

6、si.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 Telecommunica

8、tions 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 i

9、s 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 612 V14.0.0 (2017-04)23GPP TS 32.612 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may

10、 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 st

11、andards“, 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 not

12、 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 s

13、pecifications 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 612 V14.0.0 (2017-04)33GPP TS 32.612 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 7g3Introduction 7g31 Scope 8g32 References 8g33 Defini

16、tions and abbreviations . 9g33.1 Definitions 9g33.2 Abbreviations . 11g34 System Overview . 12g34.1 System Context 12g34.2 Compliance rules 13g34.3 Scope of Bulk CM Management Specification 14g35 Modelling approach 14g36 Information Object Classes 14g36.1 Information entities imported and local labe

17、l . 14g36.2 Class diagram . 15g36.2.1 Attributes and relations . 15g36.2.2 Inheritance 15g36.3 Information object classes definition 16g36.3.1 SimpleUploadBulkCMIRP . 16g36.3.1.1 Definition 16g36.3.1.2 Attributes . 16g36.3.1.3 Notifications 16g36.3.2 ControlledUploadBulkCMIRP . 16g36.3.2.1 Definitio

18、n 16g36.3.2.2 Attributes . 16g36.3.2.3 Notifications 16g36.3.3 BulkCMIRP 16g36.3.3.1 Definition 16g36.3.3.2 Attributes . 16g36.3.3.3 Notifications 16g36.4 Void 17g37 Interface Definition 18g37.1 Class Diagram 19g37.1.1 Operations and Notifications for Simple Upload 19g37.1.2 Operations and Notificat

19、ions for Controlled Upload 19g37.1.3 Main Operations and Notifications for Controlled Upload 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, u

20、pdates, 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 System Aspects; Telecommunication mana

21、gement; as identified below: 32.611: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements“. 32.612: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)“. 32.616: “Configuration Management (CM); Bulk CM Integration Ref

22、erence Point (IRP); Solution Set (SS) 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 Networ

23、k Element (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 of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications),

24、 and to maintain the overall Quality of Service. The CM actions are initiated either as a 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 612 V14.0.0 (2017-04)83GPP TS 32.612 version

25、14.0.0 Release 141 Scope The present document (Bulk Configuration Management IRP: Information Service) defines a number of Integration Reference Point (IRP) through which an IRPAgent (typically an Element Manager or Network Element) can communicate bulk Configuration Management related information t

26、o one or several IRPManagers (typically Network Managers). 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 publication, edition number, version number

27、, 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 refers to the latest version of that docum

28、ent 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: “Telecommunication management; Architecture“. 3 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Inte

29、gration Reference Point (IRP): Information Service (IS)“. 4 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 5 3GPP TS 32.642: “Telecommunication management; Configuration Managem

30、ent (CM); UTRAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 6 3GPP TS 32.652: “Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 7 3GPP TS 32.300: “Telecommuni

31、cation management; Configuration Management (CM); Name convention for Managed Objects“. 8 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 9 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) man

32、agement; Information Service (IS)“. 10 3GPP TS 32.632: “Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 11 3GPP TS 32.692 “Inventory Management (IM) network resource Integration Reference Point (IRP

33、): Network Resource Model (NRM)“. 12 3GPP TS 32.742: “Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM)“. 13 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 14 3GPP TS 32.712: “Telecommu

34、nication management; Configuration Management (CM); Transport Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. ETSI ETSI TS 132 612 V14.0.0 (2017-04)93GPP TS 32.612 version 14.0.0 Release 1415 3GPP TS 32.732: “IP Multimedia Subsystem (IMS) Netwo

35、rk Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. 16 3GPP TS 32.172: “Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. 17 3GPP TS 32.722: “Telecommunication manag

36、ement; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); information Service (IS)“. 18 3GPP TS 32.762: “Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP)

37、: Information Service (IS)“. 19 3GPP TS 32.752: “Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. 20 3GPP TS 32.522: “Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource

38、 Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. 21 3GPP TS 32.772: “Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP): Information Service (IS)“. 22 3GPP TS 32.782: “Telecommunication management

39、; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP): Information Service (IS)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. For terms and definitions n

40、ot found here, please refer to 3GPP TS 32.101 1, 3GPP TS 32.102 2 and 3GPP TS 32.600 8. 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 object

41、s. 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 rule. These are specified as separate entities in the object models (UML diagrams). Currently (in R99) however, all

42、 (non-containment) associations are modelled. by means of reference attributes of the participating MOs. Data: is any information or set of information required to give software or equipment or combinations thereof a specific state of functionality. Element Manager (EM): provides a package of end-us

43、er 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. These are basically the same functions as supported by the corresponding local

44、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 functions on the sub-network level (typically in the areas of network topology prese

45、ntation, alarm correlation, service impact analysis and circuit provisioning). Integration Reference Point (IRP): See 3GPP TS 32.150 6. ETSI ETSI TS 132 612 V14.0.0 (2017-04)103GPP TS 32.612 version 14.0.0 Release 14IRP Information Service (IS): See 3GPP TS 32.101 1. IRP Network Resource Model (NRM)

46、: See 3GPP TS 32.101 1. IRP Solution Set (SS): See 3GPP TS 32.101 1. Managed Element (ME): An instance of the Managed Object Class G3ManagedElement/ManagedElement. Managed Object (MO): In the context of the present document, a Managed Object (MO) is a software object that encapsulates the manageable

47、 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 used to characterize the objects that belong to the class (the term “attribute “ is taken from TMN and corresponds to a “propert

48、y “ according to CIM). Furthermore, a MO class can have operations that represent the behaviour relevant for that class (the term “operation “ is taken from TMN and corresponds to a “method “ according to CIM). An MO class may support notifications that provide information about an event occurrence

49、within a network resource. Managed Object Class (MOC): a description of all the common characteristics for a number of MOs, such as their attributes, operations, notifications and behaviour. Managed Object Instance (MOI): an instance of a MOC, which is the same as a MO as described above. 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 , a MIB consist of (1) a Name