RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Page History
...
| Table of Contents |
|---|
Introduction
Opensync OpenSync :
- Opensync OpenSync is designed to provide a Software Defined Network (SDN) platform, through which it virtualizes the networking and wireless management for easy service roll-out. It acts as a silicon, CPE, and cloud-agnostic connection between in-home hardware devices and the cloud.
- It provides a modern set of utilities for collecting measurement and other telemetry data from devices. It also enables remote control and management of the devices, and advanced capabilities for specific services, including Wi-Fi meshing, access control, cybersecurity,
parental controls, and IoT onboarding and telemetry.
...
| draw.io Diagram | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
System Architecture
| draw.io Diagram | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
OVSDB Manager
Cloud controller can configure Wi-Fi parameters in gateway, extender or CPE using OVSDB & Manager entities. OVSDB is a database server that executes in RDK-B CPE. Any update of parameters in this database by cloud controller is notified to OneWifi process by OVSDB manager entity over RBUS. OneWifi process validates the parameter or set of parameters and applies the configuration in WiFi driver or baseband. If successfully applied, OneWifi also notifies OVSDB manager about the successful completion so that the database tables are updated with the right state of WiFi subsystem of the CPE.
...
| VAP Index | Name | Comment |
|---|---|---|
| 1 | private_ssid_2g | 2g user private ssid |
| 2 | private_ssid_5g | 5g user private ssid |
| 12 | mesh_backhaul_2g | Mesh backhaul on 2g |
| 13 | mesh_backhaul_5g | Mesh backhaul on 5g |
| 14 | mesh_sta_2g | Mesh station on 2g |
| 15 | mesh_sta_5g | Mesh station on 5g |
Target Build Variant
- RPI4 Kirkstone build with kernel 5.15
Identified task list
Need to learn how OpenSync work with OneWiFi - Communication is through DM/RBUS, not wifi hal. May need to refer Comcast device.
Need to compile OpenSync for OneWifi (some kconfig should be enabled)
Need to know how to start OpenSync through OneWiFi
Need to know OVSDB tables of OpenSync collaborate with OVSDB tables of OneWiFi(wifi.db)
Bringup OVSDB manager for synchronization
Wi-Fi interface alignment with Netgear wifi dongle and Make sure existing wifi functionality won't be disturbed.
Netgear driver support with 2.0 USB portKirkstone version
Conversion of Linux bridge into OVS bridge(brlan0) - OVSAgent is now part of rootfs but not operational
Update dnsmasq configuration for OpenSync backhaul AP feature (wifi2, wifi3)
Enable IP_GRE as kernel module
Home AP bringup in RPI GW
Backhaul AP bringup in RPI GW
Make sure that GRE tunnel is created for backhaul communication and it is stable (Need to be tested with Extender)
Need to make sure that onewifi existing functionality is not breaking
...
Dongle's minimal support for 2AP and 1 STA.
If Netgear dongle is not providing such support, need to find new WiFi dongle.
Device provisioning in Plume Inventory (require Plume's support)
- ovsdb manager/OVSM acts as medium between onewifi webconfig subdoc and plume controller
- Opensync OpenSync have run-time dependencies with ovsdb-server & openvswitch(ovsdb-server start up is part of ovsagent . currently, this server is not running in rpi).
Considerations
Start the integration activity either in dunfell or kirkstone feature branch
if we go with dunfell, we may need to put extra effort for kirkstone based build
- dunfell may be supported for next few releases.if we want to go with dunfell based build, its better to start with 64bit build
Validation
Check opensync service / Opensync OpenSync process will be run by meshagent DM parameter
Check opensync managers
Check Manager table for Online status
Associate RPI4 extender with RPI4 gateway
- Check synchronization of both OpenSync DB and RDKB Wifi DB tables during updates through Plume NOC / RDKB WebUI/ DMCLI
- All Wi-Fi testcase should be working with Netgear Wi-Fi dongle in Kirkstone
- Validation of Mesh will be done with SuperPOD as extender
Risks
- Availability of OVSM for RDK Community is mandatory
- Wireless interface names for Wifi dongle needs to be aligned for OpenSync conventioncheck ovsdb and wifi db table updation if any action taken in plume NOC / RDK WebUI
Flow Diagram/Pseudo Code
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Sequence Diagrams
| draw.io Diagram | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Build Instructions
1. RPI4 32bit :
Dunfell branch
...
| Target | Yocto version | Build instruction |
|---|---|---|
| RPI4 32bit | Dunfell | RPI 4B Model Reference Platform |
...
Kirkstone branch
...
| RPI4 32bit | Kirkstone | kirkstone RDK-B RPI4 32 bit |
...
| RPI4 64bit |
...
Dunfell branch
...
Kirkstone branch
...
...
| RPI4 64bit | Kirkstone |
Supported device
- Raspberry Pi4 32 bit
- Raspberry Pi4 64 bit
...
EPIC/User Stories
| Jira | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Community Forums
Content Tools
Tasks