Remote access method, connection access method, device and equipment of USB (Universal Serial Bus) equipment

Abstract

The invention provides a remote access method, a connection access method, devices and equipment for USB equipment, and relates to the technical field of computer peripheral connection and communication. The method comprises the following steps: a server receives USB equipment information reported by access end equipment, and performs registration processing based on the USB equipment information; the USB equipment information is generated according to the USB equipment. And the server side pushes the USB equipment information to at least one remote use side. And the server establishes a data transmission channel between the access end equipment and the remote use end in response to the pairing request from the remote use end. And based on the data transmission channel, the remote use end creates a virtual USB device node corresponding to the USB device on a host machine where the remote use end is located, so that the host machine can access the remote USB device through the virtual USB device node. The method is used for realizing distributed unified management and dynamic scheduling of the USB equipment.

Description

Technical Field

[0001] This application relates to the field of computer peripheral connection and communication, and more specifically, to a remote access method, connection access method, apparatus and device for a USB device. Background Technology

[0002] Currently, the Universal Serial Bus (USB) serves as the de facto standard interface for connecting electronic devices, and its applications are ubiquitous. However, traditional USB connections are limited by the length of the physical cable (typically no more than 5 meters), requiring the device to be physically adjacent to the host. This presents significant inconvenience and limitations in practical applications, such as: In data centers or server rooms, administrators need to enter noisy and confined server racks to operate USB devices (such as installing drivers and updating firmware). In office or laboratory environments, expensive or specialized USB devices (such as hardware dongles and professional instruments) cannot be easily shared among multiple users or workstations, resulting in low resource utilization. Emerging cloud computing and Virtual Desktop Infrastructure (VDI) users cannot seamlessly use locally dedicated USB devices (such as bank USB tokens and high-precision drawing tablets) for remote cloud desktop sessions.

[0003] In existing technologies, the connection and management of current USB devices mainly rely on physical direct connections, lacking the flexible scheduling and virtualization management capabilities achieved through networks. Traditional USB hubs only expand physical ports; all USB signals must be transmitted to the host through physical lines, making cross-network access impossible.

[0004] Therefore, there is an urgent need for a more universal and efficient USB device connectivity extension solution that can flexibly meet the needs of different scenarios and take into account both remote network access and local physical layer extension. Summary of the Invention

[0005] The purpose of this application is to provide a remote access method, connection access method, apparatus and device for USB devices, so as to solve the above-mentioned problems existing in the prior art and realize the distributed unified management and dynamic scheduling of USB devices.

[0006] Firstly, a method for remotely accessing a USB device is provided, the method including: The server receives USB device information reported by the access device and performs registration processing based on the USB device information; wherein, the access device is physically connected to at least one USB device; the USB device information is generated based on the USB device. The server pushes the USB device information to at least one remote user terminal; The server responds to the pairing request from the remote user and establishes a data transmission channel between the access device and the remote user. Based on the data transmission channel, the remote user creates a virtual USB device node corresponding to the USB device on its own host machine, so that the host machine can access the remote USB device through the virtual USB device node.

[0007] Secondly, a connection access method for a USB device is provided, applied to a USB connection device, the USB connection device being provided with an upstream USB interface and a downstream USB interface; the method includes: If a USB device is detected inserted into the downstream USB interface, and the USB connection device is connected to the host machine through the upstream USB interface, then in a preset pass-through mode, the device descriptor of the USB device is forwarded to the host machine; wherein, the device descriptor is used to establish a USB communication channel between the host machine and the USB device; If an access request is received from the host machine, the response data is determined, and the response data is physically transmitted to the host machine based on the USB communication channel.

[0008] Thirdly, a remote access device for a USB device is provided, the device including: The registration module is used for the server to receive USB device information reported by the access device and perform registration processing based on the USB device information; wherein, the access device is physically connected to at least one USB device; the USB device information is generated based on the USB device. The push module is used by the server to push the USB device information to at least one remote user terminal; A pairing module is used by the server to establish a data transmission channel between the access device and the remote user in response to a pairing request from the remote user. An access module is used by the remote user to create a virtual USB device node corresponding to the USB device on the host machine where the remote user is located, based on the data transmission channel, so that the host machine can access the remote USB device through the virtual USB device node.

[0009] Fourthly, an electronic device is provided, which includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus. Memory, used to store computer programs; When a processor executes a program stored in memory, it implements any of the steps described in the first aspect above.

[0010] Fifthly, a computer-readable storage medium is provided, wherein a computer program is stored therein, and when executed by a processor, the computer program implements the steps of any of the methods described in the first aspect above.

