# Patent

## Title
Locality based content distribution

## Abstract

A system and method for content distribution are provided. A content provider generates a network topology having one or more subnetworks made up of content sources. The content provider segments content, such as applications, into segments for distribution. The content provider then distributes the content such that for each identified subnetwork, each content segment is distributed to a content source. Subsequent, client computing device requests for content can be serviced by selecting a content source in a particular subnetwork selected for delivering the requested content to the client computing device to minimize traffic flow of the requested content through the nodes of the distribution network.

## Background
CROSS REFERENCE TO RELATED APPLICATIONS
This application is a continuation of U.S. patent application Ser. No. 13/614,714, now U.S. Pat. No. 8,438,263, entitled “LOCALITY BASED CONTENT DISTRIBUTION” and filed on Sep. 13, 2012, which is in turn a continuation of U.S. patent application Ser. No. 13/296,189, now U.S. Pat. No. 8,275,874 entitled “LOCALITY BASED CONTENT DISTRIBUTION” and filed Nov. 14, 2011, which is in turn a continuation of U.S. patent application Ser. No. 13/170,102, which is now U.S. Pat. No. 8,060,561, entitled “LOCALITY BASED CONTENT DISTRIBUTION” and filed on Jun. 27, 2011, which is in turn a continuation of U.S. patent application Ser. No. 12/060,124, which is now U.S. Pat. No. 7,970,820, entitled “LOCALITY BASED CONTENT DISTRIBUTION” and filed on Mar. 31, 2008, the disclosures of which are incorporated herein by reference.


BACKGROUND
Generally described, computing devices and communication networks can be utilized to exchange information. In a common application, a computing device can request content from another computing device via the communication network. For example, a user at a personal computing device can utilize a software browser application to request a Web page from a server computing device via the Internet. In such embodiments, the user computing device can be referred to as a client computing device and the server computing device can be referred to as a content provider.
Content providers are generally motivated to provide requested content to client computing devices often with consideration of efficient transmission of the requested content to the client computing device and/or consideration of a cost associated with the transmission of the content. For larger scale implementations, a content provider may receive content requests from a high volume of client computing devices which can place a strain on the content provider's computing resources. Additionally, the content requested by the client computing devices may have a number of components, which can further place additional strain on the content provider's computing resources.
With reference to an illustrative example, a requested Web page, or original content, may be associated with a number of additional resources, such as images or videos, 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 would provide client computing devices data associated with the Web page as well as the data associated with the embedded resources.
In one embodiment, a content provider can utilize additional content sources as part of a content distribution network to provide data to client computing devices. Examples of the additional content sources that can be part of the content distribution network include network-based storage resources or points of presence, edge network computing devices, peer or registered computing devices, and the like. Traditional content distribution networks can become deficient, however, with the repetitive transmission of requested content (per a client computing device request) across network resource nodes (e.g., routers). For example, randomized selection of a distributed network content source can result the transmission of content across a number of distribution network nodes. Such inefficiencies can result in content distribution bottlenecks for the content distribution network.



DESCRIPTION OF THE DRAWINGS
The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
FIG. 1 is a block diagram illustrative of content delivery environment including a number of client computing devices, content provider, various third party content providers, and a content delivery network service provider;
FIG. 2 is a block diagram of the content delivery environment of FIG. 1 illustrating the registration of third party content provider with a content provider;
FIG. 3 is a block diagram illustrative of a model of a content provider distribution network;
FIG. 4 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation and processing of a content request from a client computing device to a content provider;
FIGS. 5A-5C are block diagrams of the content delivery environment of FIG. 1 illustrating the generation of content requests by a client computing device to a content source corresponding to content sources of a subnetwork corresponding to a content provider distribution network;
FIG. 6 is a flow diagram illustrative of a content distribution routine implemented by a content provider;
FIG. 7 is a flow diagram illustrative of a request routing routine implemented by a content provider; and
FIG. 8 is a flow diagram illustrative a resource request processing routine implemented by a client computing device for generating content requests to a content source corresponding to a subnetwork of a content provider distribution network.



