An apparatus, system, and method for remote upgrading of wayside equipment

Abstract

The present application belongs to the technical field of train equipment upgrading, and provides a device, system and method for remote upgrading of trackside equipment, wherein the system comprises an upgrading server and trackside equipment which interacts with the upgrading server. The system of the present application integrates the upgrading server and the trackside equipment, separates the upgrading function from the safety function, develops the upgrading function as an independent component, and can make it not necessary to follow the strict process of functional safety development, thereby significantly reducing the overall development cost. Meanwhile, the system firstly downloads the upgrading program to the temporary download area of the trackside equipment when upgrading, and then moves the upgrading program to the application program area, so that the original safety program can also normally run when the trackside equipment is in the upgrading process.

Description

Technical Field

[0001] This invention belongs to the field of train equipment upgrade technology, and specifically relates to a device, system and method for remote upgrade of trackside equipment. Background Technology

[0002] Traditional rail transit equipment maintenance primarily relies on on-site maintenance. However, as rail transit lines extend from city centers to suburbs, the installation locations of trackside equipment are increasingly characterized by distances from stations, remote locations, and poor accessibility. Some equipment may be installed beside elevated tracks, inside underground tunnels, or in remote suburban areas. Reaching these locations requires significant time for staff; for example, round trips to suburban equipment can take several hours. Furthermore, on-site operations are limited by weather, traffic, and rail operating hours. For instance, subway maintenance often occurs at night when services are closed, leading to low maintenance efficiency and difficulty in quickly responding to program upgrades or fault restart requests. Against this backdrop, remote upgrade and restart technology for trackside functional safety equipment has become a crucial industry requirement. Remote technology enables equipment program updates and fault restarts without on-site staff intervention, significantly improving maintenance efficiency, reducing costs, and minimizing the impact of equipment failures or program delays on rail transit operations.

[0003] The main technical challenges of remotely upgrading trackside equipment are as follows: 1. In the field of trackside functional safety equipment, functional safety is a core technical requirement. The programs for this type of equipment must comply with international or national functional safety standards, such as IEC 61508, EN 50128, and EN 50129. Functional safety software development requires strict procedures and meets relevant standards, resulting in high development costs. Therefore, separating upgrade functions from safety functions and developing upgrade functions as independent components eliminates the need to adhere to the stringent functional safety development process, thereby significantly reducing overall development costs.

[0004] 2. Functional safety software includes multiple safety protection measures such as memory self-test, FLASH self-test, and communication self-test. If remote upgrade function is developed directly in it, more constraints need to be considered, which will significantly increase the difficulty of system development.

[0005] 3. Currently, remote upgrades mostly use online application upgrades. If the upgrade process is interrupted, it may cause system damage and make it impossible to intervene remotely or restart the upgrade process. It must be handled on-site by staff, which will have a significant impact on the operation of the rail transit system. Summary of the Invention

[0006] To address the problems in the background art, the present invention proposes an apparatus, system, and method for remote upgrading of trackside equipment.

[0007] To achieve the above objectives, the present invention adopts the following technical solution: A remote upgrade device for trackside equipment, configured on the trackside equipment, includes: The first receiving module is used to receive the first information sent by the upgrade server; the first information includes a power failure restart request, an upgrade request, an upgrade program, and power failure information; The first sending module is used to send second information to the upgrade server. The second information includes power failure restart response information, upgrade request response information, upgrade program response information, data retransmission request, data transmission completion response information, and upgrade completion information. The analysis module is used to determine whether the upgrade program is experiencing packet loss.

[0008] Furthermore, it also includes a first memory, which comprises: The device ID configuration area contains the ID, device model, and hardware version number of the storage track-side device, as well as the ID, device model, and hardware version number of the storage upgrade server. The application area stores the safety programs currently running on the trackside equipment. A temporary download area is used to receive upgrade programs sent by the upgrade server; The boot record area is used to read the upgrade program from the temporary download area and write it to the application area.

