Project Name:
Proposed name for the project: OpenSource Access Manager
Proposed name for the repository: osam
| Child pages (Children Display) |
|---|
...
Description:
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.
Scope:
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.
...
- 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.
OSAM ARCHITECTURE
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
OSAM core will be designed as a VNF. It consists of
...
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
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.
...
Caches the PNFId, location and Ip address information. In any OSAM GW failure can recover each other by using distributed cache.
OSS/BSS
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.
Impacts:
ONAP Components:
| Component | Effort | Project Impacts |
|---|---|---|
| Active and Available Inventory (AAI) | Maybe some model will be kept here | TBD |
| Application Authorization Framework | Define application roles and access | No Impacts |
| Application Controller (AAP-C) | Directed Graphs | 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 |
| Documentation | ||
| External API Framework | TBD | |
| Holmes | Existing Structure might be reused. | No Impact |
| Integration | 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 | No Impacts |
| 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 |
...
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
How does this project fit into the rest of the ONAP Architecture?.
- 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.
How does this align with external standards/specifications?
- Alignment with the ONF, OpenAPI, BBF, IETF and ITU Standards
Are there dependencies with other open source projects?
- Integration with the VOLTHA and SEBA projects in ONF
Resources:
- Primary Contact Person: Sumithra Bhojan (sb4846@att.com)
- Names, gerrit IDs, and company affiliations of the committers
...
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
- Vendor Neutral
- Meets Board policy (including IPR)
...