Software maintenance method and equipment for chemical industry park, and medium

Abstract

The invention discloses a software maintenance method and device for a chemical industry park and a medium, and the method comprises the steps: responding to an updating instruction, downloading a target new version program package from a preset distributed file warehouse, carrying out the updating of old version client software of an Internet of Things device, and backing up the currently running old version program package; monitoring the running state of the new-version client software, deleting the target new-version program package under the condition that the new-version client software fails to start, and rolling back the old-version program package from the backup directory; and monitoring the running state of the recovered task process of the old-version client software so as to restart the old-version client software under the condition that the task process is abnormal. Through the method, the version upgrading risk is reduced, the real-time operation health degree of the distributed equipment can be remotely mastered, traditional passive fault processing is converted into active early warning, and the fault positioning time is greatly shortened.

Description

Technical Field

[0001] This application relates to the field of software maintenance technology, and in particular to a software maintenance method, equipment and medium for chemical industrial parks. Background Technology

[0002] In the intelligent construction of chemical industrial parks, IoT devices undertake critical tasks such as environmental monitoring, process control, and safety early warning, and their client software needs to operate 24 / 7. However, the complex industrial environment and highly interconnected production processes pose significant challenges to the maintenance of client software. Traditional maintenance methods relying on manual on-site inspections have significant drawbacks. Maintenance personnel must check the operating status of each device individually and manually restart it after discovering an abnormal stop in the client software. This method has a strong response lag and cannot meet the requirements for minute-level fault recovery, leading to a continuous accumulation of production interruption risks. Especially when the equipment is widely distributed and numerous, the efficiency of manual maintenance drops sharply, and the time spent on fault diagnosis increases proportionally to production losses.

[0003] The existing client software update mechanism also suffers from systemic deficiencies. Update operations are typically performed manually by uploading installation packages and triggering replacement scripts, lacking a complete closed-loop control process. Furthermore, the current system lacks centralized monitoring capabilities for client operational status. Maintenance personnel cannot perceive the real-time software operational status of distributed devices, and can only detect anomalies through periodic inspections or fault reporting. Summary of the Invention

[0004] This application provides a software maintenance method, equipment, and medium for chemical industrial parks to solve the aforementioned technical problems.

[0005] On one hand, embodiments of this application provide a software maintenance method for chemical industrial parks, including: In response to an update command, the target new version of the application package is downloaded from a pre-defined distributed file repository to update the old version of the client software for IoT devices, and the currently running old version of the application package is backed up. Monitor the running status of the new version client software, and if the new version client software fails to start, delete the target new version program package and roll back the old version program package from the backup directory; Monitor the running status of the old version client software task process after recovery, so as to restart the old version client software if the task process is abnormal.

[0006] In one implementation of this application, before downloading the target new version package from a preset distributed file repository in response to an update instruction, the method further includes: A digital profile is created for each client software of an IoT device on a centralized management platform, and the basic connection metadata of the client software is entered into the digital profile; The basic connection metadata is format-validated, and after the format validation passes, the basic connection metadata is connected to perform a connectivity test to determine whether remote operation is feasible. Upload the new version of the client software package through the centralized management platform, and perform structural integrity verification and naming convention verification on the new version of the package. After the structural integrity check and naming convention check pass, the new version of the program package is stored in a distributed file repository, and the download path and associated file summary corresponding to the new version of the program package are generated.

[0007] In one implementation of this application, in response to an update command, a target new version program package is downloaded from a preset distributed file repository to update the old version client software of the IoT device, specifically including: Based on the update request triggered by the target client software, a structured update instruction is generated, and in response to the update instruction, the target new version program package corresponding to the target client software and the file digest of the target new version program package are asynchronously downloaded from the preset distributed file repository. After the target new version program package is successfully downloaded, the integrity of the target new version program package is checked according to the summary information. If the integrity check fails, the update operation of the old version client software is interrupted and a warning of abnormal integrity of the target new version program package is reported. If the integrity verification of the target new version package passes, a predefined stop script is invoked to terminate the old version client software process and replace the old version package with the target new version package to update the old version client software of the IoT device.

