Network Authentication Using Ledger-Based Identifiers for SIM-Free IoT
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional SIM authentication methods are costly, resource-intensive, and difficult to implement in small-scale devices like IoT devices, consuming valuable real estate and requiring time-consuming computations.
Innovation Solution
Devices authenticate using pre-provisioned data and identifiers generated at the network-side, eliminating the need for physical SIM cards or eSIM profiles by maintaining records in a secure ledger at the core network and pre-provisioning devices with corresponding security parameters.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional SIM authentication methods are used, then security and authentication reliability are improved, but device manufacturing cost increases and device real estate is consumed
Solution Approach 1:
The patent uses a virtual copy of authentication credentials stored in a ledger at the network side, rather than requiring physical SIM cards or eSIM profiles in the device. The authentication application generates authentication identifiers based on these virtual credentials, eliminating the need for physical authentication hardware while maintaining security.
Solution Approach 2:
The patent extracts the authentication credentials from the device side and stores them in a ledger at the network side. Only authentication identifiers derived from these credentials are stored in the device, separating the heavy authentication data from the device to reduce manufacturing complexity and cost.
2Reliability
If traditional SIM authentication methods are used, then authentication security is improved, but device resources are consumed
Solution Approach 1:
The patent creates a lightweight copy of authentication data in the form of authentication identifiers that can be generated and verified without requiring the full authentication credentials to be present in the device. This reduces the computational and storage resources needed in the device while maintaining security.
Solution Approach 2:
Instead of storing full authentication credentials in the device and verifying them locally, the patent inverts the approach by storing credentials in the network ledger and generating verification identifiers in the device. This shifts the computational burden from the device to the network, reducing device resource consumption.
3Reliability
If traditional SIM authentication methods are used, then authentication capability is improved, but device complexity increases
Solution Approach 1:
The patent extracts the complex SIM card or eSIM profile infrastructure from the device and replaces it with a simpler authentication application that generates identifiers based on pre-provisioned security parameters. This eliminates the need for SIM card slots, eUICC hardware, and associated software complexity.
Solution Approach 2:
The patent uses simplified authentication identifiers that are functionally equivalent to traditional SIM credentials but require much simpler device infrastructure to store and process. These identifiers can be generated using basic cryptographic operations without requiring full SIM card functionality.
4Reliability
If traditional SIM authentication methods are used, then network access control is improved, but communication overhead increases
Solution Approach 1:
The patent uses compact authentication identifiers that can be transmitted efficiently over the network compared to traditional SIM authentication protocols. These identifiers are derived from the ledger credentials and can be verified with minimal communication rounds, reducing network overhead.
Data Source
AI summary
A core network comprises a data store is configured to store a record associated with a wireless communication device, wherein the record comprises a plurality of pre-provisioned security parameters related to the wireless communication device. A core authentication application at the core network is configured to receive an authentication request comprising at least one security parameter stored at both the wireless communication device and in a record at the data store, obtain a registration identifier in response to inputting the at least one security parameter received in the authentication request into a first security application, obtain a network-side authentication identifier in response to inputting the registration identifier into a second security application, and determine whether the wireless communication device is authenticated and authorized to access the carrier network when a device-side authentication identifier matches the network-side authentication identifier.


