Electronic Map Version Mirroring for Rollback and Historical Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current electronic map production process lacks efficient methods for maintaining and updating electronic maps, leading to issues such as the direct replacement of old versions with new versions, which can cause disruptions and increased development costs when issues arise with the new versions.
Innovation Solution
A method involving a backend development device that generates and publishes mirror data at different development stages to a virtual cloud server cluster, with unique identification information for each data set, allowing for the coexistence of new and old versions, facilitating rollback and historical data management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If new-version electronic map data directly replaces old-version electronic map data, then the electronic map can be updated efficiently, but it becomes difficult to rollback or retrieve historical data when issues arise
Solution Approach 1:
The patent segments the electronic map data into multiple versions by creating mirror data at different development stages (development, testing, pre-release, and production environments). Each version is stored separately with unique identification information, allowing efficient updates while maintaining the ability to rollback to any previous version when needed.
2Reliability
If multiple versions of electronic map data are maintained, then rollback capability and historical data management are improved, but system complexity and storage requirements increase
Solution Approach 1:
The patent creates a universal mirror data management system that handles multiple development stages and environments through a unified approach. The same mirror data generation and publishing process serves development, testing, pre-release, and production environments, reducing overall system complexity while maintaining comprehensive version management capabilities.
3Ease of operation
If mirror data is generated and published at each development stage, then version control and problem resolution are improved, but development time and processing overhead increase
Solution Approach 1:
The patent applies preliminary action by generating and publishing mirror data at each development stage (development, testing, pre-release) before the final production deployment. This allows potential issues to be detected and resolved earlier in the development process, reducing overall development time despite the additional processing steps, as problems are caught before reaching production.
Data Source
AI summary
A method for operating and maintaining an electronic map, a method for using electronic map data and a service system, which relate to a technical field of computer. The method includes: by the backend development device, acquiring target electronic map data to be updated, sequentially generating mirror data at different development stages, sequentially publishing the mirror data to the virtual cloud server cluster; wherein mirror data at the last development stage in the mirror data constitute new-version electronic map data, other mirror data in the mirror data except for the mirror data at the last development stage constitute old-version electronic map processing data, and then, by the virtual cloud server cluster, generating identification information corresponding to each of the mirror data, wherein the identification information is used to distinguish different mirror data.