Automatic Wireless Device Authentication via Stored Tokens

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users of wireless devices must provide explicit authentication information, such as usernames and passwords, even when accessing network servers provided by the same company that operates their service, which is inconvenient and not necessary for initial access.

Innovation Solution

Implementing Wireless Device Automatic Authentication (WDAA) that allows a provider-developed mobile application on a provider-issued wireless device to negotiate credentials with an authentication server without initial user input, using device-specific information like IMEI and ICCID to validate the device and retrieve a device token via SMS, which is stored for subsequent authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If explicit authentication information (username and password) is required for initial access to network servers, then security is maintained, but user convenience and ease of operation deteriorate

Engineering Contradiction:

ImprovesecurityVSAvoiduser convenience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary authentication by registering the wireless device with the authentication server before the user needs to access network services. The device token is obtained and stored in advance, so when the user needs to access a network server, authentication has already been completed automatically without requiring the user to provide username or password.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The wireless device automatically performs authentication with the authentication server using its own device identity, without requiring the user to manually provide credentials. The device retrieves and stores its own authentication token, and subsequently uses this token for automatic authentication when accessing network servers, making the system self-serve the authentication need.

Inventive Principle:

Principle #25Self-service

2Reliability

If explicit authentication information is required for every access attempt, then authentication reliability is improved, but loss of time and productivity worsen

Engineering Contradiction:

Improveauthentication reliabilityVSAvoidauthentication time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Authentication is performed in advance during device registration with the authentication server, obtaining a device token that can be reused for subsequent network access attempts. This preliminary authentication eliminates the need to repeatedly provide credentials for each access attempt.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Once the device token is obtained and stored, the authentication capability continues to be available for subsequent network access attempts without interruption or repetition of the authentication process. The stored token enables continuous, automatic authentication for multiple access attempts.

Inventive Principle:

Principle #20Continuity of useful action

3Ease of operation

If device token is transmitted through network infrastructure, then authentication capability is achieved, but security risk from interception increases

Engineering Contradiction:

Improveauthentication capabilityVSAvoidsecurity risk

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The critical authentication element (device token) is extracted from the network communication channel and stored locally in secure storage on the wireless device. By taking the token out of the network transmission path and keeping it stored on the device, the system eliminates the security risk of network interception while maintaining authentication capability.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of repeatedly transmitting the authentication credentials over the network, the system creates a local copy of the device token and stores it securely on the wireless device. This copy can be used for subsequent authentication without requiring repeated network transmission of sensitive credentials.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS11653207B2Automatic authentication of wireless devices

Publication Date: 2023.05.16 CHARTER COMM OPERATING LLC

AI summary

In certain embodiments, a service provider provides both wireless communication services to a wireless device and access to a network server associated with an application running on the wireless device. Network infrastructure of the service provider stores registration information about the wireless device in a provider database, receives from the wireless device an initial request for the application to access the network infrastructure, wherein the initial request includes device ID information identifying the wireless device but not explicit authentication information about a user of the wireless device, uses the device information to access the provider database to determine that the wireless device is registered, and transmits to the wireless device permission for the application to access the network infrastructure, thereby enabling the user to access the network infrastructure without having to provide explicit authentication information such as username and password.