1. The Case for ICEBERG Integrated services from diverse networks-- “PANS” (Potentially Any Network Services) Service infrastructure that allows user level service creation, dynamic customization, configuration Why Internet-based core? –Ease of service creation, customization –Low deployment cost –Supports heterogeneity –Bandwidth efficient

2. Design Goals Potentially Any Network Services (PANS) –Any service can from any network by any device; network/device independence in system design Personal Mobility –Person as communication endpoint with single identity Service Mobility –Retain services across networks Easy Service Creation and Customization –Allow callee control & filtering Scalability, Availability, Fault Tolerance Security, Authentication, Privacy

3. Architectural Elements ICEBERG Access Point (IAP) –Encapsulates network specific gateway (control and data) ICEBERG Point of Presence (iPOP) –Performs detailed signaling »Call Agent: per communication device per call party »Call Agent Dispatcher: deploy call agent Name Mapping Service –Mapping between iUID (Iceberg Unique ID) and service end point Preference Registry –Contains user profile including service subscription, configuration and customization Person Activity Coordinator (PAC) –Tracks dynamic information about user of interest Automatic Path Creation Service –Creates datapath among participants’ communications devices

4. Architectural View iPOP administration domains PSTN GSM Pager WaveLAN GSMPSTN IAP iPOP IAP Multicast tunnels Personal Activity Coordinator APC Server Naming Servers Preference Registry

5. ICEBERG: Internet- based CorE network BEyond the thiRd Generation Anthony Joseph Randy H. Katz UC Berkeley http://iceberg.cs.berkeley.edu Cellular “Core” Network Bridge to the Future S. S. 7

6. 800-MEDIA-MGR UID: mediamgr@cs.berkeley.edu 510-642-8248 UID: hohltb@cs.berkeley.edu hohltb: Prefers Desktop mediamgr: Cluster locn. Bhaskar’s Cell-Phone Bhaskar’s PSTN Phone Barbara’s Desktop Naming Service Preference Registry Automatic Path Creation Service 1 1 2 2 3 3 MediaManager Mail Access Service 3’

7. Media Manager Transcoder Services Voicemail -> Text Transcript Voicemail -> Text Summary Voicemail ->Text Outline Email -> Plain Audio Email -> GSM Audio Voicemail -> GSM Summary Voicemail -> Audio Summary Voicemail -> Skimmed Audio Mail Access Interface NinjaMail Media Manager Interface Media Manager Service Client Folder Store Mail Access Interface POP Mail Access Interface IMAP

8. Policy-Based Redirection Home Phone Voice Mail Pager Cell Phone Office Phone Calls during business hours Calls in the evening Anonymous Calls Friends & family calls E-Mail Important e-mail headers E-mail access via phone IF (9AM < hour < 5 PM) THEN Preferred-End- Point = Office-Phone IF (5 PM < hour < 11 PM) THEN Preferred-End- Point = Home-Phone IF (11 PM < hour < 9 AM) THEN Preferred-End- Point = Voice-Mail Callee location Callee state Personal Activity Coordinator Preference Registry User Preference Profiles Other Personal State Per Call State e.g., Caller ID Time of Day Caller End Point Type Callee’s Preferred End Point

9. Implementation and Current Status Version 0 Release: June 2000 –Functional implementations of major architectural components: Call Agent, Preference Registry, Preference Manager, Automatic Path Creation, Name Mapping Service –Support for VAT IPphones, GSM cell phones, instant messaging, Ninja Jukebox, multimodal email access –Service handoff between IPphones and GSM cell phones –Callee preferences via GUI or script Ninja ISpace implementation limits performance; Version 1 Release on VSpace 2, with better fail over/scalability features & reduced IPC latencies Release information: –http://iceberg.cs.berkeley.edu/release/ –iceberg-devel@iceberg.cs.berkeley.edu