Event Instance Determination for Flexible Event-Driven Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing event-driven communication systems are inflexible and require complex formatting and frequent updates, making it difficult to integrate new technologies or mechanisms, and they lack real-time data availability for network monitoring and analysis.

Innovation Solution

A method and apparatus for determining event instances in event-driven communication systems, where an event stream is received, metadata is retrieved, and event instances are instantiated based on metadata, allowing for a common understanding of events and enabling configuration without software updates, with communication sessions defined by these instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If complex formatting and hardcoded parsers are used in event-driven communication systems, then data exchange between disparate systems is facilitated, but the system becomes inflexible and requires frequent updates to integrate new event processing technologies

Engineering Contradiction:

Improveflexibility to integrate new event processing technologiesVSAvoidcomplex formatting and hardcoded parsers

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system transitions from static, hardcoded parsers to dynamic, runtime-configurable event processing. Event schemas are loaded from external metadata at runtime, allowing the system to adapt to new event types and formats without recompilation. The event instance determination process dynamically creates appropriate parser instances based on event type metadata, enabling flexible integration of new event processing mechanisms.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The invention changes the parameter of parser configuration from compile-time fixed values to runtime-modifiable metadata. Event schemas define parser behavior through configurable parameters such as event type, data format, and processing rules, which can be changed without modifying the underlying system code. This allows the system to handle diverse event formats while maintaining a unified processing framework.

Inventive Principle:

Principle #35Parameter changes

2Ease of manufacture

If separate updates are required for data analysers, filters, correlators, forwarders and persisters whenever an event is updated, then each component can be independently maintained, but the system becomes difficult to update and maintain

Engineering Contradiction:

Improveease of system updates and maintenanceVSAvoidmanual update requirement for multiple components

Core Design Contradiction:

Ease of manufactureVSExtent of automation

Solution Approach 1:

The event schema metadata serves as a universal configuration that governs all event processing components. A single schema definition is used by data analysers, filters, correlators, forwarders, and persisters, eliminating the need to update each component separately. The schema acts as a central source of truth that all components reference, ensuring consistency across the system.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The invention introduces event schemas as an intermediary layer between the event source and processing components. This metadata intermediary translates event definitions into actionable configuration for all downstream components automatically. When an event schema changes, the intermediary mechanism ensures all components receive and apply the updated configuration without manual intervention.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Productivity

If batch collection mechanism is used for counter data, then transmission efficiency is improved, but real-time data availability is lost due to inherent delay

Engineering Contradiction:

Improvedata transmission efficiencyVSAvoiddelay before counter data can be collected

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system implements periodic event schema validation and instance determination, where event data is processed at regular intervals defined by the event schema timing parameters. This periodic processing allows the system to maintain real-time responsiveness while optimizing data transmission efficiency through structured, time-based collection cycles.

Inventive Principle:

Principle #19Periodic action

4Productivity

If event schemas are hardcoded in the system, then parsing is efficient, but any changes in input sources require parser updates

Engineering Contradiction:

Improveevent processing efficiencyVSAvoidability to handle changes in input sources

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary loading of event schemas from external metadata files into memory at startup or on-demand. This preliminary action prepares the parsing configuration in advance, allowing efficient runtime processing without the need to read from disk during event handling. The schemas are cached and reused, maintaining processing efficiency while allowing external modification of the source files.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9954720B2Method and apparatus for determining an event instance

Publication Date: 2018.04.24 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

A method of determining an event instance in an event driven communications system, the method comprising the steps of: receiving (205,207) an event stream, the event stream comprising a plurality of events; retrieving (203) metadata for each event of the received event stream; instantiating (219) an event instance for each event of the received event stream based on the retrieved metadata; reading (221) event data of each event of the received event stream into the instantiated event instance.