Participating Companies
Swisscom, Huawei, Nokia
Note: more participants are welcome
Overview
This use case proposes using ONAP for the design, provisioning, life-cycle management and assurance of broadband services. In a first step, multi-Gigabit Internet Connectivity services based on PON (Passive Optical Network) access technology will be considered. The use case covers new scenarios, such as nomadic ONT (Optical Network Terminal) and service subscription plan changes.
BBS use case shows the extensibility of the ONAP platform in supporting the orchestration of services across different locations (e.g., Central Office, Core) and technology domains (e.g., Access, Edge) within the locations.
In a joint collaboration with BBF (Broadband Forum) members, BBS implements/tests some of the specifications defined in the architectural framework of CloudCO (Cloud Central Office), Technical Report TR-384, among others. CloudCO aims at re-architecting the broadband network using SDN and NFV technologies and a cloud-like infrastructure deployed at Central Offices.
The definition of External API capabilities supporting this use case will be performed in collaboration with TM Forum and MEF LSO.
Dublin Goals
Establishment of a subscriber's HSIA (High Speed Internet Access) service from an ONT to the Internet drain
The HSIA service is designed and deployed using ONAP's design and deployment capabilities
The HSIA service activation is initiated via ONAP's External APIs and orchestrated and controlled using ONAP orchestration and control capabilities. The control capabilities leverage a 3rd party controller to implement the requested action within the technology domain/location represented by the domain specific SDN management and control function.
- Change of location for ONT devices (Nomadic ONT devices)
- PNF (Re-)Registration for an ONT
- Subscriber association to an ONT via ONAP's External APIs
- ONT association with a expected Access UNI (PON port) when a HSIA service is created/deployed for a subscriber
- PNF (Re-)Registration using ONAP's PNF registration capabilities
- Service location modification that is detected by ONAP's analytic and initiated via the closed loop capabilities
- The closed loop capabilities invoke a HSIA location change service that is orchestrated and controlled using ONAP capabilities and 3rd party controllers
- PNF (Re-)Registration for an ONT
- HSIA service subscription plan changes
- The HSIA service modification (e.g. upgrade bandwidth plan) is initiated via ONAP's External APIs and orchestrated using ONAP.
- HSIA service assurance
- The HSIA service health is monitored via ONAP's data collection, analytic and closed-loop capabilities
- The HSIA service health is monitored via ONAP's data collection, analytic and closed-loop capabilities
BBS Use Case Presentations
| Date | Event | Presentation Material |
|---|---|---|
| 2018.10.29 | Dublin Architecture Planning Meeting | BroadBand_Service_BBS_Usecase.pptx |
| 2018.11.12 | Use Case Subcommittee Meeting | 20181112_BBS Usecase.pptx |
BBS Use Case Team Meetings
Weekly Meeting
Day: Thursday
Time: UTC 1200 / China 2000 / Eastern 0800 / Pacific 0500
Duration: 1.5 hours
URL: https://zoom.us/j/735324492
Impacts
The BBS Use Case for Dublin will have impacts on the following projects: AAI, DCAE, External API, Modeling, SO
See Impacts page
Project Commitments
| Project | PTL | Commitment | Notes | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AAI |
|
| |||||||||||||||||||||||||||
| APPC |
| No requirements | |||||||||||||||||||||||||||
| CLAMP |
|
Setup of Control Loop for Location change:
| |||||||||||||||||||||||||||
| DCAE |
|
Must have:
| |||||||||||||||||||||||||||
| External API |
| Nice to Have: Support for TMF 638 ServiceStateChangeNotification or ServiceAttributeValueChangeNotifications Note -
| |||||||||||||||||||||||||||
| Modeling |
| No requirements | |||||||||||||||||||||||||||
| OOF |
| No requirements | |||||||||||||||||||||||||||
| Policy |
|
| |||||||||||||||||||||||||||
| SDC |
| No requirements | |||||||||||||||||||||||||||
| SDNC |
|
Updates to SDNC DG repository to onboard new DGs developed by BBS team | |||||||||||||||||||||||||||
| SO |
| Assumption: 5G Use Case to develop PNF discovery SO to support service instance 'modification'
| |||||||||||||||||||||||||||
| UUI |
| No requirements | |||||||||||||||||||||||||||
| VFC |
| No requirements | |||||||||||||||||||||||||||
| VID |
| No requirements | |||||||||||||||||||||||||||
| VNFRQTS |
| No requirements |
Business Requirements
- Service providers need a flexible platform that integrates Broadband services using standardized APIs towards domain specific management and control systems, e.g. Access domain controller/orchestrator.
- Equipment vendors and systems integrators benefit from well defined, standardized APIs to which they can develop products and services.
- By closely collaborating with Industry consortiums, such as BBF, the BBS use case outcomes will serve as a basis for the definition of new standard interfaces and the evaluation and refinement of existing specifications.
Scope
The work leverages the CloudCO reference architectural framework (TR-384) by implementing the organization's work for integration of CloudCO to ONAP as defined in Cloud-CO-APPN-015: ONAP Integration for HSIA Service (Access). The scope of this use case for the Dublin release includes the implementation of this application note and will demonstrate modification of a subscribers subscription plan. As the Broadband Forum develops additional Broadband Service application notes that are applicable for integration with ONAP, this use case will be extended over time to incorporate the new application notes.
Priorities
Dublin will focus on Broadband Service CFS (Customer Facing Service) design, creation and activation, with support for nomadic ONT. If possible we will also implement the subscription plan change scenario (CFS "modify" action). Enabling CFS service assurance is a stretch goal for Dublin.
Action Phases
- Phase 1: CFS creation and activation [priority for Dublin]
- Phase 2: Nomadic ONT (PNF re-registration) [priority for Dublin]
- Phase 3: CFS change / reconfiguration (subscription plan change) [stretch goal for Dublin]
- Phase 4: CFS assurance [stretch goal for Dublin]
Sub-Use Cases
- 3rd party controller registration, RFS catalog discovery / abstract topology discovery (Phase 1)
- CFS design and RFS onboarding (Phase 1)
- CFS reconfiguration after PNF relocation (Phase 2)
- CFS reconfiguration after service change order from BSS (Phase 3) [stretch goal for Dublin]
- CFS termination [stretch goal for Dublin]
- CFS assurance (fault detection and self-healing) [stretch goal for Dublin]
System topology
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
| Gliffy | ||||
|---|---|---|---|---|
|
Full System Context
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
| Interface | Description |
|---|---|
| External API ↔ ESR/AAI | This interface provides for the notification of service instance state changes and the registration of the Domain Specific M&C elements (Edge, Access) that will interface later with SDN-C [To be confirmed] |
| External API ← DCAE | This interface provides the notification of Alarms and Events for the CFS HSIA and ONT health [To be confirmed] |
| External API ↔ SO | This interface provides invocation for LCM operations on the CFS HSIA and ONT application layer configuration and for the event notification on service instance order status |
| Policy ↔ DCAE | This interface provides closed loop policies for activation of the CFS HSIA and relocation of ONT |
| Policy ↔ SO | This interface supports service re-configuration triggered by ONT relocation as well as device PnP |
| SO → SDN-C | This interface provides orchestration of the CFS HSIA into requisite network services for Access and Edge. The interface also provides a relocation of ONT network service. |
| DCAE ← Domain Specific SDN M&C | This interface provides event collection for Service and ONT health as well as notification of an ONT registration to a new Access attachment interface. |
| SDN-C → Domain Specific SDN M&C | This interface provides the resource facing HSIA services for Access and Edge elements. In addition ONT application layer configuration is provided. |
VNF
List of VNFs that the BBS use case will use
| Location | VNF | VNF Provider | Comment |
|---|---|---|---|
| Datacenter | vBNG/vAAA/DHCP | Swisscom, open source | Considered as infrastructure and accessible through 3rd party controller (not deployed by ONAP) |
PNF
List of PNFs that the BBS use case will use
| Location | PNF | PNF Provider | Comment |
|---|---|---|---|
| Customer Premises | CPE (ONT+RG) | Huawei, Nokia | Accessible through Access SDN M&C (3rd party controller) |
| Central Office | OLT | Huawei, Nokia | Accessible through Access SDN M&C (3rd party controller) |
NFVI+VIM
| Location | NFVI+VIM | VIM Provider |
|---|---|---|
| Datacenter | OpenStack | Swisscom (OPNFV Fraser) |
| Datacenter | Access SDN M&C (3rd party controller) | Huawei, Nokia |
| Datacenter | Edge SDN M&C (3rd party controller) | Swisscom |
Work Commitment
Work Item | ONAP Member Committed to work on BBS |
Modeling | Nokia (Stavros Kanarakis, Tim Carey - epics), Huawei (Victor Gao - epics), Swisscom |
SDC | Nokia, Huawei |
SO | Nokia (Tamas Lendvay - epics), Huawei (Victor Gao - epics) |
SDN-C | Nokia (Stavros Kanarakis - epics), Huawei (Victor Gao - epics) |
UUI | |
DCAE | Nokia (Tamas Lendvay - epics), Huawei (Xin Miao - epics), Swisscom |
| Policy | Nokia (Tamas Lendvay - epics), Huawei (Xin Miao - epics) |
VF-C/APP-C | |
A&AI | Huawei, Nokia (Stavros Kanarakis - epics) |
External API | Huawei (Adrian O'Sullivan - epics) |