Jump to content

High Efficiency Streaming Protocol

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by JonSul21 (talk | contribs) at 15:39, 4 July 2023 (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!). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
  • Comment: This submission has two issues: 1) it does not use any good third-party sources, which are required if this is to become an article; 2) as currently written, the prose does not address wikipedia's general reader. Remember to write in layman's terms and to avoid jargon where possible. Modussiccandi (talk) 08:42, 25 June 2023 (UTC)

High Efficiency Streaming Protocol (HESP)

High Efficiency Streaming Protocol (also known as HESP) is an HTTP-based adaptive bitrate streaming protocol that enables high-quality streaming of media content over the Internet delivered from conventional HTTP web servers.[1], just like HLS and DASH. The technology was developed by THEO Technologies and made available via the HESP Alliance, which has Synamedia and THEO Technologies as founding members.[2] HESP brings sub-second latency and a fast channel change, and is seen as a challenger of Low Latency HLS (LL-HLS, first released in 2009) and Low Latency DASH (LL-DASH, standardized in 2012).[3]

Architecture

HTTP-based streaming protocols such as HLS and DASH typically use a segment-based approach. This means a video is cut up into 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.[4]

When all components of the video workflow are optimized for low latency, HESP can provide for sub-second latency.[5]

HESP requires implementation in the packager and player, and support for range requests and Chunked transfer encoding (CTE) in the CDN.[6]

Standardization

Work on HESP started in 2018; it became an IETF information draft in May 2021[7].

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[8]

References

  1. ^ "What is the High Efficiency Streaming Protocol (HESP) and why does the video industry need it?". THEO Technologies. Retrieved 2023-07-04.
  2. ^ "THEO Technologies and Synamedia form HESP Alliance". Digital TV News. Retrieved 2023-07-04.
  3. ^ "Rethink report debunks low latency hype". CSI Magazine. Retrieved 2023-07-04.
  4. ^ "HESP: Sub-second Latency, Fast Channel Change and Improved ABR over Standard CDNs". Streaming Media. Retrieved 2023-07-04.
  5. ^ "HESP: What a HESP protocol is and how it changes streaming for the better". Gcore. Retrieved 2023-07-04.
  6. ^ "HESP - Informational Draft". IETF. Retrieved 2023-07-04.
  7. ^ "High Efficiency Streaming Protocol (HESP)". IABM. Retrieved 2023-07-04.
  8. ^ "HESP Alliance Members". HESP Alliance. Retrieved 2023-07-04.