WO2012151998A1 - Procédé de traitement de données et appareil de commande pour un dispositif de diffusion mobile - Google Patents

Procédé de traitement de données et appareil de commande pour un dispositif de diffusion mobile Download PDF

Info

Publication number
WO2012151998A1
WO2012151998A1 PCT/CN2011/084135 CN2011084135W WO2012151998A1 WO 2012151998 A1 WO2012151998 A1 WO 2012151998A1 CN 2011084135 W CN2011084135 W CN 2011084135W WO 2012151998 A1 WO2012151998 A1 WO 2012151998A1
Authority
WO
WIPO (PCT)
Prior art keywords
qmi
data
module
ril
daemon
Prior art date
Application number
PCT/CN2011/084135
Other languages
English (en)
Chinese (zh)
Inventor
李焰峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012151998A1 publication Critical patent/WO2012151998A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Definitions

  • 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.
  • 3G Third Generation Mobile Communications
  • 4G Fourth Generation Mobile Communications
  • NDIS Network Driver Interface Specification
  • QMI Quad MSM Interface
  • 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.
  • 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.
  • a downlink data processing method of a mobile broadband device is provided.
  • a downlink data processing method for a mobile broadband device 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.
  • the QMI instruction comprises one of the following: WDS, CTL, DMS.
  • 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.
  • an uplink data processing method of a mobile broadband device 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.
  • a data processing method of a mobile broadband device is also provided.
  • a data processing method for a mobile broadband device includes the above-described downlink data processing method and the above-described uplink data processing method.
  • the method further comprises: starting the QMI daemon during initialization of the Android system.
  • a driving device for a mobile broadband device is also provided.
  • a driving device for a mobile broadband device 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 7 is a schematic diagram of an uplink data stream according to Embodiment 4 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.
  • 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.
  • 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.
  • the QMI instruction includes one of the following: WDS (QMI Wireless Data Service) CTL (QMI Control Service) DMS (QMI Device Management Service).
  • WDS QMI Wireless Data Service
  • CTL QMI Control Service
  • DMS QMI Device Management Service
  • the method is simple and practical, and has high operability.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the above method further comprises: starting the QMI Daemon when the Android system is initialized.
  • This method can improve the effectiveness of the system.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the NDIS driver module 36 is configured as a Universal Serial Bus (USB) in the Android system.
  • USB Universal Serial Bus
  • CDC-ECM The Class Definitions for Communication Devices-Ethernet Control Model
  • 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.
  • 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.
  • the NDIS port and the QMI protocol process the requests of the upper management software separately according to different service types.
  • 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.
  • RIL Radio Interface Layer
  • 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.
  • 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.
  • the QMI Client module 54 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.
  • ⁇ has been supported by the QMI protocol, and the existing wireless broadband service processing with the Android system is realized.
  • Embodiment 2 This embodiment provides a device driving method and system generally used in an Android system.
  • 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.
  • 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.
  • API Application Programming Interface
  • 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.
  • 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.
  • QMI instructions for example, WDS (QMI Wireless Data Service) CTL (QMI Control) Service) DMS (QMI Device Management Service), etc.
  • 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.
  • 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.
  • 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.
  • 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.
  • the method includes the following steps: Step S602: The RIL layer receives various function calls to the Android system.
  • 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.
  • 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.
  • 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.
  • 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.
  • step S614 the QMI command data is sent asynchronously. If yes, the process goes to step S616. Otherwise, the process goes to step S618.
  • 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.
  • 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.
  • step S708 the received WDS message is parsed, and the parsing result is reported to the RIL processing flow in step S716.
  • 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.
  • Step S7116 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.
  • a new driving method and device based on the Android system are used to implement
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)

Abstract

L'invention porte sur un procédé de traitement de données et un appareil de commande pour un dispositif de diffusion mobile. Le procédé comprend les étapes consistant à : recevoir une demande d'appel de fonction à partir d'un système Androïde au niveau d'une couche d'interface radio (RIL) (S202a) ; et dans la situation dans laquelle la demande d'appel de fonction est un service de données et un service de configuration, utiliser un démon QMI pour encapsuler la demande d'appel de fonction en tant qu'instruction QMI correspondante par l'intermédiaire d'une interface de protocole d'interface MSN Qualcomm (QMI) enregistrée dans la bibliothèque RIL, et envoyer les données d'instruction QMI encapsulée à un dispositif de spécification d'interface de pilote réseau (NDIS) (S204a). La présente solution étend la portée d'application du système Androïde et améliore la performance du système.
PCT/CN2011/084135 2011-08-17 2011-12-16 Procédé de traitement de données et appareil de commande pour un dispositif de diffusion mobile WO2012151998A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110235851.0A CN102323892B (zh) 2011-08-17 2011-08-17 移动宽带设备的数据处理方法及驱动装置
CN201110235851.0 2011-08-17

Publications (1)

Publication Number Publication Date
WO2012151998A1 true WO2012151998A1 (fr) 2012-11-15

Family

