Network Re-configuration

Description

Re-configuration in 3GPP management terminology refers to the process of rearranging the parts, hardware, and/or software that constitute a Public Land Mobile Network (PLMN). The scope ranges from modifying parameters or software components within a single Network Element (NE) to reorganizing the set of NEs that form the network. This broad definition intentionally covers both element-level changes, such as updating a base station's configuration parameters, and network-level changes, such as adding, removing, or re-parenting NEs in a management hierarchy.

The concept is central to the management architecture defined in TS 32.600 and the configuration management (CM) procedures in TS 32.611. In this architecture, a managing system (for example, an Element Manager or Network Manager) interacts with managed NEs through standardized interfaces. Re-configuration is realized through CM operations such as create, delete, set, and get on Managed Objects (MOs) in the Information Model. Each MO represents a manageable resource with attributes, and a re-configuration typically involves modifying one or more attributes or restructuring the containment hierarchy of MOs.

Re-configurations can be triggered by a human operator, for example during network rollout, capacity upgrades, or parameter tuning, or by the system itself through self-organizing network (SON) functions. SON use cases such as self-configuration, self-optimization, and self-healing rely on automated re-configuration to adjust coverage, capacity, and mobility parameters without manual intervention. This automation is essential in dense and heterogeneous networks where manual tuning is impractical.

A re-configuration may be atomic or incremental. In many cases, changes are applied to a subset of parameters while the NE continues to serve traffic, minimizing service disruption. For more disruptive changes, such as software upgrades or major topology changes, the NE may need to be taken out of service or placed in a maintenance state. Management systems coordinate these operations to avoid conflicts and to maintain consistency across the network.

The definition has evolved in scope over releases. In early releases (Rel-8 and Rel-9), the definition referred to the 3G network, reflecting the technology focus at the time. From Rel-10 onward, the wording was generalized to the PLMN network, acknowledging the coexistence of multiple radio access technologies and the move toward a unified, multi-RAT management framework. This change mirrors the broader 3GPP trend of abstracting management concepts from specific access technologies.

Re-configuration is closely related to other management functions such as fault management, performance management, and software management. It provides the mechanism by which the network adapts to changing demands, integrates new equipment, and recovers from failures. In modern 5G networks, re-configuration is increasingly policy-driven and closed-loop, with analytics and intent-based management feeding automated configuration changes.

Purpose & Motivation

Re-configuration exists to give network operators and management systems a standardized way to change the structure and behavior of a PLMN, whether by adjusting a single network element or by reorganizing the network elements themselves. Without a well-defined concept and associated management procedures, changes would be vendor-specific and error-prone, making multi-vendor networks difficult to operate and evolve.

The concept addresses the need for both manual and automated network adaptation. Operators must be able to roll out new sites, upgrade software, tune parameters, and respond to failures. At the same time, self-organizing network functions require a formal notion of configuration change so that automated decisions can be executed reliably and consistently. By defining re-configuration in management specifications, 3GPP ensures that these operations can be performed over standardized interfaces with predictable semantics.

Historically, early definitions were tied to the 3G network, reflecting the single-technology focus of the time. As networks became multi-RAT and more complex, the definition was broadened to the PLMN, enabling a technology-agnostic approach. This evolution supports the long-term goal of autonomous, self-managing networks where re-configuration is a routine, closed-loop activity rather than a manual, disruptive event.