Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
stylesquare

Name of Use Case

BBS (Broadband Service)

Use Case Authors

Swisscom, Huawei, Nokia

Note: more participants are welcome

Description

Sponsors

SwisscomImage Added    HuaweiImage AddedNokiaImage Added

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.

 We believe that this use case will cover several ONAP components and may also introduce some new platform capabilities by demonstrating:

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

  1. Establishment of a subscriber's HSIA (High Speed Internet Access) service from an ONT to the Internet drain

    1. The HSIA service is designed and deployed using ONAP's design and deployment capabilities

    2. 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
  1. Change of location for ONT devices (Nomadic ONT devices)
    1. PNF (Re-)Registration for an ONT
      1. Subscriber association to an ONT via ONAP's External APIs
      2. ONT association with a expected Access UNI (PON port) when a HSIA service is created/deployed for a subscriber
      3. PNF (Re-)Registration using ONAP's PNF registration capabilities
    2. Service location modification that is detected by ONAP's analytic and initiated via the closed loop capabilities
      1. The closed loop capabilities invoke a HSIA location change service that is orchestrated and controlled using ONAP capabilities and 3rd party controllers 
  2. HSIA service subscription plan changes (R5)
    1. The HSIA service modification (e.g. upgrade bandwidth plan) is initiated via ONAP's External APIs and orchestrated using ONAP.

BBS. Subscription plan change and Nomadic ONT scenariosImage Removed

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
  1. HSIA service assurance (R5)
    1. The HSIA service health is monitored via ONAP's data collection, analytic and closed-loop capabilities

Image Added

Image Added

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.


Warning
titleBBS in Frankfurt release

BBS Broadband Service Use Case (Frankfurt)


Info
titleBBS Documentation

Documentation on how to set up the use case: 

Demo videos: BBS Documentation (Dublin)#BBSServiceConfiguration


BBS Use Case Presentations

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

Meeting Minutes

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

ProjectPTLCommitmentNotes
AAI

Status
colourGreen
titlecommitted

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-1990
/
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-2154

CLAMP

Status
colourBlue
titleTEST

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCLAMP-270

Setup of Control Loop for Location change:

  • configure DCAE µS that detects location change
  • configure policy that trigger re-config 
DCAE

Status
colourGreen
titleCOMMITTED

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-1057

Must have:

  • Restconf2VES mapper (TechM commitment)
  • Restconf collector microservice (Huawei commitment)
  • RG activation microservice (Nokia commitment)


  • PRH microservice needs to trigger policy (Nokia commitment)
External API

Status
colourGreen
titleCOMMITTED

Nice to Have: Support for TMF 638 ServiceStateChangeNotification or ServiceAttributeValueChangeNotifications

Note -

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyEXTAPI-98
This EPIC was previously raised to support Service Inventory Notifications with relevant support from A&AI.

Policy

Status
colourBlue
titletest

  1. APEX modification to support CLAMP at control loop design time;
  2. Support BBS/ONT Nomadic ONT policy modeling at design time
  3. Apex policy distribution, deployment execution.
SDNC

Status
colourGreen
titleCOMMITTED

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-614

Updates to SDNC DG repository to onboard new DGs developed by BBS team


SO

Status
colourGreen
titlecommitted

Dependency: 5G Use Case to develop PNF discovery

