Vehicle control method, device and system based on trackside faults, vehicle and equipment

By receiving and processing rail-side monitoring data and automatically controlling vehicle braking, the problem of drivers being unable to brake in time when rail-side equipment fails, and improving the safety and operation efficiency of urban rail transit.

CN119058612APending Publication Date: 2024-12-03BEIJING URBAN CONSTR INTELLIGENT CONTROL TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411130863.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-16
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In urban rail transit, when the equipment on the rail is malfunctioning, the driver is unable to brake in time, causing the vehicle to enter the faulty area, which poses a safety risk.

Method used

By receiving rail-side monitoring data, processing fault data, determining braking data based on vehicle type and faulty equipment information, and automatically controlling vehicle braking to ensure that the vehicle stops before the faulty equipment or waits for the faulty equipment to return to normal before passing.

Benefits of technology

It improves the safety and efficiency of vehicle operation, avoids safety risks caused by equipment failure on the rail, and reduces the dependence on driver response time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119058612A_ABST
    Figure CN119058612A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of fault detection, and discloses a vehicle control method, device and system based on trackside faults, a vehicle and equipment. The method comprises the following steps: firstly, receiving trackside monitoring data obtained by monitoring the running state of at least one trackside device; then, processing the trackside monitoring data to obtain fault data representing the fault condition of the trackside equipment; then, if the fault data indicates that there is a faulty device in the at least one trackside device, brake data of the vehicle is determined based on the type of the vehicle and device information of the faulty device. And finally, braking the vehicle based on the braking data. Through trackside monitoring data, the operation state of trackside equipment is monitored in real time, and whether fault equipment exists in a route or not is known in time. Under the condition that the fault equipment exists, a driver does not need to wait for controlling vehicle operation, the braking data of the vehicle is determined based on the type of the vehicle and the equipment information of the fault equipment to achieve vehicle braking, the operation efficiency is improved, and meanwhile risks are avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of fault detection, and in particular to a vehicle control method, device, system, vehicle and equipment based on trackside faults. Background Art

[0002] With the development of urban rail transit technology, the fully automatic operation system has become the development direction of urban rail transit technology. However, after the vehicle fault is downgraded and the communication with the regional controller is interrupted, the trackside equipment fails and the vehicle operation needs to be controlled.

[0003] In the related art, when a trackside device fails, the driver controls the vehicle to run. However, after the vehicle enters the approach section, if a trackside device fails, the driver cannot brake in time, causing the vehicle to enter the fault area, posing a safety risk. Therefore, it is necessary to propose a vehicle control method based on trackside failure. Summary of the invention

[0004] The embodiments of this specification are intended to solve at least one of the technical problems in the related art to a certain extent. To this end, the embodiments of this specification propose a vehicle control method, device, system, vehicle and equipment based on trackside faults.

[0005] The embodiments of this specification provide a vehicle control method based on a trackside fault, the method comprising:

[0006] Receiving trackside monitoring data, wherein the trackside monitoring data is data obtained by monitoring the operating status of at least one trackside device;

[0007] Processing the trackside monitoring data to obtain fault data characterizing a fault condition of the trackside equipment;

[0008] In a case where the fault data indicates that a faulty device exists in the at least one trackside device, determining the braking data of the vehicle based on the type of the vehicle and the device information of the faulty device;

[0009] The vehicle is braked based on the braking data.

[0010] In one embodiment, the device information of the faulty device includes a device type and a device location; and when the fault data indicates that a faulty device exists in the at least one trackside device, determining the braking data of the vehicle based on the type of the vehicle and the device information of the faulty device includes:

[0011] In the case where the type of the vehicle and the device type of the faulty device have an associated relationship, determining a braking distance between the vehicle and the faulty device based on the device position of the faulty device, wherein the associated relationship indicates that the vehicle needs to brake based on the faulty device;

[0012] Braking data of the vehicle is determined based on the braking distance and the driving speed of the vehicle.

[0013] In one embodiment, there are multiple faulty devices, and determining the braking distance between the vehicle and the faulty devices based on the device positions of the faulty devices includes:

[0014] Based on the device locations of the plurality of the faulty devices, determining the nearest faulty device from the plurality of the faulty devices;

[0015] The distance data between the vehicle and the nearest faulty device is determined as a braking distance based on the device position of the nearest faulty device.

[0016] In one embodiment, the determining the braking data of the vehicle based on the type of the vehicle and the device information of the faulty device includes:

[0017] generating emergency brake data based on an activation instruction of the emergency stop button when the type of the vehicle indicates that the vehicle is a non-communication vehicle and the device type of the faulty device indicates that the faulty device is an emergency stop button;

[0018] Based on the emergency brake data, brake data of the vehicle is determined.

[0019] In one embodiment, braking the vehicle based on the braking data includes:

[0020] Based on the braking data, controlling the vehicle to stop running in front of the faulty device; or,

[0021] Based on the braking data, the vehicle is controlled to pass through the faulty device after the faulty device returns to normal.

