Temporary speed limit data interaction method and system based on remote backup mechanism

Abstract

The invention discloses a temporary speed limit data interaction method and system based on a remote backup mechanism, and the method comprises the following steps: establishing communication between a main controller and each regional controller, and backing up and storing temporary speed limit data to each regional controller based on the remote backup mechanism; after the main controller is restarted, receiving version messages uploaded by each regional controller within a preset waiting time; the main controller calls the regional controller with the maximum version number in the uploaded version message as a backup object; the backup temporary speed limit data on the backup object is read, whether the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted or not is judged based on cyclic redundancy check, if yes, the main controller stores the backup temporary speed limit data, and if not, it is considered that interaction fails, and an interaction error prompt is output. The method has the beneficial effects that the security of the system is improved, each regional controller undertakes backup storage, additional hardware storage is not needed, and the applicability is improved.

Description

Technical Field

[0001] The present application relates to the field of urban rail transit technology, and in particular to a temporary speed limit data interaction method and system based on an off-site backup mechanism. Background Art

[0002] During the operation of urban rail CBTC systems, occasional failures or temporary construction projects may necessitate temporary speed restrictions to ensure safe operation. Once the failure or construction is complete, the temporary speed restrictions can be lifted. Temporary speed restrictions affect operational safety and place extremely high demands on safety.

[0003] Existing domestic urban rail systems primarily utilize a Template Speed ​​Restrict Server (TSRS) to interact with the Automatic Train Supervision (ATS) system and distribute the temporary speed limit information to all ZCs (Zone Controllers) along the line. Each ZC then sends the information to trains within its jurisdiction for implementation. Some manufacturers combine the TSRS and ZCs, selecting a single ZC on the line to act as the TSRS for interaction with the ATS. Other ZCs then retrieve the temporary speed limit information from the TSRS-enabled ZC for implementation. This approach reduces system hardware costs and customer maintenance costs.

[0004] However, in actual passenger operations, TSRS (or ZC with TSRS function) may experience downtime or abnormal restart due to hardware failure or software defects, which often results in the loss of the temporary speed limit information currently running in the system. ATS, as a non-SIL4 system, cannot serve as a safe and reliable source of the original temporary speed limit information. In this case, the user needs to re-set the temporary speed limit, which not only carries the safety risk of errors but also has time costs.

[0005] The Chinese patent, "A Temporary Speed ​​Limit Method in Urban Rail CBTC Mode," published with publication number CN103707904A on April 9, 2014, specifically discloses the following steps: a data storage unit uploads temporary speed limit information prior to a power outage, and upon confirmation, normal line control begins; the data storage unit periodically uploads the temporary speed limit information to the automatic monitoring system; the data storage unit and the automatic monitoring system perform two interactive confirmations; the data storage unit splits the temporary speed limit and transmits the temporary speed limit information; the regional controller feeds the received temporary speed limit information back to the data storage unit and issues a mobile authorization speed limit instruction; the data storage unit stores the feedback results; and the automatic protection system applies speed limit braking to the train. However, this solution uses the data storage unit for interactive confirmation, which increases the system's hardware structure and has poor applicability.

[0006] The Chinese patent, "Train Control System, Occupancy Identification, and Method, Device, and System for Wayside Equipment Communication," published with publication number CN117533377A and publication date February 9, 2024, specifically discloses the construction of bidirectional train-to-ground wireless communication, train-to-train communication, and head-to-tail train communication based on a three-dimensional, multi-dimensional communication approach. It also integrates spatiotemporal positioning technology to implement train control technologies such as moving block, quasi-moving block, or automatic block. When conditions are met, virtual train coupling can be achieved. A train operation control system or backup train operation control method based on a bidirectional transponder can be used independently or under conditions such as when train-to-ground wireless communication is disconnected. Both train control systems support precise stopping and automated train operation. Both systems are cost-effective and highly efficient, and can be retrofitted onto existing train control systems, serving as independent train control systems. Methods for occupancy checking and train integrity determination are also proposed. This solution utilizes two train control systems to check movement authorization information, which also involves additional system hardware. Summary of the Invention

