Bhaskaran Raman, Randy Katz ICEBERG EECS, U.C.Berkeley

Slides:



Advertisements
Similar presentations
Aspire Vertical Markets Law Office. Law Office Solutions.
Advertisements

Aspire Vertical Markets Executive Suite Solution.
Vertical Markets Education, K-12 School. K – 12 Education Solution.
Fall VoN 2000 SIP for IP Communications Jonathan Rosenberg Chief Scientist.
Service Encapsulation in ICEBERG Bhaskaran Raman ICEBERG, EECS, U.C.Berkeley Presentation at Ericsson, Sweden, June 2001.
111 © 2003 Cisco Systems, Inc. All rights reserved. CVP 3.x “Full Centralized” Comprehensive: Detailed Call Flows 111 © 2003, Cisco Systems, Inc. All rights.
Universal Inbox: Personal Mobility and Service Mobility in an Integrated Network Bhaskaran Raman ICEBERG, EECS, U.C.Berkeley Home Phone Voice Mail Pager.
IP Communications Services Redefining Communications Teresa Hastings Director WorldCom SIP Services Conference – April 18-20, 2001.
MXIE overview 5/4/ Update1. MXIE Media Exchange Interface for End Users 5/4/ Update2.
SIP Simplified August 2010 By Dale Anderson. SIP Simplified Session Initiation Protocol Core of SIP specifications is documented in IETF RFC 3261 Many.
Problem Statement Requirement –Service integration and personalization Goals –Any-to-any capability –Extensibility: ease of adding new end-points –Scalability:
Pricing, Charging, & Billing Experiments Using the H.323 Gateway Jimmy Shih, Anthony Joseph, Randy Katz.
Touring ICEBERG -- An Overview and Tutorial Helen J. Wang January 10, 2000.
Iceberg Preferences Manager Rahul Biswas and Bhaskar Raman ISRG Winter 2000 Retreat.
16-Jun-151 PCS in Telephony & Intelligent Network versus ICEBERG Bhaskaran Raman Network Reading Group Friday, Feb
Metrics for Evaluating ICEBERG ICEBERG Retreat Breakout Session Jan 11, 2000 Coordinators: Chen-Nee Chuah & Jimmy Shih.
Towards I-Space Ninja Mini-Retreat June 11, 1997 David Culler, Steve Gribble, Mark Stemm, Matt Welsh Computer Science Division U.C. Berkeley.
EJB Design. Server-side components Perform –complex algorithms –high volume transactions Run in –highly available environment (365 days/year) –fault tolerant.
The Case for ICEBERG Integrated services from diverse networks-- “PANS” (Potentially Any Network Services) Service infrastructure that allows user level.
The ICEBERG H.323 Computer Telephony Service Jimmy Shih, Anthony Joseph, Randy Katz.
Chapter 2: Application layer  2.1 Web and HTTP  2.2 FTP 2-1 Lecture 5 Application Layer.
1 Internet-Scale Systems Research Group Eric Brewer, David Culler, Anthony Joseph, Randy Katz, Steven McCanne Computer Science Division, EECS Department.
Problem Definition Data path –Created by the Automatic Path Creation (APC) component –Service: program with well-defined interface –Operator: stateless.
The internet and the WWW
Damian Zolich, TTCN-3 User Conference 2011
Universal Inbox: Extensible Personal Mobility and Service Mobility in an Integrated Network Bhaskaran Raman, Randy H. Katz, Anthony D. Joseph ICEBERG,
Design Decisions / Lessons Learned Monday 21 August : :35 Top-level design decisions Rationale for IP-based approach Why an infrastructure.
H.323 An International Telecommunications Union (ITU) standard. Architecture consisting of several protocols oG.711: Encoding and decoding of speech (other.
Design Decisions / Lessons Learned Monday 21 August : :35 Top-level design decisions Rationale for IP-based approach Why an infrastructure.
A ISP free video conferencing application for mobile devices using wireless and VoIP Technology.
Internet Real-Time Laboratory demonstration Internet telephony, ubiquitous computing and ad-hoc networking Prof. Henning Schulzrinne (Presented by Ajay.
Media Gateway Figure 8-1 Comparing PSTN and VoIP voice call setup.
Countermeasures of Spam over Internet Telephony in SIP.edu Campuses with MySQL and LDAP Support Speaker: Chang-Yu Wu Adviser: Dr. Quincy Wu School: National.
NETWORK HARDWARE AND SOFTWARE MR ROSS UNIT 3 IT APPLICATIONS.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Living in a Network Centric World Network Fundamentals – Chapter 1.
Mario D’Silva National Technology Specialists Unified Communications UNC307.
 Problem Definition  Presented by Sushant and Alex Overview of the problem space Scenario Issues Example (plant care example) Discussion conclusion open.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Living in a Network Centric World Network Fundamentals – Chapter 1.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Living in a Network Centric World Network Fundamentals – Chapter 1.
Version 4.0 Living in a Network Centric World Network Fundamentals – Chapter 1.
Telephone Procedures Mrs. Dayley Administrative Procedures.
Multi-homing for small scale fixed network Using Mobile IP and NEMO IETF60 MIP6 Kenichi Nagami(INTEC Netcore) Satoshi Uda (JAIST) Nobuo Ogashiwa(INTEC.
Postech DP&NM Lab Session Initiation Protocol (SIP) Date: Seongcheol Hong DP&NM Lab., Dept. of CSE, POSTECH Date: Seongcheol.
INTERNET PROTOCOL TELEVISION (IP-TV)
IP Telephony (VoIP).
SIX MONTHS INDUSTRIAL TRAINING REPORT
Deploying IP Telephony
Design Decisions / Lessons Learned
Living in a Network Centric World
Living in a Network Centric World
ICEBERG: An Internet-Based, Integrated Communication System
INTERNET PROTOCOL TELEVISION (IP-TV)
Internet Real-Time Laboratory demonstration
Modelling the internet
Living in a Network Centric World
Modelling the internet
Living in a Network Centric World
sipc e*phone sipd Netmeeting e*phone e*phone Clouds H.323 SIP RTSP
Living in a Network Centric World
ICEBERG Release Version 0
Living in a Network Centric World
Universal In-box Bhaskaran Raman Iceberg, EECS ISRG Retreat, Jan 2000
Living in a Network Centric World
Living in a Network Centric World
Problem Statement Communication devices Communication services
Touring ICEBERG -- An Overview and Tutorial
Living in a Network Centric World
Substation Automation IT Needs
Introduction to Computer Networks
Living in a Network Centric World
Presentation transcript:

Bhaskaran Raman, Randy Katz ICEBERG EECS, U.C.Berkeley Universal Inbox Bhaskaran Raman, Randy Katz ICEBERG EECS, U.C.Berkeley April 19

Scenario Outdoors Office: 9 AM - 5 PM Home: 6 PM - 10 PM Video Conference Calls Other Calls Outdoors Office: 9 AM - 5 PM Video Conference Calls Other Calls -------------------- Home: 6 PM - 10 PM E-Mail Anonymous Calls Voice-Mail Night: 10 PM - 6 AM April 19

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 April 19

Components of Initial Design NINJA service model for scalability and fault-tolerance Operators, Connectors and Paths for data-type conversion User Preference & Name mappings stored in “directory service” Preferences - should be in an active script (not a static database) April 19

Fitting the Components 15-Apr-19 Fitting the Components E-Mail APC Service Univ-Inbox Service Univ-Inbox Service Univ-Inbox Service Univ-Inbox Service Univ-Inbox Service Laptop (VAT) Directory Service Voice Mail April 19

Univ-Inbox services make RMI calls between themselves for call setup The Services Univ-Inbox Service - handles incoming and outgoing calls Directory Service - stores name mappings and preferences APC Service - Handles path creation for data-type conversion Univ-Inbox services make RMI calls between themselves for call setup Directory service invoked at caller end APC service invoked at callee end April 19

U-Inbox Service for Cell-Phone Univ-Inbox Service Univ-Inbox Service Control Exports RMI Signaling Protocol UPSim Data IP-PAD April 19

Example Scenario 1 2 Univ-Inbox Service Directory Service Data Path 3 4 5 APC Service Univ-Inbox Service 6 April 19

Problems To do Too slow: UPSim side, RMI Speech <--> Text problems To do Real-time data-type conversion User-Preference script design Make services run in iSpace IP signaling protocol for call setup between Univ-Inbox services DTMF signaling for vat April 19

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2025 SlidePlayer.com. Inc. All rights reserved.