[0022] In one embodiment, the trackside monitoring data includes at least one of turnout status data, signal status data, axle counting section status data, platform shield door status data, emergency stop button status data, and area blocking button status data.

[0023] In one embodiment, the fault data includes at least one of switch loss indication, signal closure, axle counting section occupancy, platform shield door opening, emergency stop button activated, and area blocking button activated.

[0024] In one embodiment, when the type of the vehicle indicates that the vehicle is a non-communication vehicle; the fault data indicates that there is a faulty device in the at least one trackside device, including at least one of the following situations:

[0025] The fault data is a turnout failure indication, indicating that the turnout is the faulty device;

[0026] The fault data is that the signal is closed, indicating that the signal is the faulty device;

[0027] The fault data is the occupation of the axle counting section, indicating that the axle counting section is the faulty device;

[0028] The fault data is that the shielding door is open, indicating that the shielding door is the faulty device;

[0029] The fault data is that the emergency stop button has been activated, indicating that the emergency stop button is the faulty device;

[0030] The fault data is that the area blocking button has been activated, indicating that the area blocking button is the faulty device.

[0031] In one embodiment, when the type of the vehicle indicates that the vehicle is a communication vehicle; the fault data indicates that there is a faulty device in the at least one trackside device, including at least one of the following situations:

[0032] The fault data is a turnout failure indication, indicating that the turnout is the faulty device;

[0033] The fault data is that the signal is closed, indicating that the signal is the faulty device;

[0034] The fault data is the occupation of the axle counting section, indicating that the axle counting section is the faulty device;

[0035] The fault data is that the area blocking button has been activated, indicating that the area blocking button is the faulty device.

[0036] In one embodiment, the method further comprises:

[0037] Based on the faulty device, displaying device information of the faulty device on a train status display; or

[0038] A voice alarm is issued based on the device information of the faulty device.

[0039] The embodiments of this specification provide a vehicle control device based on trackside faults, the device comprising:

[0040] A trackside monitoring data receiving module, used to receive trackside monitoring data, wherein the trackside monitoring data is data obtained by monitoring the operating status of at least one trackside device;

[0041] a fault data determination module, configured to process the trackside monitoring data to obtain fault data characterizing a fault condition of the trackside equipment;

[0042] a braking data determination module, configured to determine braking data of the vehicle based on the type of the vehicle and the device information of the faulty device when the fault data indicates that there is a faulty device in the at least one trackside device;

[0043] A vehicle braking module is used to brake the vehicle based on the braking data.

[0044] The embodiments of this specification provide a vehicle control system based on trackside faults, the system comprising:

[0045] A trackside status module, used to monitor the operating status of at least one trackside device to obtain trackside monitoring data, and send the trackside monitoring data to the automatic protection system of the vehicle;

[0046] An automatic protection system for a vehicle, used to implement the method described in any one of the above items.

[0047] An embodiment of the present specification provides a vehicle, which is used to implement any of the methods described above.

[0048] An embodiment of the present specification provides a computer device, a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the method described in any of the above embodiments are implemented.

[0049] The embodiments of this specification provide a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method described in any of the above embodiments are implemented.

[0050] An embodiment of the present specification provides a computer program product, wherein the computer program product includes instructions, and when the instructions are executed by a processor of a computer device, the computer device is enabled to perform the steps of the method described in any one of the above embodiments.

[0051] In the implementation manner of the above specification, first, trackside monitoring data obtained by monitoring the operating status of at least one trackside device is received. Next, the trackside monitoring data is processed to obtain fault data characterizing the fault condition of the trackside device. Then, in the case where the fault data indicates that there is a faulty device in at least one trackside device, the braking data of the vehicle is determined based on the type of vehicle and the equipment information of the faulty device. Finally, based on the braking data, the vehicle is braked. Through the trackside monitoring data, the operating status of the trackside equipment is monitored in real time, and it is timely known whether there is a faulty device in the route. In the case where there is a faulty device in at least one trackside device, there is no need to wait for the driver to control the operation of the vehicle. The braking data of the vehicle is determined based on the type of vehicle and the equipment information of the faulty device to achieve braking of the vehicle, thereby improving operating efficiency while avoiding risks. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 A flow chart of a vehicle control method based on trackside faults provided in an embodiment of this specification;

[0053] Figure 2 A flow chart of a vehicle control method based on trackside faults provided in an embodiment of this specification;

[0054] Figure 3 A schematic diagram of a process for determining the braking data of a vehicle provided in an embodiment of this specification;

[0055] Figure 4 A schematic diagram of a process for determining braking distance provided in an embodiment of this specification;

[0056] Figure 5 A schematic diagram of a process for determining the braking data of a vehicle provided in an embodiment of this specification;

[0057] Figure 6 A schematic diagram of a vehicle control device based on a trackside fault provided in an embodiment of this specification;

[0058] Figure 7 A schematic diagram of the internal structure of a computer device provided for an embodiment of this specification. DETAILED DESCRIPTION

[0059] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present invention, and should not be construed as limiting the present invention.

