Patent Grant
10735214
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 client system 118 can be located in network destination area 134, client systems 120 and 122 can be located in network destination area 136, and client systems 124 and 126 can be located in network destination area 138. The network destination areas 134, 136, and 138 can either be multicast enabled areas or non multicast enabled areas. Depending on network conditions, the multicast enabled areas can change from being multicast enabled, to not being multicast enabled, and back to being multicast enabled. The routers 112, 114, and 116 can each be an edge router such that the routers can provide communication between the network 100 and the respective network destination areas 134, 136, and 138.
The edge routers 112, 114, and 116 can be aware of a multicast reachability status for each network destination area that the edge router serves, such as whether a specific network destination area is multicast enabled. The edge routers 112, 114, and 116 can also detect if a previously multicast enabled area is disabled for a period of time. In an embodiment, each of the edge routers 112, 114, and 116 may have additional network destination areas (not shown) that the edge router can service, and some of these network destination areas can be multicast enabled while others may not be multicast enabled.
The MDNC 130 can compile a list of IP prefixes associated with the multicast enabled areas based on signals obtained from the edge routers 112, 114, and 116. For example the edge router 112 can detect that the network destination area 134 is multicast enabled, and can send a signal 140 to the MDNC 130 indicating that the network destination area 134 is multicast enabled. The edge router 112 can use a Network Layer Reachability Information (NLRI) field of BGP to identify an IP prefix, such as 10.201.24.0/23, associated with the network destination area 134 that can receive multicast signals. For example the signal 140 can include NLRI{10.201.24.0/23} to indicate that the network destination area 134 is multicast enabled.
The edge router 114 can detect that the network destination area 136 is multicast enabled, and can send a signal 142 to the MDNC 130 with the NLRI field identifying the IP prefix, such as 24.94.32.0/19, associated with the network destination area 136 as being multicast enabled. The edge router 116 can detect that the network destination area 138 is not multicast enabled, and can send a signal 144 to the MDNC 130 with the NLRI field having a null value. In an embodiment, the edge router 114 may determine that network destination area 136, which was previously multicast enabled, has become disabled from receiving multicast signals, and can send a signal to the MDNC 130 with a Withdrawn Routes (WR) field having the prefix of the network destination address, such as WR{24.94.32.0/19}. The MDNC 130 can then remove the prefix 24.94.32.0/19 associated with the network destination area 136 from the list of multicast enabled areas.
When MDNC 130 has obtained the list of multicast enabled areas from edge routers 112, 114, and 116, the MDNC can store the list of multicast enabled areas within the network 100, and can then send the list of multicast enabled areas to the CDC 128 via signal 146. The NLRI field of the signal 146 can include the IP prefixes associated with the multicast enabled network destination areas 134 and 136, such as NLRI{10.201.24.0/23, 24.94.32.0/19}. The CDC 128 then can store the IP prefixes in the list of multicast enabled areas in memory 132. The CDC 128 can also select a multicast channel for providing multicast distribution of content to the network distribution areas 134, 136, and 138. The multicast channel can include a source IP address (S), and a group IP address (G) for the content.
Referring to
The client system 126 can send a request 210 for the content to the CDC 128, which can then determine whether the client system is in a multicast enabled area by comparing an IP address of the client system to the IP prefixes in the list of multicast enabled areas stored in memory 128. The CDC 128 can then determine that the client system 126 is not in a multicast enabled area, and can return a unicast address as a source address for the content to the client system via signal 212. The client system 126 can then send a request 214 for the content to the unicast address, which can be resolved at the content server 102 via routers 116, 110, 106, and 104. The content server 102 can then provide a unicast copy 216 of the content to the client system 126 in response to the request 214.
Referring to
When the CDC 128 determines that the content has a geographic restriction, such as excluding the content from network distribution area 136, the CDC can link an exclusion policy for the content to the multicast channel. The CDC 128 can then send the exclusion policy to the MDNC 130 via signal 302. In an embodiment, the exclusion policy can include the IP prefix 24.94.32.0/19 associated with network destination area 136 because the network destination area is in a restricted access zone. Thus, client systems 120 and 122 can be restricted from receiving the multicast channel. A NLRI field associated with the CV can be used in the signal 302 to identify the exclusion of the multicast channel (S,G) to the network destination area 136, such as NLRI{(S,G)}:CV{X}. In the signal 302 X can be the identifier of the access-zone defined to encompass network destination area 136, such as 24.94.32.0/19. The MDNC 130 can then distribute the exclusion policy to the edge routers 112, 114, and 116 via respective signals 304, 306, and 308. When the edge router 114 has received the exclusion policy, the edge router can determine that the exclusion policy is associated with network destination area 136, and can store the exclusion policy for enforcement of the geographic restriction.
Referring to
The client system 122, within restricted area 136, can send a request 410 for a source address of the content to the CDC 128. The CDC 128 can then compare the IP address of the client system 122 to the IP prefix of the exclusion policy. The CDC 128 can deny the request 410 for the content based on the IP address of the client system 122 matching the IP prefix of the exclusion policy, and can send a denial signal 412 to the client system. Thus, the CDC 128 can use the exclusion policy to prevent providing the client system 122 with the geographically restricted content.
The client system 120 can receive the multicast channel source IP address and group IP address without first sending a source request to the CDC 128, and can then send a multicast join message 414, such as Join(S,G), to the edge router 114. However, the edge router 114 can ignore the multicast join message 414 if the IP address of the client system 120 matches the IP prefix of the exclusion policy stored at the edge router. Thus, the distribution of the exclusion policy linked to the multicast channel providing the restricted content can prevent client systems 120 and 122 from receiving the restricted content.
Referring to
At block 612, a request for the content is obtain by the CDC from a client system. At block 614, a determination is made whether the client system requesting the content is in a multicast enabled area. For example the CDC can compare an IP address of the client system to the IP prefixes listed in the list of multicast enabled areas. If the client system is in a multicast enabled area, the multicast channel is returned as a source address for the content to the client system at block 616, otherwise the flow continues at block 624.
At block 618, a multicast join message is obtained at an edge router from the client system. A replicated multicast copy of the content is obtained by the edge router at block 620. The replicated multicast copy can be obtained from a content server and/or another router located in the CDN between the edge router and the content server. At block 622, the replicated multicast copy of the content is provided by the edge router to the client system. If the client system is not in a multicast enabled area, a unicast address is returned as the source address for the content to the client system at block 624. A unicast copy of the content is provided to the client system in response to a request for the content to the unicast address at block 626.
At block 712, the exclusion policy is stored at a multicast enabled edge router, which serves the area that is restricted from receiving the content based on the exclusion policy. A request for the content from a client system within the restricted area is denied by the CDC at block 714. For example, if a client system within the restricted area requests a source address for the content, the CDC can deny the request instead of returning the multicast channel as the source address to the client system. At block 716, a multicast join message from the client system within the restricted area is ignored by the multicast enabled edge router. In this situation, the client system in the restricted area could learn the multicast channel without sending a source request to the CDC, but the multicast enabled edge router can ignore the multicast join message based on the exclusion policy being stored in the multicast enabled edge router. At block 718, a withdrawal of the exclusion policy is sent to the multicast enabled edge router. The withdrawal can be based on the multicast channel no longer carry the restricted content, the exclusion of the content being removed for the area, and the like. The exclusion policy is removed from the multicast enabled edge router at block 720.
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 800 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 800 can be implemented using electronic devices that provide voice, video or data communication. Further, while a single computer system 800 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 800 may include a processor 802, such as a central processing unit (CPU), a graphics processing unit (GPU), or both. Moreover, the computer system 800 can include a main memory 804 and a static memory 806 that can communicate with each other via a bus 808. As shown, the computer system 800 may further include a video display unit 810 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 800 may include an input device 812 such as a keyboard, and a cursor control device 814 such as a mouse. The computer system 800 can also include a disk drive unit 816, a signal generation device 818 such as a speaker or remote control, and a network interface device 820 to communicate with a network 826. In a particular embodiment, the disk drive unit 816 may include a computer-readable medium 822 in which one or more sets of instructions 824, 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 824 may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions 824 may reside completely, or at least partially, within the main memory 804, the static memory 806, and/or within the processor 802 during execution by the computer system 800. The main memory 804 and the processor 802 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. 15/152,932, filed May 12, 2016, which is a continuation of U.S. patent application Ser. No. 14/297,952, filed Jun. 6, 2014, now U.S. Pat. No. 9,363,268, which is a continuation of and claims priority to U.S. patent application Ser. No. 13/097,458, filed Apr. 29, 2011, now U.S. Pat. No. 8,776,256, each of which are hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5790548 | Sistanizadeh et al. | Aug 1998 | A |
| 6088443 | Darland et al. | Jul 2000 | A |
| 6633765 | Maggenti | Oct 2003 | B1 |
| 7092389 | Chase et al. | Aug 2006 | B2 |
| 7120150 | Chase et al. | Oct 2006 | B2 |
| 7130393 | Hall 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 et al. | Apr 2010 | B2 |
| 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 |
| 8064449 | Fernandez Gutierrez | Nov 2011 | B2 |
| 8081631 | Chase et al. | Dec 2011 | B1 |
| 8089871 | Iloglu et al. | Jan 2012 | B2 |
| 8184641 | Alt et al. | May 2012 | B2 |
| 8274882 | Spatscheck et al. | Sep 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 et al. | Jul 2013 | B2 |
| 8537854 | Bae et al. | Sep 2013 | B2 |
| 8571011 | Alt et al. | Oct 2013 | B2 |
| 8601091 | Venouss et al. | 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 |
| 9271052 | Holden | Feb 2016 | B2 |
| 20020001310 | Mai | Jan 2002 | A1 |
| 20020007374 | Marks et al. | Jan 2002 | A1 |
| 20050044142 | Garrec et al. | Feb 2005 | A1 |
| 20050114656 | Liu et al. | May 2005 | A1 |
| 20060029035 | Chase et al. | Feb 2006 | A1 |
| 20060146857 | Naik et al. | Jul 2006 | A1 |
| 20060206606 | Barot | Sep 2006 | A1 |
| 20060262792 | Rokui | Nov 2006 | A1 |
| 20070028002 | McCanne | Feb 2007 | A1 |
| 20070115975 | Zhang | May 2007 | A1 |
| 20070226765 | Bahnck et al. | Sep 2007 | A1 |
| 20070253409 | Fu | Nov 2007 | A1 |
| 20070291944 | Wingert et al. | Dec 2007 | A1 |
| 20080056219 | Venkatachalam et al. | Mar 2008 | A1 |
| 20080065783 | Iloglu et al. | Mar 2008 | A1 |
| 20080066095 | Reinoso | Mar 2008 | A1 |
| 20080066103 | Ellis et al. | Mar 2008 | A1 |
| 20080089330 | Ballantyne | Apr 2008 | A1 |
| 20080112324 | Li | May 2008 | A1 |
| 20080151808 | O'Neill | Jun 2008 | A1 |
| 20080168487 | Chow et al. | Jul 2008 | A1 |
| 20080175239 | Sistanizadeh et al. | Jul 2008 | A1 |
| 20080256569 | Rhoades et al. | Oct 2008 | A1 |
| 20090119696 | Chow et al. | May 2009 | A1 |
| 20090207840 | McCanne | Aug 2009 | A1 |
| 20090293090 | Quigley et al. | Nov 2009 | A1 |
| 20090293095 | Karaoguz et al. | Nov 2009 | A1 |
| 20100043067 | Varadhan et al. | Feb 2010 | A1 |
| 20100083301 | Swenson | Apr 2010 | A1 |
| 20100115544 | Swenson | May 2010 | A1 |
| 20100125866 | Sofos et al. | May 2010 | A1 |
| 20100125867 | Sofos et al. | May 2010 | A1 |
| 20100138855 | Sofos et al. | Jun 2010 | A1 |
| 20100246467 | Song et al. | Sep 2010 | A1 |
| 20100322128 | Becker et al. | Dec 2010 | A1 |
| 20110061085 | Savard et al. | Mar 2011 | A1 |
| 20110075663 | Serbest | Mar 2011 | A1 |
| 20110225417 | Maharajh et al. | Sep 2011 | A1 |
| 20110302270 | Kawabe et al. | Dec 2011 | A1 |
| 20120151039 | Sayko et al. | Jun 2012 | A1 |
| 20120317235 | Nguyen et al. | Dec 2012 | A1 |
| 20130054426 | Rowland et al. | Feb 2013 | A1 |
| 20130058338 | Guttman | Mar 2013 | A1 |
| 20130077470 | Randhawa | Mar 2013 | A1 |
| 20130182710 | Scholl et al. | Jul 2013 | A1 |
| 20130227672 | Ogg et al. | Aug 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 | Schnell et al. | Sep 2014 | A1 |
| 20140310603 | Flavel et al. | Oct 2014 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20180343133 A1 | Nov 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15152932 | May 2016 | US |
| Child | 16036332 | US | |
| Parent | 14297952 | Jun 2014 | US |
| Child | 15152932 | US | |
| Parent | 13097458 | Apr 2011 | US |
| Child | 14297952 | US |
