SYSTEMS AND METHODS FOR REMOTE ACCESS TO INCIDENT DATA

• US 20100217879A1
• Filed: 05/07/2010
• Published: 08/26/2010
• Est. Priority Date: 11/14/2007
• Status: Abandoned Application

• Current Assignee: Analogics, Inc.
• Original Assignee: Analogics, Inc.
• Inventors: Weiner, Michael M.
• Application Number:
  US12/776,176
• Publication Number:
  US 20100217879A1
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/027 using movement velocity, acceleration information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Abstract

Systems, devices, and methods for acquisition, processing and display of data from devices, associated with geo-locations.

Claims

1. A system comprising:

a first processing node comprising a central processing unit and addressable member, wherein the central processing unit of the first processing node is configured to establish one or more data sessions with one or more data sources, wherein each data session is associated with a globally unique identifier and each data session is associated with a specific source with a geo-location; and

a second processing node in networked communication with the first processing node, the second processing node comprising a central processing unit and addressable member wherein the central processing unit of the second processing node is configured to display within a geographic information system the session data from the first processing node based on the geo-location associated with the data session.

2. The system of claim 1 wherein the central processing unit of the first processing node is further configured to assign a globally unique identifier to each data source based on a minimal negligible probability of duplicating an identifier of a data source by a third processing node.

3. The system of claim 1 wherein the central processing unit of the first processing node is further configured to aggregate collections of data sources and data sessions from other servers located within a designated geographical area.

4. The system of claim 1 wherein the central processing unit of the first processing node is further configured to:

determine a time of a data session;

determine a geo-location of a data session; and

determine if a data session merits designation as an incident, and if so, store the determined time and determined geo-location in an incident collection.

5. The system of claim 1 wherein the central processing unit of the first processing node is further configured to:

determine a time of a data session;

determine a geo-location of a data session; and

identify one or more data sessions that fall within a designated time interval and distance from a corresponding time and geo-location of an entry in an incident collection of an incident, and associate the identified one or more sessions with the incident.

6. A server comprising:

a central processing unit and addressable member, wherein the central processing unit is configured to establish one or more data sessions with one or more data sources, wherein each data session is associated with a unique identifier and each data session is associated with a specific source with a geo-location; and

wherein the server is configured to output data of the associated data sessions.

7. The server of claim 6 wherein the central processing unit is further configured to assign a globally unique identifier to each data source based on a minimal negligible probability of duplicating an identifier of a data source by a third processing node.

8. The server of claim 6 wherein the central processing unit is further configured to aggregate collections of data sources and data sessions from other servers located within a designated geographical area.

9. The server of claim 6 wherein the central processing unit is further configured to:

determine a time of a data session;

determine a geo-location of a data session; and

determine if a data session merits designation as an incident, and if so, store the determined time and determined geo-location in an incident collection.

10. The server of claim 6 wherein the central processing unit is further configured to:

determine a time of a data session;

determine a geo-location of a data session; and

identify one or more data sessions that fall within a designated time interval and distance from a corresponding time and geo-location of an entry in an incident collection of an incident, and associate the identified one or more sessions with the incident.

11. A client comprising:

a central processing unit and addressable member wherein the central processing unit is configured to receive session data associated with a unique identifier for a data source and is configured to receive session data associated with a specific source and a geo-location associated with the session data set; and

wherein the client is further configured to display within a geographic information system one or more session data sets based on the geo-location associated with each data session set.

12. The client of claim 11 wherein the central processing unit if further configured to aggregate collections of data sources and data sessions from other servers located within a designated geographical area.

13. A method of accessing integrated remote incident data comprising:

establishing, by a first processing node, one or more data sessions with one or more data sources;

associating, by the first processing node, each data session with a unique identifier;

associating, by the first processing node, each data session with a geo-location; and

displaying, by the second processing node and within a geographic information system the session, data from the first processing node based on the geo-location associated with the data session.

14. The method of claim 13 further comprising assigning, by the first processing node, a globally unique identifier to each data source based on a minimal negligible probability of duplicating an identifier of a data source by a third processing node.

15. The method of claim 13 further comprising aggregating, by the first processing node, collections of data sources and data sessions from other processing nodes located within a designated geographical area.

16. The method of claim 13 further comprising:

determining, by the first processing node, a time of a data session;

determining, by the first processing node, a geo-location of a data session; and

determining, by the first processing node, whether a data session merits designation as an incident, and if so, storing the determined time and determined geo-location in an incident collection.

17. The method of claim 13 further comprising:

determining, by the first processing node, a time of a data session;

determining, by the first processing node, a geo-location of a data session; and

identifying, by the first processing node, one or more data sessions that fall within a designated time interval and distance from a corresponding time and geo-location of an entry in an incident collection of an incident, and associating the identified one or more sessions with the incident.