...
| USE CASE | Integration Leads | Lab | Committed Companies | Interested Companies | Overall Commitment | |
|---|---|---|---|---|---|---|
| Bulk PM | Wind River (WR) Lab | AT&T, Ericsson* | High | |||
PNF Pre-Onboarding/ Onboarding | WR Lab | AT&T, Huawei, Ericsson*, Nokia* | High | |||
| Configuration with NetConf | WR Lab | AT&T, Ericsson* | High | |||
FM Meta Data PM Dictionary & Schema | WR Lab | AT&T, Ericsson, Nokia* | High | |||
| OOF & PCI | (Name to be provided) (Verified Feb x, 2019) | Rutgers Win WRLab | AT&T*, Wipro, Tech Mahindra | High | ||
| PNF Plug and Play | WR Lab | AT&T, Huawei, Ericsson, Nokia* | High | |||
| Network Slicing | Modeling only (no Integration) | N/A | AT&T, Amdocs*, Ericsson | Modeling only (High) | ||
| MOVED TO R5 EL ALTO | ||||||
| PNF Software Upgrade | Use Case Moved to R5 El Alto | N/A | R5 El Alto | R5 El Alto | ||
...
| U/C | SDC | VID | Port | SO | AAI ESR | SDN-C | APP-C | DCAE | OOF | Policy | CLAMP | DM aaP | AAF | VNF SDK | REQ | MODEL COMMODCOM | OOM | VIM | Pomba Panda | CIA | CLI | Consul |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Bulk PM |  | N/A | N/A | N/A | N/A | N/A | N/A | YES | N/A | N/A | N/A | YES | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| Onboarding | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | YES | YESYES | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| NetConf | N/A | N/A | N/A | YES | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | ?(1) | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| FM PM Dict | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| OOF PCI | N/A | N/A | N/A | N/A | N/A | YES | N/A | YES | YES | YES | N/A | N/A | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| PNF PnP | N/A | ?YES | YES | ?YES | YES | YES | N/A | YES | N/A | N/A | N/A | N/A | YES | N/A | ?(2) | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| N/A | ? | ? | ? | N/A | ? | ? | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ? | N/A | N/A | N/A | N/A | N/A | N/A | |
| Slicing | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A |
REQ = VNF Requirements Project. a . The VNF-RQTS project applies to both VNFs and PNFs. A "YES" here means that there are new requirements for the vendors. (Moved to Wed 10AM)
MODCOM = Modelling Subcommittee.
Ctrl = This includes all of the controllers in ONAP including SDN-C, SDN-R, APP-C and VF-C
Stretch Goal (N/A) but if extra resources are available some changes may be made.
Note (1): This is still in discussion, solution depends on AAF. Will have to either the preferred option is to include AAF, but if the Jira is not implemented in time in R4, an alternate simplified solution will be adopted that excludes AAF from the U/C.
Note (2): In Analysis now. Feb 14, 2019
Note (3): Most of the PNF S/W Upgrade Use Case has been descope out of R4/Dublin and pushed to R5/El Alto release. Stretch Goal (N/A) but if extra resources are available some changes may be madeIn discussion with Change Management team, nothing major in R4 can be done, but may want to update the Playbooks distribute through SDC, distribute with roll-back API. Some discussion w/ 3GPP S/W mgmt API and what has been done in Change management U/C and how to bridge the gap.
USE CASE REALIZATION MEETINGS
...