Analytics Version Maintenance for Cross-Source Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Version mismatches between analytics computing services and their data sources, often provided by different entities, lead to failures and failures in user interactions, exacerbated by lack of coordination in upgrades, causing unexpected behavior and service disruptions.

Innovation Solution

A cloud-delivered version maintenance service that scans and identifies version mismatches, initiating corrective actions such as version upgrades for both the analytics computing service and its data sources, using maintenance data records to coordinate upgrades and provide version data packages to administrative users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If analytics computing service and data sources are upgraded independently by different entities, then each component can be updated with new features and bug fixes, but version mismatches occur causing service failures and unexpected behavior

Engineering Contradiction:
Improveservice stabilityVSAvoidversion compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The version maintenance service continuously monitors and detects version information of the analytics computing service and its data sources, comparing them against maintenance data records to identify mismatches. This feedback mechanism triggers automatic or guided corrective actions to restore compatibility, thus maintaining service reliability while allowing independent upgrades.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

A version maintenance service acts as an intermediary between the analytics computing service and its data sources. This intermediary coordinates version upgrades, ensures compatibility, and resolves version mismatches, allowing independent entities to upgrade their components without causing service failures.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If version upgrades are coordinated across multiple components, then compatibility is maintained, but complexity of version management increases

Engineering Contradiction:
Improveversion compatibilityVSAvoidversion management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The version maintenance service automatically performs version detection, comparison, and upgrade coordination without requiring manual intervention. The system self-manages the complexity of version control across multiple components, reducing the burden on users while maintaining compatibility.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The version maintenance service provides multiple functions including version detection, comparison, mismatch identification, and upgrade coordination within a single unified system. This multi-functional approach consolidates version management complexity into one service rather than requiring separate mechanisms for each task.

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

3Adaptability or versatility

If manual version tracking and coordination is performed, then version compatibility can be monitored, but time and resources are consumed for maintenance activities

Engineering Contradiction:
Improveversion compatibilityVSAvoidmaintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system automatically detects versions, compares them against maintenance records, identifies mismatches, and initiates corrective actions without requiring manual tracking or coordination. This automation eliminates the time and resources that would otherwise be spent on manual version management activities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The version maintenance service operates continuously in the background, constantly monitoring version information and automatically responding to mismatches. This continuous operation eliminates the need for periodic manual checks and ensures version compatibility is maintained at all times without consuming user time.

Inventive Principle:
Principle #20Continuity of useful action

4Ease of operation

If cloud-delivered service is used instead of on-premise installation, then deployment and updates are simplified, but control over version management may be reduced

Engineering Contradiction:
Improvedeployment simplicityVSAvoidversion control automation
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The cloud-delivered version maintenance service continuously monitors version information and automatically responds to mismatches by initiating corrective actions. This automated feedback loop maintains version compatibility without requiring user intervention, combining cloud simplicity with effective version control.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The cloud-based version maintenance service acts as an intermediary that manages version control automatically on behalf of users. This intermediary handles the complexity of version coordination while users benefit from simplified cloud-based deployment and updates without needing to understand or manage version details.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12555079B2Version maintenance service for analytics computing
Publication Date: 2026.02.17 SAP SE
  • US12555079B2 patent drawing
  • US12555079B2 patent drawing
  • US12555079B2 patent drawing

AI summary

Various examples are directed to systems and methods of maintaining a cloud-delivered analytics computing service. A version maintenance service may access version data for a subject instance of an analytics computing service and scan a plurality of remote data sources in communication with the subject instance of the analytics computing service to determine respective versions for the plurality of remote data sources. The version maintenance service may identify a first maintenance event describing a first maintenance instance of the analytics computing service that is different than the subject instance of the analytics computing service and has a version equivalent to the version of the subject instance of the analytics computing service. Responsive to identifying the first maintenance event, the version maintenance service may initiate a corrective action.