Code Module Transfer for Secure Remote Device Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing device security methods are vulnerable to intrusion and credential theft, as authentication mechanisms can be compromised by malicious users, leading to exploitation of device functions.
Innovation Solution
A method involving the transfer of a code module between runtime environments of devices to securely access device functionality, where the code module is configured to execute within the target device's runtime environment, exposing specific functions to the initiating device, and is deleted after use to prevent unauthorized access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional authentication mechanisms (passwords, digital keys) are used to access device functions, then ease of operation is improved, but security is worsened because credentials can be stolen or forged
Solution Approach 1:
The patent extracts the authentication credentials from the traditional password/key system and replaces them with a code module that is transferred securely between devices. The code module contains the necessary authentication information in a protected format that cannot be easily stolen or forged, while still allowing easy device access.
Solution Approach 2:
The code module acts as an intermediary between the user and the device authentication system. Instead of directly using passwords or digital keys, the code module mediates the authentication process by securely carrying authentication data and enabling function invocation without exposing vulnerable credentials.
2Ease of operation
If device functions are exposed to remote devices for invocation, then ease of operation is improved, but security is worsened because malicious software may intercept credentials
Solution Approach 1:
The patent extracts credentials from the communication channel between devices, preventing interception. Instead of transmitting credentials over networks or through intermediate software, the code module is transferred directly to the target device where it executes locally, eliminating the vulnerability to credential interception.
Solution Approach 2:
The patent changes the dimension of credential storage from a shared communication channel to a localized execution environment. The code module is transferred to and executed within the target device's runtime environment, moving authentication data from a vulnerable transmission medium to a secure local context that malicious software cannot easily access.
3Reliability
If a code module is transferred to enable remote function invocation, then device security is improved, but device complexity is worsened due to runtime environment requirements
Solution Approach 1:
The patent applies universality by creating a standardized runtime environment that can execute multiple different code modules across various devices. This universal platform reduces overall system complexity by providing a common execution framework rather than requiring custom authentication mechanisms for each device-function pair.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
A first device (110) uses a first runtime environment (120) executing on the first device (110) to transfer a code module (140) to a second runtime environment (125) executing on a second device (115). The code module (140) is configured to execute within the second runtime environment (125) and expose a function of the second device (115) that is supported by the second runtime environment (125) to the first device (110). The first device (110) executes an application (130) within the first runtime environment (120). The application (130) remotely invokes the function of the second device (115) via the transferred code module (140) and the second runtime environment (125).