Authentication Event Handling for 5G Dual Registration Deletion

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In 5G communication systems, the Unified Data Repository (UDR) mistakenly deletes authentication events due to terminal dual registration, leading to communication exceptions between serving networks and the home network.

Innovation Solution

Implement methods in the Unified Data Repository (UDR) and Unified Data Management (UDM) network elements to accurately delete authentication events by associating them with serving network names, preventing mistaken deletions and ensuring reliable communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the UDR deletes authentication events based on terminal identifier alone, then the deletion process is simple and fast, but the UDR mistakenly deletes authentication events when terminal dual registration occurs

Engineering Contradiction:

Improvedeletion processing speedVSAvoidauthentication event deletion accuracy

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent segments the authentication event identification by introducing serving network name as an additional differentiation dimension. Instead of using only terminal identifier, the system now identifies authentication events through the combination of terminal identifier and serving network name, preventing mistaken deletions during dual registration scenarios while maintaining efficient processing.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces serving network name as an intermediary parameter between the terminal identifier and the authentication event. This intermediary parameter acts as a discriminator that prevents the UDR from mistakenly deleting authentication events when a terminal is registered with multiple serving networks, thereby resolving the contradiction between deletion speed and accuracy.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Device complexity

If the UDR stores authentication events with terminal identifier, then the storage structure is simple, but the UDR cannot distinguish between authentication events from different serving networks

Engineering Contradiction:

Improvestorage structure complexityVSAvoidauthentication event identification precision

Core Design Contradiction:

Device complexityVSMeasurement precision

Solution Approach 1:

The patent segments the authentication event storage by adding serving network name as a distinguishing attribute. The storage structure now organizes authentication events based on both terminal identifier and serving network name, enabling precise identification and differentiation of authentication events from different networks while maintaining a relatively simple overall structure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extends the authentication event identification from a single dimension (terminal identifier) to a two-dimensional structure (terminal identifier + serving network name). This dimensional expansion enables the system to distinguish between authentication events from different serving networks without significantly increasing storage complexity.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

3Ease of operation

If the UDM notifies the UDR to delete authentication event without specifying serving network, then the notification process is simple, but the UDR deletes the wrong authentication event in dual registration scenarios

Engineering Contradiction:

Improvedeletion notification simplicityVSAvoidauthentication event deletion correctness

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent segments the deletion notification by incorporating serving network name as a mandatory parameter. The notification structure is divided into essential components (terminal identifier, serving network name, authentication event identifier), ensuring that the UDR receives sufficient information to identify the correct authentication event for deletion without ambiguity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent enhances the deletion notification with feedback information including the serving network name and authentication event identifier. This feedback mechanism provides the UDR with precise identification details, enabling accurate deletion of the intended authentication event while preventing mistaken deletions in dual registration scenarios.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12568365B2Authentication event processing method, apparatus, and system

Publication Date: 2026.03.03 HUAWEI TECH CO LTD

AI summary

Embodiments of this application disclose example authentication event processing methods and apparatuses. One example method includes receiving, by a unified data management network element, a second authentication event processing request from an authentication server network element. The unified data management network element can then query an authentication event corresponding to the second information. The unified data management network element can then process the authentication event. The unified data management network element can then send a third authentication event processing request to a unified data repository network element. The unified data management network element can then receive a third authentication event processing response from the unified data repository network element. The unified data management network element can then send a second authentication event processing response to the authentication server network element.