Cloud Services Layer Dynamic Object Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multi-tenant, multi-service cloud environments are inflexible, as they require pre-defined object types and roles, limiting user customization and dynamic service registration, and do not allow for unique service-related object types beyond those predefined by the system.
Innovation Solution
The cloud services layer enables dynamic registration of unique service-related object types, roles, policies, and permissions through web service interfaces, allowing users to customize access and management of services, with entities like identity, security, service registration, and entitlement entities managing these objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If pre-defined object types and roles are used in cloud environments, then system management is simplified, but user customization capability is limited
Solution Approach 1:
The system transitions from static pre-defined object types to dynamic object type registration. Services can register custom object types, roles, and permissions at runtime through the service registration entity, allowing the system structure to adapt dynamically to user needs while maintaining manageable complexity through automated entity relationships.
Solution Approach 2:
The cloud environment enables self-service customization where services and users can register their own object types, roles, and permissions without requiring system administrator intervention for each customization. The identity entity and service registration entity automatically manage the registration and integration of custom objects into the existing framework.
2Adaptability or versatility
If fixed service structures are implemented, then system stability is improved, but dynamic service registration is limited
Solution Approach 1:
The system implements dynamic service registration through the service registration entity, which allows services to register custom object types, roles, and permissions at runtime. This dynamic capability is built upon a stable foundation of predefined entity relationships and security policies managed by the identity and security entities, ensuring system stability while enabling adaptability.
Solution Approach 2:
The service registration entity acts as an intermediary between new services and the existing cloud environment framework. It mediates the registration process by validating and integrating custom object types, roles, and permissions into the established system structure, maintaining stability while enabling dynamic service addition.
3Adaptability or versatility
If pre-defined roles and permissions are used, then security management is simplified, but access customization is limited
Solution Approach 1:
Services and users can self-register custom roles and permissions through the service registration entity without requiring manual security configuration. The security entity automatically integrates these custom roles and permissions into the existing security framework, maintaining simplified security management while enabling detailed access customization.
Solution Approach 2:
The security entity provides universal security management that handles both pre-defined and custom roles and permissions through a unified framework. This multi-functional approach allows the same security infrastructure to manage standard roles while accommodating service-specific custom roles and permissions, avoiding the need for separate security management systems.
Data Source
AI summary
A method including receiving a service registration request to register a service with a multi-tenant, multi-service cloud network from a user; registering object types that pertain to the service, wherein the object types include at least one service object type that is not an object type offered by the cloud network to the user; and registering objects based on the object types, wherein the objects include at least one object associated with the at least one service object type.