Understanding Transport Streams and IP Delivery Protocols
8 min
overview modern broadcast and streaming workflows rely on mpeg transport streams (ts) for reliable delivery of video, audio, and metadata across diverse networks this document explains how video and audio are encoded into transport streams how receivers extract and decode these streams how ip delivery protocols (srt, rist, zixi) ensure resilience and quality here's a basic architectural diagram of the encoding decoding flow we will look at a more complete diagram after looking at some of the details of the process encoding pipeline step by step process compression video h 264/avc, hevc (h 265), or mpeg 2 audio aac, ac 3 packetization compressed streams become elementary streams (es) es wrapped into packetized elementary streams (pes) with timing info ( {{pts}} / {{dts}} ) transport stream packetization pes split into 188 byte ts packets each packet includes sync byte (0x47) for alignment {{pid}} (packet identifier) for stream identification optional adaptation field for timing ( {{pcr}} \[program clock reference]) multiplexing video, audio, and metadata interleaved into one ts {{pat}} / {{pmt}} tables describe program structure metadata & signaling scte 35 markers for ad insertion timing references (pts/dts, pcr) for synchronization decoding pipeline demultiplexing receiver uses pat/pmt to identify pids depacketization ts packets → pes → es decoding video/audio are decoded using original codecs rendering frames and audio are synchronized for playback ip delivery protocols why ip delivery? traditional satellite/cable links are being augmented or replaced by ip based transport for flexibility and cost efficiency however, ip introduces packet loss, jitter, and latency challenges protocols zixi protocol {{arq}} (automatic repeat request) for packet recovery {{fec}} (forward error correction) for proactive error handling bonding across multiple paths for resilience aes 256 encryption and {{dtls}} security integrated orchestration via zen master srt (secure reliable transport) arq based recovery aes encryption designed for low latency contribution feeds rist (reliable internet stream transport) standards based arq with optional fec ideal for broadcast grade reliability error correction layers arq retransmits lost packets based on nacks fec (forward error correction) adds redundant data for recovery without retransmission bonding distributes traffic across multiple links for hitless failover jitter buffers smooth out packet arrival variations timing & signaling pts/dts presentation and decoding timestamps pcr program clock reference for sync scte 35 ad signaling for dynamic ad insertion end to end architecture source → contribution → core → distribution → affiliate transport stream encapsulated in ip packets delivered via srt, rist, or zixi with error correction monitored via zen master for sla compliance diagram here is a more complete diagram key benefits zixi provides reliability >99 999% uptime with bonding and error correction security aes 256 encryption and dtls flexibility multi protocol support for diverse workflows visibility real time telemetry and analytics via zen master related topics docid\ jdvs1l zsejbtnf2okav9 docid 9 olo1argk 2adoshyfbb
