Geofence information delivery systems and methods

• US 10,547,968 B2
• Filed: 02/23/2018
• Issued: 01/28/2020
• Est. Priority Date: 06/02/2015
• Status: Active Grant

• Current Assignee: GeoFrenzy, Inc
• Original Assignee: GeoFrenzy, Inc
• Inventors: Jones, Benjamin T.
• Primary Examiner(s): Patel, Hitesh
• Application Number:
  US15/903,874
• Publication Number:
  US 20180184242A1
• Time in Patent Office: 704 Days
• 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 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G08B 13/00 Burglar, theft or intruder alarms
• CPC Class Codes: G08G 5/0052 for cruising combined instruments indicating more than one navigational value G01C23/00
• 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: G08G 5/025 Navigation or guidance aids radar or analogous systems specially adapted for landing purposes G01S13/913
• 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/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04W 12/08 Access security
• 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 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

The present invention is directed to methods and systems for requesting information from a mobile device with a fencing agent. The fencing agent determines a position with a DNS resolver, queries geofences with an IP address, receives an anchor point with an IP address from the DNS resolver. The device with the fencing agent is able to receive multiple anchor points within multiple geofences within an ROI and translate fence points into fence geometries. Geofence information is stored and registered in a database of geofences, and each geofence is associated with a plurality of geographic designators, wherein each of the plurality of geographic designators is associated with an IP address.

Claims

1. A method for requesting information for at least one geofence comprising:

providing a processor coupled with a memory on at least one device;

the at least one device generating a request for geofence information, wherein the request includes a geographic location;

converting the geographic location to an Internet Protocol (IP) address with a Domain Name System (DNS) resolver;

querying for geofences based on the IP address;

receiving geofence information from the DNS resolver, wherein the geofence information includes at least one anchor point with at least one anchor point IP address, an identification of the at least one geofence, and at least one class or at least one entitlement;

wherein the at least one geofence is defined by at least one geographic designator;

wherein the at least one class and/or the at least one entitlement are encoded in the at least one anchor point IP address; and

wherein the geographic location is a current location of the at least one device, wherein the step of generating the request for geofence information is automatically performed by the at least one device upon the at least one device coming within a predetermined physical proximity of the geographic location.

2. The method of claim 1, further comprising populating a cache with the geofence information.

3. The method of claim 1, further comprising the DNS resolver retrieving the geofence information from a local cache.

4. The method of claim 1, further comprising a fencing agent translating the geofence information into a fence geometry, wherein the fence geometry is defined centroidally or noncentroidally in geoJSON format.

5. The method of claim 1, further comprising activating at least one rule associated with the at least one geofence on the at least one device by transmitting an activation packet to the at least one device, wherein transmitting the activation packet to the at least one device transforms the at least one device from a first state to a second state.

6. A system for requesting information for at least one geofence comprising:

at least one device having a processor coupled with a memory, wherein the at least one device is constructed and configured for wireless communication; and

a Domain Name System (DNS) resolveq;

wherein the DNS resolver determines an Internet Protocol (IP) address associated with a position of the at least one device;

wherein the DNS resolver determines an anchor point IP address of the at least one geofence based on the IP address;

wherein the anchor point IP address includes geofence information including metes and bounds of the at least one geofence;

wherein the at least one device translates the geofence information into a fence geometry;

wherein the geofence information includes at least one class or at least one entitlement, wherein the at least one class or at least one entitlement is encoded in the anchor point IP address; and

wherein the position is a current location of the at least one device, wherein the DNS resolver determines the anchor point IP address of the at least one geofence associated with the IP address upon the at least one device entering the at least one geofence.

7. The system of claim 6, wherein the at least one device populates a cache with the geofence information.

8. The system of claim 6, wherein the DNS resolver determines the anchor point IP address of the at least one geofence using a local cache.

9. The system of claim 6, wherein the position corresponds to a Region of Interest (ROI).

10. The system of claim 6, wherein the fence geometry is defined centroidally or noncentroidally in geoJSON format.

11. A method for requesting information for at least one geofence comprising:

providing a processor coupled with a memory, constructed and configured for wireless communication on at least one device;

the at least one device generating a request for geofence information, wherein the request includes a geographic location;

converting the geographic location to an Internet Protocol (IP) address;

querying for geofences based on the IP address;

receiving geofence information from a Domain Name System (DNS) resolver, wherein the geofence information includes at least one anchor point with at least one anchor point IP address, an identification of the at least one geofence, and at least one class or at least one entitlement;

the at least one device translating the geofence information into a fence geometry;

wherein the geographic location is a current location of the at least one device, wherein the step of generating the request for geofence information is automatically performed by the at least one device upon the at least one device coming within a predetermined physical proximity of the geographic location; and

wherein the geofence information includes at least one class or at least one entitlement, wherein the at least one class or at least one entitlement is encoded in the anchor point IP address.

12. The method of claim 11, further comprising populating a cache with the geofence information.

13. The method of claim 11, wherein the DNS resolver retrieves the geofence information from a local cache.

14. The method of claim 11, wherein the fence geometry is defined centroidally or noncentroidally in geoJSON format.