Atomicity - Consistency - Isolation - Durability

Description

ACID is a foundational concept in database transaction management, adopted within 3GPP specifications to ensure data integrity and reliability for network functions, particularly in service-based architectures (SBA) like the 5G Core (5GC). It defines four critical properties that a transaction—a logical unit of work—must satisfy to be considered reliable, especially in distributed systems where data may be replicated or accessed concurrently.

Atomicity ensures that a transaction is treated as a single, indivisible unit of work. It follows an 'all-or-nothing' principle: either all operations within the transaction are completed successfully and committed to the database, or if any part fails, the entire transaction is rolled back, leaving the system state unchanged. This prevents partial updates that could lead to data corruption. In a 3GPP network, this is crucial during procedures like registration or session establishment where multiple network functions (NFs) must update their states coherently.

Consistency guarantees that a transaction brings the database from one valid state to another, preserving all defined rules, constraints, and relationships. It ensures that only data adhering to predefined integrity constraints (e.g., foreign keys, uniqueness) is written. For example, in a 3GPP Unified Data Repository (UDR), consistency ensures subscriber profile updates comply with schema rules, preventing invalid configurations from being stored.

Isolation ensures that concurrent execution of transactions leaves the database in the same state as if they were executed sequentially. It manages how and when changes made by one transaction become visible to others, preventing phenomena like dirty reads, non-repeatable reads, and phantom reads. In a 3GPP network, isolation is vital when multiple network exposure functions (NEFs) or applications concurrently access or modify shared data like policy rules or charging records.

Durability guarantees that once a transaction is committed, its changes persist permanently in the database, even in the event of a system failure, power loss, or crash. This is typically achieved through write-ahead logging (WAL) and data replication to non-volatile storage. For 3GPP systems, durability ensures critical data—such as subscriber authentication vectors, session contexts, or charging data records (CDRs)—is not lost, supporting billing accuracy and service continuity.

In 3GPP's service-based architecture, ACID principles are implicitly or explicitly applied in the design of data storage solutions like UDR, Unified Data Management (UDM), and Network Repository Function (NRF). They underpin the reliability of interactions between network functions via HTTP-based services, ensuring that complex, multi-step procedures across distributed NFs maintain data integrity and system stability.

Purpose & Motivation

The ACID properties exist to solve fundamental problems of data reliability and integrity in database systems, which are critical for any complex software infrastructure, including telecommunications networks. Prior to the formalization of ACID, early database systems were prone to data corruption, inconsistencies, and loss during system failures or concurrent access, leading to incorrect system states, financial discrepancies (e.g., in billing), and service disruptions. The concept provides a rigorous model to ensure that transactions—business logic operations like debiting an account or updating a subscriber profile—are processed reliably.

In the context of 3GPP standards, the adoption of ACID principles became increasingly important with the evolution towards cloud-native, service-based architectures in 4G EPC and especially 5G Core. These architectures decompose monolithic network elements into distributed, microservices-based network functions that interact asynchronously and maintain their own or shared data stores. This distribution introduces challenges of data consistency across functions during procedures like handovers or policy updates. ACID provides the theoretical foundation for designing data layers (e.g., in UDM/UDR) that can handle these complex, stateful interactions without corruption.

Specifically, 3GPP specifications reference ACID in the context of service exposure, data management, and charging (as seen in specs like 23.558, 29.558). They address the need for network APIs exposed to third-party applications (via NEF) to guarantee that data modifications are atomic and durable, preventing scenarios where an application's request partially updates network data, leading to service errors. ACID principles ensure that the network can provide predictable, trustworthy data services to both internal NFs and external consumers.

Key Features

• Guarantees all operations in a transaction succeed or fail as a unit (Atomicity)
• Ensures database transitions adhere to all defined integrity constraints (Consistency)
• Manages concurrent transaction visibility to prevent data anomalies (Isolation)
• Persists committed transaction changes permanently despite system failures (Durability)
• Provides a model for reliable state management in distributed network functions
• Underpins data integrity in 3GPP service-based architecture and exposure frameworks

Evolution Across Releases

Defining Specifications