[0007] The present application addresses the problem in the prior art that temporary speed limit information interaction requires additional hardware structure to improve the reliability of the information source, and provides a temporary speed limit data interaction method and system based on an off-site backup mechanism. By storing the temporary speed limit data in each regional controller based on the off-site backup mechanism, when the main controller crashes, restarts abnormally, etc., the temporary speed limit data is synchronized and backed up from the remaining regional controllers, and the consistency between the temporary speed limit data before the restart and the backup temporary speed limit data is determined based on a cyclic redundancy check. There is no need to reset the existing TSR information of the line on the ATS system, which reduces the complexity of operation, improves efficiency, and ensures the security and reliability of the temporary speed limit data, thereby improving the security of the system. In addition, each regional controller is responsible for the backup storage, and there is no need to add additional hardware storage, which improves applicability.

[0008] To achieve the above-mentioned technical objectives, the present application provides a technical solution, which is a temporary speed limit data interaction method based on an off-site backup mechanism, comprising the following steps: S1: The main controller establishes communication with each regional controller, and backs up and stores the temporary speed limit data in each regional controller based on the off-site backup mechanism; S2: After the main controller is restarted, the main controller receives the version message uploaded by each regional controller within a preset waiting time; S3: The main controller calls the regional controller with the largest version number in the uploaded version message as the backup object; S4: Reads the backup temporary speed limit data on the backup object, and determines whether the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted based on a cyclic redundancy check. If so, the main controller stores the backup temporary speed limit data; if not, the interaction is considered to have failed, and an interaction error prompt is output.

[0009] Furthermore, the reading of the backup temporary speed limit data on the backup object also includes: the main controller sends a TSR refresh command message to the backup object, the backup object is converted to a reading state, the backup object replies with a TSR refresh response message to the main controller, and the main controller reads the backup temporary speed limit data on the backup object.

[0010] Furthermore, the backup object replies to the main controller with a TSR refresh response message, which also includes: the backup object sub-packets the backup temporary speed limit data based on the maximum message length to obtain several TSR refresh response messages, and the backup object replies to the main controller with a TSR refresh response message.

[0011] Furthermore, the reading of the backup temporary speed limit data on the backup object also includes: based on the reading time threshold, determining whether the backup temporary speed limit data on the backup object is read within the reading time threshold; if so, the reading is considered successful; if not, the reading is considered failed, and an interactive error prompt is output.

[0012] Furthermore, the output interaction error prompt also includes: sending the message data of reading failure or interaction failure to the train automatic monitoring system, and the train automatic monitoring system marks the corresponding TSR information position as speed limit loss status output based on the message data of reading failure or interaction failure.

[0013] Furthermore, the cyclic redundancy check-based judgment on whether the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted includes: the main controller calculates a backup CRC value based on the backup temporary speed limit data, and sends it to the train automatic monitoring system as a field of the TSR status information message; the train automatic monitoring system calculates the original CRC value based on the temporary speed limit data before the main controller is restarted, compares the backup CRC value and the original CRC value, and if they are consistent, it is considered that the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted; if they are inconsistent, it is considered that the backup temporary speed limit data is inconsistent with the temporary speed limit data before the main controller is restarted.

[0014] Furthermore, it also includes: S5: the main controller switches the state after receiving the speed limit determination instruction, and outputs the TSR version information containing the status field to each regional controller; S6: each regional controller performs CRC information consistency judgment and main controller status confirmation based on the TSR version information, and determines whether information update needs to be executed based on the judgment result and the confirmation result.

[0015] Furthermore, the S5 includes: after receiving the speed limit determination instruction, the main controller switches from the initialization state to the working state; and periodically outputs TSR version information including a status field to each regional controller.

