Trackside equipment management method, device and system

Abstract

The application provides a trackside equipment management system, method and device, which is used for managing equipment in a target area, and comprises a cloud manager and an edge manager group; the edge manager group comprises an edge manager and an end manager; the end manager is used for obtaining monitoring index values of first trackside equipment corresponding to a connection; the edge manager is used for obtaining monitoring index values of second trackside equipment corresponding to a connection; and the cloud manager is used for generating first control instructions corresponding to the first trackside equipment and second control instructions corresponding to the second trackside equipment based on the received monitoring index values of the first trackside equipment and the monitoring index values of the second trackside equipment; and the first trackside equipment is trackside equipment in a target sub-area and has a management level higher than a level threshold. The trackside equipment management system, method and device provided by the application can realize differentiated monitoring of trackside equipment, can more reasonably allocate monitoring resources, and can more flexibly, efficiently and accurately manage trackside equipment.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a trackside equipment management system, method, and apparatus. Background Technology

[0002] With the rapid development of my country's national economy and the pace of urbanization, the development of rail transit is accelerating, moving towards a more intelligent, convenient, and greener direction.

[0003] In recent years, the application of advanced technologies such as 5G communication and autonomous sensing in the rail transit industry has led to a continuous evolution in the types and number of trackside equipment. With the increasing number and variety of trackside equipment, existing management methods are no longer sufficient for accurate and efficient management. Therefore, how to manage trackside equipment more accurately and efficiently is a pressing technical problem that needs to be solved in this field. Summary of the Invention

[0004] This invention provides a trackside equipment management system, method, and apparatus to address the shortcomings of existing technologies in accurately and efficiently managing trackside equipment, thereby achieving more accurate and efficient management of trackside equipment.

[0005] This invention provides a trackside equipment management system for managing equipment within a target area. The system includes a cloud manager and an edge-end manager group; the edge-end manager group includes an edge manager and an end manager, and the edge manager is connected to the end manager and the cloud manager respectively.

[0006] The edge manager group corresponds one-to-one with the target sub-regions within the target area, the end manager is connected one-to-one with the first trackside device within the target sub-region, and the edge manager is connected to all the second trackside devices within the target sub-region.

[0007] The end manager is used to obtain the monitoring index value of the first trackside device connected to it, and send the monitoring index value of the first trackside device to the edge manager.

[0008] The edge manager is used to obtain the monitoring index value of the corresponding connected second trackside device, and is also used to send the monitoring index value of the second trackside device and the received monitoring index value of the first trackside device to the cloud manager.

[0009] The cloud manager is used to generate a first control command corresponding to the first trackside device and a second control command corresponding to the second trackside device based on the received monitoring index values ​​of the first trackside device and the second trackside device. Then, through the edge manager group, the first control command is sent to the first trackside device and the second control command is sent to the second trackside device.

[0010] Wherein, the first trackside device is a trackside device in the target sub-area with a management level higher than the level threshold; the second trackside device is a trackside device in the target sub-area with a management level not higher than the level threshold; the monitoring indicators of the first trackside device are determined based on the management level and device type of the first trackside device.

[0011] According to a trackside equipment management system provided by the present invention, the management level of the trackside equipment is determined based on the importance level of the trackside equipment and the time required to replace or repair the trackside equipment; the importance level of the trackside equipment is used to describe the degree of impact of a failure or damage to the trackside equipment on the operation of the rail transit system to which the trackside equipment belongs.

[0012] According to a trackside equipment management system provided by the present invention, the cloud manager is used to determine the health assessment result of the first trackside equipment based on the received monitoring index value of the first trackside equipment, and then generate a first control command corresponding to the first trackside equipment based on the health assessment result of the first trackside equipment.

[0013] The cloud manager is also used to determine the health assessment result of the second trackside device based on the received monitoring index value of the second trackside device, and then generate a second control command corresponding to the second trackside device based on the health assessment result of the second trackside device.

[0014] According to a trackside equipment management system provided by the present invention, the end manager is further configured to issue an alarm message when it is determined that the monitoring index value of the first trackside equipment is abnormal.

[0015] According to a trackside equipment management system provided by the present invention, the trackside manager is further configured to issue an alarm message when it is determined that the monitoring indicators of the acquired second trackside equipment are abnormal.

[0016] The present invention also provides a method for managing trackside equipment, comprising:

[0017] Acquire target data, which includes the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment to be managed; the importance level of the trackside equipment to be managed is used to describe the degree of impact of the failure or damage of the trackside equipment to be managed on the operation of the rail transit system to which the trackside equipment belongs.

[0018] Based on the target data, the management level of the trackside equipment to be managed is determined;

[0019] Based on the management level and equipment type of the trackside equipment to be managed, the monitoring indicators corresponding to the trackside equipment to be managed are determined.

[0020] Obtain the monitoring index values ​​corresponding to the trackside equipment to be managed, and perform equipment management on the trackside equipment to be managed based on the monitoring index values ​​corresponding to the trackside equipment to be managed.

[0021] According to a method for managing trackside equipment provided by the present invention, the step of managing the trackside equipment to be managed based on the monitoring index values ​​corresponding to the trackside equipment to be managed includes:

[0022] Based on the monitoring index values ​​corresponding to the trackside equipment to be managed, the health assessment results of the trackside equipment to be managed are determined.

[0023] Based on the health assessment results of the trackside equipment to be managed, equipment management is carried out on the trackside equipment to be managed.

[0024] The present invention also provides a trackside equipment management device, comprising:

[0025] The data acquisition module is used to acquire target data, which includes the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment to be managed. The importance level of the trackside equipment to be managed is used to describe the degree of impact of the failure or damage of the trackside equipment to be managed on the operation of the rail transit system to which the trackside equipment belongs.