[0008] In one implementation of this application, it further includes: During the asynchronous download of the target new version program package, for the interrupted download task of the target new version program package, the breakpoint resume mechanism is enabled, and the segmented program packages obtained by the breakpoint resume are merged to obtain the target new version program package. The network quality during the asynchronous download process is monitored, and the download bandwidth threshold of the target new version program package is dynamically adjusted based on the monitored real-time network quality. If the communication duration of the target new version package exceeds a preset communication threshold, a communication retry operation is triggered until the preset maximum retry count threshold is reached.

[0009] In one implementation of this application, backing up the currently running older version of the program package specifically includes: Determine the backup timestamp and version number corresponding to the currently running old version program package, and jointly name the backup directory corresponding to the old version program package based on the backup timestamp and the version number; The backed-up older version of the program package is compressed and stored, and historical backup files are automatically cleaned up according to a preset storage period strategy.

[0010] In one implementation of this application, when monitoring the running status of a new version of the client software, the method further includes: Capture the startup logs of the new version of the client software in real time, and scan the log content to see if it contains preset successful startup keywords; If no process is detected to be alive and no startup keyword is captured within a preset time, the new version of the client software is deemed to have failed to start.

[0011] In one implementation of this application, the method further includes monitoring the running status of the restored old version client software task process, and restarting the old version client software in case of an abnormal task process: The central management platform periodically sends heartbeat requests to the daemon to collect corresponding heartbeat data. The heartbeat data includes: client software version number, process running status, latest upgrade information, and abnormal events. The heartbeat data is summarized, and a corresponding visual monitoring report is generated; If the heartbeat data exceeds the constraint conditions, an abnormal alarm is triggered, and the alarm information is pushed to the corresponding management personnel; The constraints are: the number of consecutive abnormal stops of the client software exceeds the preset restart threshold, or the cumulative number of heartbeat response timeouts of the daemon reaches the preset alarm threshold, or the version update failure rate of the client software exceeds the historical baseline deviation value.

[0012] In one implementation of this application, when monitoring the running status of the restored old version client software task process, the method further includes: Periodically check the response status of the client software's listening port; If the hash value of the client software's configuration file is found to be inconsistent with the recorded value on the centralized management platform, the configuration file of the client software will be marked as a configuration tampering event. If the client software fails to maintain operation after repeated restarts, a fault alarm is sent to the centralized management platform.

[0013] On the other hand, this application embodiment also provides a software maintenance device for a chemical industrial park, the device comprising: At least one processor; And, a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, which, when executed, enable the at least one processor to perform a software maintenance method for a chemical industrial park as described above.

[0014] On the other hand, this application embodiment also provides a non-volatile computer storage medium storing computer-executable instructions, which, when executed, implement the software maintenance method for a chemical industrial park as described above.

[0015] This application provides a software maintenance method, equipment, and medium for chemical industrial parks, which has at least the following beneficial effects: By monitoring the client software process status in real time, an automatic restart is immediately executed when an abnormal process stop is detected, reducing the interruption of several hours required for traditional manual response to seconds-level recovery. This effectively avoids the chain risks of environmental monitoring interruption and process control failure caused by client software crashes in chemical production scenarios. When a new version fails to start, a closed-loop rollback process of deleting the abnormal version, restoring the old version, and restarting for verification is automatically triggered, completely solving the system unavailability problem caused by update failure and reducing the risk of version upgrades. The client software version number, process running status, and abnormal event data are collected in real time and visualized monitoring reports are generated. Maintenance personnel can remotely monitor the real-time operational health of distributed devices, transforming traditional passive fault handling into proactive early warning and significantly reducing fault location time. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 A flowchart illustrating a software maintenance method for a chemical industrial park, provided as an embodiment of this application; Figure 2 This is a schematic diagram of the internal structure of a software maintenance device for a chemical industrial park, provided as an embodiment of this application. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0018] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0019] Figure 1 This is a flowchart illustrating a software maintenance method for a chemical industrial park, as provided in an embodiment of this application.

