CN111104170A - Driving method and device for wireless internet access and computer readable medium - Google Patents

Abstract

The embodiment of the invention discloses a driving method, a device, equipment and a computer readable medium for wireless internet access, which relate to the field of communication, and the method comprises the following steps: installing a filter driver in a host; determining whether the wireless internet access terminal inserted into the host is mounted under a host controller which is not supported by Microsoft drive by utilizing the filter driver; and if the wireless internet access terminal is determined to be mounted under the host controller which is not supported by the Microsoft drive, generating a switching instruction packet for switching the wireless internet access terminal into a network port, and sending the switching instruction packet to the wireless internet access terminal.

Description

A driving method, device and computer-readable medium for wireless Internet access

technical field

Embodiments of the present invention relate to the field of communications, and in particular, to a driving method, an apparatus, and a computer-readable medium for wireless Internet access.

Background technique

When the wireless Internet terminal is used on the host, some application software is required to manage the terminal. These application software run from the large-capacity CD of the wireless Internet terminal, so the wireless Internet terminal must first be enumerated as a large-capacity CD on the host, and then Then switch the enumeration from the CD to the network port to complete the Internet access function.

The network ports enumerated by switching of the wireless Internet access terminal on the Windows operating system (or the Windows system) and the non-windows operating system (or the non-windows system) are different. Specifically, the existing technology of switching enumeration from optical discs to different network ports is based on the fact that the host controller driver of the Windows system will issue the system descriptor request, while the non-windows system will not issue the system descriptor request. When the terminal works on the windows system, if the terminal receives a system descriptor request, it will switch to a device that can be recognized by the windows system; when the terminal works on a non-windows system, the terminal will not receive the system descriptor request. Switch to a device that is not recognized by the Windows system.

The system descriptor request of the Windows system is issued by the driver that comes with the Microsoft system, and the Host Controller Driver (HCD) of some Windows systems is not native to the Microsoft system. These drivers do not issue system descriptors, resulting in The terminal does not receive the system descriptor request on the Windows system, and mistakenly believes that the working environment is not the Windows system, so it is switched to a device that can only be recognized by the non-windows system on the system, and cannot be used on the Windows system.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a driving method, a device, and a computer-readable medium for wireless Internet access. In the case where a wireless Internet access terminal is mounted on a host controller that is not supported by a Microsoft driver, the embodiments of the present invention can solve the problem of the wireless Internet access terminal. Unable to toggle enumeration as host-recognized device issue.

An embodiment of the present invention provides a driving method for wireless Internet access, including:

Install the filter driver in the host;

Using the filter driver, determine whether the wireless Internet access terminal that has been inserted into the host is mounted under a host controller not supported by a Microsoft driver;

If it is determined that the wireless surfing terminal is mounted under a host controller not supported by a Microsoft driver, a switching instruction packet for switching the wireless surfing terminal to a network port is generated and sent to the wireless surfing terminal.

An embodiment of the present invention provides a driving device for wireless Internet access, including:

Install module for installing the filter driver in the host;

a determining module, configured to use the filter driver to determine whether the wireless Internet access terminal that has been inserted into the host is mounted under a host controller supported by a non-Microsoft driver;

The sending module is configured to generate a switching instruction packet for switching the wireless Internet access terminal to a network port if it is determined that the wireless Internet access terminal is mounted under a host controller supported by a non-Microsoft driver, and send it to the wireless Internet access terminal. Internet terminal.

An embodiment of the present invention provides a driving device for wireless Internet access, the device includes: a processor and a memory, the memory stores a driver program for wireless Internet access that can run on the processor, and the memory When the driver for wireless Internet access is executed by the processor, the steps of the driving method for wireless Internet access are implemented.

An embodiment of the present invention provides a computer-readable medium on which a driver for wireless Internet access is stored, and when the driver for wireless Internet access is executed by a processor, the steps of the driving method for wireless Internet access are implemented .

In the embodiment of the present invention, a filter driver is used, and when it is determined that the wireless Internet access terminal is mounted under a host controller not supported by a Microsoft driver, a switching instruction packet carrying a request for a system descriptor already supported by the wireless Internet access terminal is delivered, so as to ensure that the wireless Internet access terminal is Complete the normal switch.

Description of drawings

1 is a schematic flowchart of a driving method for wireless Internet access provided by an embodiment of the present invention;