[0026] The management level determination module is used to determine the management level of the trackside equipment to be managed based on the target data.

[0027] The indicator determination module is used to determine the monitoring indicators corresponding to the trackside equipment to be managed based on the management level and equipment type of the trackside equipment to be managed.

[0028] The equipment management module is used to obtain the monitoring index values ​​corresponding to the trackside equipment to be managed, and to perform equipment management on the trackside equipment to be managed based on the monitoring index values ​​corresponding to the trackside equipment to be managed.

[0029] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the trackside equipment management method as described above.

[0030] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the trackside equipment management method as described above.

[0031] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the trackside equipment management method as described above.

[0032] The trackside equipment management system, method, and apparatus provided by this invention include a cloud manager and an edge manager group for managing trackside equipment within a target area. This system enables differentiated monitoring of the operational status of trackside equipment based on its management level, given the increasing number and types of trackside equipment. This allows for more rational allocation of monitoring resources while ensuring effective monitoring. Furthermore, it enables more flexible, efficient, and accurate management of trackside equipment based on obtained monitoring indicators, reducing equipment management costs, better ensuring the normal operation of rail transit, and improving user experience. Attached Figure Description

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

[0034] Figure 1 This is a schematic diagram of the trackside equipment management system provided by the present invention;

[0035] Figure 2 This is a flowchart illustrating the trackside equipment management method provided by the present invention;

[0036] Figure 3 This is a schematic diagram of the trackside equipment management device provided by the present invention;

[0037] Figure 4 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

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

[0039] In the description of the invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0040] Figure 1 This is a structural schematic diagram of the trackside equipment management system provided by the present invention. The following is in conjunction with… Figure 1 The trackside equipment management system provided by this invention is described below. It should be noted that the trackside equipment management system provided by this invention is used to manage trackside equipment within a target area. For example... Figure 1 As shown, the above system includes: cloud manager 101 and edge-end manager group 102; edge-end manager group 102 includes edge manager 103 and end manager 104, and edge manager 103 is connected to end manager 104 and cloud manager 101 respectively.

[0041] The edge manager group 102 corresponds one-to-one with the target sub-regions within the target area, the end manager 104 is connected one-to-one with the first trackside device 105 within the target sub-region, and the edge manager 103 is connected to all the second trackside devices 106 within the target sub-region.

[0042] Among them, the first trackside device 105 is a trackside device in the target sub-area with a management level higher than the level threshold; the second trackside device 106 is a trackside device in the target sub-area with a management level not higher than the level threshold.

[0043] Specifically, the trackside equipment within the target area is the management object of the trackside equipment management system provided by this invention.

[0044] In this embodiment of the invention, the target region can be divided into multiple target sub-regions based on prior knowledge and / or actual conditions.

[0045] It should be noted that, without dividing the target area, there is only one target sub-region, which is the target area.

[0046] In this embodiment of the invention, the number of cloud managers 101 in the trackside equipment management system is one. The number of edge manager groups 102 can be the same as the number of target sub-regions within the target area. There is a one-to-one correspondence between the edge manager groups 102 and the aforementioned target sub-regions.

[0047] For any target sub-region, the trackside equipment set up in the target sub-region can be referred to as the trackside equipment in the target sub-region.

[0048] It is understandable that when there are a large number of trackside devices and / or a wide variety of trackside device types within a target area, the importance of different trackside devices to the operation of their respective rail transit systems varies. Applying the same management strategy to all trackside devices within the target area would lead to management delays and inaccuracies. Therefore, in this embodiment of the invention, the management level of the trackside device is used to describe the importance of the trackside device to the operation of the rail transit system. This allows for more accurate, efficient, and flexible management of the trackside devices based on their management level.

[0049] For any trackside device within the aforementioned target sub-area, the trackside device can be designated as either the first trackside device 105 or the second trackside device 106 based on its management level.

[0050] When the management level of a trackside device is lower and its importance to the operation of the rail transit system is higher, the trackside device can be designated as a first trackside device 105 if its management level is lower than the level threshold; and when the management level of a trackside device is not lower than the level threshold, the trackside device can be designated as a second trackside device 106.

[0051] When the management level of a trackside device is higher and its importance to the operation of the rail transit system is greater, the trackside device can be designated as a first trackside device 105 if its management level is higher than the level threshold; when the management level of a trackside device is not higher than the level threshold, the trackside device can be designated as a second trackside device 106.

[0052] Optionally, the management level of the aforementioned trackside equipment can be determined based on various methods. For example, it can be determined based on the historical operating data of the trackside equipment; or, it can be determined based on the time required for repairing or replacing the trackside equipment; or, it can be determined based on the degree of impact of the trackside equipment's failure or damage on the operation of the rail transit system to which the trackside equipment belongs. The specific method for determining the management level of the trackside equipment in this embodiment of the invention is not limited.

[0053] It should be noted that the level threshold in the embodiments of the present invention can be determined based on prior knowledge and / or actual circumstances. The embodiments of the present invention do not impose specific limitations on the level threshold.

[0054] It should be noted that for any target sub-area, the number of first trackside devices 105 in the target sub-area can be one or more, and the number of second trackside devices 106 in the target sub-area can also be one or more.

[0055] For any target sub-region and the corresponding edge manager group 102, each edge manager 104 in the edge manager group 102 is connected to each first trackside device 105 in the target sub-region, and the edge manager 103 in the edge manager group 102 is connected to all second trackside devices 106 in the target sub-region.

[0056] It is understandable that the number of side managers 103 in any side manager group 102 is one, while the number of end managers 104 can be one or more.

[0057] The end manager 104 is used to obtain the monitoring index value of the first trackside device 105 connected to the corresponding trackside device 105, and send the monitoring index value of the first trackside device 105 to the edge manager 103.

