Configurable Program System Runtime Event Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing program systems require source code modifications and recompilation to adapt to changing demands, making it impossible to alter the behavior or connections between components and event handlers without access to the source code, limiting flexibility and adaptability.

Innovation Solution

A method and system that allows configuration of program systems by initializing binary program components and a source code interpreter, setting up logical connections between interfaces, and using a configuration file to manage event handling, enabling changes to be made without source code knowledge, through a runtime environment that includes a configuration binary program component and an event distributor.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the program system uses compiled binary components with fixed connections, then the system stability and reliability are improved, but the adaptability to changing demands deteriorates

Engineering Contradiction:
Improvesystem stabilityVSAvoidadaptability to changing demands
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic configurability by introducing a configuration file that allows runtime modification of event handler connections and parameters. The system transitions from static compiled connections to dynamic configurable connections, enabling the program system to adapt its behavior without recompilation while maintaining stable core functionality.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent separates the program system into fixed binary components and configurable event handler connections. The configuration file acts as an independent segment that stores connection information, allowing modification of interaction patterns without affecting the core binary components. This segmentation enables independent modification of the configuration layer while preserving system stability.

Inventive Principle:
Principle #1Segmentation

2Manufacturing precision

If the program system requires source code modification for adaptation, then the manufacturing precision and control over changes are improved, but the ease of operation and time required for adaptation deteriorates

Engineering Contradiction:
Improvecontrol over changesVSAvoidease of adaptation
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent uses a configuration file as a copyable template that defines event handler connections and parameters. Instead of modifying source code directly, users work with configuration file copies that can be edited, validated, and reverted. This approach maintains precise control over system behavior while significantly improving ease of modification through text-based configuration rather than code editing.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The configuration file serves as an intermediary layer between the user and the binary program components. Users modify the configuration file to change system behavior, and the system automatically applies these changes without requiring direct source code modification. This intermediary approach simplifies adaptation while maintaining control through structured configuration syntax and validation mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If the program system uses object-oriented linking at runtime, then the adaptability to replace objects is improved, but the ability to change interaction patterns without source code knowledge deteriorates

Engineering Contradiction:
Improveability to replace objectsVSAvoidcomplexity of interaction patterns
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The configuration file provides a universal mechanism for defining all interaction patterns between binary components and event handlers. Instead of requiring different approaches for different types of interactions, the configuration file uses a unified syntax to specify connections, event types, and handler parameters, simplifying the management of complex interaction patterns while maintaining runtime flexibility.

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

Data Source

PatentUS8099713B2Program system, and method and system arrangement for configuring it
Publication Date: 2012.01.17 SIEMENS HEALTHINEERS AG
  • US8099713B2 patent drawing
  • US8099713B2 patent drawing

AI summary

A method and system arrangement are disclosed for configuring a program system. The method includes initializing binary program components of the program system and a source code interpreter for interpreting at least one source code event handler. Logical connections are set up between interfaces of the binary program components and interfaces of the interpreted source code event handler in order for events generated by the binary program components to be processed by the at least one source code event handler. A configuration file may also additionally be evaluated.