- Flows for OSAM
- Models for OSAM
- OSAM Integration Test Case
- OSAM Meetings
- OSAM UI Requirements
- OSAM Use Case Tracking (Casablanca Release)
- OSAM User Stories
OpenSource Access Manager 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.
For Casablanca, OSAM will showcase the management of the Access Peripheral POD (located in Telco Central Offices) as a PNF. Should provide monitoring capability and support 100’s of thousands of Access Peripheral POD deployment in Telco office.
Subscriber management/activation will be contained within the POD and outside the scope of ONAP.
OpenSource Access Manager 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). 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.
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.
OSAM use case will use the similar approach to 5g use-case. OSAM consists of three components which are OSAM Gateway, OSAM Core, and SEBA. OSAM Gateway and OSAM Core and SEBA will be onboard as a service to ONAP.
- OSAM Core and OSAM Gateway will be onboarded as a VNF
- SEBA will be onboarded as a PNF
- Services will be defined for OSAM CORE and OSAM Gateway
- Another service will be defined for SEBA as a PNF and OSAM Gateway as an alloted Resource
- Auto-scaling based on fault and/or performance will be done through OSAM Gateway and OSAM Core services.
ONAP will perform the following functions for OSAM use-case which are;
- Robust environment
- Sharing different resources on different services
- Overview of the OSAM topology (From OSAM UI)
- Storage for SEBA configuration
- Service Provisioning
Users and Benefit:
Operators benefit from OSAM use case in the following aspects:
- service agility: more easy design of both VNF, PNF and network service, VNF onboarding, PNF onboarding, and agile service deployment.
- resource efficiency: through ONAP platform, the VNF resources can be utilized more efficiently, as the services which contain the OSAM Core or OSAM gateway, are deployed and scaled automatically on demand.
- operation automation and intelligence: through ONAP platform, especially integration with DCAE and policy framework, OSAM Core and OSAM Gateway VNFs and the services as a whole are expected to be managed with much less human interference and therefore will be more robust and intelligent.
It currently has 5 main modules which are SEBA, ONAP, OSS/BSS, OSAM Gateway and OSAM Core.
OSAM is addressed as PNF model of 5G use case. In 5G use case, CU and DU pairs are used. In our OSAM case, we are going to use the similar approach. SEBA is going to be mapped as DU. OSAM GW(Gateway) is going to be mapped as CU.
OSAM core will be designed as a VNF. It consists of
- OSAM UI
- OSAM DB
- Portal Service Layer
- Service Flow Manager
- GW Locator
- OSAM GW Adaptor Layer
OSAM Core is responsible for taking the required actions from OSAM UI or OSS/BSS inputs. These actions are related to technology profile management, ONT/OLT management, topology management, fcaps and subscriber management. OSAM core applies set of actions to SEBA through OSAM GW.
- OSAM UI
Technology profile management, subscriber information, service activation for the subscriber, alarm/event monitoring, ONT/OLT management and monitoring are applied from UI. OSAM UI has fully interacted with Portal Service Layer which provides PNF information and data such as technology profiles, subscribers information, ONT devices information, and OSAM network topology. In other words, Portal Service Layer provides a backend for OSAM UI with its API and callback interfaces.
- OSAM DB
OSAM DB is responsible for storing OSAM related data such as:
- Subscriber information and its relation with PNF
- Id, Ip and Location information are going to be stored for **PNF**
- OSAM Gateway information
- PNF relation with OSAM gateway
- OLT information and its relation with PNF
- ONT information(Serial Number)
- Technology profiles and their relationship with the subscriber
- OSAM topology
- Subscriber information with its relation with PNF and technology profile is going to be stored
- Alarms, events, and metrics(will be fetched from ONAP)
- Portal Framework
Portal Framework is the backend for the OSAM UI and OSS/BSS. Provides APIs and callbacks to OSAM UI and OSS/BSS. Technology profile management, ONT/OLT management, subscriber management and subscriber's service purchase operations are conveyed from Portal Framework to Service Flow Manager. PNFs(SEBAs) information and their relation with OSAM gateways are collected from GW Locator to show on OSAM UI.
- Service Flow Manager
Service Flow Manager is the coordinator module for OSAM Core. Service Flow Manager can be triggered by Portal Framework or OSAM Gateway. It decides how the incoming/outgoing requests are going to be applied or conveyed. It applies requested set of actions to OSAM DB or OSAM GW Adaptor layer. Service Flow Manager uses OSAM DB for storing information or configurations related to subscriber, ont/olt or technology profile and creating the relationship between subscriber information and pnfId. OSAM GW Adaptor layer is used for sending the information to PNF.
- GW Locator
GW Locator is responsible for locating PNFs of OSAM gateway. PNFId plays a critical role for Service Flow Manager. Also, PNF information and its relation with OSAM gateway are saved by GW Locator. PnfId, OSAM Gateway ip address and user credentials for authentication plays a mandatory role for PNF storage in OSAM DB. OSAM GW Adaptor Layer can callback to GW Locator to store OSAM Gateway and connected PNFs relation.
- OSAM GW Adaptor Layer
OSAM GW Adapter Layer is the communication layer between OSAM Core and OSAM Gateway. It interacts with GW locator and OSAM GW API services. The interaction between OSAM Gateway and Adapter Layer needs to be bidirectional. GRPC protocol is a good candidate for this purpose. Adapter Layer conveys registered technology profiles, subscriber information and ont registration. (Can be expanded more) to OSAM Gateway from Service Flow Manager. Osam Gateway Adapter layer learns osam gateway ip address from GW Locator using pnfId.
OSAM Gateway is another VNF running near the SEBA pods that can be implemented within the POD as a local OSAM function. OSAM Gateway is a bridge between SEBA and OSAM core.
In OSAM use case, every SEBA(PNF) pod must be matched with OSAM Gateway. OSAM Gateway can connect to multiple SEBA pods. SEBA's bridge gateway(OSAM GW) will be decided by ONAP side. OOF module chooses OSAM Gateway according to location input parameters in ONAP runtime.
- OSAM Core Adaptor Layer
Provides a northbound interface to OSAM Core.
API interfaces should provide the following:
- Retrieve ONT devices for PnfId
- Retrieve OLT devices for PnfId
- Delete OLT device
- Disable ONT device
- Configure Access Node(OLT/ONT)
- Subscriber information and their statuses from PNF
- Telemetry data per Subscriber and SEBA pod
- Service Profile management(Ex: technology profile)
The callback should provide the following:
- ONT, OLT and subscriber alarms
- SEBA deregistration alarm
- ONT, OLT and subscriber events
- OSAM GW Coordinator
The coordinator is responsible to deliver NEM Adaptor requests to OSAM Core adaptor and vice versa. Moreover, it decides the callback action for PM requests(etc) from NEM adaptor Layer. Such as, if telemetry data is received from SEBA. It sends to Ves Agent. If SEBA register request is received, it stores the request in distributed cache and conveys the request to OSAM core via OSAM Core Adaptor Layer. Addition to that if any request is received from OSAM Core Adaptor Layer, converts to SEBA's GRPC
format and delivers the message to SEBA pod.
- Ves Agent
Delivers telemetry data to ONAP from Ves Agent. This module is also responsible for sending telemetry data for connected SEBA pods(PNFs) as well.
- NEM Adaptor Layer
Connection point to SEBAs. It provides a GRPC callback and APIs to communicate with multiple SEBAs.
SEBA api interface should provide the following APIs:
- AccessNode Inventory Information
SEBA callback interface should provide the following:
- SEBA PoD Registration
- Broadband Service Activation
- Distributed Cache
Caches the PNFId, location and Ip address information. In any OSAM GW failure can recover each other by using distributed cache.
Technology service order for a user is done from OSS/BSS.
OSAM Design Time In ONAP
- OSAM Core and OSAM Gateway are going to onboard as a VNF. VNFD is needed to be prepared for each
- SEBA is going to be onboard as a PNF. PNFD is needed to be prepared.
- OSAM needs three services for working full functionally.
- OSAM Core VF resource will be used for OSAM Core service.
- OSAM Gateway VF resource will be used for OSAM Gateway service. (In other use-cases OSAM Gateway might be in the SEBA Pod)
- For SEBA service, SEBA PNF and OSAM Gateway as an alloted resource will be used.
|Active and Available Inventory (AAI)|
Maybe some model will be kept here
|Application Authorization Framework||Define application roles and access||No Impacts|
|Application Controller (AAP-C)|
|No Core APP-C Impacts|
|Closed Loop Automation Management Platform (CLAMP)|| CLAMP will be utilized to view and manage the automation flows|
Interface CLAMP from OSAM-UI (Future Release)
|No Core CLAMP Impacts|
|Command Line Interface||No Impacts|
|Common Controller Developer Kit (CCDK)||Used by SDNC and APPC||No Core CCDK Changes|
|Data Collection Analytics and Events (DCAE)||OSAM Core, OSAM GW and SEBA alerts and events will be sent to DCAE||No Core Impacts to DCAE|
|Data Movement as a Platform (DMaaP)||Topic and Partition Creation||No Core DMaaP Impacts|
|External API Framework||TBD|
|Holmes||Existing Structure might be reused.||No Impact|
|Logging Enhancements Project||No Impact|
|Microservices Bus||Not Used||No Impact|
|Modeling||OSAM specific models may be needed||Small impact for models|
|Multi-Cloud (VIM)||Used for installation of OSAM GW and OSAM Core||No Impacts|
|ONAP Operations Manager (OOM)||Docker/Kubernetes Container Management for ONAP||No Impacts|
|Optimization Framework||Will be utilized to select OSAM GW for SEBA pod||TBD|
|Policy Framework||Existing structure will be used|
|Portal Platform||Portal Interface to the DSC and Hardware Abstraction utilizing the Portal SDK||TBD|
|Service Design and Creation (SDC)||Development of the Rules, Recipes, Flows, Models, Policies and Services for virtualized Access|
OSAM team will attend SDC planned training.
No expected impacts to the SDC Project itself in Beijing.
|Virtual Infrastructure Deployment (VID)||VID will be utilized for the management of applications.|
Interface VID from OSAM-UI
|No VID Impacts|
|SDNC||Existing 5G use case flow will be reused.|
No Core SDNC Impacts
|Service Orchestration (SO)||Orchestration of Access Device and Service instantiation and updates||No Core Impacts|
Since the OSAM use-case is similar to 5G use-case, most impacts will be common. However, some specific design materials (such as PNFD, VNFD, configuration ) will be different due to the nature of OSAM.
Provide OSAM Core, OSAM Gateway, and SEBA specific models
Modeling will need to be added to describe how OSAM Core and OSAM Gateway VNFs are to be instantiated, removed, healed (restart, rebuild), scaled, how metrics related are gathered, how events are received.
Modeling will need to be added to describe the connection between OSAM Gateway and SEBA, plus OSAM Gateway and OSAM Core.
Design OSAM Gateway, OSAM Core and SEBA network service, TOSCA based. VNF and PNF templates will be provided by OSAM community
Design Auto-healing policy for OSAM Core and OSAM Gateway
Design or provide ansible script for PNF
- Access Management will leverage the PNF management approach and existing infrastructure components (AAI, DME, JSC, and Directed Graphs).
- Access Network Models, Flows and API’s will be developed as part of the project.
- Alignment with the ONF, OpenAPI, BBF, IETF and ITU Standards
- Integration with the VOLTHA and SEBA projects in ONF
- Primary Contact Person: Sumithra Bhojan (firstname.lastname@example.org)
- Names, gerrit IDs, and company affiliations of the committers
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
- link to seed code (if applicable)
- Vendor Neutral
- Meets Board policy (including IPR)