DETAILED DESCRIPTION
Generally described, the present disclosure is directed to the management and processing of resource requests made by client computing devices. Specifically, aspects of the disclosure will be described with regard to the utilization, by a content provider, of topology information to define various subnetworks of content sources for a content distribution network. The content provider then distributes content to the content sources in each of the subnetworks such that content can be made available to requesting client computing devices from any of the subnetworks.
In one embodiment, as client computing device content requests are processed, the content provider provides an identification of content sources that are capable of providing the requested content (or portions thereof). The client computing devices can then request the content (or content portions) from the identified content sources. Alternatively, the client computing devices can identify the appropriate content providers without requiring the identification information from the content provider, such as through the utilization of a communication protocol. In both embodiments, the content sources that are identified to receive the content request are selected in a manner to minimize the network traffic associated with the content request through the nodes of the content provider distribution network. Although various aspects of the disclosure will be described with regard to illustrative examples and embodiments, one skilled in the art will appreciate that the disclosed embodiments and examples should not be construed as limiting.
FIG. 1 is a block diagram illustrative of content delivery environment 100 for the management and processing of content requests. As illustrated in FIG. 1, the content delivery environment 100 includes a number of client computing devices 102 (generally referred to as clients) for requesting content from a content provider and/or a CDN service provider. In an illustrative embodiment, the client computing devices 102 can correspond to a wide variety of computing devices including personal computing devices, laptop computing devices, hand-held computing devices, terminal computing devices, mobile devices, wireless devices, various electronic devices and appliances and the like. In an illustrative embodiment, the client computing devices 102 include necessary hardware and software components for establishing communications over a communication network 108, such as a wide area network or local area network. For example, the client computing devices 102 may be equipped with networking equipment and browser software applications that facilitate communications via the Internet or an intranet. Although the client computing devices 102 may be described in accordance with a client-server network model, one skilled in the relevant art will appreciate that the client computing devices 102 correspond to computing devices acquiring content from another computing devices, including, but not limited to, client-server network models, peer-to-peer network models, and the like.
The content delivery environment 100 can also include a content provider 104 in communication with the one or more client computing devices 102 via the communication network 108. The content provider 104 illustrated in FIG. 1 corresponds to a logical association of one or more computing devices associated with a content provider. Specifically, the content provider 104 can include a web server component 110 corresponding to one or more server computing devices for obtaining and processing requests for content (such as Web pages) from the client computing devices 102. The content provider 104 can further include an origin server component 112 and associated storage component 114 corresponding to one or more computing devices for obtaining and processing requests for network resources from the distributed network content sources. One skilled in the relevant art will appreciate that the content provider 104 can be associated with various additional computing resources, such additional computing devices for administration of content and resources, DNS name servers, and the like. For example, although not illustrated in FIG. 1, the content provider 104 can be associated with one or more DNS name server components that would be authoritative to resolve client computing device DNS queries corresponding to a domain of the content provider.
With continued reference to FIG. 1, the content delivery environment 100 can further include a CDN service provider 106 in communication with the one or more client computing devices 102 and the content providers 104 via the communication network 108. The CDN service provider 106 illustrated in FIG. 1 corresponds to a logical association of one or more computing devices associated with a CDN service provider. Specifically, the CDN service provider 106 can include a number of Point of Presence (“POP”) locations 116, 122, 128 that correspond to nodes on the communication network 108. Each POP 116, 122, 128 includes a DNS component 118, 124, 130 made up of a number of DNS server computing devices for resolving DNS queries from the client computers 102. Each POP 116, 122, 128 also includes a resource cache component 120, 126, 132 made up of a number of cache server computing devices for storing resources from content providers and transmitting various requested resources to various client computers. The DNS components 118, 124, and 130 and the resource cache components 120, 126, 132 may further include additional software and/or hardware components that facilitate communications including, but not limited, load balancing or load sharing software/hardware components.
In an illustrative embodiment, the DNS component 118, 124, 130 and resource cache component 120, 126, 132 are considered to be logically grouped, regardless of whether the components, or portions of the components, are physically separate. Additionally, although the POPs 116, 122, 128 are illustrated in FIG. 1 as logically associated with the CDN service provider 106, the POPs will be geographically distributed throughout the communication network 108 in a manner to best serve various demographics of client computing devices 102. Additionally, one skilled in the relevant art will appreciate that the CDN service provider 106 can be associated with various additional computing resources, such additional computing devices for administration of content and resources, and the like.
The content delivery environment 100 can further include a number of third party content providers 134 that are registered with the content provider 104 (directly or indirectly). The content provider 104 can utilize the third party content providers 134 to provide content, or content portions, as peer computing devices to requesting client computing devices 102 as will be described in greater detail below. The third party content providers 134 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. Additionally, the third party content providers 134 can include additional hardware and/or software components for delivering content to other computing devices via the communication network 108, such as Web server computing device, proxy server computing device, etc. As will be explained in greater detail below, the third party content providers 134 can obtain content specifically for distribution to client computing devices 102. In still a further embodiment, the third party content providers 134 can also be client computing devices 102 that have registered with the content provider 104 and can provide previously downloaded content to other client computing devices 102.
Even further, the content delivery environment 100 can include a network-based memory 136 which can be utilized by the content provider 104 and/or CDN service provider 106 to manage content.
One skilled in the relevant art will appreciate that the components and configurations provided in FIG. 1 are illustrative in nature. Additionally, one skilled in the relevant art will appreciate that the CDN provider 106, third party providers 134 and/or network-based storage 136 may be omitted altogether from the content delivery environment 100. Still further, the CDN provider 106, third party providers 134 and/or network-based storage 136 may be affiliated directly with the content provider 104 or indirectly serve as at least partial content stores in the content distribution network. Accordingly, additional or alternative components and/or configurations, especially regarding the additional components, systems and subsystems for facilitating communications may be utilized.
With reference now to FIGS. 2-5, the interaction between various components of the content delivery environment 100 of FIG. 1 will be illustrated. For purposes of the example, however, the illustration has been simplified such that many of the components utilized to facilitate communications are not shown. One skilled in the relevant art will appreciate that such components can be utilized and that additional interactions would accordingly occur without departing from the spirit and scope of the present disclosure.
With reference to FIG. 2, an illustrative interaction for registration of third party content providers 134 with the content provider 104 will be described. As will be described in greater detail below, the content provider 104 can utilize the third party content providers 134 to provide content to requesting client computing devices. As illustrated in FIG. 2, the content hosting registration process begins with registration of the third party content providers 134 with the content provider 104. In an illustrative embodiment, the third party content providers 134 utilize a registration application program interface (“API”) to register with the content provider 104 such that the third party content providers 134 can provide content on behalf of the content provider 104 or the CDN service provider 106 on behalf of the content provider 104. The registration API includes the identification of the computing devices associated with the third party content providers 134 that will provide requested resources on behalf of the content provider 104. Additionally, the registration API can include additional identification information used by the content provider 104 to identify content previously downloaded by the third party content providers 134 and that is available for downloading by other client computing devices 102.
One skilled in the relevant art will appreciate that upon registration, the content provider 104 can begin to direct requests for content from client computing devices 102 to the third party content providers 134. With continued reference to FIG. 2, upon receiving the registration API, the content provider 104 obtains and processes the registration information. In an illustrative embodiment, the content provider 104 can use the registration information to identify the criteria used to direct client computing device content requests to the specific third party content provider 134. As will be described in greater detail below, in one embodiment, the content provider 104 selects content sources, such as third party content providers 134, as a function of a model of the network topology of the content provider's distribution network. For example, the content provider 104 can select a content source according to a network proximity to a client computing device 102 that mitigates the number of distribution network nodes that are traversed by data exchanged between the client computing device and an identified content source, such as a third party content provider 134.
In another embodiment, the content provider 104 can use additional information, in conjunction with the network topology information, to select an appropriate third party registration server (and other content source). The content provider 104 can also use the registration information to identify content previously downloaded by the third party content providers 134 (such as acting in the capacity as a client computing device 102). In still a further embodiment, the content provider 104 can also use the registration information to establish, or otherwise confirm, financial or account information that the content provider 104 will utilize to reconcile with the third party content provider 134 for content provided to client computing devices. For example, the financial or account information can correspond to account information for a particular financial institution, user identifiers for additional third party services utilized to exchange value between parties, or other information utilized in accordance with a particular type of reconciliation used between the content provider 104 and the third party content provider 134. One skilled in the relevant art will appreciate that various types of additional information may be generated or collected by the content provider 104.
The content provider 104 returns a confirmation of the registration of the third party content provider 134. Additionally, in an illustrative embodiment, the content provider 104 can begin providing content to the third party content provider 134, or instructions for downloading content from a cache server component of a POP, such as POP 116, of a CDN provider 106. An illustrative routine for the distribution of content to content sources, such as third party content providers 134, will be described below with regard to FIG. 6. The third party content provider 134 obtains the confirmation and begins performing any additional activity in correspondence with the confirmed registration, such as preparing previously downloaded content or downloading identified content in anticipation of incoming requests from the client computing devices 102.
Turning now to FIG. 3, in an illustrative embodiment, the content provider 104 may utilize network topology information to generate a model of the distribution network 300 for purposes of distributing content to content sources and associating client computing devices with content sources. As illustrated in FIG. 3, the model 300 can correspond to a multi-level network in which a plurality of computing devices are grouped into a first level. The computing devices can correspond to content sources that provide content to other computing devices. Additionally, the computing devices can also correspond to client computing devices 102 that request content from content sources. Thus, each computing device may act as a content source only, a client computing device only, or a combination of content source and client computing device. Accordingly, the computing devices will be generally referred to as client/content sources 302. The first level nodes (nodes 302A-302E) are grouped according to shared nodal connections in the distribution network, such as nodes 304A, 304B and 304C. As illustrated in FIG. 3, nodes 304A-304C represent a second level in the distribution network model 300. Nodes 304A-304C may correspond to networking equipment, such as routers, switch, etc. In such an embodiment, router node 304A would be considered a parent node to children client/content source nodes 302A, 302B and 302C and router node 304C would be considered a parent node to children client/content source nodes 302D and 302E.
In a similar manner, the second level nodes, nodes 304A-C, may also be grouped together to form a subnetwork of the distribution network for providing content based on common network node configurations. For example, nodes 304A-C may represent children nodes of a datacenter node, such as node 306. Still further, third level node, such as node 306, may be grouped with other node(s) not illustrated in the distribution network model 300 to be considered as a subnetwork of the distribution network for providing content. In an illustrative embodiment, the distribution network model 300 can include any number of levels and subnetworks. Accordingly, the nodes and subnetworks illustrated in FIG. 3 are illustrative in nature and should not be construed as limiting.
As previously described, the content provider 104 can distribute content to the content sources 302 in the defined distribution network subnetworks such that copies of the content, which may be segmented, can be found and provided to client computing devices 102 from the subnetworks. Accordingly, the content provider 104 may distribute content to the various third party computing devices in the subnetworks as part of the processing of client computing device requests or in anticipation of client computing device requests. For example, if a content provider 104 would need to distribute an application, the content provider would provide an identification of the various subnetworks in the distribution network (such as the subnetworks represented by nodes 302A-302C and 302D-302E, respectively) and distribute the application to the subnetwork as a whole. In turn, a copy of the application, either in whole or as a set of content segments, would reside in one or more of the client/content sources 302. An illustrative routine for distributing content will be described with regard to FIG. 6.
In an illustrative embodiment, the content provider 104 selects (or provides an identification of) specific subnetwork(s) utilized to provide the content to the client computing devices 102 as a function of a network proximity to the client computing device among other factors. With reference to FIG. 3, the selection of a subnetwork can correspond to an identification of the specific subnetwork (and a corresponding content source) in which the client computing device 102 resides. In such an embodiment, the information flow through the nodes of the distribution network associated with the delivery of content would be minimized because of the close nodal proximity. For example, assume that if the content provider 104 would wish to distribute an application to every computing device in the distribution network, a copy of the application would initially be distributed to a single computing device in each subnetwork (as described above). In accordance with the present disclosure, each additional client/content source could then attempt to acquire the application from another client/content source within the same defined subnetwork. By limiting content sources to within the same defined subnetwork, or a subnetwork with a close network proximity, the amount of information corresponding to the application passed through other nodes in the distribution would be minimized. If the client computing device and the content sources are child nodes, the responsive content information would only pass through one additional node, such as a router node.
With reference now to FIG. 4, after completion of the registration processes illustrated in FIG. 2, a client computing device 102 subsequently generates a content request that is received and processed by the content provider 104, such as through the Web server 110. In accordance with an illustrative embodiment, the request for content can be in accordance with common network protocols, such as the hypertext transfer protocol (“HTTP”). Upon receipt of the content request, the content provider 104 identifies the appropriate responsive content. In an illustrative embodiment, the requested content can correspond to a Web page that is displayed on the client computing device 102 via the processing of information, such as hypertext markup language (“HTML”), extensible markup language (“XML”), and the like. The requested content can also include a number of embedded resource identifiers that correspond to resource objects that should be obtained by the client computing device 102 as part of the processing of the requested content. The embedded resource identifiers can be generally referred to as resource identifiers or resource URLs. In one embodiment, the client computing device 102 may process the requested content and automatically begin requesting the resources identified by the resource URLs. Alternatively, the requested content may correspond to a list of available content, in which the client computing device 102 generates requests for the content (as represented by resource URLs) in response to a user selection. Still further, although the client computing device 102 requests have been described in conjunction with a Web page content request, one skilled in the relevant art will appreciate that the content request may originate from a number of other sources/approaches and the content request interaction illustrated in FIG. 4 may be omitted.
With reference now to FIGS. 5A and 5B, alternative steps implemented by a client computing device 102 to obtain requested content (e.g., content corresponding to the embedded URLs) from the content provider 104 will be described. With reference to FIG. 5A, the client computing device 102 initiates a resource request. The resource request can correspond to a variety of network communication protocols, including but not limited, to hypertext transfer protocol (“HTTP”), file transfer protocol (“ftp”), and any one of a variety of communications protocols. In turn, the content provider 104 processes the content request and provides identification information that includes a set of network addresses of content sources. Examples of the identification information could be in the form of a list of content sources, metadata identifying content source (e.g., a torrent file), and the like. The identification information is then returned to the client computing device 102. As previously described, in one embodiment, the identification information generated by the content provider 104 can be processed in an attempt to minimize the traffic through the distribution network nodes.
With continued reference to FIG. 5A, in addition to the set of network addresses, the content provider 104 also provides reconciliation information, such as electronic tokens, for use by the third party content providers 134. In an illustrative embodiment, the reconciliation information will be provided accompanied by any resource request submitted by the client computing device 102 to an identified third party content provider 134. For additional security/integrity purposes, the content provider 104 can include additional information in the electronic tokens, such as a client computing device identifier information, timestamp information, third party content provider 134 identifiers, information based on such information, and the like. For example, a client computing device identifier can be incorporated into the electronic information, such as via a hashing algorithm, in an effort to limit unauthorized duplication of the electronic tokens or fraudulent or repetitive reconciliations by a third party content provider 134. One skilled in the relevant art will appreciate that any one of a variety of electronic token, micropayment, or credit management methodologies may be incorporated in the content delivery environment 100 for reconciling content provided by a third party content provider 134.
With reference now to FIG. 5B, the client computing device 102 utilizes the information provided by the content provider 104 and transmits content requests to the identified content sources. If the content source is a third party content provider 134, the content requests can include the reconciliation information to be used by the third party content provider 134 to reconcile with the content provider 104 (either directly or through a proxy).
With reference now to FIG. 5C, in an alternative embodiment, the client computing device 102 does not transmit an initial request to the content provider 104 to obtain an identification of the available content sources. In this embodiment, the client computing device 102 may implement some additional processing that facilitates the identification of the appropriate content source. For example, the client computing device could utilize a hashing algorithm that determines the content source based, as least in part, on a hash of a client identifier or client identification information. As described in FIG. 5C, the client computing device 102 then utilizes the information it calculated and transmits content requests to the identified content sources. If the content source is a third party content provider 134, the content requests can include the reconciliation information to be used by the third party content provider 134 to reconcile with the content provider 104 (either directly or through a proxy).
With reference now to FIG. 6, an illustrative content distribution routine 600 implemented by the content provider 104 will be described. At block 602, the content provider 104 associates the requested content into a set of segments. As previously described, the requested content can be subdivided into a number of content segments or content chunks utilizing a variety of methodologies. At block 604, the content provider 104 obtains network topology information for the distribution network. As illustrated in FIG. 3, in an illustrative embodiment, the network topology information can correspond to a model 300 that defines various distribution network subnetworks including one or more client/content sources 302.
At block 606, the content provider 104 selects a first distribution subnetwork as defined in the model 300. As previously described, the definition of the subnetwork can correspond to a grouping of nodes of the distribution network and can correspond to more than one level of a distribution network. At block 608, the content provider 104 designates at least one client/content source within the subnetwork to be distributed the designated content segment. At decision block 610, a test is conducted to determine whether additional content segments in the content are to be distributed. If so, the routine 600 returns to block 606 to designate at least client/content source to receive the additional segments. In one embodiment, the same client/content source within a single subnetwork may be utilized to maintain all the content segments. Alternative, in another embodiment, the content segments may be distributed to various client/content sources within a subnetwork in accordance with a variety of distribution techniques including, but not limited, round robin selection, random selection, load balancing, etc.
Once all the content segments have been distributed within a subnetwork, at decision block 612, a test is conducted to determine whether additional subnetworks exist in the distribution network. If so, at block 614, the content provider 104 selects a next subnetwork in the distribution network and the routine 600 returns to block 606 in which all the content segments will be distributed to clients/content sources in the next subnetwork. Once there are no remaining subnetworks in the distribution network at decision block 612, the routine 600 terminates at block 616.
With reference now to FIG. 7, one embodiment of a content request processing routine 700 implemented by the content provider 104 for processing a resource request from a client computing device 102 will be described. At block 702, the content provider 104 receives a content request from the client computing device 102. As previously described, the embedded URLs can correspond to content to be requested in conjunction with a Web page provided by the content provider 104. In an illustrative embodiment, the client computing device 102 may correspond to client/content source in the distribution network topology.
At block 704, the content provider 104 associates the requested content into one or more content segments. As previously described, the requested content can be subdivided into a number of content segments or content chunks utilizing a variety of methodologies. At block 706, the content provider 104 identifies one or more client/content sources that can provide the requested content segment or content chunk. In an illustrative embodiment, the determination of which clients/content sources can be a function of the content previously provided by the content provider 104. Additionally, or alternatively, the determination of which third party content providers 134 and/or resource cache components can be a function of network proximity. In an illustrative embodiment, the network proximity can be defined in terms of a determination of the minimal number of content distribution nodes that the requested content would traverse between the client computing device and the potential content source. At decision block 708, a test is conducted to determine whether additional resource segments exist. If so, the routine 700 returns to block 706 for an identification of additional client/content sources for the additional resource segments. One skilled in the relevant art will appreciate, however, that routine 700 may be implemented in a manner such that the content provider 104 identifies third party content providers 134 and/or resource cache components for the requested content as a whole and not for content segments.
Once all the appropriate client/content sources have been identified, at block 710, the content provider 104 transmits identification and appropriate reconciliation information (e.g., electronic tokens) responsive to the client computing device 102 request. As previously described, the identification information may be in the form of a list or as metadata that can be processed by the client computing device.
In the event that one or more of the client/content sources corresponds to third party content provider 134, at block 712, the content provider 104 obtains reconciliation requests from one or more third party content providers 134. For purposes of this illustrative embodiment, it is assumed that the client computing device 102 has been successful in obtaining at least one content segment or content chunk from a third party content provider 134. As previously discussed, the third party content providers 134 may transmit the reconciliation requests upon completion of a content segment download to a client computing device 102 or alternatively, asynchronously, such as in a batch processing. The reconciliation requests can also include additional metric information or utilization information collected by the third party content provider 134 in processing the resource request from the client computing device 102.
At block 714, the content provider 104 reconciles with the third party content providers 134. As previously disclosed, the content provider 104 can reconcile in a variety of manners. In one example, the content provider 104 may credit a financial institution account associated with the third party content provider 134 or cause such an account to be credited. In another example, the content provider 104 may interface with a network resource, such as Web service or Web site, to have a credit provided to an account or profile associated with third party content provider 134 (e.g., a rewards program). In still another example, the content provider 104 may increment tracking information that tracks the transaction information. Such tracking information may be utilized by either the content provider 104 or the third party content provider 134 at a later date. At block 716, the routine 700 terminates.
With reference now to FIG. 8, a request routing processing routine 800 implemented by a client computing device 102 will be described. At block 802, the client computing device 102 transmits a content request to the content provider 104. As previously stated, in an illustrative embodiment, the content request corresponds to the processing of embedded URLs in content (e.g., a Web page) provided by the content provider 104. At block 804, the client computing device 102 obtains a set of network addresses from the content provider 104 in resolution of the DNS query content provider 104 that are responsive to the client request. As previously described, the set of network addresses corresponds to an identification of client/content sources that can process the resource request from the client computing device 102. Additionally, the set of network addresses may be prioritized or filtered based of the network proximity of the potential content sources to the client computing device. As previously discussed, in an illustrative embodiment, the requested content can be divided into various content segments or content chunks. Accordingly, the set of network addresses can be specified for each identifiable content segment or content chunk or alternatively, for the cumulative set of content segments/chunks.
At block 806, the client computing device 102 transmits a request for content to the identified content sources in the set of network addresses. Additionally, the request for content can include the additional reconciliation information that will be utilized by the third party content provider 134 to reconcile with the content provider 104. At decision block 808, a test is conducted to determine whether additional content segments are to be requested. If so, the routine 800 returns to block 806 for request of the content from the content sources. If not, or if the content is otherwise not able to be segmented, the routine terminates at block 810.
It will be appreciated by those skilled in the art and others that all of the functions described in this disclosure may be embodied in software executed by one or more processors of the disclosed components and mobile communication devices. The software may be persistently stored in any type of non-volatile storage.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art. It will further be appreciated that the data and/or components described above may be stored on a computer-readable medium and loaded into memory of the computing device using a drive mechanism associated with a computer readable storing the computer executable components such as a CD-ROM, DVD-ROM, or network interface further, the component and/or data can be included in a single device or distributed in any manner. Accordingly, general purpose computing devices may be configured to implement the processes, algorithms and methodology of the present disclosure with the processing and/or execution of the various data and/or components described above.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.

