Edge Module Timing Verification for Fixed-Cycle Cloud Control

Solution Overview

Problem

Migrating a controller to the cloud for industrial control systems introduces network latency, leading to variable processing times and the inability to perform fixed-cycle processing due to communication delays over the Internet.

Innovation Solution

An edge module with a data generator, transmitter, receiver, and abnormality detector that utilize timestamps and serial numbers to ensure fixed-cycle processing by detecting communication anomalies and generating emergency control signals when necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the controller is deployed in the cloud to reduce installation and update costs, then flexibility and operability are improved, but communication latency increases and fixed-cycle processing becomes infeasible

Engineering Contradiction:

Improveflexibility and operabilityVSAvoidcommunication latency

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The edge module performs preliminary actions by generating control data locally and transmitting it to the cloud controller in advance. The cloud controller processes this data and returns control commands, allowing the system to maintain fixed-cycle processing despite cloud deployment latency. The edge module prepares data packets with timestamps and serial numbers before transmission, enabling synchronized processing cycles.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The edge module acts as an intermediary between the cloud controller and the controlled device. It receives control commands from the cloud, processes them locally, and executes them without requiring real-time cloud intervention. This intermediary role compensates for cloud communication latency and maintains deterministic processing cycles at the edge.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of manufacture

If the controller is deployed in the cloud, then initial installation and update costs are reduced, but simultaneity cannot be guaranteed due to Internet communication delays

Engineering Contradiction:

Improveinstallation and update costsVSAvoidsimultaneity guarantee

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The edge module performs preliminary actions by generating control data locally and transmitting it to the cloud controller in advance. The cloud controller processes this data and returns control commands, allowing the system to maintain fixed-cycle processing despite cloud deployment latency. The edge module prepares data packets with timestamps and serial numbers before transmission, enabling synchronized processing cycles.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the edge module sends status information and control data to the cloud controller, which returns acknowledgment and control commands. This feedback loop includes timestamp verification and serial number matching to ensure data integrity and simultaneity, compensating for the lack of real-time guarantees in cloud-based Internet communication.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If the controller is deployed in the cloud, then operational flexibility is improved, but processing time variability increases making fixed-cycle processing infeasible

Engineering Contradiction:

Improveoperational flexibilityVSAvoidfixed-cycle processing capability

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The control system is segmented into cloud-based control logic and edge-based execution. The cloud controller handles high-level decision-making and data processing, while the edge module handles real-time control execution. This segmentation allows the cloud to provide flexibility while the edge maintains deterministic fixed-cycle processing with local buffer storage and timestamp-based synchronization.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The edge module performs preliminary actions by generating control data locally and transmitting it to the cloud controller in advance. The cloud controller processes this data and returns control commands, allowing the system to maintain fixed-cycle processing despite cloud deployment latency. The edge module prepares data packets with timestamps and serial numbers before transmission, enabling synchronized processing cycles.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentEP4712501A1Edge module, control system, remote control system, controller, and communication method

Publication Date: 2026.03.18 KK TOSHIBA

Figure 1
Figure 2
Figure 3

AI summary

[Problem] Provided is an edge module, a control system, a remote control system, a controller, and a communication method that enable fixed-cycle processing. [Solution to Problem] An edge module according to an embodiment includes: a data generator configured to generate first data including a serial number; a transmitter configured to assign a first timestamp to the first data and transmit the first data to a controller; a receiver configured to receive second data generated by the controller based on the first data, the second data including the serial number and the first timestamp, and to obtain a second timestamp corresponding to a reception time of the second data; and an abnormality detector configured to determine whether communication with the controller was successfully performed based on at least one of: (i) the serial number included in the second data, and (ii) a difference between the first timestamp included in the second data and the second timestamp.