Blockchain Freight Data Sharing with Role-Based Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication systems in the freight shipping industry face challenges in sharing confidential data among competing companies while ensuring timely updates and data privacy, particularly due to variations in communication protocols and geographic distribution, which hinders efficient coordination and tracking of intermodal containers and project cargo.

Innovation Solution

A system utilizing a blockchain-based distributed ledger with encryption technologies to securely share data among multiple parties, where each party's access is controlled based on their assigned role, allowing only necessary information to be shared while maintaining confidentiality and enabling real-time tracking and updates of freight shipments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional point-to-point communication protocols are used among freight shipping parties, then each party can maintain control over their own data, but communication delays occur and multiple parties cannot be kept in the loop simultaneously

Engineering Contradiction:
Improvedata controlVSAvoidcommunication delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent merges multiple point-to-point communication channels into a single blockchain-based distributed ledger system. All parties (shippers, carriers, ports, customs, etc.) connect to the same decentralized network, enabling simultaneous data sharing across multiple participants without sequential communication delays.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The blockchain network acts as a neutral intermediary that facilitates direct peer-to-peer communication between all parties. Smart contracts serve as automated intermediaries that enforce business rules and data sharing protocols without requiring manual intervention or coordination between individual parties.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If competing companies share resources and coordinate activities to achieve economies of scale, then service coverage and efficiency improve, but confidential information such as customer lists and pricing data must be disclosed

Engineering Contradiction:
Improvecoordination efficiencyVSAvoidconfidential data protection
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The blockchain system implements role-based access control where different parties have different levels of data visibility based on their specific needs. For example, a carrier can see shipping routes and schedules but not customer contact information, while a forwarder can see pricing data but not competitor pricing. Each participant receives only the specific data attributes necessary for their function.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments data into discrete attributes with granular access permissions. Instead of sharing entire datasets, the system divides information into individual data fields (e.g., container ID, routing information, pricing, customer details) and assigns access rights to specific attributes based on party roles and permissions defined in smart contracts.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If geographic distribution of parties is accommodated with traditional communication systems, then each party operates independently, but communication timeliness decreases due to business hour variations and protocol differences

Engineering Contradiction:
Improvegeographic flexibilityVSAvoidcommunication speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The blockchain network operates continuously without interruption by business hours or time zones. The decentralized ledger maintains constant synchronization across all nodes globally, enabling real-time data updates and access 24/7 regardless of local operating hours. Smart contracts execute automatically without human intervention, eliminating delays caused by manual processing across different time zones.

Inventive Principle:
Principle #20Continuity of useful action

4Reliability

If encryption technologies are implemented to protect confidential information, then data privacy is maintained, but system complexity increases

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

Solution Approach 1:

The blockchain system implements automated encryption and decryption through smart contracts that execute based on predefined access rules. When a party requests data, the smart contract automatically verifies permissions and provides decryption keys without manual intervention. This self-service approach eliminates the need for complex key management infrastructure and manual encryption operations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements a universal encryption framework where a single cryptographic protocol handles multiple functions: data encryption at rest, secure transmission between nodes, access control verification, and audit logging. This multi-functional approach reduces system complexity compared to implementing separate encryption systems for each function.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11763011B2Zero trust communication system for freight shipping organizations, and methods of use
Publication Date: 2023.09.19 OOCL INFOTECH HLDG LTD
  • US11763011B2 patent drawing
  • US11763011B2 patent drawing
  • US11763011B2 patent drawing

AI summary

Presented herein are systems and methods of securely sharing data from multiple sources with different client terminals. A server may establish an electronic document for defining a transaction. The electronic document may have data fields. Each data field may be from a client terminal. The server may identify encryption keys to encrypt the corresponding data fields included in the electronic document. The server may distribute the encryption keys across the client terminals in accordance with an access control policy. The access control policy may specify access permissions for a client terminal to each of the plurality of data fields based on a role of the client terminal in the transaction. The server may provide, to each client terminal with access to the data fields in the electronic document via the encryption keys distributed in accordance with the access control policy.