## Claims

1. A system for managing content, the system comprising:
at least one computing device for receiving a request for content from a client computing device, wherein the at least one computing device is associated with a distribution network, wherein the distribution network includes a plurality of subnetworks, and wherein individual subnetworks in the distribution network include a source of the requested content within the subnetwork, the at least one computing device configured, responsive to the request for content from the client computing device, to:
identify a subnetwork in the distribution network for providing the requested content based on a network locality of the client computing device relative to subnetworks in the distribution network; and
provide identification information for the source of the requested content in the identified subnetwork.

2. The system as recited in claim 1, wherein the at least one computing device is further configured to distribute the requested content so that the requested content is distributed among one or more content sources in each subnetwork in the distribution network.

3. The system as recited in claim 2, wherein distributing the requested content comprises distributing the requested content to one or more content sources in each subnetwork.

4. The system as recited in claim 2, wherein distributing the requested content comprises distributing the requested content to each subnetwork that does not already have one or more content sources including the requested content.

5. The system as recited in claim 1, wherein the identification information includes network address information for the source of the requested content in the identified subnetwork.

6. The system as recited in claim 1, wherein the identification information includes reconciliation information to be provided to the source of the requested content in the identified subnetwork.

7. A system for managing content at a content provider, the system comprising:
at least one computing device associated with a distribution network for receiving a request for content from a client computing device, wherein the distribution network includes a plurality of subnetworks, wherein individual subnetworks correspond to two or more logically grouped nodes within the distribution network, and wherein individual subnetworks include a source of the requested content within the subnetwork, the at least one computing device configured to:
determine a content source from a subnetwork for providing at least a portion of the requested content to the client computing device such that the determined content source will minimize distribution node traffic between one or more parent nodes to the client computing device and the content source; and
responsive to the request for content from the client computing device, provide identification information identifying the determined content source for providing at least a portion of the requested content.

