Incident-centric mass notification system
US-9641692-B2 · May 2, 2017 · US
US10271194B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10271194-B2 |
| Application number | US-201715472835-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 29, 2017 |
| Priority date | Jun 25, 2013 |
| Publication date | Apr 23, 2019 |
| Grant date | Apr 23, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. A Mass Notification System (“MNS”) Notification Engine for use in Incident-centric Mass Notification System (“Incident-centric MNS system”), the MNS Notification Engine comprising: logic configured to manage a plurality of MNS Incidents and a plurality of Notifications, 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 and the logic configured as a notification template includes data structures configured to hold pre-configured information about the plurality of Notifications and the logic configured as a notification template is included in logic configured as a Notification Template Hierarchy; and a user interface (“UI”) that allows an MNS User to interface with the MNS Notification Engine. 2. The MNS Notification Engine of claim 1 , 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. 3. The MNS Notification Engine of claim 1 , wherein the logic configured as a notification template includes logic configured as a Message Template, logic configured as a Live Announcement Template, or both. 4. The MNS Notification Engine of claim 3 , 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. 5. The MNS Notification Engine of claim 4 , 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. 6. The MNS Notification Engine of claim 5 , 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, all-clear state, completed state, and closed state. 7. The MNS Notification Engine of claim 6 , 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 and launch a notification.
for emergency applications · CPC title
with alarm systems, e.g. fire, police or burglar alarm systems · CPC title
Automatic or semi-automatic exchanges · CPC title
Physics · mapped topic
Broadcasting · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.