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 9 and 10
Revision 9 as of 2011-08-08 21:15:11
Size: 3328
Editor: MartinKaiser
Comment:
Revision 10 as of 2011-09-13 21:05:10
Size: 3931
Editor: MartinKaiser
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
Line 32: Line 33:
 * ''reassembly of fragmented LPDUs''
 * ''resource manager, application information, ca, mmi, date-time and host control resource''
 * ''reassembly of fragmented TPDUs and SPDUs''
Line 35: Line 35:
''To complete EN50221 support, fragmentation of TPDUs will be added shortly.
Line 37: Line 36:
Low-level MMI and low-speed communication will not be supported. The same goes for the DVB-CI extensions (TS 101 699).
Line 39: Line 37:
Once DVB-CI support is complete, the next milestone is CI+ 1.2 support.'' ''The table below summarizes the supported resources on the application layer''

|| || DVB-CI || CI+ 1.2 || CI+ 1.3 ||
|| Resource Manager || ok || ok || ok ||
|| Application Info || ok || ok || ok ||
|| Conditional Access || ok || ok || ok ||
|| Date-Time || ok || ok || ok ||
|| MMI (high level) || ok || ok || ok ||
|| Host Control || ok || ok || missing ||
|| Low-Speed Communication || unsupported || missing || missing ||
|| Host Language and Country || not defined || ok || ok ||
|| CAM upgrade || not defined || ok || ok ||
|| Content Control || not defined || missing || missing ||
|| Application MMI || not defined || ok || missing ||
|| Specific Application Support || not defined || ok || ok ||
|| Operator Profile || not defined || not defined || missing ||


''Missing parts will be added as time permits. There's no plans to support low-level MMI, low-speed communication for DVB-CI and the DVB-CI extensions (TS 101 699).''

DVB Common-Interface (DVB-CI)

DVB-CI defines an interface between a DVB receiver (TV set, Set-Top-Box, Bluray recorder etc.) and a PC-Card module (Conditional Access Module, CAM). It consists of a transport stream interface and a command interface.

On the transport stream interface, a DVB Transport Stream can be routed through the module and optionally be descrambled. The command interface transfers commands like start descrambling. The DVB-CI dissector processes command interface traffic and some hardware events such as module inserted/extracted

History

DVB-CI was defined by DVB in 1997. An extension document followed in 1999, but the extensions defined there were never implemented in practice.

CI+ added content security and other features on top of DVB-CI. CI+ version 1.2 was published in May 2009, version 1.3 followed in January 2011.

standards documents

Example traffic

The screenshot shows dissection of the application_info() APDU. The capture contains no timestamps. If timestamps are available, the dissector can handle them.

wiresharkDvbciPcap.png

Wireshark

The DVB-CI dissector was written by Martin Kaiser ( wireshark-wiki@kaiser.cx ). It is in beta state.

The following features of the DVB-CI standard EN50221 are supported

  • hardware events (module inserted/removed, power on/off, ...)

  • Card Information Structure (CIS)

  • link, transport, session layer

  • reassembly of fragmented TPDUs and SPDUs

The table below summarizes the supported resources on the application layer

DVB-CI

CI+ 1.2

CI+ 1.3

Resource Manager

ok

ok

ok

Application Info

ok

ok

ok

Conditional Access

ok

ok

ok

Date-Time

ok

ok

ok

MMI (high level)

ok

ok

ok

Host Control

ok

ok

missing

Low-Speed Communication

unsupported

missing

missing

Host Language and Country

not defined

ok

ok

CAM upgrade

not defined

ok

ok

Content Control

not defined

missing

missing

Application MMI

not defined

ok

missing

Specific Application Support

not defined

ok

ok

Operator Profile

not defined

not defined

missing

Missing parts will be added as time permits. There's no plans to support low-level MMI, low-speed communication for DVB-CI and the DVB-CI extensions (TS 101 699).

The dissector uses pcap files with datalink type 235. The corresponding format is documented at http://www.kaiser.cx/pcap-dvbci.html

Preference Settings

There are no preference settings for DVB-CI itself.

However, DVB-CI uses length fields in ASN.1 BER format in many messages. To dissect these length fields, the DVB-CI dissector uses the existing BER code. To display details of each length field, select Show internal BER encapsulation tokens from the Edit / Preferences / Protocols / BER preferences.

Example capture files

SampleCaptures/dvb-ci_1.pcap startup, requests for descrambling, removal

SampleCaptures/dvb-ci_2.pcap fragmentation and reassembly on the link layer

Display Filter

Capture Filter

Discussion

DVB-CI (last edited 2012-08-15 20:24:03 by MartinKaiser)