...
TIC Location | VNFs | Intended VNF Provider | NotesVNF CSAR |
Edge | vSBC | Huawei | ConfirmedvSBC_Huawei.csar |
vPCSCF | Huawei | ConfirmedvPCRF_Huawei.csar | |
vSPGW | ZTE/Huawei | ConfirmedvSPGW_ZTE.csar | |
Core | vPCRF | Huawei | ConfirmedvPCRF_Huawei.csar |
VI/SCSCF | Nokia | ConfirmedVI/SCSCF_Nokia.csar | |
vTAS | Nokia | Confirmed | |
VHSS | Huawei | ConfirmedvHSS_Huawei.csar | |
vMME | ZTE/Huawei | ConfirmedvMME_Huawei.csar |
Note: The above captures the currently committed VNF providers, we are open to adding more VNF providers.
...
| Network equipment | intended provider | Notes |
|---|---|---|
Bare Metal Host | Huawei, ZTE | Confirmed |
WAN/SPTN Router | Huawei/ZTE, Huawei | Confirmed |
| DC Gateway | Huawei, ZTE | Confirmed |
| TOR | Huawei,ZTE | Confirmed |
| Wireless Access Point | Raisecom | Confirmed |
| VoLTE Terminal Devices | Raisecom | Confirmed |
...
- Design
- 1.0: ONAP user uses SDC to import and design VoLTE E2E model/templates via Portal. The E2E models should include, vIMS + vEPC network services, SDN-WAN connection services, relevant auto-healing policy and alarm correlation rules, etc. All of these should be tied together as a E2E VoLTE model
SDC/CLAMP should distribute all above models to related components in run time when use need to instantiate the E2E VoLTE service. - 1.1 Distribute E2E model to to SO.
- 1.2 Distribute vIMS+vEPC NS to VF-C,
- 1.3 Distribute SDN-WAN connection service to SDN-C
- 1.4 Distribute auto-healing policy to Policy engine
- 1.5 Distribute alarm correlation rules to Holmes engine.
- 1.6 Design and Distribute DCAE configuration from CLAMP
...
After the fault detected and its root correlated, ONAP should do the auto-healing action as specified by a given policy to make the system back to normal.
More details about the VoLTE use case control loop.
Configuration flows (Stretch goal)
...