Common Database Architecture for MaaS Transaction Archival

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobility-as-a-Service (MaaS) platforms face challenges in managing and storing large volumes of transaction records due to high transaction message flows, leading to operational slowdowns and cumbersome data management, especially in distributed ledger systems.

Innovation Solution

A system and method utilizing a common database architecture to support large-scale transactions and node archival, involving a network environment with subscriber nodes, mobility provider nodes, and distributed ledger nodes, where transaction records are aggregated, archived, and stored based on retention thresholds, minimizing storage on individual nodes and optimizing data retention across different databases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If transaction records are stored on distributed ledger nodes, then data integrity and decentralization are maintained, but storage burden and operational slowdown increase

Engineering Contradiction:
Improvedata integrityVSAvoidoperational speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments transaction records into two categories: immutable records stored on distributed ledger nodes for integrity, and archivable records transferred to centralized storage for operational efficiency. This segmentation allows the system to maintain data integrity on the ledger while improving operational speed by removing archived records from active nodes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts archived transaction records from distributed ledger nodes and stores them in centralized archival storage systems. This extraction reduces the storage burden on individual nodes and eliminates the operational slowdown caused by managing large volumes of historical data across the distributed network.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If historical transaction data is retained on distributed ledger nodes, then audit compliance is maintained, but node performance and scalability deteriorate

Engineering Contradiction:
Improveaudit complianceVSAvoidscalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a centralized archival storage system as an intermediary between distributed ledger nodes and historical transaction data. This mediator maintains audit compliance by preserving all transaction records while allowing ledger nodes to operate with reduced data burdens, thereby improving scalability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary archiving by automatically transferring transaction records to centralized storage before they burden the distributed ledger nodes. This preliminary action ensures compliance requirements are met while preventing performance degradation and enabling system scalability.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If multiple mobility providers use separate ticket processing infrastructures, then service independence is maintained, but data management complexity and transaction overhead increase

Engineering Contradiction:
Improveservice independenceVSAvoiddata management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the ticket processing infrastructures of multiple mobility providers into a unified distributed ledger system. This combination maintains service independence through modular node design while reducing data management complexity by providing a common platform for transaction processing and historical data storage.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11966400B2Common database architecture to support largescale transactions and node archival on a MaaS platform
Publication Date: 2024.04.23 SONY GROUP CORP
  • US11966400B2 patent drawing
  • US11966400B2 patent drawing
  • US11966400B2 patent drawing

AI summary

A system, including a plurality of node packages, an aggregator database node, and an archival database node, is provided. Each node package includes a subscriber node, an MP node, and a MaaS node. A first MaaS node selects a first set of transaction records from the first MaaS node based on a first data retention threshold and a first storage duration, and transmits the first set of transaction records to the aggregator database node for storage. The first MaaS node further controls a selection of a second set of transaction records from a third set of transaction records stored on the aggregator database node and controls a transmission of the second set of transaction records to the archival database node for storage. The selection of the second set of transaction records is based on a second data retention threshold and a second storage duration.