Welcome to RedSquid

Welcome to the RedSquid platform ecosystem. This guide will help you integrate RedSquid into your television hardware, enabling your devices to support operator-branded applications while providing robust system-level functionality.

What is RedSquid?

RedSquid is an operator application launch framework for television platforms that enables seamless coexistence between operator-branded applications and essential system-level functionality.

Key Benefits for OEMs

• Operator-Ready Platform: Ship TVs that operators can brand without custom development
• Reduced Development Cost: RedSquid handles system-level functions (volume, input, settings, FTI)
• Multi-Operator Support: Single hardware SKU supports up to 3 different operator configurations
• Standardized Platform: Built on RDK (Reference Design Kit) with proven industry standards
• Flexible Deployment: Support both operator-specific and retail configurations

Platform Architecture

System Components

┌─────────────────────────────────────────────────────┐
│                 RedSquid Platform                    │
├─────────────────────────────────────────────────────┤
│  ┌─────────────────────────────────────────────┐   │
│  │         RedSquid System Application          │   │
│  │  • Volume Control  • Input Selection         │   │
│  │  • Settings UI     • FTI Workflows           │   │
│  │  • DTVKit (Live TV)                          │   │
│  └─────────────────────────────────────────────┘   │
│                       ▲                             │
│                       │ System Keys                 │
│  ┌─────────────────────────────────────────────┐   │
│  │    System-Level Key Interception Layer      │   │
│  │  (Routes Volume, Input, Settings to RedSquid)│   │
│  └─────────────────────────────────────────────┘   │
│                       │                             │
│                       ▼ Other Keys                  │
│  ┌─────────────────────────────────────────────┐   │
│  │         Operator Application                 │   │
│  │  • Branded UI  • Content Navigation          │   │
│  │  • EPG         • OTT Integration             │   │
│  └─────────────────────────────────────────────┘   │
│                                                     │
├─────────────────────────────────────────────────────┤
│              WPE Browser / Thunder API              │
├─────────────────────────────────────────────────────┤
│         RDK Platform / Linux Kernel                 │
├─────────────────────────────────────────────────────┤
│              Hardware Platform (SoC)                │
└─────────────────────────────────────────────────────┘

Technology Stack

Hardware Requirements

Minimum Platform Specifications

Required Hardware Components

1. Network Connectivity

• Ethernet: 10/100 Mbps port (mandatory)
• Wi-Fi: 802.11 b/g/n (2.4 GHz minimum), 802.11ac (5 GHz recommended)
• Bluetooth: Optional, for remote pairing

2. Broadcast Tuners

• DVB-T/T2: Terrestrial tuner (EU/UK markets)
• DVB-S/S2: Satellite tuner (optional, market-dependent)
• DVB-C: Cable tuner (optional, market-dependent)
• DVB-I: IP-delivered service discovery (recommended for hybrid line-ups)
• ATSC 3.0 (NextGen TV): Mandatory for North American SKUs

3. Content Protection

• HDCP 1.4: Mandatory for HDMI outputs
• HDCP 2.2: Required for 4K content
• DRM Support: Widevine Level 1 or PlayReady SL3000

4. Audio Support

• Dolby Digital Plus: Required for premium audio
• Dolby Atmos: Recommended for 4K/HDR content
• AAC/HE-AAC: Standard audio codec support
• Audio Pass-through: HDMI audio output support

5. Input/Output

• HDMI Inputs: Minimum 2x HDMI 2.0 ports
• HDMI Output: Pass-through for external audio (optional)
• USB Ports: Minimum 1x USB 2.0 for FTI configuration loading
• Audio Output: Optical/SPDIF for Dolby pass-through (recommended)

Integration Overview

Integration Timeline

Prerequisites

Before beginning integration, ensure you have:

• RDK-compatible SoC with necessary drivers
• RDK development environment set up
• Access to RedSquid SDK and documentation portal
• DVB tuner drivers and DTVKit license (if supporting Live TV)
• DRM credentials (Widevine/PlayReady) for your device models
• HDCP key pool allocation
• Network access for backend service connectivity

Manufacturing & Provisioning

Personality Package System

Each RedSquid device requires a unique Personality Package containing security credentials and device identity. This package is generated during manufacturing and flashed to the device.

Personality Package Contents

API Integration

Request Format:

