Wireless Reconnection Authentication Using Stored Decryption Results
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional security protocols for wireless connections, such as TLS, require repeated decryption operations for authentication, which are computationally intensive and consume significant power, especially in devices like IoT devices that frequently reconnect to the same endpoints.
Innovation Solution
Implement a method where a wireless device parses authentication values into two portions, performing a hash operation on one portion and a decryption operation on the other, and stores the decryption result for subsequent connections, allowing validation without repeated decryption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional security protocols perform decryption operations for authentication on each connection, then authentication security is maintained, but computational load and power consumption increase significantly
Solution Approach 1:
The patent performs the computationally intensive decryption operation during the initial connection to authenticate the server certificate, then stores the resulting public key. During subsequent connections, this pre-computed public key is reused for authentication, eliminating the need to repeat the decryption operation and thus reducing power consumption while maintaining security.
Solution Approach 2:
The patent creates a copy of the server's public key after the initial decryption and authentication. This copied public key is then used in place of the original certificate during reconnections, allowing authentication without repeating the expensive decryption operation, thereby reducing computational load and power usage.
2Reliability
If decryption operations are performed repeatedly for each connection, then authentication validity is ensured, but connection establishment time increases
Solution Approach 1:
The decryption and extraction of the public key is performed as a preliminary action during the first connection. The stored public key is then readily available for subsequent connections, allowing rapid authentication without repeating the time-consuming decryption process, thus reducing connection establishment time while ensuring authentication validity.
Solution Approach 2:
By creating and storing a copy of the validated public key, the system enables rapid authentication during reconnections. The copied key can be immediately used without waiting for repeated decryption operations, significantly reducing the time required to establish subsequent connections while maintaining authentication security.
3Reliability
If full authentication protocol is executed for every connection, then security is maintained, but device complexity and processing requirements increase
Solution Approach 1:
The patent segments the authentication process into two distinct phases: an initial full authentication phase that includes decryption and public key extraction, and a subsequent simplified phase that uses the stored public key. This segmentation allows the computationally intensive operations to be performed only once, reducing ongoing processing requirements while maintaining security through the two-stage approach.
Solution Approach 2:
The complex decryption and public key extraction operations are performed as preliminary actions during the first connection. Once the public key is extracted and stored, subsequent connections can use this pre-computed key for authentication, significantly reducing the processing requirements and device complexity for reconnections while maintaining the same security level.
Data Source
AI summary
A method can include, by operation of a first wireless device, executing a hash operation on a first portion of a received authentication value to generate a hash result. In response to determining that a connection is to be refreshed, an authentication validate can be validated by decrypting a second portion of the authentication value to generate a decryption result and comparing the hash result to the decryption result. The decryption result can be stored. In response to determining that a connection is not to be refreshed, an authentication value can be validated by comparing the hash result to a previously stored decryption result. Corresponding devices and systems are also disclosed.