Storing and verifying the integrity of event related data

• US 10,599,491 B2
• Filed: 09/26/2019
• Issued: 03/24/2020
• Est. Priority Date: 02/09/2018
• Status: Expired due to Fees

• Current Assignee: Banjo, Inc.
• Original Assignee: Banjo, Inc.
• Inventors: Patton, Damien, Mehta, Rish
• Primary Examiner(s): Anya, Charles E
• Application Number:
  US16/584,198
• Publication Number:
  US 20200019450A1
• Time in Patent Office: 180 Days
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06F 9/5005 to service a request
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/3297 involving time stamps, e.g. generation of time stamps
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

The present invention extends to methods, systems, and computer program products for storing and validating the integrity of event related information. To facilitate auditing and traceability, raw signals, normalized signals, detected events, event expirations, and event notifications can be stored in a queryable distributed ledger (e.g., a blockchain). Personal information can be stripped (or otherwise rendered inert, for example, unrecognizable, unreproducible, etc.) prior to storage into the distributed ledger minimizing the possibility of a person being identified. Ledger data can be used to verify actual data as well as for forensics purposes, such as, to audit data, recreate events, etc., in view of an error or inconsistency to investigate, diagnose, remediate, etc.

Claims

1. A system for validating event notifications in a distributed ledger, the system comprising:

a processor; and

system memory coupled to the processor and storing instructions configured to cause the processor to validate an event, including causing the processor to at least;

store, in the distributed ledger;

a first hash value associated a first normalized signal; and

a second hash value associated with a second normalized signal; and

a source linkage between the first hash value and the second hash value;

access an event notification notifying an entity of an event detected from the first normalized signal and the second normalized signal;

verify the integrity of the event based on contents of the distributed ledger, including causing the processor to;

simulate detection of a simulated event from the first hash value, the first normalized signal, the second hash value, the second normalized signal, and the source linkage;

compare the event to the simulated event; and

determine that simulated event verifies the event; and

based on the integrity verification, allocate a physical resource selected from among;

a first responder resource, a hospital resource, a delivery service resource, a media outlet resource, or a government entity resource to the event.

2. The system of claim 1, wherein the source linkage between the first hash value and the second hash value is based on a determination that the first hash value and the second hash value are from a same source.

3. The system of claim 1, further comprising instructions configured to:

strip personal information from a first raw signal that forms a basis of the first normalized signal;

store a hash of the first raw signal without the personal information in the distributed ledger;

strip personal information from a second raw signal that forms a basis of the second normalized signal; and

store a hash of the second raw signal without the personal information in the distributed ledger.

4. The system of claim 3, wherein instructions configured to verify the integrity of the one or more normalized signals and the event comprise instructions configured to, prior to simulating detection of the simulated event:

access the first raw signal without the personal information using the hash of the first raw signal from the distributed ledger;

simulate normalizing the first raw signal into a first simulated normalized signal;

hash the first simulated normalized signal;

access the second raw signal without the personal information using the hash of the second raw signal from the distributed ledger;

simulate normalizing the second raw signal into a second simulated normalized signal;

hash the second simulated normalized signal;

compare the hash of the first simulated normalized signal to the hash of the first normalized signal; and

compare the hash of the second simulated normalized signal to the hash of the second normalized signal.

5. The system of claim 4, wherein instructions configured to simulate normalizing the first raw signal and the second raw signal into the first simulated normalized signal and the second simulated normalized signal comprises instructions configured to apply a transdimensionality transform to source data in the first raw signal and the second raw signal to re-encode the source data into normalized data having lower dimensionality.

6. The system of claim 1, further comprising instructions configured to:

create an event expiration for the event; and

store the event expiration in the distributed ledger.

7. The system of claim 1, wherein instructions configured to simulate detection of a simulated event from the respective normalized signals comprise instructions configured to reduce contribution of the second normalized signal to simulated detection of the simulated event based on the linkage between the first normalized signal and the second normalized signal.

8. The system of claim 1, further comprising instructions configured to detect an inconsistency or error during processing of the one or more normalized signals;

and

wherein instructions configured to simulate detection of a simulated event from the respective normalized signals comprise instructions configured to follow evolution of the event from raw signal reception through to event detection to validate the event and attempt to resolve the inconsistency or error.

9. The system of claim 1, further comprising instructions configured to:

store in the distributed ledger;

a third hash value associated with a first raw signal at the basis of the first normalized signal; and

a fourth hash value associated with a second raw signal at the basis of the second normalized signal; and

wherein instructions configured to simulate detection of the simulated event from the first normalized signal comprise instructions configured to;

access the first raw signal;

generate a first verification hash of the first raw signal and comparing the first verification hash to the third hash value;

determine that the first verification hash matches the third hash value

access the second raw signal;

generate a second verification hash of the second raw signal and comparing second verification hash to the fourth raw signal; and

determine that the second verification hash matches the fourth hash value.

10. A method comprising validating an event notifications in a distributed ledger, the method comprising:

storing, in a distributed ledger;

a first hash value associated a first normalized signal;

a second hash value associated with a second normalized signal; and

a source linkage between the first hash value and the second hash value;

accessing an event notification notifying an entity of an event detected from the first normalized signal and the second normalized signal;

verifying the integrity of the event based on contents of the distributed ledger, including;

simulating detection of a simulated event from the first hash value, the first normalized signal, the second hash value, the second normalized signal, and the source linkage;

comparing the event to the simulated event; and

determining that simulated event verifies the event; and

based on the integrity verification, allocate an entity a physical resource selected from among;

a first responder resource, a hospital resource, a delivery service resource, a media outlet resource, or a government entity resource to the event.

11. The method of claim 10, wherein the source linkage between the first hash value and the second hash value is based on a determination that the first hash value and the second hash value are from a same source.

12. The method of claim 11, further comprising:

encrypting the data stored in the distributed ledger.

13. The method of claim 10, wherein verifying the integrity of the event further comprises, prior to simulating detection of the simulated event:

accessing one or more raw signals from the distributed ledger;

simulating normalizing the one or more raw signals into one or more simulated normalized signals; and

comparing the one or more normalized signals to the one or more simulated normalized signals.

14. The method of claim 13, wherein simulating normalizing the one or more raw signals into one or more simulated normalized signals comprises applying a transdimensionality transform to source data in the one or more raw signals to re-encode the one or more raw signal into the one or more simulated normalized signals having lower dimensionality.

15. The method of claim 10, further comprising:

creating an event expiration for the event; and

storing the event expiration in the distributed ledger.

16. The method of claim 10, wherein simulating detection of a simulated event from respective normalized signals comprises reducing contribution of the second normalized signal to simulated detection of the simulated event based on the linkage between the first normalized signal and the second normalized signal.

17. The method of claim 10, further comprising detecting an inconsistency or error during processing of the one or more normalized signals;

and

wherein simulating detection of a simulated event from the one or more normalized signals comprises following evolution of the event from raw signal reception through to event detection to validate the event and attempt to resolve the inconsistency or error.

18. The method of claim 10, wherein verifying the integrity of the one or more normalized signals and the event further comprises:

accessing a first raw signal using a hash of the first raw signal stored in the distributed ledger;

simulate normalizing the first raw signal into a first simulated normalized signal;

hash the first simulated normalized signal;

access a second raw signal using a hash of the second raw signal stored in the distributed ledger;

simulate normalizing the second raw signal into a second simulated normalized signal;

hash the second simulated normalized signal;

compare the hash of the first simulated normalized signal to the hash of the first normalized signal; and

compare the hash of the second simulated normalized signal to the hash of the second normalized signal.