Field Address Number and New Row Key for Data Tree Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data management systems face challenges in accurately identifying and modifying fields in a data tree structure, particularly when the data is rendered on a webpage, leading to potential data corruption if the location information is not updated correctly.
Innovation Solution
The use of a Field Address Number (FAN) and a New Row Key (NRK) to identify and modify fields in a data structure, allowing for efficient location and updating of fields both on the client device and remote server, even after the webpage has been rendered and before the fields are added to the data tree structure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire location information string is transmitted when a field is updated, then the data can be updated on the remote device, but the data transmission size increases and efficiency decreases
Solution Approach 1:
The patent extracts only the necessary field identifier information (FAN and NRK) from the complete location information string and transmits only this extracted data. This allows the system to maintain reliable field identification while significantly reducing the amount of data transmitted during updates, directly resolving the contradiction between data update reliability and transmission efficiency.
Solution Approach 2:
The location information is segmented into two independent components: Field Address Number (FAN) for identifying the field within a row, and New Row Key (NRK) for identifying the row. This segmentation allows each component to be transmitted independently and efficiently, reducing overall transmission size while maintaining the ability to precisely identify any field in the data tree.
2Stability of the object's composition
If the location string is not updated when sorting and reloading data, then the data structure remains stable, but data corruption occurs
Solution Approach 1:
The system implements feedback mechanisms where the webpage or server detects changes in data tree structure (such as sorting or reordering operations) and automatically updates the FAN/NRK mappings. This ensures that even when the data tree structure changes, the location identifiers remain valid and synchronized, preventing data corruption while maintaining structural flexibility.
Solution Approach 2:
The patent introduces dynamic adaptation where the FAN/NRK identification system can adapt to changes in data tree structure. When sorting or reordering occurs, the system dynamically updates the mapping between location strings and FAN/NRK pairs, allowing the data tree to be flexible and reconfigurable without compromising the integrity of field identification.
3Difficulty of detecting and measuring
If fields are identified using location information strings, then fields can be located in the data tree, but the identification process becomes complex and error-prone
Solution Approach 1:
The patent replaces the complex string-based mechanical identification system with a simpler numerical FAN/NRK system. Instead of parsing and processing lengthy location information strings that are prone to errors, the system uses straightforward integer pairs that are easier to generate, transmit, and process, significantly reducing complexity while improving identification accuracy.
Solution Approach 2:
The system changes the parameters used for field identification from complex string formats to simplified numerical representations (FAN and NRK). This parameter transformation makes the identification process less error-prone and more efficient, as numbers are easier to handle computationally than strings, directly reducing the difficulty of field detection and measurement.
Data Source
AI summary
Methods, apparatuses, and computer program products are provided for an address system to identify a field and/or a row in a data structure. A method may include receiving a request to modify a field of data, wherein the field of data is identified by a received field key. A method may also include determining whether the field of data was rendered for display. A method may also include modifying the field in a tree structure in an instance in which the field of data was rendered for display, wherein the received field key is configured locate an address object that is related to the field. A method may also include modifying the field of data in a tree structure in an instance in which the field of data was not rendered for display by locating the received field key in a field key lookup map, wherein the field key lookup map is configured to locate the address object.