WO2012151998A1

WO2012151998A1 - Data processing method and drive apparatus for mobile broadband device

Info

Publication number: WO2012151998A1
Application number: PCT/CN2011/084135
Authority: WO
Inventors: 李焰峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-08-17
Filing date: 2011-12-16
Publication date: 2012-11-15
Also published as: CN102323892B; CN102323892A

Abstract

Disclosed are a data processing method and drive apparatus for a mobile broadband device. The method includes the steps of: receiving a function call request from an Android system at a radio interface layer (RIL) (S202a); and in the situation where the function call request is a data service and configuration service, using a QMI daemon to encapsulate the function call request as a corresponding QMI instruction via a Qualcomm MSM Interface (QMI) protocol interface registered in the RIL library, and sending the encapsulated QMI instruction data to a network driver interface specification (NDIS) device (S204a). The present solution extends the application scope of the Android system and improves the system performance.

Description

The present invention relates to the field of wireless communications, and in particular, to a data processing method and a driving apparatus for a mobile broadband device. BACKGROUND With the evolution of technology and the popularization of mobile broadband, the mobile Internet has provided people with rich services such as home entertainment and business office; based on The Third Generation Mobile Communications (3G) With the expansion of The Fourth Generation Mobile Communications (4G), more and more Internet applications have been developed, making the pursuit of mobile broadband speed one of the main goals. Based on the global wireless chip format, Qualcomm and Microsoft's Network Driver Interface Specification (NDIS) + QMI (Qualcomm MSM Interface) mobile broadband device high-speed access solution has become the mainstream access for mobile broadband devices. One way, but limited to the "DIS+QMI" method, is currently only applied on the Windows system. Therefore, how to extend this access method to more operating systems has become one of the current efforts. With the popularity of embedded smart devices, handheld smart terminals, and especially personal digital assistants (PDAs), Android (Android, also known as Anzhi) mobile operating system is extremely popular with its open and open source features. The earth welcomes and supports. According to the latest market statistics, the Android system is already the mobile operating system with the highest market share. Therefore, adapting various mobile broadband devices on the Android system has become one of the main tasks at present. However, it is limited to the existing features of the Android system, and only supports the networking methods such as Point to Point Protocol (PPP), which cannot support the more popular and faster NDIS devices. Although there are DIS-based business processing methods on Windows systems, NDIS itself is a set of Windows-defined specifications that are difficult to copy or port to the Android operating system. Therefore, how to use the existing software and features on the Android system. It is the biggest goal to develop a driver and software system similar to the DIS solution on Windows systems. FIG. 1 is a schematic diagram of a driving system of a mobile broadband device of an Android system according to the related art. As shown in FIG. 1 , in order to implement data networking services, the Android system adopts a traditional dial-up connection method-PPP. However, this method increases the level of software and the difficulty of software development, and reduces the robustness of the software. Moreover, the use of a relatively low-level PPP protocol for data transmission increases the length of the data frame, so that the payload of the transmitted data content The reduction, thereby reducing the transmission speed between the mobile broadband device and the host controller, limits the network performance of the mobile broadband device. SUMMARY OF THE INVENTION A main object of the present invention is to provide a data processing solution for a mobile broadband device, so as to at least solve the problem that the PPP protocol is used in the related art, resulting in poor software robustness and low transmission speed. In order to achieve the above object, according to an aspect of the present invention, a downlink data processing method of a mobile broadband device is provided. A downlink data processing method for a mobile broadband device according to the present invention includes the steps of: receiving a function call request from an Android system of an RIL layer; and registering into a RIL library by a function call request for a data service and a configuration service The QMI protocol interface uses the QMI daemon to encapsulate the function call request into the corresponding QMI instruction, and sends the encapsulated QMI instruction data to the DIS device. Preferably, the QMI instruction comprises one of the following: WDS, CTL, DMS. Preferably, sending the encapsulated QMI instruction data to the DIS device comprises: the QMI daemon sending the encapsulated QMI instruction data to the DIS device through an asynchronous mechanism. In order to achieve the above object, according to another aspect of the present invention, an uplink data processing method of a mobile broadband device is also provided. The uplink data processing method of the mobile broadband device according to the present invention includes the following steps: the QMI daemon detects the status data from the DIS device; parses the message type according to the status data, and reports the analysis result to the RIL module of the Android system, where The status data includes at least one of the following: switching data of the status, conversion data of the status, and hot plug event message. In order to achieve the above object, according to still another aspect of the present invention, a data processing method of a mobile broadband device is also provided. A data processing method for a mobile broadband device according to the present invention includes the above-described downlink data processing method and the above-described uplink data processing method. Preferably, the method further comprises: starting the QMI daemon during initialization of the Android system. In order to achieve the above object, according to still another aspect of the present invention, a driving device for a mobile broadband device is also provided. A driving device for a mobile broadband device according to the present invention, comprising a RIL module, the driving device further comprising a QMI module and an NDIS driving module connected to the NDIS device, wherein the RIL module is set to receive the function of the Android system from the RIL layer In the case of calling the data service and configuring the service, the function call request is sent to the QMI module through the QMI protocol interface registered in the RIL library; the QMI module is set to receive the function request from the RIL module, and the function is used by the QMI daemon. The call request is encapsulated into a corresponding QMI instruction, and the encapsulated QMI data is sent to the DIS drive module. Preferably, the QMI module comprises: a QMI client, configured to provide an interface and encapsulation of the RIL layer, such that the RIL layer invokes a QMI daemon when processing data traffic and configuring traffic; a QMI daemon unit, configured to receive from the QMI client The function calls the request and encapsulates the function call request into a corresponding QMI instruction, wherein the QMI instruction includes one of the following: WDS, CTL, DMS. Preferably, the QMI daemon process unit is further configured to detect the status data of the DIS device from the DIS drive module, parse the message type according to the detected status data, and report the analysis result to the RIL module, wherein the status data includes at least the following One: status switching data, status conversion data, hot plug event messages. Preferably, the NDIS driver module is configured to register a hook function in the USB CDC-ECM driver in the Android system to implement the USB CDC-ECM driver to analyze the control data, wherein the hook function implements the QMI data in the QMI daemon. Send and parse. Through the invention, the "NDIS+QMI" protocol is adopted to solve the problem that the PPP protocol in the related art leads to poor software robustness and low transmission speed, expands the application range of the Android system, and improves the performance of the system. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic diagram of a driving system of a mobile broadband device of an Android system according to the related art; FIG. 2a is a flowchart of a downlink data processing method of a mobile broadband device according to an embodiment of the present invention; FIG. 2b is an implementation according to the present invention; FIG. 3 is a structural block diagram of a driving apparatus of a mobile broadband device according to an embodiment of the present invention; FIG. 4 is a structural block diagram of a driving apparatus of a mobile broadband device according to a preferred embodiment of the present invention; FIG. 5 is a schematic diagram of a driving apparatus of a mobile broadband device of an Android system according to a first embodiment of the present invention; FIG. 6 is a third embodiment of the present invention. Schematic diagram of the downlink data stream; FIG. 7 is a schematic diagram of an uplink data stream according to Embodiment 4 of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. According to an embodiment of the present invention, a downlink data processing method of a mobile broadband device is provided. 2a is a flowchart of a method for processing downlink data of a mobile broadband device according to an embodiment of the present invention. As shown in FIG. 2a, the method includes the following steps: Step S202a, receiving a radio interface layer (Radio Interface Layer, RIL for short) The function call request of the Android system; step S204a, in the case that the function call request is a data service and a configuration service, the function call request is encapsulated into a corresponding one by using a QMI daemon (Daemon) registered to the QMI protocol interface in the RIL library. The QMI instruction sends the encapsulated QMI command data to the DIS device. Through the above steps, the "DIS+QMI" protocol is adopted to solve the problem that the PPP protocol in the related technology leads to poor software robustness and low transmission speed, which expands the application range of the Android system and improves the performance of the system. Preferably, the QMI instruction includes one of the following: WDS (QMI Wireless Data Service) CTL (QMI Control Service) DMS (QMI Device Management Service). The method is simple and practical, and has high operability. Preferably, the sending the encapsulated QMI command data to the DIS device comprises: the QMI Daemon transmitting the encapsulated QMI command data to the DIS device through an asynchronous mechanism. The method is simple to implement and has high operability. According to an embodiment of the present invention, an uplink data processing method of a mobile broadband device is provided. 2b is a flowchart of an uplink data processing method of a mobile broadband device according to an embodiment of the present invention. As shown in FIG. 2b, the method includes the following steps: Step S202b, the QMI Daemon detects the status data from the DIS device; Step S204b, parses the message type according to the status data, and reports the analysis result to the RIL module of the Android system, where the status data includes at least one of the following: Switch data, status conversion data, hot plug event messages. Through the above steps, the "DIS+QMI" protocol is adopted to solve the problem that the PPP protocol in the related technology leads to poor software robustness and low transmission speed, which expands the application range of the Android system and improves the performance of the system. According to an embodiment of the present invention, a data processing method for a mobile broadband device is further provided, including the foregoing downlink data processing method and the uplink data processing method. Preferably, the above method further comprises: starting the QMI Daemon when the Android system is initialized. This method can improve the effectiveness of the system. Corresponding to the above method, an embodiment of the present invention further provides a driving device for a mobile broadband device. 3 is a structural block diagram of a driving device of a mobile broadband device according to an embodiment of the present invention. As shown in FIG. 3, the driving device includes a RIL module 32, and the driving device further includes a QMI module 34 and a DIS driver connected to the DIS device. The module 36, wherein the RIL module 32 is configured to send the function call request by registering to the QMI protocol interface in the RIL library if the function call request of the Android system from the RIL layer is received as a data service and a configuration service. The QMI module 34; the QMI module 34, coupled to the RIL module 32, is configured to receive a function request from the RIL module 32, to package the function call request into a corresponding QMI instruction using the QMI daemon (Daemon), and to encapsulate the QMI. The data is sent to the DIS drive module 36. Through the above-mentioned driving device, the "DIS+QMI" protocol is adopted to solve the problem that the PPP protocol in the related art leads to poor software robustness and low transmission speed, which expands the application range of the Android system and improves the performance of the system. 4 is a structural block diagram of a driving apparatus of a mobile broadband device according to a preferred embodiment of the present invention. As shown in FIG. 4, the QMI module 34 includes: a QMI client 342 configured to provide an interface and encapsulation of the RIL layer, such that the RIL layer The QMI Daemon is invoked when processing the data service and configuring the service; the QMI Daemon unit 344, coupled to the QMI client 342, is configured to receive the function call request from the QMI client 342 and package the function call request into a corresponding QMI command, wherein The QMI instruction includes one of the following: WDS, CTL, DMS. Preferably, the QMI Daemon unit 344 is further configured to receive a response corresponding to the function call request from the DIS device, parse the command field in the response, and report the response to the RIL module using the corresponding QMI instruction according to the command field. Preferably, the QMI Daemon unit 344 is further configured to detect the status data of the DIS device from the DIS drive module 36, parse the message type according to the detected status data, and report the analysis result to the RIL module 32, wherein the status data includes At least one of the following: status switching data, status conversion data, hot plug event messages. Preferably, the NDIS driver module 36 is configured as a Universal Serial Bus (USB) in the Android system. The Class Definitions for Communication Devices-Ethernet Control Model (CDC-ECM) The driver registers the hook function to implement the USB CDC-ECM driver to parse the control data. The hook function implements the sending and parsing of the QMI data in the QMI Daemon. The implementation process of the above embodiment will be described in detail below in conjunction with the preferred embodiments and the accompanying drawings. Embodiment 1 In order to adapt to the driving and data access of a high-speed mobile broadband device, the present embodiment provides a general mobile broadband device driving method and device on the Android system, which can improve the communication speed between the mobile broadband device and the device driver. It is compatible with the NDIS solution on the existing board side, which reduces the difficulty and workload of board side development, thus reducing development costs. The Android system-based driving method and system in this embodiment is a new optimized and normalized driving method and device. FIG. 5 is a schematic diagram of a driving device of a mobile broadband device of an Android system according to Embodiment 1 of the present invention. As shown in FIG. 5, the PPP module 12 in FIG. 1 is deleted, and the Modem port and the PPP protocol are discarded, and the performance is better. The NDIS port and the QMI protocol process the requests of the upper management software separately according to different service types. Specifically, the processing of the upper management software according to different service types may be: for the SMS, the phone book, and the like, still according to the existing Radio Interface Layer (RIL) mechanism of the Android system, through the AT (attention) The way of the command is implemented; for services such as data and configuration, it is implemented by the QMI protocol. In order to achieve compatibility with the existing methods, the functional interfaces of data and configuration services implemented through the QMI protocol are also registered in the RIL library, so that the upper layer management software does not care that the underlying implementation is PPP protocol on the RIL layer. The mode is also the way of the QMI protocol, so that transparent transmission is realized between the upper management software and the device. In order to achieve such a function, the PPP module 12 is deleted, the AT module 51 is modified, the DIS drive module 52 is added, QMI Client module 54, QMI Daemon module 53, wherein the NDIS driver module 52 is modified based on the USB CDC-ECM driver of the Android system, and the QMI Client module 54 (ie, the QMI client) and the QMI Daemon module 53 are new. Add a module. In the implementation process, for the request from the RIL layer, if it is a service such as data and configuration, it is implemented by calling the interface of the QMI Client module 54; the QMI Client module 54 notifies the QMI Daemon module 53 through the message mechanism, specifically The encapsulation, parsing, data transmission, and reception of the QMI protocol are implemented by the QMI Daemon module 53; the driving of the NDIS device is implemented by the DIS driver module 52. The QMI Daemon module 53 acts as a daemon, which is started when the Android system is initialized, asynchronously processes requests from the upper layer and response events from the device; when processing the request, the QMI Daemon module 53 After processing the encapsulation of the QMI protocol data, directly calling the driver interface to send data; for the response event, a separate process is used to detect the event from the device, so that the data can be sent and received asynchronously, and Can handle response events in a timely manner. In this embodiment, in the driver of the USB CDC-ECM (Class Definitions for Communication Devices-Ethernet Control Model) of the existing Android system, ± has been supported by the QMI protocol, and the existing wireless broadband service processing with the Android system is realized. - The seamless interface between the Radio Interface Layer (RIL) drives, so that seamless access to existing DIS devices can be achieved, and the access speed of mobile broadband devices can be improved, and can be modified less. Android system framework. In addition, the data service access mode of the Android system is extended to enable access to the mainstream NDIS device, and the current access speed of the wireless broadband device is becoming higher and higher, and the existing data service access mode of the Android system is expanded. So that the Android system can better adapt to the current development trend. Embodiment 2 This embodiment provides a device driving method and system generally used in an Android system. When implementing, the dialing mode using Modem+PPP protocol is discarded, and the mode of "NDIS+QMI" protocol is adopted; Modify the existing USB CDC-ECM driver on the Android system, so that the Android system can support the NDIS device; and support on the existing RIL driver, increase the support of the QMI protocol, so that data, configuration, SMS, phone book and other services can be Different protocols (AT, QMI) are used depending on the type of service. Among them, the QMI protocol can adopt the asynchronous mode; in the implementation mode, the QMI protocol can be integrated into the existing RIL framework of the Android system, and the architecture of the Android system RIL and Framework is not modified, so that the Android system can be added. Scalability. The optimized system block diagram is shown in Figure 5. The optimization module involves: AT module 51, NDIS driver module 52,

