User Information Management via Authorization Masking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies face challenges in managing user health information securely and efficiently, particularly in allowing third-party applications to access specific data types while maintaining user privacy and control over their personal data.

Innovation Solution

A system and method that enables secure storage and management of user health information, allowing third-party applications to request access while masking user authorization decisions, ensuring that sensitive information is only shared when explicitly authorized and providing an empty result for unauthorized data types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If third-party applications are allowed to access user health information, then data sharing and application functionality are improved, but user privacy and data security are worsened

Engineering Contradiction:
Improvedata sharing capabilityVSAvoiduser privacy risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary authorization system between users and third-party applications. This intermediary manages authorization requests, stores authorization decisions, and controls data access based on user permissions. The intermediary layer enables data sharing while protecting user privacy by mediating all access requests through a controlled interface that respects user authorization decisions.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If detailed authorization tracking is implemented, then user control over data access is improved, but system complexity is worsened

Engineering Contradiction:
Improveuser control capabilityVSAvoidauthorization management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the authorization management into distinct functional components: authorization request handling, authorization decision storage, and data access control. By dividing the authorization tracking system into separate modules, the patent maintains detailed user control capability while reducing overall system complexity through modular architecture. Each component has a specific responsibility, making the system more manageable and easier to implement.

Inventive Principle:
Principle #1Segmentation

3Loss of information

If authorization decisions are disclosed to third-party applications, then transparency is improved, but data security is worsened

Engineering Contradiction:
Improveauthorization transparencyVSAvoiddata security
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent extracts the authorization decision information from the data access control flow. Instead of disclosing authorization decisions to third-party applications, the system separates this information into a dedicated authorization store. The data access control mechanism queries the authorization store without sharing decision-making information with requesting applications, thereby maintaining data security while preserving transparency through the authorization request and response mechanisms.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP4235682A1Managing user information
Publication Date: 2023.08.30 APPLE INC
  • EP4235682A1 patent drawingFigure 1
  • EP4235682A1 patent drawingFigure 2
  • EP4235682A1 patent drawingFigure 3

AI summary

Systems, methods, and computer-readable medium are provided for managing user information. For example, data of the user may be stored in a memory. A request for a user to authorize access of at least a portion of the data may be provided. The authorization may be for an application to access the portion of the data. In some examples, a response to the request may be received, and an indication that the request was provided to the user may be provided without indicating whether the user denied the request.