RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Refer Client Fail-Over Behavior to know how clients should behave using the linear redundancy features of the CDN.
http 4xx (and 502 Bad Gateway) are considered fatal errors for a given download attempt. No retry of the same URL will be performed. For other 5xx failures, single retry will be attempted after configurable delay (default 1s).
AAMP Video Engine Timeouts for fragment, manifest, and license requests are all configurable - defaults as follows:
FOG is a separate service involved with Client-Side IP Linear Time Shift Buffer (TSB) support, caching fragments and generating virtual playlists that grow and eventually cull. As such, it shares many of the same responsibilities and behaviors as AAMP running in AAMP-only playback scenarios. FOG configuration includes:
waitTimeBeforeRetryHttp5xxMS - 1s
downloadTimeoutMS - 5s
expirationTimeMS - 30s
minFragmentDownloadDelayMS - 10ms; behind ENABLE_ABR_TESTING for randomized simulated download latency
maxFragmentDownloadDelayMS - 100ms; behind ENABLE_ABR_TESTING for randomized simulated download latency
tsbPreemptiveDownloadDelay - 5
vfsContextDumpDuration - 10000 - periodic virtual file system state logging
bitrateCheating - false
maxConcurrentDownloads - 1
sleepFraction - 1.5
manifestUpdate - 60s
defaultFetchTimeout - 60s
writeFailThreshold - 3 (write failure threshold before disabling TSB)
bitrateInit - initial bitrate while tuning normal content
bitrateInit4K - initial bitrate while tuning 4k content
fragmentFailThreshold - 5
cullLength - 1500 / 3600 (25 minutes or 1 hour)