IP Library › Granted Patent US 12,299,012
Granted Patent B2
US 12,299,012 · App. 18/109,777 · Granted May 13, 2025

System and method for location domain name service

Inventors: Xander van der Heijden (Singapore, SG); Emre Turan (Amsterdam, NL); Bulent Ozel (Bloemendaal, NL)
Assignee: UNL Network B.V.
G06F16/29G06F16/2255G06F16/2379G06F16/26G06F16/282H04L61/00H04L61/103H04L61/3025
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,299,012
App. No.
18/109,777
Granted
May 13, 2025
Kind
B2
Abstract

Clusters of locations on a geographic grid are mapped into human-friendly domain names wherein the location hierarchy is represented by a subdomain hierarchy. The resolver of the so-called location domain name service (LDNS) maps the domain name to a unique identifier of the cluster that is used as a pointer to a plurality of geohashes that are highly compressed according to a method of the present invention. Each cluster's domain name is associated with location-based static and temporal data that represent some aspect of the corresponding location including location-associated crypto economy components. An embodiment of the system of the present invention LDNS implemented on a blockchain system. Furthermore, location-oriented top-level domain categories, that enable quick data searching, are created with templatized smart contracts. Mapping a list that has long alphanumeric strings to a unique human-friendly domain name further allows definition of ownership rights for the corresponding location data.

Claims (36)

1. A system comprising:

a processor;

storage storing computer readable programmable code executable by the processor to maintain a hierarchical and human-friendly naming structure for locations on an electronic map wherein a location cluster is identified by a group of pixels, each pixel being represented by a geo-hash, the storage comprising:

(a) computer readable program code: (1) storing a unique first domain name, wherein a first location cluster on a map is identified by a group of adjacent pixels that is named using the unique first domain name, (2) storing a unique first sub-domain name, wherein a first sub-group of pixels within the group of adjacent pixels in the first location cluster is named using a unique first sub-domain name, the unique first sub-domain name comprising a concatenation of the following: the unique first domain name, a first special character, and a first, unique name portion, and (3) maintaining a first mapping of the first domain name and first sub-domain name to a first list of geo-hashes corresponding to the group of adjacent pixels and the sub-group of pixels within the group of adjacent pixel; and

(b) computer readable program code: (1) storing a unique second domain name, wherein a second location cluster on the map is identified by a plurality of non-adjacent pixel groups that is named using the unique second domain name, (2) storing a unique second sub-domain name for each non-adjacent pixel group, wherein each of the plurality of non-adjacent pixel groups are named using a unique second sub-domain-name, the second sub-domain name comprising a concatenation of the following: the unique second domain name, a second special character, and a second, unique, name portion, and (3) maintaining a second mapping of the unique second domain name and unique second sub-domain name to a second list of geo-hashes corresponding to the pixels of the plurality of non-adjacent pixel groups and the non-adjacent pixel group.

2. The system of claim 1 , wherein the special character is picked from any of the following: ‘.’, ‘-’, ‘;’ and ‘:’.

3. The system of claim 1 , wherein the storage implements a location domain name service (LDNS) database to hierarchically store domain names, sub-domain names, and mappings between such names and corresponding clusters on the map.

4. The system of claim 3 , wherein the LDNS stores a first and second geo-hash lists using a compression method of: (a) aggregating pixels in a given cluster to a highest possible geo-pixel level to store only a hash of that geo-pixel; and (b) if a given group of pixels in the given cluster cannot be aggregated into a higher-level geo-pixel, then store once a hash of the higher-level geo-hash, and for each pixel in the given group of pixels, store only an alphanumeric extension to the hash of a higher level geo-hash to derive pixel geohash.

5. The system of claim 4 , wherein uniqueness of domain names is ensured by recording a transaction of mapping a given domain name to a given cluster on a blockchain that verifies uniqueness.

6. The system of claim 5 , wherein each blockchain record comprises: a unique cluster ID that is a pointer to a corresponding LDNS record in a separate file sharing system that contains mapping of unique cluster IDs to a list of geo-hashes or compressed geo-hashes.

7. The system of claim 6 , wherein the file sharing system is any of the following:

Interplanetary File System (IPFS), Keybase or ZeroNet.

8. The system of claim 1 , wherein uniqueness of sub-domain names is further provided by a smart contract stored within a blockchain associated with their corresponding domain name.

9. The system of claim 1 , wherein each domain name has an associated smart contract that all underlying sub-domains must comply with.

10. An article of manufacture having a non-transitory computer readable storage medium comprising computer readable program code executable by a processor, the non-transitory computer readable storage medium comprising:

(a) computer readable program code maintaining a hierarchical and human-friendly naming structure for locations on an electronic map wherein a location cluster is identified by a group of pixels, each pixel being represented by a geo-hash

(b) computer readable program code storing a unique first domain name, wherein a first location cluster on a map is identified by a group of adjacent pixels that is named using the unique first domain name;

