IP Library › Granted Patent US 12,621,259
Granted Patent B2
US 12,621,259 · App. 18/784,399 · Granted May 5, 2026

Intelligent domain name service (DNS) pre-cache

Inventors: Leonard Gerald Rosenbeck (Parker, CO); Stephen Christopher Opferman (Denver, CO)
Assignee: Charter Communications Operating, LLC
H04L61/4511H04L61/5007H04L65/1069
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,621,259
App. No.
18/784,399
Granted
May 5, 2026
Kind
B2
Abstract

A gateway router is provisioned with network access by a service provider computing system associated with a service provider. The service provider computing system generates a domain name service (DNS) profile for a user of the gateway router based on customer profile data associated with the user. The DNS profile includes a predicted fully qualified domain name (FQDN). During an initialization process, the gateway router receives the DNS profile from the service provider computing system and stores the DNS profile in a DNS cache. Subsequently, the gateway router obtains an internet protocol (IP) address corresponding to the predicted FQDN in the DNS profile and stores the IP address in the DNS cache. Subsequently, the gateway router implements a local area network (LAN) and establishes connection to one or more client computing devices.

Claims (70)

1 . A method, comprising:

during an initialization process of a gateway router, receiving, by the gateway router from a service provider computing system, a domain name system (DNS) profile associated with a user of the gateway router, the DNS profile comprising a predicted fully qualified domain name (FQDN), the predicted FQDN being determined based on customer profile data associated with the user;

querying, by the gateway router, a DNS service to obtain an internet protocol (IP) address corresponding to the predicted FQDN; and

storing, by the gateway router, the IP address corresponding to the predicted FQDN in a DNS cache of the gateway router.

2 . The method of claim 1 , wherein the DNS profile is received prior to the gateway router establishing a connection to any client computing device.

3 . The method of claim 1 , wherein receiving the DNS profile associated with the user comprises:

during the initialization process, obtaining, by the gateway router from the service provider computing system, an IP address for the gateway router;

connecting, by the gateway router, to a service provider network associated with the service provider computing system; and

obtaining, by the gateway router, the DNS profile associated with the user.

4 . The method of claim 1 , wherein querying the DNS service to obtain the IP address corresponding to the predicted FQDN comprises:

in response to receiving the DNS profile associated with the user, providing, by the gateway router to a DNS server of the service provider computing system, a DNS lookup request for the predicted FQDN; and

subsequent to providing the DNS lookup request, receiving, by the gateway router from the DNS server, the IP address corresponding to the predicted FQDN.

5 . The method of claim 1 , further comprising:

subsequent to storing the IP address corresponding to the predicted FQDN in the DNS cache, implementing, by the gateway router, a local area network (LAN); and

facilitating, by the gateway router, a connection between a client computing device on the LAN and a wide area network (WAN),

wherein the client computing device is associated with the user.

6 . The method of claim 5 , further comprising:

subsequent to implementing the LAN, receiving, by the gateway router from the client computing device, a resource request associated with a web-browsing transaction initiated by the user, the resource request comprising a uniform resource locator (URL) address;

determining, by the gateway router, the URL address corresponds to the IP address corresponding to the predicted FQDN that is stored in the DNS cache of the gateway router; and

providing, by the gateway router to the client computing device, an IP address corresponding to the URL address to resolve the web-browsing transaction without querying the DNS service.

7 . The method of claim 5 , further comprising:

subsequent to implementing the LAN, receiving, by the gateway router from the client computing device, a resource request associated with a web-browsing transaction initiated by the user, the resource request comprising a uniform resource locator (URL) address;

determining, by the gateway router, the URL address does not correspond to the IP address corresponding to the predicted FQDN that is stored in the DNS cache of the gateway router;

querying, by the gateway router, the DNS service to obtain an IP address corresponding to the URL address; and

providing, by the gateway router to the client computing device, the IP address corresponding to the URL address to resolve the web-browsing transaction.

8 . The method of claim 7 , further comprising:

storing, by the gateway router, a FQDN associated with the URL address in the DNS cache; and

subsequent to storing the FQDN associated with the URL address in the DNS cache, providing, by the gateway router, feedback data to the service provider computing system, the feedback data comprising the FQDN associated with the URL address.

9 . The method of claim 1 , wherein the DNS profile associated with the user comprises a plurality of predicted FQDNs.

10 . A gateway router, comprising:

a memory; and

one or more processors operable to:

during an initialization process, receive, from a service provider computing system, a domain name system (DNS) profile associated with a user of the gateway router, the DNS profile comprising a predicted fully qualified domain name (FQDN), the predicted FQDN being determined based on customer profile data associated with the user;

query a DNS service to obtain an internet protocol (IP) address corresponding to the predicted FQDN; and

store the IP address corresponding to the predicted FQDN in the memory.

