MUD File Management with Blockchain Tracking for Predictive Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network management systems for IoT devices lack a secure and efficient mechanism for managing and updating Manufacturer Usage Description (MUD) files, leading to potential device misconfiguration and network inefficiencies due to outdated or mismatched MUD files.

Innovation Solution

Utilizing a blockchain to store and manage MUD files, enabling secure tracking, updating, and predictive analytics to anticipate and mitigate the impact of MUD file changes, ensuring network controllers can learn from past experiences and optimize network configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If MUD files are managed using traditional file servers or URLs, then devices can obtain MUD files over the network, but the MUD files may become outdated or mismatched leading to device misconfiguration

Engineering Contradiction:
ImproveMUD file accuracyVSAvoidtime to detect outdated MUD files
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements feedback mechanisms where network controllers continuously monitor and verify MUD file versions against device configurations. When MUD files are updated on the blockchain, the system automatically notifies relevant devices and verifies that they have obtained the updated files, creating a closed-loop feedback system that prevents outdated configurations from persisting in the network.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The blockchain stores MUD files and their version information in advance, allowing network controllers to proactively verify device configurations before misconfiguration occurs. The system performs preliminary checks to ensure devices have the correct MUD files before they are deployed or updated, preventing rather than detecting problems.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If MUD files are updated frequently to maintain accuracy, then device configuration reliability improves, but network disruptions increase due to updates and reconfigurations

Engineering Contradiction:
ImproveMUD file currencyVSAvoidnetwork disruptions
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system dynamically adjusts MUD file update strategies based on network conditions and device criticality. Network controllers can schedule updates during low-traffic periods, prioritize updates for critical devices, and implement gradual rollouts that allow rollback if issues occur. The blockchain's immutable ledger allows for version comparison and selective application of updates.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system prepares for potential update issues by maintaining multiple MUD file versions on the blockchain and implementing rollback mechanisms. Before applying updates, the system creates backup configurations and monitors device performance closely, allowing quick reversal if problems arise. This cushioning approach minimizes the impact of necessary updates.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Device complexity

If manual MUD file management is used, then implementation is simple, but security vulnerabilities and misconfigurations increase

Engineering Contradiction:
ImproveMUD file management systemVSAvoidnetwork security
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The blockchain acts as an intermediary layer between MUD file creators and network controllers. It provides a decentralized, tamper-proof repository that eliminates the need for complex centralized file management systems while enhancing security. The blockchain's cryptographic verification mechanisms ensure that only authorized MUD files are stored and distributed, automatically validating file integrity without requiring complex manual verification procedures.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4270229B1Device descriptor file management with predictive capability
Publication Date: 2025.09.03 BRITISH TELECOM PLC
  • EP4270229B1 patent drawingFigure 1
  • EP4270229B1 patent drawingFigure 2

AI summary

A method of managing a network of connected network devices comprising steps of: detecting that a device descriptor file for a first network device has been updated and stored to a data store managed by a peer-to-peer network of computing systems; analysing the updated device descriptor file stored to the data store; analysing historical information stored in the data store regarding other device descriptor file updates related to the first network device or related to other network devices; performing predictive analytics processing on the results of the analysing steps and generating a result; and storing the result of the performing predictive analytics processing step to the data store.