DLNA and DTCP-IP protocol stacks

And your TV device securely integrates within the home network!

Leveraging the rapid deployment of Ethernet, Wi-Fi, power line communication, and coax within households, the adoption rate of IP connectivity within Consumer Electronics devices is booming. The key issue of interoperability has been efficiently addressed by DLNA on the basis of UPnP. The DLNA consortium has reached a consensus: as of December 2011, more than 13 000 devices have received DLNA certification which translates into half a billion devices into consumers’ homes. To enhance the proposition and allow for the exchange of premium video content between DLNA devices within a multimedia home network, DLNA has specified a range of Commercial Video Profiles (CVP) based on Digital Transmission Content Protection-Internet Protocol (DTCP-IP).

A member of both DLNA and DTLA, iWedia has developed a full range of DLNA (controller, renderer, player and server) and DTCP-IP (source and sink) protocol stacks. CVP implementations are available as well.

Key features

  • DLNA protocol stack compliant with DLNA Interoperability Guidelines 1.5 supporting Digital Media Server (DMS), Player (DMP), Renderer (DMR), and Controller (DMC) device classes. All supported DLNA device classes are certified
  • Based on customized UPnP open source software (libupnp). UPnP software stack is compliant with UPnP AV Specification v1.0 and certified
  • Ported on Linux and Android OS
  • Supports Commercial Video Profiles (CVP) for the exchange of premium video contents within the home network containing:
    • DTCP-IP source/sink compliant with DTCP Volume 1 Supplement E Mapping DTCP to IP rev 1.4
    • RUI client/server based on CE-HTML (CEA-2014-B)
    • Live TV extensions
  • Supports variety of media containers (avi/divx, mp4, mov, MPEG2 TS/PS, Avchd, Matroska, flv, ogg) and media formats (also depending on the target hardware)

Arhitecture overview



  • DLNA/DTCP-IP protocol stacks generated as libraries on Customer environment (delivery of source code is an option)
  • Middleware-level API (File browsing and media playback abstraction): APIs documentation, reference implementation (in ANSI C source code)
  • Service-level API (or AAL – Application Abstraction Layer): APIs documentation
  • Integration guidelines
  • Test application (command line application in ANSI C source code or Web interface for DMS)
  • Reference system demonstrating DLNA features (reference application running on reference platform)
  • The DLNA protocol stacks successfully pass the DLNA CTT and are ready for certification

Platform requirements

  • The solution is chipset agnostic and available for Linux and Android OS; it is easily portable on a new platform thanks to the clearly defined APIs to middleware and application
  • Size of the code and static data for complete DLNA stack including UPnP and SQLite: 1.1 MB (may slightly vary depending on target platform)
  • Dynamic allocations for DMS device and 400 shared files:
    • Peak of 4 MB for one active connection
    • Peak of 5 MB for two active connections
  • Hardware descrambling capabilities for DTCP-IP: AES-128
  • Processing power: 800 DMIPS