Entity Customization in Multi-Tenant Hierarchical Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods fail to provide a standardized way for entity customization in hierarchical service provider multi-tenant systems, lacking the ability to identify and distinguish participants' hierarchy levels and the scope of entity applicability, leading to incomplete entity customization.
Innovation Solution
A method and system that uniquely identifies participants in a hierarchical service provider multi-tenant system, enabling entity-level customization by establishing a root provider-tenant hierarchy, allowing identification of customizable entities, and aggregating customizations across the hierarchy, while defining non-customizable attributes and their scope.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate instances of software are used for individual customization needs, then entity customization capability is improved, but system complexity and resource consumption increase
Solution Approach 1:
The patent segments entity customization into two distinct categories: customizable entities and non-customizable entities. This segmentation allows the system to provide targeted customization capabilities where needed while maintaining a standardized core, thereby improving adaptability without proportionally increasing system complexity. The segmentation is implemented through separate data structures and processing paths for each entity type.
Solution Approach 2:
The system dynamically determines whether to apply customization based on entity type and participant hierarchy level. Rather than a static all-or-nothing customization approach, the system adaptively applies customization rules depending on the specific entity being accessed and the participant's authorized level, optimizing the balance between adaptability and system complexity.
2Adaptability or versatility
If entity customization is allowed at all hierarchy levels, then adaptability is improved, but security and data integrity deteriorate
Solution Approach 1:
The patent implements local quality by associating specific customization permissions with specific hierarchy levels. Different participants at different levels of the hierarchy (root service provider, sub-providers, tenants) have different authorized scopes for customization. This ensures that customization is permitted only where appropriate and authorized, maintaining data integrity while providing necessary adaptability at each level.
Solution Approach 2:
The system performs preliminary validation of participant authorization and entity customizability before allowing any customization operation. By checking hierarchy level, authorized scope, and entity type in advance, the system prevents unauthorized or inappropriate customizations that could compromise data integrity, while still allowing legitimate customizations to proceed.
3Device complexity
If a standardized software instance is used across all tenants, then system simplicity is improved, but customization capability deteriorates
Solution Approach 1:
The patent segments entities into customizable and non-customizable categories, allowing a standardized instance to be maintained for non-customizable entities while enabling selective customization for specific entity types. This segmentation preserves system simplicity for the majority of entities while providing customization capability where required.
Solution Approach 2:
The system implements a universal customization framework that can handle both standardized and customized entities through a single software instance. The framework provides multi-functionality by supporting both standard operation and customization operation within the same system, eliminating the need for separate software instances while maintaining simplicity.
4Measurement precision
If hierarchy identification is implemented in multi-tenant system, then entity scope definition is improved, but processing overhead increases
Solution Approach 1:
The patent performs preliminary identification and caching of participant hierarchy information during system initialization or login. By determining and storing the hierarchy level and authorized scope in advance, the system avoids repeated hierarchy resolution during customization operations, thereby reducing processing overhead while maintaining precise entity scope definition.
Solution Approach 2:
The system creates and stores copies of hierarchy level and authorization scope information in easily accessible data structures. Instead of repeatedly querying or calculating hierarchy relationships during entity access, the system uses pre-computed copies of this information, significantly reducing processing time while maintaining accurate scope definition.
Data Source
AI summary
A method and system for entity customization in a hierarchical service provider, multi-tenant system is disclosed. The method disclosed uniquely identifies plurality of participants in the hierarchical system as a root service provider, sub-provider or a tenant. Further, the method enables identification of entities as customizable or non-customizable and authorizes the participants to customize the respective entity. The method enables to define scope of the entity that indicates whether the entity is applicable to a tenant or a provider or a sub-provider or a combination of these. The method enables identification of non-customizable or mandatory attributes within an entity. Further, the method aggregates customizations through the hierarchy and applies them for a specific tenant or a provider.