IP Library Granted Patent US 10,694,318
Granted Patent B2
US 10,694,318 · App. 15/987,477 · Granted Jun 23, 2020

Systems and methods for defining and implementing rules for three dimensional geofences

Inventor: Benjamin T. Jones (Henderson, NV)
Assignee: GEOFRENZY, INC.
H04W4/021B64C39/024G06F16/29G06F16/951G06F21/604G08G5/006G08G5/0021G08G5/0069H04L12/2816H04L12/403H04L61/1511H04L61/2007H04L67/02H04L67/141H04L67/18H04L67/2814H04W12/08H04W68/00B64C2201/145G08B21/24H04L61/609H04L61/6059H04W80/04
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,694,318
App. No.
15/987,477
Granted
Jun 23, 2020
Kind
B2
Abstract

The present invention is directed to methods and systems for enforcing at least one rule within a geofence. The rule is enforced by a fencing agent on an unmanned aerial vehicle (UAV). The geofence is defined by a plurality of geographic designators, with the plurality of geographic designators each being associated with an Internet Protocol (IP) address, preferably an IPv6 address.

Claims (41)

1. A method for enforcing at least one rule within a geofence, comprising:

defining at least one zone of the geofence by a unique Internet Protocol (IP) address anchor point in a geofence database, wherein the unique IP address anchor point is a unique identifier of the at least one zone, and wherein the unique IP address anchor point includes metadata associated with the at least one zone, including at least one rule for entering, exiting, or dwelling within the at least one zone;

determining a geographic location of an unmanned aerial vehicle (UAV) and converting the geographic location to an IP address;

identifying one of the at least one zone associated with the IP address based on a corresponding unique IP address anchor point;

identifying the at least one rule from the metadata associated with the corresponding unique IP address anchor point; and

implementing the at least one rule while the UAV is physically located within the at least one zone,

wherein the geofence is a three dimensional geofence, wherein the three dimensional geofence is a cone, a cylinder, a sphere, a spheroid, a rectangular prism, a triangular prism, a pentagonal prism, and/or a hexagonal prism, wherein the three dimensional geofence is defined by a plurality of points, wherein the plurality of points are defined by a plurality of IP addresses in the geofence database.

2. The method of claim 1 , further comprising a fencing agent performing the steps of identifying the one of the at least one zone associated with the IP address, identifying the at least one rule, and implementing the at least one rule.

3. The method of claim 2 , wherein the fencing agent is embedded in a chip including a processor and coupled with a memory in an operating system of the UAV.

4. The method of claim 2 , wherein the fencing agent is embedded in a code of an application on the UAV.

5. The method of claim 1 , wherein the unique IP address anchor point is associated with a geographic location in an airport.

6. The method of claim 1 , further comprising a server computer sending a notification over a network to the UAV or to a device in network communication with the UAV, wherein the notification includes an instruction to override the at least one rule, and a fencing agent implementing the instruction to override the at least one rule.

7. The method of claim 1 , further comprising the geofence database storing a longitude, a latitude, and an altitude corresponding to the unique IP address anchor point and updating the longitude, the latitude, and the altitude for the unique IP address anchor point in the geofence database in real-time.

8. A system for enforcing at least one rule within a geofence, comprising:

a server computer including a non-transitory computer readable medium, a processor, and a memory in network communication with a fencing agent of an unmanned aerial vehicle (UAV);

wherein the server computer is configured to define at least one zone of the geofence using a unique Internet Protocol (IP) address anchor point in a geofence database, wherein the unique IP address anchor point is a unique identifier of the at least one zone, and wherein the unique IP address anchor point includes metadata associated with the at least one zone, including at least one rule for entering, exiting, or dwelling within the at least one zone;

wherein the fencing agent is configured to determine a geographic location of the UAV and convert the geographic location to an IP address;

wherein the fencing agent is configured to identify one of the at least one zone associated with the IP address based on a corresponding unique IP address anchor point;

wherein the fencing agent is configured to identify the at least one rule from the metadata associated with the corresponding unique IP address anchor point;

wherein the fencing agent is configured to implement the at least one rule while the UAV is physically located within the at least one zone, and

wherein the geofence is a three dimensional geofence, wherein the three dimensional geofence is a cone, a cylinder, a sphere, a spheroid, a rectangular prism, a triangular prism, a pentagonal prism, and/or a hexagonal prism, wherein the three dimensional geofence is defined by a plurality of points, wherein the plurality of points are defined by a plurality of IP addresses in the geofence database.

