EAP unified management and version rollback system

Abstract

The invention discloses an EAP unified management and version rollback system, which relates to the technical field of industrial Internet of Things, is designed aiming at the problems of equipment diversification, non-unified protocols, high updating risk, rollback mechanism deficiency and the like, and consists of a system initialization and configuration module, an updating management execution module, a version rollback control module and a monitoring maintenance optimization module. The method can dynamically bind equipment and applications, preset update rollback rules, guarantee data security through cloud backup and MD5 verification, support active or passive update, realize update whole process management and control through a standardized instruction packet and a version file, roll back to a stable version according to a range when abnormity occurs, monitor states and logs in real time, set a threshold alarm, and improve the reliability of the system. The method solves the problems of poor compatibility, disordered versions and the like of the equipment, improves the updating efficiency and reliability, reduces the risk of production interruption, achieves the full-life-cycle efficient management of the equipment, and guarantees the production stability and operation and maintenance efficiency of intelligent manufacturing.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of industrial Internet of Things, in particular to an EAP unified management and version rollback system. BACKGROUND

[0002] The traditional decentralized management mode is difficult to cope with the challenges of poor device compatibility, version confusion, data security risks and production interruption, especially after device update failure, a quick rollback mechanism is lacked, and in this background, the EAP unified management and version rollback system emerges as the times require, aiming to realize efficient management of the whole life cycle of the device, improve the production stability and operation efficiency through dynamic binding of the device and the application, standardized update rules, cloud backup and real-time monitoring.

[0003] The traditional EAP unified management and version rollback system has the following technical problems: 1. The traditional EAP unified management and version rollback system lacks a device and application dynamic binding mechanism, and the device type and application program cannot be flexibly associated when entering information, which is not conducive to adapt to the change of production demand, will lead to chaotic management of devices and applications, and will cause difficulties in adapting to new devices or applications, poor system scalability, and lack of detailed processes of preset update and rollback rules, which makes it difficult to set trigger conditions according to the whole factory level, device type level or single machine level, which is not conducive to standardizing the update and rollback process, and will lead to high update risk, and cannot quickly rollback when an exception occurs, affecting the continuity of production.

[0004] 2. The traditional EAP unified management and version rollback system lacks regular backup settings, cloud storage path specification and MD5 check algorithm integrity verification in the data backup strategy initialization process, which is not conducive to ensuring the regularity, reliability and integrity of data backup, and will lead to the fact that backup data cannot be effectively used for system recovery, increasing the risk of data loss.

[0005] 3. When the traditional EAP unified management and version rollback system performs an update, it lacks detailed processes and standardized instruction packages for active and passive updates, which is not conducive to meeting the update needs of different scenarios, and will lead to low update efficiency and inability to timely discover and push new versions.

[0006] 4. In the rollback control process of the traditional EAP unified management and version rollback system, there is a lack of file hash value comparison and multi-dimensional verification process, which is not conducive to ensuring the normal function of the rollback program, and will lead to problems in the system after rollback, and cannot effectively recover, and in terms of monitoring and maintenance, there is a lack of real-time monitoring and threshold alarm mechanism, which is not conducive to timely detection of system abnormalities, and will lead to the fact that when a fault occurs, it cannot be quickly responded and handled, affecting the stable operation of the system. SUMMARY

[0007] The EAP unified management and version rollback system provided by the application solves the problems in the background art.

[0008] To solve the above technical problems, the application adopts the following technical solutions: the application provides an EAP unified management and version rollback system, comprising: a system initialization and configuration module, used for registering devices and applications and dynamically binding types, presetting update and rollback rules, initializing a data backup strategy and specifying a cloud storage path.

[0009] An update management execution module is used for preparing an uploaded update package and editing a version file, executing active or passive update, issuing an instruction, checking a state and reporting an update result to a server.