[0016] Furthermore, S6 includes: each regional controller compares the CRC information in the TSR version information with the backup CRC information to determine whether they are consistent; each regional controller confirms whether the main controller is in a working state based on the status field in the TSR version information; when the judgment result is inconsistent and the main controller is in a working state, execute information update.

[0017] Another technical solution provided by the present application is a temporary speed limit data interaction system based on an off-site backup mechanism, which is used to implement the method as described above, including: a main controller, used to interact with the train automatic monitoring system to obtain temporary speed limit data; a regional controller, used to interact with the main controller and back up the temporary speed limit data for the main controller to read after restart.

[0018] The beneficial effects of the present application are as follows: by storing temporary speed limit data in each regional controller based on an off-site backup mechanism, when the main controller crashes, restarts abnormally, etc., the temporary speed limit data is synchronized and backed up from the remaining regional controllers, and the cyclic redundancy check is used to determine whether the temporary speed limit data before the restart is consistent with the backup temporary speed limit data. There is no need to reset the existing TSR information of the line on the ATS system, which reduces the complexity of operation, improves efficiency, and ensures the security and reliability of the temporary speed limit data, thereby improving the security of the system. In addition, each regional controller is responsible for the backup storage, and there is no need to add additional hardware storage, which improves applicability. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 This is a flow chart of the temporary speed-limited data interaction method based on the off-site backup mechanism of this application.

[0020] Figure 2 This is a schematic diagram of the main controller backup reading process of the temporary speed limit data interaction method based on the off-site backup mechanism of this application.

[0021] Figure 3 This is a schematic diagram of the backup process of the temporary speed-limited data interaction method based on the off-site backup mechanism of this application. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solutions and advantages of this application more clear, the application is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific implementation method described here is only an optimal embodiment of this application, which is only used to explain this application and does not limit the scope of protection of this application. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0023] like Figure 1As shown in the first embodiment of the present application, the temporary speed limit data interaction method based on the remote backup mechanism includes the following steps: S1: The main controller establishes communication with each regional controller and backs up and stores temporary speed limit data to each regional controller based on the off-site backup mechanism; S2: After the main controller is restarted, it receives the version message uploaded by each regional controller within the preset waiting time; S3: The main controller calls the regional controller with the largest version number in the uploaded version message as the backup object; S4: Read the backup temporary speed limit data on the backup object, and determine whether the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted based on the cyclic redundancy check. If so, the main controller stores the backup temporary speed limit data. If not, it is considered that the interaction has failed and an interaction error prompt is output.

[0024] In this embodiment, by storing the temporary speed limit data in each regional controller based on an off-site backup mechanism, when the main controller crashes or restarts abnormally, the temporary speed limit data is synchronized and backed up from the remaining regional controllers, and the cyclic redundancy check is used to determine whether the temporary speed limit data before the restart is consistent with the backup temporary speed limit data. There is no need to reset the existing TSR information of the line on the ATS system, which reduces the complexity of operation, improves efficiency, and ensures the security and reliability of the temporary speed limit data, thereby improving the security of the system. In addition, each regional controller is responsible for the backup storage, and there is no need to add additional hardware storage, which improves applicability.

[0025] Among them, the main controller can be a temporary speed limit server TSRS (Template Speed ​​Restrict Server) or a regional controller ZC with TSRS function. Off-site backup is a data backup strategy, which refers to backing up data to a place far away from the original data storage location. In this embodiment, the main controller establishes communication with the remaining regional controllers. During the normal operation of the main controller, the temporary speed limit data is backed up and stored in each regional controller to achieve off-site backup. When the main controller is restarted, it enters the backup reading process and receives the message version number uploaded by each regional controller within the preset time. Since the train automatic monitoring system ATS updates the temporary speed limit TSR information each time, the TSR version number stored on the temporary speed limit server TSRS and the regional controller ZC side will be increased by 1. At this time, the larger version number corresponds to the updated version. Based on the largest version number, the latest version of the TSR information can be determined. The regional controller with the largest version number in the uploaded version message is used as the backup object, and the latest version of the TSR information can be obtained during the backup reading. At this time, step S3 also includes: continuously updating the version number with the largest field according to the size of the version number in the uploaded version message, and recording the regional controller ID corresponding to the version number; When there are equal version numbers, the regional controller ID corresponding to the version message received first is recorded; The main controller calls the regional controller with the largest version number in the uploaded version message as the backup object based on the final recorded regional controller ID.

