# US 2018/0322144 A1 · Geofence Information Delivery Systems and Methods

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0322144 A1
- Document ID: US20180322144A1
- Status: Published application
- Kind: A1
- Application number: 16/031,427
- Filed: 2018-07-10
- Published: 2018-11-08
- Earliest claimed: 2015-06-02
- Assignees: GeoFrenzy, Inc.
- Applicants: GeoFrenzy, Inc.
- Inventors: Benjamin T. Jones
- Web page: https://patentgrep.com/patent/US20180322144A1

## CPC

- G06F 16/29: Geographical information databases
- G06F 16/258: {Data format conversion from or to a database}
- H04W 4/021: Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present invention is directed to methods and systems for querying a database of geofences. A method for querying a database of geofences in the present invention includes generating at a device a first request comprising an Internet Protocol address, converting the IP address to a geographic location, identifying one or more geofences associated with the geographic location, and creating a first response to the first request wherein the first response comprises information describing the one or more geofences.

## Claims

### Claim 1

A method for delivering geofence information by one or more processors, comprising:
generating at a device a Domain Name System (DNS) query comprising an Internet Protocol version 6 (IPv6) address, wherein the IPv6 address corresponds to a geographic location of the device;
matching the IPv6 address to at least one geofence anchor point;
constructing a DNS response comprising the at least one geofence anchor point and transmitting the DNS response to the device;
generating at the device at least one secondary DNS query comprising one of the at least one geofence anchor point;
identifying fence points corresponding to the one of the at least one geofence anchor point; and
constructing at least one secondary DNS response to the at least one secondary DNS query, wherein the at least one secondary DNS response includes the fence points; and
wherein the DNS query and the at least one secondary DNS query are validated by DNS Security (DNS SEC).

### Claim 2 (depends on 1)

The method of claim 1, wherein the DNS response includes a list of geofence anchor points including the at least one geofence anchor point.

### Claim 3 (depends on 1)

The method of claim 1, wherein the DNS response and the at least one secondary DNS response each include a text (TXT) resource record, and wherein the TXT resource record indicates information about a geofence.

### Claim 4 (depends on 1)

The method of claim 1, wherein matching the IPv6 address to the at least one geofence anchor point comprises using the IPv6 address as a database key and querying a geofence database with data stored thereon for IPv6 addresses, anchor points for geofences, and coordinate points for geofences.

### Claim 5 (depends on 1)

The method of claim 1, wherein the at least one geofence anchor point and the fence points are displayed via an interactive map on a Graphical User Interface (GUI).

### Claim 6 (depends on 1)

The method of claim 1, further comprising filtering the at least one geofence anchor point by at least one class of the at least one geofence.

### Claim 7 (depends on 1)

The method of claim 1, further comprising a fencing agent on the device determining the geographic location of the device and generating the DNS query.

### Claim 8

A system for a geofence delivery network, comprising:
at least one geofence database with at least one geofence; and
at least one server comprising a processor, a memory, and a search engine;
wherein each geofence is defined by an anchor point;
wherein the search engine is configured to receive a Domain Name System (DNS) query via a network, wherein the DNS query includes an Internet Protocol version 6 (IPv6) address;
wherein the search engine is further configured to query the at least one geofence database to identify one or more anchor points corresponding to the IPv6 address;
wherein the server is operable to construct and send a DNS response including the identified one or more anchor points;
wherein the search engine is further configured to query the at least one geofence database and identify corresponding fence points; and
wherein the search engine is operable to construct and send a secondary DNS response including the corresponding fence points.

### Claim 9 (depends on 8)

The system of claim 8, further comprising a Graphical User Interface (GUI), wherein the GUI is configured to receive a request and display a response.

### Claim 10 (depends on 9)

The system of claim 9, wherein the GUI comprises an interactive map showing the one or more identified anchor points and the corresponding fence points.

### Claim 11 (depends on 8)

The system of claim 8, wherein the DNS response and the secondary DNS response each include a text (TXT) resource record.

### Claim 12 (depends on 8)

The system of claim 8, wherein the at least one geofence database includes an indication of at least one entitlement of the at least one geofence.

### Claim 13 (depends on 8)

The system of claim 8, wherein the at least one geofence is non-centroidal.

### Claim 14 (depends on 8)

The system of claim 8, wherein the at least one geofence is a three-dimensional geofence.

### Claim 15 (depends on 8)

The system of claim 8, wherein the identified one or more anchor points are one or more IPv6 addresses, wherein the one or more IPv6 addresses indicate a network, location, and metadata corresponding to the at least one geofence.

### Claim 16

A method for delivering geofence information by one or more processors, comprising:
receiving a first Domain Name System (DNS) request from at least one computing device over a network, wherein the DNS request includes an Internet Protocol version 6 (IPv6) address;
matching the IPv6 address to at least one geofence anchor point in a database, wherein the at least one geofence anchor point includes at least one rule for at least one geofence;
constructing a DNS response to the DNS request, wherein the DNS response includes the at least one geofence anchor point;
receiving a second DNS request from the at least one computing device over the network, wherein the second DNS request includes one of the at least one geofence anchor point;
matching the one of the at least one geofence anchor point to at least one fence point in the database; and
constructing a second DNS response to the second DNS request, wherein the second DNS response includes the at least one fence point.

### Claim 17 (depends on 16)

The method of claim 16, further comprising filtering the matched at least one geofence anchor point based on a zoom level of the IPv6 address.

### Claim 18 (depends on 16)

The method of claim 16, further comprising the at least one computing device converting the at least one fence point into at least one geographic coordinate and implementing the at least one rule when the at least one computing device is within the at least one geofence.

### Claim 19 (depends on 16)

The method of claim 16, further comprising the at least one computing device determining a geographic location of the at least one computing device and converting the geographic location of the at least one computing device into the IPv6 address.

### Claim 20 (depends on 16)

The method of claim 16, wherein the at least one geofence anchor point and the at least one fence point are stored in text (TXT) resource records.