[0010] A version rollback control module is used for rolling back a stable version according to a range when an exception or manual triggering occurs, downloading a replacement program and verifying, and recording a state and a reason.

[0011] A monitoring and maintenance optimization module is used for monitoring a state and a log in real time and setting a threshold alarm, verifying backup recoverability and adapting to new devices.

[0012] The application has the following beneficial effects: 1. The EAP unified management and version rollback system provided by the application is beneficial to realizing associated management of devices and applications, supporting subsequent dynamic adjustment of a binding relationship according to production needs, improving system adaptability and flexibility, through registering devices and applications and dynamically binding types in the system initialization and configuration process, inputting information such as unique identification of each manufacturer's device and communication protocol parameters, uploading a customized configuration file, dynamically mapping device types and application programs, and through presetting update and rollback rules, selecting a range dimension and setting a triggering condition, defining an automatic detection time interval, specifying a backup version retention strategy, and generating a standardized configuration file.

[0013] 2. In the update management execution process of the application, the application is beneficial to ensuring the standardization, traceability and integrity of version information of an update package, facilitating management and verification of an update process, through preparing an uploaded update package and editing a version file, compressing a to-be-updated file into a standard tar.gz format package, pushing the package to an FTP remote path according to a standard path, editing a JSON format version file containing core fields and establishing an index association.

[0014] 3、The embodiment of the present application in the version rollback control process, by downloading the replacement program and verifying, the device receives the instruction, downloads the update package and calculates the hash value comparison, completes the replacement, and executes the basic verification and business logic verification, which is beneficial to ensure the integrity of the update package and the normal function of the replaced program, and timely discovers and handles problems in the rollback process, and guarantees the system stability;Record the state and reason, which is beneficial to provide data support for subsequent operation and maintenance, and is convenient for tracing the rollback situation.

[0015] 4、The embodiment of the present application in the monitoring and maintenance optimization process, by monitoring the state and log in real time and setting threshold alarm, collecting server resource information and program running log regularly, comparing with the preset threshold and sending alarm notification, which is beneficial to timely discover system abnormalities, quickly respond and handle problems, reduce the influence of failure, and guarantee the continuous and stable operation of the system;By verifying the backup recoverability, simulating deleting files and downloading from the cloud to recover, generating a report for storage, which is beneficial to ensure the availability of backup data, and can quickly recover when the system has problems, reducing the risk of data loss;When a new device is added, the information is input, the application is bound, the configuration file is uploaded and the communication and compatibility are verified, which is beneficial to realize the rapid integration and unified management of the new device, expand the system management range, and improve the scalability of the system.

[0016] 5、The embodiment of the present application in the data backup strategy initialization process, by setting the periodic backup trigger mode, specifying the cloud storage path and associating the device type and the storage path, enabling the MD5 check algorithm to verify the backup file integrity, which is beneficial to guarantee the regularity, reliability and integrity of data backup, ensure that the backup data can be effectively used for system recovery, and enhance the system data security. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiment or prior art description, and obviously, 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 without creative labor on the basis of these drawings.

[0018] Figure 1 It is a schematic diagram of the system structure of the present application.

[0019] Figure 2 It is a schematic diagram of the principle framework of the present application. DETAILED DESCRIPTION

[0020] With reference to the drawings of the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described, obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0021] Please refer to Figure 1 As shown in the drawings, the present application provides an EAP unified management and version rollback system, which comprises a system initialization and configuration module, an update management execution module, a version rollback control module, a monitoring and maintenance optimization module

[0022] The system initialization and configuration module is used for registering devices and applications and dynamically binding types, presetting update and rollback rules, initializing a data backup strategy and specifying a cloud storage path.