curl -X POST https://api.redsquid.tv/v1/personality/generate \
  -H "Authorization: Bearer {YOUR_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "batch_type": "production",
    "batch_id": "2024-Q1-001",
    "quantity": 1000,
    "security_profile": "standard_hdcp22_widevine",
    "operator_config": "operator_a_uk"
  }'

System Integration

Dolby Audio Integration

Dolby audio support is a critical component for premium content delivery. The OEM is responsible for obtaining, integrating, and managing Dolby libraries.

OEM Responsibilities

Dolby Library Integration

The OEM receives a signed Dolby library from Dolby Laboratories containing a unique Dolby ID specific to your device manufacturer registration.

Integration Process

1. Register with Dolby Laboratories
   • Complete manufacturer registration
   • Execute licensing agreement
   • Receive unique Dolby ID
2. Obtain Signed Libraries
   • Dolby Digital Plus decoder library (libddplus.so)
   • Dolby Atmos decoder library (libdlbatmos.so) - if supporting Atmos
   • Libraries are cryptographically signed with your Dolby ID
3. Integrate with RDK Audio Pipeline
   • Place libraries in system library path (/usr/lib or /lib)
   • Configure RDK GStreamer pipeline to use Dolby decoders
   • Set up audio routing for HDMI and optical outputs
4. Configure Audio Capabilities
   • Declare Dolby codec support in device capabilities
   • Configure EDID for Dolby audio formats
   • Enable pass-through for external audio devices
5. Testing & Certification
   • Complete Dolby certification testing
   • Verify Dolby Digital Plus playback
   • Test Dolby Atmos (if supported)
   • Validate audio pass-through scenarios

Library Deployment

# Typical library locations on device
/usr/lib/libddplus.so          # Dolby Digital Plus decoder
/usr/lib/libdlbatmos.so        # Dolby Atmos decoder (optional)
/etc/dolby/dolby.conf          # Dolby configuration

# Libraries must be:
# - Signed with your unique Dolby ID
# - Read-only and protected from modification
# - Included in system partition
# - Not user-accessible

RedSquid Integration Points

Licensing Costs

OEMs should budget for Dolby licensing fees:

• Per-Device Licensing: Dolby charges per manufactured unit
• Annual Reporting: Device shipment quantities must be reported to Dolby
• Certification Costs: Initial certification testing fees apply
• Ongoing Compliance: Periodic recertification may be required for major updates

Key Interception Integration

RedSquid requires system-level interception of specific remote control keys. This must be implemented at the input driver or RDK layer.

Required Key Routing

Testing & Validation

Functional Testing Checklist

Boot & Initialization

• Cold boot completes in < 15 seconds
• Boot splash screen displays correctly
• Network connectivity established (Ethernet/Wi-Fi)
• Personality package loads successfully
• Device registers with backend

First-Time Installation (FTI)

• USB configuration detection works
• Network setup flow (Ethernet/Wi-Fi) completes
• DVB-T/T2 scanning finds channels
• DVB-S/S2 scanning works (if satellite tuner present)
• Operator app loads after FTI completion
• Theme colors apply correctly

System Keys

• Volume +/- displays overlay and adjusts audio
• Mute key toggles audio mute
• Input key shows source selection UI
• Settings key opens RedSquid settings
• Power key triggers standby/wake

Performance Benchmarks

• Boot time: < 15 seconds
• App launch time: < 3 seconds
• Channel change time: < 2 seconds
• Settings overlay: < 300ms
• Network UI loading: < 500ms

Backend Services

Required Backend Connectivity

Support & Resources

Documentation Portal

Developer Support

Technical Support Channels:

• Email: oem-support@redsquid.tv
• Developer Forum: https://forum.redsquid.tv
• Slack Channel: #redsquid-oem-integration (invite-only)

Support Tiers:

• Tier 1 - Community: Forum support, 48-hour response time
• Tier 2 - Standard: Email support, 24-hour response time
• Tier 3 - Premium: Dedicated Slack channel, 4-hour response time, on-call support

Certification Program

Complete the RedSquid OEM Certification to validate your integration:

1. Complete integration checklist
2. Submit test device for validation
3. Pass compliance testing
4. Receive certification badge

Contact Information

RedSquid Technologies Ltd.

• Website: https://www.redsquid.tv
• Email: info@redsquid.tv
• OEM Partnerships: partnerships@redsquid.tv