A USB composite device communication method, system, and storage medium

Abstract

The present invention provides a USB composite device communication method, system and medium. The method is applied to a first device and a second device. A takeover module is provided in the first device, and a virtual bus module and a PNP manager are provided in the second device. The method includes: the takeover module obtains device information of a USB composite device accessing the first device and sends the device information to the virtual bus module; the virtual bus module creates a virtual physical device object by using the device information and sends the virtual physical device object to the PNP manager; the PNP manager configures the USB composite device to the second device by using the virtual physical device object, so that the software of the second device can identify the USB composite device and communicate with the USB composite device through the takeover module and the virtual bus module; the USB composite device accessing the first device can be completely configured to the second device, so that the software in the second device can identify the USB composite device, and thus the user's usage requirements can be met.

Description

Technical Field

[0001] The present invention relates to the field of cloud computers, and particularly to a communication method, system and storage medium for a USB composite device. Background Art

[0002] With the development of network technology, cloud computers have been widely used. With the help of cloud computer technology, users can establish a network connection between a thin terminal (such as a low - configuration computer, mobile phone, browser, set - top box, etc.) and a high - performance host at a remote end, so as to use the high - performance host on the thin terminal. Since the USB devices used by users are all connected to the thin terminal, how to make the high - performance host at the remote end recognize these USB devices is an important technical problem to be solved in the field of cloud computers.

[0003] In related technologies, the USBIP technology (network - based USB device passthrough technology) is usually used to achieve transparent transmission of USB device data on multiple terminals. However, this technology can only meet the basic operation of keyboard and mouse functions, that is, it can only make the remote host recognize single - interface USB devices. For a USB composite device with multiple interfaces (such as a mouse with side buttons and other functions), since the USBIP technology cannot transmit the physical information of the USB composite device, the remote host cannot correctly recognize the USB composite device, and thus cannot meet the user's need to use the USB composite device on the remote host. Summary of the Invention

[0004] The purpose of the present invention is to provide a communication method, system and storage medium for a USB composite device, which can completely configure the USB composite device connected to the first device to the second device, so that the software in the second device can recognize the USB composite device and communicate with it through the network, and can meet the user's need to use the USB composite device on the remote host.

[0005] To solve the above - mentioned technical problems, the present invention provides a communication method for a USB composite device, which is applied to a first device and a second device. A takeover module is set in the first device, and a virtual bus module and a PNP manager are set in the second device. The method includes:

[0006] The takeover module obtains the device information of the USB composite device connected to the first device, and sends the device information to the virtual bus module;

[0007] The virtual bus module creates a virtual physical device object by using the device information, and sends the virtual physical device object to the PNP manager;

[0008] The PNP manager configures the USB composite device to the second device by using the virtual physical device object, so that the software of the second device can recognize the USB composite device and communicate with the USB composite device through the takeover module and the virtual bus module.

[0009] Preferably, the takeover module obtains the device information of the USB composite device accessing the first device and sends the device information to the virtual bus module, including:

[0010] The takeover module obtains the USB device accessing the first device and determines whether a preset field is included in the service name of the USB device;

[0011] If so, it determines that the USB device is the USB composite device and installs a takeover driver for the USB composite device, so that the takeover driver can obtain the device information and send the device information to the virtual bus module.

[0012] Preferably, before installing the takeover driver for the USB composite device, it further includes:

[0013] The takeover module obtains a preset device list and extracts the device hardware ID of the USB composite device;

[0014] Determine whether the device hardware ID exists in the preset device list;

[0015] If so, ignore the USB composite device;

[0016] If not, install a takeover driver for the USB composite device.

[0017] Preferably, the PNP manager configures the USB composite device to the second device by using the virtual physical device object, including:

[0018] The PNP manager allocates system resources for the USB composite device by using the virtual physical device object and starts the USB composite device, so that when the operating system of the second device detects the startup of the USB composite device, it initializes the USB composite device and mounts a driver program for the USB composite device.

[0019] Preferably, the device information includes a device hardware ID and a device compatibility ID, and the device compatibility ID includes a USB composite device identifier;

