...
Project | Usage | Work to be done by Team | Work needed in Project Team |
---|---|---|---|
SDC | CFS HSIA design | None | |
SO | CFS HSIA orchestration ONT PNF registration (initial) | New BPMN recipe for nomadic ONT case Assumption: PNF registration (discovery) is implemented | 5G Use Case to develop PNF discovery |
Policy | Trigger service reconfiguration due to nomadic ONT event | Support for creating policies during run-time (configuration policies ?) Support new operational policy(s) in CL To be checked: Nomadic ONT: ONSET ok / How can the ABATEMENT be detected? | None |
SDN-C (CCSDK) | Integrated with 3rd party controller | New DG/YANG model for service creation, activation and change Modify generic resource API for NBI | None |
UUI | ONT to customer association (customer ID) Service health dashboard | BBS custom UI | None |
A&AI | DM for ONT PNF | A&AI needs to scale to support high number of CFS instances
| WIP: Pending discussion with External API team |
External APIs | CFS HSIA LCM | Nice to have: Support for TMF 638 ServiceStateChangeNotification or ServiceAttributeValueChangeNotifications | |
DCAE | Collect the event data for CFS HSIA health ONT PNF (re-)registration | New Restconf2VES mapping support Enhance Restconf collector New microservice to handle RG activation event Support to be added to detect nomadic ONT move and build DCAE_CL_Event to trigger Policy to modify the existing services. Assumption: Use PRH for PNF re-registration | Must have:
|
VF-C/APP-C | None | ||
Modeling | CFS HSIA model | Need new data types: ONT PNF, OLT connectivity Dublin: Assumption is ONT PNF has both ONT and RG functionality | None |
CLAMP | Define nomadic ONT closed loop | Restconf collector; VES mapper; PRH; VES collector with Policy interactions needed | None |
...