Event Message Pulling Module With Filtering And Schema Checks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in securely and efficiently transmitting protected data between multiple cloud-based domains with proprietary communication protocols, and there is a need for a solution that addresses scalability, security, and compatibility issues in cloud-based data processing.
Innovation Solution
A module for pulling event messages to a cloud-based data service application that applies filter criteria and schema validation, ensuring secure and efficient message transfer between different cloud-based domains, while offloading non-validated messages to service applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If cloud-based implementations are used to avoid local server limitations, then scalability and accessibility are improved, but security vulnerabilities and data protection compliance become worsened
Solution Approach 1:
The patent introduces a message broker as an intermediary component between data producers and consumers in the cloud-based system. This broker acts as a trusted mediator that enforces security policies, validates messages, and manages authentication/authorization, thereby maintaining security while enabling cloud-based scalability.
Solution Approach 2:
The system segments security concerns into separate modular components: message validation logic, authentication mechanisms, and policy enforcement are separated from the core cloud applications. This allows security functions to be independently managed and updated without affecting the overall system scalability.
2Adaptability or versatility
If multiple cloud-based domains with proprietary communication protocols are integrated, then system versatility is improved, but communication compatibility and integration complexity become worsened
Solution Approach 1:
The message broker is designed with universal messaging capabilities that can handle multiple proprietary communication protocols through a single unified interface. It provides protocol translation and standardization, allowing different cloud domains to communicate without requiring complex point-to-point integration logic in each application.
Solution Approach 2:
The broker serves as a protocol translation layer between domains with different communication protocols. It receives messages in various protocol formats, normalizes them into a standard internal representation, and routes them to appropriate destinations, thereby simplifying cross-domain communication.
3Speed
If fast and secure transmission of protected data between multiple cloud domains is implemented, then data transmission speed is improved, but security risks become worsened
Solution Approach 1:
The system performs preliminary security actions before data transmission: messages are validated against schemas, authenticated, and authorized prior to being routed between cloud domains. This pre-validation approach ensures security checks are completed once at the source rather than repeatedly at each destination, maintaining both speed and security.
Solution Approach 2:
The message broker establishes continuous secure communication channels with established authentication and encryption protocols. Once a secure connection is established, data can flow continuously without repeated handshakes, maintaining high transmission speed while preserving security through persistent encrypted sessions.
Data Source
Figure 1
Figure 2
Figure 3A~3B
AI summary
There is provided a module for pulling an event message to a cloud-based data service application. The module may be configured to pull at least one event message from at least one cloud-based data streaming application. For each event message of the at least one event message, the module may be configured to select and retrieve at least one filter criterion from a plurality of filter criteria based at least in part on at least one event message configuration parameter of the event message. The module may be configured to apply the at least one filter criterion to the event message. If the event message passes the filter criterion, the module may be configured to determine whether event message schema validation is required based on the at least one event message configuration parameter. If event message schema validation is not required, the module may be configured to send the event message to at least one cloud-based data service application. If event message schema validation is required, validate the event message based at least in part on comparing the event message to at least one schema record. If the event message schema validation is successful, the module may be configured to send the event message to at least one cloud-based data service application.