Control Logic Allocation and Scheduling for Parallelized Deployment

Solution Overview

Problem

Control engineers lacking software expertise face challenges in implementing control logics on control platforms, requiring cumbersome and time-consuming tasks to meet functional and non-functional requirements without disrupting existing processes.

Innovation Solution

A method and agent that generate and optimize control logic automatically, using a Large Language Model and dynamic profiling to allocate and schedule functional code across processor cores, ensuring compliance with user-defined requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If control engineers manually create control logic with deep knowledge of the platform, middleware, and operating system, then the control logic can meet functional and non-functional requirements, but the development process becomes cumbersome and time-consuming

Engineering Contradiction:

Improvecontrol logic meets requirementsVSAvoiddevelopment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis of the control logic code to automatically determine allocation and scheduling information before deployment. This preliminary action extracts timing characteristics, resource requirements, and scheduling parameters automatically, eliminating the need for manual configuration and significantly reducing development time while maintaining reliability

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The control logic automatically determines its own allocation and scheduling requirements through self-analysis of its code structure and runtime characteristics. The system enables control logic to self-configure by automatically identifying its resource needs and scheduling constraints without requiring external manual intervention or deep platform knowledge from engineers

Inventive Principle:

Principle #25Self-service

2Stability of the object's composition

If control engineers manually configure allocation and scheduling, then the control logic can run smoothly without disturbing existing processes, but the complexity of the task increases

Engineering Contradiction:

Improvecontrol logic runs smoothlyVSAvoidconfiguration complexity

Core Design Contradiction:

Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The system replaces manual mechanical configuration processes with automated code analysis and information extraction. Instead of engineers manually analyzing and configuring allocation and scheduling parameters, the system automatically extracts this information from the control logic code itself, substituting automated computational processes for manual mechanical configuration tasks

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system introduces an intermediary automated analysis layer between the control logic code and the platform allocation/scheduling mechanisms. This intermediary automatically extracts timing characteristics, resource requirements, and scheduling parameters from the control logic and translates them into platform-specific configuration, eliminating the need for engineers to directly manage complex allocation and scheduling details

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If control engineers with rare expertise are used, then the control logic can be implemented correctly, but the availability of such engineers becomes a bottleneck

Engineering Contradiction:

Improvecontrol logic implementation correctnessVSAvoidimplementation speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The control logic automatically determines its own allocation and scheduling requirements through self-analysis of its code structure and runtime characteristics. The system enables control logic to self-configure by automatically identifying its resource needs and scheduling constraints without requiring external manual intervention or deep platform knowledge from engineers

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary analysis of the control logic code to automatically determine allocation and scheduling information before deployment. This preliminary action extracts timing characteristics, resource requirements, and scheduling parameters automatically, eliminating the need for manual configuration and significantly reducing development time while maintaining reliability

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentEP4703868A1Method, agent, and computer program for implementing a control logic into a control platform, control platform, and technical system

Publication Date: 2026.03.04 ABB (SCHWEIZ) AG

Figure 1
Figure 2~3

AI summary

A method for implementing a control logic (38) into a control platform (22) for controlling a technical system (24) is described. The method comprises: receiving a query signal (50) from an input unit (30), wherein the query signal (50) is representative of a user query (28) and wherein the user query (28) describes at least one requirement which has to be fulfilled by the control logic (38); generating a functional code (52) from the query signal (50), wherein the functional code (52) comprises computer-readable instructions determined depending on the described requirements; determining a preliminary control logic (54) by allocating and scheduling the functional code (52) on the control platform (22), wherein the allocated and scheduled functional code (52) corresponds to the preliminary control logic (54); determining at least one profile of the preliminary control logic (54) by analysing the allocated and scheduled functional code (52); and optimizing the preliminary control logic (54) depending on the profile until the requirements are fulfilled and a parallelized functional code is achieved, wherein the parallelized functional code fulfilling the requirements represents the final control logic (38).