[0011] The remote access method, connection access method, apparatus, and device for USB devices provided in this application embodiment include: A server receives USB device information reported by an access device and performs registration processing based on the USB device information; wherein the access device is physically connected to at least one USB device; the USB device information is generated based on the USB device. The server records the USB device information and broadcasts it to pre-registered remote users, which constitutes a list of available USB devices. In response to a pairing request from a remote user, the server establishes a data transmission channel between the access device and the remote user. Based on the data transmission channel, the remote user creates a virtual USB device node corresponding to the USB device on its own host machine, enabling the host machine to access the remote USB device through the virtual USB device node. In this solution, the server constructs a unified device registration, scheduling, and mapping platform based on a unified device registration, authentication, and permission management system; the access device and the simulated device are dynamically registered, paired, and mapped by the server. The software-side virtual driver implements a synchronization mechanism with the server, enabling remote access and virtualization mapping of USB devices via the network. This expands the connectivity and access capabilities of USB devices, allowing for remote access, sharing, virtual mapping, and dynamic switching, improving resource utilization and simplifying maintenance. In multi-terminal, multi-scenario applications (such as cloud terminals, remote offices, and virtual laboratories), users can easily migrate or remotely access USB devices between different hosts. It enables multi-mode collaboration of USB devices, including ordinary hubs, access terminals, analog terminals, and software terminals. It supports remote registration, virtual connections, and transparent forwarding, and allows for flexible switching between multiple modes. It is compatible with traditional USB direct connection scenarios, achieving network encapsulation, forwarding, and virtualization of USB signals and data. This allows USB devices to dynamically bind and switch between different hosts. Furthermore, it provides an open server-side management architecture that can be scaled to multiple users and nodes, enabling distributed unified management and dynamic scheduling of USB devices. Attached Figure Description

[0012] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 A flowchart illustrating a remote access method for a USB device provided in an embodiment of this application; Figure 2 A flowchart illustrating another remote access method for a USB device provided in an embodiment of this application; Figure 3 A flowchart illustrating another method for remote access to a USB device provided in this application embodiment; Figure 4 A flowchart illustrating yet another method for remote access to a USB device provided in this application; Figure 5 A flowchart illustrating yet another method for remote access to a USB device provided in this application; Figure 6 A flowchart illustrating yet another method for remote access to a USB device provided in this application; Figure 7 A flowchart illustrating a method for connecting and accessing a USB device provided in this application; Figure 8 A flowchart illustrating another method for connecting and accessing a USB device provided in this application; Figure 9 A schematic diagram of the structure of a remote access device for a USB device provided in an embodiment of this application; Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0014] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise defined, the technical or scientific terms used in this application should have the ordinary meaning understood by those skilled in the art. The words "first," "second," and similar terms used in this application do not indicate any order, quantity, or importance, but are only used to distinguish different components. The words "comprising" or "including," etc., mean that the element or object preceding the word covers the element or object listed after the word and its equivalents, but do not exclude other elements or objects. The words "connected," "coupled," or "connected," etc., are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up," "down," "left," "right," etc., are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0015] Currently, the Universal Serial Bus (USB) serves as the de facto standard interface for connecting electronic devices, and its applications are ubiquitous. However, traditional USB connections are limited by the length of the physical cable (typically no more than 5 meters), requiring the device to be physically adjacent to the host. This presents significant inconvenience and limitations in practical applications, such as: In data centers or server rooms, administrators need to enter noisy and confined server racks to operate USB devices (such as installing drivers and updating firmware). In office or laboratory environments, expensive or specialized USB devices (such as hardware dongles and professional instruments) cannot be easily shared among multiple users or workstations, resulting in low resource utilization. Emerging cloud computing and Virtual Desktop Infrastructure (VDI) users cannot seamlessly use locally dedicated USB devices (such as bank USB tokens and high-precision drawing tablets) for remote cloud desktop sessions.

[0016] In one example, existing USB device connectivity and management primarily rely on direct physical connections, lacking the flexible scheduling and virtualization management capabilities achieved through a network. Traditional USB hubs only expand physical ports; all USB signals must be transmitted to the host via physical lines, making cross-network access impossible.

[0017] In one example, some network USB Server products (such as USB over IP devices) can achieve single-end device sharing, but they typically do not support multi-mode, multi-pairing, or multi-node distributed collaboration. Software-based virtual USB solutions (such as some USBRedirector tools) rely on driver-level forwarding and lack a unified hardware management and security registration mechanism. USB redirection mechanisms in cloud desktop systems are often tied to specific virtualization platforms and lack open and standardized device collaboration capabilities. 1) The lack of security authentication and distributed management mechanisms leads to chaotic device resource scheduling and poor system stability.

