Cross-Domain Service Injection Layer for Web Interoperability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Web resources developed without consideration for interoperability may face challenges in communicating across different domains, leading to difficulties in adding new functionalities to web applications without recoding and recompiling services, which is complex and resource-intensive.

Innovation Solution

A cross-domain communication and service injection layer facilitates communication between web-based applications and services on different domains using HTML5 messaging protocols, allowing for the delivery of additional functionalities to applications without altering the service backend, by establishing a bridge for communication and service injection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If web resources are developed without interoperability considerations, then development simplicity is maintained, but communication capability between different domains deteriorates

Engineering Contradiction:

Improvedevelopment simplicityVSAvoidcommunication capability

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces a service store as an intermediary layer between web resources on different domains. This service store contains a service registry that enables services to register themselves and be discovered by applications across domain boundaries, thereby enabling communication without requiring changes to the original web resources while maintaining development simplicity

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into distinct components: web resources, service registry, service store, and applications. This segmentation allows each component to remain independent and simple to develop, while the service store provides the interoperability mechanism that connects these segmented components across domains

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If new functionalities are added to web applications by recoding and recompiling services, then functionality is enhanced, but system complexity and resource expenditure increase

Engineering Contradiction:

Improvefunctionality enhancementVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by having services register themselves in advance with the service registry before being needed. This pre-registration allows applications to discover and utilize new functionalities dynamically without requiring recoding or recompiling, as the services are already prepared and registered in the service store

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The service store provides a universal mechanism that works across different domains and applications. A single service registration in the service registry can be utilized by multiple applications, providing enhanced functionality across the system without requiring separate implementations for each application, thereby reducing overall system complexity

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9942352B2Method and system for a crowd service store

Publication Date: 2018.04.10 SAP PORTALS ISRAEL

AI summary

A method, medium, and system to receive a request for a web-based service from an application, determine whether the requested service is available for consumption, invoke an application programming interface (API) call to the requested service, establish a communication connection between the application and the requested service, and deliver the requested service to the application over the established communication link, including management thereof.