Technical Specifications Key features Fast channel change time: 0.2-0.5 sec on Broadcom platform1 Key-frame indexing Smooth transition from TCP unicast to DVB-C Supported stream encodings: MPEG2, MPEG4 AVC/H.264, HEVC/H.265 Compatible with Verimatrix scrambled streams (and other scrambling systems that preserve key-frame identification patterns) Easy integration. Software library on the client side. Monitoring and statistics Redundancy support Protocols Channel reception using DVB-C on STB side and UDP Multicast streams on server side. MPEG2 TS (Transport Stream) TCP connection is used between the server and client to retrieve initial burst data Scrambling Compatible with Verimatrix encrypted streams Compatible with scrambling systems that preserve key-frame identification patterns in Transport Stream Redundancy Failover support. When the primary FCC server is not available, client will automatically switch to the secondary FCC server. Smooth transition After the initial burst, client will switch to the DVB-C stream at the exact transition point in Transport Stream to ensure smooth transition. Transition time from TCP unicast to DVB-C is about 5 seconds2 [Type here] www.qarva.com Integration Software library based integration (statically linked library for different platforms) Management Web GUI configuration utility with DB support. Command line tool to detect and configure channel parameters automatically Comprehensive log file output Comprehensive monitoring and statistics support System requirements Operating System: Linux (RHEL/CentOS recommended) 20MB RAM per channel 1MB RAM per client NIC's must provide enough network throughput to handle simultaneous channel changes. Each channel change requires about 2MB of data burst. Performance 100 Gbps per server (total TCP traffic for initial burst) 3 Up to 300 000 concurrent clients per server4 Up to 2000 channels per server5 1. Actual channel change time depends on stream bitrate and encoding options, video decoder settings of the player application, and network bandwidth. 2. Exact transition time depends on multiple factors: network bandwidth between the client and server, stream bitrate, DVB-C tune time. 3. Performance test has been done on Intel Xeon based server with 2x CPU, 18 physical cores per CPU, 36 physical cores total (72 hyper-threading cores) 4. Exact count of maximum concurrent clients depends on available RAM and CPU performance. 5. Channel count is limited by available RAM and CPU performance.