Micro-service-based alarm monitoring system for rail transit and electronic equipment

By adopting a microservice-based architecture in the rail transit system, the problem that the alarm monitoring system cannot be quickly iterated and optimized is solved, and the diversity and scalability of functions are achieved, reducing operation and maintenance costs.

CN119058778APending Publication Date: 2024-12-03BYD CO LTD
View PDF 12 Cites 0 Cited by

Patent Information

Application Number
CN202310636885.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-31
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The existing rail transit alarm monitoring system is closely coupled with other systems, resulting in the inability to quickly iterate and optimize, increasing operation and maintenance costs.

Method used

Adopting a microservice-based architecture, the alarm signal processing resources are deployed in cloud services through signal acquisition modules, resource provisioning modules and service integration modules, and the front-end monitoring page and back-end capability center are provided through the architecture combined with the browser and server, supporting a variety of Microservices and interfaces.

Benefits of technology

It realizes free expansion, upgrade and optimization of the alarm monitoring system, improves the diversity, expansion and compatibility of functions, and reduces the operation and maintenance and redevelopment costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119058778A_ABST
    Figure CN119058778A_ABST
Patent Text Reader

Abstract

The invention discloses a micro-service-based alarm monitoring system and electronic equipment for rail transit, and the system comprises a signal obtaining module which is used for obtaining an alarm signal; the resource allocation module is used for deploying in a cloud service by using a micro-service mode based on the acquired alarm signal so as to allocate a resource for processing the alarm signal; the service integration module is used for integrating various micro services into the same module; and the display module is used for displaying the micro service provided by the service integration module. According to the micro-service-based alarm monitoring system for rail transit and the electronic equipment provided by the invention, various micro-services are integrated in the same module, so that when the alarm monitoring system is upgraded according to specific requirements, the original functions can be freely expanded, upgraded and optimized; diversity, expansibility, compatibility, transportability and the like of alarm related functions are improved, and operation and maintenance and redevelopment cost can be reduced to a great extent.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of rail transit safety, and in particular to a microservice-based alarm monitoring system and electronic equipment for rail transit. Background Art

[0002] The full name of the rail transit system is the rail transit signal system. The main purpose of this system is to ensure the safety of train operation, realize intelligent driving and modernization of train operation, and improve transportation efficiency. The alarm monitoring system of the rail transit system is usually used to comprehensively obtain alarm information from trains, trackside equipment, stations and related equipment, process it, and finally display it in a centralized manner, and provide processing functions.

[0003] There are two common implementation methods for alarm monitoring systems. One is a single application, based on industrial communication protocols, embedded in the real-time monitoring system as a module or sub-application, that is, using the traditional client / server architecture. The other is to use the web page / server architecture for deployment and installation, rendering and displaying on the web page and providing interactive functions, the background service provides the interface, and the alarm service provides its functions as a module or application.

[0004] In the current scenario, the alarm monitoring system is only used as a subsystem or sub-application in the rail transit system, and is tightly coupled with other systems. When there is a specific requirement to upgrade the alarm monitoring system, the system cannot be iterated simply and quickly, and when there are modifications to its functions, it cannot be optimized and modified in time, which greatly increases the operation and maintenance costs. Summary of the invention

[0005] A series of simplified concepts are introduced in the Summary of the Invention, which will be further described in detail in the Detailed Description of the Invention. The Summary of the Invention does not mean to attempt to define the key features and essential technical features of the claimed technical solution, nor does it mean to attempt to determine the scope of protection of the claimed technical solution.

[0006] The present invention provides a microservice-based alarm monitoring system for rail transit, comprising:

[0007] A signal acquisition module, used for acquiring an alarm signal;

[0008] A resource allocation module, which is deployed in a cloud service in a microservice manner based on the acquired alarm signal to allocate resources for processing the alarm signal;

[0009] A service integration module, used to integrate the multiple microservices into the same module;

[0010] A display module is used to display the microservices provided by the service integration module.

[0011] Furthermore, the multiple microservices include one or more of real-time alarms, historical alarms, alarm monitoring, alarm conversion to work orders, alarm processes, and alarm statistics.

[0012] Furthermore, the multiple microservices include one or more of real-time alarm service, historical alarm service, alarm status service, data persistence service, alarm status migration service, user service, equipment information service, maintenance service, notification service, monitoring service, message service, interface service, heartbeat service, microservice framework, linkage service, and work order service.

