Overload point

Description

The Overload point (OVL) is a critical threshold parameter defined within the Base Station System Management (BSSMAP) and Radio Access Network Application Part (RANAP) protocols in GSM and UMTS networks. It resides in the Base Station Controller (BSC) for GSM or the Radio Network Controller (RNC) for UMTS. The OVL represents a specific level of resource utilization (e.g., processor load, memory usage, or traffic volume) beyond which the node is considered to be entering an overloaded state. When this threshold is crossed, the BSC or RNC activates internal overload control procedures. These procedures are designed to protect the node from complete failure by selectively rejecting or throttling new service requests, such as call setup attempts or location updates, while attempting to preserve existing connections. The OVL is a proactive management tool; by defining the point at which overload control begins, network operators can balance traffic load and prevent a cascading failure scenario where the node becomes unresponsive. The specific algorithms and resources monitored are implementation-dependent, but the OVL concept provides a standardized framework for congestion management.

Purpose & Motivation

The Overload point was created to address the critical issue of network node congestion and instability in high-traffic scenarios. In early mobile networks, a sudden surge in demand (e.g., during a mass event or network fault) could overwhelm a BSC or RNC, leading to a complete crash and loss of service for all connected users. The OVL mechanism provides a controlled, graceful degradation of service. It solves the problem of an all-or-nothing failure mode by allowing the network element to shed load in a managed way. The historical context is rooted in traffic engineering and fault management principles, translating them into a concrete parameter for real-time control. It addresses the limitation of having no standardized trigger for congestion control, enabling interoperable and predictable network behavior under stress across equipment from different vendors.

Key Features

• Defines a threshold for triggering overload control in BSC/RNC
• Part of the BSSMAP (GSM) and RANAP (UMTS) management protocols
• Enables proactive network congestion management
• Aims to prevent node failure by selective service rejection
• Allows for graceful service degradation under high load
• Implementation-specific regarding the exact resource measured (CPU, memory, queue depth)

Evolution Across Releases

Defining Specifications