Message unified scheduling method and system based on operation and maintenance center system

Abstract

The invention discloses a unified message scheduling method based on an operation and maintenance center system. The method comprises the following steps: S1, constructing a unified message scheduling center; s2, the alarm information of a plurality of operation and maintenance center systems is accessed to the message unified dispatching center through respective interfaces; s3, based on the message, processing and storing the alarm information and waiting for calling by the unified dispatching center; and S4, the message unified scheduling center performs timed task, performs timed scheduling and pushes corresponding alarm information to a plurality of operators. The invention also discloses a corresponding system, an electronic device and a computer readable storage medium, the information can be pushed to the operation and maintenance personnel in a centralized, efficient and timely manner only through one unified message dispatching center, and the purposes of reducing the troubleshooting work pressure of the operation and maintenance personnel, improving the operation and maintenance efficiency and reducing the operation and maintenance cost are achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of information maintenance and scheduling, and particularly to a method and system for unified message scheduling based on an operation and maintenance center system. Background Art

[0002] With the progress of technology and the continuous development of business, there are currently many services in the prior art that build operation and maintenance systems for enterprises or medical institutions, thus providing a set of corresponding process-based maintenance means for customers. However, the operation and maintenance systems of each customer operate independently, and the alarm messages are also pushed independently. The traditional solution is to directly push messages to each operation and maintenance system through an interface, which not only has duplicate functions, but also may cause problems such as untimely and lost message pushing, resulting in low operation and maintenance efficiency.

[0003] Therefore, how to uniformly manage the alarm messages of multiple operation and maintenance systems, eliminate the duplicate message pushing functions of each operation and maintenance system, realize the centralized, efficient, and timely pushing of alarm messages to operation and maintenance personnel, reduce the troubleshooting work pressure of operation and maintenance personnel, improve operation and maintenance efficiency, and reduce operation and maintenance costs has become a major problem in this industry. Summary of the Invention

[0004] In order to solve the problems existing in the prior art, the present invention provides a method and system for unified message scheduling based on an operation and maintenance center system, so that the alarm messages of each subordinate operation and maintenance system can be centralized in the unified message scheduling center, and it is realized that only through a unified message scheduling center can the messages be pushed to operation and maintenance personnel in a centralized, efficient, and timely manner, solve the pain points of alarm message pushing in the current operation and maintenance center system, improve the operation and maintenance efficiency of this industry, reduce operation and maintenance costs, and achieve the purpose of reducing the troubleshooting work pressure of operation and maintenance personnel.

[0005] On the one hand, the present invention provides a method for unified message scheduling based on an operation and maintenance center system, including:

[0006] S1, constructing a unified message scheduling center;

[0007] S2, accessing the alarm information of multiple operation and maintenance center systems into the unified message scheduling center through their respective interfaces;

[0008] S3, processing and storing the alarm information based on the unified message scheduling center and waiting for invocation;

[0009] S4, the unified message scheduling center schedules and pushes the corresponding alarm information to multiple operators at regular intervals by executing a scheduled task.

[0010] Preferably, the S1 includes:

[0011] S11. Build an interface layer and a channel layer, where the channel layer accommodates one or more message channels;

[0012] S12. Build a queue layer, which is implemented as an MQ.

[0013] S13. Build a processing layer, which is used to preprocess the alarm information. The preprocessing includes cleaning, filtering, assembling, and deduplicating the alarm information;

[0014] S14. Build a storage layer. In this embodiment, a database is used as the main architecture of the storage layer;

[0015] S15. Build a scheduling layer, which is used to push the alarm messages stored in the storage layer to relevant operation personnel in a timely manner according to the specified message channels by executing scheduled tasks, and support querying the alarm message push results or retrying the failed alarm information push, so as to ensure that the alarm messages are not missed or under-sent.

[0016] Preferably, the message channels include pc, sms, email, wechat, wecom, or dingtalk.

[0017] Preferably, the protocol of the interface layer is formed by Feign API.

[0018] Preferably, the S2 includes:

[0019] S21. Connect the alarm information of multiple operation and maintenance center systems to the interface layer of the message unified scheduling center through their respective interfaces, so as to push the alarm messages generated during the operation and maintenance process of multiple operation and maintenance center systems into the message unified scheduling center, and specify the message channels and operation personnel groups or operation personnel sets to which the messages are to be pushed. The message channels are one or more. If there are multiple message channels, separate each message channel with a comma, and each message channel has a different custom push method;

[0020] S22. After the message unified scheduling center receives one or more alarm messages, write the alarm messages into the message queue in the queue layer.

[0021] Preferably, the S3 includes:

