WO2008017503A1 - Cache structure - Google Patents

Cache structure Download PDF

Info

Publication number
WO2008017503A1
WO2008017503A1 PCT/EP2007/007105 EP2007007105W WO2008017503A1 WO 2008017503 A1 WO2008017503 A1 WO 2008017503A1 EP 2007007105 W EP2007007105 W EP 2007007105W WO 2008017503 A1 WO2008017503 A1 WO 2008017503A1
Authority
WO
WIPO (PCT)
Prior art keywords
cache
peers
pieces
meta
information
Prior art date
Application number
PCT/EP2007/007105
Other languages
French (fr)
Inventor
Adam Twiss
David Ferguson
Jim Minter
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
Application filed by Velocix Limited filed Critical Velocix Limited
Priority to EP07801604.5A priority Critical patent/EP2057823B1/en
Publication of WO2008017503A1 publication Critical patent/WO2008017503A1/en
Priority to IL197007A priority patent/IL197007A/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1854Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with non-centralised forwarding system, e.g. chaincast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1886Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1101Session protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1061Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
    • H04L67/1063Discovery through centralising entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1074Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • H04L67/1076Resource dissemination mechanisms or network resource keeping policies for optimal resource availability in the overlay network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1074Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • H04L67/1078Resource delivery mechanisms
    • H04L67/108Resource delivery mechanisms characterised by resources being split in blocks or fragments
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/2871Implementation details of single intermediate entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/568Storing data temporarily at an intermediate stage, e.g. caching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1087Peer-to-peer [P2P] networks using cross-functional networking aspects
    • H04L67/1091Interfacing with client-server systems or between P2P systems

