110 can then generate a list of event data for the missed event message(s), which the subscriber system 110 can electronically transmit to the blockchain node 106 using a suitable communication network and method.

The blockchain node 106 can include the list of event data for the missed event message(s) in a new blockchain data entry that is generated and added to a new block that is generated and added to the blockchain using traditional methods and systems. In some cases, the blockchain data entry can also include timestamp data, an identifier, and/or a digital signature generated by the subscriber system 110 using its private key, as applicable. The processing server 102 can identify the list of event data for the missed event message(s) in the newly added blockchain data entry and identify the missed event message(s) using the event data in the list. The processing server 102 can then have the missed event message(s) delivered to the subscriber system 110, such as via a function of the event platform 108, a message broker, or other suitable method. The subscriber system 110 can then receive the missed event message(s) and then have a complete set of event messages for the time period.

The methods and systems discussed herein provide for fast, efficient, and effective reconciliation of published event messages in a pub-sub architecture via use of the blockchain network 104. The use of a blockchain ensures that data is accurate and auditable by all participants, as the data stored therein is immutable and cannot be tampered with or falsified. Such immutability can be beneficial in industries where compliance with regulations is required and can be beneficial for publishers to ensure that subscribers are not operating with missing event messages and for subscribers to ensure that publishers are not tampering with data for published event messages. As a result, publishers and subscribers can constantly maintain accurate publishing and consumption of event messages and quickly reconcile any discrepancies.

In some embodiments, the processing server 102 can include the event data with the EventCount when transmitting the EventCount to the blockchain node 106. In such an embodiment, the event data can be included in the blockchain data entry that includes the EventCount. The subscriber system 110 can then immediately identify the missed event message(s) if the subscriber system's AuditCount is different from the EventCount identified in the blockchain data entry. In such cases, the process can be further streamlined. In other embodiments, the process can be performed without the addition of the EventCount value on the blockchain.

Processing Server

FIG. 2 illustrates an embodiment of the processing server 102 in the system 100. It will be apparent to persons having skill in the relevant art that the embodiment of the processing server 102 illustrated in FIG. 2 is provided as illustration only and cannot be exhaustive to all possible configurations of the processing server 102 suitable for performing the functions as discussed herein. For example, the computer system 500 illustrated in FIG. 5 and discussed in more detail below can be a suitable configuration of the processing server 102.

The processing server 102 can include a receiving device 202. The receiving device 202 can be configured to receive data over one or more networks via one or more network protocols. In some instances, the receiving device 202 can be configured to receive data from blockchain nodes 106, event platforms 108, subscriber systems 110, and other systems and entities via one or more communication methods, such as radio frequency, local area networks, wireless area networks, cellular communication networks, Bluetooth, the Internet, etc. In some embodiments, the receiving device 202 can be comprised of multiple devices, such as different receiving devices for receiving data over different networks, such as a first receiving device for receiving data over a local area network and a second receiving device for receiving data via the Internet. The receiving device 202 can receive electronically transmitted data signals, where data can be superimposed or otherwise encoded on the data signal and decoded, parsed, read, or otherwise obtained via receipt of the data signal by the receiving device 202. In some instances, the receiving device 202 can include a parsing module for parsing the received data signal to obtain the data superimposed thereon. For example, the receiving device 202 can include a parser program configured to receive and transform the received data signal into usable input for the functions performed by the processing device to carry out the methods and systems described herein.

The receiving device 202 can be configured to receive data signals electronically transmitted by blockchain nodes 106, which can be superimposed or otherwise encoded with converted device profiles, public keys, configuration keys, configuration key requests, request for identification data, blockchain data entries, blocks, confirmation messages, etc. The receiving device 202 can also be configured to receive data signals electronically transmitted by event platforms 108 that can be superimposed or otherwise encoded with requests for event messages and other communications used in the publishing of events on the event platform 108. The receiving device 202 can also be configured to receive data signals electronically transmitted by subscriber systems 110 in implementations where a publisher can communicate directly with a subscriber for the conveyance of missed event messages or other data used in the publishing and consumption of event messages on the event platform 108.

