ETSI TS 132 111-7-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fault Management Par.pdf

《ETSI TS 132 111-7-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fault Management Par.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 111-7-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fault Management Par.pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 111-7 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Fault Management;Part 7: Alarm IRP SOAP Solution Set (SS) (3GPP TS 32.111-7 version 9.0.0 Release 9)ETSI

2、 ETSI TS 132 111-7 V9.0.0 (2010-01)13GPP TS 32.111-7 version 9.0.0 Release 9 Reference RTS/TSGS-0532111-7v900 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 Association b

3、ut 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 or perceived

4、 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 should be aw

5、are 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 services: h

6、ttp:/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 reserved. DECT

7、TM, 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 being regist

8、ered 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 111-7 V9.0.0 (2010-01)23GPP TS 32.111-7 version 9.0.0 Release 9 Intellectual Property Rights IPRs essential or potentially e

9、ssential 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, IPRs no

10、tified 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 guarantee

11、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 Project (3G

12、PP). 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 can be fo

13、und under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 111-7 V9.0.0 (2010-01)33GPP TS 32.111-7 version 9.0.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g3

14、3.2 Abbreviations . 6g34 Architectural features . 6g34.1 General . 6g35 Mapping . 8g35.1 Operation and notification mapping . 8g35.2 Operation parameter mapping 8g35.2.1 Operation acknowledgeAlarms . 9g35.2.1.1 Input parameters 9g35.2.1.2 Output parameters . 9g35.2.1.3 Fault definition 9g35.2.2 Oper

15、ation getAlarmList . 9g35.2.2.1 Input parameters 9g35.2.2.2 Output parameters . 10g35.2.2.3 Fault definition 10g35.2.3 Operation getAlarmCount 10g35.2.3.1 Input parameters 10g35.2.3.2 Output parameters . 10g35.2.3.3 Fault definition 11g35.2.4 Operation unacknowledgeAlarms . 11g35.2.4.1 Input paramet

16、ers 11g35.2.4.2 Output parameters . 11g35.2.4.3 Fault definition 11g35.2.5 Operation setComment . 12g35.2.5.1 Input parameters 12g35.2.5.2 Output parameters . 12g35.2.5.3 Fault definition 12g35.2.6 Operation clearAlarms . 12g35.2.6.1 Input parameters 12g35.2.6.2 Output parameters . 13g35.2.6.3 Fault

17、 definition 13g3Annex A (normative): WSDL specifications 14g3Annex B (informative): Void . 19g3Annex C (informative): Change history . 20g3History 21g3ETSI ETSI TS 132 111-7 V9.0.0 (2010-01)43GPP TS 32.111-7 version 9.0.0 Release 9 Foreword This Technical Specification (TS) has been produced by the

18、3rdGeneration 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 relea

19、se 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 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. t

20、echnical 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 S

21、ystem Aspects; Telecommunication management; as identified below: 32.111-1 Fault Management; Part 1: 3G fault management requirements. 32.111-2 Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS). 32.111-3 Fault Management; Part 3: Alarm Integration Reference

22、Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS). 32.111-5 Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions. 32.111-7 Alarm Integration Reference Point (IRP): SOAP Solution Set (SS). ETSI ETSI TS 132 111-7 V9.0.0 (2010-01)53GPP TS

23、32.111-7 version 9.0.0 Release 9 1 Scope The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Alarm IRP: Information Service (3GPP TS 32.111-2 4). This Solution Set specification is related to 3GPP TS 32.111-2 V9.0.X. 2 References The following documents

24、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, subsequent revisions do not apply. For a non-speci

25、fic 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 TS 32.101: “Telecommunication management; Princip

26、les and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.111-1: “Telecommunication management; Fault Management; Part 1: 3G fault management requirements“. 4 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integra

27、tion Reference Point (IRP): Information Service (IS)“. 5 3GPP TS 32.111-5: “Telecommunication management; Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 6 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Req

28、uirements“. 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 solution set“. 9 3GPP TS 32.150: “Telecommunicatio

29、n 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 (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/)

30、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 111-7 V9.0.0 (2010-01)63GPP TS 32.111-7 version 9.0.0 Release 9

31、3 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.111-1 3 and the following apply: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 6

32、. 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 Alarm IRP is specified in 3GPP TS 32.111-2 4. Thi

33、s 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. This specification uses “literal“ encoding

