5G Core Authentication Sequencing Recovery Using Blockchain Ledger
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
5G networks experience authentication sequencing issues after connection loss between 5G Cores and a central database due to power outages or other disruptions, leading to potential security vulnerabilities and fraud.
Innovation Solution
Implement a Unified Data Management system with a Distributed Subscriber Database connected to multiple 5G Cores, using a blockchain to record authentication sequence numbers, enabling local operation during connection loss, reconnecting the lost connection, identifying sequencing issues, and correcting them using recorded numbers from the blockchain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If connection between 5G Core and central database is maintained continuously, then authentication sequencing is accurate, but network resilience to power outages and disruptions is reduced
Solution Approach 1:
The system performs preliminary actions by recording authentication sequence numbers in a local buffer at the 5G Core before connection loss occurs. This allows the 5G Core to continue operating with locally stored sequence information during disruptions, maintaining both sequencing accuracy and network resilience.
Solution Approach 2:
A blockchain-based distributed ledger acts as an intermediary between the 5G Core and central database. The blockchain stores authentication sequence numbers immutably and provides a reliable reconciliation mechanism after connection restoration, resolving the contradiction between continuous connection requirements and network resilience.
2Reliability
If connection is reestablished after loss, then network availability is improved, but authentication sequencing issues occur
Solution Approach 1:
The system implements feedback mechanisms by continuously monitoring authentication sequence numbers and comparing them against the blockchain ledger after connection restoration. When discrepancies are detected, the system automatically identifies and corrects sequencing issues, ensuring both high availability and accurate authentication sequencing.
Solution Approach 2:
Authentication sequence numbers are preliminarily recorded in the blockchain before any connection loss occurs. This pre-recording enables rapid reconciliation after connection restoration without requiring complex real-time synchronization, maintaining sequencing accuracy while improving network availability.
3Ease of operation
If work-around techniques like re-setting counters are used, then sequencing issues are temporarily resolved, but security vulnerabilities and fraud risks increase
Solution Approach 1:
The system creates immutable copies of authentication sequence numbers in the blockchain distributed ledger. These copies serve as permanent records that cannot be altered or reset, eliminating security vulnerabilities associated with traditional counter-resetting workarounds while maintaining ease of sequencing issue resolution.
Solution Approach 2:
Authentication sequence numbers are preliminarily stored in the blockchain with cryptographic security before any issues occur. This pre-established secure recording eliminates the need for insecure work-around techniques like counter resetting, providing both ease of operation and enhanced security.
Data Source
AI summary
Embodiments are directed towards systems and methods for reestablishing sequencing after connection loss. One such method including: recording authentication sequence numbers from the Distributed Subscriber Database to the distributed 5G Cores using a distributed ledger of a blockchain; in response to a lost connection between a 5G Core of the plurality of 5G Cores and the Distributed Subscriber Database, enabling the 5G Core to operate from a local copy of the Distributed Subscriber Database; reconnecting the lost connection between the 5G Core of the plurality of 5G Cores and the Distributed Subscriber Database; accessing the recorded sequence numbers from the Distributed Subscriber Database using the distributed ledger of the blockchain; and obviating the number sequencing issue between the Distributed Subscriber Database and the reconnected 5G Core of the plurality of 5G Cores using the recorded authentication sequence numbers in the distributed ledger of the blockchain.


