Wrapper Profiles for Data Store Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Identity Systems face challenges in managing controlled access to common data store information among multiple entities, particularly during resource provisioning processes, where simultaneous access attempts can lead to stale data or conflicts, necessitating a framework for coordinated access control.

Innovation Solution

The implementation of wrapper objects in the data store to manage access, including attributes that indicate locking status, allowing entities to determine access permissions before accessing information, and utilizing a provisioning bridge server to ensure exclusive access during modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple applications access the same data store information simultaneously, then access efficiency is improved, but data consistency deteriorates due to stale data and conflicts

Engineering Contradiction:
Improveaccess efficiencyVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces a wrapper object as an intermediary layer between multiple applications and the data store. The wrapper includes a locking status attribute that mediates access requests, allowing the system to maintain both high access efficiency and data consistency by coordinating simultaneous access attempts through this intermediary structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If access control restrictions are implemented during resource provisioning, then data consistency is improved, but access efficiency deteriorates due to reduced simultaneous access

Engineering Contradiction:
Improvedata consistencyVSAvoidaccess efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The locking status attribute in the wrapper object is dynamic, changing states based on the provisioning process. During resource provisioning, the wrapper can transition to a locked state to ensure data consistency, then transition back to an unlocked state to restore access efficiency. This dynamic behavior allows the system to adapt access control levels to current operational needs.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If wrapper objects with locking status attributes are introduced, then controlled access capability is improved, but system complexity increases

Engineering Contradiction:
Improvecontrolled access capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the access control functionality into a separate wrapper object that is distinct from the actual data store structures. This segmentation allows the locking status attribute to be managed independently, improving controlled access capability while containing system complexity within a modular, manageable component rather than distributing complexity throughout the entire system.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8375113B2Employing wrapper profiles
Publication Date: 2013.02.12 ORACLE INT CORP
  • US8375113B2 patent drawing
  • US8375113B2 patent drawing
  • US8375113B2 patent drawing

AI summary

Technology is disclosed for controlling access to data store information among multiple entities. A corresponding wrapper is created for information that may be subject to simultaneous access attempts. The wrapper includes an attribute that identifies the accessibility of the information—indicating whether the information is locked from further access, shareable among multiple entities, or not restricted at all. Before accessing information in the data store, an entity looks at the wrapper associated with the information to determine the type of access allowed, if any. An Identity, Access, or integrated Identity/Access System may maintain the wrappers as objects in the data store, with each wrapper object controlling another object containing information. Wrappers can be utilized when multiple provisioning applications are employed to provision resources. Each user and their corresponding resources are represented as objects with corresponding wrappers. Each provisioning application employs the wrappers to ensure that it has exclusive ownership of selected user and resource objects when provisioning resources to the selected user.