Stored Summary Requests for Lower-Load Control Data Acquisition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In systems where multiple types of information are acquired in bulk, the information processing device experiences a significant load due to repeated creation of summary requests for acquiring control state data, such as machine axis positions and control program execution statuses, which increases communication processing load and network load.

Innovation Solution

The solution involves creating and storing a summary request once and reading it during data acquisition, reducing the load on the information processing device by eliminating the need for repeated summary request creation processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If summary request creation processing is repeatedly executed for each data acquisition, then data can be acquired from the control device, but the communication processing load and network load increase significantly

Engineering Contradiction:
Improvedata acquisition efficiencyVSAvoidcommunication processing load
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent applies preliminary action by creating and storing the summary request structure in advance before actual data acquisition occurs. The summary request template is prepared once and stored in the information processing device, then reused multiple times for different data acquisition operations. This eliminates the need to recreate the same request structure repeatedly, significantly reducing communication processing load and network traffic while maintaining efficient data acquisition capabilities.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If multiple types of information are acquired in bulk using summary requests, then communication frequency is reduced, but the load for creating summary requests increases

Engineering Contradiction:
Improveamount of information acquiredVSAvoidsummary request creation complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent applies copying by creating a template summary request structure once and then copying/reusing this template for multiple data acquisition operations. Instead of creating complex summary requests from scratch each time, the system copies the pre-established request structure and populates it with different parameters as needed. This dramatically reduces the computational complexity and processing load associated with creating bulk information acquisition requests.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If summary requests are created dynamically for each acquisition need, then data acquisition is flexible, but the time required for processing increases

Engineering Contradiction:
Improvedata acquisition flexibilityVSAvoidrequest creation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining and storing summary request templates that can be quickly instantiated and reused. This allows the system to maintain flexibility in data acquisition by selecting and parameterizing appropriate pre-defined templates based on current needs, while avoiding the time-consuming process of creating requests from scratch each time. The pre-prepared templates enable rapid deployment of data acquisition operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240302806A1Information processing device and computer-readable storage medium
Publication Date: 2024.09.12 FANUC LTD
  • US20240302806A1 patent drawing
  • US20240302806A1 patent drawing
  • US20240302806A1 patent drawing

AI summary

An information processing device includes a summary request storage unit that stores a summary request created in advance; a summary request management unit that receives a summary request acquisition request, that reads, from the summary request storage unit, a summary request included in the summary request acquisition request, and that provides the summary request thus read; a command execution unit that executes a command read from an application program; and a summary request execution unit that, in a case where the command is a summary request execution command, issues, to the summary request management unit, the summary request included in the summary request execution command, and executes the summary request acquired as a response to the request.