This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 2 and 18 (spanning 16 versions)
Revision 2 as of 2008-10-22 11:29:33
Size: 2150
Comment:
Revision 18 as of 2010-10-05 19:07:27
Size: 4559
Editor: GuyHarris
Comment: [[BR]] doesn't do what I suspect you think it does.
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
= Simulcrypt (Simulcrypt) = = Simulcrypt (SimulCrypt) =
Line 5: Line 5:

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).

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.

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.

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.
Line 12: Line 21:
 * [[TCP]]: For the SCS (SimulCrypt Synchroniser) to ECMG (Entitlement Control Message Generator), 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 20: Line 42:
The PROTO dissector is (fully functional, partially functional, not existing, ... whatever the current state is). Also add info of additional Wireshark features where appropriate, like special statistics of this protocol. 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 24: Line 47:
(XXX add links to preference settings affecting how PROTO is dissected). There are some [[SIMULCRYPT_Preferences]].
Line 28: Line 51:
XXX - Add a simple example capture file to the SampleCaptures page and link from here (see below). Keep this file short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.
Line 30: Line 52:
 * [[attachment:SampleCaptures/PROTO.pcap]]  * [[attachment:SampleCaptures/SIMULCRYPT.pcap]] - Simulcrypt traffic over [[TCP]] on ports 8600, 8601 and 8602.
 * [[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]].
Line 35: Line 61:
 Show only the PROTO based traffic: {{{
 proto }}}
 Show only the SIMULCRYPT based traffic: {{{
 simulcrypt }}}
Line 40: Line 66:
You cannot directly filter PROTO protocols while capturing. However, if you know the [[TCP]] port used (see above), you can filter on that one. You can directly filter SIMULCRYPT protocols while capturing if you know the [[TCP]] port used (see above).
Line 42: Line 68:
 Capture only the PROTO traffic over the default port (80): {{{
 tcp port 80 }}}
 Capture only the SIMULCRYPT traffic over the chosen port (<port>): {{{
 tcp port <port> }}}
Line 47: Line 73:
 * add link to PROTO specification and where to find additional info on the web about it, e.g.:
 * [[http://www.ietf.org/rfc/rfc123.txt|RFC 123]] ''The RFC title'' - explanation of the RFC content.
 * [[http://pda.etsi.org/pda/queryform.asp]] '' ETSI TS 103 197 V1.5.1 (2008-10)'' - Digital Video Broadcasting (DVB);Head-end implementation of DVB SimulCrypt, latest version.
 * [[http://pda.etsi.org/pda/queryform.asp]] '' ETSI TS 101 197-1 V1.1.1 (1997-06)'' - Digital Video Broadcasting (DVB);DVB SimulCrypt;Part 1: Head-end architecture and synchronization
 * [[http://www.dvb.org/technology/standards/index.xml#conditional]] '' List of DVB standards relating to Conditional Access'' - various standards
 * [[http://fr.wikipedia.org/wiki/Simulcrypt]] '' Wikipedia entry'' - currently only in French

Simulcrypt (SimulCrypt)

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).

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.

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.

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.

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)