|
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Self-Organizing Networks (SON);
Self-healing concepts and requirements
(3GPP TS 32.541 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 32.541 version 15.0.0 Release 15 1 ETSI TS 132 541 V15.0.0 (2018-11)
Reference
RTS/TSGS-0532541vf00
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 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or 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 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
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic 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.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 32.541 version 15.0.0 Release 15 2 ETSI TS 132 541 V15.0.0 (2018-11)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining 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 Secretariat. 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 the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
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 identities, 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
.
Modal verbs terminology
In the present document "shall", "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 used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 32.541 version 15.0.0 Release 15 3 ETSI TS 132 541 V15.0.0 (2018-11)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 7
4 Concepts and background . 7
4.1 Overview . 7
4.1.1 General description . 7
4.1.2 Recovery actions . 8
4.1.3 General Self-healing procedure . 8
4.2 Self-healing Concept . 11
4.2.1 Logical Function Blocks . 11
4.2.1.1 Self-healing Input Monitoring Function (SH_MON_F) . 11
4.2.1.2 Self-healing Diagnosis Function (SH_DG_F). 11
4.2.1.3 Triggering Recovery Action/s Function (SH_TG_F) . 11
4.2.1.4 Self-healing Evaluating Function (SH_EV_F) . 11
4.1.2.5 Self-healing Fallback Function (SH_FB_F) . 11
4.2.1.6 NRM IRP Update Function (NRM_UF) . 11
4.2.1.7 Self-healing Monitoring and Management Function (SH_MMF). 11
4.2.1.7.1 Self-healing Monitoring and Management Function (SH_MMF_NM). 11
4.2.1.7.2 Self-healing Monitoring and Management Function (SH_MMF_EM) . 11
4.2.1.8 Self-healing of Cell Outage Function (SH_CO_F) . 11
4.2.1.9 Self Recovery of NE software Function (SR_NSW_F) . 11
4.2.1.10 Self-healing of Board Fault Function (SH_BF_F) . 11
5 Business level requirements . 12
5.1 Requirements . 12
5.2 Actor roles . 12
5.3 Telecommunications Resources . 12
5.4 High-Level use case . 13
5.4.1 Alarm Triggered Self-healing . 13
5.4.2 Cell outage scenarios . 13
6 Specification level requirements . 14
6.1 Requirements . 14
6.1.1 Monitoring and Management part . 14
6.1.2 Self-healing of Cell Outage Function . 14
6.2 Actor roles . 15
6.3 Telecommunications Resources . 15
6.4 Use case . 15
6.4.1 Self Recovery of NE Software . 15
6.4.2 Self-healing of board faults . 16
6.4.3 Self Healing of Cell Outage . 17
6.4.3.1 Use case Cell Outage Detection . 17
6.4.3.2 Use case Cell Outage Recovery . 17
6.4.3.3 Use case Cell Outage Compensation. 18
6.4.3.4 Use case Return from Cell Outage Compensation . 18
7 Functions and Architecture . 19
7.1 Self-healing Logical Architecture . 19
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 32.541 version 15.0.0 Release 15 4 ETSI TS 132 541 V15.0.0 (2018-11)
7.2 Self-healing Reference Model . 20
Annex A (informative): Change history . 21
History . 22
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 32.541 version 15.0.0 Release 15 5 ETSI TS 132 541 V15.0.0 (2018-11)
Foreword
rd
This Technical Specification has been produced by the 3 Generation 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 change 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 substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
rd
The present document is part of a TS-family covering the 3 Generation Partnership Project Technical Specification
Group Services and System Aspects, Telecommunication management; as identified below:
32.541: "Self-Organizing Networks (SON); Self-Healing Concepts and Requirements"
Stage 2 for Self-Healing is not in a TS of its own. Stage 2 for selected Self-Healing functions is or will be part of 32.522
[6] and 32.762 [7].
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 32.541 version 15.0.0 Release 15 6 ETSI TS 132 541 V15.0.0 (2018-11)
1 Scope
The present document describes concept and requirements of OAM for Self-Healing of Self-Organizing Networks
(SON).
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]. 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[2] 3GPP TS 32.102: "Telecommunication management; Architecture".
[3] 3GPP TS 32.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault
management requirements".
[4] 3GPP TS 32.301: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP): Requirements".
[5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[6] 3GPP TS 32.522: "Telecommunication management; Self-Organizing Networks (SON) Policy
Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)"
[7] 3GPP TS 32.762: "Telecommunication management; Evolved Universal Terrestrial Radio Access
Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP);
Information Service (IS)"
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [5] 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 [5].
alarm: See 3GPP TS 32.111-1 [3].
Cell Outage: Cell outage is the total loss of radio services in the coverage area of a cell.
fault: See 3GPP TS 32.111-1 [3].
Stop condition: The Self-healing procedure may include one or more iterations until the related fault is resolved or the
thresholds of some parameters (e.g. iteration counter or iteration duration time, etc.) are reached. These thresholds may
be used to determine whether to stop the procedure if the related fault is still not resolved after several iterations or a
long time. We call these thresholds as well as fault resolution the stop conditions.
Self-healing Process: When a TCoSH is reached, particular action(s) will be triggered to solve or mitigate the
particular fault.
Self-healing Function: a Self-healing Function is to monitor a particular TCoSH and then, if necessary, to trigger a
Self-healing Process to solve or mitigate the particular fault.
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 32.541 version 15.0.0 Release 15 7 ETSI TS 132 541 V15.0.0 (2018-11)
Trigger Condition of Self-Healing (TCoSH): it is the condition which is used to judge whether a Self-healing Process
needs to be started. This condition could be an alarm or the detection of a fault.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [5] 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 [5].
ADAC Automatically Detected and Automatically Cleared
ADMC Automatically Detected and Manually Cleared
EM Element Manager
EPC Evolved Packet Core
E-UTRAN Evolved Universal Terrestrial Radio Access Network
NE Network Element
NM Network Manager
OAM Operation Administration Maintenance
SON Self Organizing Networks
TCoSH Trigger Condition of Self-Healing
UE User Equipment
4 Concepts and background
4.1 Overview
4.1.1 General description
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.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 32.541 version 15.0.0 Release 15 8 ETSI TS 132 541 V15.0.0 (2018-11)
4.1.2 Recovery actions
：
In the case of software faults, the recovery actions may be
a) system initializations (at different levels),
b) reload of a backup of software,
c) activation of a fallback software load,
d) download of a software unit,
e) reconfiguration, etc.
In the case of hardware faults, the recovery actions depend on the existence and type of redundant (i.e. back-up)
resources.
If the faulty resource has no redundancy, the recovery actions may be:
a) Isolate and remove the faulty resource from service so that it does not disturb other working resources;
b) Remove the physical and functional resources (if any) from the service, which are dependent on the faulty
one. This prevents the propagation of the fault effects to other fault-free resources;
c) State management related activities for the faulty resource and other affected/dependent resources;
d) Reset the faulty resource;
e) Other reconfiguration actions, etc.
If the faulty resource has redundancy, the recovery action shall be changeover, which includes the action a), c) and d)
above and a specific recovery sequence. The detail of the specific recovery sequence is out of the scope of the present
document.
In the case of other kinds of faults, the recovery actions are FFS.
4.1.3 General Self-healing procedure
The Self-healing Function has two parts: the monitoring part and the healing process part. The logic view of the general
Self-healing procedure is shown in figure 4.1.3-1:
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 32.
...