[0018] Therefore, there is an urgent need for a more universal and efficient USB device connectivity extension solution that can flexibly meet the needs of different scenarios and take into account both remote network access and local physical layer extension.

[0019] The remote access method for USB devices provided in this application can be applied to electronic devices. To achieve the above-mentioned inventive concept, this invention proposes a layered technical solution system. This system revolves around a core logic: intelligent "redirection" of the USB communication link. This redirection can occur at two levels: At the network protocol layer: USB protocol data packets are encapsulated into network protocol packets and transmitted over the Internet or local area network, thereby achieving "logical redirection" across space.

[0020] At the physical signal layer: the electrical signals of the USB are cleanly amplified and relayed, enabling "geo-redirection" of the physical connection without altering any data content.

[0021] Based on this, the technical solution of the present invention is specifically embodied in the following two implementation methods, which can be implemented independently or in combination, and together they constitute the overall inventive concept of the present invention.

[0022] Therefore, in this invention, the term "electronic device" in the claims has a specific meaning, generally referring to any hardware entity configured to implement the core function of "USB access capability redirection" of this invention. Depending on the implementation scenario, it can take two forms: a distributed USB management device or an integrated USB connection device. Specifically, at the network protocol layer, the electronic device can be a distributed USB management device; at the physical signal layer, the electronic device can be a USB connection device.

[0023] Despite their different physical forms, both the 'distributed USB management device' and the 'integrated USB connection device' are specific implementations of the same inventive concept—namely, the location-independent redirection of access capabilities to USB devices—in this invention.

[0024] The preferred embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application. Furthermore, the embodiments and features in the embodiments of this application can be combined with each other without conflict.

[0025] Figure 1 This is a flowchart illustrating a remote access method for a USB device provided in an embodiment of this application. Figure 1 As shown, the method may include: Step S101: The server receives the USB device information reported by the access device and performs registration processing based on the USB device information; wherein, the access device is physically connected to at least one USB device; the USB device information is generated based on the USB device.

[0026] For example, this embodiment is a networked remote access based on the network protocol layer. In this embodiment, the electronic device is specifically embodied as a distributed USB management device. This device is not a physical unit, but a collaborative system logically coupled by a service terminal system, an access terminal system, and a remote access terminal system via wired or wireless networks. These three subsystems work closely together functionally to form a virtual device entity that achieves a unified management goal. The distributed USB management device includes distributed USB management devices based on analog terminal devices and distributed USB management devices based on software clients.

