WO2024093542A1

WO2024093542A1 - Usb drive-free communication method and apparatus, and electronic device and storage medium

Info

Publication number: WO2024093542A1
Application number: PCT/CN2023/118583
Authority: WO
Inventors: 赵飞
Original assignee: 深圳市广和通无线股份有限公司
Priority date: 2022-10-31
Filing date: 2023-09-13
Publication date: 2024-05-10
Also published as: CN115905095A

Abstract

A USB drive-free communication method and apparatus, and an electronic device and a storage medium. The method comprises: enumerating an inserted USB device to obtain enumeration information of the USB device (201); according to the enumeration information, determining a primary device number and a secondary device number, which is created by the USB device in a host device (202); creating a character device according to the primary device number and the secondary device number (203); binding the USB device with a usbfs driver by means of the character device (204); and communicating with the USB device by means of the usbfs driver (205). Therefore, a primary device number and a secondary device number, which are created by a USB device in a system, are determined by means of enumeration information, a corresponding character device is created, and an IOCTL command is then executed by means of the character device, so as to bind the USB device with a usbfs driver, which is built in a kernel. Thus, the USB device can directly use the universal usbfs driver in the kernel to perform data communication, without relying on a specific driver of a manufacturer.

Description

USB driver-free communication method, device, electronic device and storage medium

This application claims priority to the Chinese patent application filed with the China Patent Office on October 31, 2022, with application number 202211352609.6 and application name “USB driver-free communication method, device, electronic device and storage medium”, the entire contents of which are incorporated by reference in this application.

Technical Field

The present invention relates to the technical field of USB device data transmission, and in particular to a USB driver-free communication method, device, electronic equipment and storage medium.

Background technique

Wireless communication modules are widely used in PCs, tablets, industrial gateways and other products with the help of operators' cellular communication networks, providing a wireless bridge for the interconnection of all things for consumer, industrial and other electronic terminal products. At present, if wireless communication modules want to achieve LOG capture or upgrade functions in an embedded Linux host environment through a USB port, existing chip solution providers generally provide manufacturers' unique drivers that need to be installed. However, due to customer tailoring, high customization and cost reasons, embedded Linux systems cannot complete the integration of drivers from various manufacturers, resulting in limited module applications.

Summary of the invention

In order to solve the above-mentioned problems existing in the prior art, the embodiments of the present application provide a USB driver-free communication method, device, electronic device and storage medium, which can enable USB devices to directly use the universal usbfs driver in the kernel for data communication without relying on the manufacturer's specific driver.

In a first aspect, an embodiment of the present application provides a USB driver-free communication method, the method specifically comprising:

Enumerate the inserted USB devices and obtain the enumeration information of the USB devices;

According to the enumeration information, determine the major device number and minor device number of the USB device created in the host device;

Create a character device based on the major device number and minor device number;

Bind the USB device to the usbfs driver through a character device, wherein the usbfs driver is pre-configured in the kernel of the host device;

Communicate with USB devices through the usbfs driver.

In one embodiment of the present invention, enumerating the inserted USB device to obtain enumeration information of the USB device includes:

Read the vendor identification and product identification code of the USB device through the inserted interface;

According to the supplier identification and product identification code, a match is performed in the preset path directory to obtain the enumeration information of the USB device.

In one embodiment of the present invention, creating a character device according to a major device number and a minor device number includes:

Dynamically create character devices based on the major and minor device numbers through the mknod interface.

In one embodiment of the present invention, before binding the USB device to the usbfs driver through the character device, the method further includes:

Run IOCTL commands through character devices to determine whether the USB device has been loaded with a driver;

When the USB device has been loaded with a driver, the binding relationship between the USB device and the driver is released.

In one embodiment of the present invention, communicating with a USB device through a usbfs driver includes:

Create a read thread through the usbfs driver;

The read thread is bound to the endpoint of the input direction, so as to obtain the data in the USB device by reading the endpoint of the input direction in a blocking manner through the read thread.

In one embodiment of the present invention, communicating with a USB device through a usbfs driver also includes:

Create a write thread through the usbfs driver;

The write thread is bound to the endpoint in the output direction, so as to write data to the endpoint in the output direction through the write thread and write data to the USB device.

