Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 32.111-2  Word version:  16.0.0

Top   Top   None   None   Next
0…   5…   6…

 

0  IntroductionWord‑p. 7
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:
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 Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions.
The present document is part of a set of TSs which describes the requirements and information model necessary for the Telecommunication Management (TM) of 3GPP systems. The TM principles and TM architecture are specified in TS 32.101 and TS 32.102.
A 3GPP system is composed of a multitude of Network Elements (NE) of various types and, typically, different vendors inter-operate in a co-ordinated manner in order to satisfy the network users' communication requirements.
The occurrence of failures in a NE may cause a deterioration of this NE's function and/or service quality and will, in severe cases, lead to the complete unavailability of the NE. In order to minimize the effects of such failures on the Quality of Service (QoS) as perceived by the network users it is necessary to:
  • detect failures in the network as soon as they occur and alert the operating personnel as fast as possible;
    isolate the failures (autonomously or through operator intervention), i.e. switch off faulty units and, if applicable, limit the effect of the failure as much as possible by reconfiguration of the faulty NE/adjacent NEs;
  • if necessary, determine the cause of the failure using diagnosis and test routines; and,
  • repair/eliminate failures in due time through the application of maintenance procedures.
This aspect of the management environment is termed "Fault Management" (FM). The purpose of FM is to detect failures as soon as they occur and to limit their effects on the network QoS as far as possible.
The latter is achieved by bringing additional/redundant equipment into operation, reconfiguring existing equipment/NEs, or by repairing/eliminating the cause of the failure.
Fault Management (FM) encompasses all of the above functionalities except commissioning/decommissioning of NEs and potential operator triggered reconfiguration (these are a matter of Configuration Management).
FM also includes associated features in the Operations System (OS), such as the administration of alarm list, the presentation of operational state information of physical and logical devices/resources/functions, and the provision and analysis of the alarm and state history of the network.
Up

1  ScopeWord‑p. 9
The present document defines the Alarm Integration Reference Point (IRP) Information Service (IS), which addresses the alarm surveillance aspects of Fault Management (FM), applied to the Itf-N.
The purpose of the AlarmIRP is to define an interface through which a "system" (typically a Network Element Manager or a Network Element) can communicate alarm information for its managed objects to one or several Manager Systems (typically Network Management Systems).
The Alarm IRP IS defines the semantics of alarms and the interactions visible across the reference point in a protocol neutral way. It defines the semantics of the operations and notifications visible in the IRP. It does not define the syntax or encoding of the operations, notifications and their parameters.
Up

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 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.
[1]
TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
[2]
ITU-T Recommendation X.733 (02/92): "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function".
[3]
ITU-T Recommendation X.721 (02/92): "Information Technology - Open Systems Interconnection -Structure of management information: Definition of management information".
[4]
TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements".
[5]
TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
[6]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[7]
TS 32.102: "Telecommunication management; Architecture".
[8]  Void.
[9]
TS 32.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault management requirements".
[10]  Void.
[11]
ITU-T Recommendation M.3100 (04/05): "Generic network information model".
[12]  Void.
[13]  Void.
[14]
TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)".
[15]
ITU-T Recommendation X.736 (01/92): "Information technology - Open Systems Interconnection - Systems Management: Security alarm reporting function".
[16]
TS 21.905: "Vocabulary for 3GPP Specifications".
[17]
TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[18]
ETSI TS 101 251 V6.3.0 (1999-07): "Digital cellular telecommunications system (Phase 2+); Fault management of the Base Station System (BSS) (GSM 12.11 version 6.3.0 Release 1997) "
Up

3  Definitions and abbreviationsWord‑p. 10

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TS 32.101, TS 32.102, TS 32.111-1 , TS 21.905 and the following apply:
active alarm:
an alarm that has not been cleared ( i.e. an alarm whose perceivedSeverity is not Cleared).
Event:
Network occurrence which has significance for the management of an NE. Events do not have state.
IRPAgent:
See TS 32.150.
IRPManager:
See TS 32.150.
IRP document version number string (IRPVersion):
See TS 32.312.
Itf-N:
Management interface defined in TS 32.101, subclause 5.1.2.2 and TS 32.102, subclause 7.3.2.
Matching-Criteria-Attributes:
which identifies a set of ITU-T Recommendation X.733 [2] defined attributes. Notifications carrying identical values for these attributes are considered to be carrying alarm information related to (a) the same network resource and (b) the same alarmed condition. The matching-criteria-attributes are: objectInstance, eventType, probableCause and specificProblem, if present.
Notification:
Information message originated below Itf-N..
Up

3.2  Abbreviations

For the purposes of the present document, the abbreviations given in TS 32.101, TS 32.102, TS 32.111-1 , TS 21.905 and the following apply . An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TS 32.101, TS 32.102, TS 32.111-1 and TS 21.905, in that order.
DN
Distinguished Name
EM
Element Manager
FM
Fault Management
IOC
Information Object Class
IRP
Integration Reference Point
IS
Information Service
NE
Network Element
NM
Network Manager
OS
Operations System
QoS
Quality of Service
SS
Solution Set
SupportIOC
Support Information Object Class
TM
Telecommunication Management
UML
Unified Modelling Language
Up

4  Basic aspectsWord‑p. 11

4.1Void

4.2  System Context

The general definition of the System Context for the present IRP is found in TS 32.150 subclause 4.7.
In addition, the set of related IRP(s) relevant to the present IRP is shown in the two diagrams below.
[not reproduced yet]
Figure 1: System Context A
Up
[not reproduced yet]
Figure 2: System Context B
Up

Up   Top   ToC