Definitions

  • the invention relates to caches used in the Internet.
  • the invention relates to caches in peer-to-peer (P2P) networks for the distribution of large digital objects.
  • P2P peer-to-peer
  • 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. In 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.
  • Caches for the intermediate storage of data transferred about the Internet are known in the art.
  • the most common type of cache used in the Internet is a proxy cache.
  • the proxy cache operates at the application level, passing some messages unaltered between a client and a server, changing other ones of the messages and sometimes responding to the messages itself rather than relaying the messages.
  • a web proxy cache sits between servers in the Internet and one or more clients and watches requests for HTML pages, images and files (collectively known as objects) pass through.
  • the web proxy cache saves a copy of the HTML pages, images and files for itself. Subsequently if there is another request for the same object, the web proxy cache will use the copy that was saved instead of asking an origin server to resend the request.
  • the cache reduces the amount of bandwidth used by a client. This saves money if the client is paying for the traffic and keeps the client's bandwidth requirements lower and more manageable.
  • a content delivery network is a network environment which involves sending information (for example in the form of a file) from a content provider to multiple content servers.
  • the multiple content servers may distribute the content to end-users ? a various destination on the network.
  • the content provider generally puts digital object that has to be distributed onto a computer connected to a network and this computer is generally wizard to as a content server.
  • a cache hierarchy is established in a CDN which comprises an edge server and either a single parent region or a subset of the edge servers.
  • a cache hierarchy is established in a CDN which comprises an edge server and either a single parent region or a subset of the edge servers.
  • the request is provided either to the single parent region or to a given one of the subset of the edge server regions for handling.
  • This handling is generally carried out as a function of meta-data associated with the given object request.
  • the meta-data is stored in the CDN edge servers so that it can be employed when a request for digital object is received.
  • a further example of a content delivery network is disclosed in the US patent application No. US 2002/0078174 (Sim et al).
  • This CDN is particularly suitable for large payload files which are distributed throughout a CDN.
  • the CDN of the Sim patent application is distributed thoughout a so-called SCDN tree and a request for the digital objects is provided to the SDSCDN port. On receipt of the request, a search is carried out for the stored pieces of the digital object throughout the CDN which are then assembled and sent and streamed to the end-user.
  • the CDN of the Sim patent application is structured such that new nodes added to the network learns from other nodes in the network what content their should have and will download the required contents without interrupting network operation. Each one of the nodes managers is local stored and decides what content to prune? based on information such as usage patents. Neither of the Akamai nor the sim patent application teach a method by which one of the caches can become a member of a swarm in the P2P network.
  • a method for distributing digital objects in a network the digital objects being distributable in a plurality of pieces, wherein at least some of a plurality of peers are connected to other ones of the plurality of peers, at least one cache and the at least one of the plurality of peers is connected to at least one data source on which at least one piece of the digital objects is stored.
  • the method comprises a first step of receiving a message relating to the digital object from a first one of the plurality of peers at the at least one cache followed by a second step of checking whether meta-information relating to the digital object is available in the at least one cache.
  • the meta- information includes, but is not limited to, a list of the peers in the swarm from which pieces of the digital object are available.
  • the meta-information is requested from a meta-information source in the event that the meta-information is unavailable in the at least one cache.
  • the meta-information is received at the at least one cache and a fifth step of storage of the plurality of pieces in the at least one cache based on the meta- information commences.
  • This method has the advantage that a cache can begin to participate in the downloading of a digital object in a peer-to-peer network and supplying pieces of the digital object to other members of the peer-to-peer network without even initially knowing about the existence of the digital object.
  • the network comprises: a plurality of peers in a peer-to-peer network which request the download of at least one piece of a first digital object.
  • At least one data source is present in the network on which at least pieces of the first digital object are stored and at least one of the plurality of peers is connected to the at least one data source.
  • the computer network comprises at least one cache with a plurality of peers being connected to the at least one cache and at least one piece of the requested piece of the first digital object is downloaded from the at least one data source to the peer.
  • at least one meta-information source is provided which comprises meta-information relating to the digital object which can be downloaded to the at least one cache to ensure that the at least one cache knows about the digital object.
  • the network comprising the at least one cache can thereby comprise only one cache or a plurality of caches that may be connected to other ones of the caches.
  • Several caches may be located in the same place or may be located on different places to provide short distance access to the peers.
  • the at least one cache may thereby function similar or identical to a peer in the P2P network, whereby the cache can provide higher download speed than other peers functioning as data sources.
  • peers can quickly collect copies of a whole digital object making use of the plurality of peers downloading different pieces of the digital object in parallel, which is particularly useful with large digital objects.
  • the at least one cache is additionally connected to a network.
  • the cache is connected to a data source, on which a whole digital object or pieces of a digital object are stored.
  • the data source may also be a data source or server of a publisher wishing to distribute digital objects.
  • the cache can act as a mirror server.
  • the method further comprises a step of delaying the requesting of some of the pieces of a digital object. For example, it may be advantageous to only pass the digital object or pieces of the digital object to the cache when a large number of peers wish to download the digital object.
  • the decision if and when to upload digital objects is based on the frequency of request for the download of the digital object.
  • FIG. 1 shows the structure of the cache
  • Fig. 2 shows a flow diagram for the downloading of data
  • Fig. 3 shows a further embodiment of the structure of the cache
  • Fig. 1 shows the structure of the cache in accordance with one embodiment of the invention.
  • the network 100 shown in Fig. 1 comprises a Peer-to-Peer (P2P) server 10 connected to Internet 20.
  • P2P Peer-to-Peer
  • Each of the four users 40a-d is also connected to the Internet over connections 50a-d.
  • Each of the four users 40a-d is also connected to a cache 30 over connections 60a-d.
  • Each of the four users 40a-d has a local memory 45a-d which can store data for local access and will also have a P2P client stored on their machines.
  • each user 40a-d is also referred to as peer 40a-d interchangeably.
  • the invention is applicable to a plurality of peers 40a-d connected to multiple caches 30 and multiple P2P servers 10.
  • one or more of the caches 30 would be connected to an access point of an Internet Service Provider.
  • the peers 40a-d may also be connected to each other.
  • connections 50a-d between the peers 40a-d and the Internet 20 are standard connections which may be implemented using any one of the standard protocols and hardware.
  • connections 60a-d between the peers 40a-d and the cache 30 are standard connections which can be implemented using any one of the standard protocols and hardware.
  • each of the peers 40a-d wish to substantially simultaneously access a digital object 70 stored on the P2P server 10.
  • the digital object 70 could, for example, be a new film or a television programme released for downloading. Once a release date and time for the new film or the downloadable television programme is announced, it is highly likely that a plurality of the peers 40a-d will wish to access the new film or downloadable television programme at substantially the same time. Since the new film or downloadable television programme has recently been released it will not be present in the cache 30 and the cache 30 will not know of the existence of the digital object. Thus the peers 40a-d will only be able to access the new film or the downloadable television programme from the P2P server 10 through the Internet 20.
  • the access of the digital object 70 may be described using the method shown in the flow chart of Fig. 2.
  • the digital object 70 is released which a number of the peers 40a-d will be interested in accessing at step 210.
  • Multiple requests for access i.e. one from each of the peers 40a-d
  • the cache 30 may not contain any pieces of the digital object 70 because the large digital object 70 has recently been released (as is tested at step 230) and furthermore, as explained above, the cache (30) will not know initially of the existence of the digital object.
  • the multiple requests to access the P2P server 10 are passed to the P2P server 10 and for each of the multiple requests pieces of the digital object 70 are passed to each of the requesting peers 40a-d.
  • the pieces sent to the peers 40a-d will be selected substantially at random and thus it is likely that whilst some of the peers 40a-d may receive the same pieces, many of the other peers 40a-d will receive different pieces.
  • the cache 30 will request meta-information relating to the digital object in step 240.
  • the meta-information includes, but is not limited to, an identity — such as a hash sum - for the digital object and lists of peers storing at least parts of the digital object (i.e. members of the swarm).
  • the peers 40a-d receive the pieces and store the pieces locally in the local memory 45a-d. At least one of the peers 40a-d will upload the meta-information to the cache 30 in step 245 relating to the digital object in one embodiment of the invention. It is possible that more than one of the peers 40a-d will upload the meta-information. Now having the meta-information the cache 30 can itself act as a peer and may, for example, upload the pieces of the digital object into the cache 30 from the peers 40a-d. At step 250, a check is then made to check whether all of the pieces required for the large digital object 70 are stored in the local memory 45a-d or whether more pieces are required. In the event that more pieces are required a further request is sent for pieces of the digital object 70 at step 220.
  • the cache 30 will now have pieces stored in the cache 30 which were not previously present.
  • the cache 30 also acts as a peer in the network 100 and will issue a message to the other peers in the network 100 to inform the other peers that it now has pieces. This is done, in the BitTorrent protocol, by sending a BitField message and/or a Have message. Similar messages are available in other protocols.
  • the peers 40a-40d in the network 100 receive the message the peers 40a-40d commence sending requests for the pieces to the cache 30.
  • the cache 30 will respond to these requests as shown in step 260 by sending the pieces to the peers 40a-40d.
  • the cache 30 generally responds to every request received; unlike the peers 40a-40d the cache 30 will not choke the requests for pieces.
  • pieces could of course be supplied from other peers 40a-d.
  • All of the peers 40a-d are connected to both the P2P server 10 and to the cache 30. Therefore, the peers 40a-d are continuously sending requests to the P2P server 10, to other ones of the peers 40a-40d and to cache 30. The peers 40a-40d thereby receive pieces from the P2P server 10, other ones of the peers 40a-40d and the cache 30. Over time, all of the pieces for the digital object 70 from the P2P server 10 will be downloaded by at least one of the peers 40a-d and uploaded to the cache 30 from where the data (bytes) are shared with the other peers 40a- d.
  • step 270 all of the bytes required to re-create the large digital object 70 are in the local memories 45a-d and the digital object 70 is assembled in the local memories 45a-d.
  • the cache 30 can also download the meta- information relating to the digital object and the pieces of the digital objectfrom the P2P server 10 without the meta-information and/or the pieces passing through the peers 40a-d.
  • a publisher provides a copy of the digital object including the meta-information to the cache 30, enabling direct download for the peer 40a to 40c.
  • the cache 30 can delay the requesting of some of the pieces of the data objects.
  • the cache 30 can supply pieces of the data object which are not available in the peers 40a-d.
  • the cache 30 can request pieces of the digital object. This level depends on the digital object being downloaded or it could be a fixed number
  • some of the peers 40a-d may be each connected to different data sources 310a-c.
  • Each of the different data sources 310a-c provide different pieces 371, 372 and 373 of the digital object 370.
  • the peer 40a may, except being connected to the cache 30, be connected to the data source 310a, for example, via the internet.
  • the data source 310a has only a first piece 371 of the digital object
  • the peer 40a may be looking for the first piece 371, the peer 40a may, also be looking for a second piece 372 and a third piece 373 which are not available on the data source 31 Oa he is connected to. However, as peer 40a is requesting the first piece 371 of the digital object 370 the peer 40a will download piece 371 to the local memory 45a and subsequently upload it to the cache 30 (shown on Fig. 1), wherefrom it is available for download to all the peers 40a-d.
  • peer 40b may also wish to download digital object 370. As the first piece 371 of the digital object 370 is available in the cache 30, peer 40b may download the first piece
  • the peer 40b may, except being connected to cache 30, also be connected to a second data source 310b which has the second piece 372 of the digital object 370 available for download. Thus peer 40b will download the second piece 372 of the digital object 370 from the data source 310b, store the second piece 372 in the local memory 45b and upload a copy of the second piece 372 to the cache 30. Thus both, the peer 40b and the cache 30 each have the first piece 371 and the second piece 372 of the digital object 370. Peer 40a may now check on a regular basis the availability of the pieces of the digital object on the cache 30. The check for the availability is done by examining BitField or Have messages issued by the cache 30.
  • the peer 40a will identify from the BitField or Have messages that the first piece 371 and the second piece 372 of the digital object 370 are available for download in the cache 30. As the peer 40a has already downloaded the first piece 371 the peer 40a will now download the second piece 372.
  • the third peer 40c may now wish to download the digital object 370.
  • the third peer 40c is connected to the cache 30 and to a third data source 310c.
  • the third peer 40c now finds the first piece 371 and the second piece 372 of the digital object 370 available on the cache 30.
  • the third peer 40c may also find the first piece 371 and the third piece 373 available on the data source 310c.
  • the third peer 40c may download the first piece 371 either from the cache 30 or from the data source 310c depending on the download speed and fast access availability.
  • the third peer 40c may download the first piece 371 from the third data source 310c.
  • the third peer 40c will download the second piece 372 form the cache 30 and the third piece 373 of the digital object 370. Subsequently, the third peer 40c will upload the third piece 373 of the digital object 370 to the cache 30.
  • the cache 30 now has the first piece 371, the second piece 372 and the third piece 373 of the digital object 370 available for download.
  • the first peer 40a and the second peer 40b may download the missing third piece 373 of the digital object 370 from the cache 30.
  • a fourth peer 4Od requesting to download digital object 370 may download all the three pieces 371, 372, and 373 of the digital object 370 from the cache 30 without accessing or connecting to any of the data sources 310a-310c. As pieces 371, 372, and 373 of the digital object 370 can be downloaded from the cache 30, the need for slow upload connections with other peer 40a -40c is eliminated. It is to be understood that the example described with respect to Fig. 3 is an illustrative example and that digital object 370 may have a plurality of pieces 371, 372, 373. The plurality of pieces 371, 372 and 373 of the digital object 370 may be downloaded by many more peers 40a-40c.
  • the peers 40a-40c may also download pieces of the digital object 370 from the data sources 310a-c and upload pieces to the cache 30 in parallel. It is also obvious that the peer 40a-40c may download a large number of pieces or even all of the pieces of the digital object 370 from a single data source.
  • the method and the network 100 are based on a P2P network, thus allowing any combination of downloads and uploads within the network 100.

