Signaling Protocol Stack Sharing in Telephony Virtualization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current virtualization techniques in telephony applications cannot seamlessly switch between operating systems, preventing seamless control over telecommunications sessions across different system software images, as they are isolated and lack access to necessary call state information.

Innovation Solution

Implementing a method that shares the signaling protocol stack across multiple system software images using a message bus and translator, allowing telephony applications on different images to synchronize and maintain session state without modifying each other, enabling seamless switching between operating systems during calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If hardware virtualization is used to run multiple operating systems concurrently, then users can access both productivity and entertainment applications, but the operating systems become isolated and cannot share telephony session state information

Engineering Contradiction:
Improveability to run multiple operating systemsVSAvoidtelephony session state information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

A message bus is introduced as an intermediary communication channel between isolated virtualized operating systems. The message bus allows telephony applications in different OS instances to exchange session state information without breaking isolation boundaries, enabling seamless handoff while maintaining system security and stability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message bus is designed as a universal communication infrastructure that serves multiple functions: transmitting telephony session state, enabling OS switching, and maintaining application compatibility across different virtualized environments. This single component resolves multiple communication needs between isolated systems

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

2Reliability

If virtualized operating systems are isolated from each other, then system stability and security are maintained, but telephony applications cannot access call state information from other operating systems

Engineering Contradiction:
Improvesystem stabilityVSAvoidseamless switching between operating systems
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The message bus acts as a controlled intermediary that allows necessary information flow between isolated OS instances. It maintains system stability by preserving isolation boundaries while enabling telephony applications to access session state through a standardized, secure communication interface

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The communication architecture is segmented into isolated OS instances that maintain their own stability, connected through a separate message bus infrastructure. This segmentation allows each OS to remain stable and secure while the message bus handles the coordination needed for seamless telephony operation across OS boundaries

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If telephony applications are modified to share the signaling protocol stack, then seamless switching between operating systems is enabled, but application compatibility and independence are reduced

Engineering Contradiction:
Improveseamless switching between operating systemsVSAvoidapplication modification requirements
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The message bus serves as an intermediary that handles the complexity of cross-OS communication without requiring application modifications. Telephony applications can remain independent and unmodified, while the message bus translates and routes messages between different OS instances, preserving application compatibility

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message bus infrastructure provides self-service by automatically managing message routing, translation, and delivery between isolated OS instances. This eliminates the need for complex application-level modifications, as the communication infrastructure handles synchronization and state sharing autonomously

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9143597B2Method for telephony client synchronization in telephone virtualization
Publication Date: 2015.09.22 ARLINGTON TECHNOLOGIES LLC
  • US9143597B2 patent drawing
  • US9143597B2 patent drawing
  • US9143597B2 patent drawing

AI summary

A method for synchronizing telephony applications running on different system software images is provided. When a telecommunications session is conducted by a first telephony application, the first telephony application controls the state of the telecommunications session through a signaling protocol stack executing on the same system software image as the first telephony application (or on a virtualization layer). The present invention allows the sharing of the signaling protocol stack by multiple telephony applications running on different system software images.