Multi-tenant Management Service Federated Dial Plan
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for deploying multi-tenant services face challenges in managing overlapping dial plans and providing unified communications across multiple tenants without the need for dedicated hardware, especially in hybrid cloud environments where resource objects share the same dialable numbers.
Innovation Solution
A multi-tenant management service (MTMS) generates federated dial plans with unique system identifiers and dialable numbers for each tenant, allowing for unified communication and controlled access to services, while avoiding the need for dedicated hardware by using a hybrid cloud architecture that integrates on-premises and off-site resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If resource objects from different tenants share the same dialable number in a multi-tenant service, then hardware costs are reduced and resource utilization is improved, but confusion arises in routing calls to the correct tenant
Solution Approach 1:
The patent segments the dial plan into hierarchical levels: global dialable numbers are shared across tenants, while tenant-specific identifiers (such as site codes or extension ranges) are appended to route calls to the correct tenant. This segmentation allows shared resources to coexist with organized routing without requiring dedicated hardware per tenant.
2Device complexity
If a unified dial plan is used across all tenants, then system simplicity is improved, but the ability to maintain unique dialing schemes for each tenant is lost
Solution Approach 1:
The patent implements local quality by allowing each tenant to define their own dialing rules and number formats within their specific context (e.g., different extension ranges, site codes, or routing preferences), while these local variations are integrated into the global dial plan through the federated structure. Each tenant's dial plan has unique local characteristics preserved within the unified whole.
3Reliability
If dedicated hardware is provided for each tenant, then call routing accuracy is improved, but cost and resource utilization deteriorate
Solution Approach 1:
The patent introduces a federated dial plan as an intermediary layer between the shared resource pool and individual tenants. This intermediary structure uses software-based routing rules that incorporate tenant identifiers (such as system IDs or site codes) to accurately route calls to the correct tenant without requiring dedicated physical hardware for each tenant.
4Adaptability or versatility
If overlapping dial plans are allowed across tenants, then resource sharing is improved, but difficulty in managing and troubleshooting dial plans increases
Solution Approach 1:
The patent resolves overlapping dial plans by adding another dimension to the routing logic: tenant identifiers (such as system IDs, site codes, or organizational units) are appended to or combined with dialable numbers. This transforms the routing from a single-dimensional number-matching problem into a multi-dimensional lookup that considers both the dialable number and the tenant context, enabling resource sharing while maintaining manageable complexity.
Data Source
AI summary
A multi-tenant management service (MTMS) can be configured to receive a plurality of requests for a multi-tenant service from a plurality of tenants. A given and another of the plurality of tenants can have a resource object (RO) with the same dialable number (DN) assigned thereto. The MTMS can also be configured to generate a federated dial plan for each of the plurality of tenants. Each federated dial plan can include a system identifier (ID) and a corresponding DN for each RO associated a respective tenant. The MTMS can further be configured to provide a federated DN corresponding to the multi-tenant service to each of the plurality of tenants.