Time-Division Data Scheduling for Low-Latency Industrial Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for transmitting time-critical data in industrial automation systems face challenges with high latency and resource requirements, particularly in cloud and edge computing environments, leading to frame backlogs and increased latency due to unsynchronized data transmission.

Innovation Solution

A method employing time-division multiplexing with application-specific time windows and synchronized cycles to transmit time-critical data, using sequence control components and network infrastructure devices to ensure low latency and efficient resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If data transmission is performed without synchronized time windows in cloud/edge computing environments, then system resource requirements increase and frame backlogs occur, but implementing synchronized time-division multiplexing increases device complexity and coordination overhead

Engineering Contradiction:
ImprovelatencyVSAvoidcoordination complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent implements periodic time windows within a cycle structure where data transmission occurs in synchronized periodic intervals. Each control application is assigned specific time windows within a predetermined cycle, creating regular periodic transmission patterns that reduce latency and frame backlogs while maintaining manageable coordination complexity through the repetitive nature of the cycle.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent segments the transmission medium into application-specific time windows within a predetermined cycle, dividing the communication resource into distinct time slots for different control applications. This segmentation allows multiple applications to share the network resource efficiently without conflict, reducing overall system latency and resource requirements.

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple control applications transmit data simultaneously without coordination, then resource utilization is high, but frame backlogs occur and latency increases

Engineering Contradiction:
Improveresource utilizationVSAvoidlatency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent uses periodic time windows within a predetermined cycle to coordinate data transmission from multiple control applications. Each application transmits data in its assigned periodic time window, ensuring high resource utilization through systematic sharing while preventing frame backlogs and latency through synchronized transmission timing.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent establishes predetermined cycles and application-specific time windows in advance before data transmission begins. This preliminary coordination of transmission schedules allows multiple control applications to efficiently share network resources without conflicts, maximizing resource utilization while maintaining low latency through pre-planned transmission opportunities.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4625079A1Method and device for transmitting time-critical data within a communication network
Publication Date: 2025.10.01 SIEMENS AG
  • EP4625079A1 patent drawingFigure 1
  • EP4625079A1 patent drawingFigure 2
  • EP4625079A1 patent drawing

AI summary

The invention relates to a method for transmitting time-critical data within a communications network, in which data is transmitted via the communications network (200) according to a time-division multiplexing method within a predetermined cycle (T). The time-critical data (400) is transmitted from and/or to control applications, each of which is provided by at least one sequence control component (131-136) that can be loaded into and executed in at least one sequence control environment (121-123) installed on a host (100). At least for time-critical data (400) assigned to selected control applications, an application-specific time window (411-417) is specified, to which an application-specific cycle is assigned, which is a 2n multiple of the predetermined cycle (T).Depending on the respective application-specific cycle, offsets of the application-specific time windows (411-417) are determined in such a way that a sequence of adjacent application-specific time windows (420) is formed. Time-critical data (400) assigned to the selected control applications are sent by the host (100) via the communication network (200) according to the application-specific cycles and the offsets of the application-specific time windows.