1 / 30

Klara Nahrstedt Spring 2012

CS 414 – Multimedia Systems Design Lecture 15 –QoS Admission, QoS Negotiation, and Establishment of AV Connections. Klara Nahrstedt Spring 2012. Administrative. HW1 posted today, February 22 HW1 deadline, March 1. Covered Aspects of Multimedia. Audio/Video Presentation Playback.

Download Presentation

Klara Nahrstedt Spring 2012

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 15 –QoS Admission, QoS Negotiation, and Establishment of AV Connections Klara Nahrstedt Spring 2012 CS 414 - Spring 2012

  2. Administrative • HW1 posted today, February 22 • HW1 deadline, March 1 CS 414 - Spring 2012

  3. Covered Aspects of Multimedia Audio/Video Presentation Playback Image/Video Capture Audio/Video Perception/ Playback Image/Video Information Representation Transmission Transmission Compression Processing Audio Capture Media Server Storage Audio Information Representation A/V Playback CS 414 - Spring 2012

  4. Multimedia System/Network Sender Receiver MM Application MM Application OS/DS/Network OS/DS/Network Network CS 414 - Spring 2012

  5. Relation between QoS and Resources (Phase 1) Admission, Reservation Translation, Negotiation CS 414 - Spring 2012

  6. Phase 1: Establishment Phase (QoS Operations) CS 414 - Spring 2012 • QoS Translation at different Layers • User-Application • Application-OS/Transport Subsystem • QoS Negotiation • Negotiation of QoS parameters among two peers/components

  7. Phase 1: Connection Establishment Logical Negotiation of Application QoS Parameters Sender Receiver MM Application MM Application Translation OS/DS/Network OS/DS/Network Logical Negotiation of Network QoS Parameters Physical Transmission of Negotiation Parameters Network CS 414 - Spring 2012

  8. QoS Operations within Establishment Phase User/Application QoS Translation Overlay P2P QoS Negotiation Application/Transport QoS Translation QoS Negotiation in Transport Subsystem CS 414 - Spring 2012

  9. Example • Video Stream Quality: • Frame size: 320x240 pixels, 24 bits (3 Bytes per pixel) • Application frame rate RA: 20 fps • Translate to Network QoS if • Assume network packet size is 4KBytes • Network packet rate (RN):= ┌320x240x3x20┐ bytes / 4096 bytes CS 414 - Spring 2012

  10. Layered Translation (Example) CS 414 - Spring 2012

  11. QoS Negotiation CS 414 - Spring 2012

  12. Different Types of Negotiation Protocols • Bilateral Peer-to-Peer Negotiation • Negotiation of QoS parameters between equal peers in the same layer • Triangular Negotiation • Negotiation of QoS parameters between layers • Triangular Negotiation with Bounded Value CS 414 - Spring 2012

  13. Bilateral QoS Negotiation CS 414 - Spring 2012

  14. Triangular QoS Negotiation CS 414 - Spring 2012

  15. Triangular Negotiation with Bounded Value CS 414 - Spring 2012

  16. Triangular Negotiation Protocol (Pseudo-Code Example) Caller Callee Caller Pseudo-Code Network-Service Provider Pseudo-Code Callee Pseudo-Code CS 414 - Spring 2012

  17. Multimedia Resource Management • Resource managers with operations and resource management protocols • Various operations must be performed by resource managers in order to provide QoS • Phase 1: Establishment Phase (resource operations) • Operations are executed where schedulable units utilizing shared resources must be admitted, reserved and allocated according to QoS requirements • Phase 2: Enforcement Phase • Operations are executed where reservations and allocations must be enforced, and adapted if needed CS 414 - Spring 2012

  18. Phase 1: Resource Preparation Operations • QoS to Resource Mapping • Need translation or profiling (e.g., how much processing CPU cycles, i.e., processing time, it takes to process 320x240 pixel video frame) • Resource Admission • Need admission tests to check availability of shared resources • Resource Reservation • Need reservation mechanisms along the end-to-end path to keep information about reservations • Resource Allocation CS 414 - Spring 2012

  19. Phase 1: Connection Establishment Sender Logical Negotiation of App QoS Parameters Receiver MM Application MM Application Translation OS/DS/Network OS/DS/Network Logical Negotiation of Net QoS Parameters System Resource Admission and Reservation Physical Transmission of Negotiation Parameters Network Resource Reservation Protocol Network Network Resource Admission and Resource Reservation CS 414 - Spring 2012

  20. Admission Tests • Task (System) schedulability tests for CPU resources • This is done for delay guarantees • Network Packet schedulability tests for sharing host network interfaces, network switches • This is done for network delay and jitter guarantees • Spatial tests for memory/buffer allocation • This is done for delay and reliability guarantees • Network Link bandwidth tests • This is done for network throughput guarantees CS 414 - Spring 2012

  21. Resource Reservation and Allocation • Two types of reservations • Pessimistic approach - Worst case reservation of resources • Optimistic approach - Average case reservation of resources • To implement resource reservation we need: • Resource table • to capture information about managed table (e.g., process management PID table) • Reservation table • to capture reservation information • Reservation function • to map QoS to resources and operate over reservation table CS 414 - Spring 2012

  22. Resource Reservation • Two types of reservation styles: • Sender-initiated reservation • Receiver-initiated reservation CS 414 - Spring 2012

  23. Relation between QoS and Resources (Phase 2) Admission, Reservation Translation, Negotiation Scheduling, Rate Control, Error Control Flow Control QoS Management Compression CS 414 - Spring 2012

  24. 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 2012

  25. 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 2012

  26. 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 2012

  27. 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 2012

  28. 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 2012

  29. 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 2012

  30. Conclusion – Current State of Art • Lack of mechanisms to support QoS guarantees • Need research in distributed control, monitoring, adaptation and maintenance of QoS mechanisms • Lack of overall frameworks • Need QoS frameworks for heterogeneous environments (diverse networks, diverse devices, diverse OS) CS 414 - Spring 2012

More Related