Open Broadband-Broadband Access Abstraction (OB-BAA)

Standardized, Automated Deployment for Cloud-based Access Services

Overview

Broadband Access Abstraction under BBF’s Open Broadband initiative is an open source project that specifies:

  • Northbound Interfaces (NBI)
  • Core Components
  • Southbound Adaptation Interfaces (SAI)

for functions associated with the access network devices (e.g., configuration, reporting, alarms) that have been virtualized. 

Inherent in the OB-BAA project is the ability to pull differing access device types, including legacy implementations, together under a single network and service management &control umbrella to be exposed to management elements such as the SDN Management and/or Control and Element Management Systems.

The OB-BAA project is designed to be deployed within the BBF's CloudCO environment as one or more virtualized network functions (VNFs). Because the NBI and SAI utilize standardized data models and the Core components of the OB-BAA project are designed as virtualized micro-services with specified interfaces, the components of the OB-BAA project can also be adapted and deployed in other virtualized environments.

What makes OB-BAA different?

The layered architecture diagram on the right shows how BAA enables independence of the north and southbound implementations. This removes the need for difficult deployment planning by decoupling the device and software implementation choices from business and market conditions. i.e., it facilitates service provider choices for local or system-wide implementation, migration, co-existence based on market demand, RoI, resources, etc.

The Need for an Open Access Abstraction

Virtual network functions (VNFs) deployed on generic computing infrastructure, interconnected by a generic switching fabric with Access and Edge Network Elements.

What controls the interaction to the Access Nodes is Access SDN Manager & Controller and BAA layer

BAA and CloudCO

While both BAA and cloudCO are truly independent and free-standing applications, BAA fits exactly into the cloudCO architecture as one of many CloudCO use cases. The BAA layer integrated into the CloudCO Framework (TR-384) is shown in the diagram on the right.

The benefits

 

For the Service Provider

  • Standard compliant NBIs (e.g. WT-411, WT-413 for BAA) provide SPs with interface contract Southbound of their OSS that is vendor and environment agnostic.
  • Standard compliant SBIs (e.g., TR-355) provide interoperable interfaces toward network elements
  • Enables the migration of legacy access nodes into the new management ecosystem.
  • Abstract interfaces (North and South) provide exposure of functions regardless of the interfacing protocol.

For Equipment Manufacturers

  • Equipment vendors are able to limit the number of different interfaces they have to support to integrate into a Service Provider network.
  • Abstract interfaces (North and South) provide isolation of Core functionality from protocols and interfaces that change over time.
  • Vendors can use and extend the software with additional features and interfaces allowing them to differentiate themselves.