ETSI TS 132 723-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf

上传人:boatfragile160 文档编号:743362 上传时间:2019-01-11 格式:PDF 页数:12 大小:80.48KB
下载 相关 举报
ETSI TS 132 723-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf_第1页
第1页 / 共12页
ETSI TS 132 723-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf_第2页
第2页 / 共12页
ETSI TS 132 723-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf_第3页
第3页 / 共12页
ETSI TS 132 723-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf_第4页
第4页 / 共12页
ETSI TS 132 723-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf_第5页
第5页 / 共12页
点击查看更多>>
资源描述

1、 ETSI TS 132 723 V9.0.0 (2010-02)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Configuration Management (CM);Repeater network resources Integration Reference Point (IRP);Common Object R

2、equest Broker Architecture (CORBA) Solution Set (SS) (3GPP TS 32.723 version 9.0.0 Release 9)ETSI ETSI TS 132 723 V9.0.0 (2010-02)13GPP TS 32.723 version 9.0.0 Release 9Reference RTS/TSGS-0532723v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +3

3、3 4 92 94 42 00 Fax: +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 avail

4、able in more than one 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

5、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 If you find er

6、rors 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 except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in

7、all media. European Telecommunications Standards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members a

8、nd of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 723 V9.0.0 (2010-02)23GPP TS 32.72

9、3 version 9.0.0 Release 9Intellectual 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 available for ETSI members and non-members, and can be found in ETSI SR 000 31

10、4: “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 server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy,

11、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 become, essential to the present document. Foreword This Technica

12、l 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 interpreted as being references to the corresponding ETSI de

13、liverables. 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 723 V9.0.0 (2010-02)33GPP TS 32.723 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g31 Scope 5g32 Refere

14、nces 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Architectural features . 6g34.1 Notifications . 6g35 Mapping . 7g35.1 General mappings . 7g35.2 Repeater NRM Information Object Class (IOC) mapping . 7g35.2.1 IOC RepeaterFunction 7g36 Rules for management infor

15、mation model extensions . 8g36.1 Allowed extensions 8g36.2 Extensions not allowed . 8g3Annex A (normative): CORBA IDL, NRM definitions 9g3A.1 IDL specification (file name “RepeaterNetworkResourcesNRMDefs.idl“) . 9g3Annex B (informative): Change history . 10g3History 11g3ETSI ETSI TS 132 723 V9.0.0 (

16、2010-02)43GPP TS 32.723 version 9.0.0 Release 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 modi

17、fy 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 where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG

18、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 is incremented when editorial only changes have been incorporated in the document. The present document is part of a TS-fa

19、mily covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.721: “Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Requirements“. 32.722: “Configurati

20、on Management (CM); Repeater network resources Integration Reference Point (IRP); Information Service (IS)“. 32.723: “Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 32.725: “Configurat

21、ion Management (CM); Repeater network resources 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 evolv

22、es. 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 of an implementation prog

23、ramme (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 involving actions on many re

24、sources/objects in one or several NEs. 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 NEs and NRs, and they may be initiated by the

25、operator or by functions in the OSs or NEs. ETSI ETSI TS 132 723 V9.0.0 (2010-02)53GPP TS 32.723 version 9.0.0 Release 91 Scope The purpose of this Repeater Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.722 4) to the protocol specific

26、 details necessary for implementation of this IRP in a CORBA/IDL environment. This Solution Set specification is related to 3GPP TS 32.722. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are eit

27、her 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 (including a GSM document), a n

28、on-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“. 3 3GPP TS 32.600: “Tel

29、ecommunication management; Configuration Management (CM); Concept and high-level requirements“. 4 3GPP TS 32.722: “Telecommunication management; Configuration Management (CM); Repeater Network Resources Model (NRM): Integration Reference Point (IRP): Information Service (IS)“. 5 3GPP TS 32.300: “Tel

30、ecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 6 OMG Notification Service, Version 1.0. 7 OMG CORBA services: Common Object Services Specification, Update: November 22, 1996. 8 The Common Object Request Broker: Architecture and Specification (for spec

31、ification of valid version, see 1). 9 3GPP TS 32.303: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 10 3GPP TS 32.111-3: “Telecommunication management; Fault Manageme

32、nt; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. ETSI ETSI TS 132 723 V9.0.0 (2010-02)63GPP TS 32.723 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For terms and definitions please refer to 3GPP TS 32.

33、101 1, 3GPP TS 32.102 2, 3GPP TS 32.600 3 and 3GPP TS 32.642 4. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CORBA Common Object Request Broker Architecture DN Distinguished Name IS Information Service IDL Interface Definition Language (OMG) IOC Info

