Cross-Domain Document Communication via User Agent Mediation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current security policies restrict cross-domain event communication between documents loaded by a user agent, limiting flexibility and functionality, especially in mobile environments where content from different providers needs to interoperate.

Innovation Solution

A method and device that allow documents from different origins to exchange information by uniquely identifying the origin of the first document and sending a message to the second document through a user agent, using APIs defined in the Document Object Model (DOM) module, enabling cross-domain communication while maintaining security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If strict security policies are implemented to restrict cross-domain event communication, then security is improved, but flexibility and functionality are worsened

Engineering Contradiction:
ImprovesecurityVSAvoidflexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The user agent acts as an intermediary between documents from different domains. It receives events from the first document, identifies the origin using uniquely generated identifiers, and forwards events to the second document. This mediator approach enables cross-domain communication while maintaining security through controlled mediation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The communication mechanism is segmented into distinct components: event identification, origin identification using uniquely generated identifiers, event forwarding, and security validation. This segmentation allows each component to be optimized for its specific function while maintaining overall security and flexibility.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If documents from different domains are allowed to communicate freely, then flexibility and functionality are improved, but security is worsened

Engineering Contradiction:
ImproveflexibilityVSAvoidsecurity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The user agent performs preliminary actions by uniquely identifying the origin of the first document before allowing communication. Origin identification occurs in advance through the use of uniquely generated identifiers, enabling subsequent security validation and controlled event forwarding to the second document.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The user agent serves as a security-aware intermediary that validates origins and controls the communication flow. It mediates between documents from different domains, ensuring that security policies are maintained while still allowing authorized cross-domain event exchange.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If cross-domain event communication is enabled, then adaptability is improved, but device complexity is worsened

Engineering Contradiction:
ImproveadaptabilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The user agent is positioned as a centralized intermediary that handles all cross-domain communication logic. By consolidating the complexity into a single mediator component, the overall system architecture remains manageable while enabling adaptable cross-domain event exchange between documents.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7895604B2Method and device for event communication between documents
Publication Date: 2011.02.22 OPERA SOFTVEAR AS
  • US7895604B2 patent drawing
  • US7895604B2 patent drawing
  • US7895604B2 patent drawing

AI summary

A method for sending data from a first to a second document when both documents are loaded by a user agent implemented on a client device. The method may comprise the execution of a script in the first document, said script providing the data to be sent to the second document. The user agent may be configured to retrieve information uniquely identifying the first document as well as an origin of the first document. This information may have been collected by the user agent when the document was first loaded, and may not be influenced by the script. The user agent may then send a message to the second document containing the data provided by the script in the first document and the identification of the first document.