Database Notification Interface Using Bit-Mask Application Identification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Enterprise servers face challenges in ensuring that client applications access updated and accurate database information, leading to unreliable services due to outdated or corrupted data.

Innovation Solution

A system and method for managing change notifications in a database, where a database manager registers applications to receive notifications of changes, inserts, updates, or deletions in a database table by creating a notification table and triggering procedures to copy changed rows, using bit-masks to identify registered applications and clear notifications once processed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the database manager implements comprehensive change notification for all tables and applications, then service reliability is improved, but device complexity increases

Engineering Contradiction:

Improveservice reliabilityVSAvoiddevice complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The notification system is segmented into multiple components: a notification table with specific fields (application_id, table_name, notification_type, timestamp), trigger procedures that fire on specific events (INSERT, UPDATE, DELETE), and a bit-mask mechanism for application identification. This segmentation allows the system to manage complexity through modular organization while maintaining comprehensive notification capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Applications register their notification preferences in advance by storing their bit-masks in the notification table before changes occur. The trigger procedure is pre-configured to automatically copy changed rows to the notification table. This preliminary setup eliminates the need for real-time configuration during data changes, reducing operational complexity while ensuring reliable notifications.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If the system creates a notification table with additional fields for managing notifications, then notification reliability is improved, but manufacturing precision (data structure design) becomes more complex

Engineering Contradiction:

Improvenotification reliabilityVSAvoiddata structure design

Core Design Contradiction:

ReliabilityVSManufacturing precision

Solution Approach 1:

The notification table serves multiple functions simultaneously: it stores change notifications, tracks application registration status through bit-masks, records notification types (INSERT, UPDATE, DELETE), and maintains timestamps for ordering. This multi-functionality consolidates what would otherwise require separate structures into a single unified table, improving reliability without proportionally increasing design complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The bit-mask field within the notification table embeds multiple application identifiers into a single data structure. Each bit represents an application's subscription status, allowing the system to track multiple application registrations within one field. This nesting approach improves notification reliability for multiple applications while keeping the data structure compact and manageable.

Inventive Principle:

Principle #7Nested doll (Nesting)

3Productivity

If the database manager uses bit-masks to identify registered applications, then notification efficiency is improved, but measurement precision (application identification accuracy) becomes more complex

Engineering Contradiction:

Improvenotification efficiencyVSAvoidapplication identification accuracy

Core Design Contradiction:

ProductivityVSMeasurement precision

Solution Approach 1:

The system changes the parameter representation from traditional application ID lists or JSON objects to a bit-mask integer. Each application is assigned a unique bit position, and the bit-mask efficiently encodes which applications are registered. This parameter transformation improves notification efficiency by enabling faster comparisons and processing, while maintaining precise application identification through the bit-position mapping.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS9292587B2Systems and methods for database notification interface to efficiently identify events and changed data

Publication Date: 2016.03.22 CITRIX SYSTEMS INC

AI summary

Systems and methods for providing notifications of changes made in a database table to a remote application is presented. The system and methods manage change notification of a table in a database by notifying an application registered to receive notifications of changes made to a database table. A database manager executing on a device may receive a request to register an application to be notified when a first table of a plurality of tables in a database is changed. The database manager may establish a notification table comprising fields of the first table and one or more additional fields for managing notification. The database manager may establish a trigger on the first table to invoke a trigger procedure to copy a changed row of the first table to the notification table. The database manager may create a rule for the notification table to notify registered applications when a new row is inserted into the notification table.