Universal Inbox

1
Universal Inbox

• Bhaskaran Raman
• UCB, EECS

2
Reasons

• GSM base station infrastructure
• Ninja application to develop on the model of
  operators, paths services
• Cool thing to have, of course

3
The Devices

• Cell Phone
• E-mail
• VAT/Netmeeting on laptop
• POTS phone

4
Example Scenarios

• From cell-phone to cell-phone
• From cell-phone to POTS-phone
• From cell-phone to VAT
• From cell-phone to e-mail
• From e-mail to cell-phone

5
Issues

• Naming
• Policy - How to specify which end point a phone
  call should go to?
• How to model the service infrastructure?

6
Necessary Components of the Solution

• Name mapping database
• User Preference database to implement policies
• Data transformations to unify different
  end-points (codecs, speechtext)
• Call setup integration with data path

7
The Big Picture
Cell Phone
POTS Phone
Internet Service Inf
---- ---- ----
E-Mail
Laptop (VAT)
8
Service Infrastructure
Directory Service
Voice-Mail Service
Univ-Inbox Service
Operators
9
Scenario 1Cell-Phone to Cell-Phone
1. Dial Number
4. Create Data-Path
2. Intercept Call
Data Path (Null)
Univ-Inbox Service
Directory Service
3. Access Directory Service
5. Complete Call-Setup
10
Scenario 2Cell-Phone to POTS-Phone
1. Dial Number
4. Create Data-Path
2. Intercept Call
GSM
Univ-Inbox Service
Directory Service
Data Path
PCM
3. Access Directory Service
5. Complete Call-Setup
11
Scenario 3Cell-Phone to E-Mail
1. Dial Number
4. Create Data-Path
2. Intercept Call
GSM
Data Path
Directory Service
Univ-Inbox Service
PCM
3. Access Directory Service
6. Another Path
Voice-mail Service
5. Complete Call-Setup
PCM
Text
---- ---- ----
7. Send e-mail
12
Questions Doubts

• What is a Service?
• Something that creates paths glues things
  together
• How should a Service be implemented?
• What are the properties that a service should
  have?