A vehicle-mounted safety platform with a 2x2 architecture and its automatic update method

Abstract

This invention discloses a two-out-of-two architecture vehicle safety platform and its automatic update method. The vehicle safety platform includes a primary MPU1 logic processing board, a primary MPU2 logic processing board, a backup MPU1 logic processing board, a backup MPU2 logic processing board, and an MCU communication board. The automatic update method includes a two-out-of-two comparison of the file to be updated, an automatic update process for the logic processing board and the communication board, and a version rollback process. This invention uses dual USB drives to update the system's configuration file and image file, and reads the updated version from the USB drives for confirmation, ensuring the security and correctness of the updated files.

Description

Technical Field

[0001] This invention relates to the field of rail transit technology, specifically to an onboard safety platform with a two-out-of-two architecture and its automatic update method. Background Technology

[0002] In rail transit train control systems, ATP (Automotic Train Protection) and ATO (Automatic Train Operation) systems operate on an onboard safety platform, which places high demands on maintainability, safety, and reliability. Generally, upgrading or updating the configuration of the onboard safety platform requires manual upgrades of each device individually.

[0003] Unlike trackside safety platforms, vehicle-mounted safety platforms cannot be universally updated remotely via the network, and it is inconvenient to carry external devices such as computers. Users can only statically update the configuration and images of each board using portable computers, which is cumbersome, time-consuming and labor-intensive. Summary of the Invention

[0004] To address or partially address the problems existing in related technologies, this invention provides a vehicle-mounted safety platform with a two-out-of-two architecture and its automatic update method. The system's configuration file and image file are updated via dual USB drives, and the updated version is read from the USB drives for confirmation, ensuring the security and correctness of the update files.

[0005] The present invention also provides an in-vehicle safety platform based on a two-out-of-two architecture, the in-vehicle safety platform comprising: a primary system, a backup system, a communication board, and a storage medium; the primary system and the backup system each include at least two logic processing boards, the logic processing boards and the communication boards communicate with each other via a bus, and the logic processing boards and / or the communication boards serve as boards to be updated; the storage medium is used to store files to be updated.

[0006] Optionally, the vehicle-mounted safety platform further includes:

[0007] The files to be updated include the storage configuration update mode verification word, configuration files and image files of all boards to be updated, and the corresponding encrypted MD5 code values.

[0008] On the other hand, the present invention also provides an automatic update method for the above-mentioned vehicle safety platform, characterized in that the main system includes main system MPU1 and main system MPU2, the backup system includes backup system MPU1 and backup system MPU2, the communication board includes MCU; the board to be updated includes at least one of main system MPU1, main system MPU2, backup system MPU1, backup system MPU2, and MCU, and the automatic update method includes: online update processing of all boards to be updated.

[0009] Optionally, prior to the online update processing of all the boards to be updated, the following is also included:

[0010] The process of performing a two-out-of-two comparison on the file to be updated.

[0011] Optionally, the two-to-two comparison process of the file to be updated specifically includes:

[0012] If the configuration update mode verification word reads as online update mode, then the online update process begins, reading the configuration files and image files of all cards to be updated in the storage medium, as well as the corresponding encrypted MD5 code values.

[0013] The primary MPU1 sends an online update request message to the primary MPU2. The online update request message contains the encrypted MD5 code values ​​of all configuration files and image files in the storage medium.

[0014] After receiving the online update request message from the main MPU1, the main MPU2 stores the MD5 hash values ​​of all configuration files and image files in the online update request message, performs a consistency comparison between the encrypted MD5 hash value in its own storage medium and the encrypted MD5 hash value in the online update request message, and sends the consistency comparison result and the local encrypted MD5 hash value to the main MPU1 through an online update request confirmation message.

[0015] After receiving the online update request confirmation message from the main MPU2, the main MPU1 compares the encrypted MD5 code value in the local storage medium with the encrypted MD5 code value in the online update request confirmation message, and compares the obtained consistency comparison result with the consistency comparison result in the online update request confirmation message.