The processing server 102 can also include a communication module 204. The communication module 204 can be configured to transmit data between modules, engines, databases, memories, and other components of the processing server 102 for use in performing the functions discussed herein. The communication module 204 can be comprised of one or more communication types and utilize various communication methods for communications within a computing device. For example, the communication module 204 can be comprised of a bus, contact pin connectors, wires, etc. In some embodiments, the communication module 204 can also be configured to communicate between internal components of the processing server 102 and external components of the processing server 102, such as externally connected databases, display devices, input devices, etc. The processing server 102 can also include a processing device. The processing device can be configured to perform the functions of the processing server 102 discussed herein as will be apparent to persons having skill in the relevant art. In some embodiments, the processing device can include and/or be comprised of a plurality of engines and/or modules specially configured to perform one or more functions of the processing device, such as a querying module 216, generation module 218, validation module 220, etc. As used herein, the term “module” can be software or hardware particularly programmed to receive an input, perform one or more processes using the input, and provides an output. The input, output, and processes performed by various modules will be apparent to one skilled in the art based upon the present disclosure.

The processing server 102 can also include an event database 206. The event database 206 can be configured to store one or more events 208 using a suitable data storage format and schema. The event database 206 can be a relational database that utilizes structured query language for the storage, identification, modifying, updating, accessing, etc. of structured data sets stored therein. Each event 208 can be a structured data set configured to store data related to an event for which an event message is published via the event platform 108. The event 208 can include the event message, an EventID unique to the event 208, and any other suitable data, such as one or more category values, timestamp data, time period data, etc.

The processing server 102 can also include a memory 214. The memory 214 can be configured to store data for use by the processing server 102 in performing the functions discussed herein, such as public and private keys, symmetric keys, etc. The memory 214 can be configured to store data using suitable data formatting methods and schema and can be any suitable type of memory, such as read-only memory, random access memory, etc. The memory 214 can include, for example, encryption keys and algorithms, communication protocols and standards, data formatting standards and protocols, program code for modules and application programs of the processing device, and other data that can be suitable for use by the processing server 102 in the performance of the functions disclosed herein as will be apparent to persons having skill in the relevant art. In some embodiments, the memory 214 can be comprised of or can otherwise include a relational database that utilizes structured query language for the storage, identification, modifying, updating, accessing, etc. of structured data sets stored therein. The memory 214 can be configured to store, for example, cryptographic keys including public keys and/or private keys, communication data, blockchain algorithms and data, encryption algorithms, event category data, timestamp data, etc.

The processing server 102 can include a querying module 216. The querying module 216 can be configured to execute queries on databases to identify information. The querying module 216 can receive one or more data values or query strings and can execute a query string based thereon on an indicated database, such as the blockchain data 206 of the processing server 102 to identify information stored therein. The querying module 216 can then output the identified information to an appropriate engine or module of the processing server 102 as necessary. The querying module 216 can, for example, execute a query on the event database 206 to identify event identifiers for events 208 whose event messages were published on the event platform 108 during a specific time period.

The processing server 102 can also include a generation module 218. The generation module 218 can be configured to generate data for use by the processing server 102 in performing the functions discussed herein. The generation module 218 can receive instructions as input, can generate data based on the instructions, and can output the generated data to one or more modules of the processing server 102. For example, the generation module 218 can be configured to generate events 208, event messages, EventCount values, lists of event data, EventIDs, etc.

The processing server 102 can also include a validation module 220. The validation module 220 can be configured to perform data validations and verifications for the processing server 102 as part of the functions discussed herein. The validation module 220 can receive instructions as input, can perform data validations or verification as instructed, and can output a result of the data validations or verifications to one or more modules of the processing server 102. In some cases, the input can include the data to be validated or verified and/or data to be used in the validation or verification. In other cases, the validation module 220 can be configured to identify such data, such as in the event database 206 and/or memory 214. The validation module 220 can be configured to, for example, validate digital signatures, perform comparisons of EventCount and AuditCount values, etc.

