Description
PRINS (Protocol for N32 Interconnect Security) is a standardized security mechanism specified in 3GPP for securing the N32 interface, which interconnects the security edge protection proxies (SEPPs) of two different public land mobile networks (PLMNs). The N32 interface is used for inter-PLMN signaling, primarily in roaming and interconnection scenarios, where network functions (NFs) like the AMF, SMF, or UDM in one PLMN need to communicate with counterparts in another PLMN. PRINS provides end-to-end protection for these signaling messages between the SEPPs, ensuring that sensitive data traversing untrusted network boundaries remains secure.
Architecturally, PRINS operates at the application layer, leveraging JSON Web Encryption (JWE) and JSON Web Signature (JWS) as defined in IETF RFCs, tailored for 3GPP's use cases. The protocol works by having the source SEPP encrypt and integrity-protect the HTTP/2-based N32 messages (using protocols like HTTP/2 with TLS for hop-by-hop security) before forwarding them to the destination SEPP. The destination SEPP then validates and decrypts the messages. PRINS supports two modes: the 'direct mode,' where a pre-shared key or certificate-based trust is established between SEPPs, and the 'indirect mode,' which may involve a security intermediary for key management. Key components include security policies negotiated via the N32-f interface, key derivation mechanisms, and algorithms for encryption (e.g., AES-GCM) and signing (e.g., ES256).
How it works: When an NF in the home PLMN sends a signaling message (e.g., a subscription update) to a visited PLMN, it reaches the home SEPP. The home SEPP applies PRINS by serializing the message into a JWE object for confidentiality and optionally wrapping it in a JWS for integrity. This protected payload is then transmitted over N32 to the visited PLMN's SEPP, which verifies the JWS (if used) and decrypts the JWE using keys established through prior security association. The decrypted message is forwarded to the target NF. This process ensures that even if the inter-PLMN link is compromised, the message content and its origin are safeguarded, preventing eavesdropping, tampering, or replay attacks.
Purpose & Motivation
PRINS was created in 3GPP Release 15 to address the security vulnerabilities inherent in inter-PLMN signaling, which became more critical with 5G's enhanced roaming capabilities and network exposure. Prior to 5G, inter-network signaling often relied on hop-by-hop security (e.g., IPsec or TLS between nodes), but this left messages exposed at intermediate points within foreign networks, risking data breaches and attacks like message injection. The motivation was to provide true end-to-end security between PLMNs, ensuring that only the intended SEPPs can access the signaling content.
The development of PRINS was driven by 5G's service-based architecture (SBA), which uses HTTP/2 APIs for NF communication, extending across network boundaries. Without PRINS, sensitive information such as subscriber identifiers, location data, or service parameters could be intercepted or altered, compromising privacy and network integrity. PRINS solves this by encrypting and signing messages at the application layer, independent of the underlying transport security, thus protecting data even if transport links are breached.
Historically, earlier mobile generations had less formalized inter-PLMN security, relying on bilateral agreements and basic encryption. PRINS introduces a standardized, scalable protocol that supports automated key management and policy negotiation via the N32-f interface, enabling seamless secure roaming in multi-vendor environments. It addresses regulatory requirements for data protection (e.g., GDPR) and enhances trust in 5G ecosystems, facilitating global interoperability while mitigating risks from increasingly sophisticated cyber threats.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (13 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the protocol for securing the N32 interconnect interface was formally introduced under the new name PRINS (Protocol for N32 Interconnect Security), which replaced the previous ALS designation. This protocol was defined to provide application-layer security for HTTP/2 messages exchanged between SEPPs, involving procedures for security capability negotiation and cipher suite selection. Specifically, when PRINS is negotiated, it enables the establishment of dedicated HTTP/2 connections for forwarding JOSE-protected messages between network functions across different PLMNs.
- ALS renaming to PRINS TS 29.573CR0017
In Release 16, the PRINS (Protocol for N32 Interconnect Security) function was formally introduced as the application layer security protocol for the N32-f interface between SEPPs, replacing the previous "ALS" designation. This release defined the procedures for security capability negotiation, cipher suite negotiation, and the establishment of HTTP/2 connections for forwarding JOSE-protected messages when PRINS is selected. Furthermore, corrections were made to the N32 procedures and call flows to solidify the operational details of the PRINS handshake and message forwarding.
In Release 17, the PRINS function was enhanced with the introduction of the PSEPRO feature, which enables the negotiation of specific security profiles between SEPPs. This release also provided clarifications on the usage and establishment of HTTP/2 connections when PRINS is selected as the security policy on the N32-f interface. Furthermore, corrections and updates were made to the associated parameter exchange and call flow procedures.
- Clarify the usage of TLS and PRINS between SEPPs TS 33.501CR1107
In Release 18, key enhancements for PRINS included the introduction of configurable security profiles for negotiation between SEPPs and explicit support for Roaming Hubs (RIs) within the protocol's architecture. The modifications also enabled the use of specific connection parameters like `senderN32fFqdn` and `senderN32fPort` when PRINS is selected as the security policy. Furthermore, provisions were made to ensure backward compatibility by supporting these modified PRINS procedures in earlier 3GPP releases.
- Enable senderN32fFqdn and senderN32fPort when PRINS is selected TS 29.573CR0127
- Modification of PRINS to enable Roaming Hubs TS 33.501CR1789
- Support of Modified PRINS in earlier releases TS 29.573CR0186
- Editorial modifications on PRINS TS 33.501CR1855
- Security profiles for PRINS TS 33.501CR1889
- Support of Modified PRINS in earlier releases TS 33.501CR1972
+ 1 more changes
In Release 19, the key new feature for the PRINS function is the introduction of trust anchoring for the N32-f interface. This enhancement is complemented by the support for Modified PRINS in earlier releases, which ensures backward compatibility and a smoother transition. These updates build upon the existing framework where PRINS is negotiated between SEPPs to provide application-layer security for HTTP/2 messages exchanged across PLMNs.
- Trust anchoring for N32-f/PRINS TS 33.501CR2053
In Release 20, the PRINS function was refined, introducing the PSEPRO feature for the negotiation of security profiles between SEPPs. This allowed an initiating SEPP to indicate a candidate list of up to 256 supported security profiles for PRINS during the security capability negotiation on the N32-c interface.
- PRINS Refinement TS 33.501CR2184
Explore further
Broader topics and technologies where PRINS plays a role.
Defining Specifications
3GPP specifications that define or reference PRINS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.573 vj50 | PLMN/SNPN Interconnection Interface Stage 3 | Rel-19 |
| TS 33.501 vk00 | 5G Security Architecture and Procedures | Rel-20 |