[0016] If the two consistency comparison results are consistent, then send an online update mode entry message to all boards to be updated.

[0017] Optionally, if the two consistency comparison results are inconsistent, exit the online update mode and display "Update Failed" on the front panel of the board.

[0018] Optionally, before reading the configuration update mode verification word to online update mode, the method further includes:

[0019] Insert storage media into primary MPU1 and primary MPU2; after detecting the insertion of storage media, primary MPU1 and primary MPU2 read the configuration update mode verification word and set it to online update mode.

[0020] Optionally, the online update process for all boards to be updated specifically includes:

[0021] S101. After receiving the online update mode entry message, the board to be updated encrypts the old configuration file and image file in its local storage. After completion, it replies with an online update mode confirmation message to the main MPU1. The online update mode confirmation message contains the local board identifier.

[0022] S102. After receiving the online update mode confirmation message from the board to be updated, the main MPU1 reads the local board identifier in the online update mode confirmation message, unpacks and sorts the configuration file and image file corresponding to the board identifier in the storage medium, and calculates the encrypted MD5 code value of each file package. After completion, the main MPU1 sends a file distribution start message to the board to be updated. The file distribution start message includes the file name, the corresponding encrypted MD5 code value, and the number of files after unpacking.

[0023] S103. After receiving the file distribution start message, the card to be updated stores the file name, the corresponding encrypted MD5 code value and the number of files after unpacking in the file distribution start message.

[0024] S104. The main MPU1 sends a file distribution message to the board to be updated. The file distribution message contains the configuration file and image file corresponding to the board identifier. The file package with the unpacking number of the image file is odd and the corresponding encrypted MD5 code value. The main MPU2 sends a file distribution message to the board to be updated. The file distribution message contains the configuration file and image file corresponding to the board identifier. The file package with the unpacking number of the image file is even and the corresponding encrypted MD5 code value.

[0025] S105. After receiving the file distribution message, the board to be updated calculates the encrypted MD5 code value for each file package and compares it with the encrypted MD5 code value in the message. If the calculated encrypted MD5 code value matches the encrypted MD5 code value in the message, the file package is stored. If the calculated encrypted MD5 code value does not match the encrypted MD5 code value in the message, the file package is discarded.

[0026] S106. After receiving the file packets, each board to be updated will group the received file packets according to their numbers, calculate the encrypted MD5 value, compare it with the encrypted MD5 code value received in the file distribution start message, and reply to the main MPU1 with the comparison result and the encrypted MD5 code value through the file reception confirmation message.

[0027] S107. After receiving the file reception confirmation message from the board to be updated, the main MPU1 compares the consistency with the encrypted MD5 code value in the storage medium. If the two comparison results are consistent, a file overwrite start message is sent to all boards to be updated, and the local image file and configuration file are overwritten in the local Flash. If the two comparison results are inconsistent, step S102 is repeated.

[0028] Optionally, the overlay of the ontology image file and configuration file specifically includes:

[0029] After the update board receives the file overwrite start message, it begins storing the configuration file and image file in the Flash memory;

[0030] After successful overwrite, the board to be updated sends a file overwrite completion message to the main MPU1 and / or main MPU2. The file overwrite completion message contains the local board identifier, the stored configuration file and the MD5 code value of the image file, as well as the encrypted MD5 code value.

[0031] After receiving the file overwrite completion message, the primary MPU1 and / or primary MPU2 store the MD5 code value in the file overwrite completion message in the storage medium; compare the encrypted MD5 code value corresponding to the board identifier with the encrypted MD5 code value stored in the storage medium, and send the comparison result to each board to be updated through the file overwrite completion confirmation message;

[0032] Once the updated board receives the confirmation message that the file overwrite is complete, it will display the update result. If the results are consistent, it will display "Update Completed"; if the results are inconsistent, it will display "Update Failed" on the front panel of the board.