2 is a schematic structural diagram of a drive system provided by an embodiment of the present invention;

FIG. 3 is a schematic flowchart of the host environment detection module 21 of FIG. 2;

FIG. 4 is a schematic flowchart of the driver installation module 22 of FIG. 2;

5 is a schematic flowchart of the instruction packet processing module 24 of FIG. 2;

6 is a schematic flowchart of installing a filter driver provided by an embodiment of the present invention;

7 is a schematic flowchart of a terminal provided by an embodiment of the present invention from being inserted into a host to completing switching;

8 is a schematic structural block diagram of a driving device for wireless Internet access provided by an embodiment of the present invention;

FIG. 9 is a schematic structural block diagram of a driving device for wireless Internet access provided by an embodiment of the present invention.

Detailed ways

The embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be understood that the embodiments described below are only used to illustrate and explain the present invention, but not to limit the present invention. The terms "comprising", "including", "having", "containing" and the like used in the embodiments of the present invention are all open-ended terms, meaning including but not limited to.

This embodiment of the present invention does not require any modification to the terminal firmware, and only needs to provide a drive system on the host side. The drive system will automatically detect the computer environment in which the terminal works. If the host controller driver of the terminal working host is from Microsoft, Then the driver (or filter driver or filter driver) in the drive system does not do any work, and the terminal still relies on the system descriptor request issued by the driver of the operating system of the host to complete the switch; If the host controller supports the system's built-in driver (or non-Microsoft driver support, Microsoft driver does not support, non-system driver support, Windows operating system built-in driver does not support, system built-in driver does not support, system driver does not support), the driver The system should pre-install a filter driver for large-capacity devices in the host. The filter driver can detect whether the device (or terminal) is mounted on the host controller that is not supported by the system driver when it is inserted into the host. Under the host controller, the filter driver will send a system descriptor USB request (or a system descriptor request) to the terminal to ensure terminal switching.

FIG. 1 is a schematic flowchart of a driving method for wireless Internet access provided by an embodiment of the present invention. As shown in FIG. 1 , the method may include:

Step S101: Install a filter driver in the host.

In one embodiment, step S101 includes: pre-installing the filter driver in the host with a host controller supported by a non-Microsoft driver, then searching for a mass device instance in the registry of the host, and Modifying the configuration identifier of the large-capacity device instance, wherein the configuration identifier is used to instruct the host to reinstall the filter for the wireless Internet access terminal after detecting the inserted (or connected) wireless Internet access terminal driver.

In this embodiment, the filter driver only runs the driver in the host kernel of the host controller not supported by the Microsoft driver, to ensure that the wireless Internet access terminal is mounted on the host controller not supported by the Microsoft driver. The Internet terminal can be switched to enumerate as a host-identifiable device.

In another embodiment, before step S101, an environment detection step is further included, and the environment detection step includes: acquiring the friendly name and driver provider of each host controller in the host, and according to each host controller in the host A friendly name of a host controller and a driver provider to determine whether the filter driver needs to be installed in the host.

In this implementation manner, if the friendly name of the host controller in the host includes USB3.0, and the driver provider is not Microsoft, it means that there is a host controller supported by a non-Microsoft driver in the host, and it is determined at this time The filter driver needs to be installed in the host.

In this embodiment, if the friendly name of the host controller in the host does not include USB3.0, or the friendly name of the host controller in the host includes USB3.0 and the driver provider is Microsoft, then It means that the host controllers existing in the host are all host controllers supported by Microsoft drivers. In this case, it is determined that the filter driver does not need to be installed in the host.

Step S102: Using the filter driver, it is determined whether the wireless Internet access terminal that has been inserted into the host is mounted under a host controller that is not supported by a Microsoft driver.

In one embodiment, step S102 includes: using the filter driver to query the mount relationship to obtain the host controller corresponding to the wireless Internet access terminal, if the friendly name of the host controller includes USB3.0 , and the driver provider is not Microsoft, it is determined that the wireless Internet access terminal is mounted under a host controller supported by a non-Microsoft driver.

Step S103: If it is determined that the wireless Internet access terminal is mounted under a host controller not supported by a Microsoft driver, a switching instruction packet for switching the wireless Internet access terminal to a network port is generated, and sent to the wireless Internet access terminal .