[0058] The monitoring indicators of the first trackside device 105 are determined based on the management level and equipment type of the first trackside device 105.

[0059] Specifically, for any target sub-region and the edge-end manager group 102 corresponding to the target sub-region, the end manager 104 in the edge-end manager group 102 can be used to obtain the monitoring index value of the first trackside device 105 based on the monitoring index of the first trackside device 105 connected to the end manager 104, and send the obtained monitoring index of the first trackside device 105 to the edge manager 103 in the edge-end manager group 102.

[0060] It should be noted that the monitoring index values ​​of the first trackside device 105 can be predetermined based on the management level and equipment type of the first trackside device 105. For example, based on the equipment type of the first trackside device 105, the monitoring indexes of the first trackside device 105 can be determined to include: operating temperature, operating capacity, stability, wear level, etc.

[0061] The edge manager 103 is used to obtain the monitoring index values ​​of the corresponding connected second trackside device 106, and also to send the monitoring index values ​​of the second trackside device 106 and the received monitoring index values ​​of the first trackside device 105 to the cloud manager 101.

[0062] Specifically, for any target sub-region and the edge manager group 102 corresponding to the target sub-region, the edge manager 103 in the edge manager group 102 can be used to obtain the monitoring index value of each second trackside device 106 in the target sub-region and send the monitoring index value of each second trackside device 106 to the cloud manager 101.

[0063] It should be noted that the monitoring indicators of the second trackside device 106 mentioned above can be predetermined based on prior knowledge and / or actual conditions.

[0064] The edge manager 103 in the edge manager group 102 can also be used to receive the monitoring index value of the first trackside device 105 sent by the end manager 104 in the edge manager group 102, and send the monitoring index value of the first trackside device 105 to the cloud manager 101.

[0065] It should be noted that the number of monitoring indicators for the second trackside device 106 is less than the number of monitoring indicators for the first trackside device 105. The monitoring resources required for the edge manager 103 to monitor the second trackside device 106 are less than the monitoring resources required for the end manager 104 to monitor the first trackside device 105.

[0066] The cloud manager 101 generates a first control command corresponding to the first trackside device 105 and a second control command corresponding to the second trackside device 106 based on the received monitoring index values ​​of the first trackside device 105 and the second trackside device 106. Then, through the edge manager group 102, the cloud manager 101 sends the first control command to the first trackside device 105 and the second control command to the second trackside device 106.

[0067] Specifically, for any target sub-region and the edge manager group 102 corresponding to the target sub-region, the cloud manager 101 can be used to receive the monitoring index values ​​of each first trackside device 105 in the target sub-region sent by each end manager 104 in the edge manager group 102, and the monitoring index of each second trackside device 106 in the target sub-region sent by the edge manager 103 in the edge manager group 102.

[0068] After receiving the monitoring index values ​​of each first trackside device 105 in the target sub-area, the cloud manager 101 can determine whether to control the first trackside device 105 based on the monitoring index values ​​of the first trackside device 105 in the target sub-area. If it is determined that control of the first trackside device 105 is required, the cloud manager 101 can generate a first control command corresponding to the first trackside device 105 based on the monitoring index values ​​of the first trackside device 105.

[0069] After generating the first control command, the cloud manager 101 can send the first control command to the edge manager 103 in the edge manager group 102. The edge manager 103 can forward the first control command to the end manager 104 connected to the first trackside device 105. The end manager 104 can forward the first control command to the first trackside device 105 so that the first trackside device 105 can respond to the first control command, thereby realizing device management of the first trackside device 105.

[0070] After receiving the monitoring index values ​​of each second trackside device 106 in the target sub-area, the cloud manager 101 can determine whether to control the second trackside device 106 based on the monitoring index values ​​of the second trackside device 106 in the target sub-area. If it is determined that control of the second trackside device 106 is required, the cloud manager 101 can generate a second control command corresponding to the second trackside device 106 based on the monitoring index values ​​of the second trackside device 106.

[0071] After generating the second control command, the cloud manager 101 can send the second control command to the edge manager 103 in the edge manager group 102. The edge manager 103 can forward the first control command to the second trackside device 106 so that the second trackside device 106 can respond to the first control command, thereby realizing device management of the second trackside device 106.

[0072] The trackside equipment management system in this embodiment of the invention includes a cloud manager and an edge manager group, used to manage trackside equipment within a target area. This system can monitor the operational status of trackside equipment in a differentiated manner based on its management level, given the increasing number and types of trackside equipment. This allows for more rational allocation of monitoring resources while ensuring effective monitoring. Based on the obtained monitoring indicators, it enables more flexible, efficient, and accurate management of trackside equipment, reduces equipment management costs, better ensures the normal operation of rail transit, and improves user experience.

[0073] Based on the above embodiments, the management level of trackside equipment is determined based on the importance level of the trackside equipment and the time required to replace or repair the trackside equipment; the importance level of trackside equipment is used to describe the degree of impact of trackside equipment failure or damage on the operation of the rail transit system to which the trackside equipment belongs.

[0074] Specifically, for any trackside device within the target sub-area, the management level of the trackside device can be determined based on its importance level and the time required to replace or repair it.

[0075] In this embodiment of the invention, if the probability of a major accident occurring in the rail transit system to which the trackside equipment belongs due to a malfunction or damage of any trackside equipment exceeds a probability threshold, then the importance level of the trackside equipment is determined to be "serious". The aforementioned major accident may include a complete shutdown or widespread delays of the rail transit system to which the trackside equipment belongs.

[0076] In this embodiment of the invention, if the probability of a moderate accident occurring in the rail transit system to which the trackside equipment belongs due to a malfunction or damage of any trackside equipment exceeds a probability threshold, then the importance level of the trackside equipment is determined to be "moderate". The aforementioned moderate accident may include slow operation in sections or passenger congestion at fewer than a first number of stations within the rail transit system to which the trackside equipment belongs. The first number can be determined based on prior knowledge and / or actual circumstances; for example, the first number may be five.

