...

Below are the functions of access network needed on top of the infrastructure services that are already provided as part of ONAP.  The requirements for Access will be isolated to the Access Module to not impact the core ONAP capabilities and deliverables.

Terminology

Access network is broken down into central and edge deployments.  Some functions of the control and management will be located centrally and some may be located at the edge in support of access.

Central Compute

• User interfaces in support of access.
  • Common ONAP interfaces (Portal, SDC, VID, OOM, CLAMP, CLI) will be reused
  • UI for Broadband Subscriber Access Network devices and Services
  • Reuse of ElasticStack (Kibana, Log Stash and Elastic Search)
• Reuse of the common ONAP functions (In addition to above - limited to the context of access)
  • AAI
  • DCAE
  • SO 
  • DMaaP
  • AAF
  • Policy
   

...

• Access Network services will operate as containers generally in an edge cloud environment utilizing Docker containers.
• Edge Network services will utilize Kubernetes and K8 models
• Virtualized Access containers will be deployed and lifecycle managed by ONAP core components
• Services provided for the Virtual Access Network will be orchestrated through SO
• VNF Management functions will be controlled by APPC
• Inventory for the access domain will be modeled for AAI
  • Tenant service relationships will be modeled in AAI between OSAM - Control and OSAM - HA
  • Broadband Subscriber profiles will be modeled for AAI
  • AAI will be the DOR for the Broadband Subscriber profiles, but pulled to a domain specific OpenLDAP system
• TOSCA resource models, K8's, Service Models, Images will be created for the OSAM components
• OSAM-UI (Suite of Docker based microservices)
• OSAM-Control (Karaf based Controller)
• OSAM-HA (Suite of Docker based microservices)
  • VOLTHA Core, NETCONF Server, REST Ser 
• FreeRADIUS
• OpenLDAP
• OSAM Collector Agent
• OSAM Analytics Agent 
• Subscriber Broadband Service  
• Access related flows will be modeled in BMPN2 for the SO
• SDC will distribute
  • SDC→SO: Distribute the Service Template(s)
  • SDC→AAI: Distribute the Inventory Model(s)
  • SDC→SDNC: Distribute the network underlay connectivity
  • SDC→APPC: Distribute the Directed Graph(s)
  • SDC→Policy: Distribute the policy Template(s)
    • Initial focus will be limited to Threshold Crossing Analytics
  • SDC→DCAE: Distribute Configuration(s)
  • SDC→DMaaP: Distribute the topic and partition configuration(s) 
• SO Flows
• Add/Update/Remove Broadband Subscriber
• Add/Remove VNFs
• Migrate Broadband Subscriber Services
• Scale Up/Down OSAM-Control and OSAM-HA

OSAM

A work effort in ONAP for bridging the Open Networking Foundation (ONF) work into ONAP. Part of this was to create a higher order UI for the Access Network, Service Models, Work Flows, Policies, etc.  The goal of the project is to build out dependencies for future support of 3rd party virtualized network services for the access network.

...

• Integration of existing Domain specific controller for broadband subscriber services 
• Provides dynamic control & user plane capabilities
• Provides REST/OpenAPI Spec Interfaces
• Provides 802.1X for RADIUS authentication
• Provides the DHCP Proxy and Client Agent
  • This may differ by implementation
• Provides the mapping from the Subscriber to the BNG 
• Log data provided by Kafka. 
  • Data will be mediated through a VES converter (OPNFV) to the DCAE Collector agent  

OSAM-HA

Provides hardware abstraction layer for the physical network device providing modular protocol and device interfaces.  Initial implementation is Open Networking Foundation (ONF) project VOLTHA.

• Integration of existing Domain Specific abstraction layer that provides uniform access to Broadband Access hardware
• Provides REST/OpenAPI Spec and NETCONF/YANG Interfaces/Models
• Log data provided by Kafka. 
  • Data will be mediated through a VES converter (OPNFV) to the DCAE Collector agent  

• VOLTHA hardware abstraction providing disaggregation of many of the functions currently performed by OLT hardware

  • Protocol Abstraction and Multi-Access API uniformity

  • Device persistence

  • Data Harmonization

OSAM-Collector Agent

Collector agent is a instance built off the DCAE collector agent framework. 

...

• Built off of the DCAE collector agent framework
• Receives the VES data from the OSAM-Control and OSAM-HA
• Provides Analytics for Access and interacts with the Policy Framework
• Existing Threshold Crossing analytics and policies will be reused and models will be built to reference a scaling SO developed OSAM 

OSAM-UI

OSAM-UI provides an implementation of a centralized management interface for the access network device and services targeted for edge and deep edge deployments.12

...

• OpenLDAP will store the subscriber authentication and profile information
• SO will interact with OpenLDAP for updating the subscriber data, security and service profiles
• System will be utilized as a reference implementation and not intended for production use
• This functionality is isolated from ONAP capabilities to support scale of the broadband authentication processes

Image RemovedImage Added

Architecture Alignment:

...

...

Contributors:

...