[0009] A remote upgrade device for trackside equipment, configured on an upgrade server, includes: The second receiving module is used to receive the second information fed back by the trackside equipment. The second information includes power failure response information, upgrade request response information, upgrade data response information, data retransmission request, and data transmission completion response information. The second sending module is used to send first information to the trackside equipment. The first information includes a power failure restart request, an upgrade request, an upgrade program, and power failure information.

[0010] Furthermore, it also includes a second memory; The second memory stores the ID, device model, and hardware version number of the trackside device, as well as the ID, device model, and hardware version number of the upgrade server.

[0011] A system for remote upgrading of trackside equipment includes an upgrade server and trackside equipment that interacts with the upgrade server. The trackside equipment is equipped with one of the aforementioned remote upgrade devices for trackside equipment; the upgrade server is equipped with one of the aforementioned remote upgrade devices for trackside equipment.

[0012] A method for remotely upgrading trackside equipment, performed via the trackside equipment, includes the following steps: Receive a power outage restart request from the upgrade server; Send a power failure restart response message to the upgrade server; Receive upgrade requests continuously sent by the upgrade server; The trackside equipment undergoes upgrade and calibration. After the calibration is completed, it sends an upgrade request response message to the upgrade server. Receive the upgrade program from the upgrade server, and after receiving it, send the upgrade program response information to the upgrade server; The trackside equipment determines whether the upgrade program has lost packets. If packets are lost, it sends a data retransmission request to the upgrade server. After sending a data retransmission request, the system receives the upgrade program from the upgrade server. After receiving the program, it checks whether the upgrade program has lost any packets. If no packets are lost, the system sends a data transmission completion response to the upgrade server. The upgrade is performed based on the upgrade program, and an upgrade completion message is sent to the upgrade server after the upgrade is completed. Receive power failure information from the upgrade server and restart after power failure.

[0013] Furthermore, the trackside equipment undergoes upgrade and calibration. After calibration, it sends an upgrade request response to the upgrade server, including the following steps: The ID, device model, and hardware version number of the trackside device sent by the upgrade server are compared with the ID, device model, and hardware version number stored in the trackside device itself. If the two match, the verification is complete. Send an upgrade request response message to the upgrade server. The response message includes the ID of the trackside device, the device model and hardware version number, as well as a signal indicating that the upgrade is permitted.

[0014] Furthermore, the upgrade process, based on the upgrade procedure, includes the following steps: The upgrade program is written from the temporary download area to the application area; the temporary download area and the application area are divided in a first memory, which is configured in a trackside device.

[0015] A method for remotely upgrading trackside equipment, executed via an upgrade server, includes the following steps: Send a power-off restart request to the trackside equipment; Receive power failure restart response information from trackside equipment; Continuously send upgrade requests to trackside equipment; Receive upgrade request response information from trackside equipment and determine whether to upgrade the trackside equipment; Send upgrade program to trackside equipment; Receive upgrade procedure response information from trackside equipment; Receive data retransmission requests from trackside equipment; Send the upgrade procedure to the trackside equipment again until no more data retransmission requests are received from the trackside equipment; Receive data transmission completion response information from trackside equipment; Receive upgrade completion information from trackside equipment; Send a power outage message to the trackside equipment.

[0016] Furthermore, continuously send upgrade requests to the trackside equipment, including the following steps: It continuously sends upgrade request signals, the ID of the trackside equipment, the equipment model and hardware version number, as well as the ID of the upgrade server, the equipment model and hardware version number to the trackside equipment.

[0017] Furthermore, receiving upgrade request response information from the trackside equipment and determining whether to upgrade the trackside equipment includes the following steps: After receiving the request and response information from the trackside device, the server reads the trackside device's ID, device model, hardware version number, and whether the upgrade is allowed. If the trackside device is allowed to be upgraded, and the ID, device model, and hardware version number of the trackside device stored on the upgrade server are consistent with the corresponding content in the request and response information received by the upgrade server, then the upgrade of the trackside device is allowed.

