Summary
This diagram illustrates the system architecture and communication model used by the Swank Cached License Server within a customer environment. The Cached License Server is deployed within the customer’s network and acts as a localized intermediary for DRM license requests.
Content
Encrypted video content is provided by Swank via USB Drive or Network Download. Content is protected using DRM and remains encrypted in transit at all times. Content orders will include:
- Encrypted video files (CMAF/CENC)
- A manifest file with paths to all content
- Publicity assets (poster art, synopsis, metadata in multiple languages)
Content Management System (CMS)
Content is delivered to client devices either directly from a Swank streaming server or from an approved third-party content server. The CMS host HTTP server must support byte‑range requests (HTTP Range headers).
This capability allows client devices to request and retrieve specific portions of media files rather than requiring the entire file to be transferred in a single request.
Client Devices
Client devices communicate with the Cached License Server over secure HTTPS connections to obtain DRM licenses required for playback. Where valid licenses are already cached locally, playback authorization can occur without requiring immediate upstream access.
Network Connectivity
The Cached License Server connects to Swank licensing services over HTTPS to request and refresh DRM licenses as needed, without requiring a constant connection. It also securely connects to Swank for activation, support, and updates. Periodic internet access is needed for:
- One-time initial activation
- Regular license synchronization
- Monthly device certificate updates from Google (recommended)
- Software updates
Technical requirements and installation details can be found here: Swank Cached License Server V2 - Download/Install Instructions
Comments
0 comments
Please sign in to leave a comment.