Gateway Virtual Interface Extension for Heterogeneous IoT Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing gateway devices in the Internet of Things architecture have poor generality due to fixed network interfaces, requiring different devices for different perception layer networks.
Innovation Solution
A method and apparatus that enables a gateway device with an Ethernet interface to create virtual interfaces corresponding to non-Ethernet interfaces on an interface extension device, allowing connection to various perception layer networks through the interface extension device, and implementing layer-2 protocol conversion to reduce resource consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a gateway device uses fixed network interfaces to connect to perception layer networks, then the connection is stable and reliable, but the gateway device has poor generality and requires different devices for different perception layer networks
Solution Approach 1:
The gateway device is enhanced with a virtual interface creation capability that allows a single physical gateway to support multiple perception layer network interfaces (PLC, RF, Zigbee, etc.) through virtualization. The virtual interface manager creates virtual interfaces on the Ethernet port that emulate different non-Ethernet interface types, enabling one gateway device to universally connect to various perception layer networks without requiring multiple specialized hardware devices.
Solution Approach 2:
The system creates virtual copies of non-Ethernet interfaces (PLC, RF, Zigbee) as virtual Ethernet interfaces on the gateway device. These virtual interfaces replicate the functionality and characteristics of physical non-Ethernet interfaces, allowing the gateway to handle multiple perception layer network protocols through a single physical Ethernet connection to the interface extension device.
2Reliability
If multiple specialized gateway devices are used for different perception layer networks, then each device can be optimized for its specific interface, but the system complexity increases and deployment becomes less flexible
Solution Approach 1:
An interface extension device is introduced as an intermediary between the perception layer networks and the gateway device. This intermediate device contains the actual non-Ethernet interfaces (PLC, RF, Zigbee) and communicates with the gateway through a standard Ethernet connection. The interface extension device acts as a mediator that translates and adapts between the diverse perception layer protocols and the gateway's Ethernet interface, simplifying the gateway's design while maintaining reliable connections to multiple network types.
Solution Approach 2:
The system architecture is segmented into two functional parts: the gateway device with a standard Ethernet interface and the interface extension device with multiple non-Ethernet interfaces. This segmentation separates the protocol-specific interface functionality into the extension device while keeping the gateway device simple and universal. The virtual interface manager on the gateway creates virtual interfaces that represent the physical interfaces on the extension device, maintaining clear functional boundaries.
3Adaptability or versatility
If the gateway device creates virtual interfaces for non-Ethernet interfaces, then the generality and flexibility are improved, but additional processing and resource consumption are required
Solution Approach 1:
The virtual interface creation and protocol conversion are performed only when and where needed - specifically at the gateway device for interfaces that require virtualization. The interface extension device handles the actual physical connections and basic protocol handling for each perception layer network, so the gateway only needs to perform partial processing for the specific virtual interfaces it needs to support, rather than implementing all protocol conversions locally.
Data Source
Figure 1~2
Figure 3
Figure 4~6
AI summary
This application discloses an interface extension method, apparatus, and system. A gateway device receives interface information sent by an interface extension device, where an Ethernet interface of the interface extension device is connected to a target Ethernet interface of the gateway device, and the interface information includes an interface type and a MAC address of a first non-Ethernet interface of the interface extension device. The gateway device creates a first virtual interface on the target Ethernet interface based on the interface information, where the first virtual interface corresponds to the first non-Ethernet interface, and an interface type of the first virtual interface is an Ethernet interface. The gateway device sends an interface creation success notification to the interface extension device. The gateway device may obtain data of the first non-Ethernet interface through the first virtual interface, thereby implementing interface extension of the gateway device. The gateway device has good generality.