8. The system as recited in claim 7, wherein the identification information includes network address information corresponding to the determined content source.

9. The system as recited in claim 7, wherein determining a content source for providing at least a portion of the content includes identifying at least one peer computing device for providing at least a portion of the requested content.

10. The system as recited in claim 9, wherein the at least one computing device is further configured to:
obtain reconciliation requests from the peer computing device, wherein the reconciliation requests include reconciliation tokens received from client computing devices; and
reconcile the reconciliation requests from the peer computing devices.

11. A computer-implemented method for managing content, the method comprising:
obtaining, at a computing device corresponding to a distribution network, a request for content from a client computing device, wherein the distribution network includes a plurality of subnetworks, and wherein individual subnetworks in the distribution network include a source of the requested content within the subnetwork; and
responsive to the request for content from the client computing device:
identifying a subnetwork in the distribution network for providing the requested content based on a network locality of the client computing device relative to subnetworks in the distribution network; and
providing identification information for the source of the requested content in the identified subnetwork.

12. The method as recited in claim 11 further comprising distributing the requested content so that the requested content is distributed among one or more content sources in each subnetwork in the distribution network.

13. The method as recited in claim 12, wherein distributing the requested content comprises distributing the requested content to one or more content sources in each subnetwork.

14. The method as recited in claim 12, wherein distributing the requested content comprises distributing the requested content to each subnetwork that does not already have one or more content sources including the requested content.

