GEOLOCATION NAME SYSTEM

Abstract

A system and method for representing physical coordinates related to an address in machine-readable format. The disclosed invention provides a method for assigning an identifier to a set of geographical coordinates, such that said identifier may be used to share location information in lieu of a regular address (street name, city, state, etc.). The disclosed invention further allows said identifier to be correlated to additional information related to the address, such as altitude, in order to more accurately point a user to the desired location by only using the assigned identifier.

Claims

1. A method for dynamically representing an address to physical location in a computer-readable format, comprising the steps of: receiving a first address related to a subject; assigning an identifier to said first address, wherein said identifier is in machine-readable format and is related to said subject; dynamically receiving a first set of geographical coordinates related to said first address; storing said identifier and said first set of geographical coordinates in a database; correlating in said database said first set of geographical coordinates to said identifier; dynamically receiving a second set of geographical coordinates related to said subject; substituting said first set of geographical coordinates with said second set of geographical coordinates; correlating in said database said second set of geographical coordinates with said identifier and not correlating said first set of geographical coordinates to said identifier.

2. The method of claim 1, further comprising the step of receiving a request for said address and said geographical coordinates related to said identifier through an Application Programming Interface (API).

3. The method of claim 2, further comprising the step of obtaining authorization from said subject to share said address and said geographical coordinates related to said identifier.

4. The method of claim 3, further comprising the step of providing said address and said geographical coordinates related to said identifier through said API.

5. The method of claim 1, further comprising the steps of: receiving at least one piece of location information related to said subject in a machine-readable format; storing said at least one piece of information in said database; correlating in said database said at least one piece of information to said identifier.

6. The method of claim 2, further comprising the steps of: receiving at least one piece of location information related to said subject in a machine-readable format; storing said at least one piece of information in said database; correlating in said database said at least one piece of information to said identifier.

7. The method of claim 3, further comprising the steps of: receiving at least one piece of location information related to said subject in a machine-readable format; storing said at least one piece of information in said database; correlating in said database said at least one piece of information to said identifier.

8. The method of claim 1, wherein said first and second sets of geographical coordinates comprise a latitude value and longitude value.

9. The method of claim 1, wherein said identifier comprises a domain name and a location name.

10. The method of claim 5, wherein said at least one piece of location information related to said subject comprises an altitude value.

11. A system for dynamically representing an address to physical location in a computer-readable format, comprising; one or more computer processors; one or more computer readable storage devices; program instructions stored on said one or more computer readable storage devices for execution by at least one of said one or more computer processors, said stored program instructions comprising: program instructions for receiving a first address related to a subject; program instructions for assigning an identifier to said first address, wherein said identifier is in a machine-readable format and is related to said first subject; program instructions for dynamically receiving a first set of geographical coordinates related to said first address; program instructions for storing said identifier and said first set of geographical coordinates in a database; program instructions for correlating in said database said first set of geographical coordinates to said identifier; program instructions for dynamically receiving a second set of geographical coordinates related to said subject; program instructions for substituting said first set of geographical coordinates with said second set of geographical coordinates; program instructions correlating in said database said second set of geographical coordinates with said identifier and not correlating said first set of geographical coordinates to said identifier.

12. The system of claim 11, further comprising program instructions for receiving a request for said address and said geographical coordinates related to said identifier through an Application Programming Interface (API).

13. The system of claim 12, further comprising program instructions for obtaining authorization from said subject to share said address and said geographical coordinates related to said identifier.

14. The system of claim 13, further comprising program instructions for providing said address and said geographical coordinates related to said identifier through said API.

15. The system of claim 11, further comprising: program instructions for receiving at least one piece of location information related to said subject in machine-readable format; program instructions for storing said at least one piece of information in said database; program instructions for correlating in said database at least one piece of information to said identifier.

16. The system of claim 12, further comprising: program instructions for receiving at least one piece of location information related to said subject in machine-readable format; program instructions for storing said at least one piece of information in said database; program instructions for correlating in said database at least one piece of information to said identifier.

17. The system of claim 13, further comprising: program instructions for receiving at least one piece of location information related to said subject in machine-readable format; program instructions for storing said at least one piece of information in said database; program instructions for correlating in said database at least one piece of information to said identifier.

18. The system of claim 11, wherein said first and second sets of geographical coordinates comprise a latitude value and a longitude value.

19. The system of claim 15, wherein said at least one piece of location information related to said subject comprises an office number.

20. The system of claim 15, wherein said at least one piece of location information related to said subject comprises a floor number.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG. 1 shows a geo-name mapped to various grid alternatives.

[0029] FIG. 2 shows how three coordinates (latitude, longitude, and altitude) may be correlated to an Internet domain.

[0030] FIG. 3 shows how a GNS may be used as a service with various operating systems through an API.

DETAILED DESCRIPTION

[0031] To provide an overall understanding of the invention, certain illustrative embodiments and examples will now be described. However, it will be understood by one of ordinary skill in the art that the same or equivalent functions and sequences may be accomplished by different embodiments that are also intended to be encompassed within the spirit and scope of the disclosure. The compositions, apparatuses, systems and/or methods described herein may be adapted and modified as is appropriate for the application being addressed and that those described herein may be employed in other suitable applications, and that such other additions and modifications will not depart from the scope hereof.