[0020] The analysis method involved in the embodiments of this application can be implemented by a terminal device or a server, and this application does not impose any special limitations on it. For ease of understanding and description, the following embodiments are all described in detail using a server as an example.

[0021] It should be noted that the server can be a single device or a system composed of multiple devices, i.e., a distributed server. This application does not make any specific limitations on this.

[0022] like Figure 1 As shown in the embodiment of this application, a software maintenance method for a chemical industrial park is provided, comprising: Step 101: In response to the update command, download the target new version program package from the preset distributed file repository to update the old version client software of the IoT device and back up the currently running old version program package.

[0023] In one embodiment of this application, to achieve lifecycle management of client programs, administrators first need to create a digital profile for each client program instance in a centralized management platform. During this process, the basic connection metadata of the node where the client program resides needs to be entered, as shown in Table 1 below: Table 1 Basic Connection Meta Information

[0024] This step ensures the platform has the ability to communicate with the daemon subsequently. The system backend performs format verification and connectivity testing on the access information to ensure that remote operations are reachable and secure.

[0025] After the connection is configured, the administrator uploads the new version of the client program package, usually in compressed format, through the centralized management platform. During the receiving process, the centralized management platform triggers an automatic verification process. First, it verifies the file structure integrity and naming conventions to prevent unauthorized overwriting. Next, it verifies the uniqueness and incrementability of the version number to prevent rollback logic confusion. Finally, after successful upload, the system automatically stores the package in a distributed file repository and generates a unique downloadable path and associated digital digest. This information will be used for subsequent remote downloading and integrity verification of the daemon program.

[0026] In one embodiment of this application, the administrator instructs personnel to select the target client software instance through a centralized management platform and click the update operation. Subsequently, the centralized management platform will issue a structured upgrade update instruction, as shown in Table 2 below: Table 2 Update Instructions

[0027] Upon receiving the instruction, the daemon initiates an asynchronous download task. Considering the instability of edge network environments, the system incorporates a mechanism for resuming interrupted downloads, timeout retries, and bandwidth control strategies to ensure stable downloads even for large file packages. After the download is complete, the daemon performs a local integrity check using pre-delivered digest information. If the check fails, the update process is immediately interrupted and an exception is reported.

[0028] In this embodiment, the update command is generated and encrypted by the centralized management platform and sent to the daemon of the IoT device. It should be noted that the command includes a download address, target version number, file verification information, and execution parameters (such as --env=prod). The file verification information uses a digest value generated by the SHA256 algorithm (such as "a3b1c5...") for subsequent integrity verification.

[0029] For example, when the daemon performs asynchronous downloads, it incorporates breakpoint resumption and bandwidth control mechanisms to address the instability of the dedicated network in the chemical industrial park. Specifically, the program package is divided into multiple data blocks for independent download. When the network is interrupted, only the incomplete blocks need to be retransmitted. The network latency is dynamically monitored; if an increase in transmission latency is detected, the number of concurrent threads is automatically reduced to control bandwidth usage. Furthermore, if the communication time for the target new version program package exceeds a preset communication threshold, a communication retry operation is triggered until a preset maximum retry threshold is reached. Additionally, a local hash value is calculated immediately after each data block download to prevent data corruption during transmission.

[0030] Specifically, after the download is complete, an integrity check is performed. Using a file digest issued by the centralized management platform, a hash calculation is performed on the complete file of the downloaded target new version program package. If the check fails, the file is deleted and the download process is retried. This mechanism effectively prevents the risk of program file corruption due to network transmission errors.

[0031] In one embodiment of this application, to improve system rollback capability, the daemon completely copies the existing running client program to the backup area before performing a replacement operation. The backup mechanism automatically names the backups by timestamp, supports multi-version storage, on-demand compression and cleanup, avoids unlimited disk space growth, and records the corresponding version number and execution status logs for easy problem tracing. In the event of a failure at any subsequent stage, it can serve as the rollback source, ensuring system reversibility.

