Sponsors
Overview
This
Table of Contents | ||
---|---|---|
|
Name of Use Case
BBS (Broadband Service)
Use Case Authors
Swisscom, Huawei, Nokia
Note: more participants are welcome
Description
Theuse 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 (R5)
- The HSIA service modification (e.g. upgrade bandwidth plan) is initiated via ONAP's External APIs and orchestrated using ONAP.
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.
- HSIA service assurance (R5)
- 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
Business Requirements
- Service providers need
Users and Benefits
Service providers benefit from- 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.
Warning | ||
---|---|---|
| ||
Info | ||
---|---|---|
| ||
Documentation on how to set up the use case:
Demo videos: BBS Documentation (Dublin)#BBSServiceConfiguration |
BBS Use Case Presentations
Date | Event | Presentation Material |
---|---|---|
2019.09.25 | Open Networking Summit Europe (ONS Europe) 2019 | |
2019.06.13 | 2019 June LFN DDF & Plugfest | |
2019.04.04 | Open Networking Summit North America (ONS NA) 2019 | |
2019.04.02 | 2019 ONAP Joint Subcommittees Silicon Valley | BBS proposal for ONAP El Alto/Frankfurt release |
2019.02.22 | BBF Q1 Feedback | BBS Status Report |
2018.11.12 | Use Case Subcommittee Meeting | 20181112_BBS Usecase.pptx |
2018.10.29 | Dublin Architecture Planning Meeting | BroadBand_Service_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, SDNC, SO
See Impacts page
Project Commitments
Project | PTL | Commitment | Notes | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AAI |
|
| |||||||||||||||||||||||
CLAMP |
|
Setup of Control Loop for Location change:
| |||||||||||||||||||||||
DCAE |
|
Must have:
| |||||||||||||||||||||||
External API |
| Nice to Have: Support for TMF 638 ServiceStateChangeNotification or ServiceAttributeValueChangeNotifications Note -
| |||||||||||||||||||||||
Policy |
|
| |||||||||||||||||||||||
SDNC |
|
Updates to SDNC DG repository to onboard new DGs developed by BBS team | |||||||||||||||||||||||
SO |
| Dependency: 5G Use Case to develop PNF discovery SO to use SDN-C GR-API for resource creation/deletion
|
Release
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: Cloud-CO-APPN-446: ONAP Integration for HSIA Service (Access) 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)
System topology
- 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 Diagram | ||||
---|---|---|---|---|
|
Gliffy Diagram | ||||
---|---|---|---|---|
|
See BBS Modeling
Full System Context
Anchor | ||||
---|---|---|---|---|
|
Gliffy Diagram | ||||
---|---|---|---|---|
|
Full System Context
Short description
Project Impact
ONAP Component Usage
[Work in progress]
ONT PNF discovery logic
New DG for service creation, activation and change
New DG for ONT location change
Service health dashboard
DM for ONT PNF
Association with subscriber
3rd party controller interfaces for VNFs
CFS HSIA LCM
ONT location change notification
ONT and CFS HSA alarms/notifications
Service modification request (subscription plan change)
ONT PNF (re-)registration
Platform Requirements
Interface | Description |
---|---|
BSS↔ External API |
This interface provides for the Subscriber to ONT association and the registration of the Domain Specific M&C elements (Edge, Access, Premises) that will interface later with SDN-C.
Advertise service catalog to external systems, e.g. BSS, service instance ordering and order status tracking, and service instance state change notifications to external systems. | |
External API ↔ AAI | This interface provides for notification of service instance state changes |
External API ↔ SDC/ |
SO | This interface provides invocation for |
the service catalog, LCM operations on the CFS HSIA |
instances, 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 ↔ SDN-C | This interface supports RFS re-configuration triggered by ONT relocation as well as device PnP |
Policy ↔ AAI | This interface supports CFS 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 |
Work Flows
Topology Discovery
Description:
- Domain specific M&C are registered in ONAP as External Systems (3rd party controller). Domain specific M&C report the abstract topology/service catalog to ONAP
Assumptions:
- Infrastructure (OLTs, Transport tunnels, BNGs, AAA, DHCP) are configured and provisioned.
- Register the 3rd party Access SDN Management & Controller to ESR.
- ESR triggers a 3rd party Controller registration event to DMaaP.
- SDN-C subscribes to the event and gets an event notification.
- SDN-C synchronizes the topology from 3rd party Access SDN M&C.
- SDN-C analyses the data from Access SDN M&C. Gets the nodes, links, terminal points of the topology.
- SDN-C calls A&AI to create the nodes, links terminal points and saves the topology.
Success Criteria:
Note: If multiple Access SDN M&C, there will be several topologies notified. The links across the domain topology should be also discovered
HSIA Service Creation and Activation (includes ONT PnP)
Description:
- The Service Provider provisions Broadband Internet Access Service using ONAP. ONT registration triggers the CFS HSIA provisioning, OLT and PON port are announced with the ONT registration
Assumptions:
- OLT/ONT/BNG related resources already modeled in SDC and distributed in ONAP
- ONT and CPE/RG functions are combined in a single device that can be easily installed by the end customer
- Optical fiber circuit to customer premises exists
- OSS sends the create CFS HSIA request to ONAP External API and sends ONT/RG device to customer
- External API transfers the request to SO.
- SO decomposes the CFS into RFSs
- SO inserts the service information into A&AI and sets service status to 'planned'.
- SO subscribes to ONT PNF registration event and waits for it
- Customer receives ONT/RG device, installs it and powers it on.
- ONT becomes online.
- OLT detects a new ONT and initiates the ONT registration process
- Access SDN M&C reports the ONT registration event to DCAE/PRH
- DCAE/PRH checks if there is an existing PNF entry in AAI for the new ONT and updates the ONT info in AAI
- DCAE/PRH publishes an ONT ready event that is read by SO
- SO continues with the provisioning of the CFS HSIA
- SO via SDN-C triggers the configuration of the ONT and the OLT by the Access SDN M&C
- SO via SDN-C triggers the creation/configuration of the RFS Internet Access (e.g. customer's speed profile)
- SO updates CFS HSIA info in AAI.
- RG becomes online and initiates the CFS HSIA activation procedure
- Access SDN M&C reports via DCAE the successful activation of the RG to SO
- SO updates CFS HSIA status to 'active' in AAI
- SO reports service 'active' status to OSS/BSS via External API
Success Criteria:
- The CFS HSIA order is successfully completed. The customer gets Internet access with the requested rate, quality of service and protection scheme
Note: ONT PnP based on 5G - PNF Plug and Play
Nomadic ONT Service
Description:
- The Service Provider provisions Broadband Internet Access Service using ONAP. One day, the customer moves the ONT to a new location without notifying the SP. The ONT (PNF) will re-register in a new location and ONAP needs to re-provision/reconfigure the customer's broadband service.
Assumptions:
- -
[Work in progress]
Subscription Plan Change
Description:
- Service Provider ONAP provisions Broadband Internet Access Service. The customer needs higher bandwidth Broadband Internet Access Service and request a bandwidth upgrade via the customer portal, the service provider upgrades the already existing Broadband service to the new subscription plan (e.g. 1Gbps to 10Gbps)
Assumptions:
- -
[Work in progress]
HSIA Service Assurance
Description:
- Service Provider ONAP provisions Broadband Internet Access Service. ONAP monitors CFS HSIA service instance KPIs and triggers closed loop policies when a predefined threshold is crossed
Assumptions:
- -
[Work in progress]
. |
Work Commitment
Attachments
attachmentsWork 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 |
Presentation Materials
Huawei (Adrian O'Sullivan - epics) |