Incident-centric mass notification system

Patent metadata

Field	Value
Publication number	US-9641692-B2
Application number	US-201313925829-A
Country	US
Kind code	B2
Filing date	Jun 25, 2013
Priority date	Jun 25, 2013
Publication date	May 2, 2017
Grant date	May 2, 2017

Abstract

An Incident-centric Mass Notification System (“Incident-centric MNS system”) for notifying a plurality of recipients of an Emergency Event is disclosed. The Incident-centric MNS system may include a Mass Notification System (“MNS”) Notification Engine, modality corridor (“MoCo”) dispatcher, and a plurality of modality corridors, wherein each modality corridor of the plurality of modality corridors establishes, for signal communication, a signal path from a plurality of signal paths, between the MNS Notification Engine and a recipient of the plurality of recipients. The MNS Notification Engine is configured to manage MNS Incidents and Notifications and the MoCo dispatcher is configured to select a first modality corridor from the plurality of modality corridors to establish a first signal path from the MNS Notification Engine.

First claim

What is claimed is:

1. An Incident-centric Mass Notification System (“Incident-centric MNS system”) for notifying a plurality of recipients of an Emergency Event, the Incident-centric MNS system comprising:
a Mass Notification System (“MNS”) Notification Engine, wherein the MNS Notification Engine is configured to manage MNS Incidents and Notifications;
a modality corridor (“MoCo”) dispatcher in signal communication with the MNS Notification Engine; and
a plurality of modality corridors,
wherein each modality corridor of the plurality of modality corridors, is over a different network and in signal communication with the MoCo dispatcher,
wherein each modality corridor of the plurality of modality corridors establishes, for signal communication, a signal path from a plurality of signal paths, between the MNS Notification Engine and a recipient of the plurality of recipients, and

wherein the MoCo dispatcher is configured to select a first modality corridor from the plurality of modality corridors to establish a first signal path from the MNS Notification Engine to the recipient based upon the recipient.

2. The Incident-centric MNS system of claim 1 , wherein the first modality corridor includes a MoCo handler is in signal communication with the MoCo dispatcher, wherein the MoCo handler is configured to deliver Notifications from the MoCo dispatcher to the plurality of recipients via a plurality of delivery paths.

3. The Incident-centric MNS system of claim 1 , wherein the MNS Notification Engine is in signal communication with a user interface (“UI”) that allows an MNS User to interface with the MNS Notification Engine.

4. The Incident-centric MNS system of claim 3 , wherein the MNS User is a System Operator, wherein the System Operator is a System User for operating the Incident-centric MNS system during the Emergency Event.

5. The Incident-centric MNS system of claim 3 ,
wherein the recipient includes at least one MNS end-device capable of receiving outbound Notifications from the MNS Notification Engine and sending inbound Notifications to the MNS Notification Engine, and
wherein the at least one MNS end-device is capable of conveying the received outbound Notifications to a recipient user corresponding to the at least one MNS end-device.

6. The Incident-centric MNS system of claim 5 ,
wherein the MNS Notification Engine includes logic configured to manage a plurality of MNS Incidents and a plurality of Notifications,
wherein the logic configured to manage MNS Incidents and Notifications includes logic configured as an incident template,
wherein the logic configured as an incident template includes logic configured as an incident template content,
wherein the logic configured as incident template content includes at least one set of logic configured as a launch group,
wherein the at least one set of logic configured as a launch group includes logic configured as a notification template,
wherein the logic configured as a notification template includes data structures configured to hold pre-configured information about the plurality of Notifications, and
wherein the logic configured as a notification template is included in logic configured as a Notification Template Hierarchy.

7. The Incident-centric MNS system of claim 6 , wherein the logic configured as a notification template includes logic configured as a Message Template, logic configured as a Live Announcement Template, or both.

8. The Incident-centric MNS system of claim 7 ,
wherein the logic configured as a Message Template includes a data structure configured to hold pre-configured details of a Message and
wherein the logic configured as a Live Announcement Template includes a data structure configured to hold pre-configured details of a Live Announcement.

9. The Incident-centric MNS system of claim 8 ,
wherein an MNS Incident, of the plurality of MNS Incidents, includes a plurality of MNS Incident states,
wherein the logic configured as a launch group includes a plurality of Notification Templates, and
wherein the launch group is configured to launch the plurality of Notification Templates simultaneously during an MNS Incident state of the plurality of MNS Incident states.

10. The Incident-centric MNS system of claim 9 , wherein the plurality of MNS Incident states includes states selected from the group consisting of an active state, suspended state, suspending state, cancelled state, cancelling state, completed state, and closed state.

11. The Incident-centric MNS system of claim 10 ,
wherein the UI includes a plurality of graphical pictograms,
wherein each graphical pictogram represents an Emergency Event from a plurality of Emergency Events,
wherein the MNS User is a System Operator,
wherein the System Operator is a System User for operating the Incident-centric MNS system during an Emergency Event, and
wherein the UI is configured to allow a System Operator to quickly initiate an MNS Incident or launch a notification.

Assignees

• Ros Johannes P
• Wienands Christoph
• Gall Michael A
• Budnik Christof J
• Wittemann Michael
• Siemens Schweiz Ag

Inventors

• Ros Johannes P
• Wienands Christoph
• Gall Michael A
• Budnik Christof J
• Wittemann Michael

Classifications

• H04M3/00

  Automatic or semi-automatic exchanges · CPC title

• H04W4/22

  Electricity · mapped topic

• H04M11/04 Primary

  with alarm systems, e.g. fire, police or burglar alarm systems · CPC title

• H04W36/00

  Hand-off or reselection arrangements · CPC title

• H04M2203/205

  Broadcasting · CPC title