1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommAdvanced AIntegratioSolutio(3GPP TS 32.1TECHNICAL SPECIFICATION132 126 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; d Alarm Management (AAM) tion Reference Point (IRP); tion Set (SS) definiti
2、ons .126 version 13.0.0 Release 1316-02) hase 2+); (UMTS); 13) ETSI ETSI TS 132 126 V13.0.0 (2016-02)13GPP TS 32.126 version 13.0.0 Release 13Reference RTS/TSGS-0532126vd00 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
3、 65 47 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/o
4、r in print. 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
5、of the 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 h
6、ttp:/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: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electroni
7、c 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. European Telecomm
8、unications Standards Institute 2016. 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. GSM and
9、the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 126 V13.0.0 (2016-02)23GPP TS 32.126 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertai
10、ning 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“, which is available from the ETSI Secretar
11、iat. 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 in ETSI SR 000 314 (or the updates on t
12、he 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 specifications or reports using their 3GPP identitie
13、s, 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. Modal verbs terminology In the present document “s
14、hall“, “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“ are NOT allowed in ETSI deliverables except when us
15、ed in direct citation. ETSI ETSI TS 132 126 V13.0.0 (2016-02)33GPP TS 32.126 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2
16、 Abbreviations . 8g34 Solution Set definitions 8g3Annex A (normative): CORBA Solution Set . 9g3A.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.2.1 General mappings . 9g3A.2.2 Operation and noti
17、fication 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 specification (file name “AAMSystem.idl“) . 14g3Annex B (nor
18、mative): 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 16g3B.3.1 XML definition structure 16g3B.3.2 Grap
19、hical 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 20g3ETSI ETSI TS 132 126 V13.0.0 (2016-02)43GPP TS 32.126 version 13.0.0 Releas
20、e 13C.1.2 Notification Services 20g3C.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 mapping . 22g3C.3 Solution Set definitions 22g3C.3.1 WSDL
21、 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 V13.0.0 (2016-02)53GPP TS 32.126 version 13.0.0 Release 13Foreword This Technical Specification has been prod
22、uced 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 TSG with an identifying cha
23、nge 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 incremented for all changes of subst
24、ance, 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; Technical Specification Group Se
25、rvices 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): Information Service (IS). 32.126: Advanced Alarm Managemen
26、t (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 IRPs is defined in 3GPP TS 32.150 4. A single network
27、 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 the one received by an IRPManager via the getAlarmList
28、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 ETSI TS 132 126 V13.0.0 (2016-02)63GPP TS 32.126 versio
29、n 13.0.0 Release 131 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 to TS 32.122 v12.0.X. 2 References The following docum
30、ents 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 specific reference, subsequent revisions do not apply. - F
31、or 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 TR 21.905: “Vocabulary for 3GPP Spe
32、cifications“. 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 (IRP) Concept and definitions“. 5 3GPP TS 32.121: “Tele
33、communication 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 (IS)“. 7 W3C REC-xml-20001006: “Extensible Markup Langua
34、ge (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-19990114: “Namespaces in XML“. 12 W3C SOAP 1.1 specifica
35、tion (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.w3.org/TR/soap12-part1/) 16 3GPP TS 32.306: “Telecommu
36、nication 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 Service (IS) 18 3GPP TS 32.300: “Telecommunication manage
37、ment; Configuration Management (CM); Name convention for Managed Objects“. ETSI ETSI TS 132 126 V13.0.0 (2016-02)73GPP TS 32.126 version 13.0.0 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1, 3GPP TS
38、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 notifications are issued by the same object instance with
39、 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 determines the end of a time span XML file: file containin
40、g 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. XML element: has a type, is identified by a name, may h
41、ave 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 may contain other XML elements NOTE: See 7. empty XML ele
42、ment: 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 simply of an XML empty-element tag NOTE: See 7. XML content
43、 (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 element is marked by an XML start-tag containing the nam
44、e 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 of an empty-element tag containing the name and the set
45、 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 DTD NOTE: See 7. ETSI ETSI TS 132 126 V13.0.0 (2016-02)
46、83GPP TS 32.126 version 13.0.0 Release 13XML 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 XML schemas can be used together by a single XML docume
47、nt; 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 namespaces identified by different XML schemas NOTE: See 11, in
48、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 defines constraints for an XML element on its XML attrib
49、ute 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 purposes of the present document, the abbreviations give
