MRPK

Manufacturer Root Public Key

Security →
Introduced in Rel-5

MRPK is the foundational cryptographic public key belonging to a device manufacturer that authenticates the device's built-in private key to enable secure bootstrapping in the 3GPP Generic Bootstrapping Architecture.

Category
Security
Introduced
Rel-5
Where
User Equipment
Specifications
1 specs
MRPK Description Purpose Specifications

Description

The Manufacturer Root Public Key (MRPK) is a core component of the 3GPP Generic Bootstrapping Architecture (GBA), defined in TS 23.057. It is a long-term, asymmetric cryptographic public key that is uniquely associated with a device manufacturer. This key is embedded into the device's hardware or secure environment (e.g., UICC or tamper-resistant hardware) during the manufacturing process, alongside a corresponding, cryptographically paired Manufacturer Root Private Key (MRPrK). The MRPK is not used for direct user or network authentication but serves as a trust anchor to validate the device's identity and its possession of a valid manufacturer-installed key pair.

The MRPK's primary function is to authenticate a device-specific public key, often referred to as the Device Public Key (DPK). During the GBA bootstrapping procedure, the device proves to the network's Bootstrapping Server Function (BSF) that it possesses the private key corresponding to its DPK. This proof is typically in the form of a digital signature created using the Device Private Key (DPrK). The BSF can then verify this signature using the DPK. However, the BSF must first trust that the DPK genuinely belongs to the device and has not been tampered with. This is where the MRPK comes in: the DPK is digitally signed by the Manufacturer Root Private Key, creating a certificate-like structure. The BSF, which is pre-provisioned with or can retrieve the trusted MRPK for that manufacturer, can verify this signature. This chain of trust (MRPK signs DPK, DPK signs bootstrapping request) authenticates the device to the BSF.

Architecturally, the MRPK is a key element in the GBA's shared secret establishment. After device authentication, the BSF and the device derive a shared, session-specific key called the Bootstrapping Transaction Identifier (B-TID) and associated key material (Ks). This Ks is then used by the device and a Network Application Function (NAF) to secure application-layer communications. The MRPK thus enables a secure, automated, and scalable method for devices without a UICC (Universal Integrated Circuit Card) or for applications beyond the USIM to establish trusted relationships with network services. It shifts some of the trust from the operator's SIM card to the device manufacturer's secure provisioning process.

The management and security of the MRPK are paramount. The corresponding private key (MRPrK) must be kept highly secure by the manufacturer, as its compromise could allow an attacker to generate valid credentials for fake devices. The public MRPK must be distributed to all BSFs in networks that wish to support devices from that manufacturer. This distribution can happen through bilateral agreements or potentially via a centralized repository. The use of the MRPK facilitates features like secure service provisioning, device management (e.g., for IoT devices), and authentication for IP Multimedia Subsystem (IMS) applications and other services leveraging GBA.

Purpose & Motivation

The Manufacturer Root Public Key was introduced to address a key challenge in mobile security: how to authenticate devices and bootstrap secure connections for applications that operate independently of the USIM-based authentication. Traditional cellular authentication relies exclusively on credentials stored on the USIM/SIM card, which is under the control of the network operator. This model is insufficient for device manufacturers or third-party service providers who need to establish their own secure channels with the device for services like firmware updates, device management, or operator-agnostic applications.

Historically, without GBA and the MRPK, alternative methods for device authentication were ad-hoc, less secure, or required complex pre-shared key management. The MRPK provides a standardized, scalable, and cryptographically robust solution. It creates a trust model where the device manufacturer acts as a Root of Trust. This was particularly motivated by the growth of machine-to-machine (M2M) communication and the Internet of Things (IoT), where devices might be deployed without a traditional user-interactive SIM or might need to authenticate to multiple service providers.

The MRPK solves the problem of initial trust establishment in a scalable way. It allows a network operator's BSF to trust a device from a given manufacturer without having to pre-provision secrets for every individual device. The manufacturer's signature on the device key serves as a verifiable credential. This enables secure 'zero-touch' provisioning and management, which is critical for large-scale IoT deployments. It also future-proofs the architecture by providing a foundation for secure services in 5G and beyond, where a diverse ecosystem of devices and services requires flexible authentication mechanisms beyond the traditional SIM.

Evolution Across Releases

Rel-5 Initial

Initial introduction of the Manufacturer Root Public Key as part of the Generic Bootstrapping Architecture (GBA) specification. Defined its role in authenticating Device Public Keys to enable secure bootstrapping for application security, establishing the foundational trust model for manufacturer-based device authentication.

Explore further

Broader topics and technologies where MRPK plays a role.

Defining Specifications

3GPP specifications that define or reference MRPK, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.057 vj00 Mobile Execution Environment (MExE) Specification Rel-19