Wind Power Data Transfer Testing with Timestamped Message Loops

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of data communication in wind power surveillance systems, involving multiple hubs and environments owned by different parties, leads to issues with data delivery and troubleshooting, exacerbated by increased security measures, making it difficult to identify and address transfer failures.

Innovation Solution

A method for testing data transfer at the application layer using test messages stamped with time and transfer stamps, allowing for comparison and identification of delays or errors, enabling continuous self-testing and alert generation for troubleshooting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If security measures are increased and data is pushed through multiple hubs and links in different environments, then security compliance is improved, but troubleshooting difficulty increases and data transfer reliability deteriorates

Engineering Contradiction:
Improvesecurity complianceVSAvoidcommunication path complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A test message with unique identifier and timestamp is introduced as an intermediary element to traverse through the complex communication path. This test message acts as a mediator that carries diagnostic information through multiple hubs and links, enabling tracking and identification of transfer issues without disrupting normal secured operations

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback by comparing the original test message with the received test message, analyzing timestamps and identifiers to detect transfer delays, losses, or errors. This feedback mechanism provides continuous monitoring of data transfer health across the complex security-compliant communication path

Inventive Principle:
Principle #23Feedback

2Reliability

If multiple hubs and links in different environments are used for data transfer, then security standards are met, but identifying transfer issues becomes more difficult

Engineering Contradiction:
Improvesecurity standard complianceVSAvoidtransfer issue detection difficulty
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The test message incorporates distinctive identifiers and timestamps that act as 'markers' to trace the message through different environments. These unique identifiers enable easy detection and measurement of transfer issues by comparing message states across different hubs and links in the communication path

Inventive Principle:
Principle #32Color changes

3Reliability

If data transfer is pushed on the initiative of SCADA systems with increased security, then security compliance is improved, but communication troubleshooting complexity increases

Engineering Contradiction:
Improvesecurity complianceVSAvoidtroubleshooting complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by sending test messages before actual data transfer operations to verify communication path health. This proactive testing identifies potential issues in advance, reducing troubleshooting complexity while maintaining security-compliant pushed communication architecture

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4207704B1A method for testing data transfer in a wind power surveillance system
Publication Date: 2026.05.13 VESTAS WIND SYSTEMS AS
  • EP4207704B1 patent drawingFigure 1
  • EP4207704B1 patent drawingFigure 2
  • EP4207704B1 patent drawingFigure 3

AI summary

The present disclosure provides a method for testing data transfer at the application layer of a wind power surveillance computer system. The method comprises the steps of preparing a test message with a message id, transferring the test message from a first computer entity to a second computer entity of at least three computer entities, stamping the test message with a time stamp, when transfer is initiated, stamping the test message with a transfer id and a corresponding transfer time stamp, when the test message is received at the second entity, transferring the test message from the second computer entity at the application layer to the first computer entity, stamping the test message with an arrival time stamp, when the test message arrives at the first entity, storing the message id and the transfer id with corresponding time stamp and corresponding transfer time stamp, and the arrival time stamp, and comparing the stored time stamp with the transfer time stamp and with the arrival time stamp.