Dredgie 3rd Review Draft Qwest Presentation.ppt

1,042 views
943 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,042
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This illustrates release 5 of 3G Call flow build: First call remains in the visited network – the user has service capability in this network and does not have to go back to the home network. The P-CSCF proxies the call to the S-CSCF which handles the service aspects for the caller, the S-CSCF then uses the I-CSCF/HSS combination to locate the called party and the call flows to this user. The second call flows into the home network (note this could also of occurred with the first call to validate the service from a home S-CSCF.) This call uses the home HSS and routes to a user in the home network. Abbreviations: Proxy-Call State Control Function, Serving-CSCF, Interrogating-CSCF and Home Subscriber Server. The Serving-CSCF handling call origination performs an analysis of the destination address, and determines whether it is a PSTN destination, a subscriber of the same network operator or a subscriber of a different operator. If the analysis of the destination address determined that it belongs to a subscriber of a different operator, the request is forwarded (optionally through an I-CSCF within the originating operator’s network) to a well-known entry point in the destination operator’s network, the I-CSCF. The I-CSCF queries the HSS for current location information. The I-CSCF then forwards the request to the S-CSCF. This is call flow procedure S-S#1b (if a firewall is used) or S-S#1a (if no firewall is used). If the analysis of the destination address determines that it belongs to a subscriber of the same operator, the S-CSCF forwards the request to a local I-CSCF, who queries the HSS for current location information. The I-CSCF then forwards the request to the SCSCF. This is call flow procedure S-S#2.
  • Dredgie 3rd Review Draft Qwest Presentation.ppt

    1. 1. Ubiquity Software Corporation ~ SIP ~ Simple Protocol - Profound Implications
    2. 2. Working Agenda <ul><li>Introduction to Ubiquity Software Corporation </li></ul><ul><li>An overview of the Session Initiation Protocol (SIP) </li></ul><ul><li>SIP in the marketplace </li></ul><ul><li>Implications for Qwest </li></ul><ul><li>Worldwide service provider SIP initiatives </li></ul><ul><li>How can Ubiquity help? </li></ul><ul><li>Going forward </li></ul><ul><li>Question & answer session </li></ul>
    3. 3. Introduction to Ubiquity <ul><li>Six years of experience developing advanced telephony applications for service providers </li></ul><ul><li>Offices in US; UK and Canada </li></ul><ul><li>Management team / directors include recognized authorities of SIP Technology: </li></ul><ul><ul><li>Michael Doyle – CTO </li></ul></ul><ul><ul><li>Professor Henning Schulzrinne - Columbia University (Board Member) </li></ul></ul><ul><ul><li>Martin De Prycker – CTO, Alcatel (Board Member) </li></ul></ul><ul><li>Raised US$42 million in venture capital - August 2000 </li></ul><ul><ul><li>CapVest Equity Partners Fund, L.P; </li></ul></ul><ul><ul><li>Celtic House International; </li></ul></ul><ul><ul><li>JK&B Capital; </li></ul></ul><ul><ul><li>Alcatel </li></ul></ul><ul><li>Recognized authorities in signaling and programming languages </li></ul><ul><ul><li>SIP; JAVA </li></ul></ul><ul><li>Active in many associated standards bodies and working groups </li></ul><ul><ul><li>IETF; SIP; SOAP; JAIN SIP LITE </li></ul></ul><ul><li>Founders of the SIP Center www.sipcenter.com </li></ul><ul><li>Co-authors of SIPstone (SIP server performance benchmarking) </li></ul><ul><li>First to enable SIP click-to-dial from within Microsoft applications </li></ul>
    4. 4. Current Relationship With Qwest <ul><li>NEED THIS INFO – SALES? </li></ul>
    5. 5. Henning Schulzrinne <ul><li>Associate Professor, Columbia University </li></ul><ul><ul><li>Department of Computer Science and Electrical Engineering </li></ul></ul><ul><li>Ubiquity Software, Corp. Board Member </li></ul><ul><ul><li>Since March 2001 </li></ul></ul><ul><li>Acknowledged as the architect of SIP </li></ul><ul><ul><li>Co-Authored RFC2543 with aid of student and colleagues </li></ul></ul><ul><li>Other related experience Includes: </li></ul><ul><ul><li>Internet telephony; Internet multimedia; quality-of-service; mobility; security </li></ul></ul><ul><li>Other co-authored RFC’s Include: </li></ul><ul><ul><li>RTSP & RTP </li></ul></ul>
    6. 6. A Brief History Of SIP <ul><li>Feb. 1996: earliest Internet drafts </li></ul><ul><li>Feb. 1999: Proposed Standard </li></ul><ul><li>March 1999: RFC 2543 </li></ul><ul><li>April 1999: first SIP bake-off </li></ul><ul><li>November 2000: SIP accepted as 3GPP signaling protocol </li></ul><ul><li>December 2001: 6th bake-off, 200+ participants </li></ul><ul><li>March 2001: 7th bake-off, first time outside U.S. </li></ul>
    7. 7. VoIP Signaling Architectures <ul><li>MGCP, Megaco = master / slave </li></ul><ul><li>H.323 = (Mostly) single administrative domain </li></ul><ul><li>SIP = Peer-to-peer, cross domain </li></ul>
    8. 8. VoIP Architectures - X X CPL - - X Servlets - - X CGI Scripting - - X Generic Events Limited ? X Extensible - X X End System Control Unlikely Fixed Set X Multimedia Single-domain - X Third-Party Control - ? X Multiple Domains Megaco/MGCP H.323 SIP Feature
    9. 9. SIP Inheritance <ul><li>URLs: </li></ul><ul><ul><li>General references to any Internet service (“forward to email”) </li></ul></ul><ul><ul><li>Recursive embedding </li></ul></ul><ul><li>HTTP: </li></ul><ul><ul><li>Basic request/response format, status codes, authentication, … </li></ul></ul><ul><ul><li>Proxies (but no caching) </li></ul></ul><ul><ul><li>CGI programming interface; servlets </li></ul></ul><ul><li>Email/SMTP: </li></ul><ul><ul><li>Addressing ( [email_address] ) </li></ul></ul><ul><ul><li>MX  SRV records for load balancing and redundancy </li></ul></ul><ul><ul><li>Header / body separation, MIME </li></ul></ul>
    10. 10. SIP Design Choices <ul><li>Transport protocol neutrality: </li></ul><ul><ul><li>Run over reliable (TCP, SCTP) and unreliable (UDP) channels, with minimal assumptions </li></ul></ul><ul><li>Request routing: </li></ul><ul><ul><li>Direct (performance) or proxy-routed (control) </li></ul></ul><ul><li>Separation signaling vs. media description: </li></ul><ul><ul><li>Can add new applications or media types, SDP  SDPng </li></ul></ul><ul><li>Extensibility: </li></ul><ul><ul><li>Indicate and require proxy and UA capabilities </li></ul></ul>
    11. 11. What is SIP? <ul><li>A Session Initiation Protocol </li></ul><ul><ul><li>Ratified as RFC2543 </li></ul></ul><ul><ul><ul><li>Being refined in RFC2543bis </li></ul></ul></ul><ul><li>A signaling protocol </li></ul><ul><ul><li>Call-control mechanism </li></ul></ul><ul><ul><ul><li>Setup – modification – teardown </li></ul></ul></ul><ul><ul><li>Resolves call endpoints </li></ul></ul><ul><ul><ul><li>Domain name to IP addresses </li></ul></ul></ul><ul><ul><li>Describes the session </li></ul></ul><ul><ul><ul><li>Typically SDP (Session Description Protocol) </li></ul></ul></ul>
    12. 12. SDP’s Role in SIP <ul><li>Session Description Protocol - RFC2327 </li></ul><ul><ul><li>Describes session information to potential session participants </li></ul></ul><ul><li>Carried within the SIP message body </li></ul><ul><li>Defines call attributes </li></ul><ul><ul><li>Structured language to describe session characteristics </li></ul></ul><ul><li>Indicates transport protocol and parameters </li></ul><ul><ul><li>Typically, RTP & payload format </li></ul></ul><ul><li>Establishes port numbers on which media should be sent </li></ul><ul><ul><li>Typically, UDP ports 1024 to 65535 </li></ul></ul><ul><li>Negotiates / exchanges available media capabilities </li></ul><ul><ul><li>Audio, video, shared apps, chat,… including encoding methods </li></ul></ul>
    13. 13. SIP Attributes <ul><li>Light & simple but flexible </li></ul><ul><ul><li>Few transactions </li></ul></ul><ul><ul><li>Scalable and extensible </li></ul></ul><ul><li>Uses ‘Internet’ formats & components </li></ul><ul><ul><li>Text-based messages - HTTP/1.1 message syntax </li></ul></ul><ul><ul><li>Internationalized: ISO 10646 char. set, UTF-8 encoding </li></ul></ul><ul><li>Re-uses common ratified standards </li></ul><ul><ul><li>SDP; MIME; DNS; URL; HTTP authentication </li></ul></ul><ul><li>Enables non-standard call set-up information </li></ul><ul><ul><li>‘ Useful’ information may be carried within payload </li></ul></ul><ul><ul><li>Allows devices to make intelligent call-handling decisions </li></ul></ul><ul><ul><li>Invokes various high-level services </li></ul></ul><ul><li>URLs as identifiers </li></ul><ul><ul><li>Easy to re-direct to web resources (web push/pull) </li></ul></ul><ul><li>Multicast ready </li></ul><ul><ul><li>For scaling and announcements (mostly future use) </li></ul></ul>
    14. 14. Basic SIP Call Flow sip:jim@zaffire.net (192.1.10.100) sip:jane@ubiquity.net (204.1.64.200) qwest.net 192.1.10.1 ubiquity.net 204.1.64.200 “ CALL JANE” 1. Register 2. Initiate call request (sip:jane@ubiquity.net) 3. DNS – resolve IP Address (ubiquity.net) 4 . Forward call request to remote proxy 5. Locate user in registry (jane) 6. Forward call request to end-user 7. Accept call request 8. Establish media connection UA UA A B SIP Proxy Root DNS Cache Local Secondary DNS Registry Primary DNS media transport network SIP Proxy Registry (3) (3) (3) (1) (1) (1) (1) (4) (4) (5) (6) (2) (7) (7) (7) (7) SIP signaling network
    15. 15. Standardization <ul><li>SIP and SIPPING working group are some of the most active in IETF </li></ul><ul><li>About 120 active internet drafts related to SIP </li></ul><ul><li>Typically, 400 attend WG meetings at IETF </li></ul><ul><li>80-20% – 20% of the technical work takes 80% of the time! </li></ul>Participation in SIP Bake-Offs (SIPit) From RFC Release to Present Day 0 10 20 30 40 50 60 Organizations Participating 04-99 08-99 12-99 04-00 08-00 12-00 08-01 Source: SiPiT Date 57 57 45 36 26 15 16 0
    16. 16. Technology Adoption
    17. 17. Columbia CS Phone System Unified Messaging Server RTSP Media Server Conferencing Server (MCU) Sun Solaris PC Linux/FreeBSD/NT Proxy/Redirect Server T1 PSTN Nortel Meridian PBX sipum RTSP sipconf rtspd 802.11b Wireless “ Plug ‘n SIP POTS Converter Cisco 2600 sipd SIP Proxy CAS/PCM SIP/RTP Video Conferencing Mobile PDA SIP Phone Black Phone sipc SIP Phone SIP Phone Data base MySQL User Database Data base LDAP Server SIP/RTP H.323/RTP
    18. 18. What Problems Does It Solve? <ul><li>Integration of telephony with other media </li></ul><ul><li>Telephony becomes another element of the IP / Internet mix </li></ul><ul><li>Lowers the barrier for application development -- making it easier to be innovative </li></ul><ul><ul><li>Minimal clients and feature programming </li></ul></ul><ul><ul><li>H323 and IN were/are not easy </li></ul></ul><ul><li>Industry-standard platforms, web servers and IP infrastructures enable new services </li></ul><ul><ul><li>Most of these platforms already exist in the network </li></ul></ul><ul><ul><li>SIP helps tie them together </li></ul></ul><ul><li>New signaling and services architecture that is widely adopted </li></ul><ul><ul><li>By service providers and vendors </li></ul></ul>
    19. 19. Impact on Service Providers <ul><li>Shift of telephony value add to the edge </li></ul><ul><li>Facilities-less network service provider  separation of bit transport and services </li></ul><ul><ul><li>AOL, Yahoo, MSN... </li></ul></ul><ul><li>It destroys the centralized business model of telephony </li></ul><ul><li>Reduces the time to create new value-add services </li></ul><ul><li>Easier to add vertical-market applications (integration with IT infrastructure) </li></ul><ul><li>Application-creation by non-specialists, similar to web services </li></ul><ul><li>More personalized service model where the user has a greater level of control </li></ul>
    20. 20. Market Dynamics <ul><li>Converged PBX (CBX) </li></ul><ul><ul><li>Packet-based PBX; 4.1% of worldwide PBX sales in 2000; 19% in 2004 </li></ul></ul><ul><li>PC CBX </li></ul><ul><ul><li>Small system for small business (CPE/CLE) </li></ul></ul><ul><li>IP CBX </li></ul><ul><ul><li>Larger systems (carrier network based) </li></ul></ul>VoIP PBX/CBX Trends
    21. 21. Network-Based Applications Services
    22. 22. High-Level Sip Opportunities <ul><li>Presence management </li></ul><ul><li>Personal & session mobility </li></ul><ul><li>User profiling </li></ul><ul><li>Web call centers </li></ul><ul><li>Desktop call management </li></ul><ul><li>Voice-enabled e-commerce </li></ul><ul><li>Mobile (3GPP) adoption </li></ul><ul><li>Location services </li></ul><ul><li>Unified messaging </li></ul><ul><li>Instant messaging </li></ul>
    23. 23. Mobility, Presence & Profiles SIP Signaling Network Application Services Broker User profile Database Voicemail Server [email_address] [email_address] <ul><li>Services associated with a user not a device </li></ul><ul><ul><li>User may have multiple associations </li></ul></ul><ul><li>Presence management for single ‘number’ reachability </li></ul><ul><li>Selective call forwarding based on profile </li></ul><ul><ul><li>E.g., unknown caller transferred to voicemail </li></ul></ul>ASB Data Base VM Server BOSS MOM Long Distance Slammer REGISTER REGISTER PROFILE CALL OK CALL OK UNKNOWN – SEND TO VM
    24. 24. Voice-Enabled Help Desk Call Center Application Voice-Enabled e-Commerce <ul><li>Customer clicks-to-dial from a web page – pertinent details popped </li></ul><ul><li>Customer browses website then navigates through an IVR </li></ul><ul><li>Representative shares media (web push) with customer (e.g., technical documentation) </li></ul><ul><li>Video conferencing initiated – negotiation, “show me” </li></ul><ul><li>Customer is connected to the appropriate representative </li></ul>SIP Signaling Network Application Services Broker Integrated Voice Response Server Web Server Name: Bert Blogs Occup: Marketing Model: Dishwasher Purchased: 11/23/96 Last Contact: 1/9/99 Last Service: 9/3/98 VoiceXML VoiceXML ASB IVR Server
    25. 25. 3rd Generation Partnership Project Calling Party Application services broker – services and applications environments Home Network # 1 Service Control Authorize QoS Resources Resource Reservation CSCF = Call State Control Function – All SIP-based signalling platforms P = Proxy – 1 st . point-of-contact. emergency service break-out and triggers local services (e.g., directory, QoS reservations) S = Serving – Determines what operator a subscriber belongs too. Provides subscriber services (call forward, VPN, etc.) I= Interrogating – Well-known entry point to different operator – ;oad Balancer for HSS HSS = Home Subscriber Server = Current location information (superset of GSM HLR (Home Location Register)) Called Party Home Network # 2 Well-Known Entry Point 3GPP Release 5 - sample call between different service providers Diameter P- CSCF Data base S- CSCF ASB P- CSCF S- CSCF I- CSCF HSS Server Serving GPRS Support Node (SGSN) Gateway GPRS Support Node (GGSN) GPRS = General Packet Radio Service Radio Access Network
    26. 26. Location-Based Mobile Services 1. Taxi service requests user location from HSS 2. Location information used to retrieve list of cab companies in the area 3. User selects taxi service – call established to cab company 4. Cab company simultaneously updated with general location – closest cab cispatched Application Services Broker Home Subscriber Service Web Server SIP Signaling Network (3) Dial-a-Cab Dial-a-Cab ASB HSS Cab 1 Cab 2 Cab 1 Cab 2 (1) (1) (2) (3) (2) (4) Server
    27. 27. Impact to Qwest <ul><li>Does Qwest need to invest in disruptive technology? </li></ul><ul><ul><li>Have the CLEC threats diminished? </li></ul></ul><ul><ul><li>Will box/software providers playing in the edge be able to sell CLASS features? </li></ul></ul><ul><li>Should Qwest fall back on traditional revenue streams? </li></ul><ul><ul><li>New services </li></ul></ul><ul><ul><li>Adding value to popular services </li></ul></ul><ul><ul><li>Reducing costs </li></ul></ul><ul><li>Should Qwest embrace or slow down technology adoption process? </li></ul><ul><ul><li>Big enough to through a large spanner in the works </li></ul></ul><ul><li>Is SIP an opportunity or a threat for / to Qwest? </li></ul>
    28. 28. Service Provider Initiatives <ul><li>Level 3 </li></ul><ul><li>WorldCom </li></ul><ul><li>AT&T </li></ul><ul><li>British Telecom </li></ul><ul><li>Telia </li></ul><ul><li>Microsoft </li></ul>
    29. 29. Level 3 <ul><li>Very active in the SIP arena </li></ul><ul><ul><li>Integral part of their softswitch strategy </li></ul></ul><ul><ul><li>Active in standards bodies and working groups </li></ul></ul><ul><ul><li>Announced industries first SIP-based IP voice network </li></ul></ul><ul><ul><li>Interoperability certification program </li></ul></ul><ul><ul><ul><li>(3)Works voice certification program </li></ul></ul></ul><ul><ul><li>Designed stateless core proxy in-house </li></ul></ul><ul><ul><li>Working closely with companies like Ubiquity on edge strategy </li></ul></ul><ul><ul><li>Aggressive plans to expand capabilities and offerings </li></ul></ul><ul><ul><li>Shunning traditional telephony applications </li></ul></ul><ul><ul><ul><li>Less vertically integrated than WorldCom, for example </li></ul></ul></ul><ul><ul><ul><li>Not attempting to reinvent the PSTN </li></ul></ul></ul>
    30. 30. Worldcom <ul><li>Very active in the SIP arena </li></ul><ul><ul><li>Employs major SIP advocate and promoter </li></ul></ul><ul><ul><ul><li>Henry Sinnreich - Distinguished Member of Engineering </li></ul></ul></ul><ul><ul><li>Designed proxy in-house </li></ul></ul><ul><ul><ul><li>Opened up to public for interoperability testing </li></ul></ul></ul><ul><ul><ul><li>http://sipaccount.wcom.com/sipregistration.html </li></ul></ul></ul><ul><ul><li>Recently announced a fully SIP-based Service </li></ul></ul><ul><ul><ul><li>“ IP Communications” service </li></ul></ul></ul><ul><ul><ul><li>Retail offering of hosted business communications applications </li></ul></ul></ul><ul><ul><ul><li>IP Centrex (PBX replacement) Plus ……. </li></ul></ul></ul><ul><ul><ul><li>Targets midsize to large customer base </li></ul></ul></ul><ul><ul><li>Using a broker architecture to layer services </li></ul></ul><ul><ul><ul><li>Designed in-house or from 3 rd party vendors </li></ul></ul></ul><ul><ul><li>Plans to offer SIP phones </li></ul></ul><ul><ul><ul><li>Can be seen as a major play to undermine Class 5 services </li></ul></ul></ul>
    31. 31. AT&T <ul><li>Taking the usual “early majority” stance </li></ul><ul><ul><li>Embracing SIP for future VoIP support </li></ul></ul><ul><ul><ul><li>Currently using H.323 until SIP is broadly accepted </li></ul></ul></ul><ul><ul><ul><ul><li>Expected to fully adopt SIP and replace H.323 in 12 to 18 months </li></ul></ul></ul></ul><ul><ul><li>Focusing on enterprise VPNs and managed services </li></ul></ul><ul><ul><ul><li>Managed Internet Service (MIS) – IP </li></ul></ul></ul><ul><ul><ul><li>Managed Router Service (MRS) – Frame </li></ul></ul></ul>
    32. 32. British Telecom <ul><li>Publicly Evaluating Ubiquity Products for Advanced Services </li></ul><ul><ul><li>Working with the Ubiquity product portfolio to create advanced, new, services </li></ul></ul><ul><ul><li>Focus on both residential & business verticals </li></ul></ul><ul><ul><li>Initial services to roll-out shortly </li></ul></ul>
    33. 33. Telia <ul><li>Early adopter of SIP-based applications and services </li></ul><ul><ul><li>‘Second-line’ residential services targeted at teenagers </li></ul></ul><ul><ul><ul><li>Presence; call profile; web push; IM </li></ul></ul></ul><ul><ul><li>Focus on specific vertical markets </li></ul></ul><ul><ul><ul><li>Market-specific applications </li></ul></ul></ul><ul><ul><ul><li>Network-based / hosted </li></ul></ul></ul><ul><ul><ul><li>Call profiles; presence; IM </li></ul></ul></ul><ul><ul><li>Employing an applications service broker architecture </li></ul></ul>
    34. 34. Microsoft <ul><li>Making a huge play for ubiquitous support of SIP at all levels </li></ul><ul><ul><li>Under the “.NET” architecture umbrella </li></ul></ul><ul><ul><li>Windows XP (GA) </li></ul></ul><ul><ul><ul><li>SIP-enabled version of messenger </li></ul></ul></ul><ul><ul><ul><li>SIP user agent / client </li></ul></ul></ul><ul><ul><li>Windows XP Server (July 2002) </li></ul></ul><ul><ul><ul><li>Extensible SIP proxy server </li></ul></ul></ul><ul><ul><li>Windows CE (July 2002) </li></ul></ul><ul><ul><ul><li>SIP user agent / client </li></ul></ul></ul><ul><ul><li>Windows Embedded - OS for Appliances (July 2002) </li></ul></ul><ul><ul><ul><li>SIP user agent / client </li></ul></ul></ul><ul><ul><li>SIP phone (Q1 2002) </li></ul></ul><ul><ul><ul><li>“ Stinger” </li></ul></ul></ul><ul><ul><li>Xbox gaming platform (Nov. 2001) </li></ul></ul><ul><ul><ul><li>“ Hoot ‘n holler” – voice with networked games </li></ul></ul></ul>
    35. 35. Other Carriers Active in SIP <ul><li>Verizon (US) </li></ul><ul><li>Genuity (US) </li></ul><ul><li>Broadwing (US) </li></ul><ul><li>Telecom Italia (Italy) </li></ul><ul><li>FranceTelecom (France) </li></ul><ul><li>Deutsche Telekom (Germany) </li></ul><ul><li>KPN Telecom (Netherlands) </li></ul><ul><li>Elisa (Helsinki Telephone - Sweden) </li></ul><ul><li>Telenor (Norway) </li></ul><ul><li>Orange (UK Mobile) </li></ul>Primary focus is advanced applications and services - not pure backbone infrastructure - US carriers Typically want to augment NB IP VPN services
    36. 36. Ubiquity Market Presence <ul><li>Extend leadership position as provider of carrier grade, end-to-end, SIP infrastructure solutions </li></ul><ul><li>Develop joint solution platforms with partners that they can sell to their customers: </li></ul><ul><ul><li>Ubiquity + Carrier  Enterprise </li></ul></ul><ul><ul><li>Ubiquity + NEV  Carrier </li></ul></ul><ul><ul><li>Ubiquity + NEV  Enterprise </li></ul></ul><ul><li>Create ‘pull’ demand in the carrier space for NEV / infrastructure solutions </li></ul><ul><li>Eventually create ‘pull’ demand directly from enterprises </li></ul><ul><li>Partner with best of breed application providers (e.g., media servers) to enable advanced bundled solutions on top of the Ubiquity platform </li></ul><ul><li>Offer telco-class applications designed in-house </li></ul>
    37. 37. Product Portfolio <ul><li>Proxy Server </li></ul><ul><li>SIP Network Server </li></ul><ul><li>Applications Services Broker </li></ul><ul><li>Design Deck </li></ul><ul><li>Element Manager </li></ul>SIP Proxy Net Server ASB NMS DD
    38. 38. Signaling Network Evolution Slower Statefull Fast Stateless Service Aware Non-Service Aware <ul><li>Edge Provisioning </li></ul><ul><ul><li>Optimized for service delivery </li></ul></ul><ul><li>Core Routing </li></ul><ul><ul><li>Optimized for speed </li></ul></ul>SIP Proxy Net Server ASB
    39. 39. SIP Network Server Load Balancing Manager Transaction Stateful Proxy SIP Engine Registrar Module Location Service Module Authentication Module SIP SIP RADIUS DNS ENUM Routing Module Database Interface Module Management Server SNMP MIB Event & Config Log SNMP JDBC Redirect Server Database
    40. 40. Ubiquity in the Converged Network Transmission Switching Call Control (Signaling) Applications The ASB Drives service creation by mediating and smoothly integrating the applications and signaling layers. Thus, the ASB aids in the deployment of new, disparate, multi-vendor services and easies feature interaction issues ASB “Gear” Network Services O/S Services
    41. 41. Application Service Broker (ASB) Service Director Service Host Transaction Stateful Proxy Registrar Module User Agent Module Location Service Module Authentication Module SIP RADIUS DNS ENUM Routing Module Database Interface Module Management Server SNMP MIB Event & Config Log SNMP JDBC HTTP SOAP SIP External Resources SERVICE LOGIC SERVICE ENGINES Media Push/Pull 3 rd Party Call Control CPL Engine Presence External Database Server Service Aggregation Service Configuration Service Policy Service Subscriptions
    42. 42. Distributed Service Architecture Source-Routing Transport NETWORK EDGE NETWORK CORE Signaling Applications Media Stream (i.e. RTP/IP) HTTP SDP/SIP ASB WEB Server Data base Net Server Net Server Net Server SIP Endpoint ‘A’ Enhanced Services SIP Signaling Network IP Transport Network SIP Endpoint ‘B’ No Services SIP Proxy Services Network
    43. 43. Enhanced, Brokered, Data Services Application Services Broker Altavista’s Babelfish Translation Server Short Message Service (SMS) Gateway 1. Send an instant message 2. Forward message to a translation server 3. Translated message forwarded to SMS gateway 4. Message delivered to mobile phone SOAP FIXED USER MOBILE USER MESSAGE sip:simon@ubiquity.net; translate=en_fr SIP/2.0 URI: “urn:xmethodsBabelFish” call.setMethodName: &quot;BabelFish&quot; translationmode: &quot;en_fr&quot; Sourcedata: &quot;Hello everybody!&quot; SMS Altavista Babelfish Hello everybody! Bonjour, tout le monde! SIP Signaling Network Mobile Network ASB SMS Gateway MBS Bonjour, tout le monde ! Hello, everybody! English to French
    44. 44. Design Deck <ul><li>A set of APIs that when ported into any IDE allow a Service Designer to create applications that can access Resources on the Application Services Broker (ASB) </li></ul><ul><ul><li>JavaBeans to Interface with ASB Modules </li></ul></ul><ul><ul><li>License to Develop and Upload CPL Scripts onto the ASB </li></ul></ul><ul><ul><li>JavaDocs Detailing the APIs </li></ul></ul><ul><ul><li>Extensive Documentation and Sample Code </li></ul></ul><ul><li>Service modules in the ASB are building blocks whose functionality is accessed via the DesignDeck API </li></ul><ul><li>Enables IP telephony call-control elements to be manipulated in combinations with user agents and web servers </li></ul><ul><li>Includes the follows Java Beans and Associated Java Docs </li></ul><ul><ul><li>Presence management; Instant messaging; Third-party call control; CPL storage; Forwarding; Call logging </li></ul></ul>
    45. 45. Sample Design Deck Application LDAP “ Automatically Establish Call When SIP Endpoint ‘B’ Becomes Available” 1. Set Call Profile Via Web Interface using Java Server Pages (JSP) 2. Endpoint ‘B’ Notifies Availability via SIP REGISTER – Presence Status Updated 3. PM Element Detects Change-of-Sate and Triggers 3PCC Element, INVITEing the Two Third Parties Java Server Pages S E R V I C E M O D U L E S Execute Service Logic call when available service CALL PROFILE WEB Server Data base ASB JDBC Data base SIP Endpoint ‘A’ SIP Endpoint ‘B’ DD Use Design Deck to Generate Java Code With Beans SIP Signaling Network Register Register HTTP HTTP IP Transport Network Media Update Presence (NOTIFY) Call Logic (Subscribe) Call Set-Up Message (UDP) Invite Invite(s) Invite “ B” OFFLINE “ B” ONLINE
    46. 46. Going Forward <ul><li>NEED THIS INFO – SALES? </li></ul>
    47. 47. Question & Answer Session <ul><li>OPEN FORUM </li></ul>

    ×