One-Time Execution Code Client Verification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional security systems fail to prevent forgery or appropriation of client programs in networked environments, leading to potential leakage of personal information and disruption of online services, such as online games, resulting in economic losses.

Innovation Solution

A security system and method utilizing one-time execution codes generated by a server, which are loaded directly onto a client's memory to execute and then deleted, allowing the server to verify the client's genuineness and block connections if errors occur, thereby preventing forgery and appropriation without the client recognizing the code's operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional security systems are used to protect personal information, then personal information protection is improved, but the systems fail to detect forgery or appropriation of client programs in networked environments

Engineering Contradiction:

Improvepersonal information protectionVSAvoiddetection of forged clients

Core Design Contradiction:

ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The server generates and transmits one-time execution codes to the client before actual service interaction. These codes are executed in advance to verify client genuineness, and the execution results are stored for later comparison during actual service usage, enabling proactive detection of forged clients before they can access personal information

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system establishes a feedback mechanism where the client executes the one-time execution code and returns the execution result to the server. The server compares the returned result with the expected result to determine client authenticity. This feedback loop enables continuous verification and detection of forgery or appropriation throughout the service interaction

Inventive Principle:

Principle #23Feedback

2Reliability

If one-time execution code is generated as a file for client verification, then verification capability is improved, but the client can recognize and analyze the code operations

Engineering Contradiction:

Improveclient verification capabilityVSAvoidclient recognition of code operations

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the one-time execution code from the traditional file-based form and embeds it directly into the network communication data stream. The code is transmitted as part of the network packet, executed in the client's memory without being stored as a file, and then deleted after execution. This extraction from file form prevents the client from recognizing and analyzing the code's operational patterns

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The one-time execution code is designed as a disposable object that is generated, executed, and then immediately deleted. It is not stored persistently in the client or server, but rather exists only during the verification process. This transient nature prevents the client from analyzing code patterns over time and recognizing the verification mechanism

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

3Adaptability or versatility

If the server transmits critical personal information to clients without verification, then service accessibility is improved, but forged or appropriated clients can access personal information

Engineering Contradiction:

Improveservice accessibilityVSAvoidpersonal information security

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The server performs client verification using one-time execution codes before allowing any service interaction or data transmission. This preliminary verification ensures that only genuine clients can access services and personal information, maintaining both accessibility for legitimate users and security against forged clients

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The one-time execution code acts as an intermediary verification mechanism between the server and client. Instead of directly trusting the client or using complex authentication protocols, the system uses this intermediate code execution as a simple yet effective mediator to verify client authenticity before allowing any information exchange

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9830434B2System and method for security using one-time execution code

Publication Date: 2017.11.28 WELLBIA COM

AI summary

The present invention relates to a security system, and more particularly, to a security system and method using a one-time execution code in an environment in which a client and a server are connected through a network. The server irregularly generates and transmits the one-time execution code to the client, and the client directly executes the one-time execution code on a memory area and transmits the execution result and deletes the one-time execution code on the memory area. Therefore, the server determines whether or not an error exists in the execution result and can prevent forgery and appropriation of the client by blocking the connection with the client.