Web Application Framework for Industrial Automation Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial automation systems face challenges in providing flexible and efficient distribution of functions across multiple control or computer units, requiring robust communication infrastructure and varying communication protocols to ensure real-time compatibility and quality of service, while also needing to accommodate different client demands and extendibility without altering existing data and function models.

Innovation Solution

The method involves providing functions as web applications that combine application components at runtime, using a standard application programming interface for initialization, event handling, and data access, allowing for flexible integration of loosely coupled services without individual programming efforts, and enabling interactions between components through metadata and data interfaces, with options for direct or isolated integration within a web portal framework.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If distributed services are provided across multiple control units, then system functionality and flexibility are improved, but communication infrastructure demands and system complexity increase

Engineering Contradiction:
Improvesystem functionalityVSAvoidcommunication infrastructure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal communication infrastructure based on standard web protocols (HTTP, TCP/IP) that can handle multiple types of service communications simultaneously. The web server architecture provides a common platform for different service components to interact, eliminating the need for separate communication channels for each service type and reducing overall infrastructure complexity.

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

Solution Approach 2:

The web server acts as an intermediary component that mediates communication between diverse service components and clients. It standardizes interaction patterns through web protocols, allowing service components to communicate through a common interface without requiring direct point-to-point connections, thereby simplifying the communication infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If real-time communication is implemented across distributed services, then response time is improved, but communication protocol requirements and infrastructure demands increase

Engineering Contradiction:
Improveresponse timeVSAvoidcommunication protocol requirements
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The web server infrastructure is designed to handle both standard web traffic and real-time service communications through a single protocol stack. By leveraging the inherent speed of TCP/IP and HTTP protocols along with modern network capabilities, the system achieves real-time response without requiring multiple specialized protocol implementations.

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

3Adaptability or versatility

If service components are highly distributed, then system extendibility is improved, but communication overhead and infrastructure demands increase

Engineering Contradiction:
Improvesystem extendibilityVSAvoidcommunication overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The web server provides a universal communication platform that handles service registration, discovery, and data exchange through standardized web protocols. This allows new service components to be added to the distributed system without requiring changes to the communication infrastructure, as all services interact through the same web-based interface.

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

Solution Approach 2:

The web server mediates all communications between distributed service components, providing centralized service registration and discovery mechanisms. This intermediary approach reduces communication overhead by allowing services to declare their capabilities once through standard web interfaces rather than requiring direct peer-to-peer negotiation between all service pairs.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of manufacture

If standard web protocols are used for service communication, then ease of implementation is improved, but real-time performance and communication reliability may be compromised

Engineering Contradiction:
Improveease of implementationVSAvoidreal-time performance
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The web server is configured to handle both standard web traffic and real-time service communications through a single infrastructure. By optimizing the web server configuration and leveraging modern network capabilities, the system achieves real-time performance through the same standard protocols that provide ease of implementation.

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

Data Source

PatentUS10078314B2Method for providing functions within an industrial automation system, and industrial automation system
Publication Date: 2018.09.18 SIEMENS AG
  • US10078314B2 patent drawing
  • US10078314B2 patent drawing
  • US10078314B2 patent drawing

AI summary

Method of providing functions within an industrial automation system and an industrial automation system thereof. Functions of the automation system are made available by web applications that are combined by the client during control program execution to form interlinked web applications. The functions are provided on a user interface of the client. The web applications are provided by a standard application programming interface that comprises a cross-component application programming interface for initializing and unloading application components and a component-specific application programming interface for event handling and providing component functions. Component instances are linked by an application programming interface for stipulating interactions between application components.