Tech-invite3GPP-SpecsFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 32.500SA5
Self-Organizing Networks (SON) –
Concepts and Requirements

use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V15.0.0 (PDF)  2018/06  15 p.
V14.0.0  2017/03  15 p.
V13.0.0  2016/01  15 p.
V12.1.0  2014/12  15 p.
V11.1.0  2011/12  15 p.
V10.1.0  2010/10  16 p.
V9.0.0  2009/12  15 p.
V8.0.0  2008/12  15 p.

Rapporteur:  Ing. Schnell, Christof

In order to reduce the operating expenditure (OPEX) associated with the management of this larger number of nodes from more than one vendor the concept of the Self-Organizing Network (SON) is introduced. Automation of some network planning, configuration and optimisation processes via the use of SON functions can help the network operator to reduce OPEX by reducing manual involvement in such tasks.
The present document describes the requirements and architecture for the Self Organizing Network (SON) functions within the OAM system.
There are four different architectures that are possible for implementing various SON use cases:
  • Centralised SON: SON solution where SON algorithms are executed in the OAM system. Centralised SON has two variants:
    • NM-Centralised SON: SON solution where SON algorithms are executed at the Network Management level.
    • EM-Centralised SON: SON solution where SON algorithms are executed at the Element Management level.
  • Distributed SON: SON solution where SON algorithms are executed at the Network Element level.
  • Hybrid SON: SON solution where SON algorithms are executed at two or more of the following levels: NE or EM or NM.
The architecture is selected depending on the needs of the SON use cases.

full Table of Contents for  TS 32.500  Word version:   15.0.0

Here   Top