Rail transit equipment software maintenance system and method

Abstract

The invention provides a rail transit equipment software maintenance system and method, and the system comprises an equipment management module which generates an update configuration attachment of corresponding software based on a software graph number in a PLM configuration table, and obtains an original target code data package of the corresponding software; the networked PTU background server is used for generating an original software package in combination with the PLM configuration table, the update configuration attachment and the original target code data package, and packaging the original software package into an update software package; the FTP server is used for storing the updating software package into a preset server database and generating file storage information of the updating software package; and the networked PTU client is used for downloading the corresponding update software package according to the software maintenance work order, checking the update software package by using the original target code configuration information, and updating the update software package passing the checking to the to-be-maintained equipment. The method has the effect of saving manpower and time in the equipment software maintenance and updating process.

Description

Technical Field

[0001] The present invention belongs to the technical field of equipment maintenance, and particularly relates to a software maintenance system and method for rail transit equipment. Background Art

[0002] With the continuous improvement of the intelligence and informatization levels of on-vehicle equipment in rail transit trains, more and more on-vehicle terminal devices need to be connected to the train's Ethernet. During the commissioning, delivery, and operation and maintenance processes of the train, the programs of on-vehicle equipment need to be updated multiple times. There are a large number of devices in the on-site train network system, and each device has multiple program files that need to be maintained and updated. These program files include underlying programs, middleware programs, application programs, etc., and the program update methods and steps for each device are different. Therefore, before operation, it is necessary to compile manual update operation manuals for different programs. Then, software maintenance personnel perform flashing and maintenance work on a device-by-device and file-by-file basis according to these manuals. However, this method results in low overall work efficiency because the data preparation, on-site operation, and post-update confirmation and verification work for program updates require the centralized cooperation of on-site designers or maintenance personnel, and a large amount of manpower and time are consumed to complete. Summary of the Invention

[0003] The present invention provides a software maintenance system and method for rail transit equipment to solve the problem that a large amount of manpower and time are consumed for equipment software maintenance and update.

[0004] In a first aspect, the present invention provides a software maintenance system for rail transit equipment, and the system includes:

[0005] An equipment management module, configured to obtain a PLM configuration table of a device to be maintained, generate an update configuration attachment for the corresponding software based on the software drawing number in the PLM configuration table, and obtain the original target code data packet of the corresponding software;

[0006] A networked PTU client, configured on the device to be maintained, for creating a software maintenance work order;

[0007] A networked PTU background server, respectively connected to the equipment management module and the networked PTU client, for generating an original software package by combining the PLM configuration table, the update configuration attachment, and the original target code data packet, and packaging the original software package into an updated software package according to the encryption interface in the update configuration attachment, the original target code in the original target code data packet, and the software maintenance work order, and generating file storage information of the updated software package;

[0008] An FTP server, connected to the networked PTU background server, for storing the updated software package in a preset server database according to the configuration table number of the PLM configuration table;

[0009] The networked PTU client is also connected to the FTP server, and is further configured to download the corresponding update software package according to the software maintenance work order, verify the update software package using the original object code, and update the device software of the device to be maintained with the update software package that passes the verification.

[0010] Optionally, the networked PTU background server includes:

[0011] A software package generation module, connected to the device management module, for generating an original software package by combining the PLM configuration table, the update configuration attachment, and the original object code data packet;

[0012] A background server management module, for creating a database table;

[0013] A background database, respectively connected to the software package generation module and the background server management module, for storing the original software package, marking the software package status of the original software package as the to-be-packed status, and sending the software package information and the software package status of the original software package to the background server management module;

[0014] The background server management module is further configured to receive the software package information and the software package status, and record the software package information and the software package status in the database table;

[0015] A background packaging module, connected to the background server management module and the background database, for polling the database table, marking all the original software packages with the software package status of the to-be-packed status as to-be-packed software packages, and packaging the to-be-packed software packages into update software packages according to the encryption interface in the update configuration attachment, the original object code in the original object code data packet, and the software maintenance work order, and updating the software package status of the to-be-packed software packages to the packed status;

[0016] An information generation module, connected to the background packaging module, for generating file storage information of the update software package.

[0017] Optionally, the background database includes a two-layer storage directory structure of a first-level directory and a second-level directory. The second-level directory is a sub-directory structure of the first-level directory. The first-level directory is based on the PLM configuration table and is used to store the original object code data packets corresponding to all the software drawing numbers associated with the PLM configuration table. The second-level directory is based on the software drawing number and is used to classify and store the original software packages according to the flashing method in the PLM configuration table.

[0018] Optionally, the background packaging module includes:

[0019] A polling marking unit, connected to the background server management module, for polling the database table and marking all the original software packages with the software package status being the to-be-packaged status as to-be-packaged software packages;

[0020] A packaging verification unit, connected to the background database, for performing version verification on the to-be-packaged software packages;

[0021] A background packaging unit, connected to the packaging verification unit, for packaging the to-be-packaged software packages that pass the verification by the packaging verification unit into updated software packages according to the encryption interface in the update configuration attachment, the original object code in the original object code data packet, and the software maintenance work order;

