Versions Compared

Key

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

Participating Companies

Swisscom, Huawei, Nokia

Note: more participants are welcomeSponsors

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.

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.

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



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, ModelingSDNC, SO

See Impacts page

Project Commitments

ProjectPTLCommitmentNotes
AAI

Status
colour

Yellow

Green
title

open

committed

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1990

WIP: Pending discussion with External API team Update: Using AAI-EVENT topic in DMaaP instead (

/

Jira Legacy
serverSystem Jira

columns

key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-

1996 is not required anymore)APPC

Status
titleNA

No requirements

2154

CLAMP

Status
colour

Yellow

Blue
title

Open

TEST

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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 Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyEXTAPI-98
This EPIC was previously raised to support Service Inventory Notifications with relevant support from A&AI.

ModelingOOF

Status
titleNA

No requirements

Status
titleNA

No requirements
Policy

Status
colour

Yellow

Blue
title

Open

test

  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.
SDC

Status
titleNA

No requirements
SDNC

Status
colour

Yellow

Green
title

Open

COMMITTED

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-614

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


SO

Status
colour

Yellow

Green
title

Open

committed

Assumption

Dependency: 5G Use Case to develop PNF discovery

SO to

support service instance 'modification'

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

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1392

UUI

Status
titleNA

No requirementsVFC Statustitle

NANo requirementsVID

Status
titleNA

No requirementsVNFRQTS

Status
titleNA

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: 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)
    • 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
    nameBBS - Arch Overview
    pagePin16
    Gliffy
    2
    nameBBS - CFS HSIA Model
    pagePin3

    See BBS Modeling 


    Full System Context
    Anchor
    bbs-system-context
    bbs-system-context

    Gliffy
    nameBBS - SystemContext
    pagePin18


    ESR/AAIExternal API
    InterfaceDescription
    BSSExternal API

    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 ← DCAEThis interface provides the notification of Alarms and Events for the CFS HSIA and ONT health [To be confirmed]
    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/SOThis interface provides invocation for the service catalog, LCM operations on the CFS HSIA and ONT application layer configuration and for the 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 ↔ SOSDN-CThis interface supports RFS re-configuration triggered by ONT relocation as well as device PnP
    Policy ↔ AAIThis interface supports service 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&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 elements. In addition ONT application layer configuration is provided.

    VNF

    List of VNFs that the BBS use case will use

    LocationVNFVNF ProviderCommentDatacentervBNG/vAAA/DHCPSwisscom, open sourceConsidered as infrastructure and accessible through 3rd party controller
    (not deployed by ONAP)

    PNF

    List of PNFs that the BBS use case will use

    LocationPNFPNF ProviderCommentCustomer PremisesCPE (ONT+RG)

    Huawei, Nokia

    Accessible through Access SDN M&C (3rd party controller)Central OfficeOLTHuawei, NokiaAccessible through Access SDN M&C (3rd party controller)

    NFVI+VIM

    LocationNFVI+VIMVIM ProviderDatacenterOpenStackSwisscom (OPNFV Fraser)DatacenterAccess SDN M&C (3rd party controller)Huawei, NokiaDatacenterEdge 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

    PolicyNokia (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)