[0018] An operating method for a remote upgrade system for trackside equipment, wherein an upgrade server and trackside equipment interact with each other; during the information interaction, the trackside equipment executes the aforementioned method for remote upgrade of trackside equipment, and the upgrade server executes the aforementioned method for remote upgrade of trackside equipment.

[0019] The beneficial effects of this invention are: 1. The present invention proposes a trackside device, which is equipped with a first receiving module to independently receive the data required for the upgrade, and a first sending module to independently send back response information. Through the above settings, the upgrade hardware of the trackside device can be separated to reduce interference with the safety hardware. 2. The first memory of the present invention is provided with a boot loading area. When the remote server downloads the upgrade program to the device's temporary download area and verifies it successfully, the bootloader will receive the upgrade instruction, read the new program from the temporary download area, and then safely and completely move it to the final program area of ​​the Flash storage to replace the old program. In this process, since the bootloader runs independently of the functional safety program, it can avoid the technical limitation of the functional safety program "replacing itself" and ensure that the normal operation of the old program is not affected when the new program is moved. At the same time, it can also reduce the risk of device failure due to program transfer errors through its own underlying operation stability, providing core support for the security and reliability of remote upgrades. 3. The upgrade server of the present invention is equipped with a second sending module and a second receiving module. When upgrading the trackside equipment, the upgrade server interacts directly with the trackside equipment through the above modules, without the need for memory self-test, FLASH self-test, communication self-test and other measures, thus improving the upgrade efficiency. 4. The system of the present invention integrates the upgrade server and the trackside equipment, separates the upgrade function from the safety function, and develops the upgrade function as an independent component. This allows it to avoid following the strict process of functional safety development, thereby significantly reducing the overall development cost. At the same time, when the system is upgrading, it first downloads the upgrade program to the temporary download area of ​​the trackside equipment, and then moves the upgrade program to the application area, so that the original safety program can also run normally when the trackside equipment is being upgraded.

[0020] 5. The method of the present invention needs to detect whether the upgrade program is losing packets. If packets are lost, the lost data needs to be downloaded again from the upgrade server to ensure the integrity of the upgrade program.

[0021] Other features and advantages of the invention will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures pointed out in the description and the drawings. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 A schematic diagram of the structure of a remote upgrade system for trackside equipment according to the present invention is shown; Figure 2 A structural diagram of the trackside device of the present invention is shown; Figure 3 A partition diagram of the first memory of the present invention is shown; Figure 4 A structural diagram of the upgrade server of the present invention is shown; Figure 5 A flowchart of the method for remote upgrade of trackside equipment according to the present invention is shown; Figure 6 A flowchart of the method for remotely upgrading trackside equipment executed by the upgrade server of the present invention is shown; Figure 7 An operational diagram of a remote upgrade system for trackside equipment according to the present invention is shown. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0025] like Figure 1 As shown, a remote upgrade system for trackside equipment is illustrated. This system includes an upgrade server and trackside equipment that interacts with the upgrade server. The trackside equipment internally includes a temporary data download area and an application area. When the trackside equipment is being upgraded, it first downloads the upgrade program from the upgrade server to the temporary download area. After the program data is complete, the upgrade program is then moved to the application area for execution.

[0026] The temporary storage area for trackside equipment is designed to prevent upgrade failures from affecting field applications and to allow for the restoration of the old version of the application in the event of an upgrade failure. Therefore, a two-stage upgrade function is designed.

[0027] like Figure 2 As shown, Figure 1 The trackside equipment includes a first receiving module, a first transmitting module, and an analysis module. During information exchange, the first receiving module can receive first information sent by the upgrade server; this first information includes, but is not limited to, a power-off restart request, an upgrade request, an upgrade program, and power-off information. Similarly, the first transmitting module can send second information to the upgrade server, which includes, but is not limited to, a power-off restart response, an upgrade request response, an upgrade program response, a data retransmission request, a data transmission completion response, and an upgrade completion information. The analysis module can determine whether the upgrade program has suffered packet loss; if packet loss occurs, the first receiving module can re-download the upgrade program from the upgrade server.

