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

System topology

Image Removed

Image Removed

• 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

See BBS Modeling 

Full System Context

Anchor
bbs-system-context bbs-system-context

Full System Context

Image Removed

Work

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 (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:

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

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:

• -

[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

Image Removed

[Work in progress]

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

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

CFS HSIA LCM
ONT location change notification
ONT and CFS HSIA alarms/notifications
Service modification request (subscription plan change)

New VES mapper might be needed
New microservice to detect nomadic ONT move

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)
• ...

Commitment

Attachments

Presentation Materials