1、 ETSI TS 132 607 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);SOAP Solution Set (SS) (3GPP TS 3
2、2.607 version 9.1.0 Release 9)ETSI ETSI TS 132 607 V9.1.0 (2010-10)13GPP TS 32.607 version 9.1.0 Release 9Reference RTS/TSGS-0532607v910 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 Siret N 348 623 562 0001
3、7 - 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 electronic version or in print. In any ca
4、se 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 within ETSI Secretariat. Users of the pr
5、esent 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 document, please send your comment to one o
6、f 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 Telecommunications Standards Institute 2010
7、. 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 Organizational Partners. LTE is a Trade Mark of
8、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 607 V9.1.0 (2010-10)23GPP TS 32.607 version 9.1.0 Release 9Intellectual Property Rights IPRs esse
9、ntial 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 Property Rights (IPRs); Essential, or potentia
10、lly 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, including IPR searches, has been carried out
11、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) has been produced by ETSI 3rd Generation P
12、artnership 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 cross reference between GSM, UMTS, 3GPP and ETS
13、I identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 607 V9.1.0 (2010-10)33GPP TS 32.607 version 9.1.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.
14、1 Definitions 6g33.2 Abbreviations . 6g34 IRP document version number string . 6g35 Architectural features . 7g35.1 General . 7g35.2 Filter language 7g35.3 Syntax for Distinguished Names and Versions 7g36 Mapping . 8g36.1 General mappings . 8g36.2 Operation mapping . 8g36.3 Operation parameter mappi
15、ng 9g36.3.1 Operation getMoAttributes 9g36.3.1.1 Input parameters 9g36.3.1.2 Output parameters . 9g36.3.1.3 Fault definition 10g36.3.2 Operation getContainment 11g36.3.2.1 Input parameters 11g36.3.2.2 Output parameters . 11g36.3.2.3 Fault definition 11g36.3.3 Operation createMO 12g36.3.3.1 Input par
16、ameters 12g36.3.3.2 Output parameters . 12g36.3.3.3 Fault definition 12g36.3.4 Operation deleteMO 13g36.3.4.1 Input parameters 13g36.3.4.2 Output parameters . 13g36.3.4.3 Fault definition 13g36.3.5 Operation setMOAttributes 14g36.3.5.1 Input parameters 14g36.3.5.2 Output parameters . 14g36.3.5.3 Fau
17、lt definition 15g3Annex A (normative): WSDL specification . 16g3Annex B (informative): Void . 23g3Annex C (informative): Change history . 24g3History 25g3ETSI ETSI TS 132 607 V9.1.0 (2010-10)43GPP TS 32.607 version 9.1.0 Release 9Foreword This Technical Specification has been produced by the 3rdGene
18、ration 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-released by the TSG with an identifying change of release date
19、 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 digit is incremented for all changes of substance, i.e. technica
20、l 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 Project: Technical Specification Group Services and System A
21、spects; Telecommunication management; as identified below: 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.603: Configuration Management (CM)
22、; Basic CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) 32.607: Configuration Management (CM); Basic CM Integration Reference Point (IRP); SOAP Solution Set (SS) Configuration Management (CM), in general, provides the operator with the abilit
23、y 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 Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (O
24、Ss) 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 overall Quality of Service (QoS). The CM actions are initiated either as single actions on single NEs of the 3
25、G network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs. ETSI ETSI TS 132 607 V9.1.0 (2010-10)53GPP TS 32.607 version 9.1.0 Release 91 Scope The purpose of this Basic CM IRP: SOAP Solution Set is to define the mapping of the Basic CM IRP: IS (3G
26、PP TS 32.602 4) to the protocol specific details necessary for implementation of this IRP in a SOAP/WSDL environment. The present document defines NRM independent data types and methods. This Solution Set specification is related to 3G TS 32.602 V9.0.X. 2 References The following documents contain p
27、rovisions which, through reference in this text, constitute provisions of the present document. 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 re
28、ference, 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 of that document in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication management; Principles an
29、d high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 4 3GPP TS 32.602: “Telecommunication management; Configuration Management (CM); Basic CM I
30、ntegration Reference Point (IRP) Information Service (IS)“. 5 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 6 3GPP TS 32.172: “Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Re
31、ference Point (IRP): Information Service“ 7 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requirement“. 8 3GPP TS 32.317: “Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP solution set“. 9 3GPP TS 32.667:
32、“Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP): SOAP solution set“. 10 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 11 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 12 W3C XPath 1.0 spe
33、cification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 13 WS-I Basic Profile Version 1.1 (http:/www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html) 14 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) ETSI ETSI TS 132 607 V9.1.0 (2010-10)63GPP TS 32.607 version 9.1.0 Release 93 De
34、finitions and abbreviations 3.1 Definitions For terms and definitions 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: DN Distinguished Name IS Information Service IRP In
35、tegration Reference Point MO Managed Object MOC Managed Object Class NRM Network Resource Model OMG Object Management Group SS Solution Set WSDL Web Service Description Language WS-I Web Services Interoperability Organization 4 IRP document version number string The IRP document version number (some
36、times 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 7. This string (or sequence of strings, if more than one version is supported) is returned in getBasicCmIRPVersion method. ETSI ETSI TS 132
37、607 V9.1.0 (2010-10)73GPP TS 32.607 version 9.1.0 Release 95 Architectural features 5.1 General 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 SOAP SS. The SOAP 1.1 specification 10 and
38、 WSDL 1.1 specification 11 are supported. The SOAP 1.2 specification 14 is supported optionally. This specification uses “document“ style in the WSDL description. This specification uses “literal“ encoding style in the WSDL description. This specification uses a number of namespace prefixes througho
39、ut that are listed in Table 5.1. Table 5.1: Prefixes and Namespaces used in this specification Prefix Namespace http http:/schemas.xmlsoap.org/wsdl/http/ soap http:/schemas.xmlsoap.org/wsdl/soap/SOAP-ENV http:/schemas.xmlsoap.org/soap/envelope/ SOAP-ENC or soapenc http:/schemas.xmlsoap.org/soap/enco
40、ding/ xs or xsd http:/www.w3.org/2001/XMLSchema xsi http:/www.w3.org/2001/XMLSchema-instance basicCMIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32607/schema/32607-800/BasicCMIRPSystem basicCMIRPData http:/www.3gpp.org/ftp/Specs/archive/32_series/32607/schema/32607-800/BasicCMIRPData gen
41、ericIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32317/schema/32317-800/GenericIRPSystem The WSDL structure is like Figure 5.1: Figure 5.1: BasicCM IRP SOAP Solution Set WSDL structure 5.2 Filter language The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specifi
42、cation 12). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex. 5.3 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 13
43、2 607 V9.1.0 (2010-10)83GPP TS 32.607 version 9.1.0 Release 96 Mapping 6.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
44、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 attribute is defined as a MOReference. The value of an MO reference contains the distinguished name of the associated
45、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. If a reference attribute is changed, an AttributeValueChange notification (see 3GPP TS 32.667 9) is emitted. 6.2 Operation
46、 mapping The Basic CM IRP: IS (see 3GPP TS 32.602 4) defines semantics of operation visible across the Basic Configuration Management IRP. Table 6.2 indicates mapping of these operations to their equivalents defined in this SS. Table 6.2: Mapping from IS Operation to SS equivalents IS Operation (3GP
47、P TS 32.602 4) SS Operation Qualifier getMoAttributes getMOAttributes MgetContainment getContainment OcancelOperation (see note 1) N/A N/A createMO createMO OdeleteMO deleteM OsetMOAttributes setMOAttributes O getIRPVersion (see note 2) getIRPVersion M getOperationProfile (see note 2) getOperationPr
48、ofile O getNotificationProfile (see note 2) getNotificationProfile O NOTE 1: This operation is NOT mapped because it“s useful for one-request-and-multiple-responses operations, which are not used in this Solution Set. NOTE 2: This operation is of IOC ManagedGenericIRP specified in 10. The IOC BasicC
49、mIRP of 4 inherits from it. ETSI ETSI TS 132 607 V9.1.0 (2010-10)93GPP TS 32.607 version 9.1.0 Release 96.3 Operation parameter 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. The following tables show the mapping of these parameters, as per operation, to their equivalents defined in the present document. 6.3.1 Operation getMoAttributes 6.3.1.1 Input parameters Mapping from IS getMoAttribut
