Page History

BUS

1. OB-USP-Agent
2. prpl Foundation (prplOS)

1. Active relationship between prpl and OBUSPA
   1. Funding of engineering efforts to implement OBUSPA features
   2. Integration of OBUSPA into prplOS for internal communications and remote management
2. Direct relationship between prpl and BBF via barter membership
3. Active marketing collaboration between prpl and BBF
   1. Regular marketing meetings
   2. Mutual support of events
      1. prpl Summit events
      2. Network X events
4. Active technical collaboration between prpl and BBF
   
   1. USP specification expansion

1. Continued investment in OBUSPA feature development

1. OB-USP-Agent
2. RDK (RDK-B)

1. In-direct relationship between RDK and OBUSPA (via BBF member companies)
   
   1. Integration of OBUSPA into RDK-B for remote management
2. Direct relationship between RDK and BBF via paid for membership

1. Active marketing collaboration between prpl and BBF
   1. Regular marketing meetings
   2. Mutual support of events
      1. RDK Summit events
      2. Network X events
2. Engagement in USP Specification
3. Better integration of OBUSPA
4. Adoption of USP over WebPA

1. WFA
2. OB-MAP
3. prpl Foundation (prplMesh)

1. BBF Liaison relationship with WFA (after years of trying), but mostly limited to Data Elements
2. OB-MAP provides a neutral meeting space for RDK, prpl, WFA, and BBF interested parties to discuss Wi-Fi concepts
3. WFA's Data Elements is largely integrated into Device:2 Root Data Model with little review (rubber stamped)

1. More WFA member company participation in BBF
   1. Better collaboration on Wi-Fi data model architecture

1. WFA
2. OB-MAP
3. prpl Foundation (prplMesh)

1. Largely covered by Data Elements as EasyMesh is a protocol for communicating between devices within a home network
   1. USP and EasyMesh could cover the same use case, but EasyMesh was first and is more efficient/fit-for-purpose

1. Expansion of features
   1. Firmware management for Wi-Fi APs

1. RDK-V

1. Direct relationship between RDK and BBF via paid for membership
2. No real adoption of BBF standards in RDK-V (STB)
   1. Doesn't use USP
   2. Doesn't use TR-135 (STBService Data Model)

1. Adoption of USP for remote management
2. Adoption of TR-135 as the device's data model
   1. Work with BBF to advance the STB data model

1. prpl Foundation (prplLCM)
2. RDK DAC

1. Limited collaboration with prpl; fairly inactive for the last 18 months
2. No collaboration with RDK

1. Renewed collaboration with prpl - at least to help develop WT-492
2. Start with initial discussions on RDK DAC and alignment with BBF
   1. Alignment with USP / Device:2 Root Data Model as it pertains to Software Module Management
   2. Contributions to WT-492

1. prpl Foundation (HL-API)

1. Direct relationship between prpl and BBF via barter membership
   1. William attends data model architecture meetings
2. Active technical collaboration between prpl and BBF
   1. Device:2 Root Data Model expansion

1. More architectural feedback on the prpl side before data models are submitted to BBF BUS

1. RDK (RDK-B, RDK-M, RDK-V)

1. Direct relationship between RDK and BBF via paid for membership
2. Some Active technical collaboration between RDK and BBF
   1. Device:2 Root Data Model expansion (PON, Cellular)

1. More collaborative work on other parts of the data model
2. Active migration from vendor specific data model components to BBF standard data model components

1. CSA / Matter
2. WBA

1. Working with CSA very loosely with joint members (mostly Orange).
   1. Really would like an actual liaison agreement with CSA.
2. Actively working with WBA via joint meetings
   1. Periodic joint calls but they move quickly.

1. Liaison with CSA
2. More collaboration with WBA