[0022] A packaging encryption unit, connected to the background packaging unit, for encrypting the corresponding updated software packages according to the encryption interface in the update configuration attachment.

[0023] Optionally, the networked PTU client includes:

[0024] A work order creation module, for creating a software maintenance work order;

[0025] An update package download module, respectively connected to the work order creation module and the FTP server, for downloading the corresponding updated software packages according to the software maintenance work order;

[0026] A pre-update verification module, respectively connected to the update package download module and the networked PTU background server, for obtaining the original object code corresponding to the updated software package and comparing the target code information of the original object code with the updated target code in the updated software package to obtain a comparison result;

[0027] A software maintenance module, connected to the update verification module, when the comparison result of the update verification module is that the target code information of the original object code is consistent with the updated target code in the updated software package, for updating the device software of the device to be maintained by using the updated software package;

[0028] A post-update verification module, for obtaining the software version information of the device to be maintained after the device software is updated and performing post-update verification on the device software based on the software version information.

[0029] In a second aspect, the present invention further provides a method for maintaining a rail transit equipment software, the method including the following steps:

[0030] Obtain the PLM configuration table of the device to be maintained, generate an update configuration attachment for the corresponding software based on the software drawing number in the PLM configuration table, and obtain the original target code data packet of the corresponding software;

[0031] Create a software maintenance work order;

[0032] Combine the PLM configuration table, the update configuration attachment, and the original target code data packet to generate an original software package, and package the original software package into an updated software package according to the encryption interface in the update configuration attachment, the original target code in the original target code data packet, and the software maintenance work order;

[0033] And generate file storage information for the updated software package;

[0034] Store the updated software package in a preset server database according to the configuration table number of the PLM configuration table;

[0035] Download the corresponding updated software package according to the software maintenance work order, verify the updated software package using the original target code, and update the device software of the device to be maintained with the updated software package that passes the verification.

[0036] Optionally, the step of combining the PLM configuration table, the update configuration attachment, and the original target code data packet to generate an original software package, and packaging the original software package into an updated software package according to the encryption interface in the update configuration attachment, the original target code in the original target code data packet, and the software maintenance work order includes the following steps:

[0037] Combine the PLM configuration table, the update configuration attachment, and the original target code data packet to generate an original software package;

[0038] Create a database table;

[0039] Store the original software package in a preset background database;

[0040] Mark the software package status of the original software package as the to-be-packaged status, and record the software package information and the software package status of the original software package in the database table;

[0041] Poll the database table, mark all the original software packages with the software package status of the to-be-packaged status as to-be-packaged software packages, package the to-be-packaged software packages into updated software packages according to the encryption interface in the update configuration attachment, the original target code in the original target code data packet, and the software maintenance work order, and update the software package status of the to-be-packaged software packages to the already-packaged status.

[0042] Optionally, the background database includes a two - level storage directory structure of a first - level directory and a second - level directory. The second - level directory is a sub - directory structure of the first - level directory. The first - level directory is based on the PLM configuration table and is used to store all the original target - code data packets corresponding to the software drawing numbers associated with the PLM configuration table. The second - level directory is based on the software drawing number and is used to classify and store the original software packages according to the flashing method in the PLM configuration table.

[0043] Optionally, polling the database table, marking all the original software packages with the software package status of the to - be - packed status as to - be - packed software packages, and packaging the to - be - packed software packages into updated software packages according to the encryption interface in the update configuration attachment, the original target code in the original target - code data packet, and the software maintenance work order, and updating the software package status of the to - be - packed software packages to the packed status includes the following steps:

[0044] Poll the database table and mark all the original software packages with the software package status of the to - be - packed status as to - be - packed software packages;

[0045] Perform version verification on the to - be - packed software packages;

[0046] According to the encryption interface in the update configuration attachment and the original target code in the original target - code data packet, package the to - be - packed software packages that pass the packaging verification unit into updated software packages;

[0047] Encrypt the corresponding updated software packages according to the encryption interface in the update configuration attachment.

[0048] Optionally, downloading the corresponding updated software package according to the software maintenance work order, verifying the updated software package using the original target code, and updating the device software of the device to be maintained with the updated software package that passes the verification includes the following steps:

[0049] Download the corresponding updated software package according to the software maintenance work order;

[0050] Obtain the original target code corresponding to the updated software package and determine whether the target code information of the original target code and the updated target code in the updated software package is consistent;

[0051] If the target code information of the original target code and the updated target code in the updated software package is consistent, then update the device software of the device to be maintained with the updated software package;

[0052] Obtain the software version information of the device to be maintained after the device software is updated, and perform post - update verification on the device software based on the software version information.

[0053] The beneficial effects of the present invention are as follows:

[0054] Compared with the prior art where a large amount of manpower and time are required to complete the update and maintenance of the device software program, the present invention has the following beneficial effects:

