# US 2021/0243551 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 2021/0243551 A1 - Document ID: US20210243551A1 - Status: Published application - Kind: A1 - Application number: 17/236,495 - Filed: 2021-04-21 - Published: 2021-08-05 - Earliest claimed: 2015-06-02 - Assignees: GeoFrenzy, Inc. - Applicants: GeoFrenzy, Inc. - Inventors: Benjamin T. Jones - Web page: https://patentgrep.com/patent/US20210243551A1 ## CPC - H04W 4/021: Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences - G06F 16/29: Geographical information databases - G06F 21/604: {Tools and structures for managing or administering access control systems} - G08B 13/00: Burglar, theft or intruder alarms - G08G 5/55: for a single aircraft - G08G 5/57: for unmanned aircraft - G08G 5/59: in accordance with predefined flight zones, e.g. to avoid prohibited zones - 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)} - H04L 61/5007: Internet protocol [IP] addresses - H04L 67/563: Data redirection of data network streams - H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching - H04W 12/08: Access security - G08G 5/53: for cruising - G08G 5/54: for approach or landing - H04L 61/4511: using domain name system [DNS] - 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} - H04L 2101/659: Internet protocol version 6 [IPv6] addresses - 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] - H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G08B: SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS - G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93}) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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 ### Claim 1 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) resolver; wherein the DNS resolver determines an Internet Protocol (IP) address associated with a geographic location; wherein the at least one device receives geofence information from the DNS resolver; wherein the at least one device translates the geofence information into a fence geometry; and wherein the geofence information includes at least one anchor point with at least one anchor point IP address and an identification of the at least one geofence. ### Claim 2 (depends on 1) The system of claim 1, wherein the DNS resolver determines the at least one anchor point IP address upon the at least one device entering the at least one geofence. ### Claim 3 (depends on 1) The system of claim 1, wherein the at least one anchor point IP address is determined based on the IP address associated with the geographic location. ### Claim 4 (depends on 1) The system of claim 1, wherein the geofence information includes metes and bounds of the at least one geofence. ### Claim 5 (depends on 1) The system of claim 1, wherein the at least one device populates a cache with the geofence information. ### Claim 6 (depends on 1) The system of claim 1, wherein the DNS resolver determines the at least one anchor point IP address using a local cache. ### Claim 7 (depends on 1) The system of claim 1, wherein the fence geometry is defined centroidally or noncentroidally. ### Claim 8 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; the at least one device translating the geofence information into a fence geometry; and wherein the geofence information includes at least one anchor point with at least one anchor point IP address and an identification of the at least one geofence. ### Claim 9 (depends on 8) The method of claim 8, 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 physical proximity of the geographic location. ### Claim 10 (depends on 8) The method of claim 8, wherein the fence geometry is defined centroidally or noncentroidally. ### Claim 11 (depends on 8) The method of claim 8, wherein the DNS resolver retrieves the geofence information from a local cache. ### Claim 12 (depends on 8) The method of claim 8, wherein the at least one anchor point IP address is determined based on the IP address associated with a position of the at least one device. ### Claim 13 (depends on 8) The method of claim 8, wherein the geofence information includes metes and bounds of the at least one geofence. ### Claim 14 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) resolver; wherein the DNS resolver determines an Internet Protocol (IP) address associated with a geographic location; wherein the at least one device receives geofence information from the DNS resolver; wherein the at least one device translates the geofence information into a fence geometry; and wherein the geofence information includes an identification of the at least one geofence. ### Claim 15 (depends on 14) The system of claim 14, wherein the DNS resolver determines the at least one anchor point IP address upon the at least one device entering the at least one geofence. ### Claim 16 (depends on 14) The system of claim 14, wherein at least one anchor point IP address of the at least one geofence is determined based on the IP address associated with the geographic location. ### Claim 17 (depends on 14) The system of claim 14, wherein the geofence information includes metes and bounds of the at least one geofence. ### Claim 18 (depends on 14) The system of claim 14, wherein the at least one device populates a cache with the geofence information. ### Claim 19 (depends on 14) The system of claim 14, wherein the DNS resolver determines at least one anchor point IP address using a local cache. ### Claim 20 (depends on 14) The system of claim 14, wherein the fence geometry is defined centroidally or noncentroidally.