[0013] Furthermore, it also includes an interface for interaction, which includes one or more of a microservice interface, a representative state transfer interface, and a message queue, and the interface supports one or more of a message queue, a Modbus communication protocol, and an open platform communication unified architecture.

[0014] Furthermore, the alarm monitoring system adopts an architecture combining a browser and a server.

[0015] Furthermore, the alarm monitoring system includes a front-end monitoring page and a back-end capability center.

[0016] Furthermore, the front-end monitoring page uses front-end components, and the front-end components include one or more of HTML, JAVASCRIPT, CSS, JQUERY, WEBSOCKET, flow chart editing components, statistical chart components, and configuration components.

[0017] Furthermore, the background capability center integrates one or more of WEBSOCKET components, REST interfaces, microservice interfaces, encryption services, time series databases, cloud service components, database services, log services, MQ protocols, MODBUS protocols, OPC UA protocols, SMS services, email services, timing services, statistical services, trend forecasting services, data analysis services, custom process services, process change services, and backup and restore.

[0018] Furthermore, the front-end monitoring page provides one or more of real-time alarms, historical alarms, alarm statistics, alarm operations, alarm status changes, alarm conversion to work orders, work order management, work order process changes, work order processing, process editing, alarm configuration display, alarm trend prediction, basic information display, basic information entry, external channels, log display, and alarm configuration; the back-end capability center provides one or more of real-time alarms, historical alarms, alarm statistics, alarm status, work order services, work order processes, alarm processes, alarm trends, basic information, log services, heartbeat services, channel services, push services, persistence services, backup and restore, and linkage services.

[0019] The present invention also provides an electronic device, characterized in that it includes a microservice-based alarm monitoring system for rail transit provided by any of the above items.

[0020] According to the microservice-based alarm monitoring system and electronic equipment for rail transit provided by the present invention, by integrating multiple microservices in the same module, when there is a specific demand for upgrading the alarm monitoring system, the original functions can be freely expanded, upgraded, and optimized, thereby improving the diversity, scalability, compatibility, portability, etc. of alarm-related functions, and at the same time can greatly reduce operation and maintenance and redevelopment costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The following drawings of the present invention are used to understand the present invention as part of the present invention. The embodiments of the present invention are shown in the drawings and the description thereof is used to explain the principle of the present invention.

[0022] In the attached figure:

[0023] Figure 1 A schematic diagram of the structure of an alarm monitoring system according to an embodiment of the present invention;

[0024] Figure 2 A schematic diagram of the composition of an alarm monitoring system according to an embodiment of the present invention;

[0025] Figure 3 is a functional schematic diagram of an alarm monitoring system according to an embodiment of the present invention;

[0026] Figure 4 A schematic diagram of a process for entering basic data of an alarm monitoring system according to an embodiment of the present invention;

[0027] Figure 5 A schematic diagram of the process of alarm reporting of an alarm monitoring system according to an embodiment of the present invention;

[0028] Figure 6 A schematic diagram of a flow chart of alarm prediction of an alarm monitoring system according to an embodiment of the present invention;

[0029] Figure 7 A schematic diagram of a flow chart of alarm trend analysis of an alarm monitoring system according to an embodiment of the present invention;

[0030] Figure 8 A schematic diagram of a push process of an alarm monitoring system according to an embodiment of the present invention;

[0031] Fig. 9 A schematic diagram of a process flow of editing a process of an alarm monitoring system according to an embodiment of the present invention;

[0032] Fig.101 is a schematic diagram of the system linkage process of the alarm monitoring system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0033] In the following description, a large number of specific details are provided to provide a more thorough understanding of the present invention. However, it is apparent to those skilled in the art that the present invention can be implemented without one or more of these details. In other examples, in order to avoid confusion with the present invention, some technical features well known in the art are not described.

[0034] It should be understood that the present invention can be implemented in different forms and should not be construed as being limited to the embodiments presented herein. On the contrary, providing these embodiments will make the disclosure thorough and complete and fully convey the scope of the present invention to those skilled in the art. In the accompanying drawings, the sizes and relative sizes of layers and regions may be exaggerated for clarity. The same reference numerals throughout represent the same elements.

[0035] The purpose of the terms used herein is only to describe specific embodiments and is not intended to be limiting of the present invention. When used herein, the singular forms "one", "an" and "said / the" are also intended to include plural forms, unless the context clearly indicates otherwise. It should also be understood that the terms "consisting of" and / or "comprising", when used in this specification, determine the presence of the features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or groups. When used herein, the term "and / or" includes any and all combinations of the relevant listed items.