[0026] Before the timer expires, the maximum version number in the field is continuously updated, and the corresponding regional controller ID is recorded at the same time. If the version numbers are equal, the version message received first will prevail. After the timer expires, the regional controller is determined to be the device that currently stores the latest version of the TSR information and is selected as the target for backup information reading.

[0027] like Figure 2 As shown, reading the backup temporary speed limit data on the backup object also includes: The main controller sends a TSR refresh command message to the backup object, the backup object switches to the read state, the backup object replies with a TSR refresh response message to the main controller, and the main controller reads the backup temporary speed limit data on the backup object.

[0028] The main controller sends a TSR refresh command message to the backup object. The backup object switches from the idle state to the read state and replies with a TSR refresh response message to implement backup reading. Because the number of TSR entries in operation may be large, the interface protocol design adopts the form of packet transmission. At this time, the backup object replies to the main controller with a TSR refresh response message, which also includes: the backup object sub-packets the backup temporary speed limit data based on the maximum message length, obtaining several TSR refresh response messages, and the backup object replies to the main controller with a TSR refresh response message.

[0029] In this embodiment, considering the maximum length of the message, the TSR refresh response message is set to send a maximum of 30 TSR entries per message, and a total packet number field is defined on the interface protocol to indicate the total number of messages, and a packet index number field is defined to indicate which subpacket it is.

[0030] During the reading process, reading exceptions may occur due to network problems. To avoid excessive system startup time or infinite waiting, a maximum time limit is set for the sub-packet receiving process. At this time, the temporary speed limit data for reading the backup object also includes: Based on the reading time threshold, it is determined whether the backup temporary speed limit data on the backup object is read within the reading time threshold. If so, the reading is considered successful. If not, the reading is considered failed and an interactive error prompt is output.

[0031] The read time threshold is the maximum read time. When the main controller sends a TSR refresh command message to the backup object, the refresh response timer is started. The timing of the refresh response timer is the read time threshold. When the refresh response timer times out and there is still no reading, it is considered that the read has failed, and an interactive error prompt is given, thereby avoiding the system startup time being too long or infinite waiting, and ensuring the efficiency of exception handling.

[0032] Determining whether the backup temporary rate limit data on the backup object is read within the read time threshold includes: If the number of TSR refresh command messages received by the main controller within the read time threshold is the same as the total number of messages, it is considered that the backup temporary speed limit data on the backup object has been read; If the number of TSR refresh command messages received by the main controller within the read time threshold is less than the total number of messages, it is considered that the backup temporary speed limit data on the backup object has failed to be read.

[0033] In this embodiment, outputting interactive error prompts also includes: The message data of failed reading or failed interaction is sent to the train automatic monitoring system, and the train automatic monitoring system marks the corresponding TSR information position as the speed limit loss state output based on the message data of failed reading or failed interaction.

[0034] When the TSR backup information fails to be read or the consistency check fails, a TSR version status message with TSR entry number 0 and CRC0 is sent to the automatic train monitoring system (ATS). The ATS marks the corresponding TSR information location as a speed limit loss state. For example, the original TSR information location can be marked in gray on the station map interface to prompt the operator of the part where reading or interaction failed. The operator can select and reset the speed limit one by one and click Confirm, or directly click to confirm the existing speed limit loss state as the desired operating state. This makes it easier for the operator to intuitively understand the content of the backup interaction error and intervene, thereby improving processing efficiency.

[0035] Step S2 also includes: If the main controller does not receive a version message uploaded by any regional controller within the preset waiting time after restarting, it is considered that the reading has failed and an interactive error prompt is output.

