Orchestration Engine Decouples Telephony From Business Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of business processes with telephony functions is complex and costly, with the cost of feature development increasing exponentially as the number of features or protocols grows, making it difficult to customize and add applications to modern telephony systems.
Innovation Solution
An orchestration engine is interposed between a business process engine and an enterprise telecommunications network to decouple atomic telephony functions from business logic, allowing for a single, easy-to-develop location for new protocols, features, or algorithm changes, and enabling additional adapters to be deployed without altering existing software.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If business processes are directly integrated with telephony functions, then the system can execute workflows that combine business logic and telephony operations, but the development cost increases exponentially as the number of features or protocols grows
Solution Approach 1:
The patent introduces an orchestration engine as an intermediary layer between the business process engine and the telephony infrastructure. This mediator handles the complexity of protocol translation and coordination, allowing business processes to interact with telephony functions without directly managing the underlying complexity. The orchestration engine absorbs the exponential complexity growth, while business processes remain simple and maintainable.
Solution Approach 2:
The system is divided into distinct modular components: the business process engine that handles workflow logic, the orchestration engine that manages telephony coordination, and the telephony infrastructure that provides communication capabilities. This segmentation allows each component to be developed and maintained independently, preventing the exponential complexity from propagating across the entire system.
2Adaptability or versatility
If multiple telephony protocols and features are supported, then the system becomes more versatile and can handle diverse communication requirements, but the time to develop features increases
Solution Approach 1:
The orchestration engine is designed as a universal platform that can handle multiple telephony protocols and features through a single unified interface. Rather than building separate integration logic for each protocol, the orchestration engine provides multi-functional capabilities that work across different telephony systems, significantly reducing feature development time while maintaining broad protocol support.
3Adaptability or versatility
If customized behavior is added to the telephony system to meet customer requirements, then the system becomes more adaptable to specific business needs, but the complexity of managing multiple communication protocols and APIs increases
Solution Approach 1:
The orchestration engine provides dynamic configuration capabilities that allow customized behavior to be added without permanently altering the system structure. Business processes can be dynamically adjusted to meet specific customer requirements through configurable workflows and parameters, while the underlying telephony integration remains standardized and manageable.
Data Source
AI summary
A technique is disclosed for interfacing business processes with telephony functions. Particularly, an orchestration engine is interposed between a business process engine that executes business processes and an enterprise telecommunications network that executes telephony functions. Acting as an intermediary between the business process engine and the telecommunications network, the orchestration engine decouples the atomic telephony functions that are required for a business application from the business logic that is used in features that comprise one or more business processes. Thus, a new protocol state, feature, or algorithm change is isolated to a single and easy-to-develop location in software.