[0028] It should be noted that the upgrade program is usually split into several data packets for storage and transmission. For example, an upgrade program can be divided into 100 data packets. When the trackside equipment downloads these 100 data packets from the upgrade server, some data packets may be lost due to factors such as transmission environment, signal interference, or network fluctuations. The loss of any data packet will result in an incomplete upgrade program and failure to complete the upgrade normally. Therefore, it is necessary to use the analysis module to check and judge the lost data packets one by one, accurately identify the lost data packets, and thus ensure that the downloaded upgrade program data is complete and error-free.

[0029] Optionally, the first receiving module and the first transmitting module may be equipped with one or more combinations of Ethernet interface circuit, CAN bus transceiver, RS485 / RS232 communication interface, Wi-Fi module, 4G / 5G wireless communication module or radio frequency transceiver device, and the analysis module may be a microcontroller MCU, processor, DSP, FPGA or embedded processing chip with data verification function, used to realize packet loss judgment and retransmission control of the upgrade program.

[0030] like Figure 3 As shown, the trackside device is also equipped with a first memory, which can be divided into a bootloader area, an application area, a temporary download area, and a device ID configuration area.

[0031] The device ID configuration area stores fixed information such as the device's unique ID (e.g., "trackside signal - number A001"), device model (e.g., "XT-2023 trackside control unit"), and hardware version number, essentially acting as the device's "identity card." The device ID area includes the device ID (including station area number, device type, and device number) and its digital signature information, used for upgrade verification. The device ID configuration area is write-protected by default and can only be unlocked and modified using a dedicated tool during factory configuration or authorized maintenance to prevent accidental tampering during remote upgrades. The upgrade server stores the device IDs and data signatures of all trackside devices. Trackside devices only store their own device ID and signature information. After the upgrade server sends an upgrade request, the trackside device sends its own device ID and signature to the upgrade server. The upgrade server verifies the device's validity to prevent accidental upgrades. During bidirectional verification between the upgrade server and trackside devices, the trackside device first parses the received upgrade request to check if it was sent to itself. If so, it returns its device ID and data signature to the upgrade server. The upgrade server verifies the device's validity by comparing the returned digital signature with its stored signature.

[0032] The application area stores the security programs currently running on the trackside device. Only the bootloader has permission to perform a "program replacement" operation on this area.

[0033] The temporary download area is used to receive upgrade programs sent by the upgrade server. It is equivalent to a "temporary storage warehouse for upgrade programs". Before successful verification, it does not affect the operation of old programs in the application area. During remote upgrade, the upgrade program is first downloaded to the temporary download area. After successful verification, the Bootloader moves the new program from the temporary download area to the application area to replace the old security program. Throughout the process, the old security program is always in a runnable state to avoid device paralysis due to upgrade failure.

[0034] The boot record area is located at the very beginning of the Flash memory (low address area), and is the first area where the program is read after the device is powered on. This area is protected by hardware-level "read-only" protection, so even if a program error occurs during a remote upgrade, the bootloader program will not be damaged, ensuring that the device can always start normally. During a remote upgrade, the bootloader does not directly receive the upgrade program. It only reads the upgrade program from the temporary download area after successful verification in the temporary download area, and then writes it to the application area, avoiding its own participation in data transmission and reducing the risk of errors.

[0035] It's important to note that the bootloader is the first basic program to run when an embedded device (such as a railside functional safety device) starts up. It acts as a startup wizard, its core function being to complete hardware initialization (such as checking the memory and Flash storage for proper function) and load and start the device's core functional programs (such as functional safety programs) after the device powers on or restarts, ensuring a smooth transition from power-on to normal operation. Simultaneously, it possesses certain low-level operational capabilities, allowing it to manipulate hardware resources such as Flash storage without relying on the core functional programs. During remote upgrades of railside devices, the bootloader plays a crucial role as a safe transporter and program guardian.

