The Experts below are selected from a list of 24735 Experts worldwide ranked by ideXlab platform
R. Kermode - One of the best experts on this subject based on the ideXlab platform.
-
SIGCOMM - Scoped hybrid automatic repeat reQuest with Forward Error Correction (SHARQFEC)
Proceedings of the ACM SIGCOMM '98 conference on Applications technologies architectures and protocols for computer communication - SIGCOMM '98, 1998Co-Authors: R. KermodeAbstract:Reliable multicast protocols scale only as well as their ability to localize traffic. This is true for repair requests, repairs, and the session traffic that enables receivers to suppress extraneous requests and repairs. We propose a new reliable multicast traffic localization technique called Scoped Hybrid Automatic Repeat reQuest with Forward Error Correction (SHARQFEC). SHARQFEC operates in an end-to-end fashion and localizes traffic using a hierarchy of administratively scoped regions. Session traffic is further reduced through the use of a novel method for indirectly determining the distances between session members. For large sessions, this mechanism reduces the amount of session traffic by several orders of magnitude over non-scoped protocols such as Scalable Reliable Multicast (SRM). Forward Error Correction is selectively added to regions which are experiencing greater loss, thereby reducing the volume of repair traffic and recovery times. Receivers request additional repairs as necessary. Simulations show that SHARQFEC out performs both SRM and non-scoped hybrid Automatic Repeat reQuest / Forward Error Correction protocols. Assuming the widespread deployment of administrative scoping, SHARQFEC could conceivably provide scalable reliable delivery to tens of millions of receivers without huge increases in network bandwidth.
-
scoped hybrid automatic repeat request with Forward Error Correction sharqfec
ACM Special Interest Group on Data Communication, 1998Co-Authors: R. KermodeAbstract:Reliable multicast protocols scale only as well as their ability to localize traffic. This is true for repair requests, repairs, and the session traffic that enables receivers to suppress extraneous requests and repairs. We propose a new reliable multicast traffic localization technique called Scoped Hybrid Automatic Repeat reQuest with Forward Error Correction (SHARQFEC). SHARQFEC operates in an end-to-end fashion and localizes traffic using a hierarchy of administratively scoped regions. Session traffic is further reduced through the use of a novel method for indirectly determining the distances between session members. For large sessions, this mechanism reduces the amount of session traffic by several orders of magnitude over non-scoped protocols such as Scalable Reliable Multicast (SRM). Forward Error Correction is selectively added to regions which are experiencing greater loss, thereby reducing the volume of repair traffic and recovery times. Receivers request additional repairs as necessary. Simulations show that SHARQFEC out performs both SRM and non-scoped hybrid Automatic Repeat reQuest / Forward Error Correction protocols. Assuming the widespread deployment of administrative scoping, SHARQFEC could conceivably provide scalable reliable delivery to tens of millions of receivers without huge increases in network bandwidth.
Ali C. Begen - One of the best experts on this subject based on the ideXlab platform.
-
Session Description Protocol Elements for the Forward Error Correction (FEC) Framework
2011Co-Authors: Ali C. BegenAbstract:This document specifies the use of Session Description Protocol (SDP) to describe the parameters required to signal the Forward Error Correction (FEC) Framework Configuration Information between the sender(s) and receiver(s). This document also provides the semantics for grouping multiple source and repair flows together for the applications that simultaneously use multiple instances of the FEC Framework.
-
Forward Error Correction Grouping Semantics in Session Description Protocol
2006Co-Authors: Ali C. BegenAbstract:This document defines the semantics that allow for grouping of Forward Error Correction (FEC) streams with the protected payload streams in Session Description Protocol (SDP). The semantics defined in this document are to be used with "Grouping of Media Lines in the Session Description Protocol" (RFC 3388) to group together "m" lines in the same session. [STANDARDS-TRACK]
Mark Watson - One of the best experts on this subject based on the ideXlab platform.
-
RTP Payload Format for Raptor Forward Error Correction (FEC)
2012Co-Authors: Thomas Stockhammer, Mark WatsonAbstract:This document specifies an RTP payload format for the Forward Error Correction (FEC) repair data produced by the Raptor FEC Schemes. Raptor FEC Schemes are specified for use with the IETF FEC Framework that supports the transport of repair data over both UDP and RTP. This document specifies the payload format that is required for the use of RTP to carry Raptor repair flows. [STANDARDS-TRACK]
-
Forward Error Correction (FEC) Framework
2011Co-Authors: Mark WatsonAbstract:This document describes for a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks to provide protection against packet loss. The framework supports applying Forward Error Correction to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media. This framework can be used to define Content Delivery Protocols that provide Forward Error Correction for streaming media delivery or other packet flows. Content Delivery Protocols defined using this framework can support any FEC Scheme (and associated FEC codes) which is compliant with various requirements defined in this document. Thus, Content Delivery Protocols can be defined which are not specific to a particular FEC Scheme and FEC Schemes can be defined which are not specific to a particular Content Delivery Protocol.
-
Raptor Forward Error Correction Scheme for Object Delivery
2007Co-Authors: Michael Luby, Mark Watson, Amin Shokrollahi, Thomas StockhammerAbstract:This document describes a Fully-Specified Forward Error Correction (FEC) scheme, corresponding to FEC Encoding ID 1, for the Raptor Forward Error Correction code and its application to reliable delivery of data objects. Raptor is a fountain code, i.e., as many encoding symbols as needed can be generated by the encoder on-the-fly from the source symbols of a source block of data. The decoder is able to recover the source block from any set of encoding symbols only slightly more in number than the number of source symbols. The Raptor code described here is a systematic code, meaning that all the source symbols are among the encoding symbols that can be generated. [STANDARDS-TRACK]
Thomas Stockhammer - One of the best experts on this subject based on the ideXlab platform.
-
Forward Error Correction for WebRTC using FEC FRAME
2013Co-Authors: Christian Foisy, Michael Luby, Giridhar D. Mandyam, Thomas StockhammerAbstract:WebRTC provides a solution for peer-to-peer streaming between web applications by leveraging a Real-Time Protocol (RTP) stream between two clients. This RTP stream is expected to be sent over an UDP (Universal Datagram Protocol) connection, which by definition has no built-in reliability. Recently the FEC FRAME Working Group of the IETF has come up with a framework and technical recommendations for applying Forward Error Correction (FEC) to unreliable streams. This framework can be applied to WebRTC with minimal changes to the specification.
-
RTP Payload Format for Raptor Forward Error Correction (FEC)
2012Co-Authors: Thomas Stockhammer, Mark WatsonAbstract:This document specifies an RTP payload format for the Forward Error Correction (FEC) repair data produced by the Raptor FEC Schemes. Raptor FEC Schemes are specified for use with the IETF FEC Framework that supports the transport of repair data over both UDP and RTP. This document specifies the payload format that is required for the use of RTP to carry Raptor repair flows. [STANDARDS-TRACK]
-
Raptor Forward Error Correction Scheme for Object Delivery
2007Co-Authors: Michael Luby, Mark Watson, Amin Shokrollahi, Thomas StockhammerAbstract:This document describes a Fully-Specified Forward Error Correction (FEC) scheme, corresponding to FEC Encoding ID 1, for the Raptor Forward Error Correction code and its application to reliable delivery of data objects. Raptor is a fountain code, i.e., as many encoding symbols as needed can be generated by the encoder on-the-fly from the source symbols of a source block of data. The decoder is able to recover the source block from any set of encoding symbols only slightly more in number than the number of source symbols. The Raptor code described here is a systematic code, meaning that all the source symbols are among the encoding symbols that can be generated. [STANDARDS-TRACK]
Alan H. Gnauck - One of the best experts on this subject based on the ideXlab platform.
-
Increased OSNR gains of Forward-Error Correction in nonlinear optical transmissions
IEEE Photonics Technology Letters, 2003Co-Authors: S. Chandrasekhar, Alan H. GnauckAbstract:We study numerically and experimentally the optical signal-to-noise ratio margin of high-speed transmissions in the nonlinear regime. It is found that the actual Forward-Error Correction coding gains can be much larger than those quoted in the ideal linear case.