Distributed Error Data Storage in Networked Embedded Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In networked embedded systems, detecting and locating error and diagnostic data is time-consuming and labor-intensive, especially when components store their data locally, and accessing this data becomes impossible during failures or malfunctions, leading to incomplete diagnoses and recurrent failures.

Innovation Solution

Storing error and diagnostic data redundantly across multiple components in a networked embedded system, using a distributed hash table for efficient retrieval, and implementing a heartbeat protocol for quick failure detection, allowing data to be accessed even if a component fails or becomes unreachable.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If error data is stored in a centralized storage facility, then data availability is improved, but system complexity and cost increase

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

Solution Approach 1:

The patent segments the centralized storage function by distributing error data storage across multiple individual components in the network. Each component stores error data locally in its own memory, eliminating the need for a centralized storage facility while maintaining data availability through decentralized redundancy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements copying by storing identical error data sets across multiple components. When a component fails, its error data can be retrieved from other components that have stored copies, ensuring data availability without requiring complex centralized storage infrastructure.

Inventive Principle:
Principle #26Copying

2Device complexity

If error data is stored in individual components, then system simplicity is improved, but data accessibility deteriorates when components fail

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

Solution Approach 1:

The patent applies preliminary action by having components store error data from other components in their own memory before those components fail. This proactive data distribution ensures that when a component fails, its error data is already available in other components, eliminating the accessibility problem.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements beforehand cushioning by creating redundant copies of error data across multiple components. This cushioning against component failure ensures that even if a component fails completely, the error data remains accessible through other components that have stored copies in advance.

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

3Extent of automation

If components send data to centralized storage, then data collection is automated, but data loss occurs when connection fails

Engineering Contradiction:
Improvedata collection automationVSAvoiddata loss
Core Design Contradiction:
Extent of automationVSLoss of information

Solution Approach 1:

The patent implements self-service by enabling each component to autonomously store error data in its own memory without requiring communication with a centralized storage facility. This eliminates the dependency on network connections for data storage, preventing data loss when connections fail while maintaining automated data collection at the component level.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8181070B2Error detection in a networked embedded system
Publication Date: 2012.05.15 NETCONNECT WIRELESS LLC
  • US8181070B2 patent drawing
  • US8181070B2 patent drawing
  • US8181070B2 patent drawing

AI summary

A method for detecting errors in a networked embedded system having a multiplicity of components. Error and/or diagnostic data which are relevant to a component are stored in a set of further components of the networked embedded system and are determined if necessary (for example if a disturbance, error or failure occurs). This method is used, in particular, to find error and/or diagnostic data relating to a failed component of a networked embedded system.