<Work in progress. only the skeleton added>

This page provides the details and guidance to the Operators on how to adopt RDK-B. The step by step procedure for an operator to get an RDK based Platform up and running is also described in detail.

Before You Begin

RDK License

Operators 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

Overview

Operator can choose preferable device from OEM and also get details from SoC vendors, SoC vendors will already have RDK ported on top of their SoC so they will be having all the features supported in SoC so based on that Operator's can select a OEM with preferred SoC platform and then they can start integrating features that Operator requires on top of the OEM layer so that they can have final product.

This document will detail the recommended step by step procedure of adopting RDK by a Operator.

Operator Checklist

Product Specifications

The first step to get a fully functional product is to define the product features and see if they meet the standard requirements. See here to know what are all the features available in RDK-V and can implement based on your requirement. SoC can use this as a guide while engineering the RDK SoC platform.

Device Firmware

Operators can make use of the details available below to start developing a Yocto build to do the final additions of Operator specific changes to the device. This will help Operator to add their own final product features as well as Operator specific patches/changes.

Yocto Manifests

<ToDo>

Operator meta-layer creation

<ToDo>

Adding the Machine Configuration File for the new Operator

<ToDo>

Operator Specific Apps

Operators will be having a range of Operator specific applications from simple generic device information apps to Operator specific content applications. RDK's Yocto based layered structure allows Operators to easily integrate, upgrade and maintain their apps in their RDK

Operator Specific UI

<ToDo>

Provisioning Support

<ToDo>

Disaster Recovery

Disaster recovery is an inevitable part of the CPE life cycle. Operator, 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. Operators could easily add their business logic to RDK as part of Operator firmware engineering

As an operator they have to handle crashes/disaster happens and support any factory reset scenarios

TDK

In short, to get an RDK based device to field, Operators need to get

• RDK license
• Commercial License Agreement
• Project agreement with OEM's/ SoC
  

What Operators get from RDK:

• Pre-certified stack for third party apps is available in RDK.
• RDKServices are available to customize RDKService plugin plugout components for all the stacks mainly Bluetooth, Wifi and front panel, power manager, device settings etc

What Operators need to do:

• As an Operator, the certification for the operators device has to be done by them
• Customization of boot loader for operator specific , operator specific UI, Operator specific any customization on the stack
• Operator specific task on RDK are customization of UI to adopt RDKServices
• Operator specific requirements has to be implemented by operator