Non-Automated Software Management

Description

Non-Automated Software Management (NASWM) is a framework specified within the 3GPP Management standards (TS 32.531) that governs the manual processes for software management in network elements. It operates within the broader Operations, Administration, and Maintenance (OAM) system, providing a structured, standardized approach for operators to perform software-related activities without relying on full automation. The architecture involves the Network Manager (NM) or Element Manager (EM) as the controlling entity, which issues software management commands to the Managed Element (ME), such as a base station or core network node. The ME then executes these commands and reports back status, but the initiation, sequencing, and decision-making are performed by human operators via management interfaces.

NASWM defines a set of stateful procedures covering the complete software lifecycle, including software download, installation, activation, and deactivation. Key components include the Software Management State Machine within the managed element, which tracks the current operational state (e.g., idle, downloading, installed, active), and the associated Management Information Base (MIB) objects that represent software inventory and status. The NM/EM interacts with these MIB objects using standardized protocols like SNMP or CORBA-based interfaces (as per the Itf-N), issuing commands that transition the ME through predefined states. This ensures that even manual operations follow a consistent, predictable pattern, reducing the risk of errors and network instability.

Its role in the network is to provide a fallback or alternative to Automated Software Management (ASWM), accommodating scenarios where regulatory, policy, or technical constraints prevent fully automated updates. For instance, in safety-critical networks or during major version upgrades, operators may require manual verification at each step. NASWM ensures these manual processes are still integrated into the formal OAM framework, allowing for audit trails, compliance reporting, and alignment with the overall Fault, Configuration, Accounting, Performance, and Security (FCAPS) model. It is particularly relevant for managing the software of Radio Access Network (RAN) equipment and core network functions where downtime must be meticulously planned and controlled.

Purpose & Motivation

NASWM was created to address the need for a standardized, operator-controlled software management process within 3GPP networks. Prior to its specification, software updates were often vendor-proprietary, ad-hoc procedures that lacked interoperability and consistent reporting. This made multi-vendor network management complex and increased the risk of human error during critical updates. NASWM provides a common, protocol-agnostic framework that ensures all 3GPP-compliant network elements support a baseline set of manual management operations, enabling operators to maintain software across diverse equipment from different suppliers using a unified operational model.

The technology exists to solve the problem of controlled, auditable software changes in environments where full automation is either not trusted or not technically possible. Some network deployments, especially in earlier 3GPP releases or in regulated industries, mandate manual oversight for any software modification. NASWM formalizes this oversight, defining the exact states, commands, and notifications required. It also complements ASWM by providing a fallback mechanism; if an automated procedure fails, operators can revert to the manual processes defined by NASWM to recover the system. Its creation was motivated by the increasing software complexity of network elements and the operational need to manage this complexity without sacrificing stability or control.