[0023] In a specific embodiment, the registering devices and applications and dynamically binding types have the following specific process: in the device management module of the front-end interface, an operator enters the unique identification, communication protocol parameters and device type of each manufacturer's device, the unique identification includes a device ID and a model, and uploads a customized configuration file, simultaneously, in the application management module, the operator registers EAP related program information, including a development language, a technical architecture, a service address and a program version number, through the device type management module, the registered device type is dynamically mapped with the application program, a new version of the general part of the program is uploaded, the association and binding of the device type and the application are realized, and the binding relationship can be dynamically adjusted according to production requirements, and the service address and the configuration file corresponding to the device are synchronously updated.

[0024] It should be noted that the device management module and the application management module both belong to the system initialization and configuration module, here, the "EAP" is a short name for enterprise application program, which refers to a business system or a software program developed or used in an enterprise, and involves management requirements in the dimensions of development language, technical architecture and version management.

[0025] In a specific embodiment, the preset update and rollback rules have the following specific process: in the version management module of the front-end interface, an operator first selects the dimension of the role range of the update rule, and sets the corresponding update trigger condition for different dimensions, the trigger condition includes manual triggering and automatic detection based on a time period, simultaneously, the time interval of automatically detecting a new version is defined, for the rollback rule, the trigger condition is preset, and the retention strategy of the backup version is specified, then the backup version mapping relationship corresponding to each application program is associated, finally, the update and rollback rules are generated into a standardized configuration file, and the configuration file is synchronously transmitted to the business logic layer for rule checking.

[0026] It should be noted that the version management module also belongs to the system initialization and configuration module, the scope of the role dimension refers to, such as the whole factory level, equipment type level or single machine level, the set trigger condition such as continuous 3 times of update failure, program abnormal crash or manual triggering, the retention strategy refers to, such as forced retention of the latest 3 historical versions, each application program includes development language, technical architecture, service address and program version number and other information.

[0027] In a specific embodiment, the initialization data backup strategy is specified and the cloud storage path is specified, and the specific process is as follows: the operator sets the backup trigger mode to periodic backup in the backup strategy configuration interface through the front-end interface, configures the backup period parameter to a specified time point every day, then specifies the storage location in the cloud storage path input box, associates the mapping relationship between the device type and the storage path, then enables the backup file integrity verification mechanism, selects the MD5 check algorithm, generates a 32-bit check code through a hash function, configures the check rule to automatically compare the check values of the source file and the cloud file after the backup is completed, and finally generates a JSON format configuration file for the above strategy parameters, which is stored in the database after being verified by the business logic layer, and is synchronized to the backup program module to perform initialization.

[0028] It should be noted that the storage format of the storage location specified in the cloud storage path input box is protocol: / / bucket name / device type / version number, the MD5 check algorithm is an encryption algorithm that converts data of any length into a 32-bit fixed-length hash value, which is used to verify whether the backup file is complete and has not been tampered with during transmission or storage, and the JSON format is a lightweight data exchange format that uses key-value pair structure to store and represent configuration information in text form.

[0029] The update management execution module is used to prepare to upload the update package and edit the version file, and to perform active or passive update, issue instructions, check the status and report the update result to the server.

[0030] In a specific embodiment, the preparation of the update package and the editing of the version file are as follows: in the update package preparation link, the developer copies the files or folders to be updated to a separate working directory, right-clicks the PowerShell command window by holding down the Shift key, executes the packaging instruction, and compresses the target file into a standard tar.gz format package through the packaging instruction.

[0031] After the packaging is completed, the compressed package is pushed to the FTP remote path of the Server end through the file upload module of the EAPAdmin front-end interface;

[0032] When editing a version file, the operator opens the configuration interface through the front-end version management module and creates a version description file corresponding to the update package. The file uses the JSON format specification. After editing is completed, the version file and the update package are indexed and associated on the server side. After the version compatibility is verified by the business logic layer, it is stored in the version management database.