In one embodiment, step S103 includes: using the filter driver to create a USB request block, filling the USB request block with a system descriptor request for switching the wireless Internet access terminal to a network port, and then Create a switching instruction packet (or instruction packet, I/O control request packet, I/O request packet), and fill the USB request block filled with the system descriptor request into the switching instruction packet, and send to the wireless Internet access terminal.

In another embodiment, the method further includes: if it is determined that the wireless Internet access terminal is mounted under a host controller supported by a Microsoft driver, no longer use the filter driver to deliver the wireless Internet access terminal to the wireless Internet access terminal. The switching instruction packet, that is, the filter driver does not perform any work.

FIG. 2 is a schematic structural diagram of a drive system provided by an embodiment of the present invention. As shown in FIG. 2 , the drive system may include: a host environment detection module 21 , a driver installation module 22 , a terminal mount relationship detection module 23 , and an instruction packet processing module twenty four.

The host environment detection module 21 is used to detect whether there is a non-system built-in driver support (or non-system built-in driver support, Windows operating system built-in driver does not support, system built-in driver does not support, system built-in driver does not support, system built-in driver does not support not supported) host controller.

The driver installation module 22 is used to pre-install the driver (or filter driver, filter driver) in the host system under the host environment of the host controller supported by the non-system built-in driver, instructing the operating system to find each time terminal, traverse the driver pool again, and install a driver for the terminal.

The terminal mounting relationship detection module 23 is used to detect which host controller the terminal is specifically mounted on after being inserted into the host. If the terminal is mounted on a host controller supported by the system driver (or supported by the system's built-in driver and the Windows operating system's built-in driver), the filter driver will not send command packets.

The instruction packet processing module 24 is used to receive an instruction from the terminal mounting relationship detection module 23, and if an instruction packet needs to be sent, the instruction packet is grouped and sent to ensure normal switching of the terminal.

FIG. 3 is a schematic flowchart of the host environment detection module 21 of FIG. 2 . As shown in FIG. 3 , the workflow of the host environment detection module 21 may include the following steps:

Steps S301 to S303: the host environment detection module 21 opens the host controller on the host, obtains the device handle of the host controller, obtains the host controller key name (or host controller drive key name) through the device handle, and controls the host through the host controller. The device key name gets the friendly name of the host controller and driver provider.

Steps S304 to S306: If all the host controller friendly names on the host do not have the word USB3.0, it is considered that the host environment does not need to install the filter driver for issuing the system descriptor request. If there is a friendly name of the host controller in the words, it will further obtain the provider of the host controller driver, and determine whether the provider is Microsoft. Recording this environment requires installing a filter driver.

FIG. 4 is a schematic flowchart of the driver installation module 22 of FIG. 2 . As shown in FIG. 4 , the workflow of the driver installation module 22 may include the following steps:

Step S401: Pre-install the driver (or filter driver, filter driver) in the host system.

Steps S402 to S404: if the driver is pre-installed successfully, search for the terminal mass storage device instance in the registry, and modify the value of ConfigFlags under this instance, the purpose is to make the host system rediscover the terminal mass device every time. At the same time, go to the driver pool to find and install the driver for the large-capacity device again.

FIG. 5 is a schematic flowchart of the instruction packet processing module 24 of FIG. 2 . As shown in FIG. 5 , the workflow of the instruction packet processing module 24 may include the following steps:

Steps S501 to S502: after starting the processing of the device request, first determine the result of the terminal mounting relationship module 23, if the terminal is mounted under the host controller supported by the system driver, the filter driver does not perform the command packet sending operation, if If the terminal is mounted under the host controller not supported by the system driver, the following command packet sending processing is performed.

Step S503: Allocate memory for the USB Request Block (URB), then construct a custom command URB to control the transmission, fill each field in the URB structure with the content required by the request, and fill the system descriptor request to the transmission buffer middle.

Step S504: Create an internal I/O control request.

Step S505: The address of the URB carrying the system descriptor request is filled in the Argument1 field of Parameters.Others of the IO stack of the I/O control request.

Step S506: Send the URB request to the next-layer driver, and the USB driver (USBD) sends the instruction packet to the terminal. So far, the terminal receives the switching instruction and completes the switching from the optical disc to the network port.

FIG. 6 is a schematic flowchart of installing a filter driver provided by an embodiment of the present invention. As shown in FIG. 6 , the process of installing a filter driver may include the following steps:

