Multi-Protocol Eventing Layer for Database Notification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing open-source databases like Cassandra lack native support for eventing and multi-protocol communication, leading to inefficiencies such as processor resource wastage and limited scalability, especially in managing network elements across various protocols like SIP and HTTP.

Innovation Solution

A multi-protocol eventing layer is developed to front-end databases like Cassandra, enabling proactive notification of changes to interested consumers through SIP, HTTP, or other protocols, independent of network size and protocol, using an API-level mechanism like Avaya Aura User Store's User Information Service.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If polling is used to monitor network elements, then network status can be checked, but processor resources are wasted and only limited elements can be monitored

Engineering Contradiction:
Improvenetwork status monitoringVSAvoidprocessor resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Instead of the server actively polling network elements for status (traditional approach), the patent inverts the approach by having network elements push event notifications to the server when status changes occur. This eliminates continuous polling and associated processor waste while maintaining reliable monitoring coverage.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

Network elements autonomously generate and send event notifications when their status changes, without requiring external polling requests. This self-service mechanism allows unlimited elements to be monitored simultaneously without increasing server processor consumption, as the server only processes actual events rather than continuously querying all elements.

Inventive Principle:
Principle #25Self-service

2Productivity

If open source databases like Cassandra are used, then scalability and speed are improved, but native eventing support and multi-protocol support are lacking

Engineering Contradiction:
Improvedatabase speed and scalabilityVSAvoidmulti-protocol support
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an eventing layer as an intermediary component between the Cassandra database and multiple communication protocols (SIP, HTTP, LDAP). This layer translates database events into protocol-specific notifications, enabling the high-performance Cassandra database to support multiple protocols without requiring native integration for each protocol, thus maintaining both speed/scalability and adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If web service eventing is used for notification delivery, then message delivery efficiency is improved, but IP multicast capability, message forwarding, and end-to-end security are limited

Engineering Contradiction:
Improvemessage delivery efficiencyVSAvoidnetwork communication capability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal notification system that combines the efficiency of web service eventing with the capabilities of SIP protocol. The system can deliver notifications efficiently while also supporting IP multicast, message forwarding through proxies, end-to-end security, and other advanced network communication features by leveraging SIP's proven capabilities alongside web service mechanisms.

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

Data Source

PatentUS9787749B2Method, apparatus, and system for providing and using multi-protocol eventing
Publication Date: 2017.10.10 AVAYA INC
  • US9787749B2 patent drawing
  • US9787749B2 patent drawing
  • US9787749B2 patent drawing

AI summary

Methods and systems for providing an elegant and efficient multi-protocol eventing layer are disclosed. The multi-protocol eventing layer includes a converged container capable of handling multiple types of protocols to manage events while using an open source database. Accordingly, the multi-protocol eventing layer efficiently provides real-time or near real-time eventing to a plurality of devices for scalability and performance enhancement.