Abstract

A method for the distribution of digital objects (370) in a peer-to-peer network is disclosed. The digital objects (370) are distributed in a plurality of pieces (371-373). At least some of a plurality of peers (40a-d) are connected to other ones of the plurality of peers (40a-d) and at least one of the peers (40a-d) is connected to at least one cache (30). The method comprise: - a first step of receiving a message relating to the digital object (370) from a first one of the plurality of peers (40a-d) at the at least one cache (30) - a second step of checking whether meta-information relating to the digital object (370) is available in the at least one cache (30); - a third step of requesting the meta-information from a meta-information source in the event that the meta-information is unavailable in the at least one cache (30); - a fourth step of receiving the meta-information at the at least one cache (30); and -a fifth step of storage of the plurality of pieces (371-373) in the at least one cache (30) based on the meta-information.

Description

Figure imgf000003_0001
FIELD OF THE INVENTION
The invention relates to caches used in the Internet. In particular, the invention relates to caches in peer-to-peer (P2P) networks for the distribution of large digital objects.
BACKGROUND TO THE INVENTION
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. In 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. 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". This is a small file which contains meta-information about the files to be shared and about the host computer (the "tracker") that coordinates the file distribution. 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. After the torrent file is created, a link to the torrent file is placed on a website or elsewhere, and it is normally registered with the tracker. 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.
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.
Initially, there may be no other peers in the swarm, in which case the client connects directly to the initial seeder and begins to request pieces. 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.
Caches for the intermediate storage of data transferred about the Internet are known in the art. The most common type of cache used in the Internet is a proxy cache. The proxy cache operates at the application level, passing some messages unaltered between a client and a server, changing other ones of the messages and sometimes responding to the messages itself rather than relaying the messages. A web proxy cache sits between servers in the Internet and one or more clients and watches requests for HTML pages, images and files (collectively known as objects) pass through. The web proxy cache saves a copy of the HTML pages, images and files for itself. Subsequently if there is another request for the same object, the web proxy cache will use the copy that was saved instead of asking an origin server to resend the request.
There are three main reasons why such proxy caches are used:
i) In order to reduce latency - in this case, the request is satisfied from the cache (which is closer to the client) instead of the origin server. It therefore takes less time for the client to get the object and display the object. This makes web sites seem more responsive to the client.
ii) To reduce traffic - Each object is only retrieved once from the server once, the cache reduces the amount of bandwidth used by a client. This saves money if the client is paying for the traffic and keeps the client's bandwidth requirements lower and more manageable. iii) To increase delivery speed. It would be advantageous if the cache could participate in the peer-to-peer distribution network and become a member of a swarm. By becoming a member, the cache would reduce traffic, increase delivery speed and reduce latency in the peer-to-peer distribution network. In order to become a member, the cache must know about the distribution of the file.
A content delivery network is a network environment which involves sending information (for example in the form of a file) from a content provider to multiple content servers. The multiple content servers may distribute the content to end-users ? a various destination on the network. The content provider generally puts digital object that has to be distributed onto a computer connected to a network and this computer is generally wizard to as a content server.
One example of a content delivery network is disclosed in international patent application No. WO 03/088065 (Akamai Technologies, Cambridge, United States). In this patent application, a cache hierarchy is established in a CDN which comprises an edge server and either a single parent region or a subset of the edge servers. When an end user wishes to access a digital object and the request cannot be serviced by one of the edge servers, the request is provided either to the single parent region or to a given one of the subset of the edge server regions for handling. This handling is generally carried out as a function of meta-data associated with the given object request. In the contents delivery network of the Akamai patent application the meta-data is stored in the CDN edge servers so that it can be employed when a request for digital object is received.
A further example of a content delivery network is disclosed in the US patent application No. US 2002/0078174 (Sim et al). This CDN is particularly suitable for large payload files which are distributed throughout a CDN. The CDN of the Sim patent application is distributed thoughout a so-called SCDN tree and a request for the digital objects is provided to the SDSCDN port. On receipt of the request, a search is carried out for the stored pieces of the digital object throughout the CDN which are then assembled and sent and streamed to the end-user. The CDN of the Sim patent application is structured such that new nodes added to the network learns from other nodes in the network what content their should have and will download the required contents without interrupting network operation. Each one of the nodes managers is local stored and decides what content to prune? based on information such as usage patents. Neither of the Akamai nor the sim patent application teach a method by which one of the caches can become a member of a swarm in the P2P network.
SUMMARY OF THE INVENTION
It is an object of the present invention to provide a method and a system for fast download of large digital objects.
It is another object of the invention to provide improved network efficiency and cheaper download in P2P networks.
These and other objects of the invention are solved by a method for distributing digital objects in a network, the digital objects being distributable in a plurality of pieces, wherein at least some of a plurality of peers are connected to other ones of the plurality of peers, at least one cache and the at least one of the plurality of peers is connected to at least one data source on which at least one piece of the digital objects is stored. The method comprises a first step of receiving a message relating to the digital object from a first one of the plurality of peers at the at least one cache followed by a second step of checking whether meta-information relating to the digital object is available in the at least one cache. In this context the meta- information includes, but is not limited to, a list of the peers in the swarm from which pieces of the digital object are available. In a third step the meta-information is requested from a meta-information source in the event that the meta-information is unavailable in the at least one cache. Finally in a fourth step the meta-information is received at the at least one cache and a fifth step of storage of the plurality of pieces in the at least one cache based on the meta- information commences.
This method has the advantage that a cache can begin to participate in the downloading of a digital object in a peer-to-peer network and supplying pieces of the digital object to other members of the peer-to-peer network without even initially knowing about the existence of the digital object.
These and other objects of the invention are also solved by a network for the distribution of digital objects wherein the digital objects are distributable in a plurality of pieces. The network comprises: a plurality of peers in a peer-to-peer network which request the download of at least one piece of a first digital object. At least one data source is present in the network on which at least pieces of the first digital object are stored and at least one of the plurality of peers is connected to the at least one data source. The computer network comprises at least one cache with a plurality of peers being connected to the at least one cache and at least one piece of the requested piece of the first digital object is downloaded from the at least one data source to the peer. Finally at least one meta-information source is provided which comprises meta-information relating to the digital object which can be downloaded to the at least one cache to ensure that the at least one cache knows about the digital object.
The network comprising the at least one cache can thereby comprise only one cache or a plurality of caches that may be connected to other ones of the caches. Several caches may be located in the same place or may be located on different places to provide short distance access to the peers.
The at least one cache may thereby function similar or identical to a peer in the P2P network, whereby the cache can provide higher download speed than other peers functioning as data sources. In addition, peers can quickly collect copies of a whole digital object making use of the plurality of peers downloading different pieces of the digital object in parallel, which is particularly useful with large digital objects.
In a preferred embodiment, the at least one cache is additionally connected to a network. In a particular embodiment, the cache is connected to a data source, on which a whole digital object or pieces of a digital object are stored. The data source may also be a data source or server of a publisher wishing to distribute digital objects. Thus, the cache can act as a mirror server.
In a further preferred embodiment, the method further comprises a step of delaying the requesting of some of the pieces of a digital object. For example, it may be advantageous to only pass the digital object or pieces of the digital object to the cache when a large number of peers wish to download the digital object. In a particular embodiment of the invention, the decision if and when to upload digital objects is based on the frequency of request for the download of the digital object.
DESCRIPTION OF THE FIGURES Fig. 1 shows the structure of the cache
Fig. 2 shows a flow diagram for the downloading of data
Fig. 3 shows a further embodiment of the structure of the cache
DETAILED DESCRIPTION OF THE INVENTION
Fig. 1 shows the structure of the cache in accordance with one embodiment of the invention. The network 100 shown in Fig. 1 comprises a Peer-to-Peer (P2P) server 10 connected to Internet 20. Four users 40a, 40b, 40c and 4Od are illustrated. Each of the four users 40a-d is also connected to the Internet over connections 50a-d. Each of the four users 40a-d is also connected to a cache 30 over connections 60a-d. Each of the four users 40a-d has a local memory 45a-d which can store data for local access and will also have a P2P client stored on their machines. Thus, each user 40a-d is also referred to as peer 40a-d interchangeably. However, it must be understood that the invention is applicable to a plurality of peers 40a-d connected to multiple caches 30 and multiple P2P servers 10. Typically, one or more of the caches 30 would be connected to an access point of an Internet Service Provider.
In various embodiments of the invention, the peers 40a-d may also be connected to each other.
The connections 50a-d between the peers 40a-d and the Internet 20 are standard connections which may be implemented using any one of the standard protocols and hardware. Similarly, the connections 60a-d between the peers 40a-d and the cache 30 are standard connections which can be implemented using any one of the standard protocols and hardware.
Suppose that each of the peers 40a-d wish to substantially simultaneously access a digital object 70 stored on the P2P server 10. The digital object 70 could, for example, be a new film or a television programme released for downloading. Once a release date and time for the new film or the downloadable television programme is announced, it is highly likely that a plurality of the peers 40a-d will wish to access the new film or downloadable television programme at substantially the same time. Since the new film or downloadable television programme has recently been released it will not be present in the cache 30 and the cache 30 will not know of the existence of the digital object. Thus the peers 40a-d will only be able to access the new film or the downloadable television programme from the P2P server 10 through the Internet 20.
In an embodiment of the present invention, the access of the digital object 70 may be described using the method shown in the flow chart of Fig. 2. At step 200, the digital object 70 is released which a number of the peers 40a-d will be interested in accessing at step 210. Multiple requests for access (i.e. one from each of the peers 40a-d) are sent in step 220 both to the P2P server 10 (via the connections 50a-d and the Internet 20) and to the cache 30 (via the connections 60a-d) and to other ones of the peers 40a-d. The cache 30 may not contain any pieces of the digital object 70 because the large digital object 70 has recently been released (as is tested at step 230) and furthermore, as explained above, the cache (30) will not know initially of the existence of the digital object.
The multiple requests to access the P2P server 10 are passed to the P2P server 10 and for each of the multiple requests pieces of the digital object 70 are passed to each of the requesting peers 40a-d. The pieces sent to the peers 40a-d will be selected substantially at random and thus it is likely that whilst some of the peers 40a-d may receive the same pieces, many of the other peers 40a-d will receive different pieces.
At the same time, the cache 30 will request meta-information relating to the digital object in step 240. The meta-information includes, but is not limited to, an identity — such as a hash sum - for the digital object and lists of peers storing at least parts of the digital object (i.e. members of the swarm).
The peers 40a-d receive the pieces and store the pieces locally in the local memory 45a-d. At least one of the peers 40a-d will upload the meta-information to the cache 30 in step 245 relating to the digital object in one embodiment of the invention. It is possible that more than one of the peers 40a-d will upload the meta-information. Now having the meta-information the cache 30 can itself act as a peer and may, for example, upload the pieces of the digital object into the cache 30 from the peers 40a-d. At step 250, a check is then made to check whether all of the pieces required for the large digital object 70 are stored in the local memory 45a-d or whether more pieces are required. In the event that more pieces are required a further request is sent for pieces of the digital object 70 at step 220. In the meantime, the cache 30 will now have pieces stored in the cache 30 which were not previously present. As explained above, the cache 30 also acts as a peer in the network 100 and will issue a message to the other peers in the network 100 to inform the other peers that it now has pieces. This is done, in the BitTorrent protocol, by sending a BitField message and/or a Have message. Similar messages are available in other protocols. When the peers 40a-40d in the network 100 receive the message the peers 40a-40d commence sending requests for the pieces to the cache 30. The cache 30 will respond to these requests as shown in step 260 by sending the pieces to the peers 40a-40d. The cache 30 generally responds to every request received; unlike the peers 40a-40d the cache 30 will not choke the requests for pieces. In step 260, pieces could of course be supplied from other peers 40a-d.
All of the peers 40a-d are connected to both the P2P server 10 and to the cache 30. Therefore, the peers 40a-d are continuously sending requests to the P2P server 10, to other ones of the peers 40a-40d and to cache 30. The peers 40a-40d thereby receive pieces from the P2P server 10, other ones of the peers 40a-40d and the cache 30. Over time, all of the pieces for the digital object 70 from the P2P server 10 will be downloaded by at least one of the peers 40a-d and uploaded to the cache 30 from where the data (bytes) are shared with the other peers 40a- d.
At step 270, all of the bytes required to re-create the large digital object 70 are in the local memories 45a-d and the digital object 70 is assembled in the local memories 45a-d.
Since the time taken to download all of the data from the P2P server 10 over the Internet 20 and the connections 50a-d is substantially longer than the time taken to download the data from the cache 30 along the connections 60a-d, there is a substantial time saving in the downloading of the data. In addition, download traffic on the Internet 20 can be considerably reduced as each of the pieces of the digital object 70 has to be downloaded only once from the P2P server 10 by one of the peers 40a-40d to finally provide a copy of the whole digital object 70 to the cache 30 and hence to all of the peers 40a to 4Od.
In a further embodiment of the invention, the cache 30 can also download the meta- information relating to the digital object and the pieces of the digital objectfrom the P2P server 10 without the meta-information and/or the pieces passing through the peers 40a-d. In another embodiment of the invention, a publisher provides a copy of the digital object including the meta-information to the cache 30, enabling direct download for the peer 40a to 40c.
In one embodiment of the invention, the cache 30 can delay the requesting of some of the pieces of the data objects. Thus the cache 30 can supply pieces of the data object which are not available in the peers 40a-d. When the number of pieces present in the cache 30 but not present in the peers 40a-d falls below a certain level, then the cache 30 can request pieces of the digital object. This level depends on the digital object being downloaded or it could be a fixed number
In yet another embodiment of the invention shown in Fig. 3, some of the peers 40a-d may be each connected to different data sources 310a-c. Each of the different data sources 310a-c provide different pieces 371, 372 and 373 of the digital object 370. For example, the peer 40a may, except being connected to the cache 30, be connected to the data source 310a, for example, via the internet. The data source 310a has only a first piece 371 of the digital object
370 available for download. The peer 40a may be looking for the first piece 371, the peer 40a may, also be looking for a second piece 372 and a third piece 373 which are not available on the data source 31 Oa he is connected to. However, as peer 40a is requesting the first piece 371 of the digital object 370 the peer 40a will download piece 371 to the local memory 45a and subsequently upload it to the cache 30 (shown on Fig. 1), wherefrom it is available for download to all the peers 40a-d.
In parallel, the peer 40b may also wish to download digital object 370. As the first piece 371 of the digital object 370 is available in the cache 30, peer 40b may download the first piece
371 of the digital object 370 from the cache 30 to the local memory 45b. The peer 40b may, except being connected to cache 30, also be connected to a second data source 310b which has the second piece 372 of the digital object 370 available for download. Thus peer 40b will download the second piece 372 of the digital object 370 from the data source 310b, store the second piece 372 in the local memory 45b and upload a copy of the second piece 372 to the cache 30. Thus both, the peer 40b and the cache 30 each have the first piece 371 and the second piece 372 of the digital object 370. Peer 40a may now check on a regular basis the availability of the pieces of the digital object on the cache 30. The check for the availability is done by examining BitField or Have messages issued by the cache 30. The peer 40a will identify from the BitField or Have messages that the first piece 371 and the second piece 372 of the digital object 370 are available for download in the cache 30. As the peer 40a has already downloaded the first piece 371 the peer 40a will now download the second piece 372.
The third peer 40c may now wish to download the digital object 370. The third peer 40c is connected to the cache 30 and to a third data source 310c. The third peer 40c now finds the first piece 371 and the second piece 372 of the digital object 370 available on the cache 30. The third peer 40c may also find the first piece 371 and the third piece 373 available on the data source 310c. The third peer 40c may download the first piece 371 either from the cache 30 or from the data source 310c depending on the download speed and fast access availability.
It is probable that access from the cache 30 is faster. In various embodiments of the invention, downloading from the cache 30 is preferred as the cache 30 is always ready for download and - as explained above - generally unchokes every request for one of the pieces. However, should the cache 30 be unavailable or slow, for example, caused by large data transfers, the third peer 40c may download the first piece 371 from the third data source 310c. The third peer 40c will download the second piece 372 form the cache 30 and the third piece 373 of the digital object 370. Subsequently, the third peer 40c will upload the third piece 373 of the digital object 370 to the cache 30.
The cache 30 now has the first piece 371, the second piece 372 and the third piece 373 of the digital object 370 available for download. The first peer 40a and the second peer 40b may download the missing third piece 373 of the digital object 370 from the cache 30.
A fourth peer 4Od requesting to download digital object 370 may download all the three pieces 371, 372, and 373 of the digital object 370 from the cache 30 without accessing or connecting to any of the data sources 310a-310c. As pieces 371, 372, and 373 of the digital object 370 can be downloaded from the cache 30, the need for slow upload connections with other peer 40a -40c is eliminated. It is to be understood that the example described with respect to Fig. 3 is an illustrative example and that digital object 370 may have a plurality of pieces 371, 372, 373. The plurality of pieces 371, 372 and 373 of the digital object 370 may be downloaded by many more peers 40a-40c. The peers 40a-40c may also download pieces of the digital object 370 from the data sources 310a-c and upload pieces to the cache 30 in parallel. It is also obvious that the peer 40a-40c may download a large number of pieces or even all of the pieces of the digital object 370 from a single data source.
The method and the network 100 are based on a P2P network, thus allowing any combination of downloads and uploads within the network 100.
Although this invention has been described with respect to the BitTorrent protocol, it is not intended to be limiting of the application to such a protocol. The invention is equally applicable to other protocols.
The invention has been described with respect to various embodiments. It will be understood that the invention is not limited thereto. Numerous charges and modifications are known to the person skilled in the art and the invention is not limited to the details shown and described herein but is intended instead to cover all such charges as are obvious to one of ordinary skill of the art.