In one embodiment of the present invention, writing data to an endpoint in an output direction through a write thread includes:

Assemble data into URB BULK packages through the write thread;

Writes a URB BULK packet to an endpoint in the output direction.

In a second aspect, an embodiment of the present application provides a USB driver-free communication device, which specifically includes:

The enumeration module is used to enumerate the inserted USB devices and obtain the enumeration information of the USB devices;

The analysis module is used to determine the major device number and the minor device number created by the USB device in the host device according to the enumeration information;

The communication module is used to create a character device according to the major device number and the minor device number, and bind the USB device to the usbfs driver through the character device, wherein the usbfs driver is pre-configured in the kernel of the host device, and communicates with the USB device through the usbfs driver.

In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor, the processor is connected to a memory, the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device performs the method of the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a computer to execute the method of the first aspect.

In a fifth aspect, an embodiment of the present application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and is computer-operable to cause the computer to execute the method of the first aspect.

The implementation of the present application has the following beneficial effects:

In the implementation mode of the present application, the enumeration information of the USB device is used to determine the primary and secondary device numbers created by the USB device in the system, and then the corresponding character device is created according to the primary and secondary device numbers. Then, the IOCTL command is executed through the character device to bind the USB device to the usbfs driver that comes with the kernel. Then, the USB device can directly use the universal usbfs driver in the kernel for data communication without relying on the manufacturer's unique driver.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the implementation modes of the present application, the drawings required for use in the description of the implementation modes will be briefly introduced below. Obviously, the drawings described below are some implementation modes of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

FIG1 is a schematic diagram of the hardware structure of a USB driver-free communication device provided in an embodiment of the present application;

FIG2 is a flow chart of a USB driver-free communication method provided in an embodiment of the present application;

FIG3 is a block diagram of the functional modules of a USB driver-free communication device provided in an embodiment of the present application;

FIG. 4 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

Detailed ways

The following will combine the drawings in the embodiments of the present application to clearly and completely explain the technical solutions in the embodiments of the present application. It is obvious that the described implementation is a part of the implementation of the present application, not all the implementations. Based on the implementation in the present application, all other implementations obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

The terms "first", "second", "third" and "fourth" etc. in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

Reference to "embodiment" herein means that a particular feature, result, or characteristic described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

First, refer to FIG1 , which is a hardware structure diagram of a USB driver-free communication device provided in an embodiment of the present application. The USB driver-free communication device 100 includes at least one processor 101 , a communication line 102 , a memory 103 and at least one communication interface 104 .

In this embodiment, the processor 101 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

The communication link 102 may include a path to transmit information between the above components.

The communication interface 104 can be any transceiver-like device (such as an antenna, etc.) used to communicate with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc.

The memory 103 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

In this embodiment, the memory 103 can exist independently and be connected to the processor 101 via the communication line 102. The memory 103 can also be integrated with the processor 101. The memory 103 provided in the embodiment of the present application can generally be non-volatile. Among them, the memory 103 is used to store computer-executable instructions for executing the scheme of the present application, and the execution is controlled by the processor 101. The processor 101 is used to execute the computer-executable instructions stored in the memory 103, thereby realizing the method provided in the following embodiment of the present application.

In an optional implementation, the computer-executable instructions may also be referred to as application code, which is not specifically limited in this application.

In an optional implementation, the processor 101 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 1 .

In an optional embodiment, the USB driver-free communication device 100 may include multiple processors, such as the processor 101 and the processor 107 in FIG. 1 . Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, and/or A processing core that processes data (such as computer program instructions).

In an optional embodiment, if the USB driver-free communication device 100 is a server, for example, it can be an independent server, or it can be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms. Then the USB driver-free communication device 100 can also include an output device 105 and an input device 106. The output device 105 communicates with the processor 101 and can display information in a variety of ways. For example, the output device 105 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 106 communicates with the processor 101 and can receive user input in a variety of ways. For example, the input device 106 can be a mouse, a keyboard, a touch screen device, or a sensor device.

The USB driver-free communication device 100 can be a general device or a dedicated device. The embodiment of the present application does not limit the type of the USB driver-free communication device 100.

The following is an explanation of the USB driver-free communication method disclosed in this application:

