ETSI TS 132 111-6-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fault Manageme.pdf

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

1、 ETSI TS 132 111-6 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Fault Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions (3GPP TS 32.111-6 v

2、ersion 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 132 111-6 V15.0.0 (2018-07)13GPP TS 32.111-6 version 15.0.0 Release 15Reference RTS/TSGS-0532111-6vf00 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

3、16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in pr

4、int. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the

5、Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users 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 https:/p

6、ortal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electr

7、onic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All

8、 rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its M

9、embers. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 132 111-6 V15.0.0 (2018-07)23GPP TS 32.111-6 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been de

10、clared 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 standards“, whi

11、ch is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). 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 other IPRs not referenced i

12、n 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. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except fo

13、r any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Fo

14、reword This Technical Specification (TS) has been produced by ETSI 3rd Generation 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 c

15、orresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “

16、cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 111-6 V15.0.0 (2018-07)33GPP TS 32.111-6 version 15.0.

17、0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Solution Set Definitions . 7g3Annex A (normative): CORBA Solution Se

18、t . 9g3A.0 General . 9g3A.1 Architectural Features 9g3A.1.0 Introduction 9g3A.1.1 Syntax for Distinguished Names 9g3A.1.2 Notification Services 9g3A.1.3 Push and Pull Style . 9g3A.1.4 Support multiple notifications in one push operation . 9g3A.1.5 AlarmIRPNotifications Interface 9g3A.1.5.1 Method pu

19、sh (M) 9g3A.1.6 Filter . 10g3A.2 Mapping . 10g3A.2.1 Operation and Notification mapping 10g3A.2.2 Operation parameter mapping 11g3A.2.3 Notification parameter mapping . 20g3A.3 Solution Set definitions 32g3A.3.1 IDL definition structure 32g3A.3.2 IDL specification “AlarmIRPConstDefs.idl“ . 32g3A.3.3

20、 IDL specification “AlarmIRPSystem.idl” 39g3A.3.4 IDL specification “AlarmIRPNotifications.idl“ . 42g3Annex B (normative): XML Definitions 49g3B.0 General . 49g3B.1 Architectural Features 49g3B.1.0 Introduction 49g3B.1.1 Syntax for Distinguished Names 49g3B.1.2 Notification Services 49g3B.1.3 IOC De

21、finitions 49g3B.2 Mapping . 49g3B.3 Solution Set definitions 49g3B.3.1 XML definition structure 49g3B.3.2 Graphical Representation . 50g3B.3.3 XML Schema “alarmIRPNotif.xsd” . 55g3B.3.4 XML Schema “alarmIRPIOCs.xsd” . 59g3Annex C (normative): SOAP Solution Set . 66g3ETSI ETSI TS 132 111-6 V15.0.0 (2

22、018-07)43GPP TS 32.111-6 version 15.0.0 Release 15C.0 General . 66g3C.1 Architectural features . 66g3C.1.0 Introduction 66g3C.1.1 Syntax for Distinguished Names 66g3C.1.2 Notification Services 66g3C.1.3 Supported W3C specifications . 66g3C.1.4 Prefixes and namespaces 66g3C.2 Mapping . 67g3C.2.1 Oper

23、ation and notification mapping . 67g3C.2.2 Operation parameter mapping 67g3C.2.2.1 Operation acknowledgeAlarms . 68g3C.2.2.1.1 Input parameters 68g3C.2.2.1.2 Output parameters . 68g3C.2.2.1.3 Fault definition 68g3C.2.2.2 Operation getAlarmList . 68g3C.2.2.2.1 Input parameters 68g3C.2.2.2.2 Output pa

24、rameters . 69g3C.2.2.2.3 Fault definition 69g3C.2.2.3 Operation getAlarmCount 69g3C.2.2.3.1 Input parameters 69g3C.2.2.3.2 Output parameters . 69g3C.2.2.3.3 Fault definition 70g3C.2.2.4 Operation unacknowledgeAlarms 70g3C.2.2.4.1 Input parameters 70g3C.2.2.4.2 Output parameters . 70g3C.2.2.4.3 Fault

25、 definition 70g3C.2.2.5 Operation setComment . 71g3C.2.2.5.1 Input parameters 71g3C.2.2.5.2 Output parameters . 71g3C.2.2.5.3 Fault definition 71g3C.2.2.6 Operation clearAlarms . 71g3C.2.2.6.1 Input parameters 71g3C.2.2.6.2 Output parameters . 72g3C.2.2.6.3 Fault definition 72g3C.3 Solution Set defi

