Project

General

Profile

Feature #4750

Feature #4477: Hardware CI Digital Devices DDCI2

DDCI2 - implement multi-transport-stream-decoding (MTD)

Added by Jaroslav Kysela about 7 years ago. Updated almost 4 years ago.

Status:
Accepted
Priority:
Normal
Assignee:
Jaroslav Kysela
Category:
Descrambling
Target version:
4.6
Start date:
2017-11-29
Due date:
% Done:

0%

Estimated time:

Description

DDCI2 (and maybe other / future CAMs) supports the decoding for multiple services on different transport streams.

MTD descrambling is a bit 'abuse' of the standard CAM mechanism. It requires PID remapping, proper CAT PID mangling and SID mangling.

The VDR has more-or-less complete implementation:

https://projects.vdr-developer.org/git/vdr.git/tree/mtd.h
  https://projects.vdr-developer.org/git/vdr.git/tree/mtd.c

The ETSI TS 103 205 specification allows multi-stream decoding using the local-TS identifiers (no PID remapping, the 0x47 sync byte is replaced with the local-TS identifier).

ETSI TS 103 205: http://www.etsi.org/deliver/etsi_ts/103200_103299/103205/01.01.01_60/ts_103205v010101p.pdf

The implementation should be separated from the actual tvh's caclient (shared code).

History

#1

Updated by Jaroslav Kysela about 7 years ago

To be more precise: DDCI2 is just a bridge for CAMs. The CAM must support the multi-stream decoding and appearently there are two standards MTD/MCD (multiple transport decoding/multiple channel decoding) and the official one defined in CI plus (ETSI TS 103 205) which uses local-TS identifiers.

#2

Updated by Flole Systems almost 4 years ago

  • Target version changed from 4.4 to 4.6

Also available in: Atom PDF