[0020] Correspondingly, mounting the driver program for the USB composite device includes:

[0021] The operating system mounts the driver according to the device hardware ID, the device compatibility ID, and the USB composite device identifier.

[0022] The present invention also provides a USB composite device communication system, including: a first device and a second device. A takeover module is provided in the first device, and a virtual bus module and a PNP manager are provided in the second device, where

[0023] The takeover module is configured to obtain device information of a USB composite device accessing the first device, and send the device information to the virtual bus module;

[0024] The virtual bus module is configured to create a virtual physical device object by using the device information, and send the virtual physical device object to the PNP manager;

[0025] The PNP manager is configured to configure the USB composite device to the second device by using the virtual physical device object, so that software of the second device can identify the USB composite device, and communicate with the USB composite device through the takeover module and the virtual bus module.

[0026] Preferably, the takeover module is further configured to obtain a USB device accessing the first device, and determine whether a preset field is included in a service name of the USB device; if so, determine that the USB device is the USB composite device, and install a takeover driver for the USB composite device, so that the takeover driver obtains the device information and sends the device information to the virtual bus module.

[0027] Preferably, the takeover module is further configured to obtain a preset device list, and extract a device hardware ID of the USB composite device; determine whether the device hardware ID exists in the preset device list; if so, ignore the USB composite device; if not, install a takeover driver for the USB composite device.

[0028] Preferably, the PNP manager is further configured to allocate system resources for the USB composite device by using the virtual physical device object, and start the USB composite device, so that when the operating system of the second device detects the startup of the USB composite device, the USB composite device is initialized, and a driver program is mounted for the USB composite device.

[0029] The present invention also provides a storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are loaded and executed by a processor, the USB composite device communication method as described above is implemented.

[0030] The present invention provides a communication method for a USB composite device, which is applied to a first device and a second device. A takeover module is provided in the first device, and a virtual bus module and a PNP manager are provided in the second device. The method includes: the takeover module obtains device information of a USB composite device accessing the first device, and sends the device information to the virtual bus module; the virtual bus module creates a virtual physical device object by using the device information, and sends the virtual physical device object to the PNP manager; the PNP manager configures the USB composite device to the second device by using the virtual physical device object, so that software of the second device can identify the USB composite device, and communicate with the USB composite device through the takeover module and the virtual bus module.

[0031] It can be seen that in the present invention, the takeover module located in the first device first obtains the complete device information of the USB composite device accessing the first device, and sends this information to the virtual bus module located in the second device, thereby transmitting the physical information of the USB composite device to the second device; after receiving the device information, the virtual bus module creates a virtual physical device object by using this information, and sends the virtual physical device object to the PNP manager for device configuration. Since the virtual physical device object contains the complete device information of the USB composite device, the PNP manager can correctly identify the USB composite device and perform corresponding configuration, so that the USB composite device can be correctly configured to the second device, so that the software in the second device can identify the USB composite device, and communicate with the USB composite device through the takeover module and the virtual bus module, which can meet the user's need to use the USB composite device on the remote host, and further improve the user experience of using the cloud computer. The present invention also provides a USB composite device communication system and a storage medium, which have the above beneficial effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.

[0033] Figure 1 It is a flowchart of a communication method for a USB composite device provided by an embodiment of the present invention;

[0034] Figure 2 It is a schematic diagram of configuring a thin client USB composite device to the host side provided by an embodiment of the present invention;

[0035] Figure 3It is a block diagram of a USB composite device communication system provided by an embodiment of the present invention. Specific embodiments