The QMI Daemon module 53, the QMI Client module 54, and the PPP module 12 will be described in detail below. (AT module 51: The AT module is the basic component of the RIL framework of the Android system. It is responsible for many services such as existing data, SMS, phone book, configuration, and telephone, especially data services. It is based on AT commands and PPP protocol dialing. It is unable to support technology update, faster and more popular DIS devices. In this system, the data service part adopts the DIS method. First, the implementation and interface of the data and configuration services in the AT module must be modified, and the corresponding AT is deleted. Commands and interfaces, instead of calling the QMI Client module to provide the Application Programming Interface (API); SMS, phonebook and other services continue to use the existing AT module. Based on the above ideas, the modification in the AT module In the middle, it is necessary to select different implementations of a data and configuration service to invoke the API implementation of the QMI Client module according to different services.

(2) NDIS driver module 52: Used to drive the DIS device so that the DIS device can communicate normally on the Android system. Implementation, can be based on the existing USB CDC-ECM driver for Android, on USB

The hook function is registered in the CDC-ECM driver, and the USB CDC-ECM driver control data is parsed in the hook function. The hook function implements the processing of sending and parsing the QMI data in the QMI Daemon module.

(3) QMI Daemon module 53: Responsible for three types of service processing: First, receiving requests from the QMI Client, and encapsulating these requests into corresponding QMI instructions, for example, WDS (QMI Wireless Data Service) CTL (QMI Control) Service) DMS (QMI Device Management Service), etc., and send these requests through the asynchronous mechanism; the second is to process the response corresponding to the request, parse and feedback the result to the upper RIL framework, so that the RIL provides a unified interface form; The third is responsible for detecting and monitoring the status of the NDIS device and hot swapping, and real-time processing of device status switching and conversion. Specifically, for the request from the QMI client, according to the corresponding QMI protocol subclass, the respective protocol encapsulation is implemented in the WDS, CTL, and DMS submodules, and the encapsulation is completed and sent to the data processing submodule; for the response from the DIS device After receiving the response, the data processing sub-module parses the command field in the response, and according to the command word, it is respectively processed by the sub-module such as WDS, CTL, DMS; for the state detection of the device, the QMI Daemon module detects through a separate thread. Data from the drive module responds to operations such as plugging and unplugging the device. In addition, considering the extensiveness and extensibility of the QMI protocol family, in the implementation part of the protocol, the layered processing method separates the protocol encapsulation and data transmission processing, reducing the number of interfaces and coupling between the two layers. Sex, which makes it easier to extend the protocol implementation.

