@article{ Digital01,
  author = {Digital Fountain},
  title = {A Quantum Leap in Content Delivery: Digital Fountain's Meta-Content Technology},
  journal = {White Paper published by Digital Fountain},
  year = {2001},
  annote = {This paper introduces Digital Fountain's technology for solving the reliability and scalability problems associated with distribution of files and streaming media over the Internet. The Fountain Server architecture consists of two main functional components: a meta-content engine, and a replication system. The key to the architecture's scalability and efficiency is the concept of meta-content: For each piece of content, the meta-content engine generates a stream of meta-content, which consists of mathematical metaphors that describe the original content. Meta-content has the following fundamental properties: - they are independently generated, i.e. there are no interrelationship between the meta-content produced for two consecutive packets. - an exact copy of the original content can be generated from any portion of meta-content of sufficient length, i.e. it is not which packets that is received that matters, but how many. The underlying coding technology behind the meta-content is the, so called, Luby-transform. Conceptually, the Luby-transform generates meta-content as follows: the content is first logically partitioned into a number of equal length pieces. The partition is performed using combinatorial mathematics. The meta-content pieces could be viewed as random linear equations over the pieces of the original content. Once a client receives enough of these equations, it can solve them to reconstruct the pieces. The heart of the Luby-transform is the structure of the meta-content equations making them linerarly independent. Multicast clients are able to directly receive the meta-content packets generated by the meta-content engine. However, meta-content sent to unicast clients cannot be delivered directly. Instead, unicast clients subscribes to the replication system which uses unicast UDP for packet distribution. Digital Fountain has also designed a new congestion control protocol. Their protocol is called Fair Layered Increase Decrease (FLID). FLID was designed with the following goals: - Scalable. The sever should not se any difference when the number of clients changes. - Receiver-driven. - Fair to contending flows. FLID is a receiver-driven, end-to-end congestion control protocol that does not require any changes to existing routers. In FLID, the server sends a separate stream of meta-content packets generated for a piece of content to several multicast groups called "layers". A client independently adjusts its reception rate in response to network conditions by joining and leaving the layers. In periods of no congestion, a client increases its reception rate by joining new layers. The client decreases its reception rate in response to congestion by leaving layers. },
  url = {papers/Digital01.pdf.gz},
  bibdate = {Thursday, April 19, 2001 at 10:00:53 (CEST)},
  submitter = {Karl-Johan Grinnemo}
}

{"_id":"h4tRfMe4bZpuE3kTL","bibbaseid":"fountain-aquantumleapincontentdeliverydigitalfountainsmetacontenttechnology-2001","downloads":0,"creationDate":"2015-12-04T23:32:56.543Z","title":"A Quantum Leap in Content Delivery: Digital Fountain's Meta-Content Technology","author_short":["Fountain, D."],"year":2001,"bibtype":"article","biburl":"http://www.cs.kau.se/cs/prtp/prtp.bib","bibdata":{"annote":"This paper introduces Digital Fountain's technology for solving the reliability and scalability problems associated with distribution of files and streaming media over the Internet. The Fountain Server architecture consists of two main functional components: a meta-content engine, and a replication system. The key to the architecture's scalability and efficiency is the concept of meta-content: For each piece of content, the meta-content engine generates a stream of meta-content, which consists of mathematical metaphors that describe the original content. Meta-content has the following fundamental properties: - they are independently generated, i.e. there are no interrelationship between the meta-content produced for two consecutive packets. - an exact copy of the original content can be generated from any portion of meta-content of sufficient length, i.e. it is not which packets that is received that matters, but how many. The underlying coding technology behind the meta-content is the, so called, Luby-transform. Conceptually, the Luby-transform generates meta-content as follows: the content is first logically partitioned into a number of equal length pieces. The partition is performed using combinatorial mathematics. The meta-content pieces could be viewed as random linear equations over the pieces of the original content. Once a client receives enough of these equations, it can solve them to reconstruct the pieces. The heart of the Luby-transform is the structure of the meta-content equations making them linerarly independent. Multicast clients are able to directly receive the meta-content packets generated by the meta-content engine. However, meta-content sent to unicast clients cannot be delivered directly. Instead, unicast clients subscribes to the replication system which uses unicast UDP for packet distribution. Digital Fountain has also designed a new congestion control protocol. Their protocol is called Fair Layered Increase Decrease (FLID). FLID was designed with the following goals: - Scalable. The sever should not se any difference when the number of clients changes. - Receiver-driven. - Fair to contending flows. FLID is a receiver-driven, end-to-end congestion control protocol that does not require any changes to existing routers. In FLID, the server sends a separate stream of meta-content packets generated for a piece of content to several multicast groups called \"layers\". A client independently adjusts its reception rate in response to network conditions by joining and leaving the layers. In periods of no congestion, a client increases its reception rate by joining new layers. The client decreases its reception rate in response to congestion by leaving layers.","author":["Fountain, Digital"],"author_short":["Fountain, D."],"bibdate":"Thursday, April 19, 2001 at 10:00:53 (CEST)","bibtex":"@article{ Digital01,\n author = {Digital Fountain},\n title = {A Quantum Leap in Content Delivery: Digital Fountain's Meta-Content Technology},\n journal = {White Paper published by Digital Fountain},\n year = {2001},\n annote = {This paper introduces Digital Fountain's technology for solving the reliability and scalability problems associated with distribution of files and streaming media over the Internet. The Fountain Server architecture consists of two main functional components: a meta-content engine, and a replication system. The key to the architecture's scalability and efficiency is the concept of meta-content: For each piece of content, the meta-content engine generates a stream of meta-content, which consists of mathematical metaphors that describe the original content. Meta-content has the following fundamental properties: - they are independently generated, i.e. there are no interrelationship between the meta-content produced for two consecutive packets. - an exact copy of the original content can be generated from any portion of meta-content of sufficient length, i.e. it is not which packets that is received that matters, but how many. The underlying coding technology behind the meta-content is the, so called, Luby-transform. Conceptually, the Luby-transform generates meta-content as follows: the content is first logically partitioned into a number of equal length pieces. The partition is performed using combinatorial mathematics. The meta-content pieces could be viewed as random linear equations over the pieces of the original content. Once a client receives enough of these equations, it can solve them to reconstruct the pieces. The heart of the Luby-transform is the structure of the meta-content equations making them linerarly independent. Multicast clients are able to directly receive the meta-content packets generated by the meta-content engine. However, meta-content sent to unicast clients cannot be delivered directly. Instead, unicast clients subscribes to the replication system which uses unicast UDP for packet distribution. Digital Fountain has also designed a new congestion control protocol. Their protocol is called Fair Layered Increase Decrease (FLID). FLID was designed with the following goals: - Scalable. The sever should not se any difference when the number of clients changes. - Receiver-driven. - Fair to contending flows. FLID is a receiver-driven, end-to-end congestion control protocol that does not require any changes to existing routers. In FLID, the server sends a separate stream of meta-content packets generated for a piece of content to several multicast groups called \"layers\". A client independently adjusts its reception rate in response to network conditions by joining and leaving the layers. In periods of no congestion, a client increases its reception rate by joining new layers. The client decreases its reception rate in response to congestion by leaving layers. },\n url = {papers/Digital01.pdf.gz},\n bibdate = {Thursday, April 19, 2001 at 10:00:53 (CEST)},\n submitter = {Karl-Johan Grinnemo}\n}","bibtype":"article","id":"Digital01","journal":"White Paper published by Digital Fountain","key":"Digital01","submitter":"Karl-Johan Grinnemo","title":"A Quantum Leap in Content Delivery: Digital Fountain's Meta-Content Technology","type":"article","url":"papers/Digital01.pdf.gz","year":"2001","bibbaseid":"fountain-aquantumleapincontentdeliverydigitalfountainsmetacontenttechnology-2001","role":"author","urls":{"Paper":"http://www.cs.kau.se/cs/prtp/papers/Digital01.pdf.gz"},"downloads":0},"search_terms":["quantum","leap","content","delivery","digital","fountain","meta","content","technology","fountain"],"keywords":[],"authorIDs":[],"dataSources":["6WGcSu2Ku7pZzqCcg"]}