[0033] It should be noted that the packaging instruction is tar-cvzf [custom upgrade package name].tar.gz [file 1] [file 2] to [file n], where -c means creating a new archive, -v shows the processing process, -z enables gzip compression, and -f specifies the archive file name. The path format follows ftp: / / [server IP] / [system type] / [version number], such as ftp: / / 192.168.1.100 / prober / v2.3.5. The version management module belongs to the update management execution module. After the file adopts the JSON format specification, the core fields included are

[0034] {"versionNum":"2.3.5","updateDesc":"Fix data collection exception","targetDevices":["prober-typeA","tester-007"],"dependences":

[0035] ["lib-v1.2.3.dll"],"updateTime":"2025-06-2022:00:00"}, where the targetDevices field specifies the device type or single machine identifier, dependencies defines the program dependency components, and updateTime specifies the planned update time point.

[0036] In a specific embodiment, the execution of active or passive updates is as follows: in the active update scenario, the operator first uploads the update program package to the remote path of the server through the front-end interface. Different system types correspond to independent storage paths. Then, the operator edits the version file in the version management module and defines the core parameters in JSON format, including the version number, target system, and the update range specified by the entire factory, equipment type or single machine dimension. After selecting the target machine and system, the server sends update instructions in batches through the message queue. The instructions include the system type, version path and machine status check conditions. After the target device receives the instruction, it first checks the machine status. If it meets the conditions, it stops the current EAP program, downloads the update package from the specified path and replaces the file. After restarting the program, it reports the status information of the successful update to the server, including the version number and timestamp.

[0037] The device end program sends a version query request to the server through the TCP protocol when starting. The server queries the latest version number from the version management database after receiving the request. If a new version is detected, the device end triggers a passive update process, and an interactive window is popped up to prompt the operation and maintenance personnel whether to upgrade immediately. After the operation and maintenance personnel confirms, the program downloads the update package from the server specified path, performs replacement operation and restarts. After the update is completed, the device end reports the update result to the server, and the server synchronizes the record to the update history module, and generates a log file containing the timestamp, version number and device state.

[0038] It should be noted that the TCP protocol is a connection-oriented, reliable transport layer communication protocol that ensures the orderly and complete transmission of data in the network through data segmentation, acknowledgment and retransmission mechanisms. The update history module belongs to the update management execution module,

[0039] In a specific embodiment, the issued instructions, status checking and update result reporting to the server are as follows: After the operation personnel selects the update range on the front-end interface, the Server generates a standardized instruction package through the message queue. After the device receives the instruction, it first calls the local script to check the state of the machine. The specified instruction is executed to check the EAP program running state. If the return process ID is "running", it is determined that the update condition is not met. The idle time of the device is calculated through the uptime command. If idleTime < 15min, the update is skipped. When the condition is met, the device stops the current program, downloads the update package from versionPath and decompresses the replacement file. After restarting, a temporary log file is generated. The device reports the result through HTTP POST request.

[0040] The Server receives and parses the message. If the status is "success", the "update history" module is updated, and the version change time and device state are recorded. If it is "failed", an alarm is triggered, and the errorMsg field is associated.

[0041] The program sends a GET request to the Server when starting. The Server queries the database and returns a response. If forceUpdate is true, the user confirmation is skipped, and the update is triggered directly. The device checks the local disk space. If the space is insufficient, the "insufficientstorage" error is reported. When the condition is met, a dialog box "New version 2.3.5 detected, do you want to update immediately?" is popped up. After the user confirms, the update process is executed. After the Server receives the WebSocket message, the device state board is refreshed in real time in the server monitoring module, and the duration and success state are written into the database.

[0042] It should be noted that the specified instruction is ps-ef|grep eap-process, the temporary log file format is / / tmp / eap_update.log, and the Server generates a standardized instruction package through a message queue, and the format is:

[0043]

[0044] The device reports the result through an HTTP POST request, and the message content is:

