Multi-tenant Repository Infrastructure for Secure Data Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Smaller organizations lack the necessary resources and budget to implement a standalone ERP software architecture, and multi-tenant hosting systems face challenges in providing secure, customized solutions while efficiently utilizing computing resources.

Innovation Solution

A multi-tenant computing system with a repository that separates and manages data for each tenant using multiple layers and versions, allowing transparent layer and version visibility, and providing a robust API for data retrieval and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple tenants are hosted on a single system to optimize resource use, then resource efficiency is improved, but data security and customization for each tenant deteriorates

Engineering Contradiction:
Improveresource efficiencyVSAvoiddata security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments tenant data into isolated storage spaces within the shared repository system. Each tenant has dedicated data containers that are logically separated but physically co-located on the same infrastructure, enabling both resource sharing and data security. The segmentation is enforced through access control lists and namespace isolation mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a repository management system as an intermediary layer between tenants and the shared storage infrastructure. This mediator handles data retrieval requests by authenticating tenants, resolving data object locations, and enforcing access policies, thereby securing data while enabling efficient shared access.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If standalone ERP software is customized for each organization, then adaptability to business processes is improved, but implementation cost and complexity deteriorates

Engineering Contradiction:
Improvecustomization capabilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal repository infrastructure that serves multiple tenants simultaneously. The system provides common core functionality for all tenants while allowing individual customization through configurable parameters and optional modules. This multi-functional platform eliminates the need for separate standalone installations while maintaining customization capabilities.

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

Solution Approach 2:

The patent shifts customization from the vertical dimension (separate software installations) to the horizontal dimension (configuration options within a unified system). Tenants can customize their experience through configurable settings, data models, and process definitions without requiring separate software deployments, thereby reducing implementation complexity while preserving adaptability.

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

3Reliability

If tenant data is separated using multiple layers and versions, then data security and customization are improved, but system complexity deteriorates

Engineering Contradiction:
Improvedata securityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a nested data structure where tenant data containers are organized within hierarchical layers and versioned subsets. Data objects are nested within tenant-specific namespaces, which are in turn nested within versioned data sets, which are organized within functional layers. This nested organization provides systematic data separation while maintaining manageable system architecture through consistent hierarchical patterns.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS8868582B2Repository infrastructure for on demand platforms
Publication Date: 2014.10.21 SAP SE
  • US8868582B2 patent drawing
  • US8868582B2 patent drawing
  • US8868582B2 patent drawing

AI summary

In an aspect there is provided a method. The method may include providing, at a repository, storage for a plurality of tenants, providing a plurality of layers, and providing a plurality of versions; and separating, based on the plurality of layers and the plurality of versions, data for each of the plurality of tenants, wherein during runtime one of the plurality of tenants corresponds to the plurality of layers and one of the plurality of versions. Related apparatus, systems, techniques and articles are also described.