1、 ETSI TS 132 652 V12.0.0 (2014-10) Digital cellular telecommunications system (Phase 2+); Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) (3GPP TS 32.652 version 12.0.0 Release 12) GLOBAL SYSTEM FOR
2、MOBILE COMMUNICATIONSRTECHNICAL SPECIFICATION ETSI ETSI TS 132 652 V12.0.0 (2014-10)13GPP TS 32.652 version 12.0.0 Release 12Reference RTS/TSGS-0532652vc00 Keywords GSM 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
3、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 The present document may be made available in electronic versions and/or in print. The content of any electronic a
4、nd/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 Document Format (PDF) versi
5、on 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 http:/portal.etsi.org/tb/status/status.asp I
6、f you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfi
7、lm 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 2014. All rights res
8、erved. 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. GSM and the GSM logo are Trade Marks registered and owned b
9、y the GSM Association. ETSI ETSI TS 132 652 V12.0.0 (2014-10)23GPP TS 32.652 version 12.0.0 Release 12Intellectual 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 a
10、vailable 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 Secretariat. Latest updates are available on the ETSI Web s
11、erver (http:/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 beco
12、me, 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 identities, UMTS identities or GSM identities. These should be
13、 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 document “shall“, “shall not“, “should“, “should not“, “may“, “m
14、ay not“, “need“, “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 when used in direct citation. ETSI ETSI T
15、S 132 652 V12.0.0 (2014-10)33GPP TS 32.652 version 12.0.0 Release 12Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 System overv
16、iew 9g34.1 Void 9g34.2 Compliance rules 9g35 Modelling approach 9g36 Information Object Classes 9g36.1 Imported information entities and local labels . 9g36.2 Class diagram . 10g36.2.1 Attributes and relationships 10g36.2.2 Inheritance 12g36.3 Information object class definitions . 12g36.3.1 BssFunc
17、tion 12g36.3.1.1 Definition 12g36.3.1.2 Attributes . 12g36.3.2 BtsSiteMgr 12g36.3.2.1 Definition 12g36.3.2.2 Attributes . 13g36.3.3 GsmCell . 13g36.3.3.1 Definition 13g36.3.3.2 Attributes . 13g36.3.3.3 Attribute constraints 13g36.3.4 GsmRelation . 13g36.3.4.1 Definition 13g36.3.4.2 Attributes . 14g3
18、6.3.4.3 Attribute constraints 14g36.3.5 ExternalGsmCell . 14g36.3.5.1 Definition 14g36.3.5.2 Attributes . 15g36.3.5.3 Attribute constraints 15g36.3.6 ExternalBssFunction . 15g36.3.6.1 Definition 15g36.3.6.2 Attributes . 15g36.3.6.3 Attribute constraints 15g36.4 Information relationship definitions .
19、 15g36.4.1 ExternalGsmNeighbourCellRelation (M) . 15g36.4.1.1 Definition 15g36.4.1.2 Roles . 15g36.4.1.3 Constraints 16g36.4.2 GsmNeighbourCellRelation (M) 17g36.4.2.1 Definition 17g36.4.2.2 Roles . 17g36.4.2.3 Constraints 17g3ETSI ETSI TS 132 652 V12.0.0 (2014-10)43GPP TS 32.652 version 12.0.0 Rele
20、ase 126.5 Information attribute definitions . 18g36.5.1 Definition and legal values . 18g36.5.2 Constraints 19g36.6 Common Notifications . 19g36.7 Void 20g3Annex A (informative): Change history . 21g3History 22g3ETSI ETSI TS 132 652 V12.0.0 (2014-10)53GPP TS 32.652 version 12.0.0 Release 12Foreword
21、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 present document, it will be re-r
22、eleased 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 change control. y the second dig
23、it 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 the 3rdGeneration Partnership
24、 Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.651: Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Requirements 32.652: Configuration Management (CM); GERAN network resources Integr
25、ation Reference Point (IRP): Network Resource Model (NRM) 32.653: Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) 32.655: Configuration Management (CM); GERAN network resources Integration R
26、eference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition 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
27、actual configuration on the Network Elements (NEs) and Network Resources, 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 pr
28、ogramme (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 involving actions on many resources/objects in one or several NEs. ETSI ETSI TS 132 652 V12.0.0
29、 (2014-10)63GPP TS 32.652 version 12.0.0 Release 121 Scope The present document specifies the GERAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes. This document specifies the semantics and behaviour of informa
30、tion object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present do
31、cument. 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 a reference to a 3GPP document (incl
32、uding 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: “Telecommunication management; Architectur
33、e“. 3 3GPP TS 24.008: “Mobile radio interface Layer 3 specification; Core network protocols; Stage 3“. 4 3GPP TS 44.018: “Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol“. 5 3GPP TS 45.008: “Radio subsystem link control“. 6 3GPP TS 45.002: “Multiplexing and multip
34、le access on the radio path“. 7 ITU-T Recommendation X.710 (1991): “Common Management Information Service Definition for CCITT Applications“. 8 3GPP TS 23.003: “Numbering, Addressing and Identification“. 9 3GPP TS 32.672: “Telecommunication management; Configuration Management (CM); State Management
35、 Integration Reference Point (IRP): Information Service (IS)“. 10 Void. 11 3GPP TS 32.111-2: “Telecommunication management; Fault Management (FM); Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 12 Void 13 3GPP TS 32.300: “Telecommunication management; Configuration Manag
36、ement (CM); Name convention for Managed Objects“. 14 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 15 Void. 16 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Ref
37、erence Point (IRP): Network Resource Model (NRM)“. ETSI ETSI TS 132 652 V12.0.0 (2014-10)73GPP TS 32.652 version 12.0.0 Release 1217 3GPP TS 32.602: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Information Service (IS)“. 18 3GPP TS 32.612:
38、“Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)“. 19 3GPP TS 32.642: “ Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM
39、) “. 20 3GPP TS 23.002: “Network architecture“. 21 3GPP TS 32.792: “Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) “. 22 3GPP TS 32.762: “Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-U
40、TRAN) 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 not found here, please refer to 3GPP TS 32.1
41、01 1, 3GPP TS 32.102 2 and 3GPP TS 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 as
42、sociations 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). Managed Element (ME): An instance of the IOC ManagedElement, defined in 3
43、GPP TS 32.622 16. 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 MO is instance of a class defined in a MIM/NRM. This class, called Informatio
44、n Object Class (IOC) 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 “property“ according to CIM). Furthermore, the IOC can have operations that represent the behaviour relevant for that cl
45、ass (the term “operation“ is taken from TMN and corresponds to a “method“ according to CIM). The IOC may support the emission of notifications that 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
46、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 number of IOCs with their attributes and (3) a number of
47、Associations between these IOCs. 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
48、a Name space and a number of participating MOs (the shown association is of a non-containment type). ETSI ETSI TS 132 652 V12.0.0 (2014-10)83GPP TS 32.652 version 12.0.0 Release 12MO Namespace (containment hierarchy) Association MIB Figure 3.1: Relationships between a Name space and a number of part
49、icipating MOs Management 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 13) 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 containment structure (with one root object). A