(c) computer readable program code storing a unique first sub-domain name, wherein a first sub-group of pixels within the group of adjacent pixels in the first location cluster is named using a unique first sub-domain name, the first unique sub-domain name comprising a concatenation of the following: the first unique domain name, a first special character, and a first, unique name portion;

(d) computer readable program code maintaining a first mapping of the first unique domain name and first sub-domain name to a first list of geo-hashes corresponding to the group of adjacent pixels and the sub-group of pixels within the group of adjacent pixel; and

(e) computer readable program code storing a unique second domain name, wherein a second location cluster on the map is identified by a plurality of non-adjacent pixel groups that is named using the unique second domain name;

(f) computer readable program code storing a unique second sub-domain name for each non-adjacent pixel group, wherein each of the plurality of non-adjacent pixel groups are named using a unique second sub-domain-name, the second unique sub-domain name comprising a concatenation of the following: the second domain name, a second special character, and a second, unique, name portion, and

(g) computer readable program code maintaining a second mapping of the second domain name and second sub-domain name to a second list of geo-hashes corresponding to the pixels of the plurality of non-adjacent pixel groups and the non-adjacent pixel group.

11. The article of manufacture of claim 10 , wherein the special character is picked from any of the following: ‘.’, ‘-’, ‘;’ and ‘:’.

12. The article of manufacture of claim 10 , wherein the storage implements a location domain name service (LDNS) database to hierarchically store domain names, sub-domain names, and mappings between such names and corresponding clusters on the map.

13. The article of manufacture of claim 12 , wherein the LDNS stores a first and second geo-hash lists using a compression method of: (a) aggregating pixels in a given cluster to a highest possible geo-pixel level to store only a hash of that geo-pixel; and (b) if a given group of pixels in the given cluster cannot be aggregated into a higher-level geo-pixel, then store once a hash of a higher-level geo-hash, and for each pixel in the given group of pixels, store only an alphanumeric extension to the hash of a higher level geo-hash to derive pixel geohash.

14. The article of manufacture of claim 13 , wherein uniqueness of domain names is ensured by recording a transaction of mapping a given domain name to a given cluster on a blockchain that verifies uniqueness.

15. The article of manufacture of claim 14 , wherein each blockchain record comprises: a unique cluster ID that is a pointer to a corresponding LDNS record in a separate file sharing system that contains mapping of unique cluster IDs to list of geo-hashes or compressed geo-hashes.

16. The article of manufacture of claim 15 , wherein the file sharing system is any of the following: Interplanetary File System (IPFS), Keybase or ZeroNet.

17. The article of manufacture of claim 10 , wherein uniqueness of sub-domain names is further provided by a smart contract stored within a blockchain associated with their corresponding domain name.

18. The article of manufacture of claim 10 , wherein each domain name has an associated smart contract that all underlying sub-domains must comply with.

19. An article of manufacture having a non-transitory computer readable storage medium comprising computer readable program code executable by a processor, the non-transitory computer readable storage medium comprising:

(a) computer readable program code maintaining a hierarchical and human-friendly naming structure for locations on an electronic map wherein a location cluster is identified by a group of pixels, each pixel being represented by a geo-hash;

(b) computer readable program code storing a top-level domain name of a cluster on a geographic map that is identified to belong to a top-level location-domain category;

(c) computer readable program code storing a second domain name that has the top-level domain name as part of the second domain name;

(d) computer readable program code naming a smaller group of pixels within the cluster using a unique third domain-name that has the second domain-name as part of its name, and wherein the top-level domain name, the second domain name and the third domain name are concatenated by a special character, wherein the second domain name and the third domain name map to corresponding geohash list of pixels.

20. The article of manufacture of claim 19 , wherein the special character in picked from any of the following: ‘.’, ‘-’, ‘;’ and ‘:’.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2023
From: VAN DER HEIJDEN, XANDER; TURAN, EMRE; OZEL, BULENT
To: UNL NETWORK B.V.
Reel/Frame 063607/0600 →
Continuity (2)
Provisional Application 63309664 · Feb 14, 2022
Related Publication 20230267134A1 · Aug 24, 2023
References Cited (11)
US 7564377B2 · Kimchi et al. · 2009 [cited by applicant]
US 7917371B2 · Jung et al. · 2011 [cited by applicant]
US 10616179B1 · McCarriar · 2020 [cited by examiner]
US 11196573B2 · Roennow et al. · 2021 [cited by applicant]
US 20190108682A1 · Spivack et al. · 2019 [cited by applicant]
US 20200409942A1 · Kasimov · 2020 [cited by examiner]
US 20240086382A1 · Soon-Shiong · 2024 [cited by examiner]
US 20240171407A1 · Wright · 2024 [cited by examiner]
WO 2014170646A1 · 2014 [cited by applicant]
“Open Location Code Addresses for Everything, everywhere,” Google-opensource.blogspot.ch., Apr. 30, 2015, pp. 1-2. [cited by applicant]
“Domain Names—Implementation and Specification,” RFC 1035, https://www.ietf.org/rfc/rfc1035.txt, Nov. 1987, pp. 1-55. [cited by applicant]