The processing server 102 can also include a transmitting device 224. The transmitting device 224 can be configured to transmit data over one or more networks via one or more network protocols. In some instances, the transmitting device 224 can be configured to transmit data to blockchain nodes 106, event platforms 108, subscriber systems 110, and other entities via one or more communication methods, local area networks, wireless area networks, cellular communication, Bluetooth, radio frequency, the Internet, etc. In some embodiments, the transmitting device 224 can be comprised of multiple devices, such as different transmitting devices for transmitting data over different networks, such as a first transmitting device for transmitting data over a local area network and a second transmitting device for transmitting data via the Internet. The transmitting device 224 can electronically transmit data signals that have data superimposed that can be parsed by a receiving computing device. In some instances, the transmitting device 224 can include one or more modules for superimposing, encoding, or otherwise formatting data into data signals suitable for transmission.

The transmitting device 224 can be configured to electronically transmit data signals to blockchain nodes 106, which can be superimposed or otherwise encoded with public key requests, configuration keys, configuration key requests, blockchain data entries, blocks, confirmation messages, EventCount values, event data, etc. The transmitting device 224 can also be configured to electronically transmit data signals to event platforms 108 that can be superimposed or otherwise encoded with event messages and other data used in the publishing of event messages on the event platform 108. The transmitting device 224 can also be configured to electronically transmit data signals to subscriber systems 110 in implementations where a publisher can communicate directly with a subscriber for the conveyance of missed event messages or other data used in the publishing and consumption of event messages on the event platform 108.

Process for Reconciliation of Event Messages

FIG. 3 illustrates a process 300 in the system 100 of FIG. 1 for the reconciliation of event messages published during a specific time period using a blockchain.

In step 302, the processing server 102 can published event messages for a plurality of events on the event platform 108 during a predetermined period of time. The event messages can be published such that any subscriber system 110 can obtain and consume the event messages via the event platform 108 using suitable methods. As part of the publishing of event messages, the processing server 102 can maintain a count of the number of published event messages during the predetermined period of time. In step 304, the transmitting device 224 of the processing server 102 can electronically transmit the EventCount value to the a blockchain node 106 in the blockchain network 104 using a suitable communication network and method.

The blockchain node 106 can receive the EventCount value and, in step 306, add the EventCount value to a blockchain associated with the blockchain network 104 that includes the blockchain node 106, where the EventCount can be included in a blockchain data entry that also includes timestamp data for the predetermined period of time. In step 308, the subscriber system 110 can read the EventCount for the predetermined period of time from the blockchain. In step 310, the subscriber system 110 can identify the number of event messages consumed from the event messages published by the processing server 102 on the event platform 108 during the predetermined period of time. In step 312, the subscriber system 110 can submit the AuditCount value to a blockchain node 106 in the blockchain network 104. The blockchain node 106 can receive the AuditCount value and, in step 314, add the AuditCount value to the blockchain, where the AuditCount can be included in a blockchain data entry that also includes timestamp data for the predetermined period of time.

In step 316, the processing server 102 can read the AuditCount for the predetermined period of time from the blockchain. In step 318, the validation module 220 of the processing server 102 can compare the EventCount and AuditCount values and determine that the AuditCount value is below the EventCount value, indicating that the subscriber system 110 missed one or more of the event messages published during the predetermined period of time. In step 320, the transmitting device 224 of the processing server 102 can transmit a list of EventIDs for all of the event messages published during the predetermined period of time to the blockchain node 106. In step 322, the blockchain node 106 can receive the EventIDs and add the EventIDs to the blockchain, where the EventIDs can be included in a blockchain data entry that also includes timestamp data for the predetermined period of time. In step 324, the subscriber system 110 can read the list of EventIDs from the blockchain. In step 326, the subscriber system 110 can use the list of EventIDs and stored data regarding consumed event messages to identify one or more EventIDs corresponding to event messages missed by the subscriber system 110 during the predetermined period of time and generate a list of the EventIDs for the missed event message(s), referred to herein as MissedIDs. In step 328, the subscriber system 110 can submit the MissedIDs to the blockchain node 106 using a suitable communication network and method.