[0033] After the storage medium is removed, the MD5 hash of each card to be updated in the storage medium is read for reconfirmation and compared with the MD5 hash in the release form. If they match, the configuration update mode check word in the storage medium is changed to normal operation mode, the storage medium is inserted and the system is restarted. If they do not match, the update mode check word in the storage medium is changed to rollback mode, rolling back to the previous version, or the file correctness is reconfirmed and updated again.

[0034] Optionally, after sending the online update mode entry message, the primary MPU1 and the primary MPU2 encrypt the old configuration files and image files in the local Flash, so as to prevent system update errors or user rollback to the previous version.

[0035] Optionally, after the online update processing of all the boards to be updated, the process further includes:

[0036] Version rollback process.

[0037] Optionally, the version rollback process specifically includes:

[0038] If the update fails or the user wants to revert to the previous version, change the storage medium configuration update mode check word to rollback mode, reinsert the modified storage medium into the main system MPU1 and the main system MPU2, and enter rollback mode;

[0039] After detecting the insertion of the storage medium, the main MPU1 and the main MPU2 read the configuration update mode verification word in the storage medium and set it to rollback mode, and send a rollback mode start message to the board to be updated;

[0040] After the updated board receives the rollback mode start message, it decrypts the encrypted file in the local Flash. After completion, it sends a rollback file completion message to the main MPU1 and the main MPU2. The rollback file completion message contains the board identifier and local file version information.

[0041] After receiving the rollback completion messages from all the boards to be updated, the main MPU1 and the main MPU2 read the board identifier and version information in the rollback completion message and compare them with the version information corresponding to the local board identifier. If they match, they send a rollback file completion confirmation message to the corresponding board. If they do not match, they display rollback failure on the front panel of the board.

[0042] The front panel displays a message indicating successful rollback. Remove the storage medium, change the configuration from online update mode to normal operation mode, restart the system, and the rollback operation is complete.

[0043] The technical solution provided by this invention may include the following beneficial effects:

[0044] 1. This invention is based on a vehicle safety platform with a two-out-of-two architecture. All files must undergo a two-out-of-two consistency comparison before proceeding to the next step, thus ensuring the validity of the files and the security of the system.

[0045] 2. This invention solves the problem of cumbersome manual updates of single boards in current vehicle systems by forwarding configuration files and image files of the boards to be updated via a bus, and overcomes the technical difficulty that vehicle systems cannot be universally updated with computers and networks.

[0046] 3. This invention also provides a version rollback function, which allows users to revert to the previous version simply by modifying the configuration, saving manpower and resources and reducing on-site maintenance costs.

[0047] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention. Attached Figure Description

[0048] To more clearly illustrate the technical solutions of the embodiments of this invention, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this invention. For those skilled in the art, the drawings can be obtained from these drawings without creative effort.

[0049] Figure 1 This is a schematic diagram of the structure of the vehicle-mounted safety platform in an embodiment of the present invention;

[0050] Figure 2 This is a flowchart of the automatic update method in an embodiment of the present invention. Detailed Implementation

[0051] Embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that the invention will be more thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0052] The terminology used in this invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular forms “a,” “the,” and “the” used in this invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0053] It should be understood that although the terms "first," "second," "third," etc., may be used in this invention to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this invention, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Thus, features defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0054] The technical solutions of the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0055] The automatic update method in this embodiment of the invention is implemented based on a vehicle safety platform with a two-out-of-two architecture. All files must undergo a two-out-of-two consistency comparison before proceeding to the next step, thus ensuring the validity of the files and the security of the system.

[0056] Please see Figure 1 The vehicle-mounted safety platform generally includes: main MPU (main processing unit) 1 logic processing board, main MPU 2 logic processing board, backup MPU 1 logic processing board, backup MPU 2 logic processing board, and MCU (main communication unit) communication board. The boards communicate with each other through a bus.

