1 / 31

Voice/Video with QoS over IPv6

The 1st GLOBAL IPv6 Summit in AP Taipei, Taiwan. Voice/Video with QoS over IPv6. Winston Seah, Dr.Eng. winston@i2r.a-star.edu.sg. Presentation Outline. Motivation and Objectives Bandwidth Reservation using Bandwidth Brokers Call setup signaling with SIP Status of work Summary

les
Download Presentation

Voice/Video with QoS over IPv6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The 1st GLOBAL IPv6 Summit in AP Taipei, Taiwan Voice/Video with QoS over IPv6 Winston Seah, Dr.Eng. winston@i2r.a-star.edu.sg

  2. Presentation Outline • Motivation and Objectives • Bandwidth Reservation using Bandwidth Brokers • Call setup signaling with SIP • Status of work • Summary • References

  3. Motivation And Objectives

  4. Project motivation • Trends showing convergence of data and voice networks into one packet based network • Packet based networks made popular by the flexibility of the WWW • Push factors of convergence includes: • Easier service creation • Simpler network maintenance & management • Better utilization of bandwidth  Leads to cost savings • Much more IP addresses are needed when convergence arrived, e.g. when all telephone unit has an unique IP address • Solution: IPv6

  5. Project objectives • To build a testbed to demonstrate an All-IP scenario • Testbed can be used for experimentations • Building competencies in SIP and DiffServ

  6. The Testbed

  7. Bandwidth Reservation Using Bandwidth Brokers

  8. Bandwidth Reservation • DiffServ architecture was chosen • QoS, in our case, bandwidth was reserved through reservation requests made to the serving Bandwidth Broker (BB) • The serving BB then performs a few tasks: • Performs Authentication before Authorizing reservation • Checks user’s SLA • Does metering – checks available BW in each DiffServ class • Generates SLS and proceed to configure edge router to do marking

  9. Bandwidth Reservation • If destination host is foreign to the source host, the serving BB carry out these additional tasks: • Checks next hop, i.e. which DiffServ domain the next hop will go, so as to identify which down stream BB it should make reservation • It proceed to do inter-domain reservation and an SLS is set up between the 2 BBs • In this way, the sender initiated reservation goes from BB to BB until the destination DiffServ domain is reached • Reservations are tagged with durations which will expire or terminated by the originator or the network operator

  10. Bandwidth Reservation • Users make QoS requests using a GUI program. The user makes reservation based on port number and IP address

  11. BB Design SQL COPS SNMP

  12. BB GUI

  13. BB GUI

  14. Platform used • Operating system: RedHat 7.3 (kernel 2.4.18) • IPROUTE2 (2.4.7-now-ss010824) • COPS • SNMP (4.2.3) • mySQL • Pentium 4 PCs

  15. Call Setup Signaling With Session Initiation Protocol (SIP)

  16. SIP work • In addition to the QoS-enabled network, a standards-based IP telephony system was developed to demonstrate the feasibility of an All-IP network • SIP was chosen as the signaling protocol for it is lightweight, scalability, and it being an effort by the IETF, it most likely will be the standard protocol to be used across the Internet • The SIP server was thoroughly tested when the SIP development team went for the 11th SIPit event held in Atlanta • Our SIP stack fulfilled 100% of basic, 50% of intermediate and 30% of advanced categories requirements

  17. SIP testbed • 3 User Agents (UA) were installed to demonstrate the call forwarding action • The SIP server runs: • SIP stateless and/or stateful proxy server • SIP registrar server • SIP presence server • With the presence server, a “click & call” feature like that of Instant Messaging where you know the online status of your contacts is made possible • Both video and audio are supported • The SIP UA supports both IPv4 and IPv6 (hot-switchable) • Based on IETF RFC2543bis9

  18. SIP UA Modules in blue are developed by I2R

  19. SIP UA GUI Similar to typical Instant Messaging, a list of contacts is shown with their online status Java was used in view that the UA can be accessed from the Web without installation hassle

  20. SIP Server GUI

  21. Typical Call Setupsignaling flow 1 2 3 4 6 5 7 8 9 10 11

  22. Location Registrar Database SIP Proxy/ Presence Server INVITE 200 OK SIP User Agents (New) MEDIA SIP User Agents MEDIA INVITE "HOLD" 200 OK MEDIA REFER 200 OK NOTIFY 200 OK SIP User Agents BYE 200 OK Typical call transfer signaling flow 7 8 13 2 1 3 4 5 6 9 10 11 12

  23. JAIN version • A separate JAIN compliant API for the SIP stack was also developed • Generic encoding/decoding framework • RFC2543bis09 message transaction layer • JAIN 1.0 API interface • For standards-based service creation

  24. Status of Work

  25. Current work • SIP signaling compression. To be incorporated into SIP server and mobile SIP UA for more bandwidth-efficient signaling

  26. Codes available • Programs developed: • Bandwidth Broker (compliant to Internet2 proposals) that supports both intra- and inter-domain BB signaling (IPv6) • SIP UA supporting IPv4 and IPv6 • SIP server (IPv6) • JAIN compliant API SIP stack (IPv6) • Traffic generator (IPv4 and IPv6) • To be released as open source, upon request

  27. Summary • Implemented a testbed to demonstrate the All-IP scenario with mobility and QoS support. • Provide bandwidth reservation, both intra- and inter-domain, using Bandwidth Brokers. • Provide call signaling using SIP with mobility and QoS support. • Signaling compression is being added. • Everything is built on IPv6 

  28. Reference • Black, D., Blake, S., Carlson, M., Davies, E., Wang, Z. and Weiss, W., “An Architecture for Differentiated Services”, RFC 2475, December 1998 • Internet2 QBone Working Group, “QBone Architecture”, available at http://qbone.internet2.edu/ • Teitelbaum, B et al, “Qbone Bandwidth Broker Architecture”, Internet2 Signalling Design Team, June 2000, Work-in-progress • Rüdiger Geib, “Draft SIBBS Message Codes”, 2001 • Durhan, D., Boyle, J., Cohen, R., Rajan, R., Herzog, S., Sastry, A., “The COPS (Common Open Policy Service) Protocol”, RFC 2748, January 2000

  29. Reference • Chan, K., Seligson, J., Durham D., Gai, S., McCloghrie, K., Herzog, S., Reichmeyer, F., Yavatkar, R., Smitch A.,“COPS Usage for Policy Provisioning (COPS-PR)”, RFC 3084, March 2001 • Dhananjaya Rao, “Bandwidth Broker Implementation”, available at http://www.ittc.ku.edu/~kdrao/BB/ • J. Case, K. McCloghrie Hughes, M. Rose, S. Waldbusser Carnegie “Introduction to version 2 of the Internet-standard Network Management Framework “ RFC 1441 • J. Case, K. McCloghrie Hughes, M. Rose, S. Waldbusser Carnegie “Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2) “ RFC 1142

  30. Reference • M. Handley et al., “SIP: Session Initiation Protocol,” RFC 2543, Mar 1999 • draft-ietf-sip-rfc2543bis-09, Feb 2002 • J. Rosenberg, et al., “SIP: Session Initiation Protocol”, RFC3261, June, 2002 • Alan Johnston, et al., “SIP Service Examples”, IETF draft, draft-ietf-sip-service-examples-03.txt, November 2001, work in progress • R. Sparks, “SIP Call Control – Transfer”, IETF draft, draft-ietf-sip-cc-transfer-05, July 18, 2001, work in progress • R. Sparks, “The REFER Method”, IETF draft, draft-ietf-sip-refer-00, October 30, 2001, work in progress

  31. Reference • J. Rosenberg, D. Willis, et al., "SIP extensions for Presence," Internet Draft, draft-ietf-simple-presence-07, Mar. 2002. Work in progress • A. B. Roach, “Session Initiation Protocol (SIP) – Specific Event Notification”, RFC3265, June 2002 • M. Day, J. Rosenberg and H. Sugano, "A Model for Presence and Instant Messaging," RFC2778, February 2000

More Related