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

Project	Usage

Impact

Work to be done by Team	Work needed in Project Team
SDC	CFS HSIA design	Use the platform PNF model in definition of service	None - using platform
SO	CFS HSIA orchestration ONT

PNF discovery logic

PnP and PNF registration & re-registration

New BPMN recipe for nomadic ONT case

Assumption: PNF registration (discovery) is implemented

5G Use Case to develop PNF discovery and re-registration - Nokia led WIP

re-use Service instance update API

Policy

Trigger service reconfiguration due to nomadic ONT event (re-registration)

Support for creating policies during run-time (configuration policies

?SDNC

associated with RestConf collector and VES mapper)

Support new operational policy(s) in CL

To be checked: Nomadic ONT: ONSET ok / How can the ABATEMENT be detected?

None - but informing there is a creation of PNF re-registration policy
SDN-C (CCSDK)	Integrated with 3rd party controller	New DG/YANG model for service creation, activation and change New DG/YANG for ONT location change Modify generic resource API for NBI	None - Update DG repository with new DGs
UUI	ONT to customer association (customer ID) Service health dashboard	BBS custom UI	None - not going to use
A&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:

update A&AI

enrichment for control loop look-up

schema for new data model	None - using platform
External APIs	CFS HSIA LCM ONT location change notification ONT and CFS HSIA alarms/notifications Service modification request (subscription plan change)		Nice to have: Support for TMF 638 ServiceStateChangeNotification or ServiceAttributeValueChangeNotifications - Huawei
DCAE	Collect the event data for CFS HSIA health ONT PNF (re-)registration	New Restconf2VES mapping support

might be needed

Enhance Restconf collector

New microservice to handle CPE authentication event

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

Assumption: Use PRH for PNF re-registration

?

	Must have: Restconf2VES mapper (BBS only have resources - TechM) Restconf collector microservice (BBS only have resources - Huawei) CPE authentication microservice (BBS only have resources - Nokia) PRH microservice needs to trigger policy (generic 5G use case resource - Nokia)
VF-C/APP-C			None - not using
Modeling	CFS HSIA model	Need new data types: ONT PNF, OLT connectivity Dublin: Assumption is ONT PNF has both ONT and RG functionality	Update platform data model for PNF resource which will provide a field for PNF re-registration (from the additional information field of the PNF registration VES event) - Swisscom/Huawei/Nokia
CLAMP	Define nomadic ONT closed loop	Restconf collector; VES mapper; PRH; VES collector with Policy interactions needed	None - creating BBS closed loop

Versions Compared