EP2764674B1 - Commutation entre des représentations durant une diffusion en continu de réseau de données multimédias codées - Google Patents

Commutation entre des représentations durant une diffusion en continu de réseau de données multimédias codées Download PDF

Info

Publication number
EP2764674B1
EP2764674B1 EP12783731.8A EP12783731A EP2764674B1 EP 2764674 B1 EP2764674 B1 EP 2764674B1 EP 12783731 A EP12783731 A EP 12783731A EP 2764674 B1 EP2764674 B1 EP 2764674B1
Authority
EP
European Patent Office
Prior art keywords
representation
video data
representations
client device
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP12783731.8A
Other languages
German (de)
English (en)
Other versions
EP2764674A1 (fr
Inventor
Lorenz Christoph Minder
Michael George LUBY
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP2764674A1 publication Critical patent/EP2764674A1/fr
Application granted granted Critical
Publication of EP2764674B1 publication Critical patent/EP2764674B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/234Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs
    • H04N21/2343Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
    • H04N21/23439Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements for generating different versions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60Network streaming of media packets
    • H04L65/61Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/612Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60Network streaming of media packets
    • H04L65/75Media network packet handling
    • H04L65/752Media network packet handling adapting media to network capabilities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80Responding to QoS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/438Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving encoded video stream packets from an IP network
    • H04N21/4383Accessing a communication channel
    • H04N21/4384Accessing a communication channel involving operations to reduce the access time, e.g. fast-tuning for reducing channel switching latency
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/845Structuring of content, e.g. decomposing content into time segments
    • H04N21/8456Structuring of content, e.g. decomposing content into time segments by decomposing the content in the time domain, e.g. in time segments
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1083In-session procedures
    • H04L65/1089In-session procedures by adding media; by removing media

Definitions

  • This disclosure relates to network streaming of encoded multimedia data.
  • Digital video capabilities can be incorporated into a wide range of devices, including digital televisions, digital direct broadcast systems, wireless broadcast systems, personal digital assistants (PDAs), laptop or desktop computers, digital cameras, digital recording devices, digital media players, video gaming devices, video game consoles, cellular or satellite radio telephones, video teleconferencing devices, and the like.
  • Digital video devices implement video compression techniques, such as those described in the standards defined by MPEG-2, MPEG-4, ITU-T H.263 or ITU-T H.264/MPEG-4, Part 10, Advanced Video Coding (AVC), and extensions of such standards, to transmit and receive digital video information more efficiently.
  • video compression techniques such as those described in the standards defined by MPEG-2, MPEG-4, ITU-T H.263 or ITU-T H.264/MPEG-4, Part 10, Advanced Video Coding (AVC), and extensions of such standards, to transmit and receive digital video information more efficiently.
  • Video compression techniques perform spatial prediction and/or temporal prediction to reduce or remove redundancy inherent in video sequences.
  • a video frame or slice may be partitioned into blocks. Each block can be further partitioned.
  • Blocks in an intra-coded (I) frame or slice are encoded using spatial prediction with respect to neighboring blocks.
  • Blocks in an inter-coded (P or B) frame or slice may use spatial prediction with respect to neighboring blocks in the same frame or slice or temporal prediction with respect to other reference frames.
  • the video data may be packetized for transmission or storage.
  • the video data may be assembled into a video file conforming to any of a variety of standards, such as the International Organization for Standardization (ISO) base media file format and extensions thereof, such as ITU-T H.264/AVC.
  • ISO International Organization for Standardization
  • Such packetized video data may be transported in a variety of ways, such as transmission over a computer network using network streaming.
  • this disclosure describes techniques for improving streaming of media data over a network.
  • the techniques of this disclosure are generally directed to improving a user's experience when initially retrieving multimedia content and when performing bandwidth adaptation.
  • the invention achieving this effect is defined by the subject matter of independent claims 1, 9, 13, 14 and 15.
  • Aspects of this disclosure relate to providing information from a server device to a client device that indicates distances between switch points of various representations of the multimedia content.
  • the client device may use this information to initially select a representation having relatively frequent switch points (albeit relatively lower perceived quality), buffer data of the representation, then switch to a representation having relatively higher perceived quality at a future switch point of the higher-quality representation.
  • a method of retrieving video data of multimedia content includes determining a first interval between switch points for a first representation of the multimedia content and a second interval between switch points for a second representation of the multimedia content, wherein the first interval is less than the second interval, based on the determination, submitting one or more network requests for an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in the second representation, and after submitting the request for the amount of video data from the first representation, retrieving video data from the second representation.
  • an apparatus for retrieving video data of multimedia content includes one or more processors configured to determine a first interval between switch points for a first representation of the multimedia content and a second interval between switch points for a second representation of the multimedia content, wherein the first interval is less than the second interval, based on the determination, submit one or more network requests for an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in the second representation, and after submitting the request for the amount of video data from the first representation, retrieve video data from the second representation.
  • an apparatus for retrieving video data of multimedia content includes means for determining a first interval between switch points for a first representation of the multimedia content and a second interval between switch points for a second representation of the multimedia content, wherein the first interval is less than the second interval, based on the determination, means for submitting one or more network requests for an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in the second representation, and after submitting the request for the amount of video data from the first representation, means for retrieving video data from the second representation.
  • aspects of this disclosure are directed to a non-transitory computer-readable storage medium storing instructions that, when executed, cause one or more processors to determine a first interval between switch points for a first representation of the multimedia content and a second interval between switch points for a second representation of the multimedia content, wherein the first interval is less than the second interval, based on the determination, submit one or more network requests for an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in the second representation, and after submitting the request for the amount of video data from the first representation, retrieve video data from the second representation.
  • a method of streaming video data of multimedia content includes receiving a plurality of representations of the multimedia content, wherein the representations include switch point interval information representative of intervals between switch points for the respective representations, sending video data of a first one of the representations to a client device in response to a request from the client device, and after sending an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in a second, different one of the representations, sending video data of the second one of the representations to the client device, wherein the interval between switch points for the second one of the representations is lower than the interval between switch points for the first one of the representations.
  • an apparatus for streaming video data of multimedia content includes one or more processors configured to receive a plurality of representations of the multimedia content, wherein the representations include switch point interval information representative of intervals between switch points for the respective representations, send video data of a first one of the representations to a client device in response to a request from the client device, and after sending an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in a second, different one of the representations, send video data of the second one of the representations to the client device, wherein the interval between switch points for the second one of the representations is lower than the interval between switch points for the first one of the representations.
  • an apparatus for streaming video data of multimedia content includes means for receiving a plurality of representations of the multimedia content, wherein the representations include switch point interval information representative of intervals between switch points for the respective representations, means for sending video data of a first one of the representations to a client device in response to a request from the client device, and after sending an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in a second, different one of the representations, means for sending video data of the second one of the representations to the client device, wherein the interval between switch points for the second one of the representations is lower than the interval between switch points for the first one of the representations.
  • aspects of this disclosure are directed to a non-transitory computer-readable storage medium storing instructions that, when executed, cause one or more processors to receive a plurality of representations of the multimedia content, wherein the representations include switch point interval information representative of intervals between switch points for the respective representations, send video data of a first one of the representations to a client device in response to a request from the client device, and after sending an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in a second, different one of the representations, send video data of the second one of the representations to the client device, wherein the interval between switch points for the second one of the representations is lower than the interval between switch points for the first one of the representations.
  • this disclosure describes techniques for streaming multimedia data, such as audio and video data, over a network.
  • the techniques of this disclosure may be used in conjunction with dynamic adaptive streaming over HTTP (DASH).
  • DASH dynamic adaptive streaming over HTTP
  • This disclosure describes various techniques that may be performed in conjunction with network streaming, any or all of which may be implemented alone or in any combination.
  • various devices performing network streaming may be configured to implement the techniques of this disclosure.
  • multimedia content (such as a movie or other audio/video content, which may also include text overlays or other data) may be encoded in a variety of ways and with a variety of characteristics.
  • a content preparation device may form multiple representations of the same multimedia content. Each representation may correspond to a particular set of characteristics, such as coding and rendering characteristics, to provide data usable by a variety of different client devices with various coding and rendering capabilities.
  • representations having various bit rates may allow for bandwidth adaptation. That is, a client device may determine an amount of bandwidth that is currently available and select a representation based on the amount of available bandwidth, along with coding and rendering capabilities of the client device.
  • a content preparation device may indicate that a set of representations has a set of common characteristics. The content preparation device may then indicate that the representations in the set form an adaptation set, in that representations in the set can be used for bandwidth adaptation.
  • an adaptation set may also be referred to as a "representation group.” That is, representations in the set may differ in bit rate, but otherwise share substantially the same characteristics.
  • a client device may determine various sets of common characteristics for adaptation sets of multimedia content, and select an adaptation set based on coding and rendering capabilities of the client device. Then, the client device may adaptively switch between representations in the selected adaptation set based on bandwidth availability.
  • the content preparation device may also provide separate network locations for different portions of a manifest file, such as a media presentation description (MPD) file in a format prescribed by 3GPP (Third Generation Partnership Project). That is, different portions of the manifest file may be independently addressable by, e.g., various uniform resource identifiers (URIs), such as uniform resource locators (URLs).
  • URIs uniform resource identifiers
  • An initial portion of the manifest file may include a URI, URL, or other location identifier of another portion of the manifest file.
  • a first portion of the manifest file may include descriptions of common characteristics of adaptation sets, as discussed above.
  • Each of the adaptation sets may be associated with a respective different portion of the manifest file, which may include data indicative of locations of media data of representations in the respective adaptation set.
  • a client device may receive the first portion of the manifest file, select an appropriate adaptation set, retrieve another portion of the manifest file for the selected adaptation set, select a representation of the selected group, and use the other portion of the manifest file to retrieve data of the selected representation.
  • the client device may adapt to changing network bandwidth using the other portion of the manifest file, that is, the portion specific to the selected adaptation set.
  • Video files such as segments of representations of media content, may conform to video data encapsulated according to any of ISO base media file format, Scalable Video Coding (SVC) file format, Advanced Video Coding (AVC) file format, Third Generation Partnership Project (3GPP) file format, and/or Multiview Video Coding (MVC) file format, or other similar video file formats.
  • SVC Scalable Video Coding
  • AVC Advanced Video Coding
  • 3GPP Third Generation Partnership Project
  • MVC Multiview Video Coding
  • the ISO Base Media File Format is designed to contain timed media information for a presentation in a flexible, extensible format that facilitates interchange, management, editing, and presentation of the media.
  • ISO Base Media File format (ISO/IEC 14496-12:2004) is specified in MPEG-4 Part-12, which defines a general structure for time-based media files.
  • the ISO Base Media File format is used as the basis for other file formats in the family such as AVC file format (ISO/IEC 14496-15) defined support for H.264/MPEG-4 AVC video compression, 3GPP file format, SVC file format, and MVC file format.
  • 3GPP file format and MVC file format are extensions of the AVC file format.
  • ISO base media file format contains the timing, structure, and media information for timed sequences of media data, such as audiovisual presentations.
  • the file structure may be object-oriented. A file can be decomposed into basic objects very simply and the structure of the objects is implied from their type.
  • Files conforming to the ISO base media file format may be formed as a series of objects, called "boxes.”
  • Data in the ISO base media file format may be contained in boxes, such that no other data needs to be contained within the file and there need not be data outside of boxes within the file. This includes any initial signature required by the specific file format.
  • a "box” may be an object-oriented building block defined by a unique type identifier and length.
  • a presentation is contained in one file, and the media presentation is self-contained.
  • the movie container (movie box) may contain the metadata of the media and the video and audio frames may be contained in the media data container and could be in other files.
  • a representation may be contained in several files, sometimes referred to as segments. Timing and framing (position and size) information is generally in the ISO base media file and the ancillary files may essentially use any format. This presentation may be 'local' to the system containing the presentation, or may be provided via a network or other stream delivery mechanism.
  • An optional metadata track can be used to tag each track with the "interesting characteristic" that it has, for which its value may differ from other members of the group (e.g., its bit rate, screen size, or language).
  • Some samples within a track may have special characteristics or may be individually identified.
  • One example of the characteristic is the synchronization point (often a video I-frame). These points may be identified by a special table in each track. More generally, the nature of dependencies between track samples can also be documented using metadata.
  • the metadata can be structured as a sequence of file format samples, just like a video track. Such a track may be referred to as a metadata track.
  • Each metadata sample may be structured as a metadata statement. There are various kinds of statements, corresponding to the various questions that might be asked about the corresponding file-format sample or its constituent samples.
  • the media When media is delivered over a streaming protocol, the media may need to be transformed from the way it is represented in the file.
  • RTP Real-time Transport Protocol
  • each frame of video is stored contiguously as a file-format sample.
  • packetization rules specific to the codec used must be obeyed to place these frames in RTP packets.
  • a streaming server may be configured to calculate such packetization at run-time. However, there is support for the assistance of the streaming servers.
  • HTTP streaming e.g., in accordance with dynamic adaptive streaming over HTTP (DASH).
  • frequently used operations include GET and partial GET.
  • the GET operation retrieves a whole file associated a given uniform resource locator (URL) or other identifier, e.g., URI.
  • the partial GET operation receives a byte range as an input parameter and retrieves a continuous number of bytes of a file corresponding to the received byte range.
  • URL uniform resource locator
  • URI e.g., URI
  • the partial GET operation receives a byte range as an input parameter and retrieves a continuous number of bytes of a file corresponding to the received byte range.
  • movie fragments may be provided for HTTP streaming, because a partial GET operation can get one or more individual movie fragments.
  • a media representation may be a structured collection of data that is accessible to the client. The client may request and download media data information to present a streaming service to a user.
  • a media representation may correspond to a structured collection of data that is accessible to an HTTP streaming client device.
  • the HTTP streaming client device may request and download media data information to present a streaming service to a user of the client device.
  • a media representation may be described in the MPD data structure, which may include updates of the MPD.
  • Multimedia content may contain a sequence of one or more periods.
  • Periods may be defined by a Period element in the MPD.
  • Each period may have an attribute start in the MPD.
  • the MPD may include a start attribute and an availableStartTime attribute for each period.
  • the sum of the start attribute of the period and the MPD attribute availableStartTime may specify the availability time of the period in UTC format, in particular the first Media Segment of each representation in the corresponding period.
  • the start attribute of the first period may be 0.
  • the start attribute may specify a time offset between the start time of the corresponding Period relative to the start time of the first Period.
  • Each period may extend until the start of the next Period, or until the end of the media presentation in the case of the last period.
  • Period start times may be precise. They may reflect the actual timing resulting from playing the media of all prior periods.
  • Each period may contain one or more representations for the same media content.
  • a representation may be one of a number of alternative encoded versions of audio or video data.
  • the representations may differ by various characteristics, such as encoding types, e.g., by bit rate, resolution, and/or codec for video data and bit rate, language, and/or codec for audio data.
  • the term representation may be used to refer to a section of encoded audio or video data corresponding to a particular period of the multimedia content and encoded in a particular way.
  • Representations of a particular period may be assigned to a group, which may be indicated by a group attribute in the MPD. Representations in the same group are generally considered alternatives to each other. For example, each representation of video data for a particular period may be assigned to the same group, such that any of the representations may be selected for decoding to display video data of the multimedia content for the corresponding period.
  • the media content within one period may be represented by either one representation from group 0, if present, or the combination of at most one representation from each non-zero group, in some examples.
  • Timing data for each representation of a period may be expressed relative to the start time of the period.
  • a representation may include one or more segments. Each representation may include an initialization segment, or each segment of a representation may be self-initializing. When present, the initialization segment may contain initialization information for accessing the representation. In general, the initialization segment does not contain media data.
  • a segment may be uniquely referenced by an identifier, such as a uniform resource locator (URL).
  • the MPD may provide the identifiers for each segment. In some examples, the MPD may also provide byte ranges in the form of a range attribute, which may correspond to the data for a segment within a file accessible by the URL or URI.
  • Each representation may also include one or more media components, where each media component may correspond to an encoded version of one individual media type, such as audio, video, and/or timed text (e.g., for closed captioning).
  • Media components may be time-continuous across boundaries of consecutive media segments within one representation.
  • a client device may determine an amount of bandwidth that is currently available and select a representation based on the amount of available bandwidth and a bit rate of the representation, along with coding and rendering capabilities of the client device.
  • a client device typically chooses the highest bit rate that is allowed by the available bandwidth. If bandwidth conditions change, the client can react by switching to a different representation, e.g., with a different bit rate.
  • Traditional video streaming techniques may require a client device to buffer received video data prior to displaying the video data in order for the video data to be displayed without interruption. There may be, in some instances, a tradeoff between the time that is needed to buffer video data and the manner in which the video data was encoded. That is, a client device may require a longer buffering duration for video data that has been encoded using a variable bit rate than for video data that has been encoded using a constant bit rate.
  • the perceptual quality of video data that has been encoded using a variable bit rate may be higher than video data that has been encoded using a constant bit rate.
  • some frames that is, intra-prediction mode encoded frames or I-frames
  • I-frames intra-prediction mode encoded frames
  • other frames that is, inter-prediction mode encoded frames such as P and B frames
  • reference frames previously coded frames
  • the techniques of this disclosure may include providing a plurality of representations, but with each of the representations having a different associated buffering duration. Accordingly, a client device may pick a representation that has a suitable bit rate, as well as a representation that has a suitable buffering time. In an example, a client device may initially select a representation having a certain bit rate and a relatively short buffering duration (albeit relatively lower quality), buffer data of the representation, then switch to a representation of the same bit rate but having a relatively longer buffering duration (e.g., having a relatively higher quality). While the example above includes two representations having the same bit rate, as described in greater detail below, in other examples, the representations may have differing bit rates (in addition to the differing buffering times).
  • the point at which the client device switches to another representation may be referred to as a "switch point.” That is, as described in greater detail below, the client device may switch to a representation at a so-called key frame.
  • a key frame is an intra-coded frame of a representation at which a client device may begin decoding the representation without access to earlier data of the representation if the data in the representation is in decode order.
  • the client device may switch from a representation at any point in the representation. For example, the client device may switch from a first representation to a second representation at any point in the first representation, provided the client device switches to the second representation at a key frame.
  • the client device may switch to the representation having the longer buffering duration after buffering an amount of data from the initial representation that is approximately equal to or greater than the longer buffering duration.
  • the client device may dynamically determine when to switch from the representation having the shorter buffering duration to the representation having the longer buffering duration based on the state of the buffer. Accordingly, the transition from the representation having the shorter buffering duration to the representation having the longer buffering duration may depend on network conditions. That is, if the buffer of the client device is filled relatively quickly (e.g., with a relatively high download data rate), the client device may be able to switch to the representation having the longer buffering duration more quickly than if the buffer of the client device is filled relatively slowly. Moreover, the client device may be playing data out from the buffer as other data is being retrieved. Accordingly, the client device may determine when to switch representations based on the relative speed of the download data rate compared to the play back data rate.
  • a server may provide a plurality of representations at a given bit rate.
  • a first representation may be of a relatively lower quality, but may have an associated buffering duration of one second.
  • a second representation may be of a relatively higher quality, but may have an associated buffering duration of 10 seconds.
  • a client device may request the fist representation. After buffering a certain amount of data of the first representation, e.g., 10 seconds of data (in terms of playback time), the client device may switch to the higher quality, second representation (e.g., having the relatively longer buffering duration). In this way, the client device may provide faster playback using the first representation, but also switch to a relatively higher quality representation after achieving a certain amount of buffered data.
  • the described example may display the content without stalls or re-buffering, despite varying buffering conditions (e.g., 10 seconds).
  • two or more representations may have the same bit rate but different switch point frequencies (referred to in this example as a target group of representations).
  • a client device may initially begin retrieving data of a different representation at a different bit rate, but at some point determine that network bandwidth availability has changed. Accordingly, the client device may switch to the target group of representations, and in particular, retrieve data of one of the target group of representations having a higher frequency of switch points. After buffering a sufficient amount of data of this representation, the client device may switch to another one of the target group of representations having a lower frequency of switch points.
  • a client device initially retrieves data from a representation having a bit rate of 10 Mbps.
  • the client device determines that network bandwidth has decreased, so the client device retrieves a set of representations having a lower bit rate, e.g., 5 Mbps.
  • the client device identifies a set of representations includes one representation with switch points every half-second (in terms of playback time), and another representation with switch points every five seconds.
  • the client device may initially retrieve data from the 5 Mbps representation with switch points every half-second, and buffer at least five seconds worth of data from this representation (again, in terms of playback time). Then, the client device may begin retrieving data from the 5 Mbps representation with switch points every five seconds.
  • the client device should have enough buffered data from the half-second switch point frequency representation to avoid buffer underflow, while also avoiding the necessity of executing two decoders simultaneously which may consume excess battery and processing power.
  • Client devices may be similarly configured to switch to a set of higher bit rate representations upon determining that network bandwidth has increased.In the example above, the client device transitions to representations having the same bit rates (e.g., 5 Mbps), but having different frequencies of switch points. In other examples, and as described in greater detail below, the client device may transition to representations having different bit rates that also have different switch point frequencies. For example, the client device may switch to a representation that has relatively a lower bit rate, but that has a higher perceptual quality due to a decreased frequency in switch points. In some examples, as described in greater detail below, the client device may also select a representation to switch to based on an amount of data that has been stored to a buffer of the client device.
  • FIG. 1 is a block diagram illustrating an example system 10 that implements techniques for streaming media data over a network.
  • system 10 includes content preparation device 20, server device 60, and client device 40.
  • Client device 40 and server device 60 are communicatively coupled by network 74, which may comprise the Internet.
  • content preparation device 20 and server device 60 may also be coupled by network 74 or another network, or may be directly communicatively coupled.
  • content preparation device 20 and server device 60 may comprise the same device.
  • Content preparation device 20 in the example of FIG. 1 , comprises audio source 22 and video source 24.
  • Audio source 22 may comprise, for example, a microphone that produces electrical signals representative of captured audio data to be encoded by audio encoder 26.
  • audio source 22 may comprise a storage medium storing previously recorded audio data, an audio data generator such as a computerized synthesizer, or any other source of audio data.
  • Video source 24 may comprise a video camera that produces video data to be encoded by video encoder 28, a storage medium encoded with previously recorded video data, a video data generation unit such as a computer graphics source, or any other source of video data.
  • Content preparation device 20 is not necessarily communicatively coupled to server device 60 in all examples, but may store multimedia content to a separate medium that is read by server device 60.
  • Raw audio and video data may comprise analog or digital data. Analog data may be digitized before being encoded by audio encoder 26 and/or video encoder 28. Audio source 22 may obtain audio data from a speaking participant while the speaking participant is speaking, and video source 24 may simultaneously obtain video data of the speaking participant. In other examples, audio source 22 may comprise a computer-readable storage medium comprising stored audio data, and video source 24 may comprise a computer-readable storage medium comprising stored video data. In this manner, the techniques described in this disclosure may be applied to live, streaming, real-time audio and video data or to archived, pre-recorded audio and video data.
  • Audio frames that correspond to video frames are generally audio frames containing audio data that was captured by audio source 22 contemporaneously with video data captured by video source 24 that is contained within the video frames.
  • audio source 22 captures the audio data
  • video source 24 captures video data of the speaking participant at the same time, that is, while audio source 22 is capturing the audio data.
  • an audio frame may temporally correspond to one or more particular video frames.
  • an audio frame corresponding to a video frame generally corresponds to a situation in which audio data and video data were captured at the same time and for which an audio frame and a video frame comprise, respectively, the audio data and the video data that was captured at the same time.
  • audio encoder 26 may encode a timestamp in each encoded audio frame that represents a time at which the audio data for the encoded audio frame was recorded
  • video encoder 28 may encode a timestamp in each encoded video frame that represents a time at which the video data for encoded video frame was recorded
  • an audio frame corresponding to a video frame may comprise an audio frame comprising a timestamp and a video frame comprising the same timestamp
  • Content preparation device 20 may include an internal clock from which audio encoder 26 and/or video encoder 28 may generate the timestamps, or that audio source 22 and video source 24 may use to associate audio and video data, respectively, with a timestamp.
  • audio source 22 may send data to audio encoder 26 corresponding to a time at which audio data was recorded
  • video source 24 may send data to video encoder 28 corresponding to a time at which video data was recorded
  • audio encoder 26 may encode a sequence identifier in encoded audio data to indicate a relative temporal ordering of encoded audio data but without necessarily indicating an absolute time at which the audio data was recorded
  • video encoder 28 may also use sequence identifiers to indicate a relative temporal ordering of encoded video data.
  • a sequence identifier may be mapped or otherwise correlated with a timestamp.
  • Audio encoder 26 generally produces a stream of encoded audio data, while video encoder 28 produces a stream of encoded video data.
  • Each individual stream of data may be referred to as an elementary stream.
  • An elementary stream is a single, digitally coded (possibly compressed) component of a representation.
  • the coded video or audio part of the representation can be an elementary stream.
  • An elementary stream may be converted into a packetized elementary stream (PES) before being encapsulated within a video file.
  • PES packetized elementary stream
  • the basic unit of data of an elementary stream is a packetized elementary stream (PES) packet.
  • coded video data generally corresponds to elementary video streams.
  • audio data corresponds to one or more respective elementary streams.
  • H.264/AVC defines the syntax, semantics, and decoding process for error-free bitstreams, any of which conform to a certain profile or level.
  • H.264/AVC does not specify the encoder, but the encoder is tasked with guaranteeing that the generated bitstreams are standard-compliant for a decoder.
  • a "profile" corresponds to a subset of algorithms, features, or tools and constraints that apply to them. As defined by the H.264 standard, for example, a "profile” is a subset of the entire bitstream syntax that is specified by the H.264 standard.
  • a “level” corresponds to the limitations of the decoder resource consumption, such as, for example, decoder memory and computation, which are related to the resolution of the pictures, bit rate, and macroblock (MB) processing rate.
  • a profile may be signaled with a profile_idc (profile indicator) value, while a level may be signaled with a level_idc (level indicator) value.
  • the H.264 standard recognizes that, within the bounds imposed by the syntax of a given profile, it is still possible to require a large variation in the performance of encoders and decoders depending upon the values taken by syntax elements in the bitstream such as the specified size of the decoded pictures.
  • the H.264 standard further recognizes that, in many applications, it is neither practical nor economical to implement a decoder capable of dealing with all hypothetical uses of the syntax within a particular profile. Accordingly, the H.264 standard defines a "level" as a specified set of constraints imposed on values of the syntax elements in the bitstream. These constraints may be simple limits on values.
  • constraints may take the form of constraints on arithmetic combinations of values (e.g., picture width multiplied by picture height multiplied by number of pictures decoded per second).
  • the H.264 standard further provides that individual implementations may support a different level for each supported profile.
  • a decoder conforming to a profile ordinarily supports all the features defined in the profile. For example, as a coding feature, B-picture coding is not supported in the baseline profile of H.264/AVC but is supported in other profiles of H.264/AVC.
  • a decoder conforming to a level should be capable of decoding any bitstream that does not require resources beyond the limitations defined in the level. Definitions of profiles and levels may be helpful for interpretability. For example, during video transmission, a pair of profile and level definitions may be negotiated and agreed for a whole transmission session.
  • a level may define, for example, limitations on the number of macroblocks that need to be processed, decoded picture buffer (DPB) size, coded picture buffer (CPB) size, vertical motion vector range, maximum number of motion vectors per two consecutive MBs, and whether a B-block can have sub-macroblock partitions less than 8x8 pixels.
  • DVB decoded picture buffer
  • CPB coded picture buffer
  • vertical motion vector range maximum number of motion vectors per two consecutive MBs
  • maximum number of motion vectors per two consecutive MBs and whether a B-block can have sub-macroblock partitions less than 8x8 pixels.
  • Video compression standards such as ITU-T H.261, H.262, H.263, MPEG-1, MPEG-2, H.264/MPEG-4 part 10, and the upcoming High Efficiency Video Coding (HEVC) standard, make use of motion compensated temporal prediction to reduce temporal redundancy.
  • the encoder such as video encoder 28, may use a motion compensated prediction from some previously encoded pictures (also referred to herein as frames) to predict the current coded pictures according to motion vectors.
  • I-pictures Intra coded picture
  • P-pictures Predicted pictures
  • B-pictures Bidirectional predicted pictures
  • B-pictures may use the reference picture before the current picture in temporal order.
  • each block of the B-picture may be predicted from one
  • Parameter sets generally contain sequence-layer header information in sequence parameter sets (SPS) and the infrequently changing picture-layer header information in picture parameter sets (PPS). With parameter sets, this infrequently changing information need not be repeated for each sequence or picture; hence, coding efficiency may be improved. Furthermore, the use of parameter sets may enable out-of-band transmission of header information, avoiding the need for redundant transmissions to achieve error resilience. In out-of-band transmission, parameter set NAL units are transmitted on a different channel than the other NAL units.
  • encapsulation unit 30 of content preparation device 20 receives elementary streams comprising coded video data from video encoder 28 and elementary streams comprising coded audio data from audio encoder 26.
  • video encoder 28 and audio encoder 26 may each include packetizers for forming PES packets from encoded data.
  • video encoder 28 and audio encoder 26 may each interface with respective packetizers for forming PES packets from encoded data.
  • encapsulation unit 30 may include packetizers for forming PES packets from encoded audio and video data.
  • Video encoder 28 may encode video data of multimedia content in a variety of ways, to produce different representations of the multimedia content at various bit rates and with various characteristics, such as pixel resolutions, frame rates, conformance to various coding standards, conformance to various profiles and/or levels of profiles for various coding standards, representations having one or multiple views (e.g., for two-dimensional or three-dimensional playback), or other such characteristics.
  • a representation as used in this disclosure, may comprise a combination of audio data and video data, e.g., one or more audio elementary stream and one or more video elementary streams.
  • Each PES packet may include a stream_id that identifies the elementary stream to which the PES packet belongs.
  • Encapsulation unit 30 is responsible for assembling elementary streams into video files of various representations.
  • Encapsulation unit 30 receives PES packets for elementary streams of a representation from audio encoder 26 and video encoder 28 and forms corresponding network abstraction layer (NAL) units from the PES packets.
  • NAL network abstraction layer
  • coded video segments are organized into NAL units, which provide a "network-friendly" video representation addressing applications such as video telephony, storage, broadcast, or streaming.
  • NAL units can be categorized to Video Coding Layer (VCL) NAL units and non-VCL NAL units.
  • VCL units may contain the core compression engine and may include block, macroblock, and/or slice level data.
  • Other NAL units may be non-VCL NAL units.
  • a coded picture in one time instance normally presented as a primary coded picture, may be contained in an access unit, which may include one or more NAL units.
  • Non-VCL NAL units may include parameter set NAL units and SEI NAL units, among others.
  • Parameter sets may contain sequence-level header information (in sequence parameter sets (SPS)) and the infrequently changing picture-level header information (in picture parameter sets (PPS)).
  • SPS sequence parameter sets
  • PPS picture parameter sets
  • PPS and SPS infrequently changing information need not to be repeated for each sequence or picture, hence coding efficiency may be improved.
  • the use of parameter sets may enable out-of-band transmission of the important header information, avoiding the need for redundant transmissions for error resilience.
  • parameter set NAL units may be transmitted on a different channel than other NAL units, such as SEI NAL units.
  • SEI Supplemental Enhancement Information
  • SEI messages may contain information that is not necessary for decoding the coded pictures samples from VCL NAL units, but may assist in processes related to decoding, display, error resilience, and other purposes.
  • SEI messages may be contained in non-VCL NAL units. SEI messages are the normative part of some standard specifications, and thus are not always mandatory for standard compliant decoder implementation.
  • SEI messages may be sequence level SEI messages or picture level SEI messages. Some sequence level information may be contained in SEI messages, such as scalability information SEI messages in the example of SVC and view scalability information SEI messages in MVC. These example SEI messages may convey information on, e.g., extraction of operation points and characteristics of the operation points.
  • encapsulation unit 30 may form a manifest file, such as a media presentation descriptor (MPD) that describes characteristics of the representations. Encapsulation unit 30 may format the MPD according to extensible markup language (XML).
  • MPD media presentation descriptor
  • Encapsulation unit 30 may provide data for one or more representations of multimedia content, along with the manifest file (e.g., the MPD) to output interface 32.
  • Output interface 32 may comprise a network interface or an interface for writing to a storage medium, such as a universal serial bus (USB) interface, a CD or DVD writer or burner, an interface to magnetic or flash storage media, or other interfaces for storing or transmitting media data.
  • Encapsulation unit 30 may provide data of each of the representations of multimedia content to output interface 32, which may send the data to server device 60 via network transmission or storage media.
  • USB universal serial bus
  • server device 60 includes storage medium 62 that stores various multimedia contents 64, each including a respective manifest file 66 and one or more representations 68A-68N (representations 68).
  • portions of manifest file 66 may be stored in separate locations, e.g., locations of storage medium 62 or another storage medium, potentially of another device of network 74 such as a proxy device.
  • representations 68 may be separated into adaptation sets.
  • an adaptation set may also be referred to as a "representation group.” That is, various subsets of representations 68 may include respective common sets of characteristics, such as codec, profile and level, resolution, number of views, file format for segments, text type information that may identify a language or other characteristics of text to be displayed with the representation and/or audio data to be decoded and presented, e.g., by speakers, camera angle information that may describe a camera angle or real-world camera perspective of a scene for representations in the adaptation set, rating information that describes content suitability for particular audiences, or the like.
  • Manifest file 66 may include data indicative of the subsets of representations 68 corresponding to particular adaptation sets, as well as common characteristics for the adaptation sets. Manifest file 66 may also include data representative of individual characteristics, such as bit rates, for individual representations of adaptation sets. In this manner, an adaptation set may provide for simplified network bandwidth adaptation. Representations in an adaptation set may be indicated using child elements of an adaptation set element of manifest file 66.
  • Server device 60 includes request processing unit 70 and network interface 72.
  • server device 60 may include a plurality of network interfaces.
  • any or all of the features of server device 60 may be implemented on other devices of a content delivery network, such as routers, bridges, proxy devices, switches, or other devices.
  • intermediate devices of a content delivery network may cache data of multimedia content 64, and include components that conform substantially to those of server device 60.
  • network interface 72 is configured to send and receive data via network 74.
  • Request processing unit 70 is configured to receive network requests from client devices, such as client device 40, for data of storage medium 72.
  • request processing unit 70 may implement hypertext transfer protocol (HTTP) version 1.1, as described in RFC 2616, "Hypertext Transfer Protocol - HTTP/1.1," by R. Fielding et al, Network Working Group, IETF, June 1999 . That is, request processing unit 70 may be configured to receive HTTP GET or partial GET requests and provide data of multimedia content 64 in response to the requests.
  • the requests may specify a segment of one of representations 68, e.g., using a URL of the segment. In some examples, the requests may also specify one or more byte ranges of the segment, thus comprising partial GET requests.
  • Request processing unit 70 may further be configured to service HTTP HEAD requests to provide header data of a segment of one of representations 68. In any case, request processing unit 70 may be configured to process the requests to provide requested data to a requesting device, such as client device 40.
  • multimedia content 64 includes manifest file 66, which may correspond to a media presentation description (MPD).
  • MPD media presentation description
  • Manifest file 66 may contain descriptions of different alternative representations 68 (e.g., video services with different qualities) and the description may include, e.g., codec information, a profile value, a level value, a bit rate, and other descriptive characteristics of representations 68.
  • Client device 40 may retrieve the MPD of a media presentation to determine how to access segments of representations 68.
  • web application 52 may retrieve configuration data (not shown) of client device 40 to determine decoding capabilities of video decoder 48 and rendering capabilities of video output 44.
  • the configuration data may also include any or all of a language preference selected by a user of client device 40, one or more camera perspectives corresponding to depth preferences set by the user of client device 40, and/or a rating preference selected by the user of client device 40.
  • Web application 52 may comprise, for example, a web browser or a media client configured to submit HTTP GET and partial GET requests.
  • Web application 52 may correspond to software instructions executed by one or more processors or processing units (not shown) of client device 40.
  • all or portions of the functionality described with respect to web application 52 may be implemented in hardware, or a combination of hardware, software, and/or firmware, where requisite hardware may be provided to execute instructions for software or firmware.
  • Web application 52 may compare the decoding and rendering capabilities of client device 40 to characteristics of representations 68 indicated by information of manifest file 66. Web application 52 may initially retrieve at least a portion of manifest file 66 to determine characteristics of representations 68. For example, web application 52 may request a portion of manifest file 66 that describes characteristics of one or more adaptation sets, in accordance with the techniques of this disclosure. Web application 52 may select a subset of representations 68 (e.g., an adaptation set) having characteristics that can be satisfied by the coding and rendering capabilities of client device 40. Web application 52 may then determine bit rates for representations in the adaptation set, determine a currently available amount of network bandwidth, and retrieve segments from one of the representations having a bit rate that can be satisfied by the network bandwidth.
  • a subset of representations 68 e.g., an adaptation set
  • higher bit rate representations may yield higher quality video playback, while lower bit rate representations may provide sufficient quality video playback when available network bandwidth decreases. Accordingly, when available network bandwidth is relatively high, web application 52 may retrieve data from relatively high bit rate representations, whereas when available network bandwidth is low, web application 52 may retrieve data from relatively low bit rate representations. In this manner, client device 40 may stream multimedia data over network 74 while also adapting to changing network bandwidth availability of network 74.
  • a client device such as client device 40
  • Client device 40 may switch between representations 68 at key frames.
  • key frames are frames of a representation 68 at which a client device may begin decoding the representation 68 without access to earlier data of the representation 68.
  • key frames are encoded as I-frames.
  • Client device 40 may switch from one representation 68 to another by retrieving data up to the temporal location of a key frame of the representation 68 to be switched to, then retrieving data starting at the key frame of the representation 68 to be switched to.
  • Key frames may therefore be referred to as switch points of a representation, or simply switch points.
  • client device 40 need not switch from a representation 68 at a key frame. For example, in certain instances, client device may switch from a representation 68 between switch points of the representation 68. In such instances, client device 40 may retrieve more of a representation 68 that necessary. That is, client device 40 may retrieve data from the representation 68 up to a switch point, but switch to another representation before reaching the switch point. In such instances, client device 40 may not play back the extra data retrieved from the switched-from representation, which may be referred to as overlap.
  • the client device 40 may only retrieve data from the representation 68 up to the point that allows playback up to the time that playback will begin for the representation to which the client device 40 switches. Thus, the client device 40 may not need to download all the data up to the next switch point in representation 68 to enable seamless switching from representation 68 to another representation. For example, suppose the sequence of frames in representation 68 is IPBBPBBPBBPBBBBI and these frames are to be played back in the order IBBPBBPBBPBBPBBI. In this example, there is a switch point at frames 1 and 16.
  • the switch point for switch to representation is at the presentation time of the 10 th frame of representation 68 to be played back, i.e., when the third P-frame in this playback sequence is to be played back, and thus this third P-frame and all subsequent frames are not to be played back.
  • Client device 40 may then download IPBBPBBPBB frames from representation 68, and thus be able to play back IBBPBBPBBP from representation 68.
  • IBBPBBPBBP IBBPBBPBBP
  • the data downloaded from representation 68 that is not played back, i.e., the data in the overlap, is the third P-frame, and thus the client device 40 does not have to download the last 5 frames preceding the next switch point at frame 16 in the representation 68 in order to enable the seamless switch.
  • the number of switch points in a given representation 68 may have an inverse relationship with a buffering duration for the representation 68. That is, a representation 68 having relatively few switch points may have a long buffering duration. Conversely, a representation 68 having relatively numerous switch points may have a relatively short buffering duration.
  • switch points Although more frequent switch points allow client device 40 to switch between representations 68 more frequently, key frames do not exploit as much redundancy as P or B frames, and therefore typically consume more coding bits than P or B frames.
  • switch points are provided less frequently in a representation 68, a client device 40 attempting to decode the representation 68 may need to wait for a lengthy period of time before receiving the next key frame, which may cause user experience to suffer (e.g., due to delayed starting of playback for the representation 68 initially or after a switch between representations 68). Therefore, strategic decisions are typically made regarding how frequently to include switch points in representations 68 of multimedia content.
  • the term "frequency" when describing the locations of switch points refers to an interval between switch points, which may describe a temporal distance between switch points in the representation 68. While the frequency may be relatively steady, the temporal distance between switch points may vary between switch points by a certain margin, in some examples.
  • the techniques of this disclosure involve providing information from the server device 60 to the client device 40 indicative of distances between switch points of various representations 68 of the multimedia content.
  • server device 60 may provide information to the client device 40 indicative of intervals between switch points for each representation (e.g., switch point frequency within a representation) within a manifest file/MPD.
  • the client device 40 may use this information to initially select a representation 68 having relatively frequent switch points (albeit relatively lower quality), buffer data of the representation 68, then switch to a representation 68 having relatively higher quality at a future switch point of the higher-quality representation 68.
  • server device 60 may assign the same bit rate to a group of representations 68, but assign different frequencies of switch points to the representations 68 in the group. Because relatively more bits are used to encode switch points (due to switch points being coded as I-frames), the representations 68 with more frequent switch points will tend to have relatively lower quality, but allow client devices to begin playback more quickly in the average case. Therefore, using information indicative of distances between switch points for the representations 68, client device 40 may initially retrieve and buffer data from a representation 68 having relatively more frequent switch points. After buffering enough data from the initial representation to avoid gaps in playback, client device 40 may begin requesting and buffering data starting at a switch point of a different representation 68 having less frequent switch points, but relatively higher quality.
  • client device 40 may begin requesting and buffering data of a representation 68 having an initial bit rate, for example at 500 Kbps with a switch point each 1 second. After buffering enough data from the initial representation to avoid gaps in playback, client device 40 may switch to a representation 68 having a relatively lower bit rate than the initial bit rate, but having the same or a higher perceptual quality (e.g., due to a decrease in the frequency of switch points), for example at 400 Kbps with a switch point each 5 seconds.
  • client device 40 may select an initial representation 68 having a relatively high frequency of switch points, for example 500 Kbps with switch points each 1 second. After buffering at least some of the initial representation 68, client device 40 may transition to a representation 68 having a lower frequency of switch points that is coded more efficiently (which may result in an increased perceptual quality), for example 450 Kbps with switch points each 3 seconds.
  • client device 40 may select a representation 68 based on an amount of data that has been buffered. For example, in general, when a buffer of client device 40 is nearly empty, client device 40 may switch to a representation 68 having relatively frequent switch points to allow a seamless transition to the representation 68. That is, client device 40 may need a relatively increased opportunity to switch representations 68 as the buffer of client device 40 empties in order to avoid an interruption in playback (e.g., re-buffering). In contrast, after the buffer has at least partially filled, client device 40 may transition to a representation 68 having relatively fewer switch points that is coded more efficiently (which may result in an increased perceptual quality).
  • the bit rate of the transition to representation 68 may be a higher bit rate, which allows an increased play back quality due to more efficient video encoding (because there are less switch points) and due to higher bit rate. That is, client device 40 may need fewer opportunities to switch representations 68 when the buffer is relatively full, because the full buffer reduces the risk of playback interruption.
  • the chosen representation when selecting a representation 68 with less frequent switch points, the chosen representation may be at a lower bit rate and the same or better quality, thus reducing the amount of data needed to play back and maintain high quality play back.
  • the chosen representation may also be at equal or higher bit rate with even better quality, thus providing an even higher quality playback experience. Accordingly, client device 40 can afford to retrieve a representation 68 having less frequent switch points, thereby retrieving content having a better perceptual quality for the same or lower bit cost, or even better quality with a higher bit cost, but in all cases with minimal chances of causing a playback stall or a re-buffering event.
  • the amount of bandwidth that is available for client device 40 may substantially increase.
  • client device 40 may begin retrieving a representation 68 having a higher bit rate that has a relatively high frequency of switch points.
  • the high frequency of switch points may provide an increased opportunity to switch to the higher bit rate representation, thereby allowing client device 40 to take advantage of the increased bandwidth to improve the experience of a user more quickly.
  • representations 68 of an adaptation set may alternate between a representation 68 having relatively frequent switch points and a representation 68 having relatively infrequent switch points for each consecutive bit rate representation. For example, there may be representations at 300 Kbps, 500 Kbps, 800 Kbps, 1300 Kbps, 2100 Kbps, and 3400 Kbps with respective switch point frequencies of 1 second, 3 seconds, 1 second, 3 seconds, 1 second, and 3 seconds.
  • client device 40 may select a representation 68 from the adaptation set based on both changes in the available bandwidth (e.g., download speed) and the status of a buffer of client device 40 (e.g., whether the buffer is relatively full or empty). For example, if the buffer is relatively close to empty and/or the amount of bandwidth that is available is drastically reduced, client device 40 may choose a representation that has a relatively lower bit rate having relatively frequent switch points.
  • client device 40 may choose a representation that has relatively low frequency switch points with a lower bit rate. This option of providing representations of an adaptation set with a mix of lower and higher frequency switch points may in some cases provide a good balance between video encoding efficiency (less frequent switch points) and reaction time to changes in network conditions (more frequent switch points).
  • representations 68 having relatively lower bit rates may have relatively frequent switch points, while representations having relatively higher bit rates may have less frequent switch points.
  • client device 40 may select a representation 68 having a low bit rate for startup (e.g., below the rate available based on bandwidth conditions) and quickly move to a higher bit rate representation 68, for example, after filling the buffer.
  • Client device 40 may continue to retrieve representations 68 having a higher bit rate to achieve a high quality play back while ameliorating the risk of stalls or re-buffering as long as the buffer is relatively full.
  • This option of providing representations of an adaptation set with lower frequency switch points for lower bit rates and higher frequency switch points for higher switch points may provide high quality video encoding efficiency when the buffer is relatively full (which can be the majority of the time if network conditions are usually good) with reasonable strategies to react to quick deterioration in network conditions (more frequent switch points for the lower bit rate representations allow switching to these representations quickly when conditions deteriorate).
  • a client device 40 may select a representation 68 having a bit rate that is substantially below an available download rate when the buffer of client device 40 is not as full, thereby reducing the likelihood of stalling or re-buffering. As the buffer fills, client device 40 may begin to retrieve representations 68 having a bit rate that is near the download rate. Accordingly, client device 40 may select a representation having a higher bit rate with fewer switch points and a decreased probability of stalling or re-buffering, because if the download rate decreases client device 40 has ample opportunity to switch to a lower bit rate representation 68 (due to the amount of data in the buffer).
  • the representation 68 having the lower bit rate also has more frequent switch points. Accordingly, client device 40 may switch to the lower bit rate representation 68 relatively quickly, which further provides protection against stalls or re-buffering when the download rate drops.
  • representations 68 having relatively lower bit rates may have relatively less frequent switch points, while representations having relatively higher bit rates may have more frequent switch points.
  • representations 68 coded at a relatively lower bit rate may suffer in quality more than representations 68 coded at a higher bit rate with more frequent switch points.
  • client device 40 may initially select a representation 68 having a relatively low bit rate, but may switch to a representation 68 having a higher bit rate (at a switch point of the higher bit rate representation 68, which may not coincide with a switch point for the lower bit rate representation) if the buffer is filling up quickly.
  • client device 40 may be configured to initially select a representation 68 based on the frequency of switch points, so long as the bit rate of the selected representation 68 does not exceed the currently available bandwidth. After buffering enough data of the initially selected representation 68, client device 40 may begin requesting data from a higher bit rate representation 68, which may have less frequent switch points than the initially selected representation 68.
  • server device 60 may broadcast a representation 68 of multimedia content with relatively long periods of time between switch points (e.g., 10 seconds of playback time).
  • Client device 40 may be configured to request a unicast of a different representation 68 of the multimedia content having relatively more frequent switch points initially, then switch to the broadcast after buffering sufficient data of the unicast representation 68.
  • the client device 40 may again begin retrieving the other representation using unicast, and switch back to the broadcast after buffering a sufficient amount of data of the unicast representation 68.
  • two or more representations may have the same bit rate but different switch point frequencies (referred to in this example as a target group of representations, which may be included in an adaptation set).
  • Client device 40 may initially begin retrieving data of a certain representation at a certain bit rate, but at some point determine that network bandwidth availability has changed. Accordingly, client device 40 may switch to a target group of representations (e.g., an adaptation set of representations having the same or approximately the same bit rate, but having different temporal intervals between switch points), and in particular, retrieve data of one of the target group of representations having a higher frequency of switch points. After buffering a sufficient amount of data of this representation, client device 40 may switch to another one of the target group of representations having a lower frequency of switch points.
  • a target group of representations e.g., an adaptation set of representations having the same or approximately the same bit rate, but having different temporal intervals between switch points
  • client device 40 initially retrieves data from a representation having a bit rate of 10 Mbps.
  • client device 40 determines that network bandwidth has decreased, so client device 40 determines a set of representations (e.g., an adaptation set) having a lower bit rate, e.g., 5 Mbps.
  • client device 40 may determine that the set of representations includes one representation with switch points every half-second (in terms of playback time), and another representation with switch points every five seconds.
  • Client device 40 may initially retrieve data from the 5 Mbps representation with switch points every half-second, and buffer at least five seconds worth of data from this representation (again, in terms of playback time). Then, client device 40 may begin retrieving data from the 5 Mbps representation with switch points every five seconds.
  • client device 40 should have enough buffered data from the half-second switch point frequency representation to avoid buffer underflow, while also avoiding the necessity of executing two decoders simultaneously which may consume excess battery and processing power.
  • Client device 40 may be similarly configured to switch to a set of higher bit rate representations upon determining that network bandwidth has increased.
  • the server device 60 may be configured to temporally align switch points across representations 68. That is, for two representations 68 having different frequencies of switch points, the switch points of the representation 68 having the lower frequency of switch points occur at the same temporal locations (during playback) as switch points of the representation 68 having the higher frequency of switch points.
  • the client device may be configured to buffer data of a full segment of the representation 68 having the higher frequency switch points, and switch to the representation 68 having the lower frequency switch points following the segment.
  • the client device 40 may avoid retrieving and decoding overlapping data from different representations 68 when switching between the representations 68.
  • client device 40 need not switch from a particular representation 68 at a switch point.
  • temporal alignment of switch points may help to avoid retrieving overlapping data
  • switch points need not be temporally aligned to perform the techniques of this disclosure.
  • client device 40 may maintain a data structure indicative of particular representations 68 from which client device 40 requested data for multimedia content 64. Client device 40 may also maintain indications of exactly what was played out, and at what time. That is, the data structure may provide information representative of start and end times in both real (or "wall clock") time and presentation time. The data structure may further provide information representative of an initial startup time and the start of playback. After finishing playback of multimedia content 64, client device 40 may send the data structure to server device 60 and/or content preparation device 20. Server device 60 and/or content preparation device 20 may use information received from client device 40 to determine more optimal ways of improving quality of experience, such as to reduce pauses in playback.
  • Network interface 54 may receive and provide data of segments of a selected representation to web application 52, which may in turn provide the segments to decapsulation unit 50.
  • Decapsulation unit 50 may decapsulate elements of a video file into constituent PES streams, depacketize the PES streams to retrieve encoded data, and send the encoded data to either audio decoder 46 or video decoder 48, depending on whether the encoded data is part of an audio or video stream, e.g., as indicated by PES packet headers of the stream.
  • Audio decoder 46 decodes encoded audio data and sends the decoded audio data to audio output 42
  • video decoder 48 decodes encoded video data and sends the decoded video data, which may include a plurality of views of a stream, to video output 44.
  • Video encoder 28, video decoder 48, audio encoder 26, audio decoder 46, encapsulation unit 30, web application 52, and decapsulation unit 50 each may be implemented as any of a variety of suitable processing circuitry, as applicable, such as one or more microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), discrete logic circuitry, software, hardware, firmware or any combinations thereof.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • Each of video encoder 28 and video decoder 48 may be included in one or more encoders or decoders, either of which may be integrated as part of a combined video encoder/decoder (CODEC).
  • each of audio encoder 26 and audio decoder 46 may be included in one or more encoders or decoders, either of which may be integrated as part of a combined CODEC.
  • An apparatus including video encoder 28, video decoder 48, audio encoder audio encoder 26, audio decoder 46, encapsulation unit 30, web application 52, and/or decapsulation unit 50 may comprise an integrated circuit, a microprocessor, and/or a wireless communication device, such as a cellular telephone.
  • FIG. 2 is a conceptual diagram illustrating elements of an example multimedia content 100.
  • Multimedia content 100 may correspond to multimedia content 64 ( FIG. 1 ), or another multimedia content stored in memory 62.
  • multimedia content 100 includes media presentation description (MPD) 102 and a plurality of representations 110-120.
  • Representation 110 includes optional header data 112 and segments 114A-114N (segments 114), while representation 120 includes optional header data 122 and segments 124A-124N (segments 124).
  • the letter N is used to designate the last movie fragment in each of representations 110, 120 as a matter of convenience. In some examples, there may be different numbers of movie fragments between representations 110, 120.
  • MPD 102 may comprise a data structure separate from representations 110-120.
  • MPD 102 may correspond to manifest file 66 of FIG. 1 .
  • representations 110-120 may correspond to representations 68 of FIG. 1 .
  • MPD 102 may include data that generally describes characteristics of representations 110-120, such as coding and rendering characteristics, adaptation sets, a profile to which MPD 102 corresponds, text type information, camera angle information, rating information, and the like.
  • Remote periods may also be referred to as external periods.
  • FIGS. 4-5 discussed in greater detail below, illustrate various examples of multimedia content with various elements included in either or both of an MPD and/or representations (such as within segments of representations or header data of representations).
  • MPD 102 and/or header data 112, 122 may include SP interval information 104 that indicates a frequency (or an interval) of switch points for representations 110, 120. That is, SP interval information 104 may provide an indication of the temporal frequency with which switch points (e.g., also referred to as key frames) occur in a given duration. Additionally or alternatively, SP interval information 104 may provide an indication of the duration, or interval between switch points. Any or all of the MPDs of FIGS. 4-5 may correspond substantially to MPD 102 of FIG. 2 .
  • Header data 112 when present, may describe characteristics of segments 114, e.g., temporal locations of random access points, which of segments 114 includes random access points, byte offsets to random access points within segments 114, uniform resource locators (URLs) of segments 114, or other aspects of segments 114.
  • Header data 122 when present, may describe similar characteristics for segments 124. Additionally or alternatively, such characteristics may be fully included within MPD 102.
  • Segments 114 include one or more coded video samples, each of which may include frames or slices of video data. Each of the coded video samples of segments 114 may have similar characteristics, e.g., height, width, and bandwidth requirements. Such characteristics may be described by data of MPD 102, though such data is not illustrated in the example of FIG. 2 .
  • MPD 102 may include characteristics as described by the 3GPP Specification, with the addition of any or all of the signaled information described in this disclosure.
  • Each of segments 114, 124 may be associated with a unique uniform resource identifier (URI), e.g., a uniform resource locator (URL).
  • URI uniform resource identifier
  • each of segments 114, 124 may be independently retrievable using a streaming network protocol, such as DASH.
  • a destination device such as client device 40, may use an HTTP Get request to retrieve segments 114 or 124.
  • client device 40 may use HTTP partial Get requests to retrieve specific byte ranges of segments 114 or 124.
  • Segments 114, 124 may include switch points for representations 110, 120.
  • a switch point may generally correspond to a random access point (RAP).
  • RAP random access point
  • Various representations may include switch points at different intervals, e.g., RAPs that occur at different frequencies in the representations.
  • each of segments 114 of representation 110 may include a switch point
  • segments 124A, 124C, 124E, and so on of representation 120 may include switch points, but segments 124B, 124D, and so on of representation 120 might not include switch points.
  • client device 40 may initially retrieve data from representation 110, then switch to representation 120 after retrieving a sufficient amount of data. For example, client device 40 may retrieve segments 114A and 114B of representation 110. In the case that segments 124A and 124C of representation 120 include random access points, client device 40 may retrieve segments 114A and 114B of representation 110, then determine that an amount of data of representation 110 has been buffered with a temporal playback time exceeding the time between switch points of representation 120. Accordingly, after retrieving data of segments 114A and 114B of representation 110, client device 40 may retrieve data of segment 124C, which follows segment 124B in representation 120.
  • FIG. 3 is a block diagram illustrating elements of an example video file 150, which may correspond to a segment of a representation, such as one of segments 114, 124 of FIG. 2 .
  • Each of segments 114, 124 may include data that conforms substantially to the arrangement of data illustrated in the example of FIG. 3 .
  • segments of FIGS. 4-5 discussed below may also conform substantially to the structure of video file 150.
  • video files in accordance with the ISO base media file format and extensions thereof store data in a series of objects, referred to as "boxes.”
  • video file 150 includes file type (FTYP) box 152, movie (MOOV) box 154, movie fragment (MOOF) boxes 162, and movie fragment random access (MFRA) box 164.
  • File type (FTYP) box 152 generally describes a file type for video file 150.
  • File type box 152 may include data that identifies a specification that describes a best use for video file 150.
  • File type box 152 may be placed before MOOV box 154, movie fragment boxes 162, and MFRA box 164.
  • a segment such as video file 150
  • the MPD update box may include information indicating that an MPD corresponding to a representation including video file 150 is to be updated, along with information for updating the MPD.
  • the MPD update box may provide a URI or URL for a resource to be used to update the MPD.
  • the MPD update box may include data for updating the MPD.
  • the MPD update box may immediately follow a segment type (STYP) box (not shown) of video file 150, where the STYP box may define a segment type for video file 150.
  • STYP segment type box
  • MOOV box 154 in the example of FIG. 3 , includes movie header (MVHD) box 156, track (TRAK) box 158, and one or more movie extends (MVEX) boxes 160.
  • MVHD box 156 may describe general characteristics of video file 150.
  • MVHD box 156 may include data that describes when video file 150 was originally created, when video file 150 was last modified, a timescale for video file 150, a duration of playback for video file 150, or other data that generally describes video file 150.
  • TRAK box 158 may include data for a track of video file 150.
  • TRAK box 158 may include a track header (TKHD) box that describes characteristics of the track corresponding to TRAK box 158.
  • TKHD track header
  • TRAK box 158 may include coded video pictures, while in other examples, the coded video pictures of the track may be included in movie fragments 162, which may be referenced by data of TRAK box 158.
  • video file 150 may include more than one track.
  • MOOV box 154 may include a number of TRAK boxes equal to the number of tracks in video file 150.
  • TRAK box 158 may describe characteristics of a corresponding track of video file 150.
  • TRAK box 158 may describe temporal and/or spatial information for the corresponding track.
  • a TRAK box similar to TRAK box 158 of MOOV box 154 may describe characteristics of a parameter set track, when encapsulation unit 30 ( FIG. 1 ) includes a parameter set track in a video file, such as video file 150.
  • Encapsulation unit 30 may signal the presence of sequence level SEI messages in the parameter set track within the TRAK box describing the parameter set track.
  • MVEX boxes 160 may describe characteristics of corresponding movie fragments 162, e.g., to signal that video file 150 includes movie fragments 162, in addition to video data included within MOOV box 154, if any.
  • coded video pictures may be included in movie fragments 162 rather than in MOOV box 154. Accordingly, all coded video samples may be included in movie fragments 162, rather than in MOOV box 154.
  • MOOV box 154 may include a number of MVEX boxes 160 equal to the number of movie fragments 162 in video file 150.
  • Each of MVEX boxes 160 may describe characteristics of a corresponding one of movie fragments 162.
  • each MVEX box may include a movie extends header box (MEHD) box that describes a temporal duration for the corresponding one of movie fragments 162.
  • MEHD movie extends header box
  • encapsulation unit 30 may store a sequence data set in a video sample that does not include actual coded video data.
  • a video sample may generally correspond to an access unit, which is a representation of a coded picture at a specific time instance.
  • the coded picture include one or more VCL NAL units which contains the information to construct all the pixels of the access unit and other associated non-VCL NAL units, such as SEI messages.
  • encapsulation unit 30 may include a sequence data set, which may include sequence level SEI messages, in one of movie fragments 162.
  • Encapsulation unit 30 may further signal the presence of a sequence data set and/or sequence level SEI messages as being present in one of movie fragments 162 within the one of MVEX boxes 160 corresponding to the one of movie fragments 162.
  • Movie fragments 162 may include one or more coded video pictures.
  • movie fragments 162 may include one or more groups of pictures (GOPs), each of which may include a number of coded video pictures, e.g., frames or pictures.
  • movie fragments 162 may include sequence data sets in some examples.
  • Each of movie fragments 162 may include a movie fragment header box (MFHD, not shown in FIG. 3 ).
  • the MFHD box may describe characteristics of the corresponding movie fragment, such as a sequence number for the movie fragment. Movie fragments 162 may be included in order of sequence number in video file 150.
  • MFRA box 164 may describe random access points within movie fragments 162 of video file 150. MFRA box 164 is generally optional and need not be included in video files, in some examples. Likewise, a client device, such as client device 40, does not necessarily need to reference MFRA box 164 to correctly decode and display video data of video file 150. MFRA box 164 may include a number of track fragment random access (TFRA) boxes (not shown) equal to the number of tracks of video file 150, or in some examples, equal to the number of media tracks (e.g., non-hint tracks) of video file 150.
  • TFRA track fragment random access
  • video file 150 may additionally include a segment index (SIDX) box (not shown in this example).
  • SIDX box may occur at or near the beginning of video file 150, and may provide an indication of a location (e.g., starting byte and length or byte range) of a RAP for video file 150.
  • a representation may include a SIDX box in header information for the representation, such as header data 112, 122 ( FIG. 2 ).
  • client device 40 may be configured to implicitly determine frequencies (or intervals) between switch points for a representation including video file 150 based on information provided by one or more SIDX boxes of the representation.
  • client device 40 may determine relative temporal intervals between RAPs for the representation.
  • SIDX box of a representation may provide an explicit indication of frequencies of or intervals between switch points for the representation.
  • FIG. 4 is a conceptual diagram illustrating an example multimedia content 200 including MPD 202 and adaptation sets 210-220.
  • Multimedia content 200 may correspond to multimedia content 64 ( FIG. 1 ), or another multimedia content stored in memory 62.
  • representations of multimedia content 200 are arranged by adaptation set. That is, representations with a common set of characteristics may be formed into an adaptation set, which provides for simplified network bandwidth adaptation.
  • MPD 202 includes common representation characteristics 204A that includes information describing common characteristics of adaptation set 210 and common representation characteristics 204B describing common characteristics of adaptation set 220.
  • the common characteristics may include coding and/or rendering characteristics of the representations, such as a codec, profile and level of the codec to which the representations in the representation conform, pixel resolution, frame rate, or other characteristics of representations.
  • the characteristics may include a text type value, a camera angle value, and/or a rating value in addition to the characteristics discussed above.
  • the text type value may describe characteristics of text to be displayed with the video data (e.g., closed captioning text).
  • the text type value may describe, for example, a language of the text, a location on the screen at which to display the text, font and/or size of the text, or other characteristics of the text.
  • the camera angle value may describe a real-world horizontal camera position for a camera used (either physically or conceptually) to generate coded video data of corresponding representations.
  • a client device may select data from two or more representations to be displayed substantially simultaneously, e.g., to produce a three-dimensional video playback effect.
  • the horizontal real-world camera locations may enable the client device to select representations to increase or decrease the relative amount of depth in the three-dimensional playback of the video data.
  • the rating may describe content suitability for particular audiences.
  • the Motion Picture Association of America defines ratings including G, PG, PG-13, R, and NC-17.
  • the British Board of Film Classification defines ratings including U, PG, 12A, 12, 15, 18, and R18.
  • categories of motion pictures include a general audiences category, a protected category, a parental guidance category, and a restricted category.
  • a client device may select an appropriate one of adaptation sets 210-220, based at least in part on the corresponding common representation characteristics 204.
  • MPD 202 also includes individual representation characteristics 206A, 206B, 208A, and 208B, corresponding respectively to representations 212A, 212B, 222A, 222B.
  • Individual representation characteristics 206A, 206B, 208A, and 208B may include information representative of characteristics of representations 212A, 212B, 222A, 222B not indicated by common representation characteristics 204.
  • individual representation characteristics 206A, 206B, 208A, and 208B may include information representative of bit rates for respective ones of representations 212A, 212B, 222A, 222B.
  • Representations of an adaptation set may be considered mutually exclusive, in that they may represent the same content (same video, same language audio, etc.) with different encoding or other parameters.
  • MPD 202 may provide information for selecting one of adaptation sets 210-220, e.g., common representation characteristics 204. This information may include information indicative of whether a client can decode and render a given representation. In this manner, the client device may remove from consideration representations that the client device is incapable of decoding and/or rendering. Accordingly, client device 40 may select a suitable adaptation set that can be decoded and rendered, then select a representation from the group based on, e.g., network bandwidth availability.
  • an adaptation set such as one of the adaptation sets 210, 220, and the like, may include a plurality of representations having the same, or approximately the same bit rate, but including different intervals of switch points.
  • the representations within the adaptation set may be of varying quality, and may have varying associated buffering durations (e.g., each of the representations within an adaptation set may have an alternative associated minBufferTime, as referred to in the DASH standard). That is, a noted above, a representation with a relatively greater number of switch points may have a relatively shorter buffering duration than a representation with fewer switch points. However, for the given bit rate of the adaptation set, the representation with the greater number of switch points may be of a relatively lower quality than the representation with fewer switch points.
  • client device 40 may select an adaptation set having a plurality of representations with the same, or approximately the same bit rate.
  • Client device 40 may initially select a representation having a certain bit rate and a relatively short buffering duration (e.g., albeit relatively lower quality), buffer data of the representation, then switch to a representation of the same bit rate but having a relatively longer buffering duration (e.g., having a relatively higher quality).
  • adaptation sets may have differing bit rates.
  • an adaptation set may have representations 68 that alternate between a representation 68 having relatively frequent switch points and a representation 68 having relatively infrequent switch points for each consecutive bit rate representation.
  • Client device 40 may also be configured with user preferences for, e.g., rating, language, and/or depth. Accordingly, client device 40 may also select one or more adaptation sets such that the selected groups conform to the user preferences. Client device 40 may then select a subset of available adaptation sets that can be played concurrently. When client device 40 is only capable of displaying one view, client device 40 may elect to retrieve data only from one representation. On the other hand, when client device 40 is stereo view or multiview capable, client device 40 may retrieve data from two or more representations.
  • client device 40 may select representations from the adaptation sets based on, e.g., available network bandwidth. As available network bandwidth changes (e.g., increases or decreases), client device 40 may adjust selections of representations from the adaptation sets to adapt to the changing network bandwidth conditions. Of course, client device 40 may also change representation selections if user preferences or device capabilities (e.g., decoding and rendering capabilities) change.
  • available network bandwidth changes (e.g., increases or decreases)
  • client device 40 may adjust selections of representations from the adaptation sets to adapt to the changing network bandwidth conditions.
  • client device 40 may also change representation selections if user preferences or device capabilities (e.g., decoding and rendering capabilities) change.
  • client device 40 may select an adaptation set having a plurality of representations with the same, or approximately the same bit rate.
  • Client device 40 may initially select a representation having a certain bit rate and a relatively short buffering duration (e.g., albeit relatively lower quality), buffer data of the representation, then switch to a representation of the same bit rate but having a relatively longer buffering duration (e.g., having a relatively higher quality).
  • Common representation characteristics 204 may correspond to RepresentationGroup XML elements of MPD 202, in some examples. Individual representation characteristics may correspond to sub-elements of corresponding RepresentationGroup elements of MPD 202, in some examples.
  • FIG. 5 is a conceptual diagram illustrating example adaptation sets.
  • a first adaptation set 300 includes representations 304A, 304B, and 304C (collectively, representations 304), while a second adaptation set 308 includes representations 312A, 312B, and 312C (collectively, representations 312).
  • the adaptation sets 300 and 308 may be similar to, or the same as, adaptation sets described with respect to FIGS. 4-5 .
  • the example adaptation sets 300 and 308 shown and described with respect to FIG. 5 may be compatible with any of the techniques described herein.
  • each of the representations 304 of adaptation set 300 may have the same, or substantially the same bit rate.
  • each of the representations 304 may have alternative numbers of switch points 316.
  • switch points 316 are typically encoded as I-frames, and may also be referred to as key frames.
  • representations 304 may have different bit rates (in addition to having alternative numbers of switch points 316).
  • switch points 316 may be generally aligned within an adaptation set.
  • representation 304A includes a relatively large number of switch points as compared to representation 304B and 304C. That is, in some examples, representation 304B may include a subset of the switch points of 304A. Moreover, representation 304C may include a subset of the switch points of 304B. In other examples, the switch points of representations in an adaptation set need not necessarily be aligned.
  • the switch points 316 of representation 304A may occur approximately every two seconds. According to the example shown in FIG. 5 , then, the switch points 316 of representation 304B may occur approximately every four seconds, with the switch points 316 of representation 304C may occur approximately every eight seconds. It should be understood that such durations between switch points are provided merely as examples for purposes of explanation, and alternative durations between switch points are possible.
  • the frequency of switch points may be related to a buffering duration (e.g., as identified in Table 3 above as minBufferTittle ).
  • a buffering duration e.g., as identified in Table 3 above as minBufferTittle .
  • representation 304A may have a shorter buffering duration than representation 304B, which may have a shorter buffering duration than representation 304C.
  • the quality of representation 304C may be better than that of 304B, which may be better than that of 304C.
  • Adaptation set 308 may be configured similarly to adaptation set 300, but may include representations having a different bit rate than adaptation set 300. While the switch points 316 of the representations 312 shown in the example of FIG. 5 are not necessarily aligned, it should be understood, as noted above, that the switch points 316 may be aligned in some examples.
  • a server device such as server device 60, may provide a plurality of adaptation sets having representations of different bit rates, such as adaptation sets 300 and 308 (e.g., as well as additional adaptation sets) shown in FIG. 5 .
  • a client device such as client device 40 may select an adaptation set having an appropriate bit rate for bandwidth conditions, as well as a representation with a certain number of switch points (e.g., and corresponding minBufferTime ).
  • client device 40 may initially select a representation having a certain bit rate and a relatively short buffering duration (e.g., albeit relatively lower quality), buffer data of the representation, then switch to a representation of the same bit rate but having a relatively longer buffering duration (e.g., having a relatively higher quality).
  • a relatively short buffering duration e.g., albeit relatively lower quality
  • FIG. 6 is a conceptual diagram illustrating example representations.
  • a first representation 320 includes a plurality of segments 322A-322D (collectively, segments 322), while a second representation 324 includes a plurality of segments 326 (e.g., beginning with segment 326A).
  • the representations shown in FIG 6 may be configured similarly to representations 110 and 120 shown in FIG. 2 .
  • the example representations shown and described with respect to FIG. 6 may be compatible with any of the techniques described herein.
  • the techniques of this disclosure generally relate to improving a user's experience when initially retrieving multimedia content and when performing bandwidth adaptation. Although certain techniques described above refer to representations having the same bit rate, these techniques may also be applied to representations having different bit rates.
  • representation 320 is an example of a representation that may be provided by a server via unicast
  • representation 324 is an example of a representation that may be provided via broadcast.
  • representation 320 includes relatively smaller segments 322 than the segments 326 of representation 324.
  • representation 320 may be associated with a relatively shorter buffering duration than representation 324.
  • a client device such as client device 40 ( FIG. 1 ) may be configured to initially select a representation based on the frequency of switch points, so long as the bit rate of the selected representation does not exceed the currently available bandwidth. Accordingly, in the example shown in FIG. 6 , client device 40 may initially select representation 320. After buffering enough data of the initially selected representation 320, client device 40 may begin requesting data from a higher bit rate representation. In the example shown in FIG. 6 , client device 40 may begin requesting data from representation 324, which may have less frequent switch points than the initially selected representation 320. Client device 40 may also switch back to representation 320 at sometime in the future, for example, if representation 324 is not available.
  • a server such as server device 60 ( FIG. 1 ) may broadcast representation 324 having relatively long periods of time between switch points (e.g., 10 seconds of playback time).
  • Client device 40 may be configured to request a unicast of representation 320 having relatively more frequent switch points initially, then switch to the broadcast representation 324 after buffering sufficient data of the unicast representation 320.
  • the client device 40 may again begin retrieving the other representation 320 using unicast, and switch back to the broadcast representation 234 after buffering a sufficient amount of data of the unicast representation 320.
  • FIG. 7 is a conceptual diagram that graphically represents an example of a determined amount of network bandwidth, and a corresponding indication of a representation from which data is retrieved.
  • the example of FIG. 7 assumes that there are at least four representations of a particular multimedia content: a 10 Mbps representation with switch points approximately every 3 seconds, a 10 Mbps representation with switch points approximately every 0.5 seconds, a 5 Mbps representation with switch points approximately every 2 seconds, and a 5 Mbps representation with switch points approximately every 0.5 seconds.
  • a server device such as server device 60, may provide indications of switch point frequencies (SP freq) for representations in a manifest file for the respective multimedia content.
  • the manifest file may correspond to, for example, a media presentation description (MPD) file for the multimedia content.
  • Client devices are generally configured to retrieve and analyze the manifest file to determine characteristics and attributes of representations of the multimedia content.
  • server device 60 may provide the indication of the frequencies of switch points for various representations in the manifest file for the representations. Providing data representative of characteristics of attributes of a representation is conventionally referred to as “signaling" the data. In other examples, server device 60 may signal the frequencies of switch points for the representations in the representations themselves. Alternatively, client devices, such as client devices 40, may be configured to infer the frequencies of switch points from data for segment index (SIDX) elements associated with segments of the representations.
  • SIDX segment index
  • client device 40 may initially retrieve 10 Mbps representation with switch points approximately every 3 seconds. Upon the available network bandwidth being reduced, client device 40 may switch to a 5 Mbps representation with switch points approximately every 0.5 seconds. After buffering enough data to avoid underflow, according to aspects of this disclosure, client device 40 may retrieve a 5 Mbps representation with switch points approximately every 2 seconds. This 5 Mbps representation may have a relatively higher perceptual quality (despite being the same bit rate) due to the decreased number of switch points. Upon the available network bandwidth being increased, client device 40 may transition to a 10 Mbps representation with switch points approximately every 0.5 seconds. After buffering enough data of this representation to avoid underflow, client device 40 may again switch to a representation having fewer switch points and an increased perceptual quality (e.g., a 10 Mbps representation with switch points approximately every 3 seconds).
  • a representation having fewer switch points and an increased perceptual quality e.g., a 10 Mbps representation with switch points approximately every 3 seconds.
  • FIG. 7 illustrates switched-to representations having the same bit rates (e.g., a 5 Mbps representation with switch points approximately every 0.5 seconds and a 5 Mbps representation with switch points approximately every 2 seconds; a 10 Mbps representation with switch points approximately every 0.5 seconds and a 10 Mbps representation with switch points approximately every 3 seconds), as noted above, the techniques of this disclosure are not limited in this way.
  • representations may alternate between alternate between representations having relatively frequent switch points and a higher bit rate and representations having less frequent switch points and a lower bit rate.
  • client device 40 may switch from the 5 Mbps representation having switch points approximately every 0.5 seconds to a representation having an even lower bit rate (e.g., 4 Mbps, 3Mbps, or the like), but with the same or higher quality due to a reduced frequency of switch points. Additionally or alternatively, as noted above, client device 40 may consider an amount of data that has been buffered when selecting a representation to switch to. That is, if the amount of data that has been buffered is relatively low, client device 40 may select a representation having relatively frequent switch points. In contrast, if the amount of data that has been buffered is higher, client device may select a representation having less frequent switch points.
  • an even lower bit rate e.g. 4 Mbps, 3Mbps, or the like
  • FIG 8 is a flowchart illustrating an example method according to the techniques described in this disclosure. Although the method of FIG. 8 is described with respect to server device 60 and client device 40, it should be understood that other devices may implement techniques similar to those of the method of FIG. 8 .
  • content preparation device 20, or one or more network devices of a content delivery network may perform some or all of the functions attributed to server device 60.
  • Server device 60 may initially obtain (e.g., create, or receive from content preparation device 20) data for one or more representations of multimedia content, as well as a manifest file for the multimedia content. Server device 60 may also provide indications of representations of multimedia content, e.g., characteristics of the representations to client device 40 (340). In addition, server device 60 may determine switch point intervals for a number of representations having the same, or approximately the same bit rate (342). Server device 60 may provide, for each representation, an indication of the number of switch points included in the representation (344). Alternatively or additionally, server device 60 may provide, for each representation , an indication of the minBufferTime.
  • Client device 40 may determine the intervals between switch points for each received representation based on the received information (346). Client device 40 may also submit a request for a first representation (348). According to some aspects of this disclosure, client device 40 may initially select a representation having a relatively large number of switch points (e.g., and a correspondingly short buffering duration).
  • server device 60 may provide the selected, first representation (350). Client device 40 may then begin buffering, decoding, and/or displaying the received data (352). According to aspects of this disclosure, upon receiving and/or buffering a certain amount of data from the first representation, client device 40 may submit a request for data from a second representation from server device 60.
  • the second representation may have relatively fewer (that is, less frequent) switch points than the first representation (e.g., and a correspondingly longer buffering duration). Moreover, the second representation may be of a higher quality than the first representation.
  • the second representation may have a bit rate that is substantially similar to the bit rate of the first representation, albeit with less frequent switch points (although in other examples the bit rates may be different, as described above). Accordingly, the second representation may achieve higher quality in that the second representation may be coded using relatively more P- and/or B-frames or slices, which may improve coding efficiency due to improved utilization of temporal redundancies within video data of the representation.
  • server device 60 may provide the second representation (356). Client device 40 may then begin buffering, decoding and/or displaying the received data (358). Steps 354-358 may be performed repeatedly, based on network bandwidth conditions.
  • the method of FIG. 8 represents an example of a method including determining a first interval between switch points for a first representation of the multimedia content and a second interval between switch points for a second representation of the multimedia content, wherein the first interval is less than the second interval.
  • the method includes, based on the determination, submitting a network request that specifies an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in the second representation; and after submitting the request for the amount of video data from the first representation, retrieving video data from the second representation.
  • the method of FIG. 8 represents an example of a method including forming a plurality of representations of the multimedia content.
  • the method also includes assigning the representations switch point interval information representative of intervals between switch points for the respective representations, and sending video data of a first one of the representations to a client device in response to a request from the client device.
  • the method also includes after sending an amount of video data from the first representation that has a playback time that is at least equal to a playback time between switch points in a second, different one of the representations, sending video data of the second one of the representations to the client device, wherein the interval between switch points for the second one of the representations is lower than the interval between switch points for the first one of the representations.
  • FIG 9 is a flowchart illustrating an example method according to the techniques described in this disclosure. Although the method of FIG. 9 is described with respect to server device 60 and client device 40, it should be understood that other devices may implement techniques similar to those of the method of FIG. 9 .
  • content preparation device 20, or one or more network devices of a content delivery network may perform some or all of the functions attributed to server device 60.
  • FIG. 9 generally illustrates techniques of this disclosure being performed by a client device, such as client device 40.
  • client device 40 may initially retrieve an MPD that specifies switch point intervals of a plurality of representations (e.g., such as representations of adaptation groups 300 and 308 shown in FIG. 5 ) (380).
  • Client device 40 may then determine an available amount of bandwidth (382). That is, client device 40 may determine an amount of network bandwidth that is currently available for transmission of data from a server device, such as server device 60, to client device 40.
  • client device 40 may identify a first representation with relatively low switch point interval and second representation with relatively high switch point interval.
  • the first and second representations may have approximately the same bit rate that can be satisfied by the available amount of bandwidth.
  • client device 40 may identify an adaptation group having the same, or approximately the same bit rate, but having representations that include different intervals of switch points (e.g., and, therefore, different qualities).
  • client device 40 may identify one or more adaptation groups that include representations having different bit rates. Client device 40 may then identify a first a first representation with relatively low switch point interval and second representation with relatively high switch point interval.
  • Client device 40 may then buffer data from first representation (386), and decode/display data of first representation (388). After buffering a sufficient amount of data of first representation (e.g., buffering an amount that has temporal data equal to or exceeding a temporal sequence between switch points of the second representation), client device 40 may switch to second representation (390). That is, client device 40 may buffer, decode, and display data of the second representation.
  • a sufficient amount of data of first representation e.g., buffering an amount that has temporal data equal to or exceeding a temporal sequence between switch points of the second representation
  • client device 40 may switch to second representation (390). That is, client device 40 may buffer, decode, and display data of the second representation.
  • FIG. 10 is a flowchart illustrating an example method according to the techniques described in this disclosure. Although the method of FIG. 10 is described with respect to server device 60 and client device 40, it should be understood that other devices may implement techniques similar to those of the method of FIG. 10 .
  • content preparation device 20, or one or more network devices of a content delivery network may perform some or all of the functions attributed to server device 60.
  • two or more representations may have the same bit rate but different switch point frequencies (referred to in this example as a target group of representations).
  • client device 40 may initially begin retrieving data of a certain representation at a certain bit rate (400). Client device 40 may then determine that network bandwidth availability has changed (402). In some examples, client device 40 may identify that the ability of the network to support the bit rate of the current representation has changed. For example, the amount of available network bandwidth may have decreased to a point that client device 40 determines that a representation with a lower bit rate that can be accommodated by the newly determined amount of available network bandwidth should be selected. Alternatively, the amount of available network bandwidth may have increased to a point that client device 40 determines that a representation with a higher bit rate should be selected, e.g., to improve playback quality.
  • Client device 40 may then identify a target group of representations, and in particular, a group of representations having the same or substantially the same bit rate, but having at least a first representation and a second representation, where the first representation includes a different frequency of switch points than the second representation (404). In a particular example the first representation may have a higher frequency of switch points than the second representation. Client device 40 may select the target group of representations based on the bit rate, where the bit rate can be satisfied by the newly determined amount of available network bandwidth. In other examples, client device 40 may select a target group of representations having slightly different bit rates that also have different frequencies of switch points.
  • Client device 40 may buffer a sufficient amount of data from a representation of the target group having a relatively high frequency of switch points (e.g., the first representation described above) (406). That is, for example, client device 40 may buffer enough data from the first representation to avoid buffer underflow, while also avoiding the necessity of executing two decoders simultaneously which may consume excess battery and processing power. After buffering a sufficient amount of data of this representation, client device 40 may switch to another one of the target group of representations (e.g., the second representation described above) having a lower frequency of switch points (408).
  • a representation of the target group having a relatively high frequency of switch points e.g., the first representation described above
  • Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol.
  • Computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave.
  • Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementation of the techniques described in this disclosure.
  • a computer program product may include a computer-readable medium.
  • such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • any connection is properly termed a computer-readable medium.
  • a computer-readable medium For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • DSL digital subscriber line
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
  • processors such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable logic arrays
  • processors may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein.
  • the functionality described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements.
  • the techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs (e.g., a chip set).
  • IC integrated circuit
  • a set of ICs e.g., a chip set.
  • Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require realization by different hardware units. Rather, as described above, various units may be combined in a codec hardware unit or provided by a collection of interoperative hardware units, including one or more processors as described above, in conjunction with suitable software and/or firmware.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Information Transfer Between Computers (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Claims (15)

  1. Procédé d'extraction de données vidéo d'un contenu multimédia, le procédé comprenant :
    déterminer (346) un premier intervalle entre des points de commutation pour une première représentation du contenu multimédia et un deuxième intervalle entre des points de commutation pour une deuxième représentation du contenu multimédia, dans lequel le premier intervalle est moindre que le deuxième intervalle;
    sur la base de la détermination, soumettre (348) une ou plusieurs demandes réseau pour une quantité de données vidéo de la première représentation qui a un temps de lecture qui est au moins égal à un temps de lecture entre des points de commutation dans la deuxième représentation; et
    après avoir soumis la demande pour la quantité de données vidéo de la première représentation, extraire (356) des données vidéo de la deuxième représentation.
  2. Procédé selon la revendication 1, comprenant en outre mettre en mémoire tampon des données vidéo de la première représentation, et déterminer quand extraire des données vidéo de la deuxième représentation sur la base d'une durée des données vidéo mises en mémoire tampon.
  3. Procédé selon la revendication 2, dans lequel extraire des données vidéo de la deuxième représentation sur la base d'une durée des données vidéo mises en mémoire tampon comprend extraire des données vidéo de la deuxième représentation après avoir mis en mémoire tampon une durée de données vidéo de la première représentation qui est approximativement égale au temps de lecture entre des points de commutation dans la deuxième représentation.
  4. Procédé selon la revendication 1, comprenant en outre :
    déterminer une quantité actuellement disponible de largeur de bande réseau;
    recevoir un manifeste pour le contenu multimédia qui indique que la première représentation et la deuxième représentation ont un débit binaire commun; et
    sélectionner la première représentation et la deuxième représentation après avoir déterminé que le débit binaire commun peut être satisfait par la quantité actuellement disponible de largeur de bande réseau.
  5. Procédé selon la revendication 1, comprenant en outre :
    déterminer une quantité actuellement disponible de largeur de bande réseau;
    recevoir un manifeste pour le contenu multimédia qui indique que la première représentation a un premier débit binaire et que la deuxième représentation a un deuxième débit binaire qui est plus élevé que le premier débit binaire; et
    déterminer si le deuxième débit binaire peut être satisfait par la quantité actuellement disponible de largeur de bande réseau,
    dans lequel demander les données vidéo de la première représentation comprend demander les données vidéo de la première représentation après avoir déterminé que le deuxième débit binaire peut être satisfait par la quantité actuellement disponible de largeur de bande réseau, et
    dans lequel recevoir les données vidéo de la deuxième représentation après avoir demandé les données vidéo de la première représentation comprend extraire les données vidéo de la deuxième représentation après avoir déterminé que le deuxième débit binaire peut être satisfait par la quantité actuellement disponible de largeur de bande réseau.
  6. Procédé selon la revendication 1, dans lequel demander les données vidéo de la première représentation comprend :
    envoyer une ou plusieurs demandes à un dispositif serveur pour les données vidéo de la première représentation; et
    recevoir les donnée vidéo de la première représentation par une diffusion point à point, et
    dans lequel extraire les données vidéo de la deuxième représentation comprend extraire les données vidéo par au moins l'une d'entre une diffusion multipoint ou une diffusion générale du dispositif serveur.
  7. Procédé selon la revendication 1, comprenant en outre recevoir un fichier de manifeste pour le contenu multimédia, dans lequel déterminer le premier intervalle comprend déterminer le premier intervalle à partir d'informations dans le fichier de manifeste, et dans lequel déterminer le deuxième intervalle comprend déterminer le deuxième intervalle à partir d'informations dans le fichier manifeste.
  8. Procédé selon la revendication 1, dans lequel la première représentation et la deuxième représentation ont un débit binaire commun, le procédé comprenant en outre :
    avant de déterminer le premier intervalle et le deuxième intervalle, extraire des données vidéo d'une troisième représentation différente ayant un débit binaire différent du débit binaire commun;
    déterminer une quantité actuellement disponible de largeur de bande réseau; et
    sur la base d'une détermination que le débit binaire commun de la première représentation et de la deuxième représentation convient mieux à la quantité actuellement disponible de largeur de bande réseau, déterminer le premier intervalle et le deuxième intervalle, soumettre l'une ou les plusieurs demandes réseau pour les données vidéo de la première représentation, et extraire les données vidéo de la deuxième représentation.
  9. Appareil pour extraire des données vidéo d'un contenu multimédia, l'appareil comprenant :
    un moyen pour déterminer un premier intervalle entre des points de commutation pour une première représentation du contenu multimédia et un deuxième intervalle entre des points de commutation pour une deuxième représentation du contenu multimédia, dans lequel le premier intervalle est moindre que le deuxième intervalle;
    sur la base de la détermination, un moyen pour soumettre une ou plusieurs demandes réseau pour une quantité de données vidéo de la première représentation qui a un temps de lecture qui est au moins égal à un temps de lecture entre des points de commutation dans la deuxième représentation; et
    après avoir soumis la demande pour une quantité de données vidéo de la première représentation, un moyen pour extraire des données vidéo de la deuxième représentation.
  10. Appareil selon la revendication 9, comprenant en outre un moyen pour mettre en mémoire tampon des données vidéo de la première représentation, et un moyen pour déterminer quand extraire des données vidéo de la deuxième représentation sur la base d'une durée des données vidéo mises en mémoire tampon.
  11. Appareil selon la revendication 10, dans lequel un moyen pour extraire des données vidéo de la deuxième représentation sur la base d'une durée des données vidéo mises en mémoire tampon comprend un moyen pour extraire des données vidéo de la deuxième représentation après avoir mis en mémoire tampon une durée de données vidéo de la première représentation qui est approximativement égale au temps de lecture entre des points de commutation dans la deuxième représentation.
  12. Appareil selon la revendication 9, comprenant en outre :
    un moyen pour déterminer une quantité actuellement disponible de largeur de bande réseau;
    un moyen pour recevoir un manifeste pour le contenu multimédia qui indique que la première représentation et la deuxième représentation ont un débit binaire commun; et
    un moyen pour sélectionner la première représentation et la deuxième représentation après avoir déterminé que le débit binaire commun peut être satisfait par la quantité actuellement disponible de largeur de bande réseau.
  13. Procédé de diffusion en continu de données vidéo d'un contenu multimédia, le procédé comprenant :
    recevoir une pluralité de représentations du contenu multimédia, dans lequel les représentations comprennent des informations d'intervalles de points de commutation représentatives des intervalles entre des points de commutation pour les représentations respectives;
    envoyer des données vidéo d'une première des représentations à un dispositif client en réponse à une demande du dispositif client; et
    après avoir envoyé une quantité de données vidéo de la première des représentations qui a un temps de lecture qui est au moins égal à un temps de lecture entre des points de commutation dans une deuxième représentation différente des représentations, envoyer des données vidéo de la deuxième des représentations au dispositif client, dans lequel l'intervalle entre des points de commutation pour la deuxième des représentations est moindre que l'intervalle entre des points de commutation pour la première des représentations.
  14. Appareil pour diffuser en continu de données vidéo d'un contenu multimédia, l'appareil comprenant :
    un moyen pour recevoir une pluralité de représentations du contenu multimédia, dans lequel les représentations comprennent des informations d'intervalles de points de commutation représentatives des intervalles entre des points de commutation pour les représentations respectives;
    un moyen pour envoyer des données vidéo d'une première des représentations à un dispositif client en réponse à une demande du dispositif client; et
    après avoir envoyé une quantité de données vidéo de la première représentation qui a un temps de lecture qui est au moins égal à un temps de lecture entre des points de commutation dans une deuxième représentation différente des représentations, un moyen pour envoyer des données vidéo de la deuxième des représentations au dispositif client, dans lequel l'intervalle entre des points de commutation pour la deuxième des représentations est moindre que l'intervalle entre des points de commutation pour la première des représentations.
  15. Support de stockage non transitoire lisible par ordinateur stockant des instructions qui, lorsque exécutées, font qu'un ou plusieurs processeurs mettent en ouvre le procédé selon l'une quelconque des revendications 1 à 8.
EP12783731.8A 2011-10-05 2012-10-05 Commutation entre des représentations durant une diffusion en continu de réseau de données multimédias codées Active EP2764674B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201161543732P 2011-10-05 2011-10-05
US13/644,373 US8935425B2 (en) 2011-10-05 2012-10-04 Switching between representations during network streaming of coded multimedia data
PCT/US2012/058913 WO2013052774A1 (fr) 2011-10-05 2012-10-05 Commutation entre des représentations durant une diffusion en continu de réseau de données multimédias codées

Publications (2)

Publication Number Publication Date
EP2764674A1 EP2764674A1 (fr) 2014-08-13
EP2764674B1 true EP2764674B1 (fr) 2015-11-25

Family

ID=48042858

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12783731.8A Active EP2764674B1 (fr) 2011-10-05 2012-10-05 Commutation entre des représentations durant une diffusion en continu de réseau de données multimédias codées

Country Status (6)

Country Link
US (1) US8935425B2 (fr)
EP (1) EP2764674B1 (fr)
JP (2) JP2014534684A (fr)
KR (1) KR101558116B1 (fr)
CN (1) CN103843301B (fr)
WO (1) WO2013052774A1 (fr)

Families Citing this family (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130227162A1 (en) * 2012-02-29 2013-08-29 F-Secure Corporation Management of Data Upload Speed
US9674247B1 (en) * 2012-06-21 2017-06-06 Google Inc. Generating manifest files for digital media items
CN104429093B (zh) * 2012-07-09 2018-01-05 华为技术有限公司 超文本传输协议动态自适应流媒体客户端及其会话管理实施方法
US9357239B2 (en) * 2012-11-16 2016-05-31 Adobe Systems Incorporated Converting live streaming content to video-on-demand streaming content
US9813325B2 (en) * 2012-12-27 2017-11-07 Comcast Cable Communications, Llc Information stream management
GB2512310A (en) * 2013-03-25 2014-10-01 Sony Corp Media Distribution
KR102241672B1 (ko) 2013-04-30 2021-04-16 소니 주식회사 송신 장치, 송신 방법, 수신 장치 및 수신 방법
FR3007615A1 (fr) * 2013-06-24 2014-12-26 France Telecom Procede d'amelioration du temps de changement entre programmes audiovisuels
CN105379294A (zh) * 2013-07-15 2016-03-02 华为技术有限公司 基于超文本传输协议的动态自适应流媒体中的远程元素的即时性间接引用
US9270721B2 (en) * 2013-10-08 2016-02-23 Qualcomm Incorporated Switching between adaptation sets during media streaming
RU2016121189A (ru) * 2013-11-25 2018-01-09 Лэ Ши Чжи Синь Электроник Технолоджи (Тяньцзинь) Лимитэд Способ воспроизведения видео, устройство и интеллектуальный терминал
KR101600469B1 (ko) * 2014-07-16 2016-03-07 김재경 스트리밍 서비스를 위한 클라이언트 및 서버의 동작 방법
US9794601B2 (en) * 2014-10-21 2017-10-17 Cisco Technology, Inc. Dynamic programming across multiple streams
WO2016093752A1 (fr) * 2014-12-10 2016-06-16 Telefonaktiebolaget Lm Ericsson (Publ) Accès au flux pour une diffusion en flux adaptative de vidéos
US10270823B2 (en) * 2015-02-10 2019-04-23 Qualcomm Incorporated Low latency video streaming
GB2536887B (en) * 2015-03-27 2021-05-05 Sony Europe Bv Video content replay
US10567816B2 (en) 2015-04-30 2020-02-18 Comcast Cable Communications, Llc Delivering content
US10652630B2 (en) * 2016-05-24 2020-05-12 Qualcomm Incorporated Sample entries and random access
US20180146019A1 (en) * 2016-11-21 2018-05-24 International Business Machines Corporation Light-weight resolution switching for online video streaming
WO2018115267A1 (fr) * 2016-12-22 2018-06-28 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Diffusion en continu de contenu multimédia avec accord rapide et commutation de canal rapide
WO2018146376A1 (fr) * 2017-02-13 2018-08-16 Nokia Technologies Oy Appareil, procédé et programme informatique de codage et de décodage vidéo
GB2563387B (en) * 2017-06-09 2020-04-15 Sony Interactive Entertainment Inc Image processing device and system
US10652166B2 (en) * 2017-06-27 2020-05-12 Cisco Technology, Inc. Non-real time adaptive bitrate recording scheduler
CN107480181B (zh) * 2017-07-05 2020-11-24 百度在线网络技术(北京)有限公司 音频播放方法、装置、设备及服务器
US10587904B2 (en) * 2017-07-10 2020-03-10 Qualcomm Incorporated Processing media data using an omnidirectional media format
US20190166170A1 (en) * 2017-11-29 2019-05-30 Comcast Cable Communications, Llc Video Streaming Delivery
US10805658B2 (en) * 2018-09-12 2020-10-13 Roku, Inc. Adaptive switching in a whole home entertainment system
US20200112753A1 (en) * 2018-10-03 2020-04-09 Qualcomm Incorporated Service description for streaming media data
CN109168020A (zh) * 2018-10-22 2019-01-08 广州虎牙科技有限公司 基于直播的视频处理方法、装置、计算设备和存储介质
CN113424549B (zh) * 2019-01-24 2024-05-28 交互数字Vc控股公司 用于利用多个细节级别和自由度的自适应空间内容流传输的系统和方法
JP7324012B2 (ja) * 2019-02-07 2023-08-09 日本放送協会 受信装置、及びプログラム
US11838452B2 (en) * 2019-08-19 2023-12-05 Nippon Telegraph And Telephone Corporation Control apparatus, control method and program
US11489899B1 (en) 2021-04-12 2022-11-01 Comcast Cable Communications, Llc Segment ladder transitioning in adaptive streaming
US11418851B1 (en) * 2021-06-28 2022-08-16 Synamedia Limited Virtual set top
US11627345B1 (en) * 2022-05-10 2023-04-11 Dish Network Technologies India Private Limited Buffer management for optimized processing in media pipeline
US20240196049A1 (en) * 2022-12-08 2024-06-13 Synamedia Limited Client Device Switching to Low Latency Content

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7885340B2 (en) 1999-04-27 2011-02-08 Realnetworks, Inc. System and method for generating multiple synchronized encoded representations of media data
EP1359722A1 (fr) * 2002-03-27 2003-11-05 BRITISH TELECOMMUNICATIONS public limited company Système et procédé pour transmettre des flux de données
DE60208474T2 (de) * 2002-08-27 2006-07-13 Matsushita Electric Industrial Co., Ltd., Kadoma Verfahren zur Übertragung von Datenströmen abhängig vom überwachten Zustand des Anwendungsspeichers des Nutzers
JP2004297117A (ja) * 2003-03-25 2004-10-21 Kyocera Corp 無線通信システム、無線通信システムにおける無線端末、動画像データ配信サーバ、および無線通信方法
CN101061718B (zh) * 2004-11-22 2010-10-13 汤姆森研究基金有限公司 用于数字订户线路系统中的频道改变的方法和设备
ES2313323T3 (es) * 2005-04-11 2009-03-01 Telefonaktiebolaget Lm Ericsson (Publ) Tecnica para controlar transmisiones de paquetes de datos de velocidad binaria variable.
US7793329B2 (en) 2006-02-06 2010-09-07 Kasenna, Inc. Method and system for reducing switching delays between digital video feeds using multicast slotted transmission technique
US8311102B2 (en) * 2006-07-26 2012-11-13 Microsoft Corporation Bitstream switching in multiple bit-rate video streaming environments
EP2124454B1 (fr) 2007-03-19 2014-11-19 Fujitsu Limited Procédé de conversion de train de bits, dispositif de conversion de train de bits, dispositif de couplage de train de bits, programme de division de train de bits, programme de conversion de train de bits et programme de couplage de train de bits
JP2009170985A (ja) * 2008-01-11 2009-07-30 Hitachi Ltd オンデマンドデータ配信システム
TWI373942B (en) 2008-01-11 2012-10-01 Quanta Comp Inc Home networking system and admission control method thereof
US8700792B2 (en) 2008-01-31 2014-04-15 General Instrument Corporation Method and apparatus for expediting delivery of programming content over a broadband network
WO2010008416A1 (fr) 2008-07-16 2010-01-21 Thomson Licensing Procédé de codage vidéo échelonnable pour changement de canal rapide afin d'augmenter le rendement de codage
JP5151763B2 (ja) * 2008-07-22 2013-02-27 日本電気株式会社 映像配信システム、映像配信装置、映像受信装置、映像配信方法、映像受信方法及びプログラム
US20100138876A1 (en) 2008-12-01 2010-06-03 At&T Intellectual Property I, L.P. System and method to transmit media content
US8279926B2 (en) 2009-06-18 2012-10-02 Cisco Technology, Inc. Dynamic streaming with latticed representations of video
US8848548B2 (en) 2009-08-04 2014-09-30 Qualcomm Incorporated Internet radio broadcast using cellular
US8355433B2 (en) 2009-08-18 2013-01-15 Netflix, Inc. Encoding video streams for adaptive video streaming
EP2545706A4 (fr) * 2010-03-08 2013-09-11 Samsung Electronics Co Ltd Appareil et procédé pour lire des données de contenu multimédia
US8689267B2 (en) * 2010-12-06 2014-04-01 Netflix, Inc. Variable bit video streams for adaptive streaming
US9026671B2 (en) * 2011-04-05 2015-05-05 Qualcomm Incorporated IP broadcast streaming services distribution using file delivery methods

Also Published As

Publication number Publication date
EP2764674A1 (fr) 2014-08-13
KR20140072183A (ko) 2014-06-12
US8935425B2 (en) 2015-01-13
WO2013052774A1 (fr) 2013-04-11
KR101558116B1 (ko) 2015-10-06
CN103843301A (zh) 2014-06-04
JP2014534684A (ja) 2014-12-18
JP2016154348A (ja) 2016-08-25
US20130091297A1 (en) 2013-04-11
CN103843301B (zh) 2016-09-28

Similar Documents

Publication Publication Date Title
EP2764674B1 (fr) Commutation entre des représentations durant une diffusion en continu de réseau de données multimédias codées
US9900363B2 (en) Network streaming of coded video data
US9270721B2 (en) Switching between adaptation sets during media streaming
US10270823B2 (en) Low latency video streaming
US9456015B2 (en) Representation groups for network streaming of coded multimedia data
EP2594073B1 (fr) Commutation vidéo pour données vidéo en continu
EP2880836B1 (fr) Remplacement de données multimédias perdues pour diffusion en flux de réseau
EP3466095B1 (fr) Entrées d'échantillons et accès aléatoire
US20150312303A1 (en) Determining whether to use sidx information when streaming media data
US20150095450A1 (en) Utilizing multiple switchable adaptation sets for streaming media data
EP3466096B1 (fr) Entrées d'échantillons et accès aléatoire

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140414

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20150505

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 763082

Country of ref document: AT

Kind code of ref document: T

Effective date: 20151215

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602012012747

Country of ref document: DE

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20160225

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 763082

Country of ref document: AT

Kind code of ref document: T

Effective date: 20151125

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160325

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160226

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160325

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012012747

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20160826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20170630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20161102

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20161031

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20161031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20161005

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20161005

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20121005

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20161031

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151125

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602012012747

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0065000000

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230914

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230915

Year of fee payment: 12