CN113132494B - Remote upgrading method and system - Google Patents
Remote upgrading method and system Download PDFInfo
- Publication number
- CN113132494B CN113132494B CN202110477768.8A CN202110477768A CN113132494B CN 113132494 B CN113132494 B CN 113132494B CN 202110477768 A CN202110477768 A CN 202110477768A CN 113132494 B CN113132494 B CN 113132494B
- Authority
- CN
- China
- Prior art keywords
- upgrade
- upgrade package
- remote
- module
- end machine
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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/12—Applying verification of the received information
- H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a remote upgrading method and a system, wherein a near-end machine and a far-end machine are mutually interacted to carry out version detection and new version acquisition, and upgrade success, upgrade failure and upgrade packet error messages are reported to a server, so that the remote automatic upgrading of software of each module is realized.
Description
Technical Field
The invention belongs to the field of wireless communication, and particularly relates to a remote upgrading method and system.
Background
More than 85% of the flow in the 5G era occurs in indoor scenes, and good indoor coverage plays a significant role in meeting the flow demand. However, the original passive indoor subsystem does not support 5G high frequency band and MIMO deployment. Aiming at the problem of the original passive indoor subsystem, the industry provides a frequency shift indoor subsystem which can support a 5G frequency band on the original passive indoor subsystem in a frequency shift mode and simultaneously cover MIMO. The frequency shift room subsystem consists of a near-end machine and a far-end machine, wherein the near-end machine is positioned at a signal source, and the far-end machine is positioned at a tail end and provides signal coverage.
At present, the system does not support the remote upgrading function, and when system software needs to be updated or maintained, the system can only adopt a manual field burning mode, so that the problems of high equipment maintenance cost, poor software updating instantaneity and low efficiency are caused.
Disclosure of Invention
The invention aims to solve the problems of high equipment maintenance cost, poor software updating real-time performance and low efficiency caused by the fact that the conventional frequency shift indoor distribution system does not support software remote updating, and provides a remote updating method and a remote updating system.
In order to achieve the above object, a remote upgrade method includes the steps of:
s1, the near-end machine 5G module continuously interacts with the far-end server to detect whether a new version exists; if so, go to S2; otherwise, re-executing S1;
s2, the near-end machine 5G module judges the type of the upgrade package, if the upgrade package is the upgrade package of the near-end machine 5G module, the 5G module version upgrade flow is entered; otherwise, transmitting the upgrade package to the near-end machine MCU module, and executing S3;
s3, the near-end machine MCU module judges the upgrade package type, if the upgrade package is the upgrade package of the near-end machine MCU module, the version upgrade flow of the near-end MCU module is entered; otherwise, go to S4;
s4, the near-end machine MCU module checks the validity of the upgrade package, if the check is legal, the upgrade package is transmitted to the near-end machine communication module, and S5 is executed; otherwise, the upgrade package is removed, and an upgrade package error message is reported to the 5G module;
s5, the near-end communication module judges the upgrade package type, if it is the upgrade package of the near-end communication module, it enters the version upgrade flow of the near-end communication module; otherwise, transmitting the upgrade package to the remote terminal communication module, and executing S6;
s6, the remote communication module judges the upgrade package type, if it is the upgrade package of the remote communication module, it enters the remote communication module version upgrade flow; otherwise, transmitting the upgrade package to the MCU module of the remote terminal, and executing S7;
and S7, after receiving the upgrade package, the MCU module of the remote terminal enters the version upgrade process of the MCU module of the remote terminal.
The specific process of the version upgrading process is as follows:
s81, carrying out validity check on the upgrade package, and if the check is successful, executing S82; otherwise, go to S83;
s82, version upgrade is carried out, if upgrade succeeds, upgrade success information is reported to the server; otherwise, go to S83;
s83, removing the upgrade package and reporting the upgrade package error message to the server.
The validity check of the upgrade package comprises four parts, namely version number check, type check, validity check and integrity check, and if any check fails, the upgrade package is judged to be illegal; if all the verification is successful, judging that the upgrade package is legal.
The version number verification method comprises the following steps:
checking the version number of the upgrade package, and if the version number of the upgrade package is greater than the version number of the current module, judging that the version number is checked successfully; otherwise, the version number is judged to be failed to check.
The type checking method comprises the following steps:
checking the type of the upgrade package, and if the type of the upgrade package is consistent with that of the current module, judging that the type checking is successful; otherwise, the type check is judged to fail.
The validity checking method comprises the following steps:
verifying the data of the upgrade package, and if the data of the upgrade package is valid according to a preset rule, judging that validity verification is successful; otherwise, judging the validity check fails.
The integrity check method comprises the following steps:
performing CRC on the whole file of the upgrade package, and judging that the integrity check is successful when the CRC of the upgrade package is valid; otherwise, the verification is judged to fail.
A remote upgrading system is characterized by comprising a near-end machine and a far-end machine, wherein the near-end machine is connected with a signal source;
the near-end machine comprises a 5G module, a near-end machine MCU module and a near-end machine communication module, wherein the near-end machine MCU module is connected with the 5G module and the near-end machine communication module;
the remote machine comprises a remote machine communication module and an MCU module, the remote machine communication module is connected with the MCU module, and the near-end machine communication module is communicated with the remote machine communication module;
the 5G module is used for interacting with the server, detecting the version, acquiring the new version, and reporting upgrading success, upgrading failure and upgrading packet error messages to the server;
the near-end machine MCU module is used for detecting the type of the upgrade package, judging the legality, transmitting the upgrade package, and reporting the upgrade success, upgrade failure and upgrade package error messages;
the near-end machine communication module is used for detecting and transmitting the type of the upgrade package and reporting the upgrade success, upgrade failure and upgrade package error messages;
the remote machine communication module is used for detecting and transmitting the type of the upgrade package and reporting upgrade success, upgrade failure and upgrade package error messages;
the remote machine MCU module is used for acquiring the upgrade package from the remote machine communication module and sending the upgrade success, upgrade failure and upgrade package error messages to the communication module.
The near-end machine is connected with the remote machine communication modules of the plurality of remote machines through the near-end machine communication module.
Compared with the prior art, the invention realizes the remote upgrading of the system without manual field burning, improves the real-time performance and efficiency of software updating and reduces the equipment maintenance cost by mutually interacting the near-end machine and the far-end machine, detecting the version and obtaining the new version and reporting the upgrading success, upgrading failure and upgrading packet error messages to the server.
The system comprises a near-end machine and a far-end machine, wherein the near-end machine is connected with a signal source, and a near-end machine communication module is communicated with a far-end machine communication module, so that the software upgrading of all modules in the near-end machine and all modules in the far-end machine in the system can be realized.
Drawings
FIG. 1 is a diagram of steps of a remote upgrade method in an embodiment of the invention;
FIG. 2 is a diagram of the steps of a version upgrade method in an embodiment of the present invention;
FIG. 3 is a flow chart of a remote upgrade method in an embodiment of the present invention;
FIG. 4 is a flow chart of a version upgrade method in an embodiment of the present invention;
FIG. 5 is a flow chart of an active upgrade in an embodiment of the present invention;
fig. 6 is a system diagram of a near-end machine in an embodiment of the present invention;
FIG. 7 is a system diagram of a remote unit in an embodiment of the present invention;
FIG. 8 is a block diagram of a system with remote upgrade capability in an embodiment of the invention.
Detailed Description
The invention is further described below with reference to the accompanying drawings.
A remote upgrade method as shown in fig. 1 specifically includes the following 7 steps:
step 1: the near-end machine 5G module interacts with the far-end server to detect whether a new version exists. If yes, downloading the upgrade package to the local; otherwise, it is not processed.
Further, the near-end machine 5G module can detect a new version according to a preset rule;
furthermore, the predetermined detection rule may be a predetermined time detection after the device is powered on, or may be a periodic detection, or a combination of the predetermined time and the periodic detection;
furthermore, the 5G module respectively stores the downloaded upgrade package according to different types, or stores the upgrade package to different directories, and can be divided into a 5G module, a near-end machine MCU module, a near-end machine communication module, a far-end machine communication module and a far-end machine MCU module.
Step 2: the near-end machine 5G module judges the type of the upgrade package, and if the upgrade package is the own upgrade package, the version upgrade process of the 5G module is started; otherwise, the upgrade package is transmitted to the MCU module of the near-end machine.
And step 3: the near-end machine MCU module judges the type of the upgrade package, and if the upgrade package is the own upgrade package, the version upgrade process of the near-end MCU module is started; otherwise, the validity of the upgrade package is checked.
And 4, step 4: the MCU module of the near-end machine checks the legality of the upgrade package, and if the check is legal, the upgrade package is transmitted to the communication module of the near-end machine; otherwise, the upgrade package is removed, and an upgrade package error message is reported to the 5G module.
Furthermore, because a plurality of remote machines exist in the actual system, the version numbers of the MCU module and the communication module of each remote machine are possibly different, so the MCU module of the near-end machine can establish a remote machine MCU module and a communication module version information management information table;
further, the remote machine version information management table comprises a remote machine SN number, a remote machine MCU module and a communication module version current version number;
furthermore, the MCU module of the near-end machine counts the lowest version number of the MCU module of the far-end machine and the communication module in the system through the version information management table;
further, when the near-end machine MCU module checks the version number of the upgrade package, specifically, the version number of the upgrade package is compared with the counted lowest version number;
further, if the validity of the upgrade package is successfully checked and the upgrade package is of a remote machine MCU module or a remote machine communication module, the upgrade package is stored to the local of a near-end machine MCU so that active upgrade can be performed when a certain remote version in the system is lower than the upgrade package;
and 5: the near-end machine communication module judges the type of the upgrade package, and if the upgrade package is the own upgrade package, the version upgrade flow of the near-end machine communication module is started; otherwise, transmitting the upgrade package to the remote terminal communication module;
further, since the system has a plurality of remote machines in practical application, the near-end machine communication module transmits the upgrade package to the remote machine communication module in a broadcasting mode.
Step 6: the remote terminal communication module judges the type of the upgrade package, and if the upgrade package is the own upgrade package, the remote terminal communication module enters the version upgrade process; otherwise, transmitting the upgrade package to the remote machine MCU module;
and 7: and after receiving the upgrade package, the remote machine MCU module enters the version upgrade process of the remote machine MCU module.
A specific flow of a remote upgrade method is shown in fig. 3, which specifically includes the following steps:
step 1: the 5G module interacts with the server to detect a new version;
and 2, step: is the 5G module detects a new version? If yes, entering step 3; otherwise, entering step 1;
and 3, step 3: the 5G module downloads the upgrade package to the local;
and 4, step 4: the 5G module judges the type of the upgrade package;
and 5: is the 5G module's own upgrade package? If yes, upgrading the 5G module version; otherwise, entering step 6;
step 6: transmitting the upgrade package to a near-end MCU module;
and 7: the near-end MCU module judges the type of the upgrade package;
and 8: is the upgrade package of the near-end MCU module itself? If yes, upgrading the version of the near-end MCU module; otherwise, go to step 9;
and step 9: the near-end MCU module carries out validity check on the upgrade package;
step 10: is the validity check passed? If yes, go to step 12; otherwise, entering step 11;
step 11: the near-end MCU module clears the upgrade package and reports an upgrade package error message to the 5G module;
step 12: the near-end MCU module transmits the upgrade package to the near-end communication module;
step 13: the near-end communication module judges the type of the upgrade package;
step 14: is the near-end communication module itself upgrade package? If yes, upgrading the version of the near-end communication module; otherwise, go to step 15;
step 15: the near-end communication module transmits the upgrade package to the far-end communication module;
step 16: the remote communication module judges the type of the upgrade package;
and step 17: is it the remote communications module self upgrade package? If yes, upgrading the version of the remote communication module; otherwise, go to step 18;
step 18: and the remote communication module transmits the upgrade package to the remote MCU module to upgrade the version of the remote MCU module.
The version upgrading process is as shown in fig. 2, and includes the following two steps:
step 1: verifying the validity of the upgrade package, and if the verification is successful, entering the next step; otherwise, the upgrade package is cleared, and an upgrade package error message is reported to the server.
Step 2: upgrading the version, and reporting an upgrading success message to a server if the upgrading is successful; otherwise, the upgrade package is removed, and an upgrade failure message is reported to the server.
The specific flow of version upgrade is shown in fig. 4, and specifically includes the following steps:
step 1: carrying out validity check on the upgrade package;
step 2: is upgrade package validity check passed? If yes, entering step 3; otherwise, entering step 4;
and step 3: clearing the upgrade package, and reporting an error message of the upgrade package;
and 4, step 4: the module carries out version upgrading;
and 5: is the module version upgrade determined to be successful? If so, reporting an upgrade success message to the server; otherwise, reporting an upgrade failure message to the server.
The logic decision table for verifying the validity of the upgrade package is shown in table 1 and comprises four parts, namely version number verification, type verification, validity verification and integrity verification.
TABLE 1 upgrade package validity check logic decision table
If any verification fails, judging that the upgrade package is illegal; and if all the verification is successful, judging that the upgrade package is legal.
And when the version number of the upgrade package is larger than the version number of the current module according to the version number verification rule, judging that the version number is verified successfully.
And when the type of the upgrade package is consistent with the type of the current module according to the type checking rule, judging that the type checking is successful.
And when the validity check rule is that the data of the upgrade package is valid according to the preset rule, judging that the validity check is successful.
The integrity check rule is to perform CRC check on the whole file of the upgrade package, and the integrity check is judged to be successful only if the CRC check of the upgrade package is valid.
An active upgrade flow is shown in fig. 5, which mainly includes the following steps:
step 1: the near-end machine MCU module collects the version numbers of the MCU module and the communication module of each far-end machine, and establishes a version information management table of the MCU module and the communication module of each far-end machine;
step 2: the near-end machine MCU module counts the lowest version numbers of the remote machine MCU module and the remote machine communication module according to the version information management table;
and step 3: the MCU module of the near-end machine compares the version number of the upgrade package with the minimum version number of the corresponding module counted;
further, the version number comparison mode is that the version number of the upgrade package of the MCU module of the remote machine is compared with the counted lowest version number of the MCU module of the remote machine; and comparing the version number of the upgrading packet of the remote terminal communication module with the counted lowest version number of the remote terminal communication module.
And 4, step 4: and judging whether the version number of the upgrade package is greater than the counted lowest version number. If yes, transmitting the upgrade package to each remote terminal to carry out corresponding version upgrade; otherwise, it is not processed.
Referring to fig. 8, a remote upgrade system includes a near-end machine and a far-end machine, the near-end machine is connected to a signal source, and the far-end machine is in communication with the near-end machine.
Referring to fig. 6, the near-end machine includes a 5G module, an MCU module and a communication module.
The near-end machine 5G module is used for interacting with the server, detecting the version, acquiring the new version, and reporting the information of successful upgrade, failed upgrade and upgrade packet error to the server.
Further, the upgrade success, upgrade failure and upgrade package error messages are specifically classified as follows:
5G module: upgrade success, upgrade failure and upgrade package error;
the near-end machine MCU module: upgrade success, upgrade failure and upgrade package error;
the near-end machine communication module: upgrade success, upgrade failure and upgrade package error;
the remote machine MCU module: upgrade success, upgrade failure and upgrade package error;
the remote machine communication module: upgrade success, upgrade failure, and upgrade package error.
The near-end machine MCU module is used as an upgrade master control and is mainly used for upgrade package type detection and legality judgment, upgrade package transmission and upgrade success, upgrade failure and upgrade package error message reporting.
The near-end machine communication module is communicated with the far-end machine communication module and is mainly used for detecting and transmitting the type of the upgrade package and reporting the upgrade success, upgrade failure and upgrade package error messages.
Further, the near-end communication module transmits the upgrade package to the far-end module in a broadcasting mode.
Referring to fig. 7, the remote machine includes a communication module and an MCU module.
The far-end machine communication module is used for communicating with the near-end machine communication module and is mainly used for detecting and transmitting the type of the upgrade package and reporting the upgrade success, upgrade failure and upgrade package error messages.
The remote machine MCU module interacts with the remote machine communication module and is mainly used for acquiring the upgrade package from the communication module and sending messages of success upgrade, failure upgrade and upgrade package error to the communication module.
Claims (9)
1. A remote upgrading method is characterized by comprising the following steps:
s1, the near-end machine 5G module continuously interacts with the far-end server to detect whether a new version exists; if so, go to S2; otherwise, re-executing S1;
s2, the near-end machine 5G module judges the type of the upgrade package, if the upgrade package is the upgrade package of the near-end machine 5G module, the 5G module version upgrade flow is entered; otherwise, transmitting the upgrade package to the near-end machine MCU module, and executing S3;
s3, the near-end machine MCU module judges the upgrade package type, if the upgrade package is the upgrade package of the near-end machine MCU module, the version upgrade flow of the near-end machine MCU module is entered; otherwise, go to S4;
s4, the near-end machine MCU module checks the validity of the upgrade package, if the check is legal, the upgrade package is transmitted to the near-end machine communication module, and S5 is executed; otherwise, the upgrade package is removed, and an upgrade package error message is reported to the 5G module;
s5, the near-end machine communication module judges the type of the upgrade package, if the upgrade package is the upgrade package of the near-end machine communication module, the version upgrade flow of the near-end machine communication module is entered; otherwise, transmitting the upgrade package to the remote terminal communication module, and executing S6;
s6, the remote communication module judges the upgrade package type, if it is the upgrade package of the remote communication module, it enters the remote communication module version upgrade flow; otherwise, transmitting the upgrade package to the MCU module of the remote terminal, and executing S7;
and S7, after receiving the upgrade package, the MCU module of the remote terminal enters the version upgrade process of the MCU module of the remote terminal.
2. The remote upgrading method according to claim 1, wherein the specific flow of the version upgrading flow is as follows:
s81, carrying out validity check on the upgrade package, and if the check is successful, executing S82; otherwise, go to S83;
s82, version upgrade is carried out, if upgrade succeeds, upgrade success information is reported to the server; otherwise, go to S83;
s83, removing the upgrade package and reporting the upgrade package error message to the server.
3. The remote upgrading method according to claim 1, wherein the upgrading packet validity check includes four parts of version number check, type check, validity check and integrity check, and if any check fails, the upgrading packet is judged to be illegal; if all the verification is successful, judging that the upgrade package is legal.
4. A remote upgrade method according to claim 3, characterized in that the version number verification method is as follows:
checking the version number of the upgrade package, and if the version number of the upgrade package is greater than the version number of the current module, judging that the version number is checked successfully; otherwise, the version number is judged to be failed to check.
5. A remote upgrade method according to claim 3, characterized in that the type check method is as follows:
checking the type of the upgrade package, and if the type of the upgrade package is consistent with that of the current module, judging that the type checking is successful; otherwise, the type check is judged to be failed.
6. A remote upgrade method according to claim 3, characterized in that the validity check method is as follows:
verifying the data of the upgrade package, and if the data of the upgrade package is valid according to a preset rule, judging that validity verification is successful; otherwise, judging the validity check fails.
7. A remote upgrade method according to claim 3, characterized in that the integrity check method is as follows:
performing CRC on the whole file of the upgrade package, and judging that the integrity check is successful when the CRC of the upgrade package is valid; otherwise, the verification is judged to be failed.
8. The system of the remote upgrading method according to claim 1, comprising a near-end machine and a far-end machine, wherein the near-end machine is connected with the information source;
the near-end machine comprises a 5G module, a near-end machine MCU module and a near-end machine communication module, wherein the near-end machine MCU module is connected with the 5G module and the near-end machine communication module;
the remote machine comprises a remote machine communication module and a remote machine MCU module, the remote machine communication module is connected with the remote machine MCU module, and the near-end machine communication module is communicated with the remote machine communication module;
the 5G module is used for interacting with the server, detecting the version, acquiring the new version, and reporting upgrading success, upgrading failure and upgrading packet error messages to the server;
the near-end machine MCU module is used for detecting the type of the upgrade package, judging the legality, transmitting the upgrade package, and reporting the upgrade success, upgrade failure and upgrade package error messages;
the near-end machine communication module is used for detecting and transmitting the type of the upgrade package and reporting the upgrade success, upgrade failure and upgrade package error messages;
the remote machine communication module is used for detecting and transmitting the type of the upgrade package and reporting upgrade success, upgrade failure and upgrade package error messages;
the remote machine MCU module is used for acquiring the upgrade package from the remote machine communication module and sending the upgrade success, upgrade failure and upgrade package error messages to the communication module.
9. The system of claim 8, wherein the near-end unit is connected to the remote unit communication modules of the plurality of remote units through the near-end unit communication module.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110477768.8A CN113132494B (en) | 2021-04-29 | 2021-04-29 | Remote upgrading method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110477768.8A CN113132494B (en) | 2021-04-29 | 2021-04-29 | Remote upgrading method and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN113132494A CN113132494A (en) | 2021-07-16 |
CN113132494B true CN113132494B (en) | 2022-09-02 |
Family
ID=76780650
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110477768.8A Active CN113132494B (en) | 2021-04-29 | 2021-04-29 | Remote upgrading method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN113132494B (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101557583A (en) * | 2009-03-19 | 2009-10-14 | 珠海银邮光电技术发展股份有限公司 | Remote-updating and version-switching method of repeater equipment embedded software |
CN101706723A (en) * | 2009-09-25 | 2010-05-12 | 厦门敏讯信息技术股份有限公司 | Realization method for avoiding error edition upgrading and upgrading system platform of embedded mobile terminal |
CN103004250A (en) * | 2012-09-19 | 2013-03-27 | 华为技术有限公司 | Base station software upgrading method, device and system |
CN104038557A (en) * | 2014-06-27 | 2014-09-10 | 武汉虹信通信技术有限责任公司 | Batch upgrading method of equipment software in optical fiber connection tree shape network structure |
CN112104738A (en) * | 2020-09-18 | 2020-12-18 | 深圳市赛秀信息技术有限公司 | Automatic upgrading method, server and system for electronic price tag system software |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101247615B (en) * | 2008-03-07 | 2011-02-02 | 上海华为技术有限公司 | Method and device for improving reliability of communication equipment |
CN102033517A (en) * | 2009-09-25 | 2011-04-27 | 大唐移动通信设备有限公司 | Software upgrading method and equipment for environmental monitoring unit |
CN102394699A (en) * | 2011-12-07 | 2012-03-28 | 深圳市零一通信技术有限公司 | Digital fiber repeater system remote upgrading method |
US9619244B2 (en) * | 2014-09-05 | 2017-04-11 | Xiaomi Inc. | Method and system for upgrading an electronic device |
CN106160852B (en) * | 2016-09-29 | 2019-01-18 | 武汉虹信通信技术有限责任公司 | A kind of network system and its remote upgrade method of transmission device |
CN106874054B (en) * | 2017-03-06 | 2020-11-10 | 四川天邑康和通信股份有限公司 | Method and system for on-line upgrading module program in repeater |
CN109347659B (en) * | 2018-09-17 | 2021-09-24 | 瓴泰科技(上海)有限公司 | Intelligent terminal equipment and module remote upgrading method based on NB-IOT |
CN209692750U (en) * | 2019-06-26 | 2019-11-26 | 北京唯得科技有限公司 | A kind of novel room 5G subsystem |
CN110704081A (en) * | 2019-09-23 | 2020-01-17 | 超讯通信股份有限公司 | Remote software upgrading system and method based on 5G distributed small base station |
CN210899186U (en) * | 2019-11-22 | 2020-06-30 | 南京泰通科技股份有限公司 | GSM-R optical fiber repeater with system software automatic upgrading function |
CN111026426B (en) * | 2019-12-16 | 2024-02-27 | 京信网络***股份有限公司 | Repeater upgrading method and device |
CN111651174A (en) * | 2020-04-23 | 2020-09-11 | 威胜信息技术股份有限公司 | Method and system for remotely upgrading MCU (microprogrammed control Unit) program |
CN112533282B (en) * | 2020-10-22 | 2021-08-06 | 中国电信股份有限公司 | Frequency synchronization method and system, near-end machine, far-end machine and storage medium |
-
2021
- 2021-04-29 CN CN202110477768.8A patent/CN113132494B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101557583A (en) * | 2009-03-19 | 2009-10-14 | 珠海银邮光电技术发展股份有限公司 | Remote-updating and version-switching method of repeater equipment embedded software |
CN101706723A (en) * | 2009-09-25 | 2010-05-12 | 厦门敏讯信息技术股份有限公司 | Realization method for avoiding error edition upgrading and upgrading system platform of embedded mobile terminal |
CN103004250A (en) * | 2012-09-19 | 2013-03-27 | 华为技术有限公司 | Base station software upgrading method, device and system |
CN104038557A (en) * | 2014-06-27 | 2014-09-10 | 武汉虹信通信技术有限责任公司 | Batch upgrading method of equipment software in optical fiber connection tree shape network structure |
CN112104738A (en) * | 2020-09-18 | 2020-12-18 | 深圳市赛秀信息技术有限公司 | Automatic upgrading method, server and system for electronic price tag system software |
Also Published As
Publication number | Publication date |
---|---|
CN113132494A (en) | 2021-07-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN1184847C (en) | Method and apparatus for updating a mobile unit | |
US7852788B2 (en) | Method of organizing nodes of a network into groupings of nodes, computer program for implementing such a method and communication device forming a node of a network of nodes | |
CN106953902B (en) | Method and device for upgrading firmware of electric energy meter | |
CN101184309A (en) | Embedded system remote upgrade method for repeater equipment | |
CN107517110B (en) | Single board configuration self-recovery method and device in distributed system | |
CN112583646A (en) | Remote upgrading method for intelligent electric meter | |
CN112104487A (en) | Remote upgrading method for terminal of Internet of things, Internet of things master station and storage medium | |
CN111459522B (en) | Air conditioner and communication module upgrading method thereof | |
CN113342375A (en) | Method and system for upgrading intelligent terminal under gateway | |
CN113132494B (en) | Remote upgrading method and system | |
CN113821242B (en) | Intelligent firmware matching method and system | |
CN111190617A (en) | Remote firmware upgrading system and method based on intelligent perception technology and terminal equipment | |
CN113572637A (en) | Network fault automatic preprocessing method and device | |
CN112737849A (en) | Equipment information processing method and device | |
CN105530132A (en) | Management system and method of CATV optical receiving module on CDOCSIS platform | |
CN115002035A (en) | Power data transmission congestion evasion method based on service level | |
CN102404714B (en) | By the method for WiFi wireless network updating apparatus software | |
US20180225170A1 (en) | Method for recognizing the communication protocol of data packets travelling over a communication bus | |
CN112888063B (en) | Remote terminal network access method, system, electronic device and storage medium | |
CN110727445B (en) | Method and system for upgrading tower hanging equipment based on OTA | |
CN114157674A (en) | Wireless communication method, device, system, server and medium | |
CN110958145A (en) | Method and device for managing ad hoc network equipment and electronic equipment | |
CN113783950A (en) | Edge distributed OTA (over the air) upgrading system and method | |
CN112667280B (en) | Locomotive vehicle-mounted application software centralized control system based on Git technology | |
CN111488235A (en) | Terminal fault processing method and system and cloud platform |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |