Redundant Layer 2 Domain Interconnection for Loop-Free Network Redundancy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies lack a single protocol to connect disparate Layer 2 networks at multiple points without creating loops, limiting the ability to establish redundant connections between Operational Technology (OT) and Information Technology (IT) networks using different Layer 2 protocols.
Innovation Solution
Implementing Redundant Layer 2 Domain Interconnection (RLDI) by designating active and standby devices within each domain to manage data traffic and prevent loops, allowing RLDI devices to negotiate using multicast control frames and operate across different Layer 2 protocols such as Spanning Tree Protocol, Device Level Ring, and Resilient Ethernet Protocol.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple gateway connections are established between disparate Layer 2 networks, then network redundancy and connectivity are improved, but loops are created and protocol compatibility issues arise
Solution Approach 1:
The patent segments the gateway connections into active and standby roles. Each domain designates one active gateway connection and one standby gateway connection, dividing the redundant connections into functional segments that prevent loops while maintaining redundancy. The active gateway forwards traffic while the standby gateway blocks traffic, creating segmented control over the redundant paths.
Solution Approach 2:
The patent introduces intermediary control frames (multicast control frames) that mediate between the active and standby gateways. These control frames carry domain identifiers and gateway identifiers to coordinate the active/standby states, enabling protocol compatibility between disparate Layer 2 networks while preventing loops through coordinated control.
2Reliability
If redundant gateway connections are established between OT and IT networks, then connectivity reliability is improved, but protocol compatibility and loop prevention become complex
Solution Approach 1:
The patent creates a universal control mechanism that works across different Layer 2 protocols (Spanning Tree Protocol, Device Level Ring, Resilient Ethernet Protocol). The multicast control frames serve multiple functions: they identify domains, identify gateways, and coordinate active/standby states across protocol boundaries, providing universal compatibility without requiring protocol-specific complex coordination.
Solution Approach 2:
The patent implements feedback through multicast control frames that continuously communicate the active and standby states between gateways. Each gateway receives feedback about the other gateway's state and adjusts its own behavior accordingly, creating a closed-loop control system that maintains connectivity reliability while simplifying protocol coordination through standardized feedback messages.
3Object-generated harmful factors
If active and standby device designation is implemented, then loop prevention is improved, but device state management complexity increases
Solution Approach 1:
The patent enables devices to self-manage their active/standby states through automated negotiation using multicast control frames. Devices automatically determine their own state based on the protocol and network conditions, eliminating the need for external manual configuration or complex centralized control. The state management becomes self-service through automated peer-to-peer coordination.
Data Source
AI summary
Redundant Layer 2 Domain Interconnection may be provided. First, a first device in a first domain may be designated as an active device in response to the first device in the first domain negotiating with a second device in the first domain. The first device in the first domain may be connected to a first device in a second domain. The first domain may use a first protocol and the second domain may use a second protocol. Next, the first device in the first domain in response to being designated as the active device, may allow data traffic to pass between the first device in the first domain and the first device in the second domain. Then the second device in the first domain may be designated as a standby device in response to the first device in the first domain negotiating with the second device in the first domain. The second device in the first domain may be connected to a second device in the second domain. The second device in the first domain, in response to being designated as the standby device, may then block data traffic between the second device in the first domain and the second device in the second domain.