[0032] Once the verification is successful, the backup mechanism is integrated to perform a backup of the old version. The backup directory name is generated according to the rule "backup_timestamp_version number" (e.g., backup_202505101200_v1.5) to ensure version traceability. The old version program files are compressed and stored using the LZMA compression algorithm, which significantly reduces disk space usage. An automatic cleanup task is also started to delete historical backups according to the preset storage policy.

[0033] Furthermore, before replacing the program, a predefined stop script, such as / bin / stop_app.sh, is called to terminate the old version of the client software process, and the process tree is verified to have completely exited via system commands to avoid file usage conflicts.

[0034] Step 102: Monitor the running status of the new version client software so that if the new version client software fails to start, delete the target new version program package and roll back the old version program package from the backup directory.

[0035] In one embodiment of this application, after the program replacement is completed, the daemon will call a unified startup script and continuously monitor the running status of the client program process. Specifically, it monitors the process status of the client program or calls the heartbeat interface to ensure that the client program has not entered a zombie state, and captures startup logs in real time to detect whether the specified "startup successful" keyword is output. If the new version of the client program runs successfully within a preset time, the update is successful, and the daemon will report information such as version number, log path, and startup time to the centralized management platform in real time and persist it. If startup fails or a serious exception occurs, the daemon will automatically trigger version rollback logic, kill the abnormal process, delete the current version file, restore the old version backup, restart and monitor the old version's running status, and finally record the entire rollback chain and report it to the platform. This failure self-healing mechanism is one of the key designs for improving the high availability of the client.

[0036] In this embodiment, after the daemon starts the target new version of the program package, it immediately starts a two-dimensional monitoring mechanism to continuously check whether the main process identifier (PID) of the client software exists in the operating system process list, and to parse the client startup log file in real time to scan whether the log file contains a preset success identifier, such as "INIT_COMPLETED".

[0037] It should be noted that the startup failure determination uses a composite condition: if, within a preset time threshold, both the process PID not being detected as alive and the successful log keyword not being captured, the rollback process is triggered. For example, in the ammonia sensor upgrade scenario, if the log continuously outputs the "DB_CONN_FAILED" error message and the process repeatedly crashes, it meets the startup failure condition.

[0038] Specifically, the rollback operation executes a five-step closed-loop process: forcibly terminating the abnormal new version process (e.g., using `kill -9 [PID]`), deleting the new version program files and their configuration files, unpacking the old version program package from the latest backup directory, calling the startup script to restart the old version client, and sending a rollback event report to the centralized management platform, including the reason for failure and the rollback version number. Understandably, this design aligns with the core features of secure rollback, ensuring that the system can automatically recover to a usable state in a very short time when an update fails.

[0039] Step 103: Monitor the running status of the task process of the restored old version client software so as to restart the old version client software in case of abnormal task process.

[0040] In one embodiment of this application, the client daemon has process monitoring capabilities, resides on the IoT device for a long time, and is responsible for collecting the daily running status of the client program, detecting anomalies, and handling disaster recovery.

[0041] The daemon has an internal scheduled task thread pool responsible for checking whether the client program's main process PID is alive, checking the client program's port status and return code, verifying whether critical configuration files have been illegally modified, and checking whether the recent running logs contain abnormal information. If the client program unexpectedly terminates, the daemon immediately invokes the restart logic to prevent business interruption. If three consecutive restarts fail, it automatically reports the issue to the centralized management platform.

[0042] The centralized management platform periodically sends heartbeat requests to the client daemon, the request including the client's unique identifier and timestamp. The daemon's response is shown in Table 3 below: Table 3 Daemon Response Content

[0043] The platform aggregates and stores all heartbeat data, allowing administrators to view the overall operational health status through the platform interface. The visual monitoring page supports aggregated statistics by project, version, region, and other dimensions, facilitating fault tracing and problem comparison analysis.

