universal inbox

Download Universal Inbox

Post on 17-Jun-2015




0 download

Embed Size (px)


  • 1. Universal Inbox: Extensible Personal Mobility and Service Mobility in an Integrated Network Bhaskaran Raman, Randy H. Katz, Anthony D. Joseph ICEBERG, EECS, U.C.Berkeley Home Phone Voice Mail Pager Cell Phone Office Phone Calls duringbusiness hours Calls in the evening Anonymous Calls Friends &family calls E-Mail Important e-mail headers E-mail access via phone

2. Motivating Scenario Personal Mobility Service Mobility 3. Problem Statement

  • Requirement
    • Service integration and personalization
  • Goals
    • Any-to-any capability
    • Extensibility : ease of adding new end-points
    • Scalability : global scale operation
    • Personal mobility and Service mobility

Communication devices Communication services 4. ICEBERG: An IP-Centric Middleware Approach ICEBERG Network (Internet) PSTN GSM Pager WaveLAN GSM PSTN 5. Internet-based Infrastructure

  • Components in the Internet:openmodel
  • Leverageproxyand cluster architectures
  • Independent components:
    • Can be independently andincrementally deployed

6. Design Principles

  • Separation of functionality
    • Separationindependent and reusable components
    • Reuseeasy extensibility
    • Shared network servicesEconomy of scale
  • Network and device independence
    • Needed for extensibility to new devices
  • Push control towards callee
    • In current communication networks, caller has control
    • Callee needs to have control for flexible handling of incoming communication

7. Caller Callee Data Transformation Name Mapping & Translation Preference Management An Example Scenario 8. Common Functionalities

  • Any-to-any data transformation
    • For communication between heterogeneous devices
    • Devicedata-type independence
    • Automatic Path Creation (APC) service
  • User preference based ubiquitous redirection
    • Forpersonalizationof communication
    • Achieves thecontrol to calleedesign principle
    • Preference Registry service

9. Common Functionalities

  • Device name mapping and translation
    • For dealing with multiple user identities and different name spaces
    • Devicename independence
    • Naming service
  • Also, gateways to access networks at different locations
    • Providenetwork independence
    • ICEBERG Access Points

10. Bhaskars Cell-Phone Barbaras Desktop Illustrating Extensibility Automatic Path Creation Service 510-642-8248 UID: hohltb@cs.berkeley.eduNaming Service 1 hohltb: Prefers Desktop Preference Registry 2 3 MediaManager Mail Access Service 11. 800-MEDIA-MGR UID: mediamgr@cs.berkeley.edumediamgr: Cluster locn. Bhaskars Cell-Phone Barbaras Desktop Naming Service Preference Registry Automatic Path Creation Service 1 2 MediaManager Mail Access Service 3 Bhaskars PSTN Phone 12. 510-642-8248 UID: hohltb@cs.berkeley.eduhohltb: Prefers Desktop Bhaskars Cell-Phone Barbaras Desktop Naming Service Preference Registry Automatic Path Creation Service 1 Bhaskars PSTN Phone 2 3 MediaManager Mail Access Service 13. Extensibility

  • Name-space
    • Hierarchical
    • New name-spaces added by creating a new sub-tree at root
  • Automatic Path Creation service
    • Operators can be plugged in
    • Old operators are reusable
  • Set of ICEBERG Access Points
    • New IAPs can be added independent of existing ones
    • Allold IAPs are reachable from the new one

IAP IAP IAP IAP IP-Addrs Tel. No:s Email-addrs Pager no:s 14. Implementation Experience

  • Extensibility
    • Universal Inbox set of features extended to manydeviceandserviceend-points
  • Scalability
    • Components tested for latency and scaling bottlenecks

15. Extensions to the Universal Inbox Step-wise addition of eight different devices and services to the system Each step involves addition of an IAP for the device/network or the service Each step integrates the device/service withALLexisting ones 16. Implementation Experience with Extension

  • Examples of extension:
    • IAP for MediaManager
      • Allow access to the MediaManager service
      • ~ 700 lines of Java
      • No other component had to be touched
    • Operators for G.723
      • Getting codec to work required effort
      • But, adding to APC was ~two hours of work( simple API for adding operators)

17. Lessons learned: What was easy?

  • Extension to include a new communication service or device
    • Build an IAP
    • Add appropriate operators

Effort involved in building a service is independent of the number of networks it is made available on 18. Scalability Analysis

  • Shared infrastructure components
    • Scaling and provisioning concerns
  • Three shared core components are:
    • APC
    • Preference Registry
    • Naming service

19. Scalability Analysis: APC

  • Performance for the following operators
    • Null (copies input to output)
    • Toast(PCM to GSM)
    • Untoast(GSM to PCM)
  • Path creationlatencyandthroughputmeasured as a function of increasing load
  • 500MHz Pentium-III 2-way multiprocessor running Linux-2.2 with IBMs JDK 1.1.8

20. Path Creation: Latency vs. Load Toast Operator Untoast Operator About 50ms latency for path creation 21. Path Creation: Throughput vs. Load Toast Operator Untoast Operator About 7.2 path creations/sec at a load of 64 simultaneous paths 22. Calculation of Scaling

  • On average
    • 2.8 calls/hour/user
    • Average duration of calls (path) is 2.6 minutes
  • Using these
    • 571 userscan be supported by a two-node APC service
    • Telephone network uses expensive TRAU at the Inter-Working Function for these transformations

23. Related Work: State-of-the-Art

  • Commercial services
    • Concentrate on functionality
    • No any-to-any capability
  • Research projects
    • Mobile People Architecture: Personal Proxies
    • Telephony Over Packet networkS
    • UMTS
  • Not all issues addressed
    • Infrastructure support for network integration
    • Extensibility
    • Scalability
    • Personal mobility + Service mobility

24. Summary

  • Universal Inbox: metaphor for any-to-any communication and service access
  • Internet-based infrastructure
  • Personal mobility
    • redirection by preference registry
  • Service mobility
    • result of the any-to-any capability
  • Architecture viable for global operation
    • IAPs can be developed and deployed by independent service providers
  • Extensibility
    • Made easy by the separation and reuse of functionality

25. The ICEBERG Project http://iceberg.cs.berkeley.edu/ (Presentation running under VMWare under Linux)