Patent Grant
11290567
The present disclosure generally relates to communications networks, and more particularly relates to content delivery networks.
Packet-switched networks, such as networks based on the TCP/IP protocol suite, can distribute a rich array of digital content to a variety of client applications. One popular application is a personal computer browser for retrieving documents over the Internet written in the Hypertext Markup Language (HTML). Frequently, these documents include embedded content. Where once the digital content consisted primarily of text and static images, digital content has grown to include audio and video content as well as dynamic content customized for an individual user.
It is often advantageous when distributing digital content across a packet-switched network to divide the duty of answering content requests among a plurality of geographically dispersed servers. For example, popular Web sites on the Internet often provide links to “mirror” sites that replicate original content at a number of geographically dispersed locations. A more recent alternative to mirroring is content distribution networks (CDNs) that dynamically redirect content requests to a cache server situated closer to the client issuing the request. CDNs either co-locate cache servers within Internet Service Providers or deploy them within their own separate networks.
It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the Figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings presented herein, in which:
The use of the same reference symbols in different drawings indicates similar or identical items.
The numerous innovative teachings of the present application will be described with particular reference to the presently preferred exemplary embodiments. However, it should be understood that this class of embodiments provides only a few examples of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present application do not necessarily limit any of the various claimed inventions. Moreover, some statements may apply to some inventive features but not to others.
The multicast server 106 can communicate with the client devices 116-130 to provide a multicast stream of content to the client devices. Similarly, each of the anycast servers 108-114 can communicate with the client devices 116-130 to provide a unicast stream of the content to the client devices. A single anycast IP address can be assigned to each of the anycast servers 108-114, such that the anycast server that is closest to a requesting client device can provide the unicast stream of content to that client device. The closest anycast server may be the anycast server having a shortest network distance, a lowest network cost, a lowest network latency, a highest link capacity, a lowest load, or any combination thereof.
The CTM server 102 can receive load information from the multicast server 106 and the anycast servers 108-114. The load information can include available bandwidth, bandwidth utilization, CPU utilization, memory utilization, number of requests being served, or the like. The multicast server 106 can advertise, such as through Border Gateway Protocol (BGP), a multicast IP address for the multicast server to the CTM server 102. Similarly, the anycast servers 108-114 can advertise a shared anycast address to the CTM server 102 via BGP. The CTM server 102 can provide either the multicast address, the anycast address, a local peer IP address, or any combination thereof as the source address for particular content and/or for error recovery to the client devices 116-130.
The multicast server 106 and the anycast servers 108-114 of the CDN 100 can provide the client devices 116-130 with different types of content, such as software files, video-on-demand files, music files, or the like. Each item of content can divided into a number of blocks. The blocks can be divided into equal sizes, and can be indexed with the order of the blocks within the content file. The structure and order of the blocks of the content file can be stored in a metadata file, which can include a file descriptor for the content file, a list of sources for the content file, and other information about the content file. The file descriptor can include file identification (ID), a number of blocks and the sequence of the blocks in the content file. The list of sources can include IP addresses for unicast sources, multicast sources, local peer sources, and the like.
During operation, the SLL server 104 can monitor current statistics for the content, such as a number of the client devices 116-130 that are receiving the content, a rate of requests for the content, and the like. The SLL server 104 can send the current statistics for the content to the CTM server 102, which in turn can create a source list 132 based on the current statistics for the content. For example, the SLL server 104 can indicate that the number of client devices 116-130 receiving the content is below a high threshold. The CTM server 102 can create the source list 132 with an anycast IP address, associated with the anycast servers 108-114, as a primary source address for the content. The anycast servers 108-114 can be unicast servers, such that each of the anycast servers can provide a different unicast address to the CTMserver 102 via BGP.
The CTM server 102 can provide the source list 132 to the SLL server 104, which in turn can include the source list 132 as part of the metadata file for the content. The SLL server 104 can then provide the metadata file associated with the content to a client device that is requesting the content. The SLL server 104 can dynamically update the metadata file, and can provide the updated metadata file to the client devices 116-130 so that the client devices can have a current list of sources for the content. The requesting client device, such as client device 118, can utilize the metadata file to determine that the anycast IP address is the source address for the content.
The client device 118 can then connect to the anycast server 108-114 that is nearest to the client device based on the anycast IP address in the metadata file received from the SLL server 104. The metadata file can have a time-to-live (TTL) period associated with it, so that the source address for the content can be continually updated. When the TTL period has expired, the client device 118 can request the metadata file from the SLL server 104 again.
When the source list 132 in the metadata file only includes the anycast IP address, the anycast servers 108-114 can be the primary source address for the content, and can be a source address for error recovery. In another embodiment, unicast addresses for each of the anycast servers 108-114 can be listed as the primary sources for the content in the metadata file. The anycast servers 108-114 can provide the client devices 116-130 with the entire content file via a unicast stream containing individual blocks of the content file from the anycast server nearest to the requesting client device. The blocks of the content file can be received in any order, and the client device 118 can use the sequence of the blocks in the metadata file to reconstruct the content file. While reconstructing the content file, the client device 118 may detect an error in one or more blocks of the content file, and can then request those blocks from the anycast server 110 again. The anycast can then deliver the requested block or blocks to the client device 118.
Referring now to
The client device 126 can utilize the updated source list 232 to determine the source IP addresses for the content. That is, the client device 126 can connect to an anycast server having the anycast IP address that is nearest to the client device, such as anycast server 112, to receive the first few blocks of the content. The anycast server 112 can then provide the client device 126 with a unicast signal containing blocks of the content. The anycast servers 108-114 can be used to provide the first few blocks, because the anycast servers can generally provide faster initial access to the blocks of the content than the multicast server 106. The client device 126 can determine that the multicast IP address should be used after the client device has received a few of the blocks of the content based on the updated source list 232. The client device 126 can then connect to the multicast server 106, which in turn can provide a multicast signal containing blocks of the content file to the client device. When the client device 126 begins to receive the multicast signal, the client device can stop receiving the unicast signal from the anycast server 112.
While the client device 126 is receiving blocks of content file, the client device can determine whether one or more of the blocks of content have an error. If a block is detected as having an error, the client device 126 can connect to the anycast server 112 to receive that block of the content again. In another embodiment, there can be multiple multicast servers, such that each of the multicast servers can provide redundancy for the other multicast servers for error recovery instead of the anycast servers 108-114.
Now referring to
The CTM server 102 can then return the updated source list 332 to the SLL server 104, which in turn can provide the updated source list to the client devices 116-130. A client device, such as client device 118, can then utilize the updated source list 332 to determine source addresses for the content. That is, the client device 118 can connect to an anycast server, such as anycast server 108, having the anycast IP address that is nearest to the client device to receive the first few blocks of the content. The anycast server 108 can then provide the client device 118 with a unicast signal containing blocks of the content.
The client device 118 can then connect to the multicast server 106, which in turn can provide a multicast signal containing the blocks of the content to the client device. When the client device 118 begins to receive the multicast signal, the client device can stop receiving the unicast signal from the anycast server 108. If the client device 118 determines that one or more of the blocks of content have an error while the content file is being received, the client device can connect to the client device 116 associated with the local peer IP address in the updated source list 332 to receive those blocks of the content. The client device 116 can then provide the client device 118 with the requested blocks of content via a peer-to-peer connection.
Referring now to
The client device 130 can then utilize the updated source list 432 to determine the source IP addresses for the content. That is, the client device 130 can connect to an anycast server, such as anycast server 114, having the anycast IP address that is nearest to the client device to receive the content. The anycast server 114 can then provide the client device 130 with a unicast signal containing blocks of the content. If the client device 130 determines that one or more of the blocks of content have an error, the client device can connect to a local peer, such as client device 128, having an IP address listed in the updated source list 432 to receive those blocks of data again. The client device 128 can then provide the client device 130 with the requested blocks of content via a peer-to-peer connection.
While the receiving of the blocks of content has only been described with respect to particular client devices, it should be understood that each of the client devices 116-130 can receive the blocks of content in a substantially similar modes using the metadata file received from the SLL server 104. In another embodiment, the anycast servers 114 can provide all of a content file and error recovery to the client device 116-130 via a unicast stream when access control features have been set for the content file. In this situation, the client device 120 can request the content via the anycast IP address, and can provide the anycast server 114 with authentication information associated with the content. The anycast server 114 can verify the authentication information and then provide the content to the client device 120 via the unicast signal.
At block 510, a multicast channel of the multicast server is allocated for delivery of the content. A list of sources is updated to include a multicast IP address of the multicast channel at block 512. The multicast IP address can be set as a primary source address of the content. The multicast address of the multicast channel can provided as the address of the content. At block 514, a determination is made that the number of client devices requesting the content has fallen below a second threshold. The multicast server is disabled when the number of client devices requesting the content has fallen below the second threshold at block 516. The multicast channel is de-allocated at block 518. At block 520, the list of sources is updated by removing the multicast IP address of the multicast channel.
Referring now to
Referring now to
At block 810, an updated list of sources including a multicast IP address of the multicast channel is received when the number of client devices requesting the content has exceeded a first threshold. The metadata file is updated to include the multicast IP address of the multicast channel as a primary source of the content at block 812. At block 814, an updated list of sources with the multicast IP address of the multicast channel removed is received when the number of client devices requesting the content has fallen below a second threshold. The metadata file is updated to replace the multicast IP address of the multicast channel with the anycast IP address as the primary source address of the content at block 816.
Referring now to
Referring now to
In a networked deployment, the computer system may operate in the capacity of a server or as a client user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system 1100 can also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, an STB, a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. In a particular embodiment, the computer system 1100 can be implemented using electronic devices that provide voice, video or data communication. Further, while a single computer system 1100 is illustrated, the term “system” shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.
The computer system 1100 may include a processor 1102, such as a central processing unit (CPU), a graphics processing unit (GPU), or both. Moreover, the computer system 1100 can include a main memory 1104 and a static memory 1106 that can communicate with each other via a bus 1108. As shown, the computer system 1100 may further include a video display unit 1110 such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, or a cathode ray tube (CRT). Additionally, the computer system 1100 may include an input device 1112 such as a keyboard, and a cursor control device 1114 such as a mouse. The computer system 1100 can also include a disk drive unit 1116, a signal generation device 1118 such as a speaker or remote control, and a network interface device 1120 to communicate with a network 1126. In a particular embodiment, the disk drive unit 1116 may include a computer-readable medium 1122 in which one or more sets of instructions 1124, such as software, can be embedded. The computer-readable medium can be a non-transitory computer readable medium, such as a hard disk drive, a flash memory, a read-only memory, a compact disk, a digital versatile disk, a cache, a random-access memory, and the like. Further, the instructions 1124 may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions 1124 may reside completely, or at least partially, within the main memory 1104, the static memory 1106, and/or within the processor 1102 during execution by the computer system 1100. The main memory 1104 and the processor 1102 also may include computer-readable media.
The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be minimized. Accordingly, the disclosure and the FIGS. are to be regarded as illustrative rather than restrictive.
The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b) and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description of the Drawings, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description of the Drawings, with each claim standing on its own as defining separately claimed subject matter.
The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true spirit and scope of the present disclosed subject matter. Thus, to the maximum extent allowed by law, the scope of the present disclosed subject matter is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
This application claims priority to and is a continuation of U.S. patent application Ser. No. 16/511,930, filed on Jul. 15, 2019, which is a continuation of U.S. patent application Ser. No. 15/362,338, filed on Nov. 28, 2016, now U.S. Pat. No. 10,356,207, which is a continuation of U.S. patent application Ser. No. 14/848,898, filed on Sep. 9, 2015, now U.S. Pat. No. 9,516,139, which is a continuation of U.S. patent application Ser. No. 13/156,849, filed on Jun. 9, 2011, now U.S. Pat. No. 9,137,202. All sections of the aforementioned applications and patents are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6088443 | Darland et al. | Jul 2000 | A |
| 6790548 | Keskula et al. | Sep 2004 | B2 |
| 7092389 | Chase et al. | Aug 2006 | B2 |
| 7120150 | Chase et al. | Oct 2006 | B2 |
| 7130393 | Hall, Jr et al. | Oct 2006 | B2 |
| 7313605 | Iloglu et al. | Dec 2007 | B2 |
| 7447151 | Mcdysan | Nov 2008 | B2 |
| 7467227 | Nguyen et al. | Dec 2008 | B1 |
| 7706401 | Bae | Apr 2010 | B2 |
| 7707594 | Foster et al. | Apr 2010 | B1 |
| 7769006 | Chase et al. | Aug 2010 | B1 |
| 7916735 | Mulligan et al. | Mar 2011 | B2 |
| 7920549 | Alt et al. | Apr 2011 | B2 |
| 7983254 | Alt et al. | Jul 2011 | B2 |
| 8028082 | Hooda et al. | Sep 2011 | B2 |
| 8040896 | Nguyen et al. | Oct 2011 | B2 |
| 8081631 | Chase et al. | Dec 2011 | B1 |
| 8089871 | Iloglu et al. | Jan 2012 | B2 |
| 8184641 | Alt et al. | May 2012 | B2 |
| 8325706 | Pacella | Dec 2012 | B2 |
| 8351435 | Mulligan et al. | Jan 2013 | B2 |
| 8407323 | Flavel et al. | Mar 2013 | B2 |
| 8411667 | Scholl et al. | Apr 2013 | B2 |
| 8417938 | Considine et al. | Apr 2013 | B1 |
| 8484355 | Lochhead et al. | Jul 2013 | B1 |
| 8498654 | Wyk, V et al. | Jul 2013 | B2 |
| 8537854 | Robertson et al. | Sep 2013 | B2 |
| 8571011 | Alt et al. | Oct 2013 | B2 |
| 8601091 | Venouss | Dec 2013 | B2 |
| 8670446 | Chase et al. | Mar 2014 | B2 |
| 8695059 | Kopti | Apr 2014 | B2 |
| 8699499 | Mulligan et al. | Apr 2014 | B2 |
| 8713628 | Kopti | Apr 2014 | B2 |
| 8776256 | Nguyen et al. | Jul 2014 | B2 |
| 8806606 | Ahmad et al. | Aug 2014 | B2 |
| 8819195 | Flavel et al. | Aug 2014 | B2 |
| 8819284 | Nguyen et al. | Aug 2014 | B2 |
| 20020143976 | Barker et al. | Oct 2002 | A1 |
| 20060029035 | Chase et al. | Feb 2006 | A1 |
| 20060047845 | Whited et al. | Mar 2006 | A1 |
| 20060182141 | Duggirala et al. | Aug 2006 | A1 |
| 20060206606 | Iloglu et al. | Sep 2006 | A1 |
| 20060239290 | Lin et al. | Oct 2006 | A1 |
| 20070101012 | Li et al. | May 2007 | A1 |
| 20070104151 | Papasakellariou et al. | May 2007 | A1 |
| 20070168523 | Jiang et al. | Jul 2007 | A1 |
| 20070195771 | Lu | Aug 2007 | A1 |
| 20080065783 | Iloglu et al. | Mar 2008 | A1 |
| 20080267511 | Bourrieres et al. | Oct 2008 | A1 |
| 20080279222 | Fuller et al. | Nov 2008 | A1 |
| 20090022064 | Oron et al. | Jan 2009 | A1 |
| 20090168752 | Segel | Jul 2009 | A1 |
| 20090168795 | Segel | Jul 2009 | A1 |
| 20090248886 | Tan et al. | Oct 2009 | A1 |
| 20090293095 | Karaoguz et al. | Nov 2009 | A1 |
| 20100121945 | Gerber et al. | May 2010 | A1 |
| 20100172282 | Zhang et al. | Jul 2010 | A1 |
| 20100287151 | Mustonen | Nov 2010 | A1 |
| 20120185298 | Abboa-offei | Jul 2012 | A1 |
| 20130028118 | Cherian | Jan 2013 | A1 |
| 20130054426 | Rowland et al. | Feb 2013 | A1 |
| 20130077470 | Mulligan et al. | Mar 2013 | A1 |
| 20130182710 | Scholl et al. | Jul 2013 | A1 |
| 20130227672 | Ogg et al. | Aug 2013 | A1 |
| 20130247082 | Wang et al. | Sep 2013 | A1 |
| 20130276090 | Kopti | Oct 2013 | A1 |
| 20140044132 | Chase et al. | Feb 2014 | A1 |
| 20140181966 | Carney et al. | Jun 2014 | A1 |
| 20140223434 | Mulligan et al. | Aug 2014 | A1 |
| 20140250240 | Schell et al. | Sep 2014 | A1 |
| 20140289813 | Nguyen et al. | Sep 2014 | A1 |
| 20140310603 | Flavel et al. | Oct 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| WO-02071720 | Sep 2002 | WO |
| Entry |
|---|
| IPv6 Anycast-based DNS Service Model Seunghoon Lee;Jaechul Suh;Kwanho Song 2007 Asia-Pacific Conference on Communications Year: 2007 | Conference Paper | Publisher: IEEE (Year: 2007). |
| Number | Date | Country | |
|---|---|---|---|
| 20210160341 A1 | May 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16511930 | Jul 2019 | US |
| Child | 17165053 | US | |
| Parent | 15362338 | Nov 2016 | US |
| Child | 16511930 | US | |
| Parent | 14848898 | Sep 2015 | US |
| Child | 15362338 | US | |
| Parent | 13156849 | Jun 2011 | US |
| Child | 14848898 | US |
