Dynamic Execution Mode Control for Software Instructions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computer operating systems face challenges in managing the execution of software instructions between privileged and non-privileged modes, where commands may require mode changes based on previous execution outcomes, leading to inconsistencies and potential unauthorized access.
Innovation Solution
A computer-implemented method that monitors execution attempts and maintains records to determine the appropriate execution mode for subsequent attempts, adjusting the mode based on previous success or failure to ensure secure and authorized execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the system uses fixed privileged/non-privileged mode designations for commands, then the system structure is simple and easy to understand, but the system cannot adapt to dynamic execution requirements and may fail to execute instructions that need mode changes based on previous outcomes
Solution Approach 1:
The patent implements dynamic execution mode selection by monitoring previous execution outcomes and automatically adjusting the privilege mode for subsequent execution attempts. The system transitions from static mode designation to dynamic mode adjustment based on runtime conditions, allowing commands to execute in appropriate privilege levels determined by previous success or failure outcomes.
Solution Approach 2:
The system incorporates feedback mechanisms by recording execution outcomes of software instructions and using this information to determine the appropriate execution mode for subsequent attempts. The monitoring component captures execution results and feeds this information back to the execution control logic, which then selects the appropriate privilege mode based on the recorded outcomes.
2Reliability
If the system allows flexible mode switching based on execution outcomes, then execution control and security are improved, but the system complexity and overhead increase
Solution Approach 1:
The system performs preliminary actions by maintaining records of execution outcomes before determining the appropriate mode for subsequent execution attempts. The monitoring component proactively captures and stores execution results, preparing this information in advance so that the execution control logic can quickly determine the appropriate privilege mode without complex real-time analysis.
Solution Approach 2:
The patent introduces an intermediary monitoring component that sits between the software instruction execution and the privilege mode selection. This intermediary component simplifies the overall system architecture by centralizing the outcome tracking and mode determination logic, reducing the complexity burden on both the execution engine and the privilege management system.
3Object-affected harmful factors
If the system monitors and records execution outcomes, then unauthorized access is prevented and security is improved, but the processing overhead and execution time increase
Solution Approach 1:
The patent extracts the monitoring and record-keeping functionality into a separate, dedicated component that operates independently from the main execution flow. This extraction allows the core execution engine to operate with minimal overhead while the monitoring component handles outcome tracking in parallel or asynchronously, reducing the time penalty associated with security monitoring.
Data Source
AI summary
Execution control of computer software instructions. A determination is made as to whether a record exists that indicates an outcome of a previous attempt to execute a computer software instruction in a first execution privilege mode. A current attempt to execute the computer software instruction is controlled by causing the current attempt to execute the computer software instruction in a second execution privilege mode if the record exists and if the outcome indicates that the attempt to execute the computer software instruction in the first execution privilege mode failed.