9. The system of claim 8 , wherein the fencing agent is embedded in a chip in an operating system of the UAV.

10. The system of claim 8 , wherein the fencing agent is embedded in a code of an application on the UAV.

11. The system of claim 8 , wherein the unique IP address anchor point is associated with a geographic location in an airport.

12. The system of claim 8 , wherein the fencing agent is configured to receive a notification from the server computer, and wherein the fencing agent is configured to override the at least one rule based on the notification from the server computer.

13. The system of claim 8 , wherein the geofence database is configured to store a longitude, a latitude, and an altitude corresponding to the unique IP address anchor point and update the longitude, the latitude, and the altitude for the unique IP address anchor point in the geofence database in real-time.

14. An apparatus for enforcing at least one rule within a geofence, comprising:

an unmanned aerial vehicle (UAV) including a non-transitory computer readable medium, a processor, a memory, and a fencing agent;

wherein the UAV is in network communication with a server computer;

wherein the server computer includes a geofence database which defines at least one zone of the geofence using a unique Internet Protocol (IP) address anchor point, wherein the unique IP address anchor point is a unique identifier of the at least one zone, and

wherein the unique IP address anchor point includes metadata associated with the at least one zone, including at least one rule for entering, exiting, or dwelling within the at least one zone;

wherein the fencing agent is configured to determine a geographic location of the UAV and convert the geographic location to an IP address;

wherein the fencing agent is configured to identify one of the at least one zone associated with the IP address based on a corresponding unique IP address anchor point;

wherein the fencing agent is configured to identify the at least one rule from the metadata associated with the corresponding unique IP address anchor point;

wherein the fencing agent is configured to implement the at least one rule while the UAV is physically located within the at least one zone, and

wherein the geofence is a three dimensional geofence, wherein the three dimensional geofence is a cone, a cylinder, a sphere, a spheroid, a rectangular prism, a triangular prism, a pentagonal prism, and/or a hexagonal prism, wherein the three dimensional geofence is defined by a plurality of points, wherein the plurality of points are defined by a plurality of IP addresses in the geofence database.

15. The apparatus of claim 14 , wherein the fencing agent is embedded in a chip in an operating system of the UAV.

16. The apparatus of claim 14 , wherein the fencing agent is embedded in a code of an application on the UAV.

17. The apparatus of claim 14 , wherein the unique IP address anchor point is associated with a geographic location in an airport.

18. The apparatus of claim 14 , wherein the fencing agent is configured to receive a notification from the server computer, and wherein the fencing agent is configured to override the at least one rule based on the notification from the server computer.

19. The apparatus of claim 14 , wherein the geofence database is configured to store a longitude, a latitude, and an altitude corresponding to the unique IP address anchor point and update the longitude, the latitude, and the altitude for the unique IP address anchor point in the geofence database in real-time.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2018
From: JONES, BENJAMIN T.
To: GEOFRENZY, INC.
Reel/Frame 046543/0070 →
Continuity (22)
Continuation 15225433 · Aug 1, 2016
Continuation In Part 15170619 · Jun 1, 2016
Continuation 14728259 · Jun 2, 2015
Continuation In Part 15213072 · Jul 18, 2016
Continuation In Part 14953485 · Nov 30, 2015
Continuation In Part 14745951 · Jun 22, 2015
Continuation In Part 14728259 · Jun 2, 2015
Continuation In Part 14811234 · Jul 28, 2015
Continuation In Part 14755669 · Jun 30, 2015
Continuation In Part 14745951 · Jun 22, 2015
Continuation In Part 14728259 · Jun 2, 2015
Continuation In Part 14728259 · Jun 2, 2015
Continuation In Part 14745951 · Jun 22, 2015
Continuation In Part 14728259 · Jun 2, 2015
Continuation In Part 14728259 · Jun 2, 2015
Continuation In Part 14740557 · Jun 16, 2015
Continuation 14728259 · Jun 2, 2015
Continuation In Part 15007661 · Jan 27, 2016
Continuation 14740557 · Jun 16, 2015
Continuation 14728259 · Jun 2, 2015
Provisional Application 62030252 · Jul 29, 2014
Related Publication 20180270611A1 · Sep 20, 2018
Cited By (7)
US 12,301,943 US 12,302,191 US 12,387,578 US 12,549,924 US 12,598,155 US 12,647,749 US 12,689,868