Transcript Anchor Node
UPMT – Universal Per-application Mobility management using Tunnels Stefano Salsano - [email protected] Marco Bonola - [email protected] Always best connected (ABC) ABC service concept: automatic selection of the “best” interface in the mobile device Dates back to the early 2000, but turning ABC services into reality is still a challenge: – Need to change networking equipment, existing applications, networking stacks ? – True ABC services require “per-application” mobility, typical solutions offers “per-device” mobility 3G offload renews interest in ABC concept Page 2 UPMT: Universal Per-application Mobility management using Tunnels Key features per-application independent management of connectivity (even per-flow) works on existing networks supports private IP networks / NAT works with ALL existing applications no changes in the correspondent hosts implemented on Linux and Android platforms Page 3 Basic principles of UPMT (see figure in next slide) IP in UDP tunnels from the Mobile Host to the Anchor Node, one tunnel for interface The Anchor Node provides a “second level” NAT, the Correspondent Hosts are unaware of UPMT Each application can be independently sent over one of the tunnels The applications see a Virtual Interface, they are shielded from any mobility/handover issue and from loss of connectivity on the physical interfaces SIP protocol is used for mobility management signaling between Mobile Host and Anchor Node Page 4 Basic principles of UPMT Anchor Node “second level” Correspondent (AN) NAT Host (CH) IP/UDP Tunnel 1 “first level” NAT Public Internet NAT 1 Virtual Interface Mobile Host (MH) NAT 2 IP/UDP Tunnel 2 Access Networks Page 5 UPMT scalability The basic scenario foresees a “centralized” Anchor Node Anchor Node (AN) Local NAT Corresp. Host Anchor NAT Public Internet AN3 AN2 (public IPs) Local NAT AN1 Mobile Host (MH) Page 6 UPMT scalability Multiple Anchor Nodes can be supported… Corresp. Host Anchor Node (AN) 2 Local NAT Anchor Node (AN) Corresp. Host Anchor NAT Public Internet AN3 AN2 (public IPs) Local NAT AN1 Mobile Host (MH) Page 7 UPMT scalability A “fixed” host with UPMT modules can play the role of the Anchor Node ! Anchor Node (AN) Local NAT Public Internet Anchor NAT Fixed Host, e.g. for example: AN3 AN2 (public IPs) Local NAT AN1 … and other over-the-top providers Mobile Host (MH) Page 8 UPMT scalability Direct Mobile Host to Mobile Host communication (work in progress!) Anchor Node (AN) Local NAT Public Internet AN3 AN2 (public IPs) AN1 Local NAT MH NAT Mobile Host (MH) Mobile Host (MH) Page 9 Policies: some examples Never run “bulk transfer” applications on expensive and/or resource-limited access nets. When connected as a guest to a wifi that only provide web access, use the wifi only for the browser. For a voice call, use wifi if the quality is OK, move to 3G if the quality on wifi is bad AND the quality on 3G is better. Page 10 Linux GUIs for policies and monitoring Page 11 Performances User level performances System level performances: the validity of kernel level implementation MH - Mobile Host AN – Anchor Node Packets/s Packets/s Page 12 Linux and Android implementation The UPMT implementation is open source http://netgroup.uniroma2.it/UPMT Tunneling and flow classification are implemented in kernel space for performance/scalability A UPMT Live distribution for Linux is available, it can be configured to be a Mobile Host or an Anchor Node Ported on Android (2.2 Platform), Nexus one terminal – Kernel modules ported, patch to support more network interfaces – Android image can be downloaded Page 13 Business scenarios UPMT can be used in different business scenarios: Operator centric User centric Corporate Net. centric Aggregator centric Over-the-top Prov. centric Page 14 Take home message To the best of our knowledge, UPMT is the only implemented solution that provides: – per-application handover – support of all legacy applications – overlay approach with no support from routers and access network – support of NAT – support of legacy correspondent host moreover, it is open source… Page 15 References M. Bonola, S. Salsano, A. Polidoro, “UPMT: Universal PerApplication Mobility Management using Tunnels”, IEEE GLOBECOM 2009 M. Bonola, S. Salsano, “Achieving Scalability in the UPMT Mobility Management Solution”, Future Network & Mobile Summit 2010, 16 – 18 June 2010, Florence, Italy. M. Bonola, S. Salsano, “Per-application Mobility Management: Performance Evaluation of the UPMT Solution”, IWCMC 2011, Istanbul, Turkey, July 2011 S. Salsano, M. Bonola, “The UPMT solution”, technical report, http://netgroup.uniroma2.it/TR/UPMT.pdf Page 16