1、 ETSI TS 132 617 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Configuration Management (CM);Bulk CM Integration Reference Point (IRP):Bulk CM IRP SOAP Solution Set (SS)
2、 (3GPP TS 32.617 version 9.0.0 Release 9)ETSI ETSI TS 132 617 V9.0.0 (2010-01)13GPP TS 32.617 version 9.0.0 Release 9Reference RTS/TSGS-0532617v900 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 6
3、23 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 electronic version or in print
4、. 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 within ETSI Secretariat. User
5、s 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 document, please send your comme
6、nt 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 Telecommunications Standards Ins
7、titute 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 Organizational Partners. LTE is a Tra
8、de 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 617 V9.0.0 (2010-01)23GPP TS 32.617 version 9.0.0 Release 9Intellectual Property Right
9、s 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 Property Rights (IPRs); Essential,
10、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, including IPR searches, has been c
11、arried 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) has been produced by ETSI 3rd G
12、eneration 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 cross reference between GSM, UMTS, 3
13、GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 617 V9.0.0 (2010-01)33GPP TS 32.617 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviati
14、ons . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Architectural features . 7g34.1 General . 7g35 Mapping . 9g35.1 Operation and notification mapping . 9g35.2 Operation parameter mapping 9g35.2.1 Operation startSession . 10g35.2.1.1 Input parameters 10g35.2.1.2 Output parameters . 10g35.2.1.3 Faul
15、t definition 10g35.2.2 Operation endSession . 10g35.2.2.1 Input parameters 10g35.2.2.2 Output parameters . 10g35.2.2.3 Fault definition 11g35.2.3 Operation abortSessionOperation . 11g35.2.3.1 Input parameters 11g35.2.3.2 Output parameters . 11g35.2.3.3 Fault definition 11g35.2.4 Operation getSession
16、Ids 11g35.2.4.1 Input parameters 11g35.2.4.2 Output parameters . 12g35.2.4.3 Fault definition 12g35.2.5 Operation getSessionStatus . 12g35.2.5.1 Input parameters 12g35.2.5.2 Output parameters . 12g35.2.5.3 Fault definition 12g35.2.6 Operation getSessionLog 13g35.2.6.1 Input parameters 13g35.2.6.2 Ou
17、tput parameters . 13g35.2.6.3 Fault definition 13g35.2.7 Operation upload . 13g35.2.7.1 Input parameters 13g35.2.7.2 Output parameters . 14g35.2.7.3 Fault definition 14g35.2.8 Operation download 14g35.2.8.1 Input parameters 14g35.2.8.2 Output parameters . 14g35.2.8.3 Fault definition 14g35.2.9 Opera
18、tion validate 15g35.2.9.1 Input parameters 15g35.2.9.2 Output parameters . 15g35.2.9.3 Fault definition 15g35.2.10 Operation preactivate . 15g3ETSI ETSI TS 132 617 V9.0.0 (2010-01)43GPP TS 32.617 version 9.0.0 Release 95.2.10.1 Input parameters 15g35.2.10.2 Output parameters . 16g35.2.10.3 Fault def
19、inition 16g35.2.11 Operation activate 16g35.2.11.1 Input parameters 16g35.2.11.2 Output parameters . 16g35.2.11.3 Fault definition 16g35.2.12 Operation fallback 17g35.2.12.1 Input parameters 17g35.2.12.2 Output parameters . 17g35.2.12.3 Fault definition 17g3Annex A (normative): WSDL specifications 1
20、8g3Annex B (informative): Void . 27g3Annex C (informative): Change history . 28g3History 29g3ETSI ETSI TS 132 617 V9.0.0 (2010-01)53GPP TS 32.617 version 9.0.0 Release 9Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the p
21、resent 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 x
22、.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 d
23、igit 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 belo
24、w: 32.611: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements“. 32.612: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)“. 32.613: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common
25、 Object Request Broker Architecture (CORBA) Solution Set (SS)“. 32.615: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition“. 32.617: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): SOAP Solutio
26、n Set (SS) ETSI ETSI TS 132 617 V9.0.0 (2010-01)63GPP TS 32.617 version 9.0.0 Release 91 Scope The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Bulk CM IRP: Information Service (3GPP TS 32.612 4). This Solution Set specification is related to 3GPP TS
27、32.612 V9.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, version number, etc.) non-specific. For a specific reference
28、, 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 of that document in the same Release as the present document. 1 3G
29、PP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.611: “ Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); Bulk CM In
30、tegration Reference Point (IRP): Requirements “. 4 3GPP TS 32.612: “ Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)“. 5 3GPP TS 32.615: “ Telecommunication man
31、agement; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition“. 6 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements“. 7 3GPP TS 32.312: “Telecommunication mana
32、gement; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 8 3GPP TS 32.317: “Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP solution set“. 9 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Conce
33、pt and definitions“. 10 3GPP TS 32.307: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): SOAP solution set“. 11 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 12 W3C XPath 1.0 specification (http:/www.w3.org/TR/1
34、999/REC-xpath-19991116) 13 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 14 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) ETSI ETSI TS 132 617 V9.0.0 (2010-01)73GPP TS 32.617 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the pu
35、rposes of the present document, the terms and definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.150 9 and 3GPP TS 32.611 3 and the following apply: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 6. 3.2 Abbreviations For the purposes of the present document
36、, the following abbreviations apply: IS Information Service SS Solution SetWSDL Web Service Description Language 4 Architectural features 4.1 General The overall architectural feature of the Bulk CM IRP is specified in 3GPP TS 32.612 4. This clause specifies features that are specific to the SOAP so
37、lution set. The SOAP 1.1 specification 11 and WSDL 1.1 specification 13 are supported. The SOAP 1.2 specification 14 is supported optionally. This specification uses “document“ style in WSDL file. This specification uses “literal“ encoding style in WSDL file. The filter language used in the SS is th
38、e XPath Language (see W3C XPath 1.0 specification 12). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex. The Bulk CM IRP SOAP SS uses the Notification IRP SOAP SS of 3GPP TS 32.307 10. The IRPAgent shall support the push interface model, which means that the IRPAg
39、ent sends Bulk CM notifications to the IRPManager as soon as new events occur. The IRPManager does not need to check (“pull“) for events. This specification uses a number of namespace prefixes throughout that are listed in Table 4.1. Table 4.1: Prefixes and Namespaces used in this specification PREF
40、IX NAMESPACE (no prefix) http:/schemas.xmlsoap.org/wsdl/ soap http:/schemas.xmlsoap.org/wsdl/soap/bulkCMIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.617#BulkCMIRPSystem bulkCMIRPData http:/www.3gpp.org/ftp/Specs/archive/32_series/32.617#BulkCMIRPData xn http:/www.3gpp.org/ftp/specs/ar
41、chive/32_series/32.625#genericNrmgenericIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.317/schema/32317-810/GenericIRPSystem ntfIRPNtfSystem “http:/www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/notification/NotificationIRPNtfSystem“ The WSDL structure is depicted in F
42、igure 4.1 below, depicting port type, binding and service. The port type contains port type operations, which again contains input, output and fault messages. The binding contains binding operations, which have the same name as the port type operations. The binding connects to a port inside the serv
43、ice. ETSI ETSI TS 132 617 V9.0.0 (2010-01)83GPP TS 32.617 version 9.0.0 Release 9Figure 4.1: Bulk CM IRP SOAP Solution Set WSDL structure ETSI ETSI TS 132 617 V9.0.0 (2010-01)93GPP TS 32.617 version 9.0.0 Release 95 Mapping 5.1 Operation and notification mapping The Bulk CM IRP IS (3GPP TS 32.612 4)
44、 defines the operations and their semantics. Table 5.1 maps the operations defined in the Bulk CM IRP IS to their equivalent types, messages, port type operation, and binding operation in this Solution Set (SS). Table 5.1 also maps the notifications of the Bulk CM IRP IS, as well as inherited operat
45、ions. Table 5.1 also qualifies if an operation is Mandatory (M) or Optional (O). Table 5.1: Mapping from IS Operation to SS Equivalents IS Operation in 3GPP TS 32.612 4 SS: Operation for WSDL port type and WSDL binding SS: Port of BulkCMIRPService Qualifier startSession startSession (note 1) BulkCMI
46、RPPort M endSession endSession (note 1) BulkCMIRPPort MabortSessionOperation abortSessionOperation (note 1) BulkCMIRPPort MgetSessionIds getSessionIds (note 1) BulkCMIRPPort M getSessionStatus getSessionStatus (note 1) BulkCMIRPPort M getSessionLog getSessionLog (note 1) BulkCMIRPPort M upload uploa
47、d (note 1) BulkCMIRPPort M download download (note 1) BulkCMIRPPort Mvalidate validate (note 1) BulkCMIRPPort O preactivate preactivate (note 1) BulkCMIRPPort Oactivate activate (note 1) BulkCMIRPPort M fallback fallback (note 1) BulkCMIRPPort M notifySessionStateChanged notify (note 2) Notification
48、IRPNtfPort M notifyGetSessionLogEnded notify (note 2) NotificationIRPNtfPort M getIRPVersion (note 3) See TS 32.317 8 GenericIRPPort M getOperationProfile (note 3) See TS 32.317 8 GenericIRPPort O getNotificationProfile (note 3) See TS 32.317 8 GenericIRPPort O NOTE 1: The operation is under the por
49、t type bulkCMIRPSystem:BulkCMIRPPortType and under the binding bulkCMIRPSystem:BulkCMIRPBinding. NOTE 2: The IS equivalent maps to an XML definition specified in 3GPP TS 32.615 5, and this being an input parameter to the operation notify under the port type ntfIRPNtfSystem:NotificationIRPNtf and under the binding ntfIRPNtfSystem:NotificationIRPNtf of 3GPP TS 32.307 10. This binding is linked to a port of the BulkCMIRPService as indicated in the table above. NOTE 3: The IS operation is inherite
