CN110690983A

CN110690983A - Alarm method and device

Info

Publication number: CN110690983A
Application number: CN201810732500.2A
Authority: CN
Inventors: 尹秀敏
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-07-05
Filing date: 2018-07-05
Publication date: 2020-01-14
Anticipated expiration: 2038-07-05
Also published as: WO2020007188A1; CN110690983B

Abstract

The invention discloses an alarm method and an alarm device, which comprise the following steps: polling and reading the stored OAMID, and if the read OAMID generates an MMG alarm, writing the read OAMID into a register designated by the FPGA, wherein one OAMID uniquely identifies one piece of OAM information; reading the remote MEGID information from the address of the latch register of the FPGA according to the OAMID stored in the register; and reporting the MMG alarm and the remote MEGID information. Therefore, by reporting the MEGID information of the remote end when the MMG alarm is given, the network manager can conveniently and quickly find out which damaged tunnel causes the OAM of the normal tunnel to generate the MMG alarm, so that the alarm can be quickly processed, the service of the normal tunnel can be recovered as soon as possible, only the OAMID generating the MMG alarm is written into the FPGA instead of writing all the OAMIDs into the FPGA, and a large amount of FPGA logic resources are saved.

Description

Alarm method and device

Technical Field

The embodiment of the invention relates to the technical field of Packet Transport Network (PTN) -Operation Administration and Maintenance (OAM), and particularly relates to an alarm method and an alarm device.

Background

