Activation Schemata for Deterministic Task Timing in OS

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Highly automated driving systems and robotics face complexity due to high computing power and memory requirements, coupled with unpredictable data transmission times, making it difficult to ensure precise timing relationships between applications and fulfilling safety requirements.

Innovation Solution

The method involves making outputs of applications visible only at the start of a time slice and freezing inputs, allowing for deterministic task activation and resimulation, using multiple activation schemata synchronized to event sources, and assigning partitions for enhanced separation and safety.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If multiple applications directly communicate and transmit data immediately when available, then data transmission speed is improved, but timing predictability deteriorates

Engineering Contradiction:
Improvedata transmission speedVSAvoidtiming precision
Core Design Contradiction:
SpeedVSMeasurement precision

Solution Approach 1:

The patent applies preliminary action by pre-defining activation schemata that specify exactly when tasks should be activated based on event sources. This allows the system to prepare and schedule data transmissions in advance according to predetermined timing rules, ensuring both timely delivery and predictable timing relationships between applications.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If fewer independent processor cores are used, then device complexity is reduced, but ability to execute multiple applications deteriorates

Engineering Contradiction:
Improveprocessor core countVSAvoidapplication execution capacity
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent applies segmentation by dividing the system into multiple partitions, each with its own dedicated activation schema and event sources. This allows independent scheduling and execution of multiple applications on fewer processor cores, improving productivity while maintaining manageable complexity through structured organization of tasks and resources.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies dynamics by implementing flexible activation schemata that can dynamically select and switch between different event sources and tasks based on current system state. This enables efficient utilization of limited processor cores to execute multiple applications by dynamically allocating processing resources according to priority and timing requirements.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If data transmission timing is made unpredictable, then system flexibility is improved, but safety requirements fulfillment deteriorates

Engineering Contradiction:
Improvesystem flexibilityVSAvoidsafety requirements fulfillment
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies local quality by assigning different timing characteristics to different partitions and event sources. Critical safety-related applications use activation schemata with strict timing constraints and deterministic behavior, while non-critical applications can use more flexible timing. This allows the system to maintain high flexibility overall while ensuring safety requirements are met in critical areas.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11086666B2Activating tasks in an operating system using activation schemata
Publication Date: 2021.08.10 ROBERT BOSCH GMBH
  • US11086666B2 patent drawing
  • US11086666B2 patent drawing

AI summary

A method is described for activating tasks in an operating system, characterized by the following features: the tasks are respectively assigned to one of multiple activation schemata; triggering events are assigned to the activation schemata; and if a triggering event occurs, which is assigned to one activation schema among the activation schemata, then the tasks assigned to the activation schema are activated in accordance with the activation schema.