Local UE Authentication Certificates for Low-Latency gNB Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized authentication in 3GPP networks is a bottleneck for increasing numbers of connected devices and fails to meet control plane latency requirements, particularly in 6G use cases, and existing UE authentication mechanisms rely on shared keys rather than public/private key pairs.

Innovation Solution

UE and gNB establish a private/public key pair for local authentication, with the gNB creating a local authentication certificate containing its public key and UE identifier, which is encrypted and used for mutual authentication without relying on the Home Network's public key, allowing decentralized and fast authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If centralized authentication is used in 5G networks, then security is maintained through centralized control, but authentication latency increases and network scalability deteriorates

Engineering Contradiction:
Improveauthentication securityVSAvoidauthentication latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the authentication process into two parts: initial centralized authentication (through UDM/AUSF) for security establishment, and subsequent local authentication (between gNB and UE using cached credentials) for fast re-authentication. This segmentation allows security to be maintained centrally while enabling fast local authentication operations, resolving the contradiction between centralized security control and authentication latency.

Inventive Principle:
Principle #1Segmentation

2Reliability

If centralized authentication components are accessed for every authentication run, then authentication security is ensured, but network load increases and scalability decreases

Engineering Contradiction:
Improveauthentication securityVSAvoidnetwork scalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by having the UE cache authentication credentials (such as authentication vectors or security context) during the initial centralized authentication. This cached information is then reused for subsequent local authentication runs without requiring repeated access to centralized components. The preliminary caching action enables fast local authentication while reducing network load on UDM/AUSF, resolving the contradiction between security and network scalability.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If local authentication with public/private key pairs is implemented, then authentication speed improves and scalability increases, but device complexity and computational effort increase

Engineering Contradiction:
Improveauthentication speedVSAvoidUE computational complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service by enabling the UE to autonomously perform local authentication using cached credentials and public/private key pairs without requiring real-time interaction with centralized components. The UE independently verifies authentication tokens or decrypts local authentication data using its stored private key, enabling fast authentication while distributing computational load to the UE. This self-service approach improves authentication speed and scalability, though it does increase UE device complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP4199565B1Certificate-based local UE authentication
Publication Date: 2026.05.06 NOKIA TECHNOLOGIES OY
  • EP4199565B1 patent drawingFigure 1
  • EP4199565B1 patent drawingFigure 2
  • EP4199565B1 patent drawingFigure 3

AI summary

A method comprising: generating a certificate comprising an identifier of a base station, a public key of the base station, and a public key of a terminal; signing the certificate by a signature based on a private key belonging to the public key of the base station; sending the signed certificate to the terminal using an established security association; monitoring whether the base station receives a request for local authentication of the terminal, wherein the request comprises an encrypted certificate unit and a base station identifier; checking, without decrypting the base station identifier, whether the base station identifier is the identifier of the base station; decrypting the encrypted certificate unit using the private key if the base station identifier is the identifier of the base station; checking whether the certificate unit comprises the signed certificate; and using the public key of the terminal for a communication with the terminal if the certificate unit comprises the signed certificate.