Topology Discovery

Description:

• Domain specific M&C (Access, 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. 

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

1. Customer orders HSIA service through BSS portal. BSS registers CPE info and posts the device to the customer address.
2. BSS/OSS sends a CFS HSIA service instance creation request to ONAP External API including BSS's external ID for the new service instance, service type ID in ONAP catalog, HSIA and CPE attributes 
3. External API triggers a service instance create in SO.
4. SO decomposes the CFS into RFSs
5. SO inserts the service information into A&AI and sets service instance orchestration status to 'planned'.
6. SO subscribes to CPE (ONT) PNF registration event and waits for it
7. Customer receives CPE device, installs it and powers it on.
8. CPE (ONT) becomes online.
9. OLT detects a new CPE (ONT) and initiates the ONT registration process
10. Access SDN M&C reports the ONT registration event to PRH using a VES event message that includes additional fields, such as PON UNI (OLT attachment port) and AccessID (ID for OLT-ONT pair)
11. PRH checks if there is an existing PNF entry in AAI for the new ONT associated with a non-active service instance and updates the received PNF info in AAI, including the PON UNI in the Attachment Point
12. PRH publishes an PNF_READY revent that is consumed by SO via DMaaP
13. SO continues with the provisioning of the CFS HSIA (PNF Activation Stage 5: Service Configuration)
14. SO via SDN-C triggers the creation of the RFS Access Connectivity, which will configure the ONT and the OLT via the Access SDN M&C
15. SO via SDN-C triggers the creation/configuration of the RFS Internet Profile (e.g. customer's speed profile)
16. SO updates CFS HSIA info in AAI.
17. CPE(RG) becomes online and initiates the CFS HSIA activation procedure via the CPE Authentication Notification

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

Note: BSS <-> ONAP interaction, Dublin priorities to extend NBI with new API for service modifications (ONAP Project Developers Event, Dec 10 - 12, 2018, (Virtual Webinars))

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
  

Note: BSS <-> ONAP interaction, Dublin priorities to extend NBI with new API for service modifications (ONAP Project Developers Event, Dec 10 - 12, 2018, (Virtual Webinars))

Note: 5G - PNF Plug and Play#5G-PNFPlugandPlay-PNPREREGISTRATIONUSECASE

Subscription Plan Change (stretch goal for Dublin)

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 (not for Dublin)

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:

• -