[0036] In this embodiment, determining whether the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted based on the cyclic redundancy check includes: The main controller calculates the backup CRC value based on the backup temporary speed limit data and sends it to the train automatic monitoring system as a field of the TSR status information message; The train automatic monitoring system calculates the original CRC value based on the temporary speed limit data before the main controller is restarted, and compares the backup CRC value with the original CRC value. If they are consistent, it is considered that the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted. If they are inconsistent, it is considered that the backup temporary speed limit data is inconsistent with the temporary speed limit data before the main controller is restarted.

[0037] Cyclic Redundancy Check (CRC) is a technology used to detect errors that may occur after data transmission or storage. By comparing the CRC values ​​of the sending end and the receiving end (or the backup end), the integrity and consistency of the data can be verified. In this embodiment, the direct comparison of the backup temporary speed limit data with the temporary speed limit data before the restart is replaced by the comparison of the backup CRC value and the original CRC value, thereby achieving consistency comparison under the direct interaction between the isolated backup temporary speed limit data and the train automatic monitoring system, and realizing the two-way judgment of whether the speed limit information is reliable between the backup data and the train automatic monitoring system. Only when the two are consistent can the interaction be realized and the backup temporary speed limit data be executed. When there is a problem with either of the two, there will inevitably be a data security problem. At this time, an interactive error prompt is output to facilitate the operator to troubleshoot the problem, which not only ensures the safety of the train system operation but also improves the efficiency of problem troubleshooting.

[0038] Reading the backup temporary rate limit data on the backup object also includes: After the backup temporary speed limit data on the backup object is read, the main controller outputs a refresh command to the backup object, and the backup object is restored from the reading state to the idle state.

[0039] After the main controller TSRS determines that it has received all sub-packets, it responds with a refresh command with a packet index equal to the total number of packets plus one. After receiving this refresh command, the backup object no longer responds to refresh commands and returns its state from the reading state to the idle state. This prevents the backup object from being in the reading state all the time and affecting its own operation.

[0040] like Figure 3 As shown, as the second embodiment of the present application, the temporary speed limit data interaction method based on the remote backup mechanism also includes: S5: After receiving the speed limit confirmation instruction, the main controller switches the state and outputs the TSR version information including the state field to each regional controller; S6: Each regional controller performs CRC information consistency judgment and main controller status confirmation based on the TSR version information, and determines whether information update needs to be performed based on the judgment result and the confirmation result.

[0041] In this embodiment, when an interactive error prompt is output, there is operator intervention. When the operator outputs a speed limit confirmation instruction, the main controller switches the state, and each regional controller determines whether to perform an information update based on the main controller state and the consistency of the CRC information. Therefore, when the operator changes the speed limit information, the backup information in the regional controller can be updated synchronously, avoiding the impact of old information on subsequent backup data retrieval, improving efficiency while ensuring the accuracy of the backup data.

[0042] Specifically, S5 includes: After receiving the speed limit determination instruction, the main controller switches from the initialization state to the working state; Periodically output TSR version information including status field to each regional controller.

[0043] S6 includes: Each regional controller compares the CRC information in the TSR version information with the backup CRC information to determine whether they are consistent; each regional controller confirms whether the main controller is in working state based on the status field in the TSR version information; When the judgment result is inconsistent and the main controller is in the working state, the information is updated.

[0044] In this embodiment, information updates are only performed when the backup CRC information of the temporary speed limit data in each zone controller is inconsistent with the CRC information in the TSR version message output by the master controller and the master controller is in an operational state. This prevents data conflicts, overwriting, or loss that could occur if the system's memory, registers, and other resources are in an unstable state while the master controller is in an initialization state. This ensures system stability and data consistency. It is understood that the master controller can periodically output TSR version information containing a status field to each zone controller in both the initialization and operational states. The zone controllers then determine whether to perform an information update based on the master controller's current status based on the status field.

[0045] In some other embodiments, S6 further includes: When the judgment result is inconsistent, the receiving time exceeds the preset receiving time and the main controller is in the working state, the information update is executed.

