Content deleted Content added
Hi Modussiccandi, many thanks for your feedback. I've reworded some sections to make them more accessible for the broader public. Extra references have also been added. Hope this addresses your feedback - please let me know if you feel other updates should be made before the article can be published, and I'd then be happy to look into these! |
Minor fixes, including phrase change (just like > such as) and deletion and addition of periods. |
||
(9 intermediate revisions by 7 users not shown) | |||
Line 1:
{{Short description|Video streaming protocol}}
{{Technical|date=November 2023}}
== High Efficiency Streaming Protocol (HESP) ==
'''High Efficiency Streaming Protocol''' (also known as '''HESP''') is an [[Hypertext Transfer Protocol|HTTP]]-based [[adaptive bitrate streaming]] protocol that enables high-quality [[Streaming media|streaming]] of media content over the Internet delivered from conventional [[Hypertext Transfer Protocol|HTTP]] web servers
== Architecture ==
HTTP-based streaming protocols such as HLS and DASH typically use a segment-based approach. This means a video is cut up into [[Transmission Control Protocol|TCP]] segments of a few seconds each, which requires video players to wait until the start of a new segment to start playback. This approach increases channel change times and introduces additional latency. HESP leverages a frame-based streaming approach, which does not require a trade-off between live latency and channel switching time.<ref>{{Cite web |title=HESP: Sub-second Latency, Fast Channel Change and Improved ABR over Standard CDNs |url=https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=153579 |access-date=2023-07-04 |website=Streaming Media | date=22 June 2022 |language=en-us}}</ref>
When all components of the video workflow are optimized for low latency, HESP can provide for sub-second latency.<ref>{{Cite web |title=HESP: What a HESP protocol is and how it changes streaming for the better |url=https://gcore.com/learning/what-a-hesp-protocol-is-and-how-it-changes-streaming-for-the-better/ |access-date=2023-07-04 |website=Gcore |language=en-us}}</ref>
HESP requires implementation in the packager and player, and support for [[byte serving|range requests]] and [[Chunked transfer encoding]] (CTE) in the [[Content delivery network|CDN]].<ref>{{Cite web |title=HESP - Informational Draft |url=https://datatracker.ietf.org/doc/draft-theo-hesp/ |access-date=2023-07-04 |website=IETF |language=en-us}}</ref>
== Standardization ==
Work on HESP started in 2018; it became an IETF information draft in May 2021<ref>{{Cite web |title=High Efficiency Streaming Protocol (HESP) |url=https://theiabm.org/bamproducts/high-efficiency-streaming-protocol-hesp/ |access-date=2023-07-04 |website=IABM |language=en-US}}</ref>
The HESP Alliance, launched in 2020, promotes and catalyzes the adoption of HESP. It consists of streaming vendors and media companies, including [[Synamedia]], THEO Technologies, G-Core, EZDRM, Mainstreaming, NativeWaves, and Hoki. The HESP Alliance technical working group is focused on further advancing the HESP standard.<ref>{{Cite web |title=HESP Alliance Members |url=https://www.hespalliance.org/members |access-date=2023-07-04 |website=HESP Alliance |language=en-US}}</ref>
== References ==
<references />
[[Category:Hypertext Transfer Protocol]]
[[Category:Network protocols]]
[[Category:Streaming media systems]]
|