1 / 38

Multimedia Networking Protoocols

Multimedia Networking Protoocols. B.Bharat Shetty 4 th semester CS&E SJCE. what is multimedia?.

nami
Download Presentation

Multimedia Networking Protoocols

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. Multimedia Networking Protoocols B.Bharat Shetty 4th semester CS&E SJCE

  2. what is multimedia? DEFNITION: Multimedia is often described as a holy grail by some people.Literally the term multimedia is just two or more media.To be precise “Multimedia” generally means the combination of two or more continuous media i.e. media that has to be played during some well defined interval usually with some user defined interaction. Before Proceeding concept of a protocol must be clear to you

  3. contents • Multimedia Networking Applications • Streaming stored audio and video • RTSP • Protocols for Real-Time Interactive Applications • RTP • RTCP • SIP. • RSVP • H.323 standard • Summary

  4. Fundamental characteristics: Typically delay sensitive. End-to-end delay. Delay jitter. But loss tolerant: infrequent losses cause minor glitches. Antithesis of data, which are loss intolerant but delay tolerant. Classes of MM applications: 1) streaming stored audio and video 2) streaming live audio and video 3) real-time interactive audio and video MM Networking Applications • Jitter -the variability • of packet delays within • the same packet stream

  5. QoS level of performance needed for application to function. Multimedia, Quality of Service: What is it? Multimedia applications: network audio and video (“continuous media”)

  6. Streaming Stored Multimedia • Streaming: • media stored at source • transmitted to client • streaming: client playout begins before all data has arrived • timing constraint for still-to-be transmitted data: in time for playout

  7. 2. video sent 3. video received, played out at client 1. video recorded network delay streaming: at this time, client playing out early part of video, while server still sending later part of video SSM: What Is It? Cumulative data time

  8. Streaming Stored Multimedia: Interactivity functionality similar to a VCR: client can pause, rewind, FF, push slider bar • 10 sec initial delay causes no problem • 1-2 sec until command effect OK • RTSP often used • timing constraint for still-to-be transmitted data: in time for playout

  9. Streaming Live Multimedia Examples: • Talk shows over the web. • Events brought live to home. Streaming. • Playback buffer. • Playback can lag tens of seconds after transmission. • Still have timing constraint. Interactivity. • Fast forward impossible. • Rewind, pause possible!

  10. VIDEO ON DEMAND Video servers switch Customer’s House ATM or SONET Backbone network Local spooling server LDN* LDN-local distribution network

  11. RTSP: Client-server application layer protocol. User can control display: rewind, fast forward, pause, resume, repositioning, etc… Disadvantages: Does not define how audio/video is encapsulated for streaming over network. No restrictions on how sm is transported. It can be transported over UDP or TCP. No specifications on how the media player buffers audio/video. User Control of Streaming Media: RTSP

  12. RTP specifies a packet structure for packets carrying audio and video data. RFC 1889. RTP packet provides. Payload type identification. Packet sequence numbering. Timestamping. RTP runs in the end systems. RTP packets are encapsulated in UDP segments. Interoperability: if two internet phone applications run RTP, then they may be able to work together. Real-time Protocol (RTP)

  13. RTP Runs on Top of UDP • RTP libraries provide a transport-layer interface that extend UDP: • port numbers, IP addresses • payload type identification • packet sequence numbering • time-stamping

  14. RTP Header • Payload Type (7 bits): Indicates type of encoding currently being used. If sender changes encoding in middle of conference, sender • informs the receiver through this payload type field. • Payload type 0: PCM mu-law, 64 kbps • Payload type 3, GSM, 13 kbps • Payload type 7, LPC, 2.4 kbps • Payload type 26, Motion JPEG • Payload type 31. H.261 • Payload type 33, MPEG2 video • Sequence Number (16 bits): Increments by one for each RTP packet • sent, and may be used to detect packet loss and to restore packet • sequence.

  15. Works in conjunction with RTP. Each participant in RTP session periodically transmits RTCP control packets to all other participants. Each RTCP packet contains sender and/or receiver reports. Key things: -Number of packets sent. -Number of packets lost. -Inter arrival jitter. Real-time Control Protocol (RTCP)

  16. RTCP - Continued - RTP session typically has a single multicast address; all RTP and RTCP packets belonging to the session use the multicast address. - RTP and RTCP packets are distinguished from each other through the use of distinct port numbers. - To limit traffic, each participant reduces his RTCP traffic as the number of conference participants increases.

  17. Receiver report packets: Fraction of packets lost, last sequence number, average interarrival jitter. Sender report packets: SSRC of the RTP stream,the current time,the number of packets sent and the number of bytes sent. Source description packets: E-mail address of sender,sender's name, SSRC of associated RTP stream. Enable mapping between the SSRC and the user/host name. RTCP Packets

  18. SIP • Session initiation protocol. • Comes from IETF. • Usually a single module suitable for internetworking. • People are identified by names or e-mail addresses, rather than by phone numbers. • You can reach the callee, no matter where the callee roams, no matter what IP device the callee is currently using.

  19. Calling a Known IP Address • Alice’s SIP invite message indicates her port number & IP address. Indicates encoding that Alice prefers to receive • Bob’s 200 OK message indicates his port number, IP address & preferred encoding (GSM) • SIP messages can be sent over TCP or UDP; here sent over RTP/UDP. • Default SIP port number is 5060.

  20. More details

  21. Definition of H.323 standard H.323 is a standard that specifies the components, protocols and procedures that provide multimedia communication services—real-time audio, video, and data communications—over packet networks, including Internet protocol (IP)–based networks. H.323 is part of a family of ITU—T recommendations called H.32x that provides multimedia communication services over a variety of networks H.323

  22. Why H.323 ? • Emergence of voice-over–IP (VoIP) applications and IP telephony • The absence of a standard for voice over IP meant products that were incompatible. - Such requirements forced the need for a standard for IP telephony. • E.g.:Version 2 of H.323—packet-based multimedia communications systems

  23. H.323 PROTOCOL STACK Control Speech RTCP H.225 (RAS) H.245(call control) Q.931 RTP TCP UDP IP Data Link Protocol Physical Layer Protocol

  24. H.323 Packet Network

  25. The H.323 architectural Model for Internet Telephony Terminal GATEWAY TELEPHONE NETWORK INTERNET Gatekeeper ZONE

  26. Similarities b/w H.323 and SIP

  27. A Comparision Table

  28. RSVP • RSVP designed at • -MIT • -PARC • -California University. • RSVP Features: • RSVP is a novel signaling protocol in at least 4 ways: • It accommodates multicast, not just point-to-multipoint (one-to-many) reservations. • QoS routing can be deployed separately (in more operations, and so is • relatively low cost • Scalability.

  29. RESERVATION IMPLEMENTATIONS • Reservations are implemented through two types of RSVP messages: PATH and RESV. • The PATH messages are sent periodically from the sender to the multicast address. A PATH message contains flow spec to describe sender template (data format, source address, source port) and traffic characteristics. • RESV messages are generated by the receivers and contains reservation parameters including flow spec and filter spec.

  30. PATH MESSAGES R1 R4 S1 H5 H4 R2 R3 H3 S2

  31. RESERVATION REQUESTS R1 R4 S1 H5 H4 R2 R3 H3 S2

  32. Video conferencing,distance learning. Distributed networking and sharing of data and info resources. Future holds so much promise. Virtual reality,digital animation,net telephony. Interactivity enabled in all sectors. Next generation internet: Intserv, RSVP, Diffserv. Multimedia Networking: Summary Graphical Analysis Ahead

  33. Multimedia market A graphical analysis

  34. Growth of Multimedia Networks Now N E T W O R K s 2003 Years Source: NASDAQ and NASSCOM survey

  35. The real-time challenges However, multimedia networking is not a trivial task. We can expect at least three difficulties. 1. When compared with traditional textual applications, multimedia applications usually require much higher bandwidth. 2. Most multimedia applications require the real-time traffic 3. In addition to the delay, network congestion also has more serious effects on real-time traffic 4. Multimedia data stream is usually bursty

  36. Bibliography Books: 1.Multimedia Handbook- Jessica Keyes-TMH 2.Computer networks – Andrew Tanenbaum 3.Multimedia systems- a perspective (IEEE) Internet: 1.www.cis.ohio-state.edu/~jain/ 2.www.google.com 3.University of colombia website. 4.IEEE papers on net

  37. THANK YOU B.Bharat Shetty 4th sem CS&E SJCE

More Related