[0077] In this embodiment of the invention, if the probability of a minor accident occurring in the rail transit system to which the trackside equipment belongs due to a malfunction or damage of any trackside equipment is greater than a probability threshold, then the importance level of the trackside equipment is determined to be "minor". The aforementioned minor accident may include passenger queues or passenger flow exceeding a preset value at fewer than a second number of stations within the rail transit system to which the trackside equipment belongs. The aforementioned second number can be determined based on prior knowledge and / or actual circumstances; for example, the second number can be 8.

[0078] It should be noted that the above probability threshold can be determined based on prior knowledge and / or actual circumstances; for example, the above probability threshold can be 80%. The specific value of the above probability threshold is not limited in the embodiments of the present invention.

[0079] Optionally, in embodiments of the present invention, the management level of the trackside equipment can be determined based on the mapping relationship between the importance level of the trackside equipment, the time required for replacing or repairing the trackside equipment, and the management level of the trackside equipment.

[0080] Table 1 shows the mapping relationship between the importance level of trackside equipment, the time required for replacement or repair, and the management level of trackside equipment. For any trackside equipment, its management level can be determined by referring to Table 1 based on its importance level and the time required for replacement or repair.

[0081] Table 1. Mapping Relationship of Management Levels

[0082]

[0083] As shown in Table 1, in this embodiment of the invention, the lower the management level of the trackside equipment, the higher its importance to the operation of the rail transit system.

[0084] Optionally, in this embodiment of the invention, the level threshold can be determined to be level 3.

[0085] Accordingly, for any trackside device in the aforementioned target sub-area, if the management level of the trackside device is lower than level 3, the trackside device can be designated as the first trackside device 105; if the management level of the trackside device is equal to or higher than level 3, the trackside device can be designated as the second trackside device 106.

[0086] Optionally, in embodiments of the present invention, the importance level of trackside equipment and the time required to replace or repair trackside equipment can be obtained in various ways. For example, the importance level of trackside equipment and the time required to replace or repair trackside equipment can be determined based on user input; or, the importance level of trackside equipment and the time required to replace or repair trackside equipment can be received from other electronic devices.

[0087] In this embodiment of the invention, the management level of trackside equipment is determined based on its importance level and the time required for replacement or repair. This allows for a more accurate determination of the management level of trackside equipment based on actual conditions, providing data support for more efficient and accurate management of trackside equipment.

[0088] Based on the above embodiments, the cloud manager 101 determines the health assessment result of the first trackside device 105 based on the received monitoring index value of the first trackside device 105, and then generates a first control command corresponding to the first trackside device 105 based on the health assessment result of the first trackside device 105.

[0089] Specifically, for any target sub-region and the edge manager group 102 corresponding to the target sub-region, after the cloud manager 101 receives the monitoring index value of each first trackside device 105 in the target sub-region, the cloud manager 101 can perform a health assessment on each first trackside device 105 in the target sub-region based on the monitoring index value of the first trackside device 105, and obtain the health assessment result of the first trackside device 105.

[0090] It should be noted that the above health assessment results may include "healthy", "sub-healthy", and "risk of damage", etc.

[0091] Optionally, based on the monitoring index values ​​of the first trackside device 105, the cloud manager 101 can perform a health assessment of the first trackside device 105 in various ways. For example, the cloud manager 101 can perform a health assessment of the first trackside device 105 based on the monitoring index values ​​of the first trackside device 105 through numerical calculation, mathematical statistics, or deep learning technology.

[0092] After obtaining the health assessment result of the first trackside device 105, the cloud manager 101 can determine whether the first trackside device 105 needs to be controlled based on the health assessment result. If it is determined that the first trackside device 105 needs to be controlled, the cloud manager 101 can generate a first control command corresponding to the first trackside device 105 based on the health assessment result.

[0093] For example, if the health assessment result of the first trackside device 105 is "healthy", the cloud manager 101 can determine that there is no need to control the first trackside device 105; if the health assessment result of the first trackside device 105 is "sub-healthy" or "damage risk", the cloud manager 101 can generate a first control command corresponding to the first trackside device 105 based on the health assessment result of the first trackside device 105, which is used to control the first trackside device 105 to shut down, so that the first trackside device 105 can be repaired.

[0094] The cloud manager 101 is also used to determine the health assessment result of the second trackside device 106 based on the received monitoring index value of the second trackside device 106, and then generate a second control command corresponding to the second trackside device 106 based on the health assessment result of the second trackside device 106.

[0095] Specifically, for any target sub-region and the edge manager group 102 corresponding to the target sub-region, after the cloud manager 101 receives the monitoring index value of each second trackside device 106 in the target sub-region, the cloud manager 101 can perform a health assessment on each second trackside device 106 based on the monitoring index value of the second trackside device 106 and obtain the health assessment result of the second trackside device 106.

[0096] Optionally, based on the monitoring index values ​​of the second trackside device 106, the cloud manager 101 can perform a health assessment of the second trackside device 106 in various ways. For example, the cloud manager 101 can perform a health assessment of the second trackside device 106 based on the monitoring index values ​​of the second trackside device 106 through numerical calculation, mathematical statistics, or deep learning techniques.

[0097] After obtaining the health assessment result of the second trackside device 106, the cloud manager 101 can determine whether the second trackside device 106 needs to be controlled based on the health assessment result. If it is determined that the second trackside device 106 needs to be controlled, the cloud manager 101 can generate a second control command corresponding to the second trackside device 106 based on the health assessment result.