26、nitions 73g3C.3.1 WSDL definition structure . 73g3C.3.2 Graphical Representation . 73g3C.3.3 WSDL specification “AlarmIRPSystem.wsdl” 74g3Annex D (informative): Change history . 82g3History 83g3ETSI ETSI TS 132 111-6 V15.0.0 (2018-07)53GPP TS 32.111-6 version 15.0.0 Release 15Foreword This Technical

27、 Specification 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 approval. Should the TSG modify the contents of the present document, it will be re-released by the

28、 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 or greater indicates TSG approved document under change control. y the second digit is incremen

29、ted 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 The present document is part of a TS-family covering the 3rdGeneration Partnership Project: Tech

30、nical Specification Group Services and System 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-6 “Fault Man

31、agement; Alarm Integration Reference Point (IRP); Solution Set (SS) definitions“. The present document is part of a TS-family, which describes the requirements and information model necessary for Telecommunications Management (TM). The TM principles and TM architecture are specified in 3GPP TS 32.10

32、1 1 and 3GPP TS 32.102 2. A communications system is composed of a multitude of Network Elements (NE) of various types and, typically, different vendors, which inter-operate in a coordinated manner in order to satisfy the network users communication requirements. The occurrence of faults in an NE ma

33、y cause deterioration or loss of this NEs function. Fault Management is the functional area, which allows the operator to detect the occurrence of faults in the network in real-time. Configuration Management and Performance Management are two more functional areas, which require the operator to be a

34、lerted to certain conditions in the network. A standard general-purpose mechanism for the management of logs containing selected notifications from the network is required to provide an ability to perform historical analysis on faults and conditions, which occurred in the network. The TS 32.33x-seri

35、es, constituting the Notification Log IRP, sets forth such a mechanism - and Annex B of the present document contains the XML definition related to Alarm IRP notifications. ETSI ETSI TS 132 111-6 V15.0.0 (2018-07)63GPP TS 32.111-6 version 15.0.0 Release 151 Scope The present document contains the So

36、lution Sets for the IRP whose semantics is specified in Alarm IRP: Information Service (TS 32.111-2 4). These Solution Set specifications are related to 3GPP TS 32.111-2 V14. 0.X 4. 2 References The following documents contain provisions which, through reference in this text, constitute provisions o

37、f 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 reference, the latest version applies. In the case of a reference to

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

39、anagement; 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 Integration Reference Point: Information Service (IS)“. 5 3GPP TS 32.150: “Tele

40、communication management; Integration Reference Point (IRP) Concept and definitions“. 6 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 7 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Int

41、egration Reference Point (IRP): Information Service (IS)“. 8 3GPP TS 32.306: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions“. 9 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Po

42、int (IRP) management; Requirements“. 10 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 11 3GPP TS 32.316: “Telecommunication management; Generic Integration Reference Point (IRP) management: Solution Set (SS) definition

43、s“. 12 3GPP TS 32.331: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements“. 13 3GPP TS 32.336: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Solution Set (SS) definitions“. 14 OMG TC Document telecom/98-11-01

44、: “OMG Notification Service“. http:/www.omg.org/technology/documents/ 15 OMG CORBA Services: “Common Object Services Specification, Update: November 22, 1996“ (Clause 4 contains the Event Service specification). http:/www.omg.org/technology/documents/ ETSI ETSI TS 132 111-6 V15.0.0 (2018-07)73GPP TS

45、 32.111-6 version 15.0.0 Release 1516 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 17 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 18 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 19 W3C XPath 1.0 specification (http:/www.w3.o

46、rg/TR/1999/REC-xpath-19991116) 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.111-1 3, 3GPP TS 32.111-2 4, 3GPP TS 32.150 5 and 3GPP TS 32.331 12 apply. IRP document version n

47、umber string The IRP document version number (sometimes called “IRP version” or “version number”) string is used to identify the present document. The definition of “IRP document version number string” in 3GPP TS 32.311 9 provides the rule to derive such a string. This string is used for the return

48、value of get_alarm_irp_versions(). It is used as return value of get_notification_categories() if the Notification IRP supports the emission of notifications defined by this Alarm IRP version. It is also used in the domain_name attribute of a structured event carrying alarm information defined by th

49、is Alarm IRP version. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CORBA Common Object Request Broker Architecture IDL Interface Definition Language IRP Integration Reference Point IS Information Service MOC Managed Object Class MOI Managed Object Instance NE Network Element NL Notification LogOMG Object Management Group SS Solution Set TMN Telecommunications Management Network UML Unified Modelling Language WSDL Web Service Description Language XML eXtensible