Namespace-Based Variable Publishing for Controller Security Settings

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In industrial automation systems, setting which variables from a user program should be published to an external device for security purposes is extremely cumbersome due to the large number of variables involved.

Innovation Solution

A control system that includes a development assistance device and a controller, where the development tool allows for a publishing setting to be made for each namespace in the user program, determining whether variables belonging to that namespace should be published to an external device.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each variable is individually specified as public or private for security, then security is ensured, but the setting process becomes extremely troublesome and time-consuming

Engineering Contradiction:
ImprovesecurityVSAvoidpublishing setting process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments variables into namespaces (e.g., namespace A, namespace B) and applies publishing settings at the namespace level rather than individually to each variable. This segmentation allows the system to maintain security by controlling access to specific namespaces while dramatically reducing the operational burden of setting permissions for numerous variables.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges the publishing setting operation for multiple variables into a single namespace-level setting. By combining the permission control for all variables within a namespace into one unified setting, the system achieves both security (through controlled access) and ease of operation (through reduced setting steps).

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If an enormous number of variables are included in the user program, then functionality is enhanced, but the process of specifying each variable as public or private becomes extremely troublesome

Engineering Contradiction:
ImprovefunctionalityVSAvoidpublishing setting complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent organizes the large number of variables into structured namespaces, creating a hierarchical organization system. This segmentation approach maintains the functionality of having numerous variables while reducing the complexity of managing their publishing settings by grouping them under namespace-level controls.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension of organization by adding the namespace hierarchy layer above individual variables. Instead of managing variables in a flat one-dimensional list, the system uses a two-dimensional structure (namespace → variable), which reduces the complexity of publishing settings by allowing batch operations at the namespace level.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP3767411B1Control system for publishing variables managed in a controller to an external device
Publication Date: 2025.05.14 OMRON CORP
  • EP3767411B1 patent drawingFigure 1
  • EP3767411B1 patent drawingFigure 2
  • EP3767411B1 patent drawingFigure 3

AI summary

There has been desired a technology for performing a publishing setting of a variable to an external device more easily. A development assistance device (100) provides a development tool (30) configured to develop a user program (210) for controlling a controller (200). The user program (210) includes at least one variable belonging to a predetermined namespace. The development tool (30) is configured to accept, for the namespace, a publishing setting for causing the controller (200) to determine whether to publish the variable belonging to the namespace to an external device that is communicatively connected to the controller (200). A communication interface (111) transfers the user program (210) and the publishing setting to the controller (200) on the basis of acceptance of transfer operation of the user program (210) by the development tool (30).