[0044] When the system detects any of the following abnormal scenarios: the client program stops more than 3 times in a row, the daemon's heartbeat timeout exceeds the threshold, the startup log continues to increase abnormally, or the version update failure rate is abnormally high, the centralized management platform will automatically trigger asynchronous alarm logic and push the alarm information to the operation and maintenance manager via WeChat, SMS or email, so as to achieve timely awareness of the fault and significantly shorten the problem response time.

[0045] In this embodiment, the daemon continuously monitors the client's runtime status through a multi-factor health check mechanism. It periodically sends status query commands to the client software's business port, such as 8080, to verify whether the return code meets expectations, such as HTTP 200, calculates the hash value of key configuration files and compares it with the benchmark value recorded by the centralized management platform, and analyzes the runtime logs in real time. When a preset error pattern is matched, it is marked as a potential fault, such as "OUT_OF_MEMORY".

[0046] It should be noted that when an abnormal process stop is detected, such as a port becoming unresponsive and the process disappearing, an automatic restart is immediately triggered. For example, in a chemical pump control system, if the pressure analysis module process crashes, causing a port 503 error, the daemon will restart the client within seconds to resume data acquisition.

[0047] Furthermore, if the client fails to restart multiple times in a row, the centralized management platform marks the device as a "serious fault state". When the platform analyzes the heartbeat data, it will automatically generate an alarm event when it detects a batch communication timeout or a sudden increase in the version rollback rate of devices in the area. The alarm information will be pushed to the operation and maintenance group through the enterprise WeChat robot, including the device location, fault type and historical operation statistics.

[0048] The above are embodiments of the method proposed in this application. Based on the same inventive concept, embodiments of this application also provide a software maintenance device for chemical industrial parks, the structure of which is as follows: Figure 2 As shown.

[0049] Figure 2 This is a schematic diagram of the internal structure of a software maintenance device for a chemical industrial park, provided as an embodiment of this application. Figure 2 As shown, the device includes: At least one processor; And, a memory that is communicatively connected to at least one processor; The memory stores instructions that can be executed by at least one processor, and the instructions, when executed by at least one processor, enable at least one processor to: In response to an update command, the target new version of the application package is downloaded from a pre-defined distributed file repository to update the old version of the client software for IoT devices, and the currently running old version of the application package is backed up. Monitor the running status of the new version client software so that if the new version client software fails to start, delete the target new version package and roll back the old version package from the backup directory; Monitor the running status of the old version client software task processes after recovery, so as to restart the old version client software in case of abnormal task processes.

[0050] This application also provides a non-volatile computer storage medium storing computer-executable instructions, which, when executed, can: In response to an update command, the target new version of the application package is downloaded from a pre-defined distributed file repository to update the old version of the client software for IoT devices, and the currently running old version of the application package is backed up. Monitor the running status of the new version client software so that if the new version client software fails to start, delete the target new version package and roll back the old version package from the backup directory; Monitor the running status of the old version client software task processes after recovery, so as to restart the old version client software in case of abnormal task processes.

[0051] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and medium embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the method embodiments.

[0052] The devices and media provided in this application are one-to-one with the methods. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0053] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0054] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0055] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0056] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0057] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0058] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0059] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0060] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0061] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A software maintenance method for chemical industrial parks, characterized in that, The method includes: In response to an update command, the target new version of the application package is downloaded from a pre-defined distributed file repository to update the old version of the client software for IoT devices, and the currently running old version of the application package is backed up. Monitor the running status of the new version client software, and if the new version client software fails to start, delete the target new version program package and roll back the old version program package from the backup directory; Monitor the running status of the old version client software task process after recovery, so as to restart the old version client software if the task process is abnormal.

2. The software maintenance method for a chemical industrial park according to claim 1, characterized in that, Before downloading the target new version package from a pre-defined distributed file repository in response to an update command, the method further includes: A digital profile is created for each client software of an IoT device on a centralized management platform, and the basic connection metadata of the client software is entered into the digital profile; The basic connection metadata is format-validated, and after the format validation passes, the basic connection metadata is connected to perform a connectivity test to determine whether remote operation is feasible. Upload the new version of the client software package through the centralized management platform, and perform structural integrity verification and naming convention verification on the new version of the package. After the structural integrity and naming convention checks pass, the new version of the program package is stored in a distributed file repository, and the download path and associated file summary corresponding to the new version of the program package are generated.

