Description
Barred Dialling Number (BDN) is a standardized service feature within the 3GPP framework, specifically defined as part of the USIM (Universal Subscriber Identity Module) application toolkit. Its primary function is to allow the barring (blocking) of outgoing voice calls, and potentially other communication attempts like SMS or data sessions, to a predefined list of telephone numbers or number ranges. The BDN list is stored as a dedicated file (EF_BDN) on the USIM card, which is a secure, tamper-resistant element. This file contains entries specifying the barred numbers, which can be full international numbers (e.g., +441234567890) or partial numbers using wildcard characters to block number ranges (e.g., blocking all premium rate numbers starting with a specific prefix). The enforcement of the barring is performed locally by the Mobile Equipment (ME), i.e., the handset or device, not by the network core. When a user initiates a call, the device's protocol stack consults the BDN list stored on the USIM before proceeding with the call setup signaling. If the dialed number matches an entry in the BDN list, the device aborts the call attempt locally and typically informs the user that the call is barred. This local enforcement is a key architectural aspect, as it does not consume network resources for a call that will ultimately be blocked, and it provides immediate feedback to the user.
The management of the BDN list can occur through several mechanisms. It can be pre-provisioned by the network operator onto the USIM, often for business or security reasons (e.g., barring international dialing on a corporate phone). Alternatively, it can be configured by the subscriber via the handset's user interface if the operator permits such user control. The USIM Application Toolkit (USAT) provides the standardized commands for secure interaction between the device and the USIM to read, update, or verify the BDN list. The feature's operation is integrated with other USIM-based services and the device's call control logic. It acts as a first-line check before any radio resource connection is established for a mobile-originated call.
From a network perspective, BDN is a subscriber-centric service management tool. While the core network (MSC/VLR in circuit-switched domains) is unaware of the BDN check happening on the device, the feature directly impacts the service experience and billing. It helps prevent unintended usage, such as calls to expensive premium-rate numbers or international numbers, which can lead to bill shock. For enterprises, it is a tool for enforcing telecom policies on company-provided devices. The specification of BDN across documents like 3GPP TS 31.102 (USIM characteristics) and TS 31.121 (UICC-terminal interface) ensures interoperability between USIMs from different vendors and mobile devices, making it a universally supported feature in 3GPP networks from 3G onwards. Its role is complementary to network-based barring services like Barring of All Outgoing Calls (BAOC) or Barring of Outgoing International Calls (BOIC), offering a more granular, number-specific control mechanism.
Purpose & Motivation
The Barred Dialling Number feature was introduced to address the need for granular, subscriber-specific control over outgoing calls in mobile networks. Prior to its standardization, call barring was primarily a network-centric feature (like BAOC) controlled by the operator via the HLR or served MSC. These network-based barring services were broad-brush, applying to entire categories of calls (e.g., all international calls) and were not easily modifiable by the subscriber. There was a growing demand, especially from corporate customers and cost-conscious consumers, for the ability to block calls to specific, known expensive numbers (e.g., certain premium-rate services) or unauthorized numbers, without restricting all calls of a certain type.
BDN solves this by moving the control point to the USIM and the handset. This decentralization allows for a personalized list of barred numbers that travels with the subscriber's SIM card. The purpose is twofold: first, to empower users or their administrators (e.g., corporate IT) with direct control over call permissions, enhancing security and cost management; second, to reduce customer service issues and disputes related to unauthorized calls, as the barring is proactively enforced by the device itself. Historically, the rise of premium SMS and voice services in the early 2000s, which sometimes led to 'subscription traps' or fraudulent charges, motivated the need for such user-accessible barring tools.
The creation of BDN was motivated by the increasing programmability and intelligence of the SIM card, evolving into the USIM. The USIM application platform provided a secure and standardized environment to host such a feature. By storing the barred list on the USIM, it becomes independent of the handset; if a user changes phones, their barring list remains intact. This solves the limitation of handset-only barring features, which were not portable. Furthermore, it provides a standardized interface that all compliant handsets can use, ensuring a consistent user experience across different device manufacturers and network operators, which was a key goal of 3GPP interoperability efforts.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (30 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-6, normative work from Rel-15.
In Release 15, updates to USIM management procedures for 5GS were introduced, alongside enhancements for configuring Mission Critical Services data and Access Identity 2 via the USIM. The update also included an enhancement to USIM OPL configuration to support 3-byte Tracking Area Codes when connected to an NG-RAN. Furthermore, clarifications were provided regarding the presence of specific configuration data files within the ISIM and USIM applications.
- USIM Service Table update for PDU session call control support TS 31.102CR0786
- Allow configuration of MCS (Access Identity 2) via USIM. TS 31.102CR0794
- Mission Critical Services configuration data update to USIM TS 31.102CR0808
- Enhance USIM OPL configuration to support 3 bytes TAC when in NG-RAN. TS 31.102CR0818
- Updates to USIM management procedures for 5GS TS 31.102CR0806
- Clarification about presence of EFIMSConfigData in ISIM and USIM TS 31.102CR0833
In Release 16, the BDN function was enhanced by introducing a new configuration for a PS Data Off list in the USIM, applicable for both home and roaming scenarios. This allowed the network operator to provision a list of numbers for which packet-switched data sessions are barred directly onto the subscriber's smart card. Additionally, the release included clarifications to the procedure for reading the UAC Access Identities Configuration EF in the USIM.
- Add new general abbreviations MCC Note: CR cover sheet wrongly shows CR number as "1118". TS 21.905CR0118
- Support for USIM configuration of RLOS PLMN list TS 31.102CR0847
- URSP storage in USIM TS 31.102CR0861
- Specify storage for a potentially separate KSEAF for non-3gpp access on the USIM TS 31.102CR0864
- USIM configuration of RLOS allowed MCC list TS 31.102CR0881
- Support for Trusted non-3GPP access networks list by USIM TS 31.102CR0891
+ 5 more changes
In Release 17, the BDN function was enhanced by introducing a dedicated USIM file for the configuration of warning messages reception in SNPNs (Standalone Non-Public Networks). This new file allows the network operator to store and manage the settings for receiving public warning system messages specifically within SNPN environments directly on the USIM. This addition provides a standardized and secure method for configuring this capability on the UICC.
- Introduce a USIM file to store pre-configured CAG information list TS 31.102CR0904
- SOR-CMCI storage in USIM TS 31.102CR0917
- Addition of USIM files for the indication of whether disaster roaming is enabled in the UE, disaster roaming wait range, disaster return wait range and applicability indicator for disaster roaming PLMNs list provided by VPLMN. TS 31.102CR0938
- Adding eDRX parameters in the USIM for NG-RAN TS 31.102CR0943
- 5G NSWO (Non-Seamless WLAN Offload) configuration support in the USIM compromised proposal. TS 31.102CR0946
- Support of 'No E-UTRA Disabling In 5GS' in USIM TS 31.102CR0947
+ 3 more changes
In Release 18, the BDN function was enhanced by adding an EF (Elementary File) for Access Control to GBA_U_APIs on the USIM. This new EF provides a structured record on the UICC to store barred dialling number data, integrating it with the USIM's file system for improved management. The update leverages the existing USIM architecture to extend barring capabilities within the 3GPP system.
In Release 19, the BDN (Barred Dialling Number) function was enhanced to include backward compatibility handling for USIMs that lack extended security parameter storage in the EF_5GAuthKeys file. This ensures that the BDN service operates correctly even when the USIM's implementation capability for storing certain security parameters is limited. The update addresses scenarios where the USIM's personalization or storage constraints might otherwise prevent the proper application of barred number restrictions.
- Backward compatibility handling of USIM without extended security parameter storage in EF_5GAuthKeys - Rel19 TS 31.102CR1074
Explore further
Broader topics and technologies where BDN plays a role.
Defining Specifications
3GPP specifications that define or reference BDN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 31.102 vj40 | USIM Application Specification | Rel-19 |
| TS 31.121 vi50 | UICC-terminal interface test specification | Rel-18 |