You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Project Name:

  • Proposed name for the project: OpenSource Access Management
  • Proposed name for the repository: osam

Project description:

OpenSource Access Management is a vendor agnostic operation suite for managing consumer broadband network elements and capabilities disaggregated from proprietary monolithic Access Network hardware and Element Management Systems (EMS).

A key component to simplify multi-vendor support is a mediation layer currently under development called VOLTHA (ONF open source project).  VOLTHA uses low-level abstraction of the network device to provide a simplified approach to higher level management and analytics.  Currently xPON and G.FAST are the initial products under active development in collaboration with ONF. 

Scope:

Describe the functionality to be provided by the project.  Please provide the full intended scope of the project; not just what is intended for the project's first release.

OpenSource Access Manager is a domain specific module for ONAP consisting of the OA&M User interface, flows, web services and microservices in support of virtualized multi-access network for consumer broadband services.  At a high level it divides into global and localized functions to operate at large scale and performance for edge networks.  The major components of Access Module that do not exist in ONAP today are the user interface (UI), the carrier grade access controller and hardware abstraction though VOLTHA.  Access specific data models, services and flows will be built on existing ONAP components and may feed additional requirements.  The infrastructure elements, services, flows, data collection processes will be utilized and existing or planned feature sets should not be impacted.

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.


Global Functions for Access

OA&M user interface (UI) for operational support of the Access Network

o   Visualization utilizing Grafana and ElasticStack

Java Service Container (JSC)

o   High level APIs created for subscriber service instantiation

Direct Messaging Engine (DME)

o   Handles message routing to the localized JSC

 Active and Available Inventory (AAI)

o   Data Store models and services to be extended for Access Network Models covering the physical network, facilities, ports, subscriber services and profile information.

Global Services will interact with the MSO, DMaaP and DCAE

Scheduler for planning of updates to system services and access devices

CLAMP for closed loop automation in the context of the Global resources

Directed Graphs/Node-Red for global service flows (TBD)



 Local Functions for Access


Java Service Container (JSC)


o   Low level APIs created for subscriber service instantiation


Directed Graphs/Node-Red for local service flows


Access Application


o   vAccess Related tenants


VOLTHA Hardware Abstraction for access devices


Active and Available Inventory (AAI)


o   Federated data store for access network data


FreeRADIUS for subscriber 802.1x authentication

All Components will feed data into DMaaP/DCAE


 


Operational User Interface Functionality:


       Pulls resources, interfaces and data elements from ONAP, DCAE and JSC into a cohesive interface supporting the Access Network Infrastructure.

      Configure settings exposed by API against 1 or more devices and services

      Ability to bulk execute a list of devices against exposed services including (Node-Red/Directed Graphs)

o   Services directly imported into interface once deployed

  A view of error details for functions/devices streaming with related hot links into the low level details (e.g. Abstraction Layer, OLT, Port, ONU, ONU Uplink Port, ONU UNI Ports, DPU,   CPE, MicroServices, and future components)


    • Advanced text and regular expression based filters based on device names or event details
    • Time range based filters



       Customizations


o   Customizations by a user, group or system level


o   Context sensitive interface changes driven by exposed APIs


o   Ability to store and share views


o   Ability for a user to load multiple views at the same time


       Single application for Network visualization with integrated  analytics from DCAE, Elastic Stack and Grafana


o Operational dashboard showing geographic distribution of the network and services health (“Heat Map”)

o  Established links between devices/service management and the graphical representations


       Interface for scheduling and coordinating access related devices and software


o   Firmware Release Management and Upgrades


o   Snapshot management of Access devices and configurations


§  This will be utilized for comparison, restoral and migration activities


o   VNF Service Versioning Management at a collection or subscriber level


o   User Migration flows in coordination with Firmware and VNF release management


o   Rollback and notification under failure conditions or forced action


o   Ability to create collections of subscribers, VNFs, and devices


o   Configurable Maintenance Window


o   Ability to operate in serial or parallel at the collection level


o   Ability to establish dependencies prior to execution


       Support for systems, network, software, service and configuration segmentation (slicing)


