Reusable Data Chunks for Cross-Application Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems face inefficiencies in sharing and updating information across multiple devices and applications, leading to obsolete data, increased processor cycles, memory usage, and manual translation errors, which hinder productivity and accuracy.
Innovation Solution
The implementation of 'chunks' of data that can be independently created, stored, updated, and shared across various applications and devices, allowing for dynamic rendering and visualization, with associated logic to ensure consistent and accurate information dissemination.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If information is copied or cut and pasted into other documents, then the information can be shared across documents, but the information becomes obsolete or incorrect when the original source is updated
Solution Approach 1:
The patent uses embedding technology where information from the original document is copied into the target document as a live reference. This embedded information automatically updates when the source changes, maintaining accuracy while enabling sharing across documents. The embedding creates a dynamic link rather than a static copy.
2Adaptability or versatility
If multiple applications are opened and interacted with to view and share information, then information can be accessed across different tools, but processor cycles, memory, battery power, and network bandwidth are inefficiently utilized
Solution Approach 1:
The patent merges information from multiple applications into a unified embedded representation within the host application. Instead of requiring users to switch between multiple applications to view related information, the embedded elements consolidate data from various sources into a single accessible location, reducing the need to open and interact with multiple applications simultaneously.
Solution Approach 2:
The embedded information elements are designed to be universally accessible across different application contexts. The same embedded element can be viewed and interacted with within the host application regardless of its original source application, providing multi-functional access to information without requiring the original application to be open.
3Adaptability or versatility
If information is manually translated and updated across applications, then information can be adapted for different applications, but rework and delays occur
Solution Approach 1:
The patent uses automated copying of information through embedding, where the source information is copied into the target document with automatic update capability. This eliminates manual translation and updating, as changes in the source are automatically reflected in the embedded element, significantly improving productivity while maintaining format compatibility.
4Reliability
If manual intervention is used to update information across devices and applications, then information can be synchronized, but errors increase and computing resources are inefficiently utilized
Solution Approach 1:
The patent implements self-service synchronization through embedded information elements that automatically update themselves when the source changes. The embedded elements monitor their source documents and automatically refresh their content without requiring manual intervention from users, thereby improving reliability while reducing operational complexity.
Data Source
AI summary
Techniques for rendering shared data include receiving, from a data store by a computing device, data indicative of a persistent data object. The persistent data object is associated with a class indicative of a data type for information contained in the persistent data object. The persistent data object is operable to be inserted in a file generated by an application executing on the computing device. The visualization logic associated with the class may be received by the computing device. The information in the persistent data object is rendered using the selected method of visualization, and other information in the document is rendered using native rendering capabilities of the application.