Mobile Terminal Interface Cache Verification for Confidentiality

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile terminals often fail to timely remove cached data, leading to the disclosure of important user information, especially when the built-in browser is repeatedly accessed, causing confidentiality issues.

Innovation Solution

A method and device that detect user input to access an application, determine if confidential data is cached, and if so, compare the user's identifying information to the cached data. If the data does not belong to the user, a protective user interface is displayed while retrieving the user's data from a remote server, replacing the cached interface to prevent unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If cached data is used to improve access speed, then response time is reduced, but user information confidentiality is compromised

Engineering Contradiction:
Improveresponse timeVSAvoidinformation leakage
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary verification mechanism that checks cached data against current user identity before display. This mediator layer validates whether cached confidential data belongs to the current user, preventing information leakage while maintaining the speed benefit of cache usage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically changes the verification parameter from simple cache hit/miss to user-identity-matched cache validation. By adding user identification comparison as a parameter, the system ensures that cached data is only displayed when it belongs to the current user, resolving the confidentiality issue.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If built-in browser is repeatedly accessed for convenience, then ease of operation is improved, but cached confidential data from previous users may be exposed

Engineering Contradiction:
Improveconvenience of repeated accessVSAvoiddata confidentiality
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies preliminary action by verifying user identity against cached data before allowing access. This pre-check ensures that even when the browser is repeatedly accessed for convenience, confidential data from previous users cannot be exposed because the verification happens in advance.

Inventive Principle:
Principle #10Preliminary action

3Speed

If cache memory is used to store application data, then access speed is improved, but unauthorized users may access previous user's confidential information

Engineering Contradiction:
Improvedata access speedVSAvoidunauthorized access
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The verification mechanism acts as an intermediary between the cache memory and the display function. It intercepts cached data retrieval operations and validates user authority, preventing unauthorized access while maintaining the speed advantage of cache storage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs self-service verification by automatically comparing user identity with cached data ownership. This self-validation mechanism ensures that only authorized users can access their own cached confidential data without requiring external intervention.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9621637B2Method, device and mobile terminal for controlling interface display
Publication Date: 2017.04.11 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US9621637B2 patent drawing
  • US9621637B2 patent drawing
  • US9621637B2 patent drawing

AI summary

A method of displaying user interfaces on an electronic device comprising: detecting a first user input to access an application by a first user, including identifying information of the first user. In response to detecting the first user input, determining whether there is confidential data associated with the application cached in memory. In accordance with a determination that there is confidential data associated with the application cached in memory, comparing identifying information of the first user to the cached confidential data. In accordance with a determination that there is cached confidential data associated with the application but not belonging to the first user, displaying a first user interface corresponding to the application while retrieving confidential data belonging to the first user from a remote server, and replacing the first user interface with a display of the application and confidential data belonging to the first user retrieved from the remote server.