Geocoding with geofences

• US 10,237,232 B2
• Filed: 07/13/2016
• Issued: 03/19/2019
• Est. Priority Date: 07/29/2014
• Status: Active Grant

• Current Assignee: GeoFrenzy, Inc
• Original Assignee: GeoFrenzy, Inc
• Inventors: Jones, Benjamin T., Branscomb, Bennett Hill
• Primary Examiner(s): Chea, Philip J
• Assistant Examiner(s): Chen, Wuji
• Application Number:
  US15/209,211
• Publication Number:
  US 20160323241A1
• Time in Patent Office: 979 Days
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 50/167 Closing
• 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 9/088 Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

Systems and methods of registering geocodes with a geofence and delivering geocodes which define geofences to devices are described herein. Geocodes include strings of words, letters, numbers, and combinations thereof. Geocodes associated with the same or similar geofences are cohesive and provide for improved location information.

Claims

1. A geocode delivery system, comprising:

at least one device having a graphical user interface (GUI), and a processor coupled with a memory, constructed and configured for wireless communication and programmed to include a fencing agent operable to send a request for geofence information over a network to at least one server computer associated with at least one geofence;

a plurality of geocodes linked to the at least one geofence and assigned a plurality of unique Internet Protocol (IP) addresses or a plurality of unique Internet Protocol version 6 (IPv6) addresses;

at least one geofence database, wherein the at least one geofence database stores information describing the at least one geofence;

wherein the at least one geofence includes an anchor point identified by one of the plurality of unique IP addresses or one of the plurality of unique IPv6 addresses;

a Domain Name Service (DNS), wherein a domain name is assignable to each unique IP address or unique IPv6 address for each of the plurality of geocodes and/or the anchor point of the at least one geofence;

wherein the domain name is automatically generated in DNS and registered with the anchor point of the at least one geofence;

wherein the domain name is comprised of a plurality of words, wherein the plurality of words are translatable to a geographic designator;

wherein the GUI is operable to display a DNS response to the request in real-time or near real-time;

wherein the plurality of geocodes are translatable to coordinate points of a geographic location and the IP address or the IPv6 address;

further comprising subdomain names and domain names assigned to the plurality of geocodes and the at least one geofence, wherein the domain names and/or the subdomain names dereference to the at least one geofence when one of the plurality of geocodes is registered as the anchor point; and

wherein a plurality of metadata are linked to one of the plurality of geocodes, wherein the plurality of metadata includes, classes, entitlements, and lookup table identifiers, wherein the plurality of metadata are operable to be redefined via the lookup table identifiers, wherein the plurality of metadata are distributed in response to forward DNS queries and/or reverse DNS queries.

2. The system of claim 1, further comprising a search engine configured to receive the request from the at least one device over the network and identify whether a searched geocode is within the at least one geofence, wherein the plurality of geocodes are directly translated to coordinate points through a lookup table or indirectly translated in real-time to coordinate points through a third party algorithm, and wherein the plurality of geocodes which make up the at least one geofence are application specific.

3. The system of claim 1, wherein at least one real estate title and at least one permission are linked to at least one real property boundary, wherein the at least one real property boundary is not defined by the user, wherein the at least one real property boundary includes the at least one geofence or the plurality of geocodes within the at least one geofence, wherein the at least one real property boundary is linked to the at least one geofence or is linked to the plurality of geocodes within the at least one geofence through one of the plurality of unique IP addresses or one of the plurality of unique IPv6 addresses, wherein the at least one real estate title or the at least one permission has at least one owner.

4. The system of claim 1, wherein the anchor point is an anchor geocode, wherein the anchor geocode or any of the plurality of geocodes is addressed through a plurality of subdomain names linked to the domain name, wherein the plurality of subdomain names linked to the domain name are comprised of a plurality of words, wherein the anchor geocode is associated with an IP address that relates the domain name of the geofence to the anchor point, wherein the anchor geocode dereferences to the geofence when the geofence has registered the geocode as the anchor geocode.

5. The system of claim 1, wherein the plurality of geocodes are stored as metadata utilizing IPv6 and DNS.

6. The system of claim 1, wherein the plurality of geocodes are stored in a DNS Resource Record (RR) defining as points for the at least one geofence referenced by the anchor point for the at least one geofence and/or an anchor geocode.

7. The system of claim 1, wherein the plurality of geocodes are fixed, mobile, or hybrid;

wherein the plurality of mobile geocodes are encoded as an IP address associated with a device operable for mobility;

wherein the plurality of hybrid geocodes are encoded as an IP address associated with a non-fixed device.

8. The system of claim 1, further comprising a geofence manager module;

wherein the geofence manager module implements rules on the at least one device;

wherein the geofence manager module is operable to confirm and/or activate at least one license associated with the at least one geofence in the at least one geofence database.

9. The system of claim 1, wherein the fencing agent implements a network protocol enabling the at least one device to be addressable through the plurality of geocodes linked to the at least one geofence.