3. The software maintenance method for a chemical industrial park according to claim 1, characterized in that, In response to an update command, the system downloads the target new version package from a pre-defined distributed file repository to update the older client software of IoT devices. Specifically, this includes: Based on the update request triggered by the target client software, a structured update instruction is generated, and in response to the update instruction, the target new version program package corresponding to the target client software and the file digest of the target new version program package are asynchronously downloaded from the preset distributed file repository. After the target new version program package is successfully downloaded, the integrity of the target new version program package is checked according to the summary information. If the integrity check fails, the update operation of the old version client software is interrupted and a warning of abnormal integrity of the target new version program package is reported. If the integrity verification of the target new version package passes, a predefined stop script is invoked to terminate the old version client software process and replace the old version package with the target new version package to update the old version client software of the IoT device.

4. The software maintenance method for a chemical industrial park according to claim 1, characterized in that, The method further includes: During the asynchronous download of the target new version program package, for the interrupted download task of the target new version program package, the breakpoint resume mechanism is enabled, and the segmented program packages obtained by the breakpoint resume are merged to obtain the target new version program package. The network quality during the asynchronous download process is monitored, and the download bandwidth threshold of the target new version program package is dynamically adjusted based on the monitored real-time network quality. If the communication duration of the target new version package exceeds a preset communication threshold, a communication retry operation is triggered until the preset maximum retry count threshold is reached.

5. A software maintenance method for a chemical industrial park according to claim 1, characterized in that, Back up the currently running older version of the program package, specifically including: Determine the backup timestamp and version number corresponding to the currently running old version program package, and jointly name the backup directory corresponding to the old version program package based on the backup timestamp and the version number; The backed-up older version of the program package is compressed and stored, and historical backup files are automatically cleaned up according to a preset storage period strategy.

6. A software maintenance method for a chemical industrial park according to claim 1, characterized in that, When monitoring the running status of the new version of the client software, the method further includes: Capture the startup logs of the new version of the client software in real time, and scan the log content to see if it contains preset successful startup keywords; If no process is detected to be alive and no startup keyword is captured within a preset time, the new version of the client software is deemed to have failed to start.

7. A software maintenance method for a chemical industrial park according to claim 1, characterized in that, The method further includes monitoring the running status of the old version client software task process after recovery, so that after restarting the old version client software in the event of an abnormal task process, the method also includes: The central management platform periodically sends heartbeat requests to the daemon to collect corresponding heartbeat data. The heartbeat data includes: client software version number, process running status, latest upgrade information, and abnormal events. The heartbeat data is summarized, and a corresponding visual monitoring report is generated; If the heartbeat data exceeds the constraint conditions, an abnormal alarm is triggered, and the alarm information is pushed to the corresponding management personnel; The constraints are: the number of consecutive abnormal stops of the client software exceeds the preset restart threshold, or the cumulative number of heartbeat response timeouts of the daemon reaches the preset alarm threshold, or the version update failure rate of the client software exceeds the historical baseline deviation value.

8. A software maintenance method for a chemical industrial park according to claim 1, characterized in that, When monitoring the running status of the task processes of the restored old version client software, the method further includes: Periodically check the response status of the client software's listening port; If the hash value of the client software's configuration file is found to be inconsistent with the recorded value on the centralized management platform, the configuration file of the client software will be marked as a configuration tampering event. If the client software fails to maintain operation after repeated restarts, a fault alarm is sent to the centralized management platform.

9. A software maintenance device for chemical industrial parks, characterized in that, The device includes: At least one processor; And, a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform a software maintenance method for a chemical industrial park as described in any one of claims 1-8.

10. A non-volatile computer storage medium storing computer-executable instructions, characterized in that, When the computer-executable instructions are executed, they implement a software maintenance method for a chemical industrial park as described in any one of claims 1-8.

Images