Skip to content
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

OB-BAA R4 Release Notes (30 September 2020)

Release 4.0.0 Highlights:

This release enhances the existing OB-BAA software by added now functionality that:

  • provides management of ONUs using virtualized OMCI message processing capabilities that includes YANG to OMCI message translation as a separate microservice and capabilities to proxy OMCI sessions between the OLT and the OMCI message translation service.
  • enhanced ONU management to include flexible ONU discovery and authentication capabilities.
  • capabilities to relay user and control plane packets between Access Nodes and SDN M&C control plane functions. The relay of user and control plane packets can be done via standard and/or vendor proprietary control adapters.
  • full support (FCAPS + Control Relay + vOMCI (OLT) capabilties for whitesboxes using standard interfaces.
  • the ability to dynamically create and deploy standard device adapters for new types of devices

In addition, this release includes:

  • a simulator for OLTs and ONUs that can be used for virtualized ONU management when developing OMCI message translation services.

Release documentation:

OBBAA for product documentation on System Description, Installation, Commissioning and Usage

Other related repos of OB-BAA includes:

NETCONF stack A NETCONF stack for use in OB-BAA implementations

vOMCI repository which contains the vOMCI Function and Proxy used in the OB-BAA Implementations

Control Relay repository contains the control relay feature of the OB-BAA project

pOLT Simulator pOLT Simulator for Broadband Forum WT-451 vOMCI project

ONU Simulator ONU simulator and test client(Extracted from pOLT Simulator)


Question : What should I do if ONU DETECT nofitication is not raised in OB-BAA for a vOMCI based ONU?

Answer : Sometimes kafka will not have the required topics being available when it started, hence vomci functionality might not work properly in that case. as a workaround after starting OB-BAA microservices using docker compose file, we should restart vomci container (wait for a minute to have the vomci container up and running) and restart vproxy container. This would solve the problem.

Release 3.0.0 Highlights:

This release enhances the existing OB-BAA software with new functionality that:

  • provides the capability that permits clients to subscribe to a set of events for notification purposes.
  • enhances the existing notification capabilities alarm relay and reporting.
  • enhances the adaptation framework to allow upgrade of Access Nodes.
  • provides the capability to check the conformance of a vendor's adapter with standard adapters.
  • enhances the adaptation framework to provide a conformance grade for adaptor's support of YANG modules for the type of node.
  • includes the Performance Monitoring (PM) collection framework with a PM collector for IPFIX exporters.
  • includes the basic SNMP adapter for use in vendor specific SNMP implementations.

In addition, this release includes:

  • a simulator that acts as an IPFIX exporter that can be used with the PM framework.
  • a time-series database, InfluxDB, that can be uses a the PM framework's data lake.


Same as release 2.1.0.

Release 2.1.0 Highlights:

This release provides additional enhancements for:

  • Vendor Device Adapters (VDA): Provides the capability for VDAs to include a default configuration to be used for initial device configurations.

  • Included the capability to have multiple versions of Vendor and Standard device adapters for a type of Access Node and/or vendor model/version.

  • Examples related to the usage of the NETCONF stack used in OB-BAA


Same as release 2.1.1.

Release 2.0.0 Highlights:

This release enhances the existing OB-BAA software by adding functionality that:

  • provides the capability for vendors of access nodes that use protocols other than NETCONF/YANG to be used in OB-BAA.

  • provides the ability for service providers to define the YANG modules that comprise a type of Access Node (e.g., OLT, DPU). The project includes examples of the YANG modules for an OLT or DPU based on the work of the Broadband Forum's TR-413 specification. Included with this feature is additional capabilities to audit the adapters and the instances of access nodes that are associated with the type of access node.

  • includes the basic framework for support NETCONF notifications needed in future releases of OB-BAA.

In addition to the new functionality, the OB-BAA distribution can be download as a docker directly from the Broadband Forum's public docker repository.

Finally this release includes additional examples of NETCONF commands that can be used to configure access nodes (OLTs, DPUs, ONTs) including the ability to configure:

  • access node network interfaces along with their associated VLAN tagging (C-VLAN, S-VLAN) and p-bit policies

  • forwarding rules for traffic between the ONU UNI and the OLT NNI

  • traffic descriptors and associated traffic filters for the access node

  • Layer 1 profiles (e.g., G.Fast) and association of the profile to the interfaces


  1. Restriction for TR-385 PON YANG modules: When trying to create a channel partition, the BAA layer returns an error that "An unexpected element channel-group-ref is present". This message is due to the Open Daylight YANG tools component used by the BAA layer. There has been an issue submitted for this problem with the OpenDaylight team.

Release 1.1.0 Highlights:

  • BAA Core Framework Enhancements:

    • Consistency checking within the BAA layer for configuration commands

    • Incorporate the ability to include vendor specific modules and deviations from the common modules per AN type using inline schema mounts.

  • Plugins and Profiles

    • NETCONF Device Adapter Plugins for OLTs and DPUs
  • BAA Layer Administration

    • Device Adapter Management
  • Relevant documentation

    • Examples of requests to the BAA layer and YANG modules for an OLT

Release 1.0.0 Highlights:

  • Framework for the BAA Layer to include:

    • NETCONF/YANG based Southbound Interface

    • NETCONF/YANG based Northbound Interface

    • Persistent management enabled BAA core that allows an Access Node to be configured when they are offline and to be synchronized when connectivity is reestablished.

  • Capabilities to discover and manage an Access Node that includes the ability to:

    • YANG module sets for a type of Access Node

    • Discover an Access Node based on Direct SSH, TR-301 CallHome

    • Create, retrieve, update and delete (CRUD) an Access Node within the BAA layer as well the AN's data

  • Relevant documentation

    • Deployment & Usage instructions

    • Simulator recommendations

    • Examples of requests to the BAA layer and YANG modules for a DPU


A reference implementation for standardized, automated Cloud-based Access Services.




No packages published

Contributors 4



You can’t perform that action at this time.