Tom san, let you report me what they support and what they don't support clearly. As you may know. Unfortunately, your board function seems to still have hide mystery. Data broadcasting content is made by broadcaster by using HTML5 language. (Your adviser cannot make content by themselves) ACAS council is a broadcasters organization. So we must obey the prerequisites they present.When broadcaster makes their content and they did not recognize the exist of receiver which has not PPV function, this operation of the function is inconsistent and causes trouble.For example, customer select a PPV, but they can not buy it. Worst case, function may freeze. Because, content(PPV secrecy menu)is made by Broadcaster at HTML5 language. If broadcaster recognized the exist of no PPV function receiver and specification is supported, broadcaster can make “This TV no PPV function so you can buy this PPV”indication. If it is not defined by broadcasting specification, Inconsistency occurs and trouble occursI don’t understand how many risks like this right now. I want to review, how many such risks our TV. Please discuss it and clarify them with your adviser.Anyway, I want to discuss with you whether we should go or stop our project in 煙台. It may be strong depend on your adviser’s behavior.