JPL 5G Subscriber Data Management (SDM) Partner Validated

The solution includes 5G Unified Data Management (UDM) Function.  UDM, as part of UE authentication procedures for 3GPP access, generates AKA authentication credentials and provides them to the Authentication Service Function (AUSF) for subscriber authentication. Similarly, for non-3GPP access, EAP-AKA’ is supported. Subscriber identities such as public identity (SUPI) and private identity (SUCI), stored in UDM, are used to perform user identification procedures. Based on the subscription data stored in UDM, service access is granted to UE. UDM also stores dynamic data of subscriber registration and session data to support service/session continuity. It also supports MT-SMS delivery functionality and other SMS management procedures.

The solution includes a distributed subscriber data repository that provides interface to retrieve, create, update, and delete data of 5G subscribers. It stores subscriptions for change notifications and provides procedures to unsubscribe from change notifications.

It is a high-performance and scalable database cluster that supports both local redundancy and geo-redundancy.

During the subscriber identification procedure, the 5G core network performs Physical Equipment Identity (PEI) check procedure. EIR maintains the devices blacklist and grey list status and provides it as and when requested by the consumer NF. 5G-EIR provides features to maintain equipment status of the entire Type Allocation Code (TAC) as well as of individual PEIs. In addition, it also supports binding of subscriber identity with PEI/TAC. EIR runs as a separate MS and can be scaled to meet changing traffic requirements.

AUSF supports authentication for 3GPP access and trusted as well as untrusted non-3GPP access. It provides UE authentication service to the requester NF, that is the AMF. It supports both 5G AKA and EAP AKA’ procedures. For AKA-based authentication, it generates KSEAF and KAUSF keys for UE authentication. JPL AUSF supports features to recover from synchronization failure of security contexts. On receiving the authentication request from the consumer NF, AUSF triggers the request to fetch the authentication data from the UDM.