What is the expected date and release where the DSG application tunnel support will be supported in the RI stack?
Just to confirm:
The DSG application tunnel support is code complete in RI 1.1.4 Rel C and is currently undergoing tests.
Is that correct?
When do you envisage test complete, 1.1.4 Rel D or 1.2?
The DSG app tunnel implementation has actually been in place for quite a while. However, we have just now gotten the firmware support implemented on our test device. We certainly hope to complete our testing with the MSO guides by the RelD release.
As a side note, I know that we have hardware vendors running the RI on their device using DSG app tunnels and we haven't received any bug reports to date. This doesn't mean that there aren't still problems, but I believe you should be able to start testing your implementation with the RelC code.
Although the Rel-C implemented the MPE_FILTER_SOURCE_DSG_APPID case in mpeos_filterSetFilter() and added some ri_dsg_pipeline files, it does not seem to support fully the DSG application object carousel defined in OCAP 188.8.131.52.
According to above spec, OCAP supports multiple object carousels on multiple DSG application tunnels and each application tunnel has one PAT and one PMT.
So, to open an application tunnel and filter the PAT in the same application tunnel, mpeos_filterSetFilter() method should set the "filterSource->parm.p_DSGA.appId" additionally to create_filter() method of ri_section_filter.
Then, the RI_Platform could open the correct application tunnel and filter the PAT with the PID value of 0.
Yes, our PC Platform currently only supports one app tunnel at a time. This is due to limitations in the test hardware we use to exercise app tunnels. The platform-independent stack, however, should be fully capable of supporting multiple carousels on multiple tunnels. If you find bugs in the platform-independent DSG code, please file a bug in IssueTracker.
A couple of issues related to DSG were resolved since 1.1.4 Rel C. These changes will be part of Rel D.
See IT issue #262:
Fix for IT-262 (Possible tight loop condition in mpe_siCreateDSGServiceHandle)
If service entry is found in the list it should not be re-added.
Also resolved issue in mpe_siSetAppType() which was re-setting the appId.
The appId is set by mpe_siSetAppId() call.
Ran smoke tests, Tunetest, DVRExerciser.
Thanks you for the update.
With these two patches, I think the DSG object carousel will be functional normally.
DSG application tunnel support should be fully implemented in the stack. We are currently in the process of testing the implementation, but we are waiting for some firmware fixes for our test hardware.
You MPEOS section filtering implementation must simply support the mpe_FilterSource_DSG_APPID filter source type as passed in to mpeos_filter_SetFilter().
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.