1 / 21

Klara Nahrstedt Spring 2009

CS 414 – Multimedia Systems Design Lecture 14 – Quality of Service Concepts (Part 3) Multimedia Transport (Part 1). Klara Nahrstedt Spring 2009. Administrative. MP2 posted, deadline March 2. Relation between QoS and Resources. Admission, Reservation. Translation, Negotiation.

jpenn
Download Presentation

Klara Nahrstedt Spring 2009

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. CS 414 – Multimedia Systems DesignLecture 14 – Quality of Service Concepts (Part 3)Multimedia Transport (Part 1) Klara Nahrstedt Spring 2009 CS 414 - Spring 2009

  2. Administrative • MP2 posted, deadline March 2 CS 414 - Spring 2009

  3. Relation between QoS and Resources Admission, Reservation Translation, Negotiation Scheduling, Rate Control, Error Control Flow Control QoS Management Compression CS 414 - Spring 2009

  4. Phase 2: Media Processing and Transmission Sender Receiver MM Application MM Application • System • Resource • Scheduling • Rate Control • Flow Control Error Control OS/DS/Network OS/DS/Network Physical Transmission of Media Network Network Resource Scheduling CS 414 - Spring 2009

  5. Phase 2: Enforcement Operations • Resource scheduling • Example: rate-monotonic scheduling • Rate control – traffic shaping • Example: leaky bucket • End-to-end error control • Example: forward error correction • Flow control • Open loop flow control (no feedback) • Close look flow control (with feedback channel) CS 414 - Spring 2009

  6. QoS Management during Transmission Phase • Resource and QoS Monitoring • Flexibility, i.e., monitoring should be turned on/off • Two types of monitoring • User-mode monitoring • Network-mode monitoring • QoS Maintenance • Compares monitored QoS with contract QoS • QoS Degradation • graceful degradation needed CS 414 - Spring 2009

  7. QoS Management during Transmission Phase • QoS Renegotiation and Signaling • In case QoS parameters need to change, renegotiation must be initiated • QoS/Resource Adaptation • As a result of re-negotiation request (request for change in quality) adaptation in QoS and resource allocation must happen CS 414 - Spring 2009

  8. QoS/Resource Adaptation • Renegotiation request can come from • User • Host system • Network • Resource adaptation • Network adaptation (e.g., dynamic re-routing mechanism) • Source adaptation (e.g., temporal scaling with feedback) CS 414 - Spring 2009

  9. Resource De-allocation – Tear-Down Phase • Reserved Resource must be freed up once multimedia session is over • Tear-down process • Sender-initiated closing (release reservation) • Receiver-initiated closing (release reservation) CS 414 - Spring 2009

  10. Investigation of Resource Managements in Distributed Multimedia Systems Multimedia Transport Systems and Network Resource Management (next 3 weeks) Multimedia Buffer Management and Caching Multimedia File Systems and Multimedia Servers Multimedia CPU Management CS 414 - Spring 2009

  11. Overview - Multimedia Transport • Requirements of transport subsystems • User/application requirements, Processing and protocol constraints, Mapping to OSI layers • Network QoS and Resource Management Concepts • Negotiation, translation, admission • Traffic shaping, rate control, error control • Monitoring, adaptation • Case Studies for multimedia transport systems (protocols, network technologies) • Streaming Protocols in P2P Overlay Networks • Streaming Support in Internet and Internet2 CS 414 - Spring 2009

  12. Introduction to Multimedia Transport System OSI Layering Standard CS 414 - Spring 2009

  13. Mapping of Multimedia Requirements into OSI Layers • Physical layer • Defines transmission methods of individual bits over physical medium • For MM – need high bandwidth and minimum delay (gigabit/terabit rates) • Data Link Layer (MAC) • Defines transmission of blocks, called data frames, as well as access protocols to physical medium, error recognition, correction, flow control, block synchronization • For MM – need reservations and throughput guarantees, and different error correction mechanisms CS 414 - Spring 2009

  14. OSI and Multimedia • Network layer • Defines transmission of information blocks, called packets (IP packets) • For MM • Need reservations and guarantees • Request for guarantees defined by network QoS parameters • Preferable connection-oriented behavior where reservation is done during connection setup along the path • Network QoS should be negotiated at this layer CS 414 - Spring 2009

  15. OSI and Multimedia • Transport Layer • Defines a process-to-process connection • For MM • Network QoS can be enhanced, i.e., if network service is poor, then transmission layer bridges the gap between what the transport user wants and network provides • Error-handling based on process-to-process communication • Error handling may not include retransmission due to delay and jitter constraints • Rate control, flow control are supported ,CS 414 - Spring 2009

  16. OSI and Multimedia • Session layer • Guarantees existence of multimedia connection(s) during whole multimedia session • For MM • Need synchronization within a stream and among streams • Need support for point-point session and multicast session CS 414 - Spring 2009

  17. OSI and Multimedia • Presentation Layer • Abstracts from different formats • For MM • Need transformation service between application specific formats and the agreed upon transport format • Audio/video format conversion is needed since many formats exist • Application Layer • Provides specific application services • For MM • need real-time access support • Playback, record, FF, rewind and pause functions CS 414 - Spring 2009

  18. Requirements on Transport/ Network Services and Protocols Audio/video communication needs to be bounded by deadlines End-to-end jitter must be bounded End-to-end guarantees are required Synchronization mechanisms for different data streams are required Variable bit rate traffic support is required Services and protocols should make sure that no starvation occurs CS 414 - Spring 2009

  19. User and Application Requirements Data Throughput – need to support application data with stream-like behavior and in real time Fast data forwarding – the faster the transport system can move packets the fewer packets have to be buffered Service Guarantees – need appropriate resource management Multicasting – need service for efficient resource sharing and reaching groups of users in applications such as video conferencing CS 414 - Spring 2009

  20. Processing and Protocol Constraints Adapter-to-adapter transmission achieves fast transmission, but does not allow control over streams Data movement in protocol stack– requires expensive data copying, hence need to explore other buffer management techniques and strategies Segmentation and re-assembly – are part of the protocol stack and need to be done fast and efficiently Retransmission error-recovery Underlying network – may provide different transmission modes CS 414 - Spring 2009

  21. Conclusion Multimedia System/networking designer must be clear about the requirements coming from the applications and users Multimedia system/networking designer must be also clear about the constraints, what underlying protocols, services and networks can and cannot do and promise what’s possible to guarantee and deliver CS 414 - Spring 2009

More Related