Matches in UGent Biblio for { <https://biblio.ugent.be/publication/705954#aggregation> ?p ?o. }
Showing items 1 to 30 of
30
with 100 items per page.
- aggregation classification "P1".
- aggregation creator person.
- aggregation creator person.
- aggregation creator person.
- aggregation creator person.
- aggregation date "2009".
- aggregation hasFormat 705954.bibtex.
- aggregation hasFormat 705954.csv.
- aggregation hasFormat 705954.dc.
- aggregation hasFormat 705954.didl.
- aggregation hasFormat 705954.doc.
- aggregation hasFormat 705954.json.
- aggregation hasFormat 705954.mets.
- aggregation hasFormat 705954.mods.
- aggregation hasFormat 705954.rdf.
- aggregation hasFormat 705954.ris.
- aggregation hasFormat 705954.txt.
- aggregation hasFormat 705954.xls.
- aggregation hasFormat 705954.yaml.
- aggregation isPartOf urn:isbn:9781605583402.
- aggregation language "eng".
- aggregation publisher "Association for Computing Machinery (ACM)".
- aggregation subject "Technology and Engineering".
- aggregation title "Transport capacity for a catch-up television service".
- aggregation abstract "One of the biggest advantages of interactive television (TV) is that it allows the viewer to watch the content at his or her most convenient time, either by pausing an ongoing broadcast or by selecting to view the content at a time later than the original airing time. The former service, often referred to as Pause Life TV (PLTV), and the latter, often referred to as Catch-Up TV (CUTV), require that an individual unicast flow is set up per user, whereas for the traditional Linear Programming TV (LPTV) the user just tunes in to a multicast flow that can serve many viewers. We first show that when services like PLTV and CUTV gain in popularity, the transport capacity required in certain parts of the network risks to grow unwieldy, unless the content is replicated (i.e., cached) in the appropriate places in the network. Subsequently, we show that a good caching algorithm that tracks the evolving popularity of the content and takes into account the initial popularity, allows keeping the required capacity under control. Finally, we discuss the trade-offs involved in determining the optimal cache location.".
- aggregation authorList BK195573.
- aggregation endPage "169".
- aggregation startPage "161".
- aggregation isDescribedBy 705954.
- aggregation similarTo LU-705954.