# US 11,121,936 B2 · Rendezvous optimization in a content delivery framework > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,121,936 B2 - Document ID: US11121936B2 - Status: Granted - Kind: B2 - Application number: 16/202,589 - Filed: 2018-11-28 - Published: 2019-04-11 - Granted: 2021-09-14 - Earliest claimed: 2012-12-13 - Assignees: Level 3 Communications, LLC - Applicants: Level 3 Communications, LLC - Inventors: Laurence R. Lipstone; William Crowder; Andrew Swart; Christopher Newton; Lewis Robert Varney - Web page: https://patentgrep.com/patent/US11121936B2 ## CPC - H04L 41/509: {wherein the managed service relates to media content delivery, e.g. audio, video or TV} - G06F 9/5055: {considering software capabilities, i.e. software resources associated or available to the machine} - G06F 15/173: using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake - G06F 15/177: Initialisation or configuration control {(processor initialisation G06F9/4405)} - H04L 41/0816: the condition being an adaptation, e.g. in response to network events - H04L 41/0823: characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability (for optimising operational conditions of wireless networks H04W24/02) - H04L 41/0869: Validating the configuration within one network element - H04L 41/12: Discovery or management of network topologies - H04L 41/50: Network service management, e.g. ensuring proper service fulfilment according to agreements - H04L 41/5041: characterised by the time relationship between creation and deployment of a service - H04L 43/04: Processing captured monitoring data, e.g. for logfile generation - H04L 47/83: based on usage prediction - H04L 61/10: of different types - H04L 61/2503: Translation of Internet protocol [IP] addresses - H04L 65/403: Arrangements for multi-party communication, e.g. for conferences (data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15) - H04L 65/60: Network streaming of media packets - H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP] - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/1078: {Resource delivery mechanisms} - H04L 67/2885: Hierarchically arranged intermediate devices, e.g. for hierarchical caching - H04L 67/289: Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network - H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services - H04L 67/55: Push-based network services - H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching - H04L 67/5682: Policies or rules for updating, deleting or replacing the stored data - H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) - H04L 69/03: {Protocol definition or specification (protocol conformance testing H04L1/244)} - G06F 9/5083: {Techniques for rebalancing the load in a distributed system} - G06F 12/0808: with cache invalidating means (G06F12/0815 takes precedence) - H04L 41/0813: characterised by the conditions triggering a change of settings - H04L 43/08: Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters - H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route - H04L 61/4511: using domain name system [DNS] - H04L 61/4535: using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers - H04L 61/58: Caching of addresses or names - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A computer-implemented method in a content delivery (CD) network includes determining at least one pseudo client IP address using first log information and second log information. The first log information being from a rendezvous service in the content delivery (CD) network, and includes at least one resolver IP address associated with at least one first request made at the rendezvous service. The second log information is from at least one probe service in the CD network, and includes at least one client IP address associated with at least one second request to the at least one probe service. The method also includes making an association between (i) the at least one pseudo client IP address and (ii) the at least one resolver IP address; and then, responsive to a name resolution request, the name resolution request including the at least one resolver IP address, the rendezvous service using the at least one pseudo client IP address instead of the resolver IP address to resolve the name. ## Claims ### Claim 1 A computer-implemented method in a content delivery (CD) network, the method comprising: (A) determining at least one pseudo client IP address using first log information and second log information, said first log information being from a rendezvous service in said content delivery (CD) network, said first log information including at least one resolver IP address associated with at least one first request made at said rendezvous service, and said second log information being from at least one probe service in said CD network, said second log information including at least one client IP address associated with at least one second request to said at least one probe service; and (B) making an association between (i) said at least one pseudo client IP address and (ii) said at least one resolver IP address; and then, (C) responsive to a name resolution request, said name resolution request including said at least one resolver IP address, said rendezvous service using said at least one pseudo client IP address instead of said resolver IP address to resolve said name, wherein said name resolution request is associated with a client, and wherein said pseudo client IP address is distinct from (i) said at least one resolver IP address, and (ii) an actual client IP address of said client. ### Claim 2 (depends on 1) The method of claim 1, wherein said first log information also includes a first at least one name, and wherein said second log information also includes a second at least one name, and wherein said determining in (A) uses said first at least one name and said second at least one name to determine said at least one pseudo client IP address. ### Claim 3 (depends on 2) The method of claim 2, wherein said association in (B) associates a particular pseudo client IP address per name. ### Claim 4 (depends on 3) The method of claim 3, wherein said at least one pseudo client IP address is based, at least in part, on a number of requests associated with a name within a time interval. ### Claim 5 (depends on 2) The method of claim 2, wherein said first at least one name comprises a first at least one property name, and wherein said second at least one name comprises a second at least one property name. ### Claim 6 (depends on 5) The method of claim 5, wherein said association in (B) associates a particular pseudo client IP address per property name. ### Claim 7 (depends on 1) The method of claim 1, wherein said association in (C) associates a particular pseudo client IP address with a particular resolver IP address. ### Claim 8 (depends on 1) The method of claim 1, wherein said association in (C) associates a particular pseudo client IP address with multiple property names. ### Claim 9 (depends on 8) The method of claim 8, wherein said particular pseudo client IP address is global for all properties. ### Claim 10 (depends on 1) The method of claim 1, wherein said at least one first request made at said rendezvous service comprises multiple first requests made at said rendezvous service. ### Claim 11 (depends on 10) The method of claim 10, wherein said multiple first requests were made from multiple clients. ### Claim 12 (depends on 1) The method of claim 1, wherein said at least one second request comprises multiple second requests to said at least one probe service. ### Claim 13 (depends on 12) The method of claim 12, wherein said multiple second requests were made to multiple probe services. ### Claim 14 (depends on 1) The method of claim 1, wherein said first log information includes first times associated with said at least one first request made at said rendezvous service, and wherein said second log information includes second times associated with said at least one second request to said at least one probe service, and wherein said determining in (A) is based, at least in part, on said first times and said second times. ### Claim 15 (depends on 1) The method of claim 1, further comprising: updating said association based on updated first log information and/or second log information. ### Claim 16 (depends on 1) The method of claim 1, wherein, for at least some requests of said at least one second request, said at least one probe service responds to or redirects said at least some requests. ### Claim 17 (depends on 1) The method of claim 1, wherein said at least one probe service comprises at least one cache service. ### Claim 18 An article of manufacture, comprising non-transitory computer-readable media having computer-readable instructions stored thereon, the computer-readable instructions including instructions for implementing a computer-implemented method, said method operable on a device comprising hardware including memory and at least one processor and running a content delivery (CD) service on said hardware, said method operable in a CD network, said method comprising: (A) determining at least one pseudo client IP address using first log information and second log information, said first log information being from a rendezvous service in said content delivery (CD) network, said first log information including at least one resolver IP address associated with at least one first request made at said rendezvous service, and said second log information being from at least one probe service in said CD network, said second log information including at least one client IP address associated with at least one second request to said at least one probe service; and (B) making an association between (i) said at least one pseudo client IP address and (ii) said at least one resolver IP address; and then, (C) responsive to a name resolution request, said name resolution request including said at least one resolver IP address, said rendezvous service using said at least one pseudo client IP address instead of said resolver IP address to resolve said name, wherein said name resolution request is associated with a client, and wherein said pseudo client IP address is distinct from (i) said at least one resolver IP address, and (ii) an actual client IP address of said client. ### Claim 19 A device, in a content delivery (CD) network, said device comprising: (a) hardware including memory and at least one processor, and (b) a CD service running on said hardware, wherein said CD service: (A) determines at least one pseudo client IP address using first log information and second log information, said first log information being from a rendezvous service in said content delivery (CD) network, said first log information including at least one resolver IP address associated with at least one first request made at said rendezvous service, and said second log information being from at least one probe service in said CD network, said second log information including at least one client IP address associated with at least one second request to said at least one probe service; and (B) makes an association between (i) said at least one pseudo client IP address and (ii) said at least one resolver IP address; and then, (C) responsive to a name resolution request, said name resolution request including said at least one resolver IP address, use said at least one pseudo client IP address instead of said resolver IP address to resolve said name, wherein said name resolution request is associated with a client, and wherein said pseudo client IP address is distinct from (i) said at least one resolver IP address, and (ii) an actual client IP address of said client. ### Claim 20 (depends on 1) The method of claim 1, wherein the pseudo client IP address is an approximation of a location of the client.