| 1. |
- Alay, Özgü, et al.
(författare)
-
Experience : An open platform for experimentation with commercial mobile broadband networks
- 2017
-
Ingår i: MobiCom '17 Proceedings of the 23rd Annual International Conference on Mobile Computing and Networking. - New York : Association for Computing Machinery (ACM). - 9781450349161 ; , s. 70-78
-
Konferensbidrag (refereegranskat)abstract
- Open experimentation with operational Mobile Broadband (MBB) networks in the wild is currently a fundamental requirement of the research community in its endeavor to address the need of innovative solutions for mobile communications. Even more, there is a strong need for objective data about stability and performance of MBB (e.g., 3G/4G) networks, and for tools that rigorously and scientifically assess their status. In this paper, we introduce the MONROE measurement platform: an open access and flexible hardware-based platform for measurements and custom experimentation on operational MBB networks. The MONROE platform enables accurate, realistic and meaningful assessment of the performance and reliability of 11 MBB networks in Europe. We report on our experience designing, implementing and testing the solution we propose for the platform. We detail the challenges we overcame while building and testing the MONROE testbed and argue our design and implementation choices accordingly. We describe and exemplify the capabilities of the platform and the wide variety of experiments that external users already perform using the system
|
|
| 2. |
- Alay, Özgü, et al.
(författare)
-
Measuring and Assessing Mobile Broadband Networks with MONROE
- 2016
-
Ingår i: 2016 IEEE International Symposium on a World of Wireless, Mobile, and Multimedia Networks (WoWMoM). - Red Hook : IEEE. - 9781509021864 - 9781509021857
-
Konferensbidrag (refereegranskat)abstract
- Mobile broadband (MBB) networks underpin numerous vital operations of the society and are arguably becoming the most important piece of the communications infrastructure. In this demo paper, our goal is to showcase the potential of a novel multi-homed MBB platform for measuring, monitoring and assessing the performance of MBB services in an objective manner. Our platform, MONROE, is composed of hundreds of nodes scattered over four European countries and a backend system that collects the measurement results. Through a user-friendly web client, the experimenters can schedule and deploy their experiments. The platform further embeds traffic analysis tools for real-time traffic flow analysis and a powerful visualization tool.
|
|
| 3. |
- Alay, Özgü, et al.
(författare)
-
MONROE, a distributed platform to measure and assess mobile broadband networks : demo
- 2016
-
Ingår i: Proceedings of the Tenth ACM International Workshop on Wireless Network Testbeds, Experimental Evaluation, and Characterization. - New York, NY, USA : Association for Computing Machinery (ACM). - 9781450342520 ; , s. 85-86
-
Konferensbidrag (refereegranskat)abstract
- This demo presents the MONROE distributed platform and how it can be used to implement measurement and assessment experiments with operational mobile broadband networks (MBBs). MONROE provides registered experimenters with open access to hundreds of nodes, distributed over several European countries and equipped with multiple MBB connections, and a backend system that collects the measurement results. Experiments are scheduled through a user-friendly web client, with no need to directly access the nodes. The platform further embeds tools for real-time traffic flow analysis and a powerful visualization tool.
|
|
| 4. |
- Bozakov, Zdravko, et al.
(författare)
-
Deliverable D2.1 - First Version of Low-Level Core Transport System
- 2016
-
Rapport (refereegranskat)abstract
- This document presents the first version of the low-level Core Transport System in NEAT, to be used for development of a reference implementation of the NEAT System. The design of this core transport system takes into consideration the Transport Services and the API defined in Task 1.3 and in close coordination with the overall architecture (Task 1.2). To realise the basic Transport Services provided by the API, a set of low-level transport functionalities has to be provided by the NEAT core transport system. These functionalities take the formof several building blocks, or NEAT Components, each representing an associated implementation activity. Some of the components are needed to ensure the basic operation of the NEAT System—e.g., a NEAT Flow Endpoint, a callback-based NEAT API Framework, the NEAT Logic and the functionality to Connect to a name. Some other components are needed to ensure connectivity usingMiddlebox Traversal techniques (e.g., TURN), discovery of path support for different transport protocols using Happy Eyeballs mechanisms, offering end-to end Security (e.g., (D)TLS over transport), gather statistics for the users or system administrators, and the ability to apply different policies in order to influence the decision-making process of the transport system. This document describes each of these building blocks and related design choices.
|
|
| 5. |
- Fairhurst, Gorry, et al.
(författare)
-
Deliverable D1.1 - NEAT Architecture
- 2016
-
Rapport (refereegranskat)abstract
- Ossification of the Internet transport-layer architecture is a significant barrier to innovation of the Internet. Such innovation is desirable for many reasons. Current applications often need to implement their own mechanisms to receive the transport service they need, but many do not have the breadth of adapting to all possible network characteristics. An updated transport architecture can do much to make the Internet more flexible and extensible. New ground-breaking services often require different or updated transport protocols, could benefit from better signalling between application and network, or desire a more flexible choice of which network path is used for which traffic. This document therefore proposes a new transport architecture. Such architecture lowers the barrier to service innovation by proposing a “transport system”, the NEAT System, that can leverage the rich set of available transport protocols. It paves the way for an architectural change of the Internet where new transport-layer services can seamlessly be integrated and quickly made available, minimising deployment difficulties, and allowing Internet innovators to take advantage of them wherever possible. The document provides a survey of the state-of-the-art to identify the architectural obstacles to, and opportunities for, evolution of the transport layer. It also details a set of general requirements for a new transport architecture. This new architecture is motivated by a set of use-cases, followed by a description of the NEAT architecture for a transport system, designed to permit applications to select appropriate transports based on their needs and the available transport services.
|
|
| 6. |
- Grinnemo, Karl-Johan, 1968-, et al.
(författare)
-
Deliverable D3.1 - Initial Report on the Extended Transport System
- 2017
-
Rapport (refereegranskat)abstract
- The NEAT System offers an enhanced API for applications that disentangles them from the actual transport protocol being used. The system also enables applications to communicate their service requirements to the transport system in a generic, transport-protocol independent way. Moreover, the architecture of the NEAT System promotes the evolution of new transport services. Work Package 3 (WP3) enhances and extends the core parts of the NEAT Transport. Efforts have been devoted to developing transport-protocol mechanisms that enable a wider spectrum of NEAT Transport Services, and that assist the NEAT System in facilitating several of the commercial use cases. Work has also started on the development of optimal transport-selection mechanisms; mechanisms that enable for the NEAT System to make optimal transport selections on the basis of application requirements and network measurements. Lastly, another research activity has been initiated on how to use SDN to signal application requirements to routers, switches, and similar network elements. This document provides an initial report on all these WP3 activities—both on completed and on near-termplanned work.
|
|
| 7. |
- Grinnemo, Karl-Johan, 1968-, et al.
(författare)
-
Deliverable D3.3 - Extended Transport System and Transparent Support of Non-NEAT Applications
- 2017
-
Rapport (refereegranskat)abstract
- This deliverable summarises and concludes our work in Work Package 3 (WP3) to extend the transport services provided by the NEAT System developed in Work Package 2, and to enable non-NEAT applications to harness the transport services offered by NEAT. We have demonstrated how a policy- and information-based selection of transport protocol by NEAT could provide a more efficient transport service for web applications. The information on which NEAT makes its transport selection decisions resides in the Characteristics Information Base (CIB). The CIB is populated by various CIB sources, and in WP3 we have designed, implemented, and evaluated various CIB sources, including meta data from mobile broadband networks, passive measurements, IPv6 Provisioning Domain protocols and the Happy Eyeballs mechanism, which caches the outcome of its connection attempts. A key property of NEAT is that it not only “vertically” decouples applications from transport protocols, but also “horizontally”. Particularly, it enables applications to harness information about resource availability and policies from Software Defined Networking (SDN) controllers in managed networks, without these applications actually being SDN-aware. To extend the use of NEAT to non-NEAT applications, we have implemented a BSDcompatible sockets API on top of NEAT and a NEAT proxy that intercepts and replaces standard TCP connections with NEAT flows, i.e., with the transport solutions deemed most appropriate by NEAT.We have also proposed a way for non-NEAT applications to make use of NEAT through the deployment of NEAT-enabled virtual appliances in SDN-controlled networks: connections from these applications are routed via an SDN-controlled proxy that terminates the original connection and replaces it with a NEAT-selected connection.
|
|
| 8. |
|
|
| 9. |
- Hurtig, Per, 1980-, et al.
(författare)
-
A NEAT Approach to Mobile Communication
- 2017
-
Ingår i: MobiArch ’17 Proceedings of the Workshop on Mobility in the Evolving Internet Architecture. - New York, NY, USA : Association for Computing Machinery (ACM). - 9781450350594 ; , s. 7-12
-
Konferensbidrag (refereegranskat)abstract
- 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.
|
|
| 10. |
- Khademi, Naeem, et al.
(författare)
-
Deliverable D2.2 - Core Transport System, with both Low-level and High-level Components
- 2017
-
Rapport (refereegranskat)abstract
- This document presents the core transport system in NEAT, as used for development of thereference implementation of the NEAT System. The document describes the componentsnecessary to realise the basic Transport Services provided by the NEAT User API, with thedescription of a set of NEAT building blocks and their related design choices. The designof this core transport system takes into consideration the Transport Services and the API(defined in Task 1.3) and in close coordination with the overall architecture (Task 1.2).To realise the Transport Services provided by the API, a set of transport functionalitieshas to be provided by the NEAT Core Transport System. These functionalities take the formof several building blocks, or NEAT Components, each representing an associated implementationactivity. Some of the components are needed to ensure the basic operation ofthe NEAT System—e.g., a NEAT Flow Endpoint, a callback-based NEAT API Framework, theNEAT Logic and the functionality to Connect to a name. Additional components are neededfor: (a) ensuring connectivity, by means of mechanisms for discovery of path support fordifferent protocols; (b) supporting end-to-end security; (c) the ability to apply differentpolicies to influence the decision-making process of the transport system; (d) providingother important functionalities (e.g., a user-space SCTP stack, or gathering statistics forusers or system administrators).This document updates Deliverable D2.1; in particular, the descriptions of NEAT componentspresented here correspond to the implementation status at the time of writing,and as such they replace those in D2.1.
|
|