[0027] Optional, Figure 2 A flowchart illustrating another remote access method for a USB device provided in this application embodiment is shown below. Figure 2 As shown, the distributed USB management device based on analog terminal devices includes a server terminal system (i.e., Figure 2 The server-side system, also known as the server terminal, and the access terminal system (i.e.) Figure 2 Access terminal equipment) and remote access terminal system (i.e. Figure 2 The analog terminal device in the middle, also known as the remote user terminal. Figure 2 It also includes USB devices and the host machine.

[0028] The server-side system includes a device registration and authentication module, a device pairing and scheduling module, and a data routing and forwarding module. The device registration and authentication module is responsible for the registration, authentication, and status management of access devices and analog devices; the device pairing and scheduling module is used to match access devices and analog devices according to user instructions or policies to achieve logical binding; and the data routing and forwarding module is used to coordinate the establishment and maintenance of network data channels to ensure the orderly forwarding of USB transmissions.

[0029] The access device includes a USB device interface module, a network communication module, and a registration client module. The USB device interface module is used to physically connect the actual USB device; the network communication module is responsible for establishing network connections with the server and analog devices; and the registration client module is used to report its own information and the connected USB devices to the server when the access device starts up.

[0030] The simulated terminal device includes a registration client module, a network communication module, a virtual USB interface module, and a host connection interface. The registration client module reports its own information and connected USB devices to the server when the simulated terminal device starts up. The network communication module maintains data and control signaling channels with the access terminal device and the server; the virtual USB interface module converts USB data frames received from the network into local USB protocol data; and the host connection interface allows the device to be plugged into the host machine via a USB male connector or other interface, enabling physical layer access.

[0031] The host machine includes a USB controller. The USB controller is used to identify virtual USB devices provided by the emulated terminal devices. From the host machine's perspective, virtual USB devices are indistinguishable from real USB devices.

[0032] Optional, Figure 3 A flowchart illustrating another remote access method for a USB device provided in this application embodiment is shown below. Figure 3 As shown, a software client-based distributed USB management device includes a server subsystem (i.e., Figure 3 The server-side system and the access subsystem (i.e.) Figure 3 Access terminal equipment) and remote access terminal system (i.e. Figure 3 The client software in the process can also be called the remote user terminal or software terminal. Figure 3 It also includes USB devices and a host operating system. The server-side system includes a device registration and authentication module, a device pairing and scheduling module, and a data routing and forwarding module. The device registration and authentication module manages the registration, login, and heartbeat detection of access devices and client software. The device pairing and scheduling module logically binds a specific access device to the client software based on user actions. The data routing and forwarding module is responsible for establishing data transmission channels between paired devices and maintaining session state.

[0033] The access device includes a USB device interface module, a network communication module, and a registration client module. The USB device interface module is responsible for collecting data from the actual USB device; the network communication module is used to encapsulate the USB transmission data via TCP / UDP protocol and send it to the target software, i.e., the client software; the registration client module is used to periodically report device status, connection status, and available USB resource information to the server.

[0034] The client software includes a registration client module, a network communication module, a virtual USB access device, and a host connection interface. The registration client module reports its own information and connected USB devices to the server upon device startup. The network communication module maintains data and control signaling channels with the access device and the server. The virtual USB access device creates a virtual USB device within the software, which the host machine recognizes as a real USB device. The host connection interface allows the device to be plugged into the host machine via a USB male connector or other interface, enabling physical layer access.

[0035] The host operating system includes a USB subsystem. The USB subsystem is used to identify device nodes created by virtual drivers, allowing applications to transparently access remote USB devices. In this step, when the access device detects a physical connection with at least one USB device, it generates USB device information and reports its own information and USB device information to the server. The USB device information includes the connected USB devices. The server receives the USB device information reported by the access device and performs registration processing based on the USB device information.

[0036] Step S102: The server pushes the USB device information to at least one remote user terminal.

[0037] For example, the server records USB device information and broadcasts this information to pre-registered remote users, which constitutes a list of available USB devices. The remote users can be either virtual or software-based, and there is no limitation on which.

[0038] Step S103: The server responds to the pairing request from the remote user and establishes a data transmission channel between the access device and the remote user.

[0039] For example, a user selects a USB device to access on a remote terminal. Based on this selection, the remote terminal generates a pairing request and sends it to the server. The server receives the pairing request from the remote terminal, establishes a logical pairing relationship between the access device and the remote terminal, sends a pairing instruction corresponding to the logical pairing relationship to the access device, and thus establishes a data transmission channel between the access device and the remote terminal.

[0040] Step S104: Based on the data transmission channel, the remote user creates a virtual USB device node corresponding to the USB device on the host machine where the remote user is located, so that the host machine can access the remote USB device through the virtual USB device node.

[0041] For example, the remote user creates a virtual USB device node corresponding to the USB device on its own host machine based on the data transmission channel. The user can access the virtual USB device node on the host machine. Based on the user's access operation, the host machine generates an access request and sends it to the access device via the data transmission channel. The access device generates response data according to the received access request and returns the response data to the host machine via the data transmission channel, thus enabling the host machine to access the remote USB device through the virtual USB device node.

[0042] The method provided in this application embodiment involves a server receiving USB device information reported by an access device and performing registration processing based on the USB device information. The access device is physically connected to at least one USB device, and the USB device information is generated based on the USB device. The server pushes the USB device information to at least one remote user. In response to a pairing request from a remote user, the server establishes a data transmission channel between the access device and the remote user. Based on the data transmission channel, the remote user creates a virtual USB device node corresponding to the USB device on its own host machine, enabling the host machine to access the remote USB device through the virtual USB device node. In this solution, the server constructs a unified device registration, scheduling, and mapping platform based on a unified device registration, authentication, and permission management system. The access device and the simulated device are dynamically registered, paired, and mapped by the server. The virtual driver implementation on the software side synchronizes with the server, enabling remote access and virtualization mapping of USB devices via the network. This expands the USB device connection and access capabilities, realizing remote access, sharing, virtual mapping, and dynamic switching of USB devices, improving resource utilization and simplifying maintenance. In multi-terminal, multi-scenario applications (such as cloud terminals, remote office, and virtual laboratories), users can easily migrate or remotely access USB devices between different hosts, enabling multi-mode collaboration of USB devices as ordinary hubs, access terminals, analog terminals, and software terminals. It supports remote registration, virtual connections, and transparent forwarding, supports flexible switching between multiple modes, is compatible with traditional USB direct connection usage scenarios, realizes network encapsulation, forwarding, and virtualization of USB signals and data, and enables USB devices to be dynamically bound and switched between different hosts. It also provides an open server-side management architecture that can be expanded to multiple users and multiple nodes, and can be widely used in cloud computing, remote office, KVM seat management, and other fields, thereby realizing distributed unified management and dynamic scheduling of USB devices.

[0043] Figure 4 A flowchart illustrating another remote access method for a USB device provided in this application is shown below. Figure 4 As shown, in this embodiment... Figure 1Based on the embodiments, the method is described in detail below, and the method includes: Step S201: The server receives the USB device information reported by the access device and performs registration processing based on the USB device information; wherein, the access device is physically connected to at least one USB device; the USB device information is generated based on the USB device.

[0044] In one example, step S201 includes multiple implementation methods: The first implementation method of step S201: If the access device has a network communication interface, the server receives the USB device information reported by the network communication interface and performs registration processing based on the USB device information.

[0045] The second implementation method of step S201: The access device does not have a network communication interface. The access device accesses the network through a network proxy host device connected to the network, and the network proxy host device performs the registration step with the server on its behalf. The server receives the USB device information reported by the network proxy host device and performs registration processing based on the USB device information.

[0046] For example, this step is a networked remote access based on the network protocol layer. When the access device detects a physical connection with at least one USB device, it generates USB device information and reports its own information and USB device information to the server. The USB device information includes the connected USB devices. The server receives the USB device information reported by the access device and performs registration processing based on the USB device information.

[0047] In the first implementation method of step S201, Figure 5 A flowchart illustrating another remote access method for a USB device provided in this application is shown below. Figure 5 As shown, if the access device has a network communication interface, it can perform remote mapping through its own network communication interface. The user inserts a USB device into the access device's USB port. After detecting the new USB device, the access device registers the USB device information with the server through its built-in network communication interface (such as Ethernet or Wi-Fi). The server receives the USB device information reported by the access device through its network communication interface and performs registration processing based on the USB device information.

[0048] In the second implementation method of step S201, Figure 6 A flowchart illustrating another remote access method for a USB device provided in this application is shown below. Figure 6As shown, the access device lacks a network communication interface and achieves remote mapping through a network proxy host device (PC / mobile phone, etc.). The user inserts a USB device into the access device's USB port. The access device connects to the network proxy host device (such as a PC, mobile phone, or router) via the USB port. The access device accesses the network through the network proxy host device, and the network proxy host device acts as an agent in the registration process with the server. The network proxy host device identifies the access device's functional modules and loads the communication or network proxy driver. After detecting its lack of network capability, the access device actively requests a network proxy channel from the network proxy host device. The network proxy host device registers with the server system on behalf of the access device, uploading data including the access device's unique identifier, USB device information, and connection status. The server receives the registered access device and USB device information reported by the network proxy host device and processes the registration based on the USB device information.

[0049] Step S202: The remote user terminal includes an analog terminal or a software terminal; the server pushes the USB device information to at least one analog terminal or a software terminal.

[0050] For example, the remote user end includes an analog end or a software end. For example... Figure 5 As shown, the server records the USB device status based on the USB device information and broadcasts a list of available USB devices to registered remote users (simulated or software clients). Figure 6 As shown, the server pushes the available USB device information to the registered remote users (simulation / software).

[0051] Optionally, if the remote user is an analog terminal, the server pushes the USB device information to at least one analog terminal; or, if the remote user is an analog terminal or a software terminal, the server pushes the USB device information to at least one analog terminal.

[0052] Step S203: The server responds to the pairing request from the remote user and establishes a data transmission channel between the access device and the remote user.

[0053] In one example, step S203 includes multiple implementation methods: The first implementation method of step S203: The server responds to the pairing request from the remote user, establishes a first logical pairing relationship between the access device and the remote user, and sends a first pairing instruction corresponding to the first logical pairing relationship to the access device; wherein, the pairing request includes the USB device to be paired; the first pairing instruction is used to establish a data transmission channel; the data transmission channel is from the access device to the remote user; or, it is from the access device to the remote user via the server.

[0054] The second implementation method of step S203: The access device does not have a network communication interface, and the access device accesses the network through a network proxy host device connected to the network; the server responds to the pairing request from the remote user, establishes a second logical pairing relationship between the access device, the network proxy host device, and the remote user, and sends a second pairing instruction corresponding to the second logical pairing relationship to the network proxy host device; so that the network proxy host device forwards the second pairing instruction to the access device; wherein, the pairing request includes the USB device to be paired; the second pairing instruction is used to establish a data transmission channel; the data transmission channel is from the access device through the network proxy host device to the remote user.

[0055] For example, such as Figure 5 As shown, the user selects the USB device to access on the remote terminal and initiates a pairing request to the server. The first access request includes the USB device to be accessed. Based on the pairing request, the server establishes a first logical pairing relationship between the access device and the remote terminal, generates a first pairing instruction corresponding to the first logical pairing relationship, and sends the first pairing instruction to the access device. The first pairing instruction is used to establish a data transmission channel. Upon receiving the first pairing instruction, the access device establishes a point-to-point or server-intermediate data transmission channel between itself and the remote terminal. The data transmission channel can be from the access device to the remote terminal, or from the access device to the remote terminal via the server.

[0056] like Figure 6 As shown, the access device lacks a network communication interface. In this case, the access device connects to the network through a network proxy host device. The user selects the device to access on the remote end. Based on the user's selection, the remote end generates a pairing request and sends it to the server. This pairing request is used for device connection and includes the USB device to be paired. The server receives the pairing request, verifies it, and generates a second pairing instruction corresponding to the second logical pairing relationship. It establishes the second logical pairing relationship between the access device, the network proxy host device, and the remote end, and sends the second pairing instruction to the network proxy host device. This second pairing instruction is used to establish a data transmission channel. The network proxy host device then forwards the pairing information to the access device. A data transmission channel based on the network proxy of the network proxy host device is established between the access device and the remote end, i.e., a USB data channel (which can be a TCP, QUIC, or WebSocket tunnel). The data transmission channel is relayed from the access device to the remote end via the network proxy host device.

[0057] Step S204: Based on the data transmission channel, the remote user creates a virtual USB device node corresponding to the USB device on the host machine where the remote user is located, so that the host machine can access the remote USB device through the virtual USB device node.

[0058] For example, such as Figure 5 As shown, the remote user creates a virtual USB device node on its own host machine based on the data transmission channel, which the host machine can then recognize. The host machine accesses the remote USB device through the virtual USB driver, and the access request is forwarded by the remote user to the access device. The access device executes the actual USB device operation and returns a response according to the data transmission channel. The response result is then sent back to the host machine via the remote user, forming a complete remote USB access loop.

[0059] like Figure 6 As shown, the remote user creates a virtual USB device node on the host machine (remote PC, etc.) through a local driver or software module, making the host machine recognize the device as a local connection. The host machine (remote end) accesses the remote USB device through the virtual USB driver, initiating an access request. The access request is forwarded by the remote user to the network proxy host device, and then by the network proxy host device to the access end device. The access end device parses the access request and performs the corresponding operation on the real USB device. After the USB device completes its operation, it sends the response data back layer by layer according to the data transmission channel. The host machine finally obtains the complete response data, realizing remote interaction with the real USB device.

[0060] Therefore, the embodiments of this application support the main modes such as USB device simulation and virtual access.

[0061] The method provided in this application embodiment involves a server receiving USB device information reported by an access device and performing registration processing based on the USB device information. The access device is physically connected to at least one USB device. The USB device information is generated based on the USB device. Remote users include either analog or software terminals. The server pushes the USB device information to at least one analog or software terminal. In response to a pairing request from the remote user, the server establishes a data transmission channel between the access device and the remote user. Based on the data transmission channel, the remote user creates a virtual USB device node corresponding to the USB device on its own host machine, enabling the host machine to access the remote USB device through the virtual USB device node. In this solution, the server constructs a unified device registration, scheduling, and mapping platform based on a unified device registration, authentication, and permission management system. The access device and analog terminal use a dynamic registration, pairing, and mapping mechanism through the server. The virtual driver implementation in the software synchronizes with the server, enabling remote access and virtualization mapping of USB devices via the network. This expands the USB device connection and access capabilities, enabling remote access, sharing, virtual mapping, and dynamic switching of USB devices, improving resource utilization and simplifying maintenance. In multi-terminal, multi-scenario applications (such as cloud terminals, remote offices, and virtual laboratories), users can easily migrate or remotely access USB devices between different hosts, enabling multi-mode collaboration of USB devices as ordinary hubs, access terminals, analog terminals, and software terminals. It supports remote registration, virtual connections, and transparent forwarding, allowing flexible switching between multiple modes and compatibility with traditional USB direct connection scenarios. It achieves network encapsulation, forwarding, and virtualization of USB signals and data, enabling dynamic binding and switching of USB devices between different hosts. It also provides an open server-side management architecture, scalable to multiple users and nodes, and can be widely applied in cloud computing, remote offices, KVM seat management, and other fields, thereby achieving distributed unified management and dynamic scheduling of USB devices. Software support is also provided, allowing terminal hosts without hardware devices to virtually connect to USB devices via software. Furthermore, it supports security authentication, bandwidth control, device identification, and permission management, enhancing device security and controllability and preventing unauthorized device access.

[0062] Figure 7 A flowchart illustrating a method for connecting and accessing a USB device provided in this application is shown below. Figure 7 As shown, the method is applied to a USB connection device, which has an upstream USB interface and a downstream USB interface; the method includes: Step S301: If it is detected that a USB device is inserted into the downstream USB interface and the USB connection device is connected to the host machine through the upstream USB interface, then in the preset pass-through mode, the device descriptor of the USB device is forwarded to the host machine; wherein, the device descriptor is used to establish a USB communication channel between the host machine and the USB device.

[0063] For example, in this embodiment, the electronic device is used directly as a regular USB adapter, achieving physical pass-through. Specifically, the electronic device is an integrated USB connection device (or pass-through device). The USB connection device implements the aforementioned redirection function within a single physical hardware unit through circuit pass-through.

[0064] Figure 8 A flowchart illustrating another USB device connection access method provided in this application is shown below. Figure 8 As shown, the user inserts a USB device (such as a USB flash drive, mouse, or camera) into the USB female port of the USB connector. The user then inserts the USB connector into the USB port of the host machine (e.g., a PC), and the host machine recognizes the USB connector as a regular USB adapter. If the USB connector detects at least one USB device inserted into the downstream USB port, and the USB connector is connected to the host machine via the upstream USB port, the USB connector is in a preset "passthrough mode," where the internal USB bus directly connects the upstream and downstream USB ports. In passthrough mode, the host machine initiates a device enumeration process to the USB connector, and the USB connector transparently forwards the device descriptor to the host machine. After enumeration is complete, a standard USB communication channel is established between the host machine and the USB device.

[0065] Step S302: If an access request is received from the host machine, determine the response data and physically transmit the response data to the host machine based on the USB communication channel.

[0066] For example, such as Figure 8 As shown, if an access request is received from the host machine, the response data is determined and physically transmitted to the host machine based on the USB communication channel. That is, all control and data transmission requests are directly transmitted by the USB connection device without involving the network or virtualization.

[0067] The method provided in this application embodiment detects that a USB device is inserted into a downstream USB port, and the USB connection device is connected to the host machine via an upstream USB port. In a preset pass-through mode, the device descriptor of the USB device is forwarded to the host machine. The device descriptor is used to establish a USB communication channel between the host machine and the USB device. If an access request is received from the host machine, response data is determined, and the response data is physically passed through to the host machine based on the USB communication channel. Therefore, this application embodiment supports key modes such as direct access of USB devices.

[0068] Corresponding to the above method, embodiments of this application also provide a remote access device for a USB device, such as... Figure 9 As shown, the device includes: Registration module 41 is used for the server to receive USB device information reported by the access terminal device and perform registration processing based on the USB device information; wherein, the access terminal device is physically connected to at least one USB device; the USB device information is generated based on the USB device. Push module 42 is used by the server to push the USB device information to at least one remote user terminal; Pairing module 43 is used by the server to establish a data transmission channel between the access device and the remote user in response to a pairing request from the remote user. Access module 44 is used by the remote user terminal to create a virtual USB device node corresponding to the USB device on the host machine where the remote user terminal is located, based on the data transmission channel, so that the host machine can access the remote USB device through the virtual USB device node.

[0069] The functions of each functional unit of the remote access device for USB devices provided in the above embodiments of this application can be implemented through the above method steps. Therefore, the specific working process and beneficial effects of each unit in the remote access device for USB devices provided in the embodiments of this application will not be repeated here.

[0070] This application also provides an electronic device, such as... Figure 10 As shown, it includes a processor 510, a communication interface 520, a memory 530, and a communication bus 540, wherein the processor 510, the communication interface 520, and the memory 530 communicate with each other through the communication bus 540.

[0071] Memory 530 is used to store computer programs; The processor 510 performs the above steps when executing the program stored in the memory 530.

[0072] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0073] The communication interface is used for communication between the aforementioned electronic devices and other devices.

[0074] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0075] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0076] The implementation methods and beneficial effects of the various components of the electronic device in the above embodiments for solving the problem can be found in [reference needed]. Figure 1 The steps in the illustrated embodiments are used to implement the electronic device. Therefore, the specific working process and beneficial effects of the electronic device provided in this application will not be repeated here.