[0045] {

[0046] "deviceID": "tester-007",

[0047] "versionAfter": "2.3.5",

[0048] "status": "success",

[0049] "errorMsg": null,

[0050] "updateTime": "2025-06-20T16:30:45",

[0051] "logPath": "ftp: / / 192.168.1.100 / logs / tester-007_20250620.log"

[0052] }.

[0053] The version rollback control module is used to rollback to a stable version by range when an exception or manual trigger occurs, download and replace the program, and record the status and reason.

[0054] In a specific embodiment, the process of downloading and replacing the program, and recording the status and reason is as follows: after receiving the update instruction issued by the server, the device downloads the update package from the specified path to the local temporary directory through the FTP protocol, synchronously calculates the file hash value and compares it with the pre-stored verification value of the server, and after verification, calls the system command to stop the current EAP program, decompresses the update package to the program installation directory to overwrite the original file, and moves the old version program to the backup directory.

[0055] After the replacement is completed, the program is restarted, and basic verifications such as local heartbeat packet sending, service interface response state detection, and key process running log reading are automatically performed. Further business logic verifications such as mechanical motion precision or test data comparison are performed according to the type of the probe or test equipment. After the verification is passed, state information including the version number, update time, and verification details is reported to the server. The server writes this record to the "update history" database. If the verification fails, the specific error reason is marked and an alarm process is triggered.

[0056] It should be noted that FTP is an application layer protocol for implementing file transfer between a client and a server in a network, supporting file upload and download operations.

[0057] The monitoring and maintenance optimization module is used to monitor the state and log in real time and set threshold alarms, verify backup recoverability, and adapt to new devices.

[0058] In a specific embodiment, the real-time monitoring of the state and log and the setting of the threshold alarm are as follows: the server CPU, memory, disk, and other resource information and EAP program running logs are collected by the front-end server monitoring module at regular intervals. The collected data is compared with the preset threshold. When the data exceeds the threshold, an alarm notification is sent through SMS, email, or enterprise WeChat according to the level, and the abnormal state is displayed in a visual manner on the front-end interface. The alarm information is recorded in the database simultaneously, including the triggering time, device ID, abnormal parameters, and processing status.

[0059] It should be noted that the server monitoring module belongs to the monitoring and maintenance optimization module, and the preset threshold refers to, for example, 80% CPU usage as a warning and 95% as a serious warning.

[0060] In a specific embodiment, the verification of backup recoverability and the adaptation to new devices are as follows: the local EAP program file is simulated to be deleted, the corresponding version compressed package is downloaded from the cloud backup path and decompressed to the original directory, and after the program is restarted, it is verified whether the data collection and communication interface function are normal. A report containing the recovery time consumption and verification result is generated and stored in the database. When adapting to new devices, the device ID and communication protocol information are entered in the front-end device management module. The corresponding application program is bound through device type management, and the customized configuration file is uploaded. After generating the device mapping relationship table, a test instruction is sent to verify the communication connectivity and program compatibility. The device status that passes the verification is marked as online and included in the unified management.

[0061] A database is used to store the configuration file in JSON format, also store the version file and the update package, also store the latest version number corresponding to the version file, also store the duration and success status, also store the state information containing the version number, update time and verification details, also store the alarm information sent when the data exceeds the threshold, also store the report containing the recovery time consumption and verification result.

[0062] The above merely illustrates and describes the concept of the present application. Those skilled in the art can make various modifications or supplements to the described specific embodiments or replace them with similar ways without departing from the concept of the present application or exceeding the scope defined in the specification.

Claims

1. An EAP unified management and version rollback system, characterized by: include: System initialization and configuration module, used to register devices and applications and dynamically bind types, preset update and rollback rules, initialize data backup strategies and specify cloud storage paths; The update management execution module is used to prepare and upload update packages and edit version files, perform active or passive updates, issue instructions, check status, and report update results to the server; The version rollback control module is used to select a stable version to roll back based on a range when an exception or manual trigger occurs, download and verify the replacement program, and record the status and reason; The monitoring, maintenance and optimization module is used to monitor status and logs in real time and set threshold alarms to verify backup recoverability and adapt to new devices.