15. The method as recited in claim 11, wherein the identification information includes network address information for the source of the requested content in the identified subnetwork.

16. The method as recited in claim 11, wherein the identification information includes reconciliation information to be provided to the source of the requested content in the identified subnetwork.

17. A computer-implemented method for managing content, the method comprising:
obtaining, at a computing device corresponding to a distribution network, a request for content from a client computing device, wherein the distribution network includes a plurality of subnetworks, wherein individual subnetworks correspond to two or more logically grouped nodes within the distribution network, and wherein individual subnetworks include a source of the requested content within the subnetwork;
determining a content source from a subnetwork for providing at least a portion of the requested content to the client computing device such that the determined content source will minimize distribution node traffic between one or more parent nodes to the client computing device and the content source; and
responsive to the request for content from the client computing device, providing identification information identifying the determined content source for providing at least a portion of the requested content.

18. The method as recited in claim 17, wherein the identification information includes network address information corresponding to the determined content source.

19. The method as recited in claim 17, wherein determining a content source for providing at least a portion of the content includes identifying at least one peer computing device for providing at least a portion of the requested content.

20. The method as recited in claim 19 further comprising:
obtaining reconciliation requests from the peer computing device, wherein the reconciliation requests includes reconciliation tokens received from client computing devices; and
reconciling the reconciliation requests from the peer computing devices.