[0077] In another embodiment provided in this application, a computer-readable storage medium is also provided, which stores instructions that, when executed on a computer, cause the computer to perform the remote access method for a USB device as described in any of the above embodiments.

[0078] In another embodiment provided in this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute the remote access method for a USB device described in any of the above embodiments.

[0079] Those skilled in the art will understand that the embodiments in this application can be provided as methods, systems, or computer program products. Therefore, the embodiments in this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the embodiments in this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0080] This application describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this application with reference to flowchart illustrations and / or block diagrams. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0081] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0082] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0083] Although preferred embodiments have been described in this application, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of this application.

[0084] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims in this application and their equivalents, then this application also intends to include these modifications and variations.

Claims

1. A method for remotely accessing a USB device, characterized in that, The method includes: The server receives USB device information reported by the access device and performs registration processing based on the USB device information; wherein, the access device is physically connected to at least one USB device; the USB device information is generated based on the USB device. The server pushes the USB device information to at least one remote user terminal; The server responds to the pairing request from the remote user and establishes a data transmission channel between the access device and the remote user. Based on the data transmission channel, the remote user creates a virtual USB device node corresponding to the USB device on its own host machine, so that the host machine can access the remote USB device through the virtual USB device node.

2. The method as described in claim 1, characterized in that, The server receives USB device information reported by the access device and performs registration processing based on the USB device information, including: If the access device has a network communication interface, the server receives the USB device information reported by the network communication interface and performs registration processing based on the USB device information.