[0060] With the continuous development of urban rail transit technology and the increasing demand for urban rail transit carrying capacity, the fully automatic operation system has become the main development direction of urban rail transit technology to further improve the safety and efficiency of urban rail transit operation systems. However, if the trackside equipment suddenly fails after the vehicle fails and degrades or the communication with the regional controller is interrupted, the vehicle operation strategy needs to be improved.

[0061] In the related technology, when a fault occurs in the trackside equipment, the driver gets on the train and drives the train according to visual signals, and interlocking is used to open the signal and lock the switch to ensure safe operation.

[0062] However, after the vehicle enters the approach section, if the trackside equipment fails and the driver is unable to brake in time, the vehicle may enter the fault area, posing a safety risk.

[0063] Based on the above analysis, the implementation method of this specification provides a vehicle control method based on trackside faults. First, trackside monitoring data obtained by monitoring the operating status of at least one trackside device is received. Next, the trackside monitoring data is processed to obtain fault data characterizing the fault condition of the trackside device. Then, when the fault data indicates that there is a faulty device in at least one trackside device, the braking data of the vehicle is determined based on the type of vehicle and the equipment information of the faulty device. Finally, based on the braking data, the vehicle is braked. Through the trackside monitoring data, the operating status of the trackside equipment is monitored in real time, and it is timely understood whether there is a faulty device in the route. In the case that there is a faulty device in at least one trackside device, there is no need to wait for the driver to control the operation of the vehicle. The braking data of the vehicle is determined based on the type of vehicle and the equipment information of the faulty device to achieve braking of the vehicle, thereby improving operating efficiency while avoiding risks.

[0064] The locking state control method of the axle counting section provided in the embodiments of this specification can be applied to the trackside state module and the automatic protection system of the vehicle, please refer to Figure 1 The trackside equipment includes turnouts, signal machines, axle counting sections, platform shield doors, emergency stop buttons (ESB buttons), and area blocking buttons (SPKS). The trackside status module monitors the operating status of the trackside equipment, obtains trackside monitoring data including turnout status data, signal machine status data, axle counting section status data, platform shield door status data, emergency stop button status data, and area blocking button status data, and sends the trackside monitoring data to the vehicle's automatic protection system through redundant network communication. The vehicle's automatic protection system processes the trackside monitoring data to obtain fault data that characterizes the fault conditions of the trackside equipment.

[0065] It should be noted that, when the type of the vehicle indicates that the vehicle is a non-communication vehicle, the faulty device is determined to be at least one of a switch, a signal, an axle counting section, a screen door, an emergency stop button, and an area blocking button based on the fault data. When the type of the vehicle indicates that the vehicle is a communication vehicle, the faulty device is determined to be at least one of a switch, a signal, an axle counting section, and an area blocking button based on the fault data.

[0066] When the vehicle type indicates that the vehicle is a non-communication vehicle and the device type of the faulty device indicates that the faulty device is an emergency stop button, emergency braking data is generated based on a start instruction of the emergency stop button, and then the vehicle is braked based on the braking data.

[0067] Except for the case where the vehicle type indicates that the vehicle is a non-communication vehicle and the device type of the faulty device indicates that the faulty device is an emergency stop button, in other cases, the braking distance between the vehicle and the faulty device is determined based on the device position of the faulty device, and the braking data of the vehicle is determined based on the braking distance and the vehicle's driving speed, and then the vehicle is braked based on the braking data.

[0068] This specification provides a vehicle control method based on trackside faults. Figure 2 , the vehicle control method based on trackside fault may include the following steps:

[0069] S210, receiving trackside monitoring data.

[0070] S220: Process the trackside monitoring data to obtain fault data representing the fault condition of the trackside equipment.

[0071] S230: When the fault data indicates that there is a faulty device in at least one trackside device, determine the braking data of the vehicle based on the type of the vehicle and the device information of the faulty device.

[0072] S240: Braking the vehicle based on the braking data.

[0073] Trackside monitoring data refers to data obtained by monitoring the operating status of at least one trackside device, and may include normal status data and fault status data of the trackside device. Braking data may be relevant parameters and information for braking the vehicle. Trackside devices may be devices along the track, used to provide information to the vehicle to maintain safe operation of the vehicle.

[0074] Specifically, the operating status of at least one trackside device is monitored and relevant monitoring data is obtained to obtain trackside monitoring data. The trackside monitoring data is received, and data processing and analysis are performed on it to determine whether there is data describing the existence of a fault in the trackside device in the received trackside monitoring data, and the data describing the existence of a fault in the trackside device is used as fault data characterizing the fault condition of the trackside device. In the case where the fault data indicates that there is a faulty device in at least one trackside device, the response strategies corresponding to different vehicle types and different faulty devices are different. For example, when the vehicle is a communication vehicle and the device type of the faulty device indicates that the faulty device is a turnout, the vehicle needs to be braked, and when the vehicle is a non-communication vehicle and the device type of the faulty device indicates that the faulty device is an emergency stop button, the vehicle needs to be emergency braked. Therefore, the braking data of the vehicle is determined based on the type of vehicle and the device information of the faulty device. The braking data will be used to control the vehicle's travel speed in order to ensure the safety of passengers and vehicles.

