|
TECHNICAL SPECIFICATIONION
Universal Mobile Telelecommunications System ( (UMTS);
LTE;
Telecommmunication management;
Self-Orgrganizina g Networks (SON)
Policy Nettwwoork Resource Model (NRM) )
Integratiotion Reference Point (IRP);
Requirements
(3GPP TS 28.6.627 version 13.2.0 Release 13 13)
---------------------- Page: 1 ----------------------
3GPP TS 28.627 version 13.2.0 Release 13 1 ETSI TS 128 627 V13.2.0 (2016-04)
Reference
RTS/TSGS-0528627vd20
Keywords
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
http://portal.etsi.org/tb/status/status.asp
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.
© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 28.627 version 13.2.0 Release 13 2 ETSI TS 128 627 V13.2.0 (2016-04)
Intellectual Property Rights
IPRs essential or potentially essential to the present document 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.
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 28.627 version 13.2.0 Release 13 3 ETSI TS 128 627 V13.2.0 (2016-04)
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.2 Self-Optimization Concept . 9
4.2.1 Logical Function Blocks . 9
4.2.1.1 Self-Optimization Input Monitoring Function (SO_MON_F) . 9
4.2.1.2 Triggering Optimization Function (TG_F) . 9
4.2.1.3 Optimization Fallback Function (O_FB_F) . 9
4.2.1.4 Self-Optimization Progress Update Function (SO_PGS_UF) . 9
4.2.1.5 NRM IRP Update Function (NRM_UF) . 9
4.2.1.6 Self-Optimization Monitoring and Management Function (SO_MMF) . 9
4.2.1.6.1 Self-Optimization Monitoring and Management Function (SO_MMF_NM) . 9
4.2.1.6.2 Self-Optimization Monitoring and Management Function (SO_MMF_EM) . 9
4.2.1.7 Load Balancing Function (LB_F) . 10
4.2.1.8 Interference Control Function (IC_F) . 10
4.2.1.9 Coverage and Capacity Function (CC_F) . 10
4.2.1.10 RACH Optimization Function (RACH_F) . 10
4.2.1.11 HandOver Optimization Function (HO_F) . 10
4.2.1.12 NM centralized Coverage and Capacity Function (CC_F_NM) . 10
4.3 SON Coordination Concepts . 10
5 Business level requirements . 10
5.1 Requirements . 11
5.1.1 Self-Optimization Monitoring and Management . 11
5.1.2 Load Balancing . 11
5.1.3 Handover (HO) Parameter optimization . 12
5.1.4 Interference control . 12
5.1.5 Coverage and Capacity optimization . 12
5.1.6 RACH optimization . 12
5.1.7 SON Coordination . 12
5.2 Actor roles . 13
5.3 Telecommunications Resources . 13
5.4 High-Level use case . 13
5.4.1 Load Balancing . 13
5.4.2 Interference control . 15
5.4.3 Coverage and capacity optimization . 16
5.4.4 NM centralized Coverage and Capacity Optimization . 18
5.4.4.0 General . 18
5.4.4.1 Use case 1: Cell coverage adapting to traffic demand. 18
5.4.4.2 Use case 2: Coverage and accessibility . 18
5.4.4.3 Use case 3: LTE coverage holes with underlaid UTRAN/GERAN . 18
5.4.4.4 Use case 4: LTE Connection failure . 19
5.4.4.5 Use case 5: Radio link quality . 21
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 28.627 version 13.2.0 Release 13 4 ETSI TS 128 627 V13.2.0 (2016-04)
6 Specification level requirements . 21
6.1 Requirements . 21
6.1.1 Self-Optimization Monitoring and Management . 21
6.1.1.1 Management Part . 21
6.1.2 Load Balancing . 22
6.1.3 Handover (HO) Parameter optimization . 22
6.1.3.1 HO failure categorization . 22
6.1.3.1.1 HO failures due to too late and too early HO triggering . 22
6.1.3.2 Reducing inefficient use of network resources due to unnecessary HOs . 23
6.1.3.3 Requirements . 24
6.1.4 Interference control . 24
6.1.5 Coverage and capacity optimization . 24
6.1.6 RACH optimization . 25
6.1.7 SON Coordination . 25
6.1.8 NM centralized coverage and capacity optimization . 25
6.2 Actor roles . 25
6.3 Telecommunications Resources . 25
6.4 Use case . 26
6.4.1 Use case Self-Optimization Monitoring and Management . 26
6.4.2 Use case Load Balancing Allowed/Prohibited Management . 26
6.4.3 Use case NM centralized Coverage and Capacity Optimization . 28
7 Functions and Architecture . 29
7.1 Self-Optimization Logical Architecture . 29
7.2 Self-Optimization Reference Model . 29
Annex A (informative): Steps for SON self-optimization Technical Specifications . 30
Annex B (informative): General descriptions related to NM centralized CCO high level use
cases . 31
B.1 General . 31
B.2 Monitoring of UE distribution . 32
Annex C (informative): Change history . 34
History . 35
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 28.627 version 13.2.0 Release 13 5 ETSI TS 128 627 V13.2.0 (2016-04)
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:
28.627: 'Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration
Reference Point (IRP): Requirements'
28.628: 'Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference
Point (IRP): Information Service (IS)'
28.629: 'Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference
Point (IRP): Solution Set (SS) definitions'
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 28.627 version 13.2.0 Release 13 6 ETSI TS 128 627 V13.2.0 (2016-04)
1 Scope
The present document describes concept and requirements of SON Policy management for Self-Optimization and SON
coordination.
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.150: "Telecommunication management; Integration Reference Point (IRP) Concept
and definitions".
[4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[5] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept
and high-level requirements".
[6] 3GPP TS 28.620: "Telecommunication management; Fixed Mobile Convergence (FMC)
Federated Network Information Model (FNIM) Umbrella Information Model (UIM)".
[7] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial
Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT);
Overall description; Stage 2".
[8] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management".
[9] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures".
[10] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access
Control (MAC) protocol specification".
[11] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer;
Measurements".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2],
3GPP TS 32.150 [3] and the following apply. A term defined in the present document takes precedence over the
definition of the same term, if any, in TS 32.101 [1], TS 32.102 [2], TS 32.150 [3] and TR 21.905 [4], in that order.
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 28.627 version 13.2.0 Release 13 7 ETSI TS 128 627 V13.2.0 (2016-04)
Target: Target provides a clear basis for assessing performance of self-optimization functions. Targets need to be
carefully specified in terms of a series of performance measurements and/or KPIs, which can be specific, and which can
be used also to identify problems. A target should be expressed in terms of a specific value or specific value range. The
present document does not specify the specific value or desired value range of each target since those should be set by
operators according to their policy and different network situation.
Trigger condition: The condition at which self-optimization should be triggered. Different self-optimization algorithms
may have different trigger conditions for achieving same objectives and targets.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CCO Coverage and Capacity Optimization
CQI Channel Quality Indicator
EM Element Manager
eNodeB evolved NodeB
EPC Evolved Packet Core
E-UTRA Evolved Universal Terrestrial Radio Access
E-UTRAN Evolved Universal Terrestrial Radio Access Network
HO Handover
ICIC Inter Cell Interference Coordination
LB Load Balancing
LTE Long Term Evolution
NE Network Element
NM Network Manager
NRM Network Resource Model
OAM Operation Administration Maintenance
PRB Physical Resource Block
RCEF RRC Connection Establishment Failure
RLF Radio Link Failure
RSRP Reference Signal Received Power
RSRQ Reference Signal Received Quality
SON Self Organizing Networks
UE User Equipment
4 Concepts and background
4.1 Overview
A self-optimization functionality will monitor input data such as performance measurements, fault alarms, notifications
etc. After analyzing the input data, optimization decisions will be made according to the optimization algorithms.
Finally, corrective actions on the affected network node(s) will be triggered automatically or manually when necessary.
IRPManager should be able to control the self-optimization procedures according to the operator"s objectives and
targets.
The following diagram is illustrated how the self-optimization functionality works:
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 28.627 version 13.2.0 Release 13 8 ETSI TS 128 627 V13.2.0 (2016-04)
Loop: Keep
Monitoring
Monitor input data
Analyse input data with Optimization
Algorithms
Yes
Meet the targets?
No
Execute corrective actions
No
Fallback may be needed to
reverse the system to the
Is system status better
previous status, which is
after the corrective
before the corrective actions
actions’ execution?
executed.
Yes
One time Self-optimization procedure
ends
Figure 4-1 Logical view of self-optimization procedure
The self-optimization functionality working procedure could be interpreted logically as following:
1. The self-optimization functionality keeps monitoring input data according to the operator"s objectives and targets.
2. Whenever the objectives and targets are not met, optimization algorithms will be triggered.
3. Corrective actions are provided and executed.
4. Then the self-optimization functionality evaluates the result of the executed corrective actions.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 28.627 version 13.2.0 Release 13 9 ETSI TS 128 627 V13.2.0 (2016-04)
a) If the system status is not satisfactory after the corrective actions" execution, fallback may be needed to
reverse the system configuration to the previous status, which is before the corrective actions executed.
b) If the system status is satisfactory after the corrective actions" execution, the one time self-optimization
procedure ends.
5. Self-optimization functionality returns to monitoring the input data.
4.2 Self-Optimization Concept
4.2.1 Logical Function Blocks
4.2.1.1 Self-Optimization Input Monitoring Function (SO_MON_F)
This functional bloc supports the following functions: [SO1].
4.2.1.2 Triggering Optimization Function (TG_F)
This functional bloc supports the following functions: [SO2], [SO3].
4.2.1.3 Optimization Fallback Function (O_FB_F)
This functional bloc supports the following functions: [SO7], [SO9], [SO10].
4.2.1.4 Self-Optimization Progress Update Function (SO_PGS_UF)
This function updates the self-optimization progress and important events to the operator: [SO11]
4.2.1.5 NRM IRP Update Function (NRM_UF)
This function updates the E-UTRAN and EPC NRM IRP with the optimization modification if needed.
4.2.1.6 Self-Optimization Monitoring and Management Function (SO_MMF)
This function monitors the self-optimization process and provides the operator with this information. This function must
be able to get information about all other functional blocs. In addition to this it allows the operator to control the
execution of the self-optimization process.
This function also resolves conflicts of different SON functions trying to change or actually changing parameter values
in different directions or reports such conflicts, if they cannot be solved.
4.2.1.6.1 Self-Optimization Monitoring and Management Function (SO_MMF_NM)
SO_MMF_NM (IRP Manager): representing the NM portion of SO_MMF (necessary monitoring and limited
interaction capabilities to support an automated optimization), as well as related IRPManager functionality
In a centralized conflict resolution approach SO_MMF_NM identifies and resolves conflicts.
In distributed and hybrid conflict resolution approach SO_MMF_NM sends policy directions towards the
SO_MMF_EM.
4.2.1.6.2 Self-Optimization Monitoring and Management Function (SO_MMF_EM)
SO_MMF_EM (IRP Agent): representing the portion of SO_MMF operating below Itf-N, as well as related IRPAgent
functionality
In distributed and hybrid conflict resolution approach SO_MMF_EM identifies, resolves and/or reports conflicts,
according to the policy directions received by SO_MMF_NM.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 28.627 version 13.2.0 Release 13 10 ETSI TS 128 627 V13.2.0 (2016-04)
In case SO_MMF_EM is not able to solve a conflict, it will request the SO_MMF_NM to resolve the conflict.
4.2.1.7 Load Balancing Function (LB_F)
This function handles the load balancing optimization.
4.2.1.8 Interference Control Function (IC_F)
This function handles the interference control optimization.
4.2.1.9 Coverage and Capacity Function (CC_F)
This function handles the Coverage and Capacity Optimization.
4.2.1.10 RACH Optimization Function (RACH_F)
This function handles the RACH optimization.
4.2.1.11 HandOver Optimization Function (HO_F)
This function handles the handover optimization.
4.2.1.12 NM centralized Coverage and Capacity Function (CC_F_NM)
This function represents the NM centralized Coverage and Capacity Optimization (operating above Itf-N) as well as the
related IRP Manager functionality.
CC_F_NM analyses monitoring data, determines improvement actions, sends configuration data, and if necessary raises
an operator action notification.
4.3 SON Coordination Concepts
When multiple SON functions attempt to change some (same or associated) network configuration parameters of some
(same or associated) nodes, one or more of these SON functions may not be able to achieve the operator"s specified
SON target(s) (for individual SON function) since they may have conflicting demands on network resources. This
situation is considered as 'SON functions in conflict' and requires conflict prevention or resolution. Detection of 'SON
functions in conflict' can be Use Case specific (for example, two SON functions make change at the same time or
during the impact time interval).
The associated network configuration parameters include parameters within the same network element or parameters of
different network elements with impact between each other. For example, the associated parameters of one cell are the
parameters of its neighbour cells. Another typical association example is the TX power, antenna azimuth and tilt of one
cell are associated with each other.
Different SON functions may have dependencies with each other. The behaviour of one SON function may have
influence on other SON functions. For example, CCO function may adjust the Neighbour Relation due to coverage
optimization, and then the changed NR will have an influence on Handover Parameter Optimization function.
SON coordination is to detect, prevent or resolve conflicts or negative influences between SON fun
...