Unicast/multicast architecture

Abstract

A system and method for providing content to users including a multicast sub-system providing content to multiple users and a unicast sub-system providing content to individual users. The multicast sub-system being operative to push to each of a plurality of user communities, content relating to the community and the unicast sub-system being operative to provide on demand to a user, content which has not been previously pushed to the user.

1. A method for bandwidth allocation in a unicast-multicast environment, said method comprising:
 selecting a sampling time duration; 
 determining a current community size for each of a plurality of communities; and 
 determining a multicast candidacy threshold for each community using data regarding said current community size for said selected sampling time duration; 
 wherein said determining the multicast candidacy threshold comprises:
 making an initial assumption as to the minimum number of hits on a site for a given population of potential surfers over a given time duration, which characterizes a “popular site”; and 
 establishing said multicast candidacy threshold for each community as said minimum number multiplied by said sampling time duration and multiplied by said current size of each community. 
 
 
     
     
       2. A method for bandwidth allocation according to  claim 1  and also comprising:
 monitoring a number of hits per URL for individual ones of said plurality of communities during each said sampling time duration; and 
 converting said number of hits to a URL hit score. 
 
     
     
       3. A method for bandwidth allocation according to  claim 2  and also comprising weighting said URL hit score according to trends in the number of hits per URL. 
     
     
       4. A method for bandwidth allocation according to  claim 2  and also comprising:
 determining multicast candidacy of a given site by applying a multicast candidacy threshold to said URL hit score. 
 
     
     
       5. A method for bandwidth allocation according to  claim 4  and also comprising continuing to monitor the number of hits on a given site per community even if said given site is not considered as a multicast candidate. 
     
     
       6. A method for bandwidth allocation according to  claim 4  and also comprising:
 if a given site is considered to be a multicast candidate:
 normalizing said URL hit score for said community size; and 
 employing said normalized URL hit score to create a clout score based not only on per capita popularity but also on the community size. 
 
 
     
     
       7. A method for bandwidth allocation according to  claim 6  and wherein said employing includes application of at least one of linear and non-linear weightings. 
     
     
       8. A method for bandwidth allocation according to  claim 6  and also comprising:
 queuing said multicast candidate sites based on their respective clout scores; and 
 multicasting content of the site having the highest queue position to the extent of the availability of multicast bandwidth. 
 
     
     
       9. A method for bandwidth allocation according to  claim 1  and wherein said sampling time duration is of the order of minutes. 
     
     
       10. A method for bandwidth allocation according to  claim 4  and wherein said determining of multicast candidacy threshold is carried out in accordance with the size of the queue of multicast candidate sites. 
     
     
       11. A method for bandwidth allocation according to  claim 10  and wherein said determining of multicast candidacy is carried out in the following manner:
 if the queue size exceeds a predetermined maximum queue threshold, the multicast candidacy threshold is modified by increasing said minimum number of hits on a site for a given population of potential surfers over a given time duration which is required to characterize a site as a “popular site”; and 
 if the queue size falls below a predetermined minimum queue threshold, the multicast candidacy threshold is modified by reducing the minimum number of hits on a site for a given population of potential surfers over a given time duration which is required to characterize a site as a “popular site”. 
 
     
     
       12. A method for bandwidth allocation according to  claim 1  and also comprising:
 monitoring the amount of bandwidth allocated to multicasting of site content to members of each community. 
 
     
     
       13. A method for bandwidth allocation in a unicast-multicast environment, wherein unicast and multicast share the same bandwidth, said method comprising:
 determining the availability of multicast bandwidth at least in part by the extent of utilization of bandwidth by unicast, which has a higher priority than multicast; 
 selecting a sampling time duration; 
 determining a current community size for each of a plurality of communities; and 
 determining a multicast candidacy threshold for each community using data regarding said current community size for said selected sampling time duration; 
 wherein said determining the multicast candidacy threshold comprises:
 making an initial assumption as to the minimum number of hits on a site for a given population of potential surfers over a given time duration, which characterizes a “popular site”; and 
 establishing said multicast candidacy threshold for each community as said minimum number multiplied by said sampling time duration and multiplied by said current size of each community. 
 
 
     
     
       14. A method for bandwidth allocation according to  claim 13  and also comprising:
 monitoring a number of hits per URL for individual ones of said plurality of communities during each said sampling time duration; and 
 converting said number of hits to a URL hit score. 
 
     
     
       15. A method for bandwidth allocation according to  claim 14  and also comprising weighting said URL hit score according to trends in the number of hits per URL. 
     
     
       16. A method for bandwidth allocation according to  claim 14  and also comprising:
 determining multicast candidacy of a given site by applying a multicast candidacy threshold to said URL hit score. 
 
     
     
       17. A method for bandwidth allocation according to  claim 16  and also comprising continuing to monitor the number of hits on a given site per community even if said given site is not considered as a multicast candidate. 
     
     
       18. A method for bandwidth allocation according to  claim 16  and also comprising:
 if a given site is considered to be a multicast candidate:
 normalizing said URL hit score for said community size; and 
 employing said normalized URL hit score to create a clout score based not only on per capita popularity but also on the community size. 
 
 
     
     
       19. A method for bandwidth allocation according to  claim 18  and wherein said employing includes application of at least one of linear and non-linear weightings. 
     
     
       20. A method for bandwidth allocation according to  claim 18  and also comprising:
 queuing said multicast candidate sites based on their respective clout scores; and 
 multicasting content of the site having the highest queue position to the extent of the availability of multicast bandwidth. 
 
     
     
       21. A method for bandwidth allocation according to  claim 13  and wherein said sampling time duration is of the order of minutes. 
     
     
       22. A method for bandwidth allocation according to  claim 13  and wherein said determining of multicast candidacy threshold is carried out in accordance with the size of the queue of multicast candidate sites. 
     
     
       23. A method for bandwidth allocation according to  claim 22  and wherein said determining of multicast candidacy is carried out in the following manner:
 if the queue size exceeds a predetermined maximum queue threshold, the multicast candidacy threshold is modified by increasing said minimum number of hits on a site for a given population of potential surfers over a given time duration which is required to characterize a site as a “popular site”; 
 if the queue size falls below a predetermined minimum queue threshold, the multicast candidacy threshold is modified by reducing the minimum number of hits on a site for a given population of potential surfers over a given time duration which is required to characterize a site as a “popular site”, subject to the condition that the multicast candidacy threshold is not permitted to fall below a minimum multicast candidacy threshold; and 
 if the minimum multicast candidacy threshold is reached, the remaining available bandwidth is allocated to unicast transmission in order to reduce latency thereof. 
 
     
     
       24. A method for bandwidth allocation according to  claim 13  and also comprising:
 monitoring the amount of bandwidth allocated to multicasting of site content to members of each community. 
 
     
     
       25. A method for bandwidth allocation in a priority multicast, unicast, non-priority multicast environment, wherein priority multicast, unicast and non-priority multicast share the same bandwidth, said method comprising:
 determining the availability of non-priority multicast bandwidth at least in part by the extent of utilization of bandwidth by priority multicast, which has a higher priority than unicast and unicast, which has a higher priority than non-priority multicast; selecting a sampling time duration; 
 determining a current community size for each of a plurality of communities; and 
 determining a non-priority multicast candidacy threshold for each community using data regarding said current community size for said selected sampling time duration; 
 wherein said determining the non-priority multicast candidacy threshold comprises:
 making an initial assumption as to the minimum number of hits on a site for a given population of potential surfers over a given time duration, which characterizes a “popular site”; and 
 establishing said non-priority multicast candidacy threshold for each community as said minimum number multiplied by said sampling time duration and multiplied by said current size of each community. 
 
 
     
     
       26. A method for bandwidth allocation according to  claim 25  and also comprising:
 monitoring a number of hits per URL for individual ones of said plurality of communities during each said sampling time duration; and 
 converting said number of hits to a URL hit score. 
 
     
     
       27. A method for bandwidth allocation according to  claim 26  and also comprising weighting said URL hit score according to trends in the number of hits per URL. 
     
     
       28. A method for bandwidth allocation according to  claim 26  and also comprising:
 determining non-priority multicast candidacy of a given site by applying a non-priority multicast candidacy threshold to said URL hit score. 
 
     
     
       29. A method for bandwidth allocation according to  claim 28  and also comprising continuing to monitor the number of hits on a given site per community even if said given site is not considered as a non-priority multicast candidate. 
     
     
       30. A method for bandwidth allocation according to  claim 28  and also comprising:
 if a given site is considered to be a non-priority multicast candidate:
 normalizing said URL hit score for said community size; and 
 employing said normalized URL hit score to create a clout score based not only on per capita popularity but also on the community size. 
 
 
     
     
       31. A method for bandwidth allocation according to  claim 30  and wherein said employing includes application of at least one of linear and non-linear weightings. 
     
     
       32. A method for bandwidth allocation according to  claim 29  and also comprising:
 queuing said non-priority multicast candidate sites based on their respective clout scores; and 
 non-priority multicasting content of the site having the highest queue position to the extent of the availability of non-priority multicast bandwidth. 
 
     
     
       33. A method for bandwidth allocation according to  claim 25  and wherein said sampling time duration is of the order of minutes. 
     
     
       34. A method for bandwidth allocation according to  claim 25  and wherein said determining of non-priority multicast candidacy threshold is carried out in accordance with the size of the queue of non-priority multicast candidate sites. 
     
     
       35. A method for bandwidth allocation according to  claim 34  and wherein said determining of non-priority multicast candidacy is carried out in the following manner:
 if the queue size exceeds a predetermined maximum queue threshold, the non-priority multicast candidacy threshold is modified by increasing said minimum number of hits on a site for a given population of potential surfers over a given time duration which is required to characterize a site as a “popular site”; 
 if the queue size falls below a predetermined minimum queue threshold, the non-priority multicast candidacy threshold is modified by reducing the minimum number of hits on a site for a given population of potential surfers over a given time duration which is required to characterize a site as a “popular site”, subject to the condition that the non-priority multicast candidacy threshold is not permitted to fall below a minimum non-priority multicast candidacy threshold; and 
 if the minimum non-priority multicast candidacy threshold is reached, the remaining available bandwidth is allocated to unicast transmission in order to reduce latency thereof. 
 
     
     
       36. A method for bandwidth allocation according to  claim 25  and also comprising:
 monitoring the amount of bandwidth allocated to non-priority multicasting of site content to members of each community.