[0098] For example, if the health assessment result of the second trackside device 106 is "healthy", the cloud manager 101 can determine that there is no need to control the second trackside device 106; if the health assessment result of the second trackside device 106 is "sub-healthy" or "damage risk", it can be determined that control of the second trackside device 106 is required. The cloud manager 101 can generate a second control command corresponding to the second trackside device 106 based on the health assessment result of the second trackside device 106, which is used to control the second trackside device 106 to shut down, so that the second trackside device 106 can be repaired.

[0099] In this embodiment of the invention, the cloud manager performs a health assessment on the first and second trackside devices based on the received monitoring index values ​​of the first and second trackside devices. Then, based on the health assessment results of the first and second trackside devices, it generates a first control command corresponding to the first trackside device and a second control command corresponding to the second trackside device. This enables more accurate and efficient health monitoring and assessment of trackside devices, more precise device management based on the health assessment results, and reduces device management costs.

[0100] Based on the above embodiments, the end manager 104 is also used to issue an alarm message when it is determined that the acquired monitoring index value of the first trackside device 105 is abnormal.

[0101] Specifically, for any target sub-region and the edge manager group 102 corresponding to the target sub-region, after the edge manager 104 in the edge manager group 102 obtains the monitoring index value of the corresponding connected first trackside device 105, it can determine whether the monitoring index value of the first trackside device 105 is abnormal.

[0102] If the terminal manager 104 determines that the monitoring index value of the first trackside device 105 is abnormal, the terminal manager 104 can issue an alarm message to remind the maintenance personnel that the first trackside device 105 may be abnormal.

[0103] Optionally, the terminal manager 104 can determine whether the monitoring index value of the first trackside device 105 is abnormal in a variety of ways. For example, the terminal manager 104 can determine whether the monitoring index value of the first trackside device 105 meets the first preset condition. If the terminal manager 104 determines that the monitoring index value of the first trackside device 105 does not meet the first preset condition, then it can be determined that the monitoring index value of the first trackside device 105 is abnormal.

[0104] It should be noted that the above-mentioned first preset condition can be determined based on prior knowledge and / or actual situation. For example, the above-mentioned first preset condition may include the operating temperature of the first trackside device 105 not exceeding the temperature threshold and the usage capacity not exceeding the capacity threshold.

[0105] It should be noted that the aforementioned alarm information can be any one or more of sound, light, and electrical signals. The aforementioned alarm information can also be alarm information displayed on the display interface of the terminal used by maintenance personnel. The specific type of the aforementioned alarm information is not limited in this embodiment of the invention.

[0106] In this embodiment of the invention, when the end manager determines that the monitoring index value of the first trackside device is abnormal, it issues an alarm message. It can realize abnormal monitoring of the first trackside device based on the end manager, and can more timely remind the operation and maintenance personnel when the first trackside device may be abnormal, which can reduce the risk of damage to the first trackside device and better ensure the normal operation of rail transit.

[0107] Based on the above embodiments, the edge manager 103 is also used to issue an alarm message when it is determined that the monitoring indicators of the acquired second trackside device 106 are abnormal.

[0108] Specifically, for any target sub-region and the edge manager group 102 corresponding to the target sub-region, after the edge manager 103 in the edge manager group 102 obtains the monitoring index value of each second trackside device 106 connected to the corresponding location, it can determine whether the monitoring index value of the second trackside device 106 is abnormal.

[0109] If the terminal manager 104 determines that the monitoring index value of the second trackside device 106 is abnormal, the terminal manager 104 can issue an alarm message to remind the maintenance personnel that the second trackside device 106 may be abnormal.

[0110] Optionally, the terminal manager 104 can determine whether the monitoring index value of the second trackside device 106 is abnormal in a variety of ways. For example, the terminal manager 104 can determine whether the monitoring index value of the second trackside device 106 meets the second preset condition. If the terminal manager 104 determines that the monitoring index value of the second trackside device 106 does not meet the second preset condition, then it can be determined that the monitoring index value of the second trackside device 106 is abnormal.

[0111] It should be noted that the above second presupposition condition can be determined based on prior knowledge and / or actual circumstances.

[0112] It should be noted that the aforementioned alarm information can be any one or more of sound, light, and electrical signals. The aforementioned alarm information can also be alarm information displayed on the display interface of the terminal used by maintenance personnel. The specific type of the aforementioned alarm information is not limited in this embodiment of the invention.

[0113] In this embodiment of the invention, when the edge manager determines that the monitoring index value of the acquired second trackside equipment is abnormal, it issues an alarm message. It can realize abnormal monitoring of the second trackside equipment based on the edge manager, and can more timely remind the operation and maintenance personnel when the second trackside equipment may be abnormal, which can reduce the risk of damage to the second trackside equipment and better ensure the normal operation of rail transit.

[0114] Figure 2 This is a flowchart illustrating the trackside equipment management method provided by the present invention. The following is in conjunction with... Figure 2 This invention describes a trackside equipment management method. For example... Figure 2 As shown, the method includes: Step 201, obtaining target data, which includes the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment to be managed; the importance level of the trackside equipment to be managed is used to describe the degree of impact on the operation of the rail transit system to which the trackside equipment to be managed is located when the trackside equipment to be managed fails or is damaged.

[0115] It should be noted that the executing entity in this embodiment of the invention is a trackside equipment management device.

[0116] Specifically, in this embodiment of the invention, target data can be obtained in various ways. For example, the target data can be obtained based on user input; or, the target data can be received from other electronic devices. This embodiment of the invention does not limit the specific method of obtaining target data.

[0117] It should be noted that, in this embodiment of the invention, if the probability of a major accident occurring in the rail transit system to which the trackside equipment belongs due to a malfunction or damage of any trackside equipment to be managed exceeds a probability threshold, then the importance level of the trackside equipment to be managed is determined to be "serious". The aforementioned major accident may include a complete shutdown or widespread delays of the rail transit system to which the trackside equipment belongs.

