Data client

• US 8,566,436 B1
• Filed: 03/23/2010
• Issued: 10/22/2013
• Est. Priority Date: 11/15/2006
• Status: Active Grant

• Current Assignee: Conviva Inc.
• Original Assignee: Conviva Inc.
• Inventors: Stoica, Ion, Zhang, Hui, Zhan, Jibin, Ganjam, Aditya R., Mccanne, Steven R.
• Primary Examiner(s): JEAN, FRANTZ B
• Application Number:
  US12/730,032
• Time in Patent Office: 1,309 Days
• Field of Search: 709/203, 709/223, 709/202, 370/329
• US Class Current: 709/223
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1076 Resource dissemination mechanisms or network resource keeping policies for optimal resource availability in the overlay network
• CPC Class Codes: H04L 67/1085 involving dynamic management of active down- or uploading connections

Abstract

Facilitating the distribution of content is disclosed. A request for content is received from a requesting peer. A peer type compatibility criteria is applied to an allocation process that allocates at least one sending peer to deliver the content to the requesting peer. The peer type compatibility criteria ensures that a lightweight peer is paired with a regular peer.

Claims

1. A system for facilitating the distribution of content, comprising:

a computer processor configured to;

receive a request for content from a requesting peer; and

apply a peer type compatibility criteria to an allocation process that allocates at least one sending peer from a plurality of candidate sending peers to deliver the content to the requesting peer;

wherein applying the peer type compatibility criteria includes determining the type of the requesting peer and at least a portion of the plurality of candidate sending peers to ensure that a lightweight peer is paired with a regular peer;

wherein a regular peer is a peer that is able to accept incoming connection requests and initiate connections; and

wherein a lightweight peer is a peer that has less functionality than the regular peer; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system of claim 1 wherein the lightweight peer is able to initiate connections but is unable to accept incoming connection requests.

3. The system of claim 1 wherein the lightweight peer is limited in the sources from which it can receive content.

4. The system of claim 3 wherein the lightweight peer is limited based at least in part on an access list.

5. The system of claim 1 wherein the lightweight peer is unable to redirect content.

6. The system of claim 1 wherein the regular peer comprises a content delivery network node.

7. The system of claim 1 wherein the lightweight peer is a no-install client.

8. The system of claim 1 wherein the sending peer is configured to send a connection request to the receiving peer.

9. The system of claim 1 wherein the receiving peer is configured to send a connection request to the sending peer.

10. The system of claim 1 wherein the sending peer is configured to send a connection request to the receiving peer and wherein the receiving peer is configured to send a connection request to the sending peer.

11. The system of claim 1 wherein the allocation process includes allocating a plurality of sending peers that cooperate to deliver the content to the requesting peer.

12. The system of claim 1 wherein the sending peer is a lightweight client and wherein the sending peer is configured to send a connection request to the receiving peer.

13. The system of claim 1 wherein the receiving peer is a lightweight client and wherein the receiving peer is configured to send a connection request to the sending peer.

14. The system of claim 1 wherein the processor is further configured to determine whether a connection attempt involving the requesting peer and the sending peer is successful.

15. A method for facilitating the distribution of content, comprising:

receiving a request for content from a requesting peer;

applying, using a computer processor, a peer type compatibility criteria to an allocation process that allocates at least one sending peer from a plurality of candidate sending peers to deliver the content to the requesting peer;

wherein applying the peer type compatibility criteria includes determining the type of the requesting peer and at least a portion of the plurality of candidate sending peers to ensure that a lightweight peer is paired with a regular peer;

wherein a regular peer is a peer that is able to accept connections and initiate connections; and

wherein a lightweight peer is able to initiate connections but is unable to accept connections.

16. A computer program product for facilitating the distribution of content, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a request for content from a requesting peer;

applying a peer type compatibility criteria to an allocation process that allocates at least one sending peer from a plurality of candidate sending peers to deliver the content to the requesting peer;

wherein applying the peer type compatibility criteria includes determining the type of the requesting peer and at least a portion of the plurality of candidate sending peers to ensure that a lightweight peer is paired with a regular peer;

wherein a regular peer is a peer that is able to accept connections and initiate connections; and

wherein a lightweight peer is able to initiate connections but is unable to accept connections.