# US 2014/0208307 A1 · Method and System for Upgrading CPE Firmware > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0208307 A1 - Document ID: US20140208307A1 - Status: Published application - Kind: A1 - Application number: 14/344,022 - Filed: 2011-11-23 - Published: 2014-07-24 - Earliest claimed: 2011-09-09 - Assignees: Zte Corporation - Inventors: Wei Zhou; Quansheng Jiang - Web page: https://patentgrep.com/patent/US20140208307A1 ## CPC - G06F 8/60: Software deployment - G06F 8/654: using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories - G06F 9/44536: {Selecting among different versions} - H04W 8/245: {from a network towards a terminal} - H04W 24/02: Arrangements for optimising operational condition - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Disclosed are a method and system for upgrading CPE firmware. An upgradable module in the CPE firmware is resolved. Detail information of the module is added to a configuration management file. The implementation of an upgrade management of the upgradable module in the firmware via the configuration management file allows for convenient selection of a corresponding module upgrade. When one module fails a validation during a downloading process, the need to perform a re-download process is obviated for other modules, thus solving the shortcoming in the prior art, in which a unified interface is used for the upgrade of all modules, of having to re-download all module upgrade packets when the validation fails during the download process, thereby improving the efficiency and ease of user of the upgrading. ## Claims ### Claim 1 A method for upgrading Customer Premises Equipment (CPE) firmware, comprising: a server adding module information in the CPE firmware to a management configuration file; and the server upgrading a module to be upgraded in the CPE firmware based on the management configuration file. ### Claim 2 (depends on 1) The method for upgrading the CPE firmware according to claim 1, wherein the server adding the module information in the CPE firmware to the management configuration file is: the management configuration file being a parameter tree file; each module corresponding to a node in the parameter tree file, adding a child node under each node, in leaf nodes of the child node storing various attributes of the module, wherein the attributes comprise module name, information whether there is a dependence module during upgrading, module version information, check code and module integrity check method; and adding a module dependence node under the child node, and in the module dependence node storing dependence module information which is needed when upgrading the module. ### Claim 3 (depends on 1) The method for upgrading the CPE firmware according to claim 1, wherein the server upgrading the module to be upgraded in the CPE firmware based on the management configuration file is: after the server starts a session with the CPE, the server sending to the CPE information of the module to be upgraded; and the CPE judging a module truly to be upgraded according to the information of the module to be upgraded, and downloading and upgrading the module truly to be upgraded. ### Claim 4 (depends on 3) The method for upgrading the CPE firmware according to claim 3, wherein the information of the module to be upgraded comprises: a module download address, module version information, module check method, module check code and module size; and the CPE judging the module truly to be upgraded according to the information of the module to be upgraded and downloading and upgrading the module truly to be upgraded is: after receiving the information of the module to be upgraded, the CPE judging whether the information of the module to be upgraded is consistent with corresponding module information saved locally, and if the information of the module to be upgraded is consistent with the corresponding module information saved locally, no upgrade needed; and if there is a module which has inconsistent information, downloading the module according to the module download address; and checking the downloaded module according to the check method corresponding to the module, and if the check result is true, then starting to upgrade the module, otherwise, reporting error information to the server. ### Claim 5 (depends on 1) The method for upgrading the CPE firmware according to claim 1. wherein in the case that the server upgrades the CPE firmware based on Open Mobile Alliance-Device Management (OMA-DM) protocol, when it is required to upgrade a new module, the server acquiring from the CPE information of the new module and adding the information of the new module into the management configuration file. ### Claim 6 A system for upgrading Customer Premises Equipment (CPE) firmware, comprising: a server and CPE; wherein the server is configured to add module information in the CPE firmware to a management configuration file and upgrade a module to be upgraded in the CPE firmware based on the management configuration file; and the CPE is configured to upgrade the module to be upgraded in cooperation with the server. ### Claim 7 (depends on 6) The system for upgrading the CPE firmware according to claim 6, wherein the management configuration file is a parameter tree file; each module corresponds to a node in the parameter tree file, a child node is added under each node, various attributes of the module are stored in leaf nodes of the child node, wherein the attributes comprise: module name, information whether there is a dependence module during upgrading, module version information, check code and module integrity check method; and a module dependence node is added under the child node, and the dependence module information which is needed when upgrading the module is stored on the module dependence node. ### Claim 8 (depends on 6) The system for upgrading the CPE firmware according to claim 6, wherein the server is further configured to, after starting a session with the CPE, send to the CPE information of the module to be upgraded; and the CPE is further configured to judge a module truly to be upgraded according to the information of the module to be upgraded, and to download and upgrade the module truly to be upgraded. ### Claim 9 (depends on 8) The system for upgrading the CPE firmware according to claim 8, wherein the information of the module to be upgraded comprises a module download address, module version information, module check method, module check code and module size; and the CPE in particular comprises a judgment downloading module and a check upgrading module; wherein the judgment downloading module is configured to, after receiving the information of the module to be upgraded, judge whether the information of the module to be upgraded is consistent with corresponding module information saved locally, and if the information of the module to be upgraded is consistent with the corresponding module information saved locally, then need no upgrade; and if there is a module which has inconsistent information, then download the module according to the module download address; and the check upgrading module is configured to check the downloaded module according to the check method corresponding to the module, and if the check result is true, then start to upgrade the module, otherwise, report error information to the server. ### Claim 10 (depends on 6) The system for upgrading the CPE firmware according to claim 6, wherein in the case that the server upgrades the CPE firmware based on Open Mobile Alliance-Device Management (OMA-DM) protocol, when it is required to upgrade a new module, the server acquires from the CPE information of the new module and adds the information of the new module into the management configuration file. ### Claim 11 (depends on 2) The method for upgrading the CPE firmware according to claim 2, wherein in the case that the server upgrades the CPE firmware based on Open Mobile Alliance-Device Management (OMA-DM) protocol, when it is required to upgrade a new module, the server acquiring from the CPE information of the new module and adding the information of the new module into the management configuration file. ### Claim 12 (depends on 3) The method for upgrading the CPE firmware according to claim 3, wherein in the case that the server upgrades the CPE firmware based on Open Mobile Alliance-Device Management (OMA-DM) protocol, when it is required to upgrade a new module, the server acquiring from the CPE information of the new module and adding the information of the new module into the management configuration file. ### Claim 13 (depends on 4) The method for upgrading the CPE firmware according to claim 4, wherein in the case that the server upgrades the CPE firmware based on Open Mobile Alliance-Device Management (OMA-DM) protocol, when it is required to upgrade a new module, the server acquiring from the CPE information of the new module and adding the information of the new module into the management configuration file. ### Claim 14 (depends on 5) The method for upgrading the CPE firmware according to claim 5, wherein in the case that the server upgrades the CPE firmware based on Open Mobile Alliance-Device Management (OMA-DM) protocol, when it is required to upgrade a new module, the server acquiring from the CPE information of the new module and adding the information of the new module into the management configuration file. ### Claim 15 (depends on 7) The system for upgrading the CPE firmware according to claim 7, wherein in the case that the server upgrades the CPE firmware based on Open Mobile Alliance-Device Management (OMA-DM) protocol, when it is required to upgrade a new module, the server acquires from the CPE information of the new module and adds the information of the new module into the management configuration file. ### Claim 16 (depends on 8) The system for upgrading the CPE firmware according to claim 8, wherein in the case that the server upgrades the CPE firmware based on Open Mobile Alliance-Device Management (OMA-DM) protocol, when it is required to upgrade a new module, the server acquires from the CPE information of the new module and adds the information of the new module into the management configuration file. ### Claim 17 (depends on 9) The system for upgrading the CPE firmware according to claim 9, wherein in the case that the server upgrades the CPE firmware based on Open Mobile Alliance-Device Management (OMA-DM) protocol, when it is required to upgrade a new module, the server acquires from the CPE information of the new module and adds the information of the new module into the management configuration file.