[0118] In this embodiment of the invention, if the probability of a malfunction or damage to any trackside equipment under management leading to a moderate accident in the rail transit system to which the trackside equipment belongs exceeds a probability threshold, then the importance level of the trackside equipment under management is determined to be "moderate". The aforementioned moderate accident may include slow operation in sections or passenger congestion at fewer than a first number of stations in the rail transit system to which the trackside equipment belongs. The first number can be determined based on prior knowledge and / or actual conditions; for example, the first number can be 5.

[0119] In this embodiment of the invention, if the probability of a minor accident occurring in the rail transit system to which the trackside equipment belongs due to a malfunction or damage of any trackside equipment under management is greater than a probability threshold, then the importance level of the trackside equipment under management is determined to be "minor". The aforementioned minor accident may include passenger queues or passenger flow exceeding a preset value at fewer than a second number of stations in the rail transit system to which the trackside equipment belongs. The aforementioned second number can be determined based on prior knowledge and / or actual circumstances; for example, the second number can be 8.

[0120] Step 202: Based on the target data, determine the management level of the trackside equipment to be managed.

[0121] Specifically, in this embodiment of the invention, the management level of the trackside equipment to be managed can be determined based on the mapping relationship between the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment to be managed, and the management level of the trackside equipment to be managed.

[0122] Based on the importance level of the trackside equipment to be managed and the time required to replace or repair it, the management level of the trackside equipment to be managed can be determined by referring to Table 1.

[0123] Step 203: Based on the management level and equipment type of the trackside equipment to be managed, determine the monitoring indicators of the trackside equipment to be managed.

[0124] Specifically, after determining the management level of the trackside equipment to be managed, the monitoring indicators of the trackside equipment to be managed can be determined based on the mapping relationship between the management level and equipment type of the trackside equipment and the monitoring indicators.

[0125] Step 204: Obtain the monitoring index values ​​of the trackside equipment to be managed, and perform equipment management based on the monitoring index values ​​of the trackside equipment to be managed.

[0126] Specifically, after obtaining the monitoring indicators of the trackside equipment to be managed, the trackside equipment to be managed can be monitored based on the above monitoring indicators to obtain the monitoring indicator values ​​of the trackside equipment to be managed.

[0127] After obtaining the monitoring index values ​​of the trackside equipment to be managed, it can be determined whether the trackside equipment to be managed needs to be controlled based on the above monitoring index values.

[0128] When it is determined that control of the aforementioned trackside equipment to be managed is required, control commands corresponding to the trackside equipment to be managed can be generated based on the monitoring index values ​​of the trackside equipment to be managed. Then, the aforementioned control commands can be sent to the trackside equipment to be managed so that the trackside equipment to be managed can respond to the aforementioned control commands, thereby realizing the equipment management of the trackside equipment to be managed.

[0129] This invention, through its embodiments, determines the management level of trackside equipment based on its importance level and the time required for replacement or repair. Then, based on the management level and equipment type, it determines the monitoring indicators for the trackside equipment, obtains the monitoring indicator values, and manages the equipment based on these values. This allows for more accurate determination of the management level based on actual conditions. With the increasing number and types of trackside equipment, it enables differentiated monitoring of the operational status of trackside equipment based on its management level. This ensures effective monitoring while allocating monitoring resources more rationally. Based on the obtained monitoring indicator values, it allows for more flexible, efficient, and accurate management of trackside equipment, reducing equipment management costs, better ensuring the normal operation of rail transit, and improving user experience.

[0130] Based on the content of the above embodiments, equipment management is performed on the trackside equipment to be managed based on the monitoring index values ​​corresponding to the trackside equipment to be managed, including: determining the health assessment result of the trackside equipment to be managed based on the monitoring index values ​​of the trackside equipment to be managed.

[0131] Specifically, after obtaining the monitoring index values ​​of the trackside equipment to be managed, a health assessment can be performed on the trackside equipment to be managed based on the above monitoring index values, and the health assessment results of the trackside equipment to be managed can be obtained.

[0132] It should be noted that the above health assessment results may include "healthy", "sub-healthy", and "risk of damage", etc.

[0133] It should be noted that, in the embodiments of the present invention, the health assessment of the trackside equipment to be managed can be carried out in a variety of ways based on the monitoring index values ​​of the trackside equipment to be managed. For example, the health assessment of the trackside equipment to be managed can be carried out based on the monitoring index values ​​of the trackside equipment to be managed through numerical calculation, mathematical statistics or deep learning technology.

[0134] Based on the health assessment results of the trackside equipment to be managed, equipment management is carried out on the trackside equipment to be managed.

[0135] Specifically, after obtaining the health assessment results of the trackside equipment to be managed, it can be determined whether the trackside equipment to be managed needs to be controlled based on the above health assessment results.

[0136] When it is determined that control of the trackside equipment to be managed is required, control commands corresponding to the trackside equipment to be managed can be generated based on the health assessment results of the trackside equipment to be managed.

[0137] For example, if the health assessment result of the trackside equipment to be managed is "healthy", it can be determined that there is no need to control the trackside equipment to be managed; if the health assessment result of the trackside equipment to be managed is "sub-healthy" or "risk of damage", it can be determined that the trackside equipment to be managed needs to be controlled, and control instructions corresponding to the trackside equipment to be managed can be generated based on the health assessment result of the trackside equipment to be managed, so as to control the trackside equipment to be managed to shut down, thereby enabling maintenance of the trackside equipment to be managed.

