tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top        in Index        Prev        Next

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

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    15 p.
(P) V13.0.0    2016/01    15 p.
(P) V12.1.0    2014/12    15 p.
(P) V11.1.0    2011/12    15 p.
(P) V10.1.0    2010/10    16 p.
(P) V9.0.0    2009/12    15 p.
(P) V8.0.0    2008/12    15 p.


Rapporteur:  Ing. Schnell, Christof
See also:  –


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. 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.


 

Here        Top