Push Notification Server Registration With Parallel 5G Authentication

Solution Overview

Problem

Existing registration processes for terminal devices in 5G networks are inefficient and latency-prone due to sequential authentication steps and lack of parallel processing in push notification scenarios.

Innovation Solution

Introduce a Push Notification Server (PNS) that facilitates parallel processing by receiving and transmitting terminal device identifiers and security keys to accelerate authentication and registration, thereby optimizing the registration process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sequential authentication steps are used in the registration process, then authentication reliability is ensured, but registration latency increases and processing efficiency decreases

Engineering Contradiction:

Improveauthentication reliabilityVSAvoidregistration latency

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The terminal device performs authentication with the AUSF before the push notification is sent. The authentication credentials are obtained in advance and stored in the terminal device, so that when the push notification arrives, the terminal is already authenticated and can quickly re-register without waiting for sequential authentication steps.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The registration process is divided into two independent parts: (1) authentication with the AUSF to obtain credentials, and (2) registration with the AMF using those credentials. These segments can be performed in different sequences or in parallel depending on the scenario, reducing overall latency.

Inventive Principle:

Principle #1Segmentation

2Reliability

If sequential authentication steps are used in the registration process, then authentication completeness is ensured, but processing efficiency decreases

Engineering Contradiction:

Improveauthentication completenessVSAvoidprocessing efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The terminal device performs authentication with the AUSF before the push notification is sent. The authentication credentials are obtained in advance and stored in the terminal device, so that when the push notification arrives, the terminal is already authenticated and can quickly re-register without waiting for sequential authentication steps.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The registration process is divided into two independent parts: (1) authentication with the AUSF to obtain credentials, and (2) registration with the AMF using those credentials. These segments can be performed in different sequences or in parallel depending on the scenario, reducing overall latency.

Inventive Principle:

Principle #1Segmentation

3Measurement precision

If the terminal device waits for sequential authentication completion before re-registration, then authentication accuracy is ensured, but re-registration speed decreases

Engineering Contradiction:

Improveauthentication accuracyVSAvoidre-registration speed

Core Design Contradiction:

Measurement precisionVSSpeed

Solution Approach 1:

The terminal device performs authentication with the AUSF before the push notification is sent. The authentication credentials are obtained in advance and stored in the terminal device, so that when the push notification arrives, the terminal is already authenticated and can quickly re-register without waiting for sequential authentication steps.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12490089B2Network nodes and methods therein for facilitating registration of terminal device

Publication Date: 2025.12.02 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

The present disclosure provides a method (300) in a Push Notification Server, PNS. The method (300) includes: receiving (310), from a terminal device, a terminal identifier of the terminal device, a network identifier of a serving network of the terminal device, and an identifier of an Access and Mobility Management Function, AMF; transmitting (320), to the AMF, a request for an identifier of an Authentication Server Function, AUSF; receiving (330) the identifier of the AUSF from the AMF; and transmitting (340), to the AUSF, the terminal identifier, the network identifier, and the identifier of the AMF.