Registrar Mapping Toolkit for Geofences

• US 20170055123A1
• Filed: 11/07/2016
• Published: 02/23/2017
• Est. Priority Date: 06/02/2015
• Status: Active Grant

• Current Assignee: GeoFrenzy, Inc
• Original Assignee: GeoFrenzy, Inc
• Inventors: Jones, Benjamin T.
• Granted Patent: US 10,021,519 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: B64C 39/024 of the remote controlled vehicle type, i.e. RPV
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G08G 5/006 in accordance with predefined flight zones, e.g. to avoid prohibited zones
• CPC Class Codes: G08G 5/0069 specially adapted for an unmanned aircraft
• CPC Class Codes: H04L 12/2816 Controlling appliance services of a home automation network by calling their functionalities arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station; in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom H04Q9/00
• CPC Class Codes: H04L 2101/659 Internet protocol version 6 [IPv6] addresses
• CPC Class Codes: H04L 2101/69 using geographic information, e.g. room number
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/457 containing identifiers of data entities on a computer, e.g. file names
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04W 12/084 using delegated authorisation, e.g. open authorisation [OAuth] protocol
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 64/003 locating network equipment
• CPC Class Codes: H04W 68/00 User notification, e.g. alerting and paging, for incoming communication, change of service or the like
• CPC Class Codes: H04W 80/04 : Network layer protocols, e.g. mobile IP [Internet Protocol]

Abstract

Systems and methods for creating a database of geofences and registering geofences, with each geofence in the database being associated with an IP address, preferably an IPv6 address. Each geofence is defined using at least one geographic designator, preferably real property boundaries. Entitlements can be associated with geofences relating to permissive and prohibitive activities within the geofences.

Claims

1. A method for geofence lookup comprising:

a fencing agent on an application of a mobile device with a processor and a memory retrieving an Internet Protocol version 6 (IPv6) address defining a geofence from a remote database on a remote server computer, wherein the remote server computer is connected to the mobile device over a network;

the fencing agent monitoring a location of the mobile device to determine the location of the mobile device relative to the geofence; and

if the fencing agent determines that the location of the mobile device is inside the geofence, the fencing agent enforcing an entitlement associated with the geofence on the mobile device;

wherein the IPv6 address is a unique identifier of the geofence; and

wherein location data associated with the geofence is encoded in the IPv6 address.

2. The method of claim 1, further comprising the mobile device automatically querying the remote database for a class and a zoom range pairing.

3. The method of claim 1, further comprising the fencing agent determining a time of day or a proximity to a geofence, wherein the step of the fencing agent enforcing the entitlement associated with the geofence on the mobile device is based on the time of day or the proximity to the geofence.

4. The method of claim 1, further comprising upon the mobile device approaching the geofence, the fencing agent determining that the mobile device is approaching the geofence and the application sending a notification to a device associated with the geofence or to the remote server computer, wherein the notification includes information about the mobile device approaching the geofence.

5. The method of claim 1, further comprising upon the mobile device exiting the geofence, the fencing agent determining that the mobile device is exiting the geofence and the application sending a notification to a device associated with the geofence or to the remote server computer, wherein the notification includes information about the mobile device exiting the geofence.

6. The method of claim 1, wherein the location data associated with the geofence is encoded in the IPv6 address using between 1 bit and 63 bits.

7. The method of claim 1, wherein boundaries of the geofence are defined within between about 0.5 microns and 30 centimeters.

8. The method of claim 1, wherein upon the fencing agent determining that the mobile device is located inside the geofence:

the mobile device receiving a request to access information accessible within the geofence;

the fencing agent sending a request to the remote server computer or a device associated with the geofence;

upon receiving approval of the request, the mobile device accessing the information accessible within the geofence.

9. The method of claim 8, wherein the request to access information accessible within the geofence includes acceptance of terms and conditions to enter the geofence, wherein the terms and conditions include data collection from the mobile device.

10. The method of claim 1, further comprising the remote server computer determining a number of times the mobile device has entered the geofence and an average duration of time spent by the mobile device in the geofence.

11. The method of claim 1, further comprising upon the fencing agent determining that the location of the mobile device is inside the geofence, automatically displaying a notification on the mobile device that the mobile device is located within the geofence.

12. A method for geofence lookup comprising:

an application on a mobile device with a processor and a memory receiving a query for a geofence in a region of interest, wherein the query includes at least one non-geographic search term;

sending the query for the geofence in the region of interest to a remote server computer connected with the mobile device over a network;

the remote server computer returning an Internet Protocol version 6 (IPv6) address associated with the geofence in the region of interest to the application on the mobile device; and

based on the IPv6 addresses, the application on the mobile device displaying the geofence in the region of interest on a map;

wherein location data associated with the geofence is encoded in the IPv6 address.

13. The method of claim 12, further comprising the mobile device receiving an input inside the geofence on the map indicating a request for the mobile device to enter the geofence.

14. The method of claim 13, wherein the request for the mobile device to enter the geofence includes acceptance of terms and conditions to enter the geofence, wherein the terms and conditions include data collection from the mobile device.

15. The method of claim 12, further comprising the mobile device querying the remote server computer for information associated with the geofence and displaying the information associated with the geofence on the map.

16. The method of claim 15, wherein the information includes a class of the geofence, hours the geofence is accessible, or an entitlement associated with the geofence.

17. The method of claim 15, wherein the location data associated with the geofence is encoded in the IPv6 address using between 1 bit and 63 bits.

18. A geofence lookup system comprising:

a mobile device with a processor and a memory; and

a remote server computer with a remote database,

wherein the mobile device is connected over a network to the remote server computer and the mobile device includes an application with a fencing agent;

wherein the fencing agent is operable to retrieve Internet Protocol version 6 (IPv6) address associated with a geofence from the remote database on the remote server computer;

wherein the IPv6 address is a unique identifier of the geofence;

wherein location data associated with the geofence is encoded in the IPv6 address;

wherein the fencing agent is operable to determine if the mobile device is located within the geofence based on the location data in the IPv6 address associated with the geofence;

wherein the fencing agent is operable to enforce an entitlement associated with the geofence on the mobile device upon the fencing agent determining that the mobile device is located within the geofence.

19. The system of claim 18, wherein the location data associated with the geofence is encoded in the IPv6 address using between 1 bit and 63 bits.

20. The system of claim 18, wherein boundaries of the geofence are defined within between about 0.5 microns and 30 centimeters.