US2015120833A1PendingUtilityA1

Optimization of peer-to-peer content delivery service

Assignee: INTERDIGITAL PATENT HOLDINGSPriority: Apr 6, 2012Filed: Apr 5, 2013Published: Apr 30, 2015
Est. expiryApr 6, 2032(~5.7 yrs left)· nominal 20-yr term from priority
H04L 67/104H04L 67/2842H04L 67/1097H04L 67/568H04L 67/1076H04W 4/029H04W 4/02
42
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A method and apparatus are described for providing a dynamic cache function in a network or cloud. A content cache server (CCS) and a lightweight CCS with a dynamic cache function may be deployed in the network or cloud. A tracker may be used to place dynamic cache peers in a peer list, and transmit the peer list to a wireless transmit/receive unit (WTRU). The peer list may include a single peer that is a dynamic cache peer allocated by the tracker to the WTRU, or at least two dynamic cache peers, with one additional “weight” parameter for each dynamic cache peer. The WTRU may connect to the dynamic cache peer with the largest “weight” parameter, and connect to a different dynamic cache peer in the peer list on a condition that the WTRU gets disconnected or gets bad service from the dynamic cache peer with the largest “weight” parameter.

Claims

exact text as granted — not AI-modified
1 .- 20 . (canceled) 
     
     
         21 . A device, comprising:
 a processor configured to:
 receive a request for a peer list from a first wireless transmit/receive unit (WTRU); 
 determine one or more peer list candidate devices; 
 place at least a first peer in the peer list; 
 send the peer list to the first wireless transmit/receive unit (WTRU); 
 receive a request from the first peer for one or more data segments, the one or more data segments requested by the WTRU; 
 identify which of the one or more data segments are stored on the first peer; 
 dynamically obtain any of the one or more data segments not stored on the first peer from at least one other node via a P2P protocol; and 
 send at least one of the identified one or more data segments, or the obtained one or more data segments to the first WTRU. 
   
     
     
         22 . The device of  claim 21 , wherein the processor is further configured to:
 identify the first peer in the peer list by a flag;   place a second peer in the peer list; and   place a second WTRU in the peer list.   
     
     
         23 . The device of  claim 21 , wherein the processor is further configured to:
 place a second peer in the peer list;   associate a first weight parameter with the first peer in the peer list; and   associate a second weight parameter with the second peer in the peer list, the first weight parameter being larger than the second weight parameter.   
     
     
         24 . The device of  claim 21 , wherein the request includes a first indication, and the processor is further configured to:
 interpret the first indication such that the device is to function as a dynamic cache peer (DCP) device regarding the request for the one or more data segments.   
     
     
         25 . A dynamic cache peer (DCP) capable device, the DCP capable device in communication with a wireless transmit/receive unit (WTRU) and at least one other node, the DCP capable device comprising:
 a processor configured to:
 receive a request from the WTRU for one or more data segments via a peer-to-peer (P2P) protocol; 
 identify which of the one or more data segments are stored on the DCP capable device; 
 dynamically obtain any of the one or more data segments not stored on the DCP capable device from the at least one other node via the P2P protocol; and 
 send at least one of the identified one or more data segments, or the obtained one or more data segments, to the WTRU via the P2P protocol. 
   
     
     
         26 . The DCP capable device of  claim 25 , wherein the processor is further configured to implement a lightweight peer-to-peer (P2P) protocol mode, and the request for the one or more data segments is received without a request from the WTRU for a bitmap corresponding to the one or more data segments. 
     
     
         27 . The DCP capable device of  claim 25 , wherein the processor is further configured to implement a lightweight peer-to-peer (P2P) protocol mode, and the request for the one or more data segments includes a second indication for the DCP capable device to operate in the lightweight P2P protocol mode. 
     
     
         28 . The DCP capable device of  claim 25 , wherein the processor is further configured to:
 communicate that the DCP capable device can provide the one or more data segments.   
     
     
         29 . The DCP capable device of  claim 25 , wherein the DCP capable device is a SuperPeer device. 
     
     
         30 . The DCP capable device of  claim 25 , wherein the DCP capable device has at least one of: a relatively larger bandwidth capacity than of a non-dynamic cache peer, or a relatively larger processing capacity than of a non-dynamic cache peer. 
     
     
         31 . The DCP capable device of  claim 25 , wherein the processor is further configured to implement a lightweight peer-to-peer (P2P) protocol mode, and the DCP capable device is at least one of: a content cache server (CCS) or a lightweight content cache server (L-CCS). 
     
     
         32 . The DCP capable device of  claim 25 , wherein the request includes a first indication, and the processor is further configured to:
 interpret the first indication such that the DCP capable device is to function as a DCP device regarding the request for the one or more data segments.   
     
     
         33 . A method for providing a dynamic cache peer (DCP) function, the method comprising:
 receiving a request from a wireless transmit/receive unit (WTRU) for one or more data segments via a peer-to-peer (P2P) protocol;   identifying which of the one or more data segments are stored on a DCP capable device;   dynamically obtaining any of the one or more data segments not stored on the DCP capable device from at least one other node in communication with the DCP capable device via the P2P protocol; and   sending at least one of the identified one or more data segments, or the obtained one or more data segments, to the WTRU via the P2P protocol.   
     
     
         34 . The method of  claim 33 , further comprising:
 implementing a lightweight peer-to-peer (P2P) protocol mode by the DCP capable device, wherein the request for the one or more data segments is received without a request from the WTRU for a bitmap corresponding to the one or more data segments.   
     
     
         35 . The method of  claim 33 , further comprising:
 implementing a lightweight peer-to-peer (P2P) protocol mode by the DCP capable device, wherein the request for the one or more data segments includes a second indication for the DCP device to operate in the lightweight P2P protocol mode.   
     
     
         36 . The method of  claim 33 , further comprising:
 communicating, by the DCP capable device, that the one or more data segments can be provided.   
     
     
         37 . The method of  claim 33 , wherein the DCP capable device is a SuperPeer device. 
     
     
         38 . The method of  claim 33 , wherein the DCP capable device has at least one of: a relatively larger bandwidth capacity than of a non-dynamic cache peer, or a relatively larger processing capacity than of a non-dynamic cache peer. 
     
     
         39 . The method of  claim 33 , further comprising:
 implementing a lightweight peer-to-peer (P2P) protocol mode by the DCP capable device, wherein the DCP capable device is at least one of: a content cache server (CCS) or a lightweight content cache server (L-CCS).   
     
     
         40 . The method of  claim 33 , wherein the request includes a first indication, and the method further comprises:
 interpreting the first indication such that the DCP capable device is to function as a DCP device regarding the request for the one or more data segments.

Join the waitlist — get patent alerts

Track US2015120833A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.