Centralized SON (C-SON) is a network automation architecture where all self-optimization and self-healing algorithms execute on a central server, usually within the Network Management System (NMS) or Operations Support System (OSS). Unlike distributed approaches, C-SON aggregates network telemetry and Key Performance Indicators (KPIs) from across the entire RAN to make globally optimal decisions. This macro-level visibility allows it to coordinate complex, multi-cell functions like Mobility Load Balancing (MLB) and Coverage and Capacity Optimization (CCO) without creating local optimization conflicts.
Glossary
Centralized SON (C-SON)

What is Centralized SON (C-SON)?
Centralized SON (C-SON) is a Self-Organizing Network architecture where optimization algorithms and decision-making logic reside in a centralized management system, typically at the Network Management System (NMS) level, providing a global, multi-cell view of the network.
The primary trade-off of C-SON is its reliance on the northbound Itf-N interface for data collection and configuration pushes, making it suitable for slow-loop control with optimization intervals of minutes or hours rather than milliseconds. It excels at non-real-time use cases such as Automated Cell Planning, PCI collision detection, and Energy Saving Management across large clusters. In modern O-RAN architectures, C-SON functions are often implemented as rApps on the Non-Real-Time RIC, leveraging the A1 interface for policy-based guidance to near-real-time xApps.
Key Features of C-SON
Centralized SON provides a macro-level view of the radio access network, enabling coordinated optimization that avoids the local minima and conflicts inherent in distributed architectures.
Global Network View
Unlike Distributed SON (D-SON) , which operates on a per-cell basis, C-SON aggregates Performance Management (PM) and Configuration Management (CM) data from thousands of cells simultaneously. This holistic perspective allows the algorithm to understand the ripple effects of a local change across the entire network topology.
- Aggregates multi-vendor telemetry via the Itf-N interface
- Maintains a centralized Network Digital Twin for what-if analysis
- Prevents the 'ping-pong' effect common in uncoordinated local optimizers
Conflict Resolution & Coordination
A critical function of C-SON is acting as an arbiter. When multiple SON use cases (e.g., Mobility Load Balancing and Coverage and Capacity Optimization) request conflicting parameter changes, the central coordinator applies policy-based arbitration to ensure network stability.
- Detects overlapping parameter targets before activation
- Applies weighted priority to life-critical functions like Cell Outage Compensation
- Logs all rejected actions for SON Conflict Resolution auditing
Multi-Vendor Abstraction
C-SON platforms abstract vendor-specific proprietary management interfaces into a unified object model. This allows operators to apply consistent optimization policies across Ericsson, Nokia, and Samsung radios simultaneously, a critical requirement for Open RAN environments.
- Normalizes Performance Counter semantics across vendors
- Translates vendor-agnostic intents to device-specific CLI/API calls
- Enables true best-of-breed RAN procurement strategies
Non-Real-Time Optimization Loops
C-SON typically operates on a slow control loop (seconds to minutes), making it ideal for Non-Real-Time RIC (Non-RT RIC) implementations in O-RAN architectures. It processes historical data to train Machine Learning (ML) models that predict optimal configurations.
- Executes policy changes via the A1 interface in O-RAN
- Ideal for Energy Saving Management and long-term Automated Cell Planning
- Complements the fast loop of D-SON in a Hybrid SON architecture
Policy-Based Intent Fulfillment
Modern C-SON systems implement Intent-Based Networking principles. Operators define high-level business goals (e.g., 'Maximize throughput for premium users while keeping dropped calls below 0.1%'), and the C-SON engine translates these into specific Physical Cell Identity (PCI) or Remote Electrical Tilt (RET) adjustments.
- Continuous closed-loop assurance against Service Level Agreements (SLAs)
- Automatic rollback if Key Performance Indicators degrade
- Reduces manual scripting errors in Network Operations Centers (NOCs)
Geo-Located Subscriber Analytics
By centralizing Minimization of Drive Tests (MDT) traces and call traces, C-SON builds a high-resolution heatmap of user experience. This enables geo-located optimization, where the system identifies a specific intersection suffering from poor Reference Signal Received Power (RSRP) and adjusts only the surrounding antennas.
- Correlates User Equipment (UE) measurements with GPS coordinates
- Identifies 'not-spots' invisible to cell-level statistics
- Drives precise Coverage and Capacity Optimization (CCO) actions
C-SON vs. D-SON vs. Hybrid SON
A comparison of the three primary Self-Organizing Network architectures based on control locus, optimization scope, and operational characteristics.
| Feature | Centralized SON (C-SON) | Distributed SON (D-SON) | Hybrid SON (H-SON) |
|---|---|---|---|
Control Locus | Network Management System (NMS) or Non-RT RIC | Individual network elements (eNB/gNB) | Split: NMS for global, eNB/gNB for local |
Optimization Scope | Multi-cell, global network view | Single-cell, local environment | Layered: global coordination with local execution |
Reaction Speed | Slow (seconds to minutes) | Fast (milliseconds to seconds) | Variable: fast locally, slower globally |
Algorithm Complexity | High; can run computationally intensive ML models | Low; lightweight heuristics and rule-based logic | Moderate; complex models centralized, simple rules distributed |
Conflict Resolution | Inherent; single decision point prevents conflicts | Requires external coordination; prone to oscillations | Built-in; central coordinator resolves local conflicts |
Standardization | 3GPP TS 32.500 series, O-RAN A1/O1 interfaces | 3GPP TS 36.902, X2/Xn interface procedures | 3GPP TS 32.522, O-RAN E2/A1 hybrid models |
Vendor Interoperability | High via open NMS APIs and O-RAN rApps | Low; proprietary algorithms per vendor | Medium; requires standardized NMS-SON and X2/Xn interfaces |
Scalability | Challenged by large network size; NMS bottleneck risk | Excellent; scales horizontally with node count | Good; central bottleneck mitigated by local offload |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clarifying the core concepts, operational mechanisms, and strategic advantages of Centralized Self-Organizing Networks for multi-vendor radio access environments.
Centralized SON (C-SON) is a Self-Organizing Network architecture where the optimization algorithms and decision-making logic reside in a centralized management system, typically at the Network Management System (NMS) or Operations Support System (OSS) level. This provides a macro-level, global view of the network. Unlike Distributed SON (D-SON), where automation functions are embedded directly within individual network elements (eNBs/gNBs) for rapid, localized reaction, C-SON collects telemetry from thousands of cells to make coordinated decisions. The fundamental trade-off is speed versus scope: D-SON executes changes in milliseconds to handle fast fading, while C-SON operates on a slower control loop (seconds to minutes) to optimize global objectives like network-wide load balancing, interference matrix management, and multi-vendor coordination. In modern Hybrid SON deployments, C-SON acts as the strategic brain, setting policy boundaries and resolving conflicts for the tactical, real-time D-SON functions running at the edge.
Related Terms
Centralized SON is a specific architectural choice within the broader Self-Organizing Network ecosystem. The following concepts define its operational scope, its alternatives, and the key functions it orchestrates.
Distributed SON (D-SON)
The architectural counterpoint to C-SON, where automation logic resides directly on the base station (eNB/gNB). D-SON excels at microsecond-level reactions to local radio changes, such as sudden interference bursts. However, it lacks a global view, making it prone to network-wide optimization conflicts without a central coordinator.
Hybrid SON (H-SON)
The practical deployment model combining C-SON and D-SON to balance global intelligence with local speed. In this architecture:
- D-SON handles time-critical, localized functions like fast fading compensation.
- C-SON provides a global view for non-real-time optimization and conflict resolution. This prevents the 'ping-pong' effect where local optimizations degrade overall network performance.
Mobility Load Balancing (MLB)
A primary C-SON use case that prevents localized congestion. The central controller analyzes cell load KPIs across a wide area and intelligently shifts traffic by adjusting handover thresholds. Unlike reactive D-SON, C-SON-based MLB can preemptively redistribute users based on predicted traffic patterns, ensuring a smooth user experience during peak hours.
Coverage and Capacity Optimization (CCO)
A complex optimization function ideally suited for C-SON due to its need for a macro-level view. The central system dynamically adjusts antenna parameters, such as Remote Electrical Tilt (RET) and transmission power, across multiple cells simultaneously to heal coverage holes without creating interference hotspots in adjacent sectors.
SON Conflict Resolution
A critical C-SON function that acts as an arbiter when multiple SON algorithms request conflicting parameter changes. For example, an energy-saving function may try to shut down a cell while a load-balancing function attempts to offload traffic to it. The central coordinator applies policy-based priority rules to ensure network stability and prevent parameter oscillation.
RAN Intelligent Controller (RIC)
In Open RAN architectures, the C-SON function is often implemented as an rApp on the Non-Real-Time RIC. This platform provides standardized interfaces (A1, O1) for the central logic to collect telemetry and enforce policies across multi-vendor equipment, moving C-SON from a monolithic, vendor-locked system to a modular, open application.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us