ABC Networks

1. ABC Networks Per.Johansson@ericsson.com

2. ABC Research Discussion • Where we are today -- “ABC 1.0” • ABC Research topics • A proposed “ABC 3.0” as goal • Define requirements • “Sustainable” research topics… • Be used! • All Adaptive Systems activities invited to use the ABC testbed • Content adaptation/adaptive video • Packet scheduling (QoS) support • Low pwr routing • Steps of ABC development -- 1.0 => 2.0 => 3.0 ... • Near term ABC research issues • Actively involve people (students)

3. “ABC Server” “Service Network” ABC testbed today -- ABC 1.0 • Discovers and Selects the “best” access for one terminal • Mobility for a mobile client (TCP only) Cellular Cellular IP Transit Cellular Data “Content&Apps Network” WLAN Network Computing Resources WLAN WLAN “ABC Client” Ethernet LAN LAN

4. ABC Research Issues • Access Discovery • Discover available access networks and/or access devices • Determine their characteristics: IP connectivity to mobility server, network technology, cost, bandwidth, quality of service, power consumption, access network operator, security level, coverage, etc. • Define a general set of parameters to easily include new types of access networks • How to retrieve these? Where are they stored? Who gets access to them? • Access Selection • Make selection of the “best” access and/or device • Policies or algorithms to combine access/device characteristics, application requirements, user preference, and operator policies • Who makes the decision? Where (user, device network)? • Prototyping in ABC: Access wizard/agent, profile server (API) • Single-logon • Logon to ONE access network -- Roaming takes care of “next” access • Based on an AAA infrastructure • ABC prototype: Use SIM card based authentication for Cellular <-> WLAN roaming

5. ABC Research Issues • Mobility Management • Session continuity between access networks (e.g. Mobile IP, Session layer mobility) • Session transfer between devices (e.g. application states between devices) • Simultaneous use of several access networks for the same application flow (e.g. performance and security reasons) • Single logon security mechanisms need to be closely integrated with mobility • ABC prototype: Session layer mobility (session continuity) and simple single logon. • Content Adaptation • Application content needs to adapt to choice of access network and device • Make use of access discovery parameters (e.g. in profile database) to adapt content dynamically • How should this information be accessed by applications (server and clients)? • ABC prototype: APIs provided through the profile server • What type of API? Security aspects?

6. PAN: device and access dynamics, local/external traffic, PAN-PAN… • MANET(ietf): low pwr networking (routing, applications etc.), mix mobile/static nodes • NEMO (ietf): Mobile networks, mobile routers, nested mobility (PAN in NEMOs) Cellular Cellular IP Transit Cellular “ABC PAN” “Content&Apps Network” WLAN Network Computing Resources WLAN WLAN “ABC MANET” “ABC Server” LAN LAN “ABC NEMO” “Service Network” LAN Proposed ABC 3.0 • Discovers and Selects the “best” access for an entire network • What’s the impact on ABC functionality?

7. Cellular WLAN “ABC PAN” WLAN • PAN acts as ethernet-like segment based on Bluetooth (BNEP) or WLAN (ad-hoc mode) • Networking based on Zeroconf functionality • Access devices act as small routers • Local traffic on link-local (autoconfig) IP addresses • External traffic uses routable (dynamic) addresses • Access Discovery and Selection one hop away? • Mobility Mgmt: mobility to access or end device ? • Security: Single Logon from a PAN? • Content adaptation: Device and access dynamics? WLAN Cellular R R ABC PAN • Any device in the PAN uses the bestaccess network • Typical Two-hops (PDA - phone - network) • PAN connectivity may be on Bluetooth or 802.11b • Mix of local and external PAN traffic • Architecture and its impact on ABC functionality?

8. Cellular Cellular IP Transit Cellular “Content&Apps Network” WLAN WLAN Network Computing Resources WLAN “ABC Server” Cellular LAN LAN “Service Network” WLAN LAN “ABC MANET” LAN ABC MANET • Surveillance type ad-hoc network with internet connectivity • Example: Low power, battery driven, semi-static nodes (mix of low pwr cameras, gateways, ad-hoc routers) updating surveillance server(s) in the network • Peer-to-peer radio: mix of Bluetooth and WLAN • Gateways: Cellular, WLAN, Fixed access • Common power budget for applications and communications • Power aware video coding and routing where network lifetime essential • Impact on ABC functionality: • How is the “best” access (gateway) Discovered and Selected several hops away? • Mobility: maintain session when “best” gateway changes? Combination of ad-hoc routing and IP/session mobility? Asymmetric flows? • Security: VPN-like network (encryption+authentication) • Content adaptation: power aware (#hops, processing, quality) Surveillance server

9. ABC NEMO (Network Mobility) • Single users or PANs connect to mobile networks (train, airplane etc.) • WLAN for local and cellular for external connectivity • The NEMO contains a Mobile Router (co-located FA with routing capabilities) • “Hides” away mobility from the NEMO users (e.g. through Mobile IP tunneling) • Nested mobility for MIP clients in the NEMO (tunnel in tunnel) • Impact on ABC functionality: ABC primarily used by the NEMO provider? • Discover and Select “best” connection for the Mobile Router • Interaction with ABC users in NEMO? • Peer-to-peer communication in NEMO? • Mobility: maintain sessions of several users/PANs. Scheduling issues? • Security: Each user part of separate VPNs “ABC NEMO” MR

10. General ABC Architecture for best connected networks? • Common functionality found in all scenarios • Discover and Select access over multiple hops • Maintain sessions when “new” access (gateway) is selected hops away from end device • Security extends beyond one device (a private PAN or entire private MANET) • Aggregate of users within one “ABC service” (NEMO provider) • Content adaptation must consider flows passing additional low rate links and thin nodes • Make use of existing solutions -- bits and pieces are out there • IETF specify IP protocols for Zeroconf, MANET, and NEMO • IEEE 802.11b p2p/infrastructure mode • Bluetooth PANs enable IEEE-like networking (BNEP) • ABC will require integration of several solutions

11. Next steps for ABC? • Make ABC useful for other Adaptive systems activities ASAP! • Begin with current ABC 1.0 • Define an extended ABC architecture to support “ABC networks” • What functionality is important for future studies? • Implement an “ABC 2.0” that covers a subset of the network functions • Next step in functionality for Adasys activities using ABC? • A first step could be a PAN-like extension to current ABC... • How do we do this? • Form a specific ABC group? • ...or become part of existing adasys activity? • Define ABC oriented student projects to study and develop pieces for ABC?