Entity-Class Change Triggers for Consolidated Notifications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data processing systems generate numerous unnecessary notifications and reanalyze applications for every minor change, leading to inefficiencies and resource wastage.
Innovation Solution
A data processing system that detects changes at a higher entity class level, generating consolidated notifications and regenerating applications only when necessary, using inter-class triggers and prefiltering to reduce unnecessary evaluations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the system generates notifications for every minor change to entities, then completeness of change detection is improved, but resource wastage and computational overhead increase
Solution Approach 1:
The patent merges multiple granular change notifications into a single consolidated notification at the entity class level. When any entity within an entity class changes, the system generates one notification specifying the entity class rather than separate notifications for each entity, thereby maintaining complete change detection while reducing computational overhead and resource consumption.
Solution Approach 2:
The system pre-establishes inter-class triggers that define relationships between entities and entity classes before changes occur. These triggers are configured in advance to automatically consolidate notifications, eliminating the need for post-change analysis and reducing computational resources required for notification management.
2Speed
If the system reanalyzes applications for every change, then responsiveness to changes is improved, but productivity and processing efficiency deteriorate
Solution Approach 1:
Multiple change events are merged into a single entity class-level notification, which then triggers a single application reanalysis instead of multiple separate reanalyses. This consolidation maintains responsiveness to all changes while significantly improving productivity by eliminating redundant analysis operations.
Solution Approach 2:
The entity class notification serves as an intermediary between individual entity changes and application reanalysis. This intermediate layer filters and consolidates change information, ensuring that applications are reanalyzed only when necessary and only once per entity class change, thereby balancing responsiveness with processing efficiency.
3Measurement precision
If the system uses detailed entity-level monitoring, then detection precision is improved, but device complexity and processing overhead increase
Solution Approach 1:
The system transitions from monitoring at the entity level (one dimension) to monitoring at the entity class level (another dimension). This dimensional shift abstracts individual entity changes into class-level notifications, maintaining detection precision while reducing system complexity by eliminating the need to track and manage numerous individual entity notifications.
Data Source
AI summary
A method implemented by a data processing system for automatically detecting a change in entities of a first entity class, and, in response to the detecting, generating a notification specifying that a change relating to a second entity class has been detected, including: storing an entity model for entity classes; determining that a notification is to be generated upon detection of a change to entities of a first entity class of the entity model, the notification specifying that the detected change relates to a second entity class; detecting a change to an entity of the first entity class; responsive to the change, traversing edges of the entity model to identify a node representing an entity of the second entity class related to another node representing the entity of the first entity class; generating the notification for the entity of the second entity class; and storing the notification for transmission.