[0036] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0037] In related technologies, the USBIP technology (network-based USB device passthrough technology) is usually used to achieve transparent transmission of USB device data on multiple terminals. However, this technology can only meet basic mouse and keyboard function operations, that is, it can only enable a remote host to recognize a single-interface USB device. For a USB composite device with multiple interfaces (such as a mouse with side buttons and other functions), since the USBIP technology cannot transmit the physical information of the USB composite device, the remote host cannot correctly recognize the USB composite device, and thus cannot meet the user's need to use the USB composite device on the remote host. In view of this, the present invention provides a USB composite device communication method, which can completely configure the USB composite device connected to the first device to the second device, so that the software in the second device can recognize the USB composite device and communicate with it through the network, and can meet the user's need to use the USB composite device on the remote host. Please refer to Figure 1 , Figure 1 It is a flowchart of a USB composite device communication method provided by an embodiment of the present invention. This method is applied to the first device and the second device. A takeover module is set in the first device, and a virtual bus module and a PNP manager are set in the second device. It should be noted that the embodiments of the present invention do not limit the specific type of the first device, as long as the first device is a computer device and has a USB interface, such as a personal computer (PC), a mobile phone, a tablet computer, etc.; the embodiments of the present invention also do not limit the specific type of the second device, such as a personal computer, a server, etc. This method may include:

[0038] S101. The takeover module obtains the device information of the USB composite device connected to the first device and sends the device information to the virtual bus module.

[0039] In an embodiment of the present invention, both the takeover module and the virtual bus module are used to configure a USB composite device connected to a first device to a second device and provide a data path for data communication between the USB composite device and the second device. For the takeover module, it first searches for the device information of the USB composite device connected to the first device in the first device. Specifically, when the USB composite device is connected to the first device, it is first configured to the device manager of the first device. After the configuration is completed, the USB composite device can be queried by the takeover module. Since the service name corresponding to the USB composite device usually contains a preset field (such as usbccgp), the takeover module can first search for the USB device connected to the first device and determine whether the service name corresponding to the USB device contains the preset field, so as to determine whether the USB device is a USB composite device. Further, in order to take over the USB composite device from the operating system of the first device to the second device, the takeover module installs a takeover driver for the USB composite device to replace the original USB common parent driver (usbccgp.sys) of the USB composite device.

[0040] In a possible case, the takeover module obtains the device information of the USB composite device connected to the first device and sends the device information to the virtual bus module, which may include:

[0041] Step 11: The takeover module obtains the USB device connected to the first device and determines whether the service name of the USB device contains a preset field; if so, go to Step 12; if not, ignore the USB device;

[0042] Step 12: Determine that the USB device is a USB composite device, and install a takeover driver for the USB composite device so that the takeover driver obtains the device information and sends the device information to the virtual bus module.

[0043] It should be noted that the embodiment of the present invention does not limit the device information that needs to be sent to the virtual bus module. For example, device descriptors, configuration descriptors, interface descriptors, etc. can be sent, and reference can be made to the relevant technologies of USB devices.

[0044] Further, considering that the first device may encounter a failure situation, at this time, maintenance personnel need to perform maintenance locally on the first device, and thus may use a USB composite device on the first device. To prevent all USB composite devices from being taken over to the second device, resulting in the inability to use the USB composite device on the first device, the takeover module can also preset a device list and record the information of the USB composite devices that do not need to be taken over to the second device in this list. After obtaining the device information of the USB composite device each time, the takeover module will compare the device information with the information in the list, and only take over this USB composite device to the second device when they are different. The embodiments of the present invention do not limit the device information that needs to be recorded in the preset device list. For example, the device hardware ID corresponding to the USB composite device can be recorded. The embodiments of the present invention do not limit the specific form of the device hardware ID, and the relevant technologies of USB devices can be referred to.

[0045] In a possible case, before installing the takeover driver for the USB composite device, it may further include:

[0046] Step 21: The takeover module obtains the preset device list and extracts the device hardware ID of the USB composite device;

[0047] Step 22: Determine whether the device hardware ID exists in the preset device list; if yes, go to Step 23; if not, go to Step 24;

[0048] Step 23: Ignore the USB composite device;

[0049] Step 24: Install the takeover driver for the USB composite device.

[0050] S102. The virtual bus module creates a virtual physical device object using the device information and sends the virtual physical device object to the PNP manager.

