Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Security

Onboarding SUCI

Onboarding Subscription Concealed Identifier

Security →

Onboarding SUCI is a Subscription Concealed Identifier derived from the Onboarding SUPI and used during SNPN onboarding procedures to conceal the onboarding subscriber identity over the air interface and protect privacy while a UE registers for onboarding services.

Introduced
Rel-17
Where
Services
Specifications
3 specs
Onboarding SUCI Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Onboarding SUCI (Subscription Concealed Identifier) is a privacy-preserving identifier defined in 3GPP Release 17 within the SNPN onboarding framework. It is constructed by the UE from the Onboarding SUPI using the standard SUCI generation procedure specified in TS 23.003 and TS 33.501: the UE applies the home network public key of the onboarding credentials holder (the ON-SNPN or DCS) using an ECIES-based concealment scheme (Profile A or Profile B), producing a scheme output that hides the permanent identifier. The resulting Onboarding SUCI is what the UE transmits in the Registration Request when performing initial registration for onboarding services in an SNPN, rather than exposing the Onboarding SUPI in cleartext.

The identifier plays a central role in the onboarding architecture defined by TS 23.700 and the security provisions of TS 33.857. When a UE in SNPN access operation mode has no valid subscription for the current SNPN, it uses default UE credentials to derive the Onboarding SUPI, and from that derives the Onboarding SUCI. The SNPN, or an onboarding network it delegates to, routes the authentication exchange toward the home entity that holds the onboarding subscription (the O-SNPN / DCS). Because the SUCI is concealed with the onboarding home network's public key, only that entity can de-conceal it and recover the Onboarding SUPI to look up the subscription and authenticate the UE.

The Onboarding SUCI follows the same structural format as any SUCI: a type field (0x01 for SUPI type IMSI, 0x02 for network-specific identifier), a home network identifier (MCC/MNC or realm), a routing indicator, a protection scheme identifier, the home network public key identifier, and the scheme output. This structure allows intermediate network functions — the AMF, the AUSF, and the UDM/ARPF in the serving network — to route the authentication request based on the routing indicator and home network identifier without ever learning the permanent identity. The serving network's SEPP and the home network's SEPP protect the N32 interface carrying the concealed identity between networks.

In the onboarding flow, the Onboarding SUCI is used only for the limited purpose of establishing the onboarding subscription and provisioning the UE with credentials for the target SNPN. Once onboarding completes and the UE obtains credentials for the target SNPN, subsequent registrations use a regular SUCI derived from the newly provisioned SUPI. This separation ensures that the onboarding identity cannot be correlated with the UE's operational identity by the serving network, preserving unlinkability as required by the privacy requirements in TS 33.501.

The Onboarding SUCI is defined in TS 24.501 as part of the 5GS mobility management messages and referenced in TS 23.700 (Study on enhancement of network slicing / SNPN onboarding) and TS 33.857 (Security aspects of SNPN onboarding). Its existence reflects the broader 3GPP principle that permanent subscriber identifiers must never traverse the air interface unprotected, extended here to the special case of a UE that has no subscription relationship with the network it is attaching to.

Purpose & Motivation

The Onboarding SUCI exists to solve a specific privacy and security problem introduced by SNPN onboarding: a UE that has no subscription in a given SNPN must still identify itself to a home entity in order to obtain credentials, and doing so with a permanent identifier would expose the subscriber to tracking and linkability. The standard SUCI mechanism was designed for UEs with an existing home subscription; onboarding introduces a new class of identity — the Onboarding SUPI — that is derived from default credentials and is not tied to an operator subscription in the conventional sense. A dedicated concealed identifier was therefore needed so that the onboarding identity is protected with the onboarding home network's key and cannot be de-concealed by the serving SNPN.

Before Release 17, SNPN onboarding was not standardized, and manual or proprietary provisioning was required. Any attempt to identify a UE during provisioning would have relied on cleartext identifiers or pre-shared secrets, both of which violate the privacy principles established for 5G. The Onboarding SUCI allows the authentication exchange to be routed to the correct onboarding server using only the routing indicator and home network identifier, while the actual subscriber identity remains concealed end-to-end.

The identifier also supports unlinkability: because the Onboarding SUCI is used only during onboarding and is replaced by a regular SUCI after provisioning, an observer cannot correlate the onboarding identity with the UE's later operational identity. This design directly addresses the threat of subscriber tracking that motivated the original SUCI concept in 5G Phase 1.

What changed in its specifications

The latest release-to-release comparison of specifications that define Onboarding SUCI. Each summary describes the whole specification, not only this term.

TS 24.501Rel-18 → Rel-19

Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.

Full comparison in TS 24.501 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 2 changes
  • Editor's note on onboarding SUCI derivation TS 24.501CR3391
  • Usage of the onboarding SUCI TS 24.501CR4368

Defining Specifications

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

SpecificationTitleRelease
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TR 33.857 vh10 Enhanced Security for Non-Public Networks Rel-17 read