CN115408025A - System upgrade management method and device - Google Patents
System upgrade management method and device Download PDFInfo
- Publication number
- CN115408025A CN115408025A CN202210973955.XA CN202210973955A CN115408025A CN 115408025 A CN115408025 A CN 115408025A CN 202210973955 A CN202210973955 A CN 202210973955A CN 115408025 A CN115408025 A CN 115408025A
- Authority
- CN
- China
- Prior art keywords
- upgraded
- upgrade
- client
- file
- upgrading
- 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; 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
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)
Abstract
The invention discloses a system upgrade management method and a device, comprising the following steps: at a management end, when a system upgrading instruction is received, obtaining upgrading data of a system to be upgraded, determining a client to be upgraded in at least one client according to the upgrading data, and sending the upgrading data to the client to be upgraded; and at the client, continuously receiving the upgrading data, setting the client receiving the upgrading data as a client to be upgraded, verifying the received upgrading data, and upgrading the system to be upgraded on the client to be upgraded according to the upgrading data if the verification is passed. Therefore, the invention adopts a centralized upgrade management mode, the management end uniformly determines the clients to be upgraded in the clients, and uniformly upgrades all the clients to be upgraded, so that the upgrade version of the system can be effectively managed, the complicated upgrade process is avoided, and the operation and maintenance efficiency is improved.
Description
Technical Field
The invention relates to the technical field of system operation and maintenance, in particular to a system upgrade management method and system upgrade management equipment.
Background
In the daily operation and maintenance process of the system, if one system has a plurality of users and the system needs the users to perform targeted upgrade, a dispersed and independent system upgrade mode is often adopted.
However, due to the large number of users, the upgrade method causes the system upgrade to be troublesome to manage.
Disclosure of Invention
Based on this, there is a need for a system upgrade management method and apparatus to solve the problem that upgrade management becomes cumbersome.
A system upgrade management method is applied to a management end, wherein the management end is connected with at least one client, and the method comprises the following steps:
when a system upgrading instruction is received, obtaining upgrading data of a system to be upgraded, determining a client to be upgraded in at least one client according to the upgrading data, and sending the upgrading data to the client to be upgraded so that the client to be upgraded responds to the upgrading data to upgrade the system.
In one embodiment, the obtaining upgrade data of a system to be upgraded, determining a client to be upgraded in the at least one client according to the upgrade data, and sending the upgrade data to the client to be upgraded includes:
acquiring the name, the target version number and the upgrading area of a system to be upgraded;
acquiring and packaging an upgrade file according to the name and the target version number of a system to be upgraded, acquiring a packaged file after packaging, and taking the packaged file and configuration information for upgrading as upgrade data; wherein the configuration information includes a system code, the target version number, and the upgrade area;
and in the at least one client, determining the client in the upgrading area as a client to be upgraded, and sending the upgrading data to the client to be upgraded.
In one embodiment, the method is applied to at least one client, and the at least one client is connected with a management terminal, and the method comprises the following steps:
the client to be upgraded receives the upgrade data sent by the management terminal; the client to be upgraded is determined by the management terminal in the at least one client according to the upgrade data;
and verifying the received upgrading data, and upgrading the system to be upgraded on the client to be upgraded according to the upgrading data if the received upgrading data passes the verification.
In one embodiment, the receiving the upgrade data sent by the management end includes:
receiving a packaging file and configuration information for upgrading, and taking the received packaging file and configuration information as upgrading data; the packaging file is a file obtained by packaging the upgrade file.
In one embodiment, the configuration information includes a system code, and the verifying the received upgrade data includes:
checking whether a system code in the upgrading data exists or not, and checking whether a system type indicated by the system code belongs to a preset system type or not;
and if the system code in the upgrading data exists and the system type indicated by the system code belongs to a preset system type, judging that the verification is passed.
In one embodiment, the configuration information includes the target version number, and the verifying the received upgrade data includes:
and acquiring a local version number of the system to be upgraded, judging whether the target version number is consistent with the local version number, and if the target version number is inconsistent with the local version number, judging that the verification is passed.
In one embodiment, the configuration information includes the upgrade area, and the verifying the received upgrade data includes:
acquiring a current client area, and judging whether the upgrading area is consistent with the current client area;
and if the upgrading area is consistent with the current client area, judging that the verification is passed.
In one embodiment, upgrading a system to be upgraded on the client to be upgraded according to the upgrade data includes:
decompressing the packed file in the upgrade data to obtain a decompressed upgrade file;
if the decompressed upgrade file is a script file, executing the upgrade file;
if the decompressed upgrade file is a batch file, operating a batch processing command to perform batch processing on the upgrade file;
if the decompressed upgrade file is a configuration file, updating the configuration based on the upgrade file;
and if the decompressed upgrade file is a replaceable file, replacing the existing file with the same name by the upgrade file.
And after the system to be upgraded is upgraded, updating the local version number of the upgraded system.
In one embodiment, upgrading the system to be upgraded on the client to be upgraded according to the upgrade data further includes:
if the decompressed upgrade file is an execution file, judging whether the upgraded execution file belongs to a system process in the system to be upgraded, if so, closing a target system process, updating the target system process, and opening the target system process again after updating; the target system process is a system process for correspondingly executing the file;
if the upgraded execution file does not belong to the system process in the system to be upgraded, judging whether the target process to be upgraded is started, if the target process to be upgraded is started, closing the started target process, updating the target process, and starting the target process again after updating.
A system upgrade management device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to carry out the steps of the above system upgrade management method.
The invention provides a system upgrade management method and equipment.A management end acquires upgrade data of a system to be upgraded when receiving a system upgrade instruction, determines a client to be upgraded in at least one client according to the upgrade data, and sends the upgrade data to the client to be upgraded; and at the client, continuously receiving the upgrading data, setting the client receiving the upgrading data as a client to be upgraded, verifying the received upgrading data, and upgrading the system to be upgraded on the client to be upgraded according to the upgrading data if the verification is passed. Therefore, the invention adopts a centralized upgrade management mode, the management end uniformly determines the clients to be upgraded in the clients, and uniformly upgrades all the clients to be upgraded, so that the upgrade version of the system can be effectively managed, the complicated upgrade process is avoided, and the operation and maintenance efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention 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 invention, 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 system upgrade management method in a first embodiment;
FIG. 2 is a diagram of a management side upgrade program in one embodiment;
FIG. 3 is a flowchart illustrating a system upgrade management method according to a second embodiment;
FIG. 4 is a diagram of a general system upgrade program in one embodiment;
FIG. 5 is a block diagram of a flow diagram of system upgrade management in one embodiment;
fig. 6 is a block diagram showing the configuration of a system upgrade management apparatus in one embodiment.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without inventive step based on the embodiments of the present invention, are within the scope of protection of the present invention.
As shown in fig. 1, fig. 1 is a schematic flow chart of a system upgrade management method in a first embodiment, and is applied to a management end, where the management end needs to be deployed on an upgrade server specially used for upgrade, and then is connected with at least one client through the upgrade server. The system upgrading method can realize the purpose of upgrading the systems on a plurality of clients at the same time by carrying out corresponding upgrading configuration on the management terminal.
The system upgrade management method in the first embodiment provides the following steps:
Specifically, the system upgrade instruction may be input into the management end by a system administrator, may be automatically initiated when the management end acquires the latest upgrade data, and may also be in other forms, which is not specifically limited herein.
As shown in fig. 2, the management end is installed with a management end upgrade program, and first, corresponding upgrade configuration is performed on the management end, including setting the name of the system to be upgraded, corresponding to "subsidy year or system selected" in fig. X, for example, the "subsidy system" is selected; also includes setting a target version number, corresponding to "version number of input system" in fig. X, e.g., 2022.7.27.5 is selected; and setting an upgrading area corresponding to the area for selecting upgrading in the diagram X, such as Shanxi province and Shaanxi province.
And then arranging the upgrade files in sequence. The upgrading file of the database needs to be arranged into an sql suffix file, other files are arranged according to the actual path and upgrading requirements of Web application, the file to be upgraded is sequentially selected according to the name and the target version number of the system to be upgraded, the upgraded target file is packaged, and therefore the packaged file can be obtained. Corresponding to the "selecting the original file to be upgraded" and "selecting the target file name to be upgraded" in fig. X, for example, a 1.Sql file is selected, and the target file after upgrading is dsql/1.Sql.
Further, the system administrator generates configuration information including the system code, the target version number, and the upgrade area after the click confirmation. And finally, taking the packaged file and the configuration information for upgrading as upgrading data, determining the client in an upgrading area as a client to be upgraded in at least one client, and sending the upgrading data to the determined client to be upgraded. Illustratively, the transmitted upgrade data includes a 22_07_27 _5file (package file), a scur _ update.txt (storing a target version number), and a sall _ update.txt (storing an upgrade region and system code).
Therefore, the invention adopts a centralized upgrade management mode, the management end uniformly determines the clients to be upgraded in the clients, and uniformly upgrades all the clients to be upgraded, so that the upgrade version of the system can be effectively managed, the complicated upgrade process is avoided, and the operation and maintenance efficiency is improved.
As shown in fig. 3, fig. 3 is a flowchart illustrating a system upgrade management method in a second embodiment, and is applied to at least one client, where the clients need to be deployed on a server where a Web application is located and are connected to a management end through the server where the Web application is located. The client mainly has the functions of automatically detecting the upgrade server at regular time and updating the local system after acquiring upgrade data from the upgrade server.
The system upgrade management method in the second embodiment provides steps including:
The client to be upgraded is determined in at least one client by the management terminal according to the upgrading data. For example, if the upgrade data defines that the upgrade area is shanxi province and shanxi province, only the clients in shanxi province and shanxi province are used as the clients to be upgraded.
Specifically, as shown in fig. 4, all the clients are installed with a general system upgrade program, and upgrade data may be downloaded from the upgrade server by inputting an http address on the general system upgrade program of the client to be upgraded. The universal system upgrading program can select 'immediate upgrading', 'upgrading stop' and 'background running', and can also know the upgrading progress and the upgrading log.
In a particular embodiment, the received upgrade data includes a package file and configuration information for the upgrade; the package file comprises an upgrade file, and the upgrade file can be used after being decompressed.
And 304, verifying the received upgrading data, and upgrading the system to be upgraded on the client to be upgraded according to the upgrading data if the received upgrading data passes the verification.
In this embodiment, the system upgrade is performed only after the upgrade data passes verification.
In one embodiment, the obtained configuration information includes system code, and a THREAD Identifier (tid) file is generated on the client system, as shown in fig. 5, where the verification process includes: whether a system code in the upgrading data exists or not can be verified based on the tid file, and whether a system type indicated by the system code belongs to a preset system type (such as a subsidy system) or not can be verified; if the system code in the upgrade data exists and the system type indicated by the system code belongs to a preset system type (such as a subsidy system), the verification is determined to be passed. And once no system code exists or the system type cannot be distinguished through the system code, upgrading is forbidden.
Further, the obtained configuration information further includes a target version number, for example, the version number is 2022.7.27.5. As shown in fig. 5, the verification process further includes: the local version number of the system to be upgraded is obtained, for example, 2022.7.27.1. And judging whether the target version number is consistent with the local version number, wherein the target version number is 2022.7.22.1 is smaller than 2022.7.22.5, so that upgrading is required, and the verification is passed. If the version numbers are consistent, the upgrading is judged not to be needed.
Further, the acquired configuration information includes upgrade areas, such as shanxi province and shanxi province. As shown in fig. 5, the verification process further includes: and acquiring the current client area. Judging whether the upgrading area is consistent with the current client area; for example, if the current client area belongs to shanxi province, the verification is determined to be passed. And if the current client area belongs to Beijing city, judging that the verification fails and forbidding upgrading.
It should be understood that the verification process may be only a part of the verification process, or may be all of the verification process, and the verification order may also be appropriately adjusted, which is not specifically limited herein. By performing the operation of verifying the upgrade data, system error upgrade can be avoided, and the accuracy of centralized management is improved.
When the verification is passed, decompressing a packaged file (22_07_27_5 file) in the upgrade data, acquiring the decompressed upgrade file, analyzing the types of all files in the upgrade file, and performing system upgrade based on the types, specifically:
in the first case, if the decompressed upgrade file is a script file, the upgrade file is executed.
In the second case, if the decompressed upgrade file is a batch file, a batch command is run to perform batch processing on the upgrade file.
In the third case, if the decompressed upgrade file is a configuration file, the configuration is updated based on the upgrade file.
In the fourth situation, if the decompressed upgrade file is a replaceable file, the upgrade file is used to replace the existing file with the same name.
In the fifth case, if the decompressed upgrade file is an execution file, it is determined whether the upgraded execution file belongs to a system process in the system to be upgraded, and if the upgraded execution file belongs to the system process in the system to be upgraded, the target system process is closed, so as to avoid that the upgrade cannot be performed, the target system process is updated, and the target system process is opened again after the update. The target system process is a system process which correspondingly executes the file.
If the upgraded execution file does not belong to the system process in the system to be upgraded, whether the target process to be upgraded is started or not is judged, if the target process to be upgraded is started, the started target process is closed, the situation that the target process cannot be upgraded is avoided, the target process is updated, and the target process is restarted after the target process is updated.
And finally, after the system to be upgraded is upgraded, updating the local version number of the upgraded system, such as 2022.7.27.5.
Therefore, the invention adopts a centralized upgrade management mode, the management end uniformly determines the clients to be upgraded in the clients, and uniformly upgrades all the clients to be upgraded, so that the upgrade version of the system can be effectively managed, the complicated upgrade process is avoided, and the operation and maintenance efficiency is improved.
FIG. 6 is a diagram that illustrates an internal structure of the system upgrade management device, in one embodiment. As shown in fig. 6, the system upgrade management device includes a processor, a memory, and a network interface connected through a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the system upgrade management apparatus stores an operating system and may further store a computer program, and the computer program, when executed by the processor, may cause the processor to implement the system upgrade management method. The internal memory may also have a computer program stored therein, which when executed by the processor, causes the processor to perform the system upgrade management method. It will be understood by those skilled in the art that the structure shown in fig. 6 is a block diagram of only a portion of the structure associated with the present application, and does not constitute a limitation on the system upgrade management apparatus to which the present application is applied, and a particular system upgrade management apparatus may include more or less components than those shown in the drawings, or may combine some components, or have a different arrangement of components.
A system upgrade management device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the following steps when executing the computer program: when a system upgrading instruction is received, obtaining upgrading data of a system to be upgraded, determining a client to be upgraded in at least one client according to the upgrading data, and sending the upgrading data to the client to be upgraded so that the client to be upgraded can respond to the upgrading data to upgrade the system.
And the following steps are realized: the method comprises the steps that a client to be upgraded receives upgrade data sent by a management end; and verifying the received upgrading data, and upgrading the system to be upgraded on the client to be upgraded according to the upgrading data if the received upgrading data passes the verification.
It should be noted that the above system upgrade management method and apparatus belong to a general inventive concept, and the contents in the embodiments of the system upgrade management method and apparatus are mutually applicable.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct Rambus Dynamic RAM (DRDRAM), and Rambus Dynamic RAM (RDRAM), among others.
All possible combinations of the technical features in the above embodiments may not be described for the sake of brevity, but should be considered as being within the scope of the present disclosure as long as there is no contradiction between the combinations of the technical features.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A system upgrade management method is applied to a management end, wherein the management end is connected with at least one client, and the method comprises the following steps:
when a system upgrading instruction is received, obtaining upgrading data of a system to be upgraded, determining a client to be upgraded in the at least one client according to the upgrading data, and sending the upgrading data to the client to be upgraded so that the client to be upgraded responds to the upgrading data to upgrade the system.
2. The method of claim 1, wherein the obtaining upgrade data of a system to be upgraded, determining a client to be upgraded among the at least one client according to the upgrade data, and sending the upgrade data to the client to be upgraded comprises:
acquiring the name, the target version number and the upgrading area of a system to be upgraded;
acquiring an upgrade file according to the name and the target version number of a system to be upgraded, packaging the upgrade file, acquiring a packaged file, and using the packaged file and configuration information for upgrading as upgrade data; wherein the configuration information includes a system code, the target version number, and the upgrade area;
and in the at least one client, determining the client in the upgrading area as a client to be upgraded, and sending the upgrading data to the client to be upgraded.
3. A system upgrade management method is applied to at least one client, and the at least one client is connected with a management end, and the method comprises the following steps:
the client to be upgraded receives the upgrade data sent by the management terminal; the client to be upgraded is determined by the management terminal in the at least one client according to the upgrading data;
and verifying the received upgrading data, and if the received upgrading data passes the verification, upgrading the system to be upgraded on the client to be upgraded according to the upgrading data.
4. The method according to claim 3, wherein the receiving the upgrade data sent by the management end comprises:
receiving a packaging file and configuration information for upgrading, and taking the received packaging file and configuration information as upgrading data; the packaged file is obtained by packaging the upgrade file.
5. The method of claim 4, wherein the configuration information comprises system code, and wherein validating the received upgrade data comprises:
checking whether a system code in the upgrading data exists or not, and checking whether a system type indicated by the system code belongs to a preset system type or not;
and if the system code in the upgrading data exists and the system type indicated by the system code belongs to a preset system type, judging that the verification is passed.
6. The method of claim 4, wherein the configuration information includes the target version number, and wherein validating the received upgrade data comprises:
and acquiring a local version number of the system to be upgraded, judging whether the target version number is consistent with the local version number, and if the target version number is inconsistent with the local version number, judging that the verification is passed.
7. The method of claim 4, wherein the configuration information includes the upgrade area, and wherein validating the received upgrade data comprises:
acquiring a current client area, and judging whether the upgrading area is consistent with the current client area;
and if the upgrading area is consistent with the current client area, judging that the verification is passed.
8. The method of claim 4, wherein upgrading the system to be upgraded on the client to be upgraded according to the upgrade data comprises:
decompressing the packed file in the upgrade data, and acquiring the decompressed upgrade file;
if the decompressed upgrade file is a script file, executing the upgrade file;
if the decompressed upgrade file is a batch file, operating a batch processing command to perform batch processing on the upgrade file;
if the decompressed upgrade file is a configuration file, updating the configuration based on the upgrade file;
if the decompressed upgrade file is a replaceable file, replacing the existing file with the same name by the upgrade file;
and after the system to be upgraded is upgraded, updating the local version number of the upgraded system.
9. The method of claim 8, wherein upgrading the system to be upgraded on the client to be upgraded according to the upgrade data further comprises:
if the decompressed upgrade file is an execution file, judging whether the upgraded execution file belongs to a system process in the system to be upgraded, if so, closing a target system process, updating the target system process, and opening the target system process again after updating; the target system process is a system process which correspondingly executes the file;
if the upgraded execution file does not belong to the system process in the system to be upgraded, judging whether the target process to be upgraded is started, if the target process to be upgraded is started, closing the started target process, updating the target process, and starting the target process again after updating.
10. A system upgrade management device comprising a memory and a processor, characterized in that the memory stores a computer program which, when executed by the processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210973955.XA CN115408025A (en) | 2022-08-15 | 2022-08-15 | System upgrade management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210973955.XA CN115408025A (en) | 2022-08-15 | 2022-08-15 | System upgrade management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115408025A true CN115408025A (en) | 2022-11-29 |
Family
ID=84159104
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210973955.XA Pending CN115408025A (en) | 2022-08-15 | 2022-08-15 | System upgrade management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115408025A (en) |
-
2022
- 2022-08-15 CN CN202210973955.XA patent/CN115408025A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108876121B (en) | Work order processing method and device, computer equipment and storage medium | |
| CN110633160A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN111158717A (en) | Firmware upgrading method, device and medium for device | |
| CN111263354B (en) | OTA differential upgrading method and device | |
| CN109358869A (en) | Configuration file amending method, device, computer equipment and storage medium | |
| CN107748668A (en) | A kind of method and device of application program updating | |
| CN110851159B (en) | Business rule updating method and device, computer equipment and storage medium | |
| CN110908681A (en) | Method and device for upgrading software | |
| CN112114994A (en) | Exception handling method, device, equipment and medium | |
| CN110968510A (en) | SSD automatic online upgrading firmware test method and device and computer equipment | |
| CN113721931A (en) | Automatic service deployment method, system and computer readable storage medium | |
| CN114265607A (en) | Gray scale publishing method and system, electronic device and storage medium | |
| CN115277677A (en) | Batch archive hooking method and device, computer equipment and storage medium | |
| CN101146111B (en) | A file download method and device | |
| CN111580927A (en) | Communication method and container communication system | |
| CN113094077B (en) | System differential upgrading method and device, intelligent terminal and storage medium | |
| CN112748949A (en) | Software package management method, device, equipment and storage medium of operating system | |
| CN111158747B (en) | APP prompt message dynamic configuration method, system, computer equipment and storage medium | |
| CN115277678B (en) | File downloading method, device, computer equipment and storage medium | |
| CN115408025A (en) | System upgrade management method and device | |
| CN111918278A (en) | Over-the-air upgrade checking method, device, medium and intelligent terminal equipment | |
| CN111338644A (en) | Task script deployment method and system | |
| CN112947956B (en) | Application software upgrading method | |
| CN114218188A (en) | Data migration method, device, equipment and storage medium | |
| CN115357260A (en) | Program upgrading method and device for terminal equipment, terminal equipment and storage medium |
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 |