GB2422236A - Remote fault acknowledgement system - Google Patents
Remote fault acknowledgement system Download PDFInfo
- Publication number
- GB2422236A GB2422236A GB0500517A GB0500517A GB2422236A GB 2422236 A GB2422236 A GB 2422236A GB 0500517 A GB0500517 A GB 0500517A GB 0500517 A GB0500517 A GB 0500517A GB 2422236 A GB2422236 A GB 2422236A
- Authority
- GB
- United Kingdom
- Prior art keywords
- alarm
- message
- fault
- technician
- acknowledge
- 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.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
- G08B25/001—Alarm cancelling procedures or alarm forwarding decisions, e.g. based on absence of alarm confirmation
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
- G08B25/01—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems characterised by the transmission medium
- G08B25/10—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems characterised by the transmission medium using wireless transmission systems
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B29/00—Checking or monitoring of signalling or alarm systems; Prevention or correction of operating errors, e.g. preventing unauthorised operation
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R25/00—Fittings or systems for preventing or indicating unauthorised use or theft of vehicles
- B60R25/10—Fittings or systems for preventing or indicating unauthorised use or theft of vehicles actuating a signalling device
- B60R2025/1013—Alarm systems characterised by the type of warning signal, e.g. visual, audible
- B60R2025/1016—Remote signals alerting owner or authorities, e.g. radio signals
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Emergency Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
A fault detection alarm system transmits a message to a remote location on detection of a fault and is able to receive a message from the remote location, allowing an off-site technician to be alerted to a failure and to acknowledge it or take action to correct it. The message may take the form of SMS, MMS or email and may use a standard telecommunication network. It is disclosed that the system may also apply labels to alarm events, indicating their category and processing status. In one example the detected fault is an attempted break-in to a car.
Description
FAULT ACKNOWLEDGEMENT SYSTEM
This invention relates to a system having a fault management system (FMS) for indicating faults to a technician who can acknowledge a fault. It has specific hut not exclusive application to telecommunication systems.
Acknowledgement of a fault is important for obvious reasons. Today's communication network systems typically use fault management tool as a secure way of indicating to technicians when and where a fault exists (e. g. in their network platform). In such actual systems acknowledgement of a fault can only be made manually. This means in other words that acknowledgement can only he made by the technician who has to be near the fault management system. A problem arises in that a fault may be flagged up out of working hours when the technician is at home.
Patent WO 98/164 12 describes an SMS alarm based on using an SMS transmitter as a car alarm. When physical damage is done to a car the SMS transmitter transmits a IS pre-programmed message to a central server for the SMS alarm, which in turn transmits an alarm message to the owner of the alarm in the form of an SMS message. The alarm message is shown e.g. on the owners mobile telephone display. The owner then has the possibility to call a centre which allows the owner if he wishes to switch of'f the alarm.
In such a system there is only one single entity flagged up i.e. a general fault indicated e.g. an alarm.
11 is an object of the invention to provide a system that allows hidirectional interactivity between a technician and a fault detection system remotely. In other words it allows a technician to intervene and acknowledge faults in a system which is physically remote from him.
With a system which has a fault detection system, a method of monitoring and dealing with faults comprising: detecting a fault; remotely transmitting a fault message to a technician; allowing the technician to acknowledge the fault by transmitting a acknowledgement message hack to the system.
According to the invention the technician is able to acknowledge the alarms and trouble tickets that are reported by a system using remote means such as SMS messages, MMS messages, email messages. Preferably the choice of message type is available to the technician.
The technician can then respond to the system to acknowledge the fault in a similar fashion. PreiBrably the technicians response will he by identical means e.g. SMS if the fault was indicating by SMS.
l'he fault management system then receives the acknowledgement. It may further act appropriately depending on the acknowledgement. I'he acknowledgement of a fault by a technician provides information to other technicians that someone is already aware that a specific fault has been acknowledged and is in charge of its resolution so as to inform that the problem is being solved and thus avoiding other technicians spending time with faults that are already being dealt with.
Further fault management systems often have associated severity levels, e. g a fault can he major and if it is not dealt with the fault status will pass to critical etc the acknowledge avoids this procedure in those systems.
1 5 Some systems as mentioned send SMS to inform technicians of a fault. However the remote acknowledgement of the current invention prevent fault management systems continuously resendtng more automatic fault notification once a technician has already responded. Thus such systems are more efficiency and independent.
The system there allows the possibility of technicians to acknowledge a fault in a remote fashion with the help of systems such as SMS, MMS and email. At first the ihult management system will detect a fault and send a message (using the preferred notification channel (e.g. SMS) configured at the system for that particular user with a fault alarm report, giving the selected technician text-based information which may be made available in the board entries screen of the FMS. The FMS also is prepared to receive a message from the technician processing the answer thus acknowledging the thult report; the status of the fault will consequently changed immediately. These steps are shown in the flow chart of figure 1
Example I
In this example a vehicle is fitted with a fault detection system. The invention is implemented by the FDS sending a message to the owner of the vehicle, e.g. to indicate an alarm has gone off. The owner will receive via his mobile a message sent by the vehicle based FDS indicating a specific fault from a variety of options (i.e. not just non selected a pre-programmed message in dictating an alarm in general. For example the fault message may distinguish between a stolen car, a window break as a result of atmospheric conditions, or due to physical attack on the car. When the message is received by the vehicle owner, he can acknowledge the fault in different way appropriately.. If the car is not being robbed but the window has been broken due to atmospheric conditions the invention allows the fault to be acknowledged by a command to stop the alarm, or where it is being robbed, an acknowledgment is (or includes) a command to alert the police. Thus such a system gives a number of options according to the type of fault indicated and response selected (remotely) by the owner/technician.The "Acknowledge" status of a trouble report means that that O&M technician is already aware of the existence of that particular alarm in the network. "Un-Acknowledge" makes sense when used in applications that work with telecommunication networks because is the default value for a newly raised alarm. The "Forward" status will allow to the technicians to receive the trouble report from the FMS and forward that same trouble report to another technician.
Alarm Event Types There are the following two basic types of alarm events: "Raised" indicates the begin of a certain alarm. "Cleared" indicates the clearing of a previously reported alarm.
After having received an alarm raised notification the FMS assumes that this alarm is present until a corresponding alarm cleared notification is received. "Clear" is an alarm means that the alarm after the clear no longer will exist in the network. The error that was the source of that trouble report no longer is present in the network. The "acknowledge" state is used by the network operator in the process of fault correction in order to keep track of the alarm work state. Every current alarm has an acknowledge state attribute. As an attribute of every current alarm instance the acknowledge state may have one of the following values: Unacknowledged: This is the default for a newly raised alarm. Besides this definition, unacknowledge status, is in some other Fault Management applications, the unacknowledge status can also he reached as you see in the new diagram below Acknowledged: Indicates that the alarm has been acknowledged by the network operator.
The invention is also applicable to telecommunication systems or any other system that have tools which deal with fault management. Where such systems employ technicians to be proximately located to the system to monitor (e.g. on systems screens) and respond to faults, it allows labour resources to be freed up. So in many non critical instances, night monitors may be (partially dispensed with) and the monitor personnel can be located anywhere. Thus in many instances permanent technicians observing screens of fault detection systems on site can he dispensed with by indicated faults remotely which can be acknowledged and or responded to further in different ways.
1 5 As mentioned the invention works with different types of' messages such as SMS messages, MMS messages and e-mail messages. [he table below shows types of messages and protocols that are used, ie., embodiments of the invention: Type of Message Protocols used by SI'Rll SPRI-l ->UCP--[PETHERNET SMS SPRH -*IJCP---*X25/FR SPRII -SMPP---'1P---*ETHERNET SPRH SM'['P -f TCP/lP-*ETHERNET
MMS
SPRH -SMTP - TCP/IP->ETHERNET
E-MAIL
The table below shows the detailed tables of the types of message that can he sent, showing direction.
ABSTRACT MESSAGE DIRECTION FIELDS TYPE
ALARM ID NOTIF SYSTEM-* Alarmld Submit a new alarm ID to TEChNICIAN RaisedTime someone via SMS, MMS or e- OhjectType mail Systemld ALARM ID DESC SYSTEM-* FventType The system sends a message to TECHNICIAN ProbCause the technician remotely with a
A larml)esc brief description of a speci flc
alarm.
ACT ALARM STATUS SYSTEM-* Alarmld The actual status of a specific TECHNICIAN Systemid alarm is send by the systeili Status AckTime or ClearTi me Fechnicianld ACK_ALARM_ID TECI-INICIAN-* Technicianid The technician Acknowledges SYSTEM TechnicianPwd the specific alarm reported.
C mdld ____________________________ _________________ Alarmid ______________________________ ACK ALARM COMP SYSTEM- Alarm Id The technician is informed that TECHNICIAN AckState the alarm was completed AckTime Acknowledge in the Fault _____________________________ __________________ ________________ Management tool.
ACK_ALARM_FA1LEJ) SYSTEM- Alarmid The system sends to the TECHNICIAN AckState technician the infi)rmation that ErrorCause the alarm Acknowledge failed UNACK ALARM ID TECHNICIAN-* Technicianld The technician Un- SYSTEM l'echnicianPwd acknowledges a speci flc alarm Cmdld reported.
Alarmld UNACK ALARM COMI SYSTEM-- Alarmld The technician is informed that TECHNICIAN AckState the alarm Un-acknowledges was completed in the Fault _____________________________ __________________ ________________ Management tool.
I.JNACK ALARM_FAILED SYSTEM---*TEC Alarmld The system sends to the I INIC1AN AckState technician the information that ErrorCause the alarm U nacknowledges ____________________________ _________________ _______________ failed.
CLR ALARM ID TECHNICIAN- Technicianld The technician sends a Clear FMS TechnicianPwd request to a specific alarm. Cmdld
Alarm Id CLR COMPID SYSTEM- Alarmld The technician is informed that I'ECHNICIAN ClearTime the Clear of the alarm was completed in the Fault Management tool successfully.
CLR ALARM FAILED SYSi'EM- Alarmid The system sends to the TECHNICIAN ErrorCause technician the information that the Clear ofa certain alarm fai led.
FWD ALARM ID TECIIN1CIAN-* Technicianid The technician sends a Forward SYSTEM TechnicianPwd Request to a specific alarm. Cmdld
Alarmid FwDestld FWD ALARM COMP SYSTEM- Alarmid The technician is informed that TECHNICIAN the Forward of a specific alarm was completed in the Fault Management tool successfully.
FWD AI.ARM FAILED SYSFEM- TEC Alarmld The system sends to the 1-INECIAN ErrorCause technician the information that the Forward of a certain alarm failed.
REQ MESSAGE TECHNIClAN- Alarmid The technician Request the SYSTEM Technicianid state of a specific alarm.
TechnicianPwd REQ_FAILED SYSTEM- Alarmid The Request state of a specific TECHNICIAN ErrorCause alarm ffiils.
ERROR. MESSA(IE SYSTEM---+ ErrorCause An Error message is send from TECHNICIAN Alarm Id the SYSTEM to the technician _______________________________ ___________________ ________________ reporting the error cause.
The table below shows each field name in the Abstract Messages:
Field Name D,finition Legal Values
Alarmld It identifies uniquely one Alarm in the ______________________ AlarmI ist.
Systemld It identities the system froni which the alarm has been raised.
ObjectType It identifies the card or module in system.
RaisedTime It indicates the date and time when the alarm All values indicating valid time.
was first raised by the alarmed resource.
EventType It indicates the type of event.
E.g Comm unications, Equipment, ___________________ Environmental, Processing Error, QOS, etc ProhCause It qualifies alarm and provides further information than Event'I'ype.
Severity It indicates the relative level of urgency for Critical, Major, Minor, Warning, ____________________ operator attention. Indeterminate AlarmDesc It contains additional detailed
description/i nforrnati on about the alarm
condition.
AckTime It identifies the time when the alarm has been All values that indicate valid time that are acknowledged or Un-acknowledges the last later than that carried in RaisedTime.
ti ille.
Cleari'ime It indicates the date and time when the alarm All values indicating valid time that are is Cleared later than that carried in RaisedTime.
Userld It identifies the O&M technician who wants to change the Alarm State.
UserPwcl Password of the user who wants to change the Alarm State for security purposes.
AckSiate It identifies the Acknowledgement State of Acknowledged: the alarm has been the alarm. acknowledged.
Un-acknowledges the alarm has been Un- acknowledges or the alarm has never been acknowledged.
Cmdld Commands sent by the user. ACK for ACK, CLR, FWD, UNACK Acknowledge, CLR for Clear, FWD fir Forward and UNACK for Un-acknowledges.
FwDest[d Used to forward an alarm fault to a specific Mobile Number or rniail account or destination (e.g. another O&M l'echnician). Userdld.
ErrorCause Error code returned when an action is not See Error Codes Table.
executed successfully ______________________________________ Status The alarm status can he ACK, UNACK or ACK, UNACK, CLR. CL R.
Figure I shows the Abstract Message Flow for Acknowledge of a message. The acknowledge complete successfully and the Acknowledge failed message flow is represented.
Figure 2 shows the Abstract Message Flow for the lJnacknowledge of a message. The Iinacknowledge complete successfully and the Unacknowledge failed message flow is represented.
Figure 3 shows the Abstract Message Flow for a Clear message. The Clear complete successfully and the Clear failed message flow is represented.
Figure 4 shows the Abstract Message Flow for Forward a message. the Forward complete successfully and the Forward filled message flow is represented.
Figure 5 shows the Abstract Message Flow for Request a message. The Request complete successfuJ!y and the Request hhued message flow is represented above.
The table below shows the Error Codes: Error Code Message Meaning 01 Syntax error Error of syntax in the message sent, _______________ __________________________________________ e.g. missing field 02 Operation not supported by system E.g command that is not recognize ______________ ________________________________________ by the EMS 03 Operation not allowed Any internal error (e.g. no resources) ____________________________________________-_________ often of temporary nature 04 Authentication failure User/password not valid or missing.
Repetition not allowed The O&M technician send the same command twice to the same alarm at ____________ ___________________________________ the FMS 06 Standard text not valid Error in the standard text 07 I'ime period not valid Timer expired 08 Message type not supported by system The FMS does not identify the _______________ __________________________________________ message type.
09 Fault not found in EMS The alarm does not exist User not in list l'he user is not in the list I Delivery in progress The response message is being ________________ ____________________________________________ processed 12 User barred l'he user is not in the list and he is not allowed to make status changes in a ________________ _____________________________________________ specific alarm fault.
13 Acknowledge hilled l'he Acknowledge already done.
14 Acknowledge failed - no alarm I'he alarm no longer exists.
Un- Acknowledge failed The Un-Acknowledge already done 16 Un- Acknowledge failed - no alarm The alarm no longer exists 1 7 Clear failed The alarm no longer exists 18 Forward failed - no alarm The alarm no longer exists.
I 9 Forward failed - recipient address not l'he recipient address is not valid correct Request thiled no alarm The alarm no longer exists.
Abbreviations E-Mail Electronic Mail FMS Fault Management Service FR Frame Relay GSM Global System for Mobile communication IP Internet Protocol MM Multimedia Message MMS Multimedia Message Service MMSC Multimedia Message Service Centre O&M Operations and Maintenance PC Personal Computer PLMN Public Land Mobile Network SM Short Message SMPP Short Message Peer to Peer Protocol SMS Short Message Service SMSC Short Message Service Centre SMTP Simple Mail Transfer Protocol SPRI-I Simple Protocol Remote Handling TCP Transport Control Protocol IJCP Universal Computer Protocol UI) User [)ornain
Claims (5)
1. With a system which has a fault detection system, a method of monitoring and dealing with faults comprising: a) detecting a iault h) remotely transmitting a fault message to a technician; c) allowing the technician to acknowledge or action the fault by transmitting a message back to the system.
2. A method as claimed in claim I wherein the acknowledgement message of step c) is selected from a plurality ol appropriate options.
3. A method as claimed in any preceding claim wherein any of said messages are selected from the following types: an SM.S message, a MMS message or an email.
4. A method as claimed in claim 3 wherein both the fault message and the acknowledgement message are of the same type.
5. A method as claimed in any preceding claim wherein said system is a telecommunication system 6 A system embodying any of the preceding claims
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB0500517A GB2422236A (en) | 2005-01-12 | 2005-01-12 | Remote fault acknowledgement system |
| PCT/EP2006/000177 WO2006074909A1 (en) | 2005-01-12 | 2006-01-10 | Fault acknowledgement system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB0500517A GB2422236A (en) | 2005-01-12 | 2005-01-12 | Remote fault acknowledgement system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| GB0500517D0 GB0500517D0 (en) | 2005-02-16 |
| GB2422236A true GB2422236A (en) | 2006-07-19 |
Family
ID=34203917
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| GB0500517A Withdrawn GB2422236A (en) | 2005-01-12 | 2005-01-12 | Remote fault acknowledgement system |
Country Status (2)
| Country | Link |
|---|---|
| GB (1) | GB2422236A (en) |
| WO (1) | WO2006074909A1 (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1998016412A1 (en) * | 1996-10-17 | 1998-04-23 | Telia Ab | Sms-alarm |
| EP0978810A2 (en) * | 1998-08-07 | 2000-02-09 | Lucent Technologies Inc. | Intermittent low bandwidth, wireless data network and method of operation thereof |
| US20020118102A1 (en) * | 1998-02-13 | 2002-08-29 | Ronald Fundak | Boat security system |
| GB2394244A (en) * | 2002-10-10 | 2004-04-21 | Corus Uk Ltd | Hollow steel railway sleeper |
| US6774786B1 (en) * | 2000-11-07 | 2004-08-10 | Fisher-Rosemount Systems, Inc. | Integrated alarm display in a process control network |
| US20040186739A1 (en) * | 2002-11-01 | 2004-09-23 | David Bolles | Customer configurable system and method for alarm system and monitoring service |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE29711886U1 (en) * | 1997-06-30 | 1997-09-11 | Daten Und Prozestechnik Gmbh | Device for reporting faults and process data in technical systems |
| US5961561A (en) * | 1997-08-14 | 1999-10-05 | Invacare Corporation | Method and apparatus for remote maintenance, troubleshooting, and repair of a motorized wheelchair |
| US6414595B1 (en) * | 2000-06-16 | 2002-07-02 | Ciena Corporation | Method and system for processing alarm objects in a communications network |
| DE20107725U1 (en) * | 2001-05-08 | 2001-10-18 | Schur Guenther | Additional device for mobile phones as an alarm device |
| DE10245953A1 (en) * | 2002-10-02 | 2004-04-29 | Heiko Viertel | Method for centralized monitoring of a number of computer-controlled machines, requires customer-specific information program for drawing up e-mails for sending to service-technician |
-
2005
- 2005-01-12 GB GB0500517A patent/GB2422236A/en not_active Withdrawn
-
2006
- 2006-01-10 WO PCT/EP2006/000177 patent/WO2006074909A1/en not_active Application Discontinuation
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1998016412A1 (en) * | 1996-10-17 | 1998-04-23 | Telia Ab | Sms-alarm |
| US20020118102A1 (en) * | 1998-02-13 | 2002-08-29 | Ronald Fundak | Boat security system |
| EP0978810A2 (en) * | 1998-08-07 | 2000-02-09 | Lucent Technologies Inc. | Intermittent low bandwidth, wireless data network and method of operation thereof |
| US6774786B1 (en) * | 2000-11-07 | 2004-08-10 | Fisher-Rosemount Systems, Inc. | Integrated alarm display in a process control network |
| GB2394244A (en) * | 2002-10-10 | 2004-04-21 | Corus Uk Ltd | Hollow steel railway sleeper |
| US20040186739A1 (en) * | 2002-11-01 | 2004-09-23 | David Bolles | Customer configurable system and method for alarm system and monitoring service |
Also Published As
| Publication number | Publication date |
|---|---|
| GB0500517D0 (en) | 2005-02-16 |
| WO2006074909A1 (en) | 2006-07-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1969444B1 (en) | A method and apparatus for using sms short code messaging to facilitate the transmission of a status update for a security system | |
| AU714679B2 (en) | Process and microcomputer system for automatic, secure and direct data transfer | |
| US6211782B1 (en) | Electronic message delivery system utilizable in the monitoring of remote equipment and method of same | |
| US6160477A (en) | Electronic message delivery system utilizable in the monitoring of remote equipment and method of same | |
| US6838986B2 (en) | Notification of use of network-enabled device | |
| WO2005065117A2 (en) | Security messaging system | |
| US20100277307A1 (en) | Municipal Operations Monitoring and Alert System | |
| US8589595B2 (en) | Communications device and system for implementing a management system remote from devices | |
| CN101432779A (en) | Security system reporting events through e-mail massages | |
| JP3876900B2 (en) | Remote monitoring system and method | |
| WO2007062124A2 (en) | Security system status notification device and method | |
| KR100697079B1 (en) | Multi-Airconditioner Center Control System and Error Report Method thereof | |
| US7245703B2 (en) | Alarm signal interceptor, middleware processor, and re-transmitter using caller ID | |
| WO2001091350A2 (en) | System and method for performing remote security management of client computer systems | |
| US6567501B1 (en) | Method and a system for transmitting alarms | |
| SE529901C2 (en) | Plant monitoring system | |
| GB2422236A (en) | Remote fault acknowledgement system | |
| KR100710766B1 (en) | Monitoring system, apparatus to be monitored, monitoring apparatus, and monitoring method | |
| CN101951563B (en) | Technique for fault avoidance in mail gateway | |
| JP3392349B2 (en) | Combustion control equipment data collection system, remote monitoring device and combustion control equipment | |
| JP3443004B2 (en) | Building management system | |
| JP2018147316A (en) | Dwelling unit security system | |
| JP2004334516A (en) | System for email notification service about installation state information | |
| JP2002190075A (en) | Monitoring information reporting device | |
| JP2023005507A (en) | security device and security system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| WAP | Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1) |