3. The method as described in claim 1, characterized in that, If the access device does not have a network communication interface, the access device accesses the network through a network proxy host device connected to the network, and the network proxy host device performs the registration step with the server on its behalf. The server receives USB device information reported by the access device and performs registration processing based on the USB device information, including: The server receives the USB device information reported by the network proxy host device and performs registration processing based on the USB device information.

4. The method as described in claim 1, characterized in that, In response to a pairing request from the remote user, the server establishes a data transmission channel between the access device and the remote user, including: In response to a pairing request from the remote user, the server establishes a first logical pairing relationship between the access device and the remote user, and sends a first pairing instruction corresponding to the first logical pairing relationship to the access device. The pairing request includes the USB device to be paired; the first pairing instruction is used to establish a data transmission channel; the data transmission channel is from the access device to the remote user; or, it is from the access device to the remote user via the server.

5. The method as described in claim 1, characterized in that, The access device does not have a network communication interface, and the access device accesses the network through a network proxy host device connected to the network. In response to a pairing request from the remote user, the server establishes a data transmission channel between the access device and the remote user, including: In response to a pairing request from the remote user, the server establishes a second logical pairing relationship between the access device, the network proxy host device, and the remote user, and sends a second pairing instruction corresponding to the second logical pairing relationship to the network proxy host device, so that the network proxy host device forwards the second pairing instruction to the access device. The pairing request includes the USB device to be paired; the second pairing instruction is used to establish a data transmission channel; the data transmission channel is relayed from the access terminal device to the remote user terminal via the network proxy host device.

