Protocol-Agnostic Key-Value UI Rendering for Smaller Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network communications are data-intensive, leading to increased storage and processing burdens, slowed processing speeds, and higher costs, with a need for improved efficiency and security.
Innovation Solution
Implementing a system that uses key-value pairing to reduce communication size by transmitting keys instead of values, with keys stored on a central server or applications, allowing applications to access corresponding values as needed for rendering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If complete transaction data is transmitted through multiple applications, then data completeness is maintained, but communication size increases and processing speed decreases
Solution Approach 1:
The patent segments transaction data into two distinct parts: identifiers (keys) and values. Only identifiers are transmitted through the communication chain between applications, while complete data remains stored locally. This segmentation allows data completeness to be maintained through reference while dramatically reducing communication size and improving processing speed.
Solution Approach 2:
The patent extracts only the essential identifying information (keys) from the complete transaction data and transmits these extracted identifiers through the application chain. The full values are taken out from the communication flow and stored locally, eliminating unnecessary data transmission while preserving data completeness through reference.
2Ease of operation
If complete transaction data is stored at each application layer, then data accessibility is improved, but storage burden increases
Solution Approach 1:
The patent extracts only the identifying keys from complete transaction data and stores these extracted identifiers at each application layer. The full values are removed from distributed storage and kept only at the origin, dramatically reducing storage burden while maintaining data accessibility through key-based reference.
Solution Approach 2:
The patent creates lightweight copies of transaction data in the form of identifiers (keys) that are transmitted and stored across applications. These key copies serve as references to the full data, enabling accessibility without duplicating the complete data burden across all systems.
3Measurement precision
If detailed transaction information is transmitted across the network, then data accuracy is maintained, but network cost increases
Solution Approach 1:
The patent segments transaction information into identifiers and values, transmitting only the identifier segment across the network. This segmentation maintains data accuracy through precise key reference while minimizing network cost by eliminating transmission of redundant value data.
Solution Approach 2:
The patent inverts the conventional approach by not transmitting the actual data values but instead transmitting references (keys) to the data. This inversion maintains data accuracy through reliable key identification while dramatically reducing network cost by minimizing data transmission volume.
Data Source
AI summary
Provided are methods for reducing the size of a communication between applications in a network. Methods may include receiving, at a computer processor running on a central server, a plurality of values and a plurality of keys from application A, each value paired with a respective key, and storing the values and keys on the central server. A first communication may be transmitted from application A to application B. A second communication may be transmitted from application B to application C, where applications A, B and C are running on the network. Each communication may contain one or more keys and are smaller than if they had contained corresponding values for the keys registered to application A. The computer processor may provide to applications B and C the values to the keys in the first and second communication, respectively, for example, when rendering data to a user interface.