COMPUTING SYSTEM PROVIDING BLOCKCHAIN-FACILITATED SEMANTIC INTEROPERABILITY BETWEEN MULTIPLE DISPARATE SYSTEMS OF RECORD (SORs) AND RELATED METHODS
Abstract
A system may include a plurality of systems of record (SORs) each including a local SOR database(s) configured to store information corresponding to local SOR identities, a change monitor service configured to detect updates to the local SOR database(s), and a transactor node configured to receive the updates from the change monitor service, communicate the updates to other transactor nodes of other SORs, and receive updates from the other transactor nodes for non-local SOR entities. Each SOR may also include a domain cache configured to store the updates received by the transactor node as an immutable list of updates to the local and non-local SOR entities over time, and a synchronization service cooperating with the domain cache to determine updates to non-local SOR identities that correspond to local SOR identities and update the local SOR database(s) based thereon.
Claims
exact text as granted — not AI-modified1 . A system comprising:
a plurality of systems of record (SORs) each comprising
at least one local SOR database configured to store information corresponding to local SOR identities,
a change monitor service configured to detect updates to the at least one local SOR database for the local SOR identities,
a transactor node configured to receive the updates from the change monitor service for the local SOR identities, communicate the updates from the change monitor service for the local SOR identities to other transactor nodes of other SORs, and receive updates from the other transactor nodes for non-local SOR entities,
a domain cache configured to store the updates received by the transactor node as an immutable list of updates to the local and non-local SOR entities over time, and
a synchronization service cooperating with the domain cache to determine updates to non-local SOR identities that correspond to local SOR identities and update the at least one local SOR database based thereon.
2 . The system of claim 1 wherein the at least one local SOR database comprises a plurality of local SOR databases that are disparate to one another.
3 . The system of claim 2 wherein the synchronization service is configured to cooperate with the domain cache to determine updates to local and non-local SOR identities that correspond to local SOR identities in each of the local SOR databases and update the local SOR databases based thereon.
4 . The system of claim 1 wherein the change monitor service and transactor node operate at a same network level.
5 . The system of claim 1 wherein the domain cache and the distributed transactor operate at a different network level.
6 . The system of claim 1 wherein the domain cache is further configured to store a history including respective states of local and non-local SOR entities known to each of the SORs as of the time of each update.
7 . The system of claim 1 wherein the domain cache is further configured to store metadata including instructions for repeatably recreating the current state of local and non-local SOR identities as of the time of the respective update.
8 . The system of claim 7 wherein the synchronization service is further configured to cooperate with the at least one local SOR database to align divergent updates otherwise preventing the at least one Local SOR database from recreating the current state of local SOR identities.
9 . A system of record (SOR) comprising:
at least one local SOR database configured to store information corresponding to local SOR identities; a change monitor service configured to detect updates to the at least one local SOR database for the local SOR identities; a transactor node configured to receive the updates from the change monitor service for the local SOR identities, communicate the updates from the change monitor service for the local SOR identities to other transactor nodes of other SORs, and receive updates from the other transactor nodes for non-local SOR entities; a domain cache configured to store the updates received by the transactor node as an immutable list of updates to the local and non-local SOR entities over time; and a synchronization service cooperating with the domain cache to determine updates to non-local SOR identities that correspond to local SOR identities and update the at least one local SOR database based thereon.
10 . The SOR of claim 9 wherein the at least one local SOR database comprises a plurality of local SOR databases that are disparate to one another.
11 . The SOR of claim 10 wherein the synchronization service is configured to cooperate with the domain cache to determine updates to local and non-local SOR identities that correspond to local SOR identities in each of the local SOR databases and update the local SOR databases based thereon.
12 . The SOR of claim 9 wherein the change monitor service and transactor node operate at a same network level.
13 . The SOR of claim 9 wherein the domain cache and the distributed transactor operate at a different network level.
14 . The SOR of claim 9 wherein the domain cache is further configured to store a history including respective states of local and non-local SOR entities known to each of the SORs as of the time of each update.
15 . The SOR of claim 9 wherein the domain cache is further configured to store metadata including instructions for repeatably recreating the current state of local and non-local SOR identities as of the time of the respective update.
16 . The SOR of claim 15 wherein the synchronization service is further configured to cooperate with the at least one local SOR database to align divergent updates otherwise preventing the at least one Local SOR database from recreating the current state of local SOR identities.
17 . A method comprising:
at each of a plurality of systems of record (SORs),
storing information corresponding to local SOR identities at at least one local SOR database,
detecting updates to the at least one local SOR database for the local SOR identities at a change monitor service,
using a transactor node configured to communicate the updates from the change monitor service for the local SOR identities to other transactor nodes of other SORs, and receive updates from the other transactor nodes for non-local SOR entities,
storing the updates received by the transactor node as an immutable list of updates to the local and non-local SOR entities over time at a domain cache, and
using a synchronization service to determine updates to non-local SOR identities from the domain cache that correspond to local SOR identities and update the at least one local SOR database based thereon.
18 . The method of claim 17 wherein the at least one local SOR database comprises a plurality of local SOR databases that are disparate to one another.
19 . The method of claim 18 further comprising using the synchronization service to determine updates to local and non-local SOR identities from the domain cache that correspond to local SOR identities in each of the local SOR databases and update the local SOR databases based thereon.
20 . The method of claim 17 wherein the change monitor service and transactor node operate at a same network level.
21 . The method of claim 17 wherein the domain cache and the distributed transactor operate at a different network level.
22 . The method of claim 17 further comprising storing at the domain cache a history including respective states of local and non-local SOR entities known to each of the SORs as of the time of each update.
23 . The method of claim 17 further comprising storing in the domain cache metadata including instructions for repeatably recreating the current state of local and non-local SOR identities as of the time of the respective update.
24 . The method of claim 23 further comprising using the synchronization service to align divergent updates otherwise preventing the at least one Local SOR database from recreating the current state of local SOR identities.Join the waitlist — get patent alerts
Track US2024037122A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.