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

《ETSI TS 132 603-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 603-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf（23页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 603 V9.1.0 (2010-10)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Configuration Management (CM);Basic CM Integration Reference Point (IRP);Common Object Request Broker Arch

2、itecture (CORBA)Solution Set (SS) (3GPP TS 32.603 version 9.1.0 Release 9)ETSI ETSI TS 132 603 V9.1.0 (2010-10)13GPP TS 32.603 version 9.1.0 Release 9Reference RTS/TSGS-0532603v910 Keywords GSM, LTE, UMTS 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 o

4、ne 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 dr

5、ive 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

6、 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 all media. European

7、 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 and of the 3GPP Orga

8、nizational 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 603 V9.1.0 (2010-10)23GPP TS 32.603 version 9.1.0 Rel

9、ease 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 314: “Intellectual Pr

10、operty 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, no investigation, i

11、ncluding 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 Technical Specification (TS

12、) 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 deliverables. The cro

13、ss reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 603 V9.1.0 (2010-10)33GPP TS 32.603 version 9.1.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 Reference

14、s 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 IRP document version number string . 6g35 Architectural features . 6g35.1 Filter language 6g35.2 Syntax for Distinguished Names and Versions 6g36 Mapping . 7g36.1 General mappings . 7g36.2 Operation mapping . 7g36.

15、3 Operation parameter mapping 7g37 Void 10g3Annex A (normative): CORBA IDL, Access Protocol 11g3A.1 IDL specification (file name “BasicCMIRPConstDefs.idl“) 11g3A.2 IDL specification (file name “BasicCMIRPSystem.idl“) . 15g3Annex B (informative): Change history . 21g3History 22g3ETSI ETSI TS 132 603

16、V9.1.0 (2010-10)43GPP TS 32.603 version 9.1.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

17、TSG modify 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 indica

18、tes TSG 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. Introduction The present docume

19、nt is part of a TS-family covering 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: “Configura

20、tion Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS)“ 32.603: “Configuration Management (CM); Basic CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)“ 32.607: “Configuration Management (CM); Basic CM Integr

21、ation Reference Point (IRP); SOAP Solution Set (SS)“ 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 Netwo

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

23、), 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 603 V9.1.0 (2010-10)53GPP TS 32.603 ve

24、rsion 9.1.0 Release 91 Scope The purpose of this Basic Configuration Management (CM) IRP: CORBA Solution Set is to define the mapping of the Basic CM IRP: IS (see 3GPP TS 32.602 4) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment. This document def

25、ines NRM independent data types and methods. This Solution Set specification is related to 3G TS 32.602 V8.1.X. 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

26、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 non-specific reference implic

27、itly 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: “Telecommunication management; C

28、onfiguration Management (CM); Concept and high-level requirements“. 4 3GPP TS 32.602: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Information Service (IS)“. 5 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Na

29、me 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 specification of valid version, see 1). 9 3GPP TS 32.303: “Telec

30、ommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 10 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (I

31、S)“. 11 3GPP TS 32.663: “Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. ETSI ETSI TS 132 603 V9.1.0 (2010-10)63GPP TS 32.603 version 9.1.0 Release 93 Definitions and abbre

32、viations 3.1 Definitions For terms and definitions please refer to 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.600 3 and 3GPP TS 32.602 4. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CORBA Common Object Request Broker Architecture DN Distinguishe

33、d Name IS Information Service IDL Interface Definition Language (OMG) IRP Integration Reference Point MO Managed Object MOC Managed Object Class NRM Network Resource Model OMG Object Management Group SS Solution Set 4 IRP document version number string The IRP document version number (sometimes call

34、ed “IRPVersion“ or “SS version number“) string is used to identify this specification. The string is derived using a rule described in 3GPP TS 32.312: 10. This string (or sequence of strings, if more than one version is supported) is returned in getBasicCmIRPVersion method. 5 Architectural features

