2019-04-19 19:51:12 +00:00
2018-10-30 03:59:15 -07:00
2019-03-24 20:32:40 +00:00
2019-03-24 20:32:40 +00:00
2018-08-31 06:52:53 -07:00
2018-06-08 12:22:10 -07:00
2018-05-30 14:16:53 -07:00
2018-05-30 14:16:53 -07:00
2018-05-30 14:16:53 -07:00
2019-04-19 19:51:12 +00:00
2018-05-30 14:16:53 -07:00
2018-10-24 20:11:17 +02:00
2018-05-07 13:25:56 +02:00
2018-05-07 13:25:56 +02:00
2018-05-07 13:25:56 +02:00
2018-05-07 13:25:56 +02:00
2018-10-26 16:48:19 +00:00
2018-10-17 03:03:00 -07:00
2018-05-07 13:25:56 +02:00
2018-10-26 05:34:40 -07:00
2019-01-22 15:32:29 +08:00
2018-05-07 13:25:56 +02:00
2018-10-26 02:39:27 -07:00
2018-05-07 13:25:56 +02:00
2018-11-03 07:09:16 +00:00
This project aims at building an automated provisioning framework for Multi-access Edge Computing (MEC) based on OpenStack platform.
Current features of APMEC are to:
-
orchestrate the MEC services
-
leverage MANO's API to allow the reuse of NF network services (currently use OpenStack Tacker - NFV Orchestration service) for MEC services
-
support multi-MANO features that offer the scalability and improve resource utilization of MEC services.
-
manage the life-cycle of MEC applications (creation, update, deletion)
-
monitor MEC applications
-
scale in/out MEC applications
On-going features:
-
fast live migration in order to support mobility in MEC
-
state management for the stateful MEC applications
-
acceleration technologies like DPDK, VPP, FPGA,...
-
container technologies like Docker/Kubernetes
Acronym:
MEP: MEC Platform
MESO: MEC Service Orchestrator
MES: MEC service
MEO: MEC Orchestrator
MEM: MEC Manager
MEA: MEC Application
MEAD: MEA Descriptor
Authors:
Deutsche Telekom Chair of Communication Networks,
Technical University of Dresden, Germany.