Refer to FIG. 2 , which is a flow chart of a USB driver-free communication method provided in an embodiment of the present application, which may specifically include the following steps:

201: Enumerate the inserted USB device to obtain enumeration information of the USB device.

The so-called enumeration is to let the host controller recognize the USB device, prepare resources for it, and establish a data transfer mechanism between the host and the device. The work in this stage is stipulated by the USB communication protocol, so it belongs to the ISO standard process. The device enumeration stage also corresponds to the five states of the USB device. That is: after the USB device is inserted into the interface, it is in the Attached state; the USB host controller will power the USB device, and it is in the Powered state at this time; in step 2 of the device enumeration stage, after the reset operation, the device is in the Default state; in step 3 of the device enumeration stage, after the address setting operation, the device is in the Addressed state; after the device enumeration is completed, the device is in the Configured state.

Specifically, the device enumeration phase can be divided into the following 8 steps: 1. Get device descriptor; 2. Reset; 3. Set address; 4. Get device descriptor again; 5. Get configuration descriptor; 6. Get interface, endpoint descriptor; 7. Get string descriptor; 8. Select and set configuration. Among them, steps 1 and 4 are to get device descriptors. However, in step 1, only the fixed-length field of the device descriptor is obtained, while step 4 is to get all the fields of the device descriptor. Through the above 8 steps, in the device enumeration phase, the host controller obtains all the detailed information of the USB device (5 major descriptors), and then allocates resources to it (sets the address).

Based on this, in this embodiment, the inserted USB device can be enumerated through the inserted interface, the device descriptor of the USB device can be read, and then the vendor identification number (VID) and product identification number (PID) of the USB device can be determined according to the field division in the device descriptor. Then, according to the VID and PID of the USB device, a match is performed in the preset path directory, for example, the sys/bus/usb directory, to obtain the enumeration information of the USB device.

202: Determine the major device number and minor device number of the USB device created in the host device according to the enumeration information.

The device management of Linux is closely integrated with the file system. Various devices are stored in the /dev directory in the form of files, which are called device files. Applications can open, close, read and write these device files to complete operations on the devices, just like operating ordinary data files. In order to manage these devices, the system numbers the devices, and each device number is divided into a major device number and a minor device number. Among them, the major device number is used to distinguish different types of devices, and the minor device number is used to distinguish multiple devices of the same type. In this embodiment, the device file can be found by enumerating information, obtaining bNumInterfaces information, obtaining the number of ports enumerated by the current module, and then determining the main device created by the USB device in the host according to uevent. The backup and secondary device numbers.

203: Create a character device based on the major device number and minor device number.

A character device is a custom device structure in Linux that can provide a continuous data stream and an input/output (I/O) device that can be read sequentially by an application. It usually supports reading and writing data by byte/character, but does not support random access. Specifically, in this implementation, a character device can be dynamically created through the mknod interface based on the major device number and the minor device number.

204: Bind the USB device to the usbfs driver through the character device.

In this embodiment, the usbfs driver is pre-configured in the kernel of the host device, that is, it is a universal driver that comes with the kernel. Specifically, before binding, it is also necessary to determine the driver loading status of the USB device, that is, whether some drivers are automatically loaded. In this embodiment, the created character device can open the USB device through the system call open, and then run the IOCTL USBDEVFS_GETDRIVER command to query whether the USB device has loaded other drivers.

At this point, if the query result shows that the USB device automatically loads the usbfs driver, you can proceed directly to the next step. If other drivers are loaded, release the binding relationship between the USB device and other drivers, and then use the IOCTL USBDEVFS_CLAIMINTERFACE command to bind the USB device to the usbfs driver.

205: Communicate with USB devices through the usbfs driver.

In this embodiment, first, the data port of the USB device used for communication is determined by the PID, and the endpoint (Endpoint, EP) of the input direction and the EP of the output direction of the USB device are set based on the data port.

Then, in this embodiment, the usbfs driver can create a read thread through the data port, and construct a usbdevfs_bulktransfer BULK read request through the read thread to request to bind the EP in the input direction. Then, after the binding is completed, the EP in the input direction is read in a blocking manner through the USBDEVFS_BULK IOCTL to obtain the data in the USB device to the user buffer, and complete the reading of the USB device.

