Closed-Network License Server for Industrial Automation Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Industrial automation systems face challenges in managing functionality licenses due to limited availability and the need to maintain security by decoupling from external networks, which complicates the addition of licenses for diverse I/O and logic capabilities.
Innovation Solution
A method and device for managing functionality licenses within a closed network using a license database that operates within the network, allowing for secure assignment, scanning, and expansion of licenses without external access, utilizing a server to match and store functionality identifiers for connected devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the fieldbus is decoupled from external networks for security reasons, then network security is improved, but the ability to add functionality licenses is worsened
Solution Approach 1:
The patent introduces a license server as an intermediary component within the closed network that mediates license distribution. This server stores license information locally and handles license requests from subscriber devices, enabling license management without external network connection while maintaining security. The intermediary resolves the contradiction by providing license addition capability through an internal server rather than external network access.
2Reliability
If functionality licenses are limited in quantity, then network security and control are improved, but the diversity of I/O and logic capabilities is worsened
Solution Approach 1:
The patent implements a universal license server that can manage multiple types of functionality licenses (I/O licenses, logic licenses, communication licenses) within a single system. The license server stores diverse license information in a unified database structure, allowing the system to support various I/O modules and logic functions while maintaining centralized control. This multi-functional approach resolves the contradiction by enabling diverse capabilities through a single controlled interface.
Solution Approach 2:
The patent uses parameter-based license management where license information is stored as structured data with specific parameters (functionality identifiers, device identifiers, license types). By changing and configuring these parameters dynamically, the system can adapt to different I/O and logic requirements while maintaining license quantity control. The flexible parameter structure allows diverse capabilities without compromising control mechanisms.
3Productivity
If a centralized license database is implemented in the closed network, then license management efficiency is improved, but network complexity is worsened
Solution Approach 1:
The patent merges the license database and license management functions into a single centralized license server within the closed network. This consolidation combines data storage and processing capabilities in one component, improving license management efficiency by eliminating the need for distributed license verification across multiple devices. The merged structure reduces network complexity compared to a distributed approach while maintaining centralized control.
Data Source
AI summary
A method for managing functionality licenses in a closed network is disclosed, wherein at least one subscriber device is connected to the closed network. The method includes operating a server having a license database, wherein the license database includes a plurality of functionality licenses and each functionality license includes a functionality identifier. When the server receives a license request from the at least one subscriber device, the license request including a further functionality identifier, the server compares the further functionality identifier to the functionality identifiers in the license database and assigns a functionality license of the database, which includes a functionality identifier that matches the further functionality identifier to the subscriber device from which the license request was received. Assigning entails storing of the at least one subscriber device from which the license request was received at the server as a licensed subscriber device in the license database.