WO2008017504A1 - Système de distribution de contenu pour un objet numérique - Google Patents

Système de distribution de contenu pour un objet numérique Download PDF

Info

Publication number
WO2008017504A1
WO2008017504A1 PCT/EP2007/007106 EP2007007106W WO2008017504A1 WO 2008017504 A1 WO2008017504 A1 WO 2008017504A1 EP 2007007106 W EP2007007106 W EP 2007007106W WO 2008017504 A1 WO2008017504 A1 WO 2008017504A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
delivery
cache
digital data
peer
Prior art date
Application number
PCT/EP2007/007106
Other languages
English (en)
Inventor
Adam Twiss
David Ferguson
Original Assignee
Velocix Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from GB0615963A external-priority patent/GB2440774B/en
Application filed by Velocix Limited filed Critical Velocix Limited
Publication of WO2008017504A1 publication Critical patent/WO2008017504A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • H04L67/1078—Resource delivery mechanisms
    • H04L67/1085—Resource delivery mechanisms involving dynamic management of active down- or uploading connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1087—Peer-to-peer [P2P] networks using cross-functional networking aspects
    • H04L67/1091—Interfacing with client-server systems or between P2P systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching

Definitions

  • the present invention relates to a network and method for content delivery from multiple data sources, in particular in a peer-to-peer network.
  • a peer-to-peer (also termed P2P) computer network is a network that relies primarily on the computing power and bandwidth of the participants in the computer network rather than concentrating computing power and bandwidth in a relatively low number of servers.
  • P2P computer networks are typically used for connecting nodes of the computer network via largely ad hoc connections.
  • the P2P computer network is useful for many purposes. Sharing content files containing, for example, audio, video and data is very common. Real time data, such as telephony traffic, is also passed using the P2P network.
  • a pure P2P network does not have the notion of clients or servers, but only equal peer nodes that simultaneously function as both "clients” and “servers” to the other nodes on the network.
  • This model of network arrangement differs from the client-server model in which communication is usually to and from a central server.
  • a typical example for a non P2P file transfer is an FTP server where the client and server programs are quite distinct, hi the FTP server clients initiate the download/uploads and the servers react to and satisfy these requests from the clients.
  • Some networks and channels such as Napster, OpenNAP, or IRC @find, use a client-server structure for some tasks (e.g., searching) and a P2P structure for other tasks.
  • Networks such as Gnutella or Freenet use the P2P structure for all purposes, and are sometimes referred to as true P2P networks, although Gnutella is greatly facilitated by directory servers that inform peers of the network addresses of other peers.
  • BitTorrent One of the most popular file distribution programmes used in P2P networks is currently BitTorrent which was created by Bram Cohen. BitTorrent is designed to distribute large amounts of data widely without incurring the corresponding consumption in costly server and bandwidth resources. To share a file or group of files through BitTorrent, clients first create a "torrent file".
  • Torrent files contain an "announce” section, which specifies the URL of a tracker, and an "info” section which contains (suggested) names for the files, their lengths, the piece length used, and a SHA-I hash code for each piece, which clients should use to verify the integrity of the data they receive.
  • the tracker is a server that keeps track of which seeds (i.e. a node with the complete file or group of files) and peers (i.e. nodes that do not yet have the complete file or group of files) are in a swarm (the expression for all of the seeds and peers involved in the distribution of a single file or group of files).
  • Nodes report information to the tracker periodically and from time-to-time request and receive information about other nodes to which they can connect.
  • the tracker is not directly involved in the data transfer and is not required to have a copy of the file.
  • Nodes that have finished downloading the file may also choose to act as seeds, i.e. the node provides a complete copy of the file.
  • BitTorrent trackers maintain lists of the nodes currently participating in each torrent.
  • the computer with the initial copy of the file is referred to as the initial seeder.
  • BitTorrent client Using a web browser, users navigate to a site listing the torrent, download the torrent, and open the torrent in a BitTorrent client stored on their local machines. After opening the torrent, the BitTorrent client connects to the tracker, which provides the BitTorrent client with a list of clients currently downloading the file or files.
  • the BitTorrent protocol breaks down files into a number of much smaller pieces, typically a quarter of a megabyte (256 KB) in size. Larger file sizes typically have larger pieces. For example, a 4.37 GB file may have a piece size of 4 MB (4096 KB).
  • the pieces are checked as they are received by the BitTorrent client using a hash algorithm to ensure that they are error free. As further peers enter the swarm, all of the peers begin sharing pieces with one another, instead of downloading directly from the initial seeder. Clients incorporate mechanisms to optimize their download and upload rates.
  • Peers may download pieces in a random order and may prefer to download the pieces that are rarest amongst it peers, to increase the opportunity to exchange data. Exchange of data is only possible if two peers have a different subset of the file. It is known, for example, in the BitTorrent protocol that a peer initially joining the swarm will send to other members of the swarm a BitField message which indicates an initial set of pieces of the digital object which the peer has available for download by other ones of the peers. On receipt of further ones of the pieces, the peer will send a Have message to the other peers to indicate that the further ones of the pieces are available for download.
  • US patent number 7,062,568 (Forcelo Networks, Inc., Milpitas, California) describes a method and apparatus for flow control over so-called point-2-point protocol (PPP) data links.
  • PPP point-2-point protocol
  • the apparatus of this patent application includes a flow controller which analysese whether conditions at one of the peers support an adjustment in the flow rate of received packet streams at the peer.
  • a network for the delivery of digital data with at least one peer downloading the digital data from a plurality of data sources at least one data monitoring device and at least one data delivery controller.
  • the data monitoring device monitors quality of service parameters for the delivery of the digital data at the cache and the data delivery controller adjusts the rates for the delivery of the digital data from the cache to manage the data delivery. This allows the optimal delivery of the digital data since the different sources of digital data can all be used to their best advantage.
  • the plurality of data sources comprise both caches and other peers.
  • Each of these different data sources has their advantages as will be explained below.
  • the quality of service parameters include, but are not limited to, the cost of the data delivery and the rate of data delivery received by the peer. These are generally the quality of service parameters of most concern. Suppliers of digital data wish to deliver the digital data as quickly as required and as cheaply as possible.
  • the objects of the invention are further solved by providing a method for the delivery of digital data to a peer from a plurality of data sources comprising the following steps:
  • This method comprises the following steps: - determining the amount of bandwidth available for the delivery of the digital data from the selected one of the plurality of data sources including at least one cache;
  • Fig. 1 shows a Peer-to Peer network as known in the art.
  • Fig. 2 shows the request for a download of a digital object.
  • Fig. 3 shows an overview of the network in accordance with the invention.
  • Fig. 4 shows an overview for the distribution of content.
  • Fig. 5 shows a geographical implementation of a content distribution network
  • Fig. 6 shows an overview of a service point of presence.
  • Fig. 7 shows an overview of a data point of presence.
  • Fig. 8 shows an overview of a data delivery controller and monitor.
  • FIG. 1 is a block diagram illustrating an environment in which various embodiments of the invention may be practiced.
  • FIG. 1 includes a Peer-to-Peer (P2P) network 100.
  • the P2P network 100 includes a plurality of peers, such as peer 102a, 102b, 102c, 102d, 102e and 102f, hereinafter referred to as peers 102, connected to each other.
  • P2P network 100 may be a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a wireless network and the like.
  • the peers 102 present in the P2P network 100 include stored digital data.
  • the digital data include, but are not limited to, an application file, a video file, a music file and the like.
  • the digital data is shared among the peers 102. It should be understood that the peers 102 may store multiple copies of the digital data.
  • FIG. 2 is a block diagram illustrating a user 202 sending a request for download of a digital object through peer 102a, in accordance with an embodiment of the invention.
  • FIG. 2 includes the peer 102a, the user 202, a server 204 and a tracker server 206.
  • the server 204 includes one or more torrent files, such as torrent file 208a, 208b and 208c, hereinafter referred to as the torrent files 208.
  • the present invention has been described with respect to BitTorrent protocol as an exemplary embodiment. It should be understood by those skilled in the art that present invention is applicable to all P2P protocols.
  • the user 202 makes a request at the peer 102a to download the digital object.
  • the peer 102a communicates with the server 204 and provides information for the digital object to be downloaded to the server 204.
  • the server 204 locates one of the torrent files related to the digital object requested for download by peer 102a, such as, for example, torrent file 208a.
  • torrent files 208 includes information related to the name, size, number of pieces and check sum error for the digital object to be downloaded by peer 102 a.
  • the tracker server 206 provides a list of peers 102 present in the P2P network 100 with the pieces of the digital object to be downloaded.
  • the peer 102a thereafter, communicates with the available list of peers 102 for downloading the related digital objects.
  • the peer 102a communicates with peers 102 by sending a bitfield of the pieces of the digital object that peer 102a has. After peer 102a receives all the bitfields from peers 102, it sends a message to the peers 102 where it finds relevant data and starts downloading the pieces of the requested digital object.
  • FIG. 3 is a block diagram illustrating peer 102a in communication with a Cache Location Server (CLS) 302, in accordance with an embodiment of the present invention.
  • FIG. 3 includes the peer 102a, the CLS 302, a database 304, an Internet Service Provider Domain Name Server (ISP DNS) 306, a central Domain Name Server (central DNS) 308, a cache
  • ISP DNS Internet Service Provider Domain Name Server
  • central DNS central Domain Name Server
  • DNS 310 and one or more caches, such as, cache 312a, 312b and 312c, hereinafter referred to as caches 312.
  • the peer 102a communicates with the CLS 302.
  • the information sent by the peer 102a to the CLS 302 may also contain the IP address of the peer 102a.
  • the CLS 302 communicates a location string to the peer 102a.
  • the CLS 302 may get the location string from the database 304.
  • the database 304 stores information about the IP address ranges of countries, ISPs, regions, towns, etc for the purpose of generating specific location strings with respect to peers 102.
  • the peer 102a then, using the location string and information from the Torrent File 208, makes communication with the ISP DNS 306.
  • the information sent by peer 102a to ISP DNS 306 may be as following:
  • Protocol-TruncatedHash.Protocol-Publisher-LocationString.Find-Cache.com An example of the information sent by CLS 302 to peer 102a may be as following: bt-1234.bt-bigcorp-bigispnyc.find-cache.com where, 'bt' represents the BitTorrent protocol used by the peer 102a, '1234' representing a specific hash value associated with the digital object to be downloaded by the peer 102a, 'bigcorp' representing the publisher (a fictional "Big Corporation") of the digital object to be downloaded, 'bigispnyc' representing the location string for the peer 102a (the New York point of presence for a fictional "Big ISP").
  • the ISP DNS 306 redirects the request to the central DNS 308 (which is the name server for the domain contained in the communication). Thereafter, the central DNS 308 provides an address of the cache DNS 310 to the ISP DNS 306.
  • the cache DNS 310 receives a DNS request from the ISP DNS 306 for the digital object to be downloaded. Subsequently, the cache DNS 310 allocates one of the caches 312, such as, for example, cache 312a. In various embodiments of the present invention, the cache DNS 310 may allocate one of the caches 312 based on the load, availability and content on each of them.
  • the cache DNS 310 communicates this information to the ISP DNS 306, which in turn communicates the information to the peer 102a.
  • the peer 102a thereafter, makes a communication with the cache 312a for downloading the digital object.
  • the communication between the peer 102a and cache 312a is explained in detail in FIG. 4.
  • FIG. 4 is a block diagram illustrating a system 400 for content distribution in the P2P network 100.
  • the system 400 includes the peer 102a, 102b and 102c, the cache 312a and 312b, a content server 402, a private tracker 404, a public tracker 406, a business logic unit 408, a central database server 410 and a user interface unit 412.
  • the peer 102a sends a request to the cache 312a for downloading the digital object.
  • the cache 312a is connected to the content server 402 and the private tracker 404.
  • the content server 402 includes complete copies of a plurality of stored digital objects in the P2P network 100.
  • the content server 402 is connected to a publisher's computer network.
  • the content server 402 receives the digital objects, which are to be distributed, from the publisher's computer network. For example, the publisher wishing to distribute a video file in the P2P network 100 would first upload the video file to the content server 402. Thereafter, the video file can be subsequently downloaded by the peers 102 from the content server 402.
  • the digital data becomes available for the peers 102 to be downloaded.
  • the peers 102 are able to download those uploaded pieces in parallel. Therefore, the capability of the system 400 to execute parallel uploads and downloads of the digital object from the content server 402 ensures an efficient real time availability of digital objects in the P2P network 100.
  • the cache 312a downloads the digital objects, based on the request from the peer 102a, from the content server 402 or from cache 312b.
  • the private tracker 404 knows which of the digital objects are available on which of the caches 312 and content servers 402 and provides this information to the cache 312a. If the digital object requested by the peer 102a is available on the cache 312a, the peer 102a downloads the digital object from the cache 312a. If the digital object is not available on the cache 312a, the cache 312a downloads the requested digital object from the content server 402 and/or the cache 312b. Thereafter, the cache 312a makes the digital object available to the peer 102a for downloading.
  • the peer 102a may also download the related digital objects from the other peers 102 available in the P2P network 100, such as, for example, peer 102b and peer 102c.
  • the cache 312a may upload digital objects from the peers 102 available in the P2P network 100. In such a case, the cache 312a acts as one of the peers 102.
  • the private tracker 404 maintains a track of all the data available on the content server 402 and the caches 312.
  • the public tracker 406 is connected to all of the caches 312 and to all of the peers 102 in the P2P network 100.
  • the public tracker 406 maintains a track of all the data digital objects transferred among the caches 312 and the peers 102.
  • the public tracker 406 maintains a list of all of the peers 102 and the caches 312 which hold copies of the digital objects available in the P2P network 100.
  • the business logic unit 408 is connected to all the caches 312 and the private tracker 404.
  • the business logic unit 408 authenticates peers 102 before allowing the peers 102 to upload any digital object.
  • the business logic unit 408 is connected to the central database server 410.
  • the business logic unit 408 acts as an interface between the P2P network 100 and the central database server 410.
  • Central database server 410 acquires log reports from the private tracker 404 and caches 312, through the business logic unit 408, for all the data transferred to and from the caches 312 and the content server 402. Using the information from the central database server 410 obtained via the business loging unit 408, such as, the log reports, the user interface unit 412 provides the required information billing purposes and for report generation.
  • the central database server 410 may be connected to the public tracker 406.
  • the public tracker 406 may be connected to the private tracker 404.
  • FIG. 5 is a block diagram illustrating an exemplary geographical implementation of a cache distribution network 500, in accordance with various embodiments of the present invention.
  • the cache distribution network 500 includes one or more service points of presence, such as, a service point of presence 502a and 502b, hereinafter referred to as the service points of presence (POPs) 502.
  • the cache distribution network 500 further includes one or more data points of presence, such as, data point of presence 504a, 504b, 504c and 504d, hereinafter referred to as data points of presence (POPs) 504.
  • the service POPs 502 are located at remote geographical locations for, such as, for example London, San Jose and so forth.
  • the number of the service POPs 502 locations are scalable and may be increased with the increase in network traffic.
  • the service POPs 502, such as the service POP 502a and 502b, are connected to each other. The connection between the service POPs 502 enables a real time data and information transfer between all of the service POPs 502,
  • the data POPs 504 are also located in remote geographical locations across the globe, such as, for example, New York, Frankfurt and so forth. It should be understood by those skilled in art that the number of the data POPs 504 locations are scalable and may be increased with the increase in network traffic and digital objects available in the P2P network 100.
  • the data POPs 504, such as the data POP 504a and 504b, are connected with all the available service POPs 502 in the P2P network 100.
  • a geographical location may include both, the service POP 502a and the data POP 504a.
  • FIG. 6 is a block diagram illustrating an arrangement 600 of the components of the service POP 502a, in accordance with an embodiment of the present invention.
  • the arrangement 600 for the service POP 502a includes the cache location server 302, the central domain name server 308, the content server 402, the private tracker 404 and the central database server 410. Further, in an embodiment of the present invention, the arrangement 600 for the service POP 502a may include the caches 312, such as, the cache 312a and 312b. Furthermore, in an embodiment of the present invention, the arrangement 600 for the service POP 502a includes the public tracker 406, the business logic unit 408 and the user interface unit 412.
  • the central database server 410 is located in each of the service POPs 502.
  • the central database server 410 of each of the service POPs 502 are connected to each other and act as a central database unit.
  • the components illustrated in the arrangement 600 for the service POP 502a are scalable and may be increased based on the network traffic and the digital objects available in the P2P network 100. .
  • FIG. 7 is a block diagram illustrating an arrangement 700 of the components of the data POP 504a, in accordance with an embodiment of the present invention.
  • the arrangement 700 for the data POP 504a includes the caches 312, such as, the cache 312a, 312b, 312c and 312d and the cache DNS 310. Only a single cache DNS 310 is shown in FIG 7 for simplicity. However, the data POP 504a may contain more than one of the single caches DNS 310 .
  • the data POP 504a provides digital objects for the peers 102 in the P2P network 100.
  • the data POPs 504 download data from the service POPs 502.
  • the components illustrated in the arrangement 700 for the data POP 504a are scalable and may be increased based on the network traffic and the digital objects available in the P2P network 100.
  • the peer 102a downloads from the cache 312a and from the other peers 102 available in the P2P network 100.
  • the rates of delivery of digital data representing the pieces of the digital objects vary from the multiple sources, as does the quality and the cost in providing the digital data.
  • the digital data from the peers 312 is not (necessarily) of high quality and the rate of delivery of the digital data can be - but is not necessarily - slow.
  • the rates of delivery of the digital data from caches 312 can be fairly high - particularly if the connection from the caches 312 to the peer 102a has a high bandwidth.
  • the quality of the digital data is also high, for example the digital data does not contain many errors.
  • the cost of delivering the digital data from the caches 312 is higher than the cost of delivering the digital data from the peers 102.
  • the cost of the connection from the peer 102a to the caches 312 is normally related to the maximum throughput provided by the caches 312. As a result, for example, during the day the caches 312 may be extremely busy but at night the caches 312 may not be so busy. The caches 312 (and the connection from the peer 102a to the caches 312) will have capacity available to the caches 312 during the night which has been paid for. The incremental cost in delivering the digital data from the caches 312 during the night is accordingly much smaller than the incremental cost in delivering the digital data from the server 312 during the day.
  • the rate of delivery of the digital data to the peer 102a is therefore a combination of the rates of delivery of the digital data from the other peers 102 and the caches 312.
  • the cost for the delivery of the digital data varies according to which ones of the multiple sources (i.e. peers 102 and/or caches 312) supplies the digital data. If the digital data is supplied principally from the other peers 102 to which the peer 102a is connected, the cost of the digital data will be small. In particular, if the other peers 102 are severed by the same ISP the cost will be very small. However, the quality of service may not be acceptable.
  • An unacceptable quality of service is when the peer 102a does not receive the digital data at sufficient speed or the received digital data contains too many errors.
  • An unacceptable quality of service may occur when a user 202 at the peer 102a wishes to watch a video.
  • the video is stored as a digital object in the form of video data. A certain amount of digital data has to reach the peer 102 within a fixed period of time in order for the peer 102a to watch the video. If the digital data representing the pieces of the digital object is not received at the peer 102a, then the user 202 will experience an interruption in the transmission of the video.
  • the pieces of the digital object may be downloaded from the caches 312.
  • the downloading of the digital data from the caches 312 is more costly as the bandwidth is wider, the digital data may have to pass over leased lines and the rate of the delivery of the digital data is much higher.
  • the peer 102a can get more than enough digital data from the caches 312 to enable the user 202 to view the video and the quality of data will be much higher.
  • the peer 102a is provided with a data delivery monitor 800 as shown in FIG. 8.
  • FIG. 8 illustrates not only the data delivery monitor 800 . but also two of the other peers 102b and 102c supplying the peer 102a with digital data and the caches 312 supplying the peer 102a with digital data. It will be understood that in practice the peer 102a will be connected to multiple other peers 102 and possibly to more than one caches 312. A data delivery controller 810 is also illustrated connected in this embodiment to the caches 312.
  • the data delivery monitor 800 is provided with predetermined quality of service (QoS) parameters. Different ones of the digital objects will have different predetermined quality of. service parameters.
  • the data delivery monitor 800 monitors the rate of receipt of the digital data at the peer 102a and may monitor the rate of receipt of the digital data from the other peers 102b and 102c as well as from the caches 312, such as cache 312a.
  • the monitored realtime quality of service parameters are compared with predetermined quality of service parameters.
  • the predetermined quality of service parameters can be pre-programmed into the data delivery monitor 800 and/or may be dynamically adjusted.
  • the rate of delivery of the digital data to the peer 102a may be adjusted on the basis of the comparison as will be discussed below.
  • the data delivery monitor 800 sends QoS information to a data delivery controller 810.
  • the quality of service parameters include, but are not limited to, the rate of receipt of the delivery of the digital data to the peer 102a, the cost of the delivery of the digital data and the error rate of the received digital data.
  • the pre-determined quality of service parameters could include the requirement that the data is received at a rate between 1Mb and 1.2 Mb per second to allow the viewing of the video by the user 202 at the peer 102a.
  • the pre-determined quality of service parameters might also require that the total cost for the delivery of the digital data not exceed, for example, 30c.
  • the data delivery monitor 800 and the data delivery controller 810 may be positioned in an appropriate place within the P2P network 100. In the embodiment shown in FIG. 8, the data delivery monitor 800 and the data delivery controller 810 is positioned at the cache 312a. In another embodiment of the invention, the data delivery monitor 800 may be positioned at the public tracker 406 but the data delivery controller 810 will be positioned at some or all of the caches 312 and some or all of the peers 102. In still another embodiment of the invention, the data delivery monitor 800 and the data delivery controller 810 may also be positioned at the peers 102 or elsewhere in the P2P network 100. In an embodiment of the invention, more than one data delivery monitor 800 and more than one data delivery controller 810 may be employed in the P2P network 100.
  • the function of the data delivery controller 810 is to receive the QoS information from the data delivery monitor 800 and to adjust the rate of delivery of the digital data from the other peers 102 and the caches 312.
  • the adjustment may be done, for example, by turning off or on some of the connection through which the digital data is delivered to the peer 102a. The peer 102a will therefore receive less data.
  • the adjustment may also be done by changing the bandwidth of the connection between the peer 102a and the other peers 102 or, more commonly, the caches 312. Changing the bandwidth is, for example, particularly appropriate when the source of the digital data is the caches 312 and turning on or off the channel is particularly appropriate when the source of the digital data is one of the other peers 102.
  • the data delivery controller 810 may make further decisions. It may choose, for example, to throttle the rate of delivery of the digital data from other peers 102 or from other ones of the caches 312 situated outside of the internet service provider (ISP) at which the peer 102a is situated.
  • ISP internet service provider
  • the ISP may wish to preferentially use the other peers 102 and any caches 312 within its domain and thus restrict traffic to any ones of the other peers 102 or any caches 312 outside of its domain.
  • the data delivery monitor 800 in one embodiment of the invention monitors the receipt of the digital data by monitoring content availability messages, such as BitField and Have messages in the BitTorrent protocol. Equivalent techniques and messages exist in other P2P protocols.
  • the data delivery controller 810 may also select to preferentially source the digital data from underused caches 312 as discussed above.
  • the nearest caches 312 of the digital data for the peer 102a in Germany is, for example, located in Frankfurt. It would be from a location viewpoint optimal to use the caches 312 in Frankfurt for the delivery of the digital data.
  • the peer 102a is accessing the digital data in the morning, it is probable that the caches 312 in San Jose is underutilised because of the different time zones whilst the caches 312 in Frankfurt is operating at or close to its maximum throughput. There may be bandwidth available from the San Jose caches 312 available at minimal incremental cost.
  • the data delivery controller 810 will attempt to deliver the digital data preferentially from the San Jose caches 312 in order to minimise costs.