SO to use SDN-C GR-API for resource creation/deletion

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-1392



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 assuranceassurance [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 termination
  • CFS assurance (fault detection and self-healing) [stretch goal for Dublin


System topology

Image Removed

Gliffy Diagram
nameBBS - Arch Overview
pagePin6
Gliffy Diagram
nameBBS - CFS HSIA Model
pagePin3

See BBS Modeling Image Removed


Full System Context

Image Removed

Short description

Anchor
bbs-system-context
bbs-system-context

Gliffy Diagram
nameBBS - SystemContext
pagePin8


/UUI → ESR/AAI
InterfaceDescription
BSSExternal 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.

External API/UUI ← DCAEThis interface provides the notification of Alarms and Events for the CFS HSIA and ONT health.
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/External API/UUI → SOThis interface provides invocation for CRUD (Create, Read, Update, Delete) the service catalog, LCM operations on the CFS HSIA and ONT application layer configuration.instances, event notification on service instance order status
Policy ↔ DCAEThis interface provides closed loop policies for activation of the CFS HSIA and relocation of ONT
Policy ↔ SDN-CThis interface supports RFS re-configuration triggered by ONT relocation as well as device PnP
Policy ↔ SOAAIThis interface supports service CFS re-configuration triggered by ONT roaming 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 and Premises. The interface also provides a relocation of ONT network service.

DCAE ← Domain Specific SDN M&CThis 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&CThis interface provides the resource facing HSIA services for Access , and Edge and Premises elements. In addition ONT application layer configuration is provided.APP-C → VIMVNF 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]LocationVNFIntended VNF ProviderVNF CSAR

PNF

List of PNFs that the BBS use case will use

[Work in progress]

LocationPNFIntended PNF ProviderSiteONTHuawei

NFVI+VIM

[Work in progress]

LocationNFVI+VIMVIM 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. 

Image Removed

  1. Register the 3rd party Access SDN Management & Controller to ESR.
  2. ESR triggers a 3rd party Controller registration event to DMaaP.
  3. SDN-C subscribes to the event and gets an event notification.
  4. SDN-C synchronizes the topology from 3rd party Access SDN M&C.
  5. SDN-C analyses the data from Access SDN M&C. Gets the nodes, links, terminal points of the topology.
  6. 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)

    ONT Discovery (PnP)Image Removed

    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

    Image Removed

    1. OSS sends the create CFS HSIA request to ONAP External API and sends ONT/RG device to customer
    2. External API transfers the request to SO.
    3. SO decomposes the CFS into RFSs
    4. SO inserts the service information into A&AI and sets service status to 'planned'.
    5. SO subscribes to ONT PNF registration event and waits for it
    6. Customer receives ONT/RG device, installs it and powers it on.
    7. ONT becomes online.
    8. OLT detects a new ONT and initiates the ONT registration process
    9. Access SDN M&C reports the ONT registration event to DCAE/PRH
    10. DCAE/PRH checks if there is an existing PNF entry in AAI for the new ONT and updates the ONT info in AAI 
    11. DCAE/PRH publishes an ONT ready event that is read by SO
    12. SO continues with the provisioning of the CFS HSIA
    13. SO via SDN-C triggers the configuration of the ONT and the OLT by the Access SDN M&C
    14. SO via SDN-C triggers the creation/configuration of the RFS Internet Access (e.g. customer's speed profile)
    15. SO updates CFS HSIA info in AAI.
    16. RG becomes online and initiates the CFS HSIA activation procedure
    17. Access SDN M&C reports via DCAE the successful activation of the RG to SO 
    18. SO updates CFS HSIA status to 'active' in AAI
    19. 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

    Image Removed

    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

    Image Removed

    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

    Image Removed

    [Work in progress]

    ProjectUsageImpactSDCCFS HSIA designSOCFS HSIA orchestration
    ONT PNF discovery logicNew BPMN recipe for nomadic ONT casePolicyTrigger 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?

    SDNCIntegrated with 3rd party controller

    New DG for service creation, activation and change
    New DG for ONT location change

    UUIONT to customer association (customer ID)
    Service health dashboardBBS custom UIA&AI

    DM for ONT PNF
    Association with subscriber
    3rd party controller interfaces for VNFs

    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
    ONT location change notification
    ONT and CFS HSIA alarms/notifications
    Service modification request (subscription plan change)

    DCAECollect the event data for CFS HSIA health
    ONT PNF (re-)registration

    New Restconf2VES mapping support might be needed
    Support to be added to detect nomadic ONT move and build DCAE_CL_Event to trigger Policy to modify the existing services.

    To be checked: Can we use PRH for PNF re-registration?

    VF-C/APP-CModelingCFS HSIA modelCLAMPDefine 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

    Attachments

    attachments

    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

    Swisscom


    DCAE

    Nokia (Tamas Lendvay - epics), Huawei (Xin Miao - epics), Swisscom

    PolicyNokia (Tamas Lendvay - epics), Huawei (Xin Miao - epics)

    VF-C/APP-C


    A&AI

    Huawei, Nokia (Stavros Kanarakis - epics)

    External API

    Huawei

    Presentation Materials

    DateEventPresentation Material2018.10.29Dublin Architecture Planning MeetingBroadBand_Service_BBS_Usecase.pptx2018.11.12Use Case Subcommittee Meeting20181112_BBS Usecase.pptx

    (Adrian O'Sullivan - epics)