RDK Connectivity provides a common software and data solution across all Connectivity access technologies including Fixed Wireless, DOCSIS, GPON, and DSL. It provides functionality such as routing, Wi-Fi, DNS, remote management, and the smaller image footprint eases deployment on devices.

Some of the key characteristics of RDK-Connectivity are:

Open-Source Platform: RDK-Connectivity is developed as an open-source project under RDK Management LLC.

Modular & Scalable Design: Component-based architecture supporting device profiles from full-featured gateways to lightweight extenders.

Standards-Based: Implements TR-181 data model and TR-069/TR-369 USP management protocols.

Easily Customizable: Standards like TR-181 are customized based on operators' needs rather than following exact specifications, enabling flexible deployment tailored to specific requirements.

Hardware-Agnostic: Clearly defined HAL APIs for each functions, making it easy for multiple chipset vendors to adopt RDK, as well as keeping RDK middleware platform agnostic.

OverviewDiagram

RDK-Connectivity supports multiple access technologies including DOCSIS 3.0/3.1, GPON/XGS-PON, DSL (ADSL2+, VDSL2, G.fast), Fixed Wireless (LTE/5G), and Ethernet WAN with multi-WAN capabilities. The platform includes networking features such as Wi-Fi (Wi-Fi 6/6E), mesh networking, LAN bridging, VLAN, DHCP server, routing, and QoS, while security is provided through firewall, WPA3 encryption, access control, and parental controls. Device management is supported via TR-069 (CWMP), TR-369 (USP), WebPA, and WebConfig protocols, with additional features including voice services (SIP/VoIP), IoT protocol support (Zigbee, Z-Wave, Thread), IPv6 support, and DNS management.

Device Profiles

Router Profile

The RDK-Connectivity router profile offers LAN management capabilities to configure and manage local area network settings. This includes features like DHCP server for automatic IP address assignment, NAT for private network connectivity, and firewall settings for network security. In terms of WAN management, RDK-Connectivity supports technologies such as EthWAN, DSL, GPON, and LTE for connections to different types of internet services.

Wi-Fi Extender Profile

The RDK-Connectivity Wi-Fi extender is designed to extend the Wi-Fi range for wireless clients. It operates in conjunction with the RDKB gateway and broadcasts the same SSID as the gateway. The hardware of the Wi-Fi extender is cost sensitive, and it does not require all the software components of the gateway. Acting as a Layer-2 switch, it supports RF technologies like MoCA, Wi-Fi, Zigbee, and BLE for user device connectivity. The extender can establish backhaul IP connectivity using MoCA, Ethernet, or Wi-Fi.

  • No labels

10 Comments

  1. Unknown User (s.bakkanagari)

    Jun 04, 2020

    Hi,
    I am trying to port an application onto RDK-B. Below lines are my recipe do_compile part. while executing do_compile part i was getting error which was mentioned below , the main theme of do compile is to setup environment and build binary after downloading the source code but i as getting an error called files not present  can you suggest me what was the backoff of went through.

    S = "${WORKDIR}"

    do_compile() {
            ./script/bootstrap
            ./bootstrap
            make -f src/posix/Makefile-posix
            make -f examples/Makefile-cc1352
    }

    ERROR: Function failed: do_compile (log file is located at /home/muddu/rdkb-2018q1/build-qemux86broadband/tmp/work/i586-rdk-linux/openthread/1-r0/temp/log.do_compile.8266)
    ERROR: Logfile of failure stored in: /home/muddu/rdkb-2018q1/build-qemux86broadband/tmp/work/i586-rdk-linux/openthread/1-r0/temp/log.do_compile.8266
    Log data follows:
    | DEBUG: Executing shell function do_compile
    | /home/muddu/rdkb-2018q1/build-qemux86broadband/tmp/work/i586-rdk-linux/openthread/1-r0/temp/run.do_compile.8266: line 100: ./script/bootstrap: No such file or directory
    | WARNING: /home/muddu/rdkb-2018q1/build-qemux86broadband/tmp/work/i586-rdk-linux/openthread/1-r0/temp/run.do_compile.8266:1 exit 1 from
    |   ./script/bootstrap
    | ERROR: Function failed: do_compile (log file is located at /home/muddu/rdkb-2018q1/build-qemux86broadband/tmp/work/i586-rdk-linux/openthread/1-r0/temp/log.do_compile.8266)
    ERROR: Task 6 (/home/muddu/rdkb-2018q1/meta-openthread/recipes-openthread/openthread/openthread_1.bb, do_compile) failed with exit code '1'

    1. Narayanaswamy Ramaiyer

      Jun 05, 2020

      Hi Unknown User (s.bakkanagari)

      Please try adding WORKDIR or S with respect to your actual folder in front of the bootstrap command

  2. Unknown User (s.bakkanagari)

    Jul 21, 2020

    .

    1. Narayanaswamy Ramaiyer

      Jun 08, 2020

      Hi Unknown User (s.bakkanagari),

      For a regular Yocto recipe, the output of do_compile will be in the same folder as source code( or as mentioned in the Makefile,if it is different from the normal format ). If you are looking for where the binaries will be available in target platform, it is as mentioned in the do_install( from you recipe and normal terms, it should be /bin/ in target platform,i presume )

  3. Unknown User (s.bakkanagari)

    Jun 09, 2020

    Hi Unknown User (nvysya200)

    LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/BSD;md5=3775480a712fc46a69647678acb234cb"
    SRCBRANCH="thread-reference-20180926"

    SRCREV = "${AUTOREV}"

    SRC_URI = "https://github.com/openthread/openthread.git;protocol=https"

    SRC_URI[md5sum] = "a30ae374b45fb970bd1931b633a69ae4"
    SRC_URI[sha256sum] = "2de394f342c8be199e801a71060655dd1bc59961aef9a9abe09482964ef6b364"


    S = "${WORKDIR}/git/openthread


    this was my recipe here i was fetching code from git hub when i open the url (in browser) which was mentioned in the recipe it was accessible but i dont know why the code is not downloading. can you help me with this

  4. Unknown User (s.bakkanagari)

    Jul 21, 2020

    .

    1. Narayanaswamy Ramaiyer

      Jun 16, 2020

      hi Unknown User (s.bakkanagari)

      Please try if you can manually try a git clone for that repo from the command line of pc where you are performing this operation

      1. Unknown User (s.bakkanagari)

        Jun 18, 2020

        Hi Unknown User (narayanaswamy)

        yes I tried in that way also, when i was tried to clone it it was cloning successfully. but through recipe it was not happening.


        1. Narayanaswamy Ramaiyer

          Jul 10, 2020

          Hi Unknown User (s.bakkanagari),

          Are you seeing a fail in do_fetch or are you seeing a fail in invoke of the recipe itself?

  5. Z-Hythem Salem

    Sept 10, 2024

    Can you please share with me the DOCSIS tests cases? and if that also including DOCSIS 4.0 testing?  Thanks 

DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.