2. The EAP unified management and version rollback system according to claim 1, characterized in that: The specific process of registering devices and applications and dynamically binding types is as follows: In the device management module of the front-end interface, the operator enters the unique identifier, communication protocol parameters and device type of each manufacturer's equipment. The unique identifier includes the device ID and model, and uploads a customized configuration file. At the same time, the EAP-related program information is registered in the application management module, including the development language, technical architecture, service address and program version number. Through the device type management module, the registered device type is dynamically mapped to the application program, and the new version of the general part of the program is uploaded to realize the association and binding of the device type and the application. It also supports the subsequent dynamic adjustment of the binding relationship according to production needs, and the synchronous update of the service address and configuration file corresponding to the device.

3. The EAP unified management and version rollback system according to claim 2, characterized in that: The specific process of the preset update and rollback rules is as follows: In the version management module of the front-end interface, the operator first selects the scope dimension of the update rule and sets corresponding update trigger conditions for different dimensions. The trigger conditions include manual triggering and automatic detection based on time periods. At the same time, the time interval for automatic detection of new versions is defined. For rollback rules, the trigger conditions are set in advance and the retention policy of the backup version is specified. Then, the corresponding backup version mapping relationship is associated with each application. Finally, a standardized configuration file is generated for the update and rollback rules and synchronized to the business logic layer for rule verification.

4. The EAP unified management and version rollback system according to claim 3, characterized in that: The specific process of initializing the data backup strategy and specifying the cloud storage path is as follows: The operator first sets the backup trigger mode to regular backup in the backup strategy configuration interface through the front-end interface, configures the backup cycle parameters to a specified time point every day, then specifies the storage location in the cloud storage path input box, and associates the mapping relationship between the device type and the storage path. Then, the backup file integrity verification mechanism is enabled, the MD5 checksum algorithm is selected, and a 32-bit checksum is generated through a hash function. The checksum rule is configured to automatically compare the checksum values ​​of the source file and the cloud file after the backup is completed. Finally, the above policy parameters are generated into a JSON format configuration file, which is stored in the database after verification by the business logic layer and synchronized to the backup program module for initialization.

5. The EAP unified management and version rollback system according to claim 4, characterized in that: The specific process of preparing and uploading the update package and editing the version file is as follows: During the update package preparation phase, developers copy the files or folders to be updated to an independent working directory, hold down the Shift key and right-click in the directory to bring up the PowerShell command window, execute the packaging instructions, and compress the target files into a standard tar.gz format package through the packaging instructions. After the package is completed, push the compressed package to the FTP remote path on the server through the file upload module of the EAPAdmin front-end interface; When editing a version file, the operator opens the configuration interface through the front-end version management module and creates a version description file corresponding to the update package. The file uses the JSON format specification. After editing is completed, the version file and the update package are indexed and associated on the server side. After the version compatibility is verified by the business logic layer, it is stored in the version management database.

6. The EAP unified management and version rollback system according to claim 5, characterized in that: The specific process of performing active or passive update is as follows: In the active update scenario, the operator first uploads the update package to the server's remote path through the front-end interface. Different system types correspond to independent storage paths. The operator then edits the version file in the version management module, defining core parameters in JSON format. These parameters include the version number, target system, and the update scope specified by the entire plant, device type, or single machine. After selecting the target machine and system, the server sends batch update instructions through the message queue. The instructions include the system type, version path, and machine status check conditions. After receiving the instructions, the target device first verifies the machine status. If the conditions are met, it stops the current EAP program, downloads the update package from the specified path, and replaces the file. After restarting the program, it reports the successful update status information, including the version number and timestamp, to the server. When the device program starts, it sends a version query request to the server via the TCP protocol. After receiving the request, the server queries the latest version number from the version management database. If a new version is detected, the device triggers a passive update process and pops up an interactive window to prompt the operation and maintenance personnel whether to upgrade immediately. After the operation and maintenance personnel confirm, the program downloads the update package from the specified path on the server, performs the replacement operation and restarts. After the update is completed, the device reports the update results to the server. The server synchronizes the record to the update history module and generates a log file containing timestamp, version number and device status.