[0075] In the above-mentioned implementation, first, trackside monitoring data obtained by monitoring the operating status of at least one trackside device is received. Next, the trackside monitoring data is processed to obtain fault data characterizing the fault condition of the trackside device. Then, in the case where the fault data indicates that there is a faulty device in at least one trackside device, the braking data of the vehicle is determined based on the type of vehicle and the equipment information of the faulty device. Finally, the vehicle is braked based on the braking data. Through the trackside monitoring data, the operating status of the trackside equipment is monitored in real time, and it is timely known whether there is a faulty device in the route. In the case where there is a faulty device in at least one trackside device, there is no need to wait for the driver to control the operation of the vehicle. The braking data of the vehicle is determined based on the type of vehicle and the equipment information of the faulty device to achieve braking of the vehicle, thereby improving operating efficiency and avoiding risks.

[0076] In some embodiments, see Figure 3 The equipment information of the faulty equipment includes the equipment type and the equipment location. When the fault data indicates that there is a faulty equipment in at least one trackside equipment, determining the braking data of the vehicle based on the type of the vehicle and the equipment information of the faulty equipment may include the following steps:

[0077] S310: When the type of the vehicle and the type of the faulty device are associated with each other, determine a braking distance between the vehicle and the faulty device based on the device position of the faulty device.

[0078] S320: Determine braking data of the vehicle based on the braking distance and the driving speed of the vehicle.

[0079] Among them, the association relationship indicates that the vehicle needs to brake based on the faulty equipment.

[0080] Specifically, different types of vehicles and different types of faulty equipment have different corresponding response strategies. By analyzing different types of vehicles and different types of faulty equipment, it is determined which specific types of vehicles need to brake the vehicle when encountering a specific type of faulty equipment, thereby establishing an association relationship. Therefore, when the type of vehicle and the device type of the faulty equipment have an association relationship, it means that the vehicle needs to be braked. According to the device position of the faulty equipment, the distance data between the faulty equipment and the vehicle is calculated and used as the braking distance. The speed curve is calculated based on the braking distance and the current driving speed of the vehicle to determine the braking data of the vehicle. The braking data will be used to control the driving speed of the vehicle to ensure the safety of passengers and vehicles.

[0081] In the above implementation, when the type of vehicle and the device type of the faulty device are associated with each other, the braking distance between the vehicle and the faulty device is determined based on the device position of the faulty device, and the braking data of the vehicle is determined based on the braking distance and the driving speed of the vehicle, thereby improving the driving safety of the vehicle.

[0082] In some embodiments, see Figure 4 There are multiple faulty devices, and determining the braking distance between the vehicle and the faulty device based on the device positions of the faulty devices may include the following steps:

[0083] S410: Determine a nearest faulty device from among the multiple faulty devices based on the device locations of the multiple faulty devices.

[0084] S420: Determine the distance data between the vehicle and the nearest faulty device as the braking distance based on the device position of the nearest faulty device.

[0085] Specifically, when there are multiple faulty devices in front of the vehicle, in order to ensure that the vehicle can take timely measures, it is necessary to determine the faulty device closest to the vehicle so as to determine the corresponding braking distance. By comparing the device positions of each faulty device, the faulty device closest to the vehicle is determined as the nearest faulty device. Based on the device position of the nearest faulty device, the distance data between the nearest faulty device and the vehicle is calculated and used as the braking distance.

[0086] In other embodiments, the distance data between each faulty device and the vehicle is calculated based on the device position of each faulty device. The distance data between each faulty device and the vehicle is compared, and then the minimum distance data is determined therefrom. The faulty device corresponding to the minimum distance data is determined as the nearest faulty device and the minimum distance data is used as the braking distance.

[0087] In the above implementation, based on the device positions of multiple faulty devices, the nearest faulty device is determined from the multiple faulty devices, and based on the device position of the nearest faulty device, the distance data between the vehicle and the nearest faulty device is determined as the braking distance, providing a data basis for subsequent determination of braking data.

[0088] In some embodiments, see Figure 5 , determining the braking data of the vehicle based on the type of the vehicle and the equipment information of the faulty equipment may include the following steps:

[0089] S510. When the type of the vehicle indicates that the vehicle is a non-communication vehicle and the device type of the faulty device indicates that the faulty device is an emergency stop button, emergency braking data is generated based on a start command of the emergency stop button.

[0090] S520: Determine the braking data of the vehicle based on the emergency braking data.

[0091] Among them, the emergency braking data may be data related to the emergency braking process generated after receiving a start command from an emergency stop button. The emergency braking data may include vehicle speed and acceleration, application of braking force, and the like.

