1、 ETSI TS 132 606 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 32.6
2、06 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 606 V14.0.0 (2017-04)13GPP TS 32.606 version 14.0.0 Release 14Reference RTS/TSGS-0532606ve00 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
3、 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 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 prin
4、t. The 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 Po
5、rtable 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:/por
6、tal.etsi.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, electron
7、ic or 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 Telecom
8、munications 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
9、logo is 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 606 V14.0.0 (2017-04)23GPP TS 32.606 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present docume
10、nt 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 Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of E
11、TSI standards“, 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 IP
12、Rs 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) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to techn
13、ical 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 cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryfor
14、m.asp. 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
15、 not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 606 V14.0.0 (2017-04)33GPP TS 32.606 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33
16、Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Solution Set Definitions . 7g3Annex A (normative): CORBA Solution Set . 8g3A.1 Architectural features . 8g3A.1.1 Syntax for Distinguished Names and Versions 8g3A.1.2 IRP document version number string . 8g3A.1.3 Filter la
17、nguage 8g3A.2 Mapping . 9g3A.2.1 General mappings . 9g3A.2.2 Operation mapping . 9g3A.2.3 Operation parameter mapping 10g3A.3 Solution Set definitions 13g3A.3.1 IDL definition structure 13g3A.3.2 IDL specification “BasicCMIRPConstDefs.idl“ 14g3A.3.3 IDL specification “BasicCMIRPSystem.idl“ 17g3Annex
18、 B (normative): SOAP Solution Set . 23g3B.1 Architectural features . 23g3B.1.1 Syntax for Distinguished Names and Versions 23g3B.1.2 Supported W3C specifications . 23g3B.1.3 Prefixes and namespaces 23g3B.1.4 Filter language 23g3B.2 Mapping . 24g3B.2.1 General mappings . 24g3B.2.2 Operation mapping .
19、 24g3B.2.3 Operation parameter mapping 25g3B.2.3.1 Operation getMoAttributes 25g3B.2.3.1.1 Input parameters 25g3B.2.3.1.2 Output parameters . 25g3B.2.3.1.3 Fault definition 26g3B.2.3.2 Operation getContainment 26g3B.2.3.2.1 Input parameters 26g3B.2.3.2.2 Output parameters . 26g3B.2.3.2.3 Fault defin
20、ition 27g3B.2.3.3 Operation createMO 27g3B.2.3.3.1 Input parameters 27g3B.2.3.3.2 Output parameters . 27g3B.2.3.3.3 Fault definition 28g3B.2.3.4 Operation deleteMO 28g3B.2.3.4.1 Input parameters 28g3ETSI ETSI TS 132 606 V14.0.0 (2017-04)43GPP TS 32.606 version 14.0.0 Release 14B.2.3.4.2 Output param
21、eters . 28g3B.2.3.4.3 Fault definition 29g3B.2.3.5 Operation setMOAttributes 29g3B.2.3.5.1 Input parameters 29g3B.2.3.5.2 Output parameters . 30g3B.2.3.5.3 Fault definition 30g3B.3 Solution Set definitions 31g3B.3.1 WSDL definition structure . 31g3B.3.2 Graphical Representation . 31g3B.3.3 WSDL spec
22、ification “BasicCMIRPSystem.wsdl” . 32g3Annex C (informative): Change history . 39g3History 40g3ETSI ETSI TS 132 606 V14.0.0 (2017-04)53GPP TS 32.606 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the
23、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-released by the TSG with an identifying change of release date and an increase in version number as follows: Version
24、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 digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third
25、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 management; as identified bel
26、ow: 32.601: “Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements“ 32.602: “Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS)“ 32.606: “Configuration Management (CM); Basic CM Integration Reference Point (IRP): Solu
27、tion 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 Network Elements (NEs) and Netw
28、ork 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), and to maintain the ove
29、rall 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 606 V14.0.0 (2017-04)63GPP TS 32.606 version 14.0.0 Release 141
30、Scope The purpose of this document is to define the mapping of the Basic CM IRP: IS (see 3GPP TS 32.602 8) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment and in a SOAP/WSDL environment. This document defines NRM independent data types and methods
31、. This Solution Set specification is related to 3GPP TS 32.602 V13.0.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 date of publication, edition number, v
32、ersion 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 implicitly refers to the latest version
33、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.300: “Telecommunication management; Configuration Management (CM); Name
34、 convention for Managed Objects“. 4 3GPP TS 32.306: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions“. 5 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Req
35、uirement“. 6 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 7 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 8 3GPP TS 32.602: “Telecommunication mana
36、gement; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Information Service (IS)“. 9 3GPP TS 32.666: “Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP): Solution Set (SS) definitions“. 10 OMG Notification Service, Versi
37、on 1.0. 11 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 12 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 13 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 14 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part
38、1/) ETSI ETSI TS 132 606 V14.0.0 (2017-04)73GPP TS 32.606 version 14.0.0 Release 143 Definitions and abbreviations 3.1 Definitions For terms and definitions please refer to 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.600 7 and 3GPP TS 32.602 8. IRP document version number string The IRP document
39、version number (sometimes called “IRPVersion“ or “SS version number“) string is used to identify this specification. The string is derived using a rule described in 3GPP TS 32.311 5. This string (or sequence of strings, if more than one version is supported) is returned in getBasicCmIRPVersion metho
40、d. 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) IRP Integration Reference Point MO Managed Object MOC Managed Object
41、Class NRM Network Resource Model OMG Object Management Group SS Solution Set WSDL Web Service Description Language 4 Solution Set Definitions This specification defines the following 3GPP Basic CM IRP Solution Set Definitions: Annex A provides the CORBA Solution Set. Annex B provides the SOAP Soluti
42、on Set. ETSI ETSI TS 132 606 V14.0.0 (2017-04)83GPP TS 32.606 version 14.0.0 Release 14Annex A (normative): CORBA Solution Set This annex specifies the CORBA Solution Set for the IRP whose semantics are specified in 3GPP TS 32.602 8. A.1 Architectural features The overall architectural feature of Ba
43、sic Configuration Management IRP is specified in 3GPP TS 32.602 8. This clause specifies features that are specific to the CORBA SS. A.1.1 Syntax for Distinguished Names and Versions The syntax of a Distinguished Name is defined in 3GPP TS 32.300 3. The version of this IRP is represented as a string
44、 (see also clause 3.1). A.1.2 IRP document version number string The IRP document version number (sometimes called “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: 6. This string (or sequence of string
45、s, if more than one version is supported) is returned in getBasicCmIRPVersion method. A.1.3 Filter language The filter language used in the SS is the Extended Trader Constraint Language (see OMG Notification Service 10). IRPAgents may throw a FilterComplexityLimit exception when a given filter is to
46、o 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 3GPP TS 32.306 4). ETSI ETSI TS 132 606 V14.0.0 (2017-04)93GPP TS 32.606 version 1
47、4.0.0 Release 14A.2 Mapping A.2.1 General 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 ar
48、e mapped to the corresponding attribute 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 associat
49、ion allows more than one referred MO, 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.666 9) is emitted. A.2.2 Operation mapping The Basic CM IRP: IS (see 3GPP TS 32.602 8) defines semantics of operation visible across the Basic Configuration Management IRP. Table A.2.2 indicates mapping of these operations to their equivalents defined in this SS. Table A.2.2: Mapping from IS Oper
