SYSTEM AND METHOD FOR DYNAMIC DATA MINING AND DISTRIBUTION OF MARITIME DATA

• US 20100138644A1
• Filed: 04/11/2008
• Published: 06/03/2010
• Est. Priority Date: 04/13/2007
• Status: Active Grant

• Current Assignee: Allen F. Labbe, Victor John Jr. Yannacone
• Original Assignee: Allen F. Labbe, Victor John Jr. Yannacone
• Inventors: Yannacone, Victor John JR., Labbe, Allen F.
• Granted Patent: US 8,332,087 B2
• Time in Patent Office: Days
• US Class Current: 713/150
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: G06Q 50/40 Business processes related to the transportation industry shipping G06Q10/083
• CPC Class Codes: G08G 3/00 Traffic control systems for marine craft marking of navigational route B63B22/16, B63B51/00

Abstract

A system for dynamically collecting and distributing maritime data includes a vessel configured to transmit at a predetermined time, or upon electronic inquiry, a signal representative of a current location of the vessel or an expected location of the vessel; a computer network including one or more databases, each of which includes one or more zone of concern data, wherein the zone of concern data corresponds to a zone of concern; and a service provider configured to receive the signal, retrieve the one or more zone of concern data from the computer network based upon the signal and transmit the one or more zone of concern data to the vessel. The zone of concern data, which may he continually changing, may be sent from the service provider to the vessel on a continuous basis with respect to the changing location and heading of the vessel.

Claims

1. A system for collecting and distributing maritime data, comprising:

a water-faring vessel configured to transmit a signal representative of (i) a current location of the vessel or (ii) an expected location of the vessel;

a computer network including a plurality of databases, wherein each of the plurality of databases includes at least one zone of concern data that is continually updated, wherein the zone of concern data corresponds to occurrences associated with a zone of concern; and

a server configured to;

receive the signal from the vessel;

receive at a first time from the plurality of databases zone of concern data based upon the signal;

store the zone of concern data retrieved at the first time;

transmit the zone of concern data retrieved at the first time to the vessel;

receive at a second time from the plurality of databases zone of concern data based upon the signal;

store the zone of concern data retrieved at the second time;

compare the zone of concern data retrieved at the first time to the zone of concern data retrieved at the second time; and

transmit the zone of concern data retrieved at the second time to the vessel if the zone of concern data retrieved at the second time is different from the zone of concern data retrieved at the first time.

2. The system of claim 1, wherein the zone of concern is (i) a three-dimensionally distance-bounded area surrounding the vessel or (ii) a time-bounded area surrounding the vessel.

3. The system of claim 2, wherein the server is operative for:

formulating a query as a function of (i) the location of the vessel or (ii) the expected location of the vessel; and

transmitting the query to the plurality of databases.

4. The system of claim 3, wherein the zone of concern data includes (i) accident data, (ii) health crises data, (iii) piracy data, (iv) terrorism data, (v) open warfare data, (vi) disease data, (vii) emergency re-routing data, (viii) political unrest data, (ix) coast guard assistance data, (x) navigation lights data, (xi) reef data, (xii) shipwreck data, or (xiii) port contact information data.

5. The system of claim 1, wherein the plurality of databases is remote from the server and the vessel.

6. The system of claim 3, wherein the signal further comprises a unique identifier identifying the vessel.

7. The system of claim 3, further comprising one or more satellites, wherein the one or more satellites is operative for:

receiving the signal from the vessel;

transmitting the signal to the service provider;

receiving the zone of concern data from the server; and

transmitting the zone of concern data to the vessel.

8. The system of claim 3, wherein the server is operative for:

formatting the zone of concern data to be compatible with an email browser of the vessel; and

stripping the zone of concern data of any non-essential data.

9. The system of claim 3, wherein the server is operative for encrypting the zone of concern data into an encrypted zone of concern data and transmitting the encrypted zone of concern data to the vessel.

10. The system of claim 8, wherein the server is operative for formatting the one or more zone of concern data into programmatic data and transmitting the programmatic data to the vessel.

11. The system of claim 10, wherein the vessel includes a local data set, wherein the local data set is at least one object image, and wherein the vessel is operative for:

receiving the programmatic data;

executing the programmatic data in the presence of the local data set; and

displaying information as a result of executing the programmatic data, wherein the information is representative of the zone of concern data in relation to the local data set.

12. The system of claim 11, wherein the vessel is operative for displaying the information in:

(i) a graphical format;

(ii) a dynamic format;

or

(iii) a user-interactive format on the email browser of the vessel.