[0036] In order to fully understand the present invention, detailed steps and detailed structures will be presented in the following description to illustrate the technical solution proposed by the present invention. The preferred embodiments of the present invention are described in detail below, but in addition to these detailed descriptions, the present invention may also have other implementations.

[0037] Aiming at the problem that the alarm monitoring system of the current rail transit system is too closely coupled with other subsystems or sub-applications and cannot be freely expanded, upgraded, and optimized, resulting in low maintainability and high upgrade and iteration costs, the present invention proposes a microservice-based alarm monitoring system 100 for rail transit, such as Figure 1 As shown, including:

[0038] A signal acquisition module 110, used to acquire an alarm signal;

[0039] A resource allocation module 120 is deployed in a cloud service using a microservice method based on the acquired alarm signal to allocate resources for processing the alarm signal;

[0040] A service integration module 130, used to integrate the multiple microservices into the same module;

[0041] The display module 140 is used to display the microservices provided by the service integration module.

[0042] In one embodiment, the alarm monitoring system 100 also includes an interface for interaction, which is a variety of types of interfaces that can interact with external systems or external devices, including but not limited to microservice interfaces, REST (Representational State Transfer) interfaces or message queues, etc.; the interface can support multiple protocols, including but not limited to MQ (Message Queue), Modbus communication protocol, OPC UA (Open Platform Communications Unified Architecture), etc.

[0043] In one embodiment, the signal acquisition module 110 is connected to a signal collection device, such as a camera and / or a sensor, through an interface. The camera includes but is not limited to a long-range camera, a mid-range camera, a stereo camera, a wide-angle camera (e.g., a fisheye camera), a surround camera (e.g., a 360-degree camera), an infrared camera or a combination thereof, and the sensor includes but is not limited to a velocity sensor, an acceleration sensor, an angle sensor, a pressure-sensitive and force-sensitive sensor, a position sensor, a liquid level sensor, an energy consumption sensor, a radiation sensor, a thermal sensor or a combination thereof.

[0044] In one embodiment, the resource allocation module 120 is connected to the cloud service through an interface and deployed in the cloud service in a microservice manner to allocate processing resources, for example, to allocate resources for processing acquired alarm signals.

[0045] In one embodiment, the service integration module 130 integrates multiple microservices in the same module. Exemplarily, the microservices include one or more of real-time alarm, historical alarm, alarm monitoring, alarm-to-work order, alarm process, and alarm statistics. Further, the microservices include one or more of real-time alarm service, historical alarm service, alarm status service, data persistence service, alarm status migration service, user service, device information service, maintenance service, notification service, monitoring service, message service, interface service, heartbeat service, microservice framework, linkage service, and work order service.

[0046] In one embodiment, the display module 140 is connected to a display device through an interface, including but not limited to a display, a mobile phone, a tablet computer, a computer, a wearable display device, etc., to display the microservices provided by the service integration module 130.

[0047] The microservice-based alarm monitoring system for rail transit provided by the present invention is self-sufficient and contains a series of functional items such as alarm collection, processing, display, and forwarding. It supports alarm detection and alarm linkage processing, has its own interface display, and provides heartbeat service, work order process, custom process configuration, entry of basic equipment information, display of alarm trend and other charts, and alarm warning functions. By integrating multiple microservices in the same module, when there is a specific demand for upgrading the alarm monitoring system, the original functions can be freely expanded, upgraded, and optimized, thereby improving the diversity, scalability, compatibility, portability, etc. of alarm-related functions, and at the same time can greatly reduce the operation and maintenance and redevelopment costs.

[0048] In addition, the microservice-based alarm monitoring system for rail transit provided by the present invention can be connected to other rail transit systems (such as real-time monitoring systems, AFC, BAS, etc.). The alarm monitoring system of the present invention can be connected to other rail transit systems as an auxiliary subsystem, and other rail transit systems can also be connected to the alarm monitoring system of the present invention as auxiliary subsystems. The present invention does not limit this.

[0049] In one embodiment, the alarm monitoring system adopts an architecture combining a browser and a server, where specific display functions and user operations are provided in the browser, and specific function implementation and docking with various systems and devices are implemented by background services.