Abstract

L'invention concerne un réseau pour la distribution de données numériques, ayant au moins un poste (102a) téléchargeant les données numériques à partir d'une pluralité de sources de données (102, 312), comprenant au moins une mémoire cache (312), au moins un dispositif de surveillance de données (800) pour surveiller au moins une qualité de paramètre de service pour la distribution des données numériques au niveau de la mémoire cache (312) et au moins une commande de distribution de données (810) pour ajuster au moins un des débits pour la distribution des données numériques à partir de la mémoire cache (312). Un procédé pour la distribution de données numériques à un poste (102a) à partir d'une pluralité de sources de données (102, 312) est également décrit. Le procédé comprend les étapes suivantes : accéder à un certain nombre de la pluralité de sources de données (102, 312) incluant au moins une mémoire cache (312) ; télécharger des données à partir du nombre des sources de données (102, 312) ; surveiller une qualité de paramètre de service pour délivrer les données numériques au niveau de la mémoire cache (312) ; comparer la qualité de paramètre de service pour la réception des données numériques avec au moins une qualité prédéterminée de paramètre de service ; ajuster la distribution des données numériques à partir de la mémoire cache (312) selon la comparaison.
PCT/EP2007/007106 2006-08-11 2007-08-10 Système de distribution de contenu pour un objet numérique WO2008017504A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
GB0615963.6 2006-08-11
GB0615963A GB2440774B (en) 2006-08-11 2006-08-11 Content Delivery System For Digital Object
US11/598,115 US7995473B2 (en) 2006-08-11 2006-11-08 Content delivery system for digital object
US11/598,115 2006-11-08

