[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 |
---|---|---|
SDC | CFS HSIA design | |
SO | CFS HSIA orchestration ONT PNF discovery logic | New BPMN recipe for nomadic ONT case |
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? |
SDNC | Integrated with 3rd party controller | New DG for service creation, activation and change |
UUI | ONT to customer association (customer ID) Service health dashboard | BBS custom UI |
A&AI | DM for ONT PNF | A&AI needs to scale to support high number of CFS instances To be checked: A&AI enrichment for control loop look-up |
External APIs | CFS HSIA LCM | |
DCAE | Collect the event data for CFS HSIA health ONT PNF (re-)registration | New Restconf2VES mapping support might be needed To be checked: Can we use PRH for PNF re-registration? |
VF-C/APP-C | ||
Modeling | CFS HSIA model | |
CLAMP | Define nomadic ONT closed loop |