WO2012100518A1 - 一种无线通讯终端的启用方法及装置 - Google Patents
一种无线通讯终端的启用方法及装置 Download PDFInfo
- Publication number
- WO2012100518A1 WO2012100518A1 PCT/CN2011/077695 CN2011077695W WO2012100518A1 WO 2012100518 A1 WO2012100518 A1 WO 2012100518A1 CN 2011077695 W CN2011077695 W CN 2011077695W WO 2012100518 A1 WO2012100518 A1 WO 2012100518A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- operating system
- communication terminal
- wireless communication
- rndis
- ecm
- Prior art date
Links
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
Definitions
- the present invention relates to the field of communication technologies, and in particular to a method and apparatus for enabling a wireless communication terminal. Background technique
- the wireless data card When a user uses a wireless communication terminal such as a universal serial bus (USB) interface, such as a wireless data card, the wireless data card is enabled by two switching modes, specifically, the first time the computer is operated. After the system, the wireless data card enumerates a virtual optical drive, which stores the driver, management program, and help files of the network communication port, the user runs the virtual optical drive, and the management program and the driver are installed, and the wireless data card is completed.
- a virtual optical drive which stores the driver, management program, and help files of the network communication port
- the wireless data card enumerates a type of device such as a human interface device (HID, Human) that is driven by the optical drive and the operating system. Interface Device ), or a combination of cameras, etc., where the optical drive is responsible for installing the management program, and the operating system has its own type of device as the operating system.
- HID human interface device
- Interface Device or a combination of cameras, etc.
- the medium for data exchange with the wireless data card network that is, the network data is exchanged by encapsulating the network data packet into the HID request, or the camera command request, etc., thereby implementing the wireless data card to drive the Internet, but the method needs
- the network packet is encapsulated into a HID request, or a camera command request, etc.
- the specific encapsulation is difficult to implement in practical applications. Therefore, the method has the disadvantages of being technically difficult and difficult to implement.
- Ethernet Control Model is USB communication.
- CDC Device Category
- RNDIS Network Driver Interface Specification
- the RNDIS-compliant wireless data card is available in Windows. When the operating system is enabled, the RNDIS driver of the operating system is automatically installed.
- the main object of the present invention is to provide a method and an apparatus for enabling a wireless communication terminal, which can realize the drive-free activation of the wireless communication terminal.
- the invention provides a method for enabling a wireless communication terminal, the method comprising:
- the wireless communication terminal After the wireless communication terminal is plugged into the host computer and powered on, the wireless communication terminal is enumerated to the RNDIS device of the host operating system, and then the operating system is determined to support the RNDIS device. After determining that the operating system supports the RNDIS device, implementing automatic installation of the wireless communication terminal by using the driver of the operating system; determining that the operating system does not support the RNDIS device, and enumerating the wireless communication terminal to the operating system as an ECM device The automatic installation of the wireless communication terminal is implemented by the driver of the operating system.
- the following includes: configuring, according to the RNDIS, the device, the interface, the descriptor information of the endpoint, and the driving of the data flow and the control flow;
- the following includes: Configuring device, interface, and descriptor information of the endpoint according to the ECM, and driving the data flow and the control flow.
- the enumerating the wireless communication terminal to the operating system of the host is an RNDIS device, which is:
- the device, the interface, and the descriptor information of the endpoint corresponding to the RNDIS sub-device are reported to the operating system.
- the determining whether the operating system of the host supports the RNDIS device is: whether the MS OS descriptor (Descriptor) request sent by the operating system is received within a specified duration.
- the enumerating the wireless communication terminal to the operating system is an ECM device, and: reporting, to the operating system, the device, the interface, and the descriptor information of the endpoint corresponding to the ECM sub-device.
- the method further includes:
- the wireless communication terminal After the automatic installation of the wireless communication terminal is implemented by the driver of the operating system, the wireless communication terminal interacts with the operating system to perform an RNDIS request and an instruction, so that the wireless communication terminal enters a working state.
- the method further includes:
- the wireless communication terminal After the automatic installation of the wireless communication terminal is implemented by the driver of the operating system, the wireless communication terminal performs an ECM request and an instruction interaction with the operating system, so that the wireless communication terminal enters Into the working state.
- the present invention also provides an apparatus for enabling a wireless communication terminal, the apparatus comprising: a configuration unit, an enumeration unit, a determination unit, and an operating system;
- a configuration unit configured to configure an ECM sub-device and an RNDIS sub-device in the wireless communication terminal
- an enumeration unit configured to insert the wireless communication terminal into the computer host and, after power-on, enumerate the wireless communication terminal to the operating system as an RNDIS device, and then Triggering the determining unit; and after receiving the notification from the determining unit, enumerating the wireless communication terminal to the operating system as an ECM device;
- the determining unit is configured to: after receiving the trigger information of the enumeration unit, determine whether the operating system supports the RNDIS device, and notify the enumeration unit operating system that the RNDIS device is not supported after determining that the operating system does not support the RNDIS device;
- the wireless communication terminal after receiving the enumeration unit enumeration, the wireless communication terminal is an RNDIS device, and after determining that the RNDIS device is supported by itself, the automatic installation of the wireless communication terminal is implemented by the driver of the RNDIS; or, the enumeration unit is received After the enumerated wireless communication terminal is an ECM device, the wireless communication terminal is automatically installed by its own driver.
- the device further includes: an RNDIS sub-device, configured to perform an RNDIS request and an instruction interaction with the operating system, so that the wireless communication terminal enters a working state;
- the operating system is further configured to perform an RNDIS request and an instruction interaction with the RNDIS sub-device after the automatic installation of the wireless communication terminal, so that the wireless communication terminal enters a working state.
- the device further includes: an ECM sub-device, configured to perform an ECM request and an instruction interaction with the operating system, so that the wireless communication terminal enters a working state;
- the operating system is further configured to perform an ECM request and an instruction interaction with the ECM sub-device after the automatic installation of the wireless communication terminal, so that the wireless communication terminal enters a working state.
- the method and device for enabling a wireless communication terminal configured an ECM sub-device and an RNDIS sub-device in a wireless communication terminal, and the wireless communication terminal is inserted into the host computer and, after power-on, enumerates the wireless communication terminal to the operating system of the host computer.
- RNDIS device determines the host's Whether the operating system supports the RNDIS device, after determining that the operating system of the host supports the RNDIS device, the automatic installation of the wireless communication terminal is implemented by the driver of the operating system of the host; determining that the operating system of the host does not support the RNDIS device,
- the wireless communication terminal is an ECM device, and the automatic installation of the wireless communication terminal is realized by the driver of the operating system of the host computer, so that the driverless automatic activation of the wireless communication terminal can be realized, thereby simplifying the user's use process and saving user time. This enhances the user experience; and, it can be applied to different operating systems.
- the activation scheme of the wireless communication terminal provided by the present invention does not need to store the driver in advance in the Flash of the wireless communication terminal, thereby reducing the space occupied by the Flash of the wireless communication terminal, thereby reducing the product cost.
- FIG. 1 is a schematic flowchart of a method for enabling a wireless communication terminal according to the present invention
- FIG. 2 is a schematic flowchart of a method for enabling a wireless data card according to an embodiment
- FIG. 3 is a schematic structural diagram of an apparatus for enabling a wireless communication terminal according to the present invention. detailed description
- the method for enabling the wireless communication terminal of the present invention includes the following steps:
- Step 100 Configure an ECM sub-device and an RNDIS sub-device in the wireless data card.
- the ECM sub-device is configured to enable the wireless data card to support the Linux operating system and the MAC operating system.
- the RNDIS sub-device is configured to enable the wireless data card.
- the ECM sub-device and the RNDIS sub-device are two independent sub-devices, that is, when the wireless data card is in use, the ECM sub-device does not perform any information interaction with the RNDIS sub-device; Since the current operating system mainly includes: Linux operating system, MAC operating system, and Windows operating system, the ECM sub-device and the RNDIS sub-device can be configured in the wireless data card, so that the wireless data card can be applied to different operating systems. ;
- the ECM sub-device When the ECM sub-device is configured, the following includes: Decoding the device, the interface, the descriptor information of the endpoint, and the data flow and the control flow according to the ECM; wherein the descriptor information of the device, the interface, and the endpoint is configured to enable the wireless data card When in use, it becomes a wireless data card that supports ECM, that is, a wireless data card that supports the Linux operating system and the MAC operating system; the data stream and the control stream are driven so that the wireless data card can be used when it is in use. The flow and control flow are controlled; the hardware configuration of the ECM sub-device is the same as the hardware configuration of the existing wireless data card;
- the RNDIS sub-device When the RNDIS sub-device is configured, the following includes: configuring the device, the interface, the descriptor information of the endpoint, and the data flow and the control flow according to the RNDIS; wherein the descriptor information of the device, the interface, and the endpoint is configured to enable the wireless data card In use, it becomes a wireless data card supporting RNDIS, namely: Supports the Windows operating system; Configures the data stream and the control stream driver to control the data stream and the control stream when the wireless data card is in use; RNDIS
- the hardware configuration of the device is the same as the hardware configuration of the existing wireless data card.
- Step 101 After the wireless data card is inserted into the host computer and is powered on, the wireless data card is enumerated to the host operating system as an RNDIS device, and then the host operating system is determined to support the RNDIS device, and after determining that the operating system of the host supports the RNDIS device, The automatic installation of the wireless data card is implemented by the driver of the operating system of the host; after determining that the operating system of the host does not support the RNDIS device, the wireless data card is enumerated to the operating system of the host as an ECM device, and the driver of the operating system of the host is implemented. Automatic installation of wireless data cards;
- the timing of enumerating the wireless data card to the RNDIS device by the operating system of the host is: the wireless data card receives the USB descriptor request sent by the operating system of the host; wherein, after the wireless data card is powered on, the host The operating system detects the wireless data card and detects the wireless data After the card is sent, the USB descriptor request is sent to the wireless data card; the specific processing flow of the operating system of the host to detect the wireless data card is exactly the same as that of the prior art, and is not described here; enumerating the wireless to the operating system of the host
- the data card is an RNDIS device, specifically:
- the device, the interface, and the descriptor information of the endpoint corresponding to the RNDIS sub-device are reported to the operating system of the host; wherein, in the descriptor information, the value of the bcdDevice parameter is set to be greater than zero, so that the operating system of the host is loaded with the driver.
- the MS OS Descriptor request is sent to the wireless data card; after the device, the interface, and the descriptor information of the endpoint corresponding to the RNDIS sub-device are reported, the wireless data card is currently in the RNDIS configuration state, namely: the wireless data card Equipment to support RNDIS;
- the determining whether the operating system of the host supports the RNDIS device is specifically:
- the MS OS Descriptor request sent by the operating system of the host is received within the specified duration; if the MS OS Descriptor request sent by the operating system of the host is received within the specified time period, the operating system of the host is considered to support the RNDIS device, if If the MS OS Descriptor descriptor request sent by the operating system of the host is not received within the specified duration, the operating system of the host does not support the RNDIS device.
- the wireless data card may be used to report the device, interface, and endpoint descriptor information corresponding to the RNDIS sub-device to the operating system of the host, and the timer may be started, or after the wireless data card is powered on, The timer is started; in actual application, since the operating system of the host detects the wireless data card and sends the USB descriptor request to the wireless data card for a very short time, for the convenience of operation, after the wireless data card is powered on, The timer is started. If the MS OS Descriptor request from the operating system of the host is received within the duration of the timer, the operating system of the host is considered to support the RNDIS device. If the timer expires, the operating system of the host is not received. The MS OS Descriptor request issued, the host operating system does not support the RNDIS device;
- the corresponding descriptor information is searched according to the reported descriptor information.
- the duration of the driver and the length of the timer after the driver is found.
- the general host's operating system searches for the driver and loads it for a few seconds. Therefore, you can set the timer to a few seconds, for example. : 3 seconds, 4 seconds, etc.;
- the operating system of the host After receiving the device, interface, and endpoint descriptor information reported by the wireless data card, the operating system of the host searches for the driver corresponding to the descriptor information according to the descriptor information, and if the driver corresponding to the descriptor is found, the descriptor is correctly loaded. Corresponding driver, and during the loading process, the MS OS Descriptor request is sent to the wireless data card; if not found, no processing is performed; therefore, the wireless data card can determine whether the host operating system supports the RNDIS device according to the determination ;
- the wireless data card after receiving the MS OS Descriptor request, the wireless data card returns a response to the operating system of the host according to the RNDIS, so that the operating system of the host can complete the loading of the driver according to the returned response, and the wireless data card clears the timer;
- the specific processing procedure for returning the response to the operating system is the same as that of the prior art, and is not described here again; the method may further include:
- the wireless data card After the automatic installation of the wireless data card is implemented by the driver of the operating system of the host, the wireless data card interacts with the operating system of the host to perform RNDIS request and instructions, so that the wireless data card can enter the working state;
- the operating system enumerates the wireless data card to the ECM device, and specifically: the device, the interface, and the descriptor information of the endpoint corresponding to the ECM sub-device are reported to the operating system of the host; wherein, the reporting corresponds to the ECM sub-device
- the wireless data card is currently in the ECM configuration state, that is: the wireless data card is an ECM-enabled device;
- the operating system of the host receives the description of the device, interface, and endpoint reported by the wireless data card. After the information, the driver corresponding to the descriptor information is found to be correctly loaded according to the descriptor information, and then the ECM request and the instruction are interacted with the wireless data card, so that the wireless data card can work in the ECM state; wherein, the operation of the host
- the specific processing procedure of the system and the wireless data card for the ECM request and the instruction interaction is the same as the existing processing process, and is not described here; here, the existing operating system supports the ECM device and the RNDIS device. One or both of them, therefore, the host operating system does not find the corresponding driver according to the device, interface, and endpoint descriptor information corresponding to the ECM sub-device.
- a wireless data card is used as an example.
- the method for enabling the wireless data card in this embodiment, as shown in FIG. 2, includes the following steps:
- Step 200 Configure an ECM sub-device and an RNDIS sub-device in the wireless data card, and then perform step 201;
- the following includes: configuring the device, the interface, the descriptor information of the endpoint, and the driving of the data flow and the control flow according to the ECM;
- the method includes: configuring the device, the interface, the descriptor information of the endpoint, and the driving of the data flow and the control flow according to the RNDIS.
- Step 201 The wireless data card is inserted into the host computer, and after the power is turned on, the timer is started, the operating system of the host machine detects the wireless data card, and then sends a USB descriptor request to the wireless data card.
- Step 202 After receiving the USB descriptor request, the wireless data card reports the device, the interface, and the descriptor information of the endpoint corresponding to the RNDIS sub-device to the operating system of the host.
- the wireless data card is currently in the RNDIS configuration state, that is, the wireless data card is a device supporting the RNDIS;
- the value of the bcdDevice parameter in the descriptor information is greater than zero.
- Step 203 The operating system of the host determines whether the RNDIS device is supported, and if yes, executes Step 204, otherwise, performing step 207;
- the operating system of the host determines whether the RNDIS device is supported, specifically: after receiving the descriptor information, the operating system of the host searches for the corresponding driver according to the descriptor information, and if the corresponding driver is searched, the host is considered The operating system supports the RNDIS device. Otherwise, the host's operating system does not support the RNDIS device and does not perform any operations.
- Step 204 Load the driver corresponding to the descriptor, and send an MS OS Descriptor request to the wireless data card during the loading process.
- Step 205 After receiving the MS OS Descriptor request sent by the operating system of the host, the wireless data card clears the timer and returns a response to the operating system of the host according to the RNDIS.
- Step 206 After receiving the response, the operating system of the host completes the loading of the driver, and then performs an RNDIS request and an instruction interaction with the wireless data card to bring the wireless data card into a working state.
- Step 207 After the timer expires, the bus of the wireless data card is restarted, and then the device, the interface, and the descriptor information of the endpoint corresponding to the ECM sub-device are reported to the operating system of the host; here, after the bus of the wireless data card is restarted In order to put the wireless data card in the ECM state.
- Step 208 After receiving the device, the interface, and the descriptor information of the endpoint reported by the wireless data card, the operating system of the host finds the driver corresponding to the descriptor information according to the descriptor information, and then loads it correctly, and then requests the wireless data card with the ECM. And the interaction of instructions so that the wireless data card can work in the ECM state.
- the present invention further provides an apparatus for enabling a wireless communication terminal.
- the apparatus includes: a configuration unit 31, an enumeration unit 32, a determination unit 33, and an operation system 34;
- the configuration unit 31 is configured to configure the ECM sub-device and the RNDIS sub-device in the wireless communication terminal;
- An enumeration unit 32 configured to insert a wireless communication terminal into the host computer and operate after powering on The system 34 enumerates the wireless communication terminal as the RNDIS device, and then triggers the determining unit 33; and after receiving the notification from the determining unit 33, enumerates the wireless communication terminal as an ECM device to the operating system 34; the determining unit 33 is configured to receive the piece After the trigger information of the unit 32 is determined, it is determined whether the operating system supports the RNDIS device, and after determining that the operating system does not support the RNDIS device, notifying the enumeration unit 32 that the operating system does not support the RNDIS device;
- the operating system 34 is configured to receive the wireless communication terminal enumerated by the enumeration unit 32 as an RNDIS device, and after determining that the RNDIS device is supported by the enumeration unit 32, implement automatic installation of the wireless communication terminal by using its own driver; or, receive the piece After the wireless communication terminal enumerated in the unit 32 is an ECM device, the automatic installation of the wireless communication terminal is realized by its own driver.
- the operating system is an operating system of a computer host into which the wireless communication terminal is inserted.
- the device may further include: an RNDIS sub-device 35, configured to perform an RNDIS request and an instruction interaction with the operating system 34 to enable the wireless communication terminal to enter a working state; and the operating system 34 is further configured to implement the wireless communication terminal.
- the RNDIS sub-device 35 After the automatic installation, the RNDIS sub-device 35 performs RNDIS request and instruction interaction, so that the wireless communication terminal enters the working state.
- the device may further include: an ECM sub-device 36, configured to perform an ECM request and an instruction interaction with the operating system 34 to enable the wireless communication terminal to enter a working state;
- the operating system 34 is further configured to perform an ECM request and an instruction interaction with the ECM sub-device 36 after the automatic installation of the wireless communication terminal, so that the wireless communication terminal enters a working state.
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)
- Mobile Radio Communication Systems (AREA)
Description
一种无线通讯终端的启用方法及装置 技术领域
本发明涉及通讯技术领域, 特别是指一种无线通讯终端的启用方法及 装置。 背景技术
用户在使用基于通用串行总线 ( USB , Universal Serial Bus )接口的无 线通讯终端比如无线数据卡时, 主要是通过两次切换的方式实现无线数据 卡的启用, 具体地, 在首次接入计算机操作系统后, 无线数据卡枚举出一 个虚拟光驱, 该光驱内存储了网络通信端口的驱动、 管理程序、 以及帮助 文件等, 用户运行虚拟光驱, 进行管理程序和驱动的安装, 完成后无线数 据卡才被切换到可工作状态, 即: 带有虚拟调制解调器(Modern ), 网络驱 动接口规范( NDIS , Network Driver Interface Specification )等端口的^ 态, 当用户再次将无线数据卡接入到已安装过驱动、 及管理程序的操作系统后, 操作系统中已安装的过滤驱动或其它方案比如后台服务等会自动将无线数 据卡切换到工作状态。 但是, 该方法只有用户在完成管理程序和驱动的安 装后, 无线数据卡才会被启用, 而安装步骤较为繁瑣, 如此, 会占用用户 的时间, 进而用户降低用户体验, 而且, 由于计算机的操作系统较为复杂, 容易引起驱动异常; 并且, 还需要在无线数据卡的闪存(Flash ) 中存储管 理程序及驱动, 如此, 使得无线数据卡的成本较高。
另外, 目前, 还有基于中间层设备的免驱动方式实现无线数据卡的启 用, 具体地, 无线数据卡枚举出光驱和操作系统自带驱动的一类设备比如 人机接口设备(HID, Human Interface Device ), 或摄像头等的一种组合, 其中, 光驱负责安装管理程序, 操作系统自带驱动的一类设备作为操作系
统与无线数据卡网络数据交换的媒介, 即: 通过将网络数据包封装到 HID 请求、 或摄像头命令请求等中实现网络数据的交互, 进而实现无线数据卡 的免驱上网, 但是, 该方法需要将网络数据包封装到 HID请求、 或摄像头 命令请求等中, 然而具体的封装在实际应用时难于实现, 因此, 该方法存 在技术难度大、 实现难度大等缺点。
除此以外, 为了实现无线数据卡的免驱动启用, 开发人员针对不同的 操作系统, 也提出了相应的解决方案, 举个例子来说, 以太网控制规范 ( ECM, Ethernet Control Model )是 USB 通信设备类( CDC, Communication Devices Class )规范规定的基于 USB的网络接口规范,符合 ECM的无线数 据卡在 Linux操作系统、 及 MAC操作系统上启用时, 会自动安装操作系统 自带的驱动, 不需要安装厂商提供的驱动, 就可以直接进行网络连接和上 网; 同样的, 网络驱动接口规范(RNDIS, Remote Network Driver Interface Specification )是微软提出的基于 USB的网络接口规范, 符合 RNDIS的无 线数据卡在 Windows操作系统上启用时,会自动安装操作系统的 RNDIS驱 动, 不需要安装厂商提供的驱动, 就可以直接进行网络连接和上网。 但是, 这种方法只适用于操作系统所支持的无线数据卡, 而对于操作系统不支持 的无线数据卡, 则仍需安装厂商提供的驱动。 发明内容
有鉴于此, 本发明的主要目的在于提供一种无线通讯终端的启用方法 及装置, 能实现无线通讯终端的免驱动启用。
为达到上述目的, 本发明的技术方案是这样实现的:
本发明提供了一种无线通讯终端的启用方法, 该方法包括:
在无线通讯终端中配置 ECM子设备及 RNDIS子设备;
无线通讯终端插入计算机主机并在上电后, 向主机的操作系统枚举无 线通讯终端为 RNDIS设备, 之后判断所述操作系统是否支持 RNDIS设备,
确定所述操作系统支持 RNDIS设备后, 通过所述操作系统的驱动程序实现 无线通讯终端的自动安装; 确定所述操作系统不支持 RNDIS设备后, 向所 述操作系统枚举无线通讯终端为 ECM设备,通过所述操作系统的驱动程序 实现无线通讯终端的自动安装。
上述方案中, 在配置 RNDIS子设备时, 具体包括: 依据 RNDIS配置 设备、 接口、 端点的描述符信息、 以及数据流、 控制流的驱动;
在配置 ECM子设备时, 具体包括: 依据 ECM配置设备、 接口、 端点 的描述符信息、 以及数据流、 控制流的驱动。
上述方案中,所述向主机的操作系统枚举无线通讯终端为 RNDIS设备, 为:
向所述操作系统上报与 RNDIS子设备对应的设备、 接口、 以及端点的 描述符信息。
上述方案中, 所述判断主机的操作系统是否支持 RNDIS设备, 为: 在规定时长内是否收到所述操作系统下发的 MS OS 描述符 ( Descriptor )请求。
上述方案中,所述向所述操作系统枚举无线通讯终端为 ECM设备,为: 向所述操作系统上报与 ECM子设备对应的设备、接口、 以及端点的描 述符信息。
上述方案中, 该方法进一步包括:
通过所述操作系统的驱动程序实现无线通讯终端的自动安装后, 无线 通讯终端与所述操作系统进行 RNDIS请求及指令的交互, 使无线通讯终端 进入工作状态。
上述方案中, 该方法进一步包括:
通过所述操作系统的驱动程序实现无线通讯终端的自动安装后, 无线 通讯终端与所述操作系统进行 ECM请求及指令的交互 ,使无线通讯终端进
入工作状态。
本发明还提供了一种无线通讯终端的启用装置, 该装置包括: 配置单 元、 枚举单元、 判断单元、 以及操作系统; 其中,
配置单元 ,用于在无线通讯终端中配置 ECM子设备及 RNDIS子设备; 枚举单元, 用于无线通讯终端插入计算机主机并在上电后, 向操作系 统枚举无线通讯终端为 RNDIS设备, 之后触发判断单元; 并在收到判断单 元的通知后, 向操作系统枚举无线通讯终端为 ECM设备;
判断单元, 用于收到枚举单元的触发信息后, 判断操作系统是否支持 RNDIS设备, 并在确定操作系统不支持 RNDIS设备后, 通知枚举单元操作 系统不支持 RNDIS设备;
操作系统, 用于收到枚举单元枚举的无线通讯终端为 RNDIS设备后, 并在确定自身支持 RNDIS设备后, 通过自身的驱动程序实现无线通讯终端 的自动安装; 或者, 收到枚举单元枚举的无线通讯终端为 ECM设备后, 通 过自身的驱动程序实现无线通讯终端的自动安装。
上述方案中, 该装置进一步包括: RNDIS子设备, 用于与操作系统进 行 RNDIS请求、 及指令的交互, 使无线通讯终端进入工作状态;
所述操作系统, 还用于实现无线通讯终端的自动安装后, 与 RNDIS子 设备进行 RNDIS请求、 及指令的交互, 使无线通讯终端进入工作状态。
上述方案中, 该装置进一步包括: ECM子设备, 用于与操作系统进行 ECM请求、 及指令的交互, 使无线通讯终端进入工作状态;
所述操作系统, 还用于实现无线通讯终端的自动安装后, 与 ECM子设 备进行 ECM请求、 及指令的交互, 使无线通讯终端进入工作状态。
本发明提供的无线通讯终端的启用方法及装置, 在无线通讯终端中配 置 ECM子设备及 RNDIS子设备, 无线通讯终端插入计算机主机并在上电 后, 向主机的操作系统枚举无线通讯终端为 RNDIS设备, 之后判断主机的
操作系统是否支持 RNDIS设备, 确定主机的操作系统支持 RNDIS设备后, 通过主机的操作系统的驱动程序实现无线通讯终端的自动安装; 确定主机 的操作系统不支持 RNDIS设备后, 向主机的操作系统枚举无线通讯终端为 ECM设备,通过主机的操作系统的驱动程序实现无线通讯终端的自动安装, 如此, 能实现无线通讯终端的免驱动自动启用, 进而能简化用户的使用过 程, 并节约用户时间, 从而提升用户体验; 并且, 还能适用于不同的操作 系统。
另外, 本发明提供的无线通讯终端的启用方案, 不需要在无线通讯终 端的 Flash中事先存储驱动程序, 如此, 能减少无线通讯终端的 Flash的空 间占用, 进而能降低产品成本。 附图说明
图 1为本发明无线通讯终端的启用方法流程示意图;
图 2为实施例无线数据卡的启用方法流程示意图;
图 3为本发明无线通讯终端的启用装置结构示意图。 具体实施方式
下面结合附图及具体实施例对本发明再作进一步详细的说明。
以无线数据卡为例, 本发明无线通讯终端的启用方法, 如图 1 所示, 包括以下步骤:
步骤 100: 在无线数据卡中配置 ECM子设备及 RNDIS子设备; 这里,配置 ECM子设备是为了使无线数据卡可以支持 Linux操作系统、 及 MAC 操作系统; 配置 RNDIS 子设备是为了使无线数据卡可以支持 Windows操作系统; 其中, ECM子设备与 RNDIS子设备为两个独立的子 设备, 即: 无线数据卡在使用时, ECM子设备与 RNDIS子设备不进行任 何信息的交互;
由于目前的操作系统主要包括: Linux操作系统、 MAC操作系统、 及 Windows操作系统, 因此,可以在无线数据卡中配置 ECM子设备及 RNDIS 子设备, 以使无线数据卡能适用于不同的操作系统;
在配置 ECM子设备时, 具体包括: 依据 ECM配置设备、 接口、 端点 的描述符信息、 以及数据流、 控制流的驱动; 其中, 配置设备、 接口、 端 点的描述符信息是为了使无线数据卡在使用时,成为支持 ECM的无线数据 卡, 即: 支持 Linux操作系统、 及 MAC操作系统的无线数据卡; 配置数据 流、 控制流的驱动, 是为了使无线数据卡在使用时, 可以对数据流及控制 流进行控制; ECM子设备的硬件的配置与现有的无线数据卡的硬件配置相 同;
在配置 RNDIS子设备时, 具体包括: 依据 RNDIS配置设备、 接口、 端点的描述符信息、 以及数据流、 控制流的驱动; 其中, 配置设备、 接口、 端点的描述符信息是为了使无线数据卡在使用时, 成为支持 RNDIS的无线 数据卡, 即: 支持 Windows操作系统; 配置数据流、 控制流的驱动, 是为 了使无线数据卡在使用时, 可以对数据流及控制流进行控制; RNDIS子设 备的硬件的配置与现有的无线数据卡的硬件配置相同。
步骤 101 : 无线数据卡插入计算机主机并在上电后, 向主机的操作系统 枚举无线数据卡为 RNDIS设备,之后判断主机的操作系统是否支持 RNDIS 设备, 确定主机的操作系统支持 RNDIS设备后, 通过主机的操作系统的驱 动程序实现无线数据卡的自动安装; 确定主机的操作系统不支持 RNDIS设 备后, 向主机的操作系统枚举无线数据卡为 ECM设备, 通过主机的操作系 统的驱动程序实现无线数据卡的自动安装;
这里,所述向主机的操作系统枚举无线数据卡为 RNDIS设备的时机为: 无线数据卡收到主机的操作系统下发的 USB描述符请求; 其中, 在无线数 据卡上电后, 主机的操作系统会检测到无线数据卡, 并在检测到无线数据
卡后, 向无线数据卡下发 USB描述符请求; 主机的操作系统检测到无线数 据卡的具体处理流程与现有技术的处理流程完全相同, 这里不再赘述; 向主机的操作系统枚举无线数据卡为 RNDIS设备, 具体为:
向主机的操作系统上报与 RNDIS子设备对应的设备、 接口、 以及端点 的描述符信息; 其中, 在描述符信息中, 设置 bcdDevice参数的值大于零, 如此, 主机的操作系统才会在加载驱动程序的过程中, 向无线数据卡下发 MS OS Descriptor请求; 上报与 RNDIS子设备对应的设备、 接口、 以及端 点的描述符信息后, 表明无线数据卡目前处于 RNDIS配置状态, 即: 无线 数据卡为支持 RNDIS的设备;
所述判断主机的操作系统是否支持 RNDIS设备, 具体为:
在规定时长内是否收到主机的操作系统下发的 MS OS Descriptor请求; 如果在规定时长内收到主机的操作系统下发的 MS OS Descriptor请求, 则 认为主机的操作系统支持 RNDIS设备, 如果在规定时长内, 未收到主机的 操作系统下发的 MS OS Descriptor描述符请求, 则认为主机的操作系统不 支持 RNDIS设备;
在实际应用过程中, 可以在无线数据卡向主机的操作系统上报与 RNDIS子设备对应的设备、接口、 端点的描述符信息的同时, 启动定时器, 或者, 可以在无线数据卡上电后, 就启动定时器; 在实际应用时, 由于主 机的操作系统检测到无线数据卡并向无线数据卡下发 USB描述符请求的时 间非常短, 因此, 为了方便操作, 可以在无线数据卡上电后就启动定时器; 在定时器的时长内, 如果收到了主机的操作系统下发的 MS OS Descriptor 请求, 则认为主机的操作系统支持 RNDIS设备, 定时器超时后, 如果未收 到主机的操作系统下发的 MS OS Descriptor请求, 则认为主机的操作系统 不支持 RNDIS设备;
其中, 可以依据主机的操作系统在根据上报的描述符信息搜索相应的
驱动程序、 以及在找到驱动程序后正确加载的时长设置定时器的时长, 一 般主机的操作系统搜索驱动程序并正确加载的时长为几秒钟, 因此, 可以 设置定时器的时长为几秒, 比如: 3秒、 4秒等等;
主机的操作系统收到无线数据卡上报的设备、 接口、 以及端点的描述 符信息后, 依据描述符信息搜索描述符信息对应的驱动程序, 如果找到描 述符对应的驱动程序, 则正确加载描述符对应的驱动程序, 并在加载过程 中, 会向无线数据卡下发 MS OS Descriptor请求; 如果没有找到, 则不进 行任何处理; 因此, 无线数据卡可以据此确定主机的操作系统是否支持 RNDIS设备;
相应的, 无线数据卡收到 MS OS Descriptor请求后, 会依据 RNDIS向 主机的操作系统返回响应, 以便主机的操作系统能根据返回的响应完成驱 动程序的加载, 同时无线数据卡清除定时器; 其中, 向操作系统返回响应 的具体处理过程与现有技术的具体处理过程完全相同, 这里不再赘述; 该方法还可以进一步包括:
通过主机的操作系统的驱动程序实现无线数据卡的自动安装后, 无线 数据卡与主机的操作系统进行 RNDIS请求、 及指令的交互, 以便无线数据 卡可以进入工作状态;
无线数据卡与主机的操作系统进行 RNDIS请求、 及指令的交互的具体 处理过程与现有的处理过程完全相同, 这里不再赘述;
所述向主机的操作系统枚举无线数据卡为 ECM设备, 具体为: 向主机的操作系统上报与 ECM子设备对应的设备、接口、 以及端点的 描述符信息; 其中, 上报与 ECM子设备对应的设备、 接口、 以及端点的描 述符信息后, 表明无线数据卡目前处于 ECM配置状态, 即: 无线数据卡为 支持 ECM的设备;
主机的操作系统收到无线数据卡上报的设备、 接口、 以及端点的描述
符信息后, 依据描述符信息找到描述符信息对应的驱动程序后正确加载, 之后与无线数据卡进行 ECM请求、 及指令的交互, 以便无线数据卡能在 ECM状态下工作; 其中, 主机的操作系统与无线数据卡进行 ECM请求、 及指令的交互的具体处理过程与现有的处理过程完全相同, 这里不再赘述; 这里, 由于现有的操作系统会支持 ECM设备和 RNDIS设备两种设备 中的一种或两种, 因此, 不会出现主机的操作系统依据 ECM子设备对应的 设备、 接口、 以及端点的描述符信息未能找到对应的驱动程序的情况。
下面结合实施例对本发明再作进一步详细的描述。
本实施例以无线数据卡为例, 本实施例无线数据卡的启用方法, 如图 2 所示, 包括以下步骤:
步骤 200: 在无线数据卡中配置 ECM子设备及 RNDIS子设备, 之后 执行步骤 201 ;
这里, 在配置 ECM子设备时, 具体包括: 依据 ECM配置设备、 接口、 端点的描述符信息、 以及数据流、 控制流的驱动;
在配置 RNDIS子设备时, 具体包括: 依据 RNDIS配置设备、 接口、 端点的描述符信息、 以及数据流、 控制流的驱动。
步骤 201 : 无线数据卡插入计算机主机, 并在上电后, 启动定时器, 主 机的操作系统检测到无线数据卡,之后向无线数据卡下发 USB描述符请求。
步骤 202: 无线数据卡收到 USB描述符请求后, 向主机的操作系统上 报与 RNDIS子设备对应的设备、 接口、 以及端点的描述符信息;
这里, 上报与 RNDIS子设备对应的设备、 接口、 以及端点的描述符信 息后, 表明无线数据卡目前处于 RNDIS配置状态, 即: 无线数据卡为支持 RNDIS的设备;
所述描述符信息中的 bcdDevice参数的值大于零。
步骤 203 : 主机的操作系统判断是否支持 RNDIS设备, 如果是, 则执
行步骤 204, 否则, 执行步骤 207;
这里, 所述主机的操作系统判断是否支持 RNDIS设备, 具体为: 主机的操作系统收到描述符信息后, 依据描述符信息搜索对应的驱动 程序, 如果搜索到对应的驱动程序, 则认为主机的操作系统支持 RNDIS设 备, 否则, 认为主机的操作系统不支持 RNDIS设备, 不进行任何操作。
步骤 204: 加载描述符对应的驱动程序, 并在加载过程中向无线数据卡 下发 MS OS Descriptor请求。
步骤 205: 无线数据卡收到主机的操作系统下发的 MS OS Descriptor 请求后, 清除定时器, 并依据 RNDIS向主机的操作系统返回响应。
步骤 206: 主机的操作系统收到响应后, 完成驱动程序的加载, 之后与 无线数据卡进行 RNDIS请求、及指令的交互,使无线数据卡进入工作状态。
步骤 207: 定时器超时后, 无线数据卡的总线重新启动, 之后向主机的 操作系统上报与 ECM子设备对应的设备、 接口、 以及端点的描述符信息; 这里, 无线数据卡的总线重新启动后, 才能使无线数据卡处于 ECM状 态。
步骤 208: 主机的操作系统收到无线数据卡上报的设备、接口、 以及端 点的描述符信息后, 依据描述符信息找到描述符信息对应的驱动程序后正 确加载, 之后与无线数据卡 ECM请求、 及指令的交互, 以便无线数据卡能 在 ECM状态下工作。
为实现上述方法, 本发明还提供了一种无线通讯终端的启用装置, 如 图 3所示, 该装置包括: 配置单元 31、 枚举单元 32、 判断单元 33、 以及操 作系统 34; 其中,
配置单元 31 , 用于在无线通讯终端中配置 ECM子设备及 RNDIS子设 备;
枚举单元 32, 用于无线通讯终端插入计算机主机并在上电后, 向操作
系统 34枚举无线通讯终端为 RNDIS设备, 之后触发判断单元 33; 并在收 到判断单元 33的通知后, 向操作系统 34枚举无线通讯终端为 ECM设备; 判断单元 33 , 用于收到枚举单元 32的触发信息后, 判断操作系统是否 支持 RNDIS设备, 并在确定操作系统不支持 RNDIS设备后, 通知枚举单 元 32操作系统不支持 RNDIS设备;
操作系统 34 , 用于收到枚举单元 32枚举的无线通讯终端为 RNDIS设 备后, 并在确定自身支持 RNDIS设备后, 通过自身的驱动程序实现无线通 讯终端的自动安装; 或者, 收到枚举单元 32枚举的无线通讯终端为 ECM 设备后, 通过自身的驱动程序实现无线通讯终端的自动安装。
这里, 需要说明的是: 操作系统为无线通讯终端插入的计算机主机的 操作系统。
其中, 该装置还可以进一步包括: RNDIS子设备 35 , 用于与操作系统 34进行 RNDIS请求、 及指令的交互, 使无线通讯终端进入工作状态; 所述操作系统 34, 还用于实现无线通讯终端的自动安装后, 与 RNDIS 子设备 35进行 RNDIS请求、 及指令的交互, 使无线通讯终端进入工作状 态。
该装置还可以进一步包括: ECM子设备 36, 用于与操作系统 34进行 ECM请求、 及指令的交互, 使无线通讯终端进入工作状态;
所述操作系统 34,还用于实现无线通讯终端的自动安装后,与 ECM子 设备 36进行 ECM请求、 及指令的交互, 使无线通讯终端进入工作状态。
这里, 本发明的所述装置中的枚举单元、 判断单元的具体处理过程已 在上文中详述, 不再赘述。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围。
Claims
1、 一种无线通讯终端的启用方法, 其特征在于, 该方法包括: 在无线通讯终端中配置以太网控制规范 (ECM )子设备及网络驱动接 口规范 (RNDIS )子设备;
无线通讯终端插入计算机主机并在上电后, 向主机的操作系统枚举无 线通讯终端为 RNDIS设备, 之后判断所述操作系统是否支持 RNDIS设备, 确定所述操作系统支持 RNDIS设备后, 通过所述操作系统的驱动程序实现 无线通讯终端的自动安装; 确定所述操作系统不支持 RNDIS设备后, 向所 述操作系统枚举无线通讯终端为 ECM设备,通过所述操作系统的驱动程序 实现无线通讯终端的自动安装。
2、 根据权利要求 1所述的方法, 其特征在于,
在配置 RNDIS子设备时, 具体包括: 依据 RNDIS配置设备、 接口、 端点的描述符信息、 以及数据流、 控制流的驱动;
在配置 ECM子设备时, 具体包括: 依据 ECM配置设备、 接口、 端点 的描述符信息、 以及数据流、 控制流的驱动。
3、 根据权利要求 2所述的方法, 其特征在于, 所述向主机的操作系统 枚举无线通讯终端为 RNDIS设备, 为:
向所述操作系统上报与 RNDIS子设备对应的设备、 接口、 以及端点的 描述符信息。
4、 根据权利要求 1、 2或 3所述的方法, 其特征在于, 所述判断主机 的操作系统是否支持 RNDIS设备, 为:
在规定时长内是否收到所述操作系统下发的 MS OS 描述符 ( Descriptor )请求。
5、 根据权利要求 2所述的方法, 其特征在于, 所述向所述操作系统枚 举无线通讯终端为 ECM设备, 为: 向所述操作系统上报与 ECM子设备对应的设备、接口、 以及端点的描 述符信息。
6、 根据权利要求 1、 2或 3的方法, 其特征在于, 该方法进一步包括: 通过所述操作系统的驱动程序实现无线通讯终端的自动安装后, 无线 通讯终端与所述操作系统进行 RNDIS请求及指令的交互, 使无线通讯终端 进入工作状态。
7、 根据权利要求 1、 2、 3或 5的方法, 其特征在于, 该方法进一步包 括:
通过所述操作系统的驱动程序实现无线通讯终端的自动安装后, 无线 通讯终端与所述操作系统进行 ECM请求及指令的交互 ,使无线通讯终端进 入工作状态。
8、 一种无线通讯终端的启用装置, 其特征在于, 该装置包括: 配置单 元、 枚举单元、 判断单元、 以及操作系统; 其中,
配置单元 ,用于在无线通讯终端中配置 ECM子设备及 RNDIS子设备; 枚举单元, 用于无线通讯终端插入计算机主机并在上电后, 向操作系 统枚举无线通讯终端为 RNDIS设备, 之后触发判断单元; 并在收到判断单 元的通知后, 向操作系统枚举无线通讯终端为 ECM设备;
判断单元, 用于收到枚举单元的触发信息后, 判断操作系统是否支持 RNDIS设备, 并在确定操作系统不支持 RNDIS设备后, 通知枚举单元操作 系统不支持 RNDIS设备;
操作系统, 用于收到枚举单元枚举的无线通讯终端为 RNDIS设备后, 并在确定自身支持 RNDIS设备后, 通过自身的驱动程序实现无线通讯终端 的自动安装; 或者, 收到枚举单元枚举的无线通讯终端为 ECM设备后, 通 过自身的驱动程序实现无线通讯终端的自动安装。
9、根据权利要求 8所述的装置,其特征在于,该装置进一步包括: RNDIS 子设备, 用于与操作系统进行 RNDIS请求、 及指令的交互, 使无线通讯终 端进入工作状态;
所述操作系统, 还用于实现无线通讯终端的自动安装后, 与 RNDIS子 设备进行 RNDIS请求、 及指令的交互, 使无线通讯终端进入工作状态。
10、 根据权利要求 8或 9所述的装置, 其特征在于, 该装置进一步包 括: ECM子设备, 用于与操作系统进行 ECM请求、 及指令的交互, 使无 线通讯终端进入工作状态;
所述操作系统, 还用于实现无线通讯终端的自动安装后, 与 ECM子设 备进行 ECM请求、 及指令的交互, 使无线通讯终端进入工作状态。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2011100333059A CN102156648A (zh) | 2011-01-30 | 2011-01-30 | 一种无线通讯终端的启用方法及装置 |
CN201110033305.9 | 2011-01-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012100518A1 true WO2012100518A1 (zh) | 2012-08-02 |
Family
ID=44438156
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/077695 WO2012100518A1 (zh) | 2011-01-30 | 2011-07-27 | 一种无线通讯终端的启用方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102156648A (zh) |
WO (1) | WO2012100518A1 (zh) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103312569B (zh) * | 2012-03-09 | 2017-03-08 | 华为终端有限公司 | 网络连接的方法及装置 |
CN103379006B (zh) * | 2012-04-19 | 2016-08-03 | 中兴通讯股份有限公司 | 数据卡自适应方法及装置 |
CN102693142A (zh) * | 2012-05-10 | 2012-09-26 | 中兴通讯股份有限公司南京分公司 | 网络适配方法及装置 |
CN102841801B (zh) * | 2012-07-11 | 2017-12-12 | 中兴通讯股份有限公司 | 免驱终端的固件升级方法和装置 |
CN104216728A (zh) * | 2013-06-03 | 2014-12-17 | 中兴通讯股份有限公司 | 一种接入usb网卡的方法、usb网卡及pc |
CN105487879B (zh) * | 2014-09-18 | 2019-04-16 | 中兴通讯股份有限公司 | 联网软件集成方法及装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040203296A1 (en) * | 2002-11-15 | 2004-10-14 | Globespan Virata Inc. | Method and system for attaching a USB network adapter supporting both RNDIS and non-RNDIS capable operating systems |
CN101478597A (zh) * | 2009-01-13 | 2009-07-08 | 深圳市同洲电子股份有限公司 | 一种连接切换的方法、系统及移动终端 |
CN102096646A (zh) * | 2011-01-30 | 2011-06-15 | 中兴通讯股份有限公司 | 一种无线通讯终端的启用方法及装置 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1456976A (zh) * | 2003-06-04 | 2003-11-19 | 无敌科技(西安)有限公司 | Usb接口设备的驱动程序安装方法 |
US7447196B2 (en) * | 2005-10-25 | 2008-11-04 | Kinghood Technology Co., Ltd. | Wireless networking communication system and communicating method for VOIP |
CN101868050B (zh) * | 2010-06-22 | 2014-12-10 | 中兴通讯股份有限公司 | 一种数据卡及其上网方法 |
-
2011
- 2011-01-30 CN CN2011100333059A patent/CN102156648A/zh active Pending
- 2011-07-27 WO PCT/CN2011/077695 patent/WO2012100518A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040203296A1 (en) * | 2002-11-15 | 2004-10-14 | Globespan Virata Inc. | Method and system for attaching a USB network adapter supporting both RNDIS and non-RNDIS capable operating systems |
CN101478597A (zh) * | 2009-01-13 | 2009-07-08 | 深圳市同洲电子股份有限公司 | 一种连接切换的方法、系统及移动终端 |
CN102096646A (zh) * | 2011-01-30 | 2011-06-15 | 中兴通讯股份有限公司 | 一种无线通讯终端的启用方法及装置 |
Also Published As
Publication number | Publication date |
---|---|
CN102156648A (zh) | 2011-08-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012100515A1 (zh) | 一种无线通讯终端的启用方法及装置 | |
TWI477970B (zh) | 電子裝置的模式切換方法與相關的電子裝置 | |
WO2012100518A1 (zh) | 一种无线通讯终端的启用方法及装置 | |
TWI610167B (zh) | 改善平台管理的計算裝置建置方法、保持電腦可執行指令之非暫存媒體及配置為提供強化管理資訊之計算裝置 | |
WO2015074232A1 (zh) | 一种内存数据的迁移方法、计算机和装置 | |
WO2012109886A1 (zh) | 通过usb虚拟网卡接入无线网络的方法、系统及装置 | |
WO2014026547A1 (zh) | 一种有源usb设备及其工作模式的切换方法 | |
JP6387581B2 (ja) | データスイッチにて学習するサーバデータポート | |
CN102880527B (zh) | 一种基板管理控制器的数据恢复方法 | |
WO2015176408A1 (zh) | 中断处理方法及中断控制器 | |
US10564707B2 (en) | System management controller | |
US9092334B2 (en) | Method for shortening enumeration of tightly coupled USB device | |
CN102622313A (zh) | Usb设备的端口切换方法、系统和区分操作系统的方法 | |
WO2010006529A1 (zh) | 数据卡的操作模式切换及其控制方法、装置及数据卡 | |
WO2012100504A1 (zh) | 一种无线通讯方法、系统及无线通讯终端 | |
US8990468B2 (en) | I/O connection system, method and program | |
JP2013513874A (ja) | データカードのアップグレーディング方法およびデバイス | |
JP2012150797A (ja) | データカード、データカードがポートを報告するための方法、およびデータカードを起動するための方法 | |
WO2011147113A1 (zh) | 多媒体广播芯片断电方法、装置及数据卡 | |
CN103631476B (zh) | 电子装置的模式切换方法与相关的电子装置 | |
WO2017075997A1 (zh) | 安卓调试桥的启动方法、装置及终端 | |
WO2015127893A1 (zh) | 能力确定方法、能力配置方法、主机、终端设备及系统 | |
CN112925730B (zh) | 一种PCIe设备链路训练控制方法及系统 | |
TWI282683B (en) | Automatic configuration method and system | |
WO2015109785A1 (zh) | 一种网卡设备及其实现方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11856809 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11856809 Country of ref document: EP Kind code of ref document: A1 |