IVRObject Framework for SIP Signaling Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current SIP-based IVR technologies, such as M*ML and VoiceXML, are complex, lack portability, and complicate development due to asynchronous signaling and split application logic, making it difficult to stabilize and test IVR applications effectively.

Innovation Solution

The IVRObject framework allows a SIP application server to control SIP signaling for IVR operations, providing a simple API, portability across different media servers, and easy testing by centralizing development and using a built-in callback mechanism, thus minimizing signaling traffic and simplifying the development process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If M*ML is used to provide IVR capabilities, then IVR functionality can be achieved, but the system complexity increases and portability is reduced

Engineering Contradiction:
ImproveportabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the IVRObject framework) between the SIP application server and the media server. This framework handles the complexity of M*ML parsing and formatting automatically, allowing the application server to interact with the media server through a simplified interface without directly dealing with M*ML complexities, thus reducing system complexity while maintaining adaptability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The IVRObject framework is designed to work with multiple media server types (Snowshore, Convedia, etc.) through a unified interface. The framework provides universal support for IVR capabilities across different media server platforms, eliminating the need for separate implementations for each server type and thereby improving portability

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

2Ease of manufacture

If M*ML is used for IVR capabilities, then IVR functionality is provided, but development difficulty increases due to parsing and formatting requirements

Engineering Contradiction:
Improveease of developmentVSAvoiddevelopment complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The IVRObject framework acts as an intermediary that automatically handles the parsing and formatting of M*ML messages. Developers interact with the framework through high-level methods rather than directly manipulating M*ML, significantly reducing development complexity while maintaining full IVR functionality

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The framework performs self-service by automatically parsing incoming M*ML messages and formatting outgoing responses. This eliminates the need for developers to manually implement parsing and formatting logic, making the system easier to develop while maintaining complexity management

Inventive Principle:
Principle #25Self-service

3Productivity

If INFO messages are used to support IVR capabilities, then IVR functionality is achieved, but the number of messages and signaling complexity increases

Engineering Contradiction:
Improvesignaling efficiencyVSAvoidsignaling complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges multiple IVR operations (playing prompts, collecting DTMF, recording audio) into a single SIP INFO message containing an M*ML script. This consolidation reduces the total number of back-and-forth messages between the application server and media server, improving signaling efficiency while maintaining functionality

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The framework prepares and formats the complete M*ML script in advance within the INFO message, including all necessary IVR commands for multiple operations. This preliminary preparation eliminates the need for sequential messaging to coordinate multiple operations, reducing signaling complexity

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If asynchronous SIP messages are used, then flexibility is achieved, but stability becomes difficult to ensure due to message crossing and combination challenges

Engineering Contradiction:
ImproveflexibilityVSAvoidstability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The framework implements feedback mechanisms that track the state of asynchronous SIP messages and ensure proper ordering. By monitoring message flow and providing feedback about message processing status, the system maintains stability despite the asynchronous nature of SIP communications, allowing flexible message handling while preventing message crossing issues

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9003049B1Interactive voice response object
Publication Date: 2015.04.07 ARLINGTON TECHNOLOGIES LLC
  • US9003049B1 patent drawing
  • US9003049B1 patent drawing
  • US9003049B1 patent drawing

AI summary

Methods, devices, and systems for creating and using an interactive voice object are provided. An alternative way of providing Interactive Voice Response (IVR) capabilities to a Session Initiation Protocol (SIP) endpoint is described. More specifically, the present invention allows the SIP endpoint to have its SIP signaling controlled by an application running in a SIP application server.