[0092] Specifically, when the type of vehicle indicates that the vehicle is a non-communication vehicle, the fact that the emergency stop button has been activated can be used as fault data, thereby determining that the emergency stop button is a faulty device. The emergency stop button is pressed, and a start command for the emergency stop button is generated, indicating that the emergency stop button has been activated. When it is determined that the emergency stop button has been activated, the vehicle data, such as the vehicle's speed, position and other information, is recorded, and then subsequent data processing is performed based on the recorded information to determine the emergency braking data for emergency braking of the vehicle. The emergency braking data is used as braking data for controlling vehicle braking, that is, the emergency braking data will be used to control the vehicle's driving speed, causing it to gradually slow down until the vehicle speed drops to zero, to ensure that in an emergency, the vehicle can stop safely and protect the safety of passengers and vehicles.

[0093] In the above embodiment, when the type of vehicle indicates that the vehicle is a non-communication vehicle and the device type of the faulty device indicates that the faulty device is an emergency stop button, emergency braking data is generated based on the start instruction of the emergency stop button, and the braking data of the vehicle is determined based on the emergency braking data to improve the safety of vehicle driving.

[0094] In some embodiments, braking the vehicle based on the braking data may include: controlling the vehicle to stop running before a faulty device based on the braking data.

[0095] Specifically, because there is a faulty device in front of the vehicle, the vehicle cannot pass through the faulty device to maintain the safety of the vehicle. Therefore, after the faulty device is determined, the vehicle's driving speed is controlled using braking data to gradually decelerate the vehicle until the speed drops to zero and the vehicle stops in front of the faulty device. This ensures that the vehicle will not mistakenly enter the section of the faulty device during the repair of the faulty device, thereby maintaining the safety of the vehicle and passengers.

[0096] In the above implementation, based on the braking data, the vehicle is controlled to stop running before the faulty equipment, thereby improving the safety of the vehicle.

[0097] In some embodiments, braking the vehicle based on the braking data may include: controlling the vehicle to pass through the faulty device after the faulty device returns to normal based on the braking data.

[0098] Specifically, when there is a faulty device in front of the vehicle, it is necessary to wait for the faulty device to be repaired before continuing to pass. Therefore, after the faulty device is determined, the vehicle's driving speed is controlled using braking data to gradually decelerate the vehicle. During the vehicle's braking and deceleration process, the faulty device is repaired, and the vehicle cannot pass the faulty device before the faulty device is repaired. After the faulty device returns to normal, the vehicle is gradually accelerated to pass through the section where the faulty device has been repaired.

[0099] In the above implementation, based on the braking data, the vehicle is controlled to use the faulty equipment after the faulty equipment returns to normal, thereby reducing the delay of vehicle operation and improving the operation efficiency.

[0100] In some embodiments, the trackside monitoring data includes at least one of turnout status data, signal status data, axle counting section status data, platform shield door status data, emergency stop button status data, and area blocking button status data.

[0101] Specifically, the turnout guides the direction of vehicle travel by switching and switching. For example, the turnout is in a normal position and can smoothly switch the direction of vehicle travel. When the turnout is faulty, it is necessary to repair the fault and control the vehicle brake to maintain the safety of the vehicle. Therefore, the turnout status data is used as trackside monitoring data to determine whether the turnout is a faulty device.

[0102] Signals are used to guide and control the operation of vehicles to ensure the safety and smoothness of rail transit. When a signal fails, it is necessary to repair the fault and control the vehicle brakes to maintain the safety of the vehicle. Therefore, the signal status data is used as trackside monitoring data to determine whether the signal is a faulty device.

[0103] The axle counter section is used for vehicles to pass through. When there is a fault in the axle counter section, it will cause danger when the vehicle is running. Therefore, the axle counter section status data is used as trackside monitoring data to determine whether the axle counter section is a faulty device.

[0104] The function of the platform screen door is to ensure that passengers do not mistakenly enter the track area when entering or leaving the platform when the vehicle enters the station, thereby reducing the risk of accidents. Therefore, the platform screen door status data is used as trackside monitoring data to determine whether the platform screen door is a faulty device.

[0105] When an emergency occurs, the emergency stop button is used to control the vehicle to avoid danger. Therefore, the emergency stop button status data is used as trackside monitoring data to determine whether the emergency stop button is a faulty device.

[0106] The area blocking button is used to restrict or prohibit vehicles from entering a specific area, thereby reducing the risk of accidents. Therefore, the area blocking button status data is used as trackside monitoring data to determine whether the area blocking button is a faulty device.

[0107] In the above implementation, the trackside monitoring data includes at least one of the switch status data, signal status data, axle counting section status data, platform shield door status data, emergency stop button status data, and area blockade button status data to provide a data basis for subsequent determination of faulty equipment.

[0108] In some embodiments, the fault data includes at least one of switch loss indication, signal closure, axle counting section occupancy, platform shield door opening, emergency stop button activated, and area blocking button activated.

