Intelligent Telephony Module Distributed Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional VoIP systems rely heavily on server involvement for feature and user interface logic, leading to network glitches, bandwidth consumption, and latency issues, which affect the performance and scalability of telephony systems.
Innovation Solution
Implementing an intelligent telephony module with determination and communication modules across endpoints, switches, and servers to distribute feature and user interface logic, allowing entities to perform requested features and UI tasks independently, reducing dependence on central servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server actively involves in every step of execution of feature logic and UI logic on the phone, then the system can maintain centralized control and consistent feature execution, but network glitches are more likely to cause service interruptions and latency increases
Solution Approach 1:
The patent segments the telephony system into three distinct components with distributed logic: endpoints (phones) that execute local feature logic and UI logic, switches that handle call routing and basic features, and servers that provide centralized management and complex features. This segmentation allows each component to operate independently to the extent possible, reducing network dependency and latency while maintaining reliability through distributed execution of telephony functions
Solution Approach 2:
The patent implements preliminary action by pre-loading feature logic and UI logic onto endpoints and switches before execution is needed. The endpoint and switch determination modules are pre-configured with the capability to autonomously determine which entity should perform specific features, eliminating the need for real-time server consultation for basic decisions and reducing latency
2Reliability
If the server actively involves in every step of execution of application features, then centralized control is maintained, but bandwidth between server and switch is consumed limiting the number of phones that can be managed
Solution Approach 1:
The patent segments telephony logic into distributed components: endpoint feature logic modules, switch feature logic modules, and server feature logic modules. Each segment handles specific features locally, eliminating the need for constant server communication and reducing bandwidth consumption. This allows the system to manage a larger number of phones without proportionally increasing server bandwidth requirements
Solution Approach 2:
The patent implements self-service by enabling endpoints and switches to autonomously execute features without requiring server involvement for every operation. The determination modules at each level independently decide which entity should perform specific features, allowing the system to scale to more devices without proportionally increasing server bandwidth consumption
3Productivity
If feature logic and UI logic are distributed across multiple entities, then network sensitivity to glitches is reduced and bandwidth is conserved, but system complexity increases
Solution Approach 1:
The patent implements universality by designing determination modules and feature logic modules that can operate at multiple levels (endpoint, switch, server) with similar functionality. Each entity type has the capability to independently determine and execute features, creating a universal architecture where any entity can potentially handle any feature type. This multi-functionality reduces the need for complex point-to-point control logic while distributing intelligence throughout the system
Data Source
AI summary
A system and a method are disclosed for reducing interaction between a server and an endpoint while executing features on an endpoint. The endpoint, and not the application server, includes part or all of the implementation of UI logic and feature logic. The endpoint therefore does not have to rely on server's instructions for executing a feature. The endpoint also includes an endpoint determination module for determining the parts of the UI logic and feature logic implemented on the endpoint and the parts implemented on a switch or a server.