Server-Based Terminal Authentication Using Runtime Operation Information
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current terminal authentication methods are unreliable and prone to data leakage due to easy modification and reading of identification codes, particularly in IoT devices, leading to security risks and increased costs.
Innovation Solution
A server-based authentication method that uses terminal operation information, such as process information, code segment hash, and application signature, matched with pre-stored data using a preset strategy to verify the legitimacy of the terminal, preventing unauthorized access and data leakage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IMEI or preset key data is used for terminal authentication, then authentication can be performed, but the authentication is unreliable and easy to be read and modified
Solution Approach 1:
The patent extracts the authentication verification from static identification codes (IMEI, preset keys) and moves it to dynamic runtime behavior verification. The server collects operation information (process information, code segment hash, stack feature information, application signature information) during terminal execution and verifies it against pre-stored standard operation information, thereby extracting authentication capability from actual runtime behavior rather than static identifiers that can be easily read and modified.
Solution Approach 2:
The patent implements preliminary action by pre-storing standard operation information (standard process information, standard code segment hash, standard stack feature information, standard application signature information) on the server before actual authentication occurs. This pre-prepared reference data enables reliable comparison during runtime authentication, allowing the system to verify terminal legitimacy based on expected operational patterns rather than vulnerable static identifiers.
2Reliability
If preset key data is introduced into terminals before leaving the factory, then authentication can be performed, but the cost increases and data leakage risk increases
Solution Approach 1:
The patent introduces the server as an intermediary that holds and manages the authentication verification data. Instead of embedding authentication keys directly in terminals (which increases device complexity and leakage risk), the server acts as a mediator that collects runtime operation information from terminals and compares it against pre-stored standard operation information. This intermediary approach centralizes authentication logic and eliminates the need for complex key management in each terminal device.
3Ease of operation
If traditional authentication methods are used, then terminals can connect to servers, but forged terminals can also access services
Solution Approach 1:
The patent applies dynamics by transitioning from static authentication (comparing fixed IMEI or preset keys) to dynamic authentication (verifying runtime operation information). The server collects process information, code segment hash, stack feature information, and application signature information that change during terminal execution. This dynamic verification approach maintains ease of connection for legitimate terminals while reliably detecting forged terminals that cannot replicate authentic runtime behavior patterns.
Data Source
AI summary
The present disclosure is applied to the field of communication technology, and provides a method, device for authenticating an accessing terminal and a system. The method includes: receiving a connection request sent by the terminal, the connection request carrying first terminal operation information; obtaining pre-stored second terminal operation information, and matching the first terminal operation information with the pre-stored second terminal operation information according to a preset matching strategy; sending, when the terminal operation information matches the pre-stored second terminal operation information, authentication success information to the terminal, and establishing communication with the terminal.