[0109] Specifically, among the various position states of the turnout, the switch failure indication means that the turnout cannot switch or shunt normally, that is, there is a fault in the turnout, so the switch failure indication is used as fault data. When the signal is closed, it will affect rail transit and driving safety is threatened, so the signal closure is used as fault data. The axle counting section occupation means that the axle counting section does not allow vehicles to enter, affecting the safe driving of the vehicle, so the axle counting section occupation is used as fault data to prevent vehicles from entering and maintain the safety of vehicle driving. When the vehicle has not reached the platform screen door and the platform screen door is open, it will increase the safety risk of passengers, so the platform screen door opening is used as fault data. The emergency stop button has been activated, which means that there is an emergency in front of the vehicle, so the emergency stop button has been activated as fault data. The area blocking button has been activated, which means that the control area is in a blocked state, which means that there is an emergency in front of the vehicle, so the area blocking button has been activated as fault data.

[0110] In the above implementation, the fault data includes at least one of the following: switch loss indication, signal closure, axle counting section occupancy, shield door opening, emergency stop button activated, and area blockade button activated, providing a data basis for subsequent determination of the faulty equipment.

[0111] In some embodiments, when the type of vehicle indicates that the vehicle is a non-communication vehicle or when the type of vehicle indicates that the vehicle is a communication vehicle, the fault data indicates that there is a faulty device in at least one trackside device, including: the fault data is indicated as a switch failure, indicating that the switch is a faulty device.

[0112] Specifically, the turnout is used to control the direction of travel of the vehicle, and its position state is independent of the type of vehicle. Therefore, regardless of whether the vehicle type is a non-communication vehicle or a communication vehicle, the same processing strategy will be adopted for the turnout loss indication. That is, when the fault data is determined to be the turnout loss indication, it is directly and clearly indicated that the turnout is a faulty device, regardless of the vehicle type. Among them, the position state of the turnout can include the turnout positive position, the turnout reverse position, etc.

[0113] In the above implementation manner, the fault data is a switch failure indication, indicating that the switch is a faulty device, which provides a basis for subsequently determining the braking data for controlling the vehicle braking.

[0114] In some embodiments, when the type of vehicle indicates that the vehicle is a non-communication vehicle or when the type of vehicle indicates that the vehicle is a communication vehicle, the fault data indicates that there is a faulty device in at least one trackside device, including: the fault data is that the signal is closed, indicating that the signal is a faulty device.

[0115] Specifically, the signal is used to guide and control the operation of vehicles, and its working state is independent of the type of vehicle. Therefore, regardless of whether the vehicle type is a non-communication vehicle or a communication vehicle, the same processing strategy will be adopted when the signal is closed. That is, when the fault data is determined to be the signal closed, it is directly and clearly stated that the signal is a faulty device, regardless of the vehicle type. Among them, the working state of the signal can be the signal is in the open state or the signal is in the closed state.

[0116] In the above implementation manner, the fault data is that the signal is closed, indicating that the signal is a faulty device, which provides a basis for subsequently determining the braking data for controlling the braking of the vehicle.

[0117] In some embodiments, when the type of vehicle indicates that the vehicle is a non-communication vehicle or when the type of vehicle indicates that the vehicle is a communication vehicle, the fault data indicates that there is a faulty device in at least one trackside device, including: the fault data is an axle counting section occupancy, indicating that the axle counting section is a faulty device.

[0118] Specifically, the axle counter section is used to manage the passage of vehicles, and its usage status information is independent of the type of vehicle. Therefore, regardless of whether the type of vehicle is a non-communication vehicle or a communication vehicle, the axle counter section occupation will adopt the same processing strategy. That is, when the fault data is determined to be the axle counter section occupation, it is directly and clearly stated that the axle counter section is a faulty device, regardless of the vehicle type. Among them, the usage status information of the axle counter section can be that the axle counter section is occupied or that the axle counter section is in an idle state.

[0119] In the above implementation, the fault data is the occupancy of the axle counter section, indicating that the axle counter section is a faulty device, which provides a basis for subsequently determining the braking data for controlling the vehicle braking.

[0120] In some embodiments, when the type of vehicle indicates that the vehicle is a non-communication vehicle or when the type of vehicle indicates that the vehicle is a communication vehicle, the fault data indicates that there is a faulty device in at least one trackside device, including: the fault data is that the area blocking button has been activated, indicating that the area blocking button is a faulty device.

[0121] Specifically, the function of the area blocking button has nothing to do with the type of vehicle, and its role is to control the blocking state of the area. Therefore, regardless of whether the vehicle type is a non-communication vehicle or a communication vehicle, the same processing strategy will be adopted. That is, when it is determined that the fault data is that the area blocking button has been activated, it is directly and clearly stated that the area blocking button is a faulty device, regardless of the vehicle type.

[0122] In the above implementation, the fault data is that the area blocking button has been activated, indicating that the area blocking button is a faulty device, which provides a basis for subsequently determining the braking data for controlling the vehicle braking.

[0123] In some embodiments, when the type of vehicle indicates that the vehicle is a non-communication vehicle, the fault data indicates that there is a faulty device in at least one trackside device, including: the fault data is that the platform screen door is open, indicating that the platform screen door is a faulty device.

