Notification Server Event Filtering and Broadcasting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large infrastructure systems face inefficiencies in monitoring and notifying users of events due to the complexity and resource-intensive nature of ad-hoc monitoring across diverse sources, leading to a need for improved notification methods that conserve processing resources.

Innovation Solution

A notification server generates a unique identifier for communication using a predefined social networking service, determines if an event satisfies a notification rule, and broadcasts the event to users with access to the identifier, leveraging a centralized control system that integrates with various communication protocols and social networking services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If ad-hoc monitoring is implemented across diverse event sources, then event detection capability is improved, but processing resource consumption increases

Engineering Contradiction:
Improveevent detection capabilityVSAvoidprocessing resource consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent introduces a notification server as an intermediary component that sits between diverse event sources and users. This server receives events from multiple sources, applies centralized filtering rules, and generates notifications only when rules are satisfied. This intermediary approach improves event detection capability while conserving processing resources by avoiding ad-hoc monitoring at every endpoint, instead centralizing the monitoring function in one optimized location.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If centralized notification control is implemented, then notification efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvenotification efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The notification server is designed as a universal system that handles multiple event sources, various filtering rules, and different notification delivery mechanisms through a single platform. By creating a multi-functional centralized system that can manage diverse events and users through standardized interfaces, the patent achieves high notification efficiency without proportionally increasing complexity, as the same core infrastructure serves multiple purposes.

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

3Reliability

If event filtering rules are applied at each monitoring point, then notification relevance is improved, but device complexity increases

Engineering Contradiction:
Improvenotification relevanceVSAvoidmonitoring point complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complex event filtering and rule evaluation logic from individual monitoring points and consolidates it into the centralized notification server. Each monitoring point becomes simpler, only needing to forward raw events to the server. The server then applies all filtering rules centrally and determines notification relevance, thereby improving notification relevance while reducing the complexity burden from distributed monitoring points.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11177972B2Event notification
Publication Date: 2021.11.16 KYNDRYL INC
  • US11177972B2 patent drawing
  • US11177972B2 patent drawing
  • US11177972B2 patent drawing

AI summary

A method, and associated computer system and computer program product, for notifying users of events. A notification server that includes a computer receives a notification rule. The notification server generates, for the received notification rule, a unique identifier for communication. The notification server receives an indication of an IT event that occurred in a source computing device. The received notification identifies a software hug associated with the IT event. The notification rule is a condition of a severity level of the software bug exceeding a predefined threshold. The notification server determines whether the received indication satisfies the notification rule. In response to determining that the received indication satisfies the notification rule, the notification server marks the received event, using the unique identifier and broadcasting the marked event for receipt by those users who have access to said unique identifier.