11 . The gateway router of claim 10 , wherein the gateway router is operable to provide layer 3 connectivity to a client computing device operating on a local area network (LAN) implemented by the gateway router.

12 . The gateway router of claim 11 , wherein the one or more processors are further operable to:

subsequent to storing the IP address corresponding to the predicted FQDN in the memory, receive, from the client computing device, a resource request associated with a web-browsing transaction initiated by the user, the resource request comprising a uniform resource locator (URL) address;

determine the URL address corresponds to the IP address corresponding to the predicted FQDN that is stored in the memory; and

provide, to the client computing device, an IP address corresponding to the URL address to resolve the web-browsing transaction without querying the DNS service.

13 . The gateway router of claim 11 , wherein the one or more processors are further operable to:

subsequent to storing the IP address corresponding to the predicted FQDN in the memory, receive, from the client computing device, a resource request associated with a web-browsing transaction initiated by the user, the resource request comprising a uniform resource locator (URL) address;

determine the URL address does not correspond to the IP address corresponding to the predicted FQDN that is stored in the memory;

query the DNS service to obtain an IP address corresponding to the URL address; and

provide, to the client computing device, the IP address corresponding to the URL address to resolve the web-browsing transaction.

14 . The gateway router of claim 10 , wherein the DNS profile associated with the user comprises a plurality of predicted FQDNs.

15 . A method, comprising:

provisioning, by a service provider computing system comprising one or more computing devices, a gateway router associated with a user;

determining, by the service provider computing system, a domain name system (DNS) profile for the user associated with the gateway router based on customer profile data associated with the user, the DNS profile comprising a predicted fully qualified domain name (FQDN); and

providing, by the service provider computing system, the DNS profile to the gateway router.

16 . The method of claim 15 , wherein determining the DNS profile for the user comprises:

providing, by the service provider computing system, the customer profile data associated with the user of the gateway router to a machine-learned model of the service provider computing system;

determining, by the service provider computing system, a plurality of predicted FQDNs for the user based on an output of the machine-learned model; and

determining, by the service provider computing system, the DNS profile for the user, the DNS profile comprising the plurality of predicted FQDNs.

17 . The method of claim 15 , wherein providing the DNS profile to the gateway router comprises:

receiving, by the service provider computing system from the gateway router, a DNS profile request; and

in response to receiving the DNS profile request, providing, by the service provider computing system to the gateway router, the DNS profile for the user.

18 . The method of claim 15 , wherein the user is a first user and the gateway router is a first gateway router, and wherein determining the DNS profile for the user comprises:

determining, by the service provider computing system, the DNS profile for the first user of the first gateway router;

subsequent to determining the DNS profile for the first user, receiving, by the service provider computing system from a second gateway router, feedback data comprising a plurality of FQDNs corresponding to a plurality of web-browsing transactions initiated by a second user associated with the second gateway router;

determining, by the service provider computing system, customer profile data associated with the second user matches the customer profile data associated with the first user; and

determining, by the service provider computing system, an updated DNS profile for the first user based on the customer profile data associated with the first user and the feedback data.

19 . The method of claim 15 , further comprising:

subsequent to providing the DNS profile to the gateway router, receiving, by the service provider computing system from the gateway router, a DNS lookup request corresponding to a web-browsing transaction initiated by the user;

in response to receiving the DNS lookup request from the gateway router, providing, by the service provider computing system to the gateway router, an IP address corresponding to the DNS lookup request;

subsequent to providing the IP address corresponding to the DNS lookup request, receiving, by the service provider computing system from the gateway router, feedback data comprising a FQDN associated with the DNS lookup request; and

training, by the service provider computing system, a machine-learned model of the service provider computing system with the feedback data, the machine-learned model operable to generate DNS profiles for a plurality of users of a plurality of gateway routers associated with the service provider computing system.

20 . The method of claim 15 , wherein the customer profile data comprises one or more of:

demographic data associated with the user; or

geographic data associated with a premises serviced by the gateway router.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 25, 2024
From: ROSENBECK, LEONARD GERALD; OPFERMAN, STEPHEN CHRISTOPHER
To: CHARTER COMMUNICATIONS OPERATING, LLC
Reel/Frame 068086/0327 →
Continuity (1)
Related Publication 20260032098A1 · Jan 29, 2026
References Cited (8)
US 10484278B2 · Lopez · 2019 [cited by examiner]
US 10931561B2 · Parla · 2021 [cited by examiner]
US 11134127B2 · Lee · 2021 [cited by examiner]
US 12166831B2 · Lee · 2024 [cited by examiner]
US 20160277293A1 · Lopez · 2016 [cited by examiner]
US 20180227229A1 · Lopez · 2018 [cited by examiner]
US 20180309658A1 · Parla · 2018 [cited by examiner]
US 20200389531A1 · Lee · 2020 [cited by examiner]