o   Can be configured by Global, Site, DMA, Service Type or Device Type and each being subdivided by Release Type


o   Support different lifecycle states of software, firmware and configuration within


§  Examples Crawl, Walk, and Run methodology of deploying changes


§  Examples Development, Test, Incubation, and Production state of services


o   Software Versions, Firmware, Policies, and configurations should be configured as a package


§  Deployed for a specific set of hardware


§  Ability to manage hierarchical configuration management and version controlled


o   Tool for viewing historical changes, comparison, events, and health of a segment



Service Engines and Message Routing for the Access Network:


  • Application Interfaces exposed to north bound systems are simplified to Create, Read, Update and Delete (CRUD) functions for subscriber associated services
  • Global
    • Provides the high level APIs that span multiple local sites and interactions with the centralized ONAP sites
    • The Message routing will be planned to be built on the ONAP’s Direct Messaging Engine (DME)
    • The service engine will be planned to be built on the ONAP JSC Service Framework
    • Global Access Network Related Flows will be built utilizing Directed Graphs
    • Provides data caching and on-demand fetch of data elements on ONAP and Local Access Services


§  APIs can be setup with a cache, lifespan and scope (user/group/all)


      • Cache will reload using an on-demand fetch update model
  • Local
    • Exposes the mid-level APIs to be utilized for the Edge devices and services
    • The service engine will be planned to be built on the ONAP JSC Service Framework
    • Local Access Network Related Flows will be built utilizing Directed Graphs
    • JSC will be the point of entry from the global sites for service instantiation flows


Data Store consists of the data store for the access subscriber data. Functionality:


Object based storage system built on existing OpenSource Object Storage technology deployed for ONAP Inventory system AAI.


Isolation of data from the AAI in order to ensure subscriber data stores do not impact ONAP operations and to limit subscriber data access


Hierarchical and horizontal scalability to support billions of subscribers and access elements (physical and virtual)


o   Subscriber Information, Security and Polices


§  This information will likely be stored in an existing BSS when integration into a carrier network, but will be needed for ONAP implementation


o   Physical plant assets


o   Access Physical and Virtual Infrastructure and Service components


o   Subscriber Services and Service Chains


 


Components utilized from Open Networking Foundation (ONF) project


Access Application and Tenants


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


 o   Protocol Abstraction and Multi-Access API uniformity


o   Device persistence


o   Data Harmonization


 


Other components


Message Bus for event and counter collection


RADIUS for authentication by the fixed access network


o   Integrated through a module within the access network controller.


VES data collection agents in Application Containers to provide system analytics to DCAE


o   Events will be allocated to different DMaaP topics and partitions based on model driven classification to improve efficiency of event processing by Closed loop


Nagios for System, VM and Container Alerting and Monitoring


Zero Touch Provisioning flows are being defined and will be added to the scope of this document and will impact several components of both the Access Module and ONAP [TBD]


Access services, models and flows will be part of an Access module that are deployable on top of the ONAP framework with impacting the core ONAP requirements and functionality.




Global Functions for Access

·        OA&M user interface (UI) for operational support of the Access Network

o   Visualization utilizing Grafana and ElasticStack

·        Java Service Container (JSC)

o   High level APIs created for subscriber service instantiation

·        Direct Messaging Engine (DME)

o   Handles message routing to the localized JSC

·        Active and Available Inventory (AAI)

o   Data Store models and services to be extended for Access Network Models covering the physical network, facilities, ports, subscriber services and profile information.

·        Global Services will interact with the MSO, DMaaP and DCAE

·        Scheduler for planning of updates to system services and access devices

·        CLAMP for closed loop automation in the context of the Global resources

·        Directed Graphs/Node-Red for global service flows (TBD)

Local Functions for Access

·        Java Service Container (JSC)

o   Low level APIs created for subscriber service instantiation

·        Directed Graphs/Node-Red for local service flows

·        Access Application

o   vAccess Related tenants

·        VOLTHA Hardware Abstraction for access devices

·        Active and Available Inventory (AAI)

o   Federated data store for access network data

·        FreeRADIUS for subscriber 802.1x authentication

·        All Components will feed data into DMaaP/DCAE

  • No labels