[0022] S31. Based on the processing layer of the message unified scheduling center, preprocess the alarm information. The preprocessing includes cleaning, filtering, assembling, and deduplicating the alarm information;

[0023] S32. Based on the storage layer of the message unified scheduling center, store and write the preprocessed alarm information into the database and wait for invocation.

[0024] Preferably, the S4 includes:

[0025] S41, ensuring that the application has enabled the timed task scheduling function by adding the annotation @EnableScheduling in the Application class;

[0026] S42, setting the timed task through the annotation @Scheduled and the Cron expression;

[0027] S43, obtaining the list of alarm messages that have not been pushed and those with push failures and traversing the list of alarm messages;

[0028] S44, respectively calling the corresponding message channel push method according to the definition of the message channel enumeration, and pushing the alarm messages in the list of alarm messages to the specified members of the operation staff group.

[0029] The second aspect of the present invention provides a message unified scheduling system based on an operation and maintenance center system for implementing the method of the first aspect, including:

[0030] A message unified scheduling center construction module (101) for constructing a message unified scheduling center;

[0031] An alarm information access module (102) for accessing the alarm information of multiple operation and maintenance center systems into the message unified scheduling center through their respective interfaces;

[0032] An alarm information processing and storage module (103) for processing and storing the alarm information based on the message unified scheduling center and waiting for invocation;

[0033] An information scheduling and push module (104) for the message unified scheduling center to schedule and push the corresponding alarm information to multiple operation staff at regular intervals by executing a timed task.

[0034] The third aspect of the present invention provides an electronic device including a processor and a memory, where the memory stores multiple instructions, and the processor is configured to read the instructions and execute the method described in the first aspect.

[0035] The fourth aspect of the present invention provides a computer-readable storage medium storing multiple instructions, and the multiple instructions can be read and executed by a processor to execute the method described in the first aspect.

[0036] The method, system, and electronic device provided by the present invention have the following beneficial effects:

[0037] Based on the centralized unified management of the alarm messages of each operation and maintenance center system by the message unified scheduling center, through the method of unified scheduling of alarm messages, the function of the traditional individual operation and maintenance center systems to repeatedly push alarm messages independently is broken, and a centralized, efficient, stable, timely, and non-missing or redundant message unified scheduling center is realized. It avoids the duplication and isolation of the message push functions of each operation and maintenance center system, and may cause problems such as untimely and lost message pushing, reduces the troubleshooting work pressure of operation and maintenance personnel, improves operation and maintenance efficiency, reduces operation and maintenance costs, and becomes an indispensable part of the modern operation and maintenance management system, providing a more efficient, convenient, and stable alarm message pushing method for the company and operation and maintenance personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a flowchart of the message unified scheduling method based on the operation and maintenance center system according to an embodiment of the present invention;

[0039] Figure 2 It is a schematic structural diagram of the principle of the message unified scheduling method based on the operation and maintenance center system according to an embodiment of the present invention;

[0040] Figure 3 It is an architecture diagram of the message unified scheduling system based on the operation and maintenance center system according to an embodiment of the present invention;

[0041] Figure 4 It is a schematic structural diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0042] In order to better understand the above technical solutions, the following will describe the above technical solutions in detail in conjunction with the accompanying drawings of the specification and specific embodiments.

[0043] The message unified scheduling center plays a crucial role. The following are the functions of the message unified scheduling center:

[0044] 1. Ensure the stability and consistency of message transmission:

[0045] The message unified scheduling center can build a highly scalable, highly reusable, and highly stable communication architecture, realize easy docking and flexible switching of message channels, and a fault automatic degradation protection mechanism, ensuring the stability and consistency of message transmission.

[0046] 2. Improve the system response speed and data processing ability:

[0047] By adopting a message-driven mechanism and optimizing the association relationship between background databases, the message unified scheduling center can significantly improve the system response speed and facilitate the coherent execution of work flows and task flows.

[0048] 3. Facilitate maintenance, expansion, and monitoring:

[0049] The message unified scheduling center can sort out the data stream, provide running data metrics, achieve visual management, facilitate the maintenance and expansion of the system, and shorten the fault discovery time and processing time.

[0050] 4. Optimize the operation and maintenance process to improve efficiency:

[0051] The message unified scheduling center can allocate various tasks according to different business requirements. In this way, various business processes can be processed more accurately and quickly, effectively improving efficiency and reducing communication costs. At the same time, the probability of major technical failures is reduced, further ensuring the stability of enterprise operations.

[0052] Embodiment 1

[0053] As Figure 1-2 shown, this embodiment provides a message unified scheduling method based on an operation and maintenance center system, including:

[0054] S1. Build a message unified scheduling center;

[0055] S2. Connect the alarm information of multiple operation and maintenance center systems to the message unified scheduling center through their respective interfaces;

[0056] S3. Process and store the alarm information based on the message unified scheduling center and wait for invocation;

[0057] S4. The message unified scheduling center schedules and pushes the corresponding alarm information to multiple operators at regular intervals by executing a scheduled task.

[0058] As a preferred implementation manner, the S1 includes:

[0059] S11. Build an interface layer and a channel layer. The channel layer accommodates one or more message channels, and the message channels include pc, sms, email, wechat, wecom, or dingtalk. In this embodiment, the Feign API is used to form the protocol of the interface layer. Of course, those skilled in the art should know that other protocol forms can also be used, which are all within the protection scope of the present invention.

[0060] Feign is a declarative web service client that simplifies the calls between microservices. By integrating Ribbon, Feign achieves load balancing. Feign is a declarative and modular HTTP client developed by Netflix, enabling faster invocation of HTTP APIs in an interface-oriented and annotation-based manner. When using Feign with a load-balanced http client, only an interface needs to be created and then annotations are added to the interface. Feign replaces RestTemplate, with a performance degradation but enhanced code readability. Feign invokes the Rest service through the methods of the interface, sends the request to the Eureka server, and directly locates the service interface through Feign. Since Ribbon is integrated during service invocation, it is the built-in Ribbon in Feign that plays the role of load balancing, rather than Feign itself.

[0061] S12. Construct a queue layer. In this embodiment, the queue layer is implemented as MQ.

[0062] S13. Construct a processing layer, which is used to preprocess the alarm information. The preprocessing includes cleaning, filtering, assembling, and deduplicating the alarm information.

[0063] S14. Construct a storage layer. In this embodiment, a database is used as the main architecture of the storage layer.

[0064] S15. Construct a scheduling layer, which is used to, by executing a scheduled task, push the alarm messages stored in the storage layer to relevant operation personnel in accordance with the specified message channels in a timely manner, and support querying the push results of the alarm messages or retrying the failed push of the alarm information, so as to ensure that the alarm messages are not missed or under-sent.

[0065] As a preferred implementation, the S2 includes:

[0066] S21. Connect the alarm information of multiple operation and maintenance center systems (in this embodiment, as shown in Figure 2 , there are three operation and maintenance center systems A, B, and C in total) to the interface layer of the message unified scheduling center through their respective interfaces, so as to push the alarm messages generated during the operation and maintenance processes of multiple operation and maintenance center systems into the message unified scheduling center, and specify the message channels and operation personnel groups or operation personnel sets to which the messages are to be pushed. The message channels are one or more. If there are multiple message channels, each message channel is separated by a comma, and each message channel has a custom different push method.

[0067] S22. After the message unified scheduling center receives one or more alarm messages, write the alarm messages into the message queue in the queue layer.

[0068] As a preferred embodiment, S3 includes:

[0069] S31, preprocessing the alarm information based on the processing layer of the message unified scheduling center, where the preprocessing includes cleaning, filtering, assembling, and deduplicating the alarm information;

[0070] S32, storing the preprocessed alarm information into a database based on the storage layer of the message unified scheduling center and waiting for invocation.

[0071] As a preferred embodiment, S4 includes:

[0072] S41, ensuring that the application has enabled the timed task scheduling function; in this embodiment, by adding the annotation @EnableScheduling in the Application class to ensure that the application has enabled the timed task scheduling function;

[0073] S42, setting the timed task through the annotation @Scheduled and the Cron expression. For example, adding @Scheduled(cron = "0 / 3 * * * *?") to a specified method to set the timed task to execute every 3 seconds: query the database message push table;

[0074] S43, obtaining the list of alarm messages that have not been pushed and those with push failures and traversing the list of alarm messages;

[0075] S44, respectively calling the corresponding message channel push methods according to the message channel enumeration definition to push the alarm messages in the list of alarm messages to the specified members of the operation staff grouping (in this embodiment, as Figure 2 shown, there are three operation staff members A, B, and C).

[0076] Embodiment 2

[0077] As Figure 3 shown, this embodiment provides a message unified scheduling system based on an operation and maintenance center system for implementing the method of Embodiment 1, including:

[0078] A message unified scheduling center construction module 101 for constructing a message unified scheduling center;

[0079] An alarm information access module 102 for accessing the alarm information of multiple operation and maintenance center systems into the message unified scheduling center through their respective interfaces;

[0080] An alarm information processing and storage module 103 for processing and storing the alarm information based on the message unified scheduling center and waiting for invocation;