ID=45451637

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/084135 WO2012151998A1 (fr) 2011-08-17 2011-12-16 Procédé de traitement de données et appareil de commande pour un dispositif de diffusion mobile

Country Status (2)

Country Link
CN (1) CN102323892B (fr)
WO (1) WO2012151998A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102662734B (zh) * 2012-03-06 2014-01-29 中国人民解放军理工大学 一种Android RIL系统及其构建方法
CN102707997B (zh) * 2012-06-12 2014-06-11 中兴通讯股份有限公司 一种移动宽带设备多pdp数据通讯的驱动装置和方法
CN103634944B (zh) * 2012-08-20 2018-10-26 南京中兴新软件有限责任公司 数据卡类终端的工作模式确定方法、装置及系统
CN103974339B (zh) 2013-01-28 2018-01-16 华为技术有限公司 一种数据缓存的方法和装置
WO2014117368A1 (fr) * 2013-01-31 2014-08-07 华为技术有限公司 Dispositif, système et procédé pour personnaliser un réseau mobile autodéfini
CN106209809B (zh) * 2016-07-01 2019-07-05 上海畅联智融通讯科技有限公司 基于安卓系统的AP与Modem的通信系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100689116B1 (ko) * 2005-10-31 2007-03-02 에스케이 텔레콤주식회사 스마트폰에서 위피를 구동하기 위한 데몬
CN101841527A (zh) * 2010-03-05 2010-09-22 北京星网锐捷网络技术有限公司 网络通讯装置及方法
CN101958932A (zh) * 2010-09-21 2011-01-26 中兴通讯股份有限公司 一种实现电信业务的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100689116B1 (ko) * 2005-10-31 2007-03-02 에스케이 텔레콤주식회사 스마트폰에서 위피를 구동하기 위한 데몬
CN101841527A (zh) * 2010-03-05 2010-09-22 北京星网锐捷网络技术有限公司 网络通讯装置及方法
CN101958932A (zh) * 2010-09-21 2011-01-26 中兴通讯股份有限公司 一种实现电信业务的方法和装置

Also Published As

Publication number Publication date
CN102323892A (zh) 2012-01-18
CN102323892B (zh) 2017-03-15

Similar Documents

Publication Publication Date Title
WO2012151998A1 (fr) Procédé de traitement de données et appareil de commande pour un dispositif de diffusion mobile
JP5726300B2 (ja) データカード、及びデータカードのネットワーキング方法
CN1770062A (zh) 用于控制两处理器之间的数据通信的方法和双处理器装置
WO2013178167A1 (fr) Carte de données et procédé et système de communication associés
WO2013071709A1 (fr) Carte de données large bande sans fil supportant l'accès réseau en modes 3g et wi-fi
WO2011088779A1 (fr) Dispositif et procédé pour implémenter une communication inter processus de différents programmes d'application dans un terminal mobile
US9451433B2 (en) Device and method of driving multi-PDP data communication for mobile broadband device
WO2010145091A1 (fr) Procédé de mise en oeuvre de port de réseau virtuel et dispositif incorporé pour mettre en oeuvre un port de réseau virtuel
WO2012034323A1 (fr) Procédé, système et carte de données pour communiquer avec un réseau sans fil à l'aide de la carte de données
JP6526238B2 (ja) 組み込み式操作システムを使ってブルートゥース（登録商標）スレーブ設備の機能を実現する操作システムと方法
WO2008052407A1 (fr) Système et procédé d'accès sans fil
KR20070026682A (ko) 네트워크 장치들 사이의 데이터 전송방법
WO2013178171A1 (fr) Procédé, dispositif et système d'obtention d'informations sur des codes d'erreur
WO2011072537A1 (fr) Appareil, procédé et système de traitement de commandes at
WO2012152007A1 (fr) Procédé et dispositif de traitement de message de pilote de dispositif
WO2012175024A1 (fr) Procédé, système et dispositif de réalisation d'un accès simultané de transmission de données sans fil et d'émission-réception de messages courts
CN100391150C (zh) 数据传送装置及数据传送方法
WO2013013578A1 (fr) Procédé de mise à jour de carte de données, ordinateur personnel et carte de données
JP2003102067A (ja) 状態モデルを備えた無線通信装置
US9619005B2 (en) Apparatus and method for saving power of USB device
WO2011160377A1 (fr) Procédé et appareil de mise en œuvre de plateforme uniforme multicoeur et multinorme
WO2013123688A1 (fr) Procédé et dispositif pour obtenir un accès à des données
WO2012019376A1 (fr) Procédé et appareil adaptés pour mettre en œuvre une fonction de dispositif de réseau pour un terminal de communication sans fil
WO2012155517A1 (fr) Dispositif, système et procédé d'extension de terminal
KR101389077B1 (ko) 통신 시스템에서 호스트에 접속된 범용 시리얼 버스네트워크 장치의 전력 소모를 제어하는 장치 및 방법

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: 11865396

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: 11865396

Country of ref document: EP

Kind code of ref document: A1