Message non-landing network management alarm processing method and device

Abstract

The invention provides a message non-landing network management alarm processing method and device. The method comprises the following steps: calling a northbound interface of a manufacturer through a collection adapter developed based on a JAVA language, and obtaining alarm data; the collection adapter converts the alarm data into a user-defined general alarm format to form a general alarm event of the general alarm format; the general alarm event is stored in a Linked Block Queue message queue, and messages in the Linked Block Queue message queue are periodically transferred to a common message queue to be sent to middleware in a point-to-point information transmission model; the WebSocket message fed back by the middleware is received, and the WebSocket message is displayed on a front end page; wherein the WebSocket message comprises the alarm data processed by the middleware and the alarm data generated by the middleware. According to the invention, the alarm data can be timely processed and reported, and non-landing transmission of network management alarm information is realized.

Description

technical field [0001] The invention relates to the technical field of communication network data processing, in particular to a network management alarm processing method and device for which messages do not land. Background technique [0002] With the continuous expansion of the network scale, the network system is becoming more and more complex, and at the same time, there are many manufacturers and equipment involved in the communication field, which increases the amount of data to be processed by the integrated network management. The integrated network management system mainly consists of a collection adapter, front-end system page, back-end database, and front-end database to form a complete system structure. The acquisition adapter extracts data through the northbound interface provided by the manufacturer's network management, and the manufacturer's network management reports the data to the acquisition adapter through its respective northbound interface. The previo...

AI Technical Summary

Problems solved by technology

Although this technology can communicate in two directions, it still needs to make repeated requests

And in Comet, the commonly used long links will also consume server resources

Regular polling takes a long time and is inefficient

For example, in the past, if the client wanted to know the processing progress of the server, it had to use Ajax to poll continuously, and let the browser send a request to the server every few seconds, which put a lot of pressure on the server.

Another kind of polling is to use long poll, which is similar to making a phone call. If you do not receive a message, you will not hang up the phone. That is to say, after the client initiates a connection, if there is no message, it will not return a Response to the client. , the connection phase is always blocked

Images