Communicating private data and data objects
US-2016380986-A1 · Dec 29, 2016 · US
US11824829B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11824829-B2 |
| Application number | US-202217882414-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 5, 2022 |
| Priority date | Jul 17, 2015 |
| Publication date | Nov 21, 2023 |
| Grant date | Nov 21, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems, devices and methods for a Domain Name Data Networking (DNDN) content delivery system are disclosed. Embodiments perform operations including obtaining a content object having a unique identifier. The operations also include storing a local instance of the content object in association with DNS resource records and the unique identifier. The operations further include providing the local instance of the content to a client in response to receiving a request from the client including the unique identifier.
Opening claim text (preview).
What is claimed is: 1. A Domain Name System (DNS) server comprising: a processor; a data storage device including: a DNS resource record store that stores DNS resource records for resolving DNS queries, and a DNS content cache that stores one or more instances of content objects; and program instructions stored on the data storage device that, when executed by the processor, control the DNS server to perform operations comprising: obtaining a content object having a unique identifier; translating the content object into at least one DNS-compatible record by segmenting the content object into one or more DNS-compatible resource records associated with the unique identifier; storing, in the DNS content cache, the DNS-compatible resource records associated with the unique identifier; receiving, from a client device, a content request that includes the unique identifier; determining, based on the unique identifier received in the content request, one or more DNS-compatible resource records associated with the unique identifier; based on the one or more DNS-compatible resource records, determining a storage location of an instance of the content object in the DNS content cache; and providing, to the client device from the DNS content cache, the instance of the content object. 2. The DNS server of claim 1 , wherein the content object is comprised of N bytes, the segmenting comprising segmenting the content object into a number X of DNS-compatible resource records, each of which includes a resource record type, a length, and an N/X byte segment of the content object. 3. The DNS server of claim 2 , wherein providing the instance of the content object comprises retranslating the DNS-compatible resource records back into the content object. 4. The DNS server of claim 1 , wherein the content object is a DNS record. 5. The DNS server of claim 1 , wherein the content object is stored using an existing DNS record type. 6. The DNS server of claim 5 , wherein the existing DNS record type is a TXT record type that supports transporting opportunistic encryption material, sender policy framework material, and DNS service discovery material. 7. The DNS server of claim 1 , wherein the one or more DNS-compatible resource records comprise a pointer to the storage location of the instance of the content object in the DNS content cache. 8. The DNS server of claim 1 , wherein the unique identifier comprises a domain name, and wherein the content object comprises a resource record type. 9. A method comprising: obtaining a content object having a unique identifier; translating the content object into a Domain Name Service (DNS)-compatible record by segmenting the content object into DNS-compatible resource records associated with the unique identifier; storing the DNS-compatible resource records associated with the unique identifier in a DNS content cache; receiving a content request that includes the unique identifier; determining, based on the unique identifier received in the content request, one or more DNS-compatible resource records associated with the unique identifier; based on the one or more DNS-compatible resource records, determining a storage location of an instance of the content object in the DNS content cache; and providing, to a client device from the DNS content cache, the instance of the content object. 10. The method of claim 9 , wherein the content object is comprised of N bytes, the segmenting comprising segmenting the content object into a number X of DNS-compatible resource records, each of which includes a resource record type, a length, and an N/X byte segment of the content object. 11. The method of claim 10 , wherein providing the instance of the content object comprises retranslating the DNS-compatible resource records back into the content object. 12. The method of claim 9 , wherein the content object is a DNS record. 13. The method of claim 9 , wherein the content object is stored using an existing DNS record type. 14. The method of claim 13 , wherein the existing DNS record type is a TXT record type that supports transporting opportunistic encryption material, sender policy framework material, and DNS service discovery material. 15. The method of claim 9 , wherein the one or more DNS-compatible resource records comprise a pointer to the storage location of the instance of the content object in the DNS content cache. 16. A method comprising: receiving, at a local Domain Name Service (DNS) server in a domain name data networking (DNDN) system, a request from a client; determining whether the request is a domain name request or a content request; responsive to determining that the request is the content request, determining whether a local instance of a content object is cached at the local DNS server in the DNDN system; responsive to determining that the local instance of the content object is cached at the local DNS server in the DNDN system, determining whether the local instance of the content object is expired; and responsive to determining that no local instance of the content object is cached at the local DNS server in the DNDN system or responsive to determining that the local instance of the content object cached at the local DNS server in the DNDN system is expired: obtaining an instance of the content object from a remote DNS server in the DNDN system, storing the instance as the local instance of the content object at the local DNS server in the DNDN system in associated with one or more DNS resource records and a unique identifier, and providing the local instance of the content object to the client from the local DNS server of the DNDN system. 17. The method of claim 16 , further comprising, responsive determining that the local instance of the content object is not expired, providing the local instance of the content object to the client from the local DNS server. 18. The method of claim 16 , further comprising, prior to receiving the request from the client: translating the content object into a DNS-compatible record by segmenting the content object into DNS-compatible resource records associated with the unique identifier; and storing the DNS-compatible resource records associated with the unique identifier in a DNS content cache of the local DNS server in the DNDN system. 19. The method of claim 18 , wherein providing the local instance of the content object to the client from the local DNS server comprises retranslating the DNS-compatible resource records back into the content object. 20. The method of claim 16 , further comprising, responsive to determining that the request is the domain name request, providing an internet protocol (IP) address to the client from the local DNS server of the DNDN system.
using domain name system [DNS] · CPC title
Caching of addresses or names · CPC title
Storing data temporarily at an intermediate stage, e.g. caching · CPC title
the source of the received data · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.