OData Key-Based Event Notification for Secure Data Change
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating different computer systems built at various times by different companies to provide accurate and secure notifications of data changes is challenging, as existing methods risk exposing outdated data and compromising security.
Innovation Solution
The use of Open Data Protocol (OData) entity keys to generate and transmit event notifications that include OData keys instead of modified data, allowing only authorized systems to access the data through a unified event structure model, ensuring data security and accuracy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the actual data change is included in the notification, then the notification provides complete information about the change, but it creates security risks by exposing data and may include outdated data
Solution Approach 1:
The patent extracts the data change information from the notification payload and places it in a separate data store. The notification only contains a reference key to the changed entity, while the actual data remains in the data store where it can be securely accessed by authorized systems. This resolves the contradiction by providing complete information access without exposing data in the notification itself.
Solution Approach 2:
The patent introduces a reference key as an intermediary between the notification and the actual data. Instead of directly including data in the notification, the system uses the key as a mediator that points to the data location in the data store. This allows systems to retrieve complete data while maintaining security control over data exposure.
2Loss of information
If the actual data change is included in the notification, then the notification is self-contained, but the data may be out of date and incorrect
Solution Approach 1:
By extracting data from the notification and storing it separately in a data store, the system ensures that the notification contains only the essential change indication and reference key. The actual data is retrieved from the authoritative data store, guaranteeing data accuracy and preventing outdated information from being propagated.
Solution Approach 2:
The system performs preliminary actions by maintaining an up-to-date data store that reflects the current state of all data. When a change notification is generated, the system references this pre-maintained data store, ensuring that any system retrieving data will receive the most current accurate information rather than potentially outdated notification data.
3Adaptability or versatility
If different data formats are used by different companies, then each system maintains its own data structure, but integration becomes challenging
Solution Approach 1:
The patent implements a universal notification structure using standardized reference keys that can reference entities across different systems and data formats. The notification framework is designed to be system-agnostic, allowing it to work with various data formats and structures while maintaining a consistent notification mechanism. This reduces integration complexity while preserving system independence.
Solution Approach 2:
The system segments the notification into distinct components: a standardized notification header with reference keys, and separate data entities stored in their native formats. This segmentation allows each system to maintain its own data structure while participating in a unified notification ecosystem through the standardized key-based reference mechanism.
Data Source
AI summary
Systems and methods of providing data change notifications using OData entity keys are disclosed. In some example embodiments, a first modification of a first property data of a first entity of a first entity type in a relational database is detected, with the first entity having at least one first OData key distinct from the first property data. In some example embodiments, a first event notification comprising a first indication that the first property data has been modified and the at least one first OData key is generated based on an event structure model in response to the detection of the first modification of the first property data, with the first event notification being absent the modified first property data, and the first event notification is transmitted to at least one API.