34、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 Alarm IRP SOAP SS uses the Notification IRP SOAP SS of 3GPP TS 32.307 10. The IRPAgent shall su

35、pport the push interface model, which means that the IRPAgent sends alarm notifications to the IRPManager as soon as new events occur. The IRPManager does not need to check (“pull“) for events. Relevant definitions are imported from the Alarm IRP XML definitions of 3GPP TS 32.111-5 5. This specifica

36、tion 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:/schemas.xmlsoap.org/wsdl/ soap http:/schemas.xmlsoap.org/wsdl/soap/alarmIRPSystem http:/www.3gpp.org/ftp/Specs/archive/32

37、_series/32.111-7#AlarmIRPSystem alarmIRPData http:/www.3gpp.org/ftp/Specs/archive/32_series/32.111-7#AlarmIRPData xai http:/www.3gpp.org/ftp/specs/archive/32_series/32.111-5#alarmIRPIOCsxn http:/www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrmgenericIRPSystem http:/www.3gpp.org/ftp/Specs/a

38、rchive/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 ETSI ETSI TS 132 111-7 V9.0.0 (2010-01)73GPP TS 32.111-7 version 9.0.0 Release 9 The WSDL structure is depicted in F

39、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

40、ice. Figure 4.1: Alarm IRP SOAP Solution Set WSDL structure ETSI ETSI TS 132 111-7 V9.0.0 (2010-01)83GPP TS 32.111-7 version 9.0.0 Release 9 5 Mapping 5.1 Operation and notification mapping The Alarm IRP IS (3GPP TS 32.111-2 4) defines the operations and their semantics. Table 5.1 maps the operation

41、s defined in the Alarm 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 Alarm IRP IS, as well as inherited operations. Table 5.1 also qualifies if an operation is Mandatory (M) or Optional (

42、O). Table 5.1: Mapping from IS Operation to SS Equivalents IS Operation in 3GPP TS 32.111-2 4 SS: Operation of WSDL port type and WSDL binding SS: Port of AlarmIRPService Qualifier acknowledgeAlarms acknowledgeAlarms (note 1) AlarmIRPPort M getAlarmList getAlarmList (note 1) AlarmIRPPort M getAlarmC

43、ount getAlarmCount (note 1) AlarmIRPPort O unacknowledgeAlarms unacknowledgeAlarms (note 1) AlarmIRPPort O setComment setComment (note 1) AlarmIRPPort O clearAlarms clearAlarms (note 1) AlarmIRPPort OnotifyNewAlarm notify (note 2) NotificationIRPNtfPort M notifyAckStateChanged notify (note 2) Notifi

44、cationIRPNtfPort M notifyClearedAlarm notify (note 2) NotificationIRPNtfPort M notifyAlarmListRebuilt notify (note 2) NotificationIRPNtfPort M notifyChangedAlarm notify (note 2) NotificationIRPNtfPort O notifyComments notify (note 2) NotificationIRPNtfPort O notifyPotentialFaultyAlarmList notify (no

45、te 2) NotificationIRPNtfPort O 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 type alarmIRPSystem:AlarmIRPPortType and under

46、 the binding alarmIRPSystem:AlarmIRPBinding. NOTE 2: The IS equivalent maps to an XML definition specified in 3GPP TS 32.111-5 5, and this being an input parameter to the operation notify under the port type ntfIRPNtfSystem:NotificationIRPNtf and under the binding ntfIRPNtfSystem:NotificationIRPNtf

47、of 3GPP TS 32.307 10. This binding is linked to a port of the AlarmIRPService 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 by the AlarmIRP IOC of 3GPP TS 32.111-2 4 inheriting from the Managed

48、GenericIRP IOC. The corresponding binding is linked to a port of the AlarmIRPService as indicated in the table above. 5.2 Operation parameter mapping The Alarm IRP IS (3GPP TS 32.111-2 4) defines semantics of parameters carried in the operations. The tables below show the mapping of these parameters

49、, as per operation, to their equivalents defined in this SS. ETSI ETSI TS 132 111-7 V9.0.0 (2010-01)93GPP TS 32.111-7 version 9.0.0 Release 9 5.2.1 Operation acknowledgeAlarms 5.2.1.1 Input parameters Table 5.2.1.1: Mapping from IS acknowledgeAlarms 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 alarmInformationAndSeverityReferenceList alar