Network Application Secure Data Sharing via Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network applications are limited in sharing and visualizing data that does not conform to their predefined data models, preventing secure and context-specific information exchange between connected entities, such as equipment operators and service providers, which hinders effective collaboration and data utilization.

Innovation Solution

A network application architecture that allows secure sharing and visualization of non-modeled data through the use of connection definitions and metadata, enabling logical connections between client systems and supporting the upload of controller and view files to format and present the data appropriately, even if the network application lacks knowledge of the data's structure or semantics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is shared through alternative electronic means (e.g., email), then data can be exchanged without conforming to network application data models, but the useful information context provided by the network application is lost

Engineering Contradiction:
Improvedata format flexibilityVSAvoidinformation context
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary component that translates and transforms data from private systems into the network application's data model format. This mediator enables data exchange without requiring the receiving system to understand the sender's native data format, thus maintaining both format flexibility and information context. The intermediary handles data transformation, metadata mapping, and context preservation between different data models.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a network application uses a predefined data model/template for data sharing, then data visualization and context are maintained, but data that does not conform to the model cannot be shared

Engineering Contradiction:
Improvedata visualization qualityVSAvoiddata type acceptance
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic data model adaptation where the system can adjust and extend the predefined data model to accommodate non-conforming data. The data model becomes flexible rather than rigid, allowing it to dynamically accept different data types and structures while maintaining the benefits of structured visualization and context. This enables the system to adapt to various data formats without losing the reliability of standardized processing.

Inventive Principle:
Principle #15Dynamics

3Productivity

If private systems are directly connected to share data, then real-time data access is achieved, but security and access control are compromised

Engineering Contradiction:
Improvedata access speedVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces a secure intermediary layer between private systems that enables real-time data access while maintaining security and access control. This intermediary component acts as a controlled gateway that authenticates requests, validates data formats, and manages permissions without requiring direct connections between systems. The mediator preserves both the speed of real-time access and the reliability of security protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10681172B2Secure data sharing through a network application
Publication Date: 2020.06.09 SAP SE
  • US10681172B2 patent drawing
  • US10681172B2 patent drawing
  • US10681172B2 patent drawing

AI summary

Some embodiments include reception, from a first client system, of first instance data of a first data structure defined by the stored metadata, the first instance data associated with a first entity, storage of the first instance data of the first data structure in a data store, reception, from the first client system, of an indication associating the first instance data, a second client system, and second data not defined by the metadata, storage of the indication in the data store, reception, from the first client system, of information for retrieving the second data from the first client system and for generating a visualization based on the second data, reception of a request for data associated with the first entity from a second client system, and, in response to the request, identification of the stored indication associating the first instance data, the second client system, and the second data, retrieval of the second data from the first client system based on the information, generation of the visualization of the second data based on the information, and transmission of a visualization of the stored first instance data and the visualization of the second data to the second client system.