[0051] In an embodiment of the present invention, a virtual bus module is used to virtualize a USB composite device in a second device. Specifically, the virtual bus module creates a virtual physical device object (PDO, Physical Device Object) using device information and sends this virtual physical device object to a PNP manager, where the PNP manager (Plug-and-Play) is used to automatically configure the boards and other devices in the underlying computer. The embodiment of the present invention does not limit the creation method of the virtual physical device object, and relevant PDO technologies can be referred to. Specifically, since the USB composite device is a special USB device, when the virtual bus module creates a virtual physical device object, in addition to filling in the device hardware ID and device compatible ID, and filling in the device class information in the device compatible ID, it is also necessary to fill in the USB composite device identifier (USB\COMPOSITE) in the device compatible ID. In other words, the device information sent by the takeover module to the virtual bus module should include the device hardware ID and device compatible ID, and the device compatible ID includes the USB composite device identifier.

[0052] S103. The PNP manager configures the USB composite device to the second device using the virtual physical device object, so that the software of the second device can recognize the USB composite device and communicate with the USB composite device through the takeover module and the virtual bus module.

[0053] Specifically, the PNP manager will allocate system resources for the USB device and start the USB composite device through the communication link composed of the virtual bus module and the takeover module, so that when the operating system in the second device detects the startup of the USB composite device, it initializes the USB composite device and mounts the corresponding driver. It can be understood that the operating system in the second device mounts the driver according to the device hardware ID, device compatible ID and USB composite device identifier mentioned above.

[0054] In a possible case, the PNP manager configures the USB composite device to the second device using the virtual physical device object, including:

[0055] Step 31: The PNP manager allocates system resources for the USB composite device using the virtual physical device object and starts the USB composite device, so that when the operating system of the second device detects the startup of the USB composite device, it initializes the USB composite device and mounts a driver for the USB composite device.

[0056] In a possible case, the device information includes the device hardware ID and device compatible ID, and the device compatible ID includes the USB composite device identifier;

[0057] Correspondingly, to mount a driver for a USB composite device, the following steps are included:

[0058] Step 41: The operating system mounts the driver according to the device hardware ID, device compatibility ID, and USB composite device identifier.

[0059] It should be noted that the embodiments of the present invention do not limit the specific processes of the PNP manager and the operating system for resource allocation and driver mounting of the USB composite device, and relevant technologies of the PNP manager and the operating system can be referred to.

[0060] Based on the above embodiments, in the present invention, the takeover module located in the first device first obtains the complete device information of the USB composite device connected to the first device, and sends this information to the virtual bus module located in the second device, thereby transmitting the physical information of the USB composite device to the second device; after receiving the device information, the virtual bus module creates a virtual physical device object using this information and sends the virtual physical device object to the PNP manager for device configuration. Since the virtual physical device object contains the complete device information of the USB composite device, the PNP manager can correctly identify the USB composite device and perform corresponding configuration, enabling the USB composite device to be correctly configured to the second device, so that the software in the second device can identify the USB composite device and communicate with the USB composite device through the takeover module and the virtual bus module, which can meet the user's need to use the USB composite device on the remote host, thereby improving the user experience of using the cloud computer.

[0061] The following introduces the above USB composite device communication method based on a specific example. Please refer to Figure 2 , Figure 2 is a schematic diagram of configuring a thin client USB composite device to the host side provided by an embodiment of the present invention. The process may include: The takeover module of the thin client (i.e., the first device) enumerates the USB devices on the thin client system through the SetupDiEnumDeviceInfo interface, differentiates whether it is a composite device by whether the device service name is usbccgp, differentiates whether it is a takeoverable device by matching the device hardware ID with the whitelist, and then the takeover module installs a takeover driver for each device. The driver structure of the USB composite device before takeover is as shown in the "Before device takeover" part on the thin client side. Under the parent driver of USB Composite Device (USB composite device), there are multiple sub-drivers, such as a mouse (HID-compliant mouse) and a keyboard (HID-KeyboardDevice); the driver structure of the USB composite device after takeover is as shown in the "After device takeover" part on the thin client side, and the driver of the USB composite device is replaced by the USB takeover driver.

