CN112039681A - Alarm reporting method and device - Google Patents
Alarm reporting method and device Download PDFInfo
- Publication number
- CN112039681A CN112039681A CN201910477364.1A CN201910477364A CN112039681A CN 112039681 A CN112039681 A CN 112039681A CN 201910477364 A CN201910477364 A CN 201910477364A CN 112039681 A CN112039681 A CN 112039681A
- Authority
- CN
- China
- Prior art keywords
- alarm
- lost
- alarms
- database
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000012544 monitoring process Methods 0.000 claims description 22
- 238000012545 processing Methods 0.000 claims description 18
- 230000000295 complement effect Effects 0.000 claims description 10
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims description 8
- 238000007726 management method Methods 0.000 description 17
- 238000004590 computer program Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000008034 disappearance Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000005065 mining Methods 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/06—Generation of reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L41/064—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
Abstract
The invention provides an alarm reporting method and device, wherein the method comprises the following steps: subscribing to an alarm from an Element Management System (EMS); adding an alarm running identifier for the subscribed alarms, and storing the alarms to an alarm database; and reporting the alarm to a northbound interface. In the invention, before the alarm is reported to the northbound interface, the alarm running ID is added to the alarm and stored in the alarm database, so that the northbound interface can judge whether the alarm is lost or not according to the alarm running ID after receiving the alarm, thereby being capable of re-collecting the lost alarm from the database.
Description
Technical Field
The invention relates to the field of communication, in particular to an alarm reporting method and device.
Background
A North Bound Interface (NBI) of a network manager is Interface software that is provided by an EMS network manager to an integrated network manager system (OSS) and accesses the EMS network manager, which can provide a public management function, a security management function, a configuration management function, a performance management function, and a fault management function to the integrated network manager, where fault management is one of the main monitoring methods for the integrated network manager to monitor various devices through the NBI.
With the rapid development of the communication industry, the types and the number of communication devices are continuously increased, the number of alarms is increased day by day, in order to better monitor and maintain the network devices, the northbound interface is required to report the alarms in real time, and higher requirements are provided for the integrity and timeliness of the reported alarms. However, due to various reasons, the problems of inconsistency between the north-direction reported alarm and the EMS alarm, loss of the alarm and the like may occur. Once the lost alarm cannot be found in time and reported to the upper layer network management again, the fault cannot be solved in time, and thus the normal operation of the whole network is seriously affected.
Disclosure of Invention
The embodiment of the invention provides an alarm reporting method and device, which are used for at least solving the problem of alarm loss caused by reasons such as abnormal northbound interface in the related technology.
According to an embodiment of the present invention, an alarm reporting method is provided, including: subscribing to an alarm from an Element Management System (EMS); adding an alarm running identifier for the subscribed alarms, and storing the alarms to an alarm database; and reporting the alarm to a northbound interface.
Wherein, before adding the warning running water mark for each warning obtained, still include: and carrying out standardized processing on the subscribed alarms.
Wherein, the method also comprises: after receiving the alarm, the northbound interface judges whether the alarm is lost or not according to the continuity of the alarm running water identifier; if the alarm is lost, the lost alarm is collected from the database.
Wherein, judge whether to report an emergency and ask for help or increased vigilance according to the continuity of reporting an emergency and asking for help or increased vigilance flowing water mark and lose, include: caching the alarm flow identifier of each received alarm, comparing the alarm flow identifier of the currently received alarm with the alarm flow identifier of the last received alarm, and determining that the alarm is lost if the alarm flow identifiers are discontinuous.
Wherein, the method also comprises: judging whether the database has an overdue alarm or not; and if the alarm with the expiration exists, deleting the alarm with the expiration.
Wherein, before judging whether there is an alarm of an overdue in the database, the method further comprises: setting an expiration time for the alarms stored in the database.
According to another embodiment of the present invention, an alarm reporting apparatus is provided, including: the subscription module is used for subscribing the alarm from an Element Management System (EMS); the storage module is used for adding an alarm running identifier for the subscribed alarms and storing the alarms to an alarm database; and the reporting module is used for reporting the alarm to a northbound interface.
Wherein, the device still includes: and the standardization processing module is used for standardizing the subscribed alarms before adding the alarm flow identifier.
Wherein, the device still includes: the monitoring module is used for judging whether the alarm is lost or not according to the continuity of the alarm running water mark after the northbound interface receives the alarm; and the alarm complementary acquisition module is used for complementarily acquiring the lost alarm from the database under the condition that the alarm is lost.
Wherein, the device still includes: and the overdue alarm clearing module is used for judging whether an overdue alarm exists in the database or not, and deleting the overdue alarm if the overdue alarm exists.
According to yet another embodiment of the present invention, there is also provided a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of the above-mentioned method embodiments when executed.
According to yet another embodiment of the present invention, there is also provided an electronic device, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in the above method embodiments.
In the above embodiment of the present invention, before the alarms are reported to the northbound interface, the alarm running ID is added for each alarm and stored in the alarm database, so that after the northbound interface receives the alarms, whether the alarms are lost or not can be determined according to the alarm running ID, and the lost alarms can be collected from the database again.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a flowchart of an alarm reporting method according to an embodiment of the present invention;
fig. 2 is a block diagram of an alarm reporting device according to an embodiment of the present invention;
fig. 3 is a block diagram of an alarm reporting device according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of an alarm complement acquisition device according to another embodiment of the invention;
FIG. 5 is a process flow diagram of an alarm normalization processing module according to an embodiment of the invention;
FIG. 6 is a process flow diagram of an alert database storage module according to an embodiment of the present invention;
FIG. 7 is a process flow diagram of an alarm continuity monitoring module according to an embodiment of the present invention;
FIG. 8 is a flow chart of the processing of the alarm auto-replenishment collection module according to an embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
In this embodiment, an alarm reporting method is provided, and fig. 1 is a flowchart according to an embodiment of the present invention, and as shown in fig. 1, the flowchart includes the following steps:
step S102, subscribing alarm from EMS;
step S104, adding alarm running marks for the subscribed alarms, and storing the alarms to an alarm database;
and step S106, reporting the alarm to a northbound interface.
In the step S102, various alarms and message alarms generated from the EMS network manager may be obtained through subscription.
In the above embodiment, the alarms may also be standardized and converted before being stored in the database based on the TMF international standard, and then the alarms are stored in the database after adding the alarm pipeline ID to each alarm.
In step S104, the main purpose of adding the alarm pipeline ID is to facilitate monitoring whether the alarms are continuous, and using a single database table can store the generated alarms and the disappeared alarms in the same table of the database, thereby facilitating the judgment of alarm continuity, and solving the problem that the previous alarms are reported directly after being subscribed by the EMS, and cannot be synchronized to the lost alarms if the alarms are lost.
In the embodiment, because the generated alarm and the message alarm are both stored in the same table, pressure may be generated on the database due to the fact that the alarm amount is too large, the overtime time can be configured in advance according to different network scales through the database timing clearing configuration, the overtime alarm is automatically cleared when the alarm in the database table exceeds the configured time, the database pressure is reduced, and the engineering site can be flexibly configured according to the network scale and the alarm amount of the engineering site because the overtime time is configurable content.
In step S106, after the alarm standardization process is completed, the alarm is stored in the database and reported to the northbound interface in real time.
In the above embodiment, after receiving the reported alarm, the northbound interface may determine whether the reported alarm is continuous through the alarm continuity monitoring system, and if the reported alarm is not continuous, the automatic alarm replenishment acquisition module is automatically started, and the automatic alarm replenishment acquisition module accurately locates which of the lost alarms through the alarm ID, and then replys the lost alarm from the database.
The targeted alarm compensation can ensure that the alarm in the compensation collection is not repeated, the automatic monitoring and compensation of the connectivity can improve the finding speed of the lost alarm, and the user can complete the alarm compensation collection under the condition that the user does not perceive the alarm loss.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (which may be a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
In this embodiment, an alarm reporting device is further provided, where the alarm reporting device is used to implement the foregoing embodiments and preferred embodiments, and details of the implementation are not described again. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 2 is a block diagram of an alarm reporting device according to an embodiment of the present invention, and as shown in fig. 2, the device includes a subscription module 10, a storage module 20, and a reporting module 30.
The subscription module 10 is used for subscribing to an alarm from an element management system EMS. The storage module 20 is configured to add an alarm flow identifier to the subscribed alarms and store the alarms in an alarm database. The reporting module 30 is configured to report the alarm to the northbound interface.
As shown in fig. 3, in another embodiment, the alarm reporting apparatus may further include a standardization processing module 40, a monitoring module 50, an alarm complementary collection module 60, and an overdue alarm clearing module 70, in addition to the above modules.
The standardization processing module 40 is configured to standardize the subscribed alarms before adding the alarm flow identifier. The monitoring module 50 is configured to determine whether there is a warning loss according to the continuity of the warning pipeline identifier after the northbound interface receives the warning. The alarm complementary collection module 60 is configured to collect the lost alarm from the database in a complementary manner in the case that the alarm is lost. The overdue alarm clearing module 70 is configured to determine whether there is an overdue alarm in the database, and delete the overdue alarm if there is an overdue alarm.
The technical solution provided by the present invention is described in detail by a specific embodiment.
In the embodiment, a technical scheme of automatic supplementary acquisition of an alarm based on a northbound interface is provided. Firstly, subscribing alarms from EMS, carrying out standardization conversion on the subscribed alarms according to TMF international standard, and then adding alarm flow ID for each alarm for the following alarm continuity monitoring. The converted alarm is reported to the north interface and stored in the alarm database. After receiving the alarm, the northbound interface judges whether the alarm is lost or not according to the alarm running water ID through the alarm continuity monitoring module. If the alarm is lost, the automatic alarm compensation collection is automatically started, and the lost alarm is compensated and collected again from the database and reported to the upper network management.
In this embodiment, the database table is introduced to store the alarm, so that the problem that the lost alarm cannot be acquired again if the alarm is lost in the prior art that the north interface directly subscribes to report the alarm can be solved, the alarm running ID is added to the standardized alarm, which lost alarms can be accurately monitored, and the lost alarm can be quickly acquired.
The present embodiment is different from the previous embodiments in the division of function modules, and specifically, as shown in fig. 4, the present embodiment includes an alarm standardization processing module 100, an alarm database storage module 200, an alarm continuity monitoring module 300, and an alarm automatic complementary acquisition module 400. In this embodiment, accurate identification and automatic replenishment of the loss alarm of the northbound interface are completed through the 4 modules, so that the problem of loss of the loss alarm of the northbound interface is solved.
The following describes the processing flow of the above 4 modules in detail.
In this embodiment, the alarm standardization processing module 100 is mainly responsible for initiating an alarm subscription to the EMS network manager, standardizing the subscribed alarm, and then adding an alarmSeqID value to be used for alarm continuity determination. As shown in fig. 5, the method comprises the following steps:
step S501: and initializing an alarm standardization processing module.
Step S502: subscribing to EMS, if the subscription fails, subscribing to the bottom EMS once again at a certain time interval, if the subscription succeeds, entering step S503
Step S503: and monitoring and receiving an EMS (enhanced message service) reported alarm.
Step S504: and (4) performing standard on the alarm based on TMF international standard, and advancing the alarm standardization processing to ensure that the reported alarm is consistent with the warehousing alarm.
Step S505: adding an alarm running water identifier (alarmseqID) for each alarm, wherein the addition of each added alarmseqID is 1, and the introduction of the alarmseqID can ensure that each alarm has a unique alarm identifier, so that a subsequent alarm continuity monitoring module can judge whether the alarm is lost through the alarmseqID and determine which alarm is lost, and then automatically collecting the lost alarm from a database according to the alarmseqID and reporting the lost alarm to an upper network manager.
Step S506: the normalized alarms are stored in a database table that stores all alarms, which may include generating alarms, confirming alarms, or clearing alarms.
Step S507: and reporting the standardized alarm to an upper network manager.
In this embodiment, the alarm data storage module 200 is mainly used for storing all alarms subjected to standardized processing and reported by the EMS, so as to ensure that the alarms generated on the network manager are stored without loss. In this embodiment, all alarms, including generation of an alarm, confirmation of an alarm, disappearance of an alarm, and the like, are not limited to the alarms of these types, which are added with the alarmSeqID, and then stored in the same table of the database. In order to adapt to network environments of different scales, the invention adds a configuration function of the alarm table. The user can adjust the alarm amount stored in the alarm table according to different network management scales and alarm amount sizes. As shown in fig. 6, the alarm data storage module 200 mainly includes the following processing steps:
step S601: and starting the network management database, and initializing the north alarm storage database table.
Step S602: and setting the storage time length of the data of the northbound interface database table through a configuration file according to the scale of the network and the alarm amount of the network manager, and if the storage time length of the northbound interface database table is not set, using the default configuration time length. Database alarm table alarms that exceed the configured time will be deleted, and the deletion mechanism will be performed at a fixed time of day. In the embodiment, the alarm amount of the database table can be flexibly controlled through the configuration file.
Step S603: after the network management is started, automatically connecting the databases;
step S604: and (4) controlling the database connection, and if the connection fails, trying the connection again. The connection is successful and the step S605 is entered;
step S605: storing all the alarms after the standardization processing into a database;
step S606: starting a database cleaning mechanism at a fixed time every day;
step S607: accessing the alarm generation time of the database, judging whether the alarm exceeds the configured time length for the configuration file, if so, entering a step S608, and if not, continuously receiving the alarm and not clearing any alarm;
step S608: and clearing all the overdue alarms and relieving the pressure of the database.
In this embodiment, the alarm continuity monitoring module 300 is mainly responsible for monitoring whether the reported alarm is lost, and if the alarm is lost, the alarm automatic compensation acquisition module is automatically started to accurately compensate and acquire the lost alarm, and if the alarm is continuous, the alarm is reported to the upper network management. As shown in fig. 7, the alarm continuity monitoring module 300 in this embodiment mainly includes the following processing flows:
step S701: monitoring and receiving a new alarm;
step S702: extracting each alarm alarmseqID and storing the extracted alarm alarmseqID in a cache to provide judgment conditions for the next alarm continuity judgment;
step S703: continuously comparing the alarmseqID of the newly received alarm with the alarmseqID of the last alarm, and determining the next execution according to the judgment result;
step S704: if step 303 judges that the alamSeqID is not continuous, the alarm is considered to be lost, an alarm automatic complementary acquisition system is started, and automatic complementary acquisition is carried out on the lost alarm;
step S705: if step 303 determines that the alarmSeqID is continuous, the alarm is considered to be not lost, and the alarm is directly reported to the upper network manager. In this embodiment, the alarm continuity monitoring module 300 may perform continuity ratio determination automatically through the alarmSeqID to determine whether an alarm is lost.
In this embodiment, the alarm automatic replenishment module 400 is mainly responsible for automatically starting the alarm automatic replenishment module when the alarm continuity monitoring module monitors that the reported alarm is lost, accurately judging the specific lost alarm through the alarm automatic replenishment module, accurately replenishing the specific lost alarm, and reporting the specific lost alarm to the upper network management in a notification manner. As shown in fig. 8, the automatic alarm replenishment module 400 mainly includes the following processing procedures:
step S801: after the alarm continuity monitoring module judges that the alarm is lost, the alarm automatic supplementary mining module is automatically started;
step S802: acquiring a latest received alarm alarmSeqID _1 from a cache;
step S803: acquiring the last alarm alarmSeqID _2 from the cache;
step S804: connecting the database, and preparing to retrieve the lost alarm from the database;
step S805: judging the database, if the connection is successful, starting to acquire a lost alarm, and if the connection of the database is failed, trying the connection again;
step S806: issuing an SQL command to a database to obtain lost alarms from alarmSeqID _2 to alarmSeqID _ 1;
step S807: if the lost alarm acquisition is successful, step 408 is executed, and if the lost alarm acquisition is failed, step 806 is executed again to perform the lost alarm acquisition.
Step S808: and after the loss alarm is successfully acquired, reporting the loss alarm to an upper network management through a notification mode. In this embodiment, the alarm continuity monitoring module can perform accurate judgment and automatic replenishment on the lost alarm through the alarmseqID, so as to ensure that all reported alarms are not lost and not repeated.
In the automatic and accurate complementary collection scheme for the alarm of the northbound interface software provided by this embodiment, an alarm identifier alarmSeqID is added to each reported alarm, and the reported alarm is continuously monitored through the alarmSeqID. When the alarmseqID is discontinuous, the alarm loss can be automatically judged, and the automatic complementing module is used for carrying out accurate complementing on the lost alarm, so that the reported alarm is not lost and repeated.
It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.
Embodiments of the present invention also provide a storage medium having a computer program stored therein, wherein the computer program is configured to perform the steps of the above-mentioned method embodiments when running.
Alternatively, in the present embodiment, the storage medium may be configured to store a computer program for executing the steps of:
optionally, in this embodiment, the storage medium may include, but is not limited to: various media capable of storing computer programs, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
Embodiments of the present invention also provide an electronic device, comprising a memory having a computer program stored therein and a processor configured to execute the computer program to perform the steps in the above-described method embodiments.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. An alarm reporting method is characterized by comprising the following steps:
subscribing to an alarm from an Element Management System (EMS);
adding an alarm running identifier for the subscribed alarms, and storing the alarms to an alarm database;
and reporting the alarm to a northbound interface.
2. The method according to claim 1, before adding an alarm pipelining identifier for each acquired alarm, further comprising:
and carrying out standardized processing on the subscribed alarms.
3. The method of claim 1, further comprising:
after receiving the alarm, the northbound interface judges whether the alarm is lost or not according to the continuity of the alarm running water identifier;
if the alarm is lost, the lost alarm is collected from the database.
4. The method of claim 3, wherein determining whether any alarms are lost according to the continuity of the alarm flow identifier comprises:
caching the alarm flow identifier of each received alarm, comparing the alarm flow identifier of the currently received alarm with the alarm flow identifier of the last received alarm, and determining that the alarm is lost if the alarm flow identifiers are discontinuous.
5. The method of claim 1, further comprising:
judging whether the database has an overdue alarm or not;
and if the alarm with the expiration exists, deleting the alarm with the expiration.
6. The method of claim 5, wherein determining whether there is an expired alarm in the database further comprises:
setting an expiration time for the alarms stored in the database.
7. An alarm reporting device, comprising:
the subscription module is used for subscribing the alarm from an Element Management System (EMS);
the storage module is used for adding an alarm running identifier for the subscribed alarms and storing the alarms to an alarm database;
and the reporting module is used for reporting the alarm to a northbound interface.
8. The apparatus of claim 7, further comprising:
and the standardization processing module is used for standardizing the subscribed alarms before adding the alarm flow identifier.
9. The apparatus of claim 7, further comprising:
the monitoring module is used for judging whether the alarm is lost or not according to the continuity of the alarm running water mark after the northbound interface receives the alarm;
and the alarm complementary acquisition module is used for complementarily acquiring the lost alarm from the database under the condition that the alarm is lost.
10. The apparatus of claim 7, further comprising:
and the overdue alarm clearing module is used for judging whether an overdue alarm exists in the database or not, and deleting the overdue alarm if the overdue alarm exists.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910477364.1A CN112039681A (en) | 2019-06-03 | 2019-06-03 | Alarm reporting method and device |
| PCT/CN2020/084012 WO2020244306A1 (en) | 2019-06-03 | 2020-04-09 | Alarm reporting method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910477364.1A CN112039681A (en) | 2019-06-03 | 2019-06-03 | Alarm reporting method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112039681A true CN112039681A (en) | 2020-12-04 |
Family
ID=73575993
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910477364.1A Pending CN112039681A (en) | 2019-06-03 | 2019-06-03 | Alarm reporting method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112039681A (en) |
| WO (1) | WO2020244306A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114244682A (en) * | 2021-11-22 | 2022-03-25 | 中盈优创资讯科技有限公司 | Equipment alarm loss leakage repairing method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1102433A2 (en) * | 1999-11-19 | 2001-05-23 | Nortel Networks Limited | Method and device for fault monitoring |
| CN102664751A (en) * | 2012-04-09 | 2012-09-12 | 大唐移动通信设备有限公司 | Method and device for processing warning message |
| CN104283704A (en) * | 2013-07-05 | 2015-01-14 | 中兴通讯股份有限公司 | Method and device for northbound interface to send notification event |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101854262B (en) * | 2010-06-24 | 2012-07-04 | 华为技术有限公司 | Alarm synchronization method, device and system |
| CN103490916A (en) * | 2012-06-11 | 2014-01-01 | 中兴通讯股份有限公司 | Data acquisition method and data acquisition device |
| CN105071970B (en) * | 2015-08-27 | 2018-09-11 | 中国电信股份有限公司 | Failure analysis methods and system and Network Management Equipment |
| CN106559248A (en) * | 2015-09-30 | 2017-04-05 | 中兴通讯股份有限公司 | A kind of alarm method, alarm device and warning system |
| CN108322322A (en) * | 2017-01-18 | 2018-07-24 | 普天信息技术有限公司 | Alarm reporting method |
| CN110012490B (en) * | 2018-01-04 | 2021-10-15 | 中兴通讯股份有限公司 | Alarm method, alarm device, operation maintenance center and computer readable storage medium |
-
2019
- 2019-06-03 CN CN201910477364.1A patent/CN112039681A/en active Pending
-
2020
- 2020-04-09 WO PCT/CN2020/084012 patent/WO2020244306A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1102433A2 (en) * | 1999-11-19 | 2001-05-23 | Nortel Networks Limited | Method and device for fault monitoring |
| CN102664751A (en) * | 2012-04-09 | 2012-09-12 | 大唐移动通信设备有限公司 | Method and device for processing warning message |
| CN104283704A (en) * | 2013-07-05 | 2015-01-14 | 中兴通讯股份有限公司 | Method and device for northbound interface to send notification event |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114244682A (en) * | 2021-11-22 | 2022-03-25 | 中盈优创资讯科技有限公司 | Equipment alarm loss leakage repairing method and device |
| CN114244682B (en) * | 2021-11-22 | 2024-01-05 | 中盈优创资讯科技有限公司 | Equipment alarm loss and leakage repairing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020244306A1 (en) | 2020-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110661659B (en) | Alarm method, device and system and electronic equipment | |
| CN108234170B (en) | Monitoring method and device for server cluster | |
| CN112650762B (en) | Data quality monitoring method and device, electronic equipment and storage medium | |
| CN110572443B (en) | Long connection state updating method, server and storage medium | |
| CN111190962B (en) | File synchronization method and device and local terminal | |
| CN112506702B (en) | Disaster recovery method, device, equipment and storage medium for data center | |
| CN110063042B (en) | Database fault response method and terminal thereof | |
| CN111104260A (en) | Service upgrade monitoring method, device, server and storage medium | |
| CN112751726A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111221890B (en) | Automatic monitoring and early warning method and device for universal index class | |
| CN110674149B (en) | Service data processing method and device, computer equipment and storage medium | |
| CN112039681A (en) | Alarm reporting method and device | |
| CN109684130B (en) | Method and device for backing up data of computer room | |
| CN112631687A (en) | Configuration method, device and equipment of service cluster | |
| CN108897667A (en) | A kind of memory temperature alarm method, device and equipment | |
| CN110069382B (en) | Software monitoring method, server, terminal device, computer device and medium | |
| CN109087107B (en) | Real-time monitoring method and system based on distributed memory database and electronic equipment | |
| CN114356722A (en) | Monitoring alarm method, system, equipment and storage medium for server cluster | |
| CN114490196A (en) | Database switching method, system, device and medium | |
| CN110730193B (en) | Method, device, server and storage medium for guaranteeing network security | |
| JP6527442B2 (en) | Network monitoring device and network monitoring method | |
| CN115086355A (en) | User information processing method and device based on block chain | |
| CN109144788B (en) | Method, device and system for reconstructing OSD | |
| CN109829016B (en) | Data synchronization method and device | |
| CN110363515B (en) | Rights and interests card account information inquiry method, system, server and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201204 |
|
| RJ01 | Rejection of invention patent application after publication |