7. The EAP unified management and version rollback system according to claim 6, characterized in that: The specific process of issuing instructions, checking status and reporting update results to the server is as follows: After the operator selects the update range on the front-end interface, the server generates a standardized instruction package through the message queue. After receiving the instruction, the device first calls the local script to verify the machine status and executes the specified instruction to check the EAP program running status. If the process ID is returned, it is judged as "running" and does not meet the update conditions. The device idle time is calculated using the uptime command. If idleTime is less than 15 minutes, the update is skipped. If the conditions are met, the device stops the current program, downloads the update package from the versionPath, decompresses and replaces the file, and generates a temporary log file after restarting. The device reports the results through an HTTP POST request. After receiving the message, the server parses it. If the status is "success," it updates the "Update History" module, recording the version change time and device status. If the status is "failed," it triggers an alarm and associates it with the errorMsg field. When the program starts, it sends a GET request to the server. The server queries the database and returns a response. If forceUpdate is true, user confirmation is skipped and the update is triggered directly. The device checks the local disk space. If insufficient space is available, an "insufficientstorage" error is reported. If the conditions are met, a dialog box pops up asking "New version 2.3.5 detected, do you want to update now?" The user confirms the update and the update process is executed. After the server receives the WebSocket message, the server monitoring module refreshes the device status dashboard in real time and writes the duration and success status to the database.

8. The EAP unified management and version rollback system according to claim 7, characterized in that: The specific process of downloading the replacement program and verifying it, recording the status and reason, is as follows: After receiving the update command from the server, the device downloads the update package from the specified path to a local temporary directory using the FTP protocol. It then calculates the file hash value and compares it with the checksum pre-stored on the server. If the hash value passes, it calls a system command to stop the current EAP program. It then decompresses the update package to the program installation directory, overwriting the original file. It also moves the old version of the program to a backup directory. After the replacement is completed, the program is restarted to automatically perform basic verifications such as sending local heartbeat packets, detecting the response status of the service interface, and reading the key process operation logs. Business logic verifications such as mechanical motion accuracy or test data comparison are further performed based on the probe or test device type. After the verification is passed, status information including the version number, update time, and verification details is reported to the server. The server writes the record into the "Update History" database. If the verification fails, the specific error cause is marked and the alarm process is triggered.

9. The EAP unified management and version rollback system according to claim 8, characterized in that: The real-time monitoring status and logs and setting threshold alarms are as follows: The front-end server monitoring module regularly collects server CPU, memory, disk and other resource information and EAP program operation logs, and compares the collected data with the preset threshold. When the data exceeds the threshold, an alarm notification is sent by SMS, email or enterprise WeChat according to the level. At the same time, the abnormal status is displayed visually on the front-end interface. The alarm information is synchronously recorded in the database, including the trigger time, device ID, abnormal parameters and processing status.

10. The EAP unified management and version rollback system according to claim 9, characterized in that: The specific process of verifying the restoreability of the backup and adapting to the newly added devices is as follows: By simulating the deletion of local EAP program files, downloading the corresponding version compressed package from the cloud backup path and decompressing it to the original directory, restarting the program to verify whether the data collection and communication interface functions are normal, generating a report including the recovery time and verification results and storing it in the database, when adapting to new devices, entering the device ID and communication protocol information in the front-end device management module, binding the corresponding application through device type management and uploading a customized configuration file, generating a device mapping relationship table and sending a test command to verify communication connectivity and program compatibility, marking the status of the device that has passed the verification as online and incorporating it into unified management.

Images