ETSI TS 132 507-2010 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Self-configuration of network elements Integration Reference Point (IRP) SOA.pdf

《ETSI TS 132 507-2010 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Self-configuration of network elements Integration Reference Point (IRP) SOA.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 507-2010 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Self-configuration of network elements Integration Reference Point (IRP) SOA.pdf（25页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 507 V9.1.0 (2010-07)Technical Specification Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Self-configuration of network elements;Integration Reference Point (IRP): SOAP Solution Set (SS) (3GPP TS 32.507 version 9.1.0 Release 9)ETSI ETSI TS 132 507 V9

2、.1.0 (2010-07)13GPP TS 32.507 version 9.1.0 Release 9Reference RTS/TSGS-0532507v910 Keywords 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 Association but non lucratif enregistre la S

3、ous-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 or perceived difference in contents between

4、 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 should be aware that the document may be su

5、bject 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 services: http:/portal.etsi.org/chaircor/E

6、TSI_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 reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHON

7、TM, 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 being registered for the benefit of its Mem

8、bers 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 507 V9.1.0 (2010-07)23GPP TS 32.507 version 9.1.0 Release 9Intellectual Property Rights IPRs essential or potentially essential to the present document may

9、 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 ETSI st

10、andards“, 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 guarantee can be given as to the existence of

11、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 Project (3GPP). The present document may refer

12、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 can be found under http:/webapp.etsi.org/key/

13、queryform.asp. ETSI ETSI TS 132 507 V9.1.0 (2010-07)33GPP TS 32.507 version 9.1.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Architectural fe

14、atures . 7g34.1 General . 7g35 Mapping . 8g35.1 Operation and notification mapping . 8g35.2 Operation parameter mapping 8g35.2.1 Operation listScManagementCapabilities . 9g35.2.1.1 Input parameters 9g35.2.1.2 Output parameters . 9g35.2.1.3 Fault definition 9g35.2.2 Operation listScManagementProfiles

15、 . 9g35.2.2.1 Input parameters 9g35.2.2.2 Output parameters . 9g35.2.3 Operation createScManagementProfile 10g35.2.3.1 Input parameters 10g35.2.3.2 Output parameters . 10g35.2.4 Operation deleteScManagementProfile 10g35.2.4.1 Input parameters 10g35.2.4.2 Output parameters . 11g35.2.5 Operation listS

16、cProcesses 11g35.2.5.1 Input parameters 11g35.2.5.2 Output parameters . 11g35.2.6 Operation resumeScProcess 11g35.2.6.1 Input parameters 11g35.2.6.2 Output parameters . 11g35.2.7 Operation resumeScProcessWithArcfData . 12g35.2.7.1 Input parameters 12g35.2.7.2 Output parameters . 12g35.2.8 Operation

17、terminateScProcess 12g35.2.8.1 Input parameters 12g35.2.8.2 Output parameters . 13g35.2.9 Operation changeScManagementProfile. 13g35.2.9.1 Input parameters 13g35.2.9.2 Output parameters . 13g3Annex A (normative): WSDL specifications 14g3Annex B (informative): Change history 23g3History 24g3ETSI ETSI

18、 TS 132 507 V9.1.0 (2010-07)43GPP TS 32.507 version 9.1.0 Release 9Foreword This Technical Specification (TS) 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 appr

19、oval. 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 where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3

20、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 incremented when editorial only changes have been incorporated in the document. Introduction T

21、he 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.501: Self-Configuration of Network Elements; Concepts and Integration Reference Point (IRP) Requ

22、irements 32.502: Self-Configuration of Network Elements Integration Reference Point (IRP); Information Service (IS) 32.503: Self-Configuration of Network Elements Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) 32.505: Self-Configuration of Netw

23、ork Elements Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition 32.507: Self-Configuration of Network Elements Integration Reference Point (IRP): SOAP Solution Set (SS)“ The present document is part of a TS-family which describe the requirements and informatio

24、n model necessary for the Telecommunication Management (TM) of 3G systems. The TM principles and TM architecture are specified in 3GPP TS 32.101 1 and 3GPP TS 32.102 2. For the purpose of Self-Configuration of Network Elements IRP, see TS 32.501 3 ETSI ETSI TS 132 507 V9.1.0 (2010-07)53GPP TS 32.507

25、 version 9.1.0 Release 91 Scope The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Self-Configuration of Network Elements Integration Reference Point (IRP): Information Service (3GPP TS 32.502 4). This Solution Set specification is related to 3GPP TS 32

26、.502 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,

27、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 3GPP

28、 TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.501: “ Technical Specification Group Services and System Aspects; Telecommunication management; Self-Configuration of Network Elements; Con