Step S601: Open all host controllers on the host through HCDx, where x is a serial number from 0 to 9. If the opening is successful, the device handle of the host controller can be obtained.

Step S602: Obtain the host controller key name (or host controller drive key name) through the device handle.

Step S603: Obtain the friendly name of the host controller through the controller key name (or the host controller drive key name).

Step S604: Determine whether the friendly name of the host controller has the word USB3.0, if there is no word USB3.0, you do not need to continue to pay attention to the information of the host controller, and perform step S609, that is, check the information of the next host controller, if all If the host controller does not have the word USB3.0, step S610 is performed, that is, the filter driver installation is not performed; if a host controller with the word USB3.0 is encountered, the next step S605 is performed.

Step S605: Obtain the provider of the host controller driver.

Step S606: Determine whether the driver provider is Microsoft. If it is Microsoft, then step S609 needs to be performed, that is, the next host controller information is checked. If the drivers of the remaining 3.0 host controllers are also Microsoft, then step S609 is performed. S610, that is, no filter driver installation is performed, otherwise, the next step S607 is performed.

Step S607: Pre-install the filter driver of the terminal's large-capacity device on the host.

Step S608: Instruct the operating system to search for and install a driver for the large-capacity device again every time the operating system discovers the large-capacity device of the terminal.

So far, the filter driver of the terminal is pre-installed in the host with a USB3.0 host controller that is not supported by the system driver, and it is enough to wait for the terminal to be inserted into the host to continue working.

7 is a schematic flowchart of a terminal from being inserted into a host to completing a handover provided by an embodiment of the present invention. As shown in FIG. 7 , the process of a terminal from being inserted into a host to completing the handover may include the following steps:

Step S701: The terminal is inserted into a host computer with a controller not supported by a system driver.

Step S702: The system finds the large-capacity device reported by the terminal, re-searches for and installs the driver for the large-capacity device, and the filter driver is loaded successfully.

Step S703: The filter-driven terminal mounting relationship module detects which host controller the terminal is mounted on.

Step S704: If the terminal is mounted on the host controller supported by the system driver, instruct the filter driver not to send the switching instruction packet; if the terminal is mounted on the host controller not supported by the system driver, instruct the filter driver to send the switching instruction packet.

Step S705: The filter driver receives the device startup request.

Step S706: The filter driver creates a URB in the device startup request, allocates memory for the URB, and then fills each field in the URB structure, wherein the system descriptor request is filled into the transmission buffer.

Step S707: Create an internal I/O control request (or I/O request package).

Step S708: Fill the address of the URB carrying the system descriptor request into the Argument1 field of Parameters.Others of the IO stack of the I/O control request.

Step S709: Send the URB request to the next-layer driver, the USBD sends the instruction packet to the terminal, and the terminal receives the switching instruction to complete the switching from the optical disc to the network port.

In view of the situation that the wireless Internet access terminal is mounted on a host controller not supported by Microsoft drivers, it cannot be guaranteed that the enumeration of the wireless Internet access terminal can be switched to a host-identifiable device. The current solution is that the service residing in the system detects After the terminal enumerates the optical disc, it sends a Small Computer System Interface (SCSI) command negotiated with the terminal to the terminal. When the terminal receives the command to switch itself from the optical disc to the network device, the terminal completes the switch. In this solution, because the service needs to wait for the CD on the system to be ready before sending the switching command, the switching time is relatively long, and sometimes the service startup is abnormal when the system is in hibernation, resulting in the terminal staying on the CD all the time, requiring the user to manually eject CD. Only the terminal can enumerate the network ports, and the user experience is not good. It can be seen from the above embodiments that the drive system of the embodiment of the present invention can send a request for a system descriptor already supported by the terminal, instead of sending a custom request negotiated with the terminal, which ensures that the terminal firmware can be completed without any modification. The normal switching of the terminal; among them, the system descriptor request issued by the driver is a USB request, so it is not necessary to wait for the CD-ROM function of the terminal on the host to be ready before it can be issued. Compared with the issuing timing of the SCSI command, the terminal switching is faster; and The driver system has carried out the environment detection and the host controller detection of the mounted terminal, which ensures that the driver can only be run in the host kernel of the host controller supported by the non-operating system driver, and avoids the driver stability caused by the installation and use of the driver in all systems. And the occurrence of bad experience caused by compatibility.

