Service Profiles for Data Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users lack transparency and control over how their data is accessed by third-party applications, as they cannot easily manage or monitor which data is shared and with which applications.

Innovation Solution

The creation and management of service profiles that allow users to define categories of data and associate them with specific applications, providing a mechanism to control access and transparency by allowing users to select which applications can access specific data categories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users share data from their account with third-party applications, then users can benefit from data sharing (e.g., shopping promotions), but users lose transparency and control over how their data is accessed and used

Engineering Contradiction:
Improvedata sharing capabilityVSAvoidtransparency of data access
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism where the first-party application notifies the user when data is accessed by the third-party application. This notification system provides real-time feedback to the user about data access events, restoring transparency while maintaining the data sharing capability. The user receives information about what data is being accessed, by whom, and when, enabling informed control over data usage.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If users share data from their account with third-party applications, then users can benefit from data sharing, but users cannot easily manage or monitor which data is shared and with which applications

Engineering Contradiction:
Improvedata sharing capabilityVSAvoiddata access management
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a service profile as an intermediary layer between the user's data and third-party applications. This service profile acts as a mediator that manages data access permissions, allowing users to control which applications can access which data categories. The intermediary simplifies data management by providing a centralized interface rather than requiring users to manage individual application permissions directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If comprehensive data access control is implemented, then user privacy and data security are enhanced, but system complexity increases due to service profile management

Engineering Contradiction:
Improvedata securityVSAvoidservice profile management system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The service profile is designed as a universal mechanism that can be applied across multiple first-party applications and third-party applications. Rather than implementing separate access control systems for each application pair, the patent creates a multi-functional service profile that works universally throughout the ecosystem. This reduces overall system complexity by providing a single, reusable access control framework.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9330278B1Service profiles for associating data services with applications
Publication Date: 2016.05.03 GOOGLE LLC
  • US9330278B1 patent drawing
  • US9330278B1 patent drawing
  • US9330278B1 patent drawing

AI summary

Service profiles for associating data services with applications are described, including receiving a first input from a user identifying a first service to include in a service profile; receiving a second input from the user identifying a second service to include in the service profile, the second service is associated with the user; receiving a third input from the user defining one or more boundaries of one or more of the first service and the second service; receiving a fourth input from the user indicating association of the service profile with one of the at least one application; storing the service profile with information of the first service, the second service, and the association with the one of the at least one application; and based on the service profile, determining whether to grant access to the first service and second service by the at least one application.