WO2014173268A1 - 基于mbim接口实现通信方法及其设备 - Google Patents

基于mbim接口实现通信方法及其设备 Download PDF

Info

Publication number
WO2014173268A1
WO2014173268A1 PCT/CN2014/075808 CN2014075808W WO2014173268A1 WO 2014173268 A1 WO2014173268 A1 WO 2014173268A1 CN 2014075808 W CN2014075808 W CN 2014075808W WO 2014173268 A1 WO2014173268 A1 WO 2014173268A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbb device
host
command
mbb
mbim
Prior art date
Application number
PCT/CN2014/075808
Other languages
English (en)
French (fr)
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 华为终端有限公司
Priority to EP14788197.3A priority Critical patent/EP2922267B1/en
Publication of WO2014173268A1 publication Critical patent/WO2014173268A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/64Hybrid switching systems
    • H04L12/6418Hybrid transport
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/51Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and device for implementing communication based on a MBIM interface.
  • MBB mobile broadband devices
  • the current MBB device communicates with the host based on the interface. After the MBB device is connected to the PC host, it can be reported as various network adapter interfaces such as Modem, Ecm, and Ndi s. Users can access the wireless network through these interfaces. surf the Internet.
  • MBB device When using an existing MBB device, it is necessary to install a unique driver and application provided by the manufacturer. After installing the driver and application, the MBB device switches from the installation mode to the working mode to provide data, voice, and SMS services.
  • Windows 8 includes a new branch in addition to the traditional X64/X86 version, the Windows RT version, which supports the use of the Arm kernel.
  • the Arm kernel With the Arm kernel, the driver for the existing interface does not work, and the upper application of the PC host cannot send data to the MBB device or receive data from the MBB device. At this point, how to make data interaction between the MBB device and the device with the Windows 8 operating system becomes a problem to be solved. Summary of the invention
  • Embodiments of the present invention provide a method and a device for implementing communication based on an MBIM interface, without An additional driver is installed to implement information exchange between the host and the MBB device for extended services on the Windows 8 system.
  • the first aspect provides a mobile broadband MBB device that implements communication based on an MBIM interface
  • the MBB device includes: a receiving module, configured to receive a service query request message sent by the host through the mapped MBIM interface; and a MBIM processing module, configured to parse
  • the service query request message acquires the service query request; the sending module reports the extended service category supported by the MBB device to the host according to the service query request, so that the host and the MBB device pass
  • the MB IM interface performs information exchange of the extended service, where the extended service category includes at least one of a transceiving AT command, a firmware upgrade, or an output MBB device status.
  • the MBB device further includes an AT command processing module, where the receiving module passes the control channel of the MBB device, when the extended service category includes an AT command.
  • the receiving module passes the control channel of the MBB device, when the extended service category includes an AT command.
  • the MBIM processing module parsing the AT command data packet to acquire an AT command; the AT command processing module, processing the AT command, generating a processing result of the AT command, And sending the MBIM processing module to the MBIM processing module to encapsulate the processing result of the AT command; the sending module, by using the control channel of the MBB device, returning the processed result of the encapsulated AT command The host.
  • the MBB device further includes an AT command processing module, when the extended service category includes an AT command, the receiving module, and the data channel of the MBB device Receiving an AT command data packet sent by the host, where the format of the AT command data packet is a device service code stream format; the MBIM processing module parses the AT command data packet to obtain an AT command; and the AT command processing module Processing the AT command to generate a processing result of the AT command; the MBIM processing module, the processing result of encapsulating the AT command is a data packet of a device service code stream format; and the sending module, by the MBB device The data channel returns a packet of the AT command processing result to the host.
  • the MBB device further includes a firmware upgrade module, where the receiving module passes the MBB when the extended service category includes a firmware upgrade.
  • the data channel of the firmware upgrade receives the firmware upgrade data packet, and the format of the firmware upgrade data packet is a device service code stream format; the MBIM processing module parses the firmware upgrade data packet, and obtains the firmware upgrade data.
  • the firmware upgrade module upgrades the firmware version of the MBB device according to the firmware upgrade data.
  • the MBB device further includes a device status output module, when the extended service category includes an MBB device status output, the receiving module, controls by the MBB device
  • the channel receives the service request of the MBB device status output sent by the host; the device status output module outputs the log data of the MBB device status; and the MBIM processing module encapsulates the Log data into the device service code stream format.
  • the sending module returns a data packet of the Log data to the host through a data channel of the MBB device.
  • the second aspect provides a host that implements communication based on the MBIM interface, where the host includes: a transmission module, sending a service query request message to the mobile broadband MBB device through the mapped MBIM interface, and receiving the MBB device returned by the MBB device a supported extended service category, where the extended service category includes at least one of a transceiving AT command, a firmware upgrade, or an MBB device status output; a MBIM interface module, configured to communicate with the MBIM interface according to the extended service class MBB devices perform information exchange for extended services.
  • the extended service category includes: when the AT command is sent and received, the MBIM interface module encapsulates the AT command into an AT command data packet of a command identifier CID format, by using the The control channel of the MBIM interface sends the AT command data packet; the MBIM interface module further receives a CID data packet of the processing result of the AT command reported by the MBB device by using a control channel of the MBIM interface; The CID packet of the processing result of the AT command acquires the processing result of the AT command.
  • the extended service category includes: when the AT command is sent and received, the MBIM interface module encapsulates the AT command as an AT command data packet in a device service code stream format, and passes the Transmitting, by the data channel of the MBIM interface, the AT command data packet to the MBB device; receiving, by using the data channel of the MBIM interface, the AT command reported by the MBB device The data packet of the processing result; parsing the data packet of the processing result of the AT command, and acquiring the processing result of the AT command.
  • the MBIM interface module when the extended service category includes a firmware upgrade, encapsulates the firmware upgrade data into a firmware upgrade data packet of a device service stream format; The data channel of the MBIM interface sends the firmware upgrade data packet to the MBB device, so that the MBB device upgrades the firmware version according to the firmware upgrade data.
  • the MBIM interface module when the extended service class MBB device status is output, the MBIM interface module sends a service request of the MBB device status output to the control channel of the MBIM interface.
  • the MBB device receives the Log data packet outputted by the MBB device status through the data channel of the MBIM interface, where the format of the Log data packet is a device service code stream format; and the Log data packet is parsed to obtain Log data.
  • a third aspect provides a method for implementing communication based on an MBIM interface, where the method includes: receiving, by a mobile broadband MBB device, a service query request message sent by a host through a mapped MBIM interface; parsing the service query request message, and acquiring the service Querying the request; the extended service class supported by the MBB device is reported to the host according to the service query request, so that the host and the MBB device perform information exchange of the extended service through the MBIM interface, where
  • the extended service category includes at least one of transceiving an AT command, a firmware upgrade, or outputting an MBB device status.
  • the extended service category includes: when the AT command is sent and received, reporting an extended service category supported by the MBB device to the host according to the service query request, to enable the
  • the information exchange between the host and the MBB device for performing the extended service by using the MBIM interface includes: receiving, by the control channel of the MBB device, an AT command data packet sent by the host; and parsing the AT command data packet to obtain an AT command; Processing the AT command, generating a processing result of the AT command; processing a result of encapsulating the AT command as a command identifier CID format; returning, by using a control channel of the MBB device, a result of processing the encapsulated AT command Said host.
  • the extended service category includes: when the AT command is sent and received, reporting, according to the service query request, an extended service category supported by the MBB device
  • the information exchange between the host and the MBB device for performing extended service by using the MBIM interface includes: receiving, by using a data channel of the MBB device, an AT command data packet sent by the host, where the AT command
  • the format of the data packet is a device service code stream format; parsing the AT command data packet to obtain an AT command; processing the AT command to generate a processing result of the AT command; and packaging the AT command to process the device service code a data packet of a stream format; returning the AT command processing result packet to the host through a data channel of the MBB device.
  • the extended service category includes a firmware upgrade
  • the information exchange between the host and the MBB device for performing the extended service by using the MBIM interface includes: receiving, by using the data channel of the MBB device, the firmware upgrade data packet, where the format of the firmware upgrade data packet is a device service code a stream format; parsing the firmware upgrade data packet, acquiring the firmware upgrade data; and upgrading the firmware version of the MBB device according to the firmware upgrade data.
  • the extended service category includes an MBB device status output, and when the extended service category supported by the MBB device is reported to the host according to the service query request,
  • the information exchange between the host and the MBB device for performing extended service through the MBIM interface includes: receiving, by using a control channel of the MBB device, a service request for outputting an MBB device status sent by the host; and packaging a status of the MBB device status output
  • the data is a data packet of the device service stream format; the data packet of the Log data is returned to the host by the data channel of the MBB device.
  • the method before the reporting the extended service category supported by the MBB device to the host, includes: receiving, by the control channel of the MBB device, a host sending Opening a data channel service request; opening the data channel according to the service request of the open data channel; returning a response message of the data channel to the host by using a control channel of the MBB device.
  • the MBB device receives the service query request message sent by the host through the mapped MBIM interface, and the mobile broadband MBB device receives the service query request message sent by the host through the mapped MB IM interface through the control channel of the MBB device.
  • the reporting, according to the service query request, the extended service category supported by the MBB device to the host includes: The service query request reports the extended service category supported by the MBB device to the host through the control channel of the MBB device.
  • the reporting, according to the service query request, the extended service category supported by the MBB device to the host includes: The service query request, by the control channel of the MBB device, reporting the universal identification code of the extended service category supported by the MBB device to the host, so that the host identifies the extended service category supported by the MBB device Or, according to the service query request, reporting, by the control channel of the MBB device, an ID of the extended service category supported by the MBB device and an ID of the standard service class, to the host, so that the host identifies the Extended service categories and standard service categories supported by MBB devices.
  • a fourth aspect a method for implementing communication based on an MBIM interface, where the method includes: sending a service query request message to a mobile broadband MBB device by using a mapped MBIM interface; and receiving an extension supported by the MBB device returned by the MBB device a service category, where the extended service category includes at least one of a transceiving AT command, a firmware upgrade, or an MBB device status output; and the information exchange of the extended service with the MBB device is performed by the MBIM interface according to the extended service category.
  • the extended service category includes: when the AT command is sent and received, the information interaction of the extended service with the MBB device by using the MBIM interface according to the extended service category includes:
  • the AT command is a command to identify an AT command data packet in a CID format; the AT command data packet is sent to the MBB device through a control channel of the MBIM interface; and the MBB device is reported to be received by the control channel of the MBIM interface.
  • a CID data packet of a processing result of the AT command a CID data packet parsing a processing result of the AT command, acquiring the AT The processing result of the command.
  • the extended service category includes: when the AT command is sent and received, the information interaction of the extended service with the MBB device by using the MBIM interface according to the extended service category includes:
  • the AT command is an AT command data packet in a device service stream format; the AT command data packet is sent to the MBB device through a data channel of the MBIM interface; and the MBB device is received through a data channel of the MBIM interface.
  • the information interaction of the extended service with the MBB device by using the MBIM interface according to the extended service category includes:
  • the firmware upgrade data is a firmware upgrade data packet of a device service stream format; the firmware upgrade data packet is sent to the MBB device through a data channel of the MBIM interface, so that the MBB device upgrades data according to the firmware. Upgrade the firmware version.
  • the information interaction of the extended service with the MBB device by using the MBIM interface according to the extended service category includes: Transmitting, by the control channel of the MBIM interface, a service request of the MBB device status output to the MBB device; receiving, by using the data channel of the MBIM interface, a Log data packet output by the MBB device status, where the format of the Log data packet is a device Service code stream format; parse the Log data packet to obtain Log data.
  • the receiving, by the MBB device, the extended service category supported by the MBB device before: sending, by using a control channel of the MBIM interface, an open data channel Receiving a service request to the MBB device; receiving, by the control channel of the MBIM interface, a response message that the MBB device starts the data channel; and performing data transmission of the extended service by using the data channel according to the response message.
  • the sending, by using the mapped MBIM interface, the service query request message to the mobile broadband MBB device includes: A service query request message is sent to the MBB device through a control channel of the mapped MBIM interface.
  • the receiving, by the MBB device, the extended service category supported by the MBB device including, by using the MBIM interface
  • the control channel receives an extended service category supported by the MBB device returned by the MBB device.
  • the receiving, by the MBB device, the extended service category supported by the MBB device includes: receiving, returning, the MBB device, The universal identification code of the extended service category supported by the MBB device and the ID, according to which the ID identifies the extended service category supported by the MBB device; or receives the extended service supported by the MBB device returned by the MBB device The UUID of the category and ID and standard service category, thereby identifying the extended service category and standard service category supported by the MBB device.
  • the method for implementing communication based on the MBIM interface in the embodiment of the present invention by reporting the extended service category supported by the MBB device to the host, so that the host performs information interaction with the MBB device through the mapped MBIM interface.
  • the host performs information interaction with the MBB device through the mapped MBIM interface.
  • FIG. 1 is a schematic structural diagram of a system for implementing communication based on an MBIM interface according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of system interaction for implementing communication based on an MBIM interface according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of implementing transmission and reception based on an MBIM interface according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of system information exchange for transmitting and receiving AT commands based on MBIM according to another embodiment of the present invention
  • FIG. 5 is a schematic diagram of system information interaction for implementing firmware upgrade based on an MBIM interface according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of system information interaction for implementing device status output based on a MBIM interface according to an embodiment of the present invention
  • FIG. 7 is a flowchart of a method for implementing communication by an MBB device based on a MBIM interface according to an embodiment of the present invention
  • FIG. 8 is a flowchart of a method for implementing an AT command by an MBB device based on a MBIM interface according to an embodiment of the present invention
  • FIG. 9 is a flowchart of a method for an MBB device to transmit and receive an AT command based on a MBIM interface according to another embodiment of the present invention.
  • FIG. 10 is a flowchart of implementing MBB device firmware upgrade based on MBIM interface according to an embodiment of the present invention
  • FIG. 11 is a flowchart of MBB device status output based on MBIM interface according to an embodiment of the present invention
  • FIG. 12 is a flowchart of a host implementing communication based on a MBIM interface according to an embodiment of the present invention
  • FIG. 13 is a flowchart of a method for a host to transmit and receive an AT command based on a MBIM interface according to an embodiment of the present invention
  • FIG. 14 is a flow chart of a host implementing an AT command based on a MBIM interface according to another embodiment of the present invention
  • FIG. 15 is a flowchart of a firmware upgrade performed by a host based on MBIM according to an embodiment of the present invention
  • FIG. 16 is a flow chart of a host performing MBB device status output based on MBIM according to an embodiment of the present invention
  • FIG. 17 is a schematic diagram of a frame of a mobile broadband MBB device that implements communication based on a MBIM interface according to an embodiment of the present invention
  • FIG. 18 is a schematic diagram of a framework of a host that implements communication based on an MBIM interface according to an embodiment of the present invention
  • FIG. 19 is a schematic structural diagram of an MBB device that implements communication based on an MBIM interface according to an embodiment of the present invention
  • FIG. 1 is a schematic structural diagram of a system for implementing communication based on a MBIM interface according to an embodiment of the present invention.
  • the system 300 can be a system for information exchange between the Mobi le Broadband (MBB) device 100 and the host 200.
  • the host 200 may be a personal computer device, a mobile phone, a PAD (Poor Table Device), a wearable device (i wa tch), or a communication device such as a server.
  • the MBB device 100 may be a data card or the like.
  • the system 300 of the embodiment of the present invention is described by taking the information exchange between the MBB device 100 and the host 200 as an example.
  • the MBB device 100 is connected to the host 200 via a universal serial bus USB interface, thereby causing the MBB device 100 to communicate with the host 200.
  • the host is installed with an operating system supporting the MBIM (Mobi le Broadband Interface Mode 1, MBIM) protocol, for example, the Windows 8 operating system, and the host 200 with the Windows 8 operating system is taken as an example to implement the present invention.
  • MBIM Mobi le Broadband Interface Mode 1, MBIM
  • the system, method and equipment of the examples are described.
  • the host computer to which the Windows 8 operating system is installed is not limited, as long as the operating system supporting the MBIM protocol is applicable to the embodiment of the present invention.
  • the MBB device involved in the embodiment of the present invention refers to a device that communicates using the MBIM protocol.
  • the MBIM protocol is a device interface specification of a network adapter.
  • the MBB device that uses the MBIM protocol can communicate with the host through the USB interface channel in the data format specified by the MBIM protocol.
  • the USB interface channel can include the MBIM protocol.
  • Control channel and data channel the control channel usually transmits a Command Ident If IER (CID) data packet between the host and the MBB device, and the data channel usually transmits the device service code stream between the host and the MBB device ( Device Service Stream (DSS) format or (device servi ce s tream, ds s for short) format.
  • CID Command Ident If IER
  • DSS Device Service Stream
  • DSS device servi ce s tream, ds s for short
  • the device service stream data packet can generally start with a DSS or ds s identifier, and send user-defined data of a non-standard category through a data channel of the USB interface.
  • the data is transmitted between the host and the MBB device by using a data channel through a USB interface.
  • the formula is described as an example of the DSS, but the scope of protection of the embodiments of the present invention is not limited. It can be understood that the format of the data transmitted between the host and the MBB device through the data channel of the USB interface may also be the ds s format.
  • the host 200 When the MBB device 100 is connected to the host 200, such as: the MBB device 100 is inserted into the USB interface of the host 200, the host 200 sends a USB descriptor request to the MBB device 100.
  • the MBB device 100 reports the descriptor information of the device, the interface, and the endpoint corresponding to the MBB device 100 to the host 200 according to the USB descriptor request, and instructs the MBB device 100 to support the MBIM protocol.
  • the host 200 maps a MBIM interface that matches the descriptor information according to the descriptor information reported by the MBB device 100, and implements automatic identification and information interaction with the MBB device through the MBIM interface.
  • FIG. 2 is a schematic diagram of system interaction for implementing communication based on a MBIM interface according to an embodiment of the present invention.
  • Step 10 The host 200 sends a service query request message to the MBB device 100 through the mapped MBIM interface.
  • the host 200 may send a service query request message named "MBIM_CID_DEVICE_SERVICES" to the MBB device 100 through the control channel of the MBIM interface, to query the extended service category supported by the MBB device 100, or query the location.
  • the format of the service query request message may be a Command Ident If ier (CID) format.
  • CID Command Ident If ier
  • the user uses the interface UI of the host operating system to perform related settings on the MBB device. According to the user operation, the host application invokes the operating system's Mobile Broadband Network Interface Function (IMbn). API, the MBIM interface sends instructions or data to the MBB device 100.
  • IMbn Mobile Broadband Network Interface Function
  • the host further includes a network adaptation driver that is provided by the operating system, and the communication between the MB IM interface and the host application is implemented by the network adaptation driver.
  • the host 200 may send a service query request message to the MBB device 100 by using a data channel of the MBIM interface, where the format of the service query request message may be a DSS cell. Style.
  • Step 20 The MBB device 100 receives a service query request message sent by the host through the mapped MBIM interface.
  • the MBB device 100 may receive a service query request message in a CID format sent by the host by using a control channel of the MBB device 100.
  • the MBB device 100 may also receive, by using a data channel of the MBB device 100, a service query request message in a DSS format sent by the host.
  • Step 30 The MBB device 100 parses the service query request message to obtain a service query request.
  • the MBB device 100 parses the service query request message in the CID format, and obtains the service query request.
  • the content of the query request may include querying an extended service category supported by the MBB device 100.
  • the query may include querying extended service categories or standard service categories supported by the MBB device 100 and function values corresponding to the service categories.
  • Step 40 The MBB device 100 reports the extended service category supported by the MBB device 100 to the host 200 according to the service query request, so that the host 200 and the MBB device 100 pass the MBIM.
  • the interface performs information exchange of the extended service, where the extended service category includes at least one of a transceiving AT command Vendor AT, a firmware upgrade F i rmware Upda te, or an output MBB device state Log Output.
  • the system for implementing communication based on the MBIM interface in the embodiment of the present invention by reporting the extended service category supported by the MBB device to the host, so that the host performs information interaction with the MBB device through the mapped MBIM interface. To implement data interaction between the host and the extended service of the MBB device.
  • the MBB device 100 is described by using the control channel of the MBB device 100 to report the extended service category to the host 200, and the control channel of the MBB device 100 is not limited. It may be the data channel of the MBB device 100.
  • the MBB device 100 reports the extension supported by the MBB device according to the service query request.
  • the service category to the host including:
  • the MBB device 100 may report, by using the control channel of the MBB device, a universal identifier (universa l ly unique ident if ier, UUID) of the extended service category supported by the MBB device, according to the service query request. a host, such that the host identifies an extended service category supported by the MBB device.
  • a universal identifier universal Ident if ier, UUID
  • the MBB device 100 may further report, according to the service query request, the UUID of the extended service category and the standard service category supported by the MBB device 100 by using the control channel of the MBB device 100.
  • the host 200 is configured to cause the host 200 to identify an extended service category and a standard service category supported by the MBB device 100.
  • the standard service category may be a short message, a phone book, a SIM card authentication management, a network/network disconnection function, and the like.
  • the MBB device 100 may report, by using the control channel of the MBB device 100, the extended service category supported by the MBB device 100 and the ID and the function corresponding to the extended service category. The value is given to the host 200.
  • the MBB device 100 may report, by using the control channel of the MBB device 100, the UUID, the standard service category, the ID, and the extension of the extended service category supported by the MBB device 100.
  • the function value corresponding to the service category is given to the host 200.
  • the extended service class that the MBB device 100 can also report to the host device 200 through the control channel may be one type or multiple types, which is not limited in the embodiment of the present invention.
  • the MBB device 100 may pre-define the extended service category and the ID, the standard service category UUID, and/or the function value corresponding to the extended service category, where the predefined may be a device manufacturer or an operation. Pre-sets that are made before shipment or before sale.
  • the MBB device 100 defines an extended service class of a transceiving AT command named "Vendor AT”, and the UUID defining the transceiving AT command extended service class may be UUID_VENDOR_AT. And define the function value of "MBIM_CID_VENDOR_AT,” to represent the actual function of "Vendor AT”.
  • the MBB device 100 customizes an extended service category of firmware upgrade named "Fi r to are Upda te", and the identifier UUID defining the firmware upgrade may be UUID_FIRMWARE_UPDATE.
  • the MBB device 100 customizes an extended service category of an output MBB device status named "Log Output", and the identification code UUID defining the output MBB device status may be UU. ID_ L0G_ OUTPUT.
  • the MBB device 100 may further add a service function module corresponding to the extended service category to perform an extended service function corresponding to the extended service category, where the service function modules are integrated in the MBB device 100.
  • the service function module corresponding to the extended service category can also be a communication device independent of the MBB device 100, and the independent communication device corresponding to the service function module can perform information interaction with the MBB device 100.
  • the service function module may include an AT command processing module, a firmware upgrade module, an output MBB device status module, and the like.
  • the type and function of the service function module are not limited in the embodiment of the present invention, and are customized according to the needs of the equipment operator or the manufacturer.
  • FIG. 3 is a schematic diagram of information interaction of transmitting and receiving AT commands based on a MBIM interface according to an embodiment of the present invention.
  • the MBB device 100 reports an extended service category supported by the MBB device to the host according to the service query request, so that the host 200 and the host
  • the information interaction of the MBB device 100 for performing extended services includes:
  • Step 21 The host 200 determines that the extended service category is a transceiving AT command, and sends an AT command C I D data packet to the MBB device 100 through a control channel of the MB IM interface.
  • the application of the host 200 invokes the mobile broadband network interface function IMbn API to open the transceiving AT command service, wherein the application is a control instruction set corresponding to the extended service category.
  • the application calls the IMbn API, and sends a string of the AT command to the MB IM interface.
  • the interface adaptation driver of the MBIM interface may use the string of the AT command to Encapsulated as an AT command CID packet and sent to the MBB device 100
  • the AT command C I D data packet may have the following format:
  • the MBB device 100 receives the AT command CI D data packet transmitted by the host 200 through the control channel of the MBB device.
  • Step 23 The MBB device 100 parses the AT command C I D data packet to obtain the AT command.
  • Step 24 The MBB device 100 further processes the AT command to generate a processing result of the AT command.
  • Step 25 The MBB device 100 may return a C ID data packet of the processing result of the AT command to the host 200 through a control channel of the MBB device 100.
  • the MBB device 100 returns the AT command CID data packet may have the following format: Step 26: The host 200 receives the MBB device through the control channel of the MBIM interface, and the U.S. 0030007 UUID VENDOR country; V; VENDOR AT ⁇ :
  • Step 27 The host 200 parses the CID data packet of the processing result of the AT command to obtain a processing result of the AT command.
  • the MBIM interface of the host 200 parses the CI D data packet of the processing result of the AT command to obtain the processing result of the AT command, and the MBIM interface sends the processing result of the AT command by using the IMbn AP I. To the application, complete the AT command processing.
  • FIG. 4 is a schematic diagram of system information exchange according to another embodiment of the present invention for transmitting and receiving an AT command according to MBIM, where the extended service category includes receiving and receiving an AT command, the MBB device 100 reports the request according to the service query request.
  • the extended service class supported by the MBB device to the host, so that the host 200 interacts with the MBB device 100 for performing extended service information which may include: Step 31: The host 200 determines that the extended service category is a transceiving AT command, and sends an AT command data packet in a DSS format to the MBB device 100 through a data channel of the MBIM interface.
  • step 31 includes:
  • Step 311 The application of the host 200 invokes the IMbn API according to the extended service category, and opens and receives an AT command service.
  • Step 312 The application invokes the IMbn API to send a request message for opening the device service code stream DSS service, that is, MBIM_CID_DSS_CO ⁇ ECT, to the MBIM interface;
  • Step 313 The host 200 sends the request message of the DSS service for transmitting and receiving the AT command to the MBB device 100 through the control channel of the MBIM interface;
  • Step 314 The MBB device 100 receives, by using a control channel of the MBB device 100, a request message that is sent by the host 200 to enable the DSS service.
  • Step 315 The MBB device 100 starts the DSS service, and returns a response message for opening the DSS service to the host 200 by using a control channel of the MBB device.
  • Step 316 The host 200 receives a response message of the DSS service by using a control channel of the MBIM interface, and the MBIM interface sends the response message to the application by using the IMbn API.
  • Step 317 The application calls the IMbn API, and sends a string of the AT command to the MBIM interface.
  • Step 318 The interface adaptation driver of the MBIM interface encapsulates the string of the AT command into a DSS data packet, and sends the data channel to the MBB device 100 through the data channel of the MBIM interface.
  • Step 32 The MBB device 100 receives the AT command DSS data packet sent by the host by using the data channel of the MBB device, where the format of the AT command DSS data packet is a DSS format.
  • Step 33 The MBB device 100 parses the AT command DSS data packet to obtain the At command.
  • Step 34 The MBB device 100 processes the AT command to generate a processing result of the AT command.
  • Step 35 The processing result of the MBB device 100 encapsulating the AT command is a DSS data packet, and the DSS data packet of the AT command processing result is returned to the host 200 by using the data channel of the MBB device 100.
  • Step 36 The MB IM interface of the host 200 receives the DSS data packet of the processing result of the AT command returned by the MBB device 100 through the data channel of the host 200.
  • Step 37 The MBIM interface parses the DSS data packet of the processing result of the AT command, and obtains a processing result of the AT command.
  • Step 38 The MBIM interface sends the processing result of the AT command to the application by using the IMbn API, and completes AT command processing.
  • FIG. 5 is a schematic diagram of system information interaction for implementing firmware upgrade based on an MBIM interface according to an embodiment of the present invention.
  • the extended service category includes, when the firmware is upgraded, reporting the extended service category supported by the MBB device to the host according to the service query request, so that the host and the MBB device pass the
  • the information interaction of the MBIM interface for extended services includes:
  • Step 51 The host 200 determines that the extended service category is a firmware upgrade, and sends a firmware upgrade data packet of the DSS format to the MBB device 100 through the data channel of the MBIM interface.
  • step 51 includes:
  • Step 511 The application of the host 200 invokes the IMbn API according to the extended service category, and opens a firmware upgrade service.
  • the application may be provided by the MBB device or obtained from a service provider.
  • the installed program or the default program that comes with the host.
  • Step 512 The application invokes the IMbn API to send a request message for starting the device service code stream DSS service, that is, MBIM_CID_DSS_C0 ⁇ ECT, to the MBIM interface;
  • Step 513 The MBIM interface sends a request message for opening the DSS service of the firmware upgrade to the MBB device 100 through the control channel of the MBIM interface;
  • Step 514 The MBB device 100 receives, by using the control channel of the MBB device 100, a DSS service request message sent by the host 200 to enable the firmware upgrade.
  • Step 515 The MBB device 100 starts the firmware upgrade DSS service, and returns a response message of the DSS service for opening the firmware upgrade to the host 200 through the control channel of the MBB device 100.
  • Step 516 The host 200 receives a response message of the firmware upgraded DSS service through a control channel of the MBIM interface, and sends the response message to the application by using the IMbn API.
  • Step 517 The application invokes the IMbn API to send firmware upgrade data to the MBIM interface.
  • Step 518 The interface adaptation driver of the MBIM interface encapsulates the firmware upgrade data into a DSS format data packet, and sends the data packet to the MBB device 100 through the data channel of the MBIM interface.
  • the DSS data packet of the firmware upgrade data may have the following standard format:
  • Step 52 The device 100 receives the firmware upgrade DSS data packet sent by the host through the data channel of the UI device.
  • Step 53 The device 100 parses the firmware upgraded DSS data packet to obtain the firmware upgrade data, and upgrades the firmware version of the UI device 100.
  • FIG. 6 is a schematic diagram of system information interaction for implementing device state output based on an MBIM interface according to an embodiment of the present invention.
  • Step 61 The host 200 determines that the extended service category is an output MBB device status, and sends a service request of the MBB device status output to the MBB device 100 through a control channel of the MBIM interface.
  • the step 61 includes: Step 611: The application of the host 200 invokes the IMbn API according to the extended service category to open a service outputted by the MBB device status.
  • Step 612 The application invokes the application interface IMbn AP I to send a request message for opening the DSS service of the MBB device status output to the MBIM interface.
  • Step 61 The host 200 sends a request message for opening the DSS service outputted by the MBB device status to the MBB device 100 through the control channel of the MBIM interface.
  • Step 614 The MBB device 100 receives the DSS service request sent by the host 200 to enable the MBB device status output by using the control channel of the MBB device 100.
  • Step 615 The MBB device 100 turns on the DSS service of the MBB device status output, and returns a response message of the DSS service outputting the MBB device status output to the host 200 through the control channel of the MBB device.
  • Step 616 The host 200 receives a response message of the DSS service output by the MBB device status through a control channel of the MBIM interface, and the MBIM interface sends the response message to the application by using the IMbn API.
  • Step 62 The Log data of the MBB device 100 encapsulating the status of the MBB device is a DSS data packet.
  • Step 63 The MBB device 100 returns a DSS data packet of the Log data to the host 200 through a data channel of the MBB device 100.
  • Step 64 The host 200 receives the DSS data packet of the Log data through a data channel of the MBIM interface.
  • Step 65 The host 200 parses the DSS data packet of the log data, and obtains the log. Data is sent to the application via the IMbn API.
  • the DSS data packet of the Log data that the MBB device 100 interacts with the host 200 may have the following format:
  • the MBB device 100 of the embodiment of the present invention can send service data with a small amount of data through the control channel of the MBB device, for example, sending and receiving an AT command, and the data volume can be sent through the data channel of the MBB device.
  • Large business data such as firmware upgrade data, to improve the transmission efficiency of the MBB device 100.
  • the system for implementing communication based on the MBIM interface in the embodiment of the present invention by reporting the extended service category supported by the MBB device to the host, so that the host performs information interaction with the MBB device through the mapped MBIM interface. To implement data interaction between the host and the extended service of the MBB device.
  • FIG. 7 is a flowchart of a method for implementing communication by an MBB device based on a MBIM interface according to an embodiment of the present invention.
  • the mobile broadband MBB device receives a service query request message sent by the host through the mapped MBIM interface;
  • the extended service category includes at least one of transceiving AT commands, firmware upgrades, or output MBB device status.
  • the MBB device that implements the communication based on the MBIM interface in the embodiment of the present invention, by reporting the extended service category supported by the MBB device to the host, so that the host performs the extended service information with the MBB device through the mapped MBIM interface.
  • Interaction implementing extended services for hosts and MBB devices Data interaction.
  • FIG. 8 is a flowchart of a method for an MBB device to transmit and receive an AT command based on a MBIM interface according to an embodiment of the present invention.
  • the MBB device 100 reports the extended service category supported by the MBB device 100 to the host according to the service query request, so that the host 200 and the MBB are
  • the information interaction of the extended service by the device 100 through the MBIM interface includes:
  • Step 731 The MBB device 100 receives an AT command CID data packet sent by the host 200 through a control channel of the MBB device 100.
  • Step 732 The MBB device 100 parses the AT command C I D data packet to obtain an AT command.
  • Step 734 The MBB device 100 returns the processing result of the AT command to the host 200 through the control channel of the MBB device 100.
  • FIG. 9 is a flowchart of a method for an MBB device to implement an AT command based on a MBIM interface according to another embodiment of the present invention.
  • the extended service category includes the sending and receiving AT command, reporting, according to the service query request, an extended service category supported by the MBB device to the host 200, so that the host 200 and the MBB device 100 pass the
  • the information interaction of the MBIM interface for extended services includes:
  • Step 741 Receive, by using a data channel of the MBB device 100, an AT command data packet sent by the host 200, where the format of the AT command data packet is a custom code stream DSS format;
  • Step 742 Parsing the AT command data packet to obtain an AT command.
  • Step 743 Processing the AT command to generate a processing result of the AT command.
  • Step 744 The processing result of encapsulating the AT command is a DSS data packet.
  • Step 745 Return, by the data channel of the MBB device 100, the DSS data packet of the AT command processing result to the host 200.
  • FIG. 10 is a flowchart of implementing an firmware upgrade based on an MBIM interface of an MBB device according to an embodiment of the present invention.
  • the extended service category includes a firmware upgrade
  • the service query request when the extended service category supported by the MBB device is reported to the host, the host and the MBB device are performed by using the MBIM interface.
  • the information interaction of the extended service includes:
  • Step 751 Receive, by using a data channel of the MBB device, the firmware upgrade data packet, where the format of the firmware upgrade data packet is a device service code stream DSS format;
  • Step 752 Parse the firmware upgrade data packet to obtain the firmware upgrade data.
  • Step 753 Upgrade the firmware version of the MBB device according to the firmware upgrade data.
  • FIG. 11 is a flowchart of MBB device status output based on MBIM interface according to an embodiment of the present invention.
  • the information interaction of the extended service by using the MBIM interface includes: Step 761: receiving, by using a control channel of the MBB device 100, a service request for outputting an MBB device status sent by the host 200;
  • Step 762 The Log data of the MBB device status output is a data packet of the device service code stream DSS format
  • Step 763 Return a DSS format data packet of the Log data to the host by using a data channel of the MBB device.
  • the MBB device of the present embodiment implements the communication based on the MBIM interface, and is implemented according to the foregoing system embodiment. For the specific implementation steps, refer to the foregoing system embodiment, which is not described herein.
  • the MBB device 100 that implements communication based on the MBIM interface in the embodiment of the present invention sends the extended service category supported by the MBB device to the host, so that the host performs extended service with the MBB device through the mapped MBIM interface.
  • Information interaction realizing data interaction between the host and the extended service of the MBB device.
  • FIG. 12 is a flowchart of a host implementing communication based on an MBIM interface according to an embodiment of the present invention.
  • the host 200 sends a service inquiry request message to the mobile broadband MBB device 100 through the mapped MBIM interface.
  • the host 200 receives the extended service category supported by the MBB device returned by the MBB device 100, where the extended service category includes at least one of a transceiving AT command, a firmware upgrade, or an MBB device status output.
  • the host 200 performs information exchange of the extended service with the MBB device 100 through the MBIM interface according to the extended service category.
  • the host 200 that implements communication based on the MBIM interface in the embodiment of the present invention receives the extended service category returned by the MBB device through the mapped MBIM interface, and performs extended service communication with the MBB device according to the extended service category to implement the host and the MBB. Data interaction of the extended service of the device.
  • FIG. 13 is a flowchart of a host implementing an AT command based on a MBIM interface according to an embodiment of the present invention.
  • the information service interaction between the host 200 and the MBB device by using the MBIM interface according to the extended service category includes:
  • FIG. 14 is a flow chart of a host implementing an AT command based on a MBIM interface according to another embodiment of the present invention.
  • the extended service category includes: when the AT command is sent and received, the information interaction between the host 200 and the MBB device by using the MBIM interface according to the extended service category includes: 841: Encapsulate the AT command as an AT command data packet of a device service code stream DSS format;
  • FIG. 15 is a flowchart of a firmware upgrade implemented by a host based on MBIM according to an embodiment of the present invention.
  • the information exchange between the host 200 and the MBB device 100 by using the MBIM interface according to the extended service category includes: 851: Encapsulating the firmware upgrade data into a device a firmware upgrade data packet in a service stream DSS format; 852: transmitting, by the data channel of the MBIM interface, the firmware upgrade data packet in a DSS format to the MBB device 100, so that the MBB device is upgraded according to the firmware Data upgrade firmware version.
  • 16 is a flow chart of a host implementing MBB device status output based on MBIM according to an embodiment of the present invention.
  • the extended service category includes the MBB device status output
  • the information interaction between the host 200 and the MBB device 100 by using the MBIM interface according to the extended service category includes:
  • the host 200 before receiving, by the MBB device 100, the extended service category supported by the MBB device, the host 200 includes: The host 200 sends a service request for opening the data channel to the MBB device through the control channel of the MBIM interface, and receives, by using the control channel of the MB IM interface, the response message of the MBB device to enable the data channel, according to the The response message transmits data of the extended service through the data channel.
  • the data channel may be a data channel corresponding to the MBIM interface.
  • the host 200 can send a service query request message to the mobile broadband MBB device 100 through the control channel of the mapped MBIM interface, and can also receive the returned by the MBB device 100 through the control channel of the MBIM interface.
  • the extended service category supported by the MBB device can be understood that the host 200 can send a service query request message to the mobile broadband MBB device 100 through the control channel of the mapped MBIM interface, and can also receive the returned by the MBB device 100 through the control channel of the MBIM interface.
  • the extended service category supported by the MBB device can be understood that the host 200 can send a service query request message to the mobile broadband MBB device 100 through the control channel of the mapped MBIM interface, and can also receive the returned by the MBB device 100 through the control channel of the MBIM interface.
  • the extended service category supported by the MBB device can be understood that the host 200 can send a service query request message to the mobile broadband MBB device 100 through the control channel of the mapped MBIM interface, and can also receive the returned by the M
  • the host 200 receives the extended service category supported by the MBB device returned by the MBB device, and the host 200 receives the universal identification of the extended service category supported by the MBB device returned by the MBB device.
  • a code UUID identifying, according to the UUID, an extended service category supported by the MBB device; or
  • the MBB device And receiving, by the MBB device, the UUID of the extended service category supported by the MBB device and the standard service category, thereby identifying the extended service category and the standard service category supported by the MBB device.
  • the host 200 that implements communication based on the MBIM interface in the embodiment of the present invention receives the extended service category returned by the MBB device through the mapped MBIM interface, performs extended service communication with the MBB device according to the extended service category, and implements the host and the MBB device.
  • the data exchange of the extended service is a schematic diagram of a frame of a mobile broadband MBB device that implements communication based on a MBIM interface according to an embodiment of the present invention.
  • the MBB device 100 includes: a receiving module 101, configured to receive a service query request message sent by the host 100 through the mapped MBIM interface;
  • the MBIM processing module 102 is configured to parse the service query request message, and obtain the service query request;
  • the sending module 103 reports the extended service category supported by the MBB device to the host, so that the host and the MBB device perform information exchange of the extended service through the MBIM interface, where
  • the extended service category includes at least one of a transceiving AT command, a firmware upgrade, or an output MBB device status.
  • the MBB device 100 that implements communication based on the MBIM interface in the embodiment of the present invention sends the extended service class supported by the MBB device to the host 200, so that the host 200 expands with the MBB device through the mapped MBIM interface.
  • the information exchange of the service realizes the data interaction between the host and the extended service of the MBB device.
  • the MBB device 100 further includes an AT command processing module 106, when the extended service category includes an AT command,
  • the receiving module 101 receives an AT command data packet sent by the host 100 through a control channel of the MBB device;
  • the MBIM processing module 102 includes a parsing unit 1 021 and an obtaining unit 1022.
  • the parsing unit 1021 parses the AT command data packet into a format recognizable by the MBB device, and the acquiring unit 1022 acquires the AT command.
  • the AT command processing module 106 processes the AT command, generates a processing result of the AT command, and sends the result to the MBIM processing module, so that the MBIM processing module encapsulates the processing result of the AT command;
  • the sending module 103 returns the processing result of the encapsulated AT command to the host 200 through the control channel of the MBB device.
  • the receiving module 101 receives an AT command data packet sent by the host 200 by using a data channel of the MBB device, where the AT command data packet
  • the format is a custom code stream DSS format
  • the MBIM processing module 102 parses the AT command data packet to obtain an AT command;
  • the AT command processing module 106 processes the AT command to generate a processing result of the AT command;
  • the MBIM processing module 102 the processing result of encapsulating the AT command is a DSS data packet
  • the sending module 103 returns a DSS data packet of the AT command processing result to the host 200 by using a data channel of the MBB device. .
  • the MBB device 100 further includes a firmware upgrade module 107, when the extended service category includes a firmware upgrade,
  • the receiving module 101 receives the firmware upgrade data packet by using a data channel of the MBB device, where the format of the firmware upgrade data packet is a device service code stream DSS format;
  • the MBIM processing module 102 parses the firmware upgrade DSS data packet to obtain the firmware upgrade data.
  • the firmware upgrade module 107 upgrades the firmware version of the MBB device according to the firmware upgrade data.
  • the MBB device 100 further includes a device status output module 108, when the extended service category includes an MBB device status output,
  • the receiving module 101 receives, by using a control channel of the MBB device, a service request outputted by the MBB device status sent by the host 100;
  • the device status output module 108 outputs Log data of the MBB device status; the MBIM processing module 102 encapsulates the Log data into a data packet of a device service code stream DSS format;
  • the sending module 103 returns a DSS format data packet of the Log data to the host 100 through a data channel of the MBB device.
  • the MBB device 100 further includes an adding module 104 and a storage module 105, where the adding module 104 is configured to add an extended service category customized by the MBB device, a function value corresponding to the extended service category, and the like.
  • the storage module 105 stores an application of the MBB device 100, extended service data, and the like. It can be understood that the receiving module 101 receives, by using the control channel of the MBB device, a service query request message sent by the host 200 through the mapped MBIM interface. The sending module 103 reports the extended service category supported by the MBB device to the host 200 through the control channel of the MBB device.
  • MBB device 100 of the embodiment of the present invention is described based on the foregoing system embodiment.
  • specific implementation process reference may be made to the foregoing system embodiment.
  • the MBB device 100 that implements communication based on the MBIM interface in the embodiment of the present invention sends the extended service class supported by the MBB device to the host 200, so that the host 200 expands with the MBB device through the mapped MBIM interface.
  • the information exchange of the service realizes the data interaction between the host and the extended service of the MBB device.
  • FIG. 18 is a schematic diagram of a framework of a host that implements communication based on a MBIM interface according to an embodiment of the present invention.
  • the host 200 includes: a transmission module 201, which sends a service query request message to the mobile broadband MBB device through the mapped MBIM interface, and receives an extended service category supported by the MBB device returned by the MBB device, where the extended service category Including at least one of sending and receiving AT commands, firmware upgrades, or MBB device status outputs;
  • the MBIM interface module 202 is configured to perform information exchange of the extended service with the MBB device by using the MBIM interface according to the extended service category.
  • the host 200 that implements communication based on the MBIM interface in the embodiment of the present invention receives the extended service category returned by the MBB device through the mapped MBIM interface, performs extended service communication with the MBB device according to the extended service category, and implements the host and the MBB device.
  • the data exchange of the extended service receives the extended service category returned by the MBB device through the mapped MBIM interface, performs extended service communication with the MBB device according to the extended service category, and implements the host and the MBB device.
  • the MBIM interface module 202 may be further configured to: when the extended service category includes an AT command, the MBIM interface module 202 encapsulates the AT command as an AT command packet in a command identifier CID format, The control channel of the MBIM interface sends the AT command data packet; and the CID data packet of the processing result of the AT command reported by the MBB device is received by the control channel of the MBIM interface; Processing the result of the CID data packet, and obtaining the processing result of the AT command.
  • the MBIM interface module 202 may further encapsulate the AT command data packet in the DSS format of the device service code stream, and send the AT command data packet in the DSS format to the data channel of the MBIM interface. Receiving, by the data channel of the MBIM interface, a DSS data packet of a processing result of the AT command reported by the MBB device; parsing a DSS data packet of a processing result of the AT command, acquiring the AT command Processing results.
  • the MBIM interface module 202 may further encapsulate the firmware upgrade data into a firmware upgrade data packet in a device service stream DSS format; and data through the MBIM interface.
  • the channel transmits the firmware upgrade data packet in the DSS format to the MBB device, so that the MBB device upgrades the firmware version according to the firmware upgrade data.
  • the MBIM interface module 202 may further send a service request of the MBB device status output to the MBB device by using a control channel of the MBIM interface;
  • the data channel of the MBIM interface receives the Log data packet outputted by the MBB device status, and the format of the Log data packet is a DSS format.
  • the Log data packet is parsed to obtain Log data.
  • the transmission module 201 may send or receive the service query request message to the MBB device through a control channel of the MB IM interface, and may receive the MBB device return by using a control channel of the MBIM interface.
  • the host 200 may further include a storage module 205 that stores the application and extended service data and the like.
  • the host 200 that implements communication based on the MB IM interface in the embodiment of the present invention receives the extended service category returned by the MBB device through the mapped MBIM interface, performs extended service communication with the MBB device according to the extended service category, and implements the host and the MBB. Data interaction of the extended service of the device.
  • FIG. 19 is a schematic structural diagram of an MBB device that implements communication based on an MB IM interface according to an embodiment of the present invention.
  • the MBB device 100 includes a processor 1 1 0 and a first interface 1 1 1 . One end of the first interface 1 1 1 is connected to the processor 1 1 0, and the other end of the first interface 1 1 1 is used.
  • the first interface 112 Connected to the host 200, the first interface 112 receives the service sent by the host 200 through the mapped MB IM interface. Inquire for the news;
  • the processor 110 parses the service query request message to obtain the service query request, and reports the extended service category supported by the MBB device to the host 200 by using the first interface 111 according to the service query request. And causing the host 200 and the MBB device 100 to perform information exchange of the extended service by using the MBIM interface, where the extended service category includes at least one of a transceiving AT command, a firmware upgrade, or an output MBB device status.
  • the MBB device 100 that implements communication based on the MBIM interface in the embodiment of the present invention sends the extended service class supported by the MBB device to the host 200, so that the host 200 expands with the MBB device through the mapped MBIM interface.
  • the information exchange of the service realizes the data interaction between the host and the extended service of the MBB device.
  • the processor 110 is further configured to parse the data packet of the AT command to acquire an AT command, and process the AT command to generate a processing result of the AT command, where the extended service class includes an AT command.
  • the processing result of the AT command is sent to the host 200 through the first interface.
  • the AT command may be a C ID format or a DSS format.
  • the processor 110 parses a firmware upgrade data packet sent by the host, acquires the firmware upgrade data, and upgrades the MBB device according to the firmware upgrade data.
  • Firmware version the firmware upgrade data packet sent by the host.
  • the processor 110 receives the service request of the MBB device status output sent by the host 200 through the control channel of the first interface 111; and encapsulates the MBB device status.
  • the output Log data is a data packet of the device service code stream DSS format; the DSS format data packet of the Log data is returned to the host through the data channel of the first interface 1 11 .
  • the processor 110 can receive and/or respond to the service query request sent by the host 200 through a control channel of the first interface 111.
  • the processor 107 is further configured to add a customized extended service class identifier and the ID. And/or an extended service function value corresponding to the extended service category.
  • the MBB device 100 may further include a memory 112, an input unit 113, a display screen 114, an RF circuit 115, an audio circuit 116, and the like; the memory 112 is configured to store an application and extended service data executed by the processor 110, where
  • the input unit 113 may include a touch panel 117 and other input devices 118, such as a keyboard, a mouse, etc., the input unit 113 may receive a user input operation instruction, and execute the operation instruction by the processor 110 to display the execution result.
  • the display screen 114 is presented to the user.
  • the first interface 111 in the embodiment of the present invention may be a universal serial bus USB interface of the MBB device 100, which is not limited in this embodiment.
  • the MBB device 100 may further include a camera, a Bluetooth module, etc., and will not be described again.
  • the MBB device 100 that implements communication based on the MBIM interface in the embodiment of the present invention sends the extended service class supported by the MBB device to the host 200, so that the host 200 expands with the MBB device through the mapped MBIM interface.
  • the information exchange of the service realizes the data interaction between the host and the extended service of the MBB device.
  • FIG. 20 is a schematic diagram of a structure of a host that implements communication based on a MBIM interface.
  • a host 200 that implements communication based on the MBIM interface includes: a host processor 210 and a second interface 211, one end of the second interface 211 is connected to the host processor 210, and the second interface 211 The other end is connected to the mobile broadband MBB device 100, the host 200 is connected to the MBB device 100, and the second interface is mapped to an MB IM interface;
  • the host processor 210 sends a service query request message to the MBB device 100 by using the mapped MBIM interface, and receives an extended service category supported by the MBB device returned by the MBB device 100, where the extended service category is Including at least one of sending and receiving AT commands, firmware upgrades, or MBB device status outputs;
  • the host processor 210 performs information exchange of the extended service with the MBB device through the MBIM interface according to the extended service category.
  • the host 200 that implements communication based on the MBIM interface in the embodiment of the present invention receives the extended service category returned by the MBB device through the mapped MBIM interface, performs extended service communication with the MBB device according to the extended service category, and implements the host and the MBB device.
  • the data exchange of the extended service is
  • the host processor 210 may be further configured to: when the extended service category includes an AT command, the host processor 210 may encapsulate the AT command into an AT command data packet of a command identifier CID format.
  • the control channel of the MBIM interface sends the AT command data packet to the MBB device 100; the CID data packet of the processing result of the AT command reported by the MBB device 100 is received by the control channel of the MBIM interface; The CID packet of the processing result of the AT command acquires the processing result of the AT command.
  • the host processor 210 may further encapsulate the AT command data packet in the device service code stream DSS format, and the data passing through the MBIM interface. Transmitting, by the channel, the AT command data packet in the DSS format to the MBB device 100; receiving, by using the data channel of the MBIM interface, a DSS data packet of the processing result of the AT command reported by the MBB device 100; parsing the AT The DSS packet of the processing result of the command acquires the processing result of the AT command.
  • the host processor 210 may further encapsulate the firmware upgrade data into a firmware upgrade data packet in a device service code stream DSS format; data passing through the MBIM interface.
  • the channel transmits the firmware upgrade packet in the DSS format to the MBB device 100 to cause the MBB device 100 to upgrade the firmware version according to the firmware upgrade data.
  • the host processor 210 sends a service request of the MBB device status output to the MBB device 100 by using a control channel of the MBIM interface;
  • the data channel of the interface receives the Log data packet outputted by the MBB device status, and the format of the Log data packet is a DSS format.
  • the Log data packet is parsed to obtain the Log data.
  • the host processor 210 can send or receive the service query request message to the MBB device 100 through the control channel of the MBIM interface, and connect through the MBIM.
  • the control channel of the port receives the extended service category supported by the MBB device returned by the MBB device.
  • the host processor 210 further adds and executes an application corresponding to the extended service category and the processing extension function customized by the MBB device.
  • the host 100 may further include a host memory 212 and a host input unit.
  • Host display 214 Host display 214, host audio circuit 215, host RF circuit 216, etc.
  • the host memory 212 can be used to store application programs and extended service data executed by the host processor 210, and the host input unit 213 can include a touch panel 217 and other input devices 219, such as a mouse.
  • the host input unit 213 can receive a user input operation instruction, and the host processor 210 executes the operation instruction, and displays the execution result on the host display screen 214 for presentation to the user.
  • the host 200 can also play a sound file through the host audio circuit 215.
  • the host 200 may further include a camera, a Bluetooth module, etc., and will not be described herein.
  • the second interface 211 in the embodiment of the present invention may be a universal serial bus USB interface of the host 200, which is not limited in this embodiment.
  • the host 200 that implements communication based on the MBIM interface in the embodiment of the present invention receives the extended service category returned by the MBB device through the mapped MBIM interface, performs extended service communication with the MBB device according to the extended service category, and implements the host and the MBB device.
  • the data exchange of the extended service receives the extended service category returned by the MBB device through the mapped MBIM interface, performs extended service communication with the MBB device according to the extended service category, and implements the host and the MBB device.
  • RAM random access memory
  • ROM read only memory
  • electrically programmable ROM electrically erasable programmable ROM
  • registers hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • RAM random access memory
  • ROM read only memory
  • electrically programmable ROM electrically erasable programmable ROM
  • registers hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种基于MBIM接口实现通信的方法及其设备,MBB设备包括:接收模块,用于接收主机通过映射的MBIM接口发送的服务查询请求消息;MBIM处理模块,用于解析所述服务查询请求消息,获取所述服务查询请求;发送模块,根据所述服务查询请求,上报所述MBB设备支持的扩展服务类别给所述主机,以使所述主机与所述MBB设备通过所述MBIM接口进行扩展服务的信息交互,其中,所述扩展服务类别包括收发AT命令、固件升级或输出MBB设备状态的至少之一。本发明实施例,通过上报所述MBB设备支持的扩展服务类别给所述主机,以使所述主机通过映射的MBIM接口与所述MBB设备进行扩展服务的信息交互。

Description

基于 MBIM接口实现通信方法及其设备 本申请要求于 2013 年 4 月 27 日提交中国专利局, 申请号为 201310152616.6, 发明名称为 "基于 MBIM接口实现通信方法及其设备" 的 中国专利申请, 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域, 具体涉及一种基于 MBIM接口实现通信的方法 及其设备。
背景技术
随着各种便携式设备的不断推广普及和通信技术的不断进步, 各种各样 与之相配合的数据通信方式应运而生, 因而, 在人们日常使用便携式设备的 过程中, 会用到各种各样的移动宽带设备(Mobi le Broadband, 简称, MBB ), 其功能各异。 目前的 MBB设备基于接口与主机进行通信, 在 MBB设备连接到 PC 主机后, 可以上报为 Modem, Ecm, Ndi s等各种各样的网络适配接口, 用户可 以通过这些接口访问无线网络, 进行上网冲浪。 在使用现有的 MBB设备时, 需 要安装由生产厂商提供的特有驱动和应用程序, 安装完驱动和应用程序后, MBB设备从安装模式切换到工作模式, 提供数据、 语音、 短信等业务。
微软公司发布了最新版的操作系统 Windows 8。与以往的 Windows版本不 同, Windows 8 除了传统的 X64/X86 版本之外, 还包含一个全新的分支, 即 Windows RT版本, 支持使用 Arm内核。 使用 Arm内核, 导致现有接口的驱动 程序无法工作, PC主机的上层应用程序无法将数据发往 MBB设备, 也无法接 收来自 MBB设备返回的数据。 至此, 如何使 MBB设备与安装有 Windows 8操 作系统的设备进行数据交互成为有待解决的问题。 发明内容
本发明实施例提供了一种基于 MBIM接口实现通信的方法及其设备, 无需 额外安装驱动, 实现在 Windows 8 系统上主机与 MBB设备进行扩展服务的信 息交互。
第一方面,提供一种基于 MBIM接口实现通信的移动宽带 MBB设备,所述 MBB 设备包括: 接收模块, 用于接收主机通过映射的 MBIM接口发送的服务查询请 求消息; MBIM处理模块, 用于解析所述服务查询请求消息, 获取所述服务查 询请求; 发送模块, 根据所述服务查询请求, 上报所述 MBB设备支持的扩展服 务类别给所述主机, 以使所述主机与所述 MBB设备通过所述 MB IM接口进行扩展 服务的信息交互, 其中, 所述扩展服务类别包括收发 AT命令、 固件升级或输 出 MBB设备状态的至少之一。
在第一方面的第一种可能的实现方式中, 所述 MBB设备还包括 AT命令处 理模块, 当所述扩展服务类别包括收发 AT命令时, 所述接收模块, 通过所述 MBB设备的控制通道接收所述主机发送的 AT命令数据包; 所述 MBIM处理模 块, 解析所述 AT命令数据包获取 AT命令; 所述 AT命令处理模块, 处理所 述 AT命令,产生所述 AT命令的处理结果,并发送给所述所述 MBIM处理模块, 使所述 MBIM处理模块封装所述 AT命令的处理结果; 所述发送模块, 通过所 述 MBB设备的控制通道返回封装的所述 AT命令的处理结果给所述主机。
在第一方面的第二种可能的实现方式中, 所述 MBB设备还包括 AT命令处 理模块, 当所述扩展服务类别包括收发 AT命令时, 所述接收模块, 通过所述 MBB设备的数据通道接收所述主机发送的 AT命令数据包,所述 AT命令数据包 的格式为设备服务码流格式; 所述 MBIM处理模块, 解析所述 AT命令数据包, 获取 AT命令; 所述 AT命令处理模块, 处理所述 AT命令, 产生所述 AT命令 的处理结果; 所述 MBIM处理模块, 封装所述 AT命令的处理结果为设备服务 码流格式的数据包; 所述发送模块, 通过所述 MBB设备的数据通道返回所述 AT命令处理结果的数据包给所述主机。
在第一方面的第三种可能的实现方式中, 所述 MBB设备还包括固件升级 模块, 当所述扩展服务类别包括固件升级时, 所述接收模块,通过所述 MBB设 备的数据通道接收所述固件升级的数据包, 所述固件升级的数据包的格式为 设备服务码流格式; 所述 MBIM处理模块, 解析所述固件升级的数据包, 获取 所述固件升级数据; 所述固件升级模块根据所述固件升级数据升级所述 MBB 设备的固件版本。
在第一方面的第四种可能的实现方式中, 所述 MBB设备还包括设备状态 输出模块, 当所述扩展服务类别包括 MBB设备状态输出时, 所述接收模块, 通过所述 MBB设备的控制通道接收所述主机发送的 MBB设备状态输出的服务 请求;所述设备状态输出模块,输出所述 MBB设备状态的 Log数据;所述 MBIM 处理模块, 封装所述 Log数据为设备服务码流格式的数据包; 所述发送模块, 通过所述 MBB设备的数据通道返回所述 Log数据的数据包给所述主机。
第二方面, 提供一种基于 MBIM接口实现通信的主机, 所述主机包括: 传输模块, 通过映射的 MBIM接口发送服务查询请求消息给移动宽带 MBB设 备, 接收所述 MBB设备返回的所述 MBB设备支持的扩展服务类别, 其中, 所述 扩展服务类别包括收发 AT命令、 固件升级或 MBB设备状态输出的至少之一; MBIM接口模块, 用于根据所述扩展服务类别通过所述 MBIM接口与所述 MBB设备 进行扩展服务的信息交互。
在第二方面的第一种可能的实现方式中, 所述扩展服务类别包括收发 AT 命令时, 所述 MBIM接口模块, 封装所述 AT命令为命令标识 CID格式的 AT 命令数据包, 通过所述 MBIM接口的控制通道发送所述 AT命令数据包; 所述 MBIM接口模块,还通过所述 MBIM接口的控制通道接收所述 MBB设备上报的所 述 AT命令的处理结果的 CID数据包; 解析所述 AT命令的处理结果的 CID数 据包, 获取所述 AT命令的处理结果。
在第二方面的第二种可能的实现方式中, 所述扩展服务类别包括收发 AT 命令时, 所述 MBIM接口模块, 封装所述 AT命令为设备服务码流格式的 AT命 令数据包,通过所述 MBIM接口的数据通道发送所述 AT命令数据包给所述 MBB 设备; 通过所述 MBIM接口的数据通道接收所述 MBB设备上报的所述 AT命令 的处理结果的数据包; 解析所述 AT命令的处理结果的数据包, 获取所述 AT 命令的处理结果。
在第二方面的第三种可能的实现方式中, 当所述扩展服务类别包括固件 升级时, 所述 MBIM接口模块, 封装所述固件升级数据为设备服务码流格式的 固件升级数据包; 通过所述 MBIM接口的数据通道发送所述固件升级数据包给 所述 MBB设备, 以使所述 MBB设备根据所述固件升级数据升级固件版本。
在第二方面的第四种可能的实现方式中, 当所述扩展服务类别 MBB设备 状态输出时, 所述 MBIM接口模块, 通过所述 MBIM接口的控制通道发送 MBB 设备状态输出的服务请求给所述 MBB设备; 通过所述 MBIM接口的数据通道接 收 MBB设备状态输出的 Log数据包, 所述 Log数据包的格式为设备服务码流 格式; 解析所述 Log数据包, 获取 Log数据。
第三方面, 提供一种基于 MBIM接口实现通信的方法, 所述方法包括: 移 动宽带 MBB设备接收主机通过映射的 MBIM接口发送的服务查询请求消息; 解 析所述服务查询请求消息, 获取所述服务查询请求; 根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给所述主机,以使所述主机与所述 MBB 设备通过所述 MBIM接口进行扩展服务的信息交互, 其中, 所述扩展服务类别 包括收发 AT命令、 固件升级或输出 MBB设备状态的至少之一。
在第三方面的第一种可能的实现方式中, 所述扩展服务类别包括收发 AT 命令时, 根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给 所述主机, 以使所述主机与所述 MBB设备通过所述 MBIM接口进行扩展服务的 信息交互包括: 通过所述 MBB设备的控制通道接收所述主机发送的 AT命令数 据包; 解析所述 AT命令数据包获取 AT命令; 处理所述 AT命令, 产生所述 AT命令的处理结果; 封装所述 AT命令的处理结果为命令标示符 CID格式; 通 过所述 MBB设备的控制通道返回封装的所述 AT命令的处理结果给所述主机。
在第三方面的第二种可能的实现方式中, 所述扩展服务类别包括收发 AT 命令时, 根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给 所述主机, 以使所述主机与所述 MBB设备通过所述 MBIM接口进行扩展服务的 信息交互包括: 通过所述 MBB设备的数据通道接收所述主机发送的 AT命令数 据包, 所述 AT命令数据包的格式为设备服务码流格式; 解析所述 AT命令数 据包, 获取 AT命令; 处理所述 AT命令, 产生所述 AT命令的处理结果; 封装 所述 AT命令的处理结果为设备服务码流格式的数据包; 通过所述 MBB设备的 数据通道返回所述 AT命令处理结果数据包给所述主机。
在第三方面的第三种可能的实现方式中, 所述扩展服务类别包括固件升 级时, 根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给所 述主机时, 以使所述主机与所述 MBB设备通过所述 MBIM接口进行扩展服务的 信息交互包括: 通过所述 MBB设备的数据通道接收所述固件升级的数据包, 所述固件升级的数据包的格式为设备服务码流格式; 解析所述固件升级的数 据包, 获取所述固件升级数据; 根据所述固件升级数据升级所述 MBB设备的 固件版本。
在第三方面的第四种可能的实现方式中, 所述扩展服务类别包括 MBB设 备状态输出, 根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类 别给所述主机时, 以使所述主机与所述 MBB设备通过所述 MBIM接口进行扩展 服务的信息交互包括:通过所述 MBB设备的控制通道接收所述主机发送的 MBB 设备状态输出的服务请求; 封装 MBB设备状态输出的 Log数据为设备服务码 流格式的数据包; 通过所述 MBB设备的数据通道返回所述 Log数据的数据包 给所述主机。
在第三方面的第五种可能的实现方式中, 根据所述服务查询请求, 上报 所述 MBB设备支持的扩展服务类别给所述主机之前, 包括: 通过所述 MBB设 备的控制通道接收主机发送的开启数据通道的服务请求; 根据所述开启数据 通道的服务请求开启所述数据通道; 通过所述 MBB设备的控制通道返回开启 所述数据通道的响应消息给所述主机。
结合第三方面或上述任一种可能的实现方式, 在第六种可能的实现方式中, 所述 MBB设备接收主机通过映射的 MBIM接口发送的服务查询请求消息, 包括: 所述移动宽带 MBB设备通过所述 MBB设备的控制通道接收主机通过映射的 MB IM 接口发送的服务查询请求消息。
结合第三方面或上述任一可能的实现方式, 在第七种可能的实现方式中, 所 述根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给所述主 机, 包括: 根据所述服务查询请求,通过所述 MBB设备的控制通道上报所述 MBB 设备支持的扩展服务类别给所述主机。
结合第三方面或上述任一可能的实现方式, 在第八种可能的实现方式中, 所述根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给所述主 机, 包括: 根据所述服务查询请求,通过所述 MBB设备的控制通道上报所述 MBB 设备支持的扩展服务类别的通用识别码而 ID给所述主机, 以使所述主机识别 所述 MBB设备支持的扩展服务类别;或者根据所述服务查询请求,通过所述 MBB 设备的控制通道上报所述 MBB设备支持的扩展服务类别的而 ID和标准服务类 别的而 ID给所述主机, 以使所述主机识别所述 MBB设备支持的扩展服务类别和 标准服务类别。
第四方面, 提供一种基于 MBIM接口实现通信的方法, 所述方法包括: 通过映射的 MBIM接口发送服务查询请求消息给移动宽带 MBB设备; 接收所 述 MBB设备返回的所述 MBB设备支持的扩展服务类别, 其中, 所述扩展服务类 别包括收发 AT命令、 固件升级或 MBB设备状态输出的至少之一; 根据所述扩展 服务类别通过所述 MBIM接口与所述 MBB设备进行扩展服务的信息交互。
在第四方面的第一种可能的实现方式中, 所述扩展服务类别包括收发 AT 命令时, 根据所述扩展服务类别通过所述 MBIM接口与所述 MBB设备进行扩展 服务的信息交互包括: 封装所述 AT命令为命令标识 CID格式的 AT命令数据 包; 通过所述 MBIM接口的控制通道发送所述 AT命令数据包给所述 MBB设备; 通过所述 MBIM接口的控制通道接收所述 MBB设备上报的所述 AT命令的处理 结果的 CID数据包; 解析所述 AT命令的处理结果的 CID数据包, 获取所述 AT 命令的处理结果。
在第四方面的第二种可能的实现方式中, 所述扩展服务类别包括收发 AT 命令时, 根据所述扩展服务类别通过所述 MBIM接口与所述 MBB设备进行扩展 服务的信息交互包括: 封装所述 AT命令为设备服务码流格式的 AT命令数据 包; 通过所述 MBIM接口的数据通道发送所述 AT命令数据包给所述 MBB设备; 通过所述 MBIM接口的数据通道接收所述 MBB设备上报的所述 AT命令的处理 结果的数据包; 解析所述 AT命令的处理结果的数据包, 获取所述 AT命令的 处理结果。
在第四方面的第三种可能的实现方式中, 当所述扩展服务类别包括固件 升级时, 根据所述扩展服务类别通过所述 MBIM接口与所述 MBB设备进行扩展 服务的信息交互包括: 封装所述固件升级数据为设备服务码流格式的固件升 级数据包;通过所述 MBIM接口的数据通道发送所述固件升级数据包给所述 MBB 设备, 以使所述 MBB设备根据所述固件升级数据升级固件版本。
在第四方面的第四种可能的实现方式中, 当所述扩展服务类别包括 MBB 设备状态输出时, 根据所述扩展服务类别通过所述 MBIM接口与所述 MBB设备 进行扩展服务的信息交互包括: 通过所述 MBIM接口的控制通道发送 MBB设备 状态输出的服务请求给所述 MBB设备;通过所述 MBIM接口的数据通道接收 MBB 设备状态输出的 Log数据包, 所述 Log数据包的格式为设备服务码流格式; 解析所述 Log数据包, 获取 Log数据。
在第四方面的第五种可能的实现方式中, 所述接收所述 MBB设备返回的 所述 MBB设备支持的扩展服务类别, 之前, 包括: 通过所述 MBIM接口的控制 通道发送开启数据通道的服务请求给所述 MBB设备; 通过所述 MBIM接口的控 制通道接收所述 MBB设备开启所述数据通道的响应消息; 根据所述响应消息 通过所述数据通道进行扩展服务的数据传输。
结合第四方面或上述任一可能的实现方式, 在第六种可能的实现方式中, 所述通过映射的 MBIM接口发送服务查询请求消息给移动宽带 MBB设备, 包括: 通过映射的 MBIM接口的控制通道发送服务查询请求消息给所述 MBB设备。
结合第四方面或上述任一可能的实现方式, 在第七种可能的实现方式中, 所述接收所述 MBB设备返回的所述 MBB设备支持的扩展服务类别, 包括, 通过 所述 MBIM接口的控制通道接收所述 MBB设备返回的所述 MBB设备支持的扩展服 务类别。
结合第四方面或上述任一可能的实现方式, 在第七种可能的实现方式中, 所述接收所述 MBB设备返回的所述 MBB设备支持的扩展服务类别, 包括, 接收 所述 MBB设备返回的所述 MBB设备支持的扩展服务类别的通用识别码而 ID, 根 据所述而 ID识别所述 MBB设备支持的扩展服务类别; 或者, 接收所述 MBB设备 返回的所述 MBB设备支持的扩展服务类别的而 ID和标准服务类别的 UUID, 从而 识别所述 MBB设备支持的扩展服务类别和标准服务类别。
本发明实施例的基于 MBIM接口实现通信的方法, 通过上报所述 MBB设备 支持的扩展服务类别给所述主机, 以使所述主机通过映射的 MBIM接口与所述 MBB设备进行扩展服务的信息交互,实现主机与 MBB设备的扩展服务的数据交 互。 附图说明
为了更清楚地说明本发明实施例的技术方案, 下面将对本发明实施例中 所需要使用的附图作简单地介绍, 显而易见地, 下面所描述的附图仅仅是本 发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动的 前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明实施例一种基于 MBIM接口实现通信的系统结构示意图; 图 2为本发明实施例一种基于 MBIM接口实现通信的系统交互示意图; 图 3为本发明实施例基于 MBIM接口实现收发 AT命令的信息交互示意图; 图 4为本发明另一实施例基于 MBIM实现收发 AT命令的系统信息交互示 意图; 图 5 为本发明实施例基于 MBIM接口实现固件升级的系统信息交互示意 图;
图 6为本发明实施例基于 MBIM接口实现设备状态输出的系统信息交互示 意图;
图 7为本发明实施例的 MBB设备基于 MBIM接口实现通信的方法流程图; 图 8为本发明实施例的 MBB设备基于 MBIM接口实现收发 AT命令的方法 流程图;
图 9为本发明另一实施例的 MBB设备基于 MBIM接口实现收发 AT命令的 方法流程图;
图 10为本发明实施例的 MBB设备基于 MBIM接口实现固件升级的流程图; 图 11为本发明实施例 MBB设备基于 MBIM接口实现 MBB设备状态输出的 流程图;
图 12为本发明实施例主机基于 MBIM接口实现通信的流程图;
图 13为本发明实施例的主机基于 MBIM接口实现收发 AT命令的流程图; 图 14为本发明另一实施例的主机基于 MBIM接口实现收发 AT命令的的流 程图;
图 15为本发明实施例的主机基于 MBIM实现固件升级的流程图; 图 16为本发明实施例的主机基于 MBIM实现 MBB设备状态输出的的流程 图;
图 17为本发明实施例基于 MBIM接口实现通信的移动宽带 MBB设备的框 架示意图;
图 18为本发明实施例基于 MBIM接口实现通信的主机的框架示意图; 图 19为本发明实施例基于 MBIM接口实现通信的 MBB设备结构示意图; 图 20发明实施例基于 MBIM接口实现通信的主机结构示意图。
具体实施方式 下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例是本发明的一部分实施例, 而不 是全部实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做出创 造性劳动的前提下所获得的所有其他实施例, 都应属于本发明保护的范围。
图 1为本发明实施例一种基于 MBIM接口实现通信的系统结构示意图。 系 统 300可以为移动宽带(Mobi le Broadband, 简称, MBB )设备 100和主机 200 进行信息交互的系统。该主机 200可以是个人计算机设备、手机、 PAD( Por table Device , 便携式设备)、 穿戴设备( i wa tch )或服务器等通信设备等, 所述 MBB 设备 100可以为数据卡等。 本发明实施例的系统 300以 MBB设备 100和主机 200进行信息交互为例进行说明。所述 MBB设备 100通过通用串行总线 USB接 口与所述主机 200连接, 从而使所述 MBB设备 100与所述主机 200进行通信。
本实施例中, 该主机安装了支持 MBIM ( Mobi le Broadband Interface Mode l , 简称 MBIM )协议的操作系统, 如, windows 8 操作系统, 以安装了 windows 8 操作系统的主机 200 为例, 对本发明实施例的系统、 方法及设备 进行描述。 但并不限定安装 windows 8操作系统的主机, 只要支持 MBIM协议 的操作系统都适用于本发明实施例。
本发明实施例中涉及的 MBB设备, 是指釆用 MBIM协议通信的设备。 MBIM 协议是一种网络适配器的设备接口规范, 釆用 MBIM协议的 MBB设备与主机之 间, 可以通过 USB接口通道以 MBIM协议规定的数据格式进行通信; 其中, 该 USB接口通道可以包括支持 MBIM协议的控制通道和数据通道, 该控制通道通 常在主机与 MBB设备之间传输命令标识( Command Ident if ier , 简称 CID )数 据包, 该数据通道通常在主机与 MBB设备之间传输设备服务码流(Device Service Stream, 简称 DSS )格式或者 ( device servi ce s tream, 简称 ds s ) 格式的数据包。 该设备服务码流数据包一般可以以 DSS或 ds s标识开头, 通 过 USB接口的数据通道, 发送非标准类别的用户自定义数据。 本发明实施例 中, 所述主机与所述 MBB设备之间以通过 USB接口的数据通道传输数据的格 式为 DSS 为例进行说明, 但并不对本发明实施例的保护范围进行限定。 可以 理解的, 所述主机与所述 MBB设备之间以通过 USB接口的数据通道传输数据 的格式也可以为 ds s格式。
当该 MBB设备 100与该主机 200连接, 如: 所述 MBB设备 100插入该主 机 200的 USB接口, 该主机 200向该 MBB设备 100发送 USB描述符请求。 该 MBB设备 100根据该 USB描述符请求,向该主机 200上报与该 MBB设备 100对 应的设备、 接口、 端点的描述符信息, 指示该 MBB设备 100支持 MBIM协议。 该主机 200根据该 MBB设备 100上报的该描述符信息, 映射一个与该描述符 信息匹配的 MBIM接口, 通过该 MBIM接口实现与该 MBB设备的自动识别和信 息交互。
图 2为本发明实施例一种基于 MBIM接口实现通信的系统交互示意图。 步骤 10: 该主机 200通过映射的 MBIM接口发送服务查询请求消息给该 MBB设备 100。
例如, 所述主机 200 可以通过所述 MBIM 接口的控制通道发送名为 "MBIM_CID_DEVICE_SERVICES"服务查询请求消息给所述 MBB设备 100 , 以查 询所述 MBB设备 100所支持的扩展服务类别, 也可以查询所述 MBB设备 100 所支持的扩展服务类别及这些扩展类别类所对应的功能值。
可以理解的是, 所述服务查询请求消息的格式可以为命令标识(Command Ident if ier , 简称 CID )格式。 用户使用该主机的操作系统自带的界面 UI, 对该 MBB设备进行相关的设置, 根据用户操作, 主机应用程序会调用操作系 统的移动宽带网络接口函数 ( Interface Mobi le Broadband Network , 简称, IMbn ) API, 该 MBIM接口向该 MBB设备 100发送指令或数据。 其中, 该主机 还包括该操作系统自带的网络适配驱动, 通过该网络适配驱动实现该 MB IM接 口与该主机应用程序之间的通信。
可选的是, 该主机 200也可以通过所述 MBIM接口的数据通道发送服务查 询请求消息给所述 MBB设备 100,所述服务查询请求消息的格式可以为 DSS格 式。
步骤 20:所述 MBB设备 1 00接收所述主机通过映射的 MBIM接口发送的服 务查询请求消息。
本实施例中, 所述 MBB设备 100可以通过所述 MBB设备 100的控制通道 接收所述主机发送的 CID格式的服务查询请求消息。
可选的, 所述 MBB设备 100也可以通过所述 MBB设备 100的数据通道接 收所述主机发送的 DSS格式的服务查询请求消息。
步骤 30: 所述 MBB设备 100解析所述服务查询请求消息, 获取服务查询 请求。
本实施例中, 所述 MBB设备 100解析 CID格式的所述服务查询请求消息, 获取所述服务查询请求,所述查询请求的内容可以包括查询所述 MBB设备 100 所支持的扩展服务类别, 也可以包括查询所述 MBB设备 100所支持的扩展服 务类别或标准服务类别及这些服务类别所对应的功能值。
步骤 40: 所述 MBB设备 100根据所述服务查询请求, 上报所述 MBB设备 1 00支持的扩展服务类别给所述主机 200, 以使所述主机 200与所述 MBB设备 1 00通过所述 MBIM接口进行扩展服务的信息交互, 其中, 所述扩展服务类别 包括收发 AT命令 Vendor AT、 固件升级 F i rmware Upda te或输出 MBB设备状 态 Log Output的至少之一。
本发明实施例的基于 MBIM接口实现通信的系统, 通过上报所述 MBB设备 支持的扩展服务类别给所述主机, 以使所述主机通过映射的 MBIM接口与所述 MBB设备进行扩展服务的信息交互,实现主机与 MBB设备的扩展服务的数据交 互。
其中, 所述 MBB设备 1 00, 以通过所述 MBB设备 1 00的控制通道上报所述 扩展服务类别给所述主机 200为例进行说明,并不限定使用所述 MBB设备 100 的控制通道, 还可以是所述 MBB设备 100的数据通道。
所述 MBB设备 100根据所述服务查询请求, 上报所述 MBB设备支持的扩 展服务类别给所述主机, 包括:
所述 MBB设备 100根据所述服务查询请求, 可以通过所述 MBB设备的控 制通道上报所述 MBB设备支持的扩展服务类别的通用识别码(universa l ly unique ident if ier , 简称 UUID)给所述主机, 以使所述主机识别所述 MBB设 备支持的扩展服务类别。
可选的, 所述 MBB设备 100根据所述服务查询请求, 还可以通过所述 MBB 设备 100的控制通道上报所述 MBB设备 100支持的扩展服务类别的 UUID和标 准服务类别的而 ID给所述主机 200 ,以使所述主机 200识别所述 MBB设备 100 支持的扩展服务类别和标准服务类别。 其中, 所述标准服务类别可以为短消 息、 电话本、 SIM卡鉴权管理、 联网 /断网等功能。
可选的, 所述 MBB设备 100根据所述服务查询请求, 还可以通过所述 MBB 设备 100的控制通道上报所述 MBB设备 100支持的扩展服务类别的而 ID及所 述扩展服务类别对应的功能值给所述主机 200。
可选的, 所述 MBB设备 100根据所述服务查询请求, 还可以通过所述 MBB 设备 100的控制通道上报所述 MBB设备 100支持的扩展服务类别的 UUID、 标 准服务类别而 ID及所述扩展服务类别对应的功能值给所述主机 200。
可以理解的, 所述 MBB设备 100还可以通过所述控制通道上报给所述主 机 200 的扩展服务类别可以是一种, 也可以是多种, 本发明实施例对此不做 限定。
本发明实施例中, 所述 MBB设备 100 可以预先定义所述扩展服务类别 而 ID 、 标准服务类别 UUID, 和 /或该扩展服务类别对应的功能值, 所述预先 定义可以为设备制造商或运营商出厂或出售前进行的预先设定。
例如, 所述扩展服务类别为收发 AT命令时, 所述 MBB设备 100 自定义一 个名为 "Vendor AT" 的收发 AT命令的扩展服务类别, 定义所述收发 AT命令 扩展服务类别的 UUID可以为 UUID_VENDOR_AT,并定义 "MBIM_CID_VENDOR_AT,, 的功能值来代表 "Vendor AT" 的实际功能。 所述扩展服务类别为固件升级时, 所述 MBB设备 100 自定义一个名为 "Fi r歸 are Upda te" 的固件升级的扩展服务类别, 定义所述固件升级的识别 码 UUID可以为 UUID_FIRMWARE_ UPDATE。
所述扩展服务类别为输出 MBB设备状态时, 所述 MBB设备 100 自定义一 个名为 "Log Output" 的输出 MBB设备状态的扩展服务类别, 定义所述输出 MBB设备状态的识别码 UUID可以为 UU ID_ L0G_ OUTPUT。
进一步的或可选的, 所述 MBB设备 100还可以添加与该扩展服务类别对 应的业务功能模块, 以执行该扩展服务类别对应的扩展服务功能, 该些业务 功能模块集成于该 MBB设备 100。 可以理解的, 与该扩展服务类别对应的业务 功能模块也可以为独立于所述 MBB设备 100的通信设备, 对应该业务功能模 块的独立的通信设备可以与该 MBB设备 100进行信息交互。
其中, 该业务功能模块可以包括 AT命令处理模块、 固件升级模块、 输出 MBB设备状态模块等。 本发明实施例对该业务功能模块种类及功能并不限定, 根据设备运营商或制造商的需要定制。
图 3为本发明实施例基于 MBIM接口实现收发 AT命令的信息交互示意图。 可选的, 所述扩展服务类别包括收发 AT命令时, 所述 MBB设备 100根据 所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给所述主机, 以 使所述主机 200与所述 MBB设备 100进行扩展服务的信息交互包括:
步骤 21 : 所述主机 200确定所述扩展服务类别为收发 AT命令, 则通过所 述 MB IM接口的控制通道发送 AT命令 C I D数据包给所述 MBB设备 100。
例如, 所述主机 200的应用程序调用移动宽带网络接口函数 IMbn API , 打开收发 AT命令服务, 其中, 所述应用程序为对应所述扩展服务类别的控制 指令集。
进一步的, 所述应用程序调用所述 IMbn API , 将 AT命令的字符串发送给 所述 MB IM接口。
进一步的, 所述 MBIM接口的接口适配驱动将所述 AT命令的字符串可以 封装为 AT命令 CID数据包, 并发送给所述 MBB设备 100
所述 AT命令 C I D数据包可以具有以下格式:
9X090909Q3 UUID —VENDOR— AT CID— VENDOR— AT AT命 ' * -^*付串
! 4'.;·· Ίί) : ϋ:、
(16子节, !1 {![|: AT+COPS? 步骤 12: 所述 MBB设备 100通过所述 MBB设备的控制通道接收所述主机 200发送的 AT命令 CI D数据包。
步骤 23: 所述 MBB设备 100解析所述 AT命令 C I D数据包获取所述 AT命 步骤 24 : 所述 MBB设备 100进一步处理所述 AT命令, 产生所述 AT命令 的处理结果。
步骤 25 : 所述 MBB设备 100可以通过所述 MBB设备 100的控制通道返回 所述 AT命令的处理结果的 C ID数据包给所述主机 200。
其中,所述 MBB设备 100返回所述 AT命令 C I D数据包可以具有以下格式: 步骤 26 :所述主机 200通过所述 MBIM接口的控制通道接收所述 MBB设备 隱議 003ί¾χ80000007 UUID VENDOR 國■ 誦; VENDOR AT ΑΤίί:
義讀義 I 漏國 (4 i
1 00上报的所述 AT命令的处理结果的 C I D数据包。
步骤 27 :所述主机 200解析所述 AT命令的处理结果的 CID数据包获取所 述 AT命令的处理结果。
例如, 所述主机 200的 MBIM接口解析所述 AT命令的处理结果的 CI D数 据包获取所述 AT命令的处理结果, 所述 MBIM接口通过所述 IMbn AP I将所述 AT命令的处理结果发送给所述应用程序, 完成 AT命令处理。
图 4为本发明另一实施例基于 MBIM实现收发 AT命令的系统信息交互示 可选的, 所述扩展服务类别包括收发 AT命令时, 所述 MBB设备 100根据 所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给所述主机, 以 使所述主机 200与所述 MBB设备 100进行扩展服务的信息交互, 可以包括: 步骤 31 : 所述主机 200确定所述扩展服务类别为收发 AT命令, 通过所述 MBIM接口的数据通道发送 DSS格式的 AT命令数据包给所述 MBB设备 100。
具体地, 步骤 31包括:
步骤 311 : 所述主机 200 的应用程序根据所述扩展服务类别, 调用所述 IMbn API , 打开收发 AT命令服务;
步骤 312: 所述应用程序调用所述 IMbn API发送开启设备服务码流 DSS 服务的请求消息, 即 MBIM_CID_DSS_CO匪 ECT, 给所述 MBIM接口;
步骤 313: 所述主机 200通过所述 MBIM接口的控制通道发送所述开启收 发 AT命令的 DSS服务的请求消息到所述 MBB设备 100;
步骤 314:所述 MBB设备 100通过所述 MBB设备 100的控制通道接收所述 主机 200发送的开启所述 DSS服务的请求消息。
步骤 315: 所述 MBB设备 100开启所述 DSS服务, 通过所述 MBB设备的控 制通道返回开启所述 DSS服务的响应消息给所述主机 200。
步骤 316: 所述主机 200通过所述 MBIM接口的控制通道接收所述 DSS服 务的响应消息, 所述 MBIM接口通过所述 IMbn API发送所述响应消息给所述 应用程序。
步骤 317: 所述应用程序调用所述 IMbn API, 将 AT命令的字符串发送给 所述 MBIM接口。
步骤 318:所述 MBIM接口的接口适配驱动将所述 AT命令的字符串封装为 DSS数据包, 通过所述 MBIM接口的数据通道发往所述 MBB设备 100。
步骤 32: 所述 MBB设备 100通过所述 MBB设备的数据通道接收主机发送 的所述 AT命令 DSS数据包, 所述 AT命令 DSS数据包的格式为 DSS格式。
步骤 33: 所述 MBB设备 100解析所述 AT命令 DSS数据包获取所述 At命 令。
步骤 34 : 所述 MBB设备 100处理所述 AT命令, 产生所述 AT命令的处理 结果。 步骤 35: 所述 MBB设备 100封装所述 AT命令的处理结果为 DSS数据包, 通过所述 MBB设备 100的数据通道返回所述 AT命令处理结果的 DSS数据包给 所述主机 200。
步骤 36: 所述主机 200的 MB IM接口通过所述主机 200的数据通道接收 所述 MBB设备 100返回的所述 AT命令的处理结果的 DSS数据包。
步骤 37: 所述 MBIM接口解析所述 AT命令的处理结果的 DSS数据包, 获 取所述 AT命令的处理结果。
步骤 38: 所述 MBIM接口通过所述 IMbn API发送所述 AT命令的处理结 果给所述应用程序, 完成 AT命令处理。
其中, 所述主机 200与所述 MBB设备 100通过数据通道发送 AT命令的数 据时, 所述 AT命令的 DSS数据包可以具有如下标准格式:
Figure imgf000018_0001
Figure imgf000018_0002
图 5 为本发明实施例基于 MBIM接口实现固件升级的系统信息交互示意 图。
可选的, 所述扩展服务类别包括固件升级时, 根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给所述主机时, 以使所述主机与所述 MBB设备通过所述 MBIM接口进行扩展服务的信息交互包括:
步骤 51:所述主机 200确定所述扩展服务类别为固件升级,通过所述 MBIM 接口的数据通道发送 DSS格式的固件升级数据包给所述 MBB设备 100。
具体地, 步骤 51包括:
步骤 511: 所述主机 200的应用程序根据所述扩展服务类别, 调用 IMbn API, 打开固件升级服务;
其中, 所述应用程序可以是所述 MBB设备提供的, 或者从服务提供商获 得的安装程序, 或者所述主机自带的默认程序。
步骤 512: 所述应用程序调用所述 IMbn API发送开启设备服务码流 DSS 服务的请求消息, 即 MBIM_CID_DSS_C0匪 ECT, 给所述 MBIM接口;
步骤 513:所述 MBIM接口通过所述 MBIM接口的控制通道发送所述开启固 件升级的 DSS服务的请求消息给所述 MBB设备 100;
步骤 514:所述 MBB设备 100通过所述 MBB设备 100的控制通道接收所述 主机 200发送的开启所述固件升级的 DSS服务请求消息。
步骤 515: 所述 MBB设备 100开启所述固件升级的 DSS服务, 通过所述 MBB设备 100的控制通道返回开启所述固件升级的 DSS服务的响应消息给所述 主机 200。
步骤 516: 所述主机 200通过所述 MBIM接口的控制通道接收所述固件升 级的 DSS服务的响应消息, 并通过所述 IMbn API发送所述响应消息给所述应 用程序。
步骤 517: 所述应用程序调用所述 IMbn API , 将固件升级的数据发送给 所述 MBIM接口。
步骤 518: 所述 MBIM接口的接口适配驱动将所述固件升级的数据封装为 DSS格式的数据包, 通过所述 MBIM接口的数据通道发送给所述 MBB设备 100。
其中, 所述主机 200通过所述 MBIM接口的数据通道发送固件升级的数据 时, 所述固件升级数据的 DSS数据包可以具有如下标准格式:
Figure imgf000019_0001
Figure imgf000019_0002
步骤 52: 所述 ΜΒΒ设备 100通过所述 ΜΒΒ设备的数据通道接收主机发送 的所述固件升级的 DSS数据包。
步骤 53: 所述 ΜΒΒ设备 100解析所述固件升级的 DSS数据包获取所述固 件升级数据, 升级所述 ΜΒΒ设备 100的固件版本。 图 6为本发明实施例基于 MBIM接口实现设备状态输出的系统信息交互示 意图。
步骤 61 : 所述主机 200确定所述扩展服务类别为输出 MBB设备状态, 通 过所述 MBIM接口的控制通道发送 MBB设备状态输出的服务请求给所述 MBB设 备 100。
所述步骤 61包括: 步骤 611 : 所述主机 200的应用程序根据所述扩展服 务类别, 调用 IMbn API , 打开 MBB设备状态输出的服务。
步骤 612 : 所述应用程序调用应用程序接口 IMbn AP I发送开启所述 MBB 设备状态输出的 DSS服务的请求消息给 MBIM接口。
步骤 61 3: 所述主机 200通过所述 MBIM接口的控制通道发送所述开启所 述 MBB设备状态输出的 DSS服务的请求消息给所述 MBB设备 100。
步骤 614 : 所述 MBB设备 100通过 MBB设备 1 00的控制通道接收所述主 机 200发送的开启所述 MBB设备状态输出的 DSS服务请求。
步骤 615 : 所述 MBB设备 100开启所述 MBB设备状态输出的 DSS服务, 通 过所述 MBB设备的控制通道返回开启所述 MBB设备状态输出的 DSS服务的响 应消息给所述主机 200。
步骤 616 : 所述主机 200通过所述 MBIM接口的控制通道接收所述 MBB设 备状态输出的 DSS服务的响应消息, 所述 MBIM接口通过所述 IMbn API发送 所述响应消息给所述应用程序。
步骤 62 : 所述 MBB设备 100封装所述 MBB设备状态的 Log数据为 DSS数 据包。
步骤 63: 所述 MBB设备 100通过所述 MBB设备 100的数据通道返回所述 Log数据的 DSS数据包给所述主机 200。
步骤 64 :所述主机 200通过所述 MBIM接口的数据通道接收所述 Log数据 的 DSS数据包,
步骤 65 : 所述主机 200解析所述 Log数据的 DSS数据包, 获取所述 Log 数据, 并通过所述 IMbn API发送给所述应用程序。
其中,所述 MBB设备 100与所述主机 200进行交互的所述 Log数据的 DSS 数据包, 可以具有如下格式:
Figure imgf000021_0001
可以理解的是, 本发明实施例的 MBB设备 100可以通过所述 MBB设备的 控制通道发送数据量较小的业务数据, 如, 收发 AT命令, 可以通过所述 MBB 设备的数据通道发送数据量较大的业务数据, 如, 固件升级数据, 以提高 MBB 设备 100的传输效率。
本发明实施例的基于 MBIM接口实现通信的系统, 通过上报所述 MBB设备 支持的扩展服务类别给所述主机, 以使所述主机通过映射的 MBIM接口与所述 MBB设备进行扩展服务的信息交互,实现主机与 MBB设备的扩展服务的数据交 互。
图 7为本发明实施例的 MBB设备基于 MBIM接口实现通信的方法流程图。 71: 移动宽带 MBB设备接收主机通过映射的 MBIM接口发送的服务查询请 求消息;
72: 解析所述服务查询请求消息, 获取所述服务查询请求;
73: 根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类别给 所述主机, 以使所述主机与所述 MBB设备通过所述 MBIM接口进行扩展服务的 信息交互, 其中, 所述扩展服务类别包括收发 AT命令、 固件升级或输出 MBB 设备状态的至少之一。
本发明实施例的基于 MBIM接口实现通信的 MBB设备, 通过上报所述 MBB 设备支持的扩展服务类别给所述主机, 以使所述主机通过映射的 MBIM接口与 所述 MBB设备进行扩展服务的信息交互, 实现主机与 MBB设备的扩展服务的 数据交互。
图 8为本发明实施例的 MBB设备基于 MBIM接口实现收发 AT命令的方法 流程图。
当所述扩展服务类别包括收发 AT命令时, 所述 MBB设备 100根据所述服 务查询请求, 上报所述 MBB设备 100支持的扩展服务类别给所述主机, 以使 所述主机 200与所述 MBB设备 100通过所述 MBIM接口进行扩展服务的信息交 互包括:
步骤 731 :所述 MBB设备 100通过所述 MBB设备 100的控制通道接收所述 主机 200发送的 AT命令 CID数据包;
步骤 732: 所述 MBB设备 100解析所述 AT命令 C I D数据包获取 AT命令; 步骤 733: 所述 MBB设备 100处理所述 AT命令, 产生所述 AT命令的处理 结果;
步骤 734:所述 MBB设备 100通过所述 MBB设备 100的控制通道返回所述 AT命令的处理结果给所述主机 200。
图 9为本发明另一实施例的 MBB设备基于 MBIM接口实现收发 AT命令的 方法流程图。
当所述扩展服务类别包括收发 AT命令时, 根据所述服务查询请求, 上报 所述 MBB设备支持的扩展服务类别给所述主机 200,以使所述主机 200与所述 MBB设备 100通过所述 MBIM接口进行扩展服务的信息交互包括:
步骤 741 : 通过所述 MBB设备 100的数据通道接收所述主机 200发送的 AT命令数据包, 所述 AT命令数据包的格式为自定义码流 DSS格式;
步骤 742: 解析所述 AT命令数据包, 获取 AT命令;
步骤 743: 处理所述 AT命令, 产生所述 AT命令的处理结果;
步骤 744: 封装所述 AT命令的处理结果为 DSS数据包;
步骤 745: 通过所述 MBB设备 100的数据通道返回所述 AT命令处理结果 的 DSS数据包给所述主机 200。 图 10为本发明实施例的 MBB设备基于 MBIM接口实现固件升级的流程图。 当所述扩展服务类别包括固件升级时, 根据所述服务查询请求, 上报所 述 MBB设备支持的扩展服务类别给所述主机时, 以使所述主机与所述 MBB设 备通过所述 MBIM接口进行扩展服务的信息交互包括:
步骤 751 : 通过所述 MBB设备的数据通道接收所述固件升级的数据包, 所述固件升级的数据包的格式为设备服务码流 DSS格式;
步骤 752 : 解析所述固件升级的数据包, 获取所述固件升级数据; 步骤 753: 根据所述固件升级数据升级所述 MBB设备的固件版本。
图 11为本发明实施例 MBB设备基于 MBIM接口实现 MBB设备状态输出的 流程图。
当所述扩展服务类别包括 MBB设备状态输出时, 根据所述服务查询请求, 上报所述 MBB设备 1 00支持的扩展服务类别给所述主机 200时, 以使所述主 机 200与所述 MBB设备 100通过所述 MBIM接口进行扩展服务的信息交互包括: 步骤 761 : 通过所述 MBB设备 100的控制通道接收所述主机 200发送的 MBB设备状态输出的服务请求;
步骤 762 :封装 MBB设备状态输出的 Log数据为设备服务码流 DSS格式的 数据包;
步骤 763: 通过所述 MBB设备的数据通道返回所述 Log数据的 DSS格式 数据包给所述主机。
可以理解的是, 本实施例的 MBB设备基于 MBIM接口实现通信的方法, 根 据上述系统实施例实现, 具体实现的步骤请参考上述系统实施例, 此处不再 敷述。
本发明实施例的基于 MBIM接口实现通信的 MBB设备 100 , 通过上报所述 MBB设备支持的扩展服务类别给所述主机, 以使所述主机通过映射的 MBIM接 口与所述 MBB设备进行扩展服务的信息交互, 实现主机与 MBB设备的扩展服 务的数据交互。 图 12为本发明实施例主机基于 MBIM接口实现通信的流程图。
81 :主机 200通过映射的 MBIM接口发送服务查询请求消息给移动宽带 MBB 设备 100。
82: 主机 200接收所述 MBB设备 100返回的所述 MBB设备支持的扩展服 务类别, 其中, 所述扩展服务类别包括收发 AT命令、 固件升级或 MBB设备状 态输出的至少之一。
83: 主机 200根据所述扩展服务类别通过所述 MBIM接口与所述 MBB设备 100进行扩展服务的信息交互。
本发明实施例的基于 MBIM接口实现通信的主机 200 ,通过映射的 MBIM接 口接收 MBB设备返回的扩展服务类别, 根据所述扩展服务类别与所述 MBB设 备进行扩展服服务的通信, 实现主机与 MBB设备的扩展服务的数据交互。
图 13为本发明实施例的主机基于 MBIM接口实现收发 AT命令的流程图。 所述扩展服务类别包括收发 AT命令时, 所述主机 200根据所述扩展服务 类别通过所述 MBIM接口与所述 MBB设备进行扩展服务的信息交互包括:
831: 封装所述 AT命令为命令标识 CID格式的 AT命令数据包;
832: 通过所述 MBIM接口的控制通道发送所述 AT命令数据包给所述 MBB 设备;
833: 通过所述 MBIM接口的控制通道接收所述 MBB设备上报的所述 AT命 令的处理结果的 CID数据包;
834: 解析所述 AT命令的处理结果的 CID数据包, 获取所述 AT命令的处 理结果。
图 14为本发明另一实施例的主机基于 MBIM接口实现收发 AT命令的的流 程图。
可选的, 所述扩展服务类别包括收发 AT命令时, 所述主机 200根据所述 扩展服务类别通过所述 MBIM接口与所述 MBB设备进行扩展服务的信息交互包 括: 841: 封装所述 AT命令为设备服务码流 DSS格式的 AT命令数据包;
842: 通过所述 MBIM接口的数据通道发送 DSS格式的所述 AT命令数据包 给所述 MBB设备 100 ;
843: 通过所述 MBIM接口的数据通道接收所述 MBB设备 100上 的所述 AT命令的处理结果的 DSS数据包;
844: 解析所述 AT命令的处理结果的 DSS数据包, 获取所述 AT命令的处 理结果。
图 15为本发明实施例的主机基于 MBIM实现固件升级的流程图。
当所述扩展服务类别包括固件升级时, 所述主机 200根据所述扩展服务 类别通过所述 MBIM接口与所述 MBB设备 100进行扩展服务的信息交互包括: 851:封装所述固件升级数据为设备服务码流 DSS格式的固件升级数据包; 852: 通过所述 MBIM接口的数据通道发送 DSS格式的所述固件升级数据 包给所述 MBB设备 1 00,以使所述 MBB设备根据所述固件升级数据升级固件版 本。
图 16为本发明实施例的主机基于 MBIM实现 MBB设备状态输出的的流程 图。
可选的, 当所述扩展服务类别包括 MBB设备状态输出时, 所述主机 200 根据所述扩展服务类别通过所述 MBIM接口与所述 MBB设备 100进行扩展服务 的信息交互包括:
861: 通过所述 MBIM接口的控制通道发送 MBB设备状态输出的服务请求 给所述 MBB设备 100 ;
862: 通过所述 MBIM接口的数据通道接收 MBB设备状态输出的 Log数据 包, 所述 Log数据包的格式为 DSS格式;
863: 解析所述 Log数据包, 获取 Log数据。
可以理解的, 所述主机 200接收所述 MBB设备 1 00返回的所述 MBB设备 支持的扩展服务类别之前, 包括: 所述主机 200通过所述 MBIM接口的控制通道发送开启数据通道的服务请 求给所述 MBB设备, 通过所述 MB IM接口的控制通道接收所述 MBB设备开启所 述数据通道的响应消息, 根据所述响应消息通过所述数据通道进行扩展服务 的数据传输。
其中, 所述数据通道可以为所述 MBIM接口对应的数据通道。
可以理解的, 所述主机 200可以通过映射的 MBIM接口的控制通道发送服 务查询请求消息给所述移动宽带 MBB设备 100, 还可以通过所述 MBIM接口的 控制通道接收所述 MBB设备 100返回的所述 MBB设备支持的扩展服务类别。
可以理解的, 所述主机 200接收所述 MBB设备返回的所述 MBB设备支持 的扩展服务类别, 包括, 所述主机 200接收所述 MBB设备返回的所述 MBB设 备支持的扩展服务类别的通用识别码 UUID,根据所述 UUID识别所述 MBB设备 支持的扩展服务类别; 或者
接收所述 MBB设备返回的所述 MBB设备支持的扩展服务类别的而 ID和标 准服务类别的 UUID, 从而识别所述 MBB设备支持的扩展服务类别和标准服务 类别。
可以理解的是, 本实施例的主机 100基于 MBIM接口实现通信的方法, 根 据上述系统实施例实现, 具体实现的步骤请参考上述系统实施例, 此处不再 敷述。
本发明实施例的基于 MBIM接口实现通信的主机 200 ,通过映射的 MBIM接 口接收 MBB设备返回的扩展服务类别, 根据所述扩展服务类别与所述 MBB设 备进行扩展服务的通信, 实现主机与 MBB设备的扩展服务的数据交互。 图 17为本发明实施例基于 MBIM接口实现通信的移动宽带 MBB设备的框 架示意图。
所述 MBB设备 100包括, 接收模块 101, 用于接收主机 100通过映射的 MBIM接口发送的服务查询请求消息; MBIM处理模块 102, 用于解析所述服务查询请求消息, 获取所述服务查 询清求;
发送模块 103,根据所述服务查询请求, 上报所述 MBB设备支持的扩展服 务类别给所述主机, 以使所述主机与所述 MBB设备通过所述 MBIM接口进行扩 展服务的信息交互, 其中, 所述扩展服务类别包括收发 AT命令、 固件升级或 输出 MBB设备状态的至少之一。
本发明实施例的基于 MBIM接口实现通信的 MBB设备 100 , 通过上报所述 MBB设备支持的扩展服务类别给所述主机 200, 以使所述主机 200通过映射的 MBIM接口与所述 MBB设备进行扩展服务的信息交互, 实现主机与 MBB设备的 扩展服务的数据交互。
进一步或可选的, 所述 MBB设备 100还包括 AT命令处理模块 106, 当所 述所述扩展服务类别包括收发 AT命令时,
所述接收模块 101,通过所述 MBB设备的控制通道接收所述主机 1 00发送 的 AT命令数据包;
所述 MBIM处理模块 102, 包括解析单元 1 021和获取单元 1022, 所述解 析单元 1021解析所述 AT命令数据包为所述 MBB设备可识别的格式, 所述获 取单元 1022获取所述 AT命令;
所述 AT命令处理模块 1 06, 处理所述 AT命令, 产生所述 AT命令的处理 结果, 并发送给所述 MBIM处理模块, 使所述 MBIM处理模块封装所述 AT命令 的处理结果;
所述发送模块 103, 通过所述 MBB设备的控制通道返回封装的所述 AT命 令的处理结果给所述主机 200。
进一步或可选的, 当所述扩展服务类别包括收发 AT命令时, 所述接收模 块 101, 通过所述 MBB设备的数据通道接收所述主机 200发送的 AT命令数据 包, 所述 AT命令数据包的格式为自定义码流 DSS格式;
所述 MBIM处理模块 102, 解析所述 AT命令数据包, 获取 AT命令; 所述 AT命令处理模块 1 06, 处理所述 AT命令, 产生所述 AT命令的处理 结果;
所述 MBIM处理模块 102, 封装所述 AT命令的处理结果为 DSS数据包; 所述发送模块 103 , 通过所述 MBB设备的数据通道返回所述 AT命令处理 结果的 DSS数据包给所述主机 200。
进一步或可选的, 所述 MBB设备 100还包括固件升级模块 107, 当所述所 述扩展服务类别包括固件升级时,
所述接收模块 101, 通过所述 MBB设备的数据通道接收所述固件升级数 据包, 所述固件升级数据包的格式为设备服务码流 DSS格式;
所述 MBIM处理模块 102, 解析所述固件升级 DSS数据包, 获取所述固件 升级数据;
所述固件升级模块 107根据所述固件升级数据升级所述 MBB设备的固件 版本。
进一步或可选的, 所述 MBB设备 100还包括设备状态输出模块 108, 当所 述扩展服务类别包括 MBB设备状态输出时,
所述接收模块 101,通过所述 MBB设备的控制通道接收所述主机 1 00发送 的 MBB设备状态输出的服务请求;
所述设备状态输出模块 108, 输出所述 MBB设备状态的 Log数据; 所述 MBIM处理模块 102, 封装所述 Log数据为设备服务码流 DSS格式的 数据包;
所述发送模块 103, 通过所述 MBB设备的数据通道返回所述 Log数据的 DSS格式数据包给所述主机 100。
可选的, 所述 MBB设备 100还包括添加模块 104和存储模块 105, 所述添 加模块 104用于添加与所述 MBB设备自定义的扩展服务类别、 所述扩展服务 类别对应的功能值等。
所述存储模块 105存储所述 MBB设备 100的应用程序、 扩展服务数据等。 可以理解的, 所述接收模块 101, 通过所述 MBB设备的控制通道接收主机 200通过映射的 MBIM接口发送的服务查询请求消息。 所述发送模块 103, 通 过所述 MBB设备的控制通道上报所述 MBB设备支持的扩展服务类别给所述主 机 200。
可以理解的, 本发明实施例的 MBB设备 100基于上述系统实施例进行描 述, 具体实现过程可以参考上述系统实施例。
本发明实施例的基于 MBIM接口实现通信的 MBB设备 100 , 通过上报所述 MBB设备支持的扩展服务类别给所述主机 200, 以使所述主机 200通过映射的 MBIM接口与所述 MBB设备进行扩展服务的信息交互, 实现主机与 MBB设备的 扩展服务的数据交互。
图 18为本发明实施例基于 MBIM接口实现通信的主机的框架示意图。 所述主机 200包括: 传输模块 201, 通过映射的 MBIM接口发送服务查询 请求消息给移动宽带 MBB设备, 接收所述 MBB设备返回的所述 MBB设备支持 的扩展服务类别,其中,所述扩展服务类别包括收发 AT命令、 固件升级或 MBB 设备状态输出的至少之一;
MBIM接口模块 202, 用于根据所述扩展服务类别通过所述 MBIM接口与所 述 MBB设备进行扩展服务的信息交互。
本发明实施例的基于 MBIM接口实现通信的主机 200 ,通过映射的 MBIM接 口接收 MBB设备返回的扩展服务类别, 根据所述扩展服务类别与所述 MBB设 备进行扩展服务的通信, 实现主机与 MBB设备的扩展服务的数据交互。
其中, 所述 MBIM接口模块 202, 还可以用于, 当所述扩展服务类别包括 收发 AT命令时, 所述 MBIM接口模块 202, 封装所述 AT命令为命令标识 CID 格式的 AT命令数据包, 通过所述 MBIM接口的控制通道发送所述 AT命令数据 包; 还可以通过所述 MBIM接口的控制通道接收所述 MBB设备上报的所述 AT 命令的处理结果的 CID数据包; 解析所述 AT命令的处理结果的 CID数据包, 获取所述 AT命令的处理结果。 可选的, 所述 MBIM接口模块 202,还可以封装所述 AT命令为设备服务码 流 DSS格式的 AT命令数据包, 通过所述 MBIM接口的数据通道发送 DSS格式 的所述 AT命令数据包给所述 MBB设备; 通过所述 MBIM接口的数据通道接收 所述 MBB设备上报的所述 AT命令的处理结果的 DSS数据包; 解析所述 AT命 令的处理结果的 DSS数据包, 获取所述 AT命令的处理结果。
可选的, 当所述扩展服务类别包括固件升级时, 所述 MBIM接口模块 202, 还可以封装所述固件升级数据为设备服务码流 DSS格式的固件升级数据包; 通过所述 MBIM接口的数据通道发送 DSS格式的所述固件升级数据包给所述 MBB设备, 以使所述 MBB设备根据所述固件升级数据升级固件版本。
可选的, 当所述扩展服务类别为 MBB设备状态输出时, 所述 MBIM接口模 块 202, 还可以通过所述 MBIM接口的控制通道发送 MBB设备状态输出的服务 请求给所述 MBB设备; 通过所述 MBIM接口的数据通道接收 MBB设备状态输出 的 Log数据包, 所述 Log数据包的格式为 DSS格式; 解析所述 Log数据包, 获取 Log数据。
可以理解的, 所述传输模块 201可以通过所述 MB IM接口的控制通道发送 或接收所述服务查询请求消息给所述 MBB设备, 并可以通过所述 MBIM接口的 控制通道接收所述 MBB设备返回的所述 MBB设备支持的扩展服务类别。
所述主机 200还可以包括存储模块 205,存储所述应用程序及扩展服务数 据等。
本发明实施例的基于 MB IM接口实现通信的主机 200 ,通过映射的 MBIM接 口接收 MBB设备返回的扩展服务类别, 根据所述扩展服务类别与所述 MBB设 备进行扩展服务的通信, 实现主机与 MBB设备的扩展服务的数据交互。
图 19为本发明实施例基于 MB IM接口实现通信的 MBB设备结构示意图。 所述 MBB设备 1 00包括处理器 1 1 0和第一接口 1 1 1,所述第一接口 1 1 1一 端与所述处理器 1 1 0连接, 所述第一接口 1 1 1另一端用于与主机 200连接, 所述第一接口 1 1 1接收所述主机 200通过映射的 MB IM接口发送的服务查 询清求消息;
所述处理器 11 0解析所述服务查询请求消息, 获取所述服务查询请求; 根据所述服务查询请求, 通过所述第一接口 111上报所述 MBB设备支持 的扩展服务类别给所述主机 200 ,以使所述主机 200与所述 MBB设备 100通过 所述 MBIM接口进行扩展服务的信息交互, 其中, 所述扩展服务类别包括收发 AT命令、 固件升级或输出 MBB设备状态的至少之一。
本发明实施例的基于 MBIM接口实现通信的 MBB设备 100 , 通过上报所述 MBB设备支持的扩展服务类别给所述主机 200, 以使所述主机 200通过映射的 MBIM接口与所述 MBB设备进行扩展服务的信息交互, 实现主机与 MBB设备的 扩展服务的数据交互。
其中, 当所述扩展服务类别包括收发 AT命令时, 所述处理器 110还用于 解析所述 AT命令的数据包获取 AT命令; 处理所述 AT命令, 产生所述 AT命 令的处理结果, 封装所述 AT命令的处理结果, 并通过所述第一接口发送给所 述主机 200。
具体地, 所述 AT命令可以为 C ID格式或 DSS格式。
可选的, 当所述所述扩展服务类别包括固件升级时, 所述处理器 110解 析主机发送的固件升级的数据包, 获取所述固件升级数据; 根据所述固件升 级数据升级所述 MBB设备的固件版本。
当所述所述扩展服务类别包括 MBB设备状态输出时, 所述处理器 110, 通 过所述第一接口 111的控制通道接收所述主机 200发送的 MBB设备状态输出 的服务请求; 封装 MBB设备状态输出的 Log数据为设备服务码流 DSS格式的 数据包; 通过所述第一接口 1 11的数据通道返回所述 Log数据的 DSS格式数 据包给所述主机。
可以理解的, 所述处理器 110可以通过所述第一接口 111的控制通道接 收和 /或响应所述主机 200发送的所述服务查询请求。
可选的, 所述处理器 1 07还用于添加自定义的扩展服务类别识别码而 ID 和 /或所述扩展服务类别对应的扩展服务功能值。
所述 MBB设备 100还可以包括存储器 112、 输入单元 113、 显示屏 114、 RF电路 115、 音频电路 116等; 所述存储器 112用于存储所述处理器 110执 行的应用程序和扩展服务数据, 所述输入单元 113可以包括触控面板 117和 其他输入设备 118, 如键盘、 鼠标等, 所述输入单元 113可以接收用户输入操 作指令, 通过所述处理器 110执行所述操作指令, 将执行结果显示于所述显 示屏 114, 呈现给用户。
可以理解的, 本发明实施例中的第一接口 111 可以为所述 MBB设备 100 通用串行总线 USB接口, 本实施例中对此不做限定。
尽管未示出, 该 MBB设备 100还可以包括摄像头、 蓝牙模块等, 在此不 再赘述。
本发明实施例的基于 MBIM接口实现通信的 MBB设备 100 , 通过上报所述 MBB设备支持的扩展服务类别给所述主机 200, 以使所述主机 200通过映射的 MBIM接口与所述 MBB设备进行扩展服务的信息交互, 实现主机与 MBB设备的 扩展服务的数据交互。
图 20发明实施例基于 MBIM接口实现通信的主机结构示意图。
一种基于 MBIM接口实现通信的主机 200 , 所述主机 200包括: 主机处理 器 210和第二接口 211,所述第二接口 211的一端与所述主机处理器 210连接, 所述第二接口 211的另一端与移动宽带 MBB设备 100连接, 所述主机 200与 所述 MBB设备 100连接, 所述第二接口映射为 MB IM接口;
所述主机处理器 210通过映射的所述 MBIM接口发送服务查询请求消息给 所述 MBB设备 100,接收所述 MBB设备 100返回的所述 MBB设备支持的扩展服 务类别, 其中, 所述扩展服务类别包括收发 AT命令、 固件升级或 MBB设备状 态输出的至少之一;
所述主机处理器 210根据所述扩展服务类别通过所述 MBIM接口与所述 MBB设备进行扩展服务的信息交互。 本发明实施例的基于 MBIM接口实现通信的主机 200 ,通过映射的 MBIM接 口接收 MBB设备返回的扩展服务类别, 根据所述扩展服务类别与所述 MBB设 备进行扩展服务的通信, 实现主机与 MBB设备的扩展服务的数据交互。
其中, 所述主机处理器 210 还可以用于, 当所述扩展服务类别包括收发 AT命令时, 所述主机处理器 210可以封装所述 AT命令为命令标识 C I D格式 的 AT命令数据包, 通过所述 MBIM接口的控制通道发送所述 AT命令数据包给 所述 MBB设备 100; 通过所述 MBIM接口的控制通道接收所述 MBB设备 100上 报的所述 AT命令的处理结果的 CID数据包; 解析所述 AT命令的处理结果的 CID数据包, 获取所述 AT命令的处理结果。
可选的, 当所述扩展服务类别包括收发 AT命令时, 所述主机处理器 210, 还可以封装所述 AT命令为设备服务码流 DSS格式的 AT命令数据包, 通过所 述 MBIM接口的数据通道发送 DSS格式的所述 AT命令数据包给所述 MBB设备 100; 通过所述 MBIM接口的数据通道接收所述 MBB设备 100上报的所述 AT命 令的处理结果的 DSS数据包; 解析所述 AT命令的处理结果的 DSS数据包, 获 取所述 AT命令的处理结果。
可选的, 当所述扩展服务类别包括固件升级时, 所述主机处理器 210, 还 可以封装所述固件升级数据为设备服务码流 DSS格式的固件升级数据包; 通 过所述 MBIM接口的数据通道发送 DSS格式的所述固件升级数据包给所述 MBB 设备 100, 以使所述 MBB设备 100根据所述固件升级数据升级固件版本。
可选的,当所述扩展服务类别 MBB设备状态输出时,所述主机处理器 210, 通过所述 MBIM接口的控制通道发送 MBB设备状态输出的服务请求给所述 MBB 设备 100; 通过所述 MBIM接口的数据通道接收 MBB设备状态输出的 Log数据 包, 所述 Log数据包的格式为 DSS格式; 解析所述 Log数据包, 获取 Log数 据。
可以理解的是, 所述主机处理器 210可以通过所述 MBIM接口的控制通道 发送或接收所述服务查询请求消息给所述 MBB设备 100, 并通过所述 MBIM接 口的控制通道接收所述 MBB设备返回的所述 MBB设备支持的扩展服务类别。 可选的, 所述主机处理器 210还用添加和执行与所述 MBB设备自定义的 扩展^ 务类别和处理扩展^ 务功能对应的应用程序。
可以理解的是, 所述主机 100还可以包括主机存储器 212、 主机输入单元
21 3、 主机显示屏 214、 主机音频电路 215、 主机 RF电路 216等。
所述主机存储器 212可以用于存储所述主机处理器 21 0执行的应用程序 和扩展服务数据, 所述主机输入单元 21 3可以包括触控面板 217及及其他输 入设备 219, 如鼠标等, 所述主机输入单元 21 3可以接收用户输入操作指令, 通过所述主机处理器 210执行所述操作指令, 将执行结果显示于所述主机显 示屏 214, 呈现给用户。
所述主机 200还可以通过所述主机音频电路 215播放声音文件。
尽管未示出, 该主机 200 还可以包括摄像头、 蓝牙模块等, 在此不再赘 述。
可以理解的, 本发明实施例中的第二接口 211 可以为主机 200的通用串 行总线 USB接口, 本实施例中对此不做限定。
本发明实施例的基于 MBIM接口实现通信的主机 200 ,通过映射的 MBIM接 口接收 MBB设备返回的扩展服务类别, 根据所述扩展服务类别与所述 MBB设 备进行扩展服务的通信, 实现主机与 MBB设备的扩展服务的数据交互。
需要说明的是, 结合本文中所公开的实施例中描述的各方法步骤和模块, 能够以电子硬件或者计算机软件和硬件二者的结合来实现, 在上述说明中已 经按照功能一般性地描述了各实施例的步骤及组成。 这些功能究竟以硬件还 是软件和硬件的方式来执行, 取决于技术方案的特定应用和设计约束条件。 本领域普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的 功能, 但是这种实现不应认为超出本发明的范围。
结合本文中所公开的实施例描述的方法或步骤可以用硬件、 处理器执行 的软件程序, 或者二者的结合来实施。 软件程序可以置于随机存储器(RAM )、 内存、 只读存储器(ROM )、 电可编程 R0M、 电可擦除可编程 R0M、 寄存器、 硬 盘、 可移动磁盘、 CD-R0M、 或技术领域内所公知的任意其它形式的存储介质 中。 但本发明并不限于此。 在不脱离本发明的精神和实质的前提下, 本领域普通 技术人员可以对本发明的实施例进行各种等效的修改或替换, 而这些修改或 替换都应在本发明的涵盖范围内。

Claims

权利要求 书
1、 一种基于 MBIM接口实现通信的移动宽带 MBB设备, 所述 MBB设备包括: 接收模块, 用于接收主机通过映射的 MBIM接口发送的服务查询请求消息; MBIM处理模块, 用于解析所述服务查询请求消息, 获取服务查询请求; 发送模块, 根据所述服务查询请求, 上报所述 MBB设备支持的扩展服务类 别给所述主机, 以使所述主机与所述 MBB设备通过所述 MBIM接口进行扩展服务 的信息交互, 其中, 所述扩展服务类别包括收发 AT命令、 固件升级或输出 MBB 设备状态的至少之一。
2、 根据权利要求 1所述的 MBB设备, 其特征在于, 所述 MBB设备还包括 AT 命令处理模块, 当所述扩展服务类别包括收发 AT命令时,
所述接收模块, 用于通过所述 MBB设备的控制通道接收所述主机发送的 AT 命令数据包, 所述 AT命令数据包的格式为 CID格式;
所述 MBIM处理模块, 用于解析所述 AT命令数据包获取 AT命令;
所述 AT命令处理模块, 用于处理所述 AT命令, 产生所述 AT命令的处理结 果, 并发送给所述 MBIM处理模块, 使所述 MBIM处理模块封装所述 AT命令的处 理结果;
所述发送模块, 用于通过所述 MBB设备的控制通道返回封装的所述 AT命令 的处理结果给所述主机。
3、 根据权利要求 1所述的 MBB设备, 其特征在于, 所述 MBB设备还包括 AT 命令处理模块, 当所述扩展服务类别包括收发 AT命令时,
所述接收模块, 通过所述 MBB设备的数据通道接收所述主机发送的 AT命令 数据包, 所述 AT命令数据包的格式为设备服务码流格式;
所述 MBIM处理模块, 解析所述 AT命令数据包, 获取 AT命令;
所述 AT命令处理模块, 处理所述 AT命令, 产生所述 AT命令的处理结果; 所述 MBIM处理模块, 封装所述 AT命令的处理结果为设备服务码流格式的 数据包; 所述发送模块, 通过所述 MBB设备的数据通道返回所述 AT命令处理结果的 设备服务码流格式的数据包给所述主机。
4、 根据权利要求 1所述的 MBB设备, 其特征在于, 所述 MBB设备还包括固 件升级模块, 当所述扩展服务类别包括固件升级时,
所述接收模块, 通过所述 MBB设备的数据通道接收所述固件升级的数据包, 所述固件升级的数据包的格式为设备服务码流格式;
所述 MBIM处理模块,解析所述固件升级的数据包,获取所述固件升级数据; 所述固件升级模块, 根据所述固件升级数据升级所述 MBB设备的固件版本。
5、 根据权利要求 1所述的 MBB设备, 其特征在于, 所述 MBB设备还包括设 备状态输出模块, 当所述扩展服务类别包括输出 MBB设备状态时,
所述接收模块, 通过所述 MBB设备的控制通道接收所述主机发送的 MBB设 备状态输出的服务请求;
所述设备状态输出模块, 输出所述 MBB设备状态的 Log数据;
所述 MBIM处理模块, 封装所述 Log数据为设备服务码流格式的数据包; 所述发送模块, 通过所述 MBB设备的数据通道返回所述 Log数据的数据包 给所述主机。
6、根据权利要求 1-5任一项所述的 MBB设备, 其特征在于, 所述接收模块, 通过所述 MBB设备的控制通道接收所述主机通过映射的 MBIM接口发送的服务查 询请求消息; 所述发送模块, 通过所述 MBB设备的控制通道上报所述 MBB设备 支持的扩展服务类别给所述主机。
7、 一种基于 MBIM接口实现通信的主机, 所述主机包括:
传输模块, 通过映射的 MBIM接口发送服务查询请求消息给移动宽带 MBB设 备, 接收所述 MBB设备返回的所述 MBB设备支持的扩展服务类别, 其中, 所述扩 展服务类别包括收发 AT命令、 固件升级或输出 MBB设备状态的至少之一;
MBIM接口模块, 用于根据所述扩展服务类别通过所述 MBIM接口与所述 MBB设 备进行扩展服务的信息交互。
8、 根据权利要求 7所述的主机, 其特征在于, 所述扩展服务类别包括收发 AT命令时, 所述 MBIM接口模块, 封装所述 AT命令为设备服务码流格式的 AT命 令数据包, 通过所述 MBIM接口的数据通道发送所述 AT命令数据包给所述 MBB 设备; 通过所述 MBIM接口的数据通道接收所述 MBB设备上报的所述 AT命令的 处理结果的数据包; 解析所述 AT命令的处理结果的数据包, 获取所述 AT命令 的处理结果。
9、 根据权利要求 7所述的主机, 其特征在于, 当所述扩展服务类别包括固 件升级时, 所述 MBIM接口模块, 封装所述固件升级数据为设备服务码流格式的 固件升级数据包; 通过所述 MBIM接口的数据通道发送所述固件升级数据包给所 述 MBB设备, 以使所述 MBB设备根据所述固件升级数据升级固件版本。
10、 根据权利要求 7 所述的主机, 其特征在于, 当所述扩展服务类别 MBB 设备状态输出时, 所述 MBIM接口模块, 通过所述 MBIM接口的控制通道发送 MBB 设备状态输出的服务请求给所述 MBB设备; 通过所述 MBIM接口的数据通道接收 MBB设备状态输出的 Log数据包, 所述 Log数据包的格式为设备服务码流格式; 解析所述 Log数据包, 获取 Log数据。
PCT/CN2014/075808 2013-04-27 2014-04-21 基于mbim接口实现通信方法及其设备 WO2014173268A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP14788197.3A EP2922267B1 (en) 2013-04-27 2014-04-21 Method for achieving communication based on mbim interface and device therefor

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310152616.6 2013-04-27
CN201310152616.6A CN104125204B (zh) 2013-04-27 2013-04-27 基于mbim接口实现通信方法及其设备

Publications (1)

Publication Number Publication Date
WO2014173268A1 true WO2014173268A1 (zh) 2014-10-30

Family

ID=51770470

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/075808 WO2014173268A1 (zh) 2013-04-27 2014-04-21 基于mbim接口实现通信方法及其设备

Country Status (3)

Country Link
EP (1) EP2922267B1 (zh)
CN (1) CN104125204B (zh)
WO (1) WO2014173268A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111722938A (zh) * 2020-05-08 2020-09-29 深圳市广和通无线股份有限公司 At指令处理方法、装置、计算机设备和存储介质
CN113595771A (zh) * 2021-07-12 2021-11-02 合肥移瑞通信技术有限公司 基于mbim接口更新数据的方法、设备以及存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104410608A (zh) * 2014-11-06 2015-03-11 深圳市广和通无线通信软件有限公司 一种win8系统利用at命令操作无线通信模块的方法
CN107333081A (zh) * 2016-04-28 2017-11-07 炬芯(珠海)科技有限公司 一种基于hdmi设备的传输方法及装置
CN108322616B (zh) * 2017-01-18 2021-09-03 中兴通讯股份有限公司 一种数据处理方法和语音数据卡
KR20220133699A (ko) * 2021-03-25 2022-10-05 삼성전자주식회사 전자 장치 및 전자 장치의 동작 방법
CN113765824A (zh) * 2021-10-15 2021-12-07 合肥移瑞通信技术有限公司 基于mbim接口的响应消息发送方法、装置、mbb设备及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102130957A (zh) * 2011-03-21 2011-07-20 中兴通讯股份有限公司 一种移动宽带设备及其使用方法
CN102158350A (zh) * 2011-02-12 2011-08-17 华为终端有限公司 一种移动宽带设备及管理移动宽带设备的方法
CN102201953A (zh) * 2011-04-14 2011-09-28 中兴通讯股份有限公司 一种联网方法及系统
CN102769612A (zh) * 2012-06-27 2012-11-07 中兴通讯股份有限公司 一种基于mbim实现gps功能的方法、设备及无线通信终端
CN102869125A (zh) * 2012-08-21 2013-01-09 中兴通讯股份有限公司 数据卡及其通信方法、系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6031867A (en) * 1993-07-02 2000-02-29 Multi-Tech Systems, Inc. Modem with firmware upgrade feature
CN102158351B (zh) * 2011-02-14 2014-11-05 中兴通讯股份有限公司 设备管理客户端多服务器下设备管理树的管理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102158350A (zh) * 2011-02-12 2011-08-17 华为终端有限公司 一种移动宽带设备及管理移动宽带设备的方法
CN102130957A (zh) * 2011-03-21 2011-07-20 中兴通讯股份有限公司 一种移动宽带设备及其使用方法
CN102201953A (zh) * 2011-04-14 2011-09-28 中兴通讯股份有限公司 一种联网方法及系统
CN102769612A (zh) * 2012-06-27 2012-11-07 中兴通讯股份有限公司 一种基于mbim实现gps功能的方法、设备及无线通信终端
CN102869125A (zh) * 2012-08-21 2013-01-09 中兴通讯股份有限公司 数据卡及其通信方法、系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111722938A (zh) * 2020-05-08 2020-09-29 深圳市广和通无线股份有限公司 At指令处理方法、装置、计算机设备和存储介质
CN111722938B (zh) * 2020-05-08 2024-07-19 深圳市广和通无线股份有限公司 At指令处理方法、装置、计算机设备和存储介质
CN113595771A (zh) * 2021-07-12 2021-11-02 合肥移瑞通信技术有限公司 基于mbim接口更新数据的方法、设备以及存储介质

Also Published As

Publication number Publication date
EP2922267A4 (en) 2015-12-16
EP2922267A1 (en) 2015-09-23
CN104125204A (zh) 2014-10-29
CN104125204B (zh) 2018-04-10
EP2922267B1 (en) 2018-05-30

Similar Documents

Publication Publication Date Title
WO2014173268A1 (zh) 基于mbim接口实现通信方法及其设备
JP5726300B2 (ja) データカード、及びデータカードのネットワーキング方法
US20230040580A1 (en) Binding method and system for device network configuration, and mobile terminal and storage medium
US20160294575A1 (en) System, Apparatus, and Method for Automatically Configuring Application Terminals in Home Network
WO2014176832A1 (zh) 智能终端管理家庭网关的系统及方法
US20150077231A1 (en) Method, apparatus, and system for intelligently controlling device, and plug-and-play device
WO2020177698A1 (zh) 小程序平台间的通讯方法、设备和计算机存储介质
WO2013083056A1 (zh) 一种管理移动宽带设备的方法、设备及系统
US10558448B2 (en) Method, user equipment, and application server for downloading application
WO2020177697A1 (zh) 小程序平台间的发现方法、设备和计算机存储介质
WO2008151576A1 (fr) Procédé, terminal et système de mise à jour de la langue du terminal
WO2015000379A1 (zh) 空调器的远程控制方法和空调器的远程控制系统
EP2905938B1 (en) Method for acquiring locating information, terminal and mobile broadband interface model (mbim) device
WO2009009968A1 (fr) Procédé, dispositif et système pour acquérir des informations d'ouverture de session
CN102088797A (zh) 一种无线通讯方法、系统及无线通讯终端
WO2013185696A2 (zh) 一种数据处理的方法与设备
WO2013149552A1 (zh) 一种移动宽带设备及其移动宽带业务处理的方法
WO2012106968A1 (zh) Java应用程序向本地传递信息的方法及设备
WO2009062396A1 (fr) Procédé d'accès à des ressources et système d'accès à des ressources
CN101917780B (zh) 无线通信终端网络设备功能的实现方法及装置
WO2013185719A1 (zh) 一种无线上网方法及设备、服务器和无线上网系统
US7738432B2 (en) Dynamic network activation apparatus, systems, and methods
WO2013166758A1 (zh) 一种配置最大传输单元(mtu)值的方法、终端及usb数据卡
WO2017124436A1 (zh) 通信的方法、移动终端、发布终端与通信系统
CN112448878B (zh) 用于PPPoE透传的方法、PPPoE服务器及电子设备

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2014788197

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE