1、 ETSI TS 132 653 V9.2.0 (2012-01) Digital cellular telecommunications system (Phase 2+); Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) (3GPP TS 32.653 version
2、 9.2.0 Release 9) GLOBAL SYSTEM FOR MOBILE COMMUNICATIONSRTechnical Specification ETSI ETSI TS 132 653 V9.2.0 (2012-01)13GPP TS 32.653 version 9.2.0 Release 9Reference RTS/TSGS-0532653v920 Keywords GSM ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +
3、33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one
4、electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
5、 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 If you find errors in the present do
6、cument, 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 except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Te
7、lecommunications Standards Institute 2012. 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. GS
8、M and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 653 V9.2.0 (2012-01)23GPP TS 32.653 version 9.2.0 Release 9Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information per
9、taining 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 Secre
10、tariat. Latest updates are available on the ETSI Web server (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
11、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 identiti
12、es, 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. ETSI ETSI TS 132 653 V9.2.0 (2012-01)33GPP TS 32.
13、653 version 9.2.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Architectural features . 6g34.1 Notifications . 6g35 Mapping . 6g35.1 General ma
14、ppings . 6g35.2 GERAN NRM Information Object Class (IOC) mapping 6g35.2.1 IOC BssFunction 6g35.2.2 IOC BtsSiteMgr 6g35.2.3 IOC GsmCell 7g35.2.4 IOC GsmRelation . 7g35.2.5 IOC ExternalGsmCell . 8g35.2.6 IOC ExternalBssFunction . 8g36 Rules for management information model extensions . 8g36.1 Allowed
15、extensions 8g36.2 Extensions not allowed . 9g3Annex A (normative): CORBA IDL, NRM Definitions 10g3A.1 IDL specification (file name “GeranNetworkResourcesNRMDefs.idl“) . 10g3Annex B (informative): Change history . 12g3History 13g3ETSI ETSI TS 132 653 V9.2.0 (2012-01)43GPP TS 32.653 version 9.2.0 Rele
16、ase 9Foreword 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, i
17、t 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 change control. y
18、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 the 3rdGenerati
19、on Partnership 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 re
20、sources Integration 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
21、 Integration Reference 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 an
22、d monitor the actual configuration on the NEs and NRs, and they may be initiated by the operator or functions in the 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 mainta
23、in the overall Quality of Service (QoS). The CM actions are initiated either as a single action on a Network Element (NE) of the 3G-network or as part of a complex procedure involving actions on many NEs. The Itf-N interface for Configuration Management is built up by a number of Integration Referen
24、ce Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 1 and 3GPP TS 32.102 2.For CM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as other tech
25、nical specifications for telecom management produced by 3GPP. ETSI ETSI TS 132 653 V9.2.0 (2012-01)53GPP TS 32.653 version 9.2.0 Release 91 Scope The purpose of this GERAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.652 4) to the pr
26、otocol specific details necessary for implementation of this IRP in a CORBA/IDL environment. This Solution Set specification is related to 3GPP TS 32.652 V9.2.X. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present docume
27、nt. 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 (includin
28、g 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; Architecture“.
29、3 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 4 3GPP TS 32.652: “Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 5 3GPP TS 32
30、.303: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 6 3GPP TS 32.111-3: “Telecommunication management; Fault Management (FM); Part 3: Alarm Integration Reference Poin
31、t (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 3 Definitions and abbreviations 3.1 Definitions For terms and definitions refer to TS 32.101 1, TS 32.102 2, TS 32.600 3 and TS 32.652 4. 3.2 Abbreviations For the purposes of the present document, the following abbreviat
32、ions apply: CORBA Common Object Request Broker Architecture DN Distinguished Name IS Information Service IDL Interface Definition Language IOC Information Object Class IRP Integration Reference Point ETSI ETSI TS 132 653 V9.2.0 (2012-01)63GPP TS 32.653 version 9.2.0 Release 9MO Managed Object MOC Ma
33、naged Object Class NRM Network Resource Model SS Solution Set 4 Architectural features The overall architectural feature of GERAN Network Resources IRP is specified in TS 32.652 4. This clause specifies features that are specific to the CORBA SS. 4.1 Notifications Notifications are sent according to
34、 the Notification IRP: CORBA SS (see TS 32.303 5). 5 Mapping 5.1 General mappings Attributes modelling associations as defined in the NRM (here also called “reference attributes“) are in this SS mapped to attributes. The names of the reference attributes in the NRM are mapped to the corresponding at
35、tribute names in the MOC. When the cardinality for an association is 01 or 11 the datatype for the reference attribute is defined as an MOReference. The value of an MO reference contains the distinguished name of the associated MO. When the cardinality for an association allows more than one referre
36、d MO, the reference attribute will be of type MOReferenceSet, which contains a sequence of MO references. 5.2 GERAN NRM Information Object Class (IOC) mapping 5.2.1 IOC BssFunction Table 5.1: Mapping from NRM IOC BssFunction attributes to SS equivalent MOC BssFunction attributes NRM Attributes of IO
37、C BssFunction in TS 32.652 4 SS Attributes SS Type Support Qualifier Read Write bssFunctionId bssFunctionId string M M -userLabel userLabel string M M M5.2.2 IOC BtsSiteMgr Table 5.2: Mapping from NRM IOC BtsSiteMgr attributes to SS equivalent MOC BtsSiteMgr attributes NRM Attributes of IOC BtsSiteM
38、gr in TS 32.652 4 SS Attributes SS Type Support Qualifier Read Write btsSiteMgrId btsSiteMgrId string M M - userLabel userLabel string M M M latitude latitude long O M Mlongitude longitude long O M MoperationalState operationalState StateManagementIRPOptConstDefs:OperationalStateTypeOpt O M - ETSI E
39、TSI TS 132 653 V9.2.0 (2012-01)73GPP TS 32.653 version 9.2.0 Release 95.2.3 IOC GsmCell Table 5.3: Mapping from NRM IOC GsmCell attributes to SS equivalent MOC GsmCell attributes NRM Attributes of IOC GsmCell in TS 32.652 4 SS Attributes SS Type Support Qualifier Read Write gsmCellId gsmCellId strin
40、g M M -userLabel userLabel string M M M cellIdentity cellIdentity long M M McellAllocation cellAllocation GenericNetworkResourcesIRPSystem:AttributesTypes:LongSet M M M ncc ncc long M M M bcc bcc long M M Mlac lac long M M M mcc mcc longmnc mnc long M M M rac rac long O M M racc racc long M Mtsc tsc
41、 long M M M rxLevAccessMin rxLevAccessMin long M M M msTxPwrMaxCCH msTxPwrMaxCCH long M M MhoppingSequenceList hoppingSequenceList genericGERANNRMAttributeTypes: HoppingSequenceListType M M M plmnPermitted plmnPermitted long M M M 5.2.4 IOC GsmRelation Table 5.4: Mapping from NRM IOC GsmRelation att
42、ributes to SS equivalent MOC GsmRelation attributes NRM Attributes of IOC GsmRelation in TS 32.652 4 SS Attributes SS Type Support Qualifier Read Write gsmRelationId gsmRelationId string M M - adjacentCell adjacentCell string M M MbcchFrequency bcchFrequency long O M - ncc ncc long O Mbcc bcc long O
43、 Mlac lac long O M - isHOAllowed isHOAllowed boolean CM M M isRemoveAllowed isRemoveAllowed boolean CM M MNOTE 1: For all support qualifiers with the value CM see attribute constraints in TS 32.652 4. ETSI ETSI TS 132 653 V9.2.0 (2012-01)83GPP TS 32.653 version 9.2.0 Release 95.2.5 IOC ExternalGsmCe
44、ll Table 5.5: Mapping from NRM IOC ExternalGsmCell attributes to SS equivalent MOC ExternalGsmCell attributes NRM Attributes of IOC ExternalGSMCell in TS 32.652 4 SS Attributes SS Type Support Qualifier Read Write externalGsmCellId externalGsmCellId string M M - userLabel userLabel string M M McellI
45、dentity cellIdentity long M M MbcchFrequency bcchFrequency long M M M ncc ncc long M M Mbcc bcc long M M Mlac lac long M M M mcc mcc longmnc mn longrac rac long O M Mracc c long M M5.2.6 IOC ExternalBssFunction Table 5.6: Mapping from NRM IOC ExternalBssFunction attributes to SS equivalent MOC Exter
46、nalBssFunction attributes NRM Attributes of IOC ExternalBssFunction in TS 32.652 4 SS Attributes SS Type Support Qualifier Read Write externalBssFunctionId externalBssFunctionId string M M - userLabel userLabel string M M M6 Rules for management information model extensions This clause discusses how
47、 the models and IDL definitions provided in the present document can be extended for a particular implementation, and still remain compliant with 3GPP SA5“s specifications. 6.1 Allowed extensions Vendor-specific IOCs may be supported. The vendor-specific IOCs may support new types of attributes. The
48、 3GPP SA5-specified notifications may be issued referring to the vendor-specific IOCs and vendor-specific attributes. New MOCs shall be distinguishable from 3GPP SA5 IOCs by name. 3GPP SA5-specified and vendor-specific attributes may be used in vendor-specific IOCs. Vendor-specific attribute names s
49、hall be distinguishable from existing attribute names. NRM IOCs may be subclassed. Subclassed IOCs shall maintain the specified behaviour of the 3GPP SA5“s superior classes. They may add vendor-specific behaviour with vendor-specific attributes. When subclassing, naming attributes cannot be changed. The subclassed IOC shall support all attributes of its superior class. Vendor-specific attributes cannot be added to 3GPP SA5 NRM IOCs without subclassing. When subclassing, the 3GPP SA5-specified containment rules and their