[0050] In one embodiment, the alarm monitoring system includes a front-end monitoring page and a back-end capability center. Figure 2 As shown, the front-end monitoring page uses a series of front-end components such as HTML, JAVASCRIPT, CSS, JQUERY, WEBSOCKET, flowchart editing components, statistical chart components, configuration components, etc.; the back-end capability center integrates WEBSOCKET components, REST interfaces, microservice interfaces, encryption services, time series databases, cloud service components, database services, log services, MQ protocol, MODBUS protocol, OPC UA protocol, SMS services, email services, timing services, statistical services, trend forecasting services, data analysis services, custom process services, process change services, backup and restore and other technical functions.

[0051] It should be noted that the front-end monitoring page does not only refer to the page provided in the browser, but also includes various functional interfaces that are connected to the alarm monitoring system of the present invention and can be browsed and operated by users.

[0052] In one embodiment, Figure 3As shown in the figure, the front-end monitoring page provides real-time alarm, historical alarm, alarm statistics, alarm operation, alarm status change, alarm to work order, work order management, work order process change, work order processing, process editing, alarm configuration display, alarm trend prediction, basic information display, basic information entry, external channel, log display, alarm configuration and other functions. The back-end capability center provides real-time alarm, historical alarm, alarm statistics, alarm status, work order service, work order process, alarm process, alarm trend, basic information, log service, heartbeat service, channel service, push service, persistence service, backup and restore, linkage service and so on.

[0053] Figure 4 A schematic diagram of a process for entering basic information of an alarm monitoring system according to an embodiment of the present invention is shown. The process 400 of entering basic information of an alarm monitoring system includes the following steps:

[0054] Step S401: Open the basic information input interface on the front-end monitoring page. The basic information includes a series of information such as device information, device location information, device system information, device status information, device alarm information, and alarm level information.

[0055] Step S402: Select an input method on the front-end monitoring page. The input methods include manual input or template import: manual input is suitable for single or small amount of information input, while template import requires pre-filling multiple pieces of information in the corresponding template first, and then importing the pre-filled multiple pieces of information as a whole.

[0056] Step S403: Input is completed and confirmed.

[0057] Step S404: Categorize and persist the input data, and store the classified and persisted data in the database.

[0058] Step S405: After the persistence is completed, the front-end is notified that the monitoring page is successful.

[0059] Figure 5 A schematic diagram of the process of alarm reporting of an alarm monitoring system according to an embodiment of the present invention is shown. The process 500 of alarm reporting of an alarm monitoring system includes the following steps:

[0060] Step S501: configure alarm-related information on the front-end monitoring page. This information can also be entered in the process 400 of entering basic information.

[0061] Step S502: Configure information related to alarm push. For example, configure the alarm of the device to be pushed, the push scope, the push method, etc. The push scope refers to the target front-end monitoring page to be pushed. The specific push methods include WEBSOCKET, MQ, short message, email, etc.

[0062] Step S503: Provide the subsystem with the reported protocol format, protocol content and message content format. The docking protocol may be MQ, MODBUS, OPC UA, etc., and the content encryption method may be defined as needed.

[0063] Step S504: Obtain the alarm message reported by the subsystem according to the protocol format content.

[0064] Step S505: Analyze the validity of the alarm content. It is necessary to determine whether the alarm content can be parsed and whether the alarm information and device information contained therein are abnormal.

[0065] Step S506: Identify the alarm content as a real-time alarm, and push the alarm information.

[0066] Figure 6 6. The flowchart of the alarm prediction of the alarm monitoring system according to an embodiment of the present invention is shown in FIG. 6. The alarm prediction process 600 of the alarm monitoring system includes the following steps:

[0067] Step S601: Configure alarm information, device status information, status values ​​that need to be prompted for alarm, as well as soft thresholds and thresholds on the front end. The soft threshold means that the alarm triggered by the threshold will not be too serious. It is also necessary to configure the triggering rules of the threshold, specifically the rule of directly generating an alarm when the status reaches the threshold, the rule of generating an alarm when the status reaches the threshold multiple times within a certain period of time, the rule of directly generating an alarm when the status does not reach the threshold, the rule of generating an alarm when the status does not reach the threshold multiple times within a certain period of time, etc.

[0068] Step S602: providing the subsystem with the protocol format, protocol content and message content format for status reporting.

[0069] Step S603: Obtain the status message reported by the subsystem according to the protocol format content.

[0070] Step S604: Determine the validity of the status message.

[0071] Step S605: Determine whether the trigger condition is met according to the trigger rule of the threshold.

[0072] Step S606: For the state that meets the threshold triggering condition, a corresponding alarm content is generated. The generated alarm is marked as a real-time alarm by default, and the alarm content will contain a record of the threshold triggering.

