Cross-Domain Data Exchange via Local Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for sharing data between web pages from different domains require a third-party entity, leading to performance, configuration, and security issues.
Innovation Solution
Implementing a method where data is shared through a local database within a navigation module, allowing modules from the same domain to access and store data securely without external entities, using HTML5 standards for secure local storage and data access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is shared between web pages from different domains using a third-party entity, then data sharing is enabled, but performance deteriorates and security issues arise
Solution Approach 1:
The patent uses a third domain's storage module as an intermediary to enable data sharing between first and second domains. The storage module in the third domain acts as a mediator that both the first domain's transmitter module and the second domain's recipient module can access, allowing cross-domain data sharing without direct communication between the originating domains.
Solution Approach 2:
The patent segments the data sharing system into distinct functional modules: transmitter module in the first domain, storage module in the third domain, and recipient module in the second domain. This segmentation allows each module to operate independently within its domain while achieving coordinated data sharing through the local database interface.
2Adaptability or versatility
If a third-party entity is used for data exchange between domains, then data communication is achieved, but bandwidth usage increases and performance decreases
Solution Approach 1:
The patent enables the navigation module to serve itself by providing local storage and access capabilities within the browser. The local database allows web pages to store and retrieve data without external server interventions, reducing the need for repeated network requests and bandwidth consumption.
Solution Approach 2:
The patent implements preliminary data storage in the local database before actual data exchange is needed. By pre-storing data locally in the navigation module, the system reduces the need for time-consuming and bandwidth-intensive data exchanges when data is subsequently accessed by different web pages.
3Adaptability or versatility
If remote entities are used for data sharing between web pages, then data exchange is enabled, but configuration complexity and security management become problematic
Solution Approach 1:
The patent extracts the storage and data access functionality from external remote entities and embeds it directly within the navigation module via the local database. This extraction eliminates the need for complex third-party server configurations and security arrangements, as the data storage capability is now an integrated part of the browser environment.
4Productivity
If local storage is used within the navigation module, then performance improves and bandwidth usage reduces, but access control between different domains becomes restricted
Solution Approach 1:
The patent applies local quality by allowing different domains to have different levels of access to the local database. Each domain's modules can store and access their own data with full permissions, while cross-domain access is controlled through the intermediary storage module mechanism, providing both local efficiency and selective adaptability.
Data Source
Figure 1~2
Figure 3
Figure 4A~4C
AI summary
The invention relates to a method for exchanging a data set between a transmitting module (32) associated with a first domain, and a receiving module (36) associated with a second domain. The transmitting module and the receiving module are adapted to be loaded onto a navigation module (20) having access to a local database (40) for recording data and accessing the data recorded by one or more modules belonging to a single navigation domain and to any module loaded on the navigation module that is also associated with said single navigation domain. The method comprises the following steps: a storage module associated with a third domain storing (120) the data set in the local database; requesting a receiving module associated with the third navigation domain to read the data set; and the receiving module reading (140) the data set in the local database.