Collaborative and distributed emergency multimedia data management

• US 9,509,842 B2
• Filed: 09/14/2015
• Issued: 11/29/2016
• Est. Priority Date: 06/17/2011
• Status: Active Grant

• Current Assignee: Motorola Solutions Connectivity Incorporated (Motorola Solutions, Inc.)
• Original Assignee: Airbus DS Communications Incorporated (Motorola Solutions, Inc.)
• Inventors: Estrada, Lorenzo Javier, Kamboh, Ameel, Wellonen, Jason
• Primary Examiner(s): Kamara, Mohamed
• Assistant Examiner(s): DEFAUW, THAD N
• Application Number:
  US14/852,940
• Publication Number:
  US 20150381806A1
• Time in Patent Office: 442 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 45/3065 for real time traffic
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04L 65/60 Network streaming of media packets
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/30 Profiles
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04M 11/04 with alarm systems, e.g. fire, police or burglar alarm systems
• CPC Class Codes: H04M 3/5116 for emergency applications
• CPC Class Codes: H04M 3/5183 Call or contact centers with computer-telephony arrangements
• CPC Class Codes: H04M 7/0075 Details of addressing, directories or routing tables
• CPC Class Codes: H04W 4/08 User group management
• CPC Class Codes: H04W 4/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]

Abstract

Systems, apparatus, and methods for collaborative and distributed emergency multimedia data management are described. In one aspect, a system includes a packet data reception interface. The system further includes a rules engine coupled with the packet data reception interface and configured to select a processing profile for packet data received, the rules engine further configured to associate packet data received with stored packet data. The system also includes a policy engine coupled with the rules engine and configured to execute the processing profile for packet data received.

Claims

1. A system for collaborative and distributed emergency multimedia data management comprising:

a packet data reception interface configured to receive first emergency event packet data and second emergency event packet data, the first emergency event packet data having a first media type and the second emergency event packet data having a second media type, the first media type being different than the second media type;

a rules engine coupled with the packet data reception interface and configured to;

generate a first event routing plan for the first emergency event packet data using a first value included in the first emergency event packet data, the first event routing plan identifying a first networked application to receive the first emergency event packet data; and

generate a second event routing plan for the second emergency event packet data using a second value included in the second emergency event packet data, the second event routing plan identifying a second networked application to receive the second emergency event packet data, wherein the second networked application is located at a different address than the first networked application; and

a policy engine coupled with the rules engine and configured to;

initiate a display via the first networked application using the first emergency event packet data; and

initiate another display of the second emergency event packet data via the second networked application, wherein the display via the first networked application indicates initiation of the another display via the second networked application.

2. The system of claim 1, wherein the rules engine is further configured to:

compare the first value or the second value with one or more values included in a plurality of processing profiles, each processing profile including an event routing plan; and

select a processing profile including the first event routing plan or the second event routing plan from the plurality of processing profiles based at least in part on the comparison.

3. The system of claim 1, wherein:

the packet data reception interface is configured to;

receive the first emergency packet data at a first time; and

receive the second emergency event packet data at a second time after the first time,

the rules engine is further configured to associate the second emergency event packet data with the first emergency event packet data based on proximity of a first time or a first location identified in the first emergency event packet data to a second time or a second location identified in second emergency event packet data.

4. The system of claim 1, wherein the packet data reception interface is configured to receive geospatial data or temporal data, and at least one of voice data, video data, text message data, email, image data, and audio data for each of the first emergency event packet data and the second emergency event packet data.

5. The system of claim 2, wherein the value that the rules engine is configured to compare comprises at least one of a header value and a content value included in the first emergency event packet data or the second emergency event packet data.

6. The system of claim 2, wherein the rules engine is configured to compare the value by generating a comparison value indicating if the value is equal to a stored value included in a processing profile.

7. The system of claim 3, wherein the rules engine is further configured to associate the first emergency event data with the second emergency event data by:

identifying a second value included in the second emergency event packet data, the second value identifying neither the second time nor the second location;

comparing the second value with one or more values included in the first emergency event packet data to obtain a comparison result; and

wherein the associating of the second emergency event packet data with first emergency event packet data is performed when the comparison result indicates a match between at least a portion of the second value included in the second emergency event packet data and at least a portion of the one or more values included in the first emergency event packet data.

8. The system of claim 3, wherein identifying a second value included in the second emergency event packet data comprises identifying at least one of a header value and a content value included in the second emergency event packet data.

9. The system of claim 5, wherein the value that the rules engine is configured to compare indicates at least one of a packet content type, a packet content length, a packet source, and a packet destination.

10. The system of claim 8, wherein the second value indicates at least one of a packet content type, a packet content length, a packet source, and a packet destination.

11. A method for collaboration and distribution of emergency multimedia data in a management system, the method comprising:

receiving a first emergency data element and a second emergency data element, the first emergency data element having a first media type and the second emergency data element having a second media type, the first media type being different than the second media type;

generating a first event routing plan for the first emergency data element using a first value included in the first emergency data element, the first event routing plan identifying a first application to receive the first emergency data element;

generating a second event routing plan for the second emergency data element using a second value included in the second emergency data element, the second event routing plan identifying a second application to receive the second emergency data element, wherein the second application is located at a different address than the first networked application;

initiating presentation of the first emergency data element via the first application; and

initiating presentation of the second emergency data element via the second application, wherein the presentation of the first emergency data element includes an indication of the initiation of the presentation of the second emergency data element via the second application.

12. The method of claim 11, further comprising:

identifying a value included in one of the first emergency data element or the second emergency data element;

comparing the identified value with one or more values included in a plurality of processing profiles, each processing profile including an event routing plan; and

selecting a processing profile including the first event routing plan or the second event routing plan from the plurality of processing profiles based at least in part on the comparison.

13. The method of claim 11, wherein the first emergency data element and the second emergency data element each include geospatial data or temporal data, and at least one of voice data, video data, text message data, email, image data, and audio data.

14. The method of claim 11, further comprising:

receiving the first emergency data element at a first time;

receiving the second emergency data element at a second time after the first time; and

associating the second emergency multimedia data element with the first emergency multimedia data element based on proximity of a first time or a first location identified in the first emergency multimedia data element to a second time or a second location identified in second emergency multimedia data element.

15. The method of claim 12, wherein identifying a value included in an emergency data element comprises identifying at least one of a header value and a content value.

16. The method of claim 12, wherein comparing the identified value comprises generating a comparison value indicating if the identified value is equal to a stored value included in a processing profile.

17. The method of claim 15, wherein the identified value indicates at least one of a packet content type, a packet content length, a packet source, and a packet destination.

18. A system for collaborative and distributed emergency multimedia data management comprising:

means for receiving a first emergency data element and a second emergency data element, the first emergency data element having a first media type and the second emergency data element having a second media type, the first media type being different than the second media type;

means for generating a first event routing plan for the first emergency data element using a first value included in the first emergency data element, the first event routing plan identifying a first application to receive the first emergency data element;

means for generating a second event routing plan for the second emergency data element using a second value included in the second emergency data element, the second event routing plan identifying a second application to receive the second emergency data element, wherein the second application is located at a different address than the first networked application;

means for initiating presentation of the first emergency data element via the first application; and

means for initiating presentation of the second emergency data element via the second application, wherein the presentation of the first emergency data element includes an indication of the initiation of the presentation of the second emergency data element via the second application.