[0057] Specifically, the A series and the B series are the same, one main and one backup, each consisting of two MPU logic processing boards; the main MPU2 logic processing board and the backup MPU1 logic processing board run the same functional software to realize the logic operation function; the MCU consists of two communication boards, which realize the communication function between the platform's MPU boards and different external devices.

[0058] Please see Figure 2 The automatic update method in this embodiment generally includes: a two-to-two comparison process of the file to be updated, online update processing of all boards to be updated, and a version rollback process.

[0059] The boards to be updated include the main MPU1 logic processing board, the main MPU2 logic processing board, the backup MPU1 logic processing board, the backup MPU2 logic processing board, and the MCU communication board.

[0060] In this embodiment, the two-to-two comparison process of the file to be updated specifically includes:

[0061] Insert a USB flash drive into the main MPU1 logic processing board and the main MPU2 logic processing board. The USB flash drive is used to store the configuration update mode verification word, the configuration files and image files of all boards to be updated, and the corresponding encrypted MD5 code values.

[0062] After detecting the insertion of a USB flash drive, the main MPU1 logic processing board and the main MPU2 logic processing board read the configuration update mode verification word and find that it is in online update mode. Then, they enter the online update process and read the configuration files and image files of all the boards to be updated on the USB flash drive, as well as the corresponding encrypted MD5 code values.

[0063] The main MPU1 logic processing board sends an online update request message to the main MPU2 logic processing board. The online update request message contains the encrypted MD5 code values ​​of all configuration files and image files in the USB flash drive.

[0064] After receiving the online update request message sent by the main MPU1, the main MPU2 logic processing board stores the MD5 codes of all configuration files and image files in the online update request message, compares the encrypted MD5 codes in the local USB flash drive with the encrypted MD5 codes in the online update request message, and sends the consistency comparison result and the local encrypted MD5 codes to the main MPU1 logic processing board through the online update request confirmation message.

[0065] After receiving the online update request confirmation message from the main MPU2 logic processing board, the main MPU1 logic processing board compares the encrypted MD5 code value in the local USB flash drive with the encrypted MD5 code value in the online update request confirmation message, and compares the obtained consistency comparison result with the consistency comparison result in the online update request confirmation message.

[0066] If the two consistency comparison results are consistent, an online update mode entry message is sent to all boards to be updated; if the two consistency comparison results are inconsistent, the online update mode is exited and an update failure is displayed on the front panel of the board.

[0067] In this embodiment, the online update process for all boards to be updated specifically includes:

[0068] S101. After receiving the online update mode entry message sent by the main MPU1 logic processing board, the board to be updated encrypts the old configuration file and image file in the local Flash. After completion, it replies with an online update mode confirmation message to the main MPU1 logic processing board. The online update mode confirmation message contains the local board identifier.

[0069] S102. After receiving the online update mode confirmation message from the board to be updated, the main MPU1 logic processing board reads the local board identifier in the online update mode confirmation message, unpacks and sorts the configuration file and image file corresponding to the board identifier in the USB flash drive, and calculates the encrypted MD5 code value of each file package. After completion, the main MPU1 logic processing board sends a file distribution start message to the board to be updated. The file distribution start message includes the file name, the corresponding encrypted MD5 code value, and the number of files after unpacking.

[0070] S103. After receiving the file distribution start message, the card to be updated stores the file name, the corresponding encrypted MD5 code value and the number of files after unpacking in the file distribution start message.

[0071] S104. The main MPU1 logic processing board sends a file distribution message to the board to be updated. The file distribution message contains the configuration file and image file corresponding to the board identifier. The file package with the unpacking number of the image file is odd and the corresponding encrypted MD5 code value. The main MPU2 logic processing board sends a file distribution message to the board to be updated. The file distribution message contains the configuration file and image file corresponding to the board identifier. The file package with the unpacking number of the image file is even and the corresponding encrypted MD5 code value.

