IoT Gateway ID Space Conversion for Device Configuration Accuracy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In IoT systems, existing devices without connection functions can be incorrectly configured when manually set, leading to incorrect data acquisition and analysis, as the correspondence between physical IDs and system IDs may not be maintained correctly, especially during device connection, disconnection, or re-connection, causing overlapping system IDs and erroneous device configurations.

Innovation Solution

An ID space conversion system that uses a gateway to convert physical IDs to system IDs, ensuring non-overlapping and unique system IDs by grouping devices based on regional locality or owner attributes, and verifying device configurations against design definitions to ensure correct data acquisition and analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual configuration is used for existing devices without connection functions, then device integration is achieved, but configuration errors occur leading to incorrect data acquisition

Engineering Contradiction:
Improvedevice integrationVSAvoidconfiguration accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by automatically generating device configurations based on device information before data acquisition occurs. The configuration generation unit creates initial configurations using device identifiers and type information, which are then verified against design definitions to prevent errors before they affect data acquisition.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The verification unit provides feedback by checking generated configurations against design definitions and notifying operators of any errors. This feedback loop ensures that configuration errors are detected and corrected, maintaining reliability while enabling device integration.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If physical IDs are converted to system IDs without verification, then data acquisition is simplified, but ID correspondence errors occur

Engineering Contradiction:
Improvedata acquisitionVSAvoidID correspondence accuracy
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The system performs preliminary verification of ID correspondence by checking generated system IDs against design definitions before data acquisition begins. This ensures that the mapping between physical IDs and system IDs is accurate, maintaining measurement precision while simplifying the data acquisition process.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If device configurations are not verified against design definitions, then system complexity is reduced, but statistical processing accuracy deteriorates

Engineering Contradiction:
Improveconfiguration managementVSAvoidstatistical processing accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The system applies partial verification by checking only critical configuration elements against design definitions, such as device identifiers and component mappings. This selective approach maintains statistical processing accuracy without requiring complete verification of all configuration parameters, thus managing device complexity effectively.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3617876B1Id space conversion system and method
Publication Date: 2023.07.05 NIPPON TELEGRAPH & TELEPHONE CORP
  • EP3617876B1 patent drawingFigure 1
  • EP3617876B1 patent drawingFigure 2
  • EP3617876B1 patent drawingFigure 3

AI summary

Provided is an ID space conversion system enabling an application to access a correct data resource by using a system ID. An ID space conversion function unit 23 generates a non-overlapping unique system ID for each type of components based on a physical ID of a component included in a device D which is determined to be a correct device by a device configuration verification function unit 22. A sharing function unit 24 shares, with a gateway 25, a gateway file f2 including a correspondence relationship between the physical ID and the system ID included in the device D. Accordingly, the gateway 25 adds, to data, the system ID, on the basis of the gateway-setting file f2, and outputs system ID-added data to a network. A data processing unit 26 determines whether component data of the device D includes the generated system ID. Accordingly, it is determined whether the data is output from the correct device D.