[0124] Specifically, the trackside monitoring data is processed to obtain the fault data of the platform shield door opening. When confirming the faulty equipment, there are differences in the fault determination of different types of vehicles. Therefore, different response strategies are adopted for different types of vehicles. When the vehicle type is indicated as a non-communication vehicle, the fault data of the platform shield door opening can clearly indicate that the platform shield door is a faulty device. When the vehicle type is indicated as a communication vehicle, even if the platform shield door is opened, the fault data is not used to indicate that the platform shield door is faulty, that is, the platform shield door is not regarded as a faulty device and the vehicle operates normally.

[0125] In the above implementation manner, the fault data is that the shield door is open, indicating that the shield door is a faulty device, which provides a basis for subsequently determining the braking data for controlling the braking of the vehicle.

[0126] In some embodiments, when the type of vehicle indicates that the vehicle is a non-communication vehicle, the fault data indicates that there is a faulty device in at least one trackside device, including: the fault data is that the emergency stop button has been activated, indicating that the emergency stop button is a faulty device.

[0127] Specifically, the trackside monitoring data is processed to obtain fault data that the emergency stop button has been activated. When confirming the faulty equipment, there are differences in the fault determination of different types of vehicles. Therefore, different response strategies are adopted for different types of vehicles. When the vehicle type is indicated as a non-communication vehicle, the fault data that the emergency stop button has been activated can clearly indicate that the emergency stop button is a faulty device. When the vehicle type is indicated as a communication vehicle, even if the emergency stop button has been activated, the fault data is not used to indicate that there is a fault in the emergency stop button, that is, the emergency stop button is not a faulty device and the vehicle operates normally.

[0128] In the above implementation, the fault data is that the emergency stop button has been activated, indicating that the emergency stop button is a faulty device, which provides a basis for subsequently determining the braking data for controlling the vehicle braking.

[0129] In some embodiments, the method may further include: based on the faulty device, displaying device information of the faulty device on a train status display.

[0130] Specifically, when there is a faulty device, the train status display will display the equipment information of the faulty device, such as the name of the faulty device, the fault type, the location, etc., so that the operator can immediately understand the information of the faulty device and quickly solve the corresponding problem.

[0131] In the above implementation, the equipment information of the faulty equipment is displayed on the train status display so that corresponding measures can be taken in time to handle the problem.

[0132] In some implementations, the method may further include: issuing a voice alarm based on device information of the faulty device.

[0133] Specifically, the voice alarm method can emphasize the importance of the equipment failure, thereby attracting higher attention and response levels. Therefore, according to the equipment information of the faulty equipment, appropriate voice content is selected to convey the fault information related to the faulty equipment. For example, the voice content can include warnings, error descriptions, recommended operations, etc.

[0134] In the above implementation, a voice alarm is issued based on the device information of the faulty device so that corresponding measures can be taken in time.

[0135] The embodiment of this specification provides a vehicle control device 600 based on trackside faults, please refer to Figure 6The vehicle control device 600 based on trackside faults includes: a trackside monitoring data receiving module 610, a fault data determination module 620, a braking data determination module 630, and a vehicle braking module 640.

[0136] A trackside monitoring data receiving module 610 is used to receive trackside monitoring data, wherein the trackside monitoring data is data obtained by monitoring the operating status of at least one trackside device;

[0137] A fault data determination module 620 is used to process the trackside monitoring data to obtain fault data representing the fault condition of the trackside equipment;

[0138] a braking data determination module 630, configured to determine braking data of the vehicle based on the type of the vehicle and the device information of the faulty device when the fault data indicates that there is a faulty device in the at least one trackside device;

[0139] The vehicle braking module 640 is used to brake the vehicle based on the braking data.

[0140] For a detailed description of the vehicle control device based on trackside faults, please refer to the description of the vehicle control method based on trackside faults above, which will not be repeated here.

[0141] The embodiments of this specification provide a vehicle control system based on trackside faults, the system comprising:

[0142] A trackside status module, used to monitor the operating status of at least one trackside device to obtain trackside monitoring data, and send the trackside monitoring data to the automatic protection system of the vehicle;

[0143] An automatic protection system for a vehicle, used to implement the method according to any one of the above-mentioned embodiments.

[0144] An embodiment of the present specification provides a vehicle, and the vehicle is used to implement the method described in any one of the above embodiments.

[0145] In some embodiments, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 7As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a vehicle control method based on trackside faults is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0146] Those skilled in the art will understand that Figure 7 The structure shown in the figure is merely a block diagram of a portion of the structure related to the solution disclosed in this specification, and does not constitute a limitation on the computer device to which the solution disclosed in this specification is applied. Specifically, the computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0147] An embodiment of the present specification provides a computer device, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the method steps in the above embodiment are implemented.

[0148] An embodiment of the present specification provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method in any of the above embodiments are implemented.

[0149] The embodiments of this specification provide a computer program product, which includes instructions. When the instructions are executed by a processor of a computer device, the computer device can perform the steps of any method of the above embodiments.

