Centralized Event Message Pushing With Mapping and Error Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for processing protected data face challenges such as scalability constraints, maintenance overhead, geographic limitations, data protection compliance, security vulnerabilities, and latency issues, particularly in the decentralized pushing of event messages to data service applications, leading to inconsistent security and inefficient error handling.

Innovation Solution

A method for pushing event messages to cloud-based data service applications using a centralized system that employs a mapping mechanism, batch processing, and error handling to ensure reliable and secure transmission, decoupling event message pushing from individual applications, and utilizing cloud-based services for validation and decryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If event message pushing is decentralized to individual applications, then applications can independently push events, but security becomes inconsistent and maintenance overhead increases

Engineering Contradiction:
Improveindependent event pushing capabilityVSAvoidsecurity consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a dedicated event message pushing component as an intermediary layer between applications and data service applications. This component centralizes the pushing logic, ensuring consistent security standards and reducing maintenance overhead while preserving application independence. The intermediary manages event message routing, authentication, and error handling centrally rather than分散ly in each application.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If event message pushing is handled application-by-application, then each application can manage its own events, but error handling becomes complex and resolution time increases

Engineering Contradiction:
Improveautonomous event managementVSAvoiderror resolution time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent merges error handling functionality into the centralized event message pushing component. All error handling logic, including error detection, notification, and resolution coordination, is consolidated in this single component rather than being distributed across multiple applications. This unification simplifies error management and accelerates resolution while maintaining autonomous event management capabilities.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If multiple applications push event messages independently, then event coverage is comprehensive, but standardisation deviates and interoperability decreases

Engineering Contradiction:
Improveevent message coverageVSAvoidstandardisation consistency
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal event message pushing component that handles all event message routing across the system. This single component provides multi-functional capabilities including event message formatting, validation, routing to multiple data service applications, and maintaining standardisation consistency. By making this component universal, the system achieves comprehensive event coverage while enforcing consistent standards across all applications.

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

Data Source

PatentUS20260037294A1Method for pushing event messages
Publication Date: 2026.02.05 BARCLAYS EXECUTION SERVICES LTD
  • US20260037294A1 patent drawing
  • US20260037294A1 patent drawing
  • US20260037294A1 patent drawing

AI summary

A computer-implemented method for pushing one or more event messages to one or more cloud-based data service applications. The method comprising: receiving a first publication trigger signal indicating that one or more event messages of a first event type are to be published; identifying the one or more event messages of the first event type in an event storage database; retrieving the one or more event messages of the first event type from the event storage database; identifying a first mapping from a plurality of stored mappings, the first mapping corresponding to the first event type; retrieving the first mapping; updating metadata associated with the one or more event messages of the first event type to indicate that publication has occurred; and pushing the one or more event messages of the first event type to one or more cloud-based data service applications according to the first mapping.