Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
A NEAT Approach to Mobile Communication
Karlstad University, Faculty of Health, Science and Technology (starting 2013), Department of Mathematics and Computer Science. (DIStributed Systems and Communications Research Group (DISCO))
Karlstad University, Faculty of Health, Science and Technology (starting 2013), Department of Mathematics and Computer Science. (DIStributed Systems and Communications Research Group (DISCO))ORCID iD: 0000-0003-0368-9221
Karlstad University, Faculty of Health, Science and Technology (starting 2013), Department of Mathematics and Computer Science. (DIStributed Systems and Communications Research Group (DISCO))
Celerway Communications.
Show others and affiliations
2017 (English)In: The ACM SIGCOMM 2017 Workshop on Mobility in the Evolving Internet Architecture (MobiArch 2017), UCLA, CA, U.S.A., August 2017. / [ed] ACM, ACM Press, 2017Conference paper, Published paper (Refereed)
Abstract [en]

The demands for mobile communication is ever increasing. Mobile applications are increasing both in numbers and in heterogeneity of their requirements, and an increasingly diverse set of mobile technologies are employed. This creates an urgent need for optimizing end-to-end services based on application requirements, conditions in the network and available transport solutions; something which is very hard to achieve with today's Internet architecture. In this paper, we introduce the NEAT transport architecture as a solution to this problem. NEAT is designed to offer a flexible and evolvable transport system, where applications communicate their transport-service requirements to the NEAT system in a generic, transport-protocol independent way. The best transport option is then configured at run time based on application requirements, network conditions, and available transport options. Through a set of real life mobile use case experiments, we demonstrate how applications with different properties and requirements could employ the NEAT system in multi-access environments, showing significant performance benefits as a result.

Place, publisher, year, edition, pages
ACM Press, 2017.
Keyword [en]
NEAT, transport selection, heterogeneity, multiple paths, policies, TCP, MPTCP, cellular, WLAN, LTE, 3G
National Category
Telecommunications
Research subject
Computer Science
Identifiers
URN: urn:nbn:se:kau:diva-48467OAI: oai:DiVA.org:kau-48467DiVA: diva2:1092762
Conference
The ACM SIGCOMM 2017 Workshop on Mobility in the Evolving Internet Architecture (MobiArch 2017)
Projects
A New, Evolutive API and Transport-Layer Architecture for the Internet (NEAT)
Funder
EU, Horizon 2020, 644334
Available from: 2017-05-04 Created: 2017-05-04 Last updated: 2017-09-01

Open Access in DiVA

fulltext(1134 kB)3 downloads
File information
File name FULLTEXT01.pdfFile size 1134 kBChecksum SHA-512
cdf0ef9dac8c2dd14f6d385144fd6190738dc63e91dd2979d6a86ef3261159953b652421dcef4140eafa789f8ea7d06202c6ffe0fbcfbcb4d5af01800a3f2dfe
Type fulltextMimetype application/pdf

Search in DiVA

By author/editor
Hurtig, PerAlfredsson, StefanBrunstrom, AnnaGrinnemo, Karl-Johan
By organisation
Department of Mathematics and Computer ScienceDepartment of Computer Science
Telecommunications

Search outside of DiVA

GoogleGoogle Scholar
Total: 3 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

Total: 178 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf