ETSI TS 132 367-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Entry Point (EP) Integ_1.pdf

1、 ETSI TS 132 367 V9.0.0 (2010-02)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Entry Point (EP) Integration Reference Point (IRP);SOAP Solution Set (SS) (3GPP TS 32.367 version 9.0.0 Re

2、lease 9)floppy3ETSI ETSI TS 132 367 V9.0.0 (2010-02)13GPP TS 32.367 version 9.0.0 Release 9Reference RTS/TSGS-0532367v900 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 00017 - NAF 742 C A

3、ssociation 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 case of existing

4、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 present document

5、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 of the following

6、 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. All rights re

7、served. 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 ETSI currently

8、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 367 V9.0.0 (2010-02)23GPP TS 32.367 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potent

9、ially 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 potentially Essential,

10、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 by ETSI. No gua

11、rantee 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 Partnership Proj

12、ect (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 ETSI identities ca

13、n be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 367 V9.0.0 (2010-02)33GPP TS 32.367 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6

14、g33.2 Abbreviations . 6g34 Architectural features . 6g34.1 General . 6g35 Mapping . 7g35.1 Operation and notification mapping . 7g35.2 Operation parameter mapping 7g35.2.1 Operation getIRPOutline 8g35.2.1.1 Input parameters 8g35.2.1.2 Output parameters . 8g35.2.1.3 Fault definition 8g35.2.2 Operatio

15、n getIRPReference 8g35.2.1.1 Input parameters 8g35.2.1.2 Output parameters . 9g35.2.1.3 Fault definition 9g35.2.3 Operation releaseIRPReference 9g35.2.1.1 Input parameters 9g35.2.1.2 Output parameters . 9g35.2.1.3 Fault definition 9g3Annex A (normative): WSDL specifications 10g3Annex B (informative)

16、: WSDL electronic files 13g3Annex C (informative): Change history . 14g3History 15g3ETSI ETSI TS 132 367 V9.0.0 (2010-02)43GPP TS 32.367 version 9.0.0 Release 9Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present do

17、cument 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.y.z wher

18、e: 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 digit is i

19、ncremented 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 below: 32.361

20、: “Entry Point (EP) Integration Reference Point (IRP): Requirements“; 32.362: “Entry Point (EP) Integration Reference Point (IRP): Information Service (IS)“; 32.363: “Entry Point (EP) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“; 32.365: “En

21、try Point (EP) Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 32.367: “Entry Point (EP) Integration Reference Point (IRP): SOAP Solution Set (SS)“. ETSI ETSI TS 132 367 V9.0.0 (2010-02)53GPP TS 32.367 version 9.0.0 Release 91 Scope The present document specifies th

22、e SOAP Solution Set for the IRP whose semantics are specified in Entry Point IRP: Information Service (3GPP TS 32.362 4). This Solution Set specification is related to 3GPP TS 32.362 V9.0.X. 2 References The following documents contain provisions which, through reference in this text, constitute pro

23、visions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) 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

24、 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 and high level requirements“. 2 3GPP TS 32.102: “Telecommunication m

25、anagement; Architecture“. 3 3GPP TS 32.361: “ Technical Specification Group Services and System Aspects; Telecommunication management; Entry Point (EP) Integration Reference Point (IRP): Requirements “. 4 3GPP TS 32.362: “ Technical Specification Group Services and System Aspects; Telecommunication

26、management; Entry Point (EP) Integration Reference Point (IRP): Information Service (IS)“. 5 3GPP TS 32.365: “ Telecommunication management; Entry Point (EP) Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 6 3GPP TS 32.311: “Telecommunication management; Generic Int

27、egration Reference Point (IRP) management; Requirements“. 7 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 8 3GPP TS 32.317: “Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP solu

28、tion set“. 9 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept 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 (

29、http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 12 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/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 367 V9.0.0 (2010-0

30、2)63GPP TS 32.367 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes 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.361 3 and the following apply: IRP document version number string

31、(or “IRPVersion“): See 3GPP TS 32.311 6. 3.2 Abbreviations For the purposes of the present document, 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 Entry Poin

32、t IRP is specified in 3GPP TS 32.362 4. This clause specifies features that are specific to the SOAP solution 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.

33、This specification uses “literal“ encoding style in WSDL file. The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification 12). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex. The Entry Point IRP SOAP SS uses the Notification IRP SO

34、AP SS of 3GPP TS 32.307 10. The IRPAgent shall support the push interface model, which means that the IRPAgent sends Entry Point 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 prefi