[0036] like Figure 4 As shown, Figure 1 The upgrade server includes a second receiving module and a second sending module. During information exchange, the second receiving module can receive second information fed back by the trackside equipment; the second sending module can send first information to the trackside equipment.

[0037] It should be noted that the upgrade server can remotely interact with trackside equipment, completing program upgrades without requiring personnel to go to the site, open the cover for wiring, or disassemble and install equipment on-site. For example, in scenarios where trackside equipment is widely distributed, deployed in remote locations, or in complex environments, it can significantly reduce on-site maintenance workload, lower labor costs and travel safety risks, while shortening upgrade time, improving maintenance efficiency, and avoiding problems such as equipment power outages and poor line contact caused by on-site operations. It enables centralized, efficient, and secure batch upgrade management of multiple trackside devices, ensuring timely system function updates and stable operation.

[0038] Furthermore, the upgrade server is also equipped with a second storage device, which can store the ID, device model, and hardware version number of the trackside equipment.

[0039] It should be noted that the information such as the ID, model, and hardware version of the trackside devices stored in the upgrade server is stored in a configuration file.

[0040] like Figure 5 As shown, a method for remotely upgrading trackside equipment, performed via the trackside equipment, includes the following steps: S1: Receive a power-off restart request from the upgrade server; specifically, the first receiving module receives the power-off restart request from the upgrade server via the Internet.

[0041] S2: Send power failure and restart response information to the upgrade server; Specifically, the trackside equipment can detect its current operating status and determine whether it meets the safe power failure conditions. If there are no business interruptions, critical task executions, or other interference factors that prohibit power failure, it can restart when it is confirmed that it is safe to power failure and restart. After restarting, it sends the corresponding power failure and restart response information to the upgrade server through the first sending module.

[0042] S3: Receive upgrade requests continuously sent by the upgrade server; specifically, the first receiving module can continuously receive upgrade requests from the upgrade server. During this process, the upgrade server will send information such as the ID, device model, and hardware version number of the trackside device to be upgraded to the first receiving module so that the trackside device can be upgraded and verified in the future.

[0043] S4: The trackside equipment undergoes upgrade verification. After verification, it sends an upgrade request response to the upgrade server. Specifically, it compares the ID, model, and hardware version number of the trackside equipment sent by the upgrade server with the ID, model, and hardware version number stored in the trackside equipment itself. If they match, the verification is complete. Subsequently, the first sending module of the trackside equipment sends an upgrade request response to the upgrade server. This information includes the ID, model, and hardware version number of the trackside equipment, as well as a signal indicating that the upgrade is permitted.

[0044] It should be noted that the upgrade request response information may also include information about the upgrade server.

[0045] S5: Receive the upgrade program from the upgrade server, and after receiving it, send the upgrade program response information to the upgrade server.

[0046] S6: The trackside device determines whether the upgrade process has lost packets. If packet loss is found, it sends a data retransmission request to the upgrade server. Specifically, the bootloader program in the trackside device's boot loading area will enter the execution state after restarting, read the upgrade ascending data packets, and help the trackside device perform integrity verification of the upgrade process. The trackside device will determine whether there are packet loss scenarios such as missing data packets, fragment disorder, or data corruption based on the read upgrade ascending data packets. If the verification confirms that packet loss exists, the trackside device sends a data retransmission request to the upgrade server through the first sending module. The request information must clearly indicate the missing data packet fragment sequence number, the number of missing fragments, and the checksum of the corresponding fragment, so that the upgrade server can locate and resend the data or resend all data packets.

[0047] S7: After sending a data retransmission request, receive the upgrade program from the upgrade server. After receiving the program, continue to determine whether the upgrade program has lost packets. If no packets are lost, send a data transmission completion response message to the upgrade server.

