Event Notification Template-Based Data Filtering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In traditional event subscription systems, event subscribers receive excessive or insufficient data from event providers, requiring complex filtering and reformatting, which increases network bandwidth usage and server load.

Innovation Solution

Event subscribers can specify data templates to event providers, allowing only relevant data fields to be sent in event notifications, reducing the amount of data transmitted and processed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If event providers send complete data packets to all subscribers, then data completeness is improved, but network bandwidth usage and server load increase

Engineering Contradiction:
Improvedata completenessVSAvoidnetwork bandwidth usage
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent segments the complete data packet into multiple data fields and allows selective transmission of only the necessary fields to each subscriber based on their subscription preferences. This is achieved by dividing the event notification into discrete fields that can be individually selected and transmitted, reducing unnecessary data transfer while maintaining completeness for subscribed fields.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by customizing the data notification to match each subscriber's specific needs and preferences. Each subscriber receives a tailored notification containing only the data fields relevant to their subscription, rather than a uniform complete data packet. This allows different quality levels of data delivery for different subscribers based on their individual requirements.

Inventive Principle:
Principle #3Local quality

2Loss of information

If event providers send complete data packets to all subscribers, then data completeness is improved, but server load increases

Engineering Contradiction:
Improvedata completenessVSAvoidserver load
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The server segments the data notification process by identifying which data fields are needed for each subscriber based on their subscription configuration. This segmentation allows the server to construct customized notifications containing only necessary fields, reducing processing load while maintaining data completeness for subscribed fields.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by having the server transmit only the necessary data fields to each subscriber rather than complete data packets. This partial transmission approach reduces server load and network bandwidth usage while still providing complete information for the fields that subscribers have explicitly requested.

Inventive Principle:
Principle #16Partial or excessive action

3Adaptability or versatility

If event subscribers use filters and expressions to reformat data, then data adaptability is improved, but processing complexity increases

Engineering Contradiction:
Improvedata adaptabilityVSAvoidprocessing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent inverts the traditional approach by having the event provider customize the data notification to match subscriber preferences rather than having subscribers filter and reformat received data. This inversion shifts the complexity from the subscriber side to the provider side, where the server constructs customized notifications based on subscriber subscription definitions, thereby reducing subscriber processing complexity while maintaining high data adaptability.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent introduces subscription definitions as an intermediary mechanism that mediates between the event provider and subscriber. These definitions act as a bridge that translates subscriber preferences into customized data notifications, eliminating the need for complex filters and expressions at the subscriber end while maintaining adaptability to different data formats and configurations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10135940B2Subscribing to event notifications using object instances
Publication Date: 2018.11.20 ORACLE INT CORP
  • US10135940B2 patent drawing
  • US10135940B2 patent drawing
  • US10135940B2 patent drawing

AI summary

A method of handling event subscriptions and notifications may include receiving a request from a client system to subscribe to an event type, and receiving a template from the client system. The template may define data that should be returned to the client system when an event of the event type occurs. In response to the event of the event type occurring, the method may also include packaging data associated with the event according to the template received from the client system to generate an event notification. The method may further include sending the event notification to the client system.