(4) QMI Client module 54: Provides interface and encapsulation of the RIL layer, so that QMI and RIL can be seamlessly connected; in the original system, the RIL layer directly calls the interface of the AT module to process the AT command; The QMI protocol is supported. The specific implementation is provided in the QMI Daemon module. This module provides an interface, so that the RIL layer can call the interface provided by the QMI Client module when processing data and configuration services. (5) PPP module 12, this module is mainly used for PPP dialing in the existing RIL framework in the Android system. Since the system uses DIS+QMI for data service processing and no longer uses PPP dialing mode, this module is deleted. . Embodiment 3 This embodiment is a method for processing a downlink data stream in a service implementation. FIG. 6 is a schematic diagram of a downlink data stream according to Embodiment 3 of the present invention. As shown in FIG. 6, the method includes the following steps: Step S602: The RIL layer receives various function calls to the Android system. In step S604, different processing flows are invoked according to different service types; if it is a data service or a configuration service, the process goes to step S606; if the service is short message or phone book, the process goes to step S608. In step S606, if it is a service such as data service or configuration, the process flow of the QMI instruction is entered, and the process goes to step S610. In step S608, if it is a service such as a short message or a telephone book, the processing flow of the AT command is entered, and the process goes to step S610. In step S610, it is determined whether the current QMI instruction is supported. If the support is transferred to step S612, otherwise the process goes to step S618. Step S612, the QMI instruction is encapsulated, and if successful, the process goes to step S614, otherwise the process goes to step S618. In step S614, the QMI command data is sent asynchronously. If yes, the process goes to step S616. Otherwise, the process goes to step S618. In step S616, the DIS driving module actually sends the QMI protocol data. Step S618, the QMI exception processing, and feedback error information to the upper layer. Steps S620~S626, the existing AT command processing flow of Android. Step S628, the AT exception is processed, and the error information is fed back to the upper layer. Embodiment 4 This embodiment is a method for processing an uplink data stream in a service implementation, and FIG. 7 is a schematic diagram of an uplink data stream according to Embodiment 4 of the present invention. As shown in FIG. 7, the method includes the following steps: Step S702, Start the QMI Daemon daemon using the daemon mechanism. Step S704, looping to determine whether there is a message, if there is a message, proceeding to step S706, otherwise continuing to wait and detect the message. Step S706, parsing the received message type, determining what message is. If it is a WDS message, the process goes to step S708, the CTL message goes to step S710, the DMS message goes to step S712, and the other message goes to step S714. deal with. In step S708, the received WDS message is parsed, and the parsing result is reported to the RIL processing flow in step S716. In step S710, the received CTL message is parsed, and the parsing result is reported to the RIL processing flow in step S716. Step S712, parsing the received DMS message, and reporting the analysis result to the RIL processing flow.

