Event Router Standardized Message Format
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing event-based publish/subscribe model lacks a standardized event message format, leading to complexities in data exchange and integration across disparate systems, particularly in IoT and IIoT devices, where different manufacturers use unique event data formats, resulting in the need for multiple Event Brokers and transformation layers, which increases computational burden and complexity.
Innovation Solution
The introduction of an Event Router ecosystem that standardizes event data using a (Domain, Entity, Attribute, Value) format, allowing for decentralized and federated networks of Event Routers to route events without the need for a centralized broker, enabling localized filtering, normalization, and transformation based on event data values.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a centralized Event Broker model is used to handle event data from disparate sources, then event routing and integration can be achieved, but system complexity and computational overhead increase significantly
Solution Approach 1:
The patent segments the centralized Event Broker functionality into distributed Event Router components deployed across multiple devices and systems. Each Event Router handles local event filtering and routing independently, eliminating the need for a single complex centralized broker while maintaining versatile event routing capabilities across the network.
Solution Approach 2:
The patent introduces a new dimension of standardization by implementing a standardized event message format with defined schemas. This schema-based approach adds a structural dimension to event processing, allowing events from disparate sources to be normalized and routed consistently without requiring complex centralized transformation logic.
2Adaptability or versatility
If multiple Event Brokers and transformation layers are deployed to handle different event data formats, then integration across disparate systems is achieved, but computational burden and processing overhead increase
Solution Approach 1:
The patent applies preliminary action by defining event schemas and data formats in advance before events are generated. Event producers create events conforming to pre-defined schemas, and Event Routers use these pre-established schemas to efficiently validate and route events without requiring complex real-time transformation, significantly reducing computational burden.
Solution Approach 2:
The patent uses schema copying where standardized event format definitions are replicated and distributed across multiple Event Routers. Each router has local copies of the schemas it needs to validate and route events, eliminating the need for centralized transformation services and reducing processing overhead at each node.
3Ease of manufacture
If event data from different manufacturers with unique formats is processed without standardization, then device-specific functionality is maintained, but data exchange and integration become complex
Solution Approach 1:
The patent implements universality by creating a standardized event message format that can accommodate events from multiple manufacturers and device types. The schema system provides universal structures with optional fields that maintain device independence while enabling seamless data exchange and integration across heterogeneous systems.
Data Source
AI summary
The subject matter includes an event-based routing system including an Event Router Domain Rules Language Compiler that parses and compiles a Domain Event Router rules file into Event Router rules instructions. An Event Router ingests incoming event data and applies the Event Router rules instructions. An Event Router Management component manages the Event Router, where the Event Router includes a single Event Router or a network of multiple Event Routers. A Domain Registry registers domain definitions and provides the domain definitions to the Event Router Domain Rules Language Compiler and a Domain Endpoint Resolver. The Domain Endpoint Resolver stores IP addresses, ports, and names of domains for which the Event Router receives event data, as well as the domain names of the Event Routers. The event data are formatted in an event message format comprising a tuple of at least: a Domain, an Entity, an Attribute, and a Value.