Network Switch Scheduling for Real-Time Ethernet Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Real-time Ethernet implementations such as PROFINET, EtherCAT, and Ethernet Powerlink are not interoperable due to custom media access control layers, preventing compatibility with standard IEEE 802.1 switches and requiring a solution for interoperability, synchronization of clocks, and scheduling of data egress across networks.

Innovation Solution

A system with switch circuitry and network nodes that route packets between real-time networks based on mappings, insert/remove routing information, and manage VLAN tags to maintain real-time behavior, synchronize clocks using master clocks, and schedule data egress through deterministic routing and queue management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If custom media access control layers are used in real-time Ethernet implementations, then real-time performance is improved, but interoperability with standard IEEE 802.1 switches deteriorates

Engineering Contradiction:
Improvereal-time performanceVSAvoidinteroperability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary device (gateway or router) that translates between custom real-time Ethernet protocols and standard IEEE 802.1 protocols. This intermediary maintains real-time performance by preserving timing-critical data while enabling interoperability with standard switches, thus resolving the contradiction between real-time performance and interoperability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments network traffic into real-time critical data and non-critical data, applying different handling mechanisms. Real-time traffic is routed through specialized paths that maintain timing requirements, while allowing standard IEEE 802.1 switching for other traffic, thus achieving both real-time performance and interoperability.

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple proprietary real-time Ethernet protocols are deployed, then real-time data transfer capability is improved, but network compatibility deteriorates

Engineering Contradiction:
Improvereal-time data transfer capabilityVSAvoidnetwork compatibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal gateway device capable of supporting multiple proprietary real-time Ethernet protocols simultaneously. This multi-functional gateway can translate between different protocols (PROFINET, EtherCAT, Ethernet Powerlink) and standard IEEE 802.1, enabling network compatibility while preserving real-time data transfer capabilities across different protocol domains.

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

3Loss of time

If time-based scheduling windows are configured, then latency is minimized, but scheduling complexity increases

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

Solution Approach 1:

The patent implements periodic time-based scheduling windows for data egress, where transmission opportunities occur at regular intervals defined by synchronization protocols. This periodic structure minimizes latency by guaranteeing regular transmission slots while reducing scheduling complexity through predictable, repeating patterns rather than arbitrary timing arrangements.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9967209B2Switch for scheduled data egress
Publication Date: 2018.05.08 NATIONAL INSTRUMENTS CORP
  • US9967209B2 patent drawing
  • US9967209B2 patent drawing
  • US9967209B2 patent drawing

AI summary

Systems and methods for scheduling data egress from a network switch. Systems may include switch circuitry, a plurality of ports, and a plurality of queues. Each port may be associated with a respective set of routing information for network packets and each port may be configured with a respective set of egress periods. Each network packet may have respective routing information and a type that specifies a respective egress period. Each queue may be associated with a respective network packet type and a port of the plurality of ports.