Event Message Mapping for Secure Cloud Push Delivery
Find Innovative SolutionsGenerate 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 a cloud-based registry for schema validation and decryption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If event message pushing is decentralized to individual applications, then each application can independently push events, but security becomes inconsistent and maintenance overhead increases
Solution Approach 1:
The patent introduces a dedicated event message pushing component as an intermediary between applications and data service applications. This mediator centralizes the pushing functionality, ensuring consistent security protocols and reducing maintenance overhead while preserving the ability of applications to independently trigger events through publish/subscribe mechanisms.
Solution Approach 2:
The patent extracts the event message pushing capability from individual applications and places it in a separate, dedicated component. This extraction allows the pushing functionality to be standardized, secured, and maintained independently from application logic, while applications retain their event generation and subscription capabilities.
2Ease of operation
If event message pushing is handled application-by-application, then each application has full control, but error handling complexity increases and response time decreases
Solution Approach 1:
The dedicated pushing component serves as a mediator that handles error management centrally. It provides standardized error handling mechanisms and monitoring for all event messages, reducing the complexity that would otherwise exist in each application while maintaining application control through configuration and subscription mechanisms.
Solution Approach 2:
The pushing component provides self-service error handling and monitoring capabilities, automatically managing failures and providing centralized visibility without requiring complex error handling logic in each application. This reduces overall system complexity while maintaining operational control.
3Ease of manufacture
If mappings between event types and data service applications are hardcoded, then integration is straightforward, but adaptability to new event types or applications decreases
Solution Approach 1:
The patent implements dynamic mappings between event types and data service applications, allowing the system to adapt to new event types and applications without code changes. The mappings can be configured and updated at runtime, providing both the simplicity of predefined relationships and the flexibility to accommodate changes.
Solution Approach 2:
The mapping mechanism is designed to be universal, handling multiple event types and data service applications through a common interface. This allows the same infrastructure to support both simple hardcoded mappings and more complex dynamic mappings, providing ease of integration while maintaining adaptability.
4Adaptability or versatility
If security protocols are implemented in each application, then each application can secure its own events, but security standards become inconsistent and vulnerabilities increase
Solution Approach 1:
The dedicated pushing component acts as a security intermediary, implementing standardized security protocols for all event messages. This ensures consistent security standards across the system while allowing applications to maintain their own security configurations through the standardized interface provided by the mediator.
Solution Approach 2:
Security implementation is extracted from individual applications and centralized in the dedicated pushing component. This extraction ensures that security protocols are applied consistently to all event messages regardless of their source, eliminating the inconsistencies and vulnerabilities that arise from decentralized security implementation.
Data Source
Figure 1
Figure 2
Figure 3A~3B
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, wherein the one or more event messages of the first event type are stored in an event storage database; identifying the one or more event messages of the first event type in the 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.