Modular Automation Station License Key Recovery After Module Replacement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for restoring license keys in automation systems require a continuous IT infrastructure or manual intervention by a skilled engineer, making it difficult to enable software functionality in replaced components, especially in remote areas without IT infrastructure.
Innovation Solution
A method and automation station that automatically restore license keys by distributing parity information across multiple storage locations, allowing functionality to be enabled even if one storage location is unavailable, using a restorer to regenerate the license key from parity information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual connection via programming device is used to restore license keys in remote areas, then license key restoration is possible, but it requires an experienced employee and manual intervention
Solution Approach 1:
The system automatically restores license keys using a restorer component that retrieves parity information from storage locations and regenerates license keys without requiring manual intervention by experienced employees. The automation station performs the restoration process autonomously after module replacement.
Solution Approach 2:
Parity information is pre-stored in multiple storage locations within the automation station before module replacement occurs. This preliminary storage of recovery data enables automatic license key restoration without needing external IT infrastructure or manual intervention.
2Extent of automation
If continuous IT infrastructure connection is used for license key restoration, then automated restoration is possible, but it is not available in remote areas without IT infrastructure
Solution Approach 1:
The solution moves the license key restoration capability from an external IT infrastructure dimension to an internal system dimension by storing parity information locally in multiple storage locations within the automation station. This enables automated restoration to function independently of external network connectivity.
Solution Approach 2:
The restorer component serves multiple functions: it automatically restores license keys using locally stored parity information, enabling the system to operate in both connected and remote environments without requiring different restoration mechanisms for different locations.
3Device complexity
If license key data is stored in a single location, then storage is simple, but it is vulnerable to data loss if that storage location fails
Solution Approach 1:
The license key data is segmented into multiple storage locations, with parity information distributed across at least two different storage locations within the automation station. This segmentation ensures that if one storage location fails, the license key can still be restored using parity information from the remaining locations.
Solution Approach 2:
Parity information is pre-stored in multiple storage locations as a cushion against potential data loss. This redundant storage of recovery information protects against storage location failures, ensuring license key restoration capability is maintained even when storage components fail.
Data Source
AI summary
Automation station and method for restoring license keys in a modular automation station which includes a main unit having a backplane bus connection and a plurality of modules having another backplane bus connection, wherein the plurality of modules or the main unit having a respective backplane bus connection communicate with one another via a backplane bus, where the plurality of modules are operated via a license key to provide software-based functionality tied to a respective license key after a module is replaced with a replacement module, and the license key is restored via automated reading of three data blocks, even when only two of the three data blocks are readable and the license key for the software-based functionality of the replaced module is assigned to the replacement module and thus the software-based functionality is enabled in the replacement module.