Unified Data Model for Access Management Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional access management systems require laborious and time-consuming processes to modify and update their persistent data structures when new components are added or removed, as they need to be implemented across multiple layers, leading to downtime and inefficiencies.
Innovation Solution
A unified data model using an Entity-Attribute-Value (EAV) model allows for dynamic modeling, management, and customization of metadata, enabling entities to be stored in a unified storage with hierarchical multi-part names, which supports zero downtime additions and updates of components and attributes without structural changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional entity relationship model is used to store persistent layer data, then data structure can be organized in tables with constraints, but when new components are added or removed, laborious and time-consuming modifications are required across multiple layers including persistent layer and business logic layer
Solution Approach 1:
The patent implements a dynamic metadata-driven data model where the persistent layer schema is not fixed but can be dynamically modified through metadata definitions. When new components are added, the system dynamically creates corresponding data structures without requiring manual modifications to persistent layer code or business logic layer code, thus resolving the contradiction between adaptability and time consumption.
Solution Approach 2:
The patent introduces a metadata layer as an intermediary between the persistent layer and business logic layer. This metadata layer acts as a mediator that automatically translates component definitions into corresponding data structures, eliminating the need for direct modifications across multiple layers and significantly reducing the time required to adapt to new components.
2Adaptability or versatility
If traditional entity relationship model is used, then data can be stored in structured tables, but structural changes from presentation layer to persistent layer are required when components are added or removed
Solution Approach 1:
The patent extracts the data structure definition from the rigid multi-layer structural framework and relocates it to a flexible metadata layer. This separation allows components to be added or removed without triggering structural changes across presentation, application, and persistent layers, thus reducing complexity while maintaining flexibility.
Solution Approach 2:
The patent creates a universal metadata-driven framework that handles all component types (new additions, removals, modifications) through a single mechanism. This universal approach eliminates the need for separate structural change processes for different layers, simplifying the system while enhancing flexibility in component management.
3Adaptability or versatility
If new components are added to access management system, then system functionality is enhanced, but product version release and implementation across layers are required causing downtime
Solution Approach 1:
The patent enables preliminary definition of new components through metadata configurations before they are actually deployed. The metadata-driven framework pre-establishes the data structures and relationships needed for new components, allowing seamless integration without requiring system downtime for structural modifications during deployment.
Solution Approach 2:
The system implements self-service automation where the metadata layer automatically generates and configures all necessary data structures, constraints, and business logic mappings when new components are added. This self-configuration capability eliminates the need for manual implementation across layers and avoids downtime associated with traditional deployment processes.
Data Source
AI summary
Techniques are provided for creating a unified data model for entities in components of an access management system. A method can include identifying an entity of a component, identifying a first attribute metadata for the entity, creating a data type for the first attribute metadata of the entity, defining the entity in accordance with the created data type, and storing the defined entity in a unified storage.