[0032] As used in the specification and claims, the singular forms “a”, “an” and “the” include plural references unless the context clearly dictates otherwise. For example, the term “a transaction” may include a plurality of transaction unless the context clearly dictates otherwise. As used in the specification and claims, singular names or types referenced include variations within the family of said name unless the context clearly dictates otherwise.

[0033] By assigning a name to a geolocation, we can increase accuracy and ease of use. There are several benefits: [0034] Simplified use—Names are easy to say, write, and share, and their format is constant among languages. For example, although Spanish and English change the written order of physical address information, GNS names use the same format. (In the same way, email addresses are compatible among languages, especially since the adoption of Unicode). [0035] Consistent use—Organizations can easily define GNS information, improving navigation and delivery. A simple domain.com:office can be used to reach a facility. If the company moves, they can simply update the GNS's underlying data, and new deliveries are routed correctly. [0036] Automated use—Contrary to current physical addresses that have to be converted to geolocations for use with most applications, GNS names have underlying computer-friendly information. Besides the latitude/longitude the invention can also provide translations to other grid systems, such as the U.S. Military Grid, Mapcode, or what3words, for compatibility, as seen in FIG. 1. [0037] Extended use—The functionality of geo-names can be extended to other uses, for example, for assets (e.g., car, boat, bike). Assets can be named and associated to geolocations for management and tracking. [0038] Dynamic capabilities—As you refer to a name, not a fixed location, the underlying data can be dynamically updated to changing conditions (e.g., moving homes, traveling, or, in the case of assets, their current location). A geoname for an asset like user@company.com!car can use the “current” keyword to get the latest registered geolocation at user@company.com!car:current. Other keywords can be used for tracking: “starting” or “destination”. This is useful for tracking packages, equipment, and other devices in an Internet of Things (IOT) environment. [0039] Programmable use—The use of geo-names and keywords can create additional opportunities for automation. For example, programming a schedule for a bike pickup at user@company!bike:current, delivering it to your user@company!bike:mechanic for maintenance, and then sending it back to user@company!bike:home after servicing. [0040] Data layer—As see in FIG. 2, Another level of data can be added to maps that includes significant geolocations with aboveground/belowground (altitude) elevation information or indoor positioning. That information can be used to calculate population density and traffic. Foursquare uses foot traffic information to provide insights about businesses. The present invention uses data that can expand the analysis with additional supporting details, including authorized business or individual information.

[0041] In an exemplary embodiment of the present invention, geo-names can become as ubiquitous as emails or websites. You can reach a person at user@domain.com, www.domain.com, or user@domain.com:work. These are computer-friendly and precise ways to reach a person. Physical addresses vary according to countries, so a standardized method of geolocation simplifies reaching a person for anyone in the world; similar to email, once you learn the format, you can email anyone anywhere.

[0042] The expected behavior in a GNS should be: [0043] Geo-names are maintained by users—The present invention allows users to create their own geo-names. To accomplish that, already existing Internet domains or email addresses may be used to avoid trademark issues and improve security. [0044] Organizations: Organizations can create names for their locations and make them public (walgreens.com:sanjuan, walgreens.com:ponce01). [0045] Individuals: Personal geo-names are places of self-interest, such as home/work/school/parents/inlaws. Geo-names can also be used to track assets, and the underlying information can be dynamically updated. [0046] Generic services: organizations or individuals without registered domains or emails can use generic service providers to create geo-names. [0047] Privacy: There should also be a concept of private and public information. A business may want its information public and easily available, whereas individuals may want to protect information through authorizations. Privacy requires special attention as well as data management. [0048] History must be stored—Changes to data should be stored to provide context for analysis or historical references. Using the geo-name will always return the latest information, but in cases where the information refers to a historical situation, the geo-name should return the value at that time. This allows for users to know where a place has its new offices or where a historical place used to be. [0049] Refine the naming data structures—Although name, latitude, longitude, and altitude are the fundamental fields for the GNS, multiple additional fields provide additional information that may be needed to support expected future solutions, such as indoor positioning. Human-readable physical addresses, user/date audit data, and geolocation relocation information, among other fields, may be added if required to store historical, current, and future information. [0050] Storage structures and processes—The GNS stores the naming information in persistent storage. In an exemplary embodiment, the storage structure can be a relational database, NoSQL database, and/or flat files. The processes that store the information can be written in Java or Node.js or even be blockchain-based. [0051] API—As seen in FIG. 3, an API allows intercommunication between applications and is necessary for accessing, retrieving, and managing information from the GNS. The API defines the authentication/authorization process for accessing the GNS and the available procedures to interact with it. A trust relationship can be established with external applications to exchange basic information. Users have to explicitly grant permission to applications to request private data from the GNS. A simple integration from the launchpad with a leading app (e.g., Uber, Lyft, Waze) can showcase the power of geo-naming.

[0052] While the disclosure includes reference to specific embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the true spirit and scope of the disclosure. In addition, many modifications may be made without departing from the essential teachings of the disclosure. When reference is made to specific known applications or systems, it will be understood by those skilled in the art that various substitutes and alternatives may be available.