[0046] The reception duration is the duration for the regional controller to receive the TSR version information output by the main controller. When the reception times out, it is considered that the reception of all version information has been completed. At this time, if the judgment result is inconsistent and the main controller is in working state, it is considered that the information can and needs to be updated.

[0047] In this embodiment, executing information update includes: Clear all local backup temporary speed limit data of the regional controller; Stop outputting mobile authorization information; Obtain the rate limit update data from the main controller for local backup.

[0048] Assuming that all zone controllers are ZCs with TSRS functions, namely TSRC, after receiving the TSR version information, TSRC determines that the backup CRC information is inconsistent with the CRC information output by TSRS and has timed out, and TSRS is already in working state, then all TSR information of TSRC will be cleared, and mobile authorization information will be stopped from being sent to CBTC trains under its jurisdiction. TSRC sends a refresh command message to TSRS, obtains the speed limit update data replied by TSRS, namely the TSR information after TSRS confirmation, and sets it to execute information update locally. If the TSRS status field in the TSR version information received by TSRC is not in working state, namely the initialization state, it will not be cleared or refreshed, and the original speed limit information will be maintained to continue running. It can be understood that the TSR information after TSRS confirmation comes from the speed limit determination instruction, namely the ATS confirmation command.

[0049] In this embodiment, because multiple TSRCs exist on a line, the system interface uses a session ID field for session management. This means that the TSRS can only respond to a TSR refresh command from one TSRC at a time to ensure consistency in the TSR transmission process. When multiple TSRCs exist, they take turns refreshing and reading from the TSRS, ensuring that all TSRCs maintain consistency with the TSRS information within a certain period of time.

[0050] The regional controller also uses a packetized approach to retrieve speed limit update data from the master controller. The TSRC sends a TSR Refresh Request message to the TSRS. The TSRS then splits the speed limit update data into packets based on the maximum message length and sends a TSR Refresh Response message to the TSRC. Upon receipt, the TSRC sends a TSR Refresh Command message to the TSRS. After the information is updated, the mobile authorization information output is resumed. It should be understood that if the number of packet transmissions exceeds the maximum number of retransmissions and the Refresh Response timer expires, the interaction is considered failed and an interaction error message is output.

[0051] As a third embodiment of the present application, a temporary speed limit data interaction system based on a remote backup mechanism includes: The main controller is used to interact with the automatic train monitoring system to obtain temporary speed limit data; The regional controller is used to interact with the main controller and back up temporary speed limit data for the main controller to read after restart.

[0052] In this embodiment, both the main controller and the regional controller are hardware that already exists in the urban rail CBTC system. The regional controller is used to back up the temporary speed limit data before restart in the main controller, and there is no need to obtain the temporary speed limit data before restart from the automatic train monitoring system. This prevents the ATS from being used as an information source as a non-SIL4 level system, thereby improving the safety of the system. At the same time, there is no need to add additional hardware, such as a data storage library, etc., avoiding an increase in system cost and hardware redundancy.

[0053] In this application, the temporary speed limit information of TSRS (ZC) is stored in other ZCs. When TSRS (main ZC) restarts abnormally, it can request the ZC with good communication status to obtain all the temporary speed limit information of the line. After success, it will be stored in the local storage again. After user confirmation by ATS, the obtained TSR information will continue to be executed, which not only ensures the security of the system, but also reduces the operation complexity of the operator, thereby improving the availability of the system.

[0054] The specific implementation method described above is a preferred implementation method of the temporary speed-limited data interaction method and system based on the off-site backup mechanism of this application, and is not intended to limit the specific implementation scope of this application. The scope of this application includes but is not limited to this specific implementation method. Any equivalent changes made in accordance with the shape and structure of this application are within the scope of protection of this application.

Claims

