Name of Use Case

BBS (Broadband Service)

Use Case Authors

Swisscom, Huawei, Nokia

Note: more participants are welcome

Description

The use case proposes using ONAP for the design, provisioning, life-cycle management and assurance of broadband services. As a first step, multi-Gigabit Internet Access services based on PON (Passive Optical Network) 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 different ONAP components and may also introduce some new platform capabilities by demonstrating:

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

Sub-Use Cases

System topology

Full System Context

Short description

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. 

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)

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 

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:

• -

[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]

Project Impact

ONAP Component Usage

[Work in progress]

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

Presentation Materials

Attachments