Centralized Server Scalability via Endpoint Feature Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized server architectures in telecommunications systems face scalability issues due to increased network traffic and resource utilization, particularly with SIP-related events, leading to degraded call processing capacity and increased complexity as more SIP-enabled endpoints and endpoint types are added, making it difficult to develop new features efficiently.

Innovation Solution

The method reallocates some feature functionality from the centralized server to client endpoints, designating a super-peer and designated endpoints within a private domain to handle specific telecommunications features, allowing limited direct access to the server and redirecting subscriptions to these endpoints based on feature type, endpoint capabilities, and resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized server architecture is used to handle all telecommunications features, then ease of operation and feature management are improved, but server scalability and call processing capacity deteriorate due to increased network traffic and SIP event handling load

Engineering Contradiction:
Improvefeature managementVSAvoidcall processing capacity
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent segments the centralized server architecture by introducing private domains that handle specific telecommunications features locally. Each private domain is associated with a user and contains endpoints that can handle features without requiring centralized server intervention for every SIP event. This segmentation reduces the load on the centralized server while maintaining ease of operation through domain-based organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by allowing different parts of the system (private domains) to handle features locally based on their capabilities and the nature of the feature. Endpoints within a private domain can handle features locally without involving the centralized server, while the server retains control over features requiring high reliability. This local handling reduces network traffic and server load while maintaining appropriate service quality.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If more SIP-enabled endpoints and endpoint types are added to increase system versatility, then adaptability is improved, but server complexity and development effort increase exponentially

Engineering Contradiction:
Improveendpoint compatibilityVSAvoidserver complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments endpoint management by organizing endpoints into private domains based on user associations and feature handling capabilities. This segmentation allows the system to accommodate diverse endpoint types within organized domains, reducing the complexity burden on the centralized server. The server only needs to manage domain-level information rather than individual endpoint configurations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces private domains as intermediary layers between the centralized server and individual endpoints. These domains act as mediators that handle feature-specific operations locally, reducing the complexity of direct server-endpoint interactions. The server communicates with domains rather than individual endpoints, simplifying the overall system architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If feature handling is distributed to private domains to reduce server load, then server scalability is improved, but network traffic patterns and message routing complexity increase

Engineering Contradiction:
Improveserver scalabilityVSAvoidmessage routing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent uses private domains as intermediary entities that simplify message routing. Instead of the server directly managing communication between all endpoints, messages are routed through domain intermediaries. This reduces the routing complexity at the server level while enabling distributed feature handling that improves scalability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates equipotentiality by establishing standardized interfaces and protocols for communication between domains and the centralized server. This standardization ensures that all domains operate at the same structural level with consistent messaging patterns, reducing routing complexity despite the distributed architecture.

Inventive Principle:
Principle #12Equipotentiality

Data Source

PatentEP1909467B1Centralized controller for distributed handling of telecommunications features
Publication Date: 2015.10.21 AVAYA TECHNOLOGY LLC
  • EP1909467B1 patent drawingFigure 1
  • EP1909467B1 patent drawingFigure 2
  • EP1909467B1 patent drawingFigure 3

AI summary

A method is disclosed that enables an improvement in the scalability of a centralized server by reallocating to the client endpoints some, but not all, of the feature functionality of the server. Each logical user in the system is represented by his own private domain of endpoint entities, from which an endpoint is selected to serve as a super peer to represent the user to the centralized server. Furthermore, a designated endpoint is selected, also from the private domain of devices; to handle some of the telecommunications features that the server otherwise would have handled. Each endpoint in the private domain is permitted to have limited direct access to the server, typically for the purposes of registering and subscribing to features, in addition to and in contrast with the indirect access through the super peer. During the subscribing process, the server redirects a subscribing endpoint to the designated endpoint that is handling the feature.