Programmable Controller ID Matching Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing programmable controller systems face challenges in conveniently preventing unauthorized use of user programs, as current methods require complex programming and are vulnerable to unauthorized copying and technology leakage.
Innovation Solution
A programmable controller system with a tool device that manages user program execution IDs, allowing only authorized execution by setting up and associating a second user program execution ID, which cannot be changed or erased, and encrypting IDs to enhance security, thereby preventing unauthorized use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hardware ID matching is implemented through user program programming, then unauthorized use can be prevented, but the operation complexity increases and convenience decreases
Solution Approach 1:
The programmable controller automatically performs the ID matching check without requiring user program intervention. The controller reads the hardware ID from its own identification storage unit and compares it with the execution ID from the tool device, enabling the system to protect itself against unauthorized use through built-in automatic verification
Solution Approach 2:
The hardware ID stored in the identification storage unit serves as an intermediary that enables automatic authentication. This stored ID acts as a mediator between the controller's internal security mechanism and the tool device's execution ID, allowing verification without complex user programming
2Adaptability or versatility
If reference user programs are provided to end users, then program customization is enabled, but unauthorized copying and technology leakage risks increase
Solution Approach 1:
The hardware ID is pre-stored in the identification storage unit during controller manufacturing, establishing a built-in security mechanism before the controller is ever used. This preliminary security setup ensures that only authorized controllers can execute protected user programs, preventing unauthorized copying even when reference programs are distributed
Solution Approach 2:
The security function is segmented from the user program itself. The hardware ID verification is handled by a separate automatic authentication mechanism in the controller, while the user program remains independent and can be freely customized. This segmentation allows program distribution without compromising security
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A programmable controller system, a tool device, a tool program, a storage medium, and a programmable controller capable of affording greater convenience in terms of preventing unauthorized use of user program running on the programmable controller. In the programmable controller system (300), the tool device (200) sets up a first user program execution ID (10) in a second non-volatile memory (113) provided in the PLC (100) and sets up a second user program execution ID (20) in a project (PR) provided in the tool device (200). The PLC (100) performs a checking operation to determine whether or not the first user program execution ID (10) matches the second user program execution ID (20) and blocks the execution of the user program (YP) if there is a mismatch.