For Operators

Product Specifications

ToDo: Generic RDK specifications, add specifications w.r.t generic.

Device Firmware

<Already have these info in accelerator pages Getting Started - MSO.However it needs to be w.r.t generic STB's  >

MSO Specific Apps

<Already have these info in accelerator pages.However it needs to be w.r.t generic STB's  >

MSO Specific UI

<Already have these info in accelerator pages.However it needs to be w.r.t generic STB's  >

App Support

<Already have these info in accelerator pages.However it needs to be w.r.t generic STB's  >

Provisioning Support

<Already have these info in accelerator pages.However it needs to be w.r.t generic STB's  >

Disaster Recovery

<Already have these info in accelerator pages.However it needs to be w.r.t generic STB's  >

Test & Certification of devices

<Already have these info in accelerator pages.However it needs to be w.r.t generic STB's  >

what are the things required for SOC to get started?

TODO

what is available and what they need to do?

TODO

Operators actually 2 things.

1 is UI, UI integration with RDKServices. for them actually only main change will be UI because the stack which they ll receive from OEM will be already proven like it is been validated by OEM SOC certification which we have RDK.It has to pass through SOC certification when it goes to opertaor.Basically that means SOC certification or OEM device certification means RDK is been validated i.e.TDK suites have been validated.For operator actually it will be main challenge will be the UI integration where they have for example in multi choice case they have a UI & their UI is actually the browser instance which they create is a web kit browser instance they ll just create a webkit brwser instance and they ll use that browser for Ui they have something called system manager.They make a copy of this webkit browser n they define that so whatever configuration it needs basically the resolution settings, port related things like which port it has to be the data socket communication which port like the current RDK we are having port 9998 for all the communications will be on port 9998 but for multichoice they have already UI it is from the previous project when they try to migrate so there UI is being configured to listen on port 80 that's the first challenge they faced.there actually akhil's team suggested in RDKServices currently everywhere it is hardcoded to 9998 so they raised Jira for comcast to make it configurable but it is current RDKServices everywhere it is been hardcoded with 9998 .So then we requested them whether they can move to 9998 or we already provided a patch to configure to port 80 they initially took our patch but later they changed UI to listen on port 80 .So all the socket communication n the navigation from the application manager will be based on port 9998.That was one of the major challenge we had in the multichoice.2nd thing is UI integration n Dial related  integration for the youtube certification.For the youtube certification dial has to be integrated in the Ui we have provided a sample app current resident app is the source code right those actually we pass on that .....so these are the operators specific related stuff which they need to do .1 is bring up the UI based  on the resident app reference implementation and as part of that i.e.1 line actually -based on resident app reference implementation they need to bring up the UI so internally to that there are so many things 1 is the eg:dial , the other one is webkit browser instance which i mentioned n other configurations settings n their persistents areas.The RDK we are mapping the persistent related whatever default persistent like OPT or whatever it is ,as a operator they might be having different it is not just youtube,those things right as a operator they have their own live TV applications just like TATA SKY or other things.there also they have a user based ,user data have to be stored.So their account for that show macs or the DSTV application they have a account manager there which will have like headend backend for billing na ll ,like how to request channels subscription those are part of Ui,those has to be integrated with RDK also,Like there the challenges are like mainly the persistent data i mean the user data where to store n whether it is secure or not those kind of info they ll tc that is another part of a sa operator they need to bring in.4 th is OTA upgrade.So OTA upgrade from RDK point of view we have provided 2 solutions 1 is xconf based where we r giving listen of xconf server like as  a sample server to they can any operator can refer to xconf server n create their OTA server but in the multi choice case they have already have a OTA backend  from the, they are having market sinnce very long time they have  headend n the backend server they have alraedy a OTA server so they don;t use xconf there,there actually we have a firmware update plugin so they will use that firmware upgrade plugin for OTA upgrade this is 1 more area where operator has to their own specific changes.till 8;05.