Web Application Adapter for Cross-Domain Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web resources often face limitations in communicating with each other due to differences in domain, communication protocols, and security mechanisms, leading to prohibited or restricted interactions, especially when their development did not contemplate such interoperability.

Innovation Solution

A web application adapter provides a mechanism to connect web resources across different domains and security provisions by requesting authorization and implementing communication protocols, acting as a bridge between web pages and web services without modifying the existing resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If web resources are developed with strict domain and security provisions, then security and protocol compliance are improved, but interoperability and adaptability between different web resources deteriorate

Engineering Contradiction:
Improvesecurity complianceVSAvoidinteroperability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an adapter as an intermediary component that sits between web resources with different domains, security provisions, and communication protocols. The adapter translates and mediates interactions between incompatible web resources, allowing them to communicate without modifying their original security configurations or code. This resolves the contradiction by maintaining strict security provisions in the original web resources while enabling interoperability through the mediating adapter layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If web resources communicate without authorization mechanisms, then ease of operation is improved, but security and access control deteriorate

Engineering Contradiction:
Improvecommunication simplicityVSAvoidsecurity control
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements preliminary authorization actions by establishing security credentials and access permissions before web resources begin communicating. The adapter pre-configures authorization rules, security tokens, and access controls, allowing web resources to communicate with improved ease of operation while maintaining strong security control. The authorization framework is set up in advance, eliminating the need for complex runtime security negotiations.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If existing web resources are modified to enable communication between incompatible resources, then adaptability is improved, but device complexity and modification requirements worsen

Engineering Contradiction:
Improvecommunication capabilityVSAvoidmodification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the communication functionality by separating the adapter component from the original web resources. Instead of modifying the existing web resources to add communication capabilities, the solution divides the system into distinct segments: the original web resources remain unchanged, and a separate adapter component handles all communication and translation functions. This reduces device complexity by isolating modifications to a single modular component rather than distributing changes across multiple existing resources.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9871873B2Adapter for communication between web applications within a browser
Publication Date: 2018.01.16 SAP SE
  • US9871873B2 patent drawing
  • US9871873B2 patent drawing
  • US9871873B2 patent drawing

AI summary

A method, medium, and system to receive a request for the first web resource to access the second web resource; request authorization to access to the second web resource by the first web resource; receive authorization to grant access to the second web resource for the first web resource; transmit an application programming interface (API) call from the first web resource to the second web resource for the first web resource having authorized access to the second web resource; and transmit a reply to the API call from the second web resource to the first web resource.