The Case for ICEBERG

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
GSM
PSTN
IAP
IAP
iPOP
iPOP
WaveLAN
IAP
Pager
IAP
iPOP
iPOP
IAP
IAP
GSM
PSTN
iPOP administration domains
Multicast tunnels
Naming Servers Preference Registry
Personal Activity Coordinator APC Server
5
ICEBERG Internet-based CorE network BEyond the
thiRd Generation Anthony JosephRandy H.
KatzUC Berkeley
Bridge to the Future
S. S. 7

• http//iceberg.cs.berkeley.edu

Cellular Core Network
6
Naming Service
800-MEDIA-MGR UID mediamgr_at_cs.berkeley.edu
510-642-8248 UID hohltb_at_cs.berkeley.edu

2
PreferenceRegistry
Barbaras Desktop
1
3
hohltb Prefers Desktop mediamgr Cluster locn.
Bhaskars Cell-Phone
3
Automatic Path Creation Service
MediaManager Mail Access Service
7
Media Manager
Client
Client
Folder Store
Client
Media Manager Interface

• Transcoder Services
• Voicemail -gt Text Transcript
• Voicemail -gt Text Summary
• Voicemail -gtText Outline
• Email -gt Plain Audio
• Email -gt GSM Audio
• Voicemail -gt GSM Summary
• Voicemail -gt Audio Summary
• Voicemail -gt Skimmed Audio

Media Manager Service
Mail Access Interface
Mail Access Interface
Mail Access Interface
NinjaMail
POP
IMAP
8
Policy-BasedRedirection

• IF (9AM lt hour lt 5 PM) THEN Preferred-End-Point
  Office-Phone
• IF (5 PM lt hour lt 11 PM) THEN Preferred-End-Point
  Home-Phone
• IF (11 PM lt hour lt 9 AM) THEN Preferred-End-Point
  Voice-Mail

Personal Activity Coordinator
Other Personal State
Callee location Callee state
Preference Registry
Per Call State e.g., Caller ID Time of
Day Caller End Point Type
Callees Preferred End Point
User Preference Profiles
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_at_iceberg.cs.berkeley.edu