Edge Cache Deduplication for Emergency Data Destage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional centralized network architectures introduce latency due to data traveling back and forth between edge devices and the network core, which can be exacerbated during emergencies like power outages, leading to potential data loss and corruption.
Innovation Solution
Implementing edge caching with deduplication fingerprinting at the edge device level to selectively send unique data blocks to the target system, reducing unnecessary data transfer and conserving battery power during emergency destages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all data blocks in the edge cache are sent to the target system during an emergency destage, then data completeness is improved, but bandwidth usage increases and data transfer time extends
Solution Approach 1:
The system performs preliminary actions by maintaining a map of data blocks already present in the target system before the emergency destage operation. This pre-knowledge allows the edge device to selectively identify and transmit only the missing data blocks, avoiding redundant transfers and significantly reducing data transfer time while ensuring data completeness.
2Reliability
If all data blocks in the edge cache are sent to the target system during an emergency destage, then data completeness is improved, but bandwidth usage increases
Solution Approach 1:
The system performs preliminary actions by maintaining a map of data blocks already present in the target system before the emergency destage operation. This pre-knowledge allows the edge device to selectively identify and transmit only the missing data blocks, avoiding redundant transfers and significantly reducing bandwidth usage while ensuring data completeness.
3Extent of automation
If data is transferred back and forth between edge devices and network core, then centralized processing is improved, but latency increases
Solution Approach 1:
The system segments the centralized processing architecture by implementing edge caching at distributed edge devices. This segmentation allows data to be processed and stored locally at the edge, eliminating the need for continuous back-and-forth communication with the network core for read operations, thereby significantly reducing latency while maintaining centralized control for critical operations.
Solution Approach 2:
The edge cache acts as an intermediary between the edge devices and the network core. It stores frequently accessed data locally, serving as a buffer that reduces the frequency and volume of communications with the centralized core, thereby reducing latency while maintaining the benefits of centralized processing for data that must be synchronized.
Data Source
AI summary
Embodiments relate improved traffic management in edge caching. Responsive to an emergency trigger, an edge device receives a map from a target system, the edge device including a cache having a plurality of blocks, where the map is representative of content in a data volume of the target system. The edge device determines at least one block of the plurality of blocks in the cache different from the content in the data volume based on the map. The edge device sends the at least one block in the cache to the target system, responsive to the emergency trigger.


