Table of Contents | ||
---|---|---|
|
Name of Use Case
BBS (Broadband Service)
Use Case Authors
Swisscom, Huawei, Nokia
Note: more participants are welcome
Description
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. We believe that this use case will cover several ONAP components and may also introduce some new platform capabilities by demonstrating:
- 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.
- The HSIA service health is monitored via ONAP's data collection, analytic and closed-loop capabilities
- 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.
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.
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.
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: 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
Action Phases
- Phase 1: CFS creation and activation
- Phase 2: Nomadic ONT (PNF re-registration)
- Phase 3: CFS change / reconfiguration (subscription plan change)
- Phase 4: CFS assurance
Sub-Use Cases
- 3rd party controller registration, RFS catalog discovery / abstract topology discovery
- CFS design and RFS onboarding
- CFS reconfiguration after PNF relocation
- CFS reconfiguration after service change order from BSS
- CFS termination
- CFS assurance (fault detection and self-healing) [stretch goal]
System topology
Full System Context
Short description
Interface | Description |
---|---|
External API/UUI → ESR/AAI | 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. |
External API/UUI ← DCAE | This interface provides the notification of Alarms and Events for the CFS HSIA and ONT health. |
External API/UUI → SO | This interface provides invocation for CRUD (Create, Read, Update, Delete) operations on the CFS HSIA and ONT application layer configuration. |
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 roaming as well as device PnP |
SO → SDN-C | This interface provides orchestration of the CFS HSIA into requisite network services for Access, Edge and Premises. 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, Edge and Premises elements. In addition ONT application layer configuration is provided. |
APP-C → VIM | VNF Life-cycle management of the Domain Specific M&C elements that are virtualized. |
VNF
List of VNFs that the BBS use case will use
[Work in progress]
Location | VNF | Intended VNF Provider | VNF CSAR |
---|---|---|---|
PNF
List of PNFs that the BBS use case will use
[Work in progress]
Location | PNF | Intended PNF Provider |
---|---|---|
NFVI+VIM
[Work in progress]
Location | NFVI+VIM | VIM Provider |
---|---|---|
Work Flows
Topology Discovery
Description:
- Domain specific M&C (Access, Transport, Edge) are registered in ONAP as External Systems (3rd party controller). Domain specific M&C report the abstract topology/service catalog to ONAP
Assumptions:
- Infrastructure (OLT, Transport tunnel, BNG, AAA, DHCP) is 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:
- The External System is registered in ONAP and successfully reports available infrastructure topology (nodes, links, terminal points)
- The available infrastructure topology gets stored in A&AI
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
- Infrastructure (OLT, Transport tunnel, BNG, AAA, DHCP) is configured and provisioned
- 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:
- The CFS HSIA exists and is active before user moves to new location
- New location can provide the same level of service as in the previous location, e.g. fiber access is available. We assume unlimited resources
Success Criteria:
- The CFS HSIA is automatically reconfigured after user moves and plugs ONT in a new location. The customer gets Internet access with the requested rate, quality of service and protection scheme
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:
- The CFS HSIA exists and is active before the customer requests a subscription plan change, e.g. upgrade Internet speed
- The existing CFS HSIA is reconfigured to accommodate the customer request
- We assume unlimited resources
Success Criteria:
- The CFS HSIA is automatically reconfigured according to the requested internet access speed
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]
Project Impact
ONAP Component Usage
[Work in progress]
Project | Usage | Impact |
---|---|---|
SDC | CFS HSIA design | |
SO | CFS HSIA orchestration ONT PNF discovery logic | New BPMN recipe for nomadic ONT case |
Policy | Trigger service reconfiguration due to nomadic ONT event | Support for creating policies during run-time (configuration policies ?) Support new operational policy(s) in CL To be checked: Nomadic ONT: ONSET ok / How can the ABATEMENT be detected? |
SDNC | Integrated with 3rd party controller | New DG for service creation, activation and change |
UUI | ONT to customer association (customer ID) Service health dashboard | BBS custom UI |
A&AI | DM for ONT PNF | A&AI needs to scale to support high number of CFS instances To be checked: A&AI enrichment for control loop look-up |
External APIs | CFS HSIA LCM | |
DCAE | Collect the event data for CFS HSIA health ONT PNF (re-)registration | New Restconf2VES mapping support might be needed To be checked: Can we use PRH for PNF re-registration? |
VF-C/APP-C | ||
Modeling | CFS HSIA model | |
CLAMP | Define nomadic ONT closed loop |
Platform Requirements
- PNF re-registration
- Hybrid (VNF+PNF) service orchestration
- Existing RFS onboarding and association to CFS? e.g. new CFS HSIA associated with existing RFS transport (infrastructure) and RFS Fiber Access (infrastructure)
- ...
Work Commitment
Work Item | ONAP Member Committed to work on BBS |
Modeling | Nokia, Huawei, Swisscom |
SDC | Nokia, Huawei |
SO | Nokia, Huawei |
SDN-C | Nokia, Huawei |
UUI | Swisscom |
DCAE | Nokia, Huawei, Swisscom |
Policy | Nokia, Huawei |
VF-C/APP-C | |
A&AI | Huawei |
External API |
Presentation Materials
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 |
Attachments
Attachments |
---|