Content management

Sivasubramanian , et al. June 17, 2

Patent Grant 8756325

U.S. patent number 8,756,325 [Application Number 13/793,886] was granted by the patent office on 2014-06-17 for content management. This patent grant is currently assigned to Amazon Technologies, Inc.. The grantee listed for this patent is Amazon Technologies, Inc.. Invention is credited to Bradley E. Marshall, David R. Richardson, Christopher L. Scofield, Swaminathan Sivasubramanian.

United States Patent 8,756,325
Sivasubramanian ,   et al. June 17, 2014
Content management

Abstract

A system and method for management and processing of resource requests is provided. A content delivery network service provider determines a class associated with a set of client computing devices and monitors resources requests for the determined class. The content delivery network service provider then identifies at least one cache component for providing additional content, such as advertisement content or other additional content provided in anticipation of future resource requests, to client computing devices as a function of the determined class. In other embodiments, instead of cache components, the content delivery network service provider identifies a second set of client computing devices as a function of the determined class for providing the additional content information.

Inventors: Sivasubramanian; Swaminathan (Seattle, WA), Richardson; David R. (Seattle, WA), Marshall; Bradley E. (Bainbridge Island, WA), Scofield; Christopher L. (Seattle, WA)
Applicant:
Name City State Country Type

Amazon Technologies, Inc.
Reno
NV
US
Assignee: Amazon Technologies, Inc. (Reno, NV)
Family ID: 41118746
Appl. No.: 13/793,886
Filed: March 11, 2013
Prior Publication Data
Document Identifier Publication Date
US 20130297717 A1 Nov 7, 2013
Related U.S. Patent Documents
Application Number Filing Date Patent Number Issue Date
12189019 Aug 8, 2008 8402137
12060213 Nov 27, 2012 8321568
Current U.S. Class: 709/226; 709/203; 709/200
Current CPC Class: H04L 67/26 (20130101); H04L 67/42 (20130101); H04L 65/4084 (20130101); G06F 16/9566 (20190101); H04L 67/22 (20130101); H04L 29/08729 (20130101); H04L 67/2842 (20130101); H04L 67/06 (20130101); H04L 67/2847 (20130101); H04L 67/306 (20130101); H04L 67/1097 (20130101)
Current International Class: G06F 15/173 (20060101)
Field of Search: ;709/200,224,226 ;705/7,14
References Cited [Referenced By]
U.S. Patent Documents
5341477 August 1994 Pitkin et al.
5611049 March 1997 Pitts
5774660 June 1998 Brendel et al.
5892914 April 1999 Pitts
5933811 August 1999 Angles et al.
5974454 October 1999 Apfel et al.
6016512 January 2000 Huitema
6026452 February 2000 Pitts
6052718 April 2000 Gifford
6085234 July 2000 Pitts et al.
6098096 August 2000 Tsirigotis et al.
6108703 August 2000 Leighton et al.
6182111 January 2001 Inohara et al.
6185598 February 2001 Farber et al.
6192051 February 2001 Lipman et al.
6205475 March 2001 Pitts
6223288 April 2001 Angles et al.
6275496 August 2001 Burns et al.
6286043 September 2001 Cuomo et al.
6286084 September 2001 Wexler et al.
6304913 October 2001 Rune
6351743 February 2002 DeArdo et al.
6351775 February 2002 Yu
6363411 March 2002 Dugan et al.
6366952 April 2002 Pitts
6374290 April 2002 Scharber et al.
6411967 June 2002 Van Renesse
6415280 July 2002 Farber et al.
6430607 August 2002 Kavner
6438592 August 2002 Killian
6452925 September 2002 Sistanizadeh et al.
6457047 September 2002 Chandra et al.
6459909 October 2002 Bilcliff et al.
6473804 October 2002 Kaiser et al.
6484143 November 2002 Swildens et al.
6505241 January 2003 Pitts
6529953 March 2003 Van Renesse
6553413 April 2003 Leighton et al.
6560610 May 2003 Eatherton et al.
6611873 August 2003 Kanehara
6654807 November 2003 Farber et al.
6658462 December 2003 Dutta
6678791 January 2004 Jacobs et al.
6694358 February 2004 Swildens et al.
6697805 February 2004 Choquier et al.
6724770 April 2004 Van Renesse
6732237 May 2004 Jacobs et al.
6754699 June 2004 Swildens et al.
6754706 June 2004 Swildens et al.
6769031 July 2004 Bero
6782398 August 2004 Bahl
6785704 August 2004 McCanne
6804706 October 2004 Pitts
6810291 October 2004 Card et al.
6810411 October 2004 Coughlin et al.
6829654 December 2004 Jungck
6874017 March 2005 Inoue et al.
6963850 November 2005 Bezos et al.
6981017 December 2005 Kasriel et al.
6986018 January 2006 O'Rourke et al.
6990526 January 2006 Zhu
6996616 February 2006 Leighton et al.
7003555 February 2006 Jungck
7006099 February 2006 Gut et al.
7007089 February 2006 Freedman
7010578 March 2006 Lewin et al.
7010598 March 2006 Sitaraman et al.
7032010 April 2006 Swildens et al.
7058706 June 2006 Iyer et al.
7058953 June 2006 Willard et al.
7065587 June 2006 Huitema et al.
7072982 July 2006 Teodosiu et al.
7076633 July 2006 Tormasov et al.
7082476 July 2006 Cohen et al.
7086061 August 2006 Joshi et al.
7092505 August 2006 Allison et al.
7092997 August 2006 Kasriel et al.
7099936 August 2006 Chase et al.
7103645 September 2006 Leighton et al.
7117262 October 2006 Bai et al.
7133905 November 2006 Dilley et al.
7139821 November 2006 Shah et al.
7143169 November 2006 Champagne et al.
7146560 December 2006 Dang et al.
7149809 December 2006 Barde et al.
7152118 December 2006 Anderson, IV et al.
7174382 February 2007 Ramanathan et al.
7185063 February 2007 Kasriel et al.
7188214 March 2007 Kasriel et al.
7194522 March 2007 Swildens et al.
7200667 April 2007 Teodosiu et al.
7216170 May 2007 Danker et al.
7225254 May 2007 Swildens et al.
7228350 June 2007 Hong et al.
7228359 June 2007 Monteiro
7233978 June 2007 Overton et al.
7240100 July 2007 Wein et al.
7254636 August 2007 O'Toole, Jr. et al.
7257581 August 2007 Steele et al.
7260598 August 2007 Liskov et al.
7269784 September 2007 Kasriel et al.
7274658 September 2007 Bornstein et al.
7289519 October 2007 Liskov
7293093 November 2007 Leighton
7310686 December 2007 Uysal
7316648 January 2008 Kelly et al.
7320131 January 2008 O'Toole, Jr.
7321918 January 2008 Burd et al.
7363291 April 2008 Page
7373416 May 2008 Kagan et al.
7430610 September 2008 Pace et al.
7441045 October 2008 Skene et al.
7461170 December 2008 Taylor et al.
7464142 December 2008 Flurry et al.
7478148 January 2009 Neerdaels
7492720 February 2009 Pruthi et al.
7499998 March 2009 Toebes et al.
7502836 March 2009 Menditto et al.
7519720 April 2009 Fishman et al.
7548947 June 2009 Kasriel et al.
7552235 June 2009 Chase et al.
7565407 July 2009 Hayball
7573916 August 2009 Bechtolsheim et al.
7594189 September 2009 Walker et al.
7596619 September 2009 Leighton et al.
7623460 November 2009 Miyazaki
7624169 November 2009 Lisiecki et al.
7640296 December 2009 Fuchs et al.
7650376 January 2010 Blumenau
7653700 January 2010 Bahl et al.
7653725 January 2010 Yahiro et al.
7657622 February 2010 Douglis et al.
7680897 March 2010 Carter et al.
7702724 April 2010 Brydon et al.
7706740 April 2010 Collins et al.
7707314 April 2010 McCarthy et al.
7711647 May 2010 Gunaseelan et al.
7716367 May 2010 Leighton et al.
7725602 May 2010 Liu et al.
7730187 June 2010 Raciborski et al.
7739400 June 2010 Lindbo et al.
7747720 June 2010 Toebes et al.
7756913 July 2010 Day
7761572 July 2010 Auerbach
7765304 July 2010 Davis et al.
7769823 August 2010 Jenny et al.
7773596 August 2010 Marques
7774342 August 2010 Virdy
7787380 August 2010 Aggarwal et al.
7792989 September 2010 Toebes et al.
7809597 October 2010 Das et al.
7813308 October 2010 Reddy et al.
7818454 October 2010 Kim et al.
7836177 November 2010 Kasriel et al.
7904875 March 2011 Hegyi
7912921 March 2011 O'Rourke et al.
7925782 April 2011 Sivasubramanian et al.
7930393 April 2011 Baumback et al.
7930427 April 2011 Josefsberg et al.
7933988 April 2011 Nasuto et al.
7937477 May 2011 Day et al.
7949779 May 2011 Farber et al.
7962597 June 2011 Richardson et al.
7966404 June 2011 Hedin et al.
7979509 July 2011 Malmskog et al.
7991910 August 2011 Richardson et al.
7996533 August 2011 Leighton et al.
7996535 August 2011 Auerbach
8000724 August 2011 Rayburn et al.
8028090 September 2011 Richardson et al.
8041809 October 2011 Sundaram et al.
8041818 October 2011 Gupta et al.
8065275 November 2011 Eriksen et al.
8069231 November 2011 Schran et al.
8073940 December 2011 Richardson et al.
8082348 December 2011 Averbuj et al.
8117306 February 2012 Baumback et al.
8122098 February 2012 Richardson et al.
8122124 February 2012 Baumback et al.
8135820 March 2012 Richardson et al.
8156243 April 2012 Richardson et al.
8190682 May 2012 Paterson-Jones et al.
8224986 July 2012 Liskov et al.
8234403 July 2012 Richardson et al.
8266288 September 2012 Banerjee et al.
8301645 October 2012 Crook
8321568 November 2012 Sivasubramanian et al.
8402137 March 2013 Sivasuramanian et al.
8452874 May 2013 MacCarthaigh et al.
8615549 December 2013 Knowles et al.
2001/0000811 May 2001 May et al.
2001/0032133 October 2001 Moran
2001/0034704 October 2001 Farhat et al.
2001/0049741 December 2001 Skene et al.
2001/0052016 December 2001 Skene et al.
2001/0056416 December 2001 Garcia-Luna-Aceves
2001/0056500 December 2001 Farber et al.
2002/0002613 January 2002 Freeman et al.
2002/0007413 January 2002 Garcia-Luna-Aceves et al.
2002/0048269 April 2002 Hong et al.
2002/0049608 April 2002 Hartsell et al.
2002/0052942 May 2002 Swildens et al.
2002/0062372 May 2002 Hong et al.
2002/0068554 June 2002 Dusse
2002/0069420 June 2002 Russell et al.
2002/0078233 June 2002 Biliris et al.
2002/0082858 June 2002 Heddaya et al.
2002/0083118 June 2002 Sim
2002/0083148 June 2002 Shaw et al.
2002/0087374 July 2002 Boubez et al.
2002/0092026 July 2002 Janniello et al.
2002/0099616 July 2002 Sweldens
2002/0099850 July 2002 Farber et al.
2002/0101836 August 2002 Dorenbosch
2002/0107944 August 2002 Bai et al.
2002/0112049 August 2002 Elnozahy et al.
2002/0116481 August 2002 Lee
2002/0116491 August 2002 Boyd et al.
2002/0124047 September 2002 Gartner et al.
2002/0124098 September 2002 Shaw
2002/0129123 September 2002 Johnson et al.
2002/0135611 September 2002 Deosaran et al.
2002/0138286 September 2002 Engstrom
2002/0138437 September 2002 Lewin et al.
2002/0143989 October 2002 Huitema et al.
2002/0147770 October 2002 Tang
2002/0147774 October 2002 Lisiecki et al.
2002/0150094 October 2002 Cheng et al.
2002/0156911 October 2002 Croman et al.
2002/0161767 October 2002 Shapiro et al.
2002/0163882 November 2002 Bornstein et al.
2002/0165912 November 2002 Wenocur et al.
2002/0188722 December 2002 Banerjee et al.
2002/0198953 December 2002 O'Rourke et al.
2003/0002484 January 2003 Freedman
2003/0009591 January 2003 Hayball et al.
2003/0028642 February 2003 Agarwal et al.
2003/0033283 February 2003 Evans et al.
2003/0037139 February 2003 Shteyn
2003/0065739 April 2003 Shnier
2003/0074401 April 2003 Connell et al.
2003/0079027 April 2003 Slocombe et al.
2003/0093523 May 2003 Cranor et al.
2003/0099202 May 2003 Lear et al.
2003/0101278 May 2003 Garcia-Luna-Aceves et al.
2003/0120741 June 2003 Wu et al.
2003/0133554 July 2003 Nykanen et al.
2003/0135509 July 2003 Davis et al.
2003/0140087 July 2003 Lincoln et al.
2003/0145038 July 2003 Tariq et al.
2003/0145066 July 2003 Okada et al.
2003/0149581 August 2003 Chaudhri et al.
2003/0154284 August 2003 Bernardin et al.
2003/0163722 August 2003 Anderson, IV
2003/0172145 September 2003 Nguyen
2003/0172183 September 2003 Anderson, IV et al.
2003/0172291 September 2003 Judge et al.
2003/0174648 September 2003 Wang et al.
2003/0182305 September 2003 Balva et al.
2003/0182413 September 2003 Allen et al.
2003/0182447 September 2003 Schilling
2003/0187935 October 2003 Agarwalla et al.
2003/0187970 October 2003 Chase et al.
2003/0191822 October 2003 Leighton et al.
2003/0200394 October 2003 Ashmore et al.
2003/0204602 October 2003 Hudson et al.
2003/0229682 December 2003 Day
2003/0233423 December 2003 Dilley et al.
2003/0236700 December 2003 Arning et al.
2004/0010621 January 2004 Afergan et al.
2004/0019518 January 2004 Abraham et al.
2004/0024841 February 2004 Becker et al.
2004/0030620 February 2004 Benjamin et al.
2004/0034744 February 2004 Karlsson et al.
2004/0039798 February 2004 Hotz et al.
2004/0044731 March 2004 Chen et al.
2004/0044791 March 2004 Pouzzner
2004/0059805 March 2004 Dinker et al.
2004/0064501 April 2004 Jan et al.
2004/0073596 April 2004 Kloninger et al.
2004/0073867 April 2004 Kausik et al.
2004/0078468 April 2004 Hedin et al.
2004/0078487 April 2004 Cernohous et al.
2004/0083307 April 2004 Uysal
2004/0117455 June 2004 Kaminsky et al.
2004/0128344 July 2004 Trossen
2004/0128346 July 2004 Melamed et al.
2004/0167981 August 2004 Douglas et al.
2004/0172466 September 2004 Douglas et al.
2004/0194085 September 2004 Beaubien et al.
2004/0194102 September 2004 Neerdaels
2004/0203630 October 2004 Wang
2004/0205149 October 2004 Dillon et al.
2004/0205162 October 2004 Parikh
2004/0215823 October 2004 Kleinfelter et al.
2004/0221034 November 2004 Kausik et al.
2004/0249971 December 2004 Klinker
2004/0249975 December 2004 Tuck et al.
2004/0254921 December 2004 Cohen et al.
2004/0267906 December 2004 Truty
2004/0267907 December 2004 Gustafsson
2005/0010653 January 2005 McCanne
2005/0021706 January 2005 Maggi et al.
2005/0021862 January 2005 Schroeder et al.
2005/0038967 February 2005 Umbehocker et al.
2005/0044270 February 2005 Grove et al.
2005/0102683 May 2005 Branson et al.
2005/0108169 May 2005 Balasubramanian et al.
2005/0108529 May 2005 Juneau
2005/0114296 May 2005 Farber et al.
2005/0132083 June 2005 Raciborski et al.
2005/0157712 July 2005 Rangarajan et al.
2005/0163168 July 2005 Sheth et al.
2005/0168782 August 2005 Kobashi et al.
2005/0171959 August 2005 Deforche et al.
2005/0188073 August 2005 Nakamichi et al.
2005/0192008 September 2005 Desai et al.
2005/0198571 September 2005 Kramer et al.
2005/0216569 September 2005 Coppola et al.
2005/0216674 September 2005 Robbin et al.
2005/0229119 October 2005 Torvinen
2005/0232165 October 2005 Brawn et al.
2005/0259672 November 2005 Eduri
2005/0262248 November 2005 Jennings, III et al.
2005/0267991 December 2005 Huitema et al.
2005/0267992 December 2005 Huitema et al.
2005/0267993 December 2005 Huitema et al.
2005/0278259 December 2005 Gunaseelan et al.
2005/0283759 December 2005 Peteanu et al.
2005/0283784 December 2005 Suzuki
2006/0013158 January 2006 Ahuja et al.
2006/0020596 January 2006 Liu et al.
2006/0020684 January 2006 Mukherjee et al.
2006/0020714 January 2006 Girouard et al.
2006/0020715 January 2006 Jungck
2006/0026067 February 2006 Nicholas et al.
2006/0026154 February 2006 Altinel et al.
2006/0036720 February 2006 Faulk, Jr.
2006/0037037 February 2006 Miranz
2006/0041614 February 2006 Oe
2006/0047787 March 2006 Agarwal et al.
2006/0047813 March 2006 Aggarwal et al.
2006/0059246 March 2006 Grove
2006/0063534 March 2006 Kokkonen et al.
2006/0064476 March 2006 Decasper et al.
2006/0064500 March 2006 Roth et al.
2006/0074750 April 2006 Clark et al.
2006/0075084 April 2006 Lyon
2006/0075139 April 2006 Jungck
2006/0083165 April 2006 McLane et al.
2006/0085536 April 2006 Meyer et al.
2006/0112066 May 2006 Hamzy
2006/0112176 May 2006 Liu et al.
2006/0120385 June 2006 Atchison et al.
2006/0129665 June 2006 Toebes et al.
2006/0143293 June 2006 Freedman
2006/0155823 July 2006 Tran et al.
2006/0161541 July 2006 Cencini
2006/0168088 July 2006 Leighton et al.
2006/0179080 August 2006 Meek et al.
2006/0184936 August 2006 Abels et al.
2006/0190605 August 2006 Franz et al.
2006/0193247 August 2006 Naseh et al.
2006/0195866 August 2006 Thukral
2006/0218304 September 2006 Mukherjee et al.
2006/0227740 October 2006 McLaughlin et al.
2006/0227758 October 2006 Rana et al.
2006/0230137 October 2006 Gare et al.
2006/0233155 October 2006 Srivastava
2006/0253546 November 2006 Chang et al.
2006/0253609 November 2006 Andreev et al.
2006/0259581 November 2006 Piersol
2006/0259690 November 2006 Vittal et al.
2006/0259984 November 2006 Juneau
2006/0265497 November 2006 Ohata et al.
2006/0265508 November 2006 Angel et al.
2006/0265516 November 2006 Schilling
2006/0265720 November 2006 Cai et al.
2006/0271641 November 2006 Stavrakos et al.
2006/0282522 December 2006 Lewin et al.
2007/0005689 January 2007 Leighton et al.
2007/0005892 January 2007 Mullender et al.
2007/0011267 January 2007 Overton et al.
2007/0014241 January 2007 Banerjee et al.
2007/0021998 January 2007 Laithwaite et al.
2007/0038994 February 2007 Davis et al.
2007/0041393 February 2007 Westhead et al.
2007/0043859 February 2007 Ruul
2007/0050522 March 2007 Grove et al.
2007/0050703 March 2007 Lebel
2007/0055764 March 2007 Dilley et al.
2007/0076872 April 2007 Juneau
2007/0086429 April 2007 Lawrence et al.
2007/0094361 April 2007 Hoynowski et al.
2007/0101377 May 2007 Six et al.
2007/0118667 May 2007 McCarthy et al.
2007/0118668 May 2007 McCarthy et al.
2007/0134641 June 2007 Lieu
2007/0168517 July 2007 Weller
2007/0174426 July 2007 Swildens et al.
2007/0174442 July 2007 Sherman et al.
2007/0174490 July 2007 Choi et al.
2007/0183342 August 2007 Wong et al.
2007/0198982 August 2007 Bolan et al.
2007/0208737 September 2007 Li et al.
2007/0219795 September 2007 Park et al.
2007/0220010 September 2007 Ertugrul
2007/0244964 October 2007 Challenger et al.
2007/0250467 October 2007 Mesnik et al.
2007/0250560 October 2007 Wein et al.
2007/0250611 October 2007 Bhogal et al.
2007/0253377 November 2007 Janneteau et al.
2007/0255843 November 2007 Zubev
2007/0266113 November 2007 Koopmans et al.
2007/0266311 November 2007 Westphal
2007/0266333 November 2007 Cossey et al.
2007/0271375 November 2007 Hwang
2007/0271385 November 2007 Davis et al.
2007/0280229 December 2007 Kenney
2007/0288588 December 2007 Wein et al.
2008/0005057 January 2008 Ozzie et al.
2008/0008089 January 2008 Bornstein et al.
2008/0025304 January 2008 Venkataswami et al.
2008/0046596 February 2008 Afergan et al.
2008/0065724 March 2008 Seed et al.
2008/0065745 March 2008 Leighton et al.
2008/0071859 March 2008 Seed et al.
2008/0071987 March 2008 Karn et al.
2008/0072264 March 2008 Crayford
2008/0082551 April 2008 Farber et al.
2008/0086574 April 2008 Raciborski et al.
2008/0103805 May 2008 Shear et al.
2008/0104268 May 2008 Farber et al.
2008/0114829 May 2008 Button et al.
2008/0134043 June 2008 Georgis et al.
2008/0147866 June 2008 Stolorz et al.
2008/0147873 June 2008 Matsumoto
2008/0155061 June 2008 Afergan et al.
2008/0155614 June 2008 Cooper et al.
2008/0162667 July 2008 Verma et al.
2008/0172488 July 2008 Jawahar et al.
2008/0189437 August 2008 Halley
2008/0201332 August 2008 Souders et al.
2008/0215718 September 2008 Stolorz et al.
2008/0215735 September 2008 Farber et al.
2008/0215750 September 2008 Farber et al.
2008/0222281 September 2008 Dilley et al.
2008/0222291 September 2008 Weller et al.
2008/0222295 September 2008 Robinson et al.
2008/0228574 September 2008 Stewart et al.
2008/0228920 September 2008 Souders et al.
2008/0235400 September 2008 Slocombe et al.
2008/0275772 November 2008 Suryanarayana et al.
2008/0281950 November 2008 Wald et al.
2008/0288722 November 2008 Lecoq et al.
2008/0301670 December 2008 Gouge et al.
2008/0319862 December 2008 Golan et al.
2009/0013063 January 2009 Soman
2009/0016236 January 2009 Alcala et al.
2009/0029644 January 2009 Sue et al.
2009/0031367 January 2009 Sue
2009/0031368 January 2009 Ling
2009/0031376 January 2009 Riley et al.
2009/0049098 February 2009 Pickelsimer et al.
2009/0070533 March 2009 Elazary et al.
2009/0083228 March 2009 Shatz et al.
2009/0086741 April 2009 Zhang
2009/0103707 April 2009 McGary et al.
2009/0106381 April 2009 Kasriel et al.
2009/0112703 April 2009 Brown
2009/0125934 May 2009 Jones et al.
2009/0132368 May 2009 Cotter et al.
2009/0132648 May 2009 Swildens et al.
2009/0144412 June 2009 Ferguson et al.
2009/0150926 June 2009 Schlack
2009/0157850 June 2009 Gagliardi et al.
2009/0158163 June 2009 Stephens et al.
2009/0164331 June 2009 Bishop et al.
2009/0177667 July 2009 Ramos et al.
2009/0182815 July 2009 Czechowski et al.
2009/0182945 July 2009 Aviles et al.
2009/0187575 July 2009 DaCosta
2009/0204682 August 2009 Jeyaseelan et al.
2009/0210549 August 2009 Hudson et al.
2009/0248852 October 2009 Fuhrmann et al.
2009/0248893 October 2009 Richardson et al.
2009/0259971 October 2009 Rankine et al.
2009/0271577 October 2009 Campana et al.
2009/0271730 October 2009 Rose et al.
2009/0279444 November 2009 Ravindran et al.
2009/0287750 November 2009 Banavar et al.
2009/0307307 December 2009 Igarashi
2009/0327489 December 2009 Swildens et al.
2009/0327914 December 2009 Adar et al.
2010/0005175 January 2010 Swildens et al.
2010/0011061 January 2010 Hudson et al.
2010/0023601 January 2010 Lewin et al.
2010/0030662 February 2010 Klein
2010/0034470 February 2010 Valencia-Campo et al.
2010/0036944 February 2010 Douglis et al.
2010/0070603 March 2010 Moss et al.
2010/0088367 April 2010 Brown et al.
2010/0088405 April 2010 Huang et al.
2010/0100629 April 2010 Raciborski et al.
2010/0111059 May 2010 Bappu et al.
2010/0121953 May 2010 Friedman et al.
2010/0122069 May 2010 Gonion
2010/0131646 May 2010 Drako
2010/0150155 June 2010 Napierala
2010/0192225 July 2010 Ma et al.
2010/0217801 August 2010 Leighton et al.
2010/0226372 September 2010 Watanabe
2010/0257566 October 2010 Matila
2010/0293479 November 2010 Rousso et al.
2010/0299439 November 2010 McCarthy et al.
2010/0318508 December 2010 Brawer et al.
2010/0332595 December 2010 Fullagar et al.
2011/0040893 February 2011 Karaoguz et al.
2011/0078000 March 2011 Ma et al.
2011/0078230 March 2011 Sepulveda
2011/0096987 April 2011 Morales et al.
2011/0153941 June 2011 Spatscheck et al.
2011/0238501 September 2011 Almeida
2011/0238793 September 2011 Bedare et al.
2011/0252142 October 2011 Richardson et al.
2011/0252143 October 2011 Baumback et al.
2011/0258049 October 2011 Ramer et al.
2011/0276623 November 2011 Girbal
2012/0066360 March 2012 Ghosh
2012/0131177 May 2012 Brandt et al.
2012/0179839 July 2012 Raciborski et al.
Foreign Patent Documents
1422468 Jun 2003 CN
1605182 Apr 2005 CN
101189598 May 2008 CN
101460907 Jun 2009 CN
2008167 Dec 2008 EP
2003-167810 Jun 2003 JP
2003522358 Jul 2003 JP
2007-133896 May 2007 JP
WO 2007/007960 Jan 2007 WO
WO 2007/126837 Nov 2007 WO
WO 2012/044587 Apr 2012 WO

