Differences between revisions 16 and 17
Revision 16 as of 2009-03-25 15:34:08
Size: 2509
Comment:
Revision 17 as of 2010-10-05 14:19:56
Size: 4583
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
A DVB protocol published by ETSI used in IPTV / broadcast TV head-ends to enable use of multiple key management systems.
The standardised SCS (Simulcrypt Synchroniser) to ECMG (Entitlement Control Message Generator) interface is used to allow multiple key management systems to operate in parallel, each generating its own (typically proprietary) ECMs (Entitlement Control Messages).
A DVB protocol published by ETSI used in IPTV / broadcast TV head-ends to enable use of multiple key management systems.[[BR]]
The standardised SCS (Simulcrypt Synchroniser) to ECMG (Entitlement Control Message Generator) interface is used to allow multiple key management systems to operate in parallel, each generating its own (typically proprietary) ECMs (Entitlement Control Messages). [[BR]]
The EMMG (Entitlement Management Message Generator) to MUX interface allows the CAS (Conditional Access System), which provides the ECMs, to provide an EMM (Entitlement Management Message) to be associated to the streamed service. [[BR]]
The interface between EIS (Event Information Scheduler) and SCS is used by the EIS to provide Scrambling Control Group (SCG) definitions and Access Criteria (AC) transitions, to allow the management of different services sharing the same key.[[BR]]
The PSIG (Program Specific Information Generator) to MUX interface is used by the PSIG to provide MUXes of the head-end with the appropriate PSI/SI (Program Specific Information/Service Information) tables for their respective transport stream.[[BR]]
Line 13: Line 17:
 * [[TCP]]: For the SCS to ECMG, SIMULCRYPT uses [[TCP]] as its transport protocol. There is no well known TCP port for SIMULCRYPT traffic as multiple TCP connections are possible (typically each TCP connection is associated to a given key management system for a particular TV channel).  * SCS - ECMG: this interface uses [[TCP]] as its transport protocol. There is no well known TCP port for SIMULCRYPT traffic as multiple TCP connections are possible (typically each TCP connection is associated to a given key management system for a particular TV channel).
 * EMMG - MUX: the head-end operator can choose between:
 - [[TCP]] based implementation for data provision and control;

 - [[UDP]] based implementation for data provision and [[TCP]] based implementation for control;

 - [[UDP]] based implementation for data provision and [[SIMF]] based implementation for control.

 * EIS - SCS: this interface uses [[TCP]] as its transport protocol.
 * PSIG - MUX: this interface may include the PSI/SI table carouselling performed by the PSIG and the PSI/SI table carouselling performed by the MUX. In the first case, the real implementation can be chosen between:
 - [[TCP]] based implementation for data and control;

 - [[ASI]] based implementation for data and [[TCP]] based implementation for control.
Line 21: Line 38:
The SIMULCRYPT dissector is fully functional for the SCS - ECMG interface. It decodes the Simulcrypt syntax to analyse different Simulcrypt messages and associated TLV parameters. The SIMULCRYPT dissector is fully functional for the following interfaces: ECMG - SCS, EMMG - MUX, EIS - SCS, PSIG - MUX (supported also MUX - CiM and (P) - CiP interfaces).
It decodes the Simulcrypt syntax to analyse different Simulcrypt messages and associated TLV parameters.
Line 31: Line 49:
 * [[attachment:SampleCaptures/ECMG-SCS.pcap]] - Simulcrypt traffic on the ECMG - SCS interface over [[TCP]].
 * [[attachment:SampleCaptures/EMMG-MUX.pcap]] - Simulcrypt traffic on the EMMG - MUX interface over [[TCP]].
 * [[attachment:SampleCaptures/EIS-SCS.pcap]] - Simulcrypt traffic on the EIS - SCS interface over [[TCP]].
 * [[attachment:SampleCaptures/PSIG-MUX.pcap]] - Simulcrypt traffic on the PSIG - MUX interface (and the MUX - CiM interface) over [[TCP]].

Simulcrypt (SimulCrypt)

A DVB protocol published by ETSI used in IPTV / broadcast TV head-ends to enable use of multiple key management systems.BR The standardised SCS (Simulcrypt Synchroniser) to ECMG (Entitlement Control Message Generator) interface is used to allow multiple key management systems to operate in parallel, each generating its own (typically proprietary) ECMs (Entitlement Control Messages). BR The EMMG (Entitlement Management Message Generator) to MUX interface allows the CAS (Conditional Access System), which provides the ECMs, to provide an EMM (Entitlement Management Message) to be associated to the streamed service. BR The interface between EIS (Event Information Scheduler) and SCS is used by the EIS to provide Scrambling Control Group (SCG) definitions and Access Criteria (AC) transitions, to allow the management of different services sharing the same key.BR The PSIG (Program Specific Information Generator) to MUX interface is used by the PSIG to provide MUXes of the head-end with the appropriate PSI/SI (Program Specific Information/Service Information) tables for their respective transport stream.BR

History

XXX - add a brief description of PROTO history

Protocol dependencies

  • SCS - ECMG: this interface uses TCP as its transport protocol. There is no well known TCP port for SIMULCRYPT traffic as multiple TCP connections are possible (typically each TCP connection is associated to a given key management system for a particular TV channel).

  • EMMG - MUX: the head-end operator can choose between:

    - TCP based implementation for data provision and control;

    - UDP based implementation for data provision and TCP based implementation for control;

    - UDP based implementation for data provision and SIMF based implementation for control.

  • EIS - SCS: this interface uses TCP as its transport protocol.

  • PSIG - MUX: this interface may include the PSI/SI table carouselling performed by the PSIG and the PSI/SI table carouselling performed by the MUX. In the first case, the real implementation can be chosen between:

    - TCP based implementation for data and control;

    - ASI based implementation for data and TCP based implementation for control.

Example traffic

XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot).

Wireshark

The SIMULCRYPT dissector is fully functional for the following interfaces: ECMG - SCS, EMMG - MUX, EIS - SCS, PSIG - MUX (supported also MUX - CiM and (P) - CiP interfaces). It decodes the Simulcrypt syntax to analyse different Simulcrypt messages and associated TLV parameters.

Preference Settings

There are some SIMULCRYPT_Preferences.

Example capture file

Display Filter

A complete list of PROTO display filter fields can be found in the display filter reference

  • Show only the SIMULCRYPT based traffic:

     simulcrypt 

Capture Filter

You can directly filter SIMULCRYPT protocols while capturing if you know the TCP port used (see above).

  • Capture only the SIMULCRYPT traffic over the chosen port (<port>):

     tcp port <port> 

Discussion

SIMULCRYPT (last edited 2010-10-05 19:07:27 by GuyHarris)