Distributed VoIP Backup Server Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

VoIP systems face challenges in achieving high availability due to the need for redundant capacity at each site, which is costly and inefficient, as redundancies are typically designed on a site-by-site basis without considering differences in configuration requirements across sites.

Innovation Solution

A distributed VoIP system architecture where each server is designated as a backup to another server, allowing them to provide applications and data to switches during normal operation and seamlessly take over in case of failures, reducing the need for dedicated backup servers and distributing the burden across different backup servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If redundant capacity is added at each site to achieve required levels of availability, then system availability is improved, but system cost increases

Engineering Contradiction:
Improvesystem availabilityVSAvoidredundant capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements a universal backup server architecture where any server in the system can function as a backup to any other server. Instead of having dedicated backup servers at each site, the system allows servers to perform multiple functions - serving their primary site and potentially backing up other sites. This multi-functionality approach maintains high availability while reducing the total quantity of redundant components needed.

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

Solution Approach 2:

The patent introduces a hierarchical backup architecture that operates across multiple levels or dimensions. Rather than simple one-to-one backup at each site, the system creates a layered redundancy model where backup servers can serve multiple primary servers across different sites. This dimensional approach to redundancy allows fewer physical components to provide equivalent or superior protection.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If dedicated backup servers are deployed at each site, then system availability is improved, but device complexity increases

Engineering Contradiction:
Improvesystem availabilityVSAvoidredundant infrastructure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system eliminates the need for dedicated backup servers by making all servers potentially backup-capable. Each server maintains its primary function while also being eligible to serve as a backup to other servers. This universal approach reduces infrastructure complexity by removing the specialized backup server component while maintaining availability through shared redundancy.

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

Solution Approach 2:

The patent merges the backup function with the primary server function into a single unified server role. Rather than having separate dedicated backup servers, the backup capability is integrated into the general server population. This consolidation reduces the number of distinct device types and simplifies the overall system architecture while preserving reliability.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8982902B1Backup server architecture in a VoIP system
Publication Date: 2015.03.17 SHORETEL INC
  • US8982902B1 patent drawing
  • US8982902B1 patent drawing
  • US8982902B1 patent drawing

AI summary

A method for providing telephony services in a distributed VoIP system includes determining that a first switch is unable to communicate with a first server, where the first switch is configured to provide telephony services to a first plurality of communication devices, and the first server is configured to provide applications and data associated with the first plurality of communication devices to the first switch. The method also includes sending an adoption request from the first switch to a second server, where the second server is configured to provide applications and data associated with a second plurality of communication devices to a second switch and also configured to provide the applications and data associated with the first plurality of communication devices to the first switch. The method also includes receiving at the first switch the applications and data associated with the first plurality of communication devices from the second server.