Slave Device Protocol Segmentation for Field Bus TCP/IP Coexistence

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing field bus systems face challenges in supporting both time-sensitive and non-time-sensitive protocols over the same physical connection without disrupting the field bus communication, particularly in initializing the Y port of the final slave device for TCP/IP communication and avoiding packet collisions with field bus packets.

Innovation Solution

Implementing packet filtering and arbitration logic in slave devices to prioritize time-sensitive field bus packets over non-time-sensitive TCP/IP packets, allowing the configurator to connect without interfering with field bus operations, and using special wake-up packets to activate TCP/IP communication while ensuring field bus packets are not disturbed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If the Y port of the final slave device is used for both field bus communication and TCP/IP configuration, then the number of physical ports is reduced, but packet collisions occur between time-sensitive field bus packets and non-time-sensitive TCP/IP packets

Engineering Contradiction:

Improvenumber of physical portsVSAvoidpacket collision avoidance

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The patent segments the packet handling process into two distinct paths: field bus packets are routed through the field bus logic module while TCP/IP packets are routed through the microcontroller. This segmentation allows both protocols to share the physical Y port without interfering with each other's timing requirements, resolving the contradiction between port reduction and packet collision avoidance.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by having the slave device detect and prioritize field bus packets before TCP/IP packets are processed. The field bus logic module is configured to give strict priority to field bus packets, ensuring that time-sensitive communications are handled first, thereby preventing packet collisions while sharing the physical port.

Inventive Principle:

Principle #10Preliminary action

2Ease of operation

If TCP/IP packets are allowed on the field bus network, then configurator can communicate with slave devices, but the strict timing requirements of field bus protocols are violated

Engineering Contradiction:

Improveconfigurator communicationVSAvoidtiming requirement compliance

Core Design Contradiction:

Ease of operationVSManufacturing precision

Solution Approach 1:

The patent applies local quality by giving different treatment to different packet types based on their destination and protocol requirements. Field bus packets receive strict priority handling with deterministic timing, while TCP/IP packets are processed only when field bus traffic is absent. This localized quality differentiation ensures timing requirements are met for critical communications while enabling configurator access.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system performs preliminary action by checking for field bus packet priority before allowing TCP/IP packet transmission. The field bus logic module is pre-configured to intercept and handle field bus packets first, ensuring that any TCP/IP communication via the Y port will not interfere with the strict timing requirements of field bus protocols.

Inventive Principle:

Principle #10Preliminary action

3Ease of operation

If the Y port is activated for TCP/IP communication, then configurator access is enabled, but field bus initialization fails due to incorrect responses from non-field bus devices

Engineering Contradiction:

Improveconfigurator accessVSAvoidfield bus initialization

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent implements dynamics by making the Y port's functional state changeable based on the operational phase of the field bus network. During field bus initialization, the Y port remains in field bus mode only. After successful initialization, the port dynamically switches to allow TCP/IP packets from the configurator, while maintaining field bus packet handling capability. This dynamic state transition resolves the contradiction between enabling configurator access and ensuring reliable field bus initialization.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS9634863B2Systems and methods for supporting two different protocols on a same physical connection

Publication Date: 2017.04.25 KOLLMORGEN CORP

AI summary

Systems and methods of supporting communications over a common network connection in a master-slave field bus network with a first type of packet formatted with a time-sensitive protocol and a second type of packet formatted with a non-time-sensitive protocol are provided. The slave devices are configured with filters to prevent the first type of packet from reaching a configurator and the second type from reaching a master device. The slave devices are also configured with arbitration logic so that the packets formatted with the time-sensitive protocol are provided with a priority over the packets formatted with the non-time-sensitive protocol.