Ongoing PoCs: Difference between revisions
From ZSM Wiki
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
* '''[[PoC 1 ServoCloud: efficient lifecycle and element management automation at scale]]''' | * '''[[PoC 1 ServoCloud: efficient lifecycle and element management automation at scale]]''' | ||
** EnterpriseWeb - Deutsche Telekom - Sprint - Amazon Web Services - Amdocs - EXFO - InfoSim - Fortinet - Metaswitch | ** EnterpriseWeb - Deutsche Telekom - Sprint - Amazon Web Services - Amdocs - EXFO - InfoSim - Fortinet - Metaswitch | ||
* '''[[PoC 2 Automated Network Slice Scaling in Multi-Site Environments]]''' | * '''[[PoC 2 Automated Network Slice Scaling in Multi-Site Environments]]''' | ||
** Telefonica - Telenor - Universidad Carlos III (UC3M) - University of Patras (UoP) - Openslice | ** Telefonica - Telenor - Universidad Carlos III (UC3M) - University of Patras (UoP) - Openslice | ||
Revision as of 09:41, 18 December 2020
List of ZSM PoCs
This page provides the list of on-going ISG ZSM PoCs. Click on them to learn further details.
The following ZSM Proofs of Concept are developed according to the ETSI ISG ZSM Proof of Concept Framework. ZSM Proofs of Concept are intended to demonstrate ZSM as a viable technology. Results are fed back to the Industry Specification Group on Zero tough network and Service Management.
Neither ETSI, the ISG ZSM, nor their members make any endorsement of any product or implementation claiming to demonstrate or conform to ZSM. No verification or test has been performed by ETSI on any part of these ZSM Proofs of Concept.
- PoC 1 ServoCloud: efficient lifecycle and element management automation at scale
- EnterpriseWeb - Deutsche Telekom - Sprint - Amazon Web Services - Amdocs - EXFO - InfoSim - Fortinet - Metaswitch
- PoC 2 Automated Network Slice Scaling in Multi-Site Environments
- Telefonica - Telenor - Universidad Carlos III (UC3M) - University of Patras (UoP) - Openslice