35、xes throughout that are listed in Table 4.1. Table 4.1: Prefixes and Namespaces used in this specification PREFIX NAMESPACE (no prefix) http:/schemas.xmlsoap.org/wsdl/ soap http:/schemas.xmlsoap.org/wsdl/soap/entryPointIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.367#EntryPointIRPSyst

36、em entryPointIRPData http:/www.3gpp.org/ftp/Specs/archive/32_series/32.367#EntryPointIRPData xn http:/www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrm genericIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.317/schema/32317-810/GenericIRPSystem genericIRPData http:/www.3gpp.org/

37、ftp/Specs/archive/32_series/32.317/schema/32317-810/GenericIRPData ntfIRPNtfSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.307/schema/32307-810/notification/NotificationIRPNtfSystem The WSDL structure is depicted in Figure 4.1 below, depicting port type, binding and service. The port type

38、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 service. ETSI ETSI TS 132 367 V9.0.0 (2010-02)73GPP TS 32.367 version 9.0.0 R

39、elease 9Figure 4.1: Entry Point IRP SOAP Solution Set WSDL structure 5 Mapping 5.1 Operation and notification mapping The Entry Point IRP IS (3GPP TS 32.362 4) defines the operations and their semantics. Table 5.1 maps the operations defined in the Entry Point IRP IS to their equivalent types, messa

40、ges, port type operation, and binding operation in this Solution Set (SS). Table 5.1 also maps the notifications of the Entry Point IRP IS, as well as inherited operations. Table 5.1 also qualifies if an operation is Mandatory (M) or Optional (O). Table 5.1: Mapping from IS Operation to SS Equivalen

41、ts IS Operation in 3GPP TS 32.362 4 SS: Operation for WSDL port type and WSDL binding SS: Port of EntryPointIRPService Qualifier getIRPOutline getIRPOutline (note 1) EntryPointIRPPort MgetIRPReference getIRPReference (note 1) EntryPointIRPPort M releaseIRPReference releaseIRPReference (note 1) Entry

42、PointIRPPort MnotifyIRPInfoChanges 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 port t

43、ype entryPointIRPSystem:EntryPointIRPPortType and under the binding entryPointIRPSystem:EntryPointIRPBinding. NOTE 2: The IS equivalent maps to an XML definition specified in 3GPP TS 32.365 5, and this being an input parameter to the operation notify under the port type ntfIRPNtfSystem:NotificationI

44、RPNtf and under the binding ntfIRPNtfSystem:NotificationIRPNtf of 3GPP TS 32.307 10. This binding is linked to a port of the EntryPointIRPService as indicated in the table above. NOTE 3: The IS operation is inherited from the ManagedGenericIRP IOC specified in 3GPP TS 32.312 7. This inheritance is b

45、y the EPIRP IOC of 3GPP TS 32.362 4 inheriting from the ManagedGenericIRP IOC. The corresponding binding is linked to a port of the EntryPointIRPService as indicated in the table above. 5.2 Operation parameter mapping The Entry Point IRP IS (3GPP TS 32.362 4) defines semantics of parameters carried

46、in the operations. The tables below show the mapping of these parameters, as per operation, to their equivalents defined in this SS. ETSI ETSI TS 132 367 V9.0.0 (2010-02)83GPP TS 32.367 version 9.0.0 Release 95.2.1 Operation getIRPOutline 5.2.1.1 Input parameters Table 5.2.1.1: Mapping from IS getIR

47、POutline input parameters to SS equivalents IS Operation parameter SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table 5.1 Qualifier iRPVersion iRPVersion M 5.2.1.2 Output parameters Table 5.2.1.2: Mapping from IS getIRPOutline o

48、utput parameters to SS equivalents IS Operation parameter SS WSDL type sub-element used in corresponding output message under corresponding port type operation as indicated in Table 5.1 Qualifier supportedIRPList supportedIRPList M status status M5.2.1.3 Fault definition Table 5.2.1.3: Mapping from

49、IS getIRPOutline exceptions to SS equivalents Assertion name SS WSDL type enumeration value used in corresponding fault message under corresponding port type operation as indicated in Table 5.1 Qualifier invalidIRPVersion InvalidIRPVersion MoperationFailed OperationFailed M 5.2.2 Operation getIRPReference 5.2.1.1 Input parameters Table 5.2.1.1: Mapping from IS getIRPReference input parameters to SS equivalents IS Operation parameter SS WSDL type sub-element used in corresponding input me