RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
SoC vendors are advised to get into an agreement with RDK Management LLC to obtain the free license so as to use the complete RDK Code base in their platform. More details about license is available at https://rdkcentral.com/licenses/ . Please email info@rdkcentral.com if you have additional questions about licenses or membership
The first step to get a fully functional product is the define the product features and see if they meet the standard requirements. A list of expected features from an IP based Set-top box are listed at Product Specifications. MSO can cross check the expected features/specifications with the capabilities of the OEM device being used and can finalize the features supported by the product.
For details of product specifications, please refer: Product Specifications
Operators can make use of the details available at MSO Platform Firmware to start developing a Yocto build to do the final additions of MSO specific changes to the device. This will help MSO to add their own final product features as well as MSO specific patches/changes.
For details, please refer: MSO Platform firmware
MSOs will be having a range of MSO specific applications from simple generic device information apps to MSO specific content applications. RDK's Yocto based layered structure allows MSOs to easily integrate, upgrade and maintain their apps in their RDK based IP Set-top devices. For more details on App support in RDK, please refer Applications as well as MSO Platform Firmware for the engineering details.
For details of MSO Specific Apps, please refer: MSO Specific Apps
RDK supports usage of multiple User Interface in the RDK IP Set-top devices. MSOs can choose from among the already available UIs that are available with RDK as well as develop and use their own UI. For more information on UI support in RDK, please refer User Interface.
Based on resident app reference implementation Operator need to bring up the UI.
For details of UI support in RDK IP Set-top devices, please refer : User Interface
Along with the MSO specific apps, MSO can support a lot of generic apps in RDK IP Set-top devices by taking advantage of RDK Support for Native as well as Web Apps in IP based Set-top platforms. MSO can easily port native apps in their platforms (for some third party apps, MSO need to obtain certification from those third party) or can host their own app store and then use Web Apps to show content. For more information on App support in RDK, please refer Applications.
For details of App support in RDK IP based Set-top devices, please refer: Applications in RDK
MSO needs to add provisioning support in device so that Device provisioning can be done once deployed at customer premise. The steps for this varies based on platform as well as MSO type.
Provisioning support refers to the scenario such as when you launch Sample app on your mobile it takes to login page and so you have to login there, account there i.e. actually the app has to authenticate your login.
Disaster recovery is an inevitable part of the CPE life cycle. MSO, based on their disaster recovery strategy, could add support for this in the device. While there are some generic guidelines followed across industry, there is no single step that works for all. MSOs could easily add their business logic to RDK as part of MSO firmware engineering as described in MSO Platform Firmware.
As an operator they have to handle crashes/disaster happens and support any factory reset like OTA upgrade.
Once the device engineering is completed from MSO side, the device can be test and verified easily by the Certification support provided by RDKM. Details of coverage as well as major cases are explained here .
For details on test & certification of devices, please refer: Test & Certification of devices
To start with RDK, MSO needs
What Operators need to get is :