[0055] 1. There is a complete process control scheme for the target code package to be updated, including configuration, packaging, verification, and distribution, which is a reliable and complete software maintenance process. After obtaining the PLM configuration table of the device to be maintained, the subsequent program verification, packaging, and distribution processes will be automatically completed, without manual transfer and verification in the middle, saving manpower and time in the update and maintenance process of the device software program;

[0056] 2. By storing the updated software package in the FTP server and associating the updated software package with the maintenance work order, it can be realized that the same updated software package involved in different maintenance work orders no longer needs to be sent repeatedly. Moreover, due to the association relationship between the updated software package and the maintenance work order, the networked PTU client can automatically associate and download the relevant updated software package without manual verification, also saving manpower and time;

[0057] 3. Through the update configuration attachment generated by the device management module, it can identify and support the update, version acquisition, and verification functions of multiple devices and multiple files. The program updates of different devices on the train can be batch-updated, without manual operation or switching to other software, also saving manpower and time. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 It is the system structure diagram of the rail transit equipment software maintenance system in the present invention.

[0059] Figure 2 It is the flow schematic diagram of the rail transit equipment software maintenance method in the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0060] The present invention discloses a rail transit equipment software maintenance system.

[0061] Referring to Figure 1 , the rail transit equipment software maintenance system specifically includes:

[0062] A device management module, configured to obtain the PLM configuration table of the device to be maintained, generate an update configuration attachment for the corresponding software based on the software drawing number in the PLM configuration table, and obtain the original target code data packet of the corresponding software;

[0063] A networked PTU client, configured on the device to be maintained, for creating a software maintenance work order;

[0064] The networked PTU background server is respectively connected to the device management module and the networked PTU client, and is used to generate an original software package by combining the PLM configuration table, the update configuration attachment and the original target code data packet, and package the original software package into an update software package according to the encryption interface in the update configuration attachment, the original target code in the original target code data packet and the software maintenance work order, and generate file storage information of the update software package;

[0065] The FTP server is connected to the networked PTU background server and is used to store the update software package into a preset server database according to the configuration table number of the PLM configuration table;

[0066] The networked PTU client is also connected to the FTP server. The networked PTU client is also used to download the corresponding update software package according to the software maintenance work order, verify the update software package by using the original target code, and update the device software of the device to be maintained with the update software package that passes the verification.

[0067] In this embodiment, the device to be maintained refers to various devices in the rail train that need software update and maintenance. The PLM configuration table is the PLM (Product Lifecycle Management) configuration resume table released by software R & D personnel. Through the one-key update configuration tool, an update configuration attachment for one-key update can be generated according to the PLM configuration table. The configured information adds information related to the version number acquisition method on the original basis. For example, if the refresh method of the software with 12 software drawing numbers in the PLM configuration table is Ethernet (indicating that one-key update can be performed), 12 attachments in the format of "onekeyupc-drawing number-resume table number.xml" can be generated by one-key update configuration as the update configuration attachment. The device management module is usually an MRO system. A connection is established between the device management module and the device to be maintained to obtain the PLM configuration table of the device. According to the software drawing number in the PLM configuration table, an update configuration attachment for the corresponding software is generated, including information such as the specified software version and update type. The original target code data packet of the corresponding software is obtained from the device management module, and this data packet contains the source code of the software, the compiled binary file, etc.

[0068] The software maintenance work order includes the identifier of the device to be maintained, the version and type of the update software package, the update time, etc. The module for the maintenance work order creation function is implemented on the client side and is created by the user. After the user creates the work order, it will be automatically pushed to the networked PTU background server. After receiving the work order, the background server will package the original software packages of multiple devices that need to be updated into an update software package according to the work order information, and then store it in the FTP server. The client is configured on the user's PC and is a client application software with a graphical interface.

[0069] Both the networked PTU background server and the networked PTU client are architected on the networked PTU software for operation. The networked PTU background server is communicatively connected to the device management module. After receiving the PLM configuration table, the updated configuration attachment, and the original target code data packet, the networked PTU background server generates an original software package containing the PLM configuration table, the updated configuration attachment, and the original target code data packet. And according to the encryption interface in the updated configuration attachment and the original target code in the original target code data packet, the original software package is packaged into an updated software package. The FTP (File Transfer Protocol) server is communicatively connected to the networked PTU background server to establish a file transfer channel. According to the configuration table number of the PLM configuration table, the updated software package is stored in a preset server database to ensure the security and reliability of the file. Generate file storage information of the updated software package, including file name, path, size, etc.

[0070] The networked PTU client connects to the networked PTU background server and the FTP server to obtain a software maintenance work order. Download the corresponding updated software package according to the software maintenance work order and store it in the local device. Use the original target code to verify the downloaded updated software package to ensure the integrity and correctness of the software package. The updated software package that passes the verification will be applied to the device to be maintained to update the device software.

[0071] The implementation principle of this embodiment is as follows:

[0072] In this embodiment, the PLM configuration table and the original target code data packet of the device to be maintained are obtained through the device management module, combined with the updated configuration attachment, to generate an updated software package and store it in the server database. Through the software maintenance work order and the FTP server, the updated software package is transmitted to the device to be maintained, and the original target code is used to verify and update the software package to realize the update of the device software. This can improve the efficiency and accuracy of in-vehicle device program updates and reduce the input of manpower and time.

[0073] In one of the embodiments, the networked PTU background server includes:

[0074] A software package generation module, connected to the device management module, for generating an original software package by combining the PLM configuration table, the updated configuration attachment, and the original target code data packet;

[0075] A background server management module, for creating a database table;

[0076] The background database is respectively connected to the software package generation module and the background server management module, and is used to store the original software package, mark the software package status of the original software package as the to-be-packed status, and send the software package information and the software package status of the original software package to the background server management module;

[0077] The background server management module is further used to receive the software package information and the software package status, and record the software package information and the software package status in the database table;

[0078] The background packaging module is connected to the background server management module and the background database, and is used to poll the database table, mark all the original software packages with the software package status of the to-be-packed status as to-be-packed software packages, and package the to-be-packed software packages into updated software packages according to the encryption interface in the update configuration attachment, the original object code in the original object code data packet, and the software maintenance work order, and update the software package status of the to-be-packed software packages to the already-packed status;

[0079] The information generation module is connected to the background packaging module and is used to generate the file storage information of the updated software package.

[0080] In this embodiment, the background server management module is used to create a database table datareceive to record the reception and storage of all original software packages. The fields of the table at least include: resume number, software drawing number, software flashing method (Ethernet and non-Ethernet), software package status (to-be-packed status, already-packed status, deleted status), data reception time, data packaging time, data deletion time, and data storage location. The background database stores the original software package and marks the software package status of the original software package as the to-be-packed status at the same time. The background server management module records the software package information and the software package status in the database table.

[0081] The background packaging module polls the database table, marks all the original software packages with the software package status of the to-be-packed status as to-be-packed software packages, packages the to-be-packed software packages into updated software packages according to the encryption interface in the update configuration attachment and the original object code in the original object code data packet, and updates the software package status of the to-be-packed software packages to the already-packed status. In one embodiment, the background server management module also polls the database table, deletes all the original software packages with the software package status of the already-packed status, and modifies the software package status to the deleted status. Finally, the information generation module generates the file storage information of the updated software package.

[0082] In one of the embodiments, the background database includes a two - level storage directory structure of a first - level directory and a second - level directory. The second - level directory is a sub - directory structure of the first - level directory. The first - level directory is based on the PLM configuration table and is used to store the original target - code data packets corresponding to all software drawing numbers associated with the PLM configuration table. The second - level directory is based on the software drawing number and is used to classify and store the original software packages according to the flashing method in the PLM configuration table.

[0083] In this embodiment, the storage directory structure of the original software package data in the background database is divided into two levels:

[0084] ① The first - level directory is a directory based on the PLM configuration table and stores the original target - code data packets (including the target code for non - Ethernet flashing) corresponding to all software drawing numbers associated with the PLM configuration table;

[0085] ② The second - level directory is a directory based on the software drawing number and is divided into two types: Ethernet flashing and non - Ethernet flashing according to the flashing method. In each directory of the software drawing number for Ethernet flashing, three types of data are stored (original target - code data packet, update configuration attachment, PLM configuration table), and in each directory of the software drawing number for non - Ethernet flashing, only the original target - code data packet is stored.

[0086] In one of the embodiments, the background packaging module includes:

[0087] A polling marking unit, connected to the background server management module, is used to poll the database table and mark the original software packages with the status of pending packaging as pending - packaging software packages;

[0088] A packaging verification unit, connected to the background database, is used to perform version verification on the pending - packaging software packages;

[0089] A background packaging unit, connected to the packaging verification unit, is used to package the pending - packaging software packages that pass the verification of the packaging verification unit into updated software packages according to the encryption interface in the update configuration attachment, the original target code in the original target - code data packet, and the software maintenance work order;

[0090] A packaging encryption unit, connected to the background packaging unit, is used to encrypt the corresponding updated software packages according to the encryption interface in the update configuration attachment.

[0091] In this embodiment, the polling marking unit polls the database table at regular intervals to check the status of the software package. For the original software package with the status of to-be-packaged, it is marked as a to-be-packaged software package. Version verification is performed on the to-be-packaged software package to ensure the consistency between the version of the software package and the relevant configuration. The version verification mainly targets the version number and MD5 value of the object code. The verification may include checking the version number and verifying the integrity of the software package. According to the encryption interface specified in the update configuration attachment and the original object code in the original object code data packet, the to-be-packaged software package that passes the version verification is subjected to a packaging operation. The packaging operation may include operations such as compressing and encrypting the files of the to-be-packaged software package to generate an update software package. The update software package is encrypted using the encryption interface specified in the update configuration attachment to ensure the security of the software package. Encryption can be performed using an encryption algorithm on the file or using an encryption key. After encryption, the update software package can be securely transmitted and stored.