1. A temporary speed-limited data interaction method based on a remote backup mechanism, characterized in that: The steps include: S1: The main controller establishes communication with each regional controller and backs up and stores the temporary speed limit data to each regional controller based on the off-site backup mechanism; S2: After the main controller is restarted, it receives the version message uploaded by each regional controller within the preset waiting time; S3: The main controller calls the regional controller with the largest version number in the uploaded version message as the backup object; S4: Read the backup temporary speed limit data on the backup object, and determine whether the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted based on the cyclic redundancy check. If so, the main controller stores the backup temporary speed limit data. If not, it is considered that the interaction has failed and an interaction error prompt is output.

2. The temporary speed-limited data interaction method based on the off-site backup mechanism according to claim 1 is characterized in that: The step of reading the backup temporary speed limit data on the backup object further includes: The main controller sends a TSR refresh command message to the backup object, the backup object switches to the read state, the backup object replies with a TSR refresh response message to the main controller, and the main controller reads the backup temporary speed limit data on the backup object.

3. The temporary speed-limited data interaction method based on the off-site backup mechanism according to claim 2 is characterized in that: The backup object replies to the main controller with a TSR refresh response message, which further includes: The backup object packets the backup temporary speed limit data based on the maximum message length to obtain a number of TSR refresh response messages, and the backup object replies the TSR refresh response message to the main controller.

4. The temporary speed-limited data interaction method based on the off-site backup mechanism according to claim 2 is characterized in that: The step of reading the backup temporary speed limit data on the backup object further includes: Based on the reading time threshold, determine whether the backup temporary speed limit data on the backup object within the reading time threshold is read. If so, it is considered that the reading is successful. If not, it is considered that the reading fails and an interactive error prompt is output.

5. The temporary speed-limited data interaction method based on the off-site backup mechanism according to claim 4 is characterized in that: The output interactive error prompt also includes: The message data of failed reading or failed interaction is sent to the train automatic monitoring system, and the train automatic monitoring system marks the corresponding TSR information position as the speed limit loss state output according to the message data of failed reading or failed interaction.

6. The temporary speed-limited data interaction method based on the off-site backup mechanism according to claim 1 is characterized in that: The method of judging whether the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted based on the cyclic redundancy check includes: The main controller calculates the backup CRC value based on the backup temporary speed limit data and sends it to the train automatic monitoring system as a field of the TSR status information message; The train automatic monitoring system calculates the original CRC value based on the temporary speed limit data before the main controller is restarted, and compares the backup CRC value and the original CRC value. If they are consistent, it is considered that the backup temporary speed limit data is consistent with the temporary speed limit data before the main controller is restarted; if they are inconsistent, it is considered that the backup temporary speed limit data is inconsistent with the temporary speed limit data before the main controller is restarted.

7. The temporary speed-limited data interaction method based on a remote backup mechanism according to claim 1, characterized in that: Also includes: S5: After receiving the speed limit determination instruction, the main controller switches the state and outputs the TSR version information including the state field to each regional controller; S6: Each regional controller performs CRC information consistency judgment and main controller status confirmation according to the TSR version information, and determines whether information update needs to be performed according to the judgment result and confirmation result.

8. The temporary speed-limited data interaction method based on the off-site backup mechanism according to claim 7 is characterized in that: The S5 includes: After receiving the speed limit determination instruction, the main controller switches from the initialization state to the working state; Periodically output TSR version information including status field to each zone controller.

9. The temporary speed-limited data interaction method based on a remote backup mechanism according to claim 7, characterized in that: The S6 includes: Each regional controller compares the CRC information in the TSR version information with the backup CRC information to determine whether they are consistent; each regional controller confirms whether the main controller is in working state according to the status field in the TSR version information; When the judgment result is inconsistent and the main controller is in working state, the information is updated.

10. A temporary speed limit data interaction system based on a remote backup mechanism, used to implement the method according to any one of claims 1 to 9, characterized in that: include: A main controller, used to interact with the automatic train monitoring system to obtain temporary speed limit data; The regional controller is used to interact with the main controller and back up temporary speed limit data for the main controller to read after restart.

Images