34、rmation Object Class IRP Integration Reference Point MO Managed Object MOC Managed Object Class NRM Network Resource Model OMG Object Management Group SS Solution Set 4 Architectural features The overall architectural feature of Repeater Network Resources IRP is specified in 3GPP TS 32.722 4. This c

35、lause specifies features that are specific to the CORBA SS. 4.1 Notifications Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.303 9). ETSI ETSI TS 132 723 V9.0.0 (2010-02)73GPP TS 32.723 version 9.0.0 Release 95 Mapping 5.1 General mappings Attributes modelling ass

36、ociations 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 attribute names in the MOC. When the cardinality for an association is 01 or 11 the datatype for the reference

37、 attribute is defined as a 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 referred MO, the reference attribute will be of type MOReferenceSet, which contains a sequence of MO references. 5.2

38、 Repeater NRM Information Object Class (IOC) mapping 5.2.1 IOC RepeaterFunction Mapping from NRM IOC RepeaterFunction attributes to SS equivalent MOC RepeaterFunction attributes NRM Attributes of IOC RepeaterFunction in 3GPP TS 32.722 4 SS Attributes SS Type Support Qualifier Read Write repeaterFunc

39、tionId repeaterFunctionId string M M - userLabel userLabel stri M priority priority long M M latitude latitude float O Longitude longitude float M M ctrlConnMode ctrlConnMode ctrlConnMode M M M environmentInfo environmentInfo string M M -powerSwitch powerSwitch powerSwitch M M M ulAttenuation ulAtte

40、nuation long M dlAttenuation dlAttenuation long M M firmwareVer firmwareVer string M - repeaterType repeaterType repeaterType M M - repeaterFunction-ExternalUtranCell repeaterFunctionExternalUtranCell GenericNetworkResourcesIRPSystem:AttributeTypes:MOReference M M - ETSI ETSI TS 132 723 V9.0.0 (2010

41、-02)83GPP TS 32.723 version 9.0.0 Release 96 Rules for management information model extensions This clause discusses how the models and IDL definitions provided the present document can be extended for a particular implementation and still remains compliant with 3GPP SA5s specifications. 6.1 Allowed

42、 extensions Vendor-specific IOCs may be supported. The vendor-specific IOCs may support new types of attributes. The 3GPP SA5-specified notifications may be issued referring to the vendor-specific IOCs and vendor-specific attributes. New IOCs shall be distinguishable from 3GPP SA5 IOCs by name. 3GPP

43、 SA5-specified and vendor-specific attributes may be used in vendor-specific IOCs. Vendor-specific attribute names shall be distinguishable from existing attribute names. NRM IOCs may be subclassed. Subclassed IOCs shall maintain the specified behaviour of the 3GPP SA5s superior classes. They may ad

44、d 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 S

45、A5-specified containment rules and their specified cardinality shall still be followed. As an example, ManagementNode (or its subclasses) shall be contained under SubNetwork (or its subclasses). Managed Object Instances may be instantiated as CORBA objects. This requires that the IOCs be represented

46、 in IDL. 3GPP SA5s NRM IOCs are not currently specified in IDL, but may be specified in IDL for instantiation or subclassing purposes. However, management information models should not require that IRPManagers access the instantiated managed objects other than through supported methods in the presen

47、t document. Extension rules related to notifications (Notification categories, Event Types, Extended Event Types etc.) are for further study. 6.2 Extensions not allowed The IDL specifications in the present document cannot be edited or altered. Any additional IDL specifications shall be specified in

48、 separate IDL files. IDL interfaces (note: not IOCs) specified in the present document may not be subclassed or extended. New interfaces may be defined with vendor-specific methods. ETSI ETSI TS 132 723 V9.0.0 (2010-02)93GPP TS 32.723 version 9.0.0 Release 9Annex A (normative): CORBA IDL, NRM defini

49、tions A.1 IDL specification (file name “RepeaterNetworkResourcesNRMDefs.idl“) /File:RepeaterNetworkResourcesNRMDefs.idl #ifndef _REPEATERNETWORKRESOURCESNRMDEFS_IDL_ #define _REPEATERNETWORKRESOURCESNRMDEFS_IDL_ #include “GenericNetworkResourcesNRMDefs.idl“ #pragma prefix “3gppsa5.org“ /* * This module defines constants for each MO class name and * the attribute names for each defined MO class. */ module RepeaterNetworkResourcesNRMDefs /* * Definitions for MO class RepeaterFunction */ interface RepeaterFunction : Generic

展开阅读全文
相关资源
猜你喜欢
相关搜索

当前位置:首页 > 标准规范 > 国际标准 > 其他

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1