[0081] An information scheduling and pushing module 104 is used for the message unified scheduling center to schedule and push corresponding alarm information to multiple operation personnel at regular intervals by executing timing tasks.

[0082] The present invention also provides a memory storing multiple instructions for implementing the method as in Embodiment 1.

[0083] As Figure 4 shown, the present invention also provides an electronic device, including a processor 301 and a memory 302 connected to the processor 301. The memory 302 stores multiple instructions that can be loaded and executed by the processor, enabling the processor to execute the method as in Embodiment 1.

[0084] Although the preferred embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications to these embodiments once they know the basic creative concept. Therefore, the appended claims are intended to be construed as including the preferred embodiments and all changes and modifications falling within the scope of the present invention. Obviously, those skilled in the art can make various changes and variations to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims

1. A message unified scheduling method based on an operation and maintenance center system, characterized in that: include: S1, build a unified message dispatch center; S2, connecting the alarm information of multiple operation and maintenance center systems to the message unified dispatch center through their respective interfaces; S3, based on the message, the unified dispatch center processes and stores the alarm information and waits for calling; S4, the unified message dispatching center executes scheduled tasks, regularly dispatches and pushes corresponding alarm information to multiple operators.

2. A message unified scheduling method based on an operation and maintenance center system according to claim 1, characterized in that: The S1 includes: S11, constructing an interface layer and a channel layer, wherein the channel layer accommodates one or more message channels; S12, constructing a queue layer, wherein the queue layer is implemented as MQ. S13, constructing a processing layer, wherein the processing layer is used to pre-process the alarm information, wherein the pre-processing includes cleaning, filtering, assembling and deduplication of the alarm information; S14, constructing a storage layer. In this embodiment, a database is used as the main architecture of the storage layer; S15, construct a scheduling layer, which is used to push the alarm messages stored in the storage layer to relevant operation personnel in a timely manner through the execution of scheduled tasks according to the specified message channel, and supports query of alarm message push results or retry of alarm message push failure, so as to ensure that the alarm message will not be missed or under-sent.

3. A message unified scheduling method based on an operation and maintenance center system according to claim 2, characterized in that: The message channel includes PC, SMS, email, WeChat, Wecom or DingTalk.

4. A message unified scheduling method based on an operation and maintenance center system according to claim 3, characterized in that: The Feign API is used to form the protocol of the interface layer.

5. A message unified scheduling method based on an operation and maintenance center system according to claim 4, characterized in that: The S2 includes: S21, connect the alarm information of multiple operation and maintenance center systems to the interface layer of the message unified dispatch center through their respective interfaces, so as to push the alarm messages generated by the operation and maintenance process of the multiple operation and maintenance center systems to the message unified dispatch center, and specify the message channel and operator group or operator set to be pushed, the message channel is one or more, if there are multiple message channels, each message channel is separated by a comma, and each message channel has a customized different push method; S22, after the message unified dispatch center receives one or more alarm messages, the alarm message is written into the message queue in the queue layer.

6. A message unified scheduling method based on an operation and maintenance center system according to claim 5, characterized in that: The S3 includes: S31, pre-processing the alarm information based on the processing layer of the message unified dispatch center, wherein the pre-processing includes cleaning, filtering, assembling and deduplication of the alarm information; S32, based on the storage layer of the message unified dispatch center, the pre-processed alarm information is stored in a database and waits for calling.

7. A message unified scheduling method based on an operation and maintenance center system according to claim 6, characterized in that: The S4 includes: S41, add the annotation @EnableScheduling to the Application class to ensure that the scheduled task scheduling function is enabled for the application; S42, setting the scheduled task through the annotation @Scheduled and the Cron expression; S43, obtaining a list of warning messages that have not been pushed or have failed to be pushed and traversing the list of warning messages; S44, according to the message channel enumeration definition, respectively call the corresponding message channel push method to push the alarm message in the alarm message list to the designated operator group members.

8. A message unified dispatching system based on an operation and maintenance center system, used to implement any of the methods described in claims 1-7, characterized in that: include: A message unified dispatch center construction module (101), used to construct a message unified dispatch center; An alarm information access module (102) is used to access the alarm information of multiple operation and maintenance center systems to the message unified dispatch center through their respective interfaces; An alarm information processing and storage module (103) is used to process and store the alarm information based on the message unified dispatch center and wait for calling; The information scheduling and pushing module (104) is used for the message unified scheduling center to perform scheduled tasks, schedule and push corresponding alarm information to multiple operators.

9. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a plurality of instructions, and the processor is used to read the instructions and execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the plurality of instructions can be read by a processor to execute the method according to any one of claims 1 to 7.

Images