CAS transplantation for set-top box Software

Looking back at the three years of graduation, 1/3 of the time was spent in CA transplantation and testing. From the very beginning to now, almost all the major and minor domestic CAs have been in touch, tongfang, tianbai, digital video, computation, etc. Although the interface standards and test cases of CAS manufacturers are different, they all aim at the same purpose and are used to provide better service for the profit of operators. Through the authorization and anti-authorization of the front-end cas, end users are controlled, and the number of paid programs and the number of activated programs are equal to the one-size-fits-all situation in the simulation era.

Because we are engaged in terminal CAS transplantation, we will not describe the front-end structure and implementation here. We have to transplant the tianbai Ca on a new platform recently, just taking this opportunity, record the entire transplantation process, and compare other transplanted CAS for various ratios.

Before migrating cas, you must pay a certain amount of money to the CA manufacturer. The ca provider will provide the test stream and test card that we need for porting, the Test Library, corresponding header files, and description documents are required for porting.

Well, let's get down to the truth. When we get some of the above-mentioned materials, we will start to make a real change. like playing games, we will all follow the rules of the other party. Otherwise, we will only go out, the rules mentioned in CAS porting are described in the documents provided. Therefore, the first thing is to carefully read the document.

Different CAS manufacturers provide different documents in different ways. For example, the interfaces provided by tianbai and the same party are transplanted to the system layer and application layer. Do not be misled by the name, the system layer is implemented for CAS by STB, and the latter is vice versa. A document of the same party includes all modules. In this document, modules such as OS, Demux, and smartcard are provided. Each interface has parameter descriptions, it indicates whether STB Is responsible for implementation or must be called by Stb.