[0048] S8: Upgrade based on the upgrade program, and send upgrade completion information to the upgrade server after the upgrade is complete. Specifically, during the upgrade process, the Bootloader reads the upgrade program and then writes it from the temporary download area to the application area. During this process, non-critical business processes are paused, while basic device communication and security monitoring functions are retained. After writing to the application area, the system immediately reads back and verifies the integrity of the upgrade program using the CRC checksum of the upgrade file. If the verification fails, the upgrade is immediately terminated, and upgrade exception information (including exception code and fault description) is sent to the upgrade server. If the upgrade process is completed successfully, the trackside device sends upgrade completion information to the upgrade server through the first sending module. The information includes key data such as the upgraded program version number, upgrade time, and the current core status parameters of the device.

[0049] S9: Receives power failure information from the upgrade server and performs a power failure restart. Specifically, after the upgrade is completed, the trackside equipment needs to be powered off and restarted. After restarting, the equipment automatically loads the upgraded program version, enters normal operation, and sends a successful restart confirmation to the upgrade server through the first sending module.

[0050] like Figure 6 As shown, a method for remotely upgrading trackside equipment, executed via an upgrade server, includes the following steps: A1: Send a power-off restart request to the trackside equipment; specifically, this step is executed through the second sending module, and the upgrade server can receive external instructions to send a power-off restart request.

[0051] A2: Receive power failure and restart response information from the trackside equipment; specifically, the second receiving module will receive the power failure response information from the trackside equipment, at which point the trackside equipment has already restarted.

[0052] A3: Continuously send upgrade requests to the trackside equipment; specifically, after A2 confirms that the trackside equipment has been restarted, the upgrade server generates an upgrade request, which includes the trackside equipment ID, equipment model, hardware version number, etc.; continuously send the upgrade request to the trackside equipment through the second sending module until the upgrade request response information of the trackside equipment is received, and at the same time carry the cumulative number of times sent in the request to avoid repeatedly triggering the trackside equipment verification process.

[0053] A4: Receive upgrade request response information from the trackside equipment; specifically, after the second receiving module receives the response information from the trackside equipment, it needs to read the content of the response information, including the trackside equipment's own ID, equipment model, hardware version number, and whether the upgrade is allowed. If the trackside equipment allows the upgrade, and the ID, equipment model, and hardware version number of the trackside equipment stored in the upgrade server are consistent with the corresponding content in the request response information received by the upgrade server, then A5 can be performed.

[0054] A5: Send the upgrade program to the trackside equipment; specifically, the second sending module sends the upgrade program to the trackside equipment and stores it in the temporary download area of ​​the first memory.

[0055] A6: Receive upgrade procedure response information from the trackside equipment; specifically, the second receiving module receives the upgrade procedure response information, which indicates that a single data transmission has been completed.

[0056] A7: Receive data retransmission requests from trackside equipment; specifically, if a single data transmission is incomplete, it indicates that packet loss has occurred in the upgrade process, and the second receiving module will also receive data retransmission requests from the trackside equipment.

[0057] A8: Send the upgrade program to the trackside equipment again until no more data retransmission requests are received from the trackside equipment; specifically, the second sending module will send the upgrade program from below based on the data retransmission request. When sending, it can resend the complete application in ascending order, or send the lost data packets to the temporary download area.

[0058] A9: Receive data transmission completion response information from the trackside equipment; specifically, when the upgrade data in the trackside equipment is complete, the second receiving module will receive the data transmission completion response information sent by its trackside equipment. At the same time, the second receiving module performs Cyclic Redundancy Check (CRC), and the result shows that no errors occurred during the data transmission and the data integrity is good. After that, the upgrade server will no longer send the upgrade program to the trackside equipment.

[0059] A10: Receive upgrade completion information from trackside equipment; specifically, the second receiving module receives upgrade completion information sent by the trackside equipment, and the upgrade server parses the data contained in the information, such as the upgraded program version number, upgrade time, and current core status parameters of the equipment, and compares it with the target upgrade version and status standard preset by the server to confirm that the upgrade result of the trackside equipment meets expectations.