[0092] In one of the embodiments, the connected PTU client includes:

[0093] A work order creation module for creating a software maintenance work order;

[0094] An update package download module, which is respectively connected to the connected PTU background server and the FTP server, and is used to download the corresponding update software package according to the software maintenance work order;

[0095] A pre-update verification module, which is respectively connected to the update package download module and the connected PTU background server, and is used to obtain the original object code corresponding to the update software package, and compare the object code information of the original object code with the updated object code in the update software package to obtain a comparison result;

[0096] A software maintenance module, which is connected to the update verification module. When the comparison result of the update verification module is that the object code information of the original object code is consistent with the updated object code in the update software package, it is used to update the device software of the device to be maintained with the update software package;

[0097] A post-update verification module for obtaining the software version information of the device to be maintained after the device software is updated, and performing post-update verification on the device software based on the software version information.

[0098] In this embodiment, according to the information provided in the software maintenance work order, the corresponding updated software package is downloaded from a specified source (such as a server or cloud storage). The download can be performed by file transfer via the HTTP or FTP protocol. The updated software package is parsed, and the original object code therein is extracted. The original object code information is obtained and compared with the updated object code information in the updated software package. The comparison can include checking the version number, MD5 value, verifying the integrity of the object code, etc. According to the instructions in the maintenance work order, the updated software package is applied to the device software of the device to be maintained. The update process can include deploying the updated software package to the device, performing the update operation, etc. The software version information of the device to be maintained is obtained to confirm that the device software has been successfully updated. According to the updated version of the device software, corresponding verification operations are performed to ensure the normal operation and consistency of the device software.

[0099] The present invention also discloses a method for maintaining the software of rail transit equipment.

[0100] Refer to Figure 2 , the method for maintaining the software of rail transit equipment specifically includes the following steps:

[0101] S101. Obtain the PLM configuration table of the device to be maintained, generate the corresponding software update configuration attachment based on the software drawing number in the PLM configuration table, and obtain the original object code data packet of the corresponding software.

[0102] Among them, a connection is established with the device to be maintained through the device management module to obtain the PLM configuration table of the device. According to the software drawing number in the PLM configuration table, the corresponding software update configuration attachment is generated, including information such as the specified software version and update type. The original object code data packet of the corresponding software is obtained from the device management module, and this data packet contains the source code and compiled binary files of the software, etc.

[0103] S102. Create a software maintenance work order.

[0104] Among them, the software maintenance work order includes the identifier of the device to be maintained, the version and type of the updated software package, the update time, etc. The module for the function of creating the maintenance work order is implemented on the client side and is created by the user. After the user creates the work order, it will be automatically pushed to the networked PTU background server. After receiving the work order, the background server will package the original software packages of multiple devices that need to be updated into an updated software package and then store it in the FTP server. The client is configured on the user's PC and is a client application software with a graphical interface.

[0105] S103. Generate the original software package by combining the PLM configuration table, the update configuration attachment, and the original object code data packet, and package the original software package into an updated software package according to the encryption interface in the update configuration attachment and the original object code in the original object code data packet.

[0106] Among them, the networked PTU background server is connected to the device management module to obtain the PLM configuration table, update the configuration attachment, and the original target code data packet. According to the information in the PLM configuration table and the updated configuration attachment, combined with the original target code data packet, an original software package is generated. According to the encryption interface in the updated configuration attachment and the original target code in the original target code data packet, the original software package is encrypted and packaged to generate an updated software package.

[0107] S104. Generate the file storage information of the updated software package.

[0108] S105. Store the updated software package into a preset server database according to the configuration table number of the PLM configuration table, and generate the file storage information of the updated software package.

[0109] Among them, the FTP server is connected to the networked PTU background server to establish a file transfer channel. According to the configuration table number of the PLM configuration table, the updated software package is stored into a preset server database to ensure the security and reliability of the file. Generate the file storage information of the updated software package, including file name, path, size, etc., for subsequent software maintenance work order creation.

[0110] S106. Download the corresponding updated software package according to the software maintenance work order, and use the original target code to verify the updated software package, and update the device software of the device to be maintained with the updated software package that passes the verification.

[0111] Among them, the networked PTU client is connected to the networked PTU background server and the FTP server to obtain the software maintenance work order. Download the corresponding updated software package according to the software maintenance work order and store it in the local device. Use the original target code to verify the downloaded updated software package to ensure the integrity and correctness of the software package. The updated software package that passes the verification will be applied to the device to be maintained to update the device software.

[0112] The implementation principle of this embodiment is as follows:

[0113] In this embodiment, by obtaining the PLM configuration table and the original target code data packet of the device to be maintained, combined with the updated configuration attachment, an updated software package is generated and stored in the server database. Through the software maintenance work order and the FTP server, the updated software package is transmitted to the device to be maintained, and the original target code is used to verify and update the software package, realizing the update of the device software. This can improve the efficiency and accuracy of in-vehicle device program updates and reduce the input of manpower and time.

