CS 414 – Multimedia Systems Design Lecture 15 – Multimedia Transport (Part 1)AdministrativeInvestigation of Resource Managements in Distributed Multimedia SystemsOverview - Multimedia TransportUser and Application Requirements on Transport SubsystemsQoS Requirements on Transport SubsystemsOSI (Open System Internconnection) Layering StandardNetwork QoS and Resource ManagementNegotiation and TranslationNegotiation Protocol (P2P Receiver-Initiated Negotiation – Example1)Negotiation Protocol (P2P Receiver-Initiated Negotiation – Example2)Negotiation Protocol (P2P Sender-Initiated Negotiation - Example)Example of TranslationBandwidth Admission TestBandwidth AdmissionPacket Scheduling AdmissionSlide 17Network Resource Reservation/AllocationPessimistic Resource Reservation (Example)Optimistic Resource Reservation/AllocationOptimistic Resource Reservation (Example)Sender-Oriented Reservation ProtocolReceiver-Oriented Reservation ProtocolReservation StylesConclusionCS 414 - Spring 2011CS 414 – Multimedia Systems Design Lecture 15 – Multimedia Transport (Part 1)Klara NahrstedtSpring 2011CS 414 - Spring 2011Administrative HW1 on – due March 2Investigation 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 ServersMultimedia CPU Management CS 414 - Spring 2011Overview - Multimedia Transport Requirements of transport subsystemsUser/application requirements, Processing and protocol constraints, Mapping to OSI layers Network QoS and Resource Management ConceptsNegotiation, translation, admissionTraffic shaping, rate control, error controlMonitoring, adaptation Case Studies for multimedia transport systems (protocols, network technologies)Streaming Protocols in P2P Overlay Networks Streaming Support in Internet and Internet2CS 414 - Spring 2011User and Application Requirements on Transport SubsystemsData Throughput – need to support application data with stream-like behavior and in real timeFast data forwarding – the faster the transport system can move packets the fewer packets have to be bufferedService 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 2011QoS Requirements on Transport SubsystemsAudio/video communication needs to be bounded by deadlines End-to-end jitter must be boundedEnd-to-end guarantees are requiredSynchronization mechanisms for different data streams are requiredVariable bit rate traffic support is requiredServices and protocols should make sure that no starvation occursCS 414 - Spring 2011OSI (Open System Internconnection) Layering StandardCS 414 - Spring 2011Peer-to-PeerStreamingNetworkQoS/ResourceManagementVOD Services(Video RetrievalAnd Video Playback)Network QoS and Resource Management Network QoS parameters: End-to-end delay, jitter, packet rate, burst, throughput, packet lossEstablishment Protocol to establish Multimedia Call:1. Application/user defines QoS parameters (e.g., video stream parameters)2. QoS parameters are distributed and negotiated among participating parties3. QoS parameters are translated between different layers4. QoS parameters are mapped to resource requirements5. Required resources are admitted, reserved and allocated along the path between sender and receiver(s) CS 414 - Spring 2011Negotiation and TranslationFor negotiation of network QoS we may use Peer-to-peer negotiation and triangular negotiation (if service provider allows for negotiation)Translation between network and application QoSCS 414 - Spring 2011Negotiation Protocol (P2P Receiver-Initiated Negotiation – Example1)CS 414 - Spring 2011Sender (Server)Receiver (Client) timetime00Setup Socket Communication Send User/Receiver requestedQoS (video rate 20fps)WaitRequested Video rate (e.g.,20fps)WaitSetup Socket Communication- Receive Requested rate-Check with Recorded rate-If requested > recordedThen decrease rate, else O.K.-Translate QoS param.-Perform Resource Admission/ReservationIf admission O.K, elseDecrease rate, redoAdmission/reservation- Send resulting rateResulting video rate (e.g.,10 fps)-Receive resulting rate -Translate QoS param.-Perform admission, If admission O.K, , then Reserve resources, elseDecrease resulting rate - Send agreed/final rateWaitFinal video rate (5 fps)-Receive final rate- Adjust reservation-Start streamingStreaming Data at final rateWaitNegotiation Protocol (P2P Receiver-Initiated Negotiation – Example2)CS 414 - Spring 2011Sender (Server)Receiver (Client) timetime00Setup Socket Communication -Get QoS (video rate) from user- Translate QoS- Perform admission, if admission O.K., then reserve local resources, else decrease requested rate, redo admission/reservation WaitRequested Video rate (e.g.,20fps)WaitSetup Socket Communication- Receive Requested rate-Check with Recorded rate-If requested > recordedThen decrease rate, else O.K.-Translate QoS param.-Perform Resource Admission/ReservationIf admission O.K, elseDecrease rate, redoAdmission/reservation-Send resulting rate-Start streamingResulting video rate (e.g.,10 fps)-Receive resulting rate -Translate QoS param.-Adjust reservation if needed- Start receiving steamStreaming Data at resulting rateNegotiation Protocol (P2P Sender-Initiated Negotiation - Example)CS 414 - Spring 2011Sender (Server)Receiver (Client) timetime00Setup Socket Comm, get movie name-Get recorded rate as the requested rate from the recorded video file -Perform admission, if admission O.K, reserve resources, else decrease rate - Send requested QoS (video rate 20fps)WaitRequested Video rate (e.g.,25ps)Setup Socket Communication (also send server requested video file/movie name)-Receive requested rate -Translate QoS param.-Perform admission, If admission O.K, , then Reserve resources, elseDecrease rate - Send agreed/final rateWaitFinal video rate (20 fps)-Receive final rate- Adjust reservation-Start streamingStreaming Data at final rateWaitExample of Translation Consider application QoS (frame size MA, frame rate RA) and network QoS (throughput BN, packet rate RN)Assume MA = (320x240 pixels, 1 pixel = 8 bits), RA = 10 fps, packet size MN = 4KBytesApplication Throughput: BA = MA x RA
View Full Document
Unlocking...