Service Gateway Event Subscriptions for Secure Push Notifications

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 computer server event notifications, particularly in systems like financial services and electronic payment transactions, where events need to be efficiently and securely shared across disparate systems.

Innovation Solution

A system and method for secure transmission of computer server event notifications involving receiving a topic subscription request, registering it in a database, determining subscribed partners, and transmitting event notifications using a service gateway with security protocols like MAC, JSON Web Tokens, and HTTPS, allowing for efficient and secure communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If file transfers or polling APIs are used for event notifications, then existing systems can transmit events between partners, but computing resource costs are high and security is lacking

Engineering Contradiction:
ImprovesecurityVSAvoidcomputing resource costs
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent introduces a service gateway as an intermediary component that mediates between event sources and event subscribers. The gateway receives event notifications, validates security tokens (JWTs), manages subscriptions, and routes events to appropriate partners. This intermediary architecture eliminates the need for direct peer-to-peer polling and file transfers, reducing computing resource costs while enhancing security through centralized token validation and subscription management.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If polling APIs are used for event notifications, then events can be transmitted between systems, but delays occur and computing resources are consumed

Engineering Contradiction:
Improvenotification efficiencyVSAvoidnotification delays
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

Instead of having subscribers actively poll for events (traditional approach), the patent inverts the approach by having event sources push notifications to subscribers through the service gateway. Event sources publish events to the gateway, which then actively delivers them to subscribed partners. This push-based model eliminates polling delays and reduces computing resource consumption by removing the need for continuous polling requests.

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

3Adaptability or versatility

If partner APIs are used for event notifications, then events can be transmitted, but the system is subject to changes in underlying APIs that force changes in other parts of the distributed system

Engineering Contradiction:
Improvesystem flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service gateway acts as an intermediary that abstracts and standardizes event notification interfaces. Partners subscribe to events through the gateway using standardized mechanisms rather than directly calling partner APIs. When underlying APIs change, only the gateway needs to be updated, not the entire distributed system. This intermediary layer decouples the system components, reducing overall complexity while maintaining adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12388703B2Systems and methods for subscribing topics and registering computer server event notifications
Publication Date: 2025.08.12 WORLDPAY LLC
  • US12388703B2 patent drawing
  • US12388703B2 patent drawing
  • US12388703B2 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.