FA Controller Packet Buffer Coordination to Prevent Data Loss

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In industrial control systems, packet data buffered in controllers connected to the same network can be lost due to buffer overflow, making it difficult to conduct detailed analysis of network abnormalities.

Innovation Solution

The implementation of a stop module in each controller that allows for the stopping of the buffering function not only in its own controller but also in other connected controllers, thereby preventing the loss of packet data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If the buffer capacity is limited to maintain device simplicity, then device complexity is reduced, but packet data is lost when the buffer is overflowed

Engineering Contradiction:
Improvebuffer capacityVSAvoidpacket data loss
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The system divides the buffering function into multiple segments by enabling different controllers to buffer packet data independently. Each controller maintains its own buffer, and when one controller's buffer is full, packet data can be buffered in another controller's buffer instead, effectively segmenting the overall buffering capacity across multiple devices.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges the buffering resources of multiple controllers into a unified system. By allowing any controller to buffer packet data from any source, the system combines the individual buffer capacities of multiple controllers to create a larger effective buffer capacity, preventing data loss without increasing the buffer size of any single controller.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If packet data is buffered in multiple controllers to prevent data loss, then reliability is improved, but device complexity increases due to coordination requirements

Engineering Contradiction:
Improvepacket data retentionVSAvoidbuffer coordination
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Each controller autonomously determines whether to buffer incoming packet data based on its own buffer status and the status of other controllers. The controllers independently make decisions about data buffering without requiring complex centralized coordination, with each controller serving itself by managing its own buffer resources and collaborating with others through simple status sharing.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where controllers share information about their buffer status with other controllers. This feedback allows controllers to make informed decisions about where to buffer packet data, with each controller adjusting its buffering behavior based on real-time status information from the network, achieving coordinated buffering through distributed feedback rather than complex centralized control.

Inventive Principle:
Principle #23Feedback

3Loss of information

If the buffer is continuously monitored to prevent overflow, then packet data loss is prevented, but productivity decreases due to additional processing overhead

Engineering Contradiction:
Improvepacket data lossVSAvoiddata processing efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

Controllers continuously monitor their buffer status and proactively identify available buffering capacity before packet data loss can occur. By performing preliminary checks of buffer status and pre-coordinating with other controllers, the system prevents overflow conditions before they happen, avoiding the need for complex real-time intervention and maintaining normal data processing flow.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements monitoring and coordination only when necessary - specifically when buffers are approaching capacity or when packet data needs to be buffered across multiple controllers. During normal operation when buffers have sufficient capacity, controllers simply buffer data locally without additional coordination overhead, applying partial monitoring action rather than continuous full-system coordination.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3767409B1Factory automation (FA) system, controller, and control method
Publication Date: 2025.06.11 OMRON CORP
  • EP3767409B1 patent drawingFigure 1
  • EP3767409B1 patent drawingFigure 2
  • EP3767409B1 patent drawingFigure 3

AI summary

A technique capable of preventing the loss of packet data for any appropriate one of controllers (100A to 100C) connected to the same network is provided. An FA system includes a plurality of controllers (100A to 100C). Each of the controllers (100A to 100C) includes: a buffer (150); a communication module (152) for performing packet communication with one or more other controllers; a packet monitor module (154) for buffering packet data generated in its own controller and packet data received by its own controller in the buffer (150); and a stop module (156) for stopping, in response to a predetermined stop condition (108) being satisfied, a buffering function of the packet monitor module (154) for a controller specified from the plurality of controllers (100A to 100C).