[0150] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection portion with one or more wirings (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or otherwise processing in a suitable manner if necessary, and then stored in a computer memory.

Claims

1. A vehicle control method based on trackside faults, characterized in that: The method comprises: Receiving trackside monitoring data, wherein the trackside monitoring data is data obtained by monitoring the operating status of at least one trackside device; Processing the trackside monitoring data to obtain fault data characterizing a fault condition of the trackside equipment; In a case where the fault data indicates that a faulty device exists in the at least one trackside device, determining the braking data of the vehicle based on the type of the vehicle and the device information of the faulty device; The vehicle is braked based on the braking data.

2. The method according to claim 1, characterized in that The device information of the faulty device includes a device type and a device location; when the fault data indicates that a faulty device exists in the at least one trackside device, determining the braking data of the vehicle based on the type of the vehicle and the device information of the faulty device includes: In the case where the type of the vehicle and the device type of the faulty device have an associated relationship, determining a braking distance between the vehicle and the faulty device based on the device position of the faulty device, wherein the associated relationship indicates that the vehicle needs to brake based on the faulty device; Braking data of the vehicle is determined based on the braking distance and the driving speed of the vehicle.

3. The method according to claim 2, characterized in that There are multiple faulty devices, and determining the braking distance between the vehicle and the faulty devices based on the device positions of the faulty devices includes: Based on the device locations of the plurality of the faulty devices, determining the nearest faulty device from the plurality of the faulty devices; The distance data between the vehicle and the nearest faulty device is determined as a braking distance based on the device position of the nearest faulty device.

4. The method according to claim 1, characterized in that: The determining the braking data of the vehicle based on the type of the vehicle and the equipment information of the faulty equipment includes: generating emergency brake data based on an activation instruction of the emergency stop button when the type of the vehicle indicates that the vehicle is a non-communication vehicle and the device type of the faulty device indicates that the faulty device is an emergency stop button; Based on the emergency brake data, brake data of the vehicle is determined.

5. The method according to claim 1, characterized in that The step of braking the vehicle based on the braking data comprises: Based on the braking data, controlling the vehicle to stop running in front of the faulty device; or, Based on the braking data, the vehicle is controlled to pass through the faulty device after the faulty device returns to normal.

6. The method according to claim 1, characterized in that The trackside monitoring data includes at least one of turnout status data, signal status data, axle counting section status data, platform shield door status data, emergency stop button status data, and area blocking button status data.

7. The method according to claim 1, characterized in that The fault data includes at least one of switch failure indication, signal closure, axle counting section occupancy, platform shield door opening, emergency stop button activated, and area blocking button activated.

8. The method according to claim 7, characterized in that In the case where the type of the vehicle indicates that the vehicle is a non-communication vehicle; the fault data indicates that there is a faulty device in the at least one trackside device, including at least one of the following cases: The fault data is a turnout failure indication, indicating that the turnout is the faulty device; The fault data is that the signal is closed, indicating that the signal is the faulty device; The fault data is the occupation of the axle counting section, indicating that the axle counting section is the faulty device; The fault data is that the shielding door is open, indicating that the shielding door is the faulty device; The fault data is that the emergency stop button has been activated, indicating that the emergency stop button is the faulty device; The fault data is that the area blocking button has been activated, indicating that the area blocking button is the faulty device.

9. The method according to claim 7, characterized in that: In the case where the type of the vehicle indicates that the vehicle is a communication vehicle; the fault data indicates that there is a faulty device in the at least one trackside device, including at least one of the following cases: The fault data is a turnout failure indication, indicating that the turnout is the faulty device; The fault data is that the signal is closed, indicating that the signal is the faulty device; The fault data is the occupation of the axle counting section, indicating that the axle counting section is the faulty device; The fault data is that the area blocking button has been activated, indicating that the area blocking button is the faulty device.

10. The method according to claim 1, characterized in that The method further comprises: Based on the faulty device, displaying device information of the faulty device on a train status display; or A voice alarm is issued based on the device information of the faulty device.

11. A vehicle control device based on trackside faults, characterized in that: The device comprises: A trackside monitoring data receiving module, used to receive trackside monitoring data, wherein the trackside monitoring data is data obtained by monitoring the operating status of at least one trackside device; a fault data determination module, configured to process the trackside monitoring data to obtain fault data characterizing a fault condition of the trackside equipment; a braking data determination module, configured to determine braking data of the vehicle based on the type of the vehicle and the device information of the faulty device when the fault data indicates that there is a faulty device in the at least one trackside device; A vehicle braking module is used to brake the vehicle based on the braking data.

12. A vehicle control system based on trackside faults, characterized in that: The system comprises: A trackside status module, used to monitor the operating status of at least one trackside device to obtain trackside monitoring data, and send the trackside monitoring data to the automatic protection system of the vehicle; An automatic protection system for a vehicle, used to implement the method according to any one of claims 1-10.

13. A vehicle, characterized in that: The vehicle is used to implement the method according to any one of claims 1-10.

14. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 10 are implemented.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 10 are implemented.