Dependency-Based Startup for Multi-Modality Medical Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current multi-modality medical processing systems require manual derivation and hard-coding of startup sequences, which becomes cumbersome when components are added or removed, and are difficult to upgrade, leading to inefficiencies and errors in initializing multiple interdependent modules.

Innovation Solution

A dependency-based startup method that generates a start order for executable components based on a dependency map, ensuring that components upon which others depend are started first, using initialization and dependency information to automate the startup sequence and facilitate efficient integration of new or removed components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual derivation and hard-coding of startup sequences is used, then the system can ensure proper initialization order, but the system becomes difficult to upgrade and maintain when components are added or removed

Engineering Contradiction:
Improveinitialization orderVSAvoidcomponent integration
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The startup sequence is transformed from a static hard-coded arrangement to a dynamic configuration driven by dependency information. The system automatically determines startup order based on component dependencies rather than following a fixed sequence, allowing the initialization process to adapt when components are added or removed without requiring manual reconfiguration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of startup sequence from a fixed manual configuration to a dynamically derived order based on dependency information. By representing dependencies as a data structure (e.g., directed graph or matrix) and using algorithms to determine startup order, the system allows automatic adaptation when component relationships change.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If manual derivation of startup sequences is performed, then correct initialization can be achieved, but extensive reconfiguration is required when new components are integrated

Engineering Contradiction:
Improveinitialization correctnessVSAvoidsystem reconfiguration
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The system performs self-service by automatically determining its own startup sequence based on dependency information. Rather than requiring external manual derivation and hard-coding, the system uses algorithms to autonomously compute the correct initialization order from its component dependency structure, eliminating the need for extensive reconfiguration when components are added or removed.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-defining dependency relationships between components in a data structure before runtime. This preliminary configuration of dependency information allows the system to automatically derive startup sequences without manual intervention during component integration, reducing reconfiguration efforts.

Inventive Principle:
Principle #10Preliminary action

3Stability of the object's composition

If hard-coded startup sequences are used, then system stability is maintained, but the system becomes difficult to upgrade

Engineering Contradiction:
Improvesystem stabilityVSAvoidsystem upgradeability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system transitions from static hard-coded sequences to dynamic algorithmic determination of startup order. This allows the system to maintain stability through consistent dependency-based initialization while simultaneously improving upgradeability, as new components can be integrated by simply updating dependency information rather than modifying hard-coded sequences.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system segments the startup sequence determination into independent dependency relationships between components. By representing the system as a collection of discrete dependency pairs in a data structure, each component's initialization requirements can be independently modified without affecting the entire startup sequence, facilitating easier upgrades and maintenance.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12016650B2Dependency-based startup in a multi-modality medical system
Publication Date: 2024.06.25 PHILIPS IMAGE GUIDED THERAPY CORP
  • US12016650B2 patent drawing
  • US12016650B2 patent drawing
  • US12016650B2 patent drawing

AI summary

A dependency-based startup method in a multi-modality medical processing system that includes receiving initialization information about a plurality of executable components to be started, the plurality of executable components including an executable modality component configured to communicate with a medical device communicatively coupled to the multi-modality medical processing system. The method also includes receiving dependency information about the executable modality component, the dependency information identifying one or more of the executable components upon which the executable modality component depends and transforming the initialization information and the dependency information into a dependency map that represents the dependencies between the plurality of executable components. Further, the method includes deriving a start order for the plurality of executable components based on the dependency map and starting the plurality of executable components in the multi-modality medical processing system according to the start order.