S716. Step S714, parsing the received other types of messages, and proceeding to step S718 to perform exception processing. Step S716, the original RIL processing flow of the Android system. Step S718, exception processing of other message types. In summary, in the embodiment of the present invention, a new driving method and device based on the Android system are used to implement

Drive and data access for high-speed mobile broadband devices on Android systems with the following advantages:

(1) The support of the DIS driver module and the QMI protocol has been added, so that the Android system has added support for the DIS device, and the existing NDIS device can be adapted to the Android system without any modification, thereby solving the existing Android system. The RIL driver cannot support DIS devices and cannot effectively improve the transfer speed between mobile broadband devices.

(2) Versatility: Based on Qualcomm's position in the field of communication chips, NDIS equipment will undoubtedly be one of the mainstream access methods for mobile broadband devices. Therefore, designing and implementing support for NDIS devices on Android devices is in line with The development trend of the access mode and technology of the subsequent multi-standard devices expands the functions of the Android system. (3) Extensibility: The solution of the embodiment of the present invention is to integrate the access mode of the DIS device into the existing RIL framework of the Android system, without modifying the architecture of the RIL and Framework of the Android system, and adding the Android system to the mobile broadband device. Access method, which increases the scalability of the Android system; at the same time, the QMI protocol part It is divided into QMI Daemon module and QMI Client module, which makes the encapsulation and implementation of QMI protocol completely in the QMI Daemon module, which increases the scalability of QMI protocol implementation. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device so that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A downlink data processing method for a mobile broadband device, comprising the following steps:

