Patent Grant
10425666
Field
One or more exemplary embodiments relate to streaming methods and apparatuses, and more particularly, to a method and apparatus for adaptively streaming media data according to fluctuations in a streaming environment.
Description of the Related Art
Examples of a method of transmitting media data through a network include a downloading method and a streaming method. In the streaming method, a server transmits media data in real time, and a client reproduces the received media data in real time.
Unlike the downloading method that starts to reproduce media data after transmitting and receiving the media data, since the streaming method transmits and receives the media data through a logical channel set between the server and the client, and reproduces the media data in real time, a method and apparatus for maintaining quality of service (QoS) in reproducing the media data by reflecting fluctuations in a streaming environment are required.
One or more exemplary embodiments provide a method and apparatus for adaptively adjusting and performing streaming, i.e., for adaptively transmitting and receiving media data according to a streaming environment.
An exemplary embodiment also provides a computer readable recording medium having recorded thereon a program for executing the methods described herein.
According to an aspect of an exemplary embodiment, there is provided a method of receiving media data, the method including: receiving a file including information regarding a plurality of media data, which are generated by encoding content to have different qualities, from a server; and receiving at least one of the plurality of media data, based on the file. Each one of the plurality of media data includes at least one data segment generated by encoding the content to have a predetermined quality and dividing the content based on time. The at least one data segment starts with a random access point.
The plurality of media data may be media data in a MPEG-2 TS (MPEG-2 transport stream) format, and may correspond to elementary streams in the MPEG-2 TS format.
The at least one data segment may include at least one packetized elementary stream (PES). The at least one PES may be completely included in the at least one data segment.
The at least one PES may include data at least one video frame or one audio frame.
A transport stream of the random access point may include information indicating that the transport stream is related to the random access point.
The file may further include information pointing to at least one of a program association table (PAT) and a program map table (PMT) regarding the plurality of media data.
The PAT and the PMT may be initialization segments and may be separated from the plurality of media data.
At least one of the PAT and the PMT may include an entire list of the plurality of media data.
Different packet identifiers (PIDs) may be assigned to the plurality of media data.
The at least one data segment may include transport streams of at least one group of pictures (GOP).
The plurality of media data may be media data in an MP4 format, and may correspond to “trak” boxes in the MP4 format.
According to another aspect of an exemplary embodiment, there is provided a method of transmitting media data, the method including transmitting a file including information about a plurality of media data, which are generated by encoding content to have different qualities, to a client; and transmitting at least one of the plurality of media data to the client, in response to a request from the client based on the file. Each one of the plurality of media data includes at least one data segment generated by encoding the content to have a predetermined quality and dividing the content based on time. The at least one data segment starts with a random access point.
According to another aspect of an exemplary embodiment, there is provided an apparatus for receiving media data, the apparatus including an information receiver for receiving a file including information regarding a plurality of media data, which are generated by encoding content to have different qualities, from a server; and a media data receiver for receiving at least one of the plurality of media data, based on the file. Each one of the plurality of media data includes at least one data segment generated by encoding the content to have a predetermined quality and dividing the content based on time. The at least one data segment starts with a random access point.
According to another aspect of an exemplary embodiment, there is provided an apparatus for transmitting media data, the apparatus including an information transmitter for transmitting a file including information about a plurality of media data, which are generated by encoding content to have different qualities, to a client; and a media data transmitter for transmitting at least one of the plurality of media data to the client, in response to a request from the client based on the file. Each one of the plurality of media data includes at least one data segment generated by encoding the content to have a predetermined quality and dividing the content based on time. The at least one data segment starts with a random access point.
According to another aspect of an exemplary embodiment, there is provided a computer readable recording medium having recorded thereon a program for executing the above-described methods.
The above and/or other aspects will become more apparent by describing in detail exemplary embodiments with reference to the attached drawings in which:
Hereinafter, exemplary embodiments will be described more fully with reference to the accompanying drawings, in which exemplary embodiments are shown. Expressions such as “at least one of,” when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list.
The encoding device 110 generates a plurality of media data about one input content by encoding the input content to have a plurality of different qualities. A streaming environment may change when the server 120 streams media data to the client 130. For example, a bandwidth of a network 140 for streaming may be changed, or a hardware source that may be used by the server 120 to transmit media data or by the client 130 to receive media data may be changed.
Accordingly, the encoding device 110 encodes one content to have different qualities for adaptive streaming according to a fluidic streaming environment. One content may be encoded to have different qualities by adjusting a factor, such as a bit rate, a sampling frequency, resolution, or a frame rate. For example, a plurality of media data in 500 Kbps, 1000 Kbps, and 2000 Kbps may be generated by encoding one image content in different resolutions.
The plurality of media data in different qualities are transmitted to the server 120, and at this time, information about the content and information about each media data may also be transmitted to the server 120. The information about the content may include, but is not limited to, information about a title, a synopsis, a content identifier (ID), and a content uniform resource locator (URL) of the content as metadata of the content. The information about each media data may include a quality, a type, an ID, or the like of each media data, and will be described in detail with reference to
The client 130 receives at least one of the information about content and information about each media data, and requests the server 120 for at least one of the plurality of media data, based on the received at least one of the information about content and information about each media data. The client 130 estimates a streaming environment, and selects at least one of the plurality of media data based on the estimated streaming environment. The at least one media data that may maintain an optimum quality of service (QoS) in the estimated streaming environment may be selected. Then, the client 130 may transmit a hypertext transfer protocol (HTTP) request for requesting the server 120 to transmit the selected at least one media data.
When a streaming environment is deteriorated and high quality media data is received but continuous reproduction of media data is not possible, low quality media data may be requested from among a plurality of media data. When a streaming environment is improved and high quality media data is received and continuous reproduction of media data is possible, the high quality media data may continue to be requested from among a plurality of media data.
The client 130 may request the server 120 to transmit another media data while receiving a predetermined media data. For example, the client 130, which requested and was receiving first media data that is of low quality in a deteriorated streaming environment, may request the server 120 to transmit second media data that is of a higher quality than the first media data as the streaming environment improves. According to a conventional streaming method, when the server 120 and the client 130 sets a quality while initially setting a streaming channel, media data is continuously transmitted and received having the same quality. However, according to the present exemplary embodiment, streaming that is adaptive to the streaming environment is possible since the client 130 is able to request the second media data again even while receiving the first media data about the same content.
The client 130 may estimate a streaming environment by using any method of estimating a streaming environment based on the bandwidth of the network 140 or the hardware resource that may be used by the server 120 or the client 130. For example, the client 130 may estimate the streaming environment based on a time stamp and a bit error rate (BER) of received media data. The streaming environment may be determined to be deteriorated when media data is received slower than a reproduction speed by checking time stamps of the received media data. Alternatively, the streaming environment may be determined to be deteriorated when BERs of the received media data are increased.
When the client 130 requests the server 120 to transmit at least one of the plurality of media data according to the streaming environment, the server 120 transmits requested media data to the client 130. The server 120 may transmit the requested media data to the client 130 as an HTTP response to the HTTP request.
Each media data may include at least one of a plurality of segments generated by encoding content in different qualities and dividing the encoded content. In other words, each media data generated by encoding the content by the encoding device 110 may include at least one segment divided based on time. The server 120 transmits the content by dividing the content into the plurality of segments and respectively transmitting the plurality of segments, instead of encoding the content in one stream and continuously transmitting the content. The plurality of segments may be generated by dividing the content into predetermined time units, such as units of 10 or 20 seconds. The time that is the basis for dividing the content may be set based on a group of pictures (GOP). Media data corresponding to pictures of one or more GOPs may be set as one segment.
For example, when content is streamed having two qualities, the first media data may include at least one segment generated by encoding the content to have a first quality and dividing the encoded content based on time, and the second media data may include at least one segment generated by encoding the content to have a second quality and dividing the encoded content based on time.
The adaptive streaming is possible by dividing each media data based on time. For example, when streaming starts, the server 120 transmits a segment corresponding to 0 to 20 seconds of the first media data that is of low quality. Then, when it is determined that the streaming environment is improved after 20 seconds and the client 130 requests media data that is of higher quality, the server 120 may transmit a segment corresponding to 20 to 40 seconds of the second media data that is of the higher quality. Since media data is divided into a plurality of segments based on time, segments of different plurality of media data may be transmitted according to a streaming environment, even during streaming.
Referring to
The data about the plurality of pictures is segmented into a plurality of transport streams in an MPEG2-TS format, and the plurality of transport streams are grouped into one segment. Since the segment is generated by grouping the plurality of transport streams, the start and end of the segment coincide with borders of a packet of a first transport stream and a packet of a last transport stream, respectively. In other words, the segment consists of the plurality of transport streams.
Referring to
In the present exemplary embodiment, for streaming adaptive to a streaming environment, media data is segmented into at least one segment and at least one segment of a media data having a quality suitable to the streaming environment is transmitted. For this reason, the at least one segment may be reproduced separately, and thus, each of the at least one segment may start with a random access point. However, since in general, a GOP may start with an intra picture and the intra picture may be used as a random access point, one segment of media data is generated by grouping a transport stream regarding at least one GOP, as illustrated in
When a plurality of transport streams in the MPEG2-TS format are generated by segmenting data about one picture, each of the plurality of transport streams may contain the data about the picture. If a plurality of transport streams are generated by segmenting data regarding a plurality of pictures into equal segments, one of the plurality of transport streams may contain data regarding two pictures. In other words, if a plurality of transport streams are generated by segmenting data about a picture at a point in time t−1 and data about a picture at a point in time t into equal parts, not in consideration of the ends of the pictures, then a last transport stream of the picture at the point in time t−1 may contain both the data about the picture at the point in time t−1 and the data about the picture at the point in time t.
In adaptive streaming according to the present exemplary embodiment, the segment 1530 and the transport stream 1520 may be reproduced separately. For example, if the client 130 of
According to another exemplary embodiment, one transport stream may contain data about a plurality of pictures. In this case, adaptive streaming may be performed in units of pictures. That is, streaming may be performed while changing pictures having different qualities in consideration of a streaming environment.
If a transport stream is related to a random access point, a header of the transport stream may contain information indicating this fact. The header of the transport stream may also contain information indicating location of a transport stream related to a subsequent random access point so as to perform random access at high speeds.
A plurality of media data may be segmented according to the method of
The plurality of media data may correspond to a plurality of elementary streams, e.g., a plurality of elementary streams according to the MPEG-2 standard, respectively. In this case, different packet IDs (PIDs) 1550, 1560, and 1570 may be assigned to the plurality of media data, respectively. According to another exemplary embodiment, a plurality of media data may be generated by encoding one content, e.g., a program, to have different qualities and may thus be assigned the same PID. The elementary stream of
According to the MPEG-2 standard, Program Specific Information (PSI) is streamed together with media data, and a PID assigned to a transport stream containing the PSI has a fixed value. However, according to an exemplary embodiment, the PSI, such as a Program Association Table (PAT) and a Program Map Table (PMT), may be separated as a header of a plurality of media data, from payload data as illustrated in
The header for all the plurality of media data, i.e., “Reference Data” in
Referring to
Also, a PES may include information for temporal synchronization of each of the plurality of media data, i.e., a time stamp. The time stamp may include time information about media data included in each PES. In particular, when a PES is generated by grouping transport streams based on time, all the transport streams included in the PES are related to media data at the same point in time. The time stamp may include at least one from among a Presentation Time Stamp (PTS) and a Decoding Time Stamp (DTS).
Time stamps of PESs included in the same type of a plurality of media data, e.g., a plurality of video data having different bit rates, or different types of a plurality of media data, e.g., video data and audio data, may be aligned based on reproduction time.
For example, if a first PES of first media data and a first PES of second media data are contents to be reproduced at the same point in time, then the same PTS and/or the same DTS may be assigned thereto. Referring to
When the second media data is to be reproduced by switching from the first media data to the second media data during reproduction of the first media data, PTSs and/or DTSs thereof may be aligned consecutively for seamless reproduction. In other words, in this case, a PTS and/or a DTS of first PES after the switching may be aligned consecutively after a PTS and/or a DTS of a last PES before the switching.
Since segments of the media data are generated in units of PESs and PTSs and/or DTSs of the PESs are aligned consecutively based on time, start times of the segments may be recognized based on the PTSs and/or DTSs. Thus, segments of the first media data may be reproduced, and then, segments of the second media data may be reproduced consecutively when the switching is performed during reproduction of the first media data.
However, according to another exemplary embodiment, no time stamp may be assigned to a PES. That is, a time stamp may be selectively assigned to a PES. If a PES does not include time information, e.g., a time stamp, it is impossible to specify start times of segments of media data. This will be described in detail with reference to
Referring to
In this case, start times of segments of the media data cannot be specified, thus preventing adaptive streaming from being performed. As described above, segments of a plurality of media data should be reproduced seamlessly for adaptive streaming, but when each PES thereof does not include a PTS and/or a DTS, start times of the segments cannot be specified and the segments of the plurality of media data cannot be consecutively) reproduced. For example, if a kth segment of first media data and a (k+1)th segment of second media data are to be sequentially reproduced, it is impossible to consecutively reproduce the kth and (k+1)th segments when start time of the (k+1)th segment cannot be specified.
Thus, according to an exemplary embodiment, time information of each segment of media data may be contained in a transport stream. For example, a PTS and/or a DTS may be contained in a first transport stream of each segment of the media data. Referring to
In Table 1, “Segment_Index( )” for indexing each segment of media data is included into a “private_data_bytes” field of a transport stream, “data_field_tag” represents that the “private_data_bytes” field of the transport stream is related to indexing of each segment, and “data_field_length” defines a field length of the transport stream. At least one selected from among a PTS, a DTS, and a Program Clock Reference (PCR) may be included as time information.
It is understood that according to an exemplary embodiment “Segment_Index( )” may be included in a first transport stream 1622 of the first PES 1620 or may be included in another transport stream 1624 or 1626 of the first PES 1620.
As described above, one PES may be included in one segment of media data and may not be included in a plurality of segments of the media data. However, when one PES 1640 is included in both a kth segment 1610 and a (k+1)th segment 1612 of media data as illustrated in
Although the PES 1640 of
Accordingly, the start times of the transport streams included in the (k+1)th segment 1612 may be specified by inserting “Segment_Index( )” into a first transport stream 1642 of the (k+1)th segment 1612.
It is understood that according to an exemplary embodiment “Segment_Index( )” may be inserted into the first transport stream 1642 of the (k+1)th segment 1612 or may be inserted into another transport stream 1644, . . . , or 1646 of the (k+1)th segment 1612.
Seamless reproduction may be impossible when PTSs and/or DTSs of PESs of a plurality of media data are not aligned according to reproduction time information. For example, when a first server produces first media data of content and a second server produces second media data of the content, PTSs and/or DTSs of PESs of the first and second media data may not be aligned according to reproduction time information.
For example, PTSs assigned to consecutive three segments of the first media data may be defined as ‘1000’, ‘12000’, and ‘13000’, respectively, and PTSs assigned to consecutive three segments of the second media data, which can be reproduced at the same point in time that the first media data is reproduced, may be defined as ‘11000’, ‘12000’, and ‘13000’, respectively. Since the PTS of the first segment of the first media data is ‘1000’ and the PTS of the first segment of the second media data is ‘11000’, it is difficult for a receiving side that receives the first and second media data to determine that the first segment of the first media data and the first segment of the second media data are reproduced at the same point in time. In this case, since the PTSs assigned to the first segment of the first media data and the first segment of the second media data are different from each other, it is impossible to perform adaptive streaming by changing the first and second media data.
Information for correcting such a problem may be generated based on the following syntax, and may be inserted into the above media presentation description or media data.
In Table 2, “Segment_Start_Adjustment( )” for time stamp adjustment is included into a “private_data_bytes” field of a transport stream, “data_field_tag” represents that the “private_data_bytes” field of the transport stream is used for time stamp adjustment, and “data_field_length” defines a field length of the transport stream. At least one from among a PTS, a DTS, and a PCR may be included as information for adjusting time stamps of segments of media data. “Segment_Start_Adjustment( )” is included in each of the segments of the media data. A time stamp of each of the segments of the media data is set according to the PTS, the DTS, or the PCR defined in “Segment_Start_Adjustment( )”.
It is understood that according to an exemplary embodiment “Segment_Start_Adjustment( )” may be included in the first transport stream 1622 or another transport stream 1624, . . . , or 1626 of the first PES 1620, similar to “Segment_Index( )”.
Also, an additional transport stream for time stamp adjustment may be defined separately at the head of the first PES 1620, and “Segment_Start_Adjustment( )” may be included in the additional transport stream.
The information for time stamp adjustment may also be included as described above when media data is segmented into segments according to the MP4 format, as will be described above with reference to
The PTS and the DTS refer to, for example, time stamps of video data. As described above, time stamps of a plurality of media data for video data are aligned according to reproduction time of the media data. In case of audio data, time stamps may also be aligned according to reproduction time of the audio data. In other words, for adaptive streaming, time stamps of a plurality of media data for audio data may be aligned based on reproduction time as described above with reference to
Referring to
The I-frame access unit 1722 includes parameters for separately reproducing the segments of the media data, e.g., a Sequence Parameter Set (SPS) 1732, a Picture Parameter Set (PPS) 1734, and a Supplemental Enhancement Information (SEI) 1736. The SEI 1736 is a factor needed for Coded Picture Buffering (CPB). The I-frame access unit 1722 is a preceding frame from among frames included in the Kth segment 1710, and includes an Instantaneous Decoding Refresh (IDR) frame 1738. The SPS 1732 and the PPS 1734 are included in a first byte of the I-frame access unit 1722, and the other access units of a video stream are provided after the SPS 1732 and the PPS 1734 are referred to.
The P or B-frame access unit 1724 includes an SEI 1742 and a P or B frame 1744. The SEI 1742 may be included in the P or B-frame access unit 1724 for the same purpose as the SEI 1736 in the I-frame access unit 1722.
For seamless reproduction considering a streaming environment, segments of a plurality of media data reproduced at the same point in time should have the same start times and durations. For example, in segments of a plurality of media data reproduced at the same point in time, the same PTS should be assigned to a first access unit and a last access unit.
In the exemplary embodiment of
A plurality of media data may be segmented into segments as illustrated in
The plurality of media data may correspond to a plurality of tracks “trak 1” 1850, “trak 2” 1860, and “trak 3” 1870 in the MP4 format, respectively. In this case, different “trak” IDs may be assigned to the plurality of media data, respectively.
According to an exemplary embodiment, a header of the plurality of media data may be separated as a “moov” box from payload data, as illustrated in
In
The other payload data except for the header information is included in the “mdat” box 1880. For example, in order to group and segment audio data into at least one segment, data regarding a plurality of audio samples corresponding to the plurality of tracks “trak 1” 1850 to “trak 3” 1870 may be grouped into one segment. A plurality of segments may be generated by grouping the audio samples corresponding to the track “trak 1” 1850 into predetermined temporal units, a plurality of segments may be generated by grouping the audio samples corresponding to the track “trak 2” into predetermined temporal units, and a plurality of segments may be generated by grouping the audio samples corresponding to the track “trak 3” in predetermined temporal units. For adaptive streaming, data regarding each of the plurality of audio samples may be included in only one segment. Headers of samples included in the “mdat” box 1880 are included in the plurality of tracks “trak 1” 1850 to “trak 3” 1870 included in the “moov” box 1840. Similarly, when video data is grouped according to the MP4 format, data regarding one GOP is included in only one segment.
The media data corresponding to the track “trak 1” 1850 may be segmented into segments, based on the “moof” box 1851 or 1853 containing metadata and the “mdat” box 1852 or 1854 containing payload data.
Here, each “moof” box may include a “traf” box containing metadata regarding samples, and data regarding one sample cannot be included in a plurality of segments as illustrated in
Upon receiving the request from the client 130, the server 120 transmits the information about the predetermined content to the client 130. The server 120 may transmit the information about the predetermined content as an HTTP response to the HTTP request to the client 130. The information about the predetermined content may be a content access descriptor (CAD) according to an open IPTV forum (OIPF) standard. The information about the predetermined content will now be described in detail with reference to
Referring to
Since conventional streaming of media data generates one media data by encoding one content to have a predetermined quality, conventional information (specifically, CAD according to OIPF) about content does not include information about a plurality of media data generated by encoding the content to have different qualities.
However, the information about content, according to the present exemplary embodiment, includes information about a plurality of media data generated by encoding one content to have different qualities, and corresponds to “Tracks”, “RefData”, and “Fragments” tags in
The “ID” attribute defines identifiers sequentially given to the plurality of media data, and the “Type” attribute defines whether media data corresponds to audio data, video data, video/audio data, or subtitle data. When the “Type” attribute is “Packed”, the media data is video/audio data, and when the “Type” attribute is “Video”, the media data is video data. The “BitRate” attribute defines a bit rate used to encode the media data.
The “RefData” tag is a selective element. The “RefData” tag is included in information about content only when a header is separated from media data and exists as a separate file, and may not be included in the information about content when the header is combined with the media data.
Referring to
The “Fragments” tag includes a “NextFragmentsXMLURL” attribute. When following content is continuously streamed after streaming of one content is completed like in the case of live streaming, the following content may be seamlessly streamed only when the client 130 is aware of information about the following content. Accordingly, the “Fragments” tag defines the information about the following content as the “NextFragmentsXMLURL” attribute. URLs of the plurality of media data with respect to the following content may be defined as the “NextFragmentsXMLURL” attribute.
The “Fragment” tag includes information about at least one segment of current content. Referring to
In
Referring back to
As described with reference to
The server 120 transmits the media data according to the request of the client 130. The server 120 may transmit at least one segment of the requested media data to the client 130. The server 120 may transmit media data requested as an HTTP response with respect to an HTTP request to the client 130. The transmitted media data may be media data that is segmented into at least one segment as illustrated in one of
Referring to
In operation 222, the client 130 requests a header of selected media data from among a plurality of media data, based on the information about content received in operation 212. At least one media data suitable for a streaming environment is selected from among the plurality of media data based on the information about content received in operation 212, and a header of the selected at least one media data is requested. The header of the selected at least one media data is requested by referring to the “RefData” tag included in the information about content received in operation 212.
The server 120 transmits the requested header to the client 130. A header file may be transmitted to the client 130, and may be an XML file. The header may be a header of all a plurality of media data, e.g., the “Reference Data” illustrated in
In operation 232, the client 130 requests the server 120 to transmit selected media data based on the information about content received in operation 212 and the header received in operation 222. The client 130 requests the server 120 to transmit at least one segment generated by dividing media data based on time, and the server 120 transmits the requested at least one segment to the client 130. The transmitted media data may be media data that is segmented into at least one segment as illustrated in one of
However, in
Compatibility with various media data formats may be maintained while performing streaming that is adaptive to a streaming environment by inserting the URL of the media presentation description into the information about content as shown in
As shown in
Specifically, the “ContentURL” tag may include a “TransferType” attribute defining a service to which streaming of content is related. The “TransferType” attribute may define whether the streaming of content is related to a Content on Delivery (CoD) service, a live service, an adaptive streaming live service, or an adaptive streaming CoD service.
Referring back to
The information about content received by the client 130 from the server 120 in operation 510 may include the URL of the media presentation description as described with reference to
Referring to
An “urlTemplate” tag defines a common portion of the URLs of the plurality of media data. For example, if “http://example.com/vod/movie/18888/Track/{TrackID}/Segments/{SegmentID}” is a URL template, a URL of media data may be defined by respectively substituting an ID of each media data and an ID of at least one segment included in each media data for “TrackID” and “SegmentID”.
A “headerUrl” tag corresponds to the “RefData” tag described with reference to
An “isLive” tag defines a service related to streaming. For example, when the “isLive” tag is defined as “Live”, the streaming is related to a live service, and when the “is Live” tag is defined as “CoD”, the streaming is related to a CoD service.
A “contentType” tag defines a container format of media data used during streaming. The “contentType” tag may indicate whether the container format is an MP4 format or an MPEG2-TS format. The container format is an MP4 format or an MPEG2-TS format herein, though it is understood that according to an exemplary embodiment the container format is not limited thereto, and any container format for transmitting media data may be used. For example, the “contentType” tag may define that the container format complies with an MPEG Media Transport (MMT) standard.
A “Stream” tag is generated for each media data and defines each media data. In order to define each media data generated by encoding one content to have different qualities, the “Stream” tag includes a “streamName” attribute, a “type” attribute, a “bitrate” attribute, a “startTime” attribute, a “firstIntervaNum” attribute, a “duration” attribute, and an “intervalCount” attribute.
The “streamName” attribute defines a name of media data, and may be an ID of media data. The “type” attribute defines a type of media data, wherein it is defined whether the media data is audio data, video data, or audio/video data. When media data only includes data about an I-frame for a trick play, such information may be defined in the “type” attribute.
The “bitrate” attribute defines a bit rate of media data, the “startTime” attribute defines a time stamp for specifying a start time of media data, and the “firstIntervaNum” attribute defines a number of a segment that initially starts.
The “duration” attribute defines a duration time of a segment included in media data, and the “intervalCount” attribute defines a total number of at least one segment included in media data.
The “Segment” tag is a sub tag of the “Stream” tag, and as described above, when media data includes at least one segment generated by encoding content in a predetermined quality and dividing the encoded content based on time, each of the at least one segment is defined.
The “IntNum” attribute defines a number of a segment, and the “StartTime” tag defines a start time of a corresponding segment. The “Duration” tag defines a duration time of a corresponding segment, and the “url” defines a URL of a corresponding segment.
The “Segment” tag is a selective tag, and may not be included in the media presentation description if the information about at least one segment included in the media data can be inferred from other attributes of the “Stream” tag. In other words, when content of the “Segment” tag can be inferred from the “startTime”, “firstIntervaNum”, “duration”, and “intervalCount” attributes defined in the “Stream” tag, the “Segment” tag may not be included in the media presentation description. Also, a “url” attribute of the “Segment” tag may not be required if a predetermined template is defined in the “urlTemplate”, and the URLs of segments are inferred by substituting each ID of the plurality of media data and an ID of at least one segment included in each media data with the defined predetermined template.
However, on the other hand, attributes of the “Segment” tag are separately defined for each segment, if the attributes of the “Segment” tag cannot be inferred from other attributes of the “Stream” tag. The attributes of the “Segment” tag may not be inferred if duration times of segments are different. When duration times are different, the duration times of segments included in media data cannot be inferred from the attributes of the “Stream” tag, and thus the duration times of the segments may be each set by using a “duration” attribute of the “Segment” tag. When the duration times of the segments are different, start times of continuous segments are also different. For example, when a duration time of a first segment of first media data is different from a duration time of a second segment of the first media data, a start time of the second segment and a start time of a third segment cannot be inferred from the “Stream” tag. Accordingly, a start time of each segment may be defined by a “startTime” attribute.
The duration times and/or start times may be defined by using a sub tag of the “Segment” tag, instead of using the “duration” attribute and the “startTime” attribute of the “Segment” tag. For example, a “Url” tag constituting a sub tag of the “Segment” tag may be set, and a duration time may be defined as an attribute of the “Url” tag, such as “<Url=www.example.com/˜/segment.ts, duration=10/>”.
According to another exemplary embodiment, duration time may be defined based on a difference between duration times of continuous segments. An upper tag may define a default duration time, and the “Url” tag constituting the sub tag may define only a difference between the default duration time and an actual duration time for each segment. As described above, the “Url” tag constituting the sub tag of the “Segment” tag may be defined as “<Url=www.example.com/˜/segment.ts, duration=difference/>”. “Difference” denotes a difference between the default duration time and the actual duration time.
When a default duration time of a corresponding segment is defined to be 10 minutes by using the “Stream” tag or the “Segment” tag, and the “Url” tag constituting the sub tag is defined to be “<Url=www.example.com/˜/segment.ts, duration=2/>”, a duration time of the corresponding segment may be defined to be 10+2=12 minutes.
Referring to
The “URLTemplate” tag and the “RefDataURL” tag of
An “ID” attribute, a “Type” attribute, a “BitRate” attribute, a “StartTime” attribute, a “SegmentDuration” attribute, a “SegmentStartID” attribute, and a “SegmentCount” attribute of
The media presentation description of
Referring to
The server 120 selectively transmits the media presentation description of
Since not only the audio data, but also the subtitle may be divided into a plurality of segments, based on time, the audio data and the subtitle may be changed to audio data and a subtitle of another language during streaming.
Referring back to
In operation 522, the client 130 requests the server 120 to transmit information about a plurality of media data based on the information about predetermined content received in operation 512. The client 130 may request the server 120 for a media presentation description through the HTTP request, and receive the media presentation description as the HTTP response.
In operation 532, the client 130 requests a header of media data selected based on the information about the plurality of media data received in operation 522. At least one media data that is suitable to a streaming environment is selected from among the plurality of media data based on the information about the plurality of media data received in operation 522, and a header of the selected at least one media data is requested. The header of the selected at least one media data is requested by referring to the information about the plurality of media data received in operation 522. The server 120 transmits a file of the header of the selected at least one media data to the client 130 in response to the request of the client 130. The header may be a header of all a plurality of media data, e.g., the “Reference Data” illustrated in
In operation 542, the client 130 requests the server 120 to transmit selected media data based on the information about the plurality of media data received in operation 522, and the header received in operation 532. The client 130 requests the server 120 to transmit at least one segment generated by encoding content to have a predetermined quality and dividing the encoded content based on time, and the server 120 transmits the requested at least one segment to the client 130. The transmitted media data may be media data that is segmented into at least one segment as illustrated in one of
Referring to
The server 120 may include information 1040 required for the client 130 to access the plurality of media data 1010 through 1030. The server 120 may include a “CadMeta.xml” file as information about content, a “MainMeta.xml” file as information about the plurality of media data 1010 through 1030, and a “Head1.ref” file, a “Head2.ref” file, etc. as header files of the plurality of media data 1010 through 1030. Here, the “Head1.ref” file may be a header file of the “Track1”, and the “Head2.ref” file may be a header file of the “Track2”.
The “CadMeta.xml” file may be a CAD file according to the OIPF standard, and the “MainMeta.xml” file may be the media presentation description described above. Also, the “Head1.ref” and “Head2.ref” files are selective elements, and may not exist when headers are included in the plurality of media data 1010 through 1030.
Referring to
Referring to
For example, when the plurality of media data 1010 through 1030 corresponds to elementary streams, e.g., an elementary stream according to the MPEG-2 standard, each of the header files of the plurality of media data 1010 through 1030 may include at least one of a PAT and a PMT. At least one of the PAT and the PMT may be separated from the plurality of media data 1010 through 1030 to prepare the header file 1050, and the media presentation description may include information pointing to the header file 1050. The information pointing to the header file 1050 may be URL information of the header file 1050 or information for specifying a transport stream packet including the header file 1050 in a MPEG-2 elementary stream. The header file 1050 may be a header of all the plurality of media data 1010 through 1030, e.g., the “Reference Data” illustrated in
The PAT and the PMT may be separated as the header file 1050 or may be included in the plurality of media data 1010 through 1030, but may include an entire list of elementary streams included in the plurality of media data 1010 through 1030 regardless of the locations of the PAT and the PMT.
A case where PSI, e.g., the PAT and the PMT, is separated as an additional header from additional payload data, has been described above with reference to
Referring back to
In operation 1120, the client 130 requests the server 120 to transmit at least one of the plurality of media data. The client 130 selects at least one media data encoded to have a quality suitable for the streaming environment by referring to the information about the plurality of media data, requests the server 120 to transmit the selected media data, and then receives the requested media data from the server 120. The transmitted media data may be media data that is segmented into at least one segment as illustrated in one of
In operation 1122, the client 130 requests a header of media data selected based on the information about the plurality of media data received in operation 1112. The client 130 requests the header of media data selected according to a streaming environment by referring to the information about the plurality of media data received in operation 1112. In response to the request, the server 120 transmits a file including the header of the selected media data to the client 130. The header may be a header of all the plurality of media data, i.e., the “Reference Data” illustrated in
In operation 1132, the client 130 requests the server 120 to transmit the selected media data based on the information about the plurality of media data received in operation 1112, and the header received in operation 1122. The client 130 requests the server 120 to transmit at least one segment generated by encoding content in a predetermined quality and dividing the encoded content based on time, and the server 120 transmits the requested at least one segment to the client 130. The transmitted media data may be media data that is segmented into at least one segment as illustrated in one of
Referring to
Here, the plurality of media data 1010 through 1030 of
Referring to
Referring to
The information transmitter 1310 receives a request to transmit predetermined information from the client 130, and transmits the predetermined information to the client 130 in response to the request. The information transmitter 1310 receives a request to transmit at least one of information about content and information about a plurality of media data from the client 130, and transmits requested information to the client 130. The information transmitter 1310 receives an HTTP request for requesting at least one of the information about content and the information about the plurality of media data from the client 130, and transmits requested information as an HTTP response.
The media data transmitter 1320 receives a request to transmit at least one media data selected from the plurality of media data according to a streaming environment from the client 130, and transmits requested media data to the client 130. The information transmitter 1310 receives a request to transmit media data selected based on the information about the plurality of media data transmitted to the client 130. The server 120 may transmit the requested media data to the client 130 by receiving and storing the plurality of media data encoded to have different qualities by the encoding device 110. Also, the server 120 may receive the requested media data from the encoding device 110 and transmit the requested media data to the client 130 in real-time according to the request of the client 130.
The information receiver 1410 transmits a request to transmit predetermined information to the server 120, and receives the predetermined information from the server 120 in response to the request. The information receiver 1410 transmits a request to transmit at least one of information about content and information about a plurality of media data to the server 120, and receives requested information from the server 120. According to the exemplary embodiments of
The media data receiver 1420 transmits a request to transmit at least one media data selected from among the plurality of media data according to a streaming environment to the server 120, and receives requested media data from the server 120. The information receiver 1410 transmits a request to transmit media data selected according to the streaming environment based on the information about the plurality of media data received from the server 120.
According to an exemplary embodiment, streaming that is adaptive to a streaming environment can be performed by using a conventional protocol without having to change a structure of a server and/or a client, and thus an adaptive streaming system that is compatible with various media data formats can be manufactured at low cost.
An exemplary embodiment can also be embodied as computer readable codes on a computer readable recording medium.
For example, a streaming apparatus of a server and a streaming apparatus of a client according to exemplary embodiments may include a bus coupled to each unit of the apparatus 1300 of
The computer readable recording medium is any data storage device that can store data which can be thereafter read by a computer system. Examples of the computer readable recording medium include, but are not limited to, read-only memory (ROM), random-access memory (RAM), CD-ROMs, magnetic tapes, floppy disks, optical data storage devices, etc. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the following claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2010-0103721 | Oct 2010 | KR | national |
This application claims priorities from U.S. Provisional Application No. 61/260,906, filed on Nov. 13, 2009, U.S. Provisional Application No. 61/262,708, filed on Nov. 19, 2009, U.S. Provisional Application No. 61/267,131, filed on Dec. 7, 2009, U.S. Provisional Application No. 61/314,233, filed on Mar. 16, 2010, U.S. Provisional Application No. 61/318,916, filed on Mar. 30, 2010, U.S. Provisional Application No. 61/380,461, filed on Sep. 7, 2010, U.S. Provisional Application No. 61/380,477, filed on Sep. 7, 2010, in the U.S. Patents and Trademark Office, and Korean Patent Application No. 10-2010-0103721, filed on Oct. 22, 2010, in the Korean Intellectual Property Office, the disclosures of which are incorporated herein in their entireties by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5784528 | Yamane et al. | Jul 1998 | A |
| 6851091 | Honda et al. | Feb 2005 | B1 |
| 6895410 | Ridge | May 2005 | B2 |
| 7103668 | Corley et al. | Sep 2006 | B1 |
| 7318099 | Stahl et al. | Jan 2008 | B2 |
| 7421127 | Bruls et al. | Sep 2008 | B2 |
| 7447791 | Leaning et al. | Nov 2008 | B2 |
| 7760990 | Kato | Jul 2010 | B2 |
| 7944908 | Lee et al. | May 2011 | B2 |
| 8176029 | Wang | May 2012 | B2 |
| 8205004 | Kaufman | Jun 2012 | B1 |
| 8341662 | Bassett et al. | Dec 2012 | B1 |
| 8619851 | Ito | Dec 2013 | B2 |
| 8661105 | Tian et al. | Feb 2014 | B2 |
| 20020053085 | Toguri | May 2002 | A1 |
| 20020161739 | Oh | Oct 2002 | A1 |
| 20020172281 | Mantchala | Nov 2002 | A1 |
| 20030061369 | Aksu et al. | Mar 2003 | A1 |
| 20030072376 | Krishnamachari et al. | Apr 2003 | A1 |
| 20030177503 | Sull et al. | Sep 2003 | A1 |
| 20030189649 | Kuno | Oct 2003 | A1 |
| 20030236895 | Ohkubo et al. | Dec 2003 | A1 |
| 20040064572 | Yamaguchi et al. | Apr 2004 | A1 |
| 20040064573 | Leaning et al. | Apr 2004 | A1 |
| 20040119814 | Clisham et al. | Jun 2004 | A1 |
| 20040187161 | Cao | Sep 2004 | A1 |
| 20040220966 | Ridge | Nov 2004 | A1 |
| 20040252771 | Oishi | Dec 2004 | A1 |
| 20050018873 | Rhoads | Jan 2005 | A1 |
| 20050047345 | Suh | Mar 2005 | A1 |
| 20050068992 | Kaku et al. | Mar 2005 | A1 |
| 20050071491 | Seo | Mar 2005 | A1 |
| 20050102371 | Aksu | May 2005 | A1 |
| 20050123136 | Shin et al. | Jun 2005 | A1 |
| 20050135476 | Gentric et al. | Jun 2005 | A1 |
| 20050160177 | Kim | Jul 2005 | A1 |
| 20050183120 | Jain et al. | Aug 2005 | A1 |
| 20050193138 | Kim | Sep 2005 | A1 |
| 20050193425 | Sull et al. | Sep 2005 | A1 |
| 20050198282 | Stahl et al. | Sep 2005 | A1 |
| 20050234892 | Tamura | Oct 2005 | A1 |
| 20050244137 | Takashima | Nov 2005 | A1 |
| 20050262541 | Oota | Nov 2005 | A1 |
| 20060037057 | Xu | Feb 2006 | A1 |
| 20060120378 | Usuki et al. | Jun 2006 | A1 |
| 20060126713 | Chou et al. | Jun 2006 | A1 |
| 20060139379 | Toma et al. | Jun 2006 | A1 |
| 20070003251 | Chung et al. | Jan 2007 | A1 |
| 20070016657 | Ito | Jan 2007 | A1 |
| 20070025687 | Kim | Feb 2007 | A1 |
| 20070101164 | Ando et al. | May 2007 | A1 |
| 20070177854 | Ando et al. | Aug 2007 | A1 |
| 20070280641 | Uchimura | Dec 2007 | A1 |
| 20080037658 | Price | Feb 2008 | A1 |
| 20080040498 | Setlur et al. | Feb 2008 | A1 |
| 20080069204 | Uchiike | Mar 2008 | A1 |
| 20080109532 | Denoual et al. | May 2008 | A1 |
| 20080177865 | Heo et al. | Jul 2008 | A1 |
| 20080195743 | Brueck et al. | Aug 2008 | A1 |
| 20080215317 | Fejzo | Sep 2008 | A1 |
| 20080216135 | Pfeffer | Sep 2008 | A1 |
| 20080301380 | Itho | Dec 2008 | A1 |
| 20090010273 | Green et al. | Jan 2009 | A1 |
| 20090010615 | Kawahara | Jan 2009 | A1 |
| 20090018681 | Lee et al. | Jan 2009 | A1 |
| 20090031007 | Boic et al. | Jan 2009 | A1 |
| 20090051811 | Yoo et al. | Feb 2009 | A1 |
| 20090055417 | Hannuksela | Feb 2009 | A1 |
| 20090055547 | Hudson et al. | Feb 2009 | A1 |
| 20090089535 | Lohmar et al. | Apr 2009 | A1 |
| 20090097819 | Dui et al. | Apr 2009 | A1 |
| 20090100496 | Bechtolsheim | Apr 2009 | A1 |
| 20090106288 | Yang et al. | Apr 2009 | A1 |
| 20090110060 | Cortes et al. | Apr 2009 | A1 |
| 20090141888 | Kim et al. | Jun 2009 | A1 |
| 20090204487 | Cansler et al. | Aug 2009 | A1 |
| 20090258594 | Martin-Cocher et al. | Oct 2009 | A1 |
| 20090263103 | Mae | Oct 2009 | A1 |
| 20090300145 | Musayev et al. | Dec 2009 | A1 |
| 20090300204 | Zhang et al. | Dec 2009 | A1 |
| 20090323822 | Rodriguez | Dec 2009 | A1 |
| 20100046611 | Tome et al. | Feb 2010 | A1 |
| 20100046924 | Ikeda et al. | Feb 2010 | A1 |
| 20100083339 | Yoshii | Apr 2010 | A1 |
| 20100092148 | Ogawa et al. | Apr 2010 | A1 |
| 20100118938 | Fuchs et al. | May 2010 | A1 |
| 20100138489 | Corley et al. | Jun 2010 | A1 |
| 20100189028 | De Camargo | Jul 2010 | A1 |
| 20100205049 | Long | Aug 2010 | A1 |
| 20100235472 | Sood et al. | Sep 2010 | A1 |
| 20100262492 | Bogestam et al. | Oct 2010 | A1 |
| 20110022471 | Brueck | Jan 2011 | A1 |
| 20110022638 | Jiang | Jan 2011 | A1 |
| 20110029649 | Tian et al. | Feb 2011 | A1 |
| 20110058675 | Brueck et al. | Mar 2011 | A1 |
| 20110080940 | Bocharov | Apr 2011 | A1 |
| 20110083144 | Bocharov et al. | Apr 2011 | A1 |
| 20110090953 | Melnyk et al. | Apr 2011 | A1 |
| 20110119394 | Wang et al. | May 2011 | A1 |
| 20110277005 | Pedlow | Nov 2011 | A1 |
| 20130166765 | Kaufman | Jun 2013 | A1 |
| 20150256585 | Brueck et al. | Sep 2015 | A1 |
| 20160323342 | Luby et al. | Nov 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 1290895 | Apr 2001 | CN |
| 1459066 | Nov 2003 | CN |
| 1481643 | Mar 2004 | CN |
| 1559119 | Dec 2004 | CN |
| 1568620 | Jan 2005 | CN |
| 1575603 | Feb 2005 | CN |
| 1592418 | Mar 2005 | CN |
| 1625880 | Jun 2005 | CN |
| 1698378 | Nov 2005 | CN |
| 1764974 | Apr 2006 | CN |
| 1784652 | Jun 2006 | CN |
| 1787422 | Jun 2006 | CN |
| 1902865 | Jan 2007 | CN |
| 1985321 | Jun 2007 | CN |
| 1988547 | Jun 2007 | CN |
| 101014947 | Aug 2007 | CN |
| 101018323 | Aug 2007 | CN |
| 101247511 | Aug 2008 | CN |
| 1 01 321 265 | Dec 2008 | CN |
| 1 01 371 307 | Feb 2009 | CN |
| 101365128 | Feb 2009 | CN |
| 101459809 | Jun 2009 | CN |
| 101518027 | Aug 2009 | CN |
| 101521583 | Sep 2009 | CN |
| 1 043 892 | Oct 2000 | EP |
| 1395014 | Jun 2006 | EP |
| 2117143 | Nov 2009 | EP |
| 06-252876 | Sep 1994 | JP |
| 200013761 | Jan 2000 | JP |
| 2000-341640 | Dec 2000 | JP |
| 2001-024994 | Jan 2001 | JP |
| 2001-359081 | Dec 2001 | JP |
| 2003-087737 | Mar 2003 | JP |
| 2003-111048 | Apr 2003 | JP |
| 2003-235031 | Aug 2003 | JP |
| 2004-013283 | Jan 2004 | JP |
| 2004-88766 | Mar 2004 | JP |
| 2004-135307 | Apr 2004 | JP |
| 2004-140584 | May 2004 | JP |
| 2004-140654 | May 2004 | JP |
| 2004-516717 | Jun 2004 | JP |
| 2004-186890 | Jul 2004 | JP |
| 2004-215074 | Jul 2004 | JP |
| 2004-312304 | Nov 2004 | JP |
| 2004-328204 | Nov 2004 | JP |
| 2005-039667 | Feb 2005 | JP |
| 2005-073138 | Mar 2005 | JP |
| 2005-229153 | Aug 2005 | JP |
| 2005-303927 | Oct 2005 | JP |
| 2006-304232 | Nov 2006 | JP |
| 2006-311328 | Nov 2006 | JP |
| 2007-11584 | Jan 2007 | JP |
| 2007-25959 | Feb 2007 | JP |
| 2007-036666 | Feb 2007 | JP |
| 2007-518294 | Jul 2007 | JP |
| 2007-274142 | Oct 2007 | JP |
| 2008-97381 | Apr 2008 | JP |
| 2008-219267 | Sep 2008 | JP |
| 2008-236667 | Oct 2008 | JP |
| 2009-17345 | Jan 2009 | JP |
| 2009-134700 | Jun 2009 | JP |
| 2009-159625 | Jul 2009 | JP |
| 2013-505680 | Feb 2013 | JP |
| 10-0805308 | Feb 2008 | KR |
| 20080044524 | May 2008 | KR |
| 10-2008-0099629 | Nov 2008 | KR |
| 10-2009-0001707 | Jan 2009 | KR |
| 10-2009-0028017 | Mar 2009 | KR |
| 1020090036765 | Apr 2009 | KR |
| 1020090063775 | Jun 2009 | KR |
| 100920733 | Oct 2009 | KR |
| 10-2010-0007368 | Jan 2010 | KR |
| 0249343 | Jun 2002 | WO |
| 2005043783 | May 2005 | WO |
| 2006105158 | Oct 2006 | WO |
| 2007095834 | Aug 2007 | WO |
| 2008130191 | Oct 2008 | WO |
| 2009119394 | Oct 2009 | WO |
| 2009158344 | Dec 2009 | WO |
| 2008062979 | Apr 2015 | WO |
| Entry |
|---|
| International Search Report (PCT/ISA/210) dated Mar. 28, 2012 in the International Patent Application No. PCT/KR2011/004064. |
| International Search Report issued by the International Searching Authority in counterpart International Application No. PCT/KR2011/001268 dated Nov. 25, 2011. |
| International Search Report dated Aug. 16, 2011 in counterpart international application No. PCT/KR2010/008060. |
| Written Opinion of the International Searching Authority dated Aug. 16, 2011 in counterpart international application No. PCT/KR2010/008060. |
| International Search report (PCT/ISA/210) dated Jul. 8, 2011 in the International Patent Application No. PCT/KR2010/008016. |
| International Search Report (PCT/ISA/210) dated Jul. 13, 2011 in the International Patent Application No. PCT/KR2010/008017. |
| International Search Report (PCT/ISA/210) dated Jul. 23, 2011 in the International Patent Application No. PCT/KR2010/008015. |
| International Search Report (PCT/ISA/210) dated Aug. 23, 2011 in the International Patent Application No. PCT/KR2010/008696. |
| International Search Report (PCT/ISA/210) dated Jul. 15, 2011 in the International Patent Application No. PCT/KR2010/008068. |
| International Search Report (PCT/ISA/210) and Written Opinion (PCT/ISA/237), dated Jul. 8, 2011, issued by the International Searching Authority in counterpart International Application No. PCT/KR2010/008016. |
| International Search Report (PCT/ISA/210) and Written Opinion (PCT/ISA/237), dated Nov. 3, 2011, issued by the International Searching Authority in counterpart International Application No. PCT/KR2011/001898. |
| Communication dated Feb. 7, 2014 issued by the European Patent Office in counterpart European Application No. 10830205.0. |
| Pantos R., et al., “HTTP Live Streaming; draft-pantos-http-live-straming-0.2.txt”, Oct. 5, 2009, 20 pgs. total, XP015064407. |
| Alex Zambelli, “IIS Smooth Streaming Technical Overview”, Mar. 31, 2009, 17 pgs. total, XP055009366. |
| Jin Young Lee et al., “DASH Evaluation Experiment #1: Compositions of Media Presentation (CMP) Proposal Comparison”, Oct. 15, 2010, 56 pgs. total, XP030046599. |
| Wager Zia, “A few comments on LGE proposal about delivery of MPEG-2-TS”, Oct. 15, 2010, 3 pgs. total, XP030047157. |
| Communication dated Feb. 12, 2014 issued by the European Patent Office in counterpart European Application No. 10830206.8. |
| Communication dated Feb. 12, 2014 issued by the European Patent Office in counterpart European Application No. 10830223.3. |
| Communication dated Feb. 25, 2014 issued by the European Patent Office in counterpart European Application No. 10830218.3. |
| Communication dated Mar. 4, 2014 issued by the European Patent Office in counterpart European Application No. 10830204.3. |
| Jaeyeon Song, et al., “Response to Call for Proposals for HTTP Streaming of MPEG Media standard”, Jul. 30, 2010, 60 pgs. total, XP030046369. |
| Gerard Fernando, et al., “HTTP Streaming Solution—Response to Call for Proposal”, Jul. 30, 2010, 32 pgs. total, XP030046346. |
| European Search Report dated Apr. 25, 2014 issued by the European Patent Office in counterpart European Application No. 10836186.6. |
| John A. Bocharov, “Smooth Streaming Technical Overview”, CM-IPTV0560, Oct. 20, 2009, 18 pgs. total, XP017826991. |
| Communication dated Apr. 25, 2014 issued by the European Patent Office in counterpart European Application No. 11747701.8. |
| Communication dated Apr. 25, 2014 issued by the European Patent Office in counterpart European Application No. 11756585.3. |
| Communication dated Feb. 18, 2014 issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Application No. 201080055449.8. |
| Communication dated Apr. 15, 2014 issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Application No. 201080061413.0. |
| Communication dated May 22, 2014 issued by the European Patent Office in counterpart European Application No. 11790033.2. |
| Communication dated Jul. 2, 2014 issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Application No. 201080061417.9. |
| Communication dated Jul. 3, 2014 issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Application No. 201180010793.X. |
| Communication dated Jul. 1, 2014 issued by the Japanese Patent Office in counterpart Japanese Application No. 2012-538764. |
| Communication dated Jul. 15, 2014 issued by the Japanese Patent Office in counterpart Japanese Application No. 2012-538765. |
| Communication dated Aug. 27, 2014, issued by the State Intellectual Property Office of the People's Republic of China in counterpart Chinese Application No. 201080061494.4. |
| Communication dated Aug. 4, 2014, issued by the State Intellectual Property Office of the People's Republic of China in counterpart Chinese Application No. 201080061416.4 |
| Communication dated Aug. 5, 2014, issued by the Japanese Patent Office in counterpart Japanese Application No. 2012-538771. |
| Communication dated Aug. 20, 2014, issued by the State Intellectual Property Office of the People's Republic of China in counterpart Chinese Application No. 201080061434.2. |
| Communication dated Aug. 5, 2014, issued by the Japanese Patent Office in counterpart Japanese Application No. 2012-538768. |
| Communication dated Aug. 19, 2014, issued by the Japanese Patent Office in counterpart Japanese Application No. 2012-543023. |
| Communication dated Sep. 24, 2014, issued by the Japanese Patent Office in counterpart Japanese Application No. 2012-553824. |
| Communication from the Japanese Patent Office dated Mar. 23, 2015 in a counterpart Japanese application No. 2012-553824. |
| Communication from the State Intellectual Property Office of P.R. China dated Mar. 17, 2015 in a counterpart application No. 201080061417.9. |
| Communication from the Japanese Patent Office dated Apr. 13, 2015 in a counterpart Japanese application No. 2012-538771. |
| Communication from the Japanese Patent Office dated Feb. 2, 2015 in a counterpart Japanese application No. 2012-538765. |
| Communication from the Japanese Patent Office dated Apr. 6, 2015 in a counterpart Japanese application No. 2012-538764. |
| “Transparent End-to-End Packet-Switched Streaming Service (PSS); Protocols and Codecs (Release 9)”, 3GPP TS 26.234, Mar. 2012, 188 pages total. |
| “Release 2 Specification HTTP Adaptive Streaming”, Open IPTV Forum, Sep. 2010, 25 pages total. |
| Communication dated Nov. 3, 2014, issued by the State Intellectual Property Office of the People's Republic of China in counterpart Chinese Application No. 201180014696.8. |
| Communication dated Dec. 19, 2014, issued by the Japanese Patent Office in counterpart Japanese Application No. 2012-543023. |
| Communication dated Mar. 24, 2015 issued by European Patent Office in counterpart European Application No. 11756585.3. |
| Communication from the State Intellectual Property Office of P.R. China dated Dec. 4, 2015 in a counterpart Chinese application No. 201080061494.4. |
| S. Bradner, “Key words for use in RFCs to Indicate Requirement Levels”, Network Working Group, Request for Comments: 2119, BCP: 14, Category: Best Current Practice, Harvard University, Mar. 1997, https://www.ietf.org/rfc/rfc2119.txt, pp. 1-3. |
| ETSI, “Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG-2 Transport Stream”, ETSI TS 101 154 V1.9.1 (Sep. 2009), Technical Specification, pp. 1-163. |
| ETSI, “Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks”, ETSI TS 102 034 V1.3.1 (Oct. 2007), Technical Specification, pp. 1-128. |
| ITU-T, “Series H: Audiovisual and Multimedia Systems Infrastructure of audiovisual services—Transmission multiplexing and synchronization”, Amendment 3: Transport of AVC video data over ITU-T Rec. H.222.0 | ISO/IEC 13818-1 streams, (Mar. 2004), ISO/IEC 13818-1:2000/Amd.3:2004 (E), International Telecommunication Union, total 26 pages. |
| International Standard, “Information technology—Coding of audio-visual objects—Part 12: ISO base media file format”, ISO/IEC 14496-12:2005(E), Second edition Apr. 1, 2005, Corrected version Oct. 1, 2005, total 93 pages. |
| International Standard, “Information technology—Coding of audio-visual objects—Part 14: MP4 file format”, ISO/IEC 14496-14:2003(E), First edition Nov. 15, 2003, total 18 pages. |
| International Standard, “Information technology—Coding of audio-visual objects—Part 15: Advanced Video Coding (AVC) file format”, ISO/IEC 14496-15:2004(E), First edition Apr. 15, 2004, total 29 pages. |
| ITU-T, “Series H: Audiovisual and Multimedia Systems Infrastructure of audiovisual services—Coding of moving video”, ITU-T Recommendation H.264, (Mar. 2005), International Telecommunication Union, total 382 pages. |
| International Standard, “Information technology—Generic coding of moving pictures and associated audio information—Part 2: Video”, ISO/IEC 13818-2:2013(E), Third edition Oct. 1, 2013, total 13 pages. |
| ETSI, “Digital Video Broadcasting (DVB); Subtitling systems”, ETSI EN 300 743 V1.3.1 (Nov. 2006), European Standard (Telecommunications series), pp. 1-51. |
| ETSI, “Digital Video Broadcasting (DVB); Specification for conveying ITU-R System B Teletext in DVB bitstreams”, ETSI EN 300 472 V1.3.1 (May 2003), European Standard (Telecommunications series), pp. 1-11. |
| International Standard, “Information technology—Coding of audio-visual objects—Part 3: Audio”, ISO/IEC 14496-3:2009(E), Fourth edition Sep. 1, 2009, total 18 pages. |
| ETSI, “Digital Audio Compression (AC-3, Enhanced AC-3) Standard”, ETSI TS 102 366 V1.2.1 (Aug. 2008), Technical Specification, pp. 1-214. |
| International Telecommunication Union, “Terminal Equipment and Protocols for Telematic Services”, Information Technology—Digital Compression and Coding of Continuous-Tone Still Images—Requirements and Guidelines, CCITT, Recommendation T.81, (Sep. 1992), ISO/IEC 10918-1 : 1993(E), total 186 pages. |
| International Standard, “Information technology—Coding of audio-visual objects—Part 2: Visual”, ISO/IEC 14496-2:2004(E), Third edition Jun. 1, 2004, total 18 pages. |
| ETSI, “Universal Mobile Telecommunications System (UMTS); LTE; Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs (3GPP TS 26.234 version 9.7.0 Release 9)”, ETSI TS 126 234 V9.7.0 (Jan. 2012), Technical Specification, total 191 pages. |
| ETSI, “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Transparent end-to-end packet switchedstreaming service (PSS); 3GPP file format (3GP) (3GPP TS 26.244 version 9.0.0 Release 9)”, ETSI TS 126 244 V9.0.0 (Jan. 2010), Technical Specification, total 54 pages. |
| Communication dated Jul. 9, 2015, issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Application No. 201180014696.8. |
| Communication dated Aug. 13, 2015, issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Application No. 201080061417.9. |
| Communication dated Aug. 5, 2015, issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Application No. 201180027573.8. |
| Communication dated May 18, 2015, issued by the State Intellectual Property Office of the People's Republic of China in counterpart Chinese Application No. 201080061494.4. |
| Communication dated Apr. 27, 2015 issued by the Japanese Patent Office in counterpart Japanese Patent Application No. 2012-538768. |
| Chen, et al., “Response to the CfP on HTTP Streaming: Adaptive Video Streaming based on AVC”, International Organization for Standardisation, MPEG Meeting, Jul. 26, 2010-Jul. 30, 2010, Issue No. M17909, pp. 1-20, Geneva, Switzerland, XP030046499. |
| Communication dated Apr. 1, 2016, issued by the State Intellectual Property Office of the People's Republic of China in counterpart Chinese Patent Application No. 201180027573.8. |
| Communication dated Apr. 25, 2016, issued by the European Patent Office in counterpart European Patent Application No. 10830204.3. |
| Communication dated May 9, 2016, issued by the European Patent Office in counterpart European Patent Application No. 11790033.2. |
| Anonymous, “OIPF Release 1 Specification Volume 2—Media Formats V 1.1” Open IPTV Forum, Oct. 8, 2009, 22 pages total. |
| Anonymous, “Open IPTV Forum—Functional Architecture—V 1.1” Open IPTV Forum, Jan. 15, 2008, 141 pages total. |
| Anonymous, “OIPF Release 1 Specification Volume 3—Content Metadata V 1.1”, Open IPTV Forum, Oct. 8, 2009, 47 pages total. |
| Communication dated Oct. 3, 2016, issued by the Japanese Patent Office in counterpart Japanese Patent Application No. 2012-553824. |
| Communication dated Oct. 31, 2016, issued by the Korean Intellectual Property Office in counterpart Korean Patent Application No. 10-2010-0103721. |
| Communication dated Oct. 31, 2016, issued by the Korean Intellectual Property Office in counterpart Korean Patent Application No. 10-2010-0103722. |
| Communication dated Nov. 7, 2016, issued by the Japanese Patent Office in counterpart Japanese Patent Application No. 2015-167763. |
| Communication dated Dec. 19, 2016, issued by the Japanese Patent Office in counterpart Japanese Patent Application No. 2015-156368. |
| Alex Zambelli, “IIS Smooth Streaming Technical Overview”, Microsoft Corporation, Mar. 2009, pp. 1-17. |
| Communication dated Jul. 15, 2016, issued by the Korean Intellectual Property Office in counterpart Korean application No. 10-2010-0103727. |
| Communication dated Aug. 15, 2016, issued by the Japanese Patent Office in counterpart Japanese application No. 2015-156368. |
| Communication dated Sep. 12, 2016, issued by the Japanese Patent Office in counterpart Japanese application No. 2012-538764. |
| Communication dated Aug. 1, 2016, issued by the State Intellectual Property Office of P.R. China in counterpart Chinese application No. 201080061494.4. |
| Communication dated Aug. 29, 2016, issued by the Japanese Patent Office in counterpart Japanese application No. 2015-159842. |
| Communication dated Aug. 29, 2016, issued by the Japanese Patent Office in counterpart Japanese application No. 2012-538771. |
| Qualcomm Incorporated, et al., “3GPP Adaptive HTTP Streaming”, Proposal to MPEG HTTP Streaming, 93rd MPEG meeting, Geneva, XP030001643, Jul. 22, 2010, pp. 1-61. |
| Qualcomm Incorporated, “Adaptive HTTPStreaming: Usage of the 3GPP File Format”, 3GPP TSG-SA4 AHI Meeting, SA-AHI172, Mar. 2-4, 2010, Aachen, Germany, XP050437444, pp. 1-8. |
| Communication dated Sep. 29, 2016, issued by the European Patent Office in counterpart European Application No. 11747701.8. |
| Qualcomm Incorporated, “Pseudo CR: Adaptive HTTP Streaming—Full Solution Proposal”, 3GPP TSG-SA4 #57, S4-100060, Jan. 25-29, 2010, St Julians, Malta, URL:http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/TSGS4_57/Docs/S4-100060.zip, total 17 pages. |
| Communication dated Sep. 26, 2016, issued by the Japanese Patent Office in counterpart Japanese application No. 2015-146132. |
| Huawei Technologies Co., Ltd., “Live Content Support in Static HTTP Streaming”, 3GPP TSG-SA4 #56, S4-090857, Nov. 9-13, 2009, Sophia-Antipolis, URL:http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/TSGS4_56/Docs/S4-090857.zip France, total 6 pages. |
| Communication dated Jan. 19, 2017, issued by the Korean Intellectual Property Office in counterpart Korean Patent Application No. 10-2010-0103725. |
| Communication dated Jan. 30, 2017, issued by the Japanese Patent Office in counterpart Japanese Patent Application No. 2015-146132. |
| Communication dated Feb. 21, 2017, issued by the Korean Intellectual Property Office in counterpart Korean Patent Application No. 10-2010-0103698. |
| Communication dated Mar. 15, 2017, issued by the Korean Intellectual Property Office in counterpart Korean Patent Application No. 10-2011-0011110. |
| Communication dated Mar. 28, 2017, issued by the State Intellectual Property Office of the People's Republic of China in counterpart Chinese Patent Application No. 201080061494.4. |
| Communication dated Sep. 29, 2018, issued by the China National Intellectual Property Administration in counterpart Chinese Application No. 201080061494.4. |
| Communication dated May 30, 2018, issued by the State Intellectual Property Office of P.R. China in counterpart Chinese Application No. 201080061494.4. |
| Number | Date | Country | |
|---|---|---|---|
| 20110119395 A1 | May 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61380461 | Sep 2010 | US | |
| 61380477 | Sep 2010 | US | |
| 61318916 | Mar 2010 | US | |
| 61314233 | Mar 2010 | US | |
| 61267131 | Dec 2009 | US | |
| 61262708 | Nov 2009 | US | |
| 61260906 | Nov 2009 | US |
