Content Replication Between Tenants via Persistence Layer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud platforms face limitations in sharing analytics content across tenants due to limited cloud storage space and the absence of sharing mechanisms in embedded applications, making it difficult to transport content from line-of-business tenants to enterprise tenants.

Innovation Solution

Implementing content replication techniques between database tenants using a file-based persistence layer, where users can trigger replication by authenticating and selecting files to import from a source tenant to a destination tenant, enabling seamless sharing and updates of analytics content.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cloud storage space is limited per tenant, then storage cost and security are improved, but the ability to share analytics content across tenants deteriorates

Engineering Contradiction:
Improvedata isolation and securityVSAvoidcontent sharing capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a persistence layer as an intermediary component between tenant databases and the sharing mechanism. This persistence layer acts as a mediator that receives content from source tenants, stores it temporarily, and makes it available to destination tenants, thereby enabling cross-tenant sharing without compromising the isolation and security of individual tenant databases

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds a new dimensional layer to the traditional single-tenant database architecture by introducing a persistence layer that operates independently from tenant databases. This additional dimension enables content to be stored and shared across tenants without affecting the existing database isolation structure, thus maintaining security while enabling sharing

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If embedded applications are integrated into cloud platforms, then functionality and versatility are improved, but the ability to share content with external applications deteriorates

Engineering Contradiction:
Improveapplication functionalityVSAvoidcontent sharing operation
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The persistence layer is designed as a universal component that serves multiple functions: it stores content for embedded applications, enables content sharing with external applications, and provides a standardized interface for content replication. This multi-functionality allows the system to maintain rich functionality within embedded applications while also enabling seamless content sharing with external systems

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

Solution Approach 2:

The persistence layer serves as an intermediary that bridges embedded applications and external applications. It receives content from embedded applications through their standard interfaces and republishes it to external applications, thereby maintaining the functionality of embedded applications while enabling content sharing without requiring direct integration between different application types

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12135694B2Content replication between tenants
Publication Date: 2024.11.05 SAP SE
  • US12135694B2 patent drawing
  • US12135694B2 patent drawing
  • US12135694B2 patent drawing

AI summary

Content replication between tenants is provided using a user interface to an application of an enterprise tenant. The user interface includes a list of files shared by an embedded tenant. A user can select one or more selected files from the list of files. This initiates a replicate content job based on the one or more selected files. The replicate content job includes pulling each of the one or more selected files from the embedded tenant to the enterprise tenant and storing the file in the enterprise tenant database.