[0114] In one of the embodiments, step S102 specifically includes the following steps:

[0115] Generate an original software package by combining the PLM configuration table, the updated configuration attachment, and the original object code data packet;

[0116] Create a database table;

[0117] Store the original software package in a preset back-end database;

[0118] Mark the software package status of the original software package as the to-be-packed status, and record the software package information and the software package status of the original software package in the database table;

[0119] Poll the database table, mark all the original software packages with the software package status of the to-be-packed status as to-be-packed software packages, and pack the to-be-packed software packages into updated software packages according to the encryption interface in the updated configuration attachment, the original object code in the original object code data packet, and the software maintenance work order, and update the software package status of the to-be-packed software packages to the packed status.

[0120] In this embodiment, the networked PTU back-end server obtains the PLM configuration table, the updated configuration attachment, and the original object code data packet. According to the information in the PLM configuration table and the updated configuration attachment, combined with the original object code data packet, an original software package is generated. Create a database table in the back-end database to record the information and status of the software package. Store the generated original software package in a preset back-end database, and binary data of files can be stored using types such as BLOB (Binary Large Object). Add a column in the database table to record the software package status, and the initial status is the to-be-packed status. Record the information and status of the original software package in the database table, including information such as file name, path, and size. The networked PTU back-end server polls the database table regularly to check the status of the software package. For the original software packages with the status of to-be-packed, pack the to-be-packed software packages into updated software packages according to the encryption interface in the updated configuration attachment and the original object code in the original data packet. During the packing process, encrypt the to-be-packed software packages according to the encryption interface specified in the updated configuration attachment. After packing is completed, update the software package status of the to-be-packed software packages to the packed status, indicating that the software package has been successfully packed into an updated software package.

[0121] In this embodiment, an original software package is generated by combining a PLM configuration table, an updated configuration attachment, and an original target code data packet. The original software package is stored in a preset background database, and a database table is created to record the information and status of the software package. By polling the database table, all original software packages with a status of to-be-packaged are marked as to-be-packaged software packages, and the to-be-packaged software packages are packaged into updated software packages according to the encryption interface in the updated configuration attachment and the original target code in the original target code data packet. Finally, the software package status of the to-be-packaged software package is updated to the packaged status, indicating that the software package has been successfully packaged into an updated software package. This can achieve the automation of software package generation and packaging, improving efficiency and accuracy. At the same time, by recording the information and status of the software package in the database, it is convenient for subsequent management and tracking.

[0122] In one of the embodiments, the background database includes a two-layer storage directory structure of a first-level directory and a second-level directory. The second-level directory is a sub-directory structure of the first-level directory. The first-level directory is based on the PLM configuration table and is used to store the original target code data packets corresponding to all software drawing numbers associated with the PLM configuration table. The second-level directory is based on the software drawing number and is used to classify and store the original software packages according to the flashing method in the PLM configuration table.

[0123] In one of the embodiments, the step of polling the database table, marking all original software packages with a software package status of to-be-packaged as to-be-packaged software packages, packaging the to-be-packaged software packages into updated software packages according to the encryption interface in the updated configuration attachment and the original target code in the original target code data packet, and updating the software package status of the to-be-packaged software package to the packaged status specifically includes the following steps:

[0124] Poll the database table and mark all original software packages with a software package status of to-be-packaged as to-be-packaged software packages;

[0125] Perform version verification on the to-be-packaged software packages;

[0126] According to the encryption interface in the updated configuration attachment, the original target code in the original target code data packet, and the software maintenance work order, package the to-be-packaged software packages that pass the packaging verification unit into updated software packages;

[0127] Encrypt the corresponding updated software packages according to the encryption interface in the updated configuration attachment.

[0128] In this embodiment, the database table is polled at regular intervals to check the status of software packages. For the original software packages with the status of to-be-packaged, they are marked as to-be-packaged software packages. Version verification is performed on the to-be-packaged software packages to ensure the consistency between the version of the software packages and the relevant configurations. The version verification mainly targets the version number and MD5 value of the object code. The verification can include checking the version number and verifying the integrity of the software package. According to the encryption interface specified in the update configuration attachment and the original object code in the original object code data packet, the to-be-packaged software packages that pass the version verification are subjected to a packaging operation. The packaging operation can include operations such as compressing and encrypting the files of the to-be-packaged software packages to generate an updated software package. The updated software package is encrypted using the encryption interface specified in the update configuration attachment to ensure the security of the software package. Encryption can be performed using an encryption algorithm on the file or using an encryption key. After encryption, the updated software package can be safely transmitted and stored.

[0129] In this embodiment, by polling the database table, all software packages with the status of to-be-packed are marked as to-be-packaged software packages. Then, version verification is performed on the to-be-packaged software packages to ensure the consistency between the version of the software packages and the relevant configurations. According to the encryption interface in the update configuration attachment and the original object code in the original object code data packet, the to-be-packaged software packages that pass the version verification are packaged into an updated software package. During the packaging process, operations such as compressing and encrypting the files of the to-be-packaged software packages can be performed to generate an updated software package. Finally, according to the encryption interface in the update configuration attachment, the updated software package is encrypted to ensure the security of the software package. This can ensure that the updated software package after verification and packaging of the to-be-packaged software package meets the requirements and is secure.