FIG. 8 is a schematic structural block diagram of a driving device for wireless Internet access provided by an embodiment of the present invention. As shown in FIG. 8 , the device may include an installation module 81 , a determination module 82 and a transmission module 83 .

The installation module 81 is used to install the filter driver in the host.

In one embodiment, the installation module 81 pre-installs the filter driver in the host with a non-Microsoft driver-supported host controller, and then searches the registry of the host for a mass device instance, And modify the configuration identifier of the large-capacity device instance, wherein the configuration identifier is used to instruct the host to reinstall the wireless Internet access terminal for the wireless Internet access terminal after detecting the inserted (or connected) wireless Internet access terminal. Filter driver.

In this embodiment, the filter driver only runs the driver in the host kernel of the host controller not supported by the Microsoft driver, to ensure that the wireless Internet access terminal is mounted on the host controller not supported by the Microsoft driver. The Internet terminal can be switched to enumerate as a host-identifiable device.

In another embodiment, the installation module 81 is further configured to perform an environment detection step before installing the filter driver in the host, that is, to obtain the friendly name and driver provider of each host controller in the host, according to the The friendly name and driver provider of each host controller in the host are used to determine whether the filter driver needs to be installed in the host.

In this embodiment, if the friendly name of the host controller in the host includes USB3.0, and the driver provider is not Microsoft, it means that there is a host controller supported by non-Microsoft drivers in the host. The installation module 81 determines that the filter driver needs to be installed in the host.

In this embodiment, if the friendly name of the host controller in the host does not include USB3.0, or the friendly name of the host controller in the host includes USB3.0 and the driver provider is Microsoft, then It means that the host controllers existing in the host are all host controllers supported by Microsoft drivers. At this time, the installation module 81 determines that the filter driver does not need to be installed in the host.

The determining module 82 is configured to use the filter driver to determine whether the wireless Internet access terminal that has been inserted into the host is mounted under a host controller supported by a non-Microsoft driver.

In one embodiment, the determination module 82 uses the filter driver to query the mount relationship to obtain the host controller corresponding to the wireless Internet access terminal, if the friendly name of the host controller includes USB3. 0, and the driver provider is not Microsoft, it is determined that the wireless Internet access terminal is mounted under a host controller supported by a non-Microsoft driver.

The sending module 83 is configured to generate a switching instruction packet for switching the wireless Internet access terminal to a network port if it is determined that the wireless Internet access terminal is mounted under a host controller not supported by a Microsoft driver, and send it to the wireless Internet access terminal.

In one embodiment, the sending module 83 uses the filter driver to create a USB request block, and fills the USB request block with a system descriptor request for switching the wireless Internet access terminal to a network port, Then, a switching instruction packet is created, and the USB request block filled with the system descriptor request is filled into the switching instruction packet, and sent to the wireless Internet access terminal.

In another embodiment, the sending module 83 is further configured to, if it is determined that the wireless Internet access terminal is mounted under the host controller supported by the Microsoft driver, no longer use the filter driver to download to the wireless Internet access terminal Send the switching instruction packet.

FIG. 9 is a schematic structural block diagram of a driving device for wireless Internet access provided by an embodiment of the present invention. As shown in FIG. 9 , the device may include: a processor 91 and a memory 92, where the memory 92 stores The driver program for wireless Internet access that can be run on the processor 91, and the steps of the driving method for wireless Internet access described when the driver program for wireless Internet access is executed by the processor 91.

Embodiments of the present invention further provide a computer-readable medium on which a driver for wireless Internet access is stored, and when the driver for wireless Internet access is executed by a processor, the driving method for wireless Internet access is implemented. step.

Those of ordinary skill in the art can understand that all or some of the steps in the methods disclosed above, functional modules/units in the systems, and devices can be implemented as software, firmware, hardware, and appropriate combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical components Components execute cooperatively. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit . Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As known to those of ordinary skill in the art, the term computer storage media includes both volatile and nonvolatile implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules or other data flexible, removable and non-removable media. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery media, as is well known to those of ordinary skill in the art .

