Data Migration System for Blockchain State Reproduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain platforms do not allow for efficient data migration between different environments, leading to challenges in reproducing the old state in the new environment, especially when transactions are linked to external systems, resulting in incomplete or inaccurate data transfer.
Innovation Solution
A data migration method and system that utilizes a management server and distributed ledger nodes to extract and transmit transaction information, allowing for the reproduction of the old state by specifying transaction IDs and executing transactions based on extracted data, ensuring consistent data transfer between old and new PaaS environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data migration is performed using client-side capability to read and write distributed ledger data, then migration can be achieved, but the old environment cannot be reproduced when transactions are linked to external systems, resulting in incomplete data transfer
Solution Approach 1:
The patent introduces a management server as an intermediary component that coordinates between the old and new blockchain platforms. The management server retrieves transaction information from the old platform, extracts necessary data, and inputs it into the new platform, ensuring complete and accurate data migration while handling external system linkages that client-side approaches cannot manage.
Solution Approach 2:
The migration process is divided into distinct functional segments: transaction information retrieval from the old platform, data extraction and processing by the management server, and data input and verification in the new platform. This segmentation allows each component to specialize in its function, ensuring data integrity while achieving complete migration including external system dependencies.
2Reliability
If blockchain platforms restrict information movement to maintain security, then platform security is preserved, but migration between platforms becomes extremely limited and cannot meet user needs
Solution Approach 1:
The management server acts as a trusted intermediary that operates outside the restrictive platform environments. It retrieves transaction information from the old platform through authorized access, processes the data, and inputs it into the new platform, thereby enabling migration while respecting the security constraints of both platforms.
Solution Approach 2:
Instead of moving actual platform-locked data, the system creates accurate copies of transaction information and state data through the management server. These copies are then used to reconstruct the old environment state in the new platform, achieving migration without violating platform security restrictions.
3Productivity
If client-side reading and writing is used for data migration, then some data transfer is possible, but external system linkages cause execution results to differ, preventing accurate reproduction of the old state
Solution Approach 1:
The management server performs preliminary retrieval of complete transaction information from the old platform before migration begins. This includes capturing all relevant data, external system linkages, and execution contexts in advance, ensuring that when data is reproduced in the new platform, it accurately reflects the old state despite differences in external system access.
Solution Approach 2:
The management server serves as a mediator that captures the complete execution context including external system dependencies from the old platform. By processing and preserving this context information, it enables accurate reproduction of execution results in the new platform, eliminating discrepancies that arise from direct client-side access to external systems.
Data Source
AI summary
A data migration system 10 includes: a management server 20 configured to obtain transaction information from a distributed ledger at a data migration source, and transmit a migration transaction to a distributed ledger node at a data migration destination, the migration transaction specifying a transaction ID indicated by the transaction information obtained; and the distributed ledger node 100 configured to receive the migration transaction, obtain transaction information in the distributed ledger at the data migration source based on the transaction ID, extract data on a predetermined processing result from the transaction information obtained, execute a transaction using the extracted data as an argument, and transmit a result of the executed transaction to a transaction distribution node 300 at the data migration destination.