[0062] The takeover driver retrieves information such as the device descriptor, configuration descriptor, and interface descriptor of the USB device and sends this information to the host side (i.e., the second device). The host virtual bus driver creates a virtual PDO. When initializing the virtual PDO information, the virtual bus driver needs to populate the device hardware ID and device compatibility ID. For a composite device, the device compatibility ID needs to populate not only the device class information but also include USB\COMPOSITE. After the virtual bus driver reports the device to the system PNP manager, the PNP manager will query the device information, allocate resources, and start the device. The driver structure of the virtual PDO in the virtual bus driver is as shown on the host side, and it can be seen that this structure is the same as the original driver structure of the USB composite device on the thin client.

[0063] After the device is started, the system will perform the USB device initialization process, such as retrieving device descriptor information and selecting a configuration. After the device configuration is completed, the host will mount a driver for the device based on the device interface information. At this time, the device can be seen in the Device Manager, which is exactly the same as the device recognized when the device is inserted into the local computer. The software of the USB device manufacturer can also easily identify its own USB device and install its own control software, and the functions are normal.

[0064] Next, a USB composite device communication system and storage medium provided by an embodiment of the present invention will be introduced. The USB composite device communication system and storage medium described below can be correspondingly referred to the USB composite device communication method described above. Please refer to Figure 3 , Figure 3 is a structural block diagram of a USB composite device communication system provided by an embodiment of the present invention. The system may include: a first device 310 and a second device 320. A takeover module 311 is provided in the first device 310, and a virtual bus module 321 and a PNP manager 322 are provided in the second device 320. Among them,

[0065] The takeover module 311 is configured to obtain device information of the USB composite device accessing the first device 310 and send the device information to the virtual bus module 321;

[0066] The virtual bus module 321 is configured to create a virtual physical device object using the device information and send the virtual physical device object to the PNP manager 322;

[0067] The PNP manager 322 is configured to configure the USB composite device to the second device 320 using the virtual physical device object, so that the software of the second device 320 can identify the USB composite device and communicate with the USB composite device through the takeover module 311 and the virtual bus module 321.

[0068] Preferably, the takeover module 311 is further configured to obtain the USB device connected to the first device 310, and determine whether a preset field is included in the service name of the USB device; if so, determine that the USB device is a USB composite device, and install a takeover driver for the USB composite device, so that the takeover driver obtains device information and sends the device information to the virtual bus module 321.

[0069] Preferably, the takeover module 311 is further configured to obtain a preset device list and extract the device hardware ID of the USB composite device; determine whether the device hardware ID exists in the preset device list; if so, ignore the USB composite device; if not, install a takeover driver for the USB composite device.

[0070] Preferably, the PNP manager 322 is further configured to allocate system resources for the USB composite device by using a virtual physical device object and start the USB composite device, so that when the operating system of the second device 320 detects the startup of the USB composite device, it initializes the USB composite device and mounts a driver program for the USB composite device.

[0071] Preferably, the device information includes a device hardware ID and a device compatibility ID, and the device compatibility ID includes a USB composite device identifier;

[0072] Correspondingly, the operating system in the second device 320 mounts a driver program according to the device hardware ID, the device compatibility ID, and the USB composite device identifier.

[0073] An embodiment of the present invention further provides a storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the USB composite device communication method in any of the above embodiments are implemented.

[0074] Since the embodiments of the storage medium part correspond to the embodiments of the USB composite device communication method part, for the embodiments of the storage medium part, please refer to the description of the embodiments of the USB composite device communication method part, which will not be elaborated here for the time being.

[0075] The various embodiments in the specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts among the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method part.

[0076] Those skilled in the art may further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the present invention.

[0077] The steps of the methods or algorithms described in combination with the embodiments disclosed herein can be directly implemented by hardware, software modules executed by a processor, or a combination of the two. The software modules can be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium well-known in the technical field.

[0078] The above has introduced in detail a USB composite device communication method, system, and storage medium provided by the present invention. Specific examples are used herein to elaborate on the principles and implementation manners of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention. It should be noted that for those of ordinary skill in the art in this technical field, without departing from the principles of the present invention, several improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the protection scope of the claims of the present invention.

