Calling Name Database

Description

The Calling Name Database (CNDB) is a specialized network database defined in 3GPP specifications that stores subscriber name information associated with telephone numbers (MSISDNs). It operates as a query-response system where network elements, typically the Home Location Register (HLR) or Mobile Switching Center (MSC), can request calling name information for presentation services. When a call is initiated, the serving network element queries the CNDB with the caller's MSISDN, and the database returns the corresponding subscriber name if available and authorized for presentation.

The CNDB architecture follows a centralized or distributed database model depending on operator implementation. It interfaces with core network elements through standardized protocols, primarily using MAP (Mobile Application Part) operations over SS7 (Signaling System No. 7) networks. The database maintains subscriber records containing MSISDN-name mappings along with service flags indicating presentation permissions, privacy settings, and subscription status. These records are provisioned through operator administration systems and may be updated dynamically based on subscriber requests or network changes.

In operation, the CNDB performs several key functions: it validates querying network elements for authorization, checks subscriber privacy preferences, retrieves name information from its database, formats the response according to presentation requirements, and logs transactions for billing and auditing purposes. The database supports both intra-network and inter-network queries, enabling calling name presentation across different operator networks when roaming agreements exist. Performance requirements include low-latency responses (typically under 500ms) to avoid call setup delays and high availability (99.999% uptime) to ensure service reliability.

The CNDB's role extends beyond simple name retrieval to include service logic execution. It applies business rules such as name formatting preferences (e.g., first name only, full name), handles special cases like corporate subscribers with department names, and manages override scenarios where subscribers can block name presentation. The database also supports supplementary services integration, allowing calling name to be combined with services like Caller ID, Call Waiting, and Conference Calling. Security features include authentication of querying entities, encryption of sensitive data, and access control mechanisms to prevent unauthorized name retrieval.

Purpose & Motivation

The CNDB was created to address the growing demand for enhanced calling services beyond basic number identification. Before its introduction, mobile networks primarily displayed only the caller's telephone number (MSISDN), which provided limited identification and poor user experience. Subscribers struggled to recognize callers from numbers alone, especially for contacts not saved in their phonebooks. This limitation became more pronounced as mobile phone adoption increased and users received calls from various business contacts, service providers, and occasional callers.

The technology solves the problem of caller identification by providing human-readable names alongside telephone numbers. This enhances user experience by allowing recipients to make informed decisions about answering calls, improves accessibility for visually impaired users through text-to-speech conversion, and enables professional communication scenarios where organizational names need presentation. The CNDB also addresses privacy concerns through configurable presentation settings, giving subscribers control over when their names are displayed.

Historically, calling name services existed in fixed-line networks but were not standardized for mobile networks. 3GPP introduced CNDB in Release 4 to create a uniform approach across GSM/UMTS networks, enabling interoperability between different vendors' equipment and consistent service delivery across operator boundaries. The standardized database approach replaced proprietary implementations that hindered roaming and inter-operator services, creating a foundation for value-added services that operators could monetize while improving customer satisfaction.

Key Features

• MSISDN-to-name mapping storage and retrieval
• MAP protocol interface for network element queries
• Subscriber privacy and presentation control mechanisms
• Inter-operator query support for roaming scenarios
• High availability and low-latency response architecture
• Integration with HLR/MSC for call setup signaling

Evolution Across Releases

Defining Specifications