Tenant Data Structure Segmentation for Hosting Downtime Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional hosting solutions for multiple clients face challenges such as increased downtime during database upgrades, high manual effort for content deployment, and inefficiencies in backup and recovery processes due to shared database environments, while single-client systems require significant client involvement and expertise for maintenance.

Innovation Solution

A system and method for hosting multiple tenants over a network where each tenant receives a shared data structure and extended data structures, combining them into a combined data structure with tenant-specific elements, allowing for separate and secure management without impacting other tenants, using shared and tenant-specific metadata for data organization and retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a multi-client system with a common database is used to host multiple clients, then the provider can manage centralized data and reduce client involvement in system maintenance, but database upgrades cause increased downtime and manual effort is required to deploy content to clients

Engineering Contradiction:
ImproveProvider management of client systemsVSAvoidDowntime during database upgrades
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent segments the database into multiple separate physical databases, one for each client. This allows the provider to perform upgrades, maintenance, and deployments on individual client databases without affecting other clients, thereby eliminating the downtime issue inherent in centralized database systems while maintaining centralized management capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses database templates that can be copied and deployed to multiple clients. The provider creates a master database template and then copies it to individual client databases, enabling rapid deployment of content and updates across multiple clients without manual intervention for each client, thus reducing both deployment effort and upgrade downtime.

Inventive Principle:
Principle #26Copying

2Extent of automation

If a multi-client system with a common database is used, then the provider can centralize system administration, but deploying content to clients requires significant manual effort and sorting through all client content

Engineering Contradiction:
ImproveCentralized content managementVSAvoidContent deployment process
Core Design Contradiction:
Extent of automationVSEase of manufacture

Solution Approach 1:

The patent segments client content into individual client databases, allowing the provider to deploy content to specific clients without having to search through or sort through all client content in a common database. This segmentation enables targeted content deployment while maintaining centralized management capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a template-based deployment system where content is stored as templates that can be automatically copied to multiple clients. This eliminates the manual effort of sorting and deploying content to each client individually, as the system can automatically replicate templates across multiple client databases.

Inventive Principle:
Principle #26Copying

3Device complexity

If a multi-client system with a common database is used, then the provider can reduce the number of systems to maintain, but standard database tools cannot be used for backup and recovery of specific client content

Engineering Contradiction:
ImproveNumber of database systemsVSAvoidBackup and recovery process
Core Design Contradiction:
Device complexityVSEase of repair

Solution Approach 1:

The patent segments client data into separate physical databases while maintaining a unified management interface. This segmentation enables the use of standard database tools for backup and recovery of individual client databases without requiring complex custom solutions, as each client database can be treated as an independent unit while still being part of the overall multi-client system.

Inventive Principle:
Principle #1Segmentation

4Reliability

If a single-client system is used for each client, then the provider can use standard database tools for backup and recovery and perform maintenance without affecting other clients, but each client must be deeply involved in system maintenance and administration

Engineering Contradiction:
ImproveIndependent backup and recoveryVSAvoidClient involvement in maintenance
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments the system into multiple independent client databases, each with its own physical storage. This allows standard database tools to be used for backup and recovery of individual clients while maintaining centralized management. Clients are involved only in their own database maintenance, not in overall system operations, thus reducing client burden while preserving reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a unified provider management system that can perform multiple functions across all client databases, including centralized content deployment, template management, and coordination of maintenance activities. This universal management layer allows the provider to maintain control and reduce client involvement while still using standard tools for individual client operations.

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

Data Source

PatentUS8069184B2Systems and methods to implement extensibility of tenant content in a provider-tenant environment
Publication Date: 2011.11.29 SAP SE
  • US8069184B2 patent drawing
  • US8069184B2 patent drawing
  • US8069184B2 patent drawing

AI summary

The present invention discloses methods and systems for hosting tenants over a network in a computer-based environment in which a provider may store a shared data structure having shared data. A tenant receives a request for a shared data structure and retrieves the shared data structure from the provider based on shared metadata identifying the locations of shared data structures stored at the provider. In addition, based on extension metadata, the tenant retrieves an extended data structure including tenant-specific elements unique to the first tenant. The tenant server then combines the shared and extended data structures into a combined data structure including the tenant-specific elements.