13. The system of claim 3, wherein the server is operative for querying each of the databases at pre-determined times.

14. A system for collecting and distributing maritime data, comprising:

means for receiving a signal from a water-faring vessel, wherein the signal is representative of (i) a current location of the vessel or (ii) an expected location of the vessel;

means for formulating a query as a function of (i) the location of the vessel or (ii) the expected location of the vessel;

means for transmitting the query at a first time and then at a second predefined time or interval to a plurality of databases remote from the server and the vessel;

means for receiving at a first time and at a second time from the plurality of databases zone of concern data;

means for storing the zone of concern data retrieved at the first time and at the second time;

means for transmitting the zone of concern data retrieved at the first time to the vessel; and

means for comparing the zone of concern data retrieved at the first time to the zone of concern data retrieved at the second time, wherein the means for transmitting the zone of concern data retrieved at the first time is further configured to transmit the zone of concern data retrieved at the second time to the vessel if the zone of concern data retrieved at the second time is different from the zone of concern data retrieved at the first time.

15. The system of claim 14, further comprising means for designating the zone of concern data retrieved at the first time and zone of concern data retrieved at the second time as representative of the zone of concern data stored on the vessel.

16. The system of claim 14, wherein the zone of concern data corresponds to occurrences associated with a zone of concern, and the zone of concern is (i) a three-dimensionally distance-bounded area surrounding the vessel or (ii) a time-bounded area surrounding the vessel, wherein the zone of concern data is (i) accident data, (ii) health crises data, (iii) piracy data, (iv) terrorism data, (v) open warfare data, (vi) disease data, (vii) emergency re-routing data, (viii) political unrest data, (ix) coast guard assistance data, (x) navigation lights data, (xi) reef data, (xii) shipwreck data, or (xiii) port contact information data.

17. The system of claim 14, wherein:

the means for storing the zone of concern data retrieved at the first time and at the second time is further configured to store an intended designated route of the vessel, wherein the designated route represents locations through which the vessel is intended to pass;

the means for transmitting the zone of concern data retrieved at the first time is further configured to transmit a request for the current location of the vessel and receive the current location thereof, wherein the system further comprises;

means for determining if the current location corresponds to any of the locations through which the vessel was intended to pass and, if the current location does not correspond to any of the locations through which the vessel was intended to pass,

formulating a second query as a function of the current location of the vessel;

transmitting the second query to the plurality of databases;

receiving at a third time from the plurality of databases zone of concern data;

storing the zone of concern data retrieved at the third time; and

transmitting the zone of concern data retrieved at the third time to the vessel and optionally designate the zone of concern data retrieved at the third time as representative of the zone of concern data stored on the vessel.

18. The system of claim 17, wherein the service provider is further configured to inform an on-shore support team responsible for vessel that the vessel has deviated from the designated route.

19. A method for collecting and distributing maritime data, comprising the steps of

(a) receiving a signal from a water-faring vessel, wherein the signal is representative of (i) a current location of the vessel or (ii) an expected location of the vessel;

(b) formulating a query as a function of (i) the location of the vessel or (ii) the expected location of the vessel;

(c) transmitting the query to a plurality of databases remote from the server and the vessel;

(d) receiving at a first time from the plurality of databases zone of concern data;

(e) storing the zone of concern data retrieved at the first time;

(f) transmitting the zone of concern data retrieved at the first time to the vessel;

(g) transmitting the query again at a predefined time or interval to the plurality of databases;

(h) receiving at a second time from the plurality of databases zone of concern data;

(i) storing the zone of concern data retrieved at the second time;

(j) comparing the zone of concern data retrieved at the first time to the zone of concern data retrieved at the second time; and

(k) transmitting the zone of concern data retrieved at the second time to the vessel if the zone of concern data retrieved at the second time is different from the zone of concern data retrieved at the first time.

20. The method of claim 19, further comprising the steps of:

(a) storing an intended designated route of the vessel, wherein the designated route represents locations through which the vessel is intended to pass;

(b) transmitting a request for the current location of the vessel and receive the current location thereof; and

(c) determining if the current location corresponds to any of the locations through which the vessel was intended to pass and, if the current location does not correspond to any of the locations through which the vessel was intended to pass,

formulating a second query as a function of the current location of the vessel;

transmitting the second query to the plurality of databases;

receiving at a third time from the plurality of databases zone of concern data;

storing the zone of concern data retrieved at the third time; and

transmitting the zone of concern data retrieved at the third time to the vessel and optionally designate the zone of concern data retrieved at the third time as representative of the zone of concern data stored on the vessel.