Claims

Claims
1. A method for distributing digital objects (370) in a network, the digital objects (370) being distributable in a plurality of pieces (371-373), wherein at least some of a plurality of peers (40a-d) are connected to other ones of the plurality of peers (40a-d) and at least one of the peers (40a-d) being connected to at least one cache (30), the method comprising:
- a first step of receiving a message relating to the digital object (370) from a first one of the plurality of peers (40a-d) at the at least one cache (30)
- a second step of checking whether meta-information relating to the digital object (370) is available in the at least one cache (30); - a third step of requesting the meta-information from a meta-information source in the event that the meta-information is unavailable in the at least one cache (30);
- a fourth step of receiving the meta-information at the at least one cache (30); and -a fifth step of storage of the plurality of pieces (371-373) in the at least one cache (30) based on the meta-information.
2. The method of claim 1, wherein the fifth step comprises obtaining pieces of the digital object from at least some of the plurality of peers (40a-d).
3. The method of claim 1 or 2, wherein the fifth step comprises obtaining pieces of the digital object from the first one of the plurality of peers (40a-d).
4. The method of claim 1 , wherein the fifth step comprises obtaining the pieces of the digital object from at least a further cache.
5. The method of any of the above claims, further comprising a step of connecting to a tracker subsequent to receiving the meta-information to identify members of a swarm and subsequently connecting to and requesting data from at least one of the members of the swarm.
6. The method of any of the above claims, further comprising a step of connecting to a tracker subsequent to receiving the meta-information to identify members of a swarm and subsequently connecting to and transmitting data to the at least one of the members of the swarm.
7. The method of any of the above claims, wherein the meta-information is selected from the group consisting of check sums, file names, file lengths, number of pieces, tracker addresses, seed addresses, server addresses, publisher information, digital signatures and piece sizes.
8. The method of any of the above claims, further comprising a step of delaying the requesting some of the pieces of some of the data objects.
9. The method of claim 8, wherein the step of delaying the requesting until the at least one cache (30) determines that the number of pieces present in the at least one cache (30) but not present in the plurality of peers (40a-40d) falls below a particular level
10. The method of claim 9, wherein the particular level is individually configured per digital object
11. The method of any one of claims 9 to 10, wherein the particular level is a fixed number of pieces.
12. The method of any one of claims 9 to 11, wherein the particular level is related to the rate at which the plurality of peers (40a-40d) are acquiring pieces of the digital object
13. The method of any of the above claims, further comprising a step of blocking the request for some of the data objects.
14. The method of any of the above claims, wherein the meta-information source is selected from the group consisting of one of the plurality of peers (40a-d), a further cache (30), a tracker, a network probe or a file-server.
15. Network for the distribution of digital objects, the digital objects being distributable in a plurality of pieces, the network (10) comprising: - a plurality of peers (40a - 4Od), at least some of the plurality of peers (40a-d) being connected to other ones of the plurality of peers (40a-d);
- at least one data source (310a-c) on which at least pieces (371, 372, 373) of the first digital object (70) are stored, at least one of the plurality of peers (40a- 40c) being connected to the at least one data source (3 lOa-c); - at least one cache (30) for storing at least one piece of the digital object, whereby at least one of the plurality of peers (40a-40d) is connected to the at least one cache (30);
- at least one meta-information source (3 lOa-c) comprising meta-information relating to the digital object. wherein the meta-information is downloadable to the at least one cache (30).
16. Network according to claim 15, wherein the at least one piece of the first digital object uploadable to the at least one cache (30) is downloadable from the at least one cache (30). .
17. Network according to claim 15 or 16, wherein the at least one cache (30) is additionally connected to the network (10).
18. Network according to claim 17 wherein the network (10) is a private network containing the pieces of digital objects.
19. Network according to any of claims 15 to 18, wherein the at least one cache (30) is directly connected to at least one of the data sources (310a-c).
20. Network according to any of claims 15 to 19, wherein the at least one cache (30) is directly connected to at least one of the meta-information sources (310a-c).
PCT/EP2007/007105 2006-08-11 2007-08-10 Cache structure WO2008017503A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07801604.5A EP2057823B1 (en) 2006-08-11 2007-08-10 Cache structure
IL197007A IL197007A (en) 2006-08-11 2009-02-11 Cache structure

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
GB0615965.1 2006-08-11
GB0615965A GB2440761A (en) 2006-08-11 2006-08-11 Using a proxy server as a cache in a peer to peer network to speed up the multicast distribution of large files.
US11/598,112 US8010748B2 (en) 2006-08-11 2006-11-08 Cache structure for peer-to-peer distribution of digital objects
US11/598,112 2006-11-08

