IVR Framework Using Data Structure for Code Segments
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing IVR applications on vendor-provided IDE tools can limit flexibility and require substantial modifications when switching vendors, leading to inefficiencies in resource utilization and integration with other systems.
Innovation Solution
An IVR application platform that orchestrates the delivery of IVR services by querying a data structure for code segments, allowing for dynamic execution and separation from vendor-specific constraints, enabling seamless updates and integrations without modifying application code on each server device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IVR applications are developed on vendor-provided IDE tools, then the applications can be created and executed, but the flexibility is limited and substantial modifications are required when switching vendors
Solution Approach 1:
The patent segments the IVR application into two distinct parts: vendor-neutral logic code stored in a data structure and vendor-specific execution environment. This separation allows the logic code to be independent of any specific IVR vendor's IDE or execution environment, enabling portability across different vendors without requiring modifications to the application logic.
Solution Approach 2:
The patent introduces an intermediary layer consisting of a data structure that stores logic code in a vendor-neutral format. This intermediary decouples the application logic from vendor-specific execution environments, allowing the same logic code to be executed across different IVR vendors' platforms without requiring substantial modifications.
2Productivity
If IVR applications are developed using vendor-specific IDE tools, then the applications can be executed on that vendor's system, but resource utilization becomes inefficient and integration with other systems is limited
Solution Approach 1:
The patent creates a universal data structure format for storing IVR logic code that can be executed across multiple IVR vendors' platforms. This universal format enables the same application logic to serve multiple functions across different systems, improving resource utilization by eliminating redundant vendor-specific development and enhancing integration capabilities with various systems.
3Reliability
If logic code is stored locally on each server device, then the application can be executed, but processing resources are consumed for duplicate storage and updates require modification of code on each server
Solution Approach 1:
The patent merges the logic code storage into a centralized data structure that can be accessed by multiple server devices. Instead of each server storing duplicate copies of the IVR application logic, the centralized data structure allows all servers to share the same logic code, reducing processing resources consumed for storage and enabling centralized updates without modifying code on each individual server.
Data Source
AI summary
A device may receive, from a server device, a request for an initial action associated with an interactive voice response (IVR) service. The request may include a service identifier. The device may obtain a set of code segments for an IVR application that supports the IVR service by using the service identifier to search a data structure. The set of code segments may be associated with logic of the IVR application. The device may provide instructions associated with an initial code segment to the server device to cause the server device to execute the initial action via a communication with a user device. The device may selectively provide, to the server device, instructions associated with another code segment to cause the server device to execute a next action via the communication with the user device.