ICEBERG: An InternetBased, Integrated Communication System

1
ICEBERGAn Internet-Based, Integrated
Communication System

• Helen J. Wang
• ICEBERG Project, U C Berkeley
• http//iceberg.cs.berkeley.edu/
• August 1, 2000

2
Motivation

• Lack support for
• Integrated use of heterogeneous devices (old
  new)
• Rapid arbitrary communication service
  customization

3
Limitations of Existing Systems

• Telecommunications network
• engineered with one app and device in mind
• Existing Internet Telephony systems
• potential of easy service creation
• scalability, availability and fault tolerance not
  fully addressed

4
How good is a communication system?

• Functionality communication services it can
  support, and the ease of creating them
• Viability scalability, robustness, wide-area
  operable
• ICEBERG a viable Internet-core communication
  system and infrastructure that supports
  heterogeneity and rapid, arbitrary communication
  service customization and creation

5
Architecture Goals

• Any-to-any communication
• inter-working (ICEBERG Access Point), composition
  of data transformation (Automatic Path Creation
  Service)
• Personal mobility
• unique ID, name mapping (Name Mapping Service)
• Personalized communication services
• preference storage and management (Preference
  Registry)
• Enable user-activity driven services
• activity tracking (Person Activity Coordinator)

6
Control ArchitectureComponents and Their
Operations
Alice_at_domain1
Bob_at_domain2
Pick up
Data Path
7
ICEBERG Architecture An Overview
Access Network Plane
ICEBERG Network Plane
Clearing House
ISP Plane
ISP1
ISP2
ISP3
8
Acronyms Lookup

• APC Automatic Path Creation
• CA Call Agent
• IAP ICEBERG Access Point
• iPOP ICEBERG Point of Presence
• NMS Name Mapping Service
• PAC Personal Activity Coordinator
• PR Preference Registry

9
Leverage Cluster Computing Platforms

• iPOP must be scalable and robust leverage
  cluster computing platforms such as Ninja, AS1
• Our requirements
• highly available service invocation Ninja
• fault tolerant service session AS1
• session state maintained on client (IAP)
• iPOP on Ninja augmented with client heartbeat
  support from AS1