Cross-Server Data Management with Encrypted ID Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of electronic device usage history data and advertisement usage history data in a single server poses a risk of private information infringement, as user and device information is managed together.
Innovation Solution
The data is managed by different servers using distinct IDs, with encryption keys to protect privacy, and a conversion server converts these IDs to ensure secure data sharing without infringing on privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If electronic device usage history data and advertisement usage history data are managed by one server, then data integration and service efficiency are improved, but private information security deteriorates
Solution Approach 1:
The patent divides the management of usage history data into separate segments: electronic device usage history data is managed by a first server with a first ID, while advertisement usage history data is managed by a second server with a second ID. This segmentation prevents a single server from accessing both types of sensitive data simultaneously, thereby reducing private information infringement risk while maintaining service efficiency through dedicated management.
Solution Approach 2:
The patent introduces a conversion server as an intermediary that converts the first ID to a second ID and vice versa. This intermediary enables secure data sharing between servers without direct access to sensitive information, allowing personalized services to be provided while maintaining privacy protection through encrypted ID conversion.
2Object-affected harmful factors
If data is managed by different servers with distinct IDs, then private information security is improved, but system complexity increases
Solution Approach 1:
The conversion server acts as a centralized intermediary that handles all ID conversion operations between the first server and second server. This single intermediary point simplifies the overall system architecture compared to implementing distributed conversion capabilities across multiple servers, reducing system complexity while maintaining security through centralized ID management.
Solution Approach 2:
The conversion server performs multiple functions: it converts first IDs to second IDs, converts second IDs to first IDs, and manages the mapping relationships between different ID systems. This multi-functionality consolidates what would otherwise require separate mechanisms in each server, reducing overall system complexity.
Data Source
Figure 1~2
Figure 3~4
Figure 5A
AI summary
Provided is a data management method of a server, including receiving, from a first server, first data, in which a first identification (ID) associated with a device and a first encryption identification (ID) that encrypts an ID associated with an advertisement are mapped and second data, in which a second ID associated with the advertisement and a second encryption ID that encrypts an ID associated with the device are mapped; converting a second encryption ID associated with an electronic device, received from a second server, to the second ID based on the second data, and transmitting the converted second ID and third data to an advertisement service server; and converting a first encryption ID associated with the electronic device, received from a third server, to the first ID based on the first data, and transmitting the converted first ID and fourth data to a general service server.