With the development of carrier ethernet technology, PTN has been widely used as a transmission network, and OAM is more and more popular as a means for detecting network failure. In order to prevent service interruption caused by a failure of a certain link, PTN deployment needs to configure protection switching, so as to ensure that a failure of a certain link can be switched to a normal link for operation, but OAM is necessarily configured for protection switching. At present, when OAM is configured, some damaged tunnels may exist due to network management configuration problems or some other exception handling, and the damaged tunnels are exactly the same as the outgoing labels of the tunnels where OAM is located, so when a home End MEP (MEG (maintenance entity Point) End Point receives a CCM (Continuity Check Message) Message of a damaged tunnel, a carried far End MEGID is different from the home End MEGID, and at this time, a normal tunnel generates an MMG (wrong merge alarm, unexpected MEG mismatch) alarm and cannot trigger protection switching, thereby causing service interruption. Certainly, if there are several tunnels, the tunnels can be checked one by one through a network manager or a command-line interface (CLI), but for the tunnels with large capacity and multiple hops, a large amount of time is required to check the tunnels with the same label, the serviceability is not high, and the requirement of quick recovery of the existing network service cannot be met.

In addition, an FPGA can be used in the current PTN device to implement an OAM function, but the current FPGA has limited resources and cannot provide enough resources to store all OAM information at the same time. In order to meet the requirement of enough FPGA logic resources, if more FPGAs are replaced, more funds are needed; if the peripheral equipment is added, the design risk of the hardware is high, and the stability is poor.

Disclosure of Invention

In view of this, an embodiment of the present invention provides an alarm method, including:

polling and reading the stored OAMID, and if the read OAMID generates an MMG alarm, writing the read OAMID into a register designated by the FPGA, wherein one OAMID uniquely identifies one piece of OAM information;

reading the remote MEGID information from the address of the latch register of the FPGA according to the OAMID stored in the register;

and reporting the MMG alarm and the remote MEGID information.

An embodiment of the present invention further provides an alarm device, including:

the reading unit is used for polling and reading the stored OAMID, if the read OAMID generates an MMG alarm, the read OAMID is written into a register designated by the FPGA, and one OAMID uniquely identifies one piece of OAM information;

the reading unit is also used for reading the remote MEGID information according to the OAMID stored in the register and the latching register address of the FPGA;

and the reporting unit is used for reporting the MMG alarm and the remote MEGID information.

The embodiment of the invention also provides an alarm device, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein when the computer program is executed by the processor, the alarm method is realized.

The embodiment of the invention also provides a computer readable storage medium, wherein an information processing program is stored on the computer readable storage medium, and the information processing program realizes the steps of the alarm method when being executed by a processor.

According to the alarming method and the alarming device provided by the embodiment of the invention, the network manager can conveniently and quickly find out which damaged tunnel causes the OAM of the normal tunnel to generate the MMG alarm by reporting the MEGID information of the remote end when the MMG alarm is given, so that the alarm can be quickly processed, the service of the normal tunnel can be quickly recovered, and only the OAMID generating the MMG alarm is written into the FPGA instead of writing all the OAMIDs into the FPGA, so that a large amount of FPGA logic resources are saved.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.

Fig. 1 is a schematic flowchart of an alarm method according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of an alarm device according to a second embodiment of the present invention;

fig. 3 is a schematic flow chart of an alarm method according to a third embodiment of the present invention;

fig. 4 is a schematic flow chart of an alarm method according to a fourth embodiment of the present invention;

fig. 5 is a schematic flowchart of an alarm method according to a fifth embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.

The steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.

Aiming at the technical problems in the background art, the embodiment of the invention provides an alarm method and an alarm device, which are convenient for a network manager to quickly find out which damaged tunnel causes the OAM of a normal tunnel to generate an MMG alarm by reporting the MEGID information of a remote end when the MMG alarm is given, so that the service of the normal tunnel is quickly recovered.

Example one

Fig. 1 is a schematic flowchart of an alarm method according to an embodiment of the present invention. As shown in fig. 1, the warning method includes:

step 101, polling and reading stored OAMIDs, and if the read OAMIDs generate MMG (multimedia messaging group) alarms, writing the read OAMIDs into a register designated by an FPGA (field programmable gate array), wherein one OAMID uniquely identifies one piece of OAM information;

step 102, reading remote MEGID information from the address of a latch register of the FPGA according to the OAMID stored in the register;

and 103, reporting the MMG alarm and the remote MEGID information.

Wherein, prior to polling for reading the saved OAMID, the method further comprises:

and receiving the sent OAM information, generating a corresponding OAMID according to the OAM information, and storing the OAM information and a corresponding OAM ID thereof.

Wherein the content of the first and second substances,

the method further comprises the following steps:

when the MMG alarm is generated for the first time, setting the reporting state of the MMG alarm as 'generating the alarm, and not applying for reading the remote MEGID';

the writing of the read OAMID to a register specified by the FPGA comprises the following steps: when the reporting state of the MMG alarm corresponding to the read OAMID is 'generate alarm and do not apply for reading far-end MEGID', writing the read OAMID into a register designated by the FPGA, and if the writing is successful, modifying the reporting state into 'generate alarm and apply for reading far-end MEGID';

the reporting of the MMG alarm and the remote MEGID information includes:

if the alarm is continuously generated and the reporting state is 'generate alarm, do not apply for reading far-end MEGID', the read OAMID is written into a register appointed by the FPGA, if the writing is successful, the reporting state is modified to 'generate alarm, apply for reading far-end MEGID';

and if the alarm is continuously generated and the reporting state is 'alarm generation and remote MEGID reading application', reading remote MEGID information from the address of a latch register of the FPGA, reporting the MMG alarm and the remote MEGID information, and simultaneously modifying the reporting state into 'alarm reporting'.

Wherein, the method also comprises:

if the alarm is continuously generated and the reporting state is 'alarm reported', the alarm is not reported any more;

and if the alarm disappears and the reporting state is 'generate alarm, do not apply for reading far-end MEGID' or 'generate alarm, apply for reading far-end MEGID', then the reporting state is modified to 'report alarm disappeared'.

And if the alarm disappears and the reporting state is 'alarm reported', reporting the MMG alarm disappearance to a network manager, and simultaneously modifying the reporting state into 'alarm reported disappearance'.

Example two

Fig. 2 is a schematic structural diagram of an alarm device according to a second embodiment of the present invention. As shown in fig. 2, the warning device includes:

Wherein, still include:

and the configuration unit is used for receiving the sent OAM information, applying for a corresponding OAMID to the resource pool unit according to the OAM information, receiving the OAMID generated by the resource pool unit, and storing the OAM information and the corresponding OAM ID thereof in the storage unit.

Wherein the content of the first and second substances,

the reading is specifically configured to set a reporting state of the MMG alarm as "generate alarm, apply for reading far-end MEGID" when the MMG alarm is generated for the first time; when the reporting state of the MMG alarm corresponding to the read OAMID is 'generate alarm and do not apply for reading far-end MEGID', writing the read OAMID into a register designated by the FPGA, and if the writing is successful, modifying the reporting state into 'generate alarm and apply for reading far-end MEGID';

and if the alarm is continuously generated and the reporting state is 'alarm generation and remote MEGID reading application', reading remote MEGID information by a latch register address of the FPGA, informing a reporting unit to report the MMG alarm and the remote MEGID information, and simultaneously modifying the reporting state into 'alarm reporting'.

The reading unit is further configured to not notify the reporting unit to report if the alarm continues to be generated and the reporting state is "alarm reported over";

If the alarm disappears and the reporting state is 'alarm reported', the reporting unit is informed to report the MMG alarm disappearance to the network management, and the reporting state is modified to 'alarm reported disappearance'.

According to the technical scheme provided by the first embodiment and the second embodiment of the invention, the network manager can conveniently and quickly find out which damaged tunnel causes the OAM of the normal tunnel to generate the MMG alarm by reporting the MEGID information of the remote end when the MMG alarm is given, so that the alarm can be quickly processed, and the service of the normal tunnel can be recovered as soon as possible; and only the OAMID generating the MMG alarm is written into the FPGA, but not all the OAMIDs are written into the FPGA completely, so that a large amount of FPGA logic resources are saved.

The technical solution of the present application is explained in detail by the following specific examples.

EXAMPLE III

Fig. 3 is a flowchart of an alarm method according to a third embodiment of the present invention. As shown in fig. 3, the warning method includes:

step 301, receiving the sent OAM information, generating a corresponding OAMID according to the OAM information, and storing the OAM information and the corresponding OAMID;

the user may configure the OAM information through a network manager or a CLI (command-line interface) and issue the OAM information.

The configuration unit can receive the sent OAM information, store the OAM information in the storage unit, and apply for OAMID to the resource pool unit according to the OAM information. And the resource pool unit sets OAMID corresponding to the OAM information according to the TMC layer, TMP layer and TMS layer information in the OAM information, and one OAMID uniquely identifies one piece of OAM information. And after receiving the OAMID generated by the resource pool unit, the configuration unit stores the OAMID to the storage unit.

When CC/CV and MEP in the OAM information are enabled, the home terminal and the corresponding remote terminal send CCM messages to each other, and when the home terminal's MEGID is inconsistent with the remote terminal's MEGID, an MMG alarm is generated.

In addition, when the MMG alarm is generated for the first time, the reporting state of the MMG alarm is set as ' generating the alarm, and no application for reading the remote MEGID ' is made '.

Step 302, polling and reading the stored OAMID, writing the read OAMID to a register designated by FPGA when the reporting state of the MMG alarm corresponding to the read OAMID is 'generate alarm and do not apply for reading the remote MEGID', and if the writing is successful, modifying the reporting state into 'generate alarm and apply for reading the remote MEGID';

wherein, the read unit can poll and read the OAMID from the storage unit and write the read OAMID to a register designated by the FPGA.

Step 303, if the alarm is continuously generated and the reporting status is "generate alarm, do not apply to read far end MEGID", writing the read OAMID to a register designated by FPGA, if the writing is successful, modifying the reporting status to "generate alarm, apply to read far end MEGID";

if the alarm continues to be generated and the reporting status is "generate alarm, no request for reading far-end MEGID" is made, it indicates that the writing in step 302 fails.

Step 304, if the alarm continues to be generated and the reporting status is "generate alarm, apply for reading far end MEGID", then go to the latching register address of FPGA to read the far end MEGID information, and report the MMG alarm and the far end MEGID information, and at the same time, modify the reporting status to "report alarm";

wherein, the MMG alarm and the remote MEGID information can be reported to a network manager or other management units. Step 305, if the alarm is continuously generated and the reporting state is 'alarm reported', the alarm is not reported any more;

step 306, if the alarm disappears and the reporting status is "generate alarm, do not apply for reading far end MEGID" or "generate alarm, have applied for reading far end MEGID", then modify the reporting status to "report alarm disappeared";

step 307, if the alarm disappears and the reporting state is "alarm reported", reporting the MMG alarm disappeared to the network manager, and meanwhile, modifying the reporting state to "alarm reported disappeared".

In the above steps, the reading unit may determine whether to continue generating the alarm or to cancel the alarm, modify the reporting status, and notify the reporting unit to report the alarm and the remote MEGID information when the reporting condition is met.

The sequence of the above steps is only exemplary, and there is no fixed sequence.

Example four

Fig. 4 is a flowchart illustrating an alarm method according to a fourth embodiment of the present invention. As shown in fig. 4, the warning method includes:

step 401, a configuration unit configures OAM information issued by a network manager and local OAMID applied to a resource pool unit to a storage unit;

wherein, OAM information includes: a register, cc (Connectivity Check)/cv (Connectivity Verification) enable information, MEP enable information, TMC layer, TMP layer, and TMS layer information, and the like.

The configuration unit can go to the resource pool unit according to different OAM information to apply for corresponding OAMID, and one OAMID can uniquely identify one OAMID. The resource pool unit may configure different oamds for different OAM information. In addition, an OAMID may be a KEY value, for example, the KEY of TMS is sectionId, the KEY of TMC is pwid, etc., and finally the applied OAMID information is configured to the storage unit.

Step 402, starting a timer, regularly polling the storage unit by the reading unit, reading the corresponding OAM information such as cc, cv, MEP, OAMID and the like from the storage unit, if the MEP is enabled, continuing the step 403, otherwise, continuing the step 402, and at this moment, reading another piece of OAM information from the storage unit by the reading unit;

step 403, the reading unit reads the OAMID according to the step 402, and the FPGA removing unit reads corresponding alarm information;

when cc, cv and MEP in the OAM information are enabled, the home terminal and the corresponding remote terminal send CCM messages to each other, and when the home terminal's fig and the remote terminal's fig are not consistent, an MMG alarm is generated, which is the prior art and is not described herein again.

When the MMG alarm is generated for the first time, setting the reporting state of the MMG alarm as 'generating the alarm, and applying for reading the remote MEGID';

wherein if the read OAMID does not generate an alarm, the next OAMID is read, and if the alarm is read, step 404 is executed.

Step 404, when the reporting status of the MMG alarm corresponding to the read OAMID is "generate alarm, do not apply to read remote MEGID", the read unit writes the read OAMID into a configuration register specified by FPGA, and sets the reporting status of the alarm information as "generate alarm, apply to read remote MEGID";

step 405, the reading unit judges whether the alarm is generated continuously;

the reading unit may periodically read MMG alarm information generated by the OAMID, and determine whether the alarm is continuously generated refers to checking whether the alarm information corresponding to the OAM has changed, and possibly the alarm has disappeared at this time, if the alarm corresponding to the OAM is continuously generated, step 406 is executed, and if the alarm has disappeared, step 407 is executed.

Step 406, if the alarm is generated continuously, different processing is performed according to different reporting states;

there are four reporting states, namely, four reporting states

1. Generating an alarm, and not applying for reading the remote MEGID;

2. generating an alarm, and applying for reading the remote MEGID;

3. reporting an alarm;

4. reporting that the alarm disappears;

if the reported state is 'generate alarm, do not apply to read far-end MEGID', then indicate that the writing is not successful yet, write the read OAMID into the configuration register appointed by FPGA, if the writing is successful, modify the reported state into 'generate alarm, apply to read far-end MEGID';

if the reporting state is 'generate alarm, applied to read far-end MEGID', then indicate that the writing is successful, then according to OAMID to latch register address of FPGA read far-end MEGID, inform reporting unit to report MMG alarm and read far-end MEGID, and change the reporting state to 'report alarm';

if the reporting state is 'alarm reported', it indicates that the alarm has been reported, and it is not necessary to notify the reporting unit to report to the network manager again.

Step 407, if the alarm disappears, different processing is performed according to different reporting states;

1. if the reporting state is 'alarm generation, far-end MEGID reading is not applied', the writing is not successful, and the alarm disappears, the reporting state is directly modified to 'alarm reporting disappears';

2. if the reporting state is ' alarm generation, remote MEGID reading ' is applied ', the writing is successful, the alarm disappears, and the reporting state is directly modified to ' alarm reporting disappears ';

when the FPGA writes a next OAMID, the FPGA can automatically cover the next OAMID.

If the reporting state is 'reporting alarm' it shows that the writing is successful and the alarm has been reported, at this moment, it needs to inform the reporting unit to report the alarm disappearance, and at the same time, the reporting state is modified to 'reporting alarm disappearance'.

The

above steps

406, 407 do not have a fixed order.

EXAMPLE five

In this embodiment, the first variable identifier, the report serial number, and the report structure identifier are configured in advance.

Fig. 5 is a schematic flowchart of an alarm method according to a fifth embodiment of the present invention. As shown in fig. 5, the warning method includes:

step 501, reading the stored OAMID information and OAMID, and reading a corresponding MMG alarm by the FPGA according to the read OAMID;

how to store the OAM information and how to apply for the OAMID, etc. can be seen in embodiments one to five, which are not described herein again.

When an alarm is generated for the first time, the reporting state of the alarm information is set as ' alarm generation, and no application for reading the remote MEGID ' is made '.

Wherein if no alarm is generated, the next OAMID can be read, and if an alarm is read, step 502 is executed.

Step 502, when the reporting state of the MMG alarm corresponding to the read OAMID is 'generate alarm, and the remote MEGID is not applied to be read', the read OAMID is written into a configuration register appointed by the FPGA;

whether the alarm information of the OAM changes needs to be checked continuously, if the OAM is always in the generation state continuing step 503, otherwise, the alarm disappears, and the step 504 is executed;

whether the alarm occurs to change from occurring to disappearing or not is judged by comparing the state at the moment with the state of the last soft table.

Step 503, if the alarm is generated continuously, different processing is performed according to different reporting states;

1. if the reporting state is 'generate alarm, do not apply for reading far-end MEGID', then write the read OAMID into the configuration register appointed by FPGA again, if write successfully, modify the reporting state to 'generate alarm, apply for reading far-end MEGID';

in addition, before the write operation, it is also necessary to determine whether the first variable identifier is "yes", if yes, it indicates "allow to read the remote MEGID information", and may write the OAMID of the OAM into the FPGA, and if successful, it sets the first variable identifier position to "no", which indicates "not allow to read the remote MEGID information".

2. If the reporting state is 'alarm generation, remote MEGID reading is applied', the latching register of the FPGA is used for reading the remote MEGID information, the MMG alarm and the remote MEGID information are reported, and meanwhile, the reporting state is modified into 'alarm reported';

in addition, it is also necessary to add 1 to the reported serial number, and the serial number changes once every time the alarm changes, where an odd number indicates that the alarm is generated and an even number indicates that the alarm disappears.

In addition, the reporting structure identifier position is set to 1, the reporting sequence number represents the reporting times, the reporting structure identifier position is set to 1 to represent that the alarm has been reported, and the reporting structure identifier position is set to 0 to represent that the alarm has not been reported;

in addition, the first variable identifier is set to be yes, the first variable identifier is used for indicating whether the remote MEGID information is allowed to be read or not, if yes, the FPGA is not written, and otherwise, the configuration register of the FPGA is not written.

3. If the reporting state is 'alarm reporting', reporting is not needed again, but the identification position of the reporting structure body is required to be 1.

Because the alarm is reported, in order to avoid the CPU overshoot, the step is not reported any more, but mainly aims to set the relevant identification field to a correct value.

And step 504, if the alarm disappears, different processing is carried out according to different reporting states.

1. If the reported state is ' alarm generation, no application for reading the far-end MEGID ' is given ', the writing is not successful, and the first variable identification position is set to be yes;

2. if the reported state is 'alarm generation, remote MEGID reading has been applied', the writing is successful, and the first variable identification position is set as yes;

the above 1 and 2 also need to modify the reporting status into "the alarm is reported to disappear".

If the reporting state is 'alarm reporting', the writing is successful, and the alarm is reported, at this time, the alarm is required to be reported, and meanwhile, the reporting state is modified into 'alarm reporting is lost'; in addition, the identification position of the reporting structure needs to be set to 1, and the sequence number needs to be increased by 1.

There is no fixed order of the above steps 503, 504.

The method and the device for alarming provided by the embodiment set the corresponding OAMID for the OAM information, and carry the remote MEGID when reporting the MMG alarm, thereby facilitating the network manager to quickly find out which damaged tunnel causes the OAM of the normal tunnel to generate the MMG alarm, and quickly recovering the service of the normal tunnel. In addition, at present, an FPGA can be used in the PTN device to implement an OAM function, but, for example, if the MEGID is 128 bits, and the maximum configurable 8KOAM requires 8k × 128 bits of FPGA logic resources, the present FPGA resources are limited, and it is not yet possible to provide sufficient resources to store all OAMIDs simultaneously, and it is convenient to read the MEGID information of each OAM. In order to meet the requirement of such a large number of FPGA logic resources, if more FPGAs are replaced, the needed capital is large; if the peripheral equipment is added, the design risk of the hardware is high, and the stability is poor. Therefore, the alarm method provided by the invention saves a large amount of FPGA logic resources by writing the OAMID generating the MMG alarm to the FPGA instead of writing all the OAMIDs into the FPGA completely.

It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.

Although the embodiments of the present invention have been described above, the above description is only for the convenience of understanding the present invention, and is not intended to limit the present invention. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. An alert method comprising:

and reporting the MMG alarm and the remote MEGID information.

2. The alerting method of claim 1 wherein prior to polling for reads of saved OAMIDs, the method further comprises:

3. The alerting method of claim 1 further comprising:

the reporting of the MMG alarm and the remote MEGID information includes:

4. The alerting method of claim 3 further comprising:

if the alarm disappears and the reporting state is 'generate alarm, do not apply for reading far-end MEGID' or 'generate alarm, apply for reading far-end MEGID', then modify the reporting state to 'report alarm disappeared';

5. An alert device, comprising:

6. The warning device of claim 5, further comprising:

7. The alert device of claim 5,

8. The alert device of claim 7,

the reading unit is further configured to not notify the reporting unit to report if the alarm continues to be generated and the reporting state is "alarm reported already";

9. An alerting device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the alerting method of any one of claims 1 to 4.

10. A computer-readable storage medium, characterized in that an information processing program is stored on the computer-readable storage medium, which when executed by a processor implements the steps of the alert method according to any one of claims 1 to 4.