[0060] A11: Send a power-off message to the trackside equipment. Specifically, the upgrade server has confirmed that the upgrade of the trackside equipment is complete and a power-off restart is required to allow the trackside equipment to load the upgrade program.

[0061] like Figure 7 The diagram illustrates an operating method for a remote upgrade system for trackside equipment, wherein the upgrade server and the trackside equipment interact; during this interaction, the trackside equipment executes S1-S9 as described above, and the upgrade server executes A1-A11 as described above; specifically: The upgrade server sends a power-off restart request to the trackside device, which then performs a power-off restart. The upgrade server then sends a power-off restart response message. After restarting, the trackside device enters the Bootloader program, which is in the boot loading state.

[0062] Subsequently, the upgrade server continuously sends upgrade requests to the trackside equipment, the bootloader program enters the upgrade process, and the trackside equipment then sends upgrade request response information. Upon receiving the upgrade request response information, the upgrade server reads the trackside equipment's ID, equipment model, hardware version number, and upgrade-permitted information. The upgrade server then compares its stored trackside equipment ID, equipment model, and hardware version number with the received request response information. If they match and the upgrade-permitted information is found, the upgrade can proceed.

[0063] Next, the upgrade server sends the data (upgrade program) to the trackside device in the form of data packets. The trackside device stores all the data packets in the temporary download area of ​​the first memory. After the data packets are downloaded, the trackside device sends the upgrade program response information to the upgrade server.

[0064] Next, the bootloader program reads the upgrade program's data packets from the temporary download area to determine if the upgrade program has lost packets. If packets are lost, the trackside device needs to send a data retransmission request to the upgrade server. After receiving the request, the upgrade server sends the lost data packets (or all data packets) to the trackside device. The trackside device continues to verify, and once it confirms that the upgrade program's data packets are complete, it can send a data transmission completion response to the upgrade server. At the same time, it ensures that the CRC (Cyclic Redundancy Check) check is completed, which is the upgrade check mentioned earlier.

[0065] The bootloader program in the boot loader area reads the upgrade program from the temporary download area, moves it to the application area and replaces the original security program, completes the upgrade, and sends an upgrade completion response message back to the upgrade server after the upgrade is complete.

[0066] Finally, the upgrade server receives the upgrade completion response and sends a power outage restart message to the trackside equipment, which then restarts and loads the upgrade program.

[0067] Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A remote upgrade device for trackside equipment, configured on the trackside equipment, characterized in that, include: The first receiving module is used to receive the first information sent by the upgrade server; The first information includes a power outage restart request, an upgrade request, an upgrade program, and power outage information; The first sending module is used to send second information to the upgrade server. The second information includes power failure restart response information, upgrade request response information, upgrade program response information, data retransmission request, data transmission completion response information, and upgrade completion information. The analysis module is used to determine whether the upgrade program is experiencing packet loss.

2. The remote upgrade device for trackside equipment according to claim 1, characterized in that, It also includes a first memory, which comprises: The device ID configuration area contains the ID, device model, and hardware version number of the storage track-side device, as well as the ID, device model, and hardware version number of the storage upgrade server. The application area stores the safety programs currently running on the trackside equipment. A temporary download area is used to receive upgrade programs sent by the upgrade server; The boot record area is used to read the upgrade program from the temporary download area and write it to the application area.

3. A remote upgrade device for trackside equipment, configured on an upgrade server, characterized in that, include: The second receiving module is used to receive second information fed back by the trackside equipment. The second information includes power failure response information, upgrade request response information, upgrade data response information, data retransmission request, and data transmission completion response information. The second sending module is used to send first information to the trackside equipment. The first information includes a power failure restart request, an upgrade request, an upgrade program, and power failure information.

4. A remote upgrade device for trackside equipment according to claim 3, characterized in that, It also includes a second memory; The second memory stores the ID, device model, and hardware version number of the trackside device, as well as the ID, device model, and hardware version number of the upgrade server.

