Fieldbus-IoT Interlinking via Virtual I/O Memory Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Interlinking conventional automatic control systems with IoT systems is complex and requires extensive knowledge and configuration, particularly due to the need for gateway devices that must conform fieldbus protocols to IoT protocols and manage different information systems.

Innovation Solution

An interlinking device and method that operates as a subordinate position device in both fieldbus-based automatic control systems and IoT systems, utilizing a fieldbus connection unit, fieldbus virtual input-output memory, IoT connection unit, message formation unit, and message processing unit to form and process variable input-output messages based on message metadata, simplifying the integration process by minimizing the need for extensive knowledge from integrators.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a gateway device is used to interlink conventional automatic control systems with IoT systems, then protocol conversion and information management are achieved, but device complexity and integration difficulty increase significantly

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidgateway configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a gateway device as an intermediary component that sits between the conventional automatic control system and the IoT system. This gateway performs protocol conversion by translating fieldbus protocols (such as Profibus, Modbus) into IoT protocols (such as MQTT, CoAP), enabling communication between incompatible systems without requiring changes to the existing control systems or IoT platforms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway device is designed with multi-functional capabilities to handle multiple fieldbus protocols and multiple IoT protocols simultaneously. It also provides additional functions including data formatting, quality of service management, and seamless integration with existing SCADA systems, making it a universal solution for various industrial automation scenarios.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If extensive configuration and coding tasks are performed for SCADA and operation devices, then system functionality is achieved, but integration time and technical knowledge requirements increase

Engineering Contradiction:
Improvesystem functionalityVSAvoidintegration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The gateway device performs preliminary actions by pre-configuring protocol conversion rules, data mapping relationships, and communication parameters before actual system integration. It comes with pre-built support for common fieldbus protocols and IoT protocols, eliminating the need for extensive on-site coding and configuration work during deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The gateway具备自我配置能力,可以通过自动发现机制识别连接的fieldbus设备和IoT平台,自动建立数据映射关系和通信参数。这种自服务功能大大减少了集成人员的手工配置工作,降低了技术知识要求,同时保持了系统的完整功能性。

Inventive Principle:
Principle #25Self-service

3Reliability

If message metadata registration is performed for each IoT device input-output information, then IoT system recognition is achieved, but configuration complexity increases

Engineering Contradiction:
Improveinformation recognition accuracyVSAvoidmessage metadata configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The gateway device creates standardized message metadata templates that replicate the essential information structures required by IoT platforms. Instead of requiring unique custom configuration for each device, the gateway uses copyable metadata templates that can be reused across multiple devices, reducing configuration complexity while maintaining accurate information recognition.

Inventive Principle:
Principle #26Copying

4Speed

If physical input-output devices are used in conventional systems, then real-time control is achieved, but adaptability to IoT protocols is limited

Engineering Contradiction:
Improvecontrol response speedVSAvoidprotocol adaptability
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The system is segmented into three independent layers: the physical fieldbus layer for real-time control, the gateway layer for protocol conversion, and the IoT application layer for connectivity. This segmentation allows the physical input-output devices to maintain their real-time control capabilities on the fieldbus side, while the gateway handles all protocol adaptation tasks, enabling the system to achieve both real-time performance and IoT protocol adaptability simultaneously.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11822315B2Device and method for interlinking conventional fieldbus-based automatic control system with IoT
Publication Date: 2023.11.21 ILPUM CORP
  • US11822315B2 patent drawing
  • US11822315B2 patent drawing
  • US11822315B2 patent drawing

AI summary

A device and a method for interlinking conventional fieldbus-based automatic control system with IoT at a subordinate position are provided. According to the present disclosure, the interlinking system device comprise a fieldbus connection unit connected to an operation device based on a fieldbus protocol and configured to operate as an input-output device, a fieldbus virtual input-output memory configured to memorize input-output information exchanged with the operation device, an IoT connection unit connected to an IoT platform based on an IoT protocol and configured to operate as an IoT device, a message formation unit configured to apply message metadata received from the IoT platform via the IoT connection unit and a message processing unit configured to process an input-output message based on the message metadata and the input-output information.