Visual Voicemail Network Architecture Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current visual voicemail systems lack user-friendly management capabilities, as they typically organize messages sequentially rather than allowing users to manage them in a customizable order, and there is a need for a more efficient and scalable solution to handle voicemail notifications and synchronization across multiple devices.

Innovation Solution

A visual voicemail system is implemented with a network architecture that includes a device layer, a voice-mail layer, and an application layer, utilizing servers and client computing modules to provide a graphical user interface for users to manage voicemail messages in any order, with features like notification, synchronization, and audio file management, and employs load balancing and transcoding to ensure scalability and reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If visual voicemail systems organize messages sequentially, then system simplicity is maintained, but user-friendly management capability deteriorates

Engineering Contradiction:
Improveuser-friendly management capabilityVSAvoidmessage organization structure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements dynamic message ordering by allowing users to customize the sequence in which voicemail messages are displayed and managed. Instead of a fixed sequential order, the system adapts to user preferences and enables flexible reordering of messages, thereby improving ease of operation while maintaining manageable complexity through user-controlled organization.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments voicemail messages into distinct, manageable units with individual ordering control. Each message can be independently positioned and organized according to user preferences, allowing complex message sets to be broken down into manageable segments that users can control and navigate easily.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If a single server handles all voicemail notifications, then system simplicity is maintained, but scalability deteriorates

Engineering Contradiction:
ImprovescalabilityVSAvoidnetwork architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the voicemail notification system into multiple servers that handle different aspects of notification delivery. This segmentation allows the system to scale by distributing load across multiple servers, with each server managing specific portions of the notification process, thereby improving scalability while maintaining architectural clarity through functional division.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a multi-functional server architecture where servers can handle various types of notifications and serve multiple clients simultaneously. This universal design enables the system to scale by adding servers that can perform multiple functions, improving adaptability while managing complexity through standardized multi-functional components.

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

3Productivity

If voicemail synchronization is performed manually, then system simplicity is maintained, but productivity deteriorates

Engineering Contradiction:
Improvesynchronization efficiencyVSAvoidsynchronization process
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The patent implements continuous automatic synchronization between voicemail systems and client devices. Instead of manual synchronization, the system maintains continuous connection and automatically updates message lists, ensuring that users always have access to the most current voicemail information without intervention, thereby improving productivity through uninterrupted automatic operation.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The patent enables the voicemail system to automatically synchronize and update itself without requiring user action. The system self-manages the synchronization process, automatically detecting changes, updating databases, and notifying clients, thereby improving productivity by eliminating manual tasks while maintaining relatively simple operation from the user perspective.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8195130B2Visual voicemail network architecture
Publication Date: 2012.06.05 VERIZON PATENT & LICENSING INC
  • US8195130B2 patent drawing
  • US8195130B2 patent drawing
  • US8195130B2 patent drawing

AI summary

A system may include a load balancer that includes a receiver configured to receive a first notification of voicemail message information associated with a voicemail mailbox. The system may also include a group of servers and each of the group of servers may include a receiver and a transmitter. The receiver may be configured to receive the first notification of the voicemail message information from the load balancer, and the transmitter may be configured to send a second notification of the voicemail message information to a communication device associated with the voicemail mailbox, wherein the second notification causes the communication device to determine whether to request a list of voicemail messages. The load balancer may also include a processor to select a first one of the plurality of servers and a transmitter to send the first notification to the first one of the plurality of servers.