Source: http://www.google.fr/patents/US9210235
Timestamp: 2017-12-14 04:40:54
Document Index: 569276746

Matched Legal Cases: ['Application No. 2726915', 'Application No. 2741895', 'Application No. 2741895', 'Application No. 200780020255', 'Application No. 200980119993', 'Application No. 200980119995', 'Application No. 3742', 'Application No. 2011', 'Application No. 2011', 'Application No. 2011', 'Application No. 2012', 'Application No. 2013', 'Application No. 2013', 'Application No. 2013', 'Application No. 2013', 'Application No. 10', 'Application No. 201180053405', 'Application No. 201310717573', 'Application No. 201103333', 'Application No. 201301573', 'Application No. 201006873', 'Application No. 200980111426', 'Application No. 200980119993', 'Application No. 2011', 'Application No. 201006837', 'Application No. 201006836', 'Application No. 201006836', 'Application No. 201006837', 'Application No. 201006874', 'Application No. 07754164', 'Application No. 09727694', 'Application No. 09728756', 'Application No. 09729072', 'Application No. 200980111426', 'Application No. 201303521']

Brevet US9210235 - Client side cache management - Google Brevets
A system, method and computer-readable medium for client-side cache management are provided. A client request for content is returned that includes executable code for generating a request for preload information. Based on processing the executable code, a client computing device requests preload information...http://www.google.fr/patents/US9210235?utm_source=gb-gplus-shareBrevet US9210235 - Client side cache management
Numéro de publication US9210235 B2
Numéro de demande US 14/012,387
Date de dépôt 28 août 2013
Autre référence de publication US8533293, US20130346539, US20160088118
Numéro de publication 012387, 14012387, US 9210235 B2, US 9210235B2, US-B2-9210235, US9210235 B2, US9210235B2
Inventeurs Swaminathan Sivasubramanian, David R. Richardson, Bradley Eugene Marshall, Mauricio Alberto Uribe
Citations de brevets (835), Citations hors brevets (121), Référencé par (25), Classifications (4)
US 9210235 B2
1. A computer-implemented method for processing content at a client computing device, the method comprising:
obtaining a set of content for processing on the client computing device, wherein the set of content includes executable code for causing the client computing device to generate a request to an identified service provider for a preload content list;
generating, at the client computing device, a request for the preload content list responsive to the execution of the executable code;
obtaining, from the identified service provider, the requested preload content list, wherein resources identified in the requested preload content list are unrelated at least in part to the set of content;
filtering, at the client computing device, the requested preload content list to identify a subset of resources from the requested preload content list; and
generating, at the client computing device, a request for preloading one or more of the subset of resources identified in the filtered preload content list at the client computing device;
wherein the method is implemented by the client computing device configured with specific executable instructions.
obtaining the one or more of the subset of resources from the filtered preload content list; and
maintaining the one or more of the subset of resources for subsequent use.
4. The computer-implemented method as recited in claim 3, wherein the requested preload content list is associated with the additional information.
5. The computer-implemented method as recited in claim 1, wherein the resources identified in the requested preload content list include resources from previous content requests serviced by one or more cache components of the identified service provider.
9. A computer-implemented method for processing content at a service provider, the method comprising:
under control of one or more computing devices associated with the service provider and configured with specific executable instructions,
obtaining a request, from a client computing device, for a resource and a preload content list;
determining a set of content for identification in the requested preload content list, wherein at least a portion of the set of content identified in the requested preload content list is unrelated to the requested resource;
filtering the determined set of content based on additional information provided by the client computing device to identify a filtered preload content list; and
causing transmission of the filtered preload content list to the client computing device.
a client computing device having specific executable instructions stored in an associated memory and operative to:
obtain a set of content for processing on the client computing device, wherein the set of content includes executable code for causing the client computing device to generate a request to an identified service provider for a preload content list;
generate, at the client computing device, a request for the preload content list responsive to the execution of the executable code;
obtain, from the identified service provider, the requested preload content list, wherein resources identified in the requested preload content list are unrelated at least in part to the set of content;
filter, at the client computing device, the requested preload content list to identify a subset of resources from the requested preload content list; and
generate, at the client computing device, a request for preloading one or more of the subset of resources identified in the filtered preload content list at the client computing device.
19. The system as recited in claim 16, wherein the resources identified in the requested preload content list include resources from previous content requests serviced by one or more cache components of the identified service provider.
a service provider computing device having specific executable instructions stored in an associated memory and operative to:
obtain a request, from a client computing device, for a resource and a preload content list;
determine a set of content for identification in the requested preload content list, wherein at least a portion of the set of content identified in the requested preload content list is unrelated to the requested resource;
filter the determined set of content based on additional information provided by the client computing device to identify a filtered preload content list; and
cause transmission of the filtered preload content list to the client computing device.
This application is a continuation of U.S. patent application Ser. No. 12/060,202, filed Mar. 31, 2008, now U.S. Pat. No. 8,533,293, entitled “CLIENT SIDE CACHE MANAGEMENT,” the disclosure of which is incorporated herein by reference.
FIG. 2 is a block diagram of the content delivery environment of FIG. 1 illustrating the registration of a content provider with a content delivery network service provider and the generation of resource request executable code;
FIG. 4 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation and processing a resource request executable code, by a client computing device, to generate requests for preload information to a content delivery network service provider;
FIG. 5 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation and processing of resource requests from a client computing device, according to preload information;
FIG. 6 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; and
FIG. 7 is a flow diagram illustrative of a resource preload processing routine implemented by a client computing device based on preload information provided by a content delivery network service provider.
Generally described, the present disclosure is directed to the management of resource identifiers utilized by a client computing device to request content from a network resource, such as content delivery network (“CDN”) service providers. Specifically, aspects of the disclosure will be described with regard to the processing, by a client computing device, of a list of resource identifiers provided by the CDN service provider to facilitate the access to such resources by the client computing device. In one embodiment, at least some portion of the identified resources may be preloaded to a client computing device memory to provide access to the resource in advance of the need to generate a request. 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 a content delivery environment 100 for the management of resource identifiers. 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 corresponds 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.
Additionally, the client computing devices 102 may also include necessary hardware and software components to execute, or otherwise process, resource request executable code as will be described in greater detail below. One skilled in the relevant art will appreciate the additional hardware/software components for processing the resource request executable code may be included with the execution of a multi-purpose software application, such as a browser software application. Alternatively, some or all of the additional hardware/software components may be embodied in stand alone or specialized components configured for the processing the resource request executable code.
With reference to FIG. 2, an illustrative interaction for registration of a content provider 104 with the CDN service provider 106 will be described. As illustrated in FIG. 2, the CDN content registration process begins with registration of the content provider 104 with the CDN service provider 106. In an illustrative embodiment, the content provider 104 utilizes a registration application programming interface (“API”) to register with the CDN service provider 106 such that the CDN service provider 106 can provide content on behalf of the content provider 104. The registration API includes the identification of the origin server 112 of the content provider 104 that will provide requested resources to the CDN service provider 106.
With continued reference to FIG. 2, upon receiving the registration API, the CDN service provider 106 obtains the registration information and generates, or otherwise obtains, resource request executable code. In an illustrative embodiment, and as will be explained in greater detail below, the resource request executable code corresponds to data or instructions that are processed by the client computing devices 102 to cause the client computing devices 102 to request a list of resources from the CDN service provider 106. Additionally, the resource request executable code can cause the client computing devices 102 to maintain any of the resources requested from the list so that they are available to the client computing device software applications, such as a browser application (at the present or at some time in the future). In an illustrative embodiment, the resource request executable code can correspond to script-based instructions that are processed by a browser software application on the client computing device 102 that causes the browser software application to request the translation information from the CDN service provider 106. One skilled in the relevant art will appreciate, however, the resource request executable code can be embodied in any one of a variety of executable code formats.
The CDN service provider 106 returns the resource request executable code to the content provider 104 along with any additional information. In turn, the content provider 104 can then store for the resource request executable code for embedding in requested content (such as Web page markup language) or otherwise transmitted to the client computing devices 102. In an illustrative embodiment, the resource request executable code can be applicable to multiple content providers 104. Alternatively, the resource request executable code can be unique to each particular content provider 104. Still further, the CDN service provider 106 may provide additional logic to the content providers 104 that controls the circumstances and/or methodologies for embedding the resource request executable code into content. For example, the resource request executable code can include instructions (or executable code) that defines that the type of content (e.g., specific Web pages) for which the resource request executable code will apply.
With reference now to FIG. 3, after completion of the registration and embedding processes illustrated in 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 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. Generally, the identification of the resources provided by the content provider 104 will be in the form of a resource identifier that can be processed by the client computing device 102, such as through a browser software application. In an illustrative embodiment, the resource identifiers can be in the form of a uniform resource locator (“URL”). Additionally, the requested content will also include the embedded resource request executable code previously provided by the CDN service provider 106. In an illustrative embodiment, the embedded execution code can be arranged in a manner such that it is processed prior to processing any other of the content in the requested content or processed in the earlier stages of the processing of the requested content, as allowed. Alternatively, the embedded execution code can also be arranged such that it can be parsed by the client computing device 102 from the other requested content.
With reference now to FIG. 4, upon receipt of the requested content, including the embedded resource identifiers and the resource request executable code, the client computing device 102 processes the resource request executable code in a manner that causes the client computing device 102 to request preload information or a listing of resources that may be preloaded from the CDN service provider 106. As described above, the resource request executable code can include script-based instructions and information that instructs a browser software application on the client computing device 102 to generate the request for preload information. The preload information request can include information identifying the content provider 104, the specific client computing device 102, the type/size of requested content (e.g. large image files), and additional information that could be used by the CDN service provider 106 to determine a list of resources to be downloaded by the client computing device.
In an illustrative embodiment, the CDN service provider 106 utilizes information corresponding to the monitoring of previous client computing device requests to the resource cache components of the CDN service provider 106 in generating the preload list. The CDN service provider 106 can further use class or clustering information in selecting the resources identified in the list of resources. Although the preload request is illustrated in FIG. 4 as directed toward the CDN service provider 106 in general, one skilled in the relevant art will appreciate that the preload request from the client computing device may be directed toward a specific POP or set of POPs provided by the CDN service provider 106. The selection of appropriate recipients can be based on a variety of factors, including, but not limited to, network topology, service level agreements, geography, and the like.
Upon receipt of the translation information request, the CDN service provider 106, such as through a POP 116, generates preload information that will be used to request additional resources by the client computing device. The preload information can also include rules or other information that specifies the applicability of the resources to be requested, additional instructions regarding the resources once they have been received, expiration timeframes for the preload information, filtering information for the return resource list, and the like. The preload information is then returned to the requesting client computing device 102. In an illustrative embodiment, the client computing device 102 can request the resources identified in the preload information, as described below, if the resource has not been previously stored in a storage location at the client computing device 102, such as a memory. Alternatively, if the resource has been previously stored, the client computing device may manipulate the resource, such as by moving the resource from one storage location (e.g., hard disk) to another storage location (e.g., memory). Still further, the client computing device 102 may manipulate storage controls, such as a cache control, to ensure that content previously stored by the client computing device 102 remains available. Still further, in another embodiment, the preload list can include some portion of the content to be requested/maintained by the client computing device 102.
With reference now to FIG. 5, an embodiment in which at least one resource on the preload list has not been previously downloaded will be described. The client computing device 102 receives and processes the preload information from the CDN service provider 106. In one embodiment, the preload information can include data, or other information, that is processed by code existing on the client computing device 102 in a manner as will be described below. For example, the client computing device 102 may be executing a software application configured specifically for the processing of the preload information. Similarly, the resource request executable code previously executed by the client computing device 102 may include executable instructions for processing the preload information and/or the requested resources once they are received by the client computing device 102. For example, the resource request executable code can specify or instruct a browser application to store the received resources in a storage location, such as memory. The stored resources would then be available for use by the browser application. One skilled in the relevant art will appreciate that the resource request transmitted by the client computing device 102 to the CDN service provider 106 could be processed by a particular POP or set of POPs provided by the CDN service provider 106.
As described above, in an illustrative embodiment, the resources identified by the CDN service provider 106 in the preload information correspond to resources from previously serviced resource requests serviced by the CDN service provider. In one example, the previously serviced resource requests correspond to resource requests previously submitted by the specific client computing device 102. In another example, the previously serviced resource requests correspond to resource requests previously submitted by a cluster or class of a set of computing devices. In still a further example, the previously serviced resource requests corresponds to resource request previously submitted by a cluster or class of a set of computing devices that match or correlate to a cluster or class associated with the client computing device. With additional processing, the preload information can include resources identified in accordance with the above techniques.
With reference now to FIG. 6, an illustrative embodiment of how the CDN service provider 106 processes and manages 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 106 in a number of ways. In one embodiment, the CDN service provider 106 can identify content information for providing to a requesting client computing device 102 based, at least in part, on the associated class information. Alternatively, as previously described, the identified content information can include the frequently requested content itself.
Referring to FIG. 6, a resource cache component, such as resource cache component 132 of POP 128, utilizes information received from previous client computing device requests to associate class information to the resource requests. 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 temporal domain (e.g., a time zone) in which the requesting client computing device 102 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 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.
Based on the above description of class or cluster information, CDN service provider 106 can match or correlate a class of a requesting client computing device 102 (FIG. 4) with a class associated with the resources in determining whether to include such resources in the preload list. For example, the CDN provider 106 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. The class of the client computing device 102 may be obtained through a user profile of a user associated with the client computing device and/or through subject matter associated with the content request submitted by the client computing device.
Alternatively, the function can involve a correlation determination in which the CDN service provider correlates a class of the requesting client computing device 102 with a different class associated with the resources. For example, the CDN service provider 106 may correlate a first geographic class, such as New York City, with another geographic class, such as San Francisco. In this case, the CDN service provider 106 would make some associations regarding the New York City geographic class is sufficiently similar to the San Francisco class to merit an association. 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. 7, a resource identifier processing routine 700 implemented by a client computing device 102 to process embedded resource identifiers with translation information will be described. At block 702, client computing device 102 transmits the request for content. As described above, the request for content may be directed to a Web server 110 of the content provider 104. At block 704, the client computing device 102 obtains responsive content that includes resource request executable code. As described above, in an illustrative embodiment, the resource request executable code can correspond to script-based instructions that can be processed by a software application running on the client computing device 102.
At block 706, the client computing device 102 transmits the request for preload information to the CDN service provider 106 identified in the resource request executable code. As previously described, the request for preload information can include information that may be used by the CDN service provider 106 to generate, or select, the translation information. The additional information may be specifically included in the request for translation or inferred from aspects of the request (e.g., IP address of the client computing device 102). The CDN service provider 106 can utilize class information or clustering information to select the resources that will be included in the preload information. The utilization of such class or cluster information facilitates the identification of resources that may not have any relation to the current set of resources to be displayed by the client computing device 102. At block 708, the client computing device 102 obtains resource information from the CDN service provider 106.
At block 710, the client computing device 102 processes the resource identifiers, or other information, with the preload information. In a further illustrative embodiment, the client computing device 102 can maintain a history of whether previous resource requests for content based on a preload list provided by the CDN provider 106 were utilized. Accordingly, the client computing device 102 can provide some additional filtering or processing based on the history. For example, if the CDN provider 106 provides selects content according to subject matter class, the client computing device 102 may filter this type of content to prevent that content from being preloaded. The filtering may be manually configured or configured by executable code on the client computing device 102 monitoring the preload requests. Additionally, the client computing device 102 can provide feedback to the CDN service provider 106 for adjustments to the preload matching algorithms or methodologies. 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.
At block 712, the client computing device 102 transmits requests for the resources associated with the resource identifiers. In an illustrative embodiment, the request for the resources associated with the translated URLs can be facilitated through various networking protocols. As set forth above, in an alternative embodiment, there are a number of ways to manage the identified set of content, e.g., preloading the content at the client computing device 102, 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. Accordingly, the processing for content at block 712 may be omitted or otherwise managed differently if the identified content is already in a client computing device memory. At block 714, the routine 700 terminates.
US7321918 * 14 oct. 2004 22 janv. 2008 Microsoft Corporation Server-side control objects for processing client-side user interface elements
US20020068554 * 9 avr. 1999 6 juin 2002 Steve Dusse Method and system facilitating web based provisioning of two-way mobile communications devices
US20020092026 * 14 août 2001 11 juil. 2002 International Business Machines Corporation Method and apparatus for broadcast delivery of content to a client-side cache based on user preferences
US20040024841 * 28 juin 2002 5 févr. 2004 International Business Machines Corporation Systems and methods for displaying and executing web services in multiple content domains
US20040267906 * 26 juin 2003 30 déc. 2004 International Business Machines Corporation Systems and methods for adjusting caching policies for web service requests
US20060218256 13 juil. 2005 28 sept. 2006 Tetsuya Maruyama Information processing system having volume guard function
US20080046596 * 30 oct. 2007 21 févr. 2008 Afergan Michael M Method for caching and delivery of compressed content in a content delivery network
US20080201332 * 20 févr. 2007 21 août 2008 Souders Steven K System and method for preloading content on the basis of user context
US20090248893 * 31 mars 2008 1 oct. 2009 Richardson David R Request routing
US20090307307 * 7 mars 2007 10 déc. 2009 Tatsuya Igarashi Content providing system, information processing apparatus, information processing method, and computer program
56 Gunther et al, "Measuring Round Trip Times to determine the Distance between WLAN Nodes",May2005, In Proc. Of Networking 2005, all pages.
68 Kato, Yoshinobu , Server load balancer-Difference in distribution technique and supported protocol-Focus on function to meet the needs, Nikkei Communications, Japan, Nikkei Business Publications, Inc., Mar. 20, 2000, vol. 314, pp. 114-123 (No Eng Trans).
72 Mulligan et al.; How DRM-based content delivery systems disrupt expectations of "personal use"; Published in: Proceeding DRM '03 Proceedings of the 3rd ACM workshop on Digital rights management; 2003; pp. 77-89; ACM Digital Library.
73 Office Action in Canadian Application No. 2726915 dated May 13, 2013.
74 Office Action in Canadian Application No. 2741895 dated Feb. 25, 2013.
75 Office Action in Canadian Application No. 2741895 dated Oct. 21, 2013.
76 Office Action in Chinese Application No. 200780020255.2 dated Mar. 4, 2013.
77 Office Action in Chinese Application No. 200980119993.1 dated Oct. 21, 2013.
78 Office Action in Chinese Application No. 200980119995.0 dated Apr. 15, 2013.
79 Office Action in Indian Application No. 3742/KOLNP/2008 dated Nov. 22, 2013.
80 Office Action in Japanese Application No. 2011-502138 mailed Feb. 1, 2013.
81 Office Action in Japanese Application No. 2011-502140 mailed Dec. 7, 2012.
82 Office Action in Japanese Application No. 2011-516466 mailed Mar. 6, 2013.
83 Office Action in Japanese Application No. 2012-052264 mailed Dec. 11, 2012 in 26 pages.
84 Office Action in Japanese Application No. 2013-123086 mailed Apr. 15, 2014 in 3 pages.
85 Office Action in Japanese Application No. 2013-123086 mailed Dec. 2, 2014 in 2 pages.
86 Office Action in Japanese Application No. 2013-529454 dated Mar. 9, 2015 (Eng Translation Not Yet Received).
87 Office Action in Japanese Application No. 2013-540982 dated Jun. 2, 2014 English Translation Not Yet Received.
88 Office Action in Korean Application No. 10-2011-7002461 mailed May 29, 2013.
89 Preliminary Examination in Chinese Application No. 201180053405.6 dated May 28, 2013. English Translation Not Yet Received.
90 Preliminary Examination in Chinese Application No. 201310717573.1 dated Feb. 25, 2014. English Translation Not Yet Received.
91 Search Report and Written Opinion in Singapore Application No. 201103333-9 mailed Nov. 19, 2012.
92 Search Report and Written Opinion in Singapore Application No. 201301573-0 mailed Jul. 1, 2014.
93 Search Report and Written Opinion issued in Singapore Application No. 201006873-2 mailed on Oct. 12, 2011.
94 Second Office Action in Chinese Application No. 200980111426.1 mailed Dec. 25, 2013.
95 Second Office Action in Chinese Application No. 200980119993.1 dated Mar. 12, 2013.
96 Second Office Action in Japanese Application No. 2011-516466 mailed Mar. 17, 2014.
97 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-22-5057752.html, 8 pages.
98 Singapore Examination Report in Application No. 201006837-7 mailed May 16, 2012.
99 Singapore Written Opinion in Application No. 201006836-9, mailed Apr. 30, 2012 in 10 pages.
100 Singapore Written Opinion in Application No. 201006836-9, mailed Oct. 12, 2011 in 12 pages.
101 Singapore Written Opinion in Application No. 201006837-7, mailed Oct. 12, 2011 in 11 pages.
102 Singapore Written Opinion in Application No. 201006874-0, mailed Oct. 12, 2011 in 10 pages.
103 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/~lars/studies/master/StrandLars-master.pdf, 158 pages.
104 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/˜lars/studies/master/StrandLars-master.pdf, 158 pages.
105 Supplementary European Search Report in Application No. 07754164.7 mailed Dec. 20, 2010 in 7 pages.
106 Supplementary European Search Report in Application No. 09727694.3 mailed Jan. 30, 2012 in 6 pages.
107 Supplementary European Search Report in Application No. 09728756.9 mailed Jan. 8, 2013.
108 Supplementary European Search Report in Application No. 09729072.0 2266064 dated Dec. 10, 2014.
109 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.
110 Tan et al., "Classification: Basic Concepts, Decision Tree, and Model Evaluation", Introduction in Data Mining; http://www-users.cs.umn.edu/~kumar/dmbook/ch4.pdf, 2005, pp. 245-205.
111 Tan et al., "Classification: Basic Concepts, Decision Tree, and Model Evaluation", Introduction in Data Mining; http://www-users.cs.umn.edu/˜kumar/dmbook/ch4.pdf, 2005, pp. 245-205.
112 Third Office Action in Chinese Application No. 200980111426.1 mailed Jul. 7, 2014.
113 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.
114 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.
115 Virtual Iron Software Home, Virtual Iron, retrieved May 3, 2006, from http://www.virtualiron.com/, 1 page.
116 Waldspurger, CA., "Spawn: A Distributed Computational Economy," Feb. 1992, IEEE Transactions on Software Engineering, 18(2): 103-117, 15 pages.
117 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.
118 Written Opinion in Singapore Application No. 201303521-7 dated May 20, 2014.
119 Xu et al., "Decision tree regression for soft classification of remote sensing data", Remote Sensing of Environment 97 (2005) pp. 322-336.
120 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.
121 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://wvvvv.hpl.hp.com/techreports/2005/HPL-2005-193R1.pdf, 9 pages.
Classification coopérative H04L67/42, H04L67/2847, H04L67/2842