35、The overall architectural feature of Basic Configuration Management IRP is specified in 3GPP TS 32.602 4. This clause specifies features that are specific to the CORBA SS. 5.1 Filter language The filter language used in the SS is the Extended Trader Constraint Language (see OMG Notification Service

36、6). IRPAgents may throw a FilterComplexityLimit exception when a given filter is too complex. However, for 3GPP Release 99 an “empty filter“ shall be used i.e. a filter that satisfies all MOs of a scoped search (this does not affect the filter for notifications as defined in the Notification IRP see

37、 3GPP TS 32.303 9). 5.2 Syntax for Distinguished Names and Versions The format of a Distinguished Name is defined in 3GPP TS 32.300 5. The version of this IRP is represented as a string (see also clause 4). ETSI ETSI TS 132 603 V9.1.0 (2010-10)73GPP TS 32.603 version 9.1.0 Release 96 Mapping 6.1 Gen

38、eral mappings The IS parameter name managedObjectInstance is mapped into DN. 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 attribu

39、te 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 referred MO,

40、 the reference attribute will be of type MOReferenceSet, which contains a sequence of MO references. If a reference attribute is changed, an AttributeValueChange notification (see TS 32.663 11) is emitted. 6.2 Operation mapping The Basic CM IRP: IS (see 3GPP TS 32.602 4) defines semantics of operati

41、on visible across the Basic Configuration Management IRP. Table 1 indicates mapping of these operations to their equivalents defined in this SS. Table 1: Mapping from IS Operation to SS equivalents IS Operation (3GPP TS 32.602 4) SS Method Qualifier getMoAttributes BasicCmIrpOperations:find_managed_

42、objects BasicCmInformationIterator:next_basic_cm_informations M getContainment BasicCmIrpOperations:find_managed_objects BasicCmInformationIterator:next_basic_cm_informations O cancelOperation BasicCmInformationIterator:destroy O createMo BasicCmIrpOperations:create_managed_object OdeleteMo BasicCmI

43、rpOperations:delete_managed_objectsDeleteResultIterator:next_basic_cm_informations DeleteResultIterator:next_delete_errors O setMoAttributes BasicCmIrpOperations:modify_managed_objects ModifyResultIterator:next_basic_cm_informations ModifyResultIterator:next_modification_errors O 6.3 Operation param

44、eter mapping The Basic CM IRP: IS (see 3GPP TS 32.602 4) defines semantics of parameters carried in operations across the Basic Configuration Management IRP. Tables 2 through 8 indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS. The SS operation find_

45、managed_objects is equivalent to the IS operation getMoAttributes when called with ResultContents set to NAMES_AND_ATTRIBUTES. Iterating the BasicCmInformationIterator is used to fetch the result. ETSI ETSI TS 132 603 V9.1.0 (2010-10)83GPP TS 32.603 version 9.1.0 Release 9Table 2: Mapping from IS ge

46、tMoAttributes parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier invokeIdentifier - (No equivalence) - invokeIdentifierOut Return value of type BasicCmInformationIterator M baseObjectInstance GenericIRPManagementConstDefs:DN base_object Mscope SearchControl search_cont

47、rol (SearchControl.type and SearchControl.level) M filter SearchControl search_control (SearchControl.filter) M attributeListIn AttributeNameSet requested_attributes MmanagedObjectClass managedObjectInstance attributeListOut Return value of type BasicCmInformationIterator - parameter out ResultSet f

48、etched_elements of method next_basic_cm_informations M status Exceptions: FindManagedObjects, GenericIRPManagementSystem:InvalidParameter, UndefinedMOException, IllegalDNFormatException, UndefinedScopeException, IllegalScopeTypeException, IllegalScopeLevelException, IllegalFilterFormatException, Fil

49、terComplexityLimit M The SS operation find_managed_objects is equivalent to the IS operation getContainment when called with ResultContents set to NAMES. Iterating the BasicCmInformationIterator is used to fetch the result. Table 3: Mapping from IS getContainment parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier invokeIdentifier - (No equivalence) - invokeIdentifierOut Return value of type BasicCmInformationIterator M baseObjectInstance GenericIRPManagementConstDefs:DN b