Publications (1)

Publication Number Publication Date
WO2008017503A1 true WO2008017503A1 (en) 2008-02-14

Family

ID=37056189

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/007105 WO2008017503A1 (en) 2006-08-11 2007-08-10 Cache structure

Country Status (5)

Country Link
US (2) US8010748B2 (en)
EP (1) EP2057823B1 (en)
GB (1) GB2440761A (en)
IL (1) IL197007A (en)
WO (1) WO2008017503A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010138036A1 (en) * 2009-05-29 2010-12-02 Telefonaktiebolaget L M Ericsson (Publ) Content sharing system performance improvement
US8200906B2 (en) 2006-08-11 2012-06-12 Velocix Limited Cache structure for peer-to-peer distribution of digital objects

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090238365A1 (en) * 2008-03-20 2009-09-24 Kinamik Data Integrity, S.L. Method and system to provide fine granular integrity to digital data
CN102113296B (en) * 2008-07-02 2013-10-16 汤姆森许可贸易公司 Device and method for disseminating content data between peers in a P2P mode, by using a bipartite peer overlay
US9386089B2 (en) * 2008-11-11 2016-07-05 Nbcuniversal Media, Llc Early detection of high volume peer-to-peer swarms
CN103597471B (en) * 2010-12-30 2017-05-17 皮尔爱普有限公司 Methods and systems for caching data communications over computer networks
US8510267B2 (en) * 2011-03-08 2013-08-13 Rackspace Us, Inc. Synchronization of structured information repositories
EP2692111A1 (en) * 2011-03-31 2014-02-05 Telefonaktiebolaget L M Ericsson (PUBL) Method and device for caching
US20130007186A1 (en) * 2011-06-30 2013-01-03 Interdigital Patent Holdings, Inc. Controlling content caching and retrieval
KR102070149B1 (en) * 2013-06-10 2020-01-28 에스케이텔레콤 주식회사 Method for delivery of content by means of caching in communication network and apparatus thereof
US9858195B2 (en) * 2014-12-10 2018-01-02 International Business Machines Corporation Near-cache distribution of manifest among peer applications in in-memory data grid (IMDG) non structured query language (NO-SQL) environments
US10148748B2 (en) 2015-02-26 2018-12-04 Microsoft Technology Licensing, Llc Co-locating peer devices for peer matching
US10270849B2 (en) 2015-02-26 2019-04-23 Microsoft Technology Licensing, Llc Scalable peer matching
KR102346689B1 (en) * 2015-08-28 2022-01-04 한국전자통신연구원 Operation method of peer to peer network management system and peer to peer network management system
US10805161B2 (en) * 2017-09-13 2020-10-13 Verizon Digital Media Services Inc. Rapid configuration propagation in a distributed multi-tenant platform

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020078174A1 (en) 2000-10-26 2002-06-20 Sim Siew Yong Method and apparatus for automatically adapting a node in a network
WO2003088065A1 (en) 2002-04-09 2003-10-23 Akamai Technologies, Inc. Method and system for tiered distribution in a content delivery network
GB2412279A (en) 2004-03-16 2005-09-21 Bbc Technology Holdings Ltd Data distribution system and method

