Secure Event Notification Broker for Topic Subscription Delivery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing distributed computing systems face high computing resource costs, delays, and lack of security in transmitting and registering computer server event notifications, particularly in systems like financial services and electronic payment transactions, due to reliance on file transfers and polling APIs, which are prone to changes in underlying APIs.

Innovation Solution

A system and method for secure transmission of computer server event notifications involving a notification server that receives subscription requests, registers them in a database, determines subscribed partners, and transmits event notifications securely over a network, using a service gateway for additional security and abstraction, with features like message authentication codes and JSON Web Tokens.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If file transfers or polling APIs are used for event notifications, then existing systems can transmit notifications, but computing resource costs increase and delays occur

Engineering Contradiction:
Improvenotification transmissionVSAvoidcomputing resource costs
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent introduces a message broker as an intermediary component that sits between event producers and consumers. The broker receives event notifications from producers, stores them in a message queue, and delivers them to subscribed consumers. This intermediary architecture eliminates the need for direct polling between systems, reducing computing resource consumption while maintaining reliable notification transmission.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If polling APIs are used for event notifications, then existing systems can receive notifications, but delays occur in notification delivery

Engineering Contradiction:
Improvenotification receptionVSAvoidnotification delivery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The message broker continuously monitors the message queue and immediately pushes notifications to subscribed consumers as soon as events occur. This continuous operation eliminates the idle waiting periods inherent in polling mechanisms, where systems must repeatedly query for updates. The broker maintains an always-on connection with consumers, ensuring notifications are delivered in real-time without delay.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If traditional notification mechanisms are used, then existing systems can transmit events, but security is insufficient

Engineering Contradiction:
Improveevent transmissionVSAvoidsecurity vulnerabilities
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The message broker acts as a secure intermediary that implements authentication and authorization mechanisms. It validates subscriber credentials, manages access rights, and encrypts messages in transit. This centralized security approach protects against unauthorized access and data breaches while maintaining reliable event transmission between systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If file transfers are used for notifications, then existing systems can communicate events, but the system lacks scalability

Engineering Contradiction:
Improveevent communicationVSAvoidsystem scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The message broker provides a universal notification service that can handle multiple event types, support various subscription models, and accommodate different consumer requirements through configuration rather than code changes. This multi-functional platform enables new systems to be added to the notification network without modifying existing components, providing horizontal scalability and adaptability to changing business requirements.

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

Data Source

PatentUS20250350525A1Systems and methods for subscribing topics and registering computer server event notifications
Publication Date: 2025.11.13 WORLDPAY LLC
  • US20250350525A1 patent drawing
  • US20250350525A1 patent drawing
  • US20250350525A1 patent drawing

AI summary

Systems and methods are disclosed for secure transmission of computer server event notifications, including receiving a topic subscription request from a partner, registering the partner topic subscription request, obtaining a new computer server event to report, determining a subscribed partner subscribed to computer server events of a same type as the new computer server event, transmitting an event notification to the subscribed partner, and registering the event notification.