Finally, in this embodiment, the usbfs driver can create a write thread through the data port, and construct a usbdevfs_urb URB write request through the write thread to request to bind the EP in the output direction. Then, after the binding is completed, the data in the user buffer is assembled into a URB BULK packet, and the URB BULK packet is written to the EP in the output direction through USBDEVFS_SUBMITURB IOCTL, and the data in the user buffer is sent to the controller of the USB device to complete the writing of the USB device.

In summary, in the USB driver-free communication method provided by the present invention, the primary and secondary device numbers created by the USB device in the system are determined through the enumeration information of the USB device, and then the corresponding character device is created according to the primary and secondary device numbers. Then, the IOCTL command is executed through the character device to bind the USB device to the usbfs driver that comes with the kernel. Then, the USB device can directly use the universal usbfs driver in the kernel for data communication without relying on the manufacturer's unique driver.

Refer to FIG. 3 , which is a block diagram of functional modules of a USB driver-free communication device provided in an embodiment of the present application. Specifically, as shown in FIG. 3 , the USB driver-free communication device 300 includes:

The enumeration module 301 is used to enumerate the inserted USB devices and obtain the enumeration information of the USB devices;

The analysis module 302 is used to determine the major device number and minor device number created by the USB device in the host device according to the enumeration information;

The communication module 303 is used to create a character device according to the major device number and the minor device number, bind the USB device to the usbfs driver through the character device, wherein the usbfs driver is pre-configured in the kernel of the host device, and communicate with the USB device through the usbfs driver.

In an embodiment of the present invention, in enumerating the inserted USB device to obtain the enumeration information of the USB device, the enumeration module 301 is specifically used to:

In the embodiment of the present invention, in terms of creating a character device according to the major device number and the minor device number, the communication module 303 is specifically used to:

In an embodiment of the present invention, before binding the USB device to the usbfs driver through the character device, the communication module 303 is further used to:

In an embodiment of the present invention, in terms of communicating with a USB device through a usbfs driver, the communication module 303 is specifically used to:

Create a read thread through the usbfs driver;

In an embodiment of the present invention, in terms of communicating with a USB device through a usbfs driver, the communication module 303 is further used to:

Create a write thread through the usbfs driver;

In the embodiment of the present invention, in terms of writing data to an endpoint in an output direction through a write thread, the communication module 303 is specifically used to:

Assemble data into URB BULK packages through the write thread;

Writes a URB BULK packet to an endpoint in the output direction.

Referring to FIG. 4 , FIG. 4 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. As shown in FIG. 4 , the electronic device 400 includes a transceiver 401, a processor 402, and a memory 403. They are connected via a bus 404. The memory 403 is used to store computer programs and data, and can transmit the data stored in the memory 403 to the processor 402.

The processor 402 is used to read the computer program in the memory 403 and perform the following operations:

Communicate with USB devices through the usbfs driver.

In an embodiment of the present invention, in enumerating the inserted USB device and obtaining the enumeration information of the USB device, the processor 402 is specifically configured to perform the following operations:

In the embodiment of the present invention, in terms of creating a character device according to the major device number and the minor device number, the processor 402 is specifically configured to perform the following operations:

In an embodiment of the present invention, before binding the USB device to the usbfs driver through the character device, the processor 402 is further configured to perform the following operations:

In an embodiment of the present invention, in terms of communicating with a USB device through a usbfs driver, the processor 402 is specifically configured to perform the following operations:

Create a read thread through the usbfs driver;

In an embodiment of the present invention, in terms of communicating with a USB device through a usbfs driver, the processor 402 is further configured to perform the following operations:

Create a write thread through the usbfs driver;

In the embodiment of the present invention, in terms of writing data to an endpoint in an output direction through a write thread, the processor 402 is specifically configured to perform the following operations:

Assemble data into URB BULK packages through the write thread;

Writes a URB BULK packet to an endpoint in the output direction.

It should be understood that the USB driver-free communication device in the present application may include a smart phone (such as an Android phone, an iOS phone, a Windows Phone phone, etc.), a tablet computer, a PDA, a laptop computer, a mobile Internet device MID (Mobile Internet Devices, referred to as: MID), a robot or a wearable device, etc. The above-mentioned USB driver-free communication device is only an example, not an exhaustive list, including but not limited to the above-mentioned USB driver-free communication device. In practical applications, the above-mentioned USB driver-free communication device may also include: a smart vehicle terminal, a computer device, etc.