5. A system for remote upgrading of trackside equipment, characterized in that, This includes upgrade servers and trackside equipment that interacts with the upgrade servers. The trackside equipment is equipped with a remote upgrade device for trackside equipment as described in claim 1 or 2. The upgrade server is equipped with a remote upgrade device for trackside equipment as described in claim 3 or 4.

6. A method for remotely upgrading trackside equipment, performed via the trackside equipment, characterized in that, Includes the following steps: Receive a power outage restart request from the upgrade server; Send a power failure restart response message to the upgrade server; Receive upgrade requests continuously sent by the upgrade server; The trackside equipment undergoes upgrade and calibration. After the calibration is completed, it sends an upgrade request response message to the upgrade server. Receive the upgrade program from the upgrade server, and after receiving it, send the upgrade program response information to the upgrade server; The trackside equipment determines whether the upgrade program has lost packets. If packets are lost, it sends a data retransmission request to the upgrade server. After sending a data retransmission request, the system receives the upgrade program from the upgrade server. After receiving the program, it checks whether the upgrade program has lost any packets. If no packets are lost, the system sends a data transmission completion response to the upgrade server. The upgrade is performed based on the upgrade program, and an upgrade completion message is sent to the upgrade server after the upgrade is completed. Receive power failure information from the upgrade server and restart after power failure.

7. A method for remote upgrading of trackside equipment according to claim 6, characterized in that, The trackside equipment undergoes upgrade and calibration. After calibration, it sends an upgrade request response to the upgrade server, including the following steps: The ID, device model, and hardware version number of the trackside device sent by the upgrade server are compared with the ID, device model, and hardware version number stored in the trackside device itself. If the two match, the verification is complete. The upgrade request response information is sent to the upgrade server. The request response information includes the ID of the trackside device, the device model and hardware version number, and a signal that the upgrade is allowed.

8. A method for remote upgrading of trackside equipment according to claim 6, characterized in that, Upgrading based on the upgrade procedure includes the following steps: The upgrade program is written from the temporary download area to the application area; the temporary download area and the application area are divided in a first memory, which is configured in the trackside device.

9. A method for remotely upgrading trackside equipment, executed via an upgrade server, characterized in that, Includes the following steps: Send a power-off restart request to the trackside equipment; Receive power failure restart response information from trackside equipment; Continuously send upgrade requests to trackside equipment; Receive upgrade request response information from trackside equipment and determine whether to upgrade the trackside equipment; Send upgrade program to trackside equipment; Receive upgrade procedure response information from trackside equipment; Receive data retransmission requests from trackside equipment; Send the upgrade procedure to the trackside equipment again until no more data retransmission requests are received from the trackside equipment; Receive data transmission completion response information from trackside equipment; Receive upgrade completion information from trackside equipment; Send a power outage message to the trackside equipment.

10. A method for remote upgrading of trackside equipment according to claim 9, characterized in that, Continuously send upgrade requests to the trackside equipment, including the following steps: It continuously sends upgrade request signals, the ID of the trackside equipment, the equipment model and hardware version number, as well as the ID of the upgrade server, the equipment model and hardware version number to the trackside equipment.

11. A method for remote upgrading of trackside equipment according to claim 9, characterized in that, Receiving upgrade request response information from trackside equipment and determining whether to upgrade the trackside equipment includes the following steps: After receiving the request and response information from the trackside device, the server reads the trackside device's ID, device model, hardware version number, and whether the upgrade is allowed. If the trackside device is allowed to be upgraded, and the ID, device model, and hardware version number of the trackside device stored on the upgrade server are consistent with the corresponding content in the request and response information received by the upgrade server, then the upgrade of the trackside device is allowed.

12. An operating method for a remote upgrade system for trackside equipment, characterized in that, Upgrade servers and trackside equipment to facilitate information exchange; During information exchange, the trackside equipment executes a method for remote upgrading of trackside equipment as described in any one of claims 6-8, and the upgrade server executes a method for remote upgrading of trackside equipment as described in any one of claims 9-11.

Images