Description
The Bootstrapping Server Function (BSF) is a central component of the 3GPP Generic Authentication Architecture (GAA), defined as a security framework for authentication and key agreement. It operates as a standalone network function that interfaces with the Home Subscriber Server (HSS) or Unified Data Management (UDM) to perform bootstrapping procedures. The core principle involves leveraging the existing, strong authentication between the User Equipment (UE) and the mobile network (via the Authentication and Key Agreement (AKA) protocol) to derive application-specific security credentials. This process, known as 'bootstrapping,' establishes a shared secret between the UE and a Network Application Function (NAF) without requiring a prior direct security association.
Architecturally, the BSF is a server-side entity that communicates with the UE (acting as a GAA client) and the NAF. The procedure begins when the UE contacts the BSF to initiate bootstrapping. The BSF then interacts with the HSS/UDM to fetch authentication vectors (e.g., quintets for UMTS AKA or vectors for EPS AKA/5G AKA). It challenges the UE using these vectors. Upon successful mutual authentication, both the BSF and the UE independently compute a shared, session-specific root key called the Bootstrapping Transaction Identifier (B-TID) and associated key material (Ks). This Ks is a long-term key derived from the AKA session.
The BSF's role is to act as a trusted key generator and distributor. After bootstrapping, when the UE needs to access a service provided by a specific NAF (e.g., a Multimedia Broadcast Multicast Service (MBMS) server, a location-based service, or a 3GPP application server), the UE presents the B-TID to the NAF. The NAF then queries the BSF, using the B-TID, to obtain the relevant key material (a NAF-specific key, Ks_NAF, derived from Ks) for that service session. This allows the NAF and UE to establish a secure channel. The BSF thus decouples the core network authentication from application-layer security, enabling a wide range of services to leverage the robust cellular authentication infrastructure.
Key interfaces for the BSF include the Ub interface towards the UE for the bootstrapping procedure, the Zn interface towards the NAF for key distribution, and the Zh interface towards the HSS or UDM for retrieving authentication data. In 5G systems, the BSF aligns with the service-based architecture, potentially exposing its capabilities as a Network Function (NF) service. Its implementation is critical for enabling secure, standardized, and scalable authentication for value-added services across 3GPP, 4G, and 5G networks, forming the backbone for many GAA-based security solutions.
Purpose & Motivation
The BSF was created to address the fundamental problem of how to securely authenticate users and devices to a multitude of application servers (NAFs) without requiring each application to manage its own separate credential database or establish a direct trust relationship with the cellular core network. Prior to GAA, applications either used weak, application-specific passwords or required complex, out-of-band provisioning of certificates or shared keys, which did not scale and were vulnerable to attacks. The BSF provides a standardized, network-operator-controlled method to reuse the strong, subscription-based authentication of the mobile network.
The primary motivation was to enable new, secure mobile services—such as broadcast/multicast content protection (MBMS), secure device management, financial transactions, and lawful interception—by providing them with a reliable source of cryptographic keys derived from the user's SIM/USIM authentication. The BSF solves the key distribution problem in a scalable way. It allows the mobile operator to act as a trusted third party, generating and providing session keys to authorized application providers, thereby creating a business-to-business security framework. This facilitated the secure commercialization of mobile services beyond basic voice and data.
Historically introduced in 3GPP Release 6 as part of GAA, the BSF addressed the security needs of emerging IP Multimedia Subsystem (IMS) services and other network applications. It provided a future-proof architecture that has evolved through 4G and into 5G, where its role remains essential for service-based security, especially in network exposure scenarios. It addresses the limitations of static, pre-configured security by enabling dynamic, on-demand key establishment that is tied to the live network authentication state of the user.
What changed in its specifications
The latest release-to-release comparison of specifications that define BSF. Each summary describes the whole specification, not only this term.
Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Rel-19 TS 23.503 adds Network Slice Replacement and Energy Saving Indicator reporting, Application Function influence on payload header handling, and Local Offloading Management Policy for edge computing. It also adds ATSSS Phase 4 multi-access steering (MPQUIC-E, ATSSS-LL), spending-limit policy for roaming, and PCF use of network analytics.
Full comparison in TS 23.503 →Architecture
Where it sits in the network
- Mobile Network → 5G Core → BSF (Signaling)
Technology family
Security functions and anchors · Security
- Phase 1 AuC
- R99 HLR/AuC
- Rel-5 HSS
- Rel-6 3GPP AAA Server, BSF
- Rel-8 ASME, MME
- Rel-9 HSS-FE
- Rel-15 AMF, ARPF, AUSF, SEAF, SEPP, SIDF
- Rel-16 AAnF
- BSF used together with HSS
“The reference point Zh used between the BSF and the HSS allows the BSF to fetch the required authentication information and all GBA user security settings from the HSS.” TS 33.220
- BSF counterpart in another generation: AAnF
“The procedures follow those given in clause 5.3.0 of TS 33.222 [7] with the AKMA AF taking the role of the NAF from GBA (see TS 33.220 [4]), with the following changes.” TS 33.535
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 10 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
The BSF is specified for the first time in TS 33.220: it mutually authenticates the UE via AKA, derives NAF-specific session keys, and supplies key material to NAFs.
- “A generic Bootstrapping Server Function (BSF) and the UE shall mutually authenticate using the AKA protocol, and agree on session keys” TS 33.220 v6.13.0
- “the BSF shall be able to send a bootstrapping transaction identifier to the UE;” TS 33.220 v6.13.0
- “The BSF shall be able to send the requested key material to the NAF;” TS 33.220 v6.13.0
BSF gained new capabilities in 33220 Rel-7: an optional GUSS timestamp option towards the HSS, removal of NAF Group attributes from USSs sent to NAFs, local policy on required USSs, and TLS-secured Zn'.
- “optionally the BSF may have the capability able to send the timestamp of subscriber's GBA user security settings to the HSS (timestamp option);” TS 33.220 v7.11.0
- “The BSF shall remove any existing attribute indicating NAF Grouping from the USSs sent to NAFs.” TS 33.220 v7.11.0
- “BSF may require one or more application-specific USS to be present in a particular subscriber’s GUSS for a particular requesting NAF” TS 33.220 v7.11.0
The BSF gained support for temporary identities (TMPI): it computes and stores a TMPI with the IMPI, and the UE and BSF signal support via the 3gpp-gba-tmpi product token over Ub.
- “The BSF shall store a TMPI together with the IMPI, from which it was derived (cf. Annex B.4)” TS 33.220 v8.9.0
- “the BSF shall compute a new TMPI as specified in Annex B.4 and store it together with the IMPI” TS 33.220 v8.9.0
- “A BSF shall always include the product token "3gpp-gba-tmpi" in the server response-header field when communicating over Ub.” TS 33.220 v8.9.0
Zn within the same operator may now alternatively be secured with TLS instead of only NDS/IP, and the BSF certificate profile now makes SHA-1 and SHA-256 hash support mandatory.
- “shall be secured according to NDS/IP [13] or may be secured using TLS as specified in RFC 2246 [28]” TS 33.220 v9.4.0
- “with the exception that the SHA-1 and SHA-256 hash functions shall be mandatory to support” TS 33.220 v9.4.0
TLS security requirements for the BSF changed: TLS now follows the TS 33.310 Annex E profile, with server certificate authentication of the BSF, replacing RFC 2246-based requirements and cipher suites.
- “The UE and the BSF shall support TLS according to the TLS profile given in TS 33.310 [19], Annex E.” TS 33.220 v10.1.0
- “The Client shall authenticate the BSF by use of a server certificate.” TS 33.220 v10.1.0
- “the DIAMETER based Zn' reference point between the Zn-Proxy and the BSF shall be secured using TLS as specified in Annex E of the present document;” TS 33.220 v10.1.0
BSF requirements changed: it must verify NAF authorization for the FQDN, support operator policies for 2G and SIP Digest subscribers per NAF, and handle GBA_Digest requests.
- “The BSF shall allow the operator to configure a BSF policy whether to accept 2G subscribers or not for a certain NAF.” TS 33.220 v11.5.0
- “The BSF shall discover from the request received from the UE over the Ub interface whether the UE intends to run GBA_Digest.” TS 33.220 v11.5.0
- “The BSF shall verify that the NAF is authorized to use that FQDN.” TS 33.220 v11.5.0
The BSF's GBA procedures changed: TLS support requirements were added (cipher suites without encryption not allowed), and the UE's check of the realm FQDN against the BSF certificate was removed from the TLS setup.
- “The UE and the BSF shall support TLS according to the TLS profile given in TS 33.310 [19], Annex E.” TS 33.220 v12.3.0
- “In the set up of the TLS tunnel, the UE shall authenticate the BSF by means of a certificate provided by the BSF.” TS 33.220 v12.3.0
- “The UE shall check that the "realm" attribute contains the same FQDN of the BSF that was present in the certificate offered by the BSF.” TS 33.220 v12.3.0
BSF gained SBI-capable GBA support (HSS/UDM discovery via NRF, N68/N65 use), SHA-256 MAC* computation, and new binding registration of PCF for a UE and MBS sessions.
- “An SBI capable BSF performs discovery and selection of an SBI capable HSS.” TS 33.220 v17.4.0
- “If an indication that the UICC supports SHA-256 is received from the HSS, the MAC* is computed as MAC*= MAC⊕ Trunc(SHA-256(IK))” TS 33.220 v17.4.0
- “This service operation also allows a NF service consumer (e.g. PCF for a UE) to register PCF for a UE binding information for a UE in the BSF” TS 29.521 v17.11.0
Rel-19 adds BSF subscription expiration times and expiry of BSF entries, plus stale-registration notification to PCFs, which indicate whether registrations are maintained, as new BSF behaviour.
- “This feature indicates the support of expiration times for BSF subscriptions.” TS 29.521 v19.7.0
- “In addition, BSF can notify any type of PCF about suspicion for stale registrations and the PCF indicates whether the registrations need to be maintained in BSF.” TS 23.502 v19.9.0
- BSF entries expiration TS 29.521CR0232
BSF notification behaviour was extended: it can notify subscribed consumers of binding events and suspicious stale PCF registrations via cleanUpCallbackUri, including bindingIds and registration expiration handling.
- “the BSF is locally configured with a registration expiration time to check the validity of bindings registered by PCF” TS 29.521 v20.1.0
- “The service operation may also be used by the BSF to notify the suspicious stale binding information.” TS 29.521 v20.1.0
- Support of BSF stale registrations handling TS 29.521CR0236
Defining Specifications
3GPP specifications that define or reference BSF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.503 vk30 | 5G Policy and Charging Control Framework | Rel-20 read |
| TS 23.862 vc00 | Operator-DAP Interworking Architecture | Rel-12 read |
| TS 24.109 vj00 | HTTP Digest AKA & GAA Stage 3 | Rel-19 read |
| TS 24.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 read |
| TS 29.309 vk00 | Nbsp Service Based Interface for GBA BSF | Rel-20 read |
| TS 29.513 vk10 | 5G PCC Signalling Flows | Rel-20 read |
| TS 29.521 vk10 | Binding Support Management Service | Rel-20 read |
| TS 29.810 vd00 | Diameter Load Control Study | Rel-13 read |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 read |
| TS 33.110 vj00 | UICC-Terminal Key Establishment | Rel-19 read |
| TS 33.141 vj00 | Security for Presence Service (Ut reference point) | Rel-19 read |
| TS 33.185 vj00 | V2X Security in LTE | Rel-19 read |
| TS 33.220 vj10 | Generic Authentication Architecture (GAA) Security | Rel-19 read |
| TS 33.221 vj00 | Subscriber Certificate Distribution via GBA | Rel-19 read |
| TS 33.222 vj00 | Secure HTTP Access in GAA | Rel-19 read |
| TS 33.223 vj00 | GBA Push Function Specification | Rel-19 read |
| TS 33.246 vj00 | MBMS Security Specification | Rel-19 read |
| TS 33.259 vj00 | Key Establishment between UICC Hosting & Remote Device | Rel-19 read |
| TS 33.303 vj00 | ProSe Security Specification for EPS | Rel-19 read |
| TS 33.503 vk00 | 5G ProSe Security Specification | Rel-20 read |
| TR 33.739 vi10 | Study on security enhancement of support for | Rel-18 read |
| TS 33.749 vj00 | Study on security aspects of edge computing enhancement | Rel-19 read |
| TS 33.804 vc00 | Non-UICC SSO using SIP Digest credentials | Rel-12 read |
| TS 33.822 v800 | Inter-Access Mobility Security Architecture | Rel-8 read |
| TS 33.823 vc20 | GBA Web Browser Integration Study | Rel-12 read |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 read |
| TR 33.919 vj00 | GAA Overview TR | Rel-19 read |
| TR 33.924 vj00 | GBA-OpenID Interworking Specification | Rel-19 read |
| TS 33.938 vj30 | 5G Standalone Cryptographic Inventory | Rel-19 read |
| TR 33.980 vj00 | GAA & Liberty Alliance Interworking Guidelines | Rel-19 read |