Tech-invite   World Map
3GPPspecs     Glossaries     T+       IETF     RFCs     Groups     SIP     ABNFs
Top        in Index        Prev        Next

TS 32.541 (SA5)
Telecommunication management –
Self-Organizing Networks (SON) – Self-healing concepts and requirements

ToC      3GPP‑Page      ETSI‑search      Help       
V14.0.0 (PDF)    2017/03    23 p.
V13.0.0    2016/01    23 p.
V12.0.0    2014/10    23 p.
V11.0.0    2012/09    23 p.
V10.0.0    2011/03    23 p.

Rapporteur:  Mr. Zhu, Weihong
See also:  –

Self-healing is a functionality of SON. The purpose of Self-healing is to solve or mitigate the faults which could be solved automatically by triggering appropriate recovery actions.

From the point of view of fault management, for each detected fault, appropriate alarms shall be generated by the faulty network entity, regardless of whether it is an ADAC or an ADMC fault.

The trigger of Self-healing can be an alarm. In this case, the Self-healing functionality monitors the alarms, and when it finds alarm/s which could be solved automatically, it gathers more necessary information (e.g. measurements, testing result, etc) and does deep analysis, and then according to the analysis result, if necessary, it triggers appropriate recovery actions to solve the fault automatically.

For some Self-healing functions which are located in NEs and require more rapid response, the trigger of Self-healing can be the detection of a fault. Hence, when a fault is detected, an appropriate Self-healing Process will be triggered to try to heal the fault automatically.

The Self-healing functionality also monitors the execution of the recovery action/s and decides the next step accordingly. After a Self-healing procedure ended, the Self-healing functionality shall generate and forward appropriate notifications to inform the IRPManager about the Self-healing result and all the information of the performed recovery actions may be logged.

This TS describes concept and requirements of OAM for Self-Healing of Self-Organizing Networks (SON).


Here        Top



1   Scope   PDF-p. 6
2   References
3   Definitions and abbreviations
4   Concepts and background
5   Business level requirements   PDF-p. 12
6   Specification level requirements   PDF-p. 14
7   Functions and Architecture   PDF-p. 19
A   Change history   PDF-p. 21

Up        Top