Mobile Apparatus Event Verification via Distributed Ledger

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized management systems for IoT-based event information sharing face challenges in validating reliability, responding to state changes, and managing operational costs, with risks of information manipulation and high operational costs.

Innovation Solution

A distributed ledger system where mobile apparatus verify incident events and publish verified information, creating event management blocks for reward distribution among subscribers, eliminating the need for trusted third parties and enhancing reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If centralized management is used for event information sharing, then information can be managed in a unified manner, but operational costs become considerably high and reliability cannot be ensured due to lack of validation mechanism

Engineering Contradiction:
Improveunified information managementVSAvoidinformation validation capability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The centralized management system is segmented into distributed nodes (mobile apparatus) that each independently verify and validate event information. Instead of one central authority, multiple distributed participants collectively ensure information reliability through cryptographic verification and consensus mechanisms, eliminating the single point of failure while maintaining unified information management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A blockchain-based distributed ledger acts as an intermediary between information providers and subscribers. This intermediary enables trustless verification of event information through cryptographic proofs and smart contracts, allowing reliable information sharing without requiring traditional trusted third parties or centralized validation authorities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If centralized service provider platform is used, then information can be managed centrally, but response time to state changes is delayed and operational costs are high

Engineering Contradiction:
Improvecentralized information managementVSAvoidresponse speed to state changes
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The centralized platform is divided into autonomous mobile apparatus nodes that independently monitor and detect incident events. Each node can immediately detect and validate local events without waiting for central platform processing, enabling real-time response to state changes while maintaining distributed operation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Mobile apparatus nodes autonomously verify event information using onboard sensors and cryptographic validation capabilities. Each node independently validates event data and publishes verified information to the distributed ledger without requiring central platform intervention, enabling self-service operation and immediate response to detected events.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If centralized management is implemented, then information can be managed in one place, but the system becomes vulnerable to information manipulation and requires high operational costs

Engineering Contradiction:
Improvecentralized management capabilityVSAvoidinformation manipulation risk
Core Design Contradiction:
Ease of operationVSObject-generated harmful factors

Solution Approach 1:

The centralized management function is distributed across multiple autonomous nodes that each independently validate event information. This segmentation prevents any single entity from manipulating information, as changes require consensus across the distributed network. Each node maintains cryptographic proofs of event authenticity, making manipulation detectable and preventable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The blockchain distributed ledger serves as an immutable intermediary that records all event information and verification processes. This intermediary prevents information manipulation by providing cryptographic verification of event data and maintaining an immutable audit trail that cannot be altered without detection, eliminating the vulnerability to manipulation inherent in centralized systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If distributed ledger technology is used for event information sharing, then reliability and security are improved, but device complexity increases

Engineering Contradiction:
Improveinformation verification capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The blockchain distributed ledger acts as an intermediary layer that handles complex verification and consensus operations. Mobile apparatus nodes interact with this intermediary through standardized interfaces, which abstract away the underlying cryptographic and consensus complexity. The intermediary manages the complex tasks of validation, consensus reaching, and immutable record-keeping, while presenting a simple interface to participating devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10310918B2Information sharing among mobile apparatus
Publication Date: 2019.06.04 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10310918B2 patent drawing
  • US10310918B2 patent drawing
  • US10310918B2 patent drawing

AI summary

A method executed by a mobile apparatus for verifying event information to be shared is disclosed. The method includes communicating with a nearby mobile or immobile apparatus to generate a verification in response to encountering the nearby mobile or immobile apparatus. The method also includes verifying existence of an incident event in response to arriving at a place of the incident event. The method further includes publishing a verified incident event in order to add into an incident event distributed ledger used for managing event information related to the incident event.