Other References

Barbir, A., et al., "Known Content Network (CN) Request-Routing Mechanisms", Request for Comments 3568, [online], IETF, Jul. 2003, [retrieved on Feb. 26, 2013], Retrieved from the Internet: (URL: http://tools.ietf.org/rfc/rfc3568.txt). cited by applicant .
Chipara et al, "Realtime Power-Aware Routing in Sensor Network", IEEE, 2006, 10 pages. cited by applicant .
International Preliminary Report on Patentability in PCT/US2011/053302 mailed Apr. 2, 2013. cited by applicant .
International Preliminary Report on Patentability in PCT/US2011/061486 mailed May 22, 2013. cited by applicant .
Office Action in Canadian Application No. 2726915 dated May 13, 2013. cited by applicant .
Office Action in Canadian Application No. 2741895 dated Feb. 25, 2013. cited by applicant .
Office Action in Chinese Application No. 200980119995.0 dated Apr. 15, 2013. cited by applicant .
Office Action in Japanese Application No. 2011-516466 mailed Mar. 6, 2013. cited by applicant .
Office Action in Korean Application No. 10-2011-7002461 mailed May 29, 2013. cited by applicant .
Preliminary Examination in Chinese Application No. 201180053405.6 dated May 28, 2013. English Translation Not Yet Received. cited by applicant .
Second Office Action in Chinese Application No. 200980119993.1 dated Mar. 12, 2013. cited by applicant .
"Global Server Load Balancing with ServerIron," Foundry Networks, retrieved Aug. 30, 2007, from http://www.foundrynet.com/pdf/an-global-server-load-bal.pdf, 7 pages. cited by applicant .
"Grid Computing Solutions," Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/software/grid, 3 pages. cited by applicant .
"Grid Offerings," Java.net, retrieved May 3, 2006, from http://wiki.java.net/bin/view/Sungrid/OtherGridOfferings, 8 pages. cited by applicant .
"Recent Advances Boost System Virtualization," eWeek.com, retrieved from May 3, 2006, http://www.eWeek.com/article2/0,1895,1772626,00.asp, 5 pages. cited by applicant .
"Scaleable Trust of Next Generation Management (STRONGMAN)," retrieved May 17, 2006, from http://www.cis.upenn.edu/.about.dsl/STRONGMAN/, 4 pages. cited by applicant .
"Sun EDA Compute Ranch," Sun Microsystems, Inc., retrieved May 3, 2006, from http://sun.com/processors/ranch/brochure.pdf, 2 pages. cited by applicant .
"Sun Microsystems Accelerates UltraSP ARC Processor Design Program With New Burlington, Mass. Compute Ranch," Nov. 6, 2002, Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/smi/Press/sunflash/2002-11/sunflash.20021106.3 .xml, 2 pages. cited by applicant .
"Sun N1 Grid Engine 6," Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/software/gridware/index.xml, 3 pages. cited by applicant .
"Sun Opens New Processor Design Compute Ranch," Nov. 30, 2001, Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/smi/Press/sunflash/2001-11/sunflash.20011130.1.xml, 3 pages. cited by applicant .
"The Softricity Desktop," Softricity, Inc., retrieved May 3, 2006, from http://www.softricity.com/products/, 3 pages. cited by applicant .
"Xen--The Xen virtual Machine Monitor," University of Cambridge Computer Laboratory, retrieved Nov. 8, 2005, from http://www.cl.cam.ac.uk/Research/SRG/netos/xen/, 2 pages. cited by applicant .
"XenFaq," retrieved Nov. 8, 2005, from http://wiki.xensource.com/xenwiki/XenFaq?action=print, 9 pages. cited by applicant .
Abi, Issam, et al., "A Business Driven Management Framework for Utility Computing Environments," Oct. 12, 2004, HP Laboratories Bristol, HPL-2004-171, retrieved Aug. 30, 2007, from http://www.hpl.hp.com/techreports/2004/HPL-2004-171.pdf, 14 pages. cited by applicant .
American Bar Association; Digital Signature Guidelines Tutorial [online]; Feb. 10, 2002 [retrived on Mar. 2, 2010]; American Bar Association Section of Science and Technology Information Security Committee; Retrieved from the internet: <URL: http://web.archive.org/web/20020210124615/www.abanet.org/scitech/ec/isc/d- sg-tutorial.html; pp. 1-8. cited by applicant .
Baglioni et al., "Preprocessing and Mining Web Log Data for Web Personalization", LNAI 2829, 2003, pp. 237-249. cited by applicant .
Bellovin, S., "Distributed Firewalls," ;login;:37-39, Nov. 1999, http://www.cs.columbia.edu/-smb/papers/distfw. html, 10 pages, retrieved Nov. 11, 2005. cited by applicant .
Blaze, M., "Using the KeyNote Trust Management System," Mar. 1, 2001, from http://www.crypto.com/trustmgt/kn.html, 4 pages, retrieved May 17, 2006. cited by applicant .
Brenton, C., "What is Egress Filtering and How Can I Implement It?--Egress Filtering v 0.2," Feb. 29, 2000, SANS Institute, http://www.sans.org/infosecFAQ/firewall/egress.htm, 6 pages. cited by applicant .
Byun et al., "A Dynamic Grid Services Deployment Mechanism for On-Demand Resource Provisioning", IEEE International Symposium on Cluster Computing and the Grid:863-870, 2005. cited by applicant .
Clark, C., "Live Migration of Virtual Machines," May 2005, NSDI '05: 2nd Symposium on Networked Systems Design and Implementation, Boston, MA, May 2-4, 2005, retrieved from http://www.usenix.org/events/nsdi05/tech/full.sub.--papers/clark/clark.pd- f, 14 pages. cited by applicant .
Coulson, D., "Network Security Iptables," Apr. 2003, Linuxpro, Part 2, retrieved from http://davidcoulson.net/writing/lxf/38/iptables.pdf, 4 pages. cited by applicant .
Coulson, D., "Network Security Iptables," Mar. 2003, Linuxpro, Part 1, retrieved from http://davidcoulson.net/writing/lxf/39/iptables.pdf, 4 pages. cited by applicant .
Deleuze, C., et al., A DNS Based Mapping Peering System for Peering CDNs, draft-deleuze-cdnp-dnsmap-peer-00.txt, Nov. 20, 2000, 20 pages. cited by applicant .
Demers, A., "Epidemic Algorithms For Replicated Database Maintenance," 1987, Proceedings of the sixth annual ACM Symposium on Principles of Distributed Computing, Vancouver, British Columbia, Canada, Aug. 10-12, 1987, 12 pages. cited by applicant .
First Office Action in Chinese Application No. 200980111426.1 mailed Feb. 16, 2013. cited by applicant .
First Office Action in Chinese Application No. 200980119993.1 dated Jul. 4, 2012. cited by applicant .
First Office Action in Chinese Application No. 200980119995.0 dated Jul. 6, 2012. cited by applicant .
First Office Action in Chinese Application No. 200980145872.4 dated Nov. 29, 2012. cited by applicant .
Gruener, J., "A Vision Of Togetherness," May 24, 2004, NetworkWorld, retrieved May 3, 2006, from, http://www.networkworld.com/supp/2004/ndc3/0524virt.html, 9 pages. cited by applicant .
International Preliminary Report on Patentability in PCT/US2007/007601 mailed Sep. 30, 2008 in 8 pages. cited by applicant .
International Search Report and Written Opinion in PCT/US07/07601 mailed Jul. 18, 2008 in 11 pages. cited by applicant .
International Search Report and Written Opinion in PCT/US2010/060567 mailed on Mar. 28, 2012. cited by applicant .
International Search Report and Written Opinion in PCT/US2011/053302 mailed Nov. 28, 2011 in 11 pages. cited by applicant .
International Search Report and Written Opinion in PCT/US2011/061486 mailed Mar. 30, 2012 in 11 pages. cited by applicant .
Ioannidis, S., et al., "Implementing a Distributed Firewall," Nov. 2000, (ACM) Proceedings of the ACM Computer and Communications Security (CCS) 2000, Athens, Greece, pp. 190-199, retrieved from http://www.cis.upenn.edu/.about.dls/STRONGMAN/Papers/df.pdf, 10 pages. cited by applicant .
Joseph, Joshy, et al., "Introduction to Grid Computing," Apr. 16, 2004, retrieved Aug. 30, 2007, from http://www.informit.com/articles/printerfriendly.aspx?p=169508, 19 pages. cited by applicant .
Kenshi, P., "Help File Library: Iptables Basics," Justlinux, retrieved Dec. 1, 2005, from http://www.justlinux.com/nhf/Security/Iptables .sub.-- Basics.html, 4 pages. cited by applicant .
Liu et al., "Combined mining of Web server logs and web contents for classifying user navigation patterns and predicting users' future requests," Data & Knowledge Engineering 61 (2007) pp. 304-330. cited by applicant .
Maesono, et al., "A Local Scheduling Method considering Data Transfer in Data Grid," Technical Report of IEICE, vol. 104, No. 692, pp. 435-440, The Institute of Electronics, Information and Communication Engineers, Japan, Feb. 2005. cited by applicant .
Office Action in Candian Application No. 2741895 dated Feb. 25, 2013. cited by applicant .
Office Action in Japanese Application No. 2011-502138 mailed Feb. 1, 2013. cited by applicant .
Office Action in Japanese Application No. 2011-502140 mailed Dec. 7, 2012. cited by applicant .
Office Action in Japanese Application No. 2012-052264 mailed Dec. 11, 2012 in 26 pages. cited by applicant .
Search Report and Written Opinion in Singapore Application No. 201103333-9 mailed Nov. 19, 2012. cited by applicant .
Shankland, S., "Sun to buy start-up to bolster N1 ," Jul. 30, 2003, CNet News.com, retrieved May 3, 2006, http://news.zdnet.com/2100-3513.sub.--22-5057752.html, 8 pages. cited by applicant .
Singapore Examination Report in Application No. 201006837-7 mailed May 16, 2012. cited by applicant .
Singapore Written Opinion in Application No. 201006836-9, mailed Apr. 30, 2012 in 10 pages. cited by applicant .
Singapore Written Opinion in Application No. 201006836-9, mailed Oct. 12, 2011 in 12 pages. cited by applicant .
Singapore Written Opinion in Application No. 201006837-7, mailed Oct. 12, 2011 in 11 pages. cited by applicant .
Singapore Written Opinion in Application No. 201006874-0, mailed Oct. 12, 2011 in 10 pages. cited by applicant .
Strand, L., "Adaptive distributed firewall using intrusion detection," Nov. 1, 2004, University of Oslo Department of Informatics, retrieved Mar. 8, 2006, from http://gnist.org/.about.lars/studies/master/StrandLars-master.pdf, 158 pages. cited by applicant .
Supplementary European Search Report in Application No. 07754164.7 mailed Dec. 20, 2010 in 7 pages. cited by applicant .
Supplementary European Search Report in Application No. 09727694.3 mailed Jan. 30, 2012 in 6 pages. cited by applicant .
Supplementary European Search Report in Application No. 09728756.9 mailed Jan. 8, 2013. cited by applicant .
Takizawa, et al., "Scalable MultiReplication Framework on The Grid," Report of Study of Information Processing Society of Japan, Information Processing Society, vol. 2004, No. 81, pp. 247-252, Japan, Aug. 1, 2004. cited by applicant .
Tan et al., "Classification: Basic Concepts, Decision Tree, and Model Evaluation", Introduction in Data Mining; http://www-users.cs.umn.edu/.about.kumar/dmbook/ch4.pdf, 2005, pp. 245-205. cited by applicant .
Van Renesse, R., "Astrolabe: A Robust And Scalable Technology For Distributed System Monitoring, Management, And Data Mining," May 2003, ACM Transactions On Computer Systems (TOCS), 21 (2): 164-206, 43 pages. cited by applicant .
Vijayan, J., "Terraspring Gives Sun's N1 a Boost," Nov. 25, 2002, Computerworld, retrieved May 3, 2006, from http://www.computerworld.com/printthis/2002/0,4814, 76159,00.html, 3 pages. cited by applicant .
Virtual Iron Software Home, Virtual Iron, retrieved May 3, 2006, from http://www.virtualiron.com/, 1 page. cited by applicant .
Waldspurger, CA., "Spawn: A Distributed Computational Economy," Feb. 1992, IEEE Transactions on Software Engineering, 18(2): 103-117, I5 pages. cited by applicant .
Watanabe, et al., "Remote Program Shipping System for GridRPC Systems," Report of Study of Information Processing Society of Japan, Information Processing Society, vol. 2003, No. 102, pp. 73-78, Japan, Oct. 16, 2003. cited by applicant .
Xu et al., "Decision tree regression for soft classification of remote sensing data", Remote Sensing of Environment 97 (2005) pp. 322-336. cited by applicant .
Yamagata, et al., "A virtual-machine based fast deployment tool for Grid execution environment," Report of Study of Information Processing Society of Japan, Information Processing Society, vol. 2006, No. 20, pp. 127-132, Japan, Feb. 28, 2006. cited by applicant .
Zhu, Xiaoyun, et al., "Utility-Driven Workload Management Using Nested Control Design," Mar. 29, 2006, HP Laboratories Palo Alto, HPL-2005-193(R.1), retrieved Aug. 30, 2007, from http://www.hpl.hp.com/techreports/2005/HPL-2005-193R1.pdf, 9 pages. cited by applicant .
Examination Report in Singapore Application No. 201103333-9 dated Aug. 13, 2013. cited by applicant .
Office Action in Canadian Application No. 2741895 dated Oct. 21, 2013. cited by applicant .
Office Action in Chinese Application No. 200780020255.2 dated Mar. 4, 2013. cited by applicant .
Office Action in Chinese Application No. 200980119993.1 dated Oct. 21, 2013. cited by applicant.

Primary Examiner: Mejia; Anthony
Attorney, Agent or Firm: Knobbe, Martens, Olson & Bear, LLP
Parent Case Text


This application is a continuation application of U.S. patent application Ser. No. 12/189,019, now U.S. Pat. No. 8,402,137, entitled CONTENT MANAGEMENT and filed on Aug. 8, 2008, which in turn is a divisional application of U.S. patent application Ser. No. 12/060,213, now U.S. Pat. No. 8,321,568, entitled CONTENT MANAGEMENT and filed on Mar. 31, 2008, the disclosures of which are incorporated herein by reference.
Claims


What is claimed is:

1. A computer-implemented method of processing, at a content delivery network service provider, resource requests from a set of two or more client computing devices, the method comprising: as implemented by one or more computing devices configured with specific executable instructions: determining a class associated with the set of two or more client computing devices; monitoring resource requests for the determined class; providing, to a content provider, information regarding the monitored resource requests for the determined class; obtaining, from the content provider, a grouping of identified content, wherein the identified content is different from, but associated with, the monitored resource requests for the determined class; identifying at least one cache component for providing content identified in the grouping to client computing devices as a function of the determined class; and providing the grouping of identified content to the identified cache component in anticipation of a request for content identified in the grouping.

2. The method of claim 1, wherein the grouping of identified content includes identifications of content without the entirety of the content itself.

3. The method of claim 2 further comprising verifying availability of the content identified in the grouping for delivery by the identified cache component.

4. The method of claim 3 further comprising obtaining content identified in the grouping if the content is not already available at the identified cache component.

5. The method of claim 2 further comprising: selecting content to be loaded at the identified cache component based on the grouping of identified content; verifying availability of the content identified in the grouping for delivery by the identified cache component; and obtaining content identified in the grouping of the content is not already available at the identified cache component.

6. The method of claim 1, wherein the grouping of identified content is a list of resources.

7. The method of claim 6 further comprising verifying availability of the listed resources for delivery by the identified cache component.

8. The method of claim 7 further comprising obtaining one or more of the listed resources if the one or more of the listed resources are not available.

9. The method of claim 6 further comprising: selecting content to be loaded at the identified cache component based on the list of resources; verifying availability of the listed resources for delivery by the identified cache component; and obtaining one or more of the listed resources if the one or more of the listed resources are not available.

10. The method of claim 1, wherein monitoring resource requests for the determined class includes identifying frequently requested content for the determined class and wherein the grouping of identified content is associated with the frequently requested content for the determined class.

11. The method of claim 1 further comprising managing content at the cache component based on the grouping of identified content.

12. The method of claim 11, wherein managing content at the cache component comprises moving at least a portion of content from a first memory of the cache component to a second memory of the cache component.

13. The method of claim 11, wherein managing content at the cache component comprises altering cache control data associated with at least a portion of content in memory of the cache component.

14. The method of claim 11, wherein managing content at the cache component includes obtaining at least a portion of content from a storage location.

15. A computer-implemented method of processing, at a content provider, requests from a content delivery network (CDN) service provider, the method comprising: as implemented by one or more computing devices configured with specific executable instructions: obtaining information from the CDN service provider regarding monitored content requests for a class of two or more client computing devices; identifying content associated with the monitored content requests for the class of two or more client computing devices, wherein the identified content includes content that is currently unsolicited by at least one of the two or more client computing devices; and providing an identification of the identified content to the CDN service provider for use in requesting at least a portion of the identified content to cache in anticipation of a future content request for the identified content.

16. The method of claim 15, wherein the identification of the identified content is a list of content.

17. The method of claim 15, wherein the monitored content requests include information regarding frequently requested content and wherein the identified content is associated with the frequently requested content.

18. A system comprising: a first network point of presence associated with a content delivery network service provider, wherein the first network point of presence comprises at least one computing device including memory and configured with specific instructions, the at least one computing device operative to: determine a class associated with the set of two or more client computing devices; monitor resource requests for the determined class; provide, to a content provider, information regarding the monitored resource requests for the determined class; obtain, from the content provider, a grouping of identified content, wherein the identified content is different from, but associated with, the monitored resource requests for the determined class; identify at least one cache component for providing content identified in the grouping to client computing devices as a function of the determined class; and provide the grouping of identified content to the identified cache component in anticipation of a request for content identified in the grouping.

19. The system of claim 18, wherein the grouping of identified content includes identifications of content without the entirety of the content itself.

20. The system of claim 19, wherein the at least one computing device is further operative to verify availability of the content identified in the grouping for delivery by the identified cache component.

21. The system of claim 19, wherein the at least one computing device is further operative to obtain content identified in the grouping if the content is not already available at the identified cache component.

22. The system of claim 19, wherein the at least one computing device is further operative to: select content to be loaded at the identified cache component based on the grouping of identified content; verify availability of the content identified in the grouping for delivery by the identified cache component; and obtain content identified in the grouping of the content is not already available at the identified cache component.

23. The system of claim 18, wherein the grouping of identified content is a list of resources.

24. The system of claim 18, wherein monitoring resource requests for the determined class includes identifying frequently requested content for the determined class and wherein the grouping of identified content is associated with the frequently requested content for the determined class.

25. The system of claim 18, wherein the at least one computing device is further operative to manage content at the cache component based on the grouping of identified content.
Description


BACKGROUND

Generally described, computing devices and communication networks can be utilized to exchange information. In a common application, a computing device can request content from another computing device via the communication network. For example, a user at a personal computing device can utilize a software browser application to request a Web page from a server computing device via the Internet. In such embodiments, the user computing device can be referred to as a client computing device and the server computing device can be referred to as a content provider.

Content providers are generally motivated to provide requested content to client computing devices often with consideration of efficient transmission of the requested content to the client computing device and/or consideration of a cost associated with the transmission of the content. For larger scale implementations, a content provider may receive content requests from a high volume of client computing devices which can place a strain on the content provider's computing resources. Additionally, the content requested by the client computing devices may have a number of components, which can further place additional strain on the content provider's computing resources.

With reference to an illustrative example, a requested Web page, or original content, may be associated with a number of additional resources, such as images or videos, that are to be displayed with the Web page. In one specific embodiment, the additional resources of the Web page are identified by a number of embedded resource identifiers, such as uniform resource locators ("URLs"). In turn, software on the client computing devices typically processes embedded resource identifiers to generate requests for the content. Often, the resource identifiers associated with the embedded resources reference a computing device associated with the content provider such that the client computing device would transmit the request for the additional resources to the referenced content provider computing device. Accordingly, in order to satisfy a content request, the content provider would provide client computing devices data associated with the Web page as well as the data associated with the embedded resources.

Some content providers attempt to facilitate the delivery of requested content, such as Web pages and/or resources identified in Web pages, through the utilization of a content delivery network ("CDN") service provider. A CDN server provider typically maintains a number of computing devices in a communication network that can maintain content from various content providers. In turn, content providers can instruct, or otherwise suggest to, client computing devices to request some, or all, of the content provider's content from the CDN service provider's computing devices.

As with content providers, CDN service providers are also generally motivated to provide requested content to client computing devices often with consideration of efficient transmission of the requested content to the client computing device and/or consideration of a cost associated with the transmission of the content. Accordingly, CDN service providers often consider factors such as latency of delivery of requested content in order to meet service level agreements or to generally improve the quality of delivery service.

DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram illustrative of content delivery environment including a number of client computing devices, a content provider, and a content delivery network service provider;

FIG. 2 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation and processing of a content request from a client computing device to a content provider;

FIG. 3 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation and processing of a DNS query corresponding to an embedded resource from a client computing device to a content delivery network service provider;

FIG. 4 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation and processing of embedded resource requests from a client computing device to a content delivery network service provider;

FIG. 5 is a block diagram of the content delivery environment of FIG. 1 illustrating the processing and management of associated class information collected by a resource cache component;

FIG. 6 is a block diagram of the content delivery environment of FIG. 1 illustrating another embodiment of the processing and management of associated class information collected by a resource cache component;

FIG. 7 is a block diagram of the content delivery environment of FIG. 1 illustrating yet another embodiment of the processing and management of associated class information collected by a resource cache component;

FIG. 8 is a flow diagram illustrative of a content monitoring routine implemented by a content delivery network service provider for monitoring resource requests from client computing devices; and

FIG. 9 is a flow diagram illustrative a content processing routine implemented by a content delivery network service provider for managing content for delivery to a class of client computing devices.

DETAILED DESCRIPTION

Generally described, the present disclosure is directed to the management and processing of resource requests made to a content delivery network ("CDN") service provider from client computing devices. Specifically, aspects of the disclosure will be described with regard to monitoring resource requests from a cluster of client computing devices and managing content for delivery to one or more client computing devices based on the monitored resource requests for the cluster. Further aspects of the disclosure are directed to monitoring resource requests corresponding to classes associated with client computing devices based on such monitored resource requests. Although various aspects of the disclosure will be described with regard to illustrative examples and embodiments, one skilled in the art will appreciate that the disclosed embodiments and examples should not be construed as limiting.

FIG. 1 is a block diagram illustrative of content delivery environment 100 for the management and processing of content requests. As illustrated in FIG. 1, the content delivery environment 100 includes a number of client computing devices 102 (generally referred to as clients) for requesting content from a content provider and/or a CDN service provider. In an illustrative embodiment, the client computing devices 102 can correspond to a wide variety of computing devices including personal computing devices, laptop computing devices, hand-held computing devices, terminal computing devices, mobile devices, wireless devices, various electronic devices and appliances and the like. In an illustrative embodiment, the client computing devices 102 include necessary hardware and software components for establishing communications over a communication network 108, such as a wide area network or local area network. For example, the client computing devices 102 may be equipped with networking equipment and browser software applications that facilitate communications via the Internet or an intranet.

Although not illustrated in FIG. 1, each client computing device 102 utilizes some type of local DNS resolver component, such as a DNS Name server, that generates the DNS queries attributed to the client computing device. In one embodiment, the local DNS resolver component may be provided by an enterprise network to which the client computing device 102 belongs. In another embodiment, the local DNS resolver component may be provided by an Internet Service Provider (ISP) that provides the communication network connection to the client computing device 102.

The content delivery environment 100 can also include a content provider 104 in communication with the one or more client computing devices 102 via the communication network 108. The content provider 104 illustrated in FIG. 1 corresponds to a logical association of one or more computing devices associated with a content provider. Specifically, the content provider 104 can include a web server component 110 corresponding to one or more server computing devices for obtaining and processing requests for content (such as Web pages) from the client computing devices 102. The content provider 104 can further include an origin server component 112 and associated storage component 114 corresponding to one or more computing devices for obtaining and processing requests for network resources from the CDN service provider. One skilled in the relevant art will appreciate that the content provider 104 can be associated with various additional computing resources, such additional computing devices for administration of content and resources, DNS name servers, and the like. For example, although not illustrated in FIG. 1, the content provider 104 can be associated with one or more DNS name server components that would be authoritative to resolve client computing device DNS queries corresponding to a domain of the content provider.

With continued reference to FIG. 1, the content delivery environment 100 can further include a CDN service provider 106 in communication with the one or more client computing devices 102 and the content providers 104 via the communication network 108. The CDN service provider 106 illustrated in FIG. 1 corresponds to a logical association of one or more computing devices associated with a CDN service provider. Specifically, the CDN service provider 106 can include a number of Point of Presence ("POP") locations 116, 122, 128 that correspond to nodes on the communication network 108. Each POP 116, 122, 128 includes a DNS component 118, 124, 130 made up of a number of DNS server computing devices for resolving DNS queries from the client computers 102. Each POP 116, 122, 128 also includes a resource cache component 120, 126, 132 made up of a number of cache server computing devices for storing resources from content providers and transmitting various requested resources to various client computers. The DNS components 118, 124 and 130 and the resource cache components 120, 126, 132 may further include additional software and/or hardware components that facilitate communications including, but not limited, load balancing or load sharing software/hardware components.

In an illustrative embodiment, the DNS component 118, 124, 130 and resource cache component 120, 126, 132 are considered to be logically grouped, regardless of whether the components, or portions of the components, are physically separate. Additionally, although the POPs 116, 122, 128 are illustrated in FIG. 1 as logically associated with the CDN service provider 106, the POPs will be geographically distributed throughout the communication network 108 in a manner to best serve various demographics of client computing devices 102. Additionally, one skilled in the relevant art will appreciate that the CDN service provider 106 can be associated with various additional computing resources, such as an additional content provider 134, additional computing devices for administration of content and resources, and the like.

One skilled in the relevant art will appreciate that the components and configurations provided in FIG. 1 are illustrative in nature. Accordingly, additional or alternative components and/or configurations, especially regarding the additional components, systems and subsystems for facilitating communications may be utilized.

With reference now to FIGS. 2-4, the interaction between various components of the content delivery environment 100 of FIG. 1 will be illustrated. For purposes of the example, however, the illustration has been simplified such that many of the components utilized to facilitate communications are not shown. One skilled in the relevant art will appreciate that such components can be utilized and that additional interactions would accordingly occur without departing from the spirit and scope of the present disclosure.

With reference to FIG. 2, a client computing device 102 generates a content request that is received and processed by the content provider 104, such as through the Web server 110. In accordance with an illustrative embodiment, the request for content can be in accordance with common network protocols, such as the hypertext transfer protocol ("HTTP"). Upon receipt of the content request, the content provider 104 identifies the appropriate responsive content. In an illustrative embodiment, the requested content can correspond to a Web page that is displayed on the client computing device 102 via the processing of information, such as hypertext markup language ("HTML"), extensible markup language ("XML"), and the like. The requested content can also include a number of embedded resource identifiers that corresponds to resource objects that should be obtained by the client computing device 102 as part of the processing of the requested content. The embedded resource identifiers can be generally referred to as resource identifiers or resource URLs.

In one embodiment, the resource URLs identify the domain of the CDN service provider 106 (e.g., "cdnprovider.com"), the same name of the resource to be requested (e.g., "resource.xxx") and the same path where the resource will be found (e.g., "path"). Additionally, the resource URL can include additional processing information (e.g., "additional information"). The resource URL would have the form of:

http://additional_information.cdnprovider.com/path/resources.xxx

In another embodiment, the information associated with the CDN service provider 106 is included with the resource URL, such as through prepending or other techniques, such that the resource URL can maintain all of the information associated with a URL previously associated with the content provider 104. In this embodiment, the resource URL would have the form of:

http://additional_information.cdnprovider.com/www.contentprovider.com/pat- h/resource.xxx

Upon receipt of the requested content, the client computing device 102, such as through a browser software application, begins processing any of the markup code included in the content and attempts to acquire the resources identified by the embedded resource identifiers. Accordingly, the first step in acquiring the content corresponds to the issuance, by the client computing device 102 (through its local DNS resolver), of a DNS query for the Resource URL resource identifier that results in the identification of a DNS server authoritative to the "." and the "com" portions of the translated URL. After resolving the "." and "com" portions of the embedded URL, the client computing device 102 then issues a DNS query for the resource URL that results in the identification of a DNS server authoritative to the ".cdnprovider" portion of the embedded URL. The issuance of DNS queries corresponding to the "." and the "com" portions of a URL are well known and have not been illustrated.

With reference now to FIG. 3, in an illustrative embodiment, the successful resolution of the "cdnprovider" portion of the resource URL identifies a network address, such as an IP address, of a DNS server associated with the CDN service provider 106. In one embodiment, the IP address can be a specific network address unique to a DNS server component of a POP. In another embodiment, the IP address can be shared by one or more POPs. In this embodiment, a further DNS query provided to the shared IP address utilizes a one-to-many network routing schema, such as anycast, such that a specific POP will receive the request as a function of network topology. For example, in an anycast implementation, a DNS query issued by a client computing device 102 to a shared IP address will arrive at a DNS server component logically having the shortest network topology distance, often referred to as network hops, from the client computing device. The network topology distance does not necessarily correspond to geographic distance. However, in some embodiments, the network topology distance can be inferred to be the shortest network distance between a client computing device 102 and a POP. It will be appreciated by one skilled in the relevant art that a number of ways exist to determine network topology distance.

With continued reference to FIG. 3, in either of the above identified embodiments (or any other embodiment), a specific DNS server in the DNS component 118 of a POP 116 receives the DNS query corresponding to the resource URL from the client computing device 102. Once one of the DNS servers in the DNS component 118 receives the request, the specific DNS server attempts to resolve the request. In one illustrative embodiment as shown in FIG. 3, a specific DNS server resolves the DNS query by identifying an IP address of a resource cache component that will process the request for the requested resource. Upon selection of a resource cache component 120, 126, 132, the DNS server component 118 provides an IP address of the cache server computing device, resource cache component or load balancer/load share device associated with a resource cache component.

With reference now to FIG. 4, the client computing device 102 can then utilize Internet communication protocols to request the resource from a resource cache component identified by the IP address. The resource cache component then processes the request, as will be described in greater detail below, and provides the resource to the client computing device 102. Upon receipt, the requested resource is processed by the browser application on the client computing device 102 as appropriate. It will be appreciated by one skilled in the relevant art that a selected resource cache component 120, 126, 132 can either provide the requested resource if it is available, as described above, or attempt to obtain the requested resource from another source, such as a peer cache server computing device or the origin server 112 of the content provider 104.

With continued reference to FIG. 4, in conjunction with processing the resource request, the resource cache component determines a class associated with the requesting client computing device. In one embodiment, the resource cache component utilizes information received from the client request to determine the class. The class can be determined from the client directly (such as information provided by the client computing device or ISP) or indirectly (such as inferred through a client computing device's IP address). Additionally, the resource cache component can use additional information to determine the class, such as a time zone in which the requesting client computing device is located. The resource cache component associates the class information with the requested content and maintains the associated class information, for example in a log file, for sharing with the CDN service provider 106. In an illustrative embodiment, the determination of class can be statically determined based on predefined class definitions so that the association of the class can be done at the time of receiving resource requests. For example, a geographic location may be known at the time of request processing. In another embodiment, the determination of class can be dynamic and may not be determined (or determinable) at request processing. For example, behavioral classes based on observing behavior over a time window may not be determined until completion of the observation window's processing of the observed data.

In one illustrative embodiment, the class can correspond to a specific geographic region to which the client computing device belongs. In addition or alternatively, the class can correspond to a temporal domain, e.g., time zone, business hours, daytime/nighttime, holidays, and the like. In another embodiment, the class can correspond to a particular subject area, such as a news group, associated with either the requested content or the user or both. Still further the class can correspond to demographic data. Depending on the information to be collected from the requesting client computing device, the resource cache component can determine and maintain this information in a number of ways as will be appreciated by one skilled in the relevant art. Moreover, it will further be appreciated by one skilled in the relevant art that one or more computing devices at the POP where the resource request is received can perform any of the above described functions.

With reference now to FIG. 5, an illustrative embodiment of how the CDN service provider 106 processes and manages the associated class information collected by the resource cache component 132 will be described. The resource cache component 132 provides the associated class information collected at the POP 128 to the CDN service provider 106. The associated class information can then be processed by the CDN service provider in a number of ways. In one embodiment, the CDN service provider can identify content information for providing to a computing device of the CDN based on the associated class information. The identified content information can include a list of frequently requested content based on the associated class information collected at the resource cache component 132. Alternatively, the identified content information can include the frequently requested content itself, as well as additional information associated with the frequently requested content such as network performance metrics, content provider service level agreements, and the like, and/or other corresponding content (for example, corresponding documents, advertisements, and the like, as will be described in further detail below with respect to FIG. 7).

In addition to identifying content information, the CDN service provider 106 can identify a specific cache component 120 for providing this content information to. The identification of the specific cache component may also be based on the associated class information collected at the resource cache component 132. For example, where the class corresponds to a time zone, the CDN service provider may identify a resource cache component 120 that is authorized to service a client computing device having a different time zone. In another embodiment, the CDN service provider could simply send the identified content information to all or a subset of resource cache components of the CDN service provider and allow the cache components to determine how to manage the identified content information.

With continued reference to FIG. 5, in accordance with the present illustrative embodiment, once the associated class information is processed by the CDN service provider, the identified content information is provided to the selected resource cache component 120 which in turn manages the identified content information provided by the CDN service provider 106. In one embodiment, the cache component 120 manages the identified content information by obtaining the content from a storage location in anticipation of subsequent content requests at the cache component 120 for the identified content. In another embodiment, the cache component 120 can move the identified content from disk memory to memory of the cache component 120. In yet another embodiment, the cache component 120 can alter an expiration associated with the identified content in memory of the cache component 120 so as to ensure that the content remains available when later requested by a client computing device. In a yet further embodiment, the cache component 120 can simply verify the availability of the identified content at the cache component.

One skilled in the relevant art will appreciate that any various methodologies or algorithms may be utilized to process and manage the associated class information within the spirit and scope of the present disclosure. The following specific examples will be provided for further illustrative purposes.

In one embodiment, where the class information corresponds to content requests monitored for a set of client computing devices in a region having a first time zone, the CDN service provider processes the class information to identify a set of frequently requested resources in the first time zone. The CDN service provider then preloads content associated with the identified set of frequently requested resources at a cache component which is authorized to service a set of client computing devices in a different time zone. Accordingly, the CDN service provider is able to thereafter provide such preloaded content at lower delivery latencies. One skilled in the relevant art will further appreciate that the cache component authorized for servicing the set of client computing devices located in a different time zone can preload content at any suitable time based on processing constraints applicable to the individual cache component. In addition, it will be yet further appreciated by one skilled in the relevant art that the content may be wholly or partially preloaded at the cache component.

In another illustrative embodiment, the CDN service provider processes the associated class information to identify a list of frequently requested resources and provides this list to a set of resource cache components. Each resource cache component can then individually determine whether to preload one or more of the frequently requested resources.

In a further illustrative embodiment, where the content information is a content list derived from resource requests made by a first cluster of client computing devices and where the content list has been provided to a cache component for servicing a second cluster of client computing devices, the CDN service provider can further monitor whether client computing devices in the second cluster subsequently request content from the list. The CDN service provider can then determine whether modifications should be made to content lists recommended by the first cluster to the second cluster based on the subsequent learned behavior of the second cluster. It will be appreciated by one skilled in the relevant art that a variety of logic may be implemented to monitor such behavior and to update recommendations based thereon.

In a still further illustrative embodiment, the CDN service provider monitors resource requests from a first cluster of client computing devices and identifies a set of content corresponding thereto. The CDN service provider can then manage the identified set of content at a resource cache component authorized to service a second cluster of client computing devices. As set forth above, there are a number of ways to manage the identified set of content, e.g., preloading the content at the resource cache component, verifying availability of content, managing cache control information related to content in memory (e.g., changing expiration data or manipulating expiration variables), and the like. It will further be appreciated by one skilled in the relevant art that the first and second clusters may be the same or different.

In yet another embodiment, the CDN service provider monitors resource requests associated with a class of computing devices and associates the resources requested with the class. The CDN service provider then, in one embodiment, preloads content at a resource cache component of the CDN as a function of the class. This function can involve a matching determination in which the CDN service provider matches a class of the client computing device with a class associated with the resources. For example, the CDN provider may match a topic of interest class, such as basketball scores, with resources that have been associated with the same class based on previous requests. Alternatively, the function can involve a correlation determination in which the CDN service provider correlates a class of the client computing device with a different class associated with the resources. For example, the CDN service provider may correlate a first geographic class, such as New York City, with another geographic class, such as San Francisco. In an illustrative embodiment, determination of matching or correlation may be facilitated through a manual process, such as by an administrator, or based on observed behaviors.

With reference now to FIG. 6, an alternative embodiment directed to how the CDN service provider 106 processes and manages the associated class information collected by the resource cache component 132 will now be described. This embodiment is virtually identical to the embodiments described above in reference to FIG. 5 with the exception that instead of identifying a specific resource cache component for sending the identified content information to, a client computing device is identified. In addition, the subsequent processing functions performed by identified resource cache components in the above embodiments can now be similarly performed by identified client computing devices. In accordance with this alternative embodiment, the CDN service provider 106 includes a client component, such as a software application, for managing the identified content information at the client computing device. The CDN service provider 106 provides the client component to client computing devices desiring to participate in such a service.

With continued reference to FIG. 6, in a specific illustrative embodiment, the resource cache component 132 provides the associated class information collected at the resource cache component 132 to the CDN service provider 106. In this embodiment, the associated class information includes data identifying content corresponding to requests made for a class associated with a first set of client computing devices. Upon receipt of this associated class information, the CDN service provider 106 identifies a second set of client computing devices as a function of the class of the first set of computing devices. The CDN service provider then provides content information related to the resource requests to a client computing device in the second set of client computing devices. In this illustrative embodiment, the content information includes a list of frequently requested content for the class associated with the first set of client computing devices. The client computing device in the second set of devices manages this content information (via a client side application provided by the CDN service provider) by verifying the availability of the listed content and obtaining one or more of the listed resources if not available.

With reference now to FIG. 7, in one embodiment, the CDN service provider 106 may provide the class information collected from the POPs for additional processing. As previously illustrated in FIG. 1, one or more additional content providers 134 may be part of the CDN service provider 106. The additional content providers 134 can correspond to additional components or services associated with the CDN service provider 106, such as advertisement engines or services, recommendation engines or services, security applications or services, and the like. Additionally, although the third party content providers 134 were previously illustrated as part of the CDN service provider 106, one skilled in the relevant art will appreciate that one or more of the third party content providers 134 may be independent.

Based on the class information provided by the CDN service provider 106 or otherwise made available by the CDN service provider 106, the third party content providers 134 can utilize the class information as inputs. For example, in one embodiment, if the third party content provider 134 corresponds to an advertisement engine or component, the class information can be processed to anticipate future advertisement display opportunities at the cache. Accordingly, the third party content provider 134 can process the input and the CDN service provider 106 can take additional steps. In another example, if the third party content provider 134 corresponds to a recommendation engine or component, the class information can be processed to anticipate additional content requests or future content request. Accordingly, the third party content provider 134 can process the input and the CDN service provider 106 can take additional steps. One skilled in the relevant art will appreciate that any various methodologies or algorithms may be utilized to process the class information within the spirit and scope of the present disclosure.

With continued reference to FIG. 7, the additional content provider 134 can provide processed information back to the CDN service provider 106 for further processing. Additionally or alternatively, the additional content provider 134 can provide the processed information directly to one or more POPs, such as POP 116. In either embodiment, the additional action undertaken by the CDN service provider 106 can include notifications of additional advertisement and/or display opportunities, the identification of additional content that can also be preloaded to a resource cache component, and/or the further management of content already stored at the resource cache component.

With reference now to FIG. 8, one embodiment of a content monitoring routine 800 implemented by the CDN service provider 106 for monitoring resource requests from client computing devices will be described. One skilled in the relevant art will appreciate that actions/steps outlined for routine 800 may be implemented by one or many computing devices/components that are associated with the CDN service provider 106. Accordingly, routine 800 has been logically associated as being generally performed by the CDN service provider 106, and thus the following illustrative embodiments should not be construed as limiting.

At block 802, a resource cache component 132 receives a content request from a client computing device. Class information associated with the client computing device is then determined at block 804. In an illustrative embodiment, the determination of class information at block 804 can specifically include associating the requesting client computing device to a first cluster of other client computing devices based on a variety of criteria. In one example, the criteria correspond to a time zone in which the client computing devices are located. Continuing at block 806, the resource cache component further associates the identified class information with the requested content. Next, at block 808, the resource cache component 132 provides information to the CDN service provider 106 regarding the associated class. The routine ends at block 810.

With reference now to FIG. 9, one embodiment of a content processing routine 900 for managing content for delivery to a class of client computing devices will be described. One skilled in the relevant art will appreciate that actions/steps outlined for routine 900 may be implemented by one or many computing devices/components that are associated with the CDN service provider 106. Accordingly, routine 900 has been logically associated as being performed by the CDN service provider 106.

At a block 902, the CDN service provider 106 receives information regarding associated class information, such as that provided from a resource cache component at block 810 of FIG. 8. Next, at a block 904, the CDN service provider 106 processes the received class information. As described above, a variety of logic for processing the received class information can be implemented at the CDN service provider. Continuing with the illustrative embodiment described in reference to FIG. 8, the CDN service provider 106 receives information about resources requests made by client computing devices in a first time zone and processes this information by identifying content for a cache component authorized to service a client computing device in a second time zone based on the resource requests made by client computing devices in the first time zone. For example, the CDN service provider 106 may provide a list of most frequently requested content in the first time zone to the cache component which is authorized to service client computing devices in a second time zone.

Continuing at a block 906 of FIG. 9, the CDN service provider manages content based on the processing performed on the associated class information at block 904. As also set forth above, a variety of logic for managing content can be implemented. In accordance with the present illustrative embodiment, the CDN service provider can manage content based on the processed information by obtaining, at the cache component in the second time zone, the identified content from a storage location or, more specifically, by preloading content from the list at the cache component in anticipation of similar requests from client computing devices in the second time zone. The routine 900 ends at block 908.

It will be appreciated by those skilled in the art and others that while processing and management functions have been described herein as being performed at various components of the CDN service provider, these functions can be distributed across one or more computing devices of the CDN service provider. In addition, the content requests and associated class information monitored at resource cache components can be maintained globally by the CDN service provider and shared with all or some subset of the cache components of the CDN service provider. Similarly, the content information identified based on processing the associated class information can be provided as a batch process to resource cache components or sent in response to a request from one cache component to another.

It will be appreciated by those skilled in the art and others that all of the functions described in this disclosure may be embodied in software executed by one or more processors of the disclosed components and mobile communication devices. The software may be persistently stored in any type of non-volatile storage.

Conditional language, such as, among others, "can," "could," "might," or "may," unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art. It will further be appreciated that the data and/or components described above may be stored on a computer-readable medium and loaded into memory of the computing device using a drive mechanism associated with a computer readable storing the computer executable components such as a CD-ROM, DVD-ROM, or network interface further, the component and/or data can be included in a single device or distributed in any manner. Accordingly, general purpose computing devices may be configured to implement the processes, algorithms and methodology of the present disclosure with the processing and/or execution of the various data and/or components described above.

It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.

* * * * *

References

uspto.report is an independent third-party trademark research tool that is not affiliated, endorsed, or sponsored by the United States Patent and Trademark Office (USPTO) or any other governmental organization. The information provided by uspto.report is based on publicly available data at the time of writing and is intended for informational purposes only.

While we strive to provide accurate and up-to-date information, we do not guarantee the accuracy, completeness, reliability, or suitability of the information displayed on this site. The use of this site is at your own risk. Any reliance you place on such information is therefore strictly at your own risk.

All official trademark data, including owner information, should be verified by visiting the official USPTO website at www.uspto.gov. This site is not intended to replace professional legal advice and should not be used as a substitute for consulting with a legal professional who is knowledgeable about trademark law.

© 2024 USPTO.report | Privacy Policy | Resources | RSS Feed of Trademarks | Trademark Filings Twitter Feed