2013
DOI: 10.1109/mcom.2013.6553677
|View full text |Cite
|
Sign up to set email alerts
|

Mobileflow: Toward software-defined mobile networks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
201
0
1

Year Published

2014
2014
2018
2018

Publication Types

Select...
6
3
1

Relationship

0
10

Authors

Journals

citations
Cited by 308 publications
(202 citation statements)
references
References 11 publications
0
201
0
1
Order By: Relevance
“…An analysis of this limitation is given by Pentikousis et al (2013). For instance, Bradai et al (2015) highlight that elements in the 4G core network are controlled through standardized interfaces and cannot be controlled by APIs.…”
Section: Deployment With 4g Systemsmentioning
confidence: 99%
“…An analysis of this limitation is given by Pentikousis et al (2013). For instance, Bradai et al (2015) highlight that elements in the 4G core network are controlled through standardized interfaces and cannot be controlled by APIs.…”
Section: Deployment With 4g Systemsmentioning
confidence: 99%
“…MobileFlow protocol: A usual attack target is the protocol used for communication, management or control purposes, such as the MobileFlow protocol [23]. For example, the southbound and northbound interfaces, shown in …”
Section: Targetmentioning
confidence: 99%
“…A third example illustrates how to achieve an efficient access to Big Data infrastructures through mobile devices (Wang, Liu, & Soyata, 2014;Soyata et al, 2014) potentially adjusted to network limitations on the network edge (e.g. terminals, radio access) A fourth example describes how to support an efficient flow forwarding (Pentikousis, Wang, & Hu, 2013) guaranteeing a complete isolation among them in the data path (i.e. using FlowVisor (Sherwood et al, 2010)).…”
Section: Mobile Networkmentioning
confidence: 99%