Selective Data Encryption for Network Privacy Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network security protocols, such as HTTPS, are computationally expensive and incur high latency due to the need for frequent key negotiations and encryption of all data, making them inefficient for blocking deep packet inspection (DPI) and protecting user data from unauthorized extraction.
Innovation Solution
Implementing a remote and local anti-extraction module that uses privacy keys to selectively encrypt only sensitive data transmitted over a network, reducing the need for frequent key exchanges and encrypting all data, thereby minimizing computational overhead and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If HTTPS is used to secure network communication, then data privacy is protected, but computational cost and latency increase significantly
Solution Approach 1:
The patent segments the data transmission into two categories: sensitive data that requires encryption and non-sensitive data that can be transmitted in plaintext. This selective encryption approach divides the data stream and applies different security measures to different segments, reducing the overall computational overhead compared to encrypting all data as HTTPS does
Solution Approach 2:
The patent applies encryption only to specific portions (local segments) of the data that are deemed sensitive, rather than applying uniform encryption to all data. This local quality approach ensures that computational resources are concentrated only where needed for privacy protection, leaving other data transmission paths open and fast
2Reliability
If SSL key negotiation is performed for each HTTPS connection, then secure communication is established, but computational overhead increases
Solution Approach 1:
The patent performs key negotiation and setup in advance, before actual data transmission begins. By establishing the encryption keys and security parameters beforehand, the system avoids repeated key negotiation overhead during subsequent data exchanges, reducing computational energy consumption while maintaining secure communication
Solution Approach 2:
The patent maintains continuous secure communication by keeping encryption keys established across multiple data transmissions. Rather than renegotiating keys for each connection, the system sustains the cryptographic session continuously, eliminating the repetitive computational cost of frequent key negotiations
3Reliability
If all data is encrypted in HTTPS, then comprehensive privacy protection is achieved, but processing speed decreases
Solution Approach 1:
The patent segments data into sensitive and non-sensitive categories, applying encryption only to the sensitive portions. This segmentation allows non-sensitive data to be processed and transmitted at full speed without encryption overhead, thereby maintaining higher overall processing productivity while still protecting privacy where necessary
Solution Approach 2:
The patent applies partial encryption to only the necessary sensitive data fields rather than encrypting all data. This partial action approach provides sufficient privacy protection for critical information while avoiding the performance penalty of encrypting unnecessary data, thus preserving processing speed
Data Source
AI summary
A privacy key is provided over a network. An information page is provided over the network. A submission of data that is to be transmitted over the network in response to the information page is detected. A subset of the data is to be encrypted using the privacy key is determined. The privacy key is used to encrypt the subset of the data.