Multi-tenant Microservice Provisioning via Entitlement Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Provisioning multi-tenant, microservice architecture-based integration services in a cloud computing environment is complex and inefficient, requiring multiple subscriptions and manual checks of user entitlements, leading to duplicate coding and maintenance overhead.

Innovation Solution

A provisioning application platform processor receives user requests, accesses user identifiers and entitlement values, and transmits these values to a platform resource manager to automatically create and manage microservices for integration services, streamlining the provisioning process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual provisioning processes are used for multi-tenant microservices, then flexibility in service configuration is improved, but provisioning time and operational complexity increase

Engineering Contradiction:
Improveservice configuration flexibilityVSAvoidprovisioning time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining service templates with configurable parameters and pre-establishing entitlement frameworks. When a provisioning request arrives, the system only needs to instantiate and configure specific parameters rather than creating services from scratch, significantly reducing provisioning time while maintaining configuration flexibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service provisioning where users can autonomously provision services by selecting from predefined templates and configuring parameters through self-service interfaces. The system automatically handles service creation, resource allocation, and entitlement assignment without manual intervention, reducing both provisioning time and operational complexity.

Inventive Principle:
Principle #25Self-service

2Productivity

If automated provisioning is implemented, then provisioning speed is improved, but system complexity increases

Engineering Contradiction:
Improveprovisioning speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The provisioning system is segmented into independent, loosely-coupled microservices including service catalog management, entitlement verification, resource provisioning, and billing components. Each segment handles a specific aspect of provisioning independently, which reduces overall system complexity while enabling high-speed automated operations through parallel processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements universal provisioning templates and entitlement frameworks that can be reused across multiple service types and tenants. This multi-functionality reduces the need for custom provisioning logic for each service, thereby reducing system complexity while maintaining high provisioning speed through standardized automated processes.

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

3Adaptability or versatility

If multiple subscriptions are required for different service levels, then service differentiation is improved, but provisioning overhead increases

Engineering Contradiction:
Improveservice level differentiationVSAvoidprovisioning overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system merges multiple service level configurations into unified service templates with parameterized entitlement levels. Instead of requiring separate subscriptions for different service levels, users select a single service template and configure the desired entitlement level through parameters, reducing provisioning overhead while maintaining service differentiation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system uses parameter changes to differentiate service levels within unified templates. By varying parameters such as resource quotas, performance SLAs, and feature access levels, the system can provide differentiated service levels without requiring separate provisioning processes, thereby reducing overhead while maintaining adaptability.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11509743B2Provisioning multi-tenant, microservice architecture-based integration service in a cloud computing environment
Publication Date: 2022.11.22 SAP SE
  • US11509743B2 patent drawing
  • US11509743B2 patent drawing
  • US11509743B2 patent drawing

AI summary

According to some embodiments, methods and systems may include a data storage device that contains user identifiers and associated entitlement values for a plurality of tenants of a cloud computing environment. A provisioning application platform processor may receive a user request for an integration service and access the data storage device. The provisioning application platform processor may then transmit at least one entitlement value to a platform resource manager processor to facilitate creation of a plurality of microservices resulting in implementation of the integration service for the user.