Secure Data Synchronization via Layered Encryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data synchronization methods in cloud storage services often compromise data integrity due to unauthorized access, as data is transmitted in unencrypted form, leading to resource wastage in managing security breaches.

Innovation Solution

A method involving a user device that encrypts files using a file symmetric key and a first encryption algorithm, then re-encrypts them with a synchronization key and metadata using different encryption algorithms, ensuring secure transmission and storage by maintaining encrypted data and keys, even if the cloud service provider's infrastructure is compromised.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If data is transmitted in unencrypted form for synchronization, then transmission speed and ease of operation are improved, but data security and integrity deteriorate due to unauthorized access

Engineering Contradiction:
Improvedata transmissionVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary encryption of data before transmission occurs. The client device encrypts files using a synchronization key and different encryption algorithms before uploading to the cloud, ensuring data is protected before the transmission process begins, thus resolving the security concern while maintaining operational ease

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary encryption layer using synchronization keys and multiple encryption algorithms that act as a mediator between the data and the transmission channel. This intermediary mechanism protects data during transmission without requiring changes to the underlying transmission infrastructure

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple encryption algorithms and keys are used for secure synchronization, then data security is improved, but computational complexity and processing time increase

Engineering Contradiction:
Improvedata securityVSAvoidencryption process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The encryption process is segmented into distinct layers: file-level encryption using symmetric keys for local storage, and synchronization-level encryption using different algorithms for cloud transmission. This segmentation allows each layer to use optimized algorithms appropriate to its specific security requirements, managing overall complexity through modular design

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically changes encryption parameters based on the operation type - using symmetric encryption for local file operations and asymmetric or different symmetric encryption for synchronization operations. This parameter adaptation optimizes the balance between security and computational efficiency for different operational contexts

Inventive Principle:
Principle #35Parameter changes

3Reliability

If data is encrypted before cloud storage synchronization, then data integrity is improved against unauthorized access, but processing time and computational resources increase

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Encryption is performed as a preliminary action before data leaves the client device. By encrypting data locally before transmission, the system ensures data integrity is established upfront, and the encryption process is optimized to minimize the time penalty through efficient algorithm selection and hardware acceleration

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system rushes through the encryption process using highly optimized algorithms and parallel processing capabilities, minimizing the time data spends in the encryption pipeline. Once encrypted, the data is rapidly transmitted without further processing delays, compensating for the initial encryption time investment

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentUS20240070294A1Secure synchronization of data
Publication Date: 2024.02.29 UAB 360 IT
  • US20240070294A1 patent drawing
  • US20240070294A1 patent drawing
  • US20240070294A1 patent drawing

AI summary

A method including receiving, by a user device, an encrypted version of a file in association with an encrypted version of metadata that is associated with the file; decrypting, by a user device, an encrypted version of a file symmetric key based at least in part on utilizing a master key to determine the file symmetric key; decrypting, by the user device, the encrypted version of the metadata based at least in part on utilizing the file symmetric key to determine a synchronization key included in the metadata; and decrypting, by the user device, the encrypted version of the file based at least in part on utilizing the synchronization key to determine an unencrypted version of the file is disclosed. Various other aspects are contemplated.