IIoT Device Integration Definitions for Hot-Pluggable Runtime Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Industrial Internet of Things (IIOT) sensor network setup and software upgrades are slow, difficult to test, and require server restarts, leading to downtime, and lack real-time integration capabilities for new devices and sensors without disturbing active deployments.
Innovation Solution
A novel integration method using a generic variable structure for defining device and sensor integrations, including a software design kit (SDK) and web-based user interface for creating integration definitions, with support for runtime-interpretable code and a hot pluggable model, allowing for near real-time addition, adjustment, and updating of sensors and devices within a live IIOT platform environment without restarting devices or recompiling cloud code.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional IIOT platform software upgrades and device integrations are implemented through internal employee development and server restarts, then system stability and security are maintained, but the process is slow (taking weeks), requires downtime, and lacks real-time integration capabilities
Solution Approach 1:
The system transitions from static, compiled code to dynamic, runtime-interpretable code. Integration definitions are loaded and executed at runtime without requiring server restarts, enabling the system to adapt and integrate new devices dynamically while maintaining continuous operation. This resolves the contradiction by making the system both fast (real-time integration) and available (no downtime).
Solution Approach 2:
The integration process is segmented into separate, modular integration definitions that can be independently developed, tested, and deployed. Each integration definition is a self-contained unit that can be loaded without affecting other integrations or requiring full system restart, enabling rapid updates without downtime.
2Adaptability or versatility
If new device integrations are added through traditional compilation and deployment methods, then security and stability are ensured, but the process is difficult to test and requires weeks to complete
Solution Approach 1:
Integration definitions are prepared and validated in advance through a user interface that allows configuration and testing before deployment. The system performs preliminary validation of integration definitions against the runtime environment, enabling thorough testing without affecting production systems and reducing deployment complexity.
Solution Approach 2:
A user interface acts as an intermediary between device manufacturers/customers and the IIOT platform. This intermediary provides templates, guides, and validation mechanisms that simplify the creation and testing of integration definitions, making the process accessible to non-experts while maintaining system security and stability.
3Stability of the object's composition
If integration definitions are hard-coded into the IIOT platform, then system stability is maintained, but backwards compatibility with legacy devices and real-time updates are compromised
Solution Approach 1:
Instead of hard-coding integrations, the system uses integration definitions that are copied and loaded at runtime from external sources. These definitions can be imported from files, databases, or external systems, enabling backwards compatibility with legacy devices while maintaining system stability through validated definition formats and sandboxed execution environments.
4Reliability
If the IIOT platform uses a closed integration process requiring internal employee involvement, then security is maintained, but the process is slow and lacks real-time capabilities
Solution Approach 1:
Device manufacturers and customers can independently create, configure, and deploy integration definitions using the user interface without requiring internal employee involvement. The system provides self-service capabilities including template-based configuration, automatic validation, and secure deployment, maintaining security through enforced protocols while enabling rapid real-time integration.
Data Source
AI summary
In an illustrative embodiment, the present disclosure relates to systems, methods, and an industrial internet of things (IIOT) platform and environment for generating a device integration definition to be used for configuring a new device type for interoperability with the IIOT platform and environment, where the device integration definition includes a standardized format in a programming language syntax, the device integration definition is customizable using code hook templates for issuing commands to the device type, and the device integration definition is customizable using control templates for applying the device integration definition as a foundation for preparing a graphical user interface for configuring devices of the device type with the IIOT platform and environment.