CN113094064A - Gateway software module upgrading method, device, equipment and storage medium - Google Patents
Gateway software module upgrading method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113094064A CN113094064A CN202110233339.6A CN202110233339A CN113094064A CN 113094064 A CN113094064 A CN 113094064A CN 202110233339 A CN202110233339 A CN 202110233339A CN 113094064 A CN113094064 A CN 113094064A
- Authority
- CN
- China
- Prior art keywords
- module
- gateway
- update
- identifier
- upgrade
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本申请实施例公开了一种网关软件模块升级方法、装置、设备及存储介质，方法包括：获取服务器发布的网关的第一升级信息，包括第一更新模块列表和模块依赖关系信息，第一更新模块列表中包括有更新的模块标识；在检测到用户的模块选择指令时，获取对应的第一模块标识；根据模块依赖关系信息，判断第一更新模块列表中是否包括与第一模块标识存在依赖关系的模块标识；若是，获取与存在依赖关系的第二模块标识；向服务器发送第一更新指令，以使服务器向网关发送第一升级文件；第一升级文件用于网关升级第一模块和第二模块，可以将有依赖关系的模块同时升级，避免只升级部分导致网关中的软件模块之间不兼容的问题，增强了升级的智能性。
The embodiments of the present application disclose a gateway software module upgrade method, device, device, and storage medium. The method includes: acquiring first upgrade information of the gateway published by a server, including a first update module list and module dependency relationship information, and the first update The module list includes updated module identifiers; when a user's module selection instruction is detected, the corresponding first module identifier is obtained; according to the module dependency relationship information, it is determined whether the first update module list includes dependencies with the first module identifier. The module identifier of the relationship; if so, obtain the second module identifier that has a dependency relationship; send the first update instruction to the server, so that the server sends the first upgrade file to the gateway; the first upgrade file is used by the gateway to upgrade the first module and the first update file. Two modules, which can upgrade the modules with dependencies at the same time, avoid the problem of incompatibility between software modules in the gateway caused by only upgrading part, and enhance the intelligence of the upgrade.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for upgrading a gateway software module.
Background
Over-the-Air Technology (OTA) for intelligent gateways typically includes a full Firmware (Firmware) refresh and partial software Module (MOD) upgrade. Most of the common upgrades involve only partial software module changes, i.e., upgrade the partial software module with changes (MOD OTA), avoiding the download and the rewriting of a larger complete firmware. However, the problem of incompatibility between software modules in the updated gateway is easily caused by the current gateway software module upgrading scheme.
Disclosure of Invention
The present application mainly aims to provide a method and an apparatus for upgrading a gateway software module, an electronic device, and a storage medium, which can solve the problem in the prior art that software modules in an intelligent gateway after upgrading are incompatible due to reasons such as updated software modules in an upgrading part.
In one aspect, the present application provides a method for upgrading a gateway software module, where the method is applied to a user side, and the method includes:
acquiring first upgrading information of a gateway issued by a server; the first updating information comprises a first updating module list and module dependency relationship information, the first updating module list comprises updated module identification, and the module dependency relationship information is used for indicating whether dependency relationship exists between modules;
when a module selection instruction of a user is detected, acquiring a first module identifier corresponding to the module selection instruction, wherein the first module identifier is at least one module identifier in the first updating module list;
judging whether the first updating module list comprises a module identifier which has a dependency relationship with the first module identifier or not according to the module dependency relationship information;
if so, acquiring a second module identifier which has a dependency relationship with the first module identifier;
sending a first updating instruction to the server so that the server sends a first upgrading file to the gateway; the first update instruction comprises the first module identification and the second module identification, and the first upgrade file is used for upgrading the first module and the second module by the gateway.
Optionally, the first update module list further includes
The module identification corresponds to an update version number;
after determining that the first updated module list includes the module identifier having a dependency relationship with the first module identifier, the method further includes:
determining whether the second module is installed on the gateway according to a history updating list of the gateway;
and if the gateway is determined not to be provided with the second module, triggering the first updating instruction to be sent to the server.
Optionally, the history update list includes a module identifier of the gateway after the last update and a history version number corresponding to the module identifier; if it is determined that the second module is installed in the gateway, the method further includes:
judging whether the historical version number corresponding to the second module identifier is lower than the update version number corresponding to the second module identifier;
and if so, triggering the server to send a first updating instruction.
Optionally, before sending the first update instruction to the server, the method further includes:
if the gateway is determined not to be provided with the second module, or the historical version number corresponding to the second module identifier is lower than the update version number corresponding to the second module identifier, outputting prompt information, wherein the prompt information is used for prompting the user to select the second module for upgrading;
triggering the sending of a first updating instruction to the server when a confirmation instruction for the prompt information is detected;
if the gateway is determined to be provided with the second module and the historical version number corresponding to the second module identifier is not lower than the update version number corresponding to the second module identifier, sending a second update instruction to the server so that the server sends a second upgrade file to the gateway; the second updating instruction comprises the first module identification, and the second upgrading file is used for upgrading the first module by the gateway.
Optionally, the method further includes:
acquiring second upgrading information of the gateway issued by the server; the second upgrading information comprises a total firmware version number and a second updating module list, and the second updating module list comprises a plurality of module identifications and latest version numbers corresponding to the module identifications;
and under the condition that the upgrading instruction is detected to be confirmed, second upgrading information is sent to the gateway through the server, so that the gateway can upgrade the software module according to the second upgrading information.
Optionally, the method further includes:
and acquiring and displaying the networking state information and the size of the upgrading module file of the gateway, wherein the networking state information and the size of the upgrading module file of the gateway are used for a user to judge whether to carry out the upgrading.
Optionally, the upgrade information further includes an upgrade file check code; the method further comprises the following steps:
calculating the downloaded upgrade file according to a preset analysis algorithm to obtain an analysis check code;
comparing the analysis check code with the upgrade file check code;
and if the analysis check code is consistent with the upgrade file check code, determining that the download of the upgrade file is correct, and triggering to acquire the current version number of the target module identifier.
In another aspect, a gateway software module upgrading method is provided, where the method is applied to a gateway, and the method includes:
acquiring upgrading information of a gateway issued by a server, wherein the upgrading information comprises a total firmware version number and a second updating module list, the second updating module list comprises a plurality of module identifications and latest version numbers corresponding to the module identifications, and the module identifications comprise module identifications which are updated in a historical manner and module identifications which are updated at this time;
acquiring the current version number of a target module identifier, wherein the target module identifier is any module identifier in the second updating module list;
and under the condition that the current version number of the target module identifier is lower than the update version number of the target module identifier, upgrading the target module corresponding to the target module identifier.
Optionally, the method further includes:
transmitting second upgrading information of the gateway firmware to the terminal equipment; the second updating information comprises a total firmware version number, a second updating module list and an updating file check code, wherein the second updating module list comprises all updated module identifications and latest version numbers corresponding to the module identifications; the upgrade file check code is used for the gateway to check the downloaded upgrade file so as to determine whether the upgrade file is downloaded correctly;
and receiving a second updating instruction from the terminal equipment, responding to the second updating instruction, and sending the second upgrading information to the gateway so that the gateway upgrades the software module according to the second upgrading information.
In another aspect, a gateway software module upgrading method is provided, where the method is applied to a server, and the method includes:
transmitting first upgrading information of the gateway firmware to the terminal equipment; the first updating information comprises a first updating module list and module dependency relationship information, the first updating module list comprises updated module identifiers, and the module dependency relationship information is used for indicating whether each module identifier in the first updating module list has a dependency relationship with other module identifiers and which module identifier has a dependency relationship with the other module identifiers;
receiving a first updating instruction from the terminal equipment, and responding to the first updating instruction to send a first upgrading file to a gateway; the first update instruction comprises the first module identification and the second module identification, and the first upgrade file is used for the gateway to upgrade the first module and the second module.
In another aspect, an apparatus for upgrading a gateway software module is provided, including:
an acquisition module to:
acquiring first upgrading information of a gateway issued by a server; the first updating information comprises a first updating module list and module dependency relationship information, the first updating module list comprises updated module identification, and the module dependency relationship information is used for indicating whether dependency relationship exists between modules;
a determining module, configured to, when a module selection instruction of a user is detected, obtain a first module identifier corresponding to the module selection instruction, where the first module identifier is at least one module identifier in the first update module list;
the judging module is used for judging whether the first updating module list comprises a module identifier which has a dependency relationship with the first module identifier according to the module dependency relationship information;
the obtaining module is further configured to obtain update information of the first module and the second module if the first update module list includes a module identifier having a dependency relationship with the first module identifier;
the transmission module is used for sending a first updating instruction to the server so that the server sends a first upgrading file to the gateway; the first update instruction comprises the first module identification and the second module identification, and the first upgrade file is used for upgrading the first module and the second module by the gateway.
In another aspect, another gateway software module upgrade apparatus is provided, the apparatus including:
the transmission module is used for acquiring the upgrading information of the gateway issued by the server, wherein the upgrading information comprises a total firmware version number and a second updating module list, the second updating module list comprises a plurality of module identifications and latest version numbers corresponding to the module identifications, and the module identifications comprise module identifications which are updated in a historical mode and module identifications which are updated at this time;
a processing module to:
acquiring the current version number of a target module identifier, wherein the target module identifier is any module identifier in the second updating module list;
and under the condition that the current version number of the target module identifier is lower than the update version number of the target module identifier, upgrading the target module corresponding to the target module identifier.
In another aspect, there is provided a gateway software module upgrading apparatus, including a transmission module configured to:
transmitting first upgrading information of the gateway firmware to the terminal equipment; the first updating information comprises a first updating module list and module dependency relationship information, the first updating module list comprises updated module identifiers, and the module dependency relationship information is used for indicating whether each module identifier in the first updating module list has a dependency relationship with other module identifiers and which module identifier has a dependency relationship with the other module identifiers;
receiving a first updating instruction from the terminal equipment, and responding to the first updating instruction to send a first upgrading file to a gateway; the first update instruction comprises the first module identification and the second module identification, and the first upgrade file is used for the gateway to upgrade the first module and the second module.
In another aspect, an electronic device is provided, comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any of the above aspects and any possible implementation thereof.
In another aspect, a computer storage medium is provided, storing one or more instructions adapted to be loaded by a processor and to perform the steps of the method of any of the above aspects and any possible implementation thereof.
The application provides a gateway software module upgrading method which is applied to a user side and is used for upgrading a gateway by acquiring first upgrading information of the gateway issued by a server; the first updating information comprises a first updating module list and module dependency relationship information, the first updating module list comprises updated module identification, and the module dependency relationship information is used for indicating whether dependency relationship exists between modules; when a module selection instruction of a user is detected, acquiring a first module identifier corresponding to the module selection instruction, wherein the first module identifier is at least one module identifier in the first updating module list; judging whether the first updating module list comprises a module identifier which has a dependency relationship with the first module identifier according to the module dependency relationship information; if so, acquiring a second module identifier which has a dependency relationship with the first module identifier; sending a first updating instruction to the server so that the server sends a first upgrading file to the gateway; the first updating instruction comprises the first module identification and the second module identification, the first updating file is used for updating the first module and the second module of the gateway, dependency relations between the modules can be judged before module updating is executed through the user side, the modules with the dependency relations can be updated at the same time, the problem that software modules in the gateway are incompatible due to the fact that only the updating part is updated is avoided, and the updating intelligence is enhanced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Wherein:
fig. 1 is a schematic flowchart of a gateway software module upgrading method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a gateway software module upgrading method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a gateway software module upgrading method according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a gateway software module upgrading method according to an embodiment of the present application;
fig. 5 is a schematic flowchart of another gateway software module upgrading method according to an embodiment of the present application;
fig. 6 is a schematic flowchart of another gateway software module upgrading method according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a gateway software module upgrading apparatus according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of another gateway software module upgrading apparatus in this embodiment of the present application;
fig. 9 is a schematic structural diagram of another gateway software module upgrading apparatus in this embodiment of the present application;
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below clearly and completely with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any inventive effort, shall fall within the scope of protection of the present application.
It is understood that the Gateway (Gateway) is also called an internetwork connector, a protocol converter. The gateway realizes network interconnection above a network layer, is the most complex network interconnection equipment and is only used for interconnection of two networks with different high-level protocols. The gateway can be used for interconnection of both wide area networks and local area networks.
In the embodiment of the application, when the gateway is used as a home gateway, due to the interconnection characteristics of the gateway, the home gateway can be compatible with a plurality of external broadband network access modes to form a bridge for connecting a home internal network and an external network, and when the gateway establishes connection with all devices capable of networking in a home, the gateway can control the access device and collect the operation parameters thereof, and store and send the relevant parameters of the operation state base to the devices outside the home.
It should be noted that the application scenario in the embodiment of the present application is a gateway software module upgrade scenario, and may include: the gateway, the server and the clients, and each client can correspondingly establish communication with one or more gateways, and perform gateway software module upgrade control through the server, and in the description of the embodiments of the present application, a client and a gateway establish communication and perform a description of gateway software module upgrade through the server.
An Application (APP) referred to in the embodiments of the present Application refers to a business program running on an operating system (operating in a user mode).
Fig. 1 is a flowchart of a gateway software module upgrading method provided in an embodiment of the present application, where as shown in fig. 1, the method is applied to a user side, and the method includes:
101. acquiring first upgrading information of a gateway issued by a server; the first updating information comprises a first updating module list and module dependency relationship information, the first updating module list comprises updated module identification, and the module dependency relationship information is used for indicating whether dependency relationship exists between modules.
The user terminal in the embodiments of the present application may be an electronic device, and in particular implementations, the electronic device may be a terminal, which may also be referred to as a terminal device, including but not limited to other portable devices such as a mobile phone, a laptop computer, or a tablet computer having a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). It should also be understood that in some embodiments, the devices described above are not portable communication devices, but rather are desktop computers having touch-sensitive surfaces (e.g., a touch screen display and/or a touchpad).
In the embodiment of the application, the software module of the gateway can be installed and upgraded (updated) through the user side control, the user selection function can be provided on the terminal interface through the server, and specifically, the user can select which application programs need to be updated.
The software modules in the embodiments of the present application may also be referred to as software programs or plug-ins, and may include applications and/or drivers.
The server in the embodiment of the application can be a cloud server, and information of the application program updated at a certain time can be maintained. Specifically, the server may issue the upgrade information that the gateway uses for the software module upgrade each time. In this application embodiment, the first upgrade information issued by the server includes a first updated module list and module dependency relationship information. The first update module list includes a module identifier updated this time, and the module dependency relationship information indicates whether a dependency relationship exists between the modules, which may specifically include whether a module has a dependency relationship with other modules and which modules have dependency relationships.
After obtaining the first upgrade information, the user side may initiate a selection request to the user to confirm the module performing the upgrade to the user. Specifically, the module identifier in the first updated module list may be displayed in the terminal interface, and may be information such as a module icon or a module name.
102. And when a module selection instruction of a user is detected, acquiring a first module identifier corresponding to the module selection instruction, wherein the first module identifier is at least one module identifier in the first updating module list.
Specifically, the software module of the gateway updated at this time can be selected at the user side. Taking the first module as an example, the user triggers a module selection instruction, selects to upgrade the first module, and then obtains the first module identifier. The user may select one or more modules for upgrade.
103. And judging whether the first updating module list comprises a module identifier which has a dependency relationship with the first module identifier or not according to the module dependency relationship information.
Specifically, after it is determined that the user selects the first module identifier to be updated, whether the first updated module list includes a module identifier having a dependency relationship with the first module identifier may be determined according to the obtained module dependency relationship information; if so, step 104 may be performed; if not, step 104 may not be executed, and a second update instruction is sent to the server, so that the server sends a second upgrade file to the gateway, where the second update instruction includes the first module identifier, and the second upgrade file is used for upgrading the first module by the gateway, that is, the gateway may upgrade the first module selected by the user.
104. And acquiring a second module identifier which has a dependency relationship with the first module identifier.
105. Sending a first updating instruction to the server so that the server sends a first upgrading file to the gateway; the first update instruction includes the first module identifier and the second module identifier, and the first upgrade file is used for upgrading the first module and the second module by the gateway.
Specifically, if the user side detects that the first update module list further includes a module identifier having a dependency relationship with the first module identifier, a second module identifier having a dependency relationship with the first module identifier may be obtained, where the second module identifier may be one or more. Because there may be dependency relationship between different software modules (application programs), and normal operation can be performed only by performing upgrade at the same time, the user side in the embodiment of the present application may completely select a module with dependency relationship for upgrade when the user does not completely select the module with dependency relationship. Further, the user side can send the first upgrade file to the gateway through the server, wherein the first module and the second module which need to be updated are specified, and the gateway can upgrade the specified module.
After the server sends the first update instruction to the gateway, the gateway may download, according to the first module identifier and the second module identifier therein, the corresponding first upgrade file from the server for upgrading the corresponding first module and the second module.
In an optional implementation manner, the gateway also obtains the upgrade file check code when downloading the first upgrade file. The gateway can calculate the analysis check code of the downloaded first upgrade file by using a preset analysis algorithm, and then the analysis check code is matched with the upgrade file check code provided by the server, if the analysis check code is the same as the upgrade file check code, the first upgrade file is downloaded correctly, and upgrading can be performed; if not, the upgrade may not be performed. Optionally, the gateway may also feed back the upgrade condition to the server after the upgrade is completed, and the upgrade condition is recorded by the server and may be fed back to the terminal device through the server.
For example, after the user completes the selection of the application program a, the terminal device determines whether an application program B having a dependency relationship with the application program a is included; if yes, it can be determined that both application program B and application program A which have a dependency relationship with application program A are upgraded.
In an optional implementation manner, the first updated module list further includes an updated version number corresponding to the module identifier; after determining that the first updated module list includes the module identifier having a dependency relationship with the first module identifier, the method further includes:
a1, determining whether the second module is installed in the gateway according to the history update list of the gateway;
a2, if it is determined that the second module is not installed in the gateway, triggering the step 105.
The history update list may be stored by being fed back to the user side by the server after each update of the software module of the gateway, and the history update list includes a module identifier of the gateway after the last update, that is, information including an installed module of the gateway. The user side may determine whether the second module is installed in the gateway after determining that the first update module list includes the module identifier having a dependency relationship with the first module identifier, and if not, may default to execute step 105, where module upgrade at this time includes installing the second module of the latest version.
In an optional embodiment, the history update list includes a module identifier of the gateway after the last update and a history version number corresponding to the module identifier; if it is determined that the second module is installed in the gateway, the method further includes:
a3, judging whether the history version number corresponding to the second module identifier is lower than the update version number corresponding to the second module identifier; if yes, step 105 is triggered.
In the case where it is determined that the second module is installed in the gateway, it may be further determined whether the second module installed in the gateway needs to be upgraded. Specifically, the user side can determine whether the historical version number of the second module is lower than the update version number of the second module issued by the server at this time, if so, the second module needs to be upgraded, and if not, the second module does not need to be upgraded, so that the data processing amount can be reduced, and the upgrading speed can be increased.
In an optional implementation manner, before sending the first update instruction to the server, the method further includes:
a21, if it is determined that the second module is not installed in the gateway, or the historical version number corresponding to the second module identifier is lower than the update version number corresponding to the second module identifier, outputting a prompt message, wherein the prompt message is used for prompting the user to select the second module for upgrading;
a22, when a confirmation command for the presentation information is detected, triggering the step 105;
a23, if it is determined that the gateway has installed the second module and the history version number corresponding to the second module identifier is not lower than the update version number corresponding to the second module identifier, sending a second update instruction to the server to enable the server to send a second upgrade file to the gateway; the second update instruction includes the first module identifier, and the second upgrade file is used for the gateway to upgrade the first module.
Specifically, when it is determined that the second module is not installed in the gateway, or the historical version number of the installed second module is lower than the version number of the update, it indicates that the gateway needs to install or upgrade the second module, and the user side may output a prompt message to prompt the user to select the second module for installation or upgrade. The user can select the first module and the second module, and after triggering the confirmation instruction, the user side can execute step 105, that is, the gateway can upgrade the first module and the second module through the server; if the user sends a rejection instruction to the prompt message, the updating may not be performed, or the gateway only updates the first module according to the selection of the user.
If the gateway is determined to install the second module and the historical version number of the second module is not lower than the updated version number, the second module is the latest version and does not need to be updated again. The second updating instruction can be sent to the server so that the server sends the second updating file to the gateway, and therefore the gateway only updates the first module, repeated updating is avoided, unnecessary data processing procedures are reduced, and time for updating is shortened.
For example, the second module includes an application program B, and if the application program B is installed in the gateway and the current version number of the application program B is consistent with the received update version number, no prompt or explanation is made; if the gateway does not install the application program B or the version number of the application program B needs to be updated, one way is: updating the version of the application program B by default; another way is to alert the user that the version of application B still needs to be updated (which otherwise would affect use or be unusable), based on the user's confirmation.
After the user selects the update, the user terminal sends the application program to be updated to the gateway through the server, and the gateway updates the application program after receiving the application program.
The method in the embodiment of the application is applied to a user side, and can be used for indicating whether a dependency exists between modules or not by acquiring first upgrading information of a gateway, which is issued by a server and comprises a first updating module list and module dependency information, wherein the first updating module list comprises updated module identifiers; when a module selection instruction of a user is detected, acquiring a first module identifier corresponding to the module selection instruction, wherein the first module identifier is at least one module identifier in the first updating module list; judging whether the first updating module list comprises a module identifier which has a dependency relationship with the first module identifier or not according to the module dependency relationship information; if so, acquiring a second module identifier which has a dependency relationship with the first module identifier; sending a first updating instruction to the server so that the server sends a first upgrading file to the gateway; the first updating instruction comprises the first module identification and the second module identification, the first updating file is used for updating the first module and the second module of the gateway, the dependency relationship between the modules can be judged before the modules are updated by the user terminal, the modules with the dependency relationship are updated at the same time, the problem that only the updating part causes incompatibility between software modules in the gateway is avoided, the updating intelligence is enhanced, and meanwhile, the interactivity with the user is also increased.
Fig. 2 is a flowchart of another gateway software module upgrading method provided in this embodiment, where as shown in fig. 1, the method is applied to a user side, and the method includes:
201. acquiring second upgrading information of the gateway, which is issued by the server; the second upgrade information includes a total firmware version number and a second update module list, the second update module list includes a plurality of module identifiers and a latest version number corresponding to each module identifier, and the module identifiers include a module identifier that has been updated in history and a module identifier that has been updated this time.
The user terminal in the embodiments of the present application may be an electronic device, and in particular implementations, the electronic device may be a terminal, which may also be referred to as a terminal device, including but not limited to other portable devices such as a mobile phone, a laptop computer, or a tablet computer having a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). It should also be understood that in some embodiments, the devices described above are not portable communication devices, but rather are desktop computers having touch-sensitive surfaces (e.g., a touch screen display and/or a touchpad).
In the embodiment of the application, the software module of the gateway can be installed and upgraded (updated) through the user side control, the user selection function can be provided on the terminal interface through the server, and specifically, the user can select which application programs need to be updated.
The software modules in the embodiments of the present application may also be referred to as software programs or plug-ins, and may include applications and/or drivers.
The server in the embodiment of the application can be a cloud server, and information of the application program updated at a certain time can be maintained. Specifically, the server may issue the upgrade information that the gateway uses for the software module upgrade each time. In this application embodiment, the second upgrade information issued by the server includes a total firmware version number and a second update module list. The second updating module list comprises a plurality of module identifications and latest version numbers corresponding to each module identification, wherein the module identifications comprise historical updated module identifications besides the module identifications updated this time.
202. And under the condition that the upgrading instruction is detected to be confirmed, sending second upgrading information to the gateway through the server, so that the gateway carries out software module upgrading according to the second upgrading information.
Specifically, the user can check the upgrade information at the user end to determine whether to perform the upgrade.
The gateway firmware is provided with a plurality of software modules, firmware update issues a MOD, the version number of the MOD is the total version number of the firmware, and the MOD is irrelevant to the updating of the modules in the MOD.
In one embodiment, issuing a version of MOD needs to include the following information:
1) MOD version number: such as 1.0.4;
2) the updated module id and the module id that has been updated in history, and the version numbers corresponding to these module ids, such as the updated a module v1.0.03, the updated b module v1.0.03, and the updated c module v1.0.01 in history.
Optionally, the MOD may further include an upgrade file check code, where the upgrade file check code is used for verifying the downloaded upgrade file by the gateway, so as to determine whether the download is correct, and improve the data accuracy.
Optionally, the method further includes: and acquiring and displaying the networking state information of the gateway and the size of the upgrade module file, wherein the networking state information of the gateway and the size of the upgrade module file are used for a user to judge whether to perform the upgrade.
The specific message format and interaction mode of the user side initiating the upgrade of the gateway software module are not limited. Specifically, the user side may send the total firmware version number to the gateway through the server. Optionally, if the gateway uses a network sensitive to traffic (for example, a 4G network, a 4G card of the gateway usually limits the usage traffic, for example, 20M, and usually a code packet to be updated of the entire gateway needs 8M), the user end may present the size of the network and the upgrade module file currently used by the gateway, so that the user can determine whether to currently perform the upgrade.
In the above example, the current latest version number of all updated modules provided to the gateway continues, that is, in addition to the updated modules a and b, another module c is updated, and the latest version is 1.0.01, and also needs to be provided to the gateway at this time of update, so that version update of the module c is avoided being missed when the gateway is upgraded in a jump. The gateway can obtain all updated module information by providing the module identifier which is updated in history and the module identifier which is updated at this time, and the problem that the version of the module is not updated completely when the gateway is upgraded in a jumping way is solved.
Fig. 3 is a flowchart of another gateway software module upgrading method provided in this embodiment, where as shown in fig. 1, the method is applied to a gateway, and the method includes:
301. acquiring upgrading information of a gateway issued by a server, wherein the upgrading information comprises a total firmware version number and a second updating module list, the second updating module list comprises a plurality of module identifications and latest version numbers corresponding to the module identifications, and the module identifications comprise module identifications which are updated in a historical manner and module identifications which are updated at this time;
302. acquiring the current version number of a target module identifier, wherein the target module identifier is any module identifier in the second updating module list;
303. and under the condition that the current version number of the target module identification is lower than the updated version number of the target module identification, upgrading the target module corresponding to the target module identification.
The gateway updating method mainly comprises the steps that the current version number of the module is compared with the current updating version number locally by the gateway, if the version is older, updating is executed, and an updating program is restarted.
The steps performed by the gateway are also described in the embodiment shown in fig. 2, and are not described in detail here.
Wherein, the gateway can obtain the current latest version number of all updated modules from the server, such as shown in table 1:
for example, when APP1.0.2 is updated, the devices purchased by user 2 and user 3 can obtain the current latest versions of all updated apps through the update list, including the application programs a and b updated this time and the application program c updated last time, and can update all the apps with updates.
In practical application, a user may perform one upgrade for a long time, during which a manufacturer has issued multiple versions of the upgrade; the method can solve the problem of 'jump upgrading' without upgrading every time. And the version number comparison of the continuously updated gateway can also avoid repeated upgrading (only updating the module which is newly required to be updated currently).
Wherein only the program list updated after release of 1.0.0 is provided, and the version list of all apps is not provided directly, so as to satisfy the upgrading of a large number of basic tools and libraries (which can be regarded as application programs) on the gateway. In addition to a small number (twenty) of autonomously developed applications, the gateway also carries a large number of open source applications and software packages/libraries, the latter being less likely but likely to be updated. In this way, the software can be updated in a large quantity, and a brother long list is not required to be provided, so that the transmission flow and the gateway comparison work are saved.
Optionally, the upgrade information further includes an upgrade file check code; the method further comprises the following steps:
calculating the downloaded upgrade file according to a preset analysis algorithm to obtain an analysis check code;
comparing the analysis check code with the upgrade file check code;
and if the analysis check code is consistent with the upgrade file check code, determining that the download of the upgrade file is correct, and triggering to acquire the current version number of the target module identifier.
The gateway can download the upgrading file corresponding to the target module identification according to the target module identification of which the current version number is lower than the updating version number, and complete upgrading. Specifically, the upgrade information of the gateway issued by the server carries the upgrade address of the upgradable module, that is, the upgrade file download address, and the gateway can obtain the upgrade address of the target module from the server, so as to download and obtain the upgrade file of the corresponding target module, and upgrade the target module. Furthermore, the analytic check code of the upgrade file can be calculated by using a preset analytic algorithm and then is matched with the upgrade file check code provided by the server, if the analytic check code of the upgrade file is the same as the analytic check code of the upgrade file, the upgrade file can be downloaded correctly, and the upgrade can be carried out; if not, the upgrade is not carried out.
Optionally, the upgrade file may be verified by a Message Digest Algorithm (Message-Digest Algorithm 5), and the file contents are the same, and the MD5 values are the same. Specifically, during network transmission, the source file is checked to obtain MD5sum, after transmission is completed, the destination file is checked, and if the source file is consistent with the destination file MD5, it indicates that there is no abnormal file transmission. Otherwise, the file is not transmitted correctly in the transmission process. Therefore, the integrity of the upgrade file can be verified, and the software module can be smoothly upgraded.
Fig. 4 is a flowchart of another gateway software module upgrading method provided in this embodiment, where as shown in fig. 4, the method is applied to a server, and the method includes:
401. transmitting first upgrading information of the gateway to the terminal equipment; the first updating information comprises a first updating module list and module dependency relationship information, the first updating module list comprises updated module identifiers, and the module dependency relationship information is used for indicating whether dependency relationships exist among modules;
402. receiving a first updating instruction from the terminal equipment, responding to the first updating instruction, and sending a first upgrading file to a gateway; the first update instruction includes a first module identifier and a second module identifier, and the first upgrade file is used for upgrading the first module and the second module by the gateway.
The server can issue new first upgrade information to be provided to the terminal device of the user side, and the user selects the module to be updated by the gateway through the terminal device. The steps performed by the terminal device may refer to the specific description in the embodiment shown in fig. 1, and are not described herein again.
And under the condition of receiving an updating instruction from the terminal equipment, the server can send a corresponding upgrading file to the gateway according to the updating instruction to upgrade the software module. Specifically, the first update instruction may include a first module identifier and a second module identifier, the server may obtain a first upgrade file for upgrading the first module and the second module by the gateway, and the gateway may upgrade the first module and the second module after receiving the first upgrade file.
In an optional embodiment, the method further comprises:
transmitting second upgrading information of the gateway firmware to the terminal equipment; the second updating information comprises a total firmware version number, a second updating module list and an updating file check code, and the second updating module list comprises all updated module identifications and latest version numbers corresponding to the module identifications; the upgrade file check code is used for the gateway to check the downloaded upgrade file so as to determine whether the upgrade file is downloaded correctly;
and receiving a second updating instruction from the terminal equipment, responding to the second updating instruction, and sending the second upgrading information to the gateway so that the gateway upgrades the software module according to the second upgrading information.
The steps executed by the gateway are also described in the embodiments shown in fig. 1 and fig. 2, and are not described herein again.
To describe the whole device interaction flow more clearly, please refer to fig. 5, where fig. 5 is a schematic flow chart of another gateway software module upgrading method provided in the embodiment of the present application, and as shown in fig. 5, the method includes:
501. the method comprises the steps that a server transmits first upgrading information of a gateway to a terminal device, wherein the first upgrading information comprises a first updating module list and module dependency relationship information, the first updating module list comprises an updated module identifier, and the module dependency relationship information is used for indicating whether dependency relationship exists between modules;
502. when detecting a module selection instruction of a user, the terminal device obtains a first module identifier corresponding to the module selection instruction, where the first module identifier is at least one module identifier in the first update module list;
503. the terminal equipment judges whether the first updating module list comprises a module identifier which has a dependency relationship with the first module identifier or not according to the module dependency relationship information; if yes, acquiring a second module identifier which has a dependency relationship with the first module identifier;
504. sending a first update instruction to the server, where the first update instruction includes the first module identifier and the second module identifier;
505. the server receives a first updating instruction from the terminal equipment, responds to the first updating instruction and sends a first upgrading file to the gateway;
506. the gateway downloads the first upgrading file from the server;
507. and the gateway uses the first upgrading file to upgrade the first module and the second module.
The above steps may refer to the related detailed description in the embodiments shown in fig. 1 to fig. 4, and are not repeated herein.
Referring to fig. 6, fig. 6 is a schematic flowchart of another gateway software module upgrading method provided in an embodiment of the present application, and as shown in fig. 6, the method includes:
601. the terminal equipment acquires second upgrading information of the gateway, which is issued by the server; the second upgrade information comprises a total firmware version number and a second update module list, the second update module list comprises a plurality of module identifiers and a latest version number corresponding to each module identifier, and the module identifiers comprise module identifiers which are updated in history and module identifiers which are updated at this time;
602. the terminal equipment sends second upgrading information to the gateway through the server under the condition of detecting that an upgrading instruction is confirmed;
603. the gateway acquires second upgrading information issued by the server;
604. the gateway acquires the current version number of a target module identifier, wherein the target module identifier is any module identifier in the second updating module list;
605. and under the condition that the current version number of the target module identification is lower than the updated version number of the target module identification, upgrading the target module corresponding to the target module identification.
The above steps may refer to the related detailed description in the embodiments shown in fig. 1 to fig. 4, and are not repeated herein.
Based on the description of the above gateway software module upgrading method embodiment, the embodiment of the present application further discloses a gateway software module upgrading device. Referring to fig. 7, the gateway software module upgrade apparatus 700 includes:
an obtaining module 710 configured to:
acquiring first upgrading information of a gateway issued by a server; the first updating information comprises a first updating module list and module dependency relationship information, the first updating module list comprises updated module identification, and the module dependency relationship information is used for indicating whether dependency relationship exists between modules;
a determining module 720, configured to, when a module selection instruction of a user is detected, obtain a first module identifier corresponding to the module selection instruction, where the first module identifier is at least one module identifier in the first updated module list;
a judging module 730, configured to judge, according to the module dependency relationship information, whether a module identifier having a dependency relationship with the first module identifier is included in the first updated module list;
the obtaining module 710 is further configured to obtain update information of the first module and the second module if the first update module list includes a module identifier having a dependency relationship with the first module identifier;
a transmission module 740, configured to send a first update instruction to the server, so that the server sends a first upgrade file to the gateway; the first update instruction comprises the first module identification and the second module identification, and the first upgrade file is used for upgrading the first module and the second module by the gateway.
According to an embodiment of the present application, each step performed by the user side related to the methods shown in fig. 1 to fig. 4 may be performed by each module in the gateway software module upgrading apparatus 700 shown in fig. 7, and is not described herein again. The gateway software module upgrading device 700 in the embodiment of the application can judge the dependency relationship between modules before module upgrading is executed as a user side, and the modules with the dependency relationship are upgraded simultaneously, so that the problem that the modules with the dependency relationship are not completely selected by the user for upgrading is solved, the problem that software modules in a gateway are incompatible due to the fact that only the upgrading part is upgraded is avoided, and the upgrading intelligence is enhanced.
Based on the description of the above gateway software module upgrading method embodiment, the embodiment of the present application further discloses a gateway software module upgrading device. Referring to fig. 8, the gateway software module upgrading apparatus 800 includes:
a transmission module 810, configured to obtain upgrade information of a gateway issued by a server, where the upgrade information includes a total firmware version number and a second update module list, the second update module list includes a plurality of module identifiers and a latest version number corresponding to each module identifier, and the module identifier includes a module identifier that has been updated in history and a module identifier that is updated this time;
a processing module 820 configured to:
acquiring the current version number of a target module identifier, wherein the target module identifier is any module identifier in the second updating module list;
and under the condition that the current version number of the target module identifier is lower than the update version number of the target module identifier, upgrading the target module corresponding to the target module identifier.
According to an embodiment of the present application, each step performed by the gateway related to the method shown in fig. 1 to fig. 4 may be performed by each module in the gateway software module upgrading apparatus 800 shown in fig. 8, and is not described herein again. The gateway software module upgrading device 800 in the embodiment of the application can be a gateway, can acquire all updated module information and select a module to be updated from a master for updating, and solves the problem of incomplete module version updating when the gateway is upgraded in a jumping mode.
Based on the description of the above gateway software module upgrading method embodiment, the embodiment of the present application further discloses a gateway software module upgrading device. Referring to fig. 9, the gateway software module upgrading apparatus 900 includes a transmission module 910 for:
transmitting first upgrading information of the gateway firmware to the terminal equipment; the first updating information comprises a first updating module list and module dependency relationship information, the first updating module list comprises updated module identifiers, and the module dependency relationship information is used for indicating whether each module identifier in the first updating module list has a dependency relationship with other module identifiers and which module identifier has a dependency relationship with the other module identifiers;
receiving a first updating instruction from the terminal equipment, and responding to the first updating instruction to send a first upgrading file to a gateway; the first update instruction comprises the first module identification and the second module identification, and the first upgrade file is used for the gateway to upgrade the first module and the second module.
According to an embodiment of the present application, each step performed by the server related to the method shown in fig. 1 to fig. 4 may be performed by each module in the gateway software module upgrading apparatus 900 shown in fig. 9, and is not described herein again. The gateway software module upgrading device 900 in the embodiment of the application can be a server, can provide dependency relationship among modules to a user side, judges whether the module to be upgraded selected by the user has the module with the dependency relationship or not by the user side, and upgrades the modules with the dependency relationship in the gateway at the same time, thereby avoiding the problem of incompatibility among software modules in the gateway caused by upgrading only parts, and enhancing the upgrading intelligence and the user interactivity.
Based on the description of the method embodiment and the device embodiment, the embodiment of the application further provides an electronic device. Referring to fig. 10, the electronic device 1000 includes at least a processor 1001, an input device 1002, an output device 1003, and a computer storage medium 1004. The processor 1001, the input device 1002, the output device 1003, and the computer storage medium 1004 in the electronic device may be connected by a bus or other means.
A computer storage medium 1004 may be stored in a memory of the electronic device, the computer storage medium 1004 may be configured to store a computer program, the computer program may include program instructions, and the processor 1001 may be configured to execute the program instructions stored in the computer storage medium 1004. The processor 1001 (or CPU) is a computing core and a control core of the electronic device, and is adapted to implement one or more instructions, and in particular, is adapted to load and execute the one or more instructions so as to implement a corresponding method flow or a corresponding function; in one embodiment, the processor 1001 described above in this embodiment of the present application may be configured to perform a series of processes, including various steps performed by a user terminal, a server, or a gateway according to the methods shown in fig. 1 to fig. 4.
An embodiment of the present application further provides a computer storage medium (Memory), which is a Memory device in an electronic device and is used to store programs and data. It is understood that the computer storage medium herein may include both a built-in storage medium in the electronic device and, of course, an extended storage medium supported by the electronic device. Computer storage media provide storage space that stores an operating system for an electronic device. Also stored in this memory space are one or more instructions, which may be one or more computer programs (including program code), suitable for being loaded and executed by processor 1001. The computer storage medium may be a high-speed RAM memory, or may be a non-volatile memory (non-volatile memory), such as at least one disk memory; and optionally at least one computer storage medium located remotely from the processor.
In one embodiment, one or more instructions stored in a computer storage medium may be loaded and executed by a processor to perform the corresponding steps in the above embodiments; in a specific implementation, one or more instructions in the computer storage medium may be loaded by the processor and execute steps executed by the user side, the server, or the gateway according to the methods shown in fig. 1 to fig. 4, and so on, which are not described herein again.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and modules may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the division of the module is only one logical division, and other divisions may be possible in practice, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not performed. The shown or discussed mutual coupling, direct coupling or communication connection may be an indirect coupling or communication connection of devices or modules through some interfaces, and may be in an electrical, mechanical or other form.
Modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on or transmitted over a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a read-only memory (ROM), or a Random Access Memory (RAM), or a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, a magnetic disk, or an optical medium, such as a Digital Versatile Disk (DVD), or a semiconductor medium, such as a Solid State Disk (SSD).
Claims (11)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110233339.6A CN113094064A (en) | 2021-03-03 | 2021-03-03 | Gateway software module upgrading method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110233339.6A CN113094064A (en) | 2021-03-03 | 2021-03-03 | Gateway software module upgrading method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113094064A true CN113094064A (en) | 2021-07-09 |
Family
ID=76666262
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110233339.6A Pending CN113094064A (en) | 2021-03-03 | 2021-03-03 | Gateway software module upgrading method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113094064A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113904932A (en) * | 2021-09-29 | 2022-01-07 | 厦门亿联网络技术股份有限公司 | Modularized server upgrading method and device, electronic equipment and medium |
| CN114661329A (en) * | 2022-04-18 | 2022-06-24 | 深圳市元征软件开发有限公司 | Software upgrade method, device, device and medium |
| WO2023185322A1 (en) * | 2022-03-28 | 2023-10-05 | 杭州涂鸦信息技术有限公司 | Function updating method and related apparatus |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102262544A (en) * | 2010-05-24 | 2011-11-30 | 腾讯科技（深圳）有限公司 | Method and device for upgrading software |
| CN109547536A (en) * | 2018-11-01 | 2019-03-29 | 福建星网智慧科技股份有限公司 | Intelligent gateway device type automatic identification and method for upgrading software version and system |
| CN110032382A (en) * | 2019-03-25 | 2019-07-19 | 深圳猛犸电动科技有限公司 | A kind of vehicle electronic control unit upgrade method, system and terminal device |
| CN110908683A (en) * | 2019-10-22 | 2020-03-24 | 深圳市广和通无线通信软件有限公司 | Software system upgrading method and device of hardware module, storage medium and terminal |
| CN111367544A (en) * | 2018-12-26 | 2020-07-03 | 美的集团股份有限公司 | Multi-peripheral firmware upgrade control method, intelligent device, firmware and electronic device |
| CN111427596A (en) * | 2020-03-12 | 2020-07-17 | 浙江大华技术股份有限公司 | Software upgrading method and device and terminal equipment |
| CN112181461A (en) * | 2020-09-28 | 2021-01-05 | 珠海格力电器股份有限公司 | Upgrading method, network module, equipment, server and upgrading system |
-
2021
- 2021-03-03 CN CN202110233339.6A patent/CN113094064A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102262544A (en) * | 2010-05-24 | 2011-11-30 | 腾讯科技（深圳）有限公司 | Method and device for upgrading software |
| CN109547536A (en) * | 2018-11-01 | 2019-03-29 | 福建星网智慧科技股份有限公司 | Intelligent gateway device type automatic identification and method for upgrading software version and system |
| CN111367544A (en) * | 2018-12-26 | 2020-07-03 | 美的集团股份有限公司 | Multi-peripheral firmware upgrade control method, intelligent device, firmware and electronic device |
| CN110032382A (en) * | 2019-03-25 | 2019-07-19 | 深圳猛犸电动科技有限公司 | A kind of vehicle electronic control unit upgrade method, system and terminal device |
| CN110908683A (en) * | 2019-10-22 | 2020-03-24 | 深圳市广和通无线通信软件有限公司 | Software system upgrading method and device of hardware module, storage medium and terminal |
| CN111427596A (en) * | 2020-03-12 | 2020-07-17 | 浙江大华技术股份有限公司 | Software upgrading method and device and terminal equipment |
| CN112181461A (en) * | 2020-09-28 | 2021-01-05 | 珠海格力电器股份有限公司 | Upgrading method, network module, equipment, server and upgrading system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113904932A (en) * | 2021-09-29 | 2022-01-07 | 厦门亿联网络技术股份有限公司 | Modularized server upgrading method and device, electronic equipment and medium |
| WO2023185322A1 (en) * | 2022-03-28 | 2023-10-05 | 杭州涂鸦信息技术有限公司 | Function updating method and related apparatus |
| CN114661329A (en) * | 2022-04-18 | 2022-06-24 | 深圳市元征软件开发有限公司 | Software upgrade method, device, device and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107992308B (en) | Plug-in management method for android terminal application program | |
| US20150220326A1 (en) | Mobile Terminal and Software Upgrade Method Thereof | |
| JP5838527B2 (en) | Method, apparatus and communication device for updating firmware | |
| CN113873010B (en) | Upgrading method and device of equipment, storage medium and electronic device | |
| WO2017071207A1 (en) | Application installation method, corresponding apparatus, and application installation system | |
| CN113094064A (en) | Gateway software module upgrading method, device, equipment and storage medium | |
| CN103518191A (en) | Upgrade method, intelligent terminal and upgrade system | |
| EP2561692A1 (en) | Method and system for proximity-based, peer-initiated device configuration | |
| US9465599B2 (en) | Method, device and system for installing terminal software | |
| CN111427594B (en) | Application program running method and device | |
| CN112612493B (en) | Software upgrade method, device, equipment and storage medium for software set | |
| CN110493644B (en) | Television application upgrading method, television terminal and server | |
| EP3091435A1 (en) | Resource management method and device for terminal system | |
| CN108701018A (en) | How to update the application | |
| CN111459524A (en) | Software upgrading method, device and system | |
| CN114185579A (en) | Software upgrading method and device, electronic equipment and readable storage medium | |
| WO2022257927A1 (en) | Key burning method and apparatus, electronic device board card, and storage medium | |
| CN108121560A (en) | Difference bag upgrade method, device, terminal and computer readable storage medium | |
| KR20180050001A (en) | Firmware upgrade system and method for IoT | |
| CN118689514B (en) | Terminal firmware upgrading method, system, equipment and medium based on communication module | |
| CN110045969B (en) | Application installation method, server, system, device and storage medium | |
| US20170359213A1 (en) | Method for performing communication between browser and mobile terminal, and browser apparatus | |
| CN114610366A (en) | A differential package upgrade method, system, intelligent electronic device and storage medium | |
| CN108989428B (en) | Bluetooth terminal upgrading method, server, computer readable storage medium and system | |
| CN106293814A (en) | Upgrade method and device |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210709 |
|
| RJ01 | Rejection of invention patent application after publication |