1、 ETSI TS 132 126 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 32.126 versi
2、on 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 126 V14.0.0 (2017-04)13GPP TS 32.126 version 14.0.0 Release 14Reference RTS/TSGS-0532126ve00 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
3、 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 print. The c
4、ontent 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 Portable D
5、ocument 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:/portal.etsi
6、.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, electronic or me
7、chanical, 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. European Telecommunicati
8、ons Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is
9、protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 126 V14.0.0 (2017-04)23GPP TS 32.126 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may h
10、ave 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 stan
11、dards“, which 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 r
12、eferenced 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 to technical spe
13、cifications 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/queryform.asp. M
14、odal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “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“ ar
15、e NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 126 V14.0.0 (2017-04)33GPP TS 32.126 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definiti
16、ons and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Solution Set definitions 8g3Annex A (normative): CORBA Solution Set . 9 g3A.0 General . 9g3A.1 Architectural features . 9g3A.1.0 Introduction 9g3A.1.1 Syntax for Distinguished Names 9g3A.1.2 Notifications . 9g3A.2 Mapping . 9g3A.
17、2.1 General mappings . 9g3A.2.2 Operation and notification mapping . 9g3A.2.3 Operation parameter mapping 10g3A.2.4 Notification parameter mapping . 10g3A.3 Solution Set definitions 11g3A.3.1 IDL definition structure 11g3A.3.2 IDL specification (file name “AAMConstDefs.idl“) 12g3A.3.3 IDL specificat
18、ion (file name “AAMSystem.idl“) . 14g3Annex B (normative): XML definitions . 16g3B.0 General . 16g3B.1 Architectural Features 16g3B.1.0 Introduction 16g3B.1.1 Syntax for Distinguished Names 16g3B.1.2 Notification Services 16g3B.1.3 IOC definitions . 16g3B.2 Mapping . 16g3B.3 Solution Set definitions
19、 16g3B.3.1 XML definition structure 16g3B.3.2 Graphical Representation . 17g3B.3.3 XML Schema “aamIRPIOCs.xsd” . 18g3Annex C (normative): SOAP Solution Set . 20g3C.0 General . 20g3C.1 Architectural features . 20g3C.1.0 Introduction 20g3C.1.1 Syntax for Distinguished Names 20g3C.1.2 Notification Serv
20、ices 20g3ETSI ETSI TS 132 126 V14.0.0 (2017-04)43GPP TS 32.126 version 14.0.0 Release 14C.1.3 Supported W3C specifications . 20g3C.1.4 Prefixes and namespaces 20g3C.2 Mapping . 21g3C.2.1 Operation and notification mapping . 21g3C.2.2 Operation parameter mapping 21g3C.2.3 Notification parameter mappi
21、ng . 22g3C.3 Solution Set definitions 22g3C.3.1 WSDL definition structure . 22g3C.3.2 Graphical Representation . 22g3C.3.3 WSDL specification “AAMIRPSystem.wsdl” . 23g3Annex D (informative): Change history . 26g3History 27g3ETSI ETSI TS 132 126 V14.0.0 (2017-04)53GPP TS 32.126 version 14.0.0 Release
22、 14Foreword This Technical 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
23、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 or greater indicates TSG approved document under change control. y th
24、e 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 The present document is part of a TS-family covering the 3rdGeneration
25、 Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.121: Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements. 32.122: Advanced Alarm Management (AAM) Integration Reference Point (IRP): Info
26、rmation Service (IS). 32.126: Advanced Alarm Management (AAM) Integration Reference Point (IRP): Solution Set (SS) definitions. The Itf-N interface is built up by a number of IRPs and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the
27、 IRPs is defined in 3GPP TS 32.150 4. A single network fault may generate a large number of alarms over space and time. In a large and complex network, simultaneous network faults may occur, causing the network operator to be flooded with high volume of alarms. The high volume of alarms, typically t
28、he one received by an IRPManager via the getAlarmList or alarm notifications of Alarm IRP specification, greatly inhibits the operator ability to quickly identify and locate the responsible network faults. Advanced Alarm Management IRP is intended to provide methods to improve this situation. ETSI E
29、TSI TS 132 126 V14.0.0 (2017-04)63GPP TS 32.126 version 14.0.0 Release 141 Scope The present specifies the Solution Set definitions for the IRP whose semantics are specified in the Advanced Alarm Management (AAM) IRP Information Service (3GPP TS 32.122 6). This Solution Set specification is related
30、to TS 32.122 v13.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.) or non-specific. - For a spec
31、ific reference, 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 presen
32、t document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (
33、IRP) Concept and definitions“. 5 3GPP TS 32.121: “Telecommunication management; Advanced Alarm Mangement (AAM) Integration Reference Point (IRP): Requirements“. 6 3GPP TS 32.122: “Telecommunication management; Advanced Alarm Management (AAM) Integrations Reference Point (IRP); Information Service (I
34、S)“. 7 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 8 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 9 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 10 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 11 W3C REC-xml-names-19
35、990114: “Namespaces in XML“. 12 W3C SOAP 1.1 specification (http:/www.w3.org/TR/2000/NOTE-SOAP-20000508/) 13 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 14 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 15 W3C SOAP 1.2 specification (http:/www.
36、w3.org/TR/soap12-part1/) 16 3GPP TS 32.306: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set definitions“. 17 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Ser
37、vice (IS)” 18 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. ETSI ETSI TS 132 126 V14.0.0 (2017-04)73GPP TS 32.126 version 14.0.0 Release 143 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, t
38、he terms and definitions given in TR 21.905 1, 3GPP TS 32.101 2, 3GPP TS 32.102 3, 3GPP TS 32.150 4 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. Alike Alarm: Two alarms are considered alike, if the corresponding alarm no
39、tifications are issued by the same object instance with the same alarmType, same perceivedSeverity, same probableCause and same specificProblem (if present). Lower Edge of Time Window: The point in time which determines the begin of a time span. Upper Edge of Time Window: The point in time which det
40、ermines the end of a time span XML file: file containing an XML document XML document: composed of the succession of an optional XML declaration followed by a root XML element NOTE: See 7; in the scope of the present document. XML declaration: it specifies the version of XML being used NOTE: See 7.
41、XML element: has a type, is identified by a name, may have a set of XML attribute specifications and is either composed of the succession of an XML start-tag followed by the XML content of the XML element followed by an XML end-tag, or composed simply of an XML empty-element tag; each XML element ma
42、y contain other XML elements NOTE: See 7. empty XML element: having an empty XML content; an empty XML element still possibly has a set of XML attribute specifications; an empty XML element is either composed of the succession of an XML start-tag directly followed by an XML end-tag, or composed simp
43、ly of an XML empty-element tag NOTE: See 7. XML content (of an XML element): empty if the XML element is simply composed of an XML empty-element tag; otherwise the part, possibly empty, of the XML element between its XML start-tag and its XML end-tag XML start-tag: the beginning of a non-empty XML e
44、lement is marked by an XML start-tag containing the name and the set of XML attribute specifications of the XML element NOTE: See 7. XML end-tag: the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML element NOTE: See 7. XML empty-element tag: composed simply
45、of an empty-element tag containing the name and the set of XML attribute specifications of the XML element. NOTE: See 7. XML attribute specification: has a name and a value NOTE: See 7. DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this
46、DTD NOTE: See 7. ETSI ETSI TS 132 126 V14.0.0 (2017-04)83GPP TS 32.126 version 14.0.0 Release 14XML schema: more powerful than a DTD, an XML schema defines structure and content constraints to be respected by an XML document to conform with this XML schema; through the use of XML namespaces several
47、XML schemas can be used together by a single XML document; an XML schema is itself also an XML document that shall conform with the XML schema for XML schemas NOTE: See 8, 9 and 10. XML namespace: enables qualifying element and attribute names used in XML documents by associating them with namespace
48、s identified by different XML schemas NOTE: See 11, in the scope of the present document. XML complex type: defined in an XML schema; cannot be directly used in an XML document; can be the concrete type or the derivation base type for an XML element type or for another XML complex type; ultimately d
49、efines constraints for an XML element on its XML attribute specifications and/or its XML content NOTE: See 8, 9 and 10. XML element type: declared by an XML schema; can be directly used in an XML document; as the concrete type of an XML element, directly or indirectly defines constraints on its XML attribute specifications and/or its XML content; can also be the concrete type or the derivation base type for another XML element type NOTE: See 8, 9 and 10 3.2 Abbreviations For the purpos