[0073] Figure 7 700 is a flowchart of an alarm trend analysis of an alarm monitoring system according to an embodiment of the present invention. The flowchart 700 of the alarm trend analysis of an alarm monitoring system includes the following steps:

[0074] Step S701: Enable the alarm trend analysis function on the front-end monitoring page. The scope of data analysis and the start and end time need to be specified. In the scenario where there is a lot of alarm data, big data analysis can be enabled, and relevant models need to be established in advance.

[0075] Step S702: Analyze the alarm data within the specified range and the specified start and end time.

[0076] Step S703: Highlight the subsystems and status values ​​that generate more alarms.

[0077] Step S704: Provide statistical charts of subsystems and status values ​​that generate more alarms in terms of time, space, and other dimensions.

[0078] Figure 8 This is a schematic diagram of a push process of an alarm monitoring system according to an embodiment of the present invention. The push process 800 of the alarm monitoring system includes the following steps:

[0079] Step S801: Determine the push methods and targets supported by the alarm monitoring system. The push methods include MQ, WEBSOCKET, short messages, emails, etc. The push target refers to the page to be pushed.

[0080] Step S802: Determine the push rules of the alarm monitoring system. The rules specifically refer to the keywords contained in the alarms, work orders, etc. that need to be pushed.

[0081] Step S803: Push content that meets the conditions.

[0082] Fig. 9 This is a schematic diagram of a process editing process of an alarm monitoring system according to an embodiment of the present invention. The process 900 of the process editing process of the alarm monitoring system includes the following steps:

[0083] Step S901: Open the editing interface of the alarm process or work order process on the front-end monitoring page.

[0084] Step S902: Drag, add, delete, and modify graphics in the editing interface to add, delete, and modify process nodes.

[0085] Step S903: Drag, add, delete, and modify actions in the editing interface to add, delete, and modify process change conditions.

[0086] Step S904: Save after editing is completed.

[0087] Step S905: Determine the closure of the process, save the flowchart information and enable it.

[0088] Fig.101000 is a flow chart of system linkage of an alarm monitoring system according to an embodiment of the present invention. The process 1000 of system linkage of an alarm monitoring system includes the following steps:

[0089] Step S1001: Configure linkage rules and actions on the front end. The linkage rules refer to the conditions that the alarm meets to trigger linkage, such as alarm level, alarm time, alarm trend change, alarm content, etc. The linkage action refers to the subsequent processing, such as transfer work order, push, recovery, etc.

[0090] Step S1002: Read relevant linkage configuration information when an alarm is generated or received.

[0091] Step S1003: Perform subsequent processing according to the linkage configuration information.

[0092] According to the microservice-based alarm monitoring system for rail transit provided by the present invention, by integrating multiple microservices in the same module, when there is a specific demand for upgrading the alarm monitoring system, the original functions can be freely expanded, upgraded, and optimized, thereby improving the diversity, scalability, compatibility, portability, etc. of alarm-related functions, and at the same time can greatly reduce operation and maintenance and redevelopment costs.

[0093] In order to implement the above embodiment, the present invention further provides an electronic device, which includes the above provided microservice-based alarm monitoring system for rail transit.

[0094] In one embodiment, the electronic device includes a processor, which can be implemented as software, hardware, firmware or any combination thereof, and can use a single or multiple application-specific integrated circuits (ASICs), a single or multiple general-purpose integrated circuits, a single or multiple microprocessors, a single or multiple programmable logic devices, or any combination of the foregoing circuits and / or devices, or other suitable circuits or devices.

[0095] In one embodiment, the electronic device further includes a memory, which may be a flash memory card, a solid-state memory, a hard disk, etc. It may be a volatile memory and / or a non-volatile memory, a removable memory and / or a non-removable memory, etc.

[0096] Although example embodiments have been described herein with reference to the accompanying drawings, it should be understood that the above example embodiments are merely exemplary and are not intended to limit the scope of the present application to this. Those of ordinary skill in the art may make various changes and modifications therein without departing from the scope and spirit of the present application. All these changes and modifications are intended to be included within the scope of the present application as required by the appended claims.

[0097] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0098] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.

[0099] In the description provided herein, a large number of specific details are described. However, it is understood that the embodiments of the present application can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.

