2016 IEEE Conference on Standards for Communications and Networking (CSCN) 2016
DOI: 10.1109/cscn.2016.7785157
|View full text |Cite
|
Sign up to set email alerts
|

A double-tier MEC-NFV architecture: Design and optimisation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
33
0

Year Published

2018
2018
2020
2020

Publication Types

Select...
8

Relationship

1
7

Authors

Journals

citations
Cited by 52 publications
(33 citation statements)
references
References 9 publications
0
33
0
Order By: Relevance
“…11 . As presented by Sciancalepore et al [122] in a compound architectural evaluation of MEC and NFV, the fundamental element of MEC is the MEC application server, which runs on top of the MEC NFVI infrastructure and provides services to the end-users, implemented as individual MEC Applications (MEC Apps). MEC Apps share communication interfaces with the MEC 11 https://datatracker.ietf.org/wg/i2rs/about/ .…”
Section: Multi-access Edge Computing (Mec)mentioning
confidence: 99%
“…11 . As presented by Sciancalepore et al [122] in a compound architectural evaluation of MEC and NFV, the fundamental element of MEC is the MEC application server, which runs on top of the MEC NFVI infrastructure and provides services to the end-users, implemented as individual MEC Applications (MEC Apps). MEC Apps share communication interfaces with the MEC 11 https://datatracker.ietf.org/wg/i2rs/about/ .…”
Section: Multi-access Edge Computing (Mec)mentioning
confidence: 99%
“…A standardized MEC framework is the subject of a recent ETSI specification [6]. The commonalities in the characteristics of NFV-MANO and the MEC management and orchestration system, and the lack of a unified way to jointly manage VNFs and MEC applications have been identified by Sciancalpore et al [14] who propose specific extensions to the MANO design to address this issue. A basic premise of our work is also the ability to jointly manage resources and virtual instances both on top of and outside the mobile edge, and our design supports this in a standards-compliant way.…”
Section: Multi-access Edge Computing For Video Deliverymentioning
confidence: 99%
“…Our design does not preclude operation in a MEC-in-NFV environment, where the MEP/MEPM are deployed as virtual instances and their instantiation and lifecycle management, as well as those of ME applications, are delegated to an NFVO. The interplay between MEC and NFV is currently under study by ETSI MEC 017 [46], and in parallel research efforts [14]. VNFs and ME applications have some distinct differences, which are reflected in the structure of their descriptors: An AppD, beyond the information included in a VNF descriptor (VNFD), also provides information about MEC services consumed and exposed by the ME application, and specific DNS rules and traffic steering directives.…”
Section: Mapping To the Etsi Nfv Mano And Mec Reference Architecturesmentioning
confidence: 99%
“…The server resources (e.g., compute, network, storage, memory) are virtualized and allocated to each VM based on the respective VM requirements. A VM when configured with some network function is referred to as a VNF, or when configured with some application function it is referred to as a Virtualized Application Function (VAF) [18]. For the sake of clarity, we consider only VNFs in our analysis.…”
Section: Related Workmentioning
confidence: 99%