Time-Controlled Distributor for Real-Time Software Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integrating software components from a development system to target hardware in a distributed real-time system while adhering to real-time constraints poses challenges, particularly in ensuring timely data exchange and synchronization across different hardware environments.

Innovation Solution

An expanded development system is created by connecting computing nodes of the target hardware to development system computers via time-controlled distributor units, establishing a sparse global time for precise timing, allowing TT message templates to be provided by both simulation and operative processes, and implementing integration in multiple phases with defined transmission and reception times.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If software components are developed separately on development system and then integrated on target hardware, then independent development and testing is enabled, but integration complexity and time increase

Engineering Contradiction:
ImproveIndependent software component developmentVSAvoidSystem integration complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The system is segmented into multiple software components that can be developed independently on the development system. Each component can be tested and debugged separately using development system tools before integration, reducing the complexity of managing large monolithic systems while enabling parallel development by different teams.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Software components are developed, tested, and debugged in advance on the development system before being integrated on the target hardware. This preliminary action allows teams to complete component preparation work beforehand, reducing the complexity and time required for actual system integration.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If development system supports additional functions beyond target hardware, then program development and debugging is facilitated, but hardware complexity and cost increase

Engineering Contradiction:
ImproveProgram development convenienceVSAvoidDevelopment system hardware complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The development system is designed with multi-functionality, supporting not only the basic functions required by the target hardware but also additional functions for interactive simulation, testing, and debugging. This universal platform serves multiple purposes: development, simulation, and validation, justifying the increased hardware complexity through enhanced operational capability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The development system acts as an intermediary between the developer and the target hardware, providing enhanced tools and functions that facilitate program development and debugging. These additional functions serve as a mediator that makes the development process easier while the final product on target hardware remains optimized for its specific purpose.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If software components are integrated gradually in multiple phases, then integration risk is reduced, but integration time increases

Engineering Contradiction:
ImproveIntegration reliabilityVSAvoidTotal integration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Software components are prepared in advance on the development system with preliminary testing and validation. This preliminary action ensures that components are ready for integration with known quality, reducing the need for extensive debugging during integration phases and making the extended integration timeline more efficient.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The integration process is segmented into multiple phases where components are integrated incrementally. This segmentation allows for systematic validation at each stage, reducing integration risk by catching issues early while maintaining a structured approach that prevents time waste through organized progression.

Inventive Principle:
Principle #1Segmentation

4Reliability

If real-time constraints are enforced during integration, then system performance is ensured, but integration flexibility decreases

Engineering Contradiction:
ImproveReal-time constraint complianceVSAvoidIntegration flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

Real-time constraints are analyzed and specified in advance during the planning phase. By determining timing requirements beforehand, the system can enforce these constraints during integration without constantly adapting to new requirements, thus maintaining flexibility in the integration process while ensuring real-time performance is achieved.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system allows for parameter changes in software components during development and integration phases. By enabling configuration adjustments and optimization of timing parameters, the system can adapt to real-time constraints while maintaining integration flexibility through programmable rather than fixed parameters.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10671382B2Device and method for integrating software components into a distributed time-controlled real-time system
Publication Date: 2020.06.02 TRUSTMOTION AUSTRIA GMBH
  • US10671382B2 patent drawing

AI summary

The invention relates to a device for integrating software components of a distributed real-time software system, said components being run on target hardware and on a development system, wherein the target hardware comprises computing nodes, and the development system comprises one or more computers. The device is designed as an expanded development system in which the computing nodes of the target hardware are connected to the computers of the development system via one or more time-controlled distributor units, wherein the expanded development system has a sparse global time of known precision, and wherein the computing nodes of the target hardware are connected to the computers of the development system via the one or more time-controlled distributor units such that the data content of a TT message template of a TT platform of the target hardware can be provided both by a simulation process of the development system as well as by an operative process of the target hardware in a timely manner.