[0100] Similarly, it should be understood that in order to streamline the present application and help understand one or more of the various inventive aspects, in the description of the exemplary embodiments of the present application, the various features of the present application are sometimes grouped together into a single embodiment, figure, or description thereof. However, the method of the present application should not be interpreted as reflecting the following intention: the claimed application requires more features than the features clearly stated in each claim. More specifically, as reflected in the corresponding claims, the inventive point is that the corresponding technical problem can be solved with features less than all the features of a single disclosed embodiment. Therefore, the claims following the specific embodiment are hereby explicitly incorporated into the specific embodiment, wherein each claim itself serves as a separate embodiment of the present application.

[0101] It will be understood by those skilled in the art that, except for mutually exclusive features, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this specification may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature that provides the same, equivalent or similar purpose.

[0102] In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present application and form different embodiments. For example, in the claims, any one of the claimed embodiments can be used in any combination.

[0103] The various component embodiments of the present application can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all of the functions of some modules in the article analysis device according to the embodiment of the present application. The present application can also be implemented as a device program (e.g., computer program and computer program product) for executing part or all of the methods described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0104] It should be noted that the above embodiments illustrate the present application rather than limit the present application, and that those skilled in the art may design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets should not be constructed as a limitation to the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of multiple such elements. The present application may be implemented by means of hardware including several different elements and by means of a suitably programmed computer. In a unit claim that lists several devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names.

[0105] The above is only a specific implementation or description of a specific implementation of the present application, and the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. The protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A microservice-based alarm monitoring system for rail transit, It is characterized in that include: A signal acquisition module, used for acquiring an alarm signal; A resource allocation module, which is deployed in a cloud service in a microservice manner based on the acquired alarm signal to allocate resources for processing the alarm signal; A service integration module, used to integrate the multiple microservices into the same module; A display module is used to display the microservices provided by the service integration module.

2. The alarm monitoring system according to claim 1, It is characterized in that The multiple microservices include one or more of real-time alarms, historical alarms, alarm monitoring, alarm conversion to work orders, alarm processes, and alarm statistics.

3. The alarm monitoring system according to claim 1, It is characterized in that The multiple microservices include one or more of real-time alarm service, historical alarm service, alarm status service, data persistence service, alarm status migration service, user service, equipment information service, maintenance service, notification service, monitoring service, message service, interface service, heartbeat service, microservice framework, linkage service, and work order service.

4. The alarm monitoring system according to claim 1, It is characterized in that It also includes an interface for interaction, which includes one or more of a microservice interface, a representative state transfer interface, and a message queue. The interface supports one or more of a message queue, a Modbus communication protocol, and an open platform communication unified architecture.

5. The alarm monitoring system according to claim 1, It is characterized in that The alarm monitoring system adopts a framework combining a browser and a server.

6. The alarm monitoring system according to claim 1, It is characterized in that The alarm monitoring system includes a front-end monitoring page and a back-end capability center.

7. The alarm monitoring system according to claim 6, It is characterized in that The front-end monitoring page uses front-end components, and the front-end components include one or more of HTML, JAVASCRIPT, CSS, JQUERY, WEBSOCKET, flow chart editing components, statistical chart components, and configuration components.

8. The alarm monitoring system according to claim 6, It is characterized in that The background capability center integrates one or more of WEBSOCKET components, REST interfaces, microservice interfaces, encryption services, time series databases, cloud service components, database services, log services, MQ protocols, MODBUS protocols, OPC UA protocols, SMS services, email services, timing services, statistical services, trend forecasting services, data analysis services, custom process services, process change services, and backup and restore.

9. The alarm monitoring system according to claim 6, It is characterized in that The front-end monitoring page provides one or more of real-time alarms, historical alarms, alarm statistics, alarm operations, alarm status changes, alarm conversion to work orders, work order management, work order process changes, work order processing, process editing, alarm configuration display, alarm trend prediction, basic information display, basic information entry, external channels, log display, and alarm configuration; the back-end capability center provides one or more of real-time alarms, historical alarms, alarm statistics, alarm status, work order services, work order processes, alarm processes, alarm trends, basic information, log services, heartbeat services, channel services, push services, persistence services, backup and restore, and linkage services.

10. An electronic device, It is characterized in that A microservice-based alarm monitoring system for rail transit provided by any one of claims 1 to 9.

Citation Information

Patent Citations

  • Rail transit information system cloud platform

    CN109741001A

  • Rail traffic light current integrated system

    CN109747682A

  • Rail transit public cloud service system based on micro-service architecture

    CN110427676A

  • Rail transit operation and maintenance management system based on micro-service architecture

    CN110949458A

  • Alarm system

    CN113141485A