Mobile Automation Containers for Cross-Device Function Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Factory operators face challenges in deploying non-critical automation functions on mobile devices due to the vast variety of mobile phones with different types, performance levels, and operating systems, making it difficult to verify and design specific programs for each device, and existing systems operate independently, hindering integration with automation systems.

Innovation Solution

A method involving subroutine operation containers on mobile devices to register and deploy automation functions, using a management server to unify mobile devices by checking capabilities, deploying automation subroutines in WebAssembly binary code, and managing them centrally, allowing seamless migration or replacement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If mobile devices of different types are used to deploy automation functions, then cost is reduced and performance is improved, but device verification complexity and programming difficulty increase

Engineering Contradiction:
ImprovecostVSAvoiddevice verification complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent creates a universal automation function deployment architecture that works across different mobile device types. By using a standardized subroutine operation container interface and capability abstraction layer, the system enables single automation programs to run on multiple device types without requiring device-specific verification or programming modifications.

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

Solution Approach 2:

The patent introduces an intermediary management server and standardized container interface between the automation functions and diverse mobile devices. This intermediary layer abstracts device-specific variations, allowing automation functions to be deployed uniformly across different devices without direct interaction with device-specific implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If device-specific programs are designed for each mobile device type, then automation function compatibility is improved, but development time and system complexity increase

Engineering Contradiction:
Improveautomation function compatibilityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system achieves universal compatibility through a standardized container interface that works across all mobile device types. The capability information mechanism allows the same automation program to adapt to different devices at runtime without requiring separate device-specific program versions, dramatically reducing development time.

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

Solution Approach 2:

The patent uses parameter-based adaptation where automation functions receive capability parameters from the mobile device and adjust their behavior accordingly. This allows a single program to work across different devices by changing operational parameters rather than requiring different program code for each device type.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If independent non-standard systems are used for mobile phone automation, then ease of deployment is improved, but integration with serious automation systems becomes difficult

Engineering Contradiction:
Improveease of deploymentVSAvoidsystem integration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a management server as an intermediary that bridges independent mobile device automation systems with serious automation systems. This intermediary provides standardized interfaces and capability abstraction, enabling seamless integration while maintaining the ease of deployment benefits of independent mobile systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments automation functions into independent, containerized subroutines that can be deployed individually on mobile devices while maintaining standardized interfaces. This segmentation allows easy independent deployment while enabling integration through the standardized container protocol and management server.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4625215A1Method for deploying automation function on mobile device and information processing method
Publication Date: 2025.10.01 SIEMENS AG
  • EP4625215A1 patent drawingFigure 1
  • EP4625215A1 patent drawingFigure 2
  • EP4625215A1 patent drawingFigure 3

AI summary

The present disclosure relates to a method for deploying an automation function on a mobile device and an information processing method. For the method for deploying an automation function on a mobile device in an automation system, the automation system comprises an automation device, a management server, and a mobile device, wherein function operation containers of multiple mobile devices are registered in the management server. The method comprises: the management server deploying an automation function in the function operation container of the mobile device; executing the automation function in the function operation container; and performing data exchange between the function operation container and the management server on the basis of an execution result of the automation function.