Service Framework Module Dependency Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing service frameworks for developing application services face challenges in managing module dependencies and compatibility, particularly when modifications to one module affect dependent modules, leading to difficulties in maintaining a stable and compatible module stack.

Innovation Solution

A computer-implemented method that provides a service framework with modules, determines if a module has been modified, and supplies dependency data to clients, using service interface data, dynamic runtime data, and communication parameters to ensure compatibility and efficient communication between clients and servers, employing service proxy and stub data generated from an IDL model in YAML format.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a module of the module stack is modified by the client, then the client can adapt the module to its specific needs, but compatibility with dependent modules may be compromised

Engineering Contradiction:
Improvemodule adaptabilityVSAvoidmodule compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The service framework performs preliminary actions by automatically detecting module modifications and providing dependency data to affected modules before compatibility issues arise. This allows dependent modules to prepare for or adapt to changes in advance, maintaining compatibility while preserving the ability to modify modules.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The framework implements a feedback mechanism where modification data about changed modules is communicated back to the service framework, which then provides dependency data to affected modules. This closed-loop feedback system ensures that compatibility is maintained through continuous information exchange about module states and dependencies.

Inventive Principle:
Principle #23Feedback

2Reliability

If dependency data is provided to all affected modules, then compatibility can be maintained, but communication overhead and system complexity increase

Engineering Contradiction:
Improvemodule compatibilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The service framework serves multiple functions: it acts as a module repository, a modification detector, a dependency analyzer, and a communication intermediary. By consolidating these functions in a single universal framework, the system avoids the complexity that would arise from implementing each function separately in multiple components.

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

Solution Approach 2:

The framework automatically performs dependency analysis and identifies affected modules without requiring manual intervention. The system serves itself by autonomously tracking modifications, analyzing dependencies, and distributing relevant information, reducing the operational complexity of managing module compatibility.

Inventive Principle:
Principle #25Self-service

3Reliability

If modification detection is implemented, then compatibility issues can be identified, but processing time and computational resources increase

Engineering Contradiction:
Improvecompatibility assuranceVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The framework implements partial monitoring by focusing detection efforts on modules that have been modified, rather than continuously analyzing all modules. This selective approach provides sufficient compatibility assurance for changed modules while avoiding the excessive processing time that would result from comprehensive continuous monitoring of the entire system.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP4270193A1Service framework for developing application services in a dependency controlled software stack
Publication Date: 2023.11.01 VOLVO CAR CORP
  • EP4270193A1 patent drawingFigure 1
  • EP4270193A1 patent drawingFigure 2
  • EP4270193A1 patent drawingFigure 3

AI summary

A computer-implemented method for a service framework to develop application services, comprising: - providing (10) at least one module (10) of a module stack to a client; - determine if the provided module has been modified (20) by the client; - determining dependency data (30), at least comprising information on the dependency of further modules of the module stack from the provided module; and - providing the dependency data (40) of the other modules of the module stack from the provided module.