Publications (1)

Publication Number Publication Date
WO2008017504A1 true WO2008017504A1 (fr) 2008-02-14

Family

ID=38828721

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/007106 WO2008017504A1 (fr) 2006-08-11 2007-08-10 Système de distribution de contenu pour un objet numérique

Country Status (1)

Country Link
WO (1) WO2008017504A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030204602A1 (en) * 2002-04-26 2003-10-30 Hudson Michael D. Mediated multi-source peer content delivery network architecture
US20040148344A1 (en) * 2003-11-19 2004-07-29 Serenade Systems Content distribution architecture

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030204602A1 (en) * 2002-04-26 2003-10-30 Hudson Michael D. Mediated multi-source peer content delivery network architecture
US20040148344A1 (en) * 2003-11-19 2004-07-29 Serenade Systems Content distribution architecture

Similar Documents

Publication Publication Date Title
US7995473B2 (en) Content delivery system for digital object
US7908362B2 (en) Method and apparatus for the delivery of digital data
US10506062B2 (en) Network-optimized content delivery for high demand non-live contents
US7945689B2 (en) Method and apparatus for transferring files to clients using a peer-to-peer file transfer model and a client-server transfer model
US8321494B2 (en) Method and apparatus for reporting and invoicing of data downloads
US7653689B1 (en) Intelligent virtual content distribution network system and method
EP2057823B1 (fr) Structure de mémoire cache
US20080040420A1 (en) Content distribution network
US8028019B2 (en) Methods and apparatus for data transfer in networks using distributed file location indices
JP6111452B2 (ja) デジタルデータを配信するための方法および装置
JP2010522386A (ja) Ｐ２ｐコンテンツ共有のための方法、システム、及びノード
WO2008017502A1 (fr) Réseau de distribution de contenu
US8244867B2 (en) System and method for the location of caches
Markakis et al. A p2p home-box overlay for efficient content distribution
WO2008017504A1 (fr) Système de distribution de contenu pour un objet numérique
GB2455301A (en) Dynamic adjustment of the delivery of digital data from multiple data sources

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07801605

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07801605

Country of ref document: EP

Kind code of ref document: A1