Network Interface Emulation for Remote Peripheral Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no simple solution for automatically and remotely accessing the interfaces of terminals with multiple physical interfaces of different types, as existing protocols like USB over IP only allow USB interfaces to be transferred and require manual association.
Innovation Solution
A method of emulating a physical interface in a network, allowing bidirectional communication between peripheral equipment and terminals, even when not directly connected, by associating network terminals with emulation devices that manage data routing and prioritize access, enabling transparent communication and pre-association of equipment with terminals.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If USB over IP protocol is used to transmit USB signals over network, then remote USB interface access is enabled, but manual association between terminal and physical interface is required
Solution Approach 1:
The system performs self-association by automatically matching virtual interfaces with physical interfaces based on interface type and network configuration, eliminating the need for manual user intervention in the association process
Solution Approach 2:
The system uses interface capability feedback from terminals to automatically determine appropriate physical interface associations, creating a closed-loop automatic configuration mechanism
2Adaptability or versatility
If USB over IP protocol is used, then USB interface remote use is enabled, but the solution is limited to USB-type interfaces only
Solution Approach 1:
The system creates a universal interface emulation framework that can handle multiple interface types (USB, SD card, NFC, etc.) through a common virtualization mechanism, making the solution applicable to various interface protocols beyond just USB
Solution Approach 2:
The patent introduces a universal emulation device as an intermediary between terminals and physical interfaces, which mediates the communication and adaptation between different interface types through standardized virtual interface protocols
3Ease of operation
If terminals are located far from user or have difficult to access interfaces, then physical connection is required, but user accessibility is reduced
Solution Approach 1:
The emulation device acts as a physical intermediary located near the user, which receives peripheral connections locally and remotely forwards them to terminals through the network, eliminating the need for users to physically access distant terminals
Solution Approach 2:
The system segments the physical connection function from the terminal by introducing a separate emulation device that handles local peripheral connections, while the terminal handles remote data processing independently
4Adaptability or versatility
If multiple physical interfaces of different types are available on terminals, then interface versatility is improved, but automatic access to specific interfaces becomes complex
Solution Approach 1:
The system automatically performs interface matching by analyzing interface capabilities and terminal requirements, enabling self-configuration without user intervention even when multiple different interface types are available
Solution Approach 2:
The system uses interface parameter matching (interface type, capabilities, protocols) to automatically identify and associate the correct physical interface with each terminal, simplifying access to specific interfaces among multiple options
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Emulation of physical equipment. The invention concerns a method for emulating a physical interface (S1-S4) of a device (C, T2-T5) capable of communicating in a network (9). The physical interface (S1, A1) is capable of receiving at least one piece of peripheral equipment (P1, P7, P6). The method is characterised in that it comprises: - a step (E11) of pre-association in order to establish a set of possible associations (TAS, S3/T3, S3/T4) between said physical interface (S1-S4) and at least one software interface (VA1, VS1- VS4) of at least one terminal (T1-T4); - a step (E13-E16) of selecting an association (S3/T3) between said physical interface (S3) and at least one software interface (VS3/T3) of at least one terminal, from all the possible associations (VS3/T3, VS3/T4); - a step (E18) of routing the messages between the physical interface (S1- S4) and the associated software interface (VA1, VS1-VS4).