Automation Pointer Migration via Absolute Address Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In automation systems, data migration of a control program's global state often fails when changes, such as renamed variables or changed data types, affect pointer elements, preventing the new control program version from accessing the global state information correctly.

Innovation Solution

A method for data migration that identifies and maps pointer elements between different control program versions by determining the absolute memory address of the associated pointer object, ensuring that the new control program can reference the correct objects, even with changes in variable names or data types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If pointer elements are updated in the new control program version, then the control program can reference correct objects, but the data migration fails when variable names or data types change

Engineering Contradiction:
Improvedata migration successVSAvoidpointer element adaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by identifying and mapping pointer elements before the actual data migration occurs. The system pre-processes the control program to establish correspondence between old and new pointer elements, ensuring that when migration happens, the pointer references are already correctly aligned. This prevents migration failures caused by variable name or data type changes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mapping mechanism that acts as a bridge between the old and new control program versions. This mapping structure stores the correspondence relationships between pointer elements across versions, allowing the system to translate references during migration without direct dependency on variable name consistency. The intermediary layer resolves conflicts when data types or names change.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the control program is replaced with a new version, then optimized operation is achieved, but a complete system restart becomes necessary

Engineering Contradiction:
Improvecontrol program update efficiencyVSAvoidsystem restart time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by preparing the pointer element mappings in advance before the control program replacement occurs. The mapping information is generated and stored during the compilation or loading phase, so when the new control program version is deployed, the pointer references are already resolved. This eliminates the need for a complete system restart, as the migration can happen seamlessly in the background.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent ensures continuity of useful action by maintaining the control program's execution state during the pointer migration process. The mapping mechanism allows the new control program version to access and modify pointer elements continuously without interruption. The system maintains operational continuity throughout the migration, avoiding stops or restarts that would break the useful action chain.

Inventive Principle:
Principle #20Continuity of useful action

3Adaptability or versatility

If pointer elements reference objects by name, then flexibility in variable renaming is possible, but reference correctness cannot be guaranteed after changes

Engineering Contradiction:
Improvevariable renaming flexibilityVSAvoidpointer reference accuracy
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent applies copying by creating a duplicate mapping structure that replicates the pointer element relationships. Instead of relying on direct name matching, the system copies the reference information into a separate mapping table that preserves the correctness of references even when original variable names change. This copy acts as a reliable reference guide during migration.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent uses an intermediary mapping mechanism that decouples the flexibility of variable renaming from the precision of pointer references. The mapping structure serves as an intermediary layer that translates flexible name changes into precise reference mappings. This allows variable names to be renamed freely in the new version while the mapping ensures accurate pointer references are maintained.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11640293B2Method for data migration of a pointer element in the course of data migration of a program state of a control program of an automation system
Publication Date: 2023.05.02 BECKHOFF AUTOMATION GMBH
  • US11640293B2 patent drawing
  • US11640293B2 patent drawing
  • US11640293B2 patent drawing

AI summary

A method for data migration of a pointer element in the course of data migration of a program state of a control program of an automation system comprises identifying the first pointer element and the second pointer element as pointer elements associated with each other via a first relation in a pointer-identifying step, and mapping the first pointer element to the second pointer element in a pointer migration step. The pointer migration step comprises identifying the first pointer object referenced by the first pointer element, identifying an object associated with the first pointer object as the second pointer object, determining an absolute memory address of the second pointer object, and writing the determined memory address of the second pointer object as a value of the second pointer element into the second pointer element.