US 8,788,671 B2Grant
Managing content delivery network service providers by a content broker
Issue Date:2014-07-22
•28 Claims
•8 Drawing Sheets
Abstract
A system, method, and computer readable medium for managing network storage provider and CDN service providers are provided. A content broker component obtains client computing device requests for content provided by a content provider. The content broker processes the client computing device requests and determines whether a subsequent request for the resource should be directed to a network storage provider or a CDN service provider as a function of the updated or processed by the content broker.
Metadata
Assignee
- Amazon Technologies, Inc.
Inventors
- David R. Richardson
- Bradley E. Marshall
- Swaminathan Sivasubramanian
- Tal Saraf
- Imran S. Patel
Application Information
Application Number:US 13/358,478
Filing Date:2012-01-25
Priority Date:2008-11-17
Art Unit:2456
Classifications
IPC:
G06F15/173
Patent Drawings (8 sheets)
Description
Cross Reference to Related Applications
[0001] This application is a continuation of U.S. patent application Ser. No. 12/272,715, now U.S. Pat. No. 8,122,098, entitled “MANAGING CONTENT DELIVERY NETWORK SERVICE PROVIDERS BY A CONTENT BROKER” and filed on Nov. 17, 2008, the disclosure of which is incorporated herein by reference.
Background
[0002] 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.
[0003] 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.
[0004] 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, which 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(s) (or any service provider on behalf of the content provider(s)) would provide client computing devices data associated with the Web page and/or the data associated with the embedded resources.
[0005] 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 network storage provider or a content delivery network (“CDN”) service provider. A network storage provider and a CDN server provider each typically maintain 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 network storage provider's or CDN service provider's computing devices.
[0006] As with content providers, network storage providers and 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
[0007] 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:
[0008] FIG. 1 is a block diagram illustrative of content delivery environment including a number of client computing devices, a content provider, a network storage provider, a content delivery network service provider, and a content broker;
[0009] FIG. 2 is a block diagram of the content delivery environment of FIG. 1 illustrating the registration of a content provider with a content broker;
[0010] FIG. 3A is a block diagram of the content delivery environment of FIG. 1 illustrating the generation and processing of a resource request by a client computing device to a content provider;
[0011] FIG. 3B is a block diagram of the content delivery environment of FIG. 1 illustrating the processing of a resource request by a content broker;
[0012] FIG. 4A is a block diagram of the content delivery environment of FIG. 1 illustrating the generation and processing of a resource request by a client computing device to a content broker;
[0013] FIG. 4B is a block diagram of the content delivery environment of FIG. 1 illustrating the processing of a resource request by a content broker upon receiving the resource request from a client computing device; and
[0014] FIG. 5 is a flow diagram illustrative of a resource DNS query processing routine implemented by a content broker.
Detailed Description
[0015] Generally described, the present disclosure is directed to delivery of one or more resources associated with a content provider by selecting from available storage service providers and content delivery network (“CDN”) service providers. Specifically, aspects of the disclosure will be described with regard to the management of resource delivery by a content broker component on behalf of a content provider as a function of request processing criteria. In one aspect, the content broker can automatically direct client computing device requests for a resource to a selected service provider (e.g., a selected network storage provider or a selected CDN service provider) as a function of request processing criteria. In another aspect, the content broker can provide recommendations to the content provider regarding the selected network storage provider or CDN service provider.
[0016] In an illustrative embodiment, the request processing criteria can correspond to a financial cost attributed to the content provider for delivery of requested resources by the network storage provider or a CDN service provider. The request processing criteria can also correspond to quality of service characteristics associated with the delivery of requested resources by a network storage provider or CDN service provider including, but not limited to a volume of client computing device resource requests made to the network storage provider, available communication network bandwidth or communication network bandwidth utilization, measured or estimated latencies, error rates or counts, and the like. Still further, the request processing criteria can correspond to content provider or client computing device specified information, such as end user specified feedback. 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.
[0017] FIG. 1 is a block diagram illustrative of content delivery environment 100 for managing registration of content with one or more service providers and subsequent 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, a content broker 111, one or more network storage providers 110, and/or one or more CDN service providers 106. 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.
[0018] Although not illustrated in FIG. 1 , each client computing device 102 utilizes some type of local DNS resolver component, such as a DNS nameserver, 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.
[0019] 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 112 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 114 and associated storage component 116 corresponding to one or more computing devices for obtaining and processing requests for network resources. One skilled in the relevant art will appreciate that the content provider 104 can be associated with various additional computing resources, such as additional computing devices for administration of content and resources, DNS nameservers, and the like. For example, as further illustrated in FIG. 1 , the content provider 104 can be associated with one or more DNS nameserver components 118 that are operative to receive DNS queries related to registered domain names associated with the content provider. The one or more DNS nameservers can be authoritative to resolve client computing device DNS queries corresponding to the registered domain names of the content provider 104. A DNS nameserver component is considered to be authoritative to a DNS query if the DNS nameserver can resolve the query by providing a responsive IP address. Additionally, the content provider 104 may include multiple components or eliminate some of the components altogether, such as origin server 114.
[0020] With continued reference to FIG. 1 , the content delivery environment 100 can further include one or more CDN service providers 106 in communication with the one or more client computing devices 102, the content provider 104, the content broker 111, and the one or more network storage providers 110 via the communication network 108. Each 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 120, 126, 132 that correspond to nodes on the communication network 108. Each POP 120, 126, 132 includes a DNS component 122, 128, 134 made up of a number of DNS nameserver computing devices for resolving DNS queries from the client computers 102. Each POP 120, 126, 132 also includes a resource cache component 124, 130, 136 made up of a number of cache server computing devices for storing resources from content providers, content brokers, or network storage providers and transmitting various requested resources to various client computers. The DNS components 122, 128, 134 and the resource cache components 124, 130, 136 may further include additional software and/or hardware components that facilitate communications including, but not limited to, load balancing or load sharing software/hardware components.
[0021] In an illustrative embodiment, the DNS component 122, 128, 134 and resource cache component 124, 130, 136 are considered to be logically grouped, regardless of whether the components, or portions of the components, are physically separate. Additionally, although the POPs 120, 126, 132 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 additional computing devices for administration of content and resources, and the like.
[0022] With further continued reference to FIG. 1 , the content delivery environment 100 can also include one or more network storage providers 110 in communication with the one or more client computing devices 102, the one or more CDN service providers 106, the content broker 111, and the content provider 104 via the communication network 108. Each network storage provider 110 illustrated in FIG. 1 also corresponds to a logical association of one or more computing devices associated with a network storage provider. Specifically, the network storage provider 110 can include a number of network storage provider Point of Presence (“NSP POP”) locations 138, 142, 146 that correspond to nodes on the communication network 108. Each NSP POP 138, 142, 146 includes a storage component 140, 144, 148 made up of a number of storage devices for storing resources from content providers or content brokers which will be processed by the network storage provider 110 and transmitted to various client computers. The storage components 140, 144, 148 may further include additional software and/or hardware components that facilitate communications including, but not limited to, load balancing or load sharing software/hardware components.
[0023] In an illustrative embodiment, the storage components 140, 144, 148 are considered to be logically grouped, regardless of whether the components, or portions of the components, are physically separate. Additionally, although the NSP POPs 138, 142, 146 are illustrated in FIG. 1 as logically associated with the network storage provider 110, the NSP 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 network storage provider 110 can be associated with various additional computing resources, such as additional computing devices for administration of content and resources, DNS nameservers, and the like. For example, the network storage provider 110 can be associated with one or more DNS nameserver components that are operative to receive DNS queries related to registered domain names associated with the network storage provider 110. The one or more DNS nameservers can be authoritative to resolve client computing device DNS queries corresponding to the registered domain names of the network storage provider 110. As similarly set forth above, a DNS nameserver component is considered to be authoritative to a DNS query if the DNS nameserver can resolve the query by providing a responsive IP address.
[0024] With further continued reference to FIG. 1 , the content delivery environment 100 can also include a content broker 111 in communication with the one or more client computing devices 102, the one or more CDN service providers 106, the one or more network storage providers 110, and the content provider 104 via the communication network 108. The content broker 111 illustrated in FIG. 1 also corresponds to a logical association of one or more computing devices associated with a content broker. Specifically, the content broker 111 can include a web server component 154 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 in embodiments in which the content broker provides original responsive content (e.g., Web pages) on behalf of the content provider, such as in the form of original hypertext markup language (“HTML”) files. The content broker 111 can further include a storage management (“SM”) component 152 for monitoring requests for resources and selecting one or more service providers (e.g., a selected network storage provider 110 or a selected CDN service provider 106) to process subsequent client computing device requests for the resources. The content broker 111 can also utilize the SM component 152 to provide selected service provider recommendations to the content provider(s) 104, such as via a Web service or other interface.
[0025] One skilled in the relevant art will appreciate that the content broker 111 can be associated with various additional computing resources, such as additional computing devices for administration of content and resources, DNS nameservers, and the like. For example, as further illustrated in FIG. 1 , the content broker 111 can be associated with one or more DNS nameserver components 150 that are operative to receive DNS queries related to registered domain names associated with the content broker 111. As will be further described below, the one or more DNS nameserver components 150 can be authoritative to resolve client computing device DNS queries corresponding to the registered domain names of the content broker 111. As similarly set forth above, a DNS nameserver component is considered to be authoritative to a DNS query if the DNS nameserver can resolve the query by providing a responsive IP address.
[0026] Even further, one skilled in the relevant art will appreciate that the components of the network storage provider 110, the CDN service provider 106, and the content broker 111 can be managed by the same or different entities. One skilled in the relevant art will also 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.
[0027] With reference now to FIGS. 2-4B , 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.
[0028] With reference to FIG. 2 , an illustrative interaction for registration of a content provider 104 with the content broker 111 will be described. As illustrated in FIG. 2 , the content broker content registration process begins with registration of the content provider 104 with the content broker 111. In an illustrative embodiment, the content provider 104 utilizes a registration application program interface (“API”) to register with the content broker 111 such that the content broker 111 can facilitate use of one or more service providers, such as CDN service provider 106 or network storage provider 110, to provide content on behalf of the content provider 104.
[0029] In one embodiment, the content provider 104 may also request that the content broker 111 provide content on its behalf, especially when the content provider 104 does not have its own DNS component. In this embodiment, the content provider 104 may request the content broker 111 to provide original responsive content on behalf of the content provider, such as Web pages in the form of HTML files. The registration API can also include the identification of the origin server 114 of the content provider 104 that may provide requested resources, such as embedded resources, to the service providers 106 and 110. In addition or alternatively, the registration API can include the content to be stored and/or provided by the service providers 106 and/or 110 on behalf of the content provider 104. In one embodiment, the content broker 111 may facilitate using the network storage provider 110 as an origin server for the content provider 104.
[0030] One skilled in the relevant art will appreciate that upon registration of the content with the content broker 111, the content provider 104 can begin to direct requests for content from client computing devices 102 to the content broker 111. Specifically, in accordance with DNS routing principles, and as will be described in further detail below, a client computing device request corresponding to a resource identifier would initially be directed to a content broker domain (e.g., a domain registered to, or otherwise associated with the content broker 111) and would then be directed toward a domain associated with a selected service provider, such as CDN service provider 106 or network storage provider 110. Alternatively, based on recommendations provided by the content broker 111, the content provider 104 can direct (or have directed) requests to the selected service provider by translating the resource identifier directly to a domain associated with the selected service provider.
[0031] With continued reference to FIG. 2 , upon receiving the registration API, the content broker 111 obtains and processes the content provider registration information. In an illustrative embodiment, the content broker 111 can then generate additional information that will be used by the client computing devices 102 as part of the content requests. The additional information can include, without limitation, content provider identifiers, such as content provider identification codes, service provider identifiers, such as service provider identification codes, content broker identifiers, such as content broker specified identification codes, executable code for processing resource identifiers, such as script-based instructions, and the like. One skilled in the relevant art will appreciate that various types of additional information may be generated by the content broker 111 and that the additional information may be embodied in any one of a variety of formats.
[0032] In an embodiment in which the content broker 111 facilitates that selection of a service provider, the content broker 111 returns an identification of applicable domains for the content broker (unless it has been previously provided) and any additional information to the content provider 104. In turn, the content provider 104 can then process the stored content with content broker specific information. In one example, as illustrated in FIG. 2 , the content provider 104 translates resource identifiers originally directed toward a domain of the origin server 114 to a domain corresponding to the content broker 111. The translated URLs are embedded into requested content in a manner such that DNS queries for the translated URLs will be processed by a DNS nameserver, such as DNS nameserver 150, corresponding to the content broker 111 and not a DNS nameserver corresponding to the content provider 104, such as DNS nameserver 118.
[0033] Generally, the identification of the resources originally directed to 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”). Because the resource identifiers are included in the requested content directed to the content provider, the resource identifiers can be referred to generally as the “content provider URL.” For purposes of an illustrative example, the content provider URL can identify a domain of the content provider 104 (e.g., contentprovider.com), a name of the resource to be requested (e.g., “resource.xxx”) and a path where the resource will be found (e.g., “path”). In this illustrative example, the content provider URL has the form of:
[0034] http://www.contentprovider.com/path/resource.xxx
[0035] During an illustrative translation process, the content provider URL is modified such that requests for the resources associated with the modified URLs resolve to the content broker 111. In one embodiment, the modified URL identifies the domain of the content broker 111 (e.g., “contentbroker.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 modified URL can include additional processing information (e.g., “additional information”). The modified URL would have the form of:
[0036] http://additional information.contentbroker.com/path/resource.xxx
[0037] In another embodiment, the information associated with the content broker 111 is included in the modified URL, such as through prepending or other techniques, such that the translated URL can maintain all of the information associated with the original URL. In this embodiment, the translated URL would have the form of:
[0038] http://additional information.contentbrokencom/www.contentprovider.com/path/resource.xxx
[0039] In an illustrative embodiment, the content broker 111 can facilitate the registration of one or more network storage providers 110 and one or more CDN service providers 106 to host content or provide content on behalf of the content provider 104. In one example, the content broker 111 generates (or causes the generation) of various user interfaces for facilitating the selection and registration of the one or more network storage providers 110 and one or more CDN service providers 106. In another example, the content broker 111 can utilize various APIs to facilitate the selection and registration of the one or more network storage providers 110 and one or more CDN service providers 106. The APIs may be processed by the content provider 104 and the content broker 111 such that the selection and registration of the one or more network storage providers 110 and one or more CDN service providers 106 can be completed without requiring additional human interaction, such as via a system administrator. Illustrative systems, methods and interfaces for facilitating the selection and registration of one or more network storage providers 110 and one or more CDN service providers 106 by a content broker 111 are described in commonly assigned and co-pending U.S. patent application Ser. No. 12/272,641, entitled Storage Provider Registration by a Content Broker, filed Nov. 17, 2008, which is incorporated in its entirety by reference herein.
[0040] With reference now to FIG. 3A , after completion of the registration and translation processes illustrated in FIG. 2 , a first client computing device 102A subsequently generates a content request that is received and processed by the content provider 104, such as through the Web server 112. 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 and transmits the appropriate responsive content to the client computing device 102A. In an illustrative embodiment, the requested content can correspond to a Web page that is displayed on the client computing device 102A via the processing of information, such as HTML, XML, and the like. The requested content can also include a number of embedded resource identifiers, described above, that corresponds to resource objects that should be obtained by the client computing device 102A as part of the processing of the requested content. The embedded resource identifiers can be generally referred to as original resource identifiers or original URLs.
[0041] With reference now to FIG. 3B , upon receipt of the requested content, the client computing device 102A, 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 102A (through its local DNS resolver), of a DNS query for the original URL resource identifier that results in the identification of a DNS nameserver authoritative to the “.” and the “corn” portions of the translated URL. Pursuant to an embodiment in which the translated URLs are directed to the content broker 111, after processing the “.” and “corn” portions of the embedded URL, the client computing device 102A then issues a DNS query for the resource URL that results in “.contentbroker” 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.
[0042] In an illustrative embodiment, the identification of a DNS nameserver authoritative to the “contentbroker” corresponds to an IP address of a DNS nameserver associated with the content broker 111. In one embodiment, the IP address is a specific network address unique to a DNS nameserver component of the content broker 111. In another embodiment, the IP address can be shared by one or more components of the content broker 111. In this embodiment, a further DNS query to the shared IP address utilizes a one-to-many network routing schema, such as anycast, such that a specific component of the content broker 111 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 102A to a shared IP address will arrive at a DNS nameserver component of the content broker 111 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 102A and a content broker component.
[0043] With continued reference to FIG. 3B , once one of the DNS nameservers in the content broker 111 receives the request, the receiving DNS nameserver attempts to resolve the request. The receiving DNS nameservers of the content broker 111 can be authoritative to resolve client computing device DNS queries corresponding to the registered domain names of the content broker 111. As similarly set forth above, a DNS nameserver is considered to be authoritative to a DNS query if the DNS nameserver can resolve the query by providing a responsive IP address. As will be explained in detail below, to resolve the DNS query, the content broker 111 can maintain request processing criteria, or requesting processing information, regarding the processing of requests for each resource, or a subset of resources, provided by the content provider 104. In an illustrative embodiment, the content broker 111 utilizes the request processing criteria to determine whether a subsequent request for the resource should be processed by a network storage provider 110 or whether the subsequent request for the resource should be processed by a CDN service provider 106.
[0044] Illustratively, the request processing criteria can include the total number of requests obtained by the content broker 111 (measured directly or indirectly) for a resource over a defined period of time, trends regarding an increase/decrease in requests for the resource, a current financial cost associated with the delivery of the resource by the network storage provider, quality of service metrics measured by the network storage provider 110 or CDN service provider 106, additional criteria provided by the content provider 104, and various combinations or alternatives thereof.
[0045] In one illustrative embodiment, a specific DNS nameserver of the content broker 111 can resolve the DNS query by identifying an IP address of a service provider storage component, such as CDN resource cache components 124, 130, 136 or network storage provider storage component 140, 144, 148 (FIG. 1 ), that will further process the request for the requested resource. As described above, the selection of a service provider and the selection of an IP address of the selected service provider can be based, at least in part, as a function of the request processing criteria. Examples of the selection of a service provider and service provider storage components as a function of the request processing criteria will be described in detail with regard to FIG. 5 .
[0046] As an alternative to resolving the received DNS query by providing the IP addresses of a service provider storage component that will attempt to provide an embedded resource, the content broker 111 can maintain sets of various alternative resource identifiers based on service provider registration information received from the service providers, such as the CDN service provider 106 or the network storage provider 110. The alternative resource identifiers can be provided by the content broker 111 to the client computing device 102A such that a subsequent DNS query on the alternative resource identifier will resolve to a DNS nameserver component within a selected service provider's network. In this embodiment, a DNS nameserver associated with the content broker 111 (directly or indirectly) is able to receive the DNS query (corresponding to the domain in the embedded resource). However, as discussed above, because the DNS nameserver does not provide a responsive IP address to the query, it is not considered authoritative to the DNS query. Instead, the content broker 111 selects (or otherwise obtains) an alternative resource identifier that is intended to resolve to an appropriate DNS nameserver of a service provider (e.g., the CDN service provider 106 or the network storage provider 110) based on a variety of criteria. For example, the content broker 111 may select an alternative resource identifier associated with a service provider based on a regional service plan or service level information obtained from the content provider 104. As will be described further below, this additional information may also be used for further request routing.
[0047] In an illustrative embodiment, the alternative resource identifiers are in the form of one or more canonical name (“CNAME”) records. In one embodiment, each CNAME record identifies a domain of the service provider (e.g., “serviceprovider.com” or “serviceprovider-1.com”). As will be explained in greater detail below, the domain in the CNAME does not need to be the same domain found in the original URL. Additionally, each CNAME record includes additional information, such as request routing information, (e.g., “request routing information”). An illustrative CNAME record can have the form of:
[0048] request_routing_information.serviceprovider.com
[0049] The CNAME records are generated and provided by the one or more DNS nameservers of the content broker 111 to direct a more appropriate DNS nameserver of a service provider, such as a DNS nameserver of the CDN service provider 106 or the network storage provider 110. As used in accordance with the present disclosure, appropriateness can be defined in any manner by the content broker 111 for a variety of purposes. In a manner similar to the process described above, the selection of an alternative resource identifier (e.g., CNAME) corresponding to a selected service provider can be based, at least in part, as a function of the request processing criteria. Examples of the selection of a service provider as a function of the request processing criteria will be described in detail with regard to FIG. 5 .
[0050] In accordance with this illustrative embodiment, the content broker 111 maintains a data store that defines CNAME records for various URLs corresponding to embedded resources. If a DNS query corresponding to a particular URL matches an entry in the data store, the content broker 111 returns a CNAME record to the client computing device 102A as defined in the data store and as illustrated in FIG. 4C . In an illustrative embodiment, the data store can include multiple CNAME records corresponding to a particular original URL. The multiple CNAME records would define a set of potential candidates that can be returned to the client computing device. In such an embodiment, the DNS nameserver of the content broker 111, either directly or via a network-based service, can implement additional logic in selecting an appropriate CNAME from a set of possible of CNAMEs.
[0051] The returned CNAME can also include request routing information that is different from or in addition to the information provided in the URL of the current DNS query. For example, if the CNAME selection is based on a regional service plan or a service level plan selected by the content provider 104, a specific identifier can be included in the “request_routing_information” portion of the specific CNAME record. In another embodiment, request routing information can be found in the identification of a service provider domain different from the domain found in the original URL. For example, if the CNAME is based on a regional plan, a specific regional plan domain (e.g., “serviceprovider-region1.com”) could be used in the domain name portion of the specific CNAME record. Any additional request routing information can be prepended to the existing request routing information in the original URL such that the previous request routing information would not be lost (e.g., http://serviceplan.regionalplan.serviceprovider.com). One skilled in the relevant art will appreciate that additional or alternative techniques and/or combination of techniques may be used to include the additional request routing information in the CNAME record that is identified by the network storage provider 110.
[0052] With reference now to FIG. 4A , in another embodiment, the content broker 111 processes client DNS queries for the original content (e.g., Web page) instead of the content provider 104 as shown in FIG. 3A . In this embodiment, during registration with the content broker 111, the content provider 104 requests the content broker to host the original content or to process requests for the original content on its behalf in addition to facilitate the provision of embedded resources by a service provider. Once the content broker 111 manages the original content on behalf of the content provider 104, the content broker 111 can, in one embodiment, translate resource identifiers corresponding to one or more embedded resources so that client DNS queries for the embedded resources are also directed to the content broker 111. In an alternative embodiment, upon registering one or more embedded resources with a service provider, the content broker 111 may instead translate the embedded resource identifiers in the original content based on service provider registration information so that subsequent DNS queries for the embedded resources are processed by one or more service providers.
[0053] With continued reference to FIG. 4A , after completion of the registration and translation processes in accordance with this embodiment, a first client computing device 102A generates a content request that is received and processed by the content broker 111 on behalf of the content provider 104. In accordance with an illustrative embodiment, the request for the content can be in accordance with common network protocols, such as HTTP. Upon receipt of the content request, the content broker 111 identifies and transmits the appropriate responsive content to the client computing device 102A. In an illustrative embodiment, the requested content can correspond to a Web page that is displayed on the client computing device 102A via the processing of information, such as HTML, XML, and the like. The requested content can also include a number of embedded resource identifiers, described above, that corresponds to resource objects that should be obtained by the client computing device 102A as part of the processing of the requested content. The embedded resource identifiers can be generally referred to as original resource identifiers or original URLs.
[0054] With reference now to FIG. 4B , in accordance with the embodiment in which the embedded resource identifiers are associated with the content broker 111, the client computing device 102A then begins processing any of the markup code included in the content and attempts to acquire the resources identified by the embedded resource identifiers from the content broker 111. If the embedded resource identifiers correspond to a domain associated with selected service provider, the client computing device 102A processes the embedded resources identifiers and transmits requests for the resources without further interaction by the content broker 111. Alternatively, if the embedded resource identifiers correspond to a domain name associated with the content broker 111, the client computing device 102A processes the embedded resource identifiers and transmits request for the resources to the applicable content broker domains. Further processing in this embodiment is identical to that described above in reference to FIG. 3B and accordingly will not be further described in reference to FIG. 4B .
[0055] With reference now to FIG. 5 , a flow diagram illustrative of a resource DNS query processing routine 500 implemented by a content broker 111 will be described. One skilled in the relevant art will appreciate that actions/steps outlined for routine 500 may be implemented by one or many computing devices/components that are associated with the content broker 111. Accordingly, routine 500 has been logically associated as being performed by the content broker 111.
[0056] At block 502, one of the DNS nameservers 150 of the content broker 111 receives a DNS query corresponding to a resource identifier. As previously discussed, the resource identifier can be a URL that has been embedded in content requested by the client computing device 102 and previously provided by the content provider 104 (FIG. 3 ) or the content broker 111 (FIG. 4 ). At decision block 504, a test is conducted to determine whether the receiving DNS nameserver is authoritative to resolve the DNS query. In an illustrative embodiment, the receiving DNS nameserver can determine whether it is authoritative to resolve the DNS query if there are no CNAME records corresponding to the received resource identifier. As previously discussed, for purposes of the routine 500, a DNS nameserver component is considered to be authoritative to a DNS query if the DNS nameserver can resolve the query by providing a responsive IP address of a service provider storage component, such as CDN resource cache components 124, 130, 136 or network storage provider storage component 140, 144, 148 (FIG. 1 ). In this context, the DNS nameserver may be operative to receive DNS queries on behalf network storage provider 110, but not authoritative if the DNS query cannot be completely resolved by providing a responsive IP address.
[0057] As previously described, to determine whether the DNS query can be resolved to an IP address of a service provider storage component, such as CDN resource cache components 124, 130, 136 or network storage provider storage component 140, 144, 148 (FIG. 1 ) or whether an alternate resource identifier should be provided, the receiving DNS nameserver utilizes request processing criteria to make such a determination. In an illustrative embodiment, the receiving DNS nameserver will utilize the cost information, at least in part, to make such a determination. The cost information corresponds to a financial cost attributable to the content provider 104 for the delivery of resources by the network storage provider 110 and the CDN service provider 106. The financial cost may be defined in a variety of ways and can be obtained by the SM component 152 of the content broker 111 in a variety of ways.
[0058] In one example, the cost information may designate that the content provider 104 has requested that the SM component 152 of the content broker 111 select the service provider (generally referred to as either the network storage provider 110 or a CDN service provider 106) associated with the lowest current financial cost to provide the requested resource. Accordingly, the SM component 152 of the content broker 111 could obtain cost information for at least a portion of the POPs and select the server provider (e.g., the network storage provider 110 or the CDN service provider 106) associated with the lowest financial cost. The financial cost information utilized to select the lowest financial costs may be based on a current financial costs or projected financial costs. The projected financial costs can be based on criteria, such as time of day, characteristics of the resource (e.g., size of the data, type of data, etc.), anticipated data throughput volumes, current loads experienced by each service provider, and the like. For example, if a service provider's POP resources are at an optimal capacity, the service provider may project financial cost at a premium cost level (e.g., a highest cost level) because any additional data traffic would cause the resources to operate above optimal rates. Conversely, the service provider may project lower financial costs for specific POPs according to historically known low volume times (e.g., time of day, days of the month, time of the year, special days/holidays, etc.). The financial cost information may be a single cost projected for each identifiable service provider. Alternatively, the financial cost information may be a set of costs associated with one or more identifiable components of each service provider (e.g., financial information for one or more POPs associated with a service provider).
[0059] In another example, the cost information may designate the content provider 104 has requested that the cost associated with the providing the requested resource be maintained below one or more cost thresholds or cost tiers. Accordingly, the SM component 152 of the content broker 111 could obtain financial cost information for the available service providers and select only those service providers with a financial cost at or below the cost thresholds. The SM component 152 of the content broker 111 could then utilize other request processing criteria to select from the selected DNS nameservers (if more than one DNS nameserver is identified) or selected in accordance with other selections methodologies (e.g., random, round robin, etc.).
[0060] In another embodiment, the SM component 152 of the content broker 111 can utilize a determined/projected volume of request information for selecting a service provider. The determined/projected volume of request information can include the total number of requests obtained by the content broker 111 for a resource over a defined period of time, trends regarding an increase/decrease in requests for the resource, and various combinations or alternatives thereof. Alternatively, as will be described below, the SM component 152 of the content broker 111 can obtain information associated with received resource requests from corresponding network storage components 110 or CDN service providers 106 to obtain the determined/projected volume of request information. For example, the various network storage providers 110 and CDN service providers 106 can provide the content broker 111 with log files of received resource requests.
[0061] In a further embodiment, the SM component 152 of the content broker 111 can utilize geographic criteria for selecting a service provider. The geographic criteria can correspond to geographic-based regional service plans available between the service providers and the content provider 104. Accordingly, a client computing device 102 DNS query received in a region not corresponding to the content provider's regional plan may be better processed by a DNS nameserver in region corresponding to the content provider's regional plan. In this example, the SM component 152 of the content broker 111 also obtains geographic information 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).
[0062] In yet another embodiment, the SM component 152 of the content broker 111 can utilize service level criteria for selecting a service provider. The service level criteria can correspond to service or performance metrics contracted between the available service providers and the content provider 104. Examples of performance metrics can include latencies of data transmission between the service provider POPs and the client computing devices 102, total data provided on behalf of the content provider 104 by the service provider POPs, error rates for data transmissions, and the like.
[0063] In still a further embodiment, the SM component 152 of the content broker 111 can utilize network performance criteria for selecting a service provider. The network performance criteria can correspond to measurements of network performance for transmitting data from the service provider POPs to the client computing device 102. Examples of network performance metrics can include network data transfer latencies (measured by the client computing device or the service providers), network data error rates, and the like.
[0064] In another embodiment, the SM component 152 of the content broker 111 can utilize content provider specified criteria for selecting a service provider. The content provider specified criteria can correspond to a variety of measurements or metrics specified by the content provider 104 and related to the delivery of resources on behalf of the content provider. The measurements or metrics can include content provider specified quality metrics (e.g., error rates), user complaints or error reports, and the like.
[0065] In accordance with an illustrative embodiment, the DNS nameserver maintains a data store that defines CNAME records for various URLs. If a DNS query corresponding to a particular URL matches an entry in the data store, the SM component 152 of the content broker 111 returns a CNAME record as defined in the data store. In an illustrative embodiment, the data store can include multiple CNAME records corresponding to a particular original URL. The multiple CNAME records would define a set of potential candidates that can be returned to the client computing device. In an illustrative embodiment, each the SM component 152 of the content broker 111 maintains the same data stores that define CNAME records, which can be managed centrally by the content broker 111. Alternatively, the content broker 111 can maintain separate copies of the CNAME records for distributed processing of DNS queries.
[0066] The returned CNAME can also include request routing information that is different from or in addition to the information provided in URL/CNAME of the current DNS query. For example, if the CNAME selection is based on regional plan, a specific regional plan can be identified in the “request_routing_information” portion of the specific CNAME record. A similar approach could be taken to identify service level plans and file management by including a specific identifier in the “request_routing_information” portion of the CNAME record. In another embodiment, request routing information can be found in the identification of a CDN service provider 106 domain different from the domain found in the current URL/CNAME. For example, if the CNAME is based on regional plan, a specific regional plan domain (e.g., “cdnprovider-region1.com”) could be used in the domain name portion of the specific CNAME record. Any additional request routing information can be prepended to the existing request routing information in the current URL/CNAME such that the previous request routing information would not be lost (e.g., serviceplan.regionalplan.cdnprovider.com). One skilled in the relevant art will appreciate that additional or alternative techniques and/or combination of techniques may be used to include the additional request routing information in the CNAME record that is selected by the SM component 152 of the content broker 111.
[0067] Alternative or additional methodologies may also be practiced to determine whether the DNS nameserver is authoritative.
[0068] If at decision block 504 the receiving DNS nameserver is not authoritative, at block 506, the DNS nameserver selects and transmits an alternative resource identifier. As described above, the DNS nameserver can utilize a data store to identify an appropriate CNAME as a function of the current DNS query. Additionally, the DNS nameserver component can also implement additional logical processing to select from a set of potential CNAMES. The routine 500 proceeds to block 510.
[0069] Alternatively, if the receiving DNS nameserver is authoritative (including a determination that the same DNS nameserver will be authoritative for subsequent DNS queries), the receiving DNS nameserver resolves the DNS query by identifying an IP address of a service provider storage component, such as CDN resource cache components 124, 130, 136 or network storage provider storage component 140, 144, 148 (FIG. 1 ) at block 508. In a non-limiting manner, a number of methodologies for selecting an appropriate IP address have been previously discussed and may be utilized by the content broker 111.
[0070] At block 510, the receiving DNS nameserver returns the DNS query result to the requesting client computing device 102. As previously described, the DNS query result can include an identification of an IP address of a service provider storage component, such as CDN resource cache components 124, 130, 136 or network storage provider storage component 140, 144, 148 (FIG. 1 ) or a CNAME. At block 512, the routine 500 terminates.
[0071] As described above, the determination by the content broker 111 of whether to utilize a network storage provider 110 or a CDN service provider 106 can be automatically implemented by the processing of the DNS queries by the content broker 111. In an alternative embodiment, the content provider 104 (directly or through content broker 111) may translate the embedded resources to include a domain name of a selected network storage provider 110 or CDN service provider 106. An example of a content broker 111 translation of embedded resource identifiers was described with regard to FIG. 4B . Accordingly, in this embodiment, the content broker 111 would not necessarily receive the client computing device 102 DNS query corresponding to the embedded resources. However, the selection methodology discussed above with regard to decision block 504 (FIG. 5 ) can be utilized to make a recommendation to the content provider 104 to modify one or more of the embedded resource identifiers based on an updated recommendation from the content broker 111. In this embodiment, the SM component 152 of the content broker 111 would receive information corresponding to client computing device requests from the network storage providers 110, CDN service providers 106 or content provider 104.
[0072] In one embodiment, the content broker 111 recommendation regarding an implementation of a CDN server provider 106 or network storage provider 110 can be provided to the content provider 104 in accordance with APIs or graphical user interfaces. As previously described, the recommendation may be independently implemented by the content provider 104 as part of the translation of embedded resource identifiers. Additionally, the recommendation may be automatically authorized or otherwise implemented by the content broker 111, on behalf of the content provider 104, via the exchange of APIs, or other interfaces. As described above, the processing of the APIs may be accomplished without requiring additional human interaction.
[0073] 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.
[0074] 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.
[0075] 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 medium 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.
[0076] 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.
Claims
What is claimed is:
1. A computer-implemented method for managing resource requests comprising:
as implemented by one or more computing devices configured with specific executable instructions,
obtaining, by a storage management component, a domain name system (DNS) query from a client computing device, the DNS query corresponding to a resource maintained by a service provider on behalf of a content provider;
identifying, by the storage management component, a plurality of service providers for providing a requested resource to a client computing device, wherein the plurality of service providers are independent of the storage management component;
associating, by the storage management component, a financial cost with each of the identified service, providers, wherein the financial cost corresponds to a financial cost attributed to the content provider for providing the resource corresponding to the DNS query by each of the identified plurality of service providers respectively;
selecting, by the storage management component, at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based at least in part on the associated financial cost; and
transmitting, by the storage management component to the client computing device, the selected one of the IP address and the alternative resource identifier associated with one of the identified plurality of service providers.
2. The method as recited in claim 1, wherein the plurality of service providers include at least a network storage service provider and one or more content delivery network (CDN) service providers.
3. The method as recited in claim 1, wherein selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based at least in part on the associated financial cost comprises selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based on a financial cost for providing the requested resource below a cost threshold.
4. The method as recited in claim 1, wherein selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers is further based on at least one of a characteristic of the content provider and a characteristic of the client computing device.
5. The method as recited in claim 1 further comprising causing, by the storage management component, the registration of the selected service provider such that the selected service provider will begin providing the requested resource.
6. The method as recited in claim 1, wherein the alternative resource identifier corresponds to a canonical name (CNAME).
7. A system for managing content requests comprising:
a memory operative to maintain request processing criteria corresponding to requested resources, the request routing criteria including financial cost information; and
a storage management component including at least one computing device associated with the memory, the storage management component operative to:
obtain a domain name system (DNS) query from a client computing device, the DNS query corresponding to a resource maintained by a service provider on behalf of a content provider;
identify a plurality of service providers for providing a requested resource to a client computing device, wherein the plurality of service providers are independent of the storage management component;
associate a financial cost with each of the identified service providers, wherein the financial cost corresponds to a financial cost attributed to the content provider for providing the resource corresponding to the DNS query by each of the identified plurality of service providers respectively;
select at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based at least in part on the associated financial cost; and
transmit, to the client computing device, the selected one of the IP address and the alternative resource identifier associated with one of the identified plurality of service providers.
8. The system as recited in claim 7, wherein the plurality of service providers include at least a network storage service provider and one or more content delivery network (CDN) service providers.
9. The system as recited in claim 7, wherein selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based at least in part on the associated financial cost comprises selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based on a financial cost for providing the requested resource below a cost threshold.
10. The system as recited in claim 7, wherein selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers is further based on at least one of a characteristic of the content provider and a characteristic of the client computing device.
11. The system as recited in claim 7, wherein the storage management component is further operative to cause the registration of the selected service provider such that the selected service provider will begin providing the requested resource.
12. The system as recited in claim 11, wherein the registration of the selected service provider is completed automatically without requiring additional interaction from the content provider.
13. The system as recited in claim 7, wherein the alternative resource identifier corresponds to a canonical name (CNAME).
14. A computer-implemented method for managing resource requests comprising:
as implemented by one or more computing devices configured with specific executable instructions,
obtaining, by a storage management component, information indicative of client computing device requests for a resource;
updating, by the storage management component, request processing criteria maintained in a data store corresponding to a request for the resource;
identifying, by the storage management component, a plurality of service providers for providing the requested resource to a client computing device, wherein the plurality of service providers are independent of the storage management component and wherein each of the plurality of service providers are operative to at least one of host or process the resource on behalf of a content provider, wherein the content provider is independent of the storage management component;
associating, by the storage management component, a financial cost with each of the plurality of service providers, wherein the financial cost corresponds to a financial cost attributed to a content provider for providing the requested resource by the plurality of service providers respectively;
selecting, by the storage management component, at least one service provider from plurality of service providers based at least in part on the corresponding financial cost for providing the requested resource; and
generating, by the storage management component, a recommendation for the content provider regarding the selected at least one service provider.
15. The method as recited in claim 14, wherein the plurality of service providers include at least a network storage service provider and one or more content delivery network (CDN) service providers.
16. The method as recited in claim 14, wherein selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based at least in part on the associated financial cost comprises selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based on a financial cost for providing the requested resource below a cost threshold.
17. The method as recited in claim 14, wherein selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers is further based on at least one of a characteristic of the content provider and a characteristic of the client computing device.
18. The method as recited in claim 14 further comprising causing the registration of the selected service provider such that the selected service provider will begin providing the requested resource.
19. The method as recited in claim 18, wherein the registration of the selected service provider is completed automatically without requiring additional interaction from the content provider.
20. The method as recited in claim 14 further comprising:
obtaining, by the storage management component, information indicative of subsequent client computing device requests for a resource;
updating, by the storage management component, the request processing criteria maintained in the data store corresponding to the subsequent request for the resource;
selecting, by the storage management component, a second service provider based at least on a financial cost for providing the requested resource below a cost threshold; and
generating, by the storage management component, an alternative recommendation regarding the selected second service provider.
21. A system for managing content requests comprising:
a memory operative to maintain request processing criteria corresponding to requested resources; and
a storage management component including at least one computing device associated with the memory, the storage management component operative to:
obtain information indicative of client computing device requests for a resource;
update the request processing criteria maintained in the data store corresponding to a request for the resource;
identify a plurality of service providers for providing the requested resource to a client computing device, wherein the plurality of service providers are independent of the storage management component and wherein each of the plurality of service providers are operative to at least one of host or process the resource on behalf of a content provider, wherein the content provider is independent of the storage management component;
associate a financial cost with each of the plurality of service providers, wherein the financial cost corresponds to a financial cost attributed to a content provider for providing the requested resource by the plurality of service providers respectively;
select at least one service provider from plurality of service providers based at least in part on the corresponding financial cost for providing the requested resource; and
generate a recommendation for the content provider regarding the selected at least one service provider.
22. The system as recited in claim 21, wherein the plurality of service providers include at least a network storage service provider and one or more content delivery network (CDN) service providers.
23. The system as recited in claim 21, wherein selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based at least in part on the associated financial cost comprises selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers based on a financial cost for providing the requested resource below a cost threshold.
24. The system as recited in claim 21, wherein selecting at least one of an IP address and an alternative resource identifier associated with one of the identified plurality of service providers is further based on at least one of a characteristic of the content provider and a characteristic of the client computing device.
25. The system as recited in claim 21, wherein the storage management component is further operative to cause the registration of the selected service provider such that the selected service provider will begin providing the requested resource.
26. The system as recited in claim 25, wherein the registration of the selected service provider is completed automatically without requiring additional interaction from the content provider.
27. The system as recited in claim 21, wherein the request processing criteria include at least one of a total number of requests obtained from client computing devices for a resource over a defined period of time, trends regarding an increase in requests from client computing devices for the resource, trends regarding a decrease in requests from client computing devices for the resource and a current financial cost associated with the delivery of the resource by a storage component.
28. The system as recited in claim 21, wherein the storage management component is further operative to:
obtain information indicative of subsequent client computing device requests for a resource;
update the request processing criteria maintained in the data store corresponding to the subsequent request for the resource;
select a second service provider based at least on a financial cost for providing the requested resource below a cost threshold; and
generate an alternative recommendation regarding the selected second service provider.
Patent Citations (600)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5341477(A) | 1994-08-01 | Pitkin et al. | Applicant |
| US5611049(A) | 1997-03-01 | Pitts | Applicant |
| US5649185(A) | 1997-07-01 | Antognini et al. | Applicant |
| US5664106(A) | 1997-09-01 | Caccavale | Applicant |
| US5774660(A) | 1998-06-01 | Brendel et al. | Applicant |
| US5819033(A) | 1998-10-01 | Caccavale | Applicant |
| US5892914(A) | 1999-04-01 | Pitts | Applicant |
| US5933811(A) | 1999-08-01 | Angles et al. | Applicant |
| US5974454(A) | 1999-10-01 | Apfel et al. | Applicant |
| US6016512(A) | 2000-01-01 | Huitema | Applicant |
| US6026452(A) | 2000-02-01 | Pitts | Applicant |
| US6052718(A) | 2000-04-01 | Gifford | Applicant |
| US6085234(A) | 2000-07-01 | Pitts et al. | Applicant |
| US6098096(A) | 2000-08-01 | Tsirigotis et al. | Applicant |
| US6108703(A) | 2000-08-01 | Leighton et al. | Applicant |
| US6182111(B1) | 2001-01-01 | Inohara et al. | Applicant |
| US6185598(B1) | 2001-02-01 | Farber et al. | Applicant |
| US6192051(B1) | 2001-02-01 | Lipman et al. | Applicant |
| US6205475(B1) | 2001-03-01 | Pitts | Applicant |
| US6223288(B1) | 2001-04-01 | Byrne | Applicant |
| US6275496(B1) | 2001-08-01 | Burns et al. | Applicant |
| US6286043(B1) | 2001-09-01 | Cuomo et al. | Applicant |
| US6286084(B1) | 2001-09-01 | Wexler et al. | Applicant |
| US6304913(B1) | 2001-10-01 | Rune | Applicant |
| US6351743(B1) | 2002-02-01 | DeArdo et al. | Applicant |
| US6351775(B1) | 2002-02-01 | Yu | Applicant |
| US6363411(B1) | 2002-03-01 | Dugan et al. | Applicant |
| US6366952(B2) | 2002-04-01 | Pitts | Applicant |
| US6374290(B1) | 2002-04-01 | Scharber et al. | Applicant |
| US6411967(B1) | 2002-06-01 | Van Renesse | Applicant |
| US6415280(B1) | 2002-07-01 | Farber et al. | Applicant |
| US6430607(B1) | 2002-08-01 | Kavner | Applicant |
| US6438592(B1) | 2002-08-01 | Killian | Applicant |
| US6457047(B1) | 2002-09-01 | Chandra et al. | Applicant |
| US6459909(B1) | 2002-10-01 | Bilcliff et al. | Applicant |
| US6473804(B1) | 2002-10-01 | Kaiser et al. | Applicant |
| US6484143(B1) | 2002-11-01 | Swildens et al. | Applicant |
| US6505241(B2) | 2003-01-01 | Pitts | Applicant |
| US6529953(B1) | 2003-03-01 | Van Renesse | Applicant |
| US6553413(B1) | 2003-04-01 | Leighton et al. | Applicant |
| US6553419(B1) | 2003-04-01 | Ram | Applicant |
| US6560610(B1) | 2003-05-01 | Eatherton et al. | Applicant |
| US6611873(B1) | 2003-08-01 | Kanehara | Applicant |
| US6633324(B2) | 2003-10-01 | Stephens, Jr. | Applicant |
| US6654807(B2) | 2003-11-01 | Farber et al. | Applicant |
| US6658462(B1) | 2003-12-01 | Dutta | Applicant |
| US6678791(B1) | 2004-01-01 | Jacobs et al. | Applicant |
| US6694358(B1) | 2004-02-01 | Swildens et al. | Applicant |
| US6697805(B1) | 2004-02-01 | Choquier et al. | Applicant |
| US6698013(B1) | 2004-02-01 | Bertero et al. | Applicant |
| US6724770(B1) | 2004-04-01 | Van Renesse | Applicant |
| US6732237(B1) | 2004-05-01 | Jacobs et al. | Applicant |
| US6754699(B2) | 2004-06-01 | Swildens et al. | Applicant |
| US6754706(B1) | 2004-06-01 | Swildens et al. | Applicant |
| US6769031(B1) | 2004-07-01 | Bero | Applicant |
| US6782398(B1) | 2004-08-01 | Bahl | Applicant |
| US6785704(B1) | 2004-08-01 | McCanne | Applicant |
| US6804706(B2) | 2004-10-01 | Pitts | Applicant |
| US6810291(B2) | 2004-10-01 | Card et al. | Applicant |
| US6810411(B1) | 2004-10-01 | Coughlin et al. | Applicant |
| US6829654(B1) | 2004-12-01 | Jungck | Applicant |
| US6874017(B1) | 2005-03-01 | Inoue et al. | Applicant |
| US6963850(B1) | 2005-11-01 | Bezos et al. | Applicant |
| US6978418(B1) | 2005-12-01 | Bain et al. | Applicant |
| US6981017(B1) | 2005-12-01 | Kasriel et al. | Applicant |
| US6986018(B2) | 2006-01-01 | O'Rourke et al. | Applicant |
| US6990526(B1) | 2006-01-01 | Zhu | Applicant |
| US6996616(B1) | 2006-02-01 | Leighton et al. | Applicant |
| US7003555(B1) | 2006-02-01 | Jungck | Applicant |
| US7006099(B2) | 2006-02-01 | Gut et al. | Applicant |
| US7007089(B2) | 2006-02-01 | Freedman | Applicant |
| US7009943(B2) | 2006-03-01 | O'Neil | Applicant |
| US7010578(B1) | 2006-03-01 | Lewin et al. | Applicant |
| US7010598(B2) | 2006-03-01 | Sitaraman et al. | Applicant |
| US7023465(B2) | 2006-04-01 | Stephens, Jr. | Applicant |
| US7032010(B1) | 2006-04-01 | Swildens et al. | Applicant |
| US7058706(B1) | 2006-06-01 | Iyer et al. | Applicant |
| US7058953(B2) | 2006-06-01 | Willard et al. | Applicant |
| US7065496(B2) | 2006-06-01 | Subbloie et al. | Applicant |
| US7065587(B2) | 2006-06-01 | Huitema et al. | Applicant |
| US7072982(B2) | 2006-07-01 | Teodosiu et al. | Applicant |
| US7076633(B2) | 2006-07-01 | Tormasov et al. | Applicant |
| US7082476(B1) | 2006-07-01 | Cohen et al. | Applicant |
| US7085825(B1) | 2006-08-01 | Pishevar et al. | Applicant |
| US7086061(B1) | 2006-08-01 | Joshi et al. | Applicant |
| US7092505(B2) | 2006-08-01 | Allison et al. | Applicant |
| US7092997(B1) | 2006-08-01 | Kasriel et al. | Applicant |
| US7099936(B2) | 2006-08-01 | Chase et al. | Applicant |
| US7103645(B2) | 2006-09-01 | Leighton et al. | Applicant |
| US7107273(B2) | 2006-09-01 | Ohata et al. | Applicant |
| US7117262(B2) | 2006-10-01 | Bai et al. | Applicant |
| US7120871(B1) | 2006-10-01 | Harrington | Applicant |
| US7120874(B2) | 2006-10-01 | Shah et al. | Applicant |
| US7133905(B2) | 2006-11-01 | Dilley et al. | Applicant |
| US7136922(B2) | 2006-11-01 | Sundaram et al. | Applicant |
| US7139821(B1) | 2006-11-01 | Shah et al. | Applicant |
| US7143169(B1) | 2006-11-01 | Champagne et al. | Applicant |
| US7146560(B2) | 2006-12-01 | Dang et al. | Applicant |
| US7149809(B2) | 2006-12-01 | Barde et al. | Applicant |
| US7152118(B2) | 2006-12-01 | Anderson, IV et al. | Applicant |
| US7174382(B2) | 2007-02-01 | Ramanathan et al. | Applicant |
| US7185063(B1) | 2007-02-01 | Kasriel et al. | Applicant |
| US7188214(B1) | 2007-03-01 | Kasriel et al. | Applicant |
| US7194522(B1) | 2007-03-01 | Swildens et al. | Applicant |
| US7200667(B2) | 2007-04-01 | Teodosiu et al. | Applicant |
| US7225254(B1) | 2007-05-01 | Swildens et al. | Applicant |
| US7228350(B2) | 2007-06-01 | Hong et al. | Applicant |
| US7233978(B2) | 2007-06-01 | Overton et al. | Applicant |
| US7240100(B1) | 2007-07-01 | Wein et al. | Applicant |
| US7254636(B1) | 2007-08-01 | O'Toole, Jr. et al. | Applicant |
| US7260598(B1) | 2007-08-01 | Liskov et al. | Applicant |
| US7269657(B1) | 2007-09-01 | Alexander et al. | Applicant |
| US7269784(B1) | 2007-09-01 | Kasriel et al. | Applicant |
| US7289519(B1) | 2007-10-01 | Liskov | Applicant |
| US7293093(B2) | 2007-11-01 | Leighton | Applicant |
| US7310686(B2) | 2007-12-01 | Uysal | Applicant |
| US7316648(B2) | 2008-01-01 | Kelly et al. | Applicant |
| US7320131(B1) | 2008-01-01 | O'Toole, Jr. | Applicant |
| US7321918(B2) | 2008-01-01 | Burd et al. | Applicant |
| US7343399(B2) | 2008-03-01 | Hayball et al. | Applicant |
| US7363291(B1) | 2008-04-01 | Page | Applicant |
| US7376736(B2) | 2008-05-01 | Sundaram et al. | Applicant |
| US7430610(B2) | 2008-09-01 | Pace et al. | Applicant |
| US7441045(B2) | 2008-10-01 | Skene et al. | Applicant |
| US7461170(B1) | 2008-12-01 | Taylor et al. | Applicant |
| US7464142(B2) | 2008-12-01 | Flurry et al. | Applicant |
| US7492720(B2) | 2009-02-01 | Pruthi et al. | Applicant |
| US7499998(B2) | 2009-03-01 | Toebes et al. | Applicant |
| US7502836(B1) | 2009-03-01 | Menditto et al. | Applicant |
| US7519720(B2) | 2009-04-01 | Fishman et al. | Applicant |
| US7548947(B2) | 2009-06-01 | Kasriel et al. | Applicant |
| US7552235(B2) | 2009-06-01 | Chase et al. | Applicant |
| US7565407(B1) | 2009-07-01 | Hayball | Applicant |
| US7573916(B1) | 2009-08-01 | Bechtolsheim et al. | Applicant |
| US7581224(B2) | 2009-08-01 | Romero | Applicant |
| US7594189(B1) | 2009-09-01 | Walker et al. | Applicant |
| US7623460(B2) | 2009-11-01 | Miyazaki | Applicant |
| US7624169(B2) | 2009-11-01 | Lisiecki et al. | Applicant |
| US7640296(B2) | 2009-12-01 | Fuchs et al. | Applicant |
| US7650376(B1) | 2010-01-01 | Blumenau | Applicant |
| US7653700(B1) | 2010-01-01 | Bahl et al. | Applicant |
| US7653725(B2) | 2010-01-01 | Yahiro et al. | Applicant |
| US7657622(B1) | 2010-02-01 | Douglis et al. | Applicant |
| US7680897(B1) | 2010-03-01 | Carter et al. | Applicant |
| US7685270(B1) | 2010-03-01 | Vermeulen et al. | Applicant |
| US7698418(B2) | 2010-04-01 | Shimada et al. | Applicant |
| US7702724(B1) | 2010-04-01 | Brydon et al. | Applicant |
| US7706740(B2) | 2010-04-01 | Collins et al. | Applicant |
| US7707314(B2) | 2010-04-01 | McCarthy et al. | Applicant |
| US7716367(B1) | 2010-05-01 | Leighton et al. | Applicant |
| US7725602(B2) | 2010-05-01 | Liu et al. | Applicant |
| US7739400(B2) | 2010-06-01 | Lindbo et al. | Applicant |
| US7747720(B2) | 2010-06-01 | Toebes et al. | Applicant |
| US7748005(B2) | 2010-06-01 | Romero et al. | Applicant |
| US7752301(B1) | 2010-07-01 | Maiocco et al. | Applicant |
| US7756032(B2) | 2010-07-01 | Feick et al. | Applicant |
| US7756913(B1) | 2010-07-01 | Day | Applicant |
| US7761572(B1) | 2010-07-01 | Auerbach | Applicant |
| US7769823(B2) | 2010-08-01 | Jenny et al. | Applicant |
| US7773596(B1) | 2010-08-01 | Marques | Applicant |
| US7774342(B1) | 2010-08-01 | Virdy | Applicant |
| US7787380(B1) | 2010-08-01 | Aggarwal et al. | Applicant |
| US7792989(B2) | 2010-09-01 | Toebes et al. | Applicant |
| US7809597(B2) | 2010-10-01 | Das et al. | Applicant |
| US7813308(B2) | 2010-10-01 | Reddy et al. | Applicant |
| US7818454(B2) | 2010-10-01 | Kim et al. | Applicant |
| US7836177(B2) | 2010-11-01 | Kasriel et al. | Applicant |
| US7865594(B1) | 2011-01-01 | Baumback et al. | Applicant |
| US7904875(B2) | 2011-03-01 | Hegyi | Applicant |
| US7912921(B2) | 2011-03-01 | O'Rourke et al. | Applicant |
| US7925782(B2) | 2011-04-01 | Sivasubramanian et al. | Applicant |
| US7930393(B1) | 2011-04-01 | Baumback et al. | Applicant |
| US7930427(B2) | 2011-04-01 | Josefsberg et al. | Applicant |
| US7933988(B2) | 2011-04-01 | Nasuto et al. | Applicant |
| US7937456(B2) | 2011-05-01 | McGrath | Applicant |
| US7937477(B1) | 2011-05-01 | Day et al. | Applicant |
| US7949779(B2) | 2011-05-01 | Farber et al. | Applicant |
| US7961736(B2) | 2011-06-01 | Ayyagari | Applicant |
| US7962597(B2) | 2011-06-01 | Richardson et al. | Applicant |
| US7966404(B2) | 2011-06-01 | Hedin et al. | Applicant |
| US7970940(B1) | 2011-06-01 | van de Ven et al. | Applicant |
| US7979509(B1) | 2011-07-01 | Malmskog et al. | Applicant |
| US7991910(B2) | 2011-08-01 | Richardson et al. | Applicant |
| US7996535(B2) | 2011-08-01 | Auerbach | Applicant |
| US8000724(B1) | 2011-08-01 | Rayburn et al. | Applicant |
| US8028090(B2) | 2011-09-01 | Richardson et al. | Applicant |
| US8051166(B1) | 2011-11-01 | Baumback et al. | Applicant |
| US8065275(B2) | 2011-11-01 | Eriksen et al. | Applicant |
| US8069231(B2) | 2011-11-01 | Schran et al. | Applicant |
| US8073940(B1) | 2011-12-01 | Richardson et al. | Applicant |
| US8082348(B1) | 2011-12-01 | Averbuj et al. | Applicant |
| US8117306(B1) | 2012-02-01 | Baumback et al. | Examiner |
| US8122098(B1) | 2012-02-01 | Richardson et al. | Applicant |
| US8122124(B1) | 2012-02-01 | Baumback et al. | Applicant |
| US8135820(B2) | 2012-03-01 | Richardson et al. | Applicant |
| US8190682(B2) | 2012-05-01 | Paterson-Jones et al. | Applicant |
| US8239530(B2) | 2012-08-01 | Sundaram et al. | Applicant |
| US8250211(B2) | 2012-08-01 | Swildens et al. | Applicant |
| US8266327(B2) | 2012-09-01 | Kumar et al. | Applicant |
| US8291117(B1) | 2012-10-01 | Eggleston et al. | Applicant |
| US8301645(B1) | 2012-10-01 | Crook | Applicant |
| US8321568(B2) | 2012-11-01 | Sivasubramanian et al. | Applicant |
| US8402137(B2) | 2013-03-01 | Sivasubramanian et al. | Applicant |
| US8468222(B2) | 2013-06-01 | Sakata et al. | Applicant |
| US8521851(B1) | 2013-08-01 | Richardson et al. | Applicant |
| US8521908(B2) | 2013-08-01 | Holmes et al. | Applicant |
| US8527658(B2) | 2013-09-01 | Holmes et al. | Applicant |
| US2001/0000811(A1) | 2001-05-01 | May et al. | Applicant |
| US2001/0032133(A1) | 2001-10-01 | Moran | Applicant |
| US2001/0034704(A1) | 2001-10-01 | Farhat et al. | Applicant |
| US2001/0049741(A1) | 2001-12-01 | Skene et al. | Applicant |
| US2001/0052016(A1) | 2001-12-01 | Skene et al. | Applicant |
| US2001/0056416(A1) | 2001-12-01 | Garcia-Luna-Aceves | Applicant |
| US2001/0056500(A1) | 2001-12-01 | Farber et al. | Applicant |
| US2002/0002613(A1) | 2002-01-01 | Freeman et al. | Applicant |
| US2002/0007413(A1) | 2002-01-01 | Garcia-Luna-Aceves et al. | Applicant |
| US2002/0048269(A1) | 2002-04-01 | Hong et al. | Applicant |
| US2002/0049608(A1) | 2002-04-01 | Hartsell et al. | Applicant |
| US2002/0052942(A1) | 2002-05-01 | Swildens et al. | Applicant |
| US2002/0062372(A1) | 2002-05-01 | Hong et al. | Applicant |
| US2002/0068554(A1) | 2002-06-01 | Dusse | Applicant |
| US2002/0069420(A1) | 2002-06-01 | Russell et al. | Applicant |
| US2002/0078233(A1) | 2002-06-01 | Biliris et al. | Applicant |
| US2002/0082858(A1) | 2002-06-01 | Heddaya et al. | Applicant |
| US2002/0083118(A1) | 2002-06-01 | Sim | Applicant |
| US2002/0083148(A1) | 2002-06-01 | Shaw et al. | Applicant |
| US2002/0087374(A1) | 2002-07-01 | Boubez et al. | Applicant |
| US2002/0092026(A1) | 2002-07-01 | Janniello et al. | Applicant |
| US2002/0099616(A1) | 2002-07-01 | Sweldens | Applicant |
| US2002/0099850(A1) | 2002-07-01 | Farber et al. | Applicant |
| US2002/0101836(A1) | 2002-08-01 | Dorenbosch | Applicant |
| US2002/0107944(A1) | 2002-08-01 | Bai et al. | Applicant |
| US2002/0112049(A1) | 2002-08-01 | Elnozahy et al. | Applicant |
| US2002/0116481(A1) | 2002-08-01 | Lee | Applicant |
| US2002/0116491(A1) | 2002-08-01 | Boyd et al. | Applicant |
| US2002/0124047(A1) | 2002-09-01 | Gartner et al. | Applicant |
| US2002/0124098(A1) | 2002-09-01 | Shaw | Applicant |
| US2002/0129123(A1) | 2002-09-01 | Johnson et al. | Applicant |
| US2002/0135611(A1) | 2002-09-01 | Deosaran et al. | Applicant |
| US2002/0138286(A1) | 2002-09-01 | Engstrom | Applicant |
| US2002/0138437(A1) | 2002-09-01 | Lewin et al. | Applicant |
| US2002/0138443(A1) | 2002-09-01 | Schran et al. | Applicant |
| US2002/0143989(A1) | 2002-10-01 | Huitema et al. | Applicant |
| US2002/0147770(A1) | 2002-10-01 | Tang | Applicant |
| US2002/0147774(A1) | 2002-10-01 | Lisiecki et al. | Applicant |
| US2002/0150094(A1) | 2002-10-01 | Cheng et al. | Applicant |
| US2002/0150276(A1) | 2002-10-01 | Chang | Applicant |
| US2002/0156911(A1) | 2002-10-01 | Croman et al. | Applicant |
| US2002/0161767(A1) | 2002-10-01 | Shapiro et al. | Applicant |
| US2002/0163882(A1) | 2002-11-01 | Bornstein et al. | Applicant |
| US2002/0165912(A1) | 2002-11-01 | Wenocur et al. | Applicant |
| US2002/0188722(A1) | 2002-12-01 | Banerjee et al. | Applicant |
| US2002/0194382(A1) | 2002-12-01 | Kausik et al. | Applicant |
| US2002/0198953(A1) | 2002-12-01 | O'Rourke et al. | Applicant |
| US2003/0002484(A1) | 2003-01-01 | Freedman | Applicant |
| US2003/0005111(A1) | 2003-01-01 | Allan | Applicant |
| US2003/0009591(A1) | 2003-01-01 | Hayball et al. | Applicant |
| US2003/0028642(A1) | 2003-02-01 | Agarwal et al. | Applicant |
| US2003/0033283(A1) | 2003-02-01 | Evans et al. | Applicant |
| US2003/0037139(A1) | 2003-02-01 | Shteyn | Applicant |
| US2003/0065739(A1) | 2003-04-01 | Shnier | Applicant |
| US2003/0074401(A1) | 2003-04-01 | Connell et al. | Applicant |
| US2003/0079027(A1) | 2003-04-01 | Slocombe et al. | Applicant |
| US2003/0093523(A1) | 2003-05-01 | Cranor et al. | Applicant |
| US2003/0099202(A1) | 2003-05-01 | Lear et al. | Applicant |
| US2003/0101278(A1) | 2003-05-01 | Garcia-Luna-Aceves et al. | Applicant |
| US2003/0120741(A1) | 2003-06-01 | Wu et al. | Applicant |
| US2003/0133554(A1) | 2003-07-01 | Nykanen et al. | Applicant |
| US2003/0135509(A1) | 2003-07-01 | Davis et al. | Applicant |
| US2003/0140087(A1) | 2003-07-01 | Lincoln et al. | Applicant |
| US2003/0145038(A1) | 2003-07-01 | Tariq et al. | Applicant |
| US2003/0145066(A1) | 2003-07-01 | Okada et al. | Applicant |
| US2003/0149581(A1) | 2003-08-01 | Chaudhri et al. | Applicant |
| US2003/0154284(A1) | 2003-08-01 | Bernardin et al. | Applicant |
| US2003/0163722(A1) | 2003-08-01 | Anderson, IV | Applicant |
| US2003/0172145(A1) | 2003-09-01 | Nguyen | Applicant |
| US2003/0172183(A1) | 2003-09-01 | Anderson, IV et al. | Applicant |
| US2003/0172291(A1) | 2003-09-01 | Judge et al. | Applicant |
| US2003/0174648(A1) | 2003-09-01 | Wang et al. | Applicant |
| US2003/0182305(A1) | 2003-09-01 | Balva et al. | Applicant |
| US2003/0182413(A1) | 2003-09-01 | Allen et al. | Applicant |
| US2003/0182447(A1) | 2003-09-01 | Schilling | Applicant |
| US2003/0187935(A1) | 2003-10-01 | Agarwalla et al. | Applicant |
| US2003/0187970(A1) | 2003-10-01 | Chase et al. | Applicant |
| US2003/0191822(A1) | 2003-10-01 | Leighton et al. | Applicant |
| US2003/0200394(A1) | 2003-10-01 | Ashmore et al. | Applicant |
| US2003/0204602(A1) | 2003-10-01 | Hudson et al. | Applicant |
| US2003/0221000(A1) | 2003-11-01 | Cherkasova et al. | Applicant |
| US2003/0229682(A1) | 2003-12-01 | Day | Applicant |
| US2003/0233423(A1) | 2003-12-01 | Dilley et al. | Applicant |
| US2003/0236700(A1) | 2003-12-01 | Arning et al. | Applicant |
| US2004/0010621(A1) | 2004-01-01 | Afergan et al. | Applicant |
| US2004/0019518(A1) | 2004-01-01 | Abraham et al. | Applicant |
| US2004/0024841(A1) | 2004-02-01 | Becker et al. | Applicant |
| US2004/0030620(A1) | 2004-02-01 | Benjamin et al. | Applicant |
| US2004/0034744(A1) | 2004-02-01 | Karlsson et al. | Applicant |
| US2004/0039798(A1) | 2004-02-01 | Hotz et al. | Applicant |
| US2004/0044731(A1) | 2004-03-01 | Chen et al. | Applicant |
| US2004/0044791(A1) | 2004-03-01 | Pouzzner | Applicant |
| US2004/0049579(A1) | 2004-03-01 | Ims et al. | Applicant |
| US2004/0059805(A1) | 2004-03-01 | Dinker et al. | Applicant |
| US2004/0064293(A1) | 2004-04-01 | Hamilton et al. | Applicant |
| US2004/0064501(A1) | 2004-04-01 | Jan et al. | Applicant |
| US2004/0064558(A1) | 2004-04-01 | Miyake | Applicant |
| US2004/0073596(A1) | 2004-04-01 | Kloninger et al. | Applicant |
| US2004/0073867(A1) | 2004-04-01 | Kausik et al. | Applicant |
| US2004/0078468(A1) | 2004-04-01 | Hedin et al. | Applicant |
| US2004/0078487(A1) | 2004-04-01 | Cernohous et al. | Applicant |
| US2004/0083283(A1) | 2004-04-01 | Sundaram et al. | Applicant |
| US2004/0083307(A1) | 2004-04-01 | Uysal | Applicant |
| US2004/0117455(A1) | 2004-06-01 | Kaminsky et al. | Applicant |
| US2004/0128344(A1) | 2004-07-01 | Trossen | Applicant |
| US2004/0128346(A1) | 2004-07-01 | Melamed et al. | Applicant |
| US2004/0167981(A1) | 2004-08-01 | Douglas et al. | Applicant |
| US2004/0172466(A1) | 2004-09-01 | Douglas et al. | Applicant |
| US2004/0194085(A1) | 2004-09-01 | Beaubien et al. | Applicant |
| US2004/0194102(A1) | 2004-09-01 | Neerdaels | Applicant |
| US2004/0203630(A1) | 2004-10-01 | Wang | Applicant |
| US2004/0205149(A1) | 2004-10-01 | Dillon et al. | Applicant |
| US2004/0205162(A1) | 2004-10-01 | Parikh | Applicant |
| US2004/0215823(A1) | 2004-10-01 | Kleinfelter et al. | Applicant |
| US2004/0221034(A1) | 2004-11-01 | Kausik et al. | Applicant |
| US2004/0249971(A1) | 2004-12-01 | Klinker | Applicant |
| US2004/0249975(A1) | 2004-12-01 | Tuck et al. | Applicant |
| US2004/0254921(A1) | 2004-12-01 | Cohen et al. | Applicant |
| US2004/0267906(A1) | 2004-12-01 | Truty | Applicant |
| US2004/0267907(A1) | 2004-12-01 | Gustafsson | Applicant |
| US2005/0010653(A1) | 2005-01-01 | McCanne | Applicant |
| US2005/0021706(A1) | 2005-01-01 | Maggi et al. | Applicant |
| US2005/0021862(A1) | 2005-01-01 | Schroeder et al. | Applicant |
| US2005/0038967(A1) | 2005-02-01 | Umbehocker et al. | Applicant |
| US2005/0044270(A1) | 2005-02-01 | Grove et al. | Applicant |
| US2005/0086645(A1) | 2005-04-01 | Diao et al. | Applicant |
| US2005/0102683(A1) | 2005-05-01 | Branson et al. | Applicant |
| US2005/0108169(A1) | 2005-05-01 | Balasubramanian et al. | Applicant |
| US2005/0108529(A1) | 2005-05-01 | Juneau | Applicant |
| US2005/0114296(A1) | 2005-05-01 | Farber et al. | Applicant |
| US2005/0132083(A1) | 2005-06-01 | Raciborski et al. | Applicant |
| US2005/0157712(A1) | 2005-07-01 | Rangarajan et al. | Applicant |
| US2005/0163168(A1) | 2005-07-01 | Sheth et al. | Applicant |
| US2005/0168782(A1) | 2005-08-01 | Kobashi et al. | Applicant |
| US2005/0171959(A1) | 2005-08-01 | Deforche et al. | Applicant |
| US2005/0188073(A1) | 2005-08-01 | Nakamichi et al. | Applicant |
| US2005/0192008(A1) | 2005-09-01 | Desai et al. | Applicant |
| US2005/0198571(A1) | 2005-09-01 | Kramer et al. | Applicant |
| US2005/0216569(A1) | 2005-09-01 | Coppola et al. | Applicant |
| US2005/0216674(A1) | 2005-09-01 | Robbin et al. | Applicant |
| US2005/0229119(A1) | 2005-10-01 | Torvinen | Applicant |
| US2005/0232165(A1) | 2005-10-01 | Brawn et al. | Applicant |
| US2005/0259672(A1) | 2005-11-01 | Eduri | Applicant |
| US2005/0262248(A1) | 2005-11-01 | Jennings, III et al. | Applicant |
| US2005/0267991(A1) | 2005-12-01 | Huitema et al. | Applicant |
| US2005/0267992(A1) | 2005-12-01 | Huitema et al. | Applicant |
| US2005/0267993(A1) | 2005-12-01 | Huitema et al. | Applicant |
| US2005/0273507(A1) | 2005-12-01 | Yan et al. | Applicant |
| US2005/0278259(A1) | 2005-12-01 | Gunaseelan et al. | Applicant |
| US2005/0283759(A1) | 2005-12-01 | Peteanu et al. | Applicant |
| US2005/0283784(A1) | 2005-12-01 | Suzuki | Applicant |
| US2006/0013158(A1) | 2006-01-01 | Ahuja et al. | Applicant |
| US2006/0020596(A1) | 2006-01-01 | Liu et al. | Applicant |
| US2006/0020684(A1) | 2006-01-01 | Mukherjee et al. | Applicant |
| US2006/0020714(A1) | 2006-01-01 | Girouard et al. | Applicant |
| US2006/0020715(A1) | 2006-01-01 | Jungck | Applicant |
| US2006/0026067(A1) | 2006-02-01 | Nicholas et al. | Applicant |
| US2006/0026154(A1) | 2006-02-01 | Altinel et al. | Applicant |
| US2006/0036720(A1) | 2006-02-01 | Faulk, Jr. | Applicant |
| US2006/0037037(A1) | 2006-02-01 | Miranz | Applicant |
| US2006/0041614(A1) | 2006-02-01 | Oe | Applicant |
| US2006/0047787(A1) | 2006-03-01 | Agarwal et al. | Applicant |
| US2006/0047813(A1) | 2006-03-01 | Aggarwal et al. | Applicant |
| US2006/0059246(A1) | 2006-03-01 | Grove | Applicant |
| US2006/0063534(A1) | 2006-03-01 | Kokkonen et al. | Applicant |
| US2006/0064476(A1) | 2006-03-01 | Decasper et al. | Applicant |
| US2006/0064500(A1) | 2006-03-01 | Roth et al. | Applicant |
| US2006/0069808(A1) | 2006-03-01 | Mitchell et al. | Applicant |
| US2006/0074750(A1) | 2006-04-01 | Clark et al. | Applicant |
| US2006/0075084(A1) | 2006-04-01 | Lyon | Applicant |
| US2006/0075139(A1) | 2006-04-01 | Jungck | Applicant |
| US2006/0083165(A1) | 2006-04-01 | McLane et al. | Applicant |
| US2006/0085536(A1) | 2006-04-01 | Meyer et al. | Applicant |
| US2006/0112066(A1) | 2006-05-01 | Hamzy | Applicant |
| US2006/0112176(A1) | 2006-05-01 | Liu et al. | Applicant |
| US2006/0120385(A1) | 2006-06-01 | Atchison et al. | Applicant |
| US2006/0129665(A1) | 2006-06-01 | Toebes et al. | Applicant |
| US2006/0143293(A1) | 2006-06-01 | Freedman | Applicant |
| US2006/0155823(A1) | 2006-07-01 | Tran et al. | Applicant |
| US2006/0161541(A1) | 2006-07-01 | Cencini | Applicant |
| US2006/0168088(A1) | 2006-07-01 | Leighton et al. | Applicant |
| US2006/0179080(A1) | 2006-08-01 | Meek et al. | Applicant |
| US2006/0184936(A1) | 2006-08-01 | Abels et al. | Applicant |
| US2006/0190605(A1) | 2006-08-01 | Franz et al. | Applicant |
| US2006/0193247(A1) | 2006-08-01 | Naseh et al. | Applicant |
| US2006/0195866(A1) | 2006-08-01 | Thukral | Applicant |
| US2006/0209701(A1) | 2006-09-01 | Zhang et al. | Applicant |
| US2006/0218304(A1) | 2006-09-01 | Mukherjee et al. | Applicant |
| US2006/0227740(A1) | 2006-10-01 | McLaughlin et al. | Applicant |
| US2006/0227758(A1) | 2006-10-01 | Rana et al. | Applicant |
| US2006/0230137(A1) | 2006-10-01 | Gare et al. | Applicant |
| US2006/0233155(A1) | 2006-10-01 | Srivastava | Applicant |
| US2006/0251339(A1) | 2006-11-01 | Gokturk et al. | Applicant |
| US2006/0253546(A1) | 2006-11-01 | Chang et al. | Applicant |
| US2006/0253609(A1) | 2006-11-01 | Andreev et al. | Applicant |
| US2006/0259581(A1) | 2006-11-01 | Piersol | Applicant |
| US2006/0259690(A1) | 2006-11-01 | Vittal et al. | Applicant |
| US2006/0259984(A1) | 2006-11-01 | Juneau | Applicant |
| US2006/0265497(A1) | 2006-11-01 | Ohata et al. | Applicant |
| US2006/0265508(A1) | 2006-11-01 | Angel et al. | Applicant |
| US2006/0265516(A1) | 2006-11-01 | Schilling | Applicant |
| US2006/0265720(A1) | 2006-11-01 | Cai et al. | Applicant |
| US2006/0271641(A1) | 2006-11-01 | Stavrakos et al. | Applicant |
| US2006/0282522(A1) | 2006-12-01 | Lewin et al. | Applicant |
| US2006/0282758(A1) | 2006-12-01 | Simons et al. | Applicant |
| US2007/0005689(A1) | 2007-01-01 | Leighton et al. | Applicant |
| US2007/0005892(A1) | 2007-01-01 | Mullender et al. | Applicant |
| US2007/0011267(A1) | 2007-01-01 | Overton et al. | Applicant |
| US2007/0014241(A1) | 2007-01-01 | Banerjee et al. | Applicant |
| US2007/0016736(A1) | 2007-01-01 | Takeda et al. | Applicant |
| US2007/0021998(A1) | 2007-01-01 | Laithwaite et al. | Applicant |
| US2007/0038994(A1) | 2007-02-01 | Davis et al. | Applicant |
| US2007/0041393(A1) | 2007-02-01 | Westhead et al. | Applicant |
| US2007/0043859(A1) | 2007-02-01 | Ruul | Applicant |
| US2007/0050522(A1) | 2007-03-01 | Grove et al. | Applicant |
| US2007/0050703(A1) | 2007-03-01 | Lebel | Applicant |
| US2007/0055764(A1) | 2007-03-01 | Dilley et al. | Applicant |
| US2007/0061440(A1) | 2007-03-01 | Sundaram et al. | Applicant |
| US2007/0076872(A1) | 2007-04-01 | Juneau | Applicant |
| US2007/0086429(A1) | 2007-04-01 | Lawrence et al. | Applicant |
| US2007/0094361(A1) | 2007-04-01 | Hoynowski et al. | Applicant |
| US2007/0101377(A1) | 2007-05-01 | Six et al. | Applicant |
| US2007/0118667(A1) | 2007-05-01 | McCarthy et al. | Applicant |
| US2007/0118668(A1) | 2007-05-01 | McCarthy et al. | Applicant |
| US2007/0134641(A1) | 2007-06-01 | Lieu | Applicant |
| US2007/0168517(A1) | 2007-07-01 | Weller | Applicant |
| US2007/0174426(A1) | 2007-07-01 | Swildens et al. | Applicant |
| US2007/0174442(A1) | 2007-07-01 | Sherman et al. | Applicant |
| US2007/0174490(A1) | 2007-07-01 | Choi et al. | Applicant |
| US2007/0183342(A1) | 2007-08-01 | Wong et al. | Applicant |
| US2007/0198982(A1) | 2007-08-01 | Bolan et al. | Applicant |
| US2007/0208737(A1) | 2007-09-01 | Li et al. | Applicant |
| US2007/0219795(A1) | 2007-09-01 | Park et al. | Applicant |
| US2007/0220010(A1) | 2007-09-01 | Ertugrul | Applicant |
| US2007/0244964(A1) | 2007-10-01 | Challenger et al. | Applicant |
| US2007/0245010(A1) | 2007-10-01 | Arn et al. | Applicant |
| US2007/0250467(A1) | 2007-10-01 | Mesnik et al. | Applicant |
| US2007/0250560(A1) | 2007-10-01 | Wein et al. | Applicant |
| US2007/0250611(A1) | 2007-10-01 | Bhogal et al. | Applicant |
| US2007/0253377(A1) | 2007-11-01 | Janneteau et al. | Applicant |
| US2007/0255843(A1) | 2007-11-01 | Zubev | Applicant |
| US2007/0266113(A1) | 2007-11-01 | Koopmans et al. | Applicant |
| US2007/0266311(A1) | 2007-11-01 | Westphal | Applicant |
| US2007/0266333(A1) | 2007-11-01 | Cossey et al. | Applicant |
| US2007/0271375(A1) | 2007-11-01 | Hwang | Applicant |
| US2007/0271385(A1) | 2007-11-01 | Davis et al. | Applicant |
| US2007/0280229(A1) | 2007-12-01 | Kenney | Applicant |
| US2007/0288588(A1) | 2007-12-01 | Wein et al. | Applicant |
| US2008/0005057(A1) | 2008-01-01 | Ozzie et al. | Applicant |
| US2008/0008089(A1) | 2008-01-01 | Bornstein et al. | Applicant |
| US2008/0025304(A1) | 2008-01-01 | Venkataswami et al. | Applicant |
| US2008/0046596(A1) | 2008-02-01 | Afergan et al. | Applicant |
| US2008/0065724(A1) | 2008-03-01 | Seed et al. | Applicant |
| US2008/0065745(A1) | 2008-03-01 | Leighton et al. | Applicant |
| US2008/0071859(A1) | 2008-03-01 | Seed et al. | Applicant |
| US2008/0071987(A1) | 2008-03-01 | Karn et al. | Applicant |
| US2008/0072264(A1) | 2008-03-01 | Crayford | Applicant |
| US2008/0082551(A1) | 2008-04-01 | Farber et al. | Applicant |
| US2008/0086559(A1) | 2008-04-01 | Davis et al. | Applicant |
| US2008/0086574(A1) | 2008-04-01 | Raciborski et al. | Applicant |
| US2008/0103805(A1) | 2008-05-01 | Shear et al. | Applicant |
| US2008/0104268(A1) | 2008-05-01 | Farber et al. | Applicant |
| US2008/0114829(A1) | 2008-05-01 | Button et al. | Applicant |
| US2008/0134043(A1) | 2008-06-01 | Georgis et al. | Applicant |
| US2008/0147866(A1) | 2008-06-01 | Stolorz et al. | Applicant |
| US2008/0147873(A1) | 2008-06-01 | Matsumoto | Applicant |
| US2008/0155061(A1) | 2008-06-01 | Afergan et al. | Applicant |
| US2008/0155614(A1) | 2008-06-01 | Cooper et al. | Applicant |
| US2008/0162667(A1) | 2008-07-01 | Verma et al. | Applicant |
| US2008/0172488(A1) | 2008-07-01 | Jawahar et al. | Applicant |
| US2008/0183721(A1) | 2008-07-01 | Bhogal et al. | Applicant |
| US2008/0189437(A1) | 2008-08-01 | Halley | Applicant |
| US2008/0201332(A1) | 2008-08-01 | Souders et al. | Applicant |
| US2008/0215718(A1) | 2008-09-01 | Stolorz et al. | Applicant |
| US2008/0215730(A1) | 2008-09-01 | Sundaram et al. | Applicant |
| US2008/0215735(A1) | 2008-09-01 | Farber et al. | Applicant |
| US2008/0215750(A1) | 2008-09-01 | Farber et al. | Applicant |
| US2008/0215755(A1) | 2008-09-01 | Farber et al. | Applicant |
| US2008/0222281(A1) | 2008-09-01 | Dilley et al. | Applicant |
| US2008/0222291(A1) | 2008-09-01 | Weller et al. | Applicant |
| US2008/0222295(A1) | 2008-09-01 | Robinson et al. | Applicant |
| US2008/0228574(A1) | 2008-09-01 | Stewart et al. | Applicant |
| US2008/0228920(A1) | 2008-09-01 | Souders et al. | Applicant |
| US2008/0235400(A1) | 2008-09-01 | Slocombe et al. | Applicant |
| US2008/0275772(A1) | 2008-11-01 | Suryanarayana et al. | Applicant |
| US2008/0281950(A1) | 2008-11-01 | Wald et al. | Applicant |
| US2008/0288722(A1) | 2008-11-01 | Lecoq et al. | Applicant |
| US2008/0301670(A1) | 2008-12-01 | Gouge et al. | Applicant |
| US2008/0319862(A1) | 2008-12-01 | Golan et al. | Applicant |
| US2009/0013063(A1) | 2009-01-01 | Soman | Applicant |
| US2009/0016236(A1) | 2009-01-01 | Alcala et al. | Applicant |
| US2009/0029644(A1) | 2009-01-01 | Sue et al. | Applicant |
| US2009/0031367(A1) | 2009-01-01 | Sue | Applicant |
| US2009/0031368(A1) | 2009-01-01 | Ling | Applicant |
| US2009/0031376(A1) | 2009-01-01 | Riley et al. | Applicant |
| US2009/0049098(A1) | 2009-02-01 | Pickelsimer et al. | Applicant |
| US2009/0063704(A1) | 2009-03-01 | Taylor et al. | Applicant |
| US2009/0070533(A1) | 2009-03-01 | Elazary et al. | Applicant |
| US2009/0083228(A1) | 2009-03-01 | Shatz et al. | Applicant |
| US2009/0086741(A1) | 2009-04-01 | Zhang | Applicant |
| US2009/0103707(A1) | 2009-04-01 | McGary et al. | Applicant |
| US2009/0106381(A1) | 2009-04-01 | Kasriel et al. | Applicant |
| US2009/0112703(A1) | 2009-04-01 | Brown | Applicant |
| US2009/0122714(A1) | 2009-05-01 | Kato | Applicant |
| US2009/0125934(A1) | 2009-05-01 | Jones et al. | Applicant |
| US2009/0132368(A1) | 2009-05-01 | Cotter et al. | Applicant |
| US2009/0132648(A1) | 2009-05-01 | Swildens et al. | Applicant |
| US2009/0144412(A1) | 2009-06-01 | Ferguson et al. | Applicant |
| US2009/0150926(A1) | 2009-06-01 | Schlack | Applicant |
| US2009/0157850(A1) | 2009-06-01 | Gagliardi et al. | Applicant |
| US2009/0158163(A1) | 2009-06-01 | Stephens et al. | Applicant |
| US2009/0164331(A1) | 2009-06-01 | Bishop et al. | Applicant |
| US2009/0177667(A1) | 2009-07-01 | Ramos et al. | Applicant |
| US2009/0182815(A1) | 2009-07-01 | Czechowski et al. | Applicant |
| US2009/0182945(A1) | 2009-07-01 | Aviles et al. | Applicant |
| US2009/0187575(A1) | 2009-07-01 | DaCosta | Applicant |
| US2009/0204682(A1) | 2009-08-01 | Jeyaseelan et al. | Applicant |
| US2009/0210549(A1) | 2009-08-01 | Hudson et al. | Applicant |
| US2009/0248787(A1) | 2009-10-01 | Sivasubramanian et al. | Applicant |
| US2009/0248852(A1) | 2009-10-01 | Fuhrmann et al. | Applicant |
| US2009/0248858(A1) | 2009-10-01 | Sivasubramanian et al. | Applicant |
| US2009/0248893(A1) | 2009-10-01 | Richardson et al. | Applicant |
| US2009/0259971(A1) | 2009-10-01 | Rankine et al. | Applicant |
| US2009/0271577(A1) | 2009-10-01 | Campana et al. | Applicant |
| US2009/0271730(A1) | 2009-10-01 | Rose et al. | Applicant |
| US2009/0279444(A1) | 2009-11-01 | Ravindran et al. | Applicant |
| US2009/0287750(A1) | 2009-11-01 | Banavar et al. | Applicant |
| US2009/0307307(A1) | 2009-12-01 | Igarashi | Applicant |
| US2009/0327489(A1) | 2009-12-01 | Swildens et al. | Applicant |
| US2009/0327914(A1) | 2009-12-01 | Adar et al. | Applicant |
| US2010/0005175(A1) | 2010-01-01 | Swildens et al. | Applicant |
| US2010/0011061(A1) | 2010-01-01 | Hudson et al. | Applicant |
| US2010/0023601(A1) | 2010-01-01 | Lewin et al. | Applicant |
| US2010/0030662(A1) | 2010-02-01 | Klein | Applicant |
| US2010/0034470(A1) | 2010-02-01 | Valencia-Campo et al. | Applicant |
| US2010/0036944(A1) | 2010-02-01 | Douglis et al. | Applicant |
| US2010/0070603(A1) | 2010-03-01 | Moss et al. | Applicant |
| US2010/0088367(A1) | 2010-04-01 | Brown et al. | Applicant |
| US2010/0088405(A1) | 2010-04-01 | Huang et al. | Applicant |
| US2010/0100629(A1) | 2010-04-01 | Raciborski et al. | Applicant |
| US2010/0111059(A1) | 2010-05-01 | Bappu et al. | Applicant |
| US2010/0121953(A1) | 2010-05-01 | Friedman et al. | Applicant |
| US2010/0122069(A1) | 2010-05-01 | Gonion | Applicant |
| US2010/0131646(A1) | 2010-05-01 | Drako | Applicant |
| US2010/0150155(A1) | 2010-06-01 | Napierala | Applicant |
| US2010/0192225(A1) | 2010-07-01 | Ma et al. | Applicant |
| US2010/0217801(A1) | 2010-08-01 | Leighton et al. | Applicant |
| US2010/0226372(A1) | 2010-09-01 | Watanabe | Applicant |
| US2010/0257024(A1) | 2010-10-01 | Holmes et al. | Applicant |
| US2010/0257266(A1) | 2010-10-01 | Holmes et al. | Applicant |
| US2010/0257566(A1) | 2010-10-01 | Matila | Applicant |
| US2010/0293479(A1) | 2010-11-01 | Rousso et al. | Applicant |
| US2010/0299439(A1) | 2010-11-01 | McCarthy et al. | Applicant |
| US2010/0312861(A1) | 2010-12-01 | Kolhi et al. | Applicant |
| US2010/0318508(A1) | 2010-12-01 | Brawer et al. | Applicant |
| US2010/0332595(A1) | 2010-12-01 | Fullagar et al. | Applicant |
| US2011/0040893(A1) | 2011-02-01 | Karaoguz et al. | Applicant |
| US2011/0078000(A1) | 2011-03-01 | Ma et al. | Applicant |
| US2011/0078230(A1) | 2011-03-01 | Sepulveda | Applicant |
| US2011/0087769(A1) | 2011-04-01 | Holmes et al. | Applicant |
| US2011/0096987(A1) | 2011-04-01 | Morales et al. | Applicant |
| US2011/0153941(A1) | 2011-06-01 | Spatscheck et al. | Applicant |
| US2011/0191449(A1) | 2011-08-01 | Swildens et al. | Applicant |
| US2011/0238501(A1) | 2011-09-01 | Almeida | Applicant |
| US2011/0238793(A1) | 2011-09-01 | Bedare et al. | Applicant |
| US2011/0252142(A1) | 2011-10-01 | Richardson et al. | Applicant |
| US2011/0252143(A1) | 2011-10-01 | Baumback et al. | Applicant |
| US2011/0258049(A1) | 2011-10-01 | Ramer et al. | Applicant |
| US2011/0276623(A1) | 2011-11-01 | Girbal | Applicant |
| US2012/0036238(A1) | 2012-02-01 | Sundaram et al. | Applicant |
| US2012/0066360(A1) | 2012-03-01 | Ghosh | Applicant |
| US2012/0124184(A1) | 2012-05-01 | Sakata et al. | Applicant |
| US2012/0131177(A1) | 2012-05-01 | Brandt et al. | Applicant |
| US2012/0179839(A1) | 2012-07-01 | Raciborski et al. | Applicant |
| US2012/0198043(A1) | 2012-08-01 | Hesketh et al. | Applicant |
| US2012/0303804(A1) | 2012-11-01 | Sundaram et al. | Applicant |
| US2012/0311648(A1) | 2012-12-01 | Swildens et al. | Applicant |
| US2013/0212300(A1) | 2013-08-01 | Eggleston et al. | Applicant |
| US2013/0268616(A1) | 2013-10-01 | Sakata et al. | Applicant |
| US2013/0339429(A1) | 2013-12-01 | Richardson et al. | Applicant |
| CN1422468(A) | 2003-06-01 | Applicant | |
| CN1605182(A) | 2005-04-01 | Applicant | |
| CN101189598(A) | 2008-05-01 | Applicant | |
| CN101460907(A) | 2009-06-01 | Applicant | |
| EP2008167 | 2008-12-01 | Applicant | |
| JP2003-167810(A) | 2003-06-01 | Applicant | |
| JP2003-167813(A) | 2003-06-01 | Applicant | |
| JP2003522358(A) | 2003-07-01 | Applicant | |
| JP2004-533738(A) | 2004-11-01 | Applicant | |
| JP2007-133896(A) | 2007-05-01 | Applicant | |
| WO2007/007960(A1) | 2007-01-01 | Applicant | |
| WO2007/126837(A3) | 2007-11-01 | Applicant | |
| WO2012/044587(A1) | 2012-04-01 | Applicant |
Non-Patent Literature (91)
- Baglioni et al., “Preprocessing and Mining Web Log Data for Web Personalization”, LNAI 2829, 2003, pp. 237-249.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.Applicant
- Singapore Written Opinion in Application No. 201006836-9, mailed. Oct. 12, 2011 in 12 pages.Applicant
- Singapore Written Opinion in Application No. 201006837-7, mailed Oct. 12, 2011 in 11 pages.Applicant
- Singapore Written Opinion in Application No. 201006874-0, mailed Oct. 12, 2011 in 10 pages.Applicant
- 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.Applicant
- Xu et al., “Decision tree regression for soft classification of remote sensing data”, Remote Sensing of Environment 97 (2005) pp. 322-336.Applicant
- Al-Fares, M. et al., A Scalable, Commodity Data Center Network Architecture, SIGCOMM '08 Proceedings, Aug. 17, 2008, pp. 63-74, 66-68, 70-71, Seattle, WA.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/dsg-tutorial.html; pp. 1-8.Applicant
- Greenberg, A. et al., Networking the Cloud, 29th IEEE International Conference on Distributed Computing Systems (ICDCS 2009), Jun. 22, 2009-Jun. 26, 2009 [online] retrieved from the Internet on Mar. 10, 2011: http://www.cse.ohio-state.edu/icdcs2009/Keynote—files/greenberg-keynote.pdf, pp. 1-45.Applicant
- Greenberg, A. et al., Towards a Next Generation Data Center Architecture: Scalability and Commoditization, SIGCOMM '08: Proceedings of the 2008 SIGCOMM Conference and Co-Located Workshops NSDR '08, WOSN '08, MOBIARCH '08, NETECON '08, & Presto '08, Seattle, WA, Aug. 17-28, 2008, ACM, Aug. 17, 2008, pp. 57-62, New York, NY.Applicant
- Greenberg, A. et al., VL2: A scalable and flexible data center network, SIGCOMM '09, Proceedings of the ACM SIGCOMM 2009 Conference on Data Communication, Aug. 17, 2009, vol. 39, Issue 4, pp. 51-62.Applicant
- International Preliminary Report on Patentability and Written Opinion in PCT/US2010/060567 mailed on Jun. 19, 2012.Applicant
- International Preliminary Report on Patentability and Written Opinion in PCT/US2010/060569 mailed Jun. 19, 2012.Applicant
- International Preliminary Report on Patentability and Written Opinion in PCT/US2010/060573 mailed Jun. 19, 2012.Applicant
- International Search Report and Written Opinion in PCT/US2011/053302 mailed Nov. 28, 2011 in 11 pages.Applicant
- International Search Report and Written Opinion in PCT/US2011/061486 mailed Mar. 30, 2012 in 11 pages.Applicant
- Mysore, R.N. et al., Portland: a scalable fault-tolerant layer 2 data center network fabric, SIGCOMM '09, Proceedings of the ACM SIGCOMM 2009 Conference on Data Communication, Aug. 17, 2009, pp. 39-50.Applicant
- Nilsson et al., IP-Address Lookup Using LC-Tries, IEEE Journalk on Selected Areas of Communication, Jun. 1999, vol. 17, Issue 6, pp. 1083-1092.Applicant
- Singapore Examination Report in Application No. 201006837-7 mailed May 16, 2012.Applicant
- Supplementary European Search Report in Application No. 09727694.3 mailed Jan. 30, 2012 in 6 pages.Applicant
- First Office Action in Chinese Application No. 200980145872.4 dated Nov. 29, 2012.Applicant
- International Search Report and Written Opinion in PCT/US2010/060567 mailed on Mar. 28, 2012.Applicant
- Search Report and Written Opinion in Singapore Application No. 201103333-9 mailed Nov. 19, 2012.Applicant
- Singapore Written Opinion in Application No. 201006836-9, mailed Apr. 30, 2012 in 10 pages.Applicant
- First Office Action in Chinese Application No. 200980119993.1 dated Jul. 4, 2012.Applicant
- First Office Action in Chinese Application No. 200980119995.0 dated Jul. 6, 2012.Applicant
- American Bar Association; Digital Signature Guidelines Tutorial [online]; Feb. 10, 2002 [retrieved 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/dsg-tutorial.html; pp. 1-8.Applicant
- Office Action in Chinese Application No. 200980119995.0 dated Apr. 15, 2013.Applicant
- Office Action in Korean Application No. 10-2011-7002461 mailed May 29, 2013.Applicant
- Preliminary Examination in Chinese Application No. 201180053405.6 dated May 28, 2013. English Translation Not Yet Received.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.Applicant
- “Grid Computing Solutions,” Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/software/grid, 3 pages.Applicant
- “Grid Offerings,” Java.net, retrieved May 3, 2006, from http://wiki.java.net/bin/view/Sungrid/OtherGridOfferings, 8 pages.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.Applicant
- “Scaleable Trust of Next Generation Management (STRONGMAN),” retrieved May 17, 2006, from http://www.cis.upenn.edu/˜dsl/STRONGMAN/, 4 pages.Applicant
- “Sun EDA Compute Ranch,” Sun Microsystems, Inc., retrieved May 3, 2006, from http://sun.com/processors/ranch/brochure.pdf, 2 pages.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.Applicant
- “Sun N1 Grid Engine 6,” Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/software/gridware/index.xml, 3 pages.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.Applicant
- “The Softricity Desktop,” Softricity, Inc., retrieved May 3, 2006, from http://www.softricity.com/products/, 3 pages.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.Applicant
- “XenFaq,” retrieved Nov. 8, 2005, from http://wiki.xensource.com/xenwiki/XenFaq?action=print, 9 pages.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.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.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.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.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.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—papers/clark/clark.pdf, 14 pages.Applicant
- Coulson, D., “Network Security Iptables,” Apr. 2003, Linuxpro, Part 2, retrieved from http://davidcoulson.net/writing/lxf/38/iptables.pdf, 4 pages.Applicant
- Coulson, D., “Network Security Iptables,” Mar. 2003, Linuxpro, Part 1, retrieved from http://davidcoulson.net/writing/lxf/39/iptables.pdf, 4 pages.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.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.Applicant
- First Office Action in Chinese Application No. 200980111426.1 mailed Feb. 16, 2013.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.Applicant
- International Preliminary Report on Patentability in PCT/US2007/007601 mailed Sep. 30, 2008 in 8 pages.Applicant
- International Search Report and Written Opinion in PCT/US07/07601 mailed Jul. 18, 2008 in 11 pages.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/˜dls/STRONGMAN/Papers/df.pdf, 10 pages.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.Applicant
- Kenshi, P., “Help File Library: Iptables Basics,” Justlinux, retrieved Dec. 1, 2005, from http://www.justlinux.com/nhf/Security/Iptables—Basics.html, 4 pages.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.Applicant
- Office Action in Candian Application No. 2741895 dated Feb. 25, 2013.Applicant
- Office Action in Japanese Application No. 2011-502138 mailed Feb. 1, 2013.Applicant
- Office Action in Japanese Application No. 2011-502140 mailed Dec. 7, 2012.Applicant
- Office Action in Japanese Application No. 2012-052264 mailed Dec. 11, 2012 in 26 pages.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—22-5057752.html, 8 pages.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/˜lars/studies/master/StrandLars-master.pdf, 158 pages.Applicant
- Supplementary European Search Report in Application No. 07754164.7 mailed Dec. 20, 2010 in 7 pages.Applicant
- Supplementary European Search Report in Application No. 09728756.9 mailed Jan. 8, 2013.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.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.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.Applicant
- Virtual Iron Software Home, Virtual Iron, retrieved May 3, 2006, from http://www.virtualiron.com/, 1 page.Applicant
- Waldspurger, CA., “Spawn: A Distributed Computational Economy,” Feb. 1992, IEEE Transactions on Software Engineering, 18(2): 103-117, 15 pages.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.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.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.Applicant
- 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).Applicant
- Bennami, M., et al., Resource Allocation for Autonomic Data Centers Using Analytic Performance Models, 2005, IEEE, 12 pages.Applicant
- Chipara et al, “Realtime Power-Aware Routing in Sensor Network”, IEEE, 2006, 10 pages.Applicant
- International Preliminary Report on Patentability in PCT/US2011/053302 mailed Apr. 2, 2013.Applicant
- International Preliminary Report on Patentability in PCT/US2011/061486 mailed May 22, 2013.Applicant
- Kounev, S., et al., Autonomic QoS-Aware Resource Management in Grid Computing Using Online Performance Models, 2007, ICST, Valuetools, 2007, 10 pages.Applicant
- Office Action in Canadian Application No. 2726915 dated May 13, 2013.Applicant
- Office Action in Chinese Application No. 200780020255.2 dated Mar. 4, 2013.Applicant
- Office Action in Japanese Application No. 2011-516466 mailed Mar. 6, 2013.Applicant
- Second Office Action in Chinese Application No. 200980119993.1 dated Mar. 12, 2013.Applicant
- First Office Action in Chinese Application No. 200980111422.3 dated Apr. 13, 2012.Applicant
- Second Office Action in Chinese Application No. 200980111426.1 mailed Dec. 25, 2013.Applicant
- Office Action in Indian Application No. 3742/KOLNP/2008 dated Nov. 22, 2013.Applicant
- First Office Action in Japanese Application No. 2011-502139 dated Nov. 5, 2013.Applicant