Through the description of the above implementation modes, those skilled in the art can clearly understand that the present invention can be implemented by combining software with a hardware platform. Based on such an understanding, all or part of the contribution of the technical solution of the present invention to the background technology can be embodied in the form of a software product, which can be stored in a storage medium such as ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various implementation modes of the present invention or some parts of the implementation modes.

Therefore, the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement some or all of the steps of any USB driver-free communication method described in the above method implementation. For example, the storage medium may include a hard disk, a floppy disk, an optical disk, a tape, a disk, a USB flash drive, a flash memory, etc.

The present application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute part or all of the steps of any one of the USB driver-free communication methods described in the above method implementation.

It should be noted that, for the sake of simplicity, the aforementioned method implementations are all described as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the order of the actions described, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the implementations described in the specification are all optional implementations, and the actions and modules involved are not necessarily the implementations of the present application. Necessary.

In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed device can be implemented in other ways. For example, the device implementation described above is only schematic, such as the division of the units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present implementation scheme.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of a software program module.

If the integrated unit is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a memory, including several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

A person of ordinary skill in the art may understand that all or part of the steps in the various methods of the above-mentioned embodiments may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable memory, and the memory may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

The above is a detailed introduction to the implementation methods of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above implementation methods is only used to help understand the method and core idea of the present application. At the same time, for general technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

A USB driver-free communication method, characterized in that the method comprises:

Enumerate the inserted USB devices to obtain enumeration information of the USB devices;

Determine the major device number and minor device number of the USB device created in the host device according to the enumeration information;

Creating a character device according to the major device number and the minor device number;

Binding the USB device to a usbfs driver through the character device, wherein the usbfs driver is pre-configured in the kernel of the host device;

Communicate with the USB device via the usbfs driver.
The method according to claim 1, characterized in that the step of enumerating the inserted USB device to obtain the enumeration information of the USB device comprises:

Reading the vendor identification and product identification code of the USB device through the inserted interface;

According to the supplier identification and the product identification code, a match is performed in a preset path directory to obtain enumeration information of the USB device.
The method according to claim 1, characterized in that the step of creating a character device according to the major device number and the minor device number comprises:

The character device is dynamically created according to the major device number and the minor device number through the mknod interface.
The method according to claim 1, characterized in that before binding the USB device to the usbfs driver through the character device, the method further comprises:

Run an IOCTL command through the character device to determine whether the USB device has been loaded with a driver;

When the driver has been loaded to the USB device, the binding relationship between the USB device and the driver is released.
The method according to any one of claims 1 to 4, characterized in that communicating with the USB device through the usbfs driver comprises:

Create a read thread through the usbfs driver;

The read thread is bound to an endpoint in an input direction, so as to obtain data in the USB device by reading the endpoint in the input direction in a blocking manner through the read thread.
The method according to any one of claims 1 to 4, characterized in that the communicating with the USB device through the usbfs driver further comprises:

Create a write thread through the usbfs driver;

The write thread is bound to an endpoint in an output direction, so that data is written to the endpoint in the output direction through the write thread, thereby writing data to the USB device.
The method according to claim 6, wherein writing data to the endpoint in the output direction through the write thread comprises:

Assemble the data into URB BULK packets through the write thread;

Write the URB BULK packet to the endpoint in the output direction.
A USB driver-free communication device, characterized in that the device comprises:

An enumeration module is used to enumerate the inserted USB devices and obtain the enumeration information of the USB devices;

An analysis module, used to determine the major device number and the minor device number created by the USB device in the host device according to the enumeration information;

A communication module is used to create a character device according to the major device number and the minor device number, and bind the USB device to a usbfs driver through the character device, wherein the usbfs driver is pre-configured in the kernel of the host device, and communicate with the USB device through the usbfs driver.
An electronic device, characterized in that it includes a processor, a memory, a communication interface and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the processor, and the one or more programs include instructions for executing the steps described in any one of the methods of claims 1-7.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the method according to any one of claims 1 to 7.