[0072] S105. After receiving the file distribution message, the board to be updated calculates the encrypted MD5 code value for each file package and compares it with the encrypted MD5 code value in the message. If the calculated encrypted MD5 code value matches the encrypted MD5 code value in the message, the file package is stored. If the calculated encrypted MD5 code value does not match the encrypted MD5 code value in the message, the file package is discarded.

[0073] S106. After receiving the file packets, each board to be updated will group the received file packets according to their numbers, calculate the encrypted MD5 value, compare it with the encrypted MD5 code value received in the file distribution start message, and reply to the main MPU1 logic processing board with the comparison result and the encrypted MD5 code value through the file reception confirmation message.

[0074] S107. After receiving the file reception confirmation message from the board to be updated, the main MPU1 logic processing board compares the consistency with the encrypted MD5 code value in the USB flash drive. If the two comparison results are consistent, a file overwrite start message is sent to all boards to be updated, and the local image file and configuration file are overwritten in the local Flash. If the two comparison results are inconsistent, step S102 is repeated.

[0075] S108. After receiving the file overwrite start message, the board to be updated begins to store the configuration file and image file in the Flash.

[0076] S109. After successful overwrite, the board to be updated sends a file overwrite completion message to the main MPU1 logic processing board and / or the main MPU2 logic processing board. The file overwrite completion message contains the local board identifier, the MD5 code value of the stored configuration file and image file, and the encrypted MD5 code value.

[0077] After receiving the file overwrite completion message, the S110 main MPU1 logic processing board and / or the main MPU2 logic processing board store the MD5 code value in the file overwrite completion message in the USB flash drive; compare the encrypted MD5 code value corresponding to the board identifier with the encrypted MD5 code value stored in the USB flash drive, and send the comparison result to each board to be updated through the file overwrite completion confirmation message;

[0078] S111. After the board to be updated receives the confirmation message that the file overwrite is complete, it displays the update result; if the results are consistent, it displays that the update is complete; if the results are inconsistent, it displays that the update failed on the front panel of the board.

[0079] S112. After the USB flash drive is removed, read the MD5 code values ​​of each card to be updated stored in the USB flash drive for reconfirmation and compare them with the MD5 code in the release form. If they match, change the configuration update mode check word in the USB flash drive to normal operation mode, insert the USB flash drive and restart the system. If they do not match, change the update mode check word in the USB flash drive to rollback mode, roll back to the previous version, or reconfirm the file's correctness and update again.

[0080] In this embodiment, the main MPU1 logic processing board and the main MPU2 logic processing board are also boards to be updated; after sending the online update mode entry message, the main MPU1 logic processing board and the main MPU2 logic processing board encrypt the old configuration files and image files in the local Flash, so that the system update will fail or the user can roll back to the previous version.

[0081] In this embodiment, the version rollback process specifically includes:

[0082] If the update fails or the user wants to revert to the previous version, change the USB drive configuration update mode check word to rollback mode, and reinsert the modified USB drive into the main MPU1 logic processing board and the main MPU2 logic processing board to enter rollback mode.

[0083] After detecting the insertion of a USB flash drive, the main MPU1 logic processing board and the main MPU2 logic processing board read the configuration update mode verification word in the USB flash drive and set it to rollback mode, and send a rollback mode start message to the board to be updated.

[0084] After receiving the rollback mode start message, the updated board decrypts the encrypted file in the local Flash. After completion, it sends a rollback file completion message to the main MPU1 logic processing board and the main MPU2 logic processing board. The rollback file completion message contains the board identifier and local file version information.

[0085] After receiving the rollback completion message from all the boards to be updated, the main MPU1 logic processing board and the main MPU2 logic processing board read the board identifier and version information in the rollback completion message and compare it with the version information corresponding to the local board identifier. If they match, a rollback file completion confirmation message is sent to the corresponding board. If they do not match, a rollback failure is displayed on the front panel of the board.

[0086] The front panel displays a message indicating successful rollback. Remove the USB drive, change the online update mode to normal operation mode, restart the system, and the rollback operation is complete.

