Ethernet Network Device Series Slave Topology

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Ethernet local area networks using hubs or switches are inadequate for applications requiring deterministic real-time data transmission and synchronization of peripherals due to high latency and unpredictability, leading to data collisions and unreliable synchronization.

Innovation Solution

An Ethernet network device with a series connection of slave devices, each equipped with a physical device and an integrated circuit that processes and modifies data packets in real-time, ensuring fast and collision-free data transmission by activating transmission only after a predetermined number of bytes have been received, and modifying data without processing delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If hubs or switches are used in Ethernet LANs to connect computers and peripherals, then data transmission speed is improved, but data collisions occur and transmission latency becomes unpredictable

Engineering Contradiction:
Improvedata transmission speedVSAvoidtransmission reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The invention segments the network into a hierarchical structure with a root hub and multiple level-1 hubs, each serving specific groups of peripherals. This segmentation reduces the number of peripherals connected to each hub, thereby reducing data collisions while maintaining fast transmission speeds through the organized tree topology

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention introduces level-1 hubs as intermediary devices between the root hub and individual peripherals. These intermediate hubs act as mediators that manage data flow, reduce collisions by limiting broadcast domains, and maintain deterministic latency through controlled signal propagation

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If hubs are used for simple signal propagation, then device complexity is reduced, but data collisions increase and synchronization becomes unreliable

Engineering Contradiction:
Improvenetwork device complexityVSAvoidsynchronization reliability
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The network is segmented into multiple hierarchical levels with standardized connection protocols. Each hub operates with simple signal propagation functions, but the overall system achieves reliable synchronization through the structured tree topology and controlled signal paths

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention changes the network topology parameter from a flat hub structure to a hierarchical tree structure. This parameter change maintains the simplicity of individual hub devices while fundamentally improving synchronization reliability through deterministic signal propagation paths

Inventive Principle:
Principle #35Parameter changes

3Reliability

If switches are used to route data packets, then data collisions are reduced, but processing delays increase and latency becomes uncontrollable

Engineering Contradiction:
Improvecollision-free transmissionVSAvoidprocessing delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The invention extracts the intelligent routing function from the network infrastructure and places it at the host computer level. The hubs are reduced to simple signal propagators without processing delays, while the host manages data routing to eliminate collisions, achieving both collision-free transmission and deterministic latency

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If the number of nodes in the network is increased, then network versatility is improved, but the probability of data collisions increases

Engineering Contradiction:
Improvenetwork scalabilityVSAvoidcollision probability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The network is segmented into multiple hierarchical levels where each hub serves a limited number of peripherals. This segmentation allows the network to scale to many nodes while maintaining low collision probability at each segment, as hubs only broadcast to their directly connected peripherals

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention transitions from a two-dimensional flat network topology to a three-dimensional hierarchical tree structure. This dimensional change organizes nodes in levels and branches, allowing scalable network growth while maintaining controlled signal propagation paths and reducing collision probability through structural organization

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP2930896B1Ethernet network device and local ethernet network
Publication Date: 2016.11.02 DVE PROGETTAZIONE ELETTRONICA DI BRUGNONI GABRIELE
  • EP2930896B1 patent drawingFigure 1
  • EP2930896B1 patent drawingFigure 2
  • EP2930896B1 patent drawingFigure 3~4

AI summary

The present invention regards an Ethernet network device (1) comprising: a host (2), a plurality of slave devices (3) connected to the host and comprising at least one first and one last slave devices (3a, 3b). Each slave device (3) has: a PHY-chip (4) and an integrated device (5) connected to the PHY-chip (4). Further, the network device (1) comprises a circuit (6) on which the host (2) and slave devices (3) with series-type connection, are active; the devices (3) have the same MAC address so that each integrated device (5) is configured for receiving the same data packet (D) sendable to the host (2), each device (5) is configured for: receiving a data packet (D) according to an Ethernet protocol, said data packet being of the type comprising a preamble (P), a receiver MAC address (MD), a source MAC address (MS), a field identifying the used protocol type (FT), a payload field (DIF), a cyclical redundancy control field (FCS); reading at least part of the payload (DIF) contents; withdrawing a part of the data of the payload (DIF) containing the information destined to the slave device itself; modifying at least part of the data contained in the payload (DIF) and/or data from the cyclical redundancy control field (FCS); simultaneously with the withdrawal of at least a part of the payload data (DIF), modifying at least a part of data inside the same payload (DIF) of the same data packet (D).