Database Conditional Access via Purpose Objects

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data access systems lack efficient mechanisms for ensuring conditional access based on processing purposes and user consent, particularly in compliance with emerging privacy regulations.

Innovation Solution

A method and system for conditional data access in a database system, where data purpose objects are stored to indicate subsets of attributes and their processing purposes, and access is granted only if the requested view's attributes are a subset of those indicated in the data purpose object, with associated entities having authorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conditional access control mechanisms are implemented to ensure compliance with privacy regulations, then data protection and consent management are improved, but system complexity and processing overhead increase

Engineering Contradiction:
Improvedata protectionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments data access control into distinct components: data purpose objects define processing purposes and attribute subsets, database views represent specific attribute combinations, and authorization records link entities to purposes. This segmentation allows independent management of each component, simplifying the overall complex system while ensuring comprehensive data protection through modular verification.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-defining data purpose objects that specify processing purposes and associated attribute subsets before data access requests occur. These purpose objects are stored and registered in advance, enabling the system to quickly verify compliance by comparing requested views against pre-established purposes, reducing real-time processing complexity while maintaining strict data protection.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If strict conditional access verification is performed to ensure view attributes are subsets of authorized attributes, then compliance with user consent is improved, but data access processing time increases

Engineering Contradiction:
Improveconsent complianceVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by pre-establishing data purpose objects that explicitly define which attribute subsets are authorized for each processing purpose. When a data access request arrives, the system only needs to verify if the requested view attributes match a pre-defined purpose, rather than performing complex analysis of user consent for each attribute. This dramatically reduces verification time while ensuring strict compliance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating database views that represent specific attribute subsets authorized for particular purposes. Instead of analyzing individual attributes during access requests, the system copies authorized attribute combinations into pre-defined view structures, allowing rapid verification by simple pattern matching against stored purpose objects, thus minimizing processing time while maintaining compliance.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12265636B2Conditional access to data
Publication Date: 2025.04.01 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12265636B2 patent drawing
  • US12265636B2 patent drawing
  • US12265636B2 patent drawing

AI summary

A database system can comprise records, each record including a set of attributes. The database system can further comprise database views, each database view representing a subset of the set of attributes. Data purpose objects indicating a subset of attributes of the set of attributes and a processing purpose can be stored. Each processing purpose can be associated with one or more entities that authorized access to the subset of attributes of the processing purpose. A request for data for a specific processing purpose and a selected view of the database views can be received. A data purpose object that indicates the specific processing purpose can be retrieved. The subset of attributes represented by the selected view can be compared with the subset of the attributes indicated in the retrieved data purpose object. Values of the subset of attributes of the selected view can be provided.