Application File Access Control With Open and Close Secret Codes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing applications lack security measures for closing and ending the use of special functions, allowing unauthorized or erroneous data input and operation, particularly in networked service processing systems, leading to potential errors and fraudulent claims.

Innovation Solution

Implementing an application with open and close secret codes to verify the correctness of data and operations at both opening and closing phases, ensuring different individuals input these codes to enhance security and prevent unauthorized access or errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If security measures are introduced for opening the application file, then security is improved, but device complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The security process is segmented into distinct phases: opening phase with open secret code verification, closing phase with close secret code verification, and special function activation phase with additional password verification. This segmentation allows comprehensive security coverage without creating a single overly complex security mechanism.

Inventive Principle:
Principle #1Segmentation

2Reliability

If multiple secret codes are required for opening and closing, then security is improved, but ease of operation deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system automatically manages the secret codes and verification processes. When the application file is opened, the system prompts for the open secret code; when closing, it prompts for the close secret code. This automated self-service approach reduces the operational burden on users compared to manual security management.

Inventive Principle:
Principle #25Self-service

3Reliability

If security verification is added at closing phase, then reliability is improved, but loss of time increases

Engineering Contradiction:
ImprovesecurityVSAvoidloss of time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The close secret code is pre-configured and stored in the application file metadata. When closing is requested, the system immediately verifies the input against the pre-stored code without requiring additional setup or complex verification procedures, minimizing time loss while maintaining security.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If different individuals are required to input open and close secret codes, then security is improved, but ease of operation deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system acts as an intermediary that manages the separation of duties. It stores both open and close secret codes, verifies them at appropriate phases, and controls access accordingly. This intermediary role simplifies the user experience while maintaining the security benefit of separated authentication.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3460708B1Application, business system using same, and insurance-covered service assistance system
Publication Date: 2026.02.18 MATSUNAGA CHIKARA
  • EP3460708B1 patent drawingFigure 1
  • EP3460708B1 patent drawingFigure 2
  • EP3460708B1 patent drawingFigure 3

AI summary

[Problem to be solved] To provide an application for setting a security for verifying the input contents and operation contents when not only opening an application file but also closing the application file. [Solution] An application available in a computer system comprises; an application file which includes an open secret code for opening each application file by the application and a close secret code for closing each application file normally by the application; an application file open function for opening the application file under the condition that the input code is match with the open secret code; an application file close function for closing the application file as normally under the condition that the input code is matched with the close secret code.