Embed Size (px)
Citation preview
1
Resumo das propostas
q Mobile Home Automation q Multiacesso simultâneo em redes móveis heterogéneas q Multiaccess control for UAV - Unmanned Aerial Vehicle q Redes Mesh com Dispositivos Móveis q PeerToPeer Collaboration in Content Delivery Networks q 3D Video Quality Monitor q Assinaturas remotas móveis (projecto com a Multicert) q Autorização Remota MofN com dispositivos móveis (projecto com a
Multicert) q Crypto Cloud (projecto com a Multicert) q Aplicação móvel para gestão de descanso! (projecto com Molaflex) Orientador: Rui Marinheiro
2
Mobile Home Automation
q Objectives § Improve the integration of mobile devices in current home automation
solutions, considering the device as a sensor § Improve the integration of different home automation hardware controlled
today by independent apps. q Supervisor: Rui Marinheiro - [email protected]
3
Mobile Home Automation q Work Plan:
1. Bibliographic research regarding home automation. 2. Analyse the OpenRemote middle-ware
1. implement a practical demo, with an integration with KNX and/or ZigBee 3. Analyse home automation applications available for iOS or Android devices, and
analyse the home automation platform HomeKit. 4. Develop modules for OpenRemote middleware that:
1. considers mobile devices as sensor for the home automation 2. considers several devices controlled today only by private apps. 3. it is easier for an end user to customise an interface.
5. Implement several scenarios and perform testes and field trials 6. Produce one paper for an International Conference and/or Journal. 7. Write the thesis.
Requirements: basic programming and networking skills.
4
q Objetivos § Há inadequação dos acessos nas redes móveis aos fluxos de dados das
aplicações/serviços. § Pretende-se uma solução que faça a gestão dos fluxos de dados por
diversas tecnologias de acesso usadas em simultâneo em dispositivos móveis, usando um controlador SDN e um sensor de QoE
§ Espera-se uma utilização mais eficiente das tecnologias de acesso com uma gestão proactiva/reativa da rede, tendo em vista a satisfação da qualidade de serviço/experiência por fluxo.
q Supervisor: Rui Marinheiro - [email protected]
networks; the client and the applications decide which one(s)to use. Beyond barriers due to business reasons, there aretechnical challenges.
Our vision requires much more than just multiple radiosand multiple networks—it requires that the mobile client(as well as the applications and user) can take advantage ofthem. Today’s clients are ill-equipped to do so, having grownup in an era of TCP connections bound to a single physi-cal network connection. This leads to several well-knownshortcomings: (1) An ongoing connection oriented flow—like TCP—cannot easily be handed over to a new interface,without re-establishing state; (2) If multiple network inter-faces are available, an application cannot take advantage ofthem to get higher throughput; at best it can use the fastestconnection available; (3) A user cannot easily and dynami-cally choose interfaces at fine granularity so as to minimizeloss, delay, power consumption, or usage charges.
The three limitations are not just consequences of TCP.They are manifestations of the way the network stack isimplemented in the operating system of the mobile devicetoday. Therefore, as a step towards our bigger vision, wewant to understand what changes are needed in the mo-bile device networking stack, to overcome these three limi-tations. In this paper, we describe how we refactored andthen modified the networking stack on Android and Linuxdevices to be able to use multiple network interfaces simul-taneously, and then we measure the performance of severalexperiments where several network interfaces are used.
Our first prototype, reported here, is purely host-based.The sending host decides which interfaces to use, and thendivides outgoing tra�c over multiple interfaces. In somecases we assume the receiver is also equipped with the samenetworking stack, so it can reconstitute the original flow.However, in this paper we assume the rest of the networkinfrastructure is unchanged. We plan to explore the benefitsof coordination between the end host and the infrastructurein future work.
2. SYSTEM DESCRIPTIONWe will now describe how we modified the Android and
Linux operating system to allow a mobile device to use mul-tiple interfaces. For our prototype, we had four high-levelrequirements: (1) it should run on commercially availablesmartphone devices and laptops, (2) it should work withunmodified existing applications, (3) it should connect toexisting production WiFi and cellular networks, and (4)wherever possible, it should reuse existing well-supportedsoftware components.
2.1 PrototypeOur prototype consists of the following components shown
in Fig. 1:
2.1.1 Android/LinuxThe first problem to solve is that, by default, Android only
allows one network interface to be active at a time—clearlyno good for us. Android chooses which interface to use ac-cording to a preference order: If the device is connected toa WiFi network, Android automatically disconnects fromWiMAX. We therefore modified the Connectivity Service inAndroid to allow us to use multiple interfaces simultane-ously.
Figure 1: System diagram illustrating the main fea-tures of our prototype
Next, we need to spread tra�c from one application overmultiple interfaces. The application sends tra�c using oneIP source address; the networking stack takes care of spread-ing the tra�c over several interfaces, each with its own IPaddress. We do this using a virtual Ethernet interface toconnect the application, with its local IP address, to a spe-cial gateway inside the Linux kernel. The gateway stitchesmultiple interfaces together, without the application know-ing. Essentially, the gateway is a tra�c load-balancer thatdemultiplexes flows using Open vSwitch (see below), withappropriate changes made to the routing table and ARPtables. In this way, the application flow is decoupled fromthe IP addresses on each interface, which allows the set ofinterfaces to change dynamically as connectivity comes andgoes. We further illustrate this setup using our experimentdescribed in section 3.1.
Android is based on a minimal Linux kernel which is miss-ing several tools and kernel modules we need (e.g. the kernelmodule for virtual Ethernet interfaces). We added the mod-ules and cross-compiled common utilities such as ifconfig,route and ip.
2.1.2 Open vSwitch (OVS)Open vSwitch (OVS) replaces the bridging code in Linux,1
and lets us dynamically change how each flow is routed.OVS has an OpenFlow interface and therefore we can use<match,action> flow-table entries to easily route, re-routeand handover existing connections.
We run OVS in kernel space, and ported it to Androidby patching and and cross-compiling its kernel module anduser-space control programs using Android Native Develop-ment Kit (NDK) for the ARM or OMAP processors.2
2.1.3 Control PlaneWe control how flows are routed and re-routed using a
small custom-built control plane, that interfaces to OVS us-ing the OpenFlow protocol. In our prototype, the controlplane is on the mobile device; but in principle the control
1OVS was recently upstreamed to Linux kernel 3.3 [6].2Our patches and instructions are publicly availableat https://docs.google.com/document/pub?id=1k5jAkz_R475Ohj0OaJdWwSpAw6mmR2Mp_Ggr8_yrXsY.
20
Multi-acesso simultâneo em redes móveis heterogéneas
5
Multi-acesso simultâneo em redes móveis heterogéneas q Plano de trabalhos:
1. Estudo do firmware opensource OpenWRT para routers, e de uma solução de mobilidade multi-fluxo multi-acesso baseada no software OPMIP e ODTONE já disponível.
2. Alterar alguma funcionalidade de um controlador SDN para § considerar requisitos de QoE recebidos e as condições da rede § atribuir fluxos pelas diversas tecnologias de acesso. § comunicar por OpenFlow regras de encaminhamento/comutação aos
dispositivos de rede (router, switch) 3. Testes com Multicast de vídeo 3D, por
múltiplas ligações, seguindo múltiplos caminhos.
4. Artigo para uma conferência ou revista internacional.
5. Dissertação
Requisitos: Conhecimentos de programação e de redes.
6
q Objectives: Implement a simultaneous multi-access solution for the control of UAVs with hand-held devices, using the architecture shown in the picture
q Supervisor: Rui Marinheiro - [email protected]
Multi-access control for UAV - Unmanned Aerial Vehicle
7
Multi-access control for UAV - Unmanned Aerial Vehicle
q Requisites: The student should have basic programming and networking skills.
q Work Plan: § Study of the OpenWRT open source firmware program for embedded
devices, and its setup in a off the shelf access router § Setup and configuration of IP connections to a video camera and to the
ardupilot serial port. § Development of two simultaneous multi-access proxies to be installed
in the UAV access router and the land PC, that will manage access links to be used by the UAV for each type of traffic.
§ Perform tests and air field trials using several scenarios. § Produce at least one paper for an International Conference and/or
Journal. § Write the thesis.
8
A configuração mesh possibilita a utilização mais eficiente dos recursos de conectividade oferecidos pela tecnologia IEEE 802.11.
q Objetivos § Melhorar a capacidade ligação de dispositivos em redes mesh
IEEE802.11s, mitigando a congestão introduzida pelo aumento do tráfego nas redes de acesso.
§ Permitir múltiplos caminhos entre ligação de dispositivos em redes mesh
§ Limitar os tempos de atraso em configuração mesh, pois nestes cenários os pacotes fazem um número maior de saltos até chegarem à rede cablada.
q Supervisor: Rui Marinheiro - [email protected] e André Moura
Redes Mesh com Dispositivos Móveis
9
Redes Mesh com Dispositivos Móveis q Plano de trabalhos:
1. Familiarização com a implementação 802.11s - open80211s em Linux que temos atualmente no ISCTE.
2. Seleção de algoritmos de encaminhamento e métricas que permitam múltiplos caminhos para diferentes fluxos, a incluir na implementação da norma IEEE802.11s
3. Adaptação do código IEEE802.11s que existe atualmente, e integra-lo em dispositivos com o SO OpenWRT 1. Definição dos cenários de teste e das experiências a realizar. 5. Obtenção e análise de resultados. 6. Escrita de um artigo no âmbito do trabalho desenvolvido e dos resultados obtidos.
Requisitos: Conhecimentos de programação e de redes.
10
Peer-to-Peer Collaboration in Content Delivery Networks (CDNs)
R4
R1
R3CPR2
Client – Server model: Non-complex implementation; Easy discovery of content.
single point of failure; low scalability
(costs increase with content popularity).
Content distribution networks: Enable content providers cost
reduction with a distribution infrastructure;
Still based in the client server model, still facing scalability problems.
11
Peer-to-Peer (P2P) distribution model:
High scalability; Low cost.
Robustness Difficult discovery of network nodes and
content; Possible high bandwidth usage in content and
node discovery.
Content distribution networks partially
supported by a P2P model
Peer-to-Peer Collaboration in CDNs
12
Peer-to-Peer Collaboration in CDNs
!
13
Peer-to-Peer Collaboration in CDNs
Three prototype applications are available: • Network Controller; • Proxy Downloader; • Content Manager.
The work on this thesis will be focused on: • testing different replication and server selection algorithms; • study the DNS TTL impact, due to the volatility of content
popularity; • improvements on the feedback mechanism
Testes have been and will be performed on at least 75 PlanetLab nodes and 2 external HTTP Servers. Software test is already available.
14
3D Video Quality Monitor q Problem:
§ How to access 3D video perceptual quality with no reference q Solution:
§ Establish a set of (Quality of Experience) QoE metrics and their relationship with objective measurements that affect the overall QoE
q Goals: § Research and development of 3D video perceptual quality
monitoring in error prone networks. § Compute metrics from a combination of transport network layer
information (quality features of 3D video signal and coding parameters embedded in compressed streams).
15
q Envisages research and development of relevant relationships between network quality of service parameters (QoS) (e.g. IP or TS packet loss/error) and quality metrics with impact on the QoE.
q A network model for evaluating multimedia transmission performance over Internet Protocol must be used (ITU-T G.1050)
q With the obtained accessed relationships, a monitor is required (next slide)
3DVQM: 3D Video Quality Monitor
ITU-T Rec. G.1050 (11/2007) 5
VDSL Very high speed Digital Subscriber Line
VoIP Voice over Internet Protocol
VTC Video Teleconferencing
5 Description of the model
The IP network model consists of many impairment combinations that are scenario-based, time-varying IP network impairments that provide a significant sample of impairment conditions. Tests using this model may be unidirectional or bidirectional. Impairments occur in both directions. Since the access links may be asymmetrical in nature and packets travelling in one direction will encounter sections of the model in a different order than packets travelling in the other direction, the impairments in each direction may differ. Figure 1 (LAN-to-LAN) illustrates an end-to-end network with LAN and access links on each side of the core as would occur in a client-to-client application such as VoIP. Figure 2 (Core-to-LAN) illustrates an end-to-end network with LAN and access on the destination side, but not on the source side as would occur in a server-to-client application such as IPTV or web server access over the Internet.
Figures 1 and 2 show the network parameters and impairments that apply to each section of the model:
A-side parameters:
• LAN A rate and type, LAN A occupancy, local access A rates in each direction, access A occupancy, MTU size.
Core parameters:
• Route flapping interval, route flapping delay change, link failure interval, link failure duration, one-way delay, jitter, reordered packets and packet loss.
B-side parameters:
• LAN B rate and type, LAN B occupancy, local access B rates in each direction, access B occupancy, MTU size.
Figure 1 – IP network impairment model: LAN-to-LAN
16
N1
N2
N3
3DVQM: 3D Video Quality Monitor
17
Work plan: § Perform some bibliographic research regarding QoE monitoring. § Analyze the “Network model for evaluating multimedia
transmission performance over Internet Protocol (ITU-T G.1050)” and its reference software.
§ Design and implement several scenarios using the reference software and perform network simulation using the above model to map QoE to network impairment
§ Contribute to the implementation of a 3D QoE monitor § Perform testes and field trials § Produce at least one paper for an International Conference and/or
Journal. § Write the thesis.
Supervisor Rui Neto Marinheiro [email protected]
3DVQM: 3D Video Quality Monitor
18
Todos nós passamos 1/3 do nosso tempo a dormir. Será que não poderemos melhorar a nossa experiencia durante esse período?
q Objetivos § Monitorar os períodos de descanso usando sensores que podem ser
colocados dentro de colchões, almofadas ou em áreas circundantes § Atuar no ambiente por forma que a qualidade de experiencia de
descanso seja melhorada. q Supervisor: Rui Marinheiro - [email protected]
Projeto em colaboração com a Molaflex
Aplicação móvel para gestão de descanso!
19
Aplicação móvel para gestão de descanso! q Plano de trabalhos:
1. Levantamento de hardware que pode ser usado para fazer a monitorização.
2. Levantamento de hardware que pode ser usado para atuar no ambiente. 3. Desenho da solução, e seu desenvolvimento numa aplicação para
dispositivos móveis. 4. Especificação e implementação de cenários de testes. 4. Artigo para uma conferência ou revista internacional. 5. Dissertação
Requisitos: Conhecimentos de programação e de redes.
20
Nomadic Cloud Computing
q Cloud solutions are available offering computing resources and services, using different architectures, but usually implemented in enterprise servers.
q In addition, alternative solutions have been using volunteer contributions to build cloud infrastructures.
q Moreover, nowadays there is an increase in the number and the resources available from nomadic devices, like smartphones, tablets, etc.
Unfortunately, nomadic devices have not yet been regarded for the provisioning of services and computing resources necessary for cloud solutions, but there is an increasing potential on their nano-contributions
21
Nomadic Cloud Computing
Objective q The provisioning of services in a transparent manner, being those
services hosted by mobile devices or servers. q Services must be universally accessed, regardless of location and
device, possibly accessing mobile storage on their execution.
Methods and approaches: q State of the art review regarding general approaches to nomadic
computing infrastructure and nomadic services; q Identification and localization of the nodes implementing services
will be the first problem to be solved. Some mobile devices may only provide services in the local area network, if using IPv4. This is a clear limitation, and an architecture will be proposed and implemented, possibly using proxies in extreme conditions, to provide universal access to devices.
22
Nomadic Cloud Computing
q Access to mobile storage must be solved. It is expected that access to storage is done in an uniform manner, regardless of the device been used. Different alternatives will be analysed (e.g. WebDav)
q An architecture for provisioning services must be proposed and implemented, considering different possibilities (e.g. implementing services through a web server). Some devices platforms have constrain on access to local resources and lack of multitasking, In addition, depending on the devices context and permanent and/or temporary capacities, different services may be available. Moreover, it is also necessary to locally monitor devices physical resources. The architecture must provide a way of advertisement services, and negotiating service level agreements. All this must be regarded in the architecture
q Finally, a selection of services will be implemented. This will allow the execution of functional and performance tests on the proposed solution for nomadic computing.
23
Nomadic Cloud Computing
Seamless access to other devices
Open API Portable Servers
![[Desarrollo] OpenWrt en Comtrend AR-5387un](https://img.pdfslide.net/doc/110x75/55cf9a9f550346d033a2a081/desarrollo-openwrt-en-comtrend-ar-5387un.jpg)
