Description
The PhoneBook IDentifier (PBID) is a standardized identifier defined in 3GPP specifications, particularly in TS 31.102 for USIM application toolkit and TS 21.905 for vocabulary terms. It serves as a unique reference key for individual entries within phonebook storage on a Universal Integrated Circuit Card (UICC), such as a SIM or USIM. Each contact record—including fields like name, phone number, and email—is assigned a PBID, allowing applications to retrieve, update, or delete specific entries without scanning the entire phonebook. The identifier is typically implemented as an integer or structured value within the UICC's file system, often tied to the Elementary File (EF) used for phonebook data storage.
Architecturally, the PBID operates within the UICC's application layer, accessible via commands defined in ETSI/3GPP standards for card communication. When a mobile device or network application needs to manipulate phonebook data, it uses the PBID in conjunction with APDU (Application Protocol Data Unit) commands to target precise entries. This is crucial for features like synchronization with external servers, backup operations, or value-added services that modify contacts. The PBID may be associated with additional attributes, such as entry visibility or group membership, supporting advanced phonebook management.
In practice, the PBID enables seamless interaction between the UICC and device software or over-the-air (OTA) platforms. For example, during contact synchronization, a server can reference PBIDs to update only changed entries, reducing data transmission. It also supports multiple phonebooks (e.g., SIM phonebook vs. device phonebook) by providing a consistent referencing scheme. The identifier's role extends to security, as access to PBID-linked data may be controlled by UICC applet permissions, ensuring user privacy. By standardizing PBID, 3GPP ensures interoperability across devices and networks, facilitating reliable contact management in mobile ecosystems.
Purpose & Motivation
PBID was introduced to address the need for efficient and standardized management of phonebook entries on UICCs, which became increasingly important as SIM cards evolved to store more contact data. Prior to its standardization, phonebook access relied on positional indexing or proprietary methods, leading to fragmentation and compatibility issues across devices and operators. Release 6 of 3GPP formalized PBID to provide a universal, unique identifier for each contact, enabling precise CRUD (Create, Read, Update, Delete) operations.
The creation of PBID was motivated by the growth of mobile services that interact with phonebooks, such as over-the-air provisioning, contact backup, and value-added services like caller ID enhancement. It solves problems of data corruption during updates and inefficient synchronization by allowing targeted entry manipulation. Historically, as phones supported larger contact lists and multi-SIM scenarios, a robust identifier became essential for maintaining data integrity and user experience. PBID also supports regulatory features, such as emergency contact storage, by ensuring reliable access to specific entries. Its inclusion in 3GPP standards reflects the industry's move toward interoperable UICC applications, reducing costs and improving service deployment.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (31 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 an enhancement to the USIM OPL configuration to support a 3-byte TAC when in NG-RAN. Additionally, the release included a clarification about the presence of the EFIMSConfigData file in both ISIM and USIM applications.
- Subscription identifier privacy suppport TS 31.102CR0778
- 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
+ 1 more changes
In Release 16, the PBID function was updated to support the USIM configuration of a "PS Data Off list" for both home and roaming scenarios. Additionally, the release introduced clarifications to the reading procedure for the UAC Access Identities Configuration EF stored on the USIM. These changes enhanced the USIM's role in managing user connectivity policies and access control parameters.
- 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
- Dedicated AID for USIM Applications with non-IMSI based SUPI Types TS 31.102CR0897
+ 4 more changes
In Release 17, the PBID function was enhanced through the addition of a new USIM file for storing pre-configured Closed Access Group (CAG) information. This allows the USIM, as a defined application on the UICC, to manage network access parameters for non-public networks. The update specifically enables the storage of CAG identifiers within the phonebook's dataset structure on the USIM.
- 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 PBID function was enhanced by mandating that Service n°133 (5G Security Parameters extended storage) be enabled whenever Service n°123 is enabled on the USIM. This ensures consistent storage capabilities for security parameters within the phonebook's infrastructure. Additionally, new Elementary Files (EFs) for Access Control to GBA_U_APIs and for IMS Data Channel configuration were added to the USIM, expanding the configurable data associated with the phonebook identifier.
- 5G Security Parameters extended storage on USIM (Mandating Service n°133 to be enabled when Service n°123 is enabled) Rel18. TS 31.102CR1014
- Add EF of Access Control to GBA_U_APIs to the USIM TS 31.102CR1007
- Add EF of IMS Data Channel configuration to the USIM TS 31.102CR1006
- Correction of DF Identifier for 5MBSUECONFIG TS 31.102CR0984
In Release 19, the enhancement for the PhoneBook IDentifier (PBID) function specifically addressed backward compatibility for USIMs that lack extended security parameter storage in the EF_5GAuthKeys file. This ensures that the PBID function and related procedures operate correctly with older USIM applications on the UICC. The update maintains functionality across different implementation capabilities of the USIM's security parameter storage.
- Backward compatibility handling of USIM without extended security parameter storage in EF_5GAuthKeys - Rel19 TS 31.102CR1074
Explore further
Broader topics and technologies where PBID plays a role.
Defining Specifications
3GPP specifications that define or reference PBID, 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 |