Residential Gateway (USP Agent in prplOS) | TR-369 (USP) | BUS | - OB-USP-Agent
- prpl Foundation (prplOS)
| - Active relationship between prpl and OBUSPA
- Funding of engineering efforts to implement OBUSPA features
- Integration of OBUSPA into prplOS for internal communications and remote management
- Direct relationship between prpl and BBF via barter membership
- Active marketing collaboration between prpl and BBF
- Regular marketing meetings
- Mutual support of events
- prpl Summit events
- Network X events
- Active technical collaboration between prpl and BBF
- USP specification expansion
| - Continued investment in OBUSPA feature development
|
Residential Gateway (USP Agent in RDK-B) | TR-369 (USP) | BUS | - OB-USP-Agent
- RDK (RDK-B)
| - In-direct relationship between RDK and OBUSPA (via BBF member companies)
- Integration of OBUSPA into RDK-B for remote management
- Direct relationship between RDK and BBF via paid for membership
| - Active marketing collaboration between prpl and BBF
- Regular marketing meetings
- Mutual support of events
- RDK Summit events
- Network X events
- Engagement in USP Specification
- Better integration of OBUSPA
- Adoption of USP over WebPA
|
Wi-Fi (Data Elements) | TR-181 (Device:2) | BUS | - WFA
- OB-MAP
- prpl Foundation (prplMesh)
| - BBF Liaison relationship with WFA (after years of trying), but mostly limited to Data Elements
- OB-MAP provides a neutral meeting space for RDK, prpl, WFA, and BBF interested parties to discuss Wi-Fi concepts
- WFA's Data Elements is largely integrated into Device:2 Root Data Model with little review (rubber stamped)
| - More WFA member company participation in BBF
- Better collaboration on Wi-Fi data model architecture
|
Wi-Fi (EasyMesh) | TR-181 (Device:2) | BUS | - WFA
- OB-MAP
- prpl Foundation (prplMesh)
| - Largely covered by Data Elements as EasyMesh is a protocol for communicating between devices within a home network
- USP and EasyMesh could cover the same use case, but EasyMesh was first and is more efficient/fit-for-purpose
| - Expansion of features
- Firmware management for Wi-Fi APs
|
STB | TR-140 | BUS | - RDK-V
| - Direct relationship between RDK and BBF via paid for membership
- No real adoption of BBF standards in RDK-V (STB)
- Doesn't use USP
- Doesn't use TR-135 (STBService Data Model)
| - Adoption of USP for remote management
- Adoption of TR-135 as the device's data model
- Work with BBF to advance the STB data model
|
App-Enabled RG | WT-492 | BUS | - prpl Foundation (prplLCM)
- RDK DAC
| - Limited collaboration with prpl; fairly inactive for the last 18 months
- No collaboration with RDK
| - Renewed collaboration with prpl - at least to help develop WT-492
- Start with initial discussions on RDK DAC and alignment with BBF
- Alignment with USP / Device:2 Root Data Model as it pertains to Software Module Management
- Contributions to WT-492
|
CPE Data Model (prplOS) | TR-181 (Device:2) | BUS | - prpl Foundation (HL-API)
| - Direct relationship between prpl and BBF via barter membership
- William attends data model architecture meetings
- Active technical collaboration between prpl and BBF
- Device:2 Root Data Model expansion
| - More architectural feedback on the prpl side before data models are submitted to BBF BUS
|
CPE Data Model (RDK-*) | TR-181 (Device:2) | BUS | - RDK (RDK-B, RDK-M, RDK-V)
| - Direct relationship between RDK and BBF via paid for membership
- Some Active technical collaboration between RDK and BBF
- Device:2 Root Data Model expansion (PON, Cellular)
| - More collaborative work on other parts of the data model
- Active migration from vendor specific data model components to BBF standard data model components
|
IoT | TR-181 (Device:2) | BUS | - CSA / Matter
- WBA
|