Family Cites Families (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE3737531A1 (en) 1987-11-05 1989-05-18 Koenig & Bauer Ag COLOR RACK FOR A ROLLING MACHINE OF A ROTARY PRINTING MACHINE
US5611049A (en) 1992-06-03 1997-03-11 Pitts; William M. System for accessing distributed data cache channel at each network node to pass requests and data
US5511208A (en) 1993-03-23 1996-04-23 International Business Machines Corporation Locating resources in computer networks having cache server nodes
EP2270687A2 (en) 1995-04-11 2011-01-05 Kinetech, Inc. Identifying data in a data processing system
US6003030A (en) 1995-06-07 1999-12-14 Intervu, Inc. System and method for optimized storage and retrieval of data on a distributed computer network
US6098096A (en) 1996-12-09 2000-08-01 Sun Microsystems, Inc. Method and apparatus for dynamic cache preloading across a network
US6167438A (en) 1997-05-22 2000-12-26 Trustees Of Boston University Method and system for distributed caching, prefetching and replication
SE510048C3 (en) 1997-07-24 1999-05-03 Mirror Image Internet Ab Internet caching system
US6745243B2 (en) 1998-06-30 2004-06-01 Nortel Networks Limited Method and apparatus for network caching and load balancing
US6108703A (en) 1998-07-14 2000-08-22 Massachusetts Institute Of Technology Global hosting system
US6823377B1 (en) 2000-01-28 2004-11-23 International Business Machines Corporation Arrangements and methods for latency-sensitive hashing for collaborative web caching
US7010578B1 (en) 2000-09-21 2006-03-07 Akamai Technologies, Inc. Internet content delivery service with third party cache interface support
US7043524B2 (en) * 2000-11-06 2006-05-09 Omnishift Technologies, Inc. Network caching system for streamed applications
US7072982B2 (en) 2000-11-22 2006-07-04 Microsoft Corporation Universal naming scheme for peer to peer resources
US20020062336A1 (en) 2000-11-22 2002-05-23 Dan Teodosiu Resource coherency among resources cached in a peer to peer environment
US7035911B2 (en) * 2001-01-12 2006-04-25 Epicrealm, Licensing Llc Method and system for community data caching
AUPR458901A0 (en) 2001-04-26 2001-05-24 Iinet Limited Cache for a peer-to-peer data transfer
US7139811B2 (en) * 2001-08-01 2006-11-21 Actona Technologies Ltd. Double-proxy remote data access system
EP1413119B1 (en) 2001-08-04 2006-05-17 Kontiki, Inc. Method and apparatus for facilitating distributed delivery of content across a computer network
JP2003153229A (en) 2001-11-15 2003-05-23 Mitsubishi Electric Corp Apparatus and method for data communication
US20030101267A1 (en) * 2001-11-28 2003-05-29 Thompson Mark R. Peer-to-peer caching network
US20030158958A1 (en) 2002-02-20 2003-08-21 Koninklijke Philips Electronics N.V. Distributed storage network architecture using user devices
US6928441B2 (en) 2002-04-16 2005-08-09 International Business Machines Corporation Electronic catalogs that provide hierarchical access for buyers of goods and services
US20030204602A1 (en) 2002-04-26 2003-10-30 Hudson Michael D. Mediated multi-source peer content delivery network architecture
US9432463B2 (en) 2003-03-25 2016-08-30 Sandvine Incorporated Ulc System and method for diverting established communication sessions on the basis of content
US8239446B2 (en) 2003-11-19 2012-08-07 Sony Computer Entertainment America Llc Content distribution architecture
EP1725948A4 (en) 2004-03-08 2013-01-16 First Oversi Ltd A method and device for peer to peer file sharing
JP4103892B2 (en) 2005-01-26 2008-06-18 オンキヨー株式会社 Peer-to-peer content distribution system
US20060224758A1 (en) * 2005-03-15 2006-10-05 1000 Oaks Hu Lian Technology Development Co., Ltd. System and method for file header operation in a peer-to-peer network providing streaming services
GB2440761A (en) 2006-08-11 2008-02-13 Cachelogic Ltd Using a proxy server as a cache in a peer to peer network to speed up the multicast distribution of large files.

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020078174A1 (en) 2000-10-26 2002-06-20 Sim Siew Yong Method and apparatus for automatically adapting a node in a network
WO2003088065A1 (en) 2002-04-09 2003-10-23 Akamai Technologies, Inc. Method and system for tiered distribution in a content delivery network
GB2412279A (en) 2004-03-16 2005-09-21 Bbc Technology Holdings Ltd Data distribution system and method

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
D. FERGUSON: "Peer to Peer Cache Discovery Protocol (CDP)", 25 August 2006 (2006-08-25), pages 1 - 8, XP002460863, Retrieved from the Internet <URL:http://www.cachelogic.com/home/pages/developers/cdp_spec.txt> [retrieved on 20071203] *
IAIN_WADE: "[BitTorrent] Re: Request for protocol extension: get_info/info messages", ONLINE, 12 January 2005 (2005-01-12), XP002460501, Retrieved from the Internet <URL:http://lists.ibiblio.org/pipermail/bittorrent/2005-January/000642.html> [retrieved on 20071129] *
THANUNCHAI THREEPAK: "Bittorrent Cache using Virtual Tracker", INTERNATIONAL SYMPOSIUM ONCOMMUNICATIONS AND INFORMATION TECHNOLOGIES, 2006. ISCIT '06., 18 October 2006 (2006-10-18), pages 162 - 165, XP002460502, Retrieved from the Internet <URL:http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=4141534> [retrieved on 20071129] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8200906B2 (en) 2006-08-11 2012-06-12 Velocix Limited Cache structure for peer-to-peer distribution of digital objects
WO2010138036A1 (en) * 2009-05-29 2010-12-02 Telefonaktiebolaget L M Ericsson (Publ) Content sharing system performance improvement

Also Published As

Publication number Publication date
EP2057823B1 (en) 2015-10-28
GB2440761A (en) 2008-02-13
IL197007A0 (en) 2009-11-18
US8010748B2 (en) 2011-08-30
US8200906B2 (en) 2012-06-12
EP2057823A1 (en) 2009-05-13
GB0615965D0 (en) 2006-09-20
US20110264744A1 (en) 2011-10-27
US20080040545A1 (en) 2008-02-14
IL197007A (en) 2013-02-28

Similar Documents

Publication Publication Date Title
EP2057823B1 (en) Cache structure
US7995473B2 (en) Content delivery system for digital object
US20080040420A1 (en) Content distribution network
US8224968B1 (en) Method and system for scalable content storage and delivery
US9106668B2 (en) Distributed peer location in peer-to-peer file transfers
JP5464423B2 (en) Method and apparatus for transferring files to a client using a peer-to-peer file transfer model and a client-server file transfer model
US8028019B2 (en) Methods and apparatus for data transfer in networks using distributed file location indices
US20140280604A1 (en) Adaptive distributed application streaming
JP2010522386A (en) Method, system, and node for P2P content sharing
WO2009152754A1 (en) Method, system and device for providing contents based on peer to peer network
US20060236386A1 (en) Method and apparatus for cooperative file distribution in the presence of firewalls
US8244867B2 (en) System and method for the location of caches
WO2008017502A1 (en) Content distribution network
El Dick et al. Flower-CDN: a hybrid P2P overlay for efficient query processing in CDN
US9241032B2 (en) Storage performance
Skevik et al. Analysis of bittorrent and its use for the design of a p2p based streaming protocol for a hybrid cdn
Berkes Decentralized peer-to-peer network architecture: Gnutella and freenet
IL197008A (en) Method and apparatus for providing improved storage performance
Johnsen et al. Peer-to-peer networking with BitTorrent
US20080288447A1 (en) Methods and apparatus for improving peer efficiency
Toole et al. Bittorrent architecture and protocol
Talaei et al. Adding multimedia streaming to BitTorrent
Varsandan A Peer to Peer Network for Distributed Case Based Reasoning Project Report
Pacitti et al. Content Distribution in P2P Systems
WO2008017504A1 (en) Content delivery system for digital object

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: 07801604

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 197007

Country of ref document: IL

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2007801604

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: RU

WWE Wipo information: entry into national phase

Ref document number: 221633

Country of ref document: IL