# US 10,771,428 B2 · Geocoding with geofences > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,771,428 B2 - Document ID: US10771428B2 - Status: Granted - Kind: B2 - Application number: 16/353,781 - Filed: 2019-03-14 - Published: 2019-07-11 - Granted: 2020-09-08 - Earliest claimed: 2014-07-29 - Assignees: GeoFrenzy, Inc. - Applicants: GeoFrenzy, Inc. - Inventors: Benjamin T. Jones; Bennett Hill Branscomb - Web page: https://patentgrep.com/patent/US10771428B2 ## CPC - H04L 61/5007: Internet protocol [IP] addresses - G06F 16/22: Indexing; Data structures therefor; Storage structures - G06Q 10/063: Operations research, analysis or management - G06Q 50/167: {Closing} - 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)} - H04L 61/4511: using domain name system [DNS] - H04W 4/029: Location-based management or tracking services - H04L 2101/69: using geographic information, e.g. room number - H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## 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 ### Claim 1 A geocode delivery system, comprising: at least one device including a processor coupled with a memory, wherein the at least one device is constructed and configured for wireless communication and programmed to send a request for geofence information over a network; at least one geocode linked to the at least one geofence, wherein each of the at least one geocode is assigned an Internet Protocol (IP) address or an Internet Protocol version 6 (IPv6) address; wherein the at least one geofence includes an anchor point, wherein the anchor point is identifiable via a unique Internet Protocol (IP) address or a unique Internet Protocol version 6 (IPv6) address and wherein one of the at least one geocode is registered as the anchor point; wherein a domain name is assignable to each unique IP address or each 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 comprised of a plurality of characters, wherein the plurality of characters is translatable to a location; wherein the at least one device is operable to receive a Domain Name Service (DNS) response to the request; wherein each of the at least one geocode and the at least one geofence is assigned at least one subdomain name and/or at least one domain name; wherein a plurality of metadata are linked to the at least one geofence; wherein the plurality of metadata includes classes, entitlements, and/or lookup table identifiers, wherein the plurality of metadata are operable to be redefined via the lookup table identifiers; wherein a search engine is configured to receive the request from the at least one device over the network and identify whether a geocode is within the at least one geofence, wherein the geocode is directly translated to coordinate points through the lookup table or indirectly translated to the coordinate points through an algorithm; and 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 a user, wherein the at least one real property boundary includes the at least one geofence or the at least one geocode, wherein the at least one real property boundary is linked to the at least one geofence or is linked to the at least one geocode through the IP address or the IPv6 address associated with the at least one geocode, wherein the at least one real estate title or the at least one permission has at least one owner. ### Claim 2 (depends on 1) The system of claim 1, wherein the domain name is automatically generated in DNS and associated with the anchor point of the at least one geofence. ### Claim 3 (depends on 1) The system of claim 1, wherein the plurality of characters includes words. ### Claim 4 (depends on 1) The system of claim 1, wherein at least one of the plurality of metadata is distributed in response to forward DNS queries and/or reverse DNS queries. ### Claim 5 A geocode delivery system, comprising: at least one device including a processor coupled with a memory, wherein the at least one device is constructed and configured for wireless communication and is operable to send a request for geofence information over a network; at least one geocode linked to at least one geofence, wherein each of the at least one geocode is assigned an Internet Protocol (IP) address or an Internet Protocol version 6 (IPv6) address; wherein the at least one geofence includes an anchor point, wherein the anchor point is identifiable via a unique Internet Protocol (IP) address or a unique Internet Protocol version 6 (IPv6) address and wherein one of the at least one geocode is registered as the anchor point; wherein a unique domain name is assignable to the unique IP address or the unique IPv6 address for the anchor point of the at least one geofence; wherein the domain name is automatically generated and registered with the anchor point of the at least one geofence; wherein the domain name is comprised of a plurality of characters, wherein the plurality of characters is translatable to a geographic designator; wherein the at least one device is operable to receive a Domain Name Service (DNS) response to the request; wherein a plurality of metadata are linked to the anchor point of the at least one geofence; wherein the plurality of metadata includes classes, entitlements, and/or lookup table identifiers, wherein the plurality of metadata are operable to be redefined via the lookup table identifiers; wherein a search engine is configured to receive the request from the at least one device over the network and identify whether a geocode is within the at least one geofence, wherein the geocode is directly translated to coordinate points through the lookup table or indirectly translated to the coordinate points through an algorithm; and 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 a user, wherein the at least one real property boundary includes the at least one geofence or the at least one geocode, wherein the at least one real property boundary is linked to the at least one geofence or is linked to the at least one geocode through the IP address or the IPv6 address associated with the at least one geocode, wherein the at least one real estate title or the at least one permission has at least one owner. ### Claim 6 (depends on 5) The system of claim 5, wherein the plurality of metadata includes the classes. ### Claim 7 (depends on 5) The system of claim 5, wherein the at least one geocode is stored in a DNS Resource Record which defines points for the at least one geofence referenced by the anchor point. ### Claim 8 (depends on 5) The system of claim 5, wherein the unique IP address is stored in the plurality of metadata utilizing IPv6 and DNS. ### Claim 9 (depends on 5) The system of claim 5, wherein at least one of the plurality of metadata is distributed in response to forward DNS queries and/or reverse DNS queries. ### Claim 10 A geocode delivery system, comprising: at least one fencing agent on at least one device including a processor coupled with a memory, wherein the at least one device is constructed and configured for wireless communication and the fencing agent is programmed to send a Domain Name Service (DNS) request for geofence information over a network; at least one unique Internet Protocol (IP) address assigned to at least one geocode, wherein the at least one unique IP address represents a point on or within a geofence; wherein the geofence includes an anchor point, wherein the anchor point is identifiable via an anchor IP address; wherein one or more of the at least one unique IP address includes a domain name, wherein the domain name is comprised of a plurality of characters, and wherein the plurality of characters is translatable to a geographic designator; wherein the at least one fencing agent is operable to receive a Domain Name Service (DNS) response to the DNS request; wherein each of the at least one geocode and the at least one geofence is assigned at least one subdomain name and/or at least one domain name; wherein a plurality of metadata are linked to the anchor point; wherein the plurality of metadata includes classes, entitlements, and/or lookup table identifiers, wherein the plurality of metadata are operable to be redefined via the lookup table identifiers; wherein a search engine is configured to receive the DNS request from the at least one device over the network and identify whether a geocode is within the at least one geofence, wherein the geocode is directly translated to coordinate points through the lookup table or indirectly translated to the coordinate points through an algorithm; and 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 a user, wherein the at least one real property boundary includes the at least one geofence or the at least one geocode, wherein the at least one real property boundary is linked to the at least one geofence or is linked to the at least one geocode through the IP address or the IPv6 address associated with the at least one geocode, wherein the at least one real estate title or the at least one permission has at least one owner. ### Claim 11 (depends on 10) The system of claim 10, wherein the at least one geocode is mobile, wherein the at least one mobile geocode is encoded as an IP address for the at least one device, wherein the at least one device is mobile, and wherein the at least one geocode is updated in real-time based on a location of the at least one device. ### Claim 12 (depends on 10) The system of claim 10, wherein the fencing agent implements a network protocol enabling the at least one device to be addressable through the anchor point. ### Claim 13 (depends on 10) The system of claim 10, 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. ### Claim 14 (depends on 10) The system of claim 10, wherein the plurality of metadata includes the entitlements and the lookup table identifiers. ### Claim 15 (depends on 10) The system of claim 10, wherein at least one of the plurality of metadata is distributed in response to forward DNS queries and/or reverse DNS queries. ### Claim 16 (depends on 10) The system of claim 10, wherein the domain name is automatically generated in DNS and registered with the anchor point of the at least one geofence.