/
OWM glossary

OWM glossary

Overview

This glossary defines key terminology used in OWM (One Wifi Manager) documentation, clarifying the differences between RDK-specific terms and OpenSync terminology.

OpenSync Terminology

ow (opensync onewifi)

  • OpenSync's [o]ne[w]ifi implementation library

  • Contains OpenSync-specific business logic including:

    • OVSDB interactions

    • Steering behavior

    • Statistics translations

    • MQTT/protobuf sendouts

  • The core business logic layer that processes wireless management requests

  • ccsp-onewifi is a spin-off for RDK platforms

osw (opensync wireless framework)

  • [o]pen[s]ync [w]ireless framework

  • Provides abstractions, helpers, utilities, and backend (driver) implementations

  • Core framework that ow builds upon

  • Includes:

    • Driver abstractions (nl80211)

    • State management

    • Configuration management

    • Statistics collection

    • Event handling

owm (one wifi manager)

  • The OpenSync onewifi implementation for non-RDK platforms (with ccsp-onewifi being a spin-off for RDK platforms)

  • Simply starts "ow" (the OpenSync OneWifi implementation)

  • Also replacing WM2 on OpenSync (non-RDK) platforms

  • The main daemon process that orchestrates wireless management

  • Entry point that initializes and runs the onewifi system

OSW Modules

  • Modular components within the OSW framework

  • Examples: osw_confsync, osw_stats, osw_state, osw_mux

  • Can be loaded on-demand

  • Provide specific functionality that can be composed together

osw_conf

  • Configuration intent layer

  • Holds the "intended" configuration

  • Populated from OVSDB tables (Wifi_Radio_Config, Wifi_VIF_Config)

  • Represents what the system should be

osw_state

  • State layer

  • Holds the "actual" current state

  • Populated from driver/netlink/netdev events

  • Represents what the system currently is

osw_confsync

  • Configuration synchronization engine

  • Compares osw_conf vs osw_state

  • Generates commands to reconcile differences

  • Sends commands to osw_mux

osw_mux

  • Driver multiplexer

  • Routes commands to appropriate drivers (nl80211)

  • Provides unified interface to hardware

ow_steer

  • Steering module

  • Handles client and band steering

  • Includes policies for steering decisions

  • Executes steering actions (BTM, deauth, ACL)

ow_stats

  • Statistics module

  • Collects wireless statistics

  • Publishes statistics via TLV format

  • Integrates with data pipeline for cloud reporting

RDK-Specific Terminology

OneWifi

  • A bracket term that is ambiguous and should only be used with a pre-established context within a given discussion

  • Not a specific component, but rather a conceptual term

ccsp-onewifi

  • A spin-off of OWM by RDK-B that supersedes ccspwifiagent

  • ccsp-onewifi was/is intended to integrate with "ow" (a hardcoded and maintained version by RDK-B from OpenSync 4.4, maintained outside of OpenSync)

  • Used primarily in RDK-B deployments

Related Terminology

WM2

  • Wireless Manager 2

  • Legacy wireless management system

  • Being replaced by OWM

  • Used direct target API calls which leaked abstraction

BM (Band Manager)

  • Legacy band steering manager

  • Separate from WM2

  • Functionality now integrated into OWM via ow_steer_bm

SM (Statistics Manager)

  • Statistics manager used in traditional OpenSync deployments

  • Still actively used and fully supported

  • When using OWM, part of SM functionality has been moved to OWM via ow_stats

  • Remaining SM functionality continues to operate in SM

nl80211

  • Linux netlink 802.11 interface

  • One of the driver backends for OSW

  • Provides access to wireless hardware via kernel netlink sockets

Target API

  • Legacy platform-specific driver interface

  • No longer used in OWM

  • Previously implemented by each platform/target

  • Historical hardware abstraction layer