Core Process Control Interface for Verified Cloud-Edge Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The NAMUR Open Architecture's Verification of Requests mechanism is not adequately implemented, leading to stability, security, and reliability issues in industrial control systems due to lack of feedback control and excessive load from external clients, which complicates software development and management.

Innovation Solution

A method and processor network architecture that separates processing resources into cloud, edge, and protected domains to authenticate and authorize requests, ensuring secure and efficient execution of actions on industrial control systems, with auditing capabilities and feedback mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If external clients are allowed to write values to CPC variables through server interfaces, then operational flexibility and control capabilities are improved, but system stability and security deteriorate due to potential malicious actions and excessive load

Engineering Contradiction:
Improvecontrol capabilitiesVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary verification mechanism between external clients and the CPC domain. The server interface acts as a mediator that receives requests from external clients, verifies their authenticity and authorization status, and only forwards verified requests to the CPC domain. This intermediary layer prevents malicious actions while maintaining operational flexibility for authorized clients.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary verification actions before allowing external clients to write values to CPC variables. The server performs authentication and authorization checks in advance, verifying the client's identity and permissions before processing write requests. This preliminary action prevents unauthorized or malicious modifications while maintaining system stability.

Inventive Principle:
Principle #10Preliminary action

2Speed

If the server responds to each write call from external clients, then real-time control responsiveness is improved, but computational load and system resource consumption worsen

Engineering Contradiction:
Improvecontrol responsivenessVSAvoidcomputational load
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by implementing selective verification - the server performs full authentication and authorization checks only for critical write operations, while using lighter verification for routine operations. This partial verification approach maintains real-time responsiveness for time-critical controls while reducing computational load for less critical operations.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The server performs preliminary caching of authorization decisions and client credentials. Once a client is authenticated and authorized, the server caches these credentials and uses them for subsequent requests without repeating full verification. This preliminary action reduces computational load while maintaining real-time responsiveness through cached authentication data.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If comprehensive verification and authorization mechanisms are implemented, then system security and reliability are improved, but device complexity and implementation difficulty worsen

Engineering Contradiction:
Improvesystem securityVSAvoidimplementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the verification and authorization process into distinct modular components: authentication module, authorization module, request verification module, and response validation module. Each module handles a specific aspect of security verification, making the overall complex system manageable through clear separation of concerns and independent module development.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements universal verification functions that can be applied across different client types and communication protocols. The server interface uses a unified authentication and authorization framework that works for various external clients (SCADA systems, mobile devices, web interfaces) without requiring separate verification mechanisms for each client type, thereby reducing implementation complexity.

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

4Adaptability or versatility

If the architecture allows feedback from M+O domain to CPC domain, then operational flexibility and monitoring capabilities are improved, but automation security and plant availability worsen due to potential feedback loops and instability

Engineering Contradiction:
Improvemonitoring capabilitiesVSAvoidautomation security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements controlled feedback mechanisms where the server verifies requests from the M+O domain before allowing them to reach the CPC domain. The verification process includes checking the authenticity of feedback messages, validating authorization permissions, and ensuring feedback content meets safety criteria. This controlled feedback enables monitoring capabilities while preventing unauthorized or harmful feedback loops.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240275771A1Interface for a core process control system
Publication Date: 2024.08.15 ABB (SCHWEIZ) AG
  • US20240275771A1 patent drawing
  • US20240275771A1 patent drawing
  • US20240275771A1 patent drawing

AI summary

A method of executing a request to an industrial control system, which runs in a protected domain and is configured to control one or more field devices. Each step of the method is to be executed on processing resources of a cloud domain (CD), an edge domain (ED) or the protected domain. According to the first aspect, a step of receiving, from a client, a message with a request containing logical actions and a step of authenticating the client are performed using CD resources. Next, a step of initiating a verification of the message and a step of checking whether the authenticated client is authorized to perform the logical actions are performed using ED resources. Then, a step of mapping the logical actions to physical actions and a step where the industrial control system is caused to execute the physical actions are performed using resources in the protected domain.