Service Name Modification for Mobile Data Privacy Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile terminal systems inadequately protect user privacy as they do not continuously monitor or inform users about the usage of their private data by applications, leading to potential data leakage.
Innovation Solution
A method and device that modify the service name of applications requesting private data, prompting users for permission each time the data is accessed, ensuring transparency and control over data usage by using a modified service name distinct from the original, thereby preventing unauthorized access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the system grants data access permission during application installation, then the application can be installed and used, but the user cannot be informed about subsequent data usage which leads to privacy leakage
Solution Approach 1:
The system performs preliminary actions by modifying service names before the application can access private data. When an application requests private data, the system intercepts the service name, modifies it to a jump service name, and stores the mapping relationship. This preliminary modification ensures that every subsequent data access request can be tracked and prompted to the user, solving the problem of unauthorized data usage after installation.
Solution Approach 2:
The patent introduces an intermediary mechanism between the application and the private data. The service name modification system acts as this intermediary - when an application requests data using its original service name, the system intercepts this request, modifies the service name to a jump service name, and processes the request through this intermediate layer. This intermediary enables the system to monitor and control all data access operations, providing continuous user notification and consent opportunities.
2Reliability
If the system continuously monitors and prompts users about data usage, then user privacy is better protected, but the system complexity increases due to service name modification and management
Solution Approach 1:
The system creates a copy mechanism by generating jump service names that are derivatives of the original service names. Instead of fundamentally changing the service identification system, the patent creates a parallel copying layer where each original service name has a corresponding modified jump service name. This copying approach maintains the original service structure while adding monitoring capabilities, reducing the complexity increase compared to a complete system redesign.
Solution Approach 2:
The system changes parameters by modifying service names through adding prefixes or suffixes rather than creating entirely new identification systems. The jump service name is derived from the original service name by parameter modification (e.g., adding a specific prefix). This parameter-based transformation maintains compatibility with existing service naming conventions while enabling the monitoring functionality, thereby limiting the increase in system complexity.
3Productivity
If the system uses original service names for data access, then service identification is simple and direct, but unauthorized applications can access data without user knowledge
Solution Approach 1:
The system performs preliminary modification of service names before data access occurs. When an application requests private data, the service name is预先 modified to a jump service_name, and the mapping relationship is stored in advance. This preliminary action ensures that the original simple service identification mechanism remains in place for direct access, while the modified jump service names provide an additional layer of security control for preventing unauthorized access.
Data Source
AI summary
The present invention discloses a data calling method and device, wherein the data calling method comprises: receiving a service request to use a first service, wherein the first service needs to use private data of a mobile terminal, and the service request comprises a service name of the first service; according to the service name, sending to a user of the mobile terminal a prompt about whether to permit the first service to use the private data; according to the user's input, determining that the requesting first service is permitted to use the private data; determining a jump service name corresponding to the service name, and calling the first service according to the jump service name, wherein the jump service name is a service name resulting from modification to the service name of the first service in a service listing maintained by the system whenever the mobile terminal is activated, and the jump service name is different from service names of other services except for the first service in the service listing. Safety of the private data of the mobile terminal is improved through the present application.