Claims

1. A vehicle-mounted safety platform based on a two-out-of-two architecture, characterized in that, The vehicle-mounted safety platform includes: a main system, a backup system, communication boards, and a storage medium; the main system and the backup system each include at least two logic processing boards, and the main system includes a main system MPU1 and a main system MPU2; the logic processing boards and the communication boards communicate via a bus, and the logic processing boards and / or the communication boards serve as boards to be updated; the storage medium is used to store files to be updated, and the files to be updated include a configuration update mode verification word, configuration files and image files of all boards to be updated, and corresponding encrypted MD5 codes; The main MPU1 and main MPU2 are used to perform a two-out-of-two comparison process on the files to be updated before the online update processing of all boards to be updated, including: The main MPU1 and main MPU2 are used to enter the online update process when the configuration update mode verification word is read as online update mode, and read the configuration files and image files of all cards to be updated in the storage medium, as well as the corresponding encrypted MD5 code values. The primary MPU1 is used to send an online update request message to the primary MPU2. The online update request message contains the encrypted MD5 code value of all configuration files and image files in the storage medium. After receiving an online update request message from the main MPU1, the main MPU2 stores the MD5 hash values ​​of all configuration files and image files in the online update request message, performs a consistency comparison between the encrypted MD5 hash value in the local storage medium and the encrypted MD5 hash value in the online update request message, and sends the consistency comparison result and the local encrypted MD5 hash value to the main MPU1 through an online update request confirmation message. After receiving the online update request confirmation message from the main MPU2, the primary MPU1 performs a consistency comparison between the encrypted MD5 code value in the local storage medium and the encrypted MD5 code value in the online update request confirmation message, and compares the obtained consistency comparison result with the consistency comparison result in the online update request confirmation message. The primary MPU1 and primary MPU2 are used to send an online update mode entry message to all boards to be updated when the two consistency comparison results are consistent.

2. An automatic update method for the vehicle-mounted safety platform according to claim 1, characterized in that, The backup system includes backup MPU1 and backup MPU2, and the communication board includes an MCU; the board to be updated includes at least one of the main MPU1, main MPU2, backup MPU1, backup MPU2, and MCU. The automatic update method includes: online update processing for all boards to be updated.

3. The automatic update method as described in claim 2, characterized in that, If the two consistency comparison results are inconsistent, exit the online update mode and display "Update Failed" on the front panel of the board.

4. The automatic update method as described in claim 2, characterized in that, Before the read configuration update mode verification word is set to online update mode, the following is also included: Insert storage media into primary MPU1 and primary MPU2; after detecting the insertion of storage media, primary MPU1 and primary MPU2 read the configuration update mode verification word and set it to online update mode.

5. The automatic update method as described in claim 2, characterized in that, The online update process for all boards to be updated specifically includes: S101. After receiving the online update mode entry message, the board to be updated encrypts the old configuration file and image file in its local storage. After completion, it replies with an online update mode confirmation message to the main MPU1. The online update mode confirmation message contains the local board identifier. S102. After receiving the online update mode confirmation message from the board to be updated, the main MPU1 reads the local board identifier in the online update mode confirmation message, unpacks and sorts the configuration file and image file corresponding to the board identifier in the storage medium, and calculates the encrypted MD5 code value of each file package. After completion, the main MPU1 sends a file distribution start message to the board to be updated. The file distribution start message includes the file name, the corresponding encrypted MD5 code value, and the number of files after unpacking. S103. After receiving the file distribution start message, the card to be updated stores the file name, the corresponding encrypted MD5 code value and the number of files after unpacking in the file distribution start message. S104. The main MPU1 sends a file distribution message to the board to be updated. The file distribution message contains the configuration file and image file corresponding to the board identifier. The file package with the unpacking number of the image file is odd and the corresponding encrypted MD5 code value. The main MPU2 sends a file distribution message to the board to be updated. The file distribution message contains the configuration file and image file corresponding to the board identifier. The file package with the unpacking number of the image file is even and the corresponding encrypted MD5 code value. S105. After receiving the file distribution message, the board to be updated calculates the encrypted MD5 code value for each file package and compares it with the encrypted MD5 code value in the message. If the calculated encrypted MD5 code value matches the encrypted MD5 code value in the message, the file package is stored. If the calculated encrypted MD5 code value does not match the encrypted MD5 code value in the message, the file package is discarded. S106. After receiving the file packets, each board to be updated will group the received file packets according to their numbers, calculate the encrypted MD5 value, compare it with the encrypted MD5 code value received in the file distribution start message, and reply to the main MPU1 with the comparison result and the encrypted MD5 code value through the file reception confirmation message. S107. After receiving the file reception confirmation message from the board to be updated, the main MPU1 compares the consistency with the encrypted MD5 code value in the storage medium. If the two comparison results are consistent, a file overwrite start message is sent to all boards to be updated, and the local image file and configuration file are overwritten in the local Flash. If the two comparison results are inconsistent, step S102 is repeated.

6. The automatic update method as described in claim 2 or 5, characterized in that, The update method further includes: overwriting the ontology image file and configuration file, specifically including: After the update board receives the file overwrite start message, it begins storing the configuration file and image file in the Flash memory; After a successful overwrite, the board to be updated sends a file overwrite completion message to primary MPU1 and / or primary MPU2. This message includes the local board identifier, the MD5 hash of the stored configuration file and image file, and an encrypted MD5 hash. Upon receiving the file overwrite completion message, primary MPU1 and / or primary MPU2 will then... Stored in the storage medium; compare the encrypted MD5 code value corresponding to the board identifier with the encrypted MD5 code value stored in the storage medium, and send the comparison result to each board to be updated through a file overwrite confirmation message; Once the updated board receives the confirmation message that the file overwrite is complete, it will display the update result. If the results are consistent, it will display "Update Completed"; if the results are inconsistent, it will display "Update Failed" on the front panel of the board. After the storage medium is removed, the MD5 hash of each card to be updated in the storage medium is read for reconfirmation and compared with the MD5 hash in the release form. If they match, the configuration update mode check word in the storage medium is changed to normal operation mode, the storage medium is inserted and the system is restarted. If they do not match, the update mode check word in the storage medium is changed to rollback mode, rolling back to the previous version, or the file correctness is reconfirmed and updated again.

7. The automatic update method as described in claim 2, characterized in that, After sending the online update mode entry message, the main MPU1 and the main MPU2 encrypt the old configuration files and image files in the local Flash, so that if the system update fails or the user rolls back to the previous version.

8. The automatic update method as described in claim 2, characterized in that, After the online update processing of all the boards to be updated, the following process is also included: version rollback processing.

9. The automatic update method as described in claim 8, characterized in that, The version rollback process specifically includes: If the update fails or the user wants to revert to the previous version, change the storage medium configuration update mode check word to rollback mode, reinsert the modified storage medium into the main system MPU1 and the main system MPU2, and enter rollback mode; After detecting the insertion of the storage medium, the main MPU1 and the main MPU2 read the configuration update mode verification word in the storage medium and set it to rollback mode, and send a rollback mode start message to the board to be updated; After the updated board receives the rollback mode start message, it decrypts the encrypted file in the local Flash. After completion, it sends a rollback file completion message to the main MPU1 and the main MPU2. The rollback file completion message contains the board identifier and local file version information. After receiving the rollback completion messages from all the boards to be updated, the main MPU1 and the main MPU2 read the board identifier and version information in the rollback completion message and compare them with the version information corresponding to the local board identifier. If they match, they send a rollback file completion confirmation message to the corresponding board. If they do not match, they display rollback failure on the front panel of the board. The front panel displays a message indicating successful rollback. Remove the storage medium, change the configuration from online update mode to normal operation mode, restart the system, and the rollback operation is complete.

Images