[0138] This invention, through its embodiments, performs a health assessment of the trackside equipment based on its monitoring index values. Then, based on the health assessment results, it generates corresponding control commands for the trackside equipment. This allows for equipment management based on these control commands, enabling more accurate and efficient health monitoring and assessment of trackside equipment. Furthermore, it allows for more precise equipment management based on the health assessment results, and reduces equipment management costs.

[0139] Based on the above embodiments, after obtaining the monitoring index values ​​of the trackside equipment to be managed, the method further includes: issuing an alarm signal when it is determined that the monitoring index values ​​of the trackside equipment to be managed are abnormal.

[0140] Figure 3 This is a structural schematic diagram of the trackside equipment management device provided by the present invention. The following is in conjunction with… Figure 3 The trackside equipment management device provided by this invention will be described below. The trackside equipment management device described below can be referred to in correspondence with the trackside equipment management method provided by this invention described above. For example... Figure 3 As shown, the device includes: a data acquisition module 301, a level determination module 302, an indicator determination module 303, and an equipment management module 304.

[0141] The data acquisition module 301 is used to acquire target data, which includes the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment to be managed. The importance level of the trackside equipment to be managed is used to describe the degree of impact on the operation of the rail transit system to which the trackside equipment belongs when the trackside equipment to be managed fails or is damaged.

[0142] The level determination module 302 is used to determine the management level of the trackside equipment to be managed based on the target data;

[0143] The indicator determination module 303 is used to determine the monitoring indicators corresponding to the trackside equipment to be managed based on the management level and equipment type of the trackside equipment to be managed.

[0144] The equipment management module 304 is used to obtain the monitoring index values ​​corresponding to the trackside equipment to be managed, and to perform equipment management on the trackside equipment to be managed based on the monitoring index values ​​corresponding to the trackside equipment to be managed.

[0145] Specifically, the data acquisition module 301, the level determination module 302, the indicator determination module 303, and the equipment management module 304 are electrically connected.

[0146] The trackside equipment management device in this embodiment of the invention determines the management level of the trackside equipment to be managed based on its importance level and the time required for replacement or repair. Then, based on the management level and equipment type, it determines the monitoring indicators of the trackside equipment, obtains the monitoring indicator values, and manages the equipment based on these values. This allows for more accurate determination of the management level of trackside equipment based on actual conditions. With the increasing number and types of trackside equipment, it enables differentiated monitoring of the operational status of trackside equipment based on its management level. This allows for more rational allocation of monitoring resources while ensuring monitoring effectiveness. Based on the obtained monitoring indicator values, it enables more flexible, efficient, and accurate management of trackside equipment, reduces equipment management costs, better ensures the normal operation of rail transit, and improves user experience.

[0147] Figure 4 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 4 As shown, the electronic device may include: a processor 410, a communication interface 420, a memory 430, and a communication bus 440. The processor 410, communication interface 420, and memory 430 communicate with each other via the communication bus 440. The processor 410 can call logical instructions in the memory 430 to execute a trackside equipment management method. This method includes: acquiring target data, which includes the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment; the importance level of the trackside equipment to be managed describes the impact of a fault or damage to the trackside equipment on the operation of the rail transit system to which the trackside equipment belongs; determining the management level of the trackside equipment to be managed based on the target data; determining the monitoring indicators corresponding to the trackside equipment to be managed based on the management level and equipment type of the trackside equipment to be managed; acquiring the monitoring indicator values ​​corresponding to the trackside equipment to be managed; and performing equipment management on the trackside equipment to be managed based on the monitoring indicator values ​​corresponding to the trackside equipment to be managed.

[0148] Furthermore, the logical instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0149] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the trackside equipment management method provided by the above methods. The method includes: acquiring target data, which includes the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment to be managed; the importance level of the trackside equipment to be managed is used to describe the degree of impact of a failure or damage to the trackside equipment on the operation of the rail transit system to which the trackside equipment belongs; determining the management level of the trackside equipment to be managed based on the target data; determining the monitoring indicators corresponding to the trackside equipment to be managed based on the management level and equipment type of the trackside equipment to be managed; acquiring the monitoring indicator values ​​corresponding to the trackside equipment to be managed; and performing equipment management on the trackside equipment to be managed based on the monitoring indicator values ​​corresponding to the trackside equipment to be managed.

[0150] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the trackside equipment management method provided by the above methods. This method includes: acquiring target data, the target data including the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment; the importance level of the trackside equipment to be managed describes the degree of impact of a fault or damage to the trackside equipment on the operation of the rail transit system to which the trackside equipment belongs; determining the management level of the trackside equipment to be managed based on the target data; determining the monitoring indicators corresponding to the trackside equipment to be managed based on the management level and equipment type of the trackside equipment to be managed; acquiring the monitoring indicator values ​​corresponding to the trackside equipment to be managed; and performing equipment management on the trackside equipment to be managed based on the monitoring indicator values ​​corresponding to the trackside equipment to be managed.

