Data client

• US 9,807,163 B1
• Filed: 07/20/2015
• Issued: 10/31/2017
• Est. Priority Date: 11/15/2006
• Status: Active Grant

• Current Assignee: Conviva Inc.
• Original Assignee: Conviva Inc.
• Inventors: Stoica, Ion, Zhang, Hui, Mccanne, Steven R., Zhan, Jibin, Ganjam, Aditya Ravikumar
• Primary Examiner(s): Jean, Frantz
• Application Number:
  US14/804,165
• Time in Patent Office: 834 Days
• Field of Search: 709203, 709223, 709228, 370329
• 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/1074 for supporting data block transmission mechanisms file transfer H04L67/06
• 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 of the requesting peer is determined. Determining the peer type of the requesting peer includes determining whether the requesting peer is a regular peer or a lightweight peer. A regular peer is one that is able to accept incoming connection requests and initiate connections. A lightweight peer is one that has less functionality than the regular peer.

Claims

1. A system, comprising:

a set of one or more processors configured to;

receive a request for content from a requesting peer; and

determine a peer type of the requesting peer, wherein determining the peer type of the requesting peer includes determining whether the requesting peer is a regular peer or a lightweight 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 reduced functionality in comparison to the regular peer, and wherein the lightweight peer is at least one of unable to accept incoming connection requests, limited in the sources from which it can receive content, and unable to redirect content; and

a memory coupled to the set of one or more processors and configured to provide the set of one or more processors with instructions.

2. The system of claim 1 wherein determining the peer type of the requesting peer includes testing a functionality of the requesting peer.

3. The system of claim 1 wherein determining the peer type of the requesting peer is based at least in part on implementation information associated with the requesting peer.

4. The system of claim 1 wherein the set of one or more processors is further configured to assign a sending peer to the requesting peer.

5. The system of claim 4 wherein the assigning is based at least in part on the determined peer type of the requesting peer.

6. The system of claim 4 wherein the sending peer is configured to send a connection request to the requesting peer.

7. The system of claim 4 wherein the requesting peer is configured to send a connection request to the sending peer.

8. The system of claim 4 wherein the sending peer is configured to send a connection request to the requesting peer and wherein the requesting peer is configured to send a connection request to the sending peer.

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

10. The system of claim 4 wherein the sending peer is a lightweight peer and wherein the sending peer is configured to send a connection request to the requesting peer.

11. The system of claim 4 wherein the requesting peer is a lightweight peer and wherein the requesting peer is configured to send a connection request to the sending peer.

12. The system of claim 4 wherein the set of one or more processors is further configured to determine whether a connection attempt involving the requesting peer and the sending peer is successful.

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

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

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

16. A method, comprising:

receiving a request for content from a requesting peer;

determining, using a set of one or more processors, a peer type of the requesting peer, wherein determining the peer type of the requesting peer includes determining whether the requesting peer is a regular peer or a lightweight 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 reduced functionality in comparison to the regular peer, and wherein the lightweight peer is at least one of unable to accept incoming connection requests, limited in the sources from which it can receive content, and unable to redirect content.

17. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a request for content from a requesting peer;

determining a peer type of the requesting peer, wherein determining the peer type of the requesting peer includes determining whether the requesting peer is a regular peer or a lightweight 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 reduced functionality in comparison to the regular peer, and wherein the lightweight peer is at least one of unable to accept incoming connection requests, limited in the sources from which it can receive content, and unable to redirect content.