Abstract

An explicit slice-based mode type selection scheme for use in H.264/AVC has recently been developed, which reduces the burstiness effect of standard frame-based H.264/AVC by breaking up the Group of Picture structure. In this paper, slice-based encoded video streams are characterized using the token bucket traffic model and compared to standard frame-based encoded streams. Both lossless, loss bounded and delay bounded token bucket models are investigated and the high quantiles are found for the amount of loss. Loss above the amount given by the high quantiles will happen only with a very small probability. It is shown that the reduced burstiness for the slice-based video encoding leads to lower token bucket parameters compared to frame-based video encoding for a stream without scene changes, and a larger reduction in the token bucket parameters compared to the frame-based video encoding when a small amount of delay or loss is allowed for the stream with scene changes. Next, reshuffling of the frames of the video streams with scene changes is employed to better understand the effects of long-range dependence on the token bucket parameters. Only small effects are found from reshuffling the scenes, but reshuffling of the frames inside the scenes leads to lower token bucket parameters. Finally, an approach to estimate the parameters for the token bucket model using simple characteristics of the slice-based stream is developed.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.