Software Inventory Scheduling for Safety-Compliant Application Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computing environments face challenges in scheduling software applications due to resource contention and interference between compliant and noncompliant applications, leading to unpredictable behavior and potential failures, as they strive to meet functional safety standards like ISO 26262.
Innovation Solution
An application scheduler utilizes software inventories (SBOMs) to manage execution by identifying compliance with safety standards, prioritizing resource allocation, and controlling execution based on availability and metadata to minimize interference.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software applications are scheduled without considering compliance status, then resource allocation is simple, but safety compliance cannot be ensured
Solution Approach 1:
The patent segments software applications into compliant and noncompliant categories based on their safety standard compliance status. The scheduler then applies different scheduling policies to each segment, ensuring compliant applications receive prioritized resource allocation while maintaining separate management tracks for noncompliant applications. This segmentation enables safety compliance without requiring complete redesign of the scheduling system.
Solution Approach 2:
The patent implements local quality by applying differentiated scheduling policies to different groups of applications based on their compliance status. Compliant applications receive preferential treatment in resource allocation, while noncompliant applications are handled differently. This localized differentiation ensures safety compliance is maintained where needed without unnecessarily complicating the entire scheduling system.
2Productivity
If compliant and noncompliant applications share resources equally, then resource utilization is high, but interference and unpredictable behavior increase
Solution Approach 1:
The patent implements dynamic scheduling policies that adjust resource allocation based on the compliance status of applications. The scheduler dynamically prioritizes compliant applications during critical periods while still allowing noncompliant applications to access resources when safe to do so. This dynamic adaptation maintains high resource utilization while preventing interference that would compromise execution predictability.
Solution Approach 2:
The patent introduces the scheduler as an intermediary layer between resource allocation and application execution. This intermediary actively manages the interactions between compliant and noncompliant applications, mediating resource access to prevent harmful interference while maintaining overall system productivity. The scheduler acts as a buffer that translates resource availability into safe execution patterns.
3Reliability
If noncompliant applications are prevented from executing, then safety compliance is maintained, but system functionality is reduced
Solution Approach 1:
The patent applies partial action by allowing noncompliant applications to execute under specific conditions rather than completely blocking them. The scheduler permits noncompliant applications to run when they do not interfere with compliant applications or when execution does not compromise safety compliance. This partial allowance maintains system functionality while ensuring safety compliance is not compromised.
Solution Approach 2:
The patent changes the execution parameters of noncompliant applications based on system state and compliance requirements. Rather than a binary allow/deny approach, the system adjusts execution parameters such as resource allocation, timing, and isolation levels dynamically. This parameter-based control enables noncompliant applications to function within safety boundaries, maintaining system versatility while ensuring compliance.
Data Source
AI summary
An application scheduler can schedule an execution of a software application based on compliance with a safety standard and an availability of system resources. The application scheduler can determine, based on a software inventory, that the software application is associated with the safety standard. The software inventory can include metadata corresponding to the software application. The application scheduler additionally can determine, based on the metadata of the software inventory, a set of system resources used to execute the software application. Subsequently, the application scheduler can schedule an execution of the software application based on the availability of the set of system resources.