Common database architecture to support largescale transactions and node archival on a MaaS platform

1. A system, comprising:

a plurality of node packages, wherein

each node package of the plurality of node packages includes a subscriber node of a first Mobility-as-a-Service (MaaS) network, and a MaaS node; and

a first subscriber node of a first node package of the plurality of node packages receives a transaction message;

an aggregator database node communicatively coupled to each of the plurality of node packages; and

an archival database node communicatively coupled to the aggregator database node, wherein a first MaaS node of the first node package of the plurality of node packages is configured to:

select a first set of transaction records from a first plurality of transaction records stored on the first MaaS node, wherein

a transaction record of the first plurality of transaction records is included in a first set of state objects,

a state object in the first set of state objects includes at least a first smart contract,

the selection of the first set of transaction records is based on a first data retention threshold and a first storage duration of each of the first plurality of transaction records on the first MaaS node, and

each of the first plurality of transaction records is associated with the transaction message received by the first subscriber node of the first node package;

transmit the selected first set of transaction records with the first set of state objects to the aggregator database node for storage at the aggregator database node;

invalidate the selected first set of transaction records from the first MaaS node based on the transmission of the selected first set of transaction records to the aggregator database node by the first smart contract included in the transmitted first set of state objects;

control a selection, by the aggregator database node, of a second set of transaction records from a third set of transaction records stored on the aggregator database node, where the selected second set of transaction records is generated by a second smart contract from the second set of state objects, wherein

a transaction record of the third set of transaction records is included in a second set of state objects,

a state object in the second set of state objects includes at least the second smart contract,

the selection of the second set of transaction records is based on a second data retention threshold and a second storage duration of each of the third set of transaction records on the aggregator database node, and

the third set of transaction records stored on the aggregator database node comprises at least the first set of transaction records; and

control a transmission of the selected second set of transaction records to the archival database node, where the selected second set of transaction records is generated by the second smart contract from the second set of state objects, to minimize a delay in processing of transactions associated with transaction records stored on the first MaaS node for storage at the archival database node.

2. The system according to claim 1 , wherein the first MaaS node is further configured to:

compare the first storage duration of each of the first plurality of transaction records on the first MaaS node with the first data retention threshold; and

select the first set of transaction records from the first plurality of transaction records based on the comparison.

3. The system according to claim 1 , wherein the first MaaS node is further configured to:

control a comparison of the second storage duration of each of the third set of transaction records on the aggregator database node with the second data retention threshold; and

control a selection of the second set of transaction records from the third set of transaction records based on the comparison.

4. The system according to claim 1 , wherein the first MaaS node is further configured to control an invalidation of the selected second set of transaction records from the aggregator database node based on the transmission of the selected second set of transaction records to the archival database node.

5. The system according to claim 1 , wherein the subscriber node of each of the plurality of node packages is associated to the first MaaS network through a plug-in interface, wherein the plug-in interface comprises at least one of:

a network protocol handler plug-in,

security plug-in,

a data scheme and data quality check plugin,

a monitor and alert plug-in,

a transaction management plug-in,

a transaction error handling plug-in, or

a concurrent thread management plug-in.

6. The system according to claim 1 , wherein one or more of the plurality of node packages comprise the subscriber node, a plurality of MP nodes of a first distributed ledger, and the MaaS node of a second distributed ledger.

7. The system according to claim 6 , wherein each of the plurality of MP nodes is associated with a separate mobility provider of the first MaaS network.

8. The system according to claim 1 , further comprising a first server associated with each of the aggregator database node and the archival database node, wherein the first server is configured to:

transmit, to the aggregator database node, a query for one or more first transaction records stored on the aggregator database node;

receive, from the aggregator database node, the queried one or more first transaction records; and

verify one or more transactions associated with the queried one or more first transaction records.

9. The system according to claim 8 , wherein the first server is further configured to:

transmit, to the archival database node, a query for one or more second transaction records stored on the archival database node; and

receive, from the archival database node, the queried one or more second transaction records; and

display statistical information associated with the queried one or more second transaction records.

10. The system according to claim 9 , further comprising a cache database node, wherein the cache database node is further configured to:

receive, from the archival database node, the queried one or more second transaction records;

store the received one or more second transaction records on the cache database node;

receive, from the first server, a query for one or more third transaction records from the one or more second transaction records stored on the cache database node; and

transmit, to the first server, the one or more third transaction records based on the received query for the one or more third transaction records.

11. The system according to claim 1 , wherein the aggregator database node and the archival database node are distributed ledger nodes related to the first MaaS network.

12. The system according to claim 1 , wherein the aggregator database node and the archival database node are non-distributed ledger nodes related to the first MaaS network.

13. The system according to claim 1 , wherein the second data retention threshold is greater than the first data retention threshold.

