Asynchronous Ethernet Bandwidth Utilization via Master-Slave Scheduling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Real-time capable Ethernet networks face inefficiencies in utilizing asynchronous bandwidth due to collisions and the need for large data buffers and intelligent coupling elements, which limits the increase in asynchronous data traffic without compromising real-time capabilities.

Innovation Solution

A method where slaves request asynchronous data transmission needs to the master within a transmission cycle, and the master responds with an invitation packet specifying the time for transmission, allowing precise planning and optimization of asynchronous data traffic without requiring additional hardware or buffers, enabling better utilization of available bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional Ethernet protocols are used for asynchronous data communication, then data can be transmitted between master and slave, but bandwidth utilization is inefficient due to collisions and requires large data buffers and intelligent coupling elements

Engineering Contradiction:
Improveasynchronous bandwidth utilizationVSAvoiddata buffer size and coupling element intelligence
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The master node performs preliminary planning of asynchronous data communication by pre-determining time slots for each slave node within the transmission cycle. This advance scheduling eliminates the need for large buffers and complex collision handling, as data transmission times are predetermined rather than contested.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where slave nodes indicate their asynchronous data communication needs to the master node, which then adjusts the transmission cycle planning accordingly. This allows the master to optimize bandwidth utilization by allocating time slots based on actual demand rather than using fixed, inefficient allocations.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If more asynchronous data traffic is allowed in real-time capable Ethernet networks, then communication flexibility increases, but real-time capabilities are compromised due to cycle time extensions

Engineering Contradiction:
Improveasynchronous data traffic capacityVSAvoidcycle time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The transmission cycle structure is made dynamic by allowing flexible allocation of asynchronous communication time slots within the predetermined cycle. The master node can adjust the timing and duration of asynchronous segments based on traffic demands while maintaining the overall cycle time constraints, enabling both high asynchronous capacity and real-time performance.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

By pre-planning asynchronous communication within the transmission cycle framework, the system determines optimal time slots in advance that maximize bandwidth utilization without extending the fundamental cycle time. This preliminary scheduling ensures real-time capabilities are preserved while accommodating flexible asynchronous traffic.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10389806B2Method for asynchronous data communication in a real-time capable ethernet data network
Publication Date: 2019.08.20 ABB (SCHWEIZ) AG
  • US10389806B2 patent drawing
  • US10389806B2 patent drawing
  • US10389806B2 patent drawing

AI summary

According to the invention, in order that the asynchronous bandwidth available in a real-time capable Ethernet data network protocol can be better utilized without collision at least one slave (S1, . . . , Sn) which wishes to transmit asynchronous data informs the master (M) in a transmission cycle (Z(m)) by means of a request data packet (DPa) how much asynchronous data this slave (S1, . . . , Sn) wishes to transmit asynchronously and by means of an invitation data packet (DPe) the master (M) informs the slave (S1, . . . , Sn) as to the time (tas) within a following transmission cycle (Z(m+k+l)) at which the slave (S1, . . . , Sn) should transmit the asynchronous data in an asynchronous data packet (DPas).