Deployment Architecture

zixi protected multicast deployments includes the following zixi components origin – the origin of the stream can be either a zec, a file playing locally, or any device streaming remotely or locally in any of the following formats zixi protected transport (pull/push) mpeg ts over udp and/or rtp with smpte 2022 (unicast/multicast) file transport stream files from local file system rtmp pull from cdns and/or other sources rtmp push rtmps rtsp input hls ts over http rist contribution/distribution – in the contribution/distribution segment there is a zixi broadcaster component that streams a zixi protected transport stream to a multicast supported network consumption – in the consumption segment there are a variety of devices that can receive and playback a multicast zixi protected stream, including mobile device running a zixi player mobile device running a customer application with zixi proxy embedded pc running vlc with zixi embedded pc/server running zec as a receiver the endpoints/receivers/zec connect to the zixi broadcaster to pull an input stream the zixi broadcaster redirects them to a multicast address if the multicast connection does not succeed and the input stream has not been marked as “ multicast only ”, the entire transmission of the stream will fall back to unicast however, enabling the multicast only flag will prevent the fallback to unicast if the multicast connection is successful, but there are errors in the transmission, the error correction will be transmitted in udp unicast directly to the specific device that suffered the error