One or more embodiments relate generally to obtaining content and, in particular, to delivery of video content using dynamic adaptive hypertext transport protocol (HTTP) streaming (DASH) without using HTTP in a broadcast network.
Transmission Control Protocol (TCP) has been considered as unsuitable for the delivery of real-time media, such as audio and video content. This is mainly due to the aggressive congestion control algorithm and the retransmission procedure that TCP implements. In TCP, the sender reduces the transmission rate significantly (e.g., by 50%) upon detection of a congestion event, typically recognized through packet loss or excessive transmission delays.
Hypertext Transport Protocol (HTTP) is a preferred protocol for the delivery of multimedia content over the Internet. HTTP runs on top of TCP and is a textual protocol.
Dynamic Adaptive HTTP Streaming (DASH) has been standardized by the 3rd Generation Partnership Project (3GPP) and Motion Pictures Expert Group (MPEG). Several other proprietary solutions for adaptive HTTP streaming, such as APPLE's HTTP Live Streaming (HLS) and MICROSOFT's Smooth Streaming, are being commercially deployed. Unlike those, however, DASH is a fully-open and standardized media streaming solution, which drives inter-operability among different implementations.
In one embodiment, a method provides for content delivery using dynamic adaptive hypertext transport protocol (HTTP) streaming (DASH) without using HTTP. One embodiment includes receiving a media presentation description (MPD) file and one or more DASH segments by a client device. In one embodiment, information in the MPD file is used to filter the one or more DASH segments. The filtered DASH segments are stored in a segments buffer. In one embodiment, particular DASH segments are requested from the segments buffer by the client device based on the information.
One embodiment provides a client device for content delivery using DASH without using HTTP. The client device includes a segments buffer and a DASH processing component that receives a MPD file and one or more DASH segments. The DASH processing component further filters the one or more DASH segments using information from the MPD file, stores the filtered one or more DASH segments in the segments buffer and requests one or more particular DASH segments from the segments buffer based on the information for presenting content.
Another embodiment provides a non-transitory computer-readable medium having instructions which when executed on a computer perform a method for content delivery using DASH without using HTTP. In one embodiment, the method comprises receiving an MPD file and one or more DASH segments by a client device. In one embodiment, information in the MPD file is used to filter the one or more DASH segments. In one embodiment, the filtered one or more DASH segments are stored in a segments buffer. In one embodiment, one or more particular DASH segments are requested from the segments buffer by the client device based on the information.
These and other aspects and advantages of the embodiments will become apparent from the following detailed description, which, when taken in conjunction with the drawings, illustrate by way of example the principles of the embodiments.
For a fuller understanding of the nature and advantages of the embodiments, as well as a preferred mode of use, reference should be made to the following detailed description read in conjunction with the accompanying drawings, in which:
The following description is made for the purpose of illustrating the general principles of the embodiments and is not meant to limit the inventive concepts claimed herein. Further, particular features described herein can be used in combination with other described features in each of the various possible combinations and permutations. Unless otherwise specifically defined herein, all terms are to be given their broadest possible interpretation including meanings implied from the specification as well as meanings understood by those skilled in the art and/or as defined in dictionaries, treatises, etc.
One or more embodiments relate generally to delivery of video content using dynamic adaptive hypertext transport protocol (HTTP) streaming (DASH) with the content segments delivered over MMTP instead of HTTP in a broadcast network. In one embodiment, a method includes receiving a media presentation description (MPD) file and one or more DASH segments by a client device. In one embodiment, information in the MPD file is used to filter the one or more DASH segments. The filtered DASH segments are stored in a segments buffer. In one embodiment, particular DASH segments are requested from the segments buffer by the client device based on the information.
One embodiment provides a client device for content delivery using DASH without using HTTP. The client device includes a segments buffer and a DASH processing component that receives a MPD file and one or more DASH segments. The DASH processing component further filters the one or more DASH segments using information from the MPD file, stores the filtered one or more DASH segments in the segments buffer and requests one or more particular DASH segments from the segments buffer based on the information for presenting content.
One or more embodiments employ DASH for broadcast without HTTP. In one embodiment, the client devices are not HTTP client devices and a broadcast system does not employ an HTTP server. In one embodiment, a broadcast server delivers an MPD file MPD and DASH segments to the broadcast client. The broadcast client delivers the DASH segments to a broadcast DASH buffer. In one embodiment, the MPD file is used to filter DASH segments (e.g., based on uniform resource locator (URL)). In one embodiment, the broadcast DASH buffer stores the DASH segments with the associated URL. The broadcast DASH client device finds segments based on the URL in the broadcast DASH buffer. In one embodiment, if a DASH segment at the desired quality level is not found, the DASH segment at the next lower quality level may be found (if available) by modifying the URL as per the DASH specification.
DASH refers to a typical scheme of adaptive streaming, which changes server-controlled adaptive streaming to client-controlled adaptive streaming. In server-controlled adaptive streaming, a server device has information about its connections to all connected client devices and generates what each client requires, for transmitting optimal content for each network situation. The server device, however, may become overloaded as the client devices increase in number. In DASH, the server device generates media segments and metadata in advance for several possible cases, and the client devices request and play content depending on the situation. This makes it possible to download and play the optimal content depending on the network conditions while reducing the load placed on the server device.
Examples of content may include audio information, video information, audio-video information, and data. Content items may include multiple components, such as audio information, video information, and subtitle information. For example, a component may be a subtitle stream composed in a particular language or a video stream obtained at a certain camera angle. The component may include a track, an elementary stream (ES), etc., depending on its container. Content resources refer to content items (such as various qualities, bit rates, and angles) that are provided in multiple representations to enable adaptive streaming for content items. A service discovery process may be referred to as content resources. The content resources may include one or more consecutive time periods, which comprise a temporal section of content resources.
Representations refer to versions (for all or some components) of content resources in a period. Representations may be different in a subset of components or in encoding parameters (such as bit rate) for components. Although representations are referred to as media data, they may also be referred to as any such terms indicating data, including one or more components, without being limited thereto. A segment or DASH segment refers to a temporal section of representations, which is named by a unique URL in a particular system layer type (such as Transport Stream (TS) or Moving Picture Experts Group (MPEG)-4 (MP4) Part 14).
In one embodiment, the client device 100 includes a processor 105, a communications unit 110, one or more speakers 115, a bus system 120, an input/output (I/O) unit 125, a display 130, and a memory 135. The client device 100 may also include one or more microphones 140. In one embodiment, the communications unit 110 may include a wireless communications unit 145. The memory 135 includes an operating system (OS) program 150 and at least one multimedia program 155. In one embodiment, the client device may include one or more sensors, such as lighting sensors, temperature sensors, locating sensors (e.g., global positioning system (GPS), one or more cameras, etc.
In one embodiment, the communications unit 110 provides for communications with other systems or devices over a network. For example, the communications unit 110 may include a network interface card or a wireless transceiver. The communications unit 110 may provide communications through wired, optical, wireless, or other communication links to a network.
In one or more embodiments, the client device 100 is capable of receiving information over a wireless network. For example, the communications unit 110 may include the wireless communications unit 145. The wireless communications unit 145 may include an antenna, radio frequency (RF) transceiver, and processing circuitry. The RF transceiver may receive via the antenna an incoming RF signal transmitted by a base station, eNodeB, or access point of a wireless network. The RF transceiver down-converts the incoming RF signal to produce an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to receiver (RX) processing circuitry, which produces a processed baseband signal by filtering, digitizing, demodulation, and/or decoding operations. The RX processing circuitry transmits the processed baseband signal to the speaker(s) 115 (such as for audio data) or to the processor 105 for further processing (such as for video data and audio data processing).
The wireless communications unit 145 may also include transmitter (TX) processing circuitry that receives analog or digital voice data from the microphone(s) 140 or other outgoing baseband data (such as web data, e-mail, or generated location information) from the processor 105. The transmitter processing circuitry may encode, modulate, multiplex, and/or digitize the outgoing baseband data to produce a processed baseband or IF signal. The RF transceiver may receive the outgoing baseband or intermediate frequency (IF) signal from the transmitter processing circuitry and up-convert the baseband or IF signal to an RF signal that is transmitted via the antenna.
The processor 105 processes instructions that may be loaded into the memory 135. The processor 105 may include a number of processors, a multi-processor core, or other type(s) of processing device(s) depending on the particular implementation. In some embodiments, the processor 105 may be or include one or more graphics processors for processing and rendering graphical and/or video data for presentation by the display 130. In one or more embodiments, the processor 105 may comprise a microprocessor or microcontroller. In one embodiment, the memory 135 is connected to the processor 105. Part of the memory 135 may include a random access memory (RAM), and another part of the memory 135 may include a non-volatile memory such as a Flash memory, an optical disk, a rewritable magnetic tape, or any other type of persistent storage.
In one embodiment, the processor 105 executes the OS program 150 stored in the memory 135 in order to control the overall operation of the client device 100. In one or more embodiments, the processor 105 controls the reception of forward channel signals and the transmission of reverse channel signals by the wireless communications unit 145.
In one embodiment, the processor 105 is capable of executing other processes and programs resident in the memory 135, such as the multimedia program 155. The processor 105 may move data into or out of the memory 135 as required by an executing process. The processor 105 is also connected to the I/O interface 125. The I/O interface 125 provides for input and output of data using other devices that may be connected to the client device 100. For example, the I/O unit 125 may provide a connection for user input through a keyboard, a mouse, voice control, remote control, or other suitable input device. The I/O unit 125 may also send output to a display, printer, or other suitable output device.
The display 130 provides a mechanism to visually present information to a user. In one embodiment, the display 130 may be a liquid crystal display (LCD), light emitting diode (LED), organic LED (OLED) or other display capable of rendering text and/or graphics. The display 130 may also be one or more display lights indicating information to a user. In one or more embodiments, the display 130 is a touch screen that allows user inputs to be received and interpreted by the client device 100. The multimedia program 155 is stored in the memory 135 and executable by the processor 105.
Server computers 210-215 and client devices 220-235 connect to the network 205. Each of the client devices 220-235 may, for example, represent the client device 100 in
In one or more embodiments, the network 205 includes a wireless network of base stations, eNodeBs, access points, or other components that provide wireless broadband access to the network 205 and the client devices 220-235 within a wireless coverage area. In one or more embodiments, base stations or eNodeBs in the network 205 may communicate with each other and with the client devices 220-235 using orthogonal frequency-division multiplexing (OFDM) or OFDM access (OFDMA) techniques.
In one embodiment, the client devices 220-235 receive streamed multimedia content from the multimedia streaming server 210. In one or more embodiments, the client devices 220-235 receive the multimedia content using DASH segments delivered through MMTP. In other embodiments, the client devices 220-235 may receive multimedia content using the real-time streaming protocol (RTSP), the real-time transport protocol (RTP), the HTTP adaptive streaming (HAS) protocol, the HTTP live streaming (HLS) protocol, smooth streaming, and/or other type of standard for streaming content over a network.
It should be noted that the illustrations of the client device 100 in
When streaming a DASH presentation, e.g. over a broadcast channel, the HTTP protocol can no longer be used. MMTP provides the necessary tools to support the delivery of a DASH presentation. A DASH presentation consists of the presentation information, which is the MPD and the data segments (initialization and media segments). The MPD makes the core part of the presentation information of the presentation. The MPD is assigned its own multi-purpose Internet mail extensions (MIME) type: “application/dash+xml”, which is used to identify the type of the presentation. The MPD is embedded in a message passing interface (MPI) table, which in turn is delivered using an MPI message. The format of the message may either be binary or XML. In case of XML format, the MPD is embedded using the <![CDATA[ ]]>(e.g., marked for the parser to interpret as only character data, not markup data) encapsulation. The MPD updates are delivered using the same mechanism. The updates are discovered by checking for the table identifier in signaling messages of that particular package. The MPD is then used by the client (DASH client) to drive the presentation. It is required that all segments that are addressed by the MPD shall be readily available at the receiver side, i.e., delivered and recovered by their segment availability start time. This may be ensured by setting delivery schedule and hypothetical receiver buffer model (HRBM) parameters appropriately.
Referring to
The adaptation set 406 may enable features like multiple language support for audio. Each adaptation set 406 contains multiple representations 408, each a single stream in the adaptive streaming experience. In one example, a first representation 408 may provide 640×480@500 Kbps, while a second representation 408 may provide 640×480@250 Kbps. Each representation 408 is divided into media segments, essentially the chunks of data that all HTTP-based adaptive streaming technologies use. Data chunks can be presented in discrete files, as in HTTP live streaming (HLS), or as byte ranges in a single media file. Presentation in a single file helps improve file administration and caching efficiency as compared to chunked technologies that can create hundreds of thousands of files for a single audio/video event.
The client device may continue to add complementary representations 408 that contain additional media components. The content offered for DASH streaming may be described to the client device. This may be done using the MPD file 400. The MPD file 400 is an extensible markup language (XML) file that contains a description of the content, the periods 404 of the content, the adaptation sets 406, the representations 408 of the content, and how to access each piece of the content. An MPD element is the main element in the MPD file 400, as it contains general information about the content, such as its type and the time window during which the content is available.
The one or more periods 404 each describes a time segment of the content. Each period 404 may contain one or more representations 408 of the content grouped into one or more adaptation sets 406. Each representation 408 is an encoding of one or more content components with a specific configuration. Representations 408 differ mainly in their bandwidth requirements, the media components they contain, the codecs in use, the languages, or the like. The MPD file 400 identifies the various content components and the location of all alternative streams. This enables a DASH player (e.g., a client device 100,
When delivering DASH content using the musical instruments digital interface (MIDI) processing unit (MPU) mode, each representation 408 is considered as an MPU. It is important to note that the concatenation of all segments of a representation 408 results in a fragmented ISOBMFF compatible file, which is equivalent to an MPU in MMTP terms. The initialization segment of a representation 408 is the MPU metadata and is marked appropriately during the delivery to ensure that it is recovered by the client device/receiver. The MPU metadata has to be delivered repetitively to ensure that all client devices, independent of the time they join the session will ultimately be able to recover it. The MPU mode provides the means for marking these important packets by setting a format table (FT) field to MPU metadata. Similarly, fragment metadata is important for every fragment and should also be delivered repetitively to increase the probability of recovery.
All segments of a representation 408 are then marked as belonging to the same MPU by using the same packet_id and MPU sequence number to mark them. The mapping between the representation 408 and the packet_id and MPU sequence number is provided by the Identifier_mapping syntax element that is provided in a media presentation (MP) table. One usage of the identifier_mapping is to provide the representation_id as provided in the MPD. Other approaches, e.g. using the URL template for all segments of that Representation may be used instead.
At the sender side, the data is delivered on movie fragment basis. At the receiver side (e.g., client device), each media segment needs to be recovered appropriately and timely. It is then necessary for the receiver to be able to identify the segment boundaries and the segment information. For example, a segment is recovered by identifying its boundaries using the presence of the segment index box (“sidx”) from the current and the following segment; a segment is recovered by checking the timestamp of the first sample in the movie fragment (for example extracted from the “tfdt” box or the “sidx” box) and using the MPD to identify the media segment that has the same starting time; or the segment boundary may be determined from the segment duration by dividing the fragment start time by the duration of the media segment for that representation 408.
In DASH, the client device is fully responsible for the media session and controls the rate adaptation by deciding on which representation 408 (
When using a generic file delivery (GFD) mode in DASH, each segment of the DASH representation 408 (
In one embodiment, different bit rates are provided for dealing with network congestion, e.g. the bit rate is reduced as the segments buffer 610 becomes filled. In one example, network congestion may not be a problem encountered, but signal strength and impairments may provide a problem. In this case, a more robust signal may be chosen with more forward error correction (FEC) bits and less data bits. In one example using an embodiment, two services are simulcast: one service for a fixed TV and another service for a mobile TV. The fixed TV service is of a higher data rate than the mobile TV service, which has a higher level of robustness implemented by sending additional FEC bits.
In one embodiment, the MMTP packet filter 805 receives MMTP packets from the broadcast network (e.g., one-way broadcast network) and delivers them to the appropriate processing block, either the MMTP signal message parser 810 or the FEC decoding buffer 820. In one embodiment, the MMTP packet filter 805 performs the following checks depending on the packet_id of each MMTP packets. When the DASH client device 605 is tuned into the specific service, then the MMTP packet filter 805 is only given the packet_id of MMTP signaling messages by the processing block (not shown). After the MPT_message is processed by the MMTP signal message parser 810, the MMTP packet filter 805 is given the packet_id of media component and starts to filter MMTP packets with a media component.
In one embodiment, the MMTP signal message parser 810 receives MMTP packets from the MMTP packet filter 805 and parses the MMTP signaling message carried in the packet. Information retrieved from the MMTP signaling message is delivered to the appropriate processing blocks. In one embodiment, when the DASH client device 605 is tuned into the specific service, the MMTP signal message parser 810 firstly looks for the MPT_message and processes it to obtain the list of MMT assets and their packet_ids. Whenever an MPI_message is received, the MMTP message parser 810 processes the PI_content_type_byte field of MPI_table( ) and then delivers the data carried as PI_content_byte of MPI_table( ) to either the MPEG-H CI parser 835, the MPD parser 840 or the presentation engine 870. In one embodiment, if the value of PI_content_type_byte is HTML5, then the contained data is delivered to the presentation engine 870. If the value of the PI_content_type_byte is MPEG-H CI then the contained data is delivered to the MPEG-H CI parser 835. If the value of the PI_content_type_byte is DASH MPD, then the contained data is delivered to the (DASH) MPD parser 840.
In one embodiment, whenever an AL_FEC message is received, the information in the message is signaled to the FEC decoding buffer 820. Whenever an HRBM message is received, the information in the message is signaled to the De-jitter buffer 825. In one embodiment, the MPEG-H CI parser 835 receives MPEG-H CI from the MMTP signal message parser 810 and processes it. The presentation time of the first access unit of the MPU is known from the ‘MediaSync’ element referencing such MPU and is delivered to the presentation engine 870. The presentation time of the first access unit of the first segment described by the DASH MPD is also known from the ‘MediaSync’ elements referencing the relevant DASH MPD file and is delivered to the presentation engine 870.
In one embodiment, the (DASH) MPD parser 840 receives the DASH MPD through the MMTP signal message parser 810 and processes it. The (DASH) MPD parser 840 provides relative presentation time of each DASH segment to the presentation engine 870. In one embodiment, the FEC decoding buffer 820 receives MMTP packets with dedicated packet_id and immediately copies packets to the De-jitter buffer 825. If there are any packets which are not received until the protection window time of an AL_FEC message signaled by the MMTP signal message parser 810, a repair operation is applied to the received packets. If packets are recovered they are also immediately copied to the De-jitter buffer 825.
In one embodiment, the De-jitter buffer 825 receives MMTP packets from the FEC decoding buffer 820. The De-jitter buffer 825 stores those packets until the fixed_end_to_end_delay provided by the HRBM message has passed since the time specified in the time_stamp field of each MMTP packet and copies them to the MMTP De-capsulation buffer 830. In one embodiment, the MMTP De-capsulation buffer 830 depacketizes MMTP packets received from the De-jitter buffer 825 and reconstructs the MPUs. Reconstructed MPUs are delivered to the media engines 860.
In one embodiment, the HTTP engine 850 makes GET requests with the URL received from the MPD parser 840 through the broadband network and receives DASH segments as responses. Received DASH segments are delivered to the DASH segments buffer 610.
In one embodiment, the DASH segments buffer 610 receives DASH segments from the HTTP engine 850 and delivers them to media engines 860 as soon as the processing of previously delivered DASH segments are finished. In one embodiment, the media engines 860 receive MPUs and DASH segments and decodes them with appropriate decoders. The media engines 860 delivers decoded results to the presentation engine 870. In one embodiment, the presentation engine 870 receives the HTML 5 document from the MMTP signal message parser 810. The presentation engine 870 renders media data from the media engines 860 in the location specified by the HTML 5 document and at the time provided by the MPEG-H CI parser 835 and the MPD parser 840.
In one embodiment, in block 905 the URL and DASH segment are extracted from the MPU. In block 906, the URL and DASH segment are extracted using GFD transmission (GFDT). In one embodiment, in block 907, the extracted segment and associated URL are stored together in the (DASH) segments buffer. In block 908, it is determined if the end of the session is reached. If the end of the session is reached, process 900 proceeds to block 909 where the process 900 ends. If it is determined that the end of the session has not been reached, process 900 proceeds to block 902.
In one embodiment, in block 957 the DASH segment is processed for presentation on the client device. In block 958, it is determined if the process 900 is at an end of the list of segments in MPU to process. If the process 900 is at the end of the list, process 950 proceeds to block 959 and the process 900 ends. If process 900 is not at the end of the list yet, the process 950 proceeds to block 953 to continue the process 950.
Any suitable circuitry, device, system or combination of these (e.g., a wireless communications infrastructure including communications towers and telecommunications servers) operative to create a communications network may be used to create communications network 1010. Communications network 1010 may be capable of providing communications using any suitable communications protocol. In some embodiments, communications network 1010 may support, for example, traditional telephone lines, cable television, Wi-Fi (e.g., a 802.11 protocol), Bluetooth®, high frequency systems (e.g., 900 MHz, 2.4 GHz, and 5.6 GHz communication systems), infrared, other relatively localized wireless communication protocol, or any combination thereof. In some embodiments, communications network 1010 may support protocols used by wireless and cellular phones and personal email devices (e.g., a Blackberry®). Such protocols can include, for example, GSM, GSM plus EDGE, CDMA, quadband, and other cellular protocols. In another example, a long range communications protocol can include Wi-Fi and protocols for placing or receiving calls using VOIP or LAN. Transmitting device 1012 and receiving device 1011, when located within communications network 1010, may communicate over a bidirectional communication path such as path 1013. Both transmitting device 1012 and receiving device 1011 may be capable of initiating a communications operation and receiving an initiated communications operation.
Transmitting device 1012 and receiving device 1011 may include any suitable device for sending and receiving communications operations. For example, transmitting device 1012 and receiving device 1011 may include smart television device, a media player, a cellular telephone or a landline telephone, a personal e-mail or messaging device with audio and/or video capabilities, pocket-sized personal computers such as an iPAQ, personal digital assistants (PDAs), a desktop computer, a laptop computer, and any other device capable of communicating wirelessly (with or without the aid of a wireless enabling accessory system) or via wired pathways (e.g., using traditional telephone wires), such as client device 100,
In one embodiment, the display 1121 may be a separate device from the television device 1120 or integrated with the television device 1120. In one embodiment, the camera 1122 may be a separate device from the television device 1120 or integrated with the television device 1120. In one embodiment, the network connection device 1110 may comprise a network interface, such as a network modem, router, etc. for handling communications between the client device 1120 and the server device 1130 and for forming a local network that the client device 1120 may be connected with (e.g., network 205,
In one embodiment, the client device 1120 may comprise input mechanisms (e.g., touchscreen, voice recognition, keyboards, remote control, etc.), communications circuitry, control circuitry, audio output, and any other suitable components.
In one embodiment, all of the applications employed by display 1121, the input mechanism, the audio output and communications circuitry may be interconnected and managed by control circuitry. In one example, a hand held music player capable of transmitting content including video, music, etc. to other devices may be incorporated into the client device 1120.
In one embodiment, the audio output may include any suitable audio component for providing audio to a user of the client device 1120. For example, the audio output may include one or more speakers (e.g., mono or stereo speakers) built into the client device 1120. In some embodiments, the audio output may include an audio component that is remotely coupled to the client device 1120. For example, the audio output may include a headset, headphones or earbuds that may be coupled to communications device with a wire (e.g., coupled to the client device 1120 with a jack) or wirelessly (e.g., Bluetooth® headphones or a Bluetooth® headset).
In one embodiment, display 1121 may include any suitable screen or projection system for providing a display visible to the user. For example, display 1121 may include a screen (e.g., an LCD screen) that is incorporated in the client device 1120. As another example, display 1121 may include a movable display or a projecting system for providing a display of content on a surface remote from the client device 1120 (e.g., a video projector). Display 1121 may be operative to display content (e.g., information regarding communications operations or information regarding available media selections) under the direction of the control circuitry.
In some embodiments, the communications circuitry of the client device 1120 may be operative to create a communications network using any suitable communications protocol. For example, the communications circuitry may create a short-range communications network using a short-range communications protocol to connect to other communications devices. For example, the communications circuitry may be operative to create a local communications network using the Bluetooth® protocol with other electronic devices.
In one embodiment, the control circuitry of the client device 1120 may be operative to perform the operations of one or more applications 11126 to N 1128 implemented on the client device 1120. Any suitable number or type of applications may be implemented. Although the following discussion will enumerate different applications, it will be understood that some or all of the applications may be combined into one or more applications. Example applications may include include an application connection application, a dialog application, a map application, a media application (e.g., QuickTime, MobileMusic.app, or MobileVideo.app), social networking applications, etc. In some embodiments, the client device 1120 may include one or several applications operative to perform communications operations. For example, the client device 1120 may include a messaging application, a mail application, a telephone application, a voicemail application, an instant messaging application (e.g., for chatting), a videoconferencing application, a fax application, or any other suitable application for performing any suitable communications operation.
In one embodiment, a user may direct the client device 1120 to perform a communications operation using any suitable approach. As one example, a user may receive a communications request from another device (e.g., an incoming telephone call, an email or text message, an instant message), and may initiate a communications operation by accepting the communications request. As another example, the user may initiate a communications operation by identifying another communications device and transmitting a request to initiate a communications operation (e.g., dialing a telephone number, sending an email, typing a text message, or selecting a chat screen name and sending a chat request).
In one embodiment, the information from the MPD file is URL information. In one embodiment, the one or more DASH segments and the associated URL information are stored together in the segments buffer. In one embodiment, process 1200 may include tuning to a service by the client device for receiving the one or more DASH segments over MMTP without using HTTP.
In one embodiment, the client device comprises the segments buffer without an HTTP cache. In one embodiment, process 1200 may provide that the one or more DASH segments comprise reconstructed DASH segments, and the reconstructed DASH segments are stored in the segments buffer immediately after reconstruction.
In one embodiment, the one or more reconstructed DASH segments comprise multiple representations. In one implementation, the multiple representations each comprise one or more of different data rates (e.g., 250 Kbps, 500 Kbps, 1000 Kbps, etc.) and different levels of video quality (e.g., ultra-high definition (UHD), high definition (HD), standard definition (SD), 640×480, 1024×768, etc.). In one embodiment, process 1200 may include if a requested DASH segment for a particular representation having a desired level of video quality is not found in the segments buffer, modifying the URL and searching for another representation of the requested DASH segment having a next lower level of video quality.
In one embodiment, process 1200 may include that the URL information is used as an index for searching the segments buffer for the one or more particular DASH segments.
As is known to those skilled in the art, the aforementioned example architectures described above, according to said architectures, can be implemented in many ways, such as program instructions for execution by a processor, as software modules, microcode, as computer program product on computer readable media, as analog/logic circuits, as application specific integrated circuits, as firmware, as consumer electronic devices, AV devices, wireless/wired transmitters, wireless/wired receivers, networks, multi-media devices, etc. Further, embodiments of said Architecture can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements.
Embodiments have been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to one or more embodiments. Each block of such illustrations/diagrams, or combinations thereof, can be implemented by computer program instructions. The computer program instructions when provided to a processor produce a machine, such that the instructions, which execute via the processor, create means for implementing the functions/operations specified in the flowchart and/or block diagram. Each block in the flowchart/block diagrams may represent a hardware and/or software module or logic, implementing one or more embodiments. In alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures, concurrently, etc.
The terms “computer program medium,” “computer usable medium,” “computer readable medium”, and “computer program product,” are used to generally refer to media such as main memory, secondary memory, removable storage drive, a hard disk installed in hard disk drive. These computer program products are means for providing software to the computer system. The computer readable medium allows the computer system to read data, instructions, messages or message packets, and other computer readable information from the computer readable medium. The computer readable medium, for example, may include non-volatile memory, such as a floppy disk, ROM, flash memory, disk drive memory, a CD-ROM, and other permanent storage. It is useful, for example, for transporting information, such as data and computer instructions, between computer systems. Computer program instructions may be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
Computer program instructions representing the block diagram and/or flowcharts herein may be loaded onto a computer, programmable data processing apparatus, or processing devices to cause a series of operations performed thereon to produce a computer implemented process. Computer programs (i.e., computer control logic) are stored in main memory and/or secondary memory. Computer programs may also be received via a communications interface. Such computer programs, when executed, enable the computer system to perform the features of one or more embodiments as discussed herein. In particular, the computer programs, when executed, enable the processor and/or multi-core processor to perform the features of the computer system. Such computer programs represent controllers of the computer system. A computer program product comprises a tangible storage medium readable by a computer system and storing instructions for execution by the computer system for performing a method of one or more embodiments.
Though the embodiments have been described with reference to certain versions thereof; however, other versions are possible. Therefore, the spirit and scope of the appended claims should not be limited to the description of the preferred versions contained herein.
This application claims the priority benefit of U.S. Provisional Patent Application Ser. No. 61/887,846, filed Oct. 7, 2013, incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
8914835 | Chen | Dec 2014 | B2 |
9386125 | Bae | Jul 2016 | B2 |
20120023254 | Park et al. | Jan 2012 | A1 |
20120124179 | Cappio et al. | May 2012 | A1 |
20120209952 | Lotfallah et al. | Aug 2012 | A1 |
20120259994 | Gillies | Oct 2012 | A1 |
20130007814 | Cherian et al. | Jan 2013 | A1 |
20130036234 | Pazos et al. | Feb 2013 | A1 |
20130091251 | Walker et al. | Apr 2013 | A1 |
20130182643 | Pazos et al. | Jul 2013 | A1 |
20130195204 | Reznik | Aug 2013 | A1 |
20130268577 | Oyman | Oct 2013 | A1 |
20130268761 | Giladi | Oct 2013 | A1 |
20130276035 | Walker et al. | Oct 2013 | A1 |
20130298177 | Rhyu | Nov 2013 | A1 |
20140019635 | Reznik | Jan 2014 | A1 |
20140020111 | Wang | Jan 2014 | A1 |
20140133489 | Bae | May 2014 | A1 |
20140245359 | De Foy | Aug 2014 | A1 |
20140282792 | Bao | Sep 2014 | A1 |
20140313916 | Hwang | Oct 2014 | A1 |
20140317476 | Hwang | Oct 2014 | A1 |
20140317664 | Park | Oct 2014 | A1 |
20140317674 | Hwang | Oct 2014 | A1 |
20140325572 | Yie | Oct 2014 | A1 |
20140334504 | Yie | Nov 2014 | A1 |
20140344470 | Lee | Nov 2014 | A1 |
20150012956 | Kim | Jan 2015 | A1 |
20150032845 | Bouazizi | Jan 2015 | A1 |
20150100996 | Freeman | Apr 2015 | A1 |
20150106862 | Watanabe | Apr 2015 | A1 |
20150189337 | Pedan | Jul 2015 | A1 |
20150215369 | Yamagishi | Jul 2015 | A1 |
20150229676 | Bouazizi | Aug 2015 | A1 |
20150281799 | Lim | Oct 2015 | A1 |
20150334152 | Oyman | Nov 2015 | A1 |
20160006784 | Lee | Jan 2016 | A1 |
20160234532 | Lee | Aug 2016 | A1 |
Number | Date | Country |
---|---|---|
2596615 | May 2013 | EP |
2012011746 | Jan 2012 | WO |
2012134530 | Oct 2012 | WO |
Entry |
---|
Kim, C-S., “A study on Dynamic Adaptive Streaming System over HPPT for Various Streaming Services”, International Journal of Future Generation Communication and Networking, Sep. 2012, Department of Multimedia Engineering, College of Engineering, Hannam University and Department of Computer Engineering, College of Engineering, Paichai University, Korea pp. 1-10, vol. , No. 3, Korea. |
International Search Report and Written Opinion dated Jan. 5, 2015 for International Application No. PCT/KR2014/009422 from Korean Intellectual Property Office, pp. 1-10, Daejeon, Republic of Korea. |
Extended European Search Report dated May 4, 2017 for European Application No. 14852565.2 from European Patent Office, pp. 1-10, Munich, Germany. |
Yongkwon, L. et al,, “Client operation for DASH service delivered through MMT Protocol”, Proceedings in the 2014 International Organisation for Standardisation for Coding of Moving Pictures and Audio, Jul. 7, 2014, pp. 1-3, Samsung Electronics, Sapporo, Japan. |
International Orgianization for Statndarization (ISO) and International Electrotechnical Commision (IEC), “Information technology-High efficiency coding and media delivery in heterogeneous environments—Part 13: MMT implementation guidelines”, Jan. 1, 2013, pp. 1-22, Geneva. |
Stockhammer, T. et al., “Dash in Mobile Networks and Services”, Proceedings of the 2012 Visual Communications and Image Processing (VCIP), Nov. 27-30, 2012, pp. 1-6, IEEE, United States. |
Bouazizi, I. et al., “Proposed changes to MMTP and Payload Format”, International Organisation for Standardisation for Coding of Moving Pictures and Audio, Jul. 29, 2013, pp. 1-18, Vienna, Austria. |
International Orgianization for Statndarization (ISO) and International Electrotechnical Commision (EIC), “Inforrnation technology-High efficiency coding and media delivery in heterogeneous environments—Part 1: MPEG media transport (MMT)”, Apr. 26, 2013, pp. 1-92, Geneva. |
International Orgianization for Statndarization (ISO) and International Electrotechnical Commision (IEC), “Study of ISO/IEC PDTR 23008-13 MPEG Media Transport Implementation Guidelines”, 109. MPEG Meeting, Jul. 7, 2014—Jul. 11, 2014, Sapporo, (Motion Picture Expert Group or ISO/IEC JTC1/SC29/WG11), Oct. 3, 2014, pp. 1-54, No. N14643, XP030021381, Geneva. |
Number | Date | Country | |
---|---|---|---|
20150100996 A1 | Apr 2015 | US |
Number | Date | Country | |
---|---|---|---|
61887846 | Oct 2013 | US |