The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements.
Advanced Alarm Management (AAM) Integration Reference Point (IRP): Information Service (IS).
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 IRPs is defined in TS 32.150.
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 the 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.
The present specifies the Solution Set definitions for the IRP whose semantics are specified in the Advanced Alarm Management (AAM) IRP Information Service (TS 32.122).
This Solution Set specification is related to TS 32.122 v14.0.X.
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 specific 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 present document.
For the purposes of the present document, the terms and definitions given in TR 21.905, TS 32.101, TS 32.102, TS 32.150 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Two alarms are considered alike, if the corresponding alarm notifications 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 determines the end of a time span
file containing an XML document
composed of the succession of an optional XML declaration followed by a root XML element
it specifies the version of XML being used
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 may contain other XML elements
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 simply of an XML empty-element tag
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
the beginning of a non-empty XML element is marked by an XML start-tag containing the name and the set of XML attribute specifications of the XML element
the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML element
XML empty-element tag:
composed simply of an empty-element tag containing the name and the set of XML attribute specifications of the XML element.
XML attribute specification:
has a name and a value
defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD
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 document; an XML schema is itself also an XML document that shall conform with the XML schema for XML schemas
enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by different XML schemas
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 attribute specifications and/or its XML content
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
For the purposes of the present document, the abbreviations given in TR 21.905, in TS 32.101, TS 32.102, TS 32.150, and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
This specification defines the following 3GPP Advance Alarm Management IRP Solution Set definitions:
Annex A provides the CORBA Solution Set.
Annex B provides the XML Definitions.
Annex C provides the SOAP Solution Set.