Centralized Cloud Data Snapshot System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions lack the ability to effectively track and retrieve distributed business data from various cloud services, necessitating a method to gather and store data in a central repository to meet legal requirements and prevent data loss.

Innovation Solution

A computer-implemented method using a process engine to retrieve and map data from cloud-based applications via APIs, converting it into a client-specific format for storage in a central repository, with scheduling and auditing capabilities for snapshot generation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is stored in distributed cloud services, then cost and accessibility are improved, but data tracking and control become difficult

Engineering Contradiction:
Improvedata storage capacityVSAvoiddata tracking complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent introduces a central repository as an intermediary system that mediates between distributed cloud services and the company's need for data control. This repository receives, stores, and manages snapshots of data from multiple cloud services, providing a single point of control while maintaining the benefits of distributed storage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary action by creating snapshots of data before it is needed for analysis or compliance. The snapshot mechanism captures data at specific points in time, allowing the company to review, audit, and control data without interfering with ongoing cloud-based operations.

Inventive Principle:
Principle #10Preliminary action

2Ease of manufacture

If cloud-based applications are used, then total cost of ownership is reduced, but legal compliance and data control are weakened

Engineering Contradiction:
Improvecost efficiencyVSAvoiddata control reliability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the central repository continuously monitors and receives snapshots from cloud services. This feedback loop ensures the company maintains awareness of its data holdings, enabling compliance with legal requirements while preserving the cost benefits of cloud migration.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system creates copies of data in the form of snapshots stored in the central repository. These copies serve as legal records and control mechanisms, allowing the company to fulfill archival and audit requirements without maintaining direct control over the original cloud-stored data.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If data is distributed across multiple cloud services, then system flexibility and scalability are improved, but data retrieval and consolidation become complex

Engineering Contradiction:
Improvesystem flexibilityVSAvoiddata retrieval efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the data management function by separating the operational cloud services from the consolidation function. The central repository handles data retrieval and consolidation from multiple cloud services, allowing each service to maintain its flexibility while the repository provides efficient consolidation through standardized interfaces.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8990163B2Snapshot of distributed enterprise business data stored in various cloud services
Publication Date: 2015.03.24 SAP SE
  • US8990163B2 patent drawing
  • US8990163B2 patent drawing
  • US8990163B2 patent drawing

AI summary

A system and method for generating a snapshot of data associated with one or more cloud-based applications are disclosed. Application programming interfaces (APIs) and connections associated with one or more applications registered and on a server computer and used by a company are retrieved from a table by a lookup. All data associated with the one or more applications based on the APIs and connections are also retrieved. The data associated with the one or more applications is then mapped to a client-specific representation and data format. The data associated with the one or more applications is converted to the client-specific representation and data format.