Software-Defined Industrial Control for Heterogeneous IoT Orchestration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial systems face challenges in managing complex IoT devices and systems due to their heterogeneous nature, leading to management complexity and reluctance in adopting new technologies, which hinders the wide-scale deployment of IoT and software-defined technologies in industrial settings.

Innovation Solution

The implementation of a software-defined industrial system (SDIS) architecture that enables dynamic data models, orchestration of functions across distributed resources, and self-descriptive modules, allowing for flexible configuration, management, and integration of IoT devices, while supporting legacy systems and heterogeneous environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If IoT devices and software-defined technologies are deployed in industrial systems, then system flexibility and adaptability improve, but device complexity and management difficulty increase

Engineering Contradiction:
Improvesystem flexibilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (edge computing platform, virtualization layer, or gateway) between heterogeneous IoT devices and the control system. This intermediary abstracts device-specific protocols and interfaces, translating diverse device communications into standardized formats that the control system can manage uniformly, thereby reducing management complexity while preserving adaptability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements universal communication protocols, standardized data models, and multi-functional edge computing platforms that can handle multiple device types and protocols through a single interface. This universality allows the system to manage heterogeneous devices through common mechanisms, reducing the need for device-specific management procedures

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If new technologies are adopted in industrial systems, then system capabilities improve, but reliability and operational stability deteriorate

Engineering Contradiction:
Improvetechnology adoptionVSAvoidoperational stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements redundancy mechanisms, failover capabilities, and validation layers that cushion against potential failures of new technologies. Critical control functions are backed up with alternative execution paths, and new device integrations undergo validation before full deployment, preventing instability while enabling technology adoption

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The patent employs dynamic configuration and runtime adaptation mechanisms that allow the system to adjust its behavior based on the reliability performance of newly adopted technologies. If new devices or protocols exhibit instability, the system can dynamically adjust parameters, isolate problematic components, or revert to proven configurations, maintaining operational stability while enabling innovation

Inventive Principle:
Principle #15Dynamics

3Reliability

If statically configured I/O and subsystems are used, then system reliability improves, but flexibility and ease of updates worsen

Engineering Contradiction:
Improvesystem reliabilityVSAvoidconfiguration flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent transforms static I/O configurations into dynamic, programmable interfaces using virtualization and software-defined I/O. Configuration parameters, data formats, and communication protocols can be modified at runtime without physical reconfiguration, allowing the system to maintain reliability through controlled changes while gaining flexibility for updates and adaptations

Inventive Principle:
Principle #15Dynamics

4Adaptability or versatility

If heterogeneous IoT devices are integrated, then system functionality improves, but ease of operation and management worsen

Engineering Contradiction:
Improvedevice functionalityVSAvoidmanagement ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces standardized intermediary interfaces and abstraction layers that translate heterogeneous device functionalities into uniform operation modes. Users interact with devices through common command sets and data models regardless of underlying device differences, significantly improving ease of operation while preserving access to diverse device capabilities

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements homogeneous data models, unified communication protocols, and standardized interface layers that present all heterogeneous devices in a consistent format. This homogenization of interfaces allows operators to manage diverse devices through uniform procedures, reducing the cognitive load and complexity associated with heterogeneity while maintaining full device functionality

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS11330087B2Distributed software-defined industrial systems
Publication Date: 2022.05.10 INTEL CORP
  • US11330087B2 patent drawing
  • US11330087B2 patent drawing
  • US11330087B2 patent drawing

AI summary

Various systems and methods for implementing a software defined industrial system are described herein. For example, an orchestrated system of distributed nodes may run an application, including modules implemented on the distributed nodes. In response to a node failing, a module may be redeployed to a replacement node. In an example, self-descriptive control applications and software modules are provided in the context of orchestratable distributed systems. The self-descriptive control applications may be executed by an orchestrator or like control device and use a module manifest to generate a control system application. For example, an edge control node of the industrial system may include a system on a chip including a microcontroller (MCU) to convert IO data. The system on a chip includes a central processing unit (CPU) in an initial inactive state, which may be changed to an activated state in response an activation signal.