Receiving a function call request from the Android interface of the wireless interface layer RIL;

In the case that the function call request is a data service and a configuration service, the QMI daemon process is used to encapsulate the function call request into a corresponding QMI instruction by using a QMI protocol interface registered in the RIL library, and the encapsulated QMI instruction is encapsulated. The data is sent to the network drive interface specification DIS device.

2. The method according to claim 1, wherein the QMI instruction comprises one of the following: a wireless data service WDS, a control service CTL, and a device management service DMS.

3. The method of claim 1, wherein transmitting the encapsulated QMI command data to the DIS device comprises:

The QMI daemon sends the encapsulated QMI instruction data to the NDIS device through an asynchronous mechanism.

4. An uplink data processing method for a mobile broadband device, comprising the following steps:

The QMI daemon detects the status data from the network driver interface specification DIS device; parses the message type according to the status data, and reports the analysis result to the radio interface layer RIL module of the Android system, where the status data includes at least the following One: status switching data, status conversion data, hot plug event messages.

A data processing method for a mobile broadband device, comprising the downlink data processing method according to any one of claims 1 to 3 and the uplink data processing method according to claim 4.

The method according to claim 5, wherein the method further comprises:

The QMI daemon is started when the Android system is initialized.

A driving device for a mobile broadband device, comprising a wireless interface layer RIL module, the driving device further comprising a QMI module and an NDIS driving module connected to the network driving interface specification DIS device, wherein the RIL module is set to be When the function call request of the Android system from the RIL layer is received as a data service and a configuration service, the function call request is sent to the QMI module by using a QMI protocol interface registered in the RIL library; The QMI module is configured to receive the function request from the RIL module, use the QMI daemon to encapsulate the function call request into a corresponding QMI instruction, and send the encapsulated QMI data to the DIS driver module . The driving device according to claim 7, wherein the QMI module comprises:

a QMI client, configured to provide an interface and encapsulation of the RIL layer, such that the RIL layer invokes the QMI daemon when processing the data service and the configuration service;

The QMI daemon unit is configured to receive the function call request from the QMI client, and encapsulate the function call request into a corresponding QMI instruction, where the QMI instruction includes one of the following: a wireless data service WDS, Control Service CTL, Device Management Service DMS. The driving apparatus according to claim 8, wherein said QMI daemon unit is further configured to detect status data of said DIS device from said DIS driving module, and parse according to the detected message type of said status data And parsing the result of the parsing to the RIL module, where the status data includes at least one of the following: switching data of the status, conversion data of the status, and hot plug event message. The driving device according to any one of claims 7 to 9, wherein the DIS driving module is configured to register a hook function in a USB communication device type Ethernet control model CDC-ECM driver in the Android system, Implementing the analysis of the control data by the USB CDC-ECM driver, wherein the hook function implements sending and parsing the QMI data in the QMI daemon.