System-of-Record Event Notifications Across Isolated Ecosystems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems face inefficiencies in disseminating events across isolated ecosystems, leading to high latency and manual, costly processes, and lack the ability to efficiently notify appropriate users about events of interest.

Innovation Solution

A system of record that processes events through a unified platform using machine-learning techniques to automatically classify and notify interested users, allowing for efficient event dissemination across disparate ecosystems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual processes are used to notify users about events, then user preference management is possible, but the process becomes costly and time-consuming

Engineering Contradiction:
Improveuser preference managementVSAvoidnotification process efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system enables users to self-manage their notification preferences by allowing them to subscribe to or unsubscribe from event notifications directly through the interface, eliminating the need for manual administrator intervention while maintaining precise user preference control

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical notification processes with an automated electronic system that uses databases to store user preferences and automatically sends notifications when events occur, significantly improving efficiency while preserving user preference management capabilities

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Stability of the object's composition

If events are processed in isolated ecosystems, then each ecosystem can operate independently, but latency increases and cross-ecosystem notification is difficult

Engineering Contradiction:
Improveecosystem independenceVSAvoidevent notification latency
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent introduces a centralized event processing system that acts as an intermediary between isolated ecosystems, receiving events from multiple sources, processing them according to unified rules, and distributing notifications to appropriate users across all ecosystems, thereby reducing latency while preserving ecosystem independence

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates a universal event processing platform that handles events from diverse ecosystems using common processing logic and notification mechanisms, enabling efficient cross-ecosystem communication without requiring ecosystem-specific handling for each event type

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If a unified system processes events from all ecosystems, then notification efficiency improves, but system complexity increases

Engineering Contradiction:
Improveevent notification efficiencyVSAvoidsystem architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the event processing system into distinct modular components including event collection modules for different ecosystems, a central processing module that统一 handles all events, and notification modules that distribute information to users, making the complex unified system manageable through segmentation while maintaining high processing efficiency

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250363087A1Notifications of events of a system of record
Publication Date: 2025.11.27 DEVREV INC
  • US20250363087A1 patent drawing
  • US20250363087A1 patent drawing
  • US20250363087A1 patent drawing

AI summary

Techniques for notifying users of events for objects in a system of record are described. A request to generate the event is received. The event is indicative of a modification of an object. The event is recorded in a timeline table for a timeline of the object. Based on the modified object in the timeline table and a user table, one or more users may be identified. Further, the event is classified to determine a notification type of the one or more users from the user table. All interested users are selected from the one or more users and notified of the event. In an example, the system automatically subscribes users to receive notification of the occurrence of an event for the object. In an example, the one or more users may request to stop receiving the notification of the occurrence of the event for the object.