14. The system according to claim 1 , wherein the second data retention threshold is lower than the first data retention threshold.

15. A method, comprising:

in a system comprising

a plurality of node packages, wherein

each node package of the plurality of node packages includes a subscriber node of a first Mobility-as-a-Service (MaaS) network, and a MaaS node; and

a first subscriber node of a first node package of the plurality of node packages receives a transaction message;

an aggregator database node communicatively coupled to each of the plurality of node packages; and

an archival database node communicatively coupled to the aggregator database node:

selecting, by a first MaaS node of the first node package of the plurality of node packages, a first set of transaction records from a first plurality of transaction records stored on the first MaaS node, wherein

a transaction record of the first plurality of transaction records is included in a first set of state objects,

a state object in the first set of state objects includes at least a first smart contract,

the selection of the first set of transaction records is based on a first data retention threshold and a first storage duration of each of the first plurality of transaction records on the first MaaS node, and

each of the first plurality of transaction records is associated with the transaction message received by the first subscriber node of the first node package;

transmitting, by the first MaaS node, the selected first set of transaction records with the first set of state objects to the aggregator database node for storage at the aggregator database node;

invalidating, by the first MaaS node, the selected first set of transaction records from the first MaaS node based on the transmission of the selected first set of transaction records to the aggregator database node by the first smart contract included in the transmitted first set of state objects;

controlling, by the first MaaS node, a selection, by the aggregator database node, of a second set of transaction records from a third set of transaction records stored on the aggregator database node, where the selected second set of transaction records is generated by a second smart contract from the second set of state objects, wherein

a transaction record of the third set of transaction records is included in a second set of state objects,

a state object in the second set of state objects includes at least the second smart contract,

the selection of the second set of transaction records is based on a second data retention threshold and a second storage duration of each of the third set of transaction records on the aggregator database node, and

the third set of transaction records stored on the aggregator database node comprises at least the first set of transaction records; and

controlling, by the first MaaS node, a transmission of the selected second set of transaction records to the archival database node, where the selected second set of transaction records is generated by the second smart contract from the second set of state objects, to minimize a delay in processing of transactions associated with transaction records stored on the first MaaS node for storage at the archival database node.

16. The method according to claim 15 , further comprising:

comparing, by the first MaaS node, the first storage duration of each of the first plurality of transaction records on the first MaaS node with the first data retention threshold; and

selecting, by the first MaaS node, the first set of transaction records from the first plurality of transaction records based on the comparison.

17. The method according to claim 15 , further comprising:

controlling, by the first MaaS node, a comparison of the second storage duration of each of the third set of transaction records on the aggregator database node with the second data retention threshold; and

controlling, by the first MaaS node, a selection of the second set of transaction records from the third set of transaction records based on the comparison.

18. A non-transitory computer-readable medium having stored thereon, computer-executable instructions that when executed by a system including an aggregator database node, an archival database node, and a plurality of node packages, wherein each node package of the plurality of node packages includes a subscriber node of a first Mobility-as-a-Service (MaaS) network, and a MaaS node, causes the system to execute operations, the operations comprising:

selecting, by a first MaaS node of a first node package of the plurality of node packages, a first set of transaction records from a first plurality of transaction records stored on the first MaaS node, wherein

a transaction record of the first plurality of transaction records is included in a first set of state objects,

a state object in the first set of state objects includes at least a first smart contract,

the selection of the first set of transaction records is based on a first data retention threshold and a first storage duration of each of the first plurality of transaction records on the first MaaS node,

a first subscriber node of the first node package receives a transaction message, and

each of the first plurality of transaction records is associated with the transaction message received by the first subscriber node of the first node package;

transmitting, by the first MaaS node, the selected first set of transaction records with the first set of state objects to the aggregator database node for storage at the aggregator database node;

invalidating, by the first MaaS node, the selected first set of transaction records from the first MaaS node based on the transmission of the selected first set of transaction records to the aggregator database node by the first smart contract included in the transmitted first set of state objects;

controlling, by the first MaaS node, a selection, by the aggregator database node, of a second set of transaction records from a third set of transaction records stored on the aggregator database node, where the selected second set of transaction records is generated by a second smart contract from the second set of state objects, wherein

a transaction record of the third set of transaction records is included in a second set of state objects,

a state object in the second set of state objects includes at least the second smart contract,

the selection of the second set of transaction records is based on a second data retention threshold and a second storage duration of each of the third set of transaction records on the aggregator database node, and

the third set of transaction records stored on the aggregator database node comprises at least the first set of transaction records; and

controlling, by the first MaaS node, a transmission of the selected second set of transaction records to the archival database node, where the selected second set of transaction records is generated by the second smart contract from the second set of state objects, to minimize a delay in processing of transactions associated with transaction records stored on the first MaaS node for storage at the archival database node.