Content for TS 28.111 Word version: 19.3.0
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
...
...
1 Scope p. 8
The present document describes the SBMA based Fault Management Service (see TS 28.533). It includes stages 1, 2 and 3.
The Fault Management MnS is based on the SBMA principles using CRUD operations, modelled OAM data in the NRM together with fault management specific notifications. An IRP based solution for fault management is out of scope for the present document.
2 References p. 8
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 28.532: "Management and orchestration; Generic Management services".
[3]
ETSI TS 101 251 (V6.3.0): "Digital cellular telecommunications system (Phase 2+); Fault management of the Base Station System (BSS) (GSM 12.11 version 6.3.0 Release 1997)".
[4] Void.
[5]
TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[6] Void.
[7]
ITU-T Recommendation M.3100: "Generic network information model".
[8]
ITU-T Recommendation X.733 (02/92): "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function".
[9]
Text Attribution: Creator: ONAP, under Creative Commons Attribution 4.0 International License, https://creativecommons.org/licenses/by/4.0/ , URI to access the text: https://github.com/onap/vnfrqts-requirements/blob/05f26fac2b941513a7d0e856b99fd8c61d688299/docs/Chapter8/ves7_1spec.rst#resource-structure .
[10]
TS 32.158: "Management and orchestration; Design rules for Representational State Transfer (REST) Solution Sets (SS)".
[11] Void.
[12]
TS 32.401: "Telecommunication management; Performance Measurement (PM); Concept and requirements".
[13]
ITU-T Recommendation X.736 (01/92): "Information technology - Open Systems Interconnection - Systems Management: Security alarm reporting function".
[14]
TS 28.533: "Management and orchestration; Architecture framework".
[15]
TS 32.160: "Management and orchestration; Management service template".
[16]
TS 28.623: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
3 Definitions of terms, symbols and abbreviations p. 9
3.1 Terms p. 9
For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Alarm:
A management representation of a fault, an error or a failure that requires attention or reaction by an operator or some machine. Alarms have state.
Alarm identifying attributes:
A set of attributes (objectInstance, alarmType, probableCause and specificProblem, if present) that identify an alarm. ObjectInstance identifies the network resource ,while alarmType, probableCause and specificProblem (if present) identify the alarming condition.
Alarming condition:
Identifies the reason an alarm is raised. Identified by a combination of alarmType, probableCause and specificProblem (if present).
Error:
A state of the system different from the correct system state. An error may or may not lead to a service failure. An error has a begin and end time.
Event:
Anything that occurs at a certain point in time, for example a configuration change, a threshold crossing, a transition to an error state or a transition to a failure state. Events do not have states.
Failure:
A state of inability to deliver the correct service as defined by the service specification. A service failure is the result of an error. A failure has a begin and end time.
Fault:
The (hypothesized or adjudged) cause for an error or a failure (such as system malfunctions, a defect in system design, a defect in software, or external interference).
MonitoredEntity:
Any class that can have an alarmed state.
Root cause:
The primary fault (cause), if any, leading to one or multiple errors or failures.
3.2 Symbols p. 9
Void.
3.3 Abbreviations p. 9
For the purposes of the present document, the abbreviations given in TR 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 TR 21.905.
ADAC
Automatically Detected and Automatically Cleared
ADMC
Automatically Detected and Manually Cleared
CRUD
Create, Read, Update and Delete
FM
Fault Management
MnS
Management Service
NRM
Network Resource Model
SBMA
Service Based Management Architecture
