WO2017124736A1 - 一种升级异常信息的传输方法、设备和系统 - Google Patents

一种升级异常信息的传输方法、设备和系统 Download PDF

Info

Publication number
WO2017124736A1
WO2017124736A1 PCT/CN2016/095343 CN2016095343W WO2017124736A1 WO 2017124736 A1 WO2017124736 A1 WO 2017124736A1 CN 2016095343 W CN2016095343 W CN 2016095343W WO 2017124736 A1 WO2017124736 A1 WO 2017124736A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile terminal
upgrade
information
device management
management server
Prior art date
Application number
PCT/CN2016/095343
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 中兴通讯股份有限公司
Publication of WO2017124736A1 publication Critical patent/WO2017124736A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0884—Network architectures or network communication protocols for network security for authentication of entities by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • This document relates to, but is not limited to, wireless communication technology, and more particularly to a transmission method, device and system for upgrading abnormal information.
  • OMA DM Open Mobile Alliance Device Management
  • FOTA Firmware Over The Air
  • FOTA firmware Update
  • the mobile terminal reports the corresponding failure result code to the device management server.
  • the result code corresponding to the upgrade package and the mobile terminal firmware mismatch is 403
  • the mobile The result code corresponding to the upgrade failure of the upgrade package is 410.
  • the developer cannot analyze the specific cause of the upgrade failure from the failed result code received by the server.
  • R&D personnel need to wait for the upgraded mobile terminal to return the warranty before it can be analyzed by the relevant upgrade log file from the mobile device. Therefore, after the current FOTA upgrade fails, only the failure result code is reported, and it cannot be timely fed back to the R&D personnel. Therefore, the R&D personnel cannot take corresponding countermeasures to remedy after the FOTA upgrade fails. For example, add a new one to avoid the upgrade failure. Upgrade package, etc.
  • the embodiment of the invention provides a method, a device and a system for transmitting upgrade abnormal information, which can timely feedback the upgrade abnormality information of the mobile terminal, so that the research and development personnel can timely take corresponding countermeasures according to the upgrade abnormal information.
  • An embodiment of the present invention provides a method for transmitting upgrade abnormal information, where the method includes:
  • the mobile terminal After the abnormality of the upgrade occurs, the mobile terminal sends a result code corresponding to the cause of the upgrade abnormality to the device management server;
  • the mobile terminal sends a log file for upgrading an abnormality according to the idle log server information.
  • the mobile terminal sends a result code corresponding to the cause of the upgrade abnormality to the device management server, including:
  • the mobile terminal sends a result code corresponding to the matching failure to the device management server;
  • the mobile terminal sends a result corresponding to the upgrade failure to the device management server. code.
  • the receiving, by the mobile terminal, the idle log server information returned by the device management server includes:
  • the replacement instruction is configured to add a leaf node including the idle log server information on an extended node in a device management tree DMT of the mobile terminal .
  • the method further includes:
  • the mobile terminal receives authentication mode information sent by the idle log server;
  • the mobile terminal receives the authentication success information sent by the idle log server.
  • the log file of the upgrade exception includes:
  • Device information of the mobile terminal and upgrade data information when the mobile terminal performs upgrade And an upgrade process log when the mobile terminal performs an upgrade.
  • An embodiment of the present invention provides another method for transmitting upgrade abnormal information, where the method includes:
  • the device management server After receiving the result code corresponding to the upgrade abnormality reason sent by the mobile terminal, the device management server acquires the idle log server information;
  • the device management server transmits the idle log server information to the mobile terminal.
  • the sending, by the device management server, the idle log server information to the mobile terminal includes:
  • the device management server generates a replacement instruction and sends the replacement instruction to the mobile terminal; wherein the replacement instruction is configured to add the idleness on an extended node in a device management tree DMT of the mobile terminal The leaf node of the log server information.
  • An embodiment of the present invention provides a mobile terminal, where the mobile terminal includes: an upgrade module, a first sending module, and a first receiving module;
  • the upgrade module is configured to upgrade the mobile terminal; and after the upgrade is abnormal, triggering the first sending module;
  • the first sending module is configured to send a result code corresponding to the cause of the upgrade abnormality to the device management server; after receiving the idle log server information, the first receiving module sends a log file of the upgrade abnormality according to the idle log server information;
  • the first receiving module is configured to receive idle log server information returned by the device management server.
  • the first sending module is configured to send a result code corresponding to the reason for sending the upgrade abnormality to the device management server in the following manner:
  • the upgrade package matches the firmware of the mobile terminal, and the upgrade module fails to upgrade according to the successfully upgraded upgrade package, the result code corresponding to the upgrade failure is sent to the device management server.
  • the first receiving module is configured to: receive, be returned by the device management server And a replacement instruction, wherein the replacement instruction is configured to add a leaf node including the idle log server information on an extension node in a device management tree DMT of the mobile terminal.
  • the first sending module is further configured to:
  • the first receiving module After the first receiving module receives the authentication mode information, the first receiving module sends the authentication information to the idle log server according to the authentication mode information, before sending the upgrade abnormal log file according to the idle log server information;
  • the first receiving module is further configured to receive the authentication mode information sent by the idle log server, and receive the authentication success information sent by the idle log server.
  • An embodiment of the present invention provides a device management server, where the device management server includes: a second receiving module, an obtaining module, and a second sending module;
  • the second receiving module is configured to receive a result code corresponding to an upgrade abnormality reason sent by the mobile terminal;
  • the obtaining module is configured to obtain idle log server information
  • the second sending module is configured to send the idle log server information to the mobile terminal.
  • the second sending module is configured to: generate a replacement instruction, and send the replacement instruction to the mobile terminal; wherein the replacement instruction is used in a device management tree DMT of the mobile terminal A leaf node containing the idle log server information is added to the extended node.
  • An embodiment of the present invention provides a transmission system for upgrading abnormal information, where the system includes: a mobile terminal, a device management server, and a log server;
  • the mobile terminal is configured to send a result code corresponding to the cause of the upgrade abnormality to the device management server after the upgrade is abnormal;
  • the device management server is configured to obtain the idle log server information after receiving the result code corresponding to the upgrade abnormality reason sent by the mobile terminal;
  • Embodiments of the present invention also provide a computer readable storage medium storing computer executable instructions for performing any of the methods described above.
  • the embodiment of the present invention provides a method, a device, and a system for transmitting an upgrade abnormality information.
  • the device management server feeds back the report address of the upgrade log file to the mobile terminal, so that the mobile terminal can
  • the upgrade log file is sent according to the report address, and the upgrade abnormal information of the mobile terminal is fed back in time, so that the R&D personnel can take corresponding countermeasures according to the upgrade abnormal information in time.
  • FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of a method for transmitting upgrade abnormal information according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a process for authenticating a mobile terminal by a log server according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of a log file according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic flowchart of a method for transmitting upgrade abnormality information applied to a mobile terminal side according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of performing authentication on a mobile terminal according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a method for transmitting upgrade abnormality information applied to a device management server according to an embodiment of the present disclosure
  • FIG. 8 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a device management server according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a transmission system for upgrading abnormal information according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present invention.
  • the scenario includes: a mobile terminal that follows the OMA DM protocol, a device management DM server, and a download that is configured to provide an upgrade package for the mobile terminal.
  • the server and the log server set up to store log files.
  • the connection relationship between the four is as shown in FIG. 1.
  • a device upgrade agent (DUA, Device Update Agent) that upgrades the mobile terminal by using the upgrade package is embedded. Therefore, during the upgrade process, the DUA can Think of it as part of a mobile terminal.
  • DUA Device Update Agent
  • Figure 2 shows a flow of a method for transmitting upgrade exception information provided by an embodiment of the present invention, which may include:
  • the mobile terminal can send its own device information and the software version number to the DM server. Subsequently, the DM server obtains the download server where the mobile device software version upgrade package is located according to the device information and the software version number of the mobile terminal. Address, and by sending a replacement command to the mobile terminal, replacing the address of the download server in the device management tree (DMT, OMA Device Managemet Tree) of the mobile terminal with the address of the download server where the previously acquired mobile device software version upgrade package is located Then, the mobile terminal downloads the upgrade package according to the address of the download server, and upgrades the mobile terminal by using the upgrade package by the DUA.
  • DMT device management tree
  • OMA Device Managemet Tree OMA Device Managemet Tree
  • how to obtain the address of the download server where the mobile device software version upgrade package is located can be implemented by using the well-known technology of the present invention, and is not used to limit the protection scope of the embodiment of the present invention, and details are not described herein again.
  • the mobile terminal upgrades successfully, an alert command is sent to the DM server to report the result code 200 indicating that the upgrade is successful.
  • the corresponding result code is generated according to the abnormal reason.
  • the check code of the upgrade package does not match the real check code
  • the corresponding result code is 402
  • the upgrade package does not match the firmware of the mobile terminal
  • the corresponding result code is 403
  • the upgrade package digital signature verification fails
  • the corresponding result code is 404
  • the mobile terminal fails to upgrade according to the upgrade package, the corresponding result code is 410, etc., in the OMA DM protocol.
  • the related content of the firmware upgrade includes: when the structure of the result code is 2XX, it indicates that the upgrade result is successful; when the structure of the result code is 4XX or 5XX, it indicates that the upgrade is abnormal; where X represents a number.
  • step S201 after the upgrade terminal has an abnormality, the mobile terminal sends a result code corresponding to the cause of the upgrade abnormality to the device management server, including:
  • the mobile terminal sends a result code corresponding to the matching failure to the device management server;
  • the mobile terminal sends a result code corresponding to the upgrade failure to the device management server.
  • the mobile terminal may encapsulate the result code in an Alert command, and send the encapsulated Alert command to the device management server.
  • the device management server After receiving the result code corresponding to the cause of the upgrade abnormality, the device management server obtains the idle log server information.
  • the device management server may select an idle log server from the log server of its own jurisdiction according to the current log server load amount and traffic throughput indicators, and generate corresponding idle log server information, optionally
  • the idle log server information may include a Uniform Resource Locator (URL) of the idle log server.
  • URL Uniform Resource Locator
  • the load of the log service weapon is balanced according to the throughput index of the current log server and the throughput indicator such as the traffic volume.
  • S203 The device management server sends the idle log server information to the mobile terminal.
  • the device manager can generate a replacement instruction and send the replacement instruction to the mobile terminal; and the replacement instruction can be used for an extension (Ext, Extension) node in a device management tree (DMT) of the mobile terminal Add a leaf node that contains free log server information.
  • extension Ext, Extension
  • DMT device management tree
  • the device manager may reply to the Alert command sent by the mobile terminal, and generate a Replace command for adding an leaf node including the LogURL in the Ext node in the mobile terminal DMT; wherein the LogURL indicates idle The URL of the log server.
  • the replacement command is then sent to the mobile terminal.
  • S204 The mobile terminal sends a log file of the upgrade abnormality according to the idle log server information.
  • the mobile terminal records the running process during the daily operation, thereby generating a log file. Accordingly, in the upgrade process, the mobile terminal also records the upgrade process and generates a log file of the upgrade process; When the upgrade process is abnormal, the log file of the upgrade process recorded by the mobile terminal is the basis for the R&D personnel to analyze the upgrade abnormality.
  • the R&D personnel can read the upgrade abnormal log file from the log server and analyze it in time, without waiting for the mobile terminal to return.
  • the log file is exported from the mobile terminal for analysis. Therefore, the R&D personnel can obtain the upgrade abnormal information of the mobile terminal in time, and can also take corresponding countermeasures according to the upgrade abnormal information in time, for example, adding a new upgrade to avoid the upgrade failure. Package, etc.
  • the mobile terminal can upload the log plaintext data by using the HyperText Transfer Protocol (HTTP), and can use an encryption algorithm or a Hyper Text Transfer Protocol over Secure Socket Layer (HTTPS).
  • HTTP HyperText Transfer Protocol
  • HTTPS Hyper Text Transfer Protocol over Secure Socket Layer
  • the file transfer protocol (FTP, File Transfer Protocol) and other file transfer protocols may also be used to send log files; the specific transfer mode may be set by the log server or determined by the log server and the mobile terminal.
  • the method may further include an authentication process of the mobile terminal by the idle log server, including:
  • the mobile terminal sends the device information corresponding to the mobile terminal to the idle log server.
  • the device information includes: manufacturer information, network operator information, model information, and International Mobile Equipment Identity (IMEI, International Mobile Equipment Identity);
  • IMEI International Mobile Equipment Identity
  • the idle log server sends the authentication mode information to the mobile terminal.
  • the authentication mode information includes basic authentication information and digest authentication information.
  • S303 The mobile terminal sends the authentication information to the idle log server according to the authentication mode information.
  • S304 The idle log server sends the authentication success information to the mobile terminal.
  • the mobile terminal can send the upgrade abnormal day to the idle log server.
  • Zhi file It should be noted that, since the mobile terminal can encapsulate its own device information, such as manufacturer information, network operator information, model information, and IMEI corresponding to the mobile terminal, in the log file, step S301 is in some specific applications. Can be ignored in the scene. At this time, the device information of the mobile terminal itself can be obtained by parsing the log file through the idle log server.
  • the abnormally updated log file may include: device information of the mobile terminal, upgrade data information when the mobile terminal performs upgrade, and an upgrade process log when the mobile terminal performs upgrade.
  • the abnormal log file may include: OEM (Original Equipment Manufacturer), network operator (IPS, Internet Service Provider), and model ( Model), device information such as IMEI of the mobile device; and the upgrade file file (File) or image (Image) name of the upgrade, the file of the upgraded data block or the memory technology device (MTD, Memory Technology Device) Binary Data Offset Address, Binary Data Size, and the upgraded binary data block (Binary Data) and the upgrade process log (DUA log) of the DUA in the mobile terminal.
  • OEM Olinal Equipment Manufacturer
  • IPS Internet Service Provider
  • Model model
  • device information such as IMEI of the mobile device
  • the upgrade file file (File) or image (Image) name of the upgrade the file of the upgraded data block or the memory technology device (MTD, Memory Technology Device) Binary Data Offset Address, Binary Data Size, and the upgraded binary data block (Bin
  • the device management server feeds back to the mobile terminal the idle log server address reported by the upgrade log file, so that the mobile terminal can follow the idle state.
  • the log server address sends the upgrade log file to feedback the upgrade abnormal information of the mobile terminal in time, so that the R&D personnel can take corresponding countermeasures according to the upgrade abnormal information in time.
  • a method for transmitting upgrade abnormality information applied to a mobile terminal side may be included, which may include:
  • the mobile terminal sends a result code corresponding to the cause of the upgrade abnormality to the device management server, including:
  • the mobile terminal sends a result code corresponding to the matching failure to the device management server;
  • the mobile terminal sends a result code corresponding to the upgrade failure to the device management server.
  • S502 The mobile terminal receives the idle log server information returned by the device management server.
  • the mobile terminal receiving the idle log server information returned by the device management server includes:
  • the mobile terminal receives a replacement instruction returned by the device management server; wherein the replacement instruction is used to add an inclusion on the extension node in the device management tree DMT of the mobile terminal
  • Leaf node for idle log server information.
  • S503 The mobile terminal sends a log file of the upgrade abnormality according to the idle log server information.
  • the method further includes:
  • the mobile terminal sends the device information corresponding to the mobile terminal to the idle log server.
  • the device information includes: manufacturer information, network operator information, model information, and an international mobile device identifier IMEI;
  • S602 The mobile terminal receives the authentication mode information sent by the idle log server.
  • S603 The mobile terminal sends the authentication information to the idle log server according to the authentication mode information.
  • S604 The mobile terminal receives the authentication success information sent by the idle log server.
  • upgrading an abnormal log file may include:
  • the log file of the abnormal upgrade may include: device information of the manufacturer (OEM), network operator (IPS), model (Model) of the mobile terminal, IMEI of the mobile device, and the upgrade package of the abnormal upgrade.
  • OEM manufacturer
  • IPS network operator
  • Model model
  • IMEI model
  • a method for transmitting upgrade abnormality information applied to a device management server side may be included, which may include:
  • the device management server After receiving the result code corresponding to the reason for the abnormality of the upgrade sent by the mobile terminal, the device management server acquires the idle log server information.
  • the device management server sends the idle log server information to the mobile terminal.
  • the device management server sends the idle log server information to the mobile terminal, including:
  • the device management server generates a replacement instruction and transmits the replacement instruction to the mobile terminal; wherein the replacement instruction is for adding a leaf node including the idle log server information on the extension node in the device management tree DMT of the mobile terminal.
  • the device manager may generate an alternate Replace instruction for adding an leaf node containing the LogURL in the Ext node in the mobile terminal DMT; wherein the LogURL represents the URL of the idle log server. The replacement command is then sent to the mobile terminal.
  • a mobile terminal 80 may include: an upgrade module 801, a first sending module 802, and a first receiving module 803;
  • the upgrade module 801 is configured to trigger the first sending module 802 after an abnormality occurs in the upgrade;
  • the first sending module 802 is configured to send a result code corresponding to the upgrade abnormality reason to the device management server; after receiving the idle log server information, the first receiving module 803 sends a log file of the upgrade abnormality according to the idle log server information;
  • the first receiving module 803 is configured to receive the idle log server information returned by the device management server.
  • the first sending module 802 is configured to send a result code corresponding to the reason for the upgrade abnormality to the device management server in the following manner:
  • the result code corresponding to the matching failure is sent to the device management server;
  • the upgrade package matches the firmware of the mobile terminal 80, and the upgrade module 801 fails to upgrade according to the successful upgrade package, the result code corresponding to the upgrade failure is sent to the device management server.
  • the first receiving module 803 is configured to: receive a replacement instruction returned by the device management server; wherein the replacement instruction is used to add the idle log server information on the extended node in the device management tree DMT of the mobile terminal 80.
  • Leaf node is configured to: receive a replacement instruction returned by the device management server; wherein the replacement instruction is used to add the idle log server information on the extended node in the device management tree DMT of the mobile terminal 80.
  • the first sending module 802 is further configured to:
  • the idle log server Before sending the log file of the upgrade abnormality according to the idle log server information, sending the device information corresponding to the mobile terminal 80 to the idle log server; after receiving the authentication mode information, the first receiving module according to the authentication mode information The idle log server sends the authentication information;
  • the first receiving module 803 is further configured to receive the authentication mode information sent by the idle log server, and receive the authentication success information sent by the idle log server.
  • a device management server 90 includes: a second receiving module 901, an obtaining module 902, and a second sending module 903;
  • the second receiving module 901 is configured to receive a result code corresponding to an upgrade abnormality reason sent by the mobile terminal;
  • the obtaining module 902 is configured to obtain idle log server information
  • the second sending module 903 is configured to send the idle log server information to the mobile terminal.
  • the second sending module 903 is configured to: generate a replacement instruction, and send the replacement instruction to the mobile terminal; wherein the replacement instruction is used to add the idle log server on the extended node in the device management tree DMT of the mobile terminal Leaf node for information.
  • the system 100 may include: a mobile terminal 80, a device management server 90, and a idle log server. 110; among them,
  • the mobile terminal 80 is configured to send a result code corresponding to the reason for the upgrade abnormality to the device management server 90 after the upgrade is abnormal.
  • the device management server 90 is configured to receive the idle log server 110 information after receiving the result code corresponding to the upgrade abnormality reason sent by the mobile terminal 80.
  • the idle log server 110 information is transmitted to the mobile terminal 80.
  • the device management server 90 feeds back the report address of the upgrade log file to the mobile terminal 80, so that the mobile terminal 80 can follow the The escalation log file is sent to the reporting address, and the upgrade abnormality information of the mobile terminal 80 is fed back in time, so that the R&D personnel can timely take corresponding countermeasures according to the upgrade abnormal information.
  • Embodiments of the present invention also provide a computer readable storage medium storing computer executable instructions for performing any of the methods described above.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the computer readable memory is stored in the computer readable memory.
  • the instructions in the production result include an article of manufacture of the instruction device that implements the functions specified in one or more blocks of the flowchart or in a flow or block of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program in a storage and a memory by a processor. / instruction to achieve its corresponding function.
  • the invention is not limited to any specific form of combination of hardware and software.
  • the above technical solution timely feedbacks the abnormal information of the upgrade of the mobile terminal, so that the R&D personnel can take corresponding countermeasures according to the upgrade abnormal information in time.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种升级异常信息的传输方法、设备和系统；该方法可以包括：移动终端在升级出现异常后，向设备管理服务器发送升级异常原因对应的结果码；移动终端接收设备管理服务器返回的空闲日志服务器信息；移动终端根据空闲日志服务器信息发送升级异常的日志文件。

Description

一种升级异常信息的传输方法、设备和系统 技术领域
本文涉及但不限于无线通信技术，尤指一种升级异常信息的传输方法、设备和系统。
背景技术
开放移动联盟设备管理(OMA DM，Open Mobile Alliance Device Management)工作组制定了统一的设备管理规范；空中固件更新(FOTA，Firmware Over The Air)则是OMA DM协议提供的一种用于管理移动终端的更新和升级的技术；终端厂商可以通过空中下载升级包的方式对移动终端中的固件或应用程序进行升级更新，不仅能够使得移动终端的固件或应用程序版本保持在最新状态，而且也为用户升级移动终端提供了便捷。
在当前OMA DM协议中，如果通过FOTA进行升级出现失败的时候，移动终端会向设备管理服务器上报相应的失败结果码，例如，升级包与移动终端固件不匹配所对应的结果码为403，移动终端通过升级包升级失败所对应的结果码为410。
但是，研发人员无法从服务器所接收到的失败结果码中，对升级失败的具体原因进行分析。研发人员需要等待升级失败的移动终端退回保修时，才能够通过从移动设备中相关的升级日志文件进行分析。因此，当前FOTA升级失败后仅上报失败结果码，无法及时地反馈至研发人员，从而无法让研发人员在FOTA升级失败后，采取相应的应对措施进行补救，例如，增加新的用于避免升级失败的升级包等。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种升级异常信息的传输方法、设备和系统，能够及时反馈移动终端的升级异常信息，从而便于研发人员能够及时根据升级异常信息采取相应的应对措施。
本发明实施例提供了一种升级异常信息的传输方法，所述方法包括：
移动终端在升级出现异常后，向设备管理服务器发送升级异常原因对应的结果码；
所述移动终端接收所述设备管理服务器返回的空闲日志服务器信息；
所述移动终端根据所述空闲日志服务器信息发送升级异常的日志文件。
可选的，所述移动终端在升级出现异常后，向设备管理服务器发送升级异常原因对应的结果码包括：
在所述升级包与所述移动终端的固件不匹配的情况下，所述移动终端向所述设备管理服务器发送匹配失败对应的结果码；
或者，在所述升级包与所述移动终端的固件相匹配，且所述移动终端根据匹配成功的升级包升级失败的情况下，所述移动终端向所述设备管理服务器发送升级失败对应的结果码。
可选的，所述移动终端接收所述设备管理服务器返回的空闲日志服务器信息包括：
所述移动终端接收由所述设备管理服务器返回的替换指令；其中，所述替换指令用于在所述移动终端的设备管理树DMT中的扩展节点上添加包含所述空闲日志服务器信息的叶子节点。
可选的，所述方法还包括：
所述移动终端根据所述空闲日志服务器信息发送升级异常的日志文件之前，
所述移动终端向所述空闲日志服务器发送移动终端对应的设备信息；
所述移动终端接收由所述空闲日志服务器所发送的鉴权模式信息；
所述移动终端根据所述鉴权模式信息向所述空闲日志服务器发送鉴权信息；
所述移动终端接收所述空闲日志服务器发送的鉴权成功信息。
可选的，所述升级异常的日志文件包括：
所述移动终端的设备信息、所述移动终端进行升级时的升级数据信息以 及所述移动终端进行升级时的升级流程日志。
本发明实施例提供了另一种升级异常信息的传输方法，所述方法包括：
设备管理服务器接收移动终端发送的升级异常原因对应的结果码之后，获取空闲日志服务器信息；
所述设备管理服务器将所述空闲日志服务器信息发送至所述移动终端。
可选的，所述设备管理服务器将所述空闲日志服务器信息发送至所述移动终端包括：
所述设备管理服务器生成替换指令，并将所述替换指令发送至所述移动终端；其中，所述替换指令用于在所述移动终端的设备管理树DMT中的扩展节点上添加包含所述空闲日志服务器信息的叶子节点。
本发明实施例提供了一种移动终端，所述移动终端包括：升级模块、第一发送模块和第一接收模块；其中，
所述升级模块，设置为对所述移动终端进行升级；并在升级出现异常后，触发所述第一发送模块；
所述第一发送模块，设置为向设备管理服务器发送升级异常原因对应的结果码；在第一接收模块接收到空闲日志服务器信息后，根据所述空闲日志服务器信息发送升级异常的日志文件；
所述第一接收模块，设置为接收所述设备管理服务器返回的空闲日志服务器信息。
可选的，所述第一发送模块是设置为采用如下方式实现向设备管理服务器发送升级异常原因对应的结果码：
在所述升级包与所述移动终端的固件不匹配的情况下，向所述设备管理服务器发送匹配失败对应的结果码；
或者，在所述升级包与所述移动终端的固件相匹配，且所述升级模块根据匹配成功的升级包升级失败的情况下，向所述设备管理服务器发送升级失败对应的结果码。
可选的，所述第一接收模块是设置为：接收由所述设备管理服务器返回 的替换指令；其中，所述替换指令用于在所述移动终端的设备管理树DMT中的扩展节点上添加包含所述空闲日志服务器信息的叶子节点。
可选的，所述第一发送模块，还设置为：
根据所述空闲日志服务器信息发送升级异常的日志文件之前，在第一接收模块接收到鉴权模式信息后，根据所述鉴权模式信息向所述空闲日志服务器发送鉴权信息；
所述第一接收模块，还设置为接收由所述空闲日志服务器所发送的鉴权模式信息；接收所述空闲日志服务器发送的鉴权成功信息。
本发明实施例提供了一种设备管理服务器，所述设备管理服务器，包括：第二接收模块、获取模块和第二发送模块；其中，
所述第二接收模块，设置为接收移动终端发送的升级异常原因对应的结果码；
所述获取模块，设置为获取空闲日志服务器信息；
所述第二发送模块，设置为将所述空闲日志服务器信息发送至所述移动终端。
可选的，所述第二发送模块是设置为：生成替换指令，并将所述替换指令发送至所述移动终端；其中，所述替换指令用于在所述移动终端的设备管理树DMT中的扩展节点上添加包含所述空闲日志服务器信息的叶子节点。
本发明实施例提供了一种升级异常信息的传输系统，所述系统包括：移动终端、设备管理服务器和日志服务器；其中，
所述移动终端，设置为在升级出现异常后，向所述设备管理服务器发送升级异常原因对应的结果码；
以及，接收所述设备管理服务器返回的空闲日志服务器信息；
以及，根据所述空闲日志服务器信息发送升级异常的日志文件；
所述设备管理服务器，设置为接收所述移动终端发送的升级异常原因对应的结果码之后，获取空闲日志服务器信息；
以及，将所述空闲日志服务器信息发送至所述移动终端。
本发明实施例还提出了一种计算机可读存储介质，存储有计算机可执行指令，计算机可执行指令用于执行上述描述的任意一个方法。
本发明实施例提供了一种升级异常信息的传输方法、设备和系统；当移动终端向设备管理服务器上报失败结果码之后，设备管理服务器向移动终端反馈升级日志文件的上报地址，使得移动终端能够按照该上报地址发送升级日志文件，及时反馈移动终端的升级异常信息，从而便于研发人员能够及时根据升级异常信息采取相应的应对措施。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明实施例提供的一种应用场景示意图；
图2为本发明实施例提供的升级异常信息的传输方法流程示意图；
图3为本发明实施例提供的一种日志服务器对移动终端的鉴权过程示意图；
图4为本发明实施例提供的一种日志文件结构示意图；
图5为本发明实施例提供的一种应用于移动终端侧的升级异常信息的传输方法流程示意图；
图6为本发明实施例提供的一种对移动终端进行鉴权的流程示意图；
图7为本发明实施例提供的一种应用于设备管理服务器侧的升级异常信息的传输方法流程示意图；
图8为本发明实施例提供的一种移动终端的结构示意图；
图9为本发明实施例提供的一种设备管理服务器结构示意图；
图10为本发明实施例提供的一种升级异常信息的传输系统的结构示意图。
本发明的实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述。
参见图1，其示出了本发明实施例提供的一种应用场景示意，在该场景中，包括：遵循OMA DM协议的移动终端、设备管理DM服务器、设置为为移动终端提供升级包的下载服务器以及设置为存储日志文件的日志服务器。四者之间的连接关系如图1所示，在移动终端中，内嵌了利用升级包对移动终端进行升级的设备升级代理(DUA，Device Update Agent)，因此，在升级过程中，DUA可以认为是移动终端的一部分。
基于图1所示的应用场景，提出本发明方法多个可选地实施例。
实施例一
基于图1所示的应用场景，参见图2，其示出了本发明实施例提供的升级异常信息的传输方法流程，该流程可以包括：
S201：移动终端在升级出现异常后，向设备管理服务器发送升级异常原因所对应的结果码；
需要说明的是，移动终端可以通过将自身的设备信息以及软件版本号发送至DM服务器；随后，DM服务器根据移动终端的设备信息及软件版本号获取该移动设备软件版本升级包所在的下载服务器的地址，并通过向移动终端发送替换命令，将移动终端的设备管理树(DMT，OMA Device Managemet Tree)中下载服务器的地址替换为之前所获取的该移动设备软件版本升级包所在的下载服务器的地址；接着，移动终端根据下载服务器的地址下载升级包，并通过DUA利用升级包对移动终端进行升级。
具体如何获取移动设备软件版本升级包所在的下载服务器的地址可以采用本领域技术人员的熟知技术实现，并不用于限定本发明实施例的保护范围，这里不再赘述。
可以理解地，移动终端升级成功时，会向DM服务器发送Alert命令来上报指示升级成功的结果码200；但是，当移动终端在升级中出现异常时，会根据异常的原因向生成相应的结果码，并向DM服务器发送Alert命令来上报异常原因所对应的结果码。例如，升级包的校验码与真实的校验码不匹配时，相应的结果码为402；升级包与移动终端的固件不匹配时，相应的结果码为403；升级包数字签名验证失败时，相应的结果码为404；移动终端根据升级包进行升级失败时，相应的结果码为410等等，在OMA DM协议中 关于固件升级的相关内容包括：结果码的结构为2XX时，表示升级结果成功；结果码的结构为4XX或5XX时，表示升级异常；其中，X表示数字。
示例性地，基于上述多种升级异常原因所对应的结果码，在步骤S201中，移动终端在升级出现异常后，向设备管理服务器发送升级异常原因对应的结果码包括：
在升级包与移动终端的固件不匹配的情况下，移动终端向设备管理服务器发送匹配失败对应的结果码；
或者，在升级包与移动终端的固件相匹配，且移动终端根据匹配成功的升级包升级失败的情况下，移动终端向设备管理服务器发送升级失败对应的结果码。
在具体实现过程中，移动终端可以将结果码封装于Alert命令，并将封装后的Alert命令发送至设备管理服务器。
S202：设备管理服务器接收到升级异常原因所对应的结果码后，获取空闲日志服务器信息；
在实现过程中，设备管理服务器可以根据当前日志服务器的负载量和通信量等吞吐量指标，从自身所辖的日志服务器中选取空闲的日志服务器，并生成对应的空闲日志服务器信息，可选地，空闲日志服务器信息可以包括空闲日志服务器的统一资源定位符(URL，Uniform Resource Locator)。
其中，在选取空闲的日志服务器时，根据当前日志服务器的负载量和通信量等吞吐量指标，使得日志服务武器的负载均衡。
S203：设备管理服务器将空闲日志服务器信息发送至移动终端；
示例性地，设备管理器可以生成替换指令，并且将替换指令发送至移动终端；而替换指令可以用于在移动终端的设备管理树(DMT，Device Management Tree)中的扩展(Ext，Extension)节点上添加包含空闲日志服务器信息的叶子节点。
在具体实现过程中，设备管理器可以对移动终端发送的Alert命令进行回复，并且生成用于在移动终端DMT中的Ext节点添加包含LogURL的叶子节点的替换(Replace)指令；其中，LogURL表示空闲日志服务器的URL。 随后，将该替换指令发送至移动终端。
S204：移动终端根据空闲日志服务器信息发送升级异常的日志文件。
可以理解地，移动终端在日常运行的过程中，都会对运行过程进行记录，从而产生日志文件，相应地，在升级过程中，移动终端也会记录下升级过程，产生升级过程的日志文件；那么，当升级过程出现异常时，移动终端所记录的升级过程的日志文件则是研发人员针对升级异常进行分析的依据。
当移动终端根据空闲日志服务器信息发送升级异常的日志文件至空闲日志服务器后，研发人员就能够及时地从日志服务器中读取升级异常的日志文件并进行分析，而不需要等到移动终端退回之后，从移动终端进行日志文件的导出在进行分析，从而是研发人员及时获取移动终端的升级异常信息，也能够及时根据升级异常信息采取相应的应对措施，例如，增加新的用于避免升级失败的升级包等。
具体实现过程中，移动终端可以采用超文本传输协议(HTTP，HyperText Transfer Protocol)上传日志明文数据，可以采用加密算法或采用超文本传输安全协议(HTTPS，Hyper Text Transfer Protocol over Secure Socket Layer)传送，还可以利用文件传输协议(FTP，File Transfer Protocol)等其它文件传输协议发送日志文件；具体的传输方式可以由日志服务器进行设定或者由日志服务器与移动终端进行协商确定。
示例性地，在步骤S204之前，参见图3，本方法还可以包括空闲日志服务器对移动终端的鉴权过程，包括：
S301：移动终端向空闲日志服务器发送移动终端对应的设备信息；
可选的，设备信息包括：制造商信息、网络运营商信息、型号信息、国际移动设备标识(IMEI，International Mobile Equipment Identity)；
S302：空闲日志服务器向移动终端发送鉴权模式信息；
本步骤中，鉴权模式信息包括基本鉴权信息和摘要鉴权信息。
S303：移动终端根据鉴权模式信息向空闲日志服务器发送鉴权信息；
S304：空闲日志服务器向移动终端发送鉴权成功信息。
在鉴权成功之后，移动终端就可以向空闲日志服务器发送升级异常的日 志文件。需要说明的是，由于移动终端可以将自身的设备信息，诸如，移动终端对应的制造商信息、网络运营商信息、型号信息、IMEI封装在日志文件中，因此，步骤S301在某些特定的应用场景下可以忽略。此时，移动终端自身的设备信息可以通过空闲日志服务器对日志文件进行解析获得。
示例性地，升级异常的日志文件，可以包括：移动终端的设备信息、移动终端进行升级时的升级数据信息以及移动终端进行升级时的升级流程日志。在具体实现过程中，参见图4所示的日志文件结构，升级异常的日志文件可以包括：移动终端的制造商(OEM，Original Equipment Manufacturer)、网络运营商(IPS，Internet Service Provider)、型号(Model)、移动设备的IMEI等设备信息；以及，升级异常的升级包文件(File)或镜像(Image)名、被升级数据块所在文件或内存技术设备(MTD，Memory Technology Device)的起始偏移地址(Binary Data Offset Address)、被升级数据块的大小(Binary Data Size)；以及被升级二进制数据块(Binary Data)和移动终端中DUA进行升级的升级流程日志(DUA log)。
本实施例提供的升级异常信息的传输方法，当移动终端向设备管理服务器上报失败结果码之后，设备管理服务器向移动终端反馈对升级日志文件进行上报的空闲日志服务器地址，使得移动终端能够按照空闲日志服务器地址发送升级日志文件，及时反馈移动终端的升级异常信息，从而便于研发人员能够及时根据升级异常信息采取相应的应对措施。
实施例二
基于前述实施例相同的技术构思，参见图5，其示出了本发明实施例提供的一种应用于移动终端侧的升级异常信息的传输方法，可以包括：
S501：移动终端在升级出现异常后，向设备管理服务器发送升级异常原因对应的结果码；
示例性地，移动终端在升级出现异常后，向设备管理服务器发送升级异常原因对应的结果码包括：
在升级包与移动终端的固件不匹配的情况下，移动终端向设备管理服务器发送匹配失败对应的结果码；
或者，在升级包与移动终端的固件相匹配，且移动终端根据匹配成功的升级包升级失败的情况下，移动终端向设备管理服务器发送升级失败对应的结果码。
S502：移动终端接收设备管理服务器返回的空闲日志服务器信息；
示例性地，移动终端接收设备管理服务器返回的空闲日志服务器信息包括：
移动终端接收由设备管理服务器返回的替换指令；其中，替换指令用于在移动终端的设备管理树DMT中的扩展节点上添加包含
空闲日志服务器信息的叶子节点。
S503：移动终端根据空闲日志服务器信息发送升级异常的日志文件。
示例性地，参见图6，移动终端根据空闲日志服务器信息发送升级异常的日志文件之前，方法还包括：
S601：移动终端向空闲日志服务器发送移动终端对应的设备信息；
可选的，设备信息包括：制造商信息、网络运营商信息、型号信息、国际移动设备标识IMEI；
S602：移动终端接收由空闲日志服务器所发送的鉴权模式信息；
S603：移动终端根据鉴权模式信息向空闲日志服务器发送鉴权信息；
S604：移动终端接收空闲日志服务器发送的鉴权成功信息。
示例性地，升级异常的日志文件，可以包括：
移动终端的设备信息、移动终端进行升级时的升级数据信息以及移动终端进行升级时的升级流程日志。在具体实现过程中，升级异常的日志文件可以包括：移动终端的制造商(OEM)、网络运营商(IPS)、型号(Model)、移动设备的IMEI等设备信息；以及，升级异常的升级包文件(File)或镜像(Image)名、被升级数据块所在文件或内存技术设备(MTD，Memory Technology Device)的起始偏移地址(Binary Data Offset Address)、被升级数据块的大小(Binary Data Size)；以及被升级二进制数据块(Binary Data)和移动终端中DUA进行升级的升级流程日志(DUA log)。
实施例三
基于前述实施例相同的技术构思，参见图7，其示出了本发明实施例提供的一种应用于设备管理服务器侧的升级异常信息的传输方法，可以包括：
S701：设备管理服务器接收移动终端发送的升级异常原因对应的结果码之后，获取空闲日志服务器信息；
S702：设备管理服务器将空闲日志服务器信息发送至移动终端。
示例性地，设备管理服务器将空闲日志服务器信息发送至移动终端包括：
设备管理服务器生成替换指令，并将替换指令发送至移动终端；其中，替换指令用于在移动终端的设备管理树DMT中的扩展节点上添加包含空闲日志服务器信息的叶子节点。在具体实现过程中，设备管理器可以生成用于在移动终端DMT中的Ext节点添加包含LogURL的叶子节点的替换Replace指令；其中，LogURL表示空闲日志服务器的URL。随后，将该替换指令发送至移动终端。
实施例四
基于前述实施例相同的技术构思，参见图8，其示出了本发明实施例提供的一种移动终端80，可以包括：升级模块801、第一发送模块802和第一接收模块803；其中
升级模块801，设置为在升级出现异常后，触发第一发送模块802；
第一发送模块802，设置为向设备管理服务器发送升级异常原因对应的结果码；在第一接收模块803接收到空闲日志服务器信息后，根据所述空闲日志服务器信息发送升级异常的日志文件；
第一接收模块803，设置为接收设备管理服务器返回的空闲日志服务器信息。
可选地，第一发送模块802是设置为采用如下方式实现向设备管理服务器发送升级异常原因对应的结果码：
在升级包与移动终端80的固件不匹配的情况下，向设备管理服务器发送匹配失败对应的结果码；
或者，在升级包与移动终端80的固件相匹配，且升级模块801根据匹配成功的升级包升级失败的情况下，向设备管理服务器发送升级失败对应的结果码。
可选地，第一接收模块803是设置为：接收由设备管理服务器返回的替换指令；其中，替换指令用于在移动终端80的设备管理树DMT中的扩展节点上添加包含空闲日志服务器信息的叶子节点。
可选地，第一发送模块802，还设置为：
根据所述空闲日志服务器信息发送升级异常的日志文件之前，向空闲日志服务器发送移动终端80对应的设备信息；在第一接收模块接收到鉴权模式信息后，根据所述鉴权模式信息向所述空闲日志服务器发送鉴权信息；
第一接收模块803，还设置为接收由空闲日志服务器所发送的鉴权模式信息；接收空闲日志服务器发送的鉴权成功信息。
实施例五
基于前述实施例相同的技术构思，参见图9，其示出了本发明实施例提供的一种设备管理服务器90，包括：第二接收模块901、获取模块902和第二发送模块903；其中，
第二接收模块901，设置为接收移动终端发送的升级异常原因对应的结果码；
获取模块902，设置为获取空闲日志服务器信息；
第二发送模块903，设置为将空闲日志服务器信息发送至移动终端。
可选地，第二发送模块903是设置为：生成替换指令，并将替换指令发送至移动终端；其中，替换指令用于在移动终端的设备管理树DMT中的扩展节点上添加包含空闲日志服务器信息的叶子节点。
实施例六
基于前述实施例相同的技术构思，参见图10，其示出了本发明实施例提供的一种升级异常信息的传输系统100，系统100可以包括：移动终端80、设备管理服务器90和空闲日志服务器110；其中，
移动终端80，设置为在升级出现异常后，向设备管理服务器90发送升级异常原因对应的结果码；
以及，接收设备管理服务器90返回的空闲日志服务器110信息；
以及，根据空闲日志服务器110信息发送升级异常的日志文件；
设备管理服务器90，设置为接收移动终端80发送的升级异常原因对应的结果码之后，获取空闲日志服务器110信息；
以及，将空闲日志服务器110信息发送至移动终端80。
本实施例提供的升级异常信息的传输系统100，当移动终端80向设备管理服务器90上报失败结果码之后，设备管理服务器90向移动终端80反馈升级日志文件的上报地址，使得移动终端80能够按照该上报地址发送升级日志文件，及时反馈移动终端80的升级异常信息，从而便于研发人员能够及时根据升级异常信息采取相应的应对措施。
本发明实施例还提出了一种计算机可读存储介质，存储有计算机可执行指令，计算机可执行指令用于执行上述描述的任意一个方法。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器 中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储与存储器中的程序/指令来实现其相应功能。本发明不限于任何特定形式的硬件和软件的结合。
以上，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。
工业实用性
上述技术方案及时的反馈了移动终端的升级异常信息，从而便于研发人员及时的根据升级异常信息采取相应的应对措施。

Claims (14)

  1. 一种升级异常信息的传输方法，所述方法包括：
    移动终端在升级出现异常后，向设备管理服务器发送升级异常原因对应的结果码；
    所述移动终端接收所述设备管理服务器返回的空闲日志服务器信息；
    所述移动终端根据所述空闲日志服务器信息发送升级异常的日志文件。
  2. 根据权利要求1所述的方法，其中，所述移动终端在升级出现异常后，向设备管理服务器发送升级异常原因对应的结果码包括：
    在所述升级包与所述移动终端的固件不匹配的情况下，所述移动终端向所述设备管理服务器发送匹配失败对应的结果码；
    或者，在所述升级包与所述移动终端的固件相匹配，且所述移动终端根据匹配成功的升级包升级失败的情况下，所述移动终端向所述设备管理服务器发送升级失败对应的结果码。
  3. 根据权利要求1所述的方法，其中，所述移动终端接收所述设备管理服务器返回的空闲日志服务器信息包括：
    所述移动终端接收由所述设备管理服务器返回的替换指令；其中，所述替换指令用于在所述移动终端的设备管理树DMT中的扩展节点上添加包含所述空闲日志服务器信息的叶子节点。
  4. 根据权利要求1所述的方法，所述方法还包括：
    所述移动终端根据所述空闲日志服务器信息发送升级异常的日志文件之前，
    所述移动终端接收由所述空闲日志服务器所发送的鉴权模式信息；
    所述移动终端根据所述鉴权模式信息向所述空闲日志服务器发送鉴权信息；
    所述移动终端接收所述空闲日志服务器发送的鉴权成功信息。
  5. 根据权利要求1所述的方法，其中，所述升级异常的日志文件包括：
    所述移动终端的设备信息、所述移动终端进行升级时的升级数据信息以及所述移动终端进行升级时的升级流程日志。
  6. 一种升级异常信息的传输方法，所述方法包括：
    设备管理服务器接收移动终端发送的升级异常原因对应的结果码之后，获取空闲日志服务器信息；
    所述设备管理服务器将所述空闲日志服务器信息发送至所述移动终端。
  7. 根据权利要求5所述的方法，其中，所述设备管理服务器将所述空闲日志服务器信息发送至所述移动终端包括：
    所述设备管理服务器生成替换指令，并将所述替换指令发送至所述移动终端；其中，所述替换指令用于在所述移动终端的设备管理树DMT中的扩展节点上添加包含所述空闲日志服务器信息的叶子节点。
  8. 一种移动终端，所述移动终端包括：升级模块、第一发送模块和第一接收模块；其中，
    所述升级模块，设置为在升级出现异常后，触发所述第一发送模块；
    所述第一发送模块，设置为向设备管理服务器发送升级异常原因对应的结果码；在第一接收模块接收到空闲日志服务器信息后，根据所述空闲日志服务器信息发送升级异常的日志文件；
    所述第一接收模块，设置为接收所述设备管理服务器返回的空闲日志服务器信息。
  9. 根据权利要求8所述的移动终端，其中，所述第一发送模块是设置为采用如下方式实现向设备管理服务器发送升级异常原因对应的结果码：
    在所述升级包与所述移动终端的固件不匹配的情况下，向所述设备管理服务器发送匹配失败对应的结果码；
    或者，在所述升级包与所述移动终端的固件相匹配，且所述升级模块根据匹配成功的升级包升级失败的情况下，向所述设备管理服务器发送升级失败对应的结果码。
  10. 根据权利要求8所述的移动终端，其中，所述第一接收模块是设置 为：接收由所述设备管理服务器返回的替换指令；其中，所述替换指令用于在所述移动终端的设备管理树DMT中的扩展节点上添加包含所述空闲日志服务器信息的叶子节点。
  11. 根据权利要求8所述的移动终端，所述第一发送模块，还设置为：
    根据所述空闲日志服务器信息发送升级异常的日志文件之前，向所述空闲日志服务器发送移动终端对应的设备信息；在第一接收模块接收到鉴权模式信息后，根据所述鉴权模式信息向所述空闲日志服务器发送鉴权信息；
    所述第一接收模块，还设置为接收由所述空闲日志服务器所发送的鉴权模式信息；接收所述空闲日志服务器发送的鉴权成功信息。
  12. 一种设备管理服务器，所述设备管理服务器，包括：第二接收模块、获取模块和第二发送模块；其中，
    所述第二接收模块，设置为接收移动终端发送的升级异常原因对应的结果码；
    所述获取模块，设置为获取空闲日志服务器信息；
    所述第二发送模块，设置为将所述空闲日志服务器信息发送至所述移动终端。
  13. 根据权利要求12所述的设备管理服务器，其中，所述第二发送模块是设置为：生成替换指令，并将所述替换指令发送至所述移动终端；其中，所述替换指令用于在所述移动终端的设备管理树DMT中的扩展节点上添加包含所述空闲日志服务器信息的叶子节点。
  14. 一种升级异常信息的传输系统，所述系统包括：移动终端、设备管理服务器和日志服务器；其中，
    所述移动终端，设置为在升级出现异常后，向所述设备管理服务器发送升级异常原因对应的结果码；
    以及，接收所述设备管理服务器返回的空闲日志服务器信息；
    以及，根据所述空闲日志服务器信息发送升级异常的日志文件；
    所述设备管理服务器，设置为接收所述移动终端发送的升级异常原因对 应的结果码之后，获取空闲日志服务器信息；
    以及，将所述空闲日志服务器信息发送至所述移动终端。
PCT/CN2016/095343 2016-01-19 2016-08-15 一种升级异常信息的传输方法、设备和系统 WO2017124736A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610034207.XA CN106982445A (zh) 2016-01-19 2016-01-19 一种升级异常信息的传输方法、设备和系统
CN201610034207.X 2016-01-19

Publications (1)

Publication Number Publication Date
WO2017124736A1 true WO2017124736A1 (zh) 2017-07-27

Family

ID=59339941

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/095343 WO2017124736A1 (zh) 2016-01-19 2016-08-15 一种升级异常信息的传输方法、设备和系统

Country Status (2)

Country Link
CN (1) CN106982445A (zh)
WO (1) WO2017124736A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109739718A (zh) * 2018-11-30 2019-05-10 贵阳朗玛信息技术股份有限公司 日志报警方法及装置
CN111405543A (zh) * 2019-01-02 2020-07-10 中国移动通信有限公司研究院 一种无线固件升级中的数据包推送下载方法、装置及系统
CN112307276A (zh) * 2020-08-31 2021-02-02 北京沃东天骏信息技术有限公司 日志收集方法、装置和系统
CN113759394A (zh) * 2021-07-26 2021-12-07 广州南方卫星导航仪器有限公司 一种gnss接收机远程维护系统、方法及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109428936B (zh) * 2017-09-04 2021-07-13 中国移动通信有限公司研究院 App的升级方法、装置、系统、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1969504A (zh) * 2004-07-09 2007-05-23 Lg电子株式会社 设备管理系统和设备管理命令调度方法
EP1929706A1 (en) * 2005-10-01 2008-06-11 LG Electronics Inc. Device management system using log management object and method for generating and controlling logging data therein
CN101400044A (zh) * 2007-09-28 2009-04-01 华为技术有限公司 操作结果上报方法和终端
CN103036706A (zh) * 2012-11-26 2013-04-10 青岛海信传媒网络技术有限公司 应用升级异常的本地处理方法

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070093243A1 (en) * 2005-10-25 2007-04-26 Vivek Kapadekar Device management system
JP5191705B2 (ja) * 2007-08-09 2013-05-08 京セラドキュメントソリューションズ株式会社 保守管理システム、データベースサーバ、保守管理プログラムおよび保守管理方法
CN101170455B (zh) * 2007-11-20 2010-12-29 中兴通讯股份有限公司 异常信息自动上报方法和装置
CN101184301A (zh) * 2007-12-14 2008-05-21 中兴通讯股份有限公司 移动终端远程固件升级方法及系统
US8083140B1 (en) * 2008-02-05 2011-12-27 Sprint Communications Company L.P. System and method of over-the-air provisioning
US8005067B2 (en) * 2008-10-31 2011-08-23 Avaya Inc. Method for communication information recall in an enterprise network
CN102158814A (zh) * 2010-02-11 2011-08-17 希姆通信息技术（上海）有限公司 一种实现模块端远程升级及管理的服务器处理方法
CN101808009B (zh) * 2010-03-08 2014-01-01 中兴通讯股份有限公司 一种网络设备升级的方法和系统
CN101937533A (zh) * 2010-09-08 2011-01-05 成都四方信息技术有限公司 基于ota空中下载技术的综合调度终端支撑系统工作方法
CN102136934B (zh) * 2010-10-21 2015-01-21 华为技术有限公司 实现Zigbee设备远程升级的方法、装置及网络系统
US8750862B2 (en) * 2010-10-26 2014-06-10 At&T Intellectual Property I, L.P. Performance diagnosis of wireless equipment and a wireless network over out-of-band communication
CN103051956A (zh) * 2012-12-24 2013-04-17 乐视致新电子科技（天津）有限公司 一种实现日志上报和故障诊断的机顶盒及其方法
CN104253704B (zh) * 2013-06-28 2018-10-26 腾讯科技（深圳）有限公司 一种上报终端日志的方法、装置和系统
CN104915234B (zh) * 2015-06-10 2019-09-10 Tcl集团股份有限公司 一种Android移动终端升级上报方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1969504A (zh) * 2004-07-09 2007-05-23 Lg电子株式会社 设备管理系统和设备管理命令调度方法
EP1929706A1 (en) * 2005-10-01 2008-06-11 LG Electronics Inc. Device management system using log management object and method for generating and controlling logging data therein
CN101400044A (zh) * 2007-09-28 2009-04-01 华为技术有限公司 操作结果上报方法和终端
CN103036706A (zh) * 2012-11-26 2013-04-10 青岛海信传媒网络技术有限公司 应用升级异常的本地处理方法

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109739718A (zh) * 2018-11-30 2019-05-10 贵阳朗玛信息技术股份有限公司 日志报警方法及装置
CN111405543A (zh) * 2019-01-02 2020-07-10 中国移动通信有限公司研究院 一种无线固件升级中的数据包推送下载方法、装置及系统
CN111405543B (zh) * 2019-01-02 2023-04-07 中国移动通信有限公司研究院 一种无线固件升级中的数据包推送下载方法、装置及系统
CN112307276A (zh) * 2020-08-31 2021-02-02 北京沃东天骏信息技术有限公司 日志收集方法、装置和系统
CN113759394A (zh) * 2021-07-26 2021-12-07 广州南方卫星导航仪器有限公司 一种gnss接收机远程维护系统、方法及存储介质

Also Published As

Publication number Publication date
CN106982445A (zh) 2017-07-25

Similar Documents

Publication Publication Date Title
US11606677B2 (en) Method for sharing application between terminals, and terminal
WO2017124736A1 (zh) 一种升级异常信息的传输方法、设备和系统
US9037642B2 (en) Platform for deployment and distribution of modules to endpoints
CN104811484B (zh) Fota升级方法和装置
EP3029566A1 (en) Application packaging device and method
US20220083326A1 (en) Upgrading method and system, server, and terminal device
CN104077160B (zh) 一种升级安卓软件的方法、设备和系统
KR20170094765A (ko) 차량용 무선 소프트웨어 업데이트 방법 및 장치
JP2015092374A5 (zh)
CN112867988A (zh) 由移动设备实现合规设置以遵循配置场景
CN104125276A (zh) 升级方法及装置
CN112970020A (zh) 使用分布式账本监视设备部件
CN109391673A (zh) 一种管理更新文件的方法、系统及终端设备
JP7279899B2 (ja) データ収集方法、データ収集装置、データ収集デバイスおよびコンピュータ可読記憶媒体
CN109814889B (zh) 用于更新源代码库的方法和装置
CN106339273A (zh) 一种应用程序修复方法、终端及服务器
CN112416396B (zh) 一种应用程序更新方法和系统
CN107656742A (zh) 一种软件产品发布方法和装置
CN109495874A (zh) Profile下载的方法和装置
KR20120111852A (ko) 사물통신에서 원격 소프트웨어를 분리 업그레이드하는 방법 및 장치
CN111399867A (zh) 一种软件升级方法、装置、设备及计算机可读存储介质
WO2016202047A1 (zh) 应用推荐方法、装置、服务器和终端
CN113132409B (zh) 一种数据传输方法及装置
CN115174389A (zh) 一种升级方法、装置、设备及可读存储介质
CN108830050A (zh) 计算机程序的注册方法、装置和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16885996

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16885996

Country of ref document: EP

Kind code of ref document: A1