[0151] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0152] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0153] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A trackside equipment management system, characterized in that, The system is used to manage devices within a target area. It includes a cloud manager and an edge-end manager group. The edge-end manager group includes an edge manager and an end manager. The edge manager is connected to the end manager and the cloud manager, respectively. The edge manager group corresponds one-to-one with the target sub-regions within the target area, the end manager is connected one-to-one with the first trackside device within the target sub-region, and the edge manager is connected to all the second trackside devices within the target sub-region. The end manager is used to obtain the monitoring index value of the first trackside device connected to it, and send the monitoring index value of the first trackside device to the edge manager. The edge manager is used to obtain the monitoring index value of the corresponding connected second trackside device, and is also used to send the monitoring index value of the second trackside device and the received monitoring index value of the first trackside device to the cloud manager. The cloud manager is used to generate a first control command corresponding to the first trackside device and a second control command corresponding to the second trackside device based on the received monitoring index values ​​of the first trackside device and the second trackside device. Then, through the edge manager group, the first control command is sent to the first trackside device and the second control command is sent to the second trackside device. Wherein, the first trackside device is a trackside device in the target sub-area with a management level higher than the level threshold; the second trackside device is a trackside device in the target sub-area with a management level not higher than the level threshold; the monitoring indicators of the first trackside device are determined based on the management level and device type of the first trackside device; The management level of the trackside equipment is determined based on the importance level of the trackside equipment and the time required to replace or repair the trackside equipment; the importance level of the trackside equipment is used to describe the degree of impact of a failure or damage to the trackside equipment on the operation of the rail transit system to which the trackside equipment belongs. If any trackside equipment malfunctions or is damaged, and the probability of a major, moderate, or minor accident in the rail transit system to which that trackside equipment belongs exceeds a probability threshold, then the importance level of that trackside equipment is determined as severe, moderate, or minor. A major accident includes a complete shutdown of the rail transit system or widespread delays; a moderate accident includes slow operation in sections of the rail transit system to which the trackside equipment belongs or passenger congestion at fewer than a first number of stations; and a minor accident includes passenger queues in the rail transit system to which the trackside equipment belongs or passenger flow at fewer than a second number of stations exceeding a preset value.

2. The trackside equipment management system according to claim 1, characterized in that, The cloud manager is used to determine the health assessment result of the first trackside device based on the received monitoring index value of the first trackside device, and then generate a first control command corresponding to the first trackside device based on the health assessment result of the first trackside device. The cloud manager is also used to determine the health assessment result of the second trackside device based on the received monitoring index value of the second trackside device, and then generate a second control command corresponding to the second trackside device based on the health assessment result of the second trackside device.

3. The trackside equipment management system according to any one of claims 1 to 2, characterized in that, The endpoint manager is also used to issue alarm information when it is determined that the monitoring indicator value of the first trackside device is abnormal.

4. The trackside equipment management system according to any one of claims 1 to 2, characterized in that, The edge manager is also used to issue alarm information when it is determined that the monitoring indicators of the acquired second trackside device are abnormal.

5. A method for managing trackside equipment, characterized in that, include: Acquire target data, which includes the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment to be managed; The importance level of the trackside equipment to be managed is used to describe the degree of impact of a failure or damage to the trackside equipment on the operation of the rail transit system to which the trackside equipment belongs. Based on the target data, the management level of the trackside equipment to be managed is determined; Based on the management level and equipment type of the trackside equipment to be managed, the monitoring indicators corresponding to the trackside equipment to be managed are determined. Obtain the monitoring index values ​​corresponding to the trackside equipment to be managed, and perform equipment management on the trackside equipment to be managed based on the monitoring index values ​​corresponding to the trackside equipment to be managed. The management level of the trackside equipment is determined based on the importance level of the trackside equipment and the time required to replace or repair the trackside equipment; the importance level of the trackside equipment is used to describe the degree of impact of a failure or damage to the trackside equipment on the operation of the rail transit system to which the trackside equipment belongs. If any trackside equipment malfunctions or is damaged, and the probability of a major, moderate, or minor accident in the rail transit system to which that trackside equipment belongs exceeds a probability threshold, then the importance level of that trackside equipment is determined as severe, moderate, or minor. A major accident includes a complete shutdown of the rail transit system or widespread delays; a moderate accident includes slow operation in sections of the rail transit system to which the trackside equipment belongs or passenger congestion at fewer than a first number of stations; and a minor accident includes passenger queues in the rail transit system to which the trackside equipment belongs or passenger flow at fewer than a second number of stations exceeding a preset value.

6. The trackside equipment management method according to claim 5, characterized in that, The step of managing the trackside equipment based on the monitoring index values ​​corresponding to the trackside equipment to be managed includes: Based on the monitoring index values ​​corresponding to the trackside equipment to be managed, the health assessment results of the trackside equipment to be managed are determined. Based on the health assessment results of the trackside equipment to be managed, equipment management is carried out on the trackside equipment to be managed.

7. A trackside equipment management device, characterized in that, include: The data acquisition module is used to acquire target data, which includes the importance level of the trackside equipment to be managed and the time required to replace or repair the trackside equipment to be managed. The importance level of the trackside equipment to be managed is used to describe the degree of impact of a failure or damage to the trackside equipment on the operation of the rail transit system to which the trackside equipment belongs. The management level determination module is used to determine the management level of the trackside equipment to be managed based on the target data. The indicator determination module is used to determine the monitoring indicators corresponding to the trackside equipment to be managed based on the management level and equipment type of the trackside equipment to be managed. The equipment management module is used to obtain the monitoring index values ​​corresponding to the trackside equipment to be managed, and to perform equipment management on the trackside equipment to be managed based on the monitoring index values ​​corresponding to the trackside equipment to be managed. The management level of the trackside equipment is determined based on the importance level of the trackside equipment and the time required to replace or repair the trackside equipment; the importance level of the trackside equipment is used to describe the degree of impact of a failure or damage to the trackside equipment on the operation of the rail transit system to which the trackside equipment belongs. If any trackside equipment malfunctions or is damaged, and the probability of a major, moderate, or minor accident in the rail transit system to which that trackside equipment belongs exceeds a probability threshold, then the importance level of that trackside equipment is determined as severe, moderate, or minor. A major accident includes a complete shutdown of the rail transit system or widespread delays; a moderate accident includes slow operation in sections of the rail transit system to which the trackside equipment belongs or passenger congestion at fewer than a first number of stations; and a minor accident includes passenger queues in the rail transit system to which the trackside equipment belongs or passenger flow at fewer than a second number of stations exceeding a preset value.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the trackside equipment management method as described in any one of claims 5 and 6.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the trackside equipment management method as described in any one of claims 5 and 6.

Images