Web Application Data Model Registration for Cross-App Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional Web browsers are unable to efficiently and accurately share data between disparate Web applications executing within the same Web page, as they operate as standalone entities and can only inefficiently acquire visible data from other applications by parsing HTML code.

Innovation Solution

Implementing a data model registration system where Web applications can expose and consume data, allowing one Web application to register and another to query and utilize its data model, enabling seamless data sharing between applications within a Web page, facilitated by a proxy and UI framework.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Web applications operate as standalone entities, then each application maintains its independence and security boundaries, but data sharing between applications becomes inefficient and inaccurate

Engineering Contradiction:
Improvedata sharing accuracyVSAvoidapplication integration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a data model registration system that acts as an intermediary between Web applications. Applications register their data models with the system, which then enables other applications to query and consume the registered data models. This intermediary approach allows accurate data sharing while maintaining application independence, as applications don't need direct integration but can still access each other's data through the registration system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If Web applications parse HTML code to acquire data from other applications, then data can be accessed, but the process is inefficient and limited to visible data only

Engineering Contradiction:
Improvedata acquisition efficiencyVSAvoiddata accessibility
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent implements preliminary action by requiring Web applications to register their data models in advance with the data model registration system. This registration occurs before other applications need to access the data. When data is needed, applications can efficiently query the registered data models without having to parse HTML code or wait for data to be rendered visible. This preliminary registration enables both efficient data acquisition and access to data that may not yet be visible in the UI.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If Web applications are integrated to share data, then functionality is enhanced, but the complexity of integration and data model management increases

Engineering Contradiction:
Improveapplication functionalityVSAvoiddata model management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies self-service by enabling Web applications to autonomously register their own data models with the data model registration system. Each application can independently expose its data models without requiring manual configuration or complex integration setup. The system automatically manages the registered data models, allowing applications to consume data from other applications simply by querying the registration system. This self-service approach enhances functionality while minimizing integration complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10460005B2Data consumption between heterogeneous web applications
Publication Date: 2019.10.29 SAP SE
  • US10460005B2 patent drawing
  • US10460005B2 patent drawing
  • US10460005B2 patent drawing

AI summary

A system includes reception of first Web application code for a first Web page from a first Web server, reception of second Web application code for the first Web page from a second Web server, execution of the first Web application code to register a first data model in a container of the first Web page, and execution of the second Web application to query the container of the first Web page for data models, request the first data model from the container, receive the first data model from the container, extract first data from the first data model, and present the first data in the first Web page.