# US 11,909,715 B2 · Content delivery system using embedded requestor information > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,909,715 B2 - Document ID: US11909715B2 - Status: Granted - Kind: B2 - Application number: 18/114,265 - Filed: 2023-02-26 - Published: 2023-06-29 - Granted: 2024-02-20 - Earliest claimed: 2019-12-31 - Assignees: Level 3 Communications, LLC - Applicants: Level 3 Communications, LLC - Inventors: Kevin Johns - Web page: https://patentgrep.com/patent/US11909715B2 ## CPC - H04L 61/4511: using domain name system [DNS] - H04L 67/1021: based on client or server locations - H04L 61/4552: Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories - H04L 61/5007: Internet protocol [IP] addresses - H04L 67/1001: for accessing one among a plurality of replicated servers - H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching - H04L 2101/69: using geographic information, e.g. room number - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A DNS resolution request for a hostname of a CDN is received. An edge server of the CDN may be identified, which may be associated with a subnet. The subnet is used to generate a response IP address, where the remaining bits of the response IP address may be used to store requestor information (e.g., a requestor IP address). When a client computing device uses the response IP address to access the edge server, requestor information is extracted and associated with client computing device information (e.g., an IP address and/or location, etc.) in an association record. Association records may be used to determine predicted characteristics for devices served by a requestor. When the authoritative DNS server resolves a request from the requestor, such predicted characteristics may be used rather than relying solely on information about a requestor. Thus, an edge server proximate to the predicted location may be returned instead. ## Claims ### Claim 1 A system comprising: at least one processor; and memory, operatively connected to the at least one processor and storing instructions that, when executed by the at least one processor, cause the system to perform a set of operations, the set of operations comprising: receiving a request to resolve a hostname of a content distribution network (CDN), the request comprising a source Internet Protocol (IP) address of a requestor; determining an edge server of the CDN, wherein the edge server is associated with an IP address subnet; generating, based on the IP address subnet of the edge server, a response IP address comprising requestor information, the requestor information comprising an indication of the source IP address of the requestor; and providing a response to the request to resolve the hostname, wherein a payload of the response comprises the generated response IP address. ### Claim 2 (depends on 1) The system of claim 1, wherein: the generated response IP address is an IPv6 address; the source IP address of the requestor is an IPv4 address; and the indication of the source IP address is a full representation of the IPv4 address. ### Claim 3 (depends on 1) The system of claim 1, wherein: the generated response IP address is an IPv6 address; the source IP address of the requestor is an IPv6 address; and the indication of the source IP address is a subset of bits of the IPv6 address of the source IP address. ### Claim 4 (depends on 1) The system of claim 1, wherein the IP address subnet of the edge server is in a most significant set of bits of the generated response IP address and the requestor information is in a least significant set of bits of the generated response IP address. ### Claim 5 (depends on 1) The system of claim 1, wherein the requestor is an intermediate Domain Name System (DNS) server. ### Claim 6 (depends on 1) The system of claim 1, wherein determining the edge server of the CDN comprises evaluating a location associated with the requestor. ### Claim 7 A method for embedding requestor information in a Domain Name System (DNS) resolution request, the method comprising: receiving a request to resolve a hostname of a content distribution network (CDN), the request comprising a source Internet Protocol (IP) address of a requestor; determining an edge server of the CDN, wherein the edge server is associated with an IP address subnet; generating, based on the IP address subnet of the edge server, a response IP address comprising requestor information, the requestor information comprising an indication of the source IP address of the requestor; and providing a response to the request to resolve the hostname, wherein a payload of the response comprises the generated response IP address. ### Claim 8 (depends on 7) The method of claim 7, wherein: the generated response IP address is an IPv6 address; the source IP address of the requestor is an IPv4 address; and the indication of the source IP address is a full representation of the IPv4 address. ### Claim 9 (depends on 7) The method of claim 7, wherein: the generated response IP address is an IPv6 address; the source IP address of the requestor is an IPv6 address; and the indication of the source IP address is a subset of bits of the IPv6 address of the source IP address. ### Claim 10 (depends on 7) The method of claim 7, wherein the IP address subnet of the edge server is in a most significant set of bits of the generated response IP address and the requestor information is in a least significant set of bits of the generated response IP address. ### Claim 11 (depends on 7) The method of claim 7, wherein the requestor is an intermediate Domain Name System (DNS) server. ### Claim 12 (depends on 7) The method of claim 7, wherein determining the edge server of the CDN comprises evaluating a location associated with the requestor.