In step 330, the blockchain node 106 can receive the MissedIDs and add the MissedIDs to the blockchain, where the MissedIDs can be included in a blockchain data entry that also includes timestamp data for the predetermined period of time. In step 332, the processing server 102 can read the MissedIDs from the blockchain. In step 334, the querying module 216 of the processing server 102 can execute one or more queries on the event database 206 of the processing server 102 to identify event messages for the missed events 208 using the MissedIDs read from the blockchain. In step 336, the transmitting device 224 of the processing server 102 can electronically transmit the identified event messages for the missed events for delivery to the subscriber system 110 via a message broker. The result of the process 300 is that the subscriber system 110 can always ensure that all event messages are consumed and where all participants in the system 100 can ensure consumption of all event messages and auditing of the publishing and consumption of event messages for accuracy.

Exemplary Method for Reconciliation of Published Events

FIG. 4 illustrates a method 400 for reconciliation of published events via use of a blockchain to ensure all published event messages during a period of time are consumed by a subscriber in a pub-sub architecture.

In step 402, a plurality of events (e.g., events 208) can be published on an event platform (e.g., event platform 108) by a processing server (e.g., processing server 102) during a period of time. In step 404, a numerical count of the plurality of events published on the event platform (e.g., EventCount) during the period of time can be transmitted by a transmitter (e.g., transmitting device 224) of the processing server to a blockchain node (e.g., blockchain node 106) of a blockchain network (e.g., blockchain network 104) for adding to a blockchain.

In step 406, a first block on the blockchain that includes a number of event consumed on the event platform (e.g., AuditCount) during the period of time can be received by a receiver (e.g., receiving device 202) of the processing server, wherein the number of events consumed is less than the numerical count of the plurality of events. In step 408, event data for each of one or more of the plurality of events published on the event platform during the period of time can be generated by a processor (e.g., querying module 216, generation module 218, etc.) of the processing server. In step 410, the generated event data can be transmitted by the transmitter of the processing server to the blockchain node of the blockchain network for adding to the blockchain.

In one embodiment, the method 400 can further include: receiving, by the receiver of the processing server, a second block on the blockchain that includes a list of a subset of events (e.g., MissedIDs) of the plurality of events; identifying, by the processor of the processing server, each event of the plurality of the subset of events on the list of events; and transmitting, by the transmitter of the processing server, the identified events. In a further embodiment, the event data for each of the one or more of the plurality of events can include an event identifier, and the list of the subset of events can include the event identifier for each event of the subset of events. In another further embodiment, the identified events can be transmitted to a third party system (e.g., subscriber system 110). In an even further embodiment, the identified events can be transmitted to the third party system via the event platform. In another even further embodiment, the second block can include identifying information for the third party system.

In some embodiments, the first block can further include an event identifier associated with each event consumed on the event platform during the period of time, and the one or more of the plurality of events can include events associated with an event identifier not included in the first block. In one embodiment, the method 400 can also include determining, by the processor of the processing server, that the number of events consumed on the event platforms is less than the numerical count of the plurality of events prior to generating the event data.

Computer System Architecture

FIG. 5 illustrates a computer system 500 in which embodiments of the present disclosure, or portions thereof, can be implemented as computer-readable code. For example, the processing server 102, blockchain nodes 106, event platform 108, and subscriber system 110 can be implemented in the computer system 500 using hardware, non-transitory computer readable media having instructions stored thereon, or a combination thereof and can be implemented in one or more computer systems or other processing systems. Hardware can embody modules and components used to implement the methods of