Process Automation Network Testing Using Communication Intents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for testing industrial networks require extensive hardware setup and high manual effort, resulting in low test coverage and high costs, especially when testing converged networks with dynamic capacity requirements like voice/video communication, which is economically infeasible for full-scale implementation.

Innovation Solution

A computer-implemented method for automatically testing process automation network topology and configuration using communication intents to configure traffic generators and analyzers, allowing for automated test case generation and execution, which reduces the need for physical hardware setup and enables parallel testing across multiple devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If real applications and hardware are used for network testing, then test fidelity is high, but hardware availability and cost are major constraints

Engineering Contradiction:
Improvetest fidelityVSAvoidhardware setup complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent creates virtual copies of network devices, applications, and traffic patterns through software-based network emulators. These virtual representations replicate the behavior and characteristics of physical hardware without requiring actual device presence, thereby maintaining test fidelity while eliminating hardware availability constraints

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent replaces physical mechanical hardware systems with software-based virtualization technologies. Network devices, applications, and traffic are emulated through software rather than requiring physical instantiation, substituting the mechanical/physical layer with a software abstraction layer that provides the same testing functionality

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If all network devices and applications are connected for comprehensive testing, then test coverage is complete, but economic feasibility deteriorates

Engineering Contradiction:
Improvetest coverageVSAvoideconomic feasibility
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal software-based testing platform that can emulate multiple different network devices, applications, and traffic patterns within a single virtualized environment. This multi-functional emulator can represent various hardware configurations and application scenarios without requiring separate physical setups for each test case, achieving comprehensive coverage at low cost

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

Solution Approach 2:

The patent enables dynamic modification of testing parameters including device configurations, traffic patterns, network topology, and application behaviors through software controls. This allows comprehensive testing of various scenarios by changing virtual parameters rather than physically reconfiguring hardware, maintaining test coverage while reducing economic burden

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If manual configuration of artificial traffic is performed, then traffic representation accuracy is high, but manual effort and time requirements increase

Engineering Contradiction:
Improvetraffic representation accuracyVSAvoidconfiguration time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements automated traffic generation capabilities within the virtualized testing environment that self-configure and self-adapt to match real-world traffic patterns. The system automatically learns and replicates communication behaviors, protocols, and traffic characteristics without requiring manual configuration, achieving both accuracy and efficiency

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent pre-configures virtual network devices, applications, and traffic patterns within the virtualized environment before actual testing begins. By preparing the entire testing scenario in advance through software deployment, the system eliminates on-site manual configuration requirements and enables immediate execution of comprehensive tests

Inventive Principle:
Principle #10Preliminary action

4Reliability

If end-to-end application testing is performed, then real-world scenario validation is achieved, but test granularity and insight are reduced

Engineering Contradiction:
Improvereal-world scenario validationVSAvoidtest insight
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the end-to-end application testing into discrete, analyzable components at the network protocol and device interaction levels. The virtualized testing environment captures and analyzes individual protocol exchanges, device responses, and communication patterns separately, providing granular insights into each layer while maintaining the context of the complete end-to-end scenario

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4451637A1Method for automated network testing
Publication Date: 2024.10.23 ABB (SCHWEIZ) AG
  • EP4451637A1 patent drawingFigure 1~2
  • EP4451637A1 patent drawingFigure 3~4
  • EP4451637A1 patent drawingFigure 5A~5B

AI summary

The invention relates to a computer implemented method for creating a test setup for automatically testing a topology and/or configuration of a process automation network. The method comprises the following steps. In a first step (210), communication intents containing a definition of communication connections between communication endpoints and connection specifications between the communication endpoints are received, and at least one communication intent to be tested is selected. In a second step (220), topology information of the network to be tested is received and analyzed. In a third step (230), test cases for each of the at least one communication intents are generated by generating a configuration for at least one traffic generator and a configuration for at least one traffic analyzer using the selected communication intents and the topology information. In a fourth step (240), the at least one test case is deployed to test facilities on which test functions are to be run using the traffic generator and traffic analyzer, and the test functions are configured. In a fifth step (250), the process automation network is configured to receive data from traffic generator and provide data to the traffic analyzer.