6. The method according to any one of claims 1-5, characterized in that, The remote user terminal includes either an analog terminal or a software terminal; The server pushes the USB device information to at least one remote user terminal, including: The server pushes the USB device information to at least one analog terminal, or a software terminal.

7. A method for connecting and accessing a USB device, characterized in that, The method is applied to a USB connectivity device, the USB connectivity device being provided with an upstream USB interface and a downstream USB interface; the method includes: If a USB device is detected inserted into the downstream USB interface, and the USB connection device is connected to the host machine through the upstream USB interface, then in a preset pass-through mode, the device descriptor of the USB device is forwarded to the host machine; wherein, the device descriptor is used to establish a USB communication channel between the host machine and the USB device; If an access request is received from the host machine, the response data is determined, and the response data is physically transmitted to the host machine based on the USB communication channel.

8. A remote access device for a USB device, characterized in that, The device includes: The registration module is used for the server to receive USB device information reported by the access device and perform registration processing based on the USB device information; wherein, the access device is physically connected to at least one USB device; the USB device information is generated based on the USB device. The push module is used by the server to push the USB device information to at least one remote user terminal; A pairing module is used by the server to establish a data transmission channel between the access device and the remote user in response to a pairing request from the remote user. An access module is used by the remote user to create a virtual USB device node corresponding to the USB device on the host machine where the remote user is located, based on the data transmission channel, so that the host machine can access the remote USB device through the virtual USB device node.

9. An electronic device, characterized in that, The electronic device includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the method of any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method described in any one of claims 1-7.

Images