Runtime Report Generation in Multi-Tenant Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-tenant database environments, inadvertent data intermingling during report generation can lead to data security and modeling issues, compromising the privacy and integrity of data across different entities.

Innovation Solution

A data management system that performs runtime generation of reports by accessing and merging datasets from a multi-tenant database in a way that prevents intermingling, using a hybrid class to generate a hybrid runtime data object and evaluating a mapping file to determine data retrieval from appropriate data objects, ensuring data separation and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data from multiple client entities is merged during report generation in a multi-tenant database, then reporting functionality is enabled, but data security and privacy are compromised due to inadvertent intermingling

Engineering Contradiction:
Improvereporting functionalityVSAvoiddata security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments data by client entity using separate schemas in the multi-tenant database, allowing reports to be generated for specific clients without intermingling their data with other clients' data. Each client's data is accessed and processed within its own schema context, preventing unauthorized data mixing while still enabling comprehensive reporting capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the reporting mechanism with schema-aware data access) that mediates between the multi-tenant database structure and the report generation process. This intermediary ensures that data from different client entities is retrieved and processed separately, then combined only in the final report output, not during intermediate processing steps.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If separate schemas are used for each client entity, then data security is improved, but system complexity increases

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

Solution Approach 1:

The patent implements a universal reporting framework that works across multiple client entities with separate schemas. The same reporting mechanism and data access patterns are used for all clients, providing multi-functionality that handles different client data uniformly without requiring custom solutions for each client, thus managing complexity while maintaining security.

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

Solution Approach 2:

The patent uses parameter changes (specifically, schema identifiers or client entity parameters) to dynamically adjust data access queries. Instead of hardcoding separate access paths for each client, the system modifies query parameters to target the appropriate schema based on the current reporting context, reducing system complexity while maintaining data separation.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If data is accessed and merged at runtime for report generation, then reporting accuracy is improved, but processing time and computational costs increase

Engineering Contradiction:
Improvereporting accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-defining schema structures and data access paths for each client entity. The reporting mechanism is pre-configured with knowledge of where to find data for each client, eliminating the need for complex runtime data discovery and reducing processing time while maintaining accurate data retrieval from the appropriate schemas.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating temporary working copies of data from separate client schemas during the report generation process. These copies are merged in memory for the duration of report creation, then discarded. This approach allows accurate reporting on combined data without permanently intermingling the source data, and the copies can be efficiently managed and disposed of after use.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20240331057A1Run-Time Generation of Reports from Multi-Tenant Database
Publication Date: 2024.10.03 PEOPLE CENTER INC
  • US20240331057A1 patent drawing
  • US20240331057A1 patent drawing
  • US20240331057A1 patent drawing

AI summary

Provided is a data management platform that can facilitate runtime reporting across multiple entities without intermingling data of the multiple entities in accordance with at least one embodiment described herein. For instance, a data management platform according to one or more embodiments of the present disclosure can generate and/or maintain a single, centralized database (e.g., a multi-tenant database) that can include a plurality of data models (e.g., data graphs) that can respectively correspond to different entities. The data management platform can further employ and/or access such data models that can be stored in such a centralized database to facilitate runtime reporting associated with at least one of the different entities without intermingling the data of the different entities.