Policy Enforcer for Consolidated User Information Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for managing user information across multiple data repositories face challenges in ensuring data consistency and synchronization, as changes in one system may not align with others, leading to inconsistencies and requiring manual reconciliation, which complicates updates and integration across different applications and services.

Innovation Solution

A policy-enforcing mechanism that intercepts and processes data manipulation requests, analyzes the request type, and selects appropriate policies to ensure data consistency by delegating processing to the relevant data systems or handling it centrally, using a unified interface for data aggregation and identity management across multiple repositories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is stored in multiple separate data repositories for different services, then each system can independently manage its data, but data consistency and synchronization across systems deteriorates

Engineering Contradiction:
Improveindependent data managementVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a profile manager as an intermediary component that mediates between multiple data repositories and applications. The profile manager intercepts data manipulation requests, determines the appropriate repository, and coordinates updates across systems. This mediator ensures data consistency is maintained while allowing each repository to independently manage its data according to its own schemas and access controls.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a common data model and single repository are used, then data consistency is improved, but system complexity and the difficulty of implementation increases

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

Solution Approach 1:

The patent segments the data management architecture into distinct components: multiple independent data repositories, a profile manager, and policy enforcers. Each repository maintains its own data model and schema, avoiding the need for a unified data model. The profile manager handles coordination logic, separating concerns and reducing overall system complexity while maintaining data consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The profile manager serves as an intermediary that abstracts the complexity of multi-repository coordination from applications. It handles repository selection, data manipulation coordination, and policy enforcement, allowing applications to work with simplified data access interfaces while the intermediary manages the complex interactions between multiple repositories.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If manual reconciliation processes are used to update data across systems, then data consistency can be maintained, but time consumption and operational complexity increases

Engineering Contradiction:
Improvedata consistencyVSAvoidreconciliation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements automated self-service mechanisms where the profile manager automatically intercepts data manipulation requests, determines the appropriate data repositories, and executes updates across systems without manual intervention. Policy enforcers automatically evaluate conditions and trigger necessary updates, eliminating the need for manual reconciliation processes and significantly reducing time consumption.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where the profile manager monitors data manipulation requests and automatically triggers reconciliation processes when inconsistencies are detected. Policy enforcers continuously evaluate data states and initiate updates as needed, creating a self-correcting system that maintains data consistency without manual intervention.

Inventive Principle:
Principle #23Feedback

4Reliability

If centralized control is implemented to manage data updates, then data consistency is improved, but system flexibility and autonomy of individual systems decreases

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem autonomy
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by allowing each data repository to maintain its own data model, schema, and access control policies while the profile manager provides centralized coordination. Each repository can be independently configured and managed according to its specific requirements, while the profile manager ensures overall data consistency across the distributed system.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The profile manager serves multiple functions: it acts as a centralized coordinator for data consistency, a policy enforcer for security and access control, a repository selector for routing requests, and an updater for maintaining data synchronization. This multi-functional component provides centralized control without requiring a single-point architecture, preserving system flexibility.

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

Data Source

PatentUS8533773B2Methods and systems for implementing service level consolidated user information management
Publication Date: 2013.09.10 ORACLE INT CORP
  • US8533773B2 patent drawing
  • US8533773B2 patent drawing
  • US8533773B2 patent drawing

AI summary

Embodiments of the invention provide methods and systems for implementing service level consolidated user information management. According to one embodiment, a method comprises intercepting, at a policy enforcer, a manipulation request of data. The method may further include analyzing the request to determine which data the manipulation request is associated with and, based on that analysis, selecting a policy from a plurality of policies. Furthermore, the method may execute the selected policy. The policy may be configured to direct the policy enforcer to allow the manipulation request to pass through to the associated destination data system to process the request, delegate processing of the manipulation request to at least one of a plurality of data systems, or process the manipulation request by the policy enforcer.