Software Update Correction Instruction Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software updates often require manual effort and translation for multiple languages, leading to inefficiencies and inconsistencies in creating and implementing correction instructions, especially when changes cannot be automated.

Innovation Solution

Automatically generating correction instructions, with manual instructions using templates and natural language processing to reduce developer effort and ensure consistency across languages, allowing for automated and manual updates to be sent to client systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual correction instructions are created for each language version, then translation coverage is improved, but development time and consistency are worsened

Engineering Contradiction:
Improvetranslation coverageVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by automatically generating correction instructions in advance using templates and natural language processing. Instead of manually translating each correction instruction for every language, the system pre-processes the correction logic and generates localized versions automatically, saving significant development time while maintaining translation coverage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses templates as reusable copies that can be instantiated across multiple languages. Rather than creating unique correction instructions for each language from scratch, the system copies and adapts standardized templates through natural language processing, ensuring consistency while reducing repetitive manual work.

Inventive Principle:
Principle #26Copying

2Measurement precision

If manual correction instructions are created for each language version, then translation accuracy is improved, but consistency and developer effort are worsened

Engineering Contradiction:
Improvetranslation accuracyVSAvoiddeveloper effort
Core Design Contradiction:
Measurement precisionVSEase of manufacture

Solution Approach 1:

The system applies universality by creating multi-functional templates that serve all language versions. A single template can be instantiated across multiple languages through natural language processing, ensuring that the same correction logic is applied consistently while allowing for language-specific nuances. This reduces developer effort while maintaining translation accuracy.

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

Solution Approach 2:

The system uses parameter changes by modifying template parameters (such as language-specific text, formatting, or cultural adaptations) rather than rewriting entire correction instructions. This allows consistent core logic to be preserved while adapting surface-level parameters for different languages, maintaining accuracy with minimal developer effort.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If entirely new software versions are distributed, then update completeness is improved, but download cost and deployment time are worsened

Engineering Contradiction:
Improveupdate completenessVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system extracts only the necessary correction instructions from the new software version and distributes them separately as standalone updates. Instead of requiring users to download entire new software versions, the system extracts and distributes only the specific corrections needed, reducing download size and deployment time while maintaining update completeness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system segments the software update into separate correction instruction modules that can be distributed independently. Rather than distributing a monolithic new version, the system breaks down updates into discrete, targeted corrections that can be applied selectively, reducing overall deployment time and bandwidth requirements.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9164753B2Generating software updates
Publication Date: 2015.10.20 SAP SE
  • US9164753B2 patent drawing
  • US9164753B2 patent drawing
  • US9164753B2 patent drawing

AI summary

Techniques for generating a software update include determining changes between a previous version of a software package and a new version of the software package. Whether each change can be implemented as automatic correction instructions that can be executed by a client computer system is determined. Automatic correction instructions are generated for changes that can be implemented as automatic correction instructions. Manual correction instructions are generated for changes that cannot be implemented as automatic correction instructions, including, for each of those changes, identifying a corresponding template for a text string for the change from a repository of templates and including the text string in the manual correction instruction.