Universal Inbox Bhaskaran Raman Randy Katz ICEBERG EECS
Universal Inbox Bhaskaran Raman, Randy Katz ICEBERG EECS, U. C. Berkeley 12/12/2021 1
Video Conference Calls Other Calls --------- E-Mail Voice-Mail 12/12/2021 2
Requirements • Universal mechanism for integration • Service architecture for scalability and high availability • Any-to-Any data type conversion mechanism • Mechanism for User-Preference specification • Name mapping across different types of end-devices 12/12/2021 3
Components of Initial Design • NINJA service model for scalability and fault-tolerance • Operators, Connectors and Paths for datatype conversion • User Preference & Name mappings stored in “directory service” • Preferences - should be in an active script (not a static database) 12/12/2021 4
Fitting the Components E-Mail APC Service Univ-Inbox Service Directory Service 12/12/2021 Univ-Inbox Service Voice Mail Laptop (VAT) 5
• The Services – Univ-Inbox Service - handles incoming and outgoing calls – Directory Service - stores name mappings and preferences – APC Service - Handles path creation for datatype conversion • Univ-Inbox services make RMI calls between themselves for call setup • Directory service invoked at caller end • APC service invoked at callee end 12/12/2021 6
U-Inbox Service for Cell-Phone Univ-Inbox Service Control UPSim Univ-Inbox Service Exports RMI Signaling Protocol Data IP-PAD 12/12/2021 7
Example Scenario 1 2 Univ-Inbox Service Data Path APC Service 12/12/2021 5 3 Directory Service 4 Univ-Inbox Service 6 8
Problems • Too slow: UPSim side, RMI • Speech <--> Text problems To do • • Real-time data-type conversion User-Preference script design Make services run in i. Space IP signaling protocol for call setup between Univ-Inbox services • DTMF signaling for vat 12/12/2021 9
- Slides: 9