Skip to main content

Filtering on VCT ID

2 replies [Last post]
steve_wadsworth
Offline
Joined: 2010-07-14
Points: 0

Currently the RI does not appear to filter VCT tables based on their VCT_ID value. This means if there are multiple different VCT's the last one parsed "wins" rather than the correct VCT as specified in the DSG_Directory or feature_parameters APDU from the CableCard (see section 9.20.5 of the CCIF spec). This behaviour is seen in testing on a Cisco headend.

Is this filtering expected to be done entirely in a lower layer (i.e POD) or is it a bug?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
greg80303
Offline
Joined: 2008-07-03
Points: 0

This APDU is sent by the card and is directed towards the eCM (host) for DSG filter configuration. The stack is not involved in this process. The stack expects to only receive the VCT that has been properly filtered by the eCM as directed by the CableCARD.

Our PC Platform can simulatethis sort of behavior. If you are using canned SI files that have more than one VCT ID in it, you can use the following variables in platform.cfg to configure VCT filtering:

# Should we filter SVCT FDC tables

RI.Platform.FilterSvct = FALSE

# What VCT_ID should we use to filter SVCT FDC tables

RI.Platform.FilterSvctId = 1

Greg

pmodem
Offline
Joined: 2008-12-17
Points: 0

It is true that the MPE SI layer does not filter VCT tables based on VCD_ID. It is expected to be done in the platform layer. The MPE layer expects to only receive tables that are already filtered for the host.