CN111104170A - Driving method and device for wireless internet access and computer readable medium - Google Patents
Driving method and device for wireless internet access and computer readable medium Download PDFInfo
- Publication number
- CN111104170A CN111104170A CN201811254922.XA CN201811254922A CN111104170A CN 111104170 A CN111104170 A CN 111104170A CN 201811254922 A CN201811254922 A CN 201811254922A CN 111104170 A CN111104170 A CN 111104170A
- Authority
- CN
- China
- Prior art keywords
- wireless internet
- internet access
- host
- driver
- access terminal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4416—Network booting; Remote initial program loading [RIPL]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
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
Technical Field
The present invention relates to the field of communications, and in particular, to a driving method and apparatus for wireless internet access, and a computer readable medium.
Background
When the wireless internet access terminal is used on the host, some application software is needed to manage the terminal, and the application software runs from the large-capacity optical disc of the wireless internet access terminal, so that the wireless internet access terminal is firstly enumerated as the large-capacity optical disc on the host, and then is switched from the optical disc to the network port to complete the internet access function.
The wireless internet access terminal switches enumerated network ports on a windows operating system (or a windows system) and a non-windows operating system (or a non-windows system) to be different. Specifically, the existing technology for switching enumeration from an optical disc to a different network port is based on that a windows system with a host controller driver issues a system descriptor request, but the windows system does not issue the system descriptor request. When the terminal works on the windows system, if the terminal receives a system descriptor request, switching to equipment which can be identified by the windows system; when the terminal works on the non-windows system, the terminal does not receive the system descriptor request, and the device which can be identified by the non-windows system is switched to.
The system descriptor requests of the windows system are issued by own drivers of the windows system, while Host Controller Drivers (HCD) of some windows systems are not own drivers of the windows system, and the drivers do not issue the system descriptor, so that the terminal does not receive the system descriptor requests on the windows system, and the working environment is not the windows system by mistake, so that a device which can be identified by the non-windows system is switched on the system and cannot be used on the windows system.
Disclosure of Invention
The embodiment of the invention provides a driving method and device for wireless internet access and a computer readable medium, aiming at the condition that a wireless internet access terminal is mounted on a host controller which is not supported by Microsoft drive, the embodiment of the invention can solve the problem that the wireless internet access terminal can not be switched and enumerated as host identifiable equipment.
The embodiment of the invention provides a driving method for wireless internet access, which 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.
The embodiment of the invention provides a driving device for wireless internet access, which comprises:
the installation module is used for installing a filter driver in the host;
the determining module is used for 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 the sending module is used for 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 if the wireless internet access terminal is determined to be mounted under the host controller which is not supported by Microsoft drive.
The embodiment of the invention provides a driving device for wireless internet access, which comprises: the driving program for wireless internet access is executed by the processor, and the steps of the driving method for wireless internet access are realized.
The embodiment of the invention provides a computer readable medium, on which a driver for wireless internet access is stored, and when being executed by a processor, the driver for wireless internet access realizes the steps of the driving method for wireless internet access.
The embodiment of the invention utilizes the filter driving program to send the switching instruction packet carrying the system descriptor request supported by the wireless internet access terminal when the wireless internet access terminal is determined to be mounted under the host controller which is not supported by the Microsoft drive, thereby ensuring that the wireless internet access terminal completes normal switching.
Drawings
Fig. 1 is a flowchart illustrating a driving method for wireless internet access according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a driving system provided in an embodiment of the present invention;
FIG. 3 is a schematic flow diagram of host environment detection module 21 of FIG. 2;
FIG. 4 is a schematic flow diagram of the drive mounting module 22 of FIG. 2;
FIG. 5 is a schematic flow diagram of the instruction packet processing module 24 of FIG. 2;
FIG. 6 is a flow chart illustrating installation of a filter driver according to an embodiment of the present invention;
fig. 7 is a schematic flowchart of a terminal switching from host insertion to host completion according to an embodiment of the present invention;
fig. 8 is a schematic structural block diagram of a driving apparatus for wireless internet access according to an embodiment of the present invention;
fig. 9 is a schematic structural block diagram of a driving device for wireless internet access according to an embodiment of the present invention.
Detailed Description
The embodiments of the present invention will be described in detail below with reference to the accompanying drawings, and it should be understood that the embodiments described below are only for illustrating and explaining the present invention and are not intended to limit the present invention. Embodiments of the present invention use the terms "comprising," "including," "having," "containing," and the like, as open-ended terms, i.e., meaning including, but not limited to.
The embodiment of the invention does not need to change the terminal firmware, only a drive system is provided at the host side, the drive system can automatically detect the computer environment of the terminal working, if the host controller drive of the terminal working host is Microsoft, the drive (or the filter drive program) in the drive system does not work, and the terminal still completes the switching by the system descriptor request sent by the operating system of the host from the tape drive; if a host controller which is not supported by the system self-contained driver (or is not supported by the microsoft driver, is not supported by the non-system driver, is not supported by the windows operating system self-contained driver, is not supported by the system self-contained driver, and is not supported by the system driver) exists in the host environment where the terminal is to operate, the drive system is to pre-install a filter driver of a large-capacity device in the host, wherein the filter driver can detect whether the device (or the terminal) is mounted under the host controller which is not supported by the system driver when the device (or the terminal) is plugged into the host, and if the filter driver is mounted under the host controller, the filter driver can send a system descriptor USB request (or a system descriptor request) to the terminal, so that the terminal.
Fig. 1 is a schematic flowchart of a driving method for wireless internet access according to an embodiment of the present invention, and as shown in fig. 1, the method may include:
step S101: a filter driver is installed in the host.
In one embodiment, step S101 includes: the method comprises the steps of pre-installing the filter driver in a host with a host controller supported by non-Microsoft drive, then searching a large-capacity device instance in a registry of the host, and modifying a configuration identifier of the large-capacity device instance, wherein the configuration identifier is used for indicating the host to reinstall the filter driver for a wireless internet access terminal after detecting the inserted (or accessed) wireless internet access terminal.
In this embodiment, the filter driver only runs the driver in the host kernel of the host controller supported by the non-microsoft driver, and it is ensured that the wireless internet access terminal can switch and enumerate as the host recognizable device when the wireless internet access terminal is mounted on the host controller supported by the non-microsoft driver.
In another embodiment, before step S101, an environment detection step is further included, and the environment detection step includes: and acquiring the friendly name and the driver provider of each host controller in the host, and determining whether the filter driver is required to be installed in the host according to the friendly name and the driver provider of each host controller 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 indicates that there is a host controller supported by non-microsoft driver in the host, and at this time, it is determined 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 if the friendly name of the host controller in the host includes USB3.0 and the driver provider is microsoft, it is determined that the host controllers existing in the host are all host controllers supported by microsoft driver, and at this time, it is determined that the host does not need to install the filter driver.
Step S102: and 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.
In one embodiment, step S102 includes: and querying a mounting relation by using the filter driver to obtain the host controller corresponding to the wireless internet access terminal, and if the friendly name of the host controller contains USB3.0 and the driver provider is not Microsoft, determining that the wireless internet access terminal is mounted under the host controller supported by non-Microsoft driver.
Step S103: 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.
In one embodiment, step S103 includes: and creating a USB request block by using the filter driver, filling a system descriptor request for switching the wireless internet terminal into a network port into the USB request block, then creating a switching instruction packet (or an instruction packet, an I/O control request packet and an I/O request packet), filling the USB request block filled with the system descriptor request into the switching instruction packet, and sending the USB request block to the wireless internet terminal.
In another embodiment, the method further comprises: if the wireless internet access terminal is determined to be mounted under the host controller supported by the microsoft drive, the switching instruction packet is not sent to the wireless internet access terminal by using the filter driver, namely the filter driver does not work.
Fig. 2 is a schematic structural diagram of a driving system according to an embodiment of the present invention, and as shown in fig. 2, the driving system may include: the system comprises a host environment detection module 21, a drive installation module 22, a terminal mounting relation detection module 23 and an instruction packet processing module 24.
The host environment detection module 21 is configured to detect whether a host controller that is not supported by the system driver (or is supported by the system driver, and is not supported by the windows os driver, and is not supported by the system driver) exists on a host to which the terminal is about to operate.
The driver installation module 22 is configured to, in a host environment with a host controller that is not supported by a system-owned driver, pre-install a driver (or a filter driver, a filter driver) in the host system, instruct an operating system to discover a terminal each time, traverse a driver pool again, and install the driver for the terminal.
The terminal mounting relationship detection module 23 is configured to detect under which host controller a terminal is specifically mounted after being inserted into a host, instruct the filter driver to send the instruction packet if the terminal is mounted under a host controller that is not supported by the system driver, and not send the instruction packet if the terminal is mounted under a host controller that is supported by the system driver (or supported by the system driver and supported by the windows operating system).
The instruction packet processing module 24 is configured to receive an instruction from the terminal mounting relationship detecting module 23, and if the instruction packet needs to be sent, perform instruction packet packaging and sending to ensure normal switching of the terminal.
Fig. 3 is a schematic flowchart of the host environment detection module 21 in fig. 2, and as shown in fig. 3, the workflow of the host environment detection module 21 may include the following steps:
step S301 to step S303: the host environment detection module 21 opens the host controller on the host to obtain the device handle of the host controller, obtains the host controller key name (or host controller drive key name) through the device handle, and obtains the friendly name and the drive provider of the host controller through the host controller key name.
Step S304 to step S306: if all host controller friendly names on the host do not have the USB3.0 word, the host environment is considered to be free from installing a filter driver for issuing a system descriptor request, if the host has the host controller friendly names with the USB3.0 word, a provider of the host controller driver is further obtained, whether the provider is Microsoft is judged, and if the host has a host controller which is not supported by the Microsoft driver (namely, the Microsoft driver does not support), the environment is recorded to be required to install the filter driver.
Fig. 4 is a schematic flow chart of the driver installation module 22 of fig. 2, and as shown in fig. 4, the work flow of the driver installation module 22 may include the following steps:
step S401: the driver (or filter driver, filter driver) is pre-installed in the host system.
Step S402 to step S404: if the driver is preinstalled successfully, searching the terminal mass storage device instance in the registry, and modifying the value of the ConfigFlags under the instance, so that the host system searches and installs the driver for the mass storage device again in the driver pool every time the host system redisfinds the mass storage device of the terminal.
Fig. 5 is a schematic flow chart of the instruction packet processing module 24 of fig. 2, and as shown in fig. 5, the work flow of the instruction packet processing module 24 may include the following steps:
step S501 to step S502: after the processing of the device request is started, the result of the terminal mount relation module 23 is first determined, if the terminal is mounted under the host controller supported by the system driver, the filter driver does not perform the instruction packet transmission operation, and if the terminal is mounted under the host controller not supported by the system driver, the following instruction packet transmission processing is performed.
Step S503: allocating memory for USB Request Block (URB), then constructing a custom command URB to control transmission, filling each field in URB structure with the content required by the Request, wherein the system descriptor Request is filled in the transmission buffer.
Step S504: an internal I/O control request is created.
Step S505: the address of the URB carrying the system descriptor request fills in the alignment 1 field of parameters.
Step S506: sends a URB request to the next layer driver, and the USB driver (USBD) sends the command packet to the terminal. At this point, the terminal receives the switching instruction to complete the switching from the optical disc to the network port.
Fig. 6 is a schematic flowchart of installing a filter driver according to an embodiment of the present invention, and as shown in fig. 6, the process of installing the filter driver may include the following steps:
step S601: all host controllers on the host are opened via HCDx, where x is a sequence number from 0 to 9, and if the opening is successful, the device handle for that host controller is available.
Step S602: the host controller key name (or host controller drive key name) is obtained from the device handle.
Step S603: the host controller friendly name is obtained by the controller key name (or host controller drive key name).
Step S604: judging whether the friendly name of the host controller has a USB3.0 character, if the friendly name of the host controller has no USB3.0 character, continuing to pay attention to the information of the host controller, executing step S609, namely checking the information of the next host controller, and if all the host controllers have no USB3.0 characters, executing step S610, namely, not installing a filter driver; if a host controller having a USB3.0 character is encountered, the next operation S605 is performed.
Step S605: a provider of the host controller driver is obtained.
Step S606: and judging whether the driver provider is microsoft, if so, executing a step S609, namely, checking information of the next host controller, and if the drivers of the remaining 3.0 host controllers are microsoft, executing a step S610, namely, installing the filter driver, otherwise, executing the next operation S607.
Step S607: the host is pre-installed with a filter driver of a large capacity device of the terminal.
Step S608: and instructing the operating system to search and install the driver for the large-capacity device again each time the large-capacity device of the terminal is found.
Therefore, in the host with the USB3.0 host controller which is not supported by the system driver, the filter driver of the terminal is pre-installed, and the terminal is required to be inserted into the host to continue working.
Fig. 7 is a schematic flowchart of a process from host insertion to handover completion of a terminal according to an embodiment of the present invention, where as shown in fig. 7, the process from host insertion to handover completion of a terminal may include the following steps:
step S701: the terminal is plugged into a host with a controller that is not supported by the system driver.
Step S702: the system finds the large-capacity equipment reported by the terminal, searches and installs the driver for the large-capacity equipment again, and the filter driver is loaded successfully.
Step S703: the filter-driven terminal mount relationship module detects which host controller the terminal is mounted on.
Step S704: if the filter driver is mounted under the host controller supported by the system driver, the filter driver is instructed not to send a switching instruction packet; and if the terminal is mounted under the host controller which is not supported by the system driver, indicating the filter driver to send a switching instruction packet.
Step S705: the filter driver receives a device start request.
Step S706: the filter driver creates a URB in the device start request, allocates memory for the URB, and then fills each domain in the URB structure, wherein the system descriptor requests to be filled into the transport buffer.
Step S707: an internal I/O control request (or I/O request packet) is created.
Step S708: fill in the address of the URB carrying the system descriptor request in the alignment 1 field of parameters.
Step S709: and sending a URB request to a next layer of driver, sending the instruction packet to the terminal by the USBD, and finishing the switching from the optical disc to the network port after the terminal receives the switching instruction.
In order to solve the problem that enumeration of a wireless internet terminal cannot be guaranteed to be switched to a host recognizable device when the wireless internet terminal is mounted on a host controller which is not supported by microsoft drive, a currently adopted scheme is that after a service resident in a System detects an optical disc enumerated by the terminal, a Small Computer System Interface (SCSI) instruction which is negotiated with the terminal is sent to the terminal, and when the terminal receives an instruction for switching the terminal from the optical disc to a network device, the terminal completes switching. In the scheme, since the switching instruction can be sent only after the optical disc on the system is ready, the switching time is long, and the problem of abnormal service start sometimes occurs under the condition of system dormancy, so that the terminal stays on the optical disc all the time, and a user needs to manually eject the optical disc. The terminal can enumerate the network port, and the user experience is not good. It can be seen from the above embodiments that the driving system of the embodiment of the present invention can send a system descriptor request that the terminal has supported, instead of sending a custom request negotiated with the terminal, thereby ensuring that the terminal firmware completes normal switching of the terminal without any modification; the system descriptor request issued by the driver is a USB request, so that the system descriptor request can be issued without waiting for the ready optical disc function of the terminal on the host, and the terminal switching is faster than the issuing opportunity of a SCSI instruction; and the drive system carries out environment detection and host controller detection of the mounted terminal, ensures that the drive is only operated in a host kernel of the host controller supported by the drive of the non-operating system, and avoids the occurrence of bad experience caused by drive stability and compatibility when all systems are installed and used with the drive.
Fig. 8 is a schematic structural block diagram of a driving apparatus for wireless internet access according to an embodiment of the present invention, and as shown in fig. 8, the apparatus may include: an installation module 81, a determination module 82 and a sending module 83.
The installation module 81 is configured to install a filter driver in the host.
In one embodiment, the installation module 81 pre-installs the filter driver in the host with a host controller supported by non-microsoft driver, then searches a registry of the host for an instance of a mass storage device, and modifies a configuration identifier of the instance of the mass storage device, wherein the configuration identifier is used to instruct the host to re-install the filter driver for the wireless internet access terminal after detecting the inserted (or accessed) wireless internet access terminal.
In this embodiment, the filter driver only runs the driver in the host kernel of the host controller supported by the non-microsoft driver, and it is ensured that the wireless internet access terminal can switch and enumerate as the host recognizable device when the wireless internet access terminal is mounted on the host controller supported by the non-microsoft driver.
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, obtain a friendly name and a driver provider of each host controller in the host, and determine whether the filter driver needs to be installed in the host according to the friendly name and the driver provider of each host controller 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 indicates that there is a host controller supported by a non-microsoft driver in the host, and at this time, 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 if the friendly name of the host controller in the host includes USB3.0 and the driver provider is microsoft, it indicates that the host controllers existing in the host are all host controllers supported by microsoft driver, and 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 determine, by using the filter driver, whether the wireless internet access terminal that has been inserted into the host is mounted under a host controller that is not supported by microsoft driver.
In an embodiment, the determining module 82 queries a mount relationship by using the filter driver to obtain the host controller corresponding to the wireless internet access terminal, and if the friendly name of the host controller includes USB3.0 and the driver provider is not microsoft, determines that the wireless internet access terminal is mounted under the host controller supported by 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 in the host controller that is not supported by microsoft driver, and send the switching instruction packet to the wireless internet access terminal.
In an embodiment, the sending module 83 creates a USB request block by using the filter driver, fills a system descriptor request for switching the wireless internet terminal to a network port into the USB request block, then creates a switch instruction packet, fills the USB request block filled with the system descriptor request into the switch instruction packet, and sends the switch instruction packet to the wireless internet terminal.
In another embodiment, the sending module 83 is further configured to not use the filter driver to issue the switching instruction packet to the wireless internet access terminal if it is determined that the wireless internet access terminal is mounted in the host controller supported by microsoft driver.
Fig. 9 is a schematic structural block diagram of a driving device for wireless internet access according to an embodiment of the present invention, and as shown in fig. 9, the device may include: a processor 91 and a memory 92, wherein the memory 92 stores a driver for wireless internet access that can run on the processor 91, and the driver for wireless internet access performs the steps of the driving method for wireless internet access when executed by the processor 91.
The embodiment of the present invention further provides a computer readable medium, on which a driver for wireless internet access is stored, where the driver for wireless internet access, when executed by a processor, implements the steps of the driving method for wireless internet access.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable 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 performed by several physical components in cooperation. Some or all of the 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). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can 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 includes any information delivery media as known to those skilled in the art.
The driving system of the embodiment of the invention issues the system descriptor request supported by the terminal by depending on the filtering drive of the terminal large-capacity equipment, instead of sending the user-defined request negotiated with the terminal, thereby ensuring that the terminal firmware completes the normal switching of the terminal under the condition of not modifying any; the driving system carries out environment detection and host controller detection of the mounted terminal, ensures that the driving is only operated in a host kernel with problems (namely, the filtering driving is operated in the host controller supported by non-Microsoft driving), and avoids the occurrence of bad experience caused by driving stability and compatibility when all systems are installed and used; the system descriptor request issued by the driver is a USB request, and can be issued without waiting for the optical disc function of the terminal on the host to be ready, so that the time for issuing the SCSI instruction can be earlier than the time for issuing the SCSI instruction, and the terminal can complete the switching more quickly.
Although the embodiments of the present invention have been described in detail above, the embodiments of the present invention are not limited thereto, and those skilled in the art can make various modifications according to the principles of the embodiments of the present invention. Therefore, any modifications made to the principles of the embodiments of the present invention should be understood to fall within the scope of the present invention.
Claims (10)
1. A driving method for wireless internet access is characterized by comprising 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.
2. The method of claim 1, prior to installing and loading the filter driver in the host, further comprising:
obtaining a friendly name and a driver provider for each host controller in the host;
determining whether the filter driver needs to be installed in the host based on the friendly name and the driver provider of each host controller in the host.
3. The method of claim 2, wherein determining whether the filter driver needs to be installed in the host based on a friendly name and a driver provider of each host controller in the host comprises:
if USB3.0 is included in the friendly name of the host controller in the host 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 installing the filter driver in the host comprises:
pre-installing the filter driver in the host with a host controller that is not Microsoft drive supported;
and searching a large-capacity device example in a registry of the host, and modifying a configuration identifier of the large-capacity device example, wherein the configuration identifier is used for indicating the host to reinstall the filter driver for the wireless internet access terminal after detecting the inserted wireless internet access terminal.
5. The method of claim 1, wherein determining, by using the filter driver, whether the wireless internet access terminal that is plugged into the host is mounted under a host controller that is not supported by microsoft driver comprises:
utilizing the filter driving program to inquire the mounting relation to obtain the host controller corresponding to the wireless internet access terminal;
if the friendly name of the host controller comprises USB3.0 and the driver provider is not Microsoft, determining that the wireless internet access terminal is mounted under the host controller supported by the non-Microsoft driver.
6. The method according to claim 1, wherein if it is determined that the wireless internet access terminal is mounted on a host controller that is not supported by microsoft driver, generating a switching instruction packet for switching the wireless internet access terminal to a network port, and sending the switching instruction packet to the wireless internet access terminal comprises:
filling a system descriptor request for switching the wireless internet terminal into a network port into a USB request block by using the filter driver;
and filling the USB request block filled with the system descriptor request into a switching instruction packet, and sending the switching instruction packet to the wireless internet access terminal.
7. The method of claim 6, further comprising:
and if the wireless internet access terminal is determined to be mounted under the host controller supported by the Microsoft drive, the switching instruction packet is not sent to the wireless internet access terminal by using the filter driver.
8. A driving apparatus for wireless internet access, the apparatus comprising:
the installation module is used for installing a filter driver in the host;
the determining module is used for 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 the sending module is used for 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 if the wireless internet access terminal is determined to be mounted under the host controller which is not supported by Microsoft drive.
9. A driving apparatus for wireless internet access, the apparatus comprising: processor and memory, characterized in that the memory stores a driver for wireless internet access, the driver being executable on the processor, and when being executed by the processor, the driver for wireless internet access realizes the steps of the driving method for wireless internet access according to any one of claims 1 to 7.
10. A computer-readable medium, on which a driver for wireless internet access is stored, and when executed by a processor, the driver for wireless internet access implements the steps of the driving method for wireless internet access according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811254922.XA CN111104170A (en) | 2018-10-26 | 2018-10-26 | Driving method and device for wireless internet access and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811254922.XA CN111104170A (en) | 2018-10-26 | 2018-10-26 | Driving method and device for wireless internet access and computer readable medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111104170A true CN111104170A (en) | 2020-05-05 |
Family
ID=70418897
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811254922.XA Withdrawn CN111104170A (en) | 2018-10-26 | 2018-10-26 | Driving method and device for wireless internet access and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111104170A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101609408A (en) * | 2009-06-19 | 2009-12-23 | 中兴通讯股份有限公司 | A kind of method and system that realize self-start of terminal equipment |
| CN102088797A (en) * | 2011-01-30 | 2011-06-08 | 中兴通讯股份有限公司 | Wireless communication method and system as well as wireless communication terminal |
| CN104216728A (en) * | 2013-06-03 | 2014-12-17 | 中兴通讯股份有限公司 | Method for connecting USB network card, USB network card and PC |
-
2018
- 2018-10-26 CN CN201811254922.XA patent/CN111104170A/en not_active Withdrawn
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101609408A (en) * | 2009-06-19 | 2009-12-23 | 中兴通讯股份有限公司 | A kind of method and system that realize self-start of terminal equipment |
| CN102088797A (en) * | 2011-01-30 | 2011-06-08 | 中兴通讯股份有限公司 | Wireless communication method and system as well as wireless communication terminal |
| CN104216728A (en) * | 2013-06-03 | 2014-12-17 | 中兴通讯股份有限公司 | Method for connecting USB network card, USB network card and PC |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US4974151A (en) | Configuration capability for devices in an open system having the capability of adding or changing devices by user commands | |
| US10445258B1 (en) | Method for creation of device drivers and device objects for peripheral devices | |
| US7970974B2 (en) | Method and system for adding or removing a logical unit of a USB mass storage device | |
| CN107526653B (en) | Virtual machine management method and server | |
| EP3885903A1 (en) | Cloud desktop upgrade method, device, cloud server, and storage medium | |
| US10678465B2 (en) | Seamless migration of storage volumes between storage arrays | |
| EP3382535A1 (en) | Method for loading drive program, and server | |
| US20190037043A1 (en) | Data Prefetching Method and Apparatus | |
| JP2010219725A (en) | Network device and method of releasing external storage device on network | |
| EP3647929A1 (en) | Installation of operating system | |
| EP2182444A1 (en) | Method for restraining requirements for i/o space of pci device | |
| US20150127916A1 (en) | Dynamic memory allocation | |
| US8528007B1 (en) | Firmware downloading through process file system | |
| WO2020113478A1 (en) | Address information processing method and apparatus, electronic device, and storage medium | |
| CN112015352B (en) | Storage block device identification device, system and storage block device reading and writing method | |
| JP2013105237A (en) | Job processing system, job processing device, load distributing device, job processing program, and load distributing program | |
| CN111104170A (en) | Driving method and device for wireless internet access and computer readable medium | |
| CN107203329B (en) | Storage management method and equipment | |
| US7418716B2 (en) | Method, apparatus, system, and article of manufacture for interfacing a device | |
| US20060130043A1 (en) | Method and apparatus to upgrade software of an apparatus having a plurality of microprocessors | |
| US10049070B2 (en) | Data card, and data card switching method and apparatus | |
| CN109634721B (en) | Method and related device for starting communication between virtual machine and host | |
| CN113900765A (en) | Cloud application starting method, equipment, terminal and computer readable storage medium | |
| CN101826062A (en) | Computer executing method and electric system | |
| US8046560B1 (en) | Serial number based storage device allocation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200505 |
|
| WW01 | Invention patent application withdrawn after publication |