Usage-Driven Codebase Adaptation for Distributed Application Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Complex applications in distributed environments maintain obsolete features, leading to increased development and maintenance costs, prolonged downtimes, performance issues, and security risks due to ever-growing release packages and feature sets.

Innovation Solution

A method and system for adapting a code base and software release product based on usage patterns, involving a service center that collects usage information, generates an adapted code base by removing obsolete features, and provides tailored update packages to local sites, utilizing large language models and dependency graphs for efficient optimization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If obsolete features are maintained in the release cycles, then the application fulfills diverse customer requirements and provides comprehensive functionality, but the release package size increases and development and maintenance costs increase

Engineering Contradiction:

Improveapplication functionalityVSAvoidrelease package size

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent segments the release package into used and unused features by analyzing usage data from customer sites. The build is divided into a core set of actively used features and optional features that are not currently utilized, allowing the release package to be optimized based on actual customer needs while maintaining the capability to provide comprehensive functionality when required.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of release package composition by dynamically adjusting which features are included based on usage analysis. By monitoring feature usage metrics and modifying the build configuration accordingly, the system transforms the static release package into a dynamic, data-driven assembly that adapts to actual customer behavior patterns.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If obsolete features are maintained in the release cycles, then all customer requirements are covered, but development and maintenance costs increase

Engineering Contradiction:

Improvecustomer requirement coverageVSAvoiddevelopment and maintenance costs

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent implements a feedback mechanism where usage data from customer sites is collected and analyzed to determine which features are actually being used. This feedback loop enables the service provider to make informed decisions about feature maintenance, removing unused features from future builds while preserving those that provide value, thereby reducing development and maintenance costs without compromising customer requirements.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent applies the principle of discarding obsolete features by identifying and removing unused functionality from the release package. Simultaneously, the system recovers resources by redirecting development and maintenance efforts toward features that are actively used and provide value to customers, optimizing the allocation of computational and human resources.

Inventive Principle:

Principle #34Discarding and recovering

3Adaptability or versatility

If obsolete features are maintained in the release cycles, then the application remains comprehensive, but update downtime increases

Engineering Contradiction:

Improveapplication comprehensivenessVSAvoidupdate downtime

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent extracts unused features from the release package based on usage analysis. By removing features that are not currently utilized by customers, the update package size is reduced, enabling faster deployment and shorter downtime during updates while maintaining the comprehensiveness of the application for actively used functionality.

Inventive Principle:

Principle #2Taking out (Extraction)

4Adaptability or versatility

If obsolete features are maintained in the release cycles, then the feature set remains complete, but system performance deteriorates

Engineering Contradiction:

Improvefeature completenessVSAvoidsystem performance

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent introduces dynamics into the release package by making feature inclusion dependent on actual usage patterns. The build configuration transitions from a static, complete feature set to a dynamic assembly that adapts to customer behavior, including only those features that contribute to system performance while maintaining the ability to provide complete functionality when needed.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS20250291577A1Methods and systems for adapting a code base of an application and updating an application in a distributed environment

Publication Date: 2025.09.18 SIEMENS HEALTHINEERS AG

AI summary

A method for adapting a code base of an application including a plurality of features and being deployed in a distributed environment including a service center and one or more local sites, comprises: obtaining, at the service center, usage information indicating a usage of one or more of the plurality of features of the application operated at at least one of the one or more local sites; obtaining, at the service center, a code base of the application; generating, at the service center, an adapted code base of the application from the code base and based on the usage information; and providing the adapted code base.