The drive system of the embodiment of the present invention relies on the filter driver of the terminal's large-capacity device to issue the system descriptor request already supported by the terminal, instead of sending a custom request negotiated with the terminal, which ensures that the terminal firmware can be completed without any modification. The normal switching of the terminal; the driver system performs the environment detection and the host controller detection of the mounted terminal to ensure that the driver is only run in the host kernel in question (that is, the filter driver is run in the host controller that is not supported by the Microsoft driver) , to avoid the occurrence of bad experience caused by driver stability and compatibility when all systems install and use the driver; the system descriptor request issued by the driver is a USB request, and it is not necessary to wait for the CD-ROM function of the terminal on the host to be ready. The timing of issuing the SCSI command can be earlier, so that the terminal can complete the handover more quickly.

Although the embodiments of the present invention are described in detail above, the embodiments of the present invention are not limited thereto, and various modifications can be made by those skilled in the art according to the principles of the embodiments of the present invention. Therefore, all modifications made according to the principles of the embodiments of the present invention should be understood as falling within the protection scope of the present invention.

Claims (10)

1. a driving method for wireless Internet access, characterized in that the method comprises: Install the filter driver in the host; Using the filter driver, determine whether the wireless Internet access terminal that has been inserted into the host is mounted under a host controller not supported by a Microsoft driver; If it is determined that the wireless surfing terminal is mounted under a host controller not supported by a Microsoft driver, a switching instruction packet for switching the wireless surfing terminal to a network port is generated and sent to the wireless surfing terminal. 2. The method according to claim 1, wherein before installing and loading the filter driver in the host, the method further comprises: Obtain the friendly name and driver provider of each host controller in the host; Whether the filter driver needs to be installed in the host is determined according to the friendly name and driver provider of each host controller in the host. 3. The method according to claim 2, wherein the determining whether the filter driver needs to be installed in the host according to the friendly name and driver provider of each host controller in the host comprises: If the friendly name of the host controller in the host includes USB3.0, and the driver provider is not Microsoft, it is determined that the filter driver needs to be installed in the host. 4. The method according to any one of claims 1-3, wherein the installing the filter driver in the host comprises: pre-installing the filter driver in the host having a non-Microsoft driver-supported host controller; Look up a large-capacity device instance in the registry of the host, and modify the configuration identifier of the high-capacity device instance, where the configuration identifier is used to indicate that the host is the The wireless Internet access terminal reinstalls the filter driver. 5. The method according to claim 1, characterized in that, determining whether the wireless Internet access terminal that has been inserted into the host is mounted under a host controller supported by a non-Microsoft driver by using the filter driver program comprises: Using the filter driver, query the mount relationship to obtain the host controller corresponding to the wireless Internet access terminal; If the friendly name of the host controller includes USB3.0, and the driver provider is not Microsoft, it is determined that the wireless Internet access terminal is mounted under a host controller supported by a non-Microsoft driver. 6. The method according to claim 1, characterized in that, if it is determined that the wireless Internet access terminal is mounted under a host controller supported by a non-Microsoft driver, then the generation is used to switch the wireless Internet access terminal to a network The port switching instruction packet sent to the wireless Internet access terminal includes: Using the filter driver, filling the USB request block with a system descriptor request for switching the wireless Internet access terminal to a network port; Filling the USB request block filled with the system descriptor request into a switching instruction packet, and sending it to the wireless Internet access terminal. 7. The method according to claim 6, wherein the method further comprises: If it is determined that the wireless Internet access terminal is mounted under the host controller supported by the Microsoft driver, the filter driver is no longer used to deliver the switching instruction packet to the wireless Internet access terminal. 8. A driving device for wireless Internet access, wherein the device comprises: Install module for installing the filter driver in the host; a determining module, configured to use the filter driver to determine whether the wireless Internet access terminal that has been inserted into the host is mounted under a host controller supported by a non-Microsoft driver; The sending module is configured to generate a switching instruction packet for switching the wireless Internet access terminal to a network port if it is determined that the wireless Internet access terminal is mounted under a host controller supported by a non-Microsoft driver, and send it to the wireless Internet access terminal. Internet terminal. 9. A drive device for wireless Internet access, the device comprising: a processor and a memory, wherein the memory stores a driver for wireless Internet access that can be run on the processor, so When the driver for wireless Internet access is executed by the processor, the steps of the driving method for wireless Internet access according to any one of claims 1 to 7 are implemented. 10. A computer-readable medium, characterized in that a driver for wireless Internet access is stored thereon, and the driver for wireless Internet access is implemented as described in any one of claims 1 to 7 when the processor is executed. The steps of the described driving method for wireless Internet access.

Images