Explore chapters and articles related to this topic
Alternate Television Delivery Systems
Published in Skip Pizzi, Graham A. Jones, A Broadcast Engineering Tutorial for Non-Engineers, 2014
Another technology that attempts to address this issue is adaptive streaming, by which video content can be encoded at several bit rates and presented for streaming as a single offering. The viewing device automatically selects the highest quality version that current network conditions will allow. In its latest incarnation at this writing, dynamic adaptive streaming performs such encoding of a program by breaking it into many smaller files and encoding each segment at the various bit rates. The program is presented to the viewer as a kind of progressive download, with the viewing device continually monitoring current network conditions and deciding as the end of each segment approaches whether to stay at the current encoding level, or to up- or down-shift to a different encoding level, based on whether the device estimates that the next segment will download in time to be viewed without interruption given the connection's current status. A number of companies have developed proprietary methods of providing this capability, and a standard has been developed by MPEG called Dynamic Adaptive Streaming over HTTP (DASH), often referred to simply as MPEG-DASH.
Information-Centric Networking Future Internet Video Delivery
Published in M. Bala Krishna, User-Centric and Information-Centric Networking and Services, 2019
Jordi Ortiz, Pedro Martinez-Julia, Antonio Skarmeta
As introduced above, DASH is the acronym for Dynamic Adaptive Streaming over HTTP. DASH [40] relies on the HTTP client server model in addition to eXtensible Markup Language(XML) to provide on top of the Internet efficient and high-quality media delivery. XML is employed to expose the metadata needed to describe technically and index the media to be streamed so that it can be deployed on standard HTTP servers and accesses like any other web page. The complexity on the streaming process is delegated to the client which is in charge of parse the metadata file and download the corresponding media data.
Digital TV Architecture Standardization
Published in Hassnaa Moustafa, Sherali Zeadally, Media Networks: Architectures, Applications, and Standards, 2016
PSS allows for conventional streaming to be used, that is, the session control protocol used between the PSS client and PSS server is RTSP while the transport protocol is RTP, cf. [ETSI TS 126 234] for further details. In addition, Progressive download over HTTP as well as Dynamic Adaptive Streaming over HTTP (DASH) can be used as alternatives methods to conventional streaming [ETSI TS 126 247].
Efficient video transmission—a critical review of various protocols and strategies
Published in Journal of the Chinese Institute of Engineers, 2021
Ali Siddique, Abdul Rauf Bhatti, Ahmed Bilal Awan, Arslan Dawood Butt, Ali S. Alghamdi, Muhammad Farhan, Nadia Rasheed
As can be seen from Table 1, except congestion-control, TCP fulfills none of the above-mentioned requirements. Therefore, TCP is not suitable for video transport, especially in the case of 3D videos. Interestingly, it is still being used for progressive downloading. This is because in progressive downloading, the delay constraints are not very tight and hence, TCP can be used with no problem. While in the past, most video streaming technologies utilized streaming protocols such as real-time protocol (RTP, see [Schulzrinne et al. 2003]) with a real-time streaming protocol (RTSP, see [Schulzrinne, Rao,and, and Lanphier 1998]). Today’s adaptive streaming technologies are almost exclusively based on hypertext transport protocol (HTTP) and designed to work efficiently over large distributed HTTP networks such as the Internet (Fielding et al. 1999). Popular video-sharing websites such as Metacafe and the Vimeo use HTTP over TCP for video streaming (Gurler et al. 2011). YouTube has used MPEG-DASH (Schierl et al. 2012) in the past but now it uses Adobe dynamic streaming for flash (ADSF). DASH, which stands for dynamic adaptive streaming over HTTP uses TCP as the transport- layer protocol (Sodagar 2011; Stockhammer 2011; Lederer, Muller, and Timmerer 2012). The MPEG-DASH aims to optimize bitrate and quality for the available network. Moreover, it has been shown in Gurler et al. (2011) that TCP performs well when the available network bandwidth is about twice the maximum video rate, with a few seconds of pre-roll delays. Nevertheless, the TCP is not at all suitable for real-time video streaming because the delay incurred by TCP is very large. Furthermore, the rapidly changing transmission rate exhibited by TCP is not acceptable in real-time streaming Wenger (2003).