Configurable Database Views for Service Provider Data Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for sharing and customizing database information with service providers are time-consuming, costly, and require extensive knowledge of SQL techniques, especially when dealing with large databases and multiple service providers.

Innovation Solution

Implementing pre-defined configurable views of databases using CalcViews and CalcEngines, which allow customers and service providers to customize and filter data without deep SQL knowledge, enabling different views for various service providers with features like encryption, data modification, and instantaneous changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If detailed code is written to share database information with service providers, then data sharing capability is improved, but time consumption and cost increase

Engineering Contradiction:
Improvedata sharing capabilityVSAvoidtime consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-generates multiple views of the database data before actual service provider requests are made. These views are stored and can be quickly retrieved and distributed to different service providers, eliminating the need to write and execute detailed code each time data needs to be shared.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of modifying the original database or writing custom code for each service provider, the system creates copy views - simplified representations of the database data that can be distributed to multiple service providers. These copies maintain the necessary data structure while reducing the complexity of data sharing operations.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If detailed code is written to customize database views for different service providers, then data customization capability is improved, but resource costs and processing time increase

Engineering Contradiction:
Improvedata customization capabilityVSAvoidresource costs
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The database data is segmented into multiple pre-defined views, each optimized for different service provider needs. Instead of processing entire databases through custom code, the system divides data into manageable segments (views) that can be independently retrieved and distributed, reducing computational resources required.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple customized views are generated in advance before service provider requests arrive. This preliminary processing allows the system to store pre-processed, customized data representations that can be quickly delivered without requiring expensive real-time processing resources.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If detailed code is written to implement different encryption passwords for different service providers, then security capability is improved, but complexity of operation increases

Engineering Contradiction:
Improvesecurity capabilityVSAvoidcomplexity of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system introduces an intermediary layer (the view mechanism) between the database and service providers. Encryption and security parameters are managed at this intermediary level rather than requiring direct code implementation for each service provider. The view system automatically handles different encryption requirements for different providers without exposing the complexity to users.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If multiple databases are maintained for different service providers, then data security and customization are improved, but device complexity and maintenance costs increase

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

Solution Approach 1:

The system merges multiple service provider requirements into a single database system with multiple views. Instead of maintaining separate physical databases for each service provider, the system combines them into one unified database that presents different views to different providers. This reduces system complexity while maintaining security and customization through the view mechanism.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The single database system is designed to be universal, serving multiple service providers with different requirements through its multi-view capability. The same database infrastructure supports different encryption schemes, data formats, and access permissions for different providers, eliminating the need for separate database systems.

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

Data Source

PatentUS20130159355A1Configurable views for a database
Publication Date: 2013.06.20 SAP SE
  • US20130159355A1 patent drawing
  • US20130159355A1 patent drawing
  • US20130159355A1 patent drawing

AI summary

According to some embodiments, a business enterprise platform may install a database associated with a customer of the business enterprise platform. The business enterprise platform may then provide to the customer at least one pre-defined configurable view of the information in the database. Moreover, customization of the pre-defined configurable view of the information in the database by the customer and/or a service provider may be automatically facilitated.