Claims

1. A USB composite device communication method, characterized in that, Applied to a first device and a second device, where a takeover module is provided in the first device, and a virtual bus module and a PNP manager are provided in the second device, the method includes: The takeover module obtains complete device information of a USB composite device connected to the first device, and sends the device information to the virtual bus module; the device information includes a device hardware ID and a device compatibility ID, and the device compatibility ID includes a USB composite device identifier; The virtual bus module creates a virtual physical device object using the device information, and sends the virtual physical device object to the PNP manager; The PNP manager configures the USB composite device to the second device using the virtual physical device object, so that the software of the second device can identify the USB composite device, and communicate with the USB composite device through the takeover module and the virtual bus module; The takeover module obtains complete device information of a USB composite device connected to the first device, and sends the device information to the virtual bus module, including: The takeover module installs a takeover driver for the USB composite device, and uses the takeover driver to replace the parent driver of the USB composite device, so that the takeover driver can obtain the device information and send the device information to the virtual bus module; there are multiple sub-drivers under the parent driver; The PNP manager configures the USB composite device to the second device using the virtual physical device object, including: The PNP manager allocates system resources for the USB composite device using the virtual physical device object, and starts the USB composite device, so that when the operating system of the second device detects the start of the USB composite device, it initializes the USB composite device, and mounts the parent driver according to the device hardware ID and the device compatibility ID.

2. The USB composite device communication method according to claim 1, wherein Before installing the takeover driver for the USB composite device, it further includes: The takeover module obtains a USB device connected to the first device, and determines whether a preset field is included in the service name of the USB device; If so, it determines that the USB device is the USB composite device, and enters the step of installing the takeover driver for the USB composite device.

3. The USB composite device communication method according to claim 2, wherein Before installing the takeover driver for the USB composite device, it further includes: The takeover module obtains a preset device list, and extracts the device hardware ID of the USB composite device; Determines whether the device hardware ID exists in the preset device list; If so, ignores the USB composite device; If not, installs the takeover driver for the USB composite device.

4. A USB composite device communication system, characterized in that, Includes: A first device and a second device, where a takeover module is provided in the first device, and a virtual bus module and a PNP manager are provided in the second device, where, The takeover module is used to obtain the complete device information of the USB composite device accessing the first device, and send the device information to the virtual bus module; the device information includes a device hardware ID and a device compatibility ID, and the device compatibility ID includes a USB composite device identifier; The virtual bus module is used to create a virtual physical device object by using the device information, and send the virtual physical device object to the PNP manager; The PNP manager is used to configure the USB composite device to the second device by using the virtual physical device object, so that the software of the second device can identify the USB composite device, and communicate with the USB composite device through the takeover module and the virtual bus module; The takeover module is further used to install a takeover driver for the USB composite device, and use the takeover driver to replace the parent driver of the USB composite device, so that the takeover driver can obtain the device information and send the device information to the virtual bus module; the parent driver includes multiple sub-drivers; The PNP manager is further used to allocate system resources for the USB composite device by using the virtual physical device object, and start the USB composite device, so that when the operating system of the second device detects the start of the USB composite device, it initializes the USB composite device, and mounts the parent driver according to the device hardware ID and the device compatibility ID.

5. The USB composite device communication system according to claim 4, characterized in that, The takeover module is further used to obtain the USB device accessing the first device, and determine whether a preset field is included in the service name of the USB device; if so, enter the step of installing a takeover driver for the USB composite device.

6. The USB composite device communication system according to claim 5, wherein The takeover module is further used to obtain a preset device list, and extract the device hardware ID of the USB composite device; determine whether the device hardware ID exists in the preset device list; if so, ignore the USB composite device; If not, install a takeover driver for the USB composite device.

7. A storage medium, characterized in that, The computer-executable instructions are stored in the storage medium, and when the computer-executable instructions are loaded and executed by a processor, the USB composite device communication method according to any one of claims 1 to 3 is implemented.

Images