29、cepts and Integration Reference Point (IRP) Requirements “. 4 3GPP TS 32.502: “ Technical Specification Group Services and System Aspects; Telecommunication management; Self-Configuration of Network Elements Integration Reference Point (IRP); Information Service (IS)“. 5 3GPP TS 32.505: “ Telecommun

30、ication management; A Self-Configuration of Network Elements 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: “Telecommuni

31、cation management; 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

32、(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 (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 12 W3C XPath 1.0 specification (http:/www.

33、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 507 V9.1.0 (2010-07)63GPP TS 32.507 version 9.1.0 Release 93 Definitions and abbreviations 3.1 Definitions

34、 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.501 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 prese

35、nt document, the following abbreviations apply: IS Information Service SC Self ConfigurationSS Solution Set WSDL Web Service Description Language ETSI ETSI TS 132 507 V9.1.0 (2010-07)73GPP TS 32.507 version 9.1.0 Release 94 Architectural features 4.1 General The overall architectural feature of the

36、Self-Configuration of Network Elements IRP is specified in 3GPP TS 32.502 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

37、 uses “document“ style in WSDL file. 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. Relevant definition

38、s are imported from the Self-Configuration of Network Elements22 XML definitions of 3GPP TS 32.505 5. 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 PREFIX NAMESPACE (no prefix) http:/schem

39、as.xmlsoap.org/wsdl/ soap http:/schemas.xmlsoap.org/wsdl/soap/ScIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.507#SCIRPSystem ScIRPData http:/www.3gpp.org/ftp/Specs/archive/32_series/32.507#SCIRPData xsc http:/www.3gpp.org/ftp/specs/archive/32_series/32.505#ScIRPIOCs genericIRPSystem h

40、ttp:/www.3gpp.org/ftp/Specs/archive/32_series/32.507/schema/32317-810/GenericIRPSystem ntfIRPNtfSystem http:/www.3gpp.org/ftp/Specs/archive/32_series/32.507/schema/32507-810/notification/NotificationScNtfSystem The WSDL structure is depicted in Figure 4.1 below, depicting port type, binding and serv

41、ice. 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 service. Figure 4.1: Self-Configuration of Network Element

42、s IRP SOAP Solution Set WSDL structure ETSI ETSI TS 132 507 V9.1.0 (2010-07)83GPP TS 32.507 version 9.1.0 Release 95 Mapping 5.1 Operation and notification mapping The Self-Configuration of Network Elements IRP IS (3GPP TS 32.502 4) defines the operations and their semantics. Table 5.1 maps the oper

43、ations defined in the Self-Configuration of Network Elements IRP IS to their equivalent port type and binding operations in this Solution Set (SS). Table 5.1 also maps the notifications of the Self-Configuration of Network Elements IRP IS, as well as inherited operations. Table 5.1 also qualifies if

44、 an operation is Mandatory (M) or Optional (O). Table 5.1: Mapping from IS Operation to SS Equivalents IS Operation in 3GPP TS 32.502 4 SS: Operation for WSDL port type and WSDL binding SS: Port of SCIRPService Qualifier listScManagementCapabilities listScManagementCapabilities (note 1) SCIRPOperati

45、on1 M listScManagementProfiles listScManagementProfiles (note 1) SCIRPOperation1 M createScManagementProfile createScManagementProfile (note1) SCIRPOperation1 M deleteScManagementProfile deleteScManagementProfile (note1) SCIRPOperation1 M listScProcesses listScProcesses (note1) SCIRPOperation1 M res

46、umeScProcess resumeScProcess (note1) SCIRPOperation1 M resumeScProcessWithArcfData resumeScProcessWithArcfData(note1) SCIRPOperation1 M terminateScProcess terminateScProcess (note1) SCIRPOperation1 M changeScManagementProfile changeScManagementProfile (note1) SCIRPOperation1 O notifyScManagementProf

47、ileCreation notify (note 2) NotificationIRPNtfPort M notifyScManagementProfileDeletion notify (note 2) NotificationIRPNtfPort M notifyScProcessCreation notify (note 2) NotificationIRPNtfPort M notifyScProcessStage notify (note 2) NotificationIRPNtfPort M notifyScProcessDeletion notify (note 2) Notif

48、icationIRPNtfPort M notifyNewScManagementCapabilityAvailabilitynotify (note 2) NotificationIRPNtfPort M notifyScManagementProfileChange notify (note 2) NotificationIRPNtfPort O getIRPVersion (note 3) See TS 32.317 8 GenericIRPPort M getOperationProfile (note 3) See TS 32.317 8 GenericIRPPort O getNo

49、tificationProfile (note 3) See TS 32.317 8 GenericIRPPort O NOTE 1: The operation is under the port type SCIRPSystem:SCIRPPortType and under the binding SCIRPSystem:SCIRPBinding. NOTE 2: The IS equivalent maps to an XML definition specified in 3GPP TS 32.505 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