Models/Frameworks
Telcos have (for past 15-20 yrs - maybe even more) AI/ML systems solving business problems (customer churns) and/or legacy Network management (failures prediction, anomaly detection, etc.). Is it Important that the models we develop should work in these frameworks (of legacy systems) ?
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Integration with legacy AI/ML Systems |
|---|
| showComments | true |
|---|
|
YES (we don't want to maintain multiple systems)
NO (Managed by different silos) |
Importance of AI/ML Problems related to NFV
Please add any other problems you consider that is important here:
|
|---|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Failure Prediction (VM) |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Failure Prediction (Containers) |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Failure Prediction (Links) |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Failure Prediction (Apps) |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Failure Prediction (Services - control/middleware/) |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Traffic Engineering (Ex: Reinforcement Learning) |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Other Predictions (resource utilization, attack, SLA-breach) |
|---|
| showComments | true |
|---|
|
5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Resource Optimization (scheduling, deployment scaling, migration, etc.) |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Anomaly Detection (metrics, logs, stats) |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Alert Filtering/classification - Finding Actionable Alerts |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
| Vote |
|---|
| changeableVotes | true |
|---|
| title | Importance of Correlation - as part of causal analysis |
|---|
| showComments | true |
|---|
| 5. Very Important
4. Important
3. Good to have
2. Not important
1. No value addition. |
|
|
...