[0130] In this embodiment, the updated software package is downloaded according to the software maintenance work order, and the original object code of the updated software package is obtained. By comparing the original object code with the object code information in the updated software package, it is judged whether they are consistent. If they are consistent, the updated software package is applied to the device software of the device to be maintained to implement software update of the device. Finally, the software version information of the updated device is obtained and verified to ensure the normal operation and consistency of the device software.

[0131] In one of the embodiments, step S105 specifically includes the following steps:

[0132] Download the corresponding updated software package according to the software maintenance work order;

[0133] Obtain the original object code corresponding to the updated software package, and judge whether the object code information of the original object code is consistent with the updated object code in the updated software package;

[0134] If the object code information of the original object code is consistent with the updated object code in the updated software package, use the updated software package to update the device software of the device to be maintained;

[0135] Obtain the software version information of the device to be maintained after the device software is updated, and perform post-update verification on the device software based on the software version information.

[0136] In this embodiment, according to the information provided in the software maintenance work order, download the corresponding update software package from a specified source (such as a server or cloud storage). The download method can be file transfer via the HTTP or FTP protocol. Parse the update software package and extract the original target code therein. Obtain the original target code information and compare it with the updated target code information in the update software package. The comparison can include checking the version number, MD5 value, verifying the integrity of the target code, etc. Apply the update software package to the device software of the device to be maintained according to the instructions in the maintenance work order. The update process can include deploying the update software package to the device, performing the update operation, etc. Obtain the software version information of the device to be maintained and confirm that the device software has been successfully updated. Perform corresponding verification operations according to the post-update version of the device software to ensure the normal operation and consistency of the device software.

[0137] Those of ordinary skill in the art should understand that: the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of protection of this application is limited to these examples; under the concept of this application, the technical features in the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations in different aspects of one or more of the above embodiments of this application, which are not provided in detail for the sake of brevity.

[0138] One or more embodiments of this application are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of this application. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of this application shall be included within the scope of protection of this application.

Claims

1. A software maintenance system for rail transit equipment, characterized in that, the system includes: An equipment management module, which is used to obtain the PLM configuration table of the equipment to be maintained, generate an update configuration attachment for the corresponding software based on the software drawing number in the PLM configuration table, and obtain the original target code data packet of the corresponding software; A networked PTU client, configured on the equipment to be maintained, which is used to create a software maintenance work order; A networked PTU background server, which is respectively connected to the equipment management module and the networked PTU client, and is used to generate an original software package by combining the PLM configuration table, the update configuration attachment and the original target code data packet, and according to the encryption interface in the update configuration attachment, the original target code in the original target code data packet and the software maintenance work order, package the original software package into an updated software package, and generate file storage information of the updated software package; An FTP server, which is connected to the networked PTU background server, and is used to store the updated software package into a preset server database according to the configuration table number of the PLM configuration table; The networked PTU client is also connected to the FTP server, and the networked PTU client is also used to download the corresponding updated software package according to the software maintenance work order, verify the updated software package with the original target code, and update the equipment software of the equipment to be maintained with the updated software package that passes the verification.

2. The software maintenance system for rail transit equipment according to claim 1, characterized in that, the networked PTU background server includes: A software package generation module, which is connected to the equipment management module, and is used to generate an original software package by combining the PLM configuration table, the update configuration attachment and the original target code data packet; A background server management module, which is used to create a database table; A background database, which is respectively connected to the software package generation module and the background server management module, and is used to store the original software package, mark the software package status of the original software package as the to-be-packaged status, and send the software package information and the software package status of the original software package to the background server management module; The background server management module is also used to receive the software package information and the software package status, and record the software package information and the software package status in the database table; A background packaging module, which is connected to the background server management module and the background database, and is used to poll the database table, mark all the original software packages with the software package status of the to-be-packaged status as to-be-packaged software packages, and according to the encryption interface in the update configuration attachment, the original target code in the original target code data packet and the software maintenance work order, package the to-be-packaged software packages into updated software packages, and update the software package status of the to-be-packaged software packages to the already-packaged status; An information generation module, which is connected to the background packaging module, and is used to generate file storage information of the updated software package.

3. The software maintenance system for rail transit equipment according to claim 2, characterized in that, The background database includes a two - level storage directory structure of a first - level directory and a second - level directory. The second - level directory is a sub - directory structure of the first - level directory. The first - level directory is based on the PLM configuration table and is used to store all the original target code data packets corresponding to the software drawing numbers associated with the PLM configuration table. The second - level directory is based on the software drawing number and is used to classify and store the original software packages according to the flashing method in the PLM configuration table.

