Software Module Integrity via Distributed Ledger Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of software supply chains makes it difficult to track and verify the authenticity of software modules, leading to unclear relationships among modules and potential tampering issues, which complicates vulnerability detection and updates.

Innovation Solution

A system using a distributed ledger platform to store module information, including unique values and dependence relationships, generates software information that includes a tree diagram to visualize these relationships and verify authenticity, ensuring tamper-proof integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If module information is stored in a centralized database, then data access and management become simpler, but the system becomes vulnerable to tampering and loses transparency in the supply chain

Engineering Contradiction:
Improveintegrity of software module informationVSAvoidcomplexity of information storage system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments module information into two distinct types: dependence relationship information (stored in centralized database) and unique value information (stored in distributed ledger). This segmentation allows each storage system to handle the type of data it is best suited for, improving overall reliability while managing complexity through functional separation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a server device as an intermediary that coordinates between the centralized database and the distributed ledger. The server manages the separation of information storage, handling dependence relationships in the database and unique values in the ledger, thereby resolving the contradiction between centralized management simplicity and distributed security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If all module information is stored in a distributed ledger, then tamper-proof integrity is achieved, but storage efficiency and access speed decrease

Engineering Contradiction:
Improvetamper-proof integrity of software modulesVSAvoidefficiency of information access and processing
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments information storage between centralized database and distributed ledger based on data type. Dependence relationship information that requires frequent access is stored in the centralized database for efficient retrieval, while unique value information requiring tamper-proof storage is placed in the distributed ledger, optimizing both integrity and efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies distributed ledger technology partially - only for storing unique value information rather than all module information. This partial application achieves tamper-proof integrity for critical authentication data while avoiding the performance penalties of storing all data in the distributed ledger.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of information

If complete software module information is provided to all entities in the supply chain, then transparency is improved, but information security and access control become problematic

Engineering Contradiction:
Improvetransparency of software supply chainVSAvoidunauthorized access to sensitive module information
Core Design Contradiction:
Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by providing different information to different entities in the supply chain based on their roles and authorization. Each entity receives the specific module information they need for their function, achieving transparency where required while maintaining security through role-based information distribution.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The server device acts as an intermediary that controls information distribution to entities in the supply chain. It manages access rights and determines what module information each entity can access, thereby achieving both transparency for authorized parties and security against unauthorized access.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If module information is divided and stored separately, then security and tamper-detection are improved, but system complexity and integration difficulty increase

Engineering Contradiction:
Improvedetection of tampered software modulesVSAvoidcomplexity of information management system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments module information into dependence relationship information and unique value information, storing them in separate systems (centralized database and distributed ledger respectively). This segmentation improves tamper-detection capability while managing complexity through clear functional separation of the two storage systems.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements feedback mechanisms where the server device continuously verifies the consistency between dependence relationship information in the database and unique value information in the distributed ledger. This feedback system automatically detects tampering and maintains system integrity, reducing the operational complexity of managing separate storage systems.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250208845A1Information processing device and information processing method
Publication Date: 2025.06.26 TOYOTA JIDOSHA KK
  • US20250208845A1 patent drawing
  • US20250208845A1 patent drawing
  • US20250208845A1 patent drawing

AI summary

Module information about software modules constituting first software and produced by one or more first companies included in a supply chain of the first software is received from a terminal corresponding to the first companies. Different parts of the module information are stored in a storage device and a distributed ledger that uses a block chain platform. Software information including information about one or more software modules constituting the first software is generated based on one or more pieces of the module information stored in the storage device and the distributed ledger. The software information is transmitted to a terminal corresponding to a second company.