Transportation Network Data Consistency via Distributed Ledger

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Transportation networks face challenges in maintaining data consistency across independent and incompatible electronic routing systems, leading to fragmented and inaccurate asset transfer data, which is exacerbated by the lack of a unified platform and the impracticality and cost of repurposing or replacing existing routing platforms.

Innovation Solution

A distributed ledger system is employed to verify and store asset transfer transactions, using smart contracts and digital signatures to ensure data consistency and accuracy across disparate transportation hubs, allowing each hub to maintain independent routing platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a unified electronic routing platform is implemented to coordinate operations across transportation hubs, then data consistency is improved, but device complexity and implementation cost increase significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidplatform complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the transportation network into independent transportation hubs, each maintaining its own routing platform. A distributed ledger system is introduced as a separate layer to coordinate between hubs without requiring integration of the hubs' internal systems. This segmentation allows data consistency across hubs while preserving the independence and simplicity of each hub's internal operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A distributed ledger acts as an intermediary between independent transportation hubs. Each hub's routing platform continues to operate independently, but asset transfers are recorded and verified on the distributed ledger. This intermediary layer ensures data consistency without requiring direct integration or communication protocols between different hub systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If existing routing platforms are repurposed or replaced to achieve unity, then data consistency is improved, but implementation cost and time increase

Engineering Contradiction:
Improvedata consistencyVSAvoidimplementation ease
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The system merges the functionality of existing independent routing platforms with a new distributed ledger system. Rather than replacing or repurposing existing platforms, the distributed ledger is added as a complementary layer that captures and coordinates asset transfer information from each hub's existing system, preserving investment in existing infrastructure while achieving data consistency.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The distributed ledger is established in advance as a coordination mechanism before asset transfers occur. By pre-configuring the ledger with the necessary smart contracts and verification protocols, the system enables immediate data consistency upon deployment without requiring gradual reconfiguration of existing platforms.

Inventive Principle:
Principle #10Preliminary action

3Ease of manufacture

If independent routing systems are maintained at each transportation hub, then implementation cost is reduced, but data consistency and accuracy deteriorate

Engineering Contradiction:
Improveimplementation costVSAvoiddata consistency
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system segments the network into independent hubs that each maintain their own routing platforms, preserving the cost benefits of independent operation. The distributed ledger is introduced as a separate coordination layer that does not require modification of each hub's internal systems, thus maintaining low implementation cost while achieving data consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The distributed ledger serves as an intermediary that receives asset transfer information from independent hub systems and ensures consistency across the network. This intermediary approach allows hubs to remain independent and inexpensive to operate while the ledger provides the coordination needed for data consistency.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Device complexity

If asset transfer information is communicated between routing systems through conventional channels, then system simplicity is maintained, but data loss and unreliability increase

Engineering Contradiction:
Improvesystem simplicityVSAvoiddata accuracy
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The distributed ledger acts as a reliable intermediary for asset transfer information. Instead of relying on conventional communication channels that may lose or corrupt data, each hub's routing system communicates transfer information to the distributed ledger, which provides guaranteed delivery, verification, and permanent recording of asset transfer data.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The distributed ledger provides feedback mechanisms through smart contracts that verify asset transfer information before recording it. This feedback loop ensures data accuracy by validating transfers against predefined rules and providing confirmation to the originating hub, eliminating data loss while maintaining system simplicity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12417427B2Enforcing data consistency in a transportation network
Publication Date: 2025.09.16 UNITED PARCEL SERVICE OF AMERICAN INC
  • US12417427B2 patent drawing
  • US12417427B2 patent drawing
  • US12417427B2 patent drawing

AI summary

Systems and methods are described for enforcing consistency of data between disparate systems of a transportation network with verified transactions. Embodiments include receiving a transaction that is generated based on a command indicating an intent to transfer an asset from the originating hub to a destination hub. The generated transaction can include a sender identifier associated with the originating hub, an asset identifier associated with the asset, and a detected location of the asset. The received transaction is communicated to any node of the plurality of nodes that are configured store it onto a distributed ledger based on a determined verification that the included detected location corresponds to a location associated with the included sender identifier.