4. The rail transit equipment software maintenance system according to claim 2, wherein, the background packaging module includes: a polling marking unit, connected to the background server management module, for polling the database table and marking all the original software packages with the software package status of the to - be - packaged status as to - be - packaged software packages; a packaging verification unit, connected to the background database, for performing version verification on the to - be - packaged software packages; a background packaging unit, connected to the packaging verification unit, for packaging the to - be - packaged software packages passed by the packaging verification unit into updated software packages according to the encryption interface in the update configuration attachment, the original target code in the original target code data packet, and the software maintenance work order; a packaging encryption unit, connected to the background packaging unit, for encrypting the corresponding updated software packages according to the encryption interface in the update configuration attachment.

5. The rail transit equipment software maintenance system according to claim 1, wherein, the networked PTU client includes: a work order creation module, for creating a software maintenance work order; an update package download module, connected to the work order creation module and the FTP server respectively, for downloading the corresponding updated software package according to the software maintenance work order; a pre - update verification module, connected to the update package download module and the networked PTU background server respectively, for obtaining the original target code corresponding to the updated software package and comparing the target code information of the original target code with the updated target code in the updated software package to obtain a comparison result; a software maintenance module, connected to the update verification module. When the comparison result of the update verification module is that the target code information of the original target code is consistent with the updated target code in the updated software package, it is used to update the device software of the device to be maintained with the updated software package; a post - update verification module, for obtaining the software version information of the device to be maintained after the device software is updated and performing post - update verification on the device software based on the software version information.

6. A rail transit equipment software maintenance method, wherein, it includes the following steps: Obtain the PLM configuration table of the device to be maintained, generate an update configuration attachment for the corresponding software based on the software drawing number in the PLM configuration table, and obtain the original target code data packet of the corresponding software; Create a software maintenance work order; Generate an original software package by combining the PLM configuration table, the update configuration attachment, and the original object code data packet, and package the original software package into an updated software package according to the encryption interface in the update configuration attachment, the original object code in the original object code data packet, and the software maintenance work order; Generate file storage information for the updated software package; Store the updated software package in a preset server database according to the configuration table number of the PLM configuration table; Download the corresponding updated software package according to the software maintenance work order, verify the updated software package using the original object code, and update the device software of the device to be maintained with the updated software package that passes the verification.

7. The rail transit equipment software maintenance method according to claim 6, wherein, The step of generating an original software package by combining the PLM configuration table, the update configuration attachment, and the original object code data packet, and packaging the original software package into an updated software package according to the encryption interface in the update configuration attachment, the original object code in the original object code data packet, and the software maintenance work order includes the following steps: Generate an original software package by combining the PLM configuration table, the update configuration attachment, and the original object code data packet; Create a database table; Store the original software package in a preset background database; Mark the software package status of the original software package as the to-be-packaged status, and record the software package information and the software package status of the original software package in the database table; Poll the database table, mark all the original software packages with the software package status of the to-be-packaged status as to-be-packaged software packages, package the to-be-packaged software packages into updated software packages according to the encryption interface in the update configuration attachment, the original object code in the original object code data packet, and the software maintenance work order, and update the software package status of the to-be-packaged software packages to the packaged status.

8. The rail transit equipment software maintenance method according to claim 7, wherein, The background database includes a two-layer storage directory structure of a first-level directory and a second-level directory. The second-level directory is a subordinate directory structure of the first-level directory. The first-level directory is based on the PLM configuration table and is used to store all the original object code data packets corresponding to the software drawing numbers associated with the PLM configuration table. The second-level directory is based on the software drawing number and is used to store the original software packages classified according to the flashing method in the PLM configuration table.

9. The rail transit equipment software maintenance method according to claim 7, wherein, The step of polling the database table, marking all the original software packages with the software package status of the to-be-packaged status as to-be-packaged software packages, packaging the to-be-packaged software packages into updated software packages according to the encryption interface in the update configuration attachment, the original object code in the original object code data packet, and the software maintenance work order, and updating the software package status of the to-be-packaged software packages to the packaged status includes the following steps: Poll the database table and mark all the original software packages with the software package status of the to-be-packaged status as to-be-packaged software packages; Perform version verification on the to-be-packaged software packages; Package the to-be-packaged software packages that pass the verification of the packaging verification unit into updated software packages according to the encryption interface in the update configuration attachment, the original object code in the original object code data packet, and the software maintenance work order; Encrypt the corresponding updated software packages according to the encryption interface in the update configuration attachment.

10. The rail transit equipment software maintenance method according to claim 6, characterized in that, The steps of downloading the corresponding updated software package according to the software maintenance work order, verifying the updated software package with the original object code, and updating the device software of the to-be-maintained device with the updated software package that passes the verification include the following steps: Download the corresponding updated software package according to the software maintenance work order; Obtain the original object code corresponding to the updated software package, and determine whether the object code information of the original object code is consistent with the updated object code in the updated software package; If the object code information of the original object code is consistent with the updated object code in the updated software package, update the device software of the to-be-maintained device with the updated software package; Obtain the software version information of the to-be-maintained device after the device software is updated, and perform post-update verification on the device software based on the software version information.

Images