US20190124132A1 - Apparatus and method for providing streaming content - Google Patents
Apparatus and method for providing streaming content Download PDFInfo
- Publication number
- US20190124132A1 US20190124132A1 US16/228,097 US201816228097A US2019124132A1 US 20190124132 A1 US20190124132 A1 US 20190124132A1 US 201816228097 A US201816228097 A US 201816228097A US 2019124132 A1 US2019124132 A1 US 2019124132A1
- Authority
- US
- United States
- Prior art keywords
- baseurl
- elements
- media
- url
- metadata
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 230000003044 adaptive effect Effects 0.000 abstract description 12
- 238000013507 mapping Methods 0.000 abstract description 10
- 238000012546 transfer Methods 0.000 abstract description 2
- 239000012634 fragment Substances 0.000 description 34
- 238000001824 photoionisation detection Methods 0.000 description 21
- 230000011664 signaling Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 11
- 230000006978 adaptation Effects 0.000 description 6
- 239000012092 media component Substances 0.000 description 5
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000002123 temporal effect Effects 0.000 description 3
- 238000009877 rendering Methods 0.000 description 2
- 101100194362 Schizosaccharomyces pombe (strain 972 / ATCC 24843) res1 gene Proteins 0.000 description 1
- 101100194363 Schizosaccharomyces pombe (strain 972 / ATCC 24843) res2 gene Proteins 0.000 description 1
- 206010041235 Snoring Diseases 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H04L29/06027—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H04L65/4084—
-
- H04L65/607—
-
- H04L65/608—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/70—Media network packetisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/234—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs
- H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
- H04N21/23439—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements for generating different versions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
- H04N21/26258—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists for generating a list of items to be played back in a given order, e.g. playlist, or scheduling item distribution according to such list
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/47—End-user applications
- H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
- H04N21/47202—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for requesting content on demand, e.g. video on demand
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
- H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6156—Network physical structure; Signal processing specially adapted to the upstream path of the transmission network
- H04N21/6175—Network physical structure; Signal processing specially adapted to the upstream path of the transmission network involving transmission via Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/65—Transmission of management data between client and server
- H04N21/658—Transmission by the client directed to the server
- H04N21/6581—Reference data, e.g. a movie identifier for ordering a movie or a product identifier in a home shopping application
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
- H04N21/84—Generation or processing of descriptive data, e.g. content descriptors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/85—Assembly of content; Generation of multimedia applications
- H04N21/854—Content authoring
- H04N21/8543—Content authoring using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/4302—Content synchronisation processes, e.g. decoder synchronisation
- H04N21/4305—Synchronising client clock from received content stream, e.g. locking decoder clock with encoder clock, extraction of the PCR packets
Definitions
- the present invention relates to a technology for providing streaming content, and more particularly, to an apparatus and method for providing media content using adaptive streaming.
- Streaming is one of schemes for transmitting and playing back multimedia content such as sounds, moving images, and the like.
- a client may play back content while receiving the content through the streaming.
- An adaptive streaming service refers to providing a streaming service employing a communication scheme with a request of a client and a response of a server in response to the request.
- the client may request a media sequence suitable for an environment of the client (for example, a transmission channel of the client), using the adaptive streaming service.
- the server may provide a media sequence matched to the request of the client among media sequences with various qualities that are included in the server.
- the adaptive streaming service may be provided based on various protocols.
- a Hypertext Transfer Protocol (HTTP) adaptive streaming service refers to an adaptive streaming service provided based on an HTTP protocol.
- a client of the HTTP adaptive streaming service may receive content from a server using the HTTP protocol, and may transmit a request associated with a streaming service to the server.
- An aspect of the present invention provides an apparatus and method that may interpret a Uniform Resource Locator (URL) of a segment using one or more BaseURL elements during playback of content.
- URL Uniform Resource Locator
- Another aspect of the present invention provides an apparatus and method that may generate a URL of a segment by mapping a BaseURL element among one or more BaseURL elements to a sourceURL attribute of the segment.
- a method for providing media including: receiving metadata of media, the metadata including one or more BaseURL elements; sending a request for a segment of the media using a Uniform Resource Locator (URL) of the segment, the URL being resolved with respect to a BaseURL element; receiving the segment; and decoding and rendering data of the media that is included in the segment.
- URL Uniform Resource Locator
- the request may be sent using an HTTP GET method.
- the metadata may include a range attribute.
- the request may include a request for bytes of a resource indicated by the URL that are designated by the range attribute.
- the URL may be an absolute URL or a relative URL.
- Identical segments may be accessible at multiple locations indicated by URLs resolved with respect to the respective BaseURL, elements.
- a first BaseURL element among the BaseURL elements may be used as a basic Universal Resource Indicator (URI), and BaseURL elements other than the first BaseURL element may be used as alternative BaseURL elements.
- URI Universal Resource Indicator
- the metadata may selectively include a sourceURL attribute of the segment.
- a BaseURL element among the BaseURL elements may be mapped to the sourceURL attribute, so that the URL may be generated.
- the metadata may be a Media Presentation Description (MPD) of the media.
- MPD Media Presentation Description
- the media may include a sequence of one or more periods.
- a BaseURL element may include one or more MPD level BaseURL elements of the MPD, and one or more period level BaseURL, elements of the periods.
- a URL of a segment included in each of the periods may be resolved with respect to a period level BaseURL element.
- the period level BaseURL elements may be resolved with respect to the MPD level BaseURL elements.
- Each of the periods may include one or more groups.
- the BaseURL element may further include one or more group level BaseURL elements of the groups.
- a URL of a segment included in each of the groups may be resolved with respect to a group level BaseURL element.
- the group level BaseURL elements may be resolved with respect to the period level BaseURL elements.
- Each of the groups may include one or more representations.
- Each of the representations may be a structured collection of one or more components of the media within a period.
- the BaseURL element may further include one or more representation level BaseURL elements of the representations
- a URL of a segment included in each of the representations may be resolved with respect to a representation level BaseURL element.
- the representation level BaseURL elements may be resolved with respect to the group level BaseURL elements or the period level BaseURL elements.
- a terminal including: an access engine to receive metadata of media, to send a request for a segment of the media using a Uniform Resource Locator (URL) of the segment, to receive the segment, and to decode data of the media that is included in the segment, the metadata including one or more BaseURL elements, and the URL being resolved with respect to a BaseURL element; and a media engine to receive the data of the media from the access engine, and to output the media.
- an access engine to receive metadata of media, to send a request for a segment of the media using a Uniform Resource Locator (URL) of the segment, to receive the segment, and to decode data of the media that is included in the segment, the metadata including one or more BaseURL elements, and the URL being resolved with respect to a BaseURL element
- a media engine to receive the data of the media from the access engine, and to output the media.
- URI Uniform Resource Locator
- FIG. 1 is a diagram illustrating categories of signaling information according to an embodiment of the present invention.
- FIG. 2 is a diagram illustrating categories of signaling information according to an embodiment of the present invention.
- FIG. 3 is a diagram illustrating a hierarchy of content division and levels of signaling information according to an embodiment of the present invention.
- FIG. 4 is a diagram illustrating detection of virtual boundaries in a Moving Picture Experts Group-2 Transport Stream (MPEG-2 TS) according to an embodiment of the present invention.
- MPEG-2 TS Moving Picture Experts Group-2 Transport Stream
- FIG. 5 is a diagram illustrating a configuration of a terminal 100 according to an embodiment of the present invention.
- FIG. 6 is a diagram illustrating a configuration of a terminal 100 according to an embodiment of the present invention.
- a Dynamic Adaptive Streaming over HTTP may specify formats that enable 1) delivery of media content from an HTTP server to an HTTP client, and enable 2) caching of content by standard HTTP cashes.
- a media component may be an encoded version of individual media types, such as audios, videos, or timed texts with specific attributes, for example bandwidths, languages, or resolutions.
- Media content may be a set of media components having a common timeline, for example audios, videos, or timed texts. Additionally, media components may have relationships on how the media components may be presented (for example, individually, jointly, or mutually exclusive) as programs or movies.
- a media presentation may be a structured collection of data used to establish bounded or unbounded presentation of media content including components of continuous media.
- the media presentation may be a structured collection of data that is accessible to a DASH client in order to provide a streaming service to a user.
- a Media Presentation Description may be a formalized description for a media presentation.
- the media presentation may be described by an MPD including possible updates of the MPD.
- Content may be content on demand, or live content.
- the content may be divided into one or more intervals.
- the content may include one or more intervals.
- Intervals may be interchangeable with periods.
- the term period may be used as a term of 3 rd Generation Partnership Project (3GPP) adaptive HTTP streaming.
- 3GPP 3 rd Generation Partnership Project
- a period may be an interval of a media presentation.
- a continuous sequence of all periods may constitute the media presentation.
- the media presentation may include a sequence of one or snore periods.
- One or more intervals may be a basic unit.
- One or more intervals may be described by signaling metadata.
- metadata may describe each of the one or more intervals.
- the metadata may be an MPD.
- the MPD may define a format to announce resource identifiers for segments.
- the MPD may provide a context for identified resources within the media presentation.
- the resource identifiers may be HTTP-Uniform Resource Locators (URLs). URLs may be restricted by a byte range attribute.
- Each interval may be divided into fragments.
- Fragments may be interchangeable with segments.
- the term segment may be used as a term of 3GPP adaptive HTTP streaming.
- a segment may refer to an entity body of a response to an HTTP/1.1 GET request for an HTTP-URL, for example as defined in RFC 2616 , (or a GET request for a part indicated by a byte range).
- a terminal may play back media content using received bytes (namely, a segment).
- a sub-segment may refer to a smallest unit within segments that may be indexed by a segment index at the segment level.
- Two or more sets of fragments corresponding to a single interval may exist. Each of the sets may be called an alternative.
- Each period may include one or more groups.
- Each group may include one or more representations of the same media content.
- a representation may refer to a structured collection of one or more media components within a single period.
- a representation may be one of alternative choices of the media content or a subset of the media content typically differing by the encoding choice, for example by a bitrate, a resolution, a language, a codec, and the like.
- An MPD (or an MPD element) may provide descriptive information that enables a client to select one or more representations.
- a Random Access Point may be a specific location in a media segment.
- the RAP may be identified as a location in which playback may be started continuously from a location of the RAP using only information included in a media segment.
- Each representation may be formed of one or more segments.
- a representation may include one or more segments.
- An MPD may be a document including metadata required to a DASH client to form appropriate HTTP-URLs in order to 1) access segments and to 2) provide a user with a streaming service.
- the HTTP-URLs may be absolute or relative.
- the MPD may be an Extensible Markup Language (XML)-document.
- XML Extensible Markup Language
- the MPD may include an MPD element.
- the MPD may include only a single MPD element.
- FIG. 1 is a signal flowchart illustrating a content processing method according to an embodiment of the present invention.
- a terminal 100 may be a DASH client.
- the DASH client may be compatible with a client specified in RFC 2616 .
- the DASH client may typically use an HTTP GET method or an HTTP partial GET method, as specified in RFC 2616 , to access segments or parts of segments.
- a server 110 may perform hosting on DASH segments.
- the server 110 may be compatible with a server specified in RFC 2616 .
- the terminal 100 may receive metadata of media (or content) from the server 110 .
- the server 110 may transmit the metadata of the media to the terminal 100 .
- the metadata may include BaseURL elements. One or more BaseURL elements may be provided.
- the terminal 100 may process the received metadata. In operation 130 , the terminal 100 may extract information provided by the metadata, or information included in the metadata.
- the terminal 100 may access a segment of the media based on the information provided by the metadata.
- Each period may include one or more groups, and each of the groups may include one or more representations of the media. Each of the representations may include one or more segments.
- the metadata may describe a group element describing each of the groups.
- the terminal 100 may send a request for a segment of the media to the server 110 using a URL of the segment.
- the URL may be resolved with respect to one of the above-described BaseURL elements.
- the URL of the segment may be generated based on a BaseURL element.
- the terminal 100 may request the server 110 to transmit a segment suitable for a specific interval based on the processed metadata.
- the requested segment may be selected based on the metadata.
- the request may be sent using the HTTP GET method.
- the metadata may include a range attribute.
- the request may include a request for bytes of a resource indicated by a URL that are designated by the range at tribute.
- the URL of the segment may be an absolute URL or a relative URL.
- Identical segments may be accessible at multiple locations indicated by URLs resolved with respect to the respective BaseURL elements. In other words, identical segments may be selectively accessible by the URLs provided by the BaseURL elements.
- a first BaseURL element among the BaseURL elements may be used as a basic Universal Resource Indicator (URI), and BaseURL elements other than the first BaseURL element may be used as alternative BaseURL elements.
- URI Universal Resource Indicator
- the metadata may selectively include a sourceURL attribute of the segment.
- a BaseURL element among the BaseURL elements may be mapped to the sourceURL attribute, so that the URL of the segment may be generated.
- the server 110 may need to parse content (for example, a Moving Picture Experts Group (MPEG) layer 4 (MP4) file for Scalable Video Coding (SVC)), and may extract a data part suitable for the requested segment.
- MPEG Moving Picture Experts Group
- MP4 Scalable Video Coding
- the server 110 may transmit, to the terminal 100 , segments suitable for each request from the terminal 100 .
- the terminal 100 may receive the segments from the server.
- the terminal 100 may perform decoding and rendering on data of the media included in the segment, to play back the media.
- the terminal 100 may play back the media using the received segments by repeating operations 120 through 160 .
- a BaseURL element may include an MPD level BaseURL element of an MPD, and a period level BaseURL element of each period.
- the period level BaseURL element may refer to a BaseURL element applied to a period to which the period level BaseURL element belongs.
- a URL of a segment included in each period may be resolved with respect to the period level BaseURL element.
- One or more MPD level BaseURL elements may be provided, and one or more period level BaseURL elements may be provided.
- the BaseURL element may further include a group level BaseURL element of a group.
- a URL of a segment included in each group may be resolved with respect to the group level BaseURL element.
- One or more group level BaseURL elements may be provided.
- the BaseURL element may further include a representation level BaseURL element of a representation.
- a URL of a segment included in each representation may be resolved with respect to the representation level BaseURL element.
- a BaseURL element of a specific level may be resolved with respect to a BaseURL element of a higher level.
- a period level BaseURL element may be resolved with respect to an MPD level BaseURL element.
- a group level BaseURL element may be resolved with respect to a period level BaseURL element.
- a representation level BaseURL element may be resolved with respect to a group level BaseURL element or a period level BaseURL element.
- FIG. 2 is a diagram illustrating categories of signaling information according to an embodiment of the present invention.
- the signaling information (namely, metadata) may be divided into the following categories 1) through 4):
- General information 210 includes common description of content, and general description of each interval, such as a duration, and a start time.
- QoS information 220 describes characteristics of each alternative, such as a bitrate, a resolution, and a quality.
- the QoS information describes characteristics of each of alternatives of content.
- An alternative may be physical (namely, created in advance), or may be virtual (namely, to be created on the fly). Based on information of alternatives, the client may select a fragment of an appropriate alternative. Accordingly, adaptivity to contexts of terminals and networks may be supported.
- Mapping information 230 describes locations to retrieve content. Depending on specific cases, different alternatives may have the same or different locations.
- Client request 240 this type of signaling information may conform to a format of HTTP 1.1 request message. As shown in FIG. 1 , parameters requested by the client may be derived from the information of categories 1) through 3).
- FIG. 3 is a diagram illustrating a hierarchy of content division and levels of signaling information according to an embodiment of the present invention.
- Signaling of metadata may be physically separated into content-level information 310 , interval-level information 320 , QoS information 330 , and mapping information 340 .
- Linking of related parts of the content-level information 310 , the interval-level information 320 , the QoS information 330 , and the mapping information 340 may be performed by reference.
- a processing model may be “server-based.”
- the model may be “distributed.”
- the model may be client-based, because most (or all) processing (namely, computations for deciding alternatives and resolving locations) is performed by the client.
- the separation of metadata parts may enable efficiency in storage and delivery. For example, during a session, metadata of the content-level information 310 may be sent once, and only the interval-level information 320 may be periodically updated. Similarly, a single file containing the QoSInfo 330 may be used for different intervals and different contents.
- both XML and pseudo-code may be used to represent signaling syntax.
- XML syntax may be used for clients that support an XLM profile based on an MPEG-21 and similar schema.
- pseudo-code syntax may be based on a “language” of an International Organization for Standardization (ISO) base media file format and the like, and may be used in non-XML clients.
- a profile of the pseudo-code syntax may employ a parsing module similar to a parsing module of file-format parsing.
- a table of common elements may be defined and elements in each format may be represented, in the following embodiments.
- the proposed syntax may be represented by any other languages.
- a child element may be shown in a column on the right of a parent element of the child element.
- “Leaf”-level elements may be shown in italic, and parent elements may be shown in bold letter.
- a parent element may be represented by a corresponding XML type and a file box.
- 0 . . . N may mean that the number of instances of an occurrence element may be from 0 to “unbounded.”
- the minimum occurrence of 0 may mean that an element may be optional (namely, not present).
- a minimum occurrence equal to or greater than 1 may mean that an element is mandatory in the syntax.
- Occurrence may be interchangeable with cardinality.
- A indicates an attribute
- F indicates an element.
- M indicates mandatory
- O indicates optional.
- M indicates mandatory
- O indicates optional
- OD indicates optional with default value
- CM indicates conditionally mandatory.
- elements may be represented as ⁇ minOccurs> . . . ⁇ maxOccurs>.
- N may be unbounded.
- QoSInfo may be also called AdaptationInfo to make QoSInfo more specific. Moreover, a few elements may be revised to increase flexibility of the syntax.
- HttpStr 1 Describes the top-level element of HttpStreamingType ‘htps’ box signaling metadata for HTTP streaming GeneralInfo 0 . . . N Contains the general information of GeneralInfoType ‘geni’ box the described content
- TimeScale 0 . . . 1 Describes the number of time units integer unsigned int(32) in 1 second. This value is used with time-related elements, when a time unit is not specified.
- LiveStartTime 0 . . . 1 If LiveStartTime element is not dateTime unsigned int(64) present, the content is of VoD type.
- LiveStartTime element indicates a live content that is to be displayed at a time value of LiveStartTime. If LiveStartTime has a time value of 0, the display time is unknown. Duration 0 . . . 1 If present, indicates duration of the integer unsigned int(32) content. Otherwise, the duration is unknown. DefaultIntDuration 0 . . . 1 If present, indicates a default integer unsigned int(32) duration of each interval of the content. MinUpdateTime 0 . . . 1 If present, indicates the minimum integer unsigned int(32) waiting time before requesting the main description file again. ConsistentQoSInfo 0 . . .
- IntervalsRef 0 . . . N Provides reference to description IntervalsRefType ‘iref’ box containing one or more instances of Interval element. One or more instances of Interval element represent a sequence of consecutive interval(s).
- Interval 0 . . . N Provides information of an interval IntervalType ‘intv’ box of content. The information of the interval may be either included as an instance of Interval element or referenced by IntervalsRef element.
- QoSInfoRef 0 . . . 1 Provides reference to description dia: ReferenceType ‘qref’ box represented by QoSInfo element. If QosInfoRef element is present, QoSInfo element may not be present at the same level.
- QoSInfo 0 . . . 1 Provides information about QoSInfoType ‘QoSi’ box alternatives of content, such as resource characteristics and quality/utility. If QoSInfo element is present, QoSInfoRef element may not be present.
- MappingInfoRef 0 . . . 1 Provides reference to description dia: ReferenceType ‘mref’ box represented by MappingInfo element.
- MappingInfoRef element may not be present at the same level.
- MappingInfo 0 . . . 1 Provides information about MappingInfoType ‘mapi’ box locations of content alternatives. If the information is not provided, DefaultContentIntLoc element (if not, DefaultContentLoc) can be used to retrieve content. If MappingInfo element is present, MappingInfoRef element may not be present.
- NextIntervalsRef 0 . . . 1 Provides reference to information of IntervalsRefType, ‘nref’ box next interval(s). may be extended from The information of next interval(s) dia: ReferenceType is description containing one or more instances of Interval element.
- next interval(s) is description represented by Interval element.
- NextIntervalsRef element the client does not need to reload the main description represented by HttpStr element. Within the current time window, only the final interval may contain NextIntervalsRef element.
- PreviousIntervalsRef 0 . . . 1 Provides reference to information of IntervalsRefType, ‘nref box previous interval(s). may be extended from The information of next interval(s) dia: ReferenceType is description containing one or more instances of Interval element.
- the information of next interval(s) is description represented by Interval element.
- PreviousIntervalsRef element the client does not need to reload the main description represented by HttpStr element. Within the current time window, only the first interval may contain NextIntervalsRef element.
- QoSInfoRef (based on code (File Ocurrence Semantics MPEG-21) format box)
- QoSInfoRef, Mapping- InfoRef Index 1 Indicates the order (starting from 1) of not unsigned the referenced description or box applicable int(8) (Interval, QoSInfo, MappingInfo) in the description file referenced by the next Location element.
- Location 1 Provides reference to description uri element string represented by Interval, QoSInfo, or in dia: (representing MappingInfo. ReferenceType url)
- IntervalInfo TimeScale 0 . . . 1 Describes the number of time units in integer unsigned one second. This value is used with int(32) time-related elements, when a time unit is not specified.
- TimeScale element if present, overrides the time scale provided by GeneralInfo.
- StartTime 0 . . . 1 Indicates the start tune of the interval.
- Duration 0 . . . 1 Indicates the duration of the interval.
- Default- 0 . . . 1 Provides a default location for the anyURI type string ContentInt- content interval.
- Loc Last 0 . . . 1 If true, indicates the final interval of the boolean by flag content.
- IntervalsRef, Previous- Intervals- RefNext- IntervalRef startTime Indicates the start time of the referenced xs: duration sequence of intervals/periods relative to the start time of the content (LiveStartTime for live content and 0 for on-demand content). AvailableTime 0 . . . 1 Indicates the time the description of the integer unsigned next interval is available. The is the int(32) relative time from the start time of the content. Index 1 Indicates the order (starting from 1) of not unsigned the referenced interval description (or applicable int(8) box) in the description file referenced by the next Location element. Location 1 Provides reference to description file sx: anyURI string that contains Interval descriptions. type or uri (representing element in dia: url) ReferenceType
- QoSInfo 1 Provides information about a list of QoSInfoType containing a ‘QoSi’ box content alternatives, such as UtlityFunction of dia: resource characteristics and AdaptiveQoSType quality/utility.
- ClassSchemeRef 0 . . . 1 Provides a list of classification dia: DescriptionMetadataType ‘csmr’ box schemes. The classification schemes provide semantics for some terms or names.
- scheme 1 . . . N Provides reference to a Attr. alias & href in dia: a url string classification scheme.
- Each instance of Utility element dia: UFDataType ‘util’ box describes, for a list of alternatives, values in a certain quality/utility type (e.g., MOS).
- UtilityRank 0 . . . 1 Describes the quality ranking for a dia: UtilityRankType ‘utir’ box list of alternatives.
- Value 1 . . . N Indicates the quality/utility rank of integer unsigned int(16) an alternative. The number of instances of Value element is equal to the number of alternatives.
- Table 4 shows common semantics of (1) Resource, (2) AdaptationOperator, and (3) Utility of Table 3.
- QoSInfo 1 Provides information about a list QoSInfoType containing a ‘QoSi’ box of content alternatives, such as UtilityFunction of dia: resource characteristics and AdaptiveQoSType quality/utility.
- ClassSchemeRef 0 . . . 1 Provides a list of classification dia: DescriptionMetadataType ‘csmr’ box schemes. The classification schemes provide semantics for some terms or names.
- scheme 1 . . . N Provides reference to a Attr. alias & href in dia: a url string classification scheme.
- Utility element dia UFDataType ‘util’ box describes, for a list of alternatives, values in a certain quality/utility type (e.g., MOS).
- UtilityRank 0 . . . 1 Describes the quality ranking for a dia: UtilityRankType ‘utir’ box list of alternatives.
- Value 1 . . . N Indicates the quality/utility rank of integer unsigned int(16) an alternative. The number of instances of Value element is equal to the number of alternatives.
- Pseudo-code Element XML syntax (based (File format (1), (2), (3) Semantics on MPEG-21) box) Name 1 Describes an identifier for a Att. ‘iOPinRef’, ref.
- CSref_ind 0 . . . 1 Indicates the reference index of a Not applicable unsigned int(16) classification scheme in the list provided by ClassSchemeRef element.
- LevelNum 0 . . . 1 Indicates the number of levels.
- Not applicable unsigned int(16) LevelIndex 1 . . . N
- Each instance of LevelIndex Not applicable unsigned int(16) element represents an index value at a level of the classification scheme.
- Value 1 . . . N Indicates the value of a resource a component in dia: unsigned int(32) type (adaptation operator, or VectorDataType utility) of an alternative.
- the number of instances of Value element is equal to the number of alternatives.
- MappingInfo 0 . . . 1 Mapping ‘mapi’box InfoType AlterLocID 0 . . . 1 Provides a location ID for each dia:Integer ‘aloc’ alternative described in QoSInfo.
- Vector box If AlterLocID element is not Type present, the first location in the location list may be used for all alternatives. Value 1 . . . N Indicates a location ID for an integer unsigned alternative. int(16) The number of instances of this element is equal to the number of alternatives.
- n th instance of Value element corresponds to the n th alternative of QoSInfo description.
- ReqQoSPara 0 . . . N Indicates a parameter of QoSInfo ReqQoS ‘reqp’ that may be put in the request (for ParaType box an alternative) sent by the client to that the server.
- a parameter may be an instance of dia:Boolean Resource, AdaptationOperator, Vector Utility, or UtilityRank elements.
- Type RefIndex 1 Indicates instance index/reference represented unsigned in the instance list of Resource, by int(16) AdaptationOperator, Utility and attribute UtilityRank elements.
- ReqFlag 0 . . . N
- LocationList 1 Provides a list of locations for Location ‘locl’ retrieving content alternatives
- ListType box Location 1 . . . N Provides information of a location Location ‘loca’ Type box
- Semantics of Location elements may be further provided as shown in Table 6,
- anyURItype string FragmentUrl 0 . . . N Describes a URL of a fragment. anyURItype string
- the number of instances of FragmentUrl element is the number of fragments.
- FragTime 0 . . . 1 Provides durations of dia:VectorDataType ‘frtm’ fragments.
- box Value 1 . . . N Indicates a duration of a integer unsigned fragment. int(32)
- the number of instances of Value element is the number of fragments. RandAccess 0 . . . 1 Describes fragments that dia:VectorDataType ‘rdac’ support random access. box Value 1 . . .
- MP2TSPara 0 . . . 1 Describes additional parameters MP2TSParaType ‘mp2p’ (beside URL) for locating a box content/program in a MPEG-2 TS.
- PID 0 . . . N Describes values of PIDs of integer unsigned content/program in a MPEG-2 int(16) TS.
- FragBoundaries 0 . . . 1 Describes boundaries of FragBoundariesType ‘frbd’ (virtual) fragments in a stream. box The number of instances of FragBoundaries element is equal to the number of fragments of the stream.
- MP2TSBoundary 0 . . . N Describes parameters for MP2TSBoundaryType ‘mp2b’ detecting (virtual) fragment box boundary in a MPEG-2 TS. If there are two instances of MP2TSBoundary element, the two instances are starting and ending boundaries of a fragment. If there is only one instance of MP2TSBoundary element, the instance is the starting boundary. The ending boundary is right before the starting boundary of the next fragment.
- PCR_PID 1 Describes PID carrying PCR of the integer unsigned concerned content/program.
- PCR_base 1 Describes a value of a PCR base long unsigned field int(40)
- PCR_ext 1 Describes a value of a PCR integer unsigned extension field.
- int(16) Appearance 1 Describes the appearance order integer unsigned (e.g., 1 st , 2 nd ) of the TS packet int(16) containing the PCR value identified by the above two elements.
- a PCR value may appear more than once during an interval.
- Media_PID 1 . . . N Describes PID of a media (e.g., integer unsigned video) of a program. int(16) The number of instances of Media_PID element is equal to the number of media of the program/content.
- Media_Offset 1 . . . N Describes the offset (in TS packets integer unsigned of the same media PID) from the int(16) above identified PCR packet to the first media packet of a fragment. The n th instance of Media_Offset is associated with the n th instance of Media_PID.
- a value of ′ ⁇ 1′ means that this value in the HTTP request is missing.
- Start-End instances are present in pair.
- the n th instance of End is associated with the n th instance of Start.
- Media_PID 0 . . . N Describes PID of a media (e.g., integer unsigned video) that needs to be extracted int(16) from the byte range of the above pair of Start-End.
- Media_PID element is used when the byte range is a segment of MPEG-2 TS, and all PTDs do not need to be delivered.
- Signaling of metadata obtained by a client may include different parts or levels of signaling information. Accordingly, a request from the client to a server may include parameters of different levels of details.
- Main parameters of the client may be URIs, and may be associated with a query part.
- the metadata provided from the server to the client may include general content information 310 and general interval information 320 .
- DefaultContentIntLoc (if not, DefaultContentIntLoc) may be used.
- the following parameters a) and b) are defined in the query part (of the request in operation 140 ):
- the metadata provided from the server to the client may include general content information 310 , general interval information 320 , and QoS information 330 .
- QoS-related parameters a) through c) are defined in the query part (of the request in operation 140 ) to enable the client to request an appropriate alternative:
- Adaptation operators are as the following a) through e).
- a) audiolayers indicates the number of scalable audio layers to be discarded.
- temporallayers indicates the number of temporal layers of scalable video to be discarded.
- c) spatiallayers indicates the number of spatial layers of scalable video to be discarded
- qualitylayers indicates the number of quality layers of scalable video to be discarded
- prioritylayers indicates the number of priority layers of scalable video to be discarded.
- Resource types are as the following a) through d).
- bitrate indicates the average bitrate (in Kbps) of the requested alternative.
- vertresolution indicates the vertical resolution of the requested alternative.
- c) horiresolution indicates the horizontal resolution of the requested alternative.
- d) fratnerate indicates the framerate of the requested alternative.
- the metadata provided from the server to the client may include general content, general interval information, QoS information, and mapping information.
- the QoS-related parameters used in the request may be indicated by a ReqQoSPara part of QoSInfo metadata.
- ReqQoSPara part of QoSInfo metadata.
- the “alter” parameter may be used instead of other options,
- the QoS-related parameters may not be used. Alternatives in this case may be implied by locations of MappingInfo.
- a URI of content may be derived from rich description of MappingInfo.
- PIDs may be used to locate the content in the stream.
- the following parameters 1) through 3) for the query part (of the request in operation 140 ) may be used.
- Semantics of the above parameters may be provided in semantics of a FragBoundaries element.
- Table 8 shows syntax representation of HTTPStreamingType in the XML format.
- Table 9 shows syntax representation of GeneralInfoType in the XML format.
- Table 10 shows syntax representation of IntervalRefType in the XML format.
- Table 11 shows syntax representation of IntervalType in the XML format.
- Table 12 shows syntax representation of IntervalInfoType in the XML format.
- Table 13 shows syntax representations of ISOFileBoundaryType and ByteRangesType in the XML format.
- Table 14 shows syntax representation of HTTPStreamingBox in the MP4 pseudo-code format.
- HTTPStreamingBox Box Type ‘htps’ Container: Signaling file Mandatory: Yes Quantity: One Aligned(8) class HTTPStreamingBox extends Box(‘htps’) ⁇ ⁇
- FIG. 4 is a diagram illustrating detecting of virtual boundaries in an MPEG-2 TS according to an embodiment of the present invention.
- PCR packets of a given program may be carried with fixed PIDs (namely, PCR_PID), and may be inserted at least every 100 ms.
- the PCT packets may be considered as anchor points of the program.
- each media of a program may be carried by packets of a given PID (namely, Media_PID).
- a fragment boundary of a media stream may be defined or identified by 1) a specific anchor point and 2) an offset from the anchor to the packet at the boundary.
- the offset may be counted by the packets of the same Media_PID.
- PCR values may be occasionally reset (discontinuity). For example, when one or more PCR packets have the same PCR value in an interval, an appearance order of PCR packets used as anchors may be indicated.
- a sourceURL attribute may be changed from required to optional. This is because haseURL already provides a complete URL. The sourceURL may be unnecessary.
- a segment of a low frame rate (that is able to be used in a trickmode) may be extracted on-the-fly from a stream or an original segment.
- Each level of description (a top-level, a Period level, and a Representation level) may provide only a single BaseURL for building absolute URLs from the description.
- Multiple BaseURLs may be provided at each description level. Multiple BaseURLs may signal availability of resources at multiple locations.
- the client may select one or more BaseURLs in a process of retrieving resources.
- Such a modification may be implemented by different ways.
- One way may be to use an additional attribute called “more baseURLs,” or an element called “BaseURLs.”
- the attribute or element may be a string formed of multiple (base) URLs.
- the string may be separated by several special characters, for example “;” (namely, a semicolon and a space).
- the semicolon or space may be encoded by the rules of RFC 2616 .
- the morebaseURLs attribute (or BaseURLs element) of a lower description level may override the same attribute (or element) of the higher description level.
- BaseURLs attribute and BaseURLs element may be restricted to be mutually exclusive. In other words, only a single type may exist in a whole description.
- Another way may be to use a MoreBaseURL element of any URI type with multiple instances, where each instance provides a BaseURL.
- the different ways may be merely examples of ideas for providing multiple BaseURLs.
- the ideas may be implemented in many other ways or even other languages.
- Resource/content may be divided into one or more components/streams.
- Each of the one or more components/streams may be delivered from a location.
- the delivering may be supported by allowing multiple instances of an UrlTemplate element or a Url element set in SegmentInfoType.
- the appearance order of an UrlTemplate instance or a Url set instance may indicate importance of “location/stream.” A more important location may appear before a less important location.
- a video Representation may include two streams (for example, a spatial base layer, and a spatial enhancement layer). Each of the two streams may be delivered from a location described by UrlTemplate. Subsequently, the first instance of UrlTemplate may be a location for the spatial base layer.
- n th instance of InitialisationSegmentURL may correspond to an n th instance of a location (by either the UrlTemplate element or the Url element set).
- the instance may be used for all locations.
- Tables 15 through 19 show the schema of 3GPP AdaptiveHTTPStreaming.
- FIG. 5 is a diagram illustrating a configuration of the terminal 100 according to an embodiment of the present invention.
- a controller 510 may perform operations 130 and 140 . Specifically, the controller 510 may process the metadata of the interval.
- a transceiver 520 that selects a fragment suitable for the interval based on the processing may perform operations 120 , 140 , and 150 . Specifically, the transceiver 520 may receive the metadata of the interval of the content from the server 110 , may send a request for the fragment suitable for the interval to the server, and may receive the fragment from the server.
- FIG. 6 is a diagram illustrating a configuration of the terminal 100 according to an embodiment of the present invention.
- the terminal 100 may include an access engine 610 , and a media engine 620 .
- the access engine 610 may be a access engine.
- the access engine 610 may receive metadata (for example, an MPD) from the server 110 .
- metadata for example, an MPD
- the access engine 610 may form requests, and may issue the formed requests to the server 110 .
- the access engine 610 may receive media (for example, segments or parts of the segments) from the server 110 .
- the access engine may request a segment of the media using a URL of the segment.
- the access engine 610 may receive segments of the media based on information provided by the metadata.
- each period may include one or more groups, and each of the groups may include one or more representations of the media.
- Each of the representations may include one or more segments.
- the access engine 610 may provide the media to the media engine 620 .
- the access engine 610 may decode data of the media included in the segments.
- An output of the access engine 610 may include media (or a part of the media) of an MPEG container (for example, an ISO/IEC 14492-12 ISO base media file format, or an ISO/IEC 13818-2 MPEG-2 TS) Additionally, the output of the access engine 610 may include timing information used to map internal timing of the media to a timeline of a media presentation.
- an MPEG container for example, an ISO/IEC 14492-12 ISO base media file format, or an ISO/IEC 13818-2 MPEG-2 TS
- timing information used to map internal timing of the media to a timeline of a media presentation.
- the media engine 620 may play back the provided media. Specifically, the media engine 620 may receive data of the media from the access engine, and may output the media. The media engine 620 may output the media using the data of the media and the timing information that are output from the access engine 610 .
- the method according to the above-described embodiments of the present invention may be recorded in computer-readable media including program instructions to implement various operations embodied by a computer.
- the media may also include, alone or in combination with the program instructions, data files, data structures, and the like.
- the program instructions recorded on the media may be those specially designed and constructed for the purposes of the embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts.
- Examples of computer-readable media include magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD ROM disks and DVDs; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory (ROM), random access memory (RAM), flash memory, and the like.
- Examples of program instructions include both machine code, such as produced by a compiler, and files containimg higher level code that may be executed by the computer using an interpreter.
- the described hardware devices may be configured to act as one or more software modules in order to perform the operations of the above-described embodiments of the present invention, or vice versa.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
- The present invention relates to a technology for providing streaming content, and more particularly, to an apparatus and method for providing media content using adaptive streaming.
- Streaming is one of schemes for transmitting and playing back multimedia content such as sounds, moving images, and the like. A client may play back content while receiving the content through the streaming.
- An adaptive streaming service refers to providing a streaming service employing a communication scheme with a request of a client and a response of a server in response to the request.
- The client may request a media sequence suitable for an environment of the client (for example, a transmission channel of the client), using the adaptive streaming service. The server may provide a media sequence matched to the request of the client among media sequences with various qualities that are included in the server.
- The adaptive streaming service may be provided based on various protocols.
- A Hypertext Transfer Protocol (HTTP) adaptive streaming service refers to an adaptive streaming service provided based on an HTTP protocol. A client of the HTTP adaptive streaming service may receive content from a server using the HTTP protocol, and may transmit a request associated with a streaming service to the server.
- An aspect of the present invention provides an apparatus and method that may interpret a Uniform Resource Locator (URL) of a segment using one or more BaseURL elements during playback of content.
- Another aspect of the present invention provides an apparatus and method that may generate a URL of a segment by mapping a BaseURL element among one or more BaseURL elements to a sourceURL attribute of the segment.
- According to an aspect of the present invention, there is provided a method for providing media, the method including: receiving metadata of media, the metadata including one or more BaseURL elements; sending a request for a segment of the media using a Uniform Resource Locator (URL) of the segment, the URL being resolved with respect to a BaseURL element; receiving the segment; and decoding and rendering data of the media that is included in the segment.
- The request may be sent using an HTTP GET method.
- The metadata may include a range attribute.
- The request may include a request for bytes of a resource indicated by the URL that are designated by the range attribute.
- The URL may be an absolute URL or a relative URL.
- Identical segments may be accessible at multiple locations indicated by URLs resolved with respect to the respective BaseURL, elements.
- A first BaseURL element among the BaseURL elements may be used as a basic Universal Resource Indicator (URI), and BaseURL elements other than the first BaseURL element may be used as alternative BaseURL elements.
- The metadata may selectively include a sourceURL attribute of the segment. When the metadata selectively includes the sourceURL attribute of the segment, a BaseURL element among the BaseURL elements may be mapped to the sourceURL attribute, so that the URL may be generated.
- The metadata may be a Media Presentation Description (MPD) of the media.
- The media may include a sequence of one or more periods.
- A BaseURL element may include one or more MPD level BaseURL elements of the MPD, and one or more period level BaseURL, elements of the periods.
- A URL of a segment included in each of the periods may be resolved with respect to a period level BaseURL element.
- The period level BaseURL elements may be resolved with respect to the MPD level BaseURL elements.
- Each of the periods may include one or more groups.
- The BaseURL element may further include one or more group level BaseURL elements of the groups.
- A URL of a segment included in each of the groups may be resolved with respect to a group level BaseURL element.
- The group level BaseURL elements may be resolved with respect to the period level BaseURL elements.
- Each of the groups may include one or more representations.
- Each of the representations may be a structured collection of one or more components of the media within a period.
- The BaseURL element may further include one or more representation level BaseURL elements of the representations
- A URL of a segment included in each of the representations may be resolved with respect to a representation level BaseURL element.
- The representation level BaseURL elements may be resolved with respect to the group level BaseURL elements or the period level BaseURL elements.
- According to another aspect of the present invention, there is provided a terminal, including: an access engine to receive metadata of media, to send a request for a segment of the media using a Uniform Resource Locator (URL) of the segment, to receive the segment, and to decode data of the media that is included in the segment, the metadata including one or more BaseURL elements, and the URL being resolved with respect to a BaseURL element; and a media engine to receive the data of the media from the access engine, and to output the media.
- According to embodiments of the present invention, it is possible to interpret a. Uniform Resource Locator (URI) of a segment using one or more BaseURL elements during playback of content.
- Additionally, according to embodiments of the present invention, it is possible to generate a URL of a segment by mapping a BaseURL element among one or more BaseURL elements to a sourceURL attribute of the segment.
-
FIG. 1 is a diagram illustrating categories of signaling information according to an embodiment of the present invention. -
FIG. 2 is a diagram illustrating categories of signaling information according to an embodiment of the present invention. -
FIG. 3 is a diagram illustrating a hierarchy of content division and levels of signaling information according to an embodiment of the present invention. -
FIG. 4 is a diagram illustrating detection of virtual boundaries in a Moving Picture Experts Group-2 Transport Stream (MPEG-2 TS) according to an embodiment of the present invention. -
FIG. 5 is a diagram illustrating a configuration of aterminal 100 according to an embodiment of the present invention. -
FIG. 6 is a diagram illustrating a configuration of aterminal 100 according to an embodiment of the present invention. - Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below in order to explain the present invention by referring to the figures.
- A Dynamic Adaptive Streaming over HTTP (DASH) may specify formats that enable 1) delivery of media content from an HTTP server to an HTTP client, and enable 2) caching of content by standard HTTP cashes.
- A media component may be an encoded version of individual media types, such as audios, videos, or timed texts with specific attributes, for example bandwidths, languages, or resolutions.
- Media content may be a set of media components having a common timeline, for example audios, videos, or timed texts. Additionally, media components may have relationships on how the media components may be presented (for example, individually, jointly, or mutually exclusive) as programs or movies.
- Media content and content may be used as interchangeable terms.
- A media presentation (or media) may be a structured collection of data used to establish bounded or unbounded presentation of media content including components of continuous media.
- In other words, the media presentation may be a structured collection of data that is accessible to a DASH client in order to provide a streaming service to a user.
- A Media Presentation Description (MPD) may be a formalized description for a media presentation.
- The media presentation may be described by an MPD including possible updates of the MPD.
- Content may be content on demand, or live content.
- The content may be divided into one or more intervals. In other words, the content may include one or more intervals.
- Intervals may be interchangeable with periods. The term period may be used as a term of 3rd Generation Partnership Project (3GPP) adaptive HTTP streaming.
- A period may be an interval of a media presentation. A continuous sequence of all periods may constitute the media presentation.
- In other words, the media presentation may include a sequence of one or snore periods.
- One or more intervals may be a basic unit. One or more intervals may be described by signaling metadata. In other words, metadata may describe each of the one or more intervals.
- The metadata may be an MPD.
- The MPD may define a format to announce resource identifiers for segments. The MPD may provide a context for identified resources within the media presentation. The resource identifiers may be HTTP-Uniform Resource Locators (URLs). URLs may be restricted by a byte range attribute.
- Each interval may be divided into fragments.
- Fragments may be interchangeable with segments. The term segment may be used as a term of 3GPP adaptive HTTP streaming.
- A segment may refer to an entity body of a response to an HTTP/1.1 GET request for an HTTP-URL, for example as defined in RFC 2616, (or a GET request for a part indicated by a byte range).
- A terminal may play back media content using received bytes (namely, a segment).
- A sub-segment may refer to a smallest unit within segments that may be indexed by a segment index at the segment level.
- Two or more sets of fragments corresponding to a single interval may exist. Each of the sets may be called an alternative.
- An alternative may be interchangeable with a representation expression).
- Each period may include one or more groups.
- Each group may include one or more representations of the same media content.
- A representation may refer to a structured collection of one or more media components within a single period. A representation may be one of alternative choices of the media content or a subset of the media content typically differing by the encoding choice, for example by a bitrate, a resolution, a language, a codec, and the like.
- An MPD (or an MPD element) may provide descriptive information that enables a client to select one or more representations.
- A Random Access Point (RAP) may be a specific location in a media segment. The RAP may be identified as a location in which playback may be started continuously from a location of the RAP using only information included in a media segment.
- Each representation may be formed of one or more segments. In other words, a representation may include one or more segments.
- An MPD may be a document including metadata required to a DASH client to form appropriate HTTP-URLs in order to 1) access segments and to 2) provide a user with a streaming service. The HTTP-URLs may be absolute or relative.
- The MPD may be an Extensible Markup Language (XML)-document.
- The MPD may include an MPD element. The MPD may include only a single MPD element.
-
FIG. 1 is a signal flowchart illustrating a content processing method according to an embodiment of the present invention. - A terminal 100 may be a DASH client.
- The DASH client may be compatible with a client specified in RFC 2616.
- The DASH client may typically use an HTTP GET method or an HTTP partial GET method, as specified in RFC 2616, to access segments or parts of segments.
- A
server 110 may perform hosting on DASH segments. Theserver 110 may be compatible with a server specified in RFC 2616. - In
operation 120, the terminal 100 may receive metadata of media (or content) from theserver 110. In other words, theserver 110 may transmit the metadata of the media to the terminal 100. - The metadata may include BaseURL elements. One or more BaseURL elements may be provided.
- In
operation 130, the terminal 100 may process the received metadata. Inoperation 130, the terminal 100 may extract information provided by the metadata, or information included in the metadata. - In
operations 140 through 150, the terminal 100 may access a segment of the media based on the information provided by the metadata. - Each period may include one or more groups, and each of the groups may include one or more representations of the media. Each of the representations may include one or more segments.
- The metadata may describe a group element describing each of the groups.
- In
operation 140, the terminal 100 may send a request for a segment of the media to theserver 110 using a URL of the segment. The URL may be resolved with respect to one of the above-described BaseURL elements. For example, the URL of the segment may be generated based on a BaseURL element. - The terminal 100 may request the
server 110 to transmit a segment suitable for a specific interval based on the processed metadata. In other words, the requested segment may be selected based on the metadata. The request may be sent using the HTTP GET method. - The metadata may include a range attribute. The request may include a request for bytes of a resource indicated by a URL that are designated by the range at tribute.
- The URL of the segment may be an absolute URL or a relative URL.
- Identical segments may be accessible at multiple locations indicated by URLs resolved with respect to the respective BaseURL elements. In other words, identical segments may be selectively accessible by the URLs provided by the BaseURL elements.
- Additionally, a first BaseURL element among the BaseURL elements may be used as a basic Universal Resource Indicator (URI), and BaseURL elements other than the first BaseURL element may be used as alternative BaseURL elements.
- The metadata may selectively include a sourceURL attribute of the segment. When the metadata selectively includes the sourceURL attribute of the segment, a BaseURL element among the BaseURL elements may be mapped to the sourceURL attribute, so that the URL of the segment may be generated.
- In
operation 145, in several cases, theserver 110 may need to parse content (for example, a Moving Picture Experts Group (MPEG) layer 4 (MP4) file for Scalable Video Coding (SVC)), and may extract a data part suitable for the requested segment. - In
operation 150, theserver 110 may transmit, to the terminal 100, segments suitable for each request from the terminal 100. The terminal 100 may receive the segments from the server. - In
operation 160, the terminal 100 may perform decoding and rendering on data of the media included in the segment, to play back the media. - The terminal 100 may play back the media using the received segments by repeating
operations 120 through 160. - Here, a BaseURL element may include an MPD level BaseURL element of an MPD, and a period level BaseURL element of each period. The period level BaseURL element may refer to a BaseURL element applied to a period to which the period level BaseURL element belongs. In other words, a URL of a segment included in each period may be resolved with respect to the period level BaseURL element.
- One or more MPD level BaseURL elements may be provided, and one or more period level BaseURL elements may be provided.
- Additionally, the BaseURL element may further include a group level BaseURL element of a group. A URL of a segment included in each group may be resolved with respect to the group level BaseURL element. One or more group level BaseURL elements may be provided.
- The BaseURL element may further include a representation level BaseURL element of a representation. A URL of a segment included in each representation may be resolved with respect to the representation level BaseURL element.
- A BaseURL element of a specific level may be resolved with respect to a BaseURL element of a higher level. For example, a period level BaseURL element may be resolved with respect to an MPD level BaseURL element. A group level BaseURL element may be resolved with respect to a period level BaseURL element. A representation level BaseURL element may be resolved with respect to a group level BaseURL element or a period level BaseURL element.
-
FIG. 2 is a diagram illustrating categories of signaling information according to an embodiment of the present invention. - The signaling information (namely, metadata) may be divided into the following categories 1) through 4):
- 1) General information 210: includes common description of content, and general description of each interval, such as a duration, and a start time.
- 2) Quality of Service (QoS) information 220: describes characteristics of each alternative, such as a bitrate, a resolution, and a quality. In other words, the QoS information describes characteristics of each of alternatives of content.
- An alternative may be physical (namely, created in advance), or may be virtual (namely, to be created on the fly). Based on information of alternatives, the client may select a fragment of an appropriate alternative. Accordingly, adaptivity to contexts of terminals and networks may be supported.
- 3) Mapping information 230: describes locations to retrieve content. Depending on specific cases, different alternatives may have the same or different locations.
- 4) Client request 240: this type of signaling information may conform to a format of HTTP 1.1 request message. As shown in
FIG. 1 , parameters requested by the client may be derived from the information of categories 1) through 3). -
FIG. 3 is a diagram illustrating a hierarchy of content division and levels of signaling information according to an embodiment of the present invention. - Signaling of metadata according to an embodiment of the present invention may be physically separated into content-
level information 310, interval-level information 320,QoS information 330, andmapping information 340. Linking of related parts of the content-level information 310, the interval-level information 320, theQoS information 330, and themapping information 340 may be performed by reference. - These parts of signaling information may be combined in different ways to support the flexibility.
- For example, when only the content-
level information 310 and interval-level information 320 are sent to a client, all computations for deciding alternatives and resolving locations may be performed by a server. Accordingly, when only the content-level information 310 and interval-level information 320 are sent to the client, a processing model may be “server-based.” - When the content-
level information 310, the interval-level information 320, and theQoS information 330 are sent to the client, all computations for deciding alternatives and resolving locations may be distributed and performed by the client and the server. Accordingly, when the content-level information 310, the interval-level information 320, and theQoS information 330 are sent to the client, the model may be “distributed.” - When all the signaling information (namely, the content-
level information 310, the interval-level information 320, theQoS information 330, and the mapping information 340) is sent to the client, the model may be client-based, because most (or all) processing (namely, computations for deciding alternatives and resolving locations) is performed by the client. - The separation of metadata parts may enable efficiency in storage and delivery. For example, during a session, metadata of the content-
level information 310 may be sent once, and only the interval-level information 320 may be periodically updated. Similarly, a single file containing theQoSInfo 330 may be used for different intervals and different contents. - There are different ways to represent a set of metadata, for example XML, pseudo-code, a Session Description Protocol (SDP), and the like.
- In embodiments of the present invention, both XML and pseudo-code may be used to represent signaling syntax. XML syntax may be used for clients that support an XLM profile based on an MPEG-21 and similar schema. On the other hand, pseudo-code syntax may be based on a “language” of an International Organization for Standardization (ISO) base media file format and the like, and may be used in non-XML clients. In particular, a profile of the pseudo-code syntax may employ a parsing module similar to a parsing module of file-format parsing. To design the syntax for the above purpose, a table of common elements may be defined and elements in each format may be represented, in the following embodiments.
- The proposed syntax may be represented by any other languages.
- Hereinafter, tables of general syntax elements will be described.
- In the following tables, the syntax elements may be described hierarchically. In other words, a child element may be shown in a column on the right of a parent element of the child element. “Leaf”-level elements may be shown in italic, and parent elements may be shown in bold letter. A parent element may be represented by a corresponding XML type and a file box.
- In the column of occurrence, “0 . . . N” may mean that the number of instances of an occurrence element may be from 0 to “unbounded.” The minimum occurrence of 0 may mean that an element may be optional (namely, not present). A minimum occurrence equal to or greater than 1 may mean that an element is mandatory in the syntax.
- Occurrence may be interchangeable with cardinality.
- In a row of type, A indicates an attribute, and F indicates an element. In a row of optionality, M indicates mandatory, and O indicates optional. For attributes, M indicates mandatory, O indicates optional, OD indicates optional with default value, and CM indicates conditionally mandatory. For elements, elements may be represented as <minOccurs> . . . <maxOccurs>. Here. N may be unbounded.
- The above meaning may equally be applied to other tables in the present specification.
- Additionally, QoSInfo may be also called AdaptationInfo to make QoSInfo more specific. Moreover, a few elements may be revised to increase flexibility of the syntax.
- The following Table 1 describes general information.
-
TABLE 1 Pseudo-code XML syntax (based (File format Occurrence Semantics on MPEG-21) box) HttpStr 1 Describes the top-level element of HttpStreamingType ‘htps’ box signaling metadata for HTTP streaming GeneralInfo 0 . . . N Contains the general information of GeneralInfoType ‘geni’ box the described content TimeScale 0 . . . 1 Describes the number of time units integer unsigned int(32) in 1 second. This value is used with time-related elements, when a time unit is not specified. LiveStartTime 0 . . . 1 If LiveStartTime element is not dateTime unsigned int(64) present, the content is of VoD type. The presence of LiveStartTime element indicates a live content that is to be displayed at a time value of LiveStartTime. If LiveStartTime has a time value of 0, the display time is unknown. Duration 0 . . . 1 If present, indicates duration of the integer unsigned int(32) content. Otherwise, the duration is unknown. DefaultIntDuration 0 . . . 1 If present, indicates a default integer unsigned int(32) duration of each interval of the content. MinUpdateTime 0 . . . 1 If present, indicates the minimum integer unsigned int(32) waiting time before requesting the main description file again. ConsistentQoSInfo 0 . . . 1 If true, indicates that QoS boolean flag of the box information is the same as the whole content duration. DefaultContentLoc 0 . . . 1 Provides a default location for the anyURI string of URL content. IntervalsRef 0 . . . N Provides reference to description IntervalsRefType ‘iref’ box containing one or more instances of Interval element. One or more instances of Interval element represent a sequence of consecutive interval(s). Interval 0 . . . N Provides information of an interval IntervalType ‘intv’ box of content. The information of the interval may be either included as an instance of Interval element or referenced by IntervalsRef element. IntervalInfo 0 . . . 1 Provides general information of an IntervalInfoType ‘inti’ box interval. QoSInfoRef 0 . . . 1 Provides reference to description dia: ReferenceType ‘qref’ box represented by QoSInfo element. If QosInfoRef element is present, QoSInfo element may not be present at the same level. QoSInfo 0 . . . 1 Provides information about QoSInfoType ‘QoSi’ box alternatives of content, such as resource characteristics and quality/utility. If QoSInfo element is present, QoSInfoRef element may not be present. MappingInfoRef 0 . . . 1 Provides reference to description dia: ReferenceType ‘mref’ box represented by MappingInfo element. If MappingInfoRef element is present, MappingInfo element may not be present at the same level. MappingInfo 0 . . . 1 Provides information about MappingInfoType ‘mapi’ box locations of content alternatives. If the information is not provided, DefaultContentIntLoc element (if not, DefaultContentLoc) can be used to retrieve content. If MappingInfo element is present, MappingInfoRef element may not be present. NextIntervalsRef 0 . . . 1 Provides reference to information of IntervalsRefType, ‘nref’ box next interval(s). may be extended from The information of next interval(s) dia: ReferenceType is description containing one or more instances of Interval element. The information of next interval(s) is description represented by Interval element. Using NextIntervalsRef element, the client does not need to reload the main description represented by HttpStr element. Within the current time window, only the final interval may contain NextIntervalsRef element. PreviousIntervalsRef 0 . . . 1 Provides reference to information of IntervalsRefType, ‘nref box previous interval(s). may be extended from The information of next interval(s) dia: ReferenceType is description containing one or more instances of Interval element. The information of next interval(s) is description represented by Interval element. Using PreviousIntervalsRef element, the client does not need to reload the main description represented by HttpStr element. Within the current time window, only the first interval may contain NextIntervalsRef element. - The following Table 2 describes IntervalsRef, NextIntervalsRef, PreviousintervalsRef, QoSInfoRef, MappingInfoRef a, and IntervalInfo.
-
TABLE 2 XML syntax Pseudo- (based on code (File Ocurrence Semantics MPEG-21) format box) QoSInfoRef, Mapping- InfoRef Index 1 Indicates the order (starting from 1) of not unsigned the referenced description or box applicable int(8) (Interval, QoSInfo, MappingInfo) in the description file referenced by the next Location element. Location 1 Provides reference to description uri element string represented by Interval, QoSInfo, or in dia: (representing MappingInfo. ReferenceType url) IntervalInfo TimeScale 0 . . . 1 Describes the number of time units in integer unsigned one second. This value is used with int(32) time-related elements, when a time unit is not specified. TimeScale element, if present, overrides the time scale provided by GeneralInfo. StartTime 0 . . . 1 Indicates the start tune of the interval. Duration 0 . . . 1 Indicates the duration of the interval. integer unsigned int(32) Default- 0 . . . 1 Indicates the default duration of integer unsigned FragDuration fragments of the interval (except the last int(32) fragment). Default- 0 . . . 1 Provides a default location for the anyURI type string ContentInt- content interval. Loc Last 0 . . . 1 If true, indicates the final interval of the boolean by flag content. IntervalsRef, Previous- Intervals- RefNext- IntervalRef startTime Indicates the start time of the referenced xs: duration sequence of intervals/periods relative to the start time of the content (LiveStartTime for live content and 0 for on-demand content). AvailableTime 0 . . . 1 Indicates the time the description of the integer unsigned next interval is available. The is the int(32) relative time from the start time of the content. Index 1 Indicates the order (starting from 1) of not unsigned the referenced interval description (or applicable int(8) box) in the description file referenced by the next Location element. Location 1 Provides reference to description file sx: anyURI string that contains Interval descriptions. type or uri (representing element in dia: url) ReferenceType - The following Table 3 describes the QoSInfo element.
-
TABLE 3 Pseudo-code XML syntax (based (File format Occurrence Semantics on MPEG-21) box) QoSInfo 1 Provides information about a list of QoSInfoType containing a ‘QoSi’ box content alternatives, such as UtlityFunction of dia: resource characteristics and AdaptiveQoSType quality/utility. ClassSchemeRef 0 . . . 1 Provides a list of classification dia: DescriptionMetadataType ‘csmr’ box schemes. The classification schemes provide semantics for some terms or names. scheme 1 . . . N Provides reference to a Attr. alias & href in dia: a url string classification scheme. DescriptionMetadataType (1) Resource 0 . . . N Each instance of Resource element Element constraint of dia: ‘resi’ box describes, for a list of alternatives, UFDataType in DIA Utility- characteristic values of a certain FunctionType resource type (e.g., bitrate). (2) AdaptationOperator 0 . . . N Each instance of dia: UFDataType ‘adpo’ box AdaptationOperator element describes, for a list of alternatives, values of a certain adaptation type (e.g., remove temporal layers). (3) Utility 0 . . . N Each instance of Utility element dia: UFDataType ‘util’ box describes, for a list of alternatives, values in a certain quality/utility type (e.g., MOS). UtilityRank 0 . . . 1 Describes the quality ranking for a dia: UtilityRankType ‘utir’ box list of alternatives. Value 1 . . . N Indicates the quality/utility rank of integer unsigned int(16) an alternative. The number of instances of Value element is equal to the number of alternatives. - The following Table 4 shows common semantics of (1) Resource, (2) AdaptationOperator, and (3) Utility of Table 3.
-
TABLE 4 Pseudo-code XML syntax (based (File format Occurrence Semantics on MPEG-21) box) QoSInfo 1 Provides information about a list QoSInfoType containing a ‘QoSi’ box of content alternatives, such as UtilityFunction of dia: resource characteristics and AdaptiveQoSType quality/utility. ClassSchemeRef 0 . . . 1 Provides a list of classification dia: DescriptionMetadataType ‘csmr’ box schemes. The classification schemes provide semantics for some terms or names. scheme 1 . . . N Provides reference to a Attr. alias & href in dia: a url string classification scheme. DescriptionMetadataType (1) Resource 0 . . . N Each instance of Resource element Element constraint of ‘resi’ box describes, for a list of alternatives, dia: UFDataType in DIA characteristic values of a certain Utility-FunctionType resource type (e.g., bitrate). (2) AdaptationOperator 0 . . . N Each instance of dia: UFDataType ‘adpo’ box AdaptationOperator element describes, for a list of alternatives, values of a certain adaptation type (e.g., remove temporal layers). (3) Utility 0 . . . N Each instance of Utility element dia: UFDataType ‘util’ box describes, for a list of alternatives, values in a certain quality/utility type (e.g., MOS). UtilityRank 0 . . . 1 Describes the quality ranking for a dia: UtilityRankType ‘utir’ box list of alternatives. Value 1 . . . N Indicates the quality/utility rank of integer unsigned int(16) an alternative. The number of instances of Value element is equal to the number of alternatives. Pseudo-code Element XML syntax (based (File format (1), (2), (3) Semantics on MPEG-21) box) Name 1 Describes an identifier for a Att. ‘iOPinRef’, ref. unsigned int(32) certain type of the element. a CSterm When the identifier is not semantically defined by the above embodiment, next three elements are used to find semantics of the identifier in a classification scheme. CSref_ind 0 . . . 1 Indicates the reference index of a Not applicable unsigned int(16) classification scheme in the list provided by ClassSchemeRef element. LevelNum 0 . . . 1 Indicates the number of levels. Not applicable unsigned int(16) LevelIndex 1 . . . N Each instance of LevelIndex Not applicable unsigned int(16) element represents an index value at a level of the classification scheme. Value 1 . . . N Indicates the value of a resource a component in dia: unsigned int(32) type (adaptation operator, or VectorDataType utility) of an alternative. The number of instances of Value element is equal to the number of alternatives. - The following Table 5 shows mapping information.
-
TABLE 5 XML syntax (based Pseudocode on (File MPEG- format Occurrence Semantics 21) box) MappingInfo 0 . . . 1 Mapping ‘mapi’box InfoType AlterLocID 0 . . . 1 Provides a location ID for each dia:Integer ‘aloc’ alternative described in QoSInfo. Vector box If AlterLocID element is not Type present, the first location in the location list may be used for all alternatives. Value 1 . . . N Indicates a location ID for an integer unsigned alternative. int(16) The number of instances of this element is equal to the number of alternatives. The nth instance of Value element corresponds to the nth alternative of QoSInfo description. ReqQoSPara 0 . . . N Indicates a parameter of QoSInfo ReqQoS ‘reqp’ that may be put in the request (for ParaType box an alternative) sent by the client to that the server. extends A parameter may be an instance of dia:Boolean Resource, AdaptationOperator, Vector Utility, or UtilityRank elements. Type RefIndex 1 Indicates instance index/reference represented unsigned in the instance list of Resource, by int(16) AdaptationOperator, Utility and attribute UtilityRank elements. ‘iOPinRef’ that references an IOPin in QoSInfo All 1 If true, the parameter needs to be boolean flag requested for all alternatives and ReqFlag may be skipped. ReqFlag 0 . . . N Each instance of ReqFlag element component unsigned corresponds to an alternative. of int(8) If ReqFlag is true, the request for Boolean the corresponding alternative has VectorType the parameter identified above. LocationList 1 Provides a list of locations for Location ‘locl’ retrieving content alternatives ListType box Location 1 . . . N Provides information of a location Location ‘loca’ Type box - Semantics of Location elements may be further provided as shown in Table 6,
-
TABLE 6 XML syntax (based Pseudocode Occurrence Semantics on DIA) (MP4) Location 0 . . . N LocationType ‘loca’ box LocID 1 Indicate an ID of an instance of integer unsigned Location element. Location int(16) element is referred to by AlterLocID. StrLocation 0 . . . N Provides location information StrLocationType ‘stlo’ of a stream of a content box interval. Each stream is provided by either a stream URL or a number of fragment URLs. FragNum 0 . . . 1 Provides the number of integer unsigned fragments int(16) StreamUrl 0 . . . 1 Describes a URL of a stream anyURItype string FragmentUrl 0 . . . N Describes a URL of a fragment. anyURItype string The number of instances of FragmentUrl element is the number of fragments. FragTime 0 . . . 1 Provides durations of dia:VectorDataType ‘frtm’ fragments. box Value 1 . . . N Indicates a duration of a integer unsigned fragment. int(32) The number of instances of Value element is the number of fragments. RandAccess 0 . . . 1 Describes fragments that dia:VectorDataType ‘rdac’ support random access. box Value 1 . . . N Indicates the order of a random- integer unsigned access fragment. int(16) MP2TSPara 0 . . . 1 Describes additional parameters MP2TSParaType ‘mp2p’ (beside URL) for locating a box content/program in a MPEG-2 TS. PID 0 . . . N Describes values of PIDs of integer unsigned content/program in a MPEG-2 int(16) TS. FragBoundaries 0 . . . 1 Describes boundaries of FragBoundariesType ‘frbd’ (virtual) fragments in a stream. box The number of instances of FragBoundaries element is equal to the number of fragments of the stream. Only one type of following elements is present in a FragBoundaries instance. MP2TSBoundary 0 . . . N Describes parameters for MP2TSBoundaryType ‘mp2b’ detecting (virtual) fragment box boundary in a MPEG-2 TS. If there are two instances of MP2TSBoundary element, the two instances are starting and ending boundaries of a fragment. If there is only one instance of MP2TSBoundary element, the instance is the starting boundary. The ending boundary is right before the starting boundary of the next fragment. ISOFileBoundary 1 . . . 2 Describes parameters for ISOFileBoundaryType ‘isfb’ detecting (virtual) fragment box boundary in a file based on ISO base media file format. If there are two instances of ISOFileBoundary element, the two instances are starting and ending boundaries of a fragment. If there is only one instance of ISOFileBoundary element, the instance is the starting boundary. The ending boundary is right before the starting boundary of the next fragment. ByteRanges 1 Describes byte ranges that ByteRangesType ‘brag’ identify a part/fragment of a box file. Parameters provided by ByteRanges element may be used for byte range options in an HTTP request. - Semantics of M2TSBoundary, ISOFileBoundary, and ByteRanges may be further provided as shown in Table 7.
-
TABLE 7 XML syntax Pseudo- (based on code Occurrence Semantics DIA) (MP4) MP2TS- MP2TS- ′mp2b′ Boundary BoundaryType box PCR_PID 1 Describes PID carrying PCR of the integer unsigned concerned content/program. int(16) PCR_base 1 Describes a value of a PCR base long unsigned field int(40) PCR_ext 1 Describes a value of a PCR integer unsigned extension field. int(16) Appearance 1 Describes the appearance order integer unsigned (e.g., 1st, 2nd) of the TS packet int(16) containing the PCR value identified by the above two elements. If there is resetting/discontinuity of PCR, a PCR value may appear more than once during an interval. Media_PID 1 . . . N Describes PID of a media (e.g., integer unsigned video) of a program. int(16) The number of instances of Media_PID element is equal to the number of media of the program/content. Media_Offset 1 . . . N Describes the offset (in TS packets integer unsigned of the same media PID) from the int(16) above identified PCR packet to the first media packet of a fragment. The nth instance of Media_Offset is associated with the nth instance of Media_PID. ISOFile- ISOFile- ′isfb′ Boundary BoundaryType box SequenceNo 1 Describes the sequence number integer unsigned provided in the mfhd box. int(16) The mfhd box defines a fragment of an MP4 file. SequenceNo with a value of 0 indicates the beginning of the file. ByteRanges ByteRanges- ′brag′ Type box Start 1 . . . N Describes the starting value of a integer unsigned byte range. int(32) A value of ′−1′ means that this value in the HTTP request is missing. End 1 . . . N Describes the ending value of a byte integer unsigned range. int(32) A value of ′−1′ means that this value in the HTTP request is missing. Start-End instances are present in pair. The nth instance of End is associated with the nth instance of Start. Media_PID 0 . . . N Describes PID of a media (e.g., integer unsigned video) that needs to be extracted int(16) from the byte range of the above pair of Start-End. Media_PID element is used when the byte range is a segment of MPEG-2 TS, and all PTDs do not need to be delivered. - Hereinafter, A Client Request will be Described.
- Signaling of metadata obtained by a client may include different parts or levels of signaling information. Accordingly, a request from the client to a server may include parameters of different levels of details.
- Main parameters of the client may be URIs, and may be associated with a query part.
- Three main scenarios are examined as follows:
- 1) Server-Based Scenario
- In the server-based scenario, the metadata provided from the server to the client may include
general content information 310 andgeneral interval information 320. - For an URI of requested content, DefaultContentIntLoc (if not, DefaultContentIntLoc) may be used. To enable the client to request a specific fragment of content, the following parameters a) and b) are defined in the query part (of the request in operation 140):
- a) “fragno”: Order value of the fragment in the interval
- b) “fragti”: Start time of the fragment in the interval
- For example, a request URI may be “HTTP://server.com/file.mp4?fragno=5.”
- 2) Distributed Scenario
- In the distributed scenario, the metadata provided from the server to the client may include
general content information 310,general interval information 320, andQoS information 330. - In addition to the above parameters, the following QoS-related parameters a) through c) are defined in the query part (of the request in operation 140) to enable the client to request an appropriate alternative:
- a) “alter”: Order value of an alternative. Based on the order value of the alternative, the alternative may appear in the QoS information.
- b) “oper1”, “oper2”, . . . , and “operN”: “opera” carries a value of an ith adaptation operation that appears in the QoS information.
- c) “res1”, “res2”, “resN”: “resi” carries a value of ani resource that appears in the QoS information.
- Only one of the above three options may be used in a single request.
- With typical adaptation operators and resource types, specific parameter names for better intelligibility and interoperability may be defined.
- Adaptation operators are as the following a) through e).
- a) audiolayers: indicates the number of scalable audio layers to be discarded.
- b) temporallayers: indicates the number of temporal layers of scalable video to be discarded.
- c) spatiallayers: indicates the number of spatial layers of scalable video to be discarded,
- d) qualitylayers: indicates the number of quality layers of scalable video to be discarded,
- e) prioritylayers: indicates the number of priority layers of scalable video to be discarded.
- Resource types are as the following a) through d).
- a) bitrate: indicates the average bitrate (in Kbps) of the requested alternative.
- b) vertresolution: indicates the vertical resolution of the requested alternative.
- c) horiresolution: indicates the horizontal resolution of the requested alternative.
- d) fratnerate: indicates the framerate of the requested alternative.
- Using the pre-defined parameters, an example of a request URI based on the bitrate may be “http://server.com/file.mp4?fragno=5&bitrate=550.”
- 3) Client-Based Scenario
- In the client-based scenario, the metadata provided from the server to the client may include general content, general interval information, QoS information, and mapping information.
- The QoS-related parameters used in the request may be indicated by a ReqQoSPara part of QoSInfo metadata. For example, when Refindex of ReqQoSPara is 0 or null, the “alter” parameter may be used instead of other options,
- When ReqQoSPara is not present in the QoSInfo metadata, the QoS-related parameters may not be used. Alternatives in this case may be implied by locations of MappingInfo.
- A URI of content may be derived from rich description of MappingInfo. When content/program is conveyed in an MPEG-2 TS, one or more PIDs may be used to locate the content in the stream.
- When additional information for detecting fragment boundaries are provided, the following parameters 1) through 3) for the query part (of the request in operation 140) may be used.
- 1) For an MPEG-2 TS boundary, Appearance, PCR_PID, PCR_base, PCR_ext, Media_PID, and Media_Offset
- 2) For an ISO media file boundary, SequenceNo
- 3) For a file considered as a raw byte-sequence, Start and End
- Semantics of the above parameters may be provided in semantics of a FragBoundaries element.
- Start-End pairs may be used by a range header of an HTTP request message. For example, if {(Start=0, End=99); (Start=200, End=299)}, the header may be “Range: bytes=0-99,200-299.”
- Hereinafter, syntax representation in an XML format will be described. Representations of the above syntax elements may be provided in the XML format. Semantics of each element may be traced back in the above Tables 1 through 7.
- Several elements may be extensions of several types defined in an MPEG-21 DIA. Several few elements may take several types defined in the MPEG-21 DIA,
- The following Table 8 shows syntax representation of HTTPStreamingType in the XML format.
-
TABLE 8 <complexType name=”HTTPStreamingType″> <complexContent> <extension base=″dia:DIADescriptionType″> <sequence> <element name=″GeneralInfo″ type=″GeneralInfoType″ minOccurs=″0″/> <choice minOccurs=″0″ maxOccurs=″unbounded″> <element name=″IntervalsRef″ type=″IntervalsRefType″/> <element name=″Interval″ type=″IntervalType″/> </choice> </sequence> </complexContent> </complexType> - The following Table 9 shows syntax representation of GeneralInfoType in the XML format.
-
TABLE 9 <complexType name=“GeneralInfoType″> <complexContent> <extension base=″dia:DIADescriptionType″> <sequence> <element name=“TimeScale“ type=“integer″ minOccurs=″0″/> <element name=“LiveStartTime” type=“dateTime” minOccurs=″0″/> <element name=“Duration“ type=“integer″ minOccurs=″0″/> <element name=“DefaultIntDuration“ type=“integer” minOccurs=″0″/> <element name=“MinUpdateTime“ type=“integer” minOccurs=″0″/> <element name=“ConsistentQoSInfo“ type=“boolean” minOccurs=″0″/> <element name=“DefaultContentLoc“ type=“anyURI” minOccurs=″0″/> </sequence> </extension> </complexContent> </complexType> - The following Table 10 shows syntax representation of IntervalRefType in the XML format.
-
TABLE 10 <complexType name=“IntervalsRefType”> <complexContent> <extension base=“dia:ReferenceType”> <sequence> <element name=“AvaliableTime” type=“integer” minOccurs=“0”/> </sequence> <attribute name=“startTime” type=“xs:duration” use=“optional”/> </extension> </complexContent> </complexType> - The following Table 11 shows syntax representation of IntervalType in the XML format.
-
TABLE 11 <complexType name=”IntervalType”> <complexContent> <extension base=″dia:DIADescriptionType″> <sequence> <element name=″IntervalInfo″ type=″IntervalInfoType″ minOccurs=″0″/> <choice minOccurs=″0″> <element name=″QoSInfo″ type=″QoSInfoType″/> <element name=″QoSInfoRef″ type=″dia:ReferenceType″/> </choice> <choice minOccurs=″0″> <element name=″MappingInfo″ type=″MappingInfoType″/> <element name=″MappingInfoRef″ type=″dia:ReferenceType″/> </choice> <element name=″PreviousIntervalsRef″ type=“IntervalsRefType″ minOccurs=″0″/> <element name=″NextIntervalsRef″ type=“IntervalsRefType″ minOccurs=″0″/> </sequence> </extension> </complexContent> </complexType> - The following Table 12 shows syntax representation of IntervalInfoType in the XML format.
-
TABLE 12 <complexType name=“IntervalInfoType″> <sequence> <element name=“TimeScale“ type=“integer″ minOccurs=″0″/> <element name=“StartTime“ type=“dateTime″ minOccurs=″0″/> <element name=“Duration“ type=“integer″ minOccurs=″0″/> <element name=“DefaultFragDuration“ type=“integer” minOccurs=″0″/> <element name=“DefaultContentIntLoc“ type=“anyURI” minOccurs=″0″/> <element name=“Last“ type=“boolean″ minOccurs=″0″/> </sequence> </complexType> - The following Table 13 shows syntax representations of ISOFileBoundaryType and ByteRangesType in the XML format.
-
TABLE 13 <complexType name=”ISOFileBoundaryType”> <sequence> <element name=“SequenceNo” type=“integer” maxOccurs=″unbounded″/> </sequence> </complexType> <complexType name=”ByteRangesType”> <sequence maxOccurs=″unbounded″> <element name=“Start” type=“integer”/> <element name=“End” type=“integer”/> <element name=“Media_PID” type=“integer” minOccurs=″0″/> </sequence> </complexType> - Hereinafter, syntax representation in an MP4 pseudo-code format be described. Representation of the above syntax elements may be provided in the MP4 pseudo-code format.
- The following Table 14 shows syntax representation of HTTPStreamingBox in the MP4 pseudo-code format.
-
TABLE 14 HTTPStreamingBox Box Type: ‘htps’ Container: Signaling file Mandatory: Yes Quantity: One Aligned(8) class HTTPStreamingBox extends Box(‘htps’) { } -
FIG. 4 is a diagram illustrating detecting of virtual boundaries in an MPEG-2 TS according to an embodiment of the present invention. - In a TS, PCR packets of a given program may be carried with fixed PIDs (namely, PCR_PID), and may be inserted at least every 100 ms.
- The PCT packets (with increasing values) may be considered as anchor points of the program. On the other hand, each media of a program may be carried by packets of a given PID (namely, Media_PID).
- Accordingly, a fragment boundary of a media stream may be defined or identified by 1) a specific anchor point and 2) an offset from the anchor to the packet at the boundary.
- The offset may be counted by the packets of the same Media_PID.
- PCR values may be occasionally reset (discontinuity). For example, when one or more PCR packets have the same PCR value in an interval, an appearance order of PCR packets used as anchors may be indicated.
- A sourceURL attribute may be changed from required to optional. This is because haseURL already provides a complete URL. The sourceURL may be unnecessary.
- The use of multiple byte ranges may provide flexibility in downloading “virtual segments.” For example, a segment of a low frame rate (that is able to be used in a trickmode) may be extracted on-the-fly from a stream or an original segment.
- In addition, to support using multiple URLs for a Representation, the following modifications may be applied to the schema of 3GPP Adaptive HTTP Streaming.
- Hereinafter, Multiple Locations for the Same Resource/Content will be Described.
- Each level of description (a top-level, a Period level, and a Representation level) may provide only a single BaseURL for building absolute URLs from the description.
- Multiple BaseURLs may be provided at each description level. Multiple BaseURLs may signal availability of resources at multiple locations.
- Depending on an actual location of a client, the client may select one or more BaseURLs in a process of retrieving resources.
- Such a modification may be implemented by different ways. One way may be to use an additional attribute called “more baseURLs,” or an element called “BaseURLs.”
- The attribute or element may be a string formed of multiple (base) URLs. The string may be separated by several special characters, for example “;” (namely, a semicolon and a space).
- For example, when a semicolon or space appears within a URL, the semicolon or space may be encoded by the rules of RFC 2616.
- The morebaseURLs attribute (or BaseURLs element) of a lower description level may override the same attribute (or element) of the higher description level.
- For clarity, the morebaseURLs attribute and BaseURLs element may be restricted to be mutually exclusive. In other words, only a single type may exist in a whole description.
- Another way may be to use a MoreBaseURL element of any URI type with multiple instances, where each instance provides a BaseURL.
- The different ways may be merely examples of ideas for providing multiple BaseURLs. The ideas may be implemented in many other ways or even other languages.
- Hereinafter, multiple locations for resource/content components will be described.
- Resource/content may be divided into one or more components/streams. Each of the one or more components/streams may be delivered from a location. The delivering may be supported by allowing multiple instances of an UrlTemplate element or a Url element set in SegmentInfoType. A modification “<xs:choice maxOccurs=“unbounded”>” in SegmentInfoType may be used for the above purpose.
- The appearance order of an UrlTemplate instance or a Url set instance may indicate importance of “location/stream.” A more important location may appear before a less important location. For example, a video Representation may include two streams (for example, a spatial base layer, and a spatial enhancement layer). Each of the two streams may be delivered from a location described by UrlTemplate. Subsequently, the first instance of UrlTemplate may be a location for the spatial base layer.
- Moreover, multiple instances of InitialisationSegmentURL may be allowed. An nth instance of InitialisationSegmentURL may correspond to an nth instance of a location (by either the UrlTemplate element or the Url element set).
- For example, when only a single instance of InitialisationSegmentURL exists, the instance may be used for all locations.
- The following Tables 15 through 19 show the schema of 3GPP AdaptiveHTTPStreaming.
-
TABLE 15 <?xml version=″1.0″ encoding=″UTF-8″?> <xs:schema targetNamespace=″urn:3GPP:ns:PSS:AdaptiveHTTPStreamingMPD:2009″ attributeFormDefault=″unqualified″ elementFormDefault=″qualified″ xmlns:xs=″http://www.w3.org/2001/XMLSchema″ xmlns=″urn:3GPP:ns:PSS:AdaptiveHTTPStreamingMPD:2009″> <xs:annotation> <xs:appinfo>Media Presentation Description</xs:appinfo> <xs:documentation xml:lang=″en″> This Schema defines 3GPP Media Presentation Description! </xs:documentation> </xs:annotation> <!-- MPD: main element --> <xs:element name=″MPD″ type=″MPDtype″/> <!-- MPD Type --> <xs:complexType name=″MPDtype″> <xs:sequence> <xs:element minOccurs=″0″ name=″ProgramInformation″ type=″ProgramInformationType″/> <xs:choice maxOccurs=″unbounded″> <xs:element name=″Period″ type=″PeriodType″/> <xs:element name=″PeriodsRef″ type=″PeriodsRefType″/> </xs:choice> <xs:element minOccurs=″0″ name=″BaseUrls″ type=″xs:string″/> <xs:element minOccurs=″0″ maxOccurs=″unbounded″ name=″MoreBaseUrl″ type=″xs:anyURI″/> <xs:any namespace=″##other″ processContents=″lax″ minOccurs=″0″ maxOccurs=″unbounded″/> </xs:sequence> <xs:attribute default=″OnDemand″ name=″type″ type=″PresentationType″/> <xs:attribute name=″availabilityStartTime″ type=″xs:dateTime″/> <xs:attribute name=″availabilityEndTime″ type=″xs:dateTime″/> <xs:attribute name=″mediaPresentationDuration″ type=″xs:duration″/> <xs:attribute name=″minimumUpdatePeriodMPD″ type=″xs:duration″/> <xs:attribute name=″minBufferTime″ type=″xs:duration″ use=″required″/> <xs:attribute name=″timeShiftBufferDepth″ type=″xs:duration″/> <xs:attribute name=″baseUrl″ type=″xs:anyURI″/> <xs:attribute name=″morebaseUrls″ type=″xs:string″/> <xs:anyAttribute namespace=″##other″ processContents=″lax″/> </xs:complexType> <xs:complexType name=“PeriodsRefType″> <xs:sequence> <xs:element name=“Location″ type=″xs:anyURI″/> </xs:sequence> <xs:attribute name=″startTime″ type=″xs:duration″/> <xs:attribute name=″duration″ type=″xs:duration″/> <xs:attribute name=″availableTime″ type=″xs:duration″/> </xs:complexType> -
TABLE 16 <!-- Type of presentation - live or on-demand --> <xs:simpleType name=“PresentationType”> <xs:restriction base=“xs:string”> <xs:enumeration value=“OnDemand”/> <xs:enumeration value=“Live”/> </xs:restriction> </xs:simpleType> <!-- Period of a presentation --> <xs:complexType name=“PeriodType”> <xs:sequence> <xs:element minOccurs=“0” name=“SegmentInfoDefault” type=“SegmentInfoDefaultType”/> <xs:element maxOccurs=“unbounded” name=“Representation” type=“RepresentationType”/> <xs:element minOccurs=“0” name=“PreviousPeriodsRef” type=“xs:PeriodsRef”/> <xs:element minOccurs=“0” name=“NextPeriodsRef” type=“xs:PeriodsRef”/> <xs:any namespace=“##other” processContents=“lax” minOccurs=“0” maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute name=“start” type=“xs:duration”/> <xs:attribute default=“false” name=“segmentAlignmentFlag” type=“xs:boolean”/> <xs:attribute default=“false” name=“bitStreamSwitchingFlag” type=“xs:boolean”/> <xs:attribute default=“false” name=“lastPeriodFlag” type=“xs:boolean”/> <xs:anyAttribute namespace=“##other” processContents=“lax”/> </xs:complexType> <!-- Program information for a presentation --> <xs:complexType name=“ProgramInformationType”> <xs:sequence> <xs:element minOccurs=“0” name=“Title” type=“xs:string”/> <xs:element minOccurs=“0” name=“Source” type=“xs:string”/> <xs:element minOccurs=“0” name=“Copyright” type=“xs:string”/> <xs:any namespace=“##other” processContents=“lax” minOccurs=“0” maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute name=“moreInformationURL” type=“xs:anyURI”/> <xs:anyAttribute namespace=“##other” processContents=“lax”/> </xs:complexType> -
TABLE 17 <!-- Default Segment access information --> <xs:complexType name=“SegmentInfoDefaultType”> <xs:sequence> <xs:element minOccurs=“0” name=“BaseUrls” type=“xs:string”/> <xs:element minOccurs=“0” maxOccurs=“unbounded” name=“MoreBaseUrl” type=“xs:anyURI”/> <xs:any namespace=“##other” processContents=“lax” minOccurs=“0” maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute name=“baseURL” type=“xs:anyURI”/> <xs:attribute name=“morebaseUrls” type=“xs:string”/> <xs:attribute name=“duration” type=“xs:duration”/> <xs:attribute name=“sourceUrlTemplatePeriod” type=“xs:string”/> <xs:anyAttribute namespace=“##other” processContents=“lax”/> </xs:complexType> <!-- A Representation of the presentation content for a specific Period --> <xs:complexType name=“RepresentationType”> <xs:sequence> <xs:element name=“SegmentInfo” type=“SegmentInfoType”/> <xs:element minOccurs=“0” name=“ContentProtection” type=“ContentProtectionType”/> <xs:element minOccurs=“0” name=“TrickMode” type=“TrickModeType”/> <xs:element minOccurs=“0” maxOccurs=“unbounded” name=“Quality” type=“QualityType”/> <xs:any namespace=“##other” processContents=“lax” minOccurs=“0” maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute name=“bandwidth” type=“xs:unsignedInt” use=“required”/> <xs:attribute default=“0” name=“group” type=“xs:unsignedInt”/> <xs:attribute name=“width” type=“xs:unsignedInt”/> <xs:attribute name=“height” type=“xs:unsignedInt”/> <xs:attribute name=“lang” type=“xs:string”/> <xs:attribute name=“mimeType” type=“xs:string” use=“required”/> <xs:attribute default=“false” name=“startWithRAP” type=“xs:boolean”/> <xs:attribute name=“qualityRanking” type=“xs:unsignedInt”/> <xs:attribute name=“requestPara” type=“xs:string”/> <xs:anyAttribute namespace=“##other” processContents=“lax”/> </xs:complexType> <xs:complexType name=“QualityType”> <xs:sequence> <xs:any namespace=“##other” processContents=“lax” minOccurs=“0” maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute name=“name” type=“xs:QualityNameType”/> <xs:attribute name=“value” type=“xs:float”/> </xs:complexType> -
TABLE 18 <xs:simpleType name=″QualityNameType″> <xs:restriction base=″xs:string″> <xs:enumeration value=″PSNR″/> <xs:enumeration value=″MOS″/> <xs:enumeration value=″ODG″/> <xs:enumeration value=″DI″/> </xs:restriction> </xs:simpleType> <!-- Segment access information --> <xs:complexType name=″SegmentInfoType″> <xs:sequence> <xs:element minOccurs=″0″ name=″BaseUrls″ type=″xs:string″/> <xs:element minOccurs=″0″ maxOccurs=″unbounded″ name=″MoreBaseUrl″ type=″xs:anyURI″/> <xs:element minOccurs=″0″ maxOccurs=”unbounded” name=″InitialisationSegmentURL″ type=″UrlType″/> <xs:choice maxOccurs=”unbounded”> <xs:element minOccurs=″0″ name=″UrlTemplate″ type=″UrlTemplateType″/> <xs:sequence> <xs:element maxOccurs=″unbounded″ name=″Url″ type=″UrlType″/> <xs:any namespace=″##other″ processContents=″lax″ minOccurs=″0″ maxOccurs=″unbounded″/> </xs:sequence> <xs:any namespace=″##other″ processContents=″lax″ minOccurs=″0″ maxOccurs=″unbounded″/> </xs:choice> </xs:sequence> <xs:attribute name=″baseURL″ type=″xs:anyURI″/> <xs:attribute name=″morebaseUrls″ type=″xs:string″/> <xs:attribute name=″duration″ type=″xs:duration″/> <xs:attribute name=″randAccess″ type=″xs:string″/> <xs:anyAttribute namespace=″##other″ processContents=″lax″/> </xs:complexType> <!-- A Segment URL --> <xs:complexType name=″UrlType″> <xs:sequence> <xs:any namespace=″##other″ processContents=″lax″ minOccurs=″0″ maxOccurs=″unbounded″/> </xs:sequence> <xs:attribute name=″sourceURL″ type=″xs:anyURI″ use=″optional″/> <xs:attribute name=″range″ type=″xs:string″/> <xs:anyAttribute namespace=″##other″ processContents=″lax″/> </xs:complexType> -
TABLE 19 <!-- A URL template --> <xs:complexType name=“UrlTemplateType”> <xs:sequence> <xs:any namespace=“##other” processContents=“lax” minOccurs=“0” maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute name=“sourceURL” type=“xs:anyURI”/> <xs:attribute name=“id” type=“xs:string”/> <xs:attribute default=“1” name=“startIndex” type=“xs:unsignedInt”/> <xs:attribute name=“endIndex” type=“xs:unsignedInt”/> <xs:anyAttribute namespace=“##other” processContents=“lax”/> </xs:complexType> <!-- Gives information about the content protection --> <xs:complexType name=“ContentProtectionType”> <xs:sequence> <xs:element minOccurs=“0” name=“SchemeInformation” type=“xs:string”/> <xs:any namespace=“##other” processContents=“lax” minOccurs=“0” maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute name=“schemeIdUri” type=“xs:anyURI”/> <xs:anyAttribute namespace=“##other” processContents=“lax”/> </xs:complexType> <!-- Gives information about trick mode --> <xs:complexType name=“TrickModeType”> <xs:sequence> <xs:any namespace=“##other” processContents=“lax” minOccurs=“0” maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute name=“alternatePlayoutRate” type=“xs:string”/> <xs:anyAttribute namespace=“##other” processContents=“lax”/> </xs:complexType> </xs:schema> -
FIG. 5 is a diagram illustrating a configuration of the terminal 100 according to an embodiment of the present invention. - A
controller 510 may performoperations controller 510 may process the metadata of the interval. - A
transceiver 520 that selects a fragment suitable for the interval based on the processing may performoperations transceiver 520 may receive the metadata of the interval of the content from theserver 110, may send a request for the fragment suitable for the interval to the server, and may receive the fragment from the server. -
FIG. 6 is a diagram illustrating a configuration of the terminal 100 according to an embodiment of the present invention. - The terminal 100 may include an
access engine 610, and amedia engine 620. - The
access engine 610 may be a access engine. - The
access engine 610 may receive metadata (for example, an MPD) from theserver 110. - The
access engine 610 may form requests, and may issue the formed requests to theserver 110. Theaccess engine 610 may receive media (for example, segments or parts of the segments) from theserver 110. The access engine may request a segment of the media using a URL of the segment. - The
access engine 610 may receive segments of the media based on information provided by the metadata. Here, each period may include one or more groups, and each of the groups may include one or more representations of the media. Each of the representations may include one or more segments. - The
access engine 610 may provide the media to themedia engine 620. Theaccess engine 610 may decode data of the media included in the segments. - An output of the
access engine 610 may include media (or a part of the media) of an MPEG container (for example, an ISO/IEC 14492-12 ISO base media file format, or an ISO/IEC 13818-2 MPEG-2 TS) Additionally, the output of theaccess engine 610 may include timing information used to map internal timing of the media to a timeline of a media presentation. - The
media engine 620 may play back the provided media. Specifically, themedia engine 620 may receive data of the media from the access engine, and may output the media. Themedia engine 620 may output the media using the data of the media and the timing information that are output from theaccess engine 610. - Technical information according to the embodiments of the present invention described above with reference to
FIGS. 1 through 5 may equally be applied to the present embodiment. Accordingly, further description thereof will be omitted. - The method according to the above-described embodiments of the present invention may be recorded in computer-readable media including program instructions to implement various operations embodied by a computer. The media may also include, alone or in combination with the program instructions, data files, data structures, and the like. The program instructions recorded on the media may be those specially designed and constructed for the purposes of the embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable media include magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD ROM disks and DVDs; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory (ROM), random access memory (RAM), flash memory, and the like. Examples of program instructions include both machine code, such as produced by a compiler, and files containimg higher level code that may be executed by the computer using an interpreter. The described hardware devices may be configured to act as one or more software modules in order to perform the operations of the above-described embodiments of the present invention, or vice versa.
- Although a few embodiments of the present invention have been shown and described, the present invention is not limited to the described embodiments. Instead, it would be appreciated by those skilled in the art that changes may be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/228,097 US10277660B1 (en) | 2010-09-06 | 2018-12-20 | Apparatus and method for providing streaming content |
Applications Claiming Priority (14)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US38027710P | 2010-09-06 | 2010-09-06 | |
US39032810P | 2010-10-06 | 2010-10-06 | |
US40567410P | 2010-10-22 | 2010-10-22 | |
US41446210P | 2010-11-17 | 2010-11-17 | |
US41793110P | 2010-11-30 | 2010-11-30 | |
US201161434036P | 2011-01-19 | 2011-01-19 | |
PCT/KR2011/006573 WO2012033319A2 (en) | 2010-09-06 | 2011-09-06 | Apparatus and method for providing streaming content |
KR10-2011-0089923 | 2011-09-06 | ||
KR1020110089923A KR101206111B1 (en) | 2010-09-06 | 2011-09-06 | Apparatus and method for providing streaming contents |
US201313820955A | 2013-03-05 | 2013-03-05 | |
US14/146,500 US9467493B2 (en) | 2010-09-06 | 2014-01-02 | Apparatus and method for providing streaming content |
US15/287,260 US10027736B2 (en) | 2010-09-06 | 2016-10-06 | Apparatus and method for providing streaming content |
US16/036,703 US20180324241A1 (en) | 2010-09-06 | 2018-07-16 | Apparatus and method for providing streaming content |
US16/228,097 US10277660B1 (en) | 2010-09-06 | 2018-12-20 | Apparatus and method for providing streaming content |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/036,703 Continuation US20180324241A1 (en) | 2010-09-06 | 2018-07-16 | Apparatus and method for providing streaming content |
Publications (2)
Publication Number | Publication Date |
---|---|
US20190124132A1 true US20190124132A1 (en) | 2019-04-25 |
US10277660B1 US10277660B1 (en) | 2019-04-30 |
Family
ID=50548518
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/146,500 Active 2032-06-02 US9467493B2 (en) | 2010-09-06 | 2014-01-02 | Apparatus and method for providing streaming content |
US15/287,260 Active US10027736B2 (en) | 2010-09-06 | 2016-10-06 | Apparatus and method for providing streaming content |
US16/036,703 Abandoned US20180324241A1 (en) | 2010-09-06 | 2018-07-16 | Apparatus and method for providing streaming content |
US16/228,097 Active US10277660B1 (en) | 2010-09-06 | 2018-12-20 | Apparatus and method for providing streaming content |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/146,500 Active 2032-06-02 US9467493B2 (en) | 2010-09-06 | 2014-01-02 | Apparatus and method for providing streaming content |
US15/287,260 Active US10027736B2 (en) | 2010-09-06 | 2016-10-06 | Apparatus and method for providing streaming content |
US16/036,703 Abandoned US20180324241A1 (en) | 2010-09-06 | 2018-07-16 | Apparatus and method for providing streaming content |
Country Status (1)
Country | Link |
---|---|
US (4) | US9467493B2 (en) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20120034550A (en) | 2010-07-20 | 2012-04-12 | 한국전자통신연구원 | Apparatus and method for providing streaming contents |
US9467493B2 (en) * | 2010-09-06 | 2016-10-11 | Electronics And Telecommunication Research Institute | Apparatus and method for providing streaming content |
CN103493499B (en) | 2011-03-16 | 2018-04-06 | 韩国电子通信研究院 | Device and method using the streaming medium content represented is provided |
CN103975602B (en) * | 2011-10-20 | 2017-06-09 | Lg电子株式会社 | Broadcasting service reception method and broadcasting service reception device |
FR2996715A1 (en) * | 2012-10-09 | 2014-04-11 | France Telecom | HERITAGE OF UNIVERSAL RESOURCE IDENTIFIER PARAMETERS (URI) |
US10135896B1 (en) * | 2014-02-24 | 2018-11-20 | Amazon Technologies, Inc. | Systems and methods providing metadata for media streaming |
GB2528039A (en) * | 2014-07-01 | 2016-01-13 | Canon Kk | Method for identifying objects across time periods and corresponding device |
US10587934B2 (en) * | 2016-05-24 | 2020-03-10 | Qualcomm Incorporated | Virtual reality video signaling in dynamic adaptive streaming over HTTP |
CN112188905B (en) | 2018-05-25 | 2022-12-20 | 施曼信医疗Asd公司 | Systems and methods for improving operation of infusion pumps |
Family Cites Families (96)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030093790A1 (en) | 2000-03-28 | 2003-05-15 | Logan James D. | Audio and video program recording, editing and playback systems using metadata |
US7330875B1 (en) | 1999-06-15 | 2008-02-12 | Microsoft Corporation | System and method for recording a presentation for on-demand viewing over a computer network |
US20050193425A1 (en) | 2000-07-24 | 2005-09-01 | Sanghoon Sull | Delivery and presentation of content-relevant information associated with frames of audio-visual programs |
US20050203927A1 (en) | 2000-07-24 | 2005-09-15 | Vivcom, Inc. | Fast metadata generation and delivery |
US20050204385A1 (en) | 2000-07-24 | 2005-09-15 | Vivcom, Inc. | Processing and presentation of infomercials for audio-visual programs |
US20050193408A1 (en) | 2000-07-24 | 2005-09-01 | Vivcom, Inc. | Generating, transporting, processing, storing and presenting segmentation information for audio-visual programs |
AU2001283004A1 (en) | 2000-07-24 | 2002-02-05 | Vivcom, Inc. | System and method for indexing, searching, identifying, and editing portions of electronic multimedia files |
US7512665B1 (en) * | 2000-08-17 | 2009-03-31 | International Business Machines Corporation | Chained uniform resource locators |
US20050273514A1 (en) | 2000-12-22 | 2005-12-08 | Ray Milkey | System and method for automated and optimized file transfers among devices in a network |
FI118830B (en) | 2001-02-08 | 2008-03-31 | Nokia Corp | Streaming playback |
US20050005308A1 (en) | 2002-01-29 | 2005-01-06 | Gotuit Video, Inc. | Methods and apparatus for recording and replaying sports broadcasts |
US20030069991A1 (en) | 2001-10-09 | 2003-04-10 | Brescia Paul T. | Location-based address provision |
US7739601B1 (en) | 2002-01-23 | 2010-06-15 | Microsoft Corporation | Media authoring and presentation |
CN1650628B (en) | 2002-02-25 | 2010-10-13 | 索尼电子有限公司 | Method and apparatus for supporting AVC in MP4 |
US7451229B2 (en) * | 2002-06-24 | 2008-11-11 | Microsoft Corporation | System and method for embedding a streaming media format header within a session description message |
US7418494B2 (en) | 2002-07-25 | 2008-08-26 | Intellectual Ventures Holding 40 Llc | Method and system for background replication of data objects |
KR100486713B1 (en) | 2002-09-17 | 2005-05-03 | 삼성전자주식회사 | Apparatus and method for streaming multimedia data |
US7535900B2 (en) | 2003-01-21 | 2009-05-19 | Symmetricom, Inc. | Multiple transmission bandwidth streams with defferentiated quality of service |
KR20040096718A (en) | 2003-05-10 | 2004-11-17 | 삼성전자주식회사 | Multimedia data decoding apparatus, audio data receiving method and audio data structure therein |
JP4340483B2 (en) | 2003-06-27 | 2009-10-07 | 富士通株式会社 | Composite content delivery method and delivery system |
JP2005071318A (en) | 2003-08-01 | 2005-03-17 | Toshiyuki Yamamoto | Homepage management device |
US20050102371A1 (en) | 2003-11-07 | 2005-05-12 | Emre Aksu | Streaming from a server to a client |
KR100563659B1 (en) | 2003-12-09 | 2006-03-23 | 한국전자통신연구원 | Real-time streaming service apparatus |
KR101022471B1 (en) | 2004-01-17 | 2011-03-16 | 삼성전자주식회사 | Information storage medium containing multimedia data, reproducing method and apparatus thereof |
US8218439B2 (en) | 2004-11-24 | 2012-07-10 | Sharp Laboratories Of America, Inc. | Method and apparatus for adaptive buffering |
US7680785B2 (en) | 2005-03-25 | 2010-03-16 | Microsoft Corporation | Systems and methods for inferring uniform resource locator (URL) normalization rules |
US20060235883A1 (en) | 2005-04-18 | 2006-10-19 | Krebs Mark S | Multimedia system for mobile client platforms |
KR101008698B1 (en) | 2005-05-03 | 2011-01-17 | 노키아 코포레이션 | Signaling quality of service QOS parameters for a multimedia session |
WO2007134196A2 (en) | 2006-05-10 | 2007-11-22 | Digital Fountain, Inc. | Code generator and decoder using hybrid codes |
US9386064B2 (en) | 2006-06-09 | 2016-07-05 | Qualcomm Incorporated | Enhanced block-request streaming using URL templates and construction rules |
US9209934B2 (en) | 2006-06-09 | 2015-12-08 | Qualcomm Incorporated | Enhanced block-request streaming using cooperative parallel HTTP and forward error correction |
US9380096B2 (en) | 2006-06-09 | 2016-06-28 | Qualcomm Incorporated | Enhanced block-request streaming system for handling low-latency streaming |
US9432433B2 (en) | 2006-06-09 | 2016-08-30 | Qualcomm Incorporated | Enhanced block-request streaming system using signaling or block creation |
US20080034424A1 (en) | 2006-07-20 | 2008-02-07 | Kevin Overcash | System and method of preventing web applications threats |
US7711797B1 (en) | 2006-07-31 | 2010-05-04 | Juniper Networks, Inc. | Optimizing batch size for prefetching data over wide area networks |
KR20080018778A (en) | 2006-08-25 | 2008-02-28 | 삼성전자주식회사 | Method, av cp device and home network system for performing av contents with segment unit |
CN101155260A (en) * | 2006-09-30 | 2008-04-02 | 华为技术有限公司 | Control method, authentication method and server for electronic equipments |
US20080155602A1 (en) | 2006-12-21 | 2008-06-26 | Jean-Luc Collet | Method and system for preferred content identification |
US8069260B2 (en) | 2007-01-12 | 2011-11-29 | Microsoft Corporation | Dynamic buffer settings for media playback |
US8533310B2 (en) | 2007-03-09 | 2013-09-10 | Riverbed Technology, Inc. | Method and apparatus for acceleration by prefetching associated objects |
JP2008259001A (en) | 2007-04-06 | 2008-10-23 | Japan Radio Co Ltd | Digital content distribution system |
US9542394B2 (en) | 2007-06-14 | 2017-01-10 | Excalibur Ip, Llc | Method and system for media-based event generation |
JP5018560B2 (en) * | 2007-09-03 | 2012-09-05 | ソニー株式会社 | IPTV client terminal, SIP-INVITE message generation method, IPTV system, IPTV session control method, computer program, IPTV client system, and session management apparatus |
US8635360B2 (en) | 2007-10-19 | 2014-01-21 | Google Inc. | Media playback point seeking using data range requests |
US20090157859A1 (en) * | 2007-12-17 | 2009-06-18 | Morris Robert P | Methods And Systems For Accessing A Resource Based On URN Scheme Modifiers |
US8365271B2 (en) | 2008-02-27 | 2013-01-29 | International Business Machines Corporation | Controlling access of a client system to access protected remote resources supporting relative URLs |
US7925774B2 (en) | 2008-05-30 | 2011-04-12 | Microsoft Corporation | Media streaming using an index file |
US20100011274A1 (en) | 2008-06-12 | 2010-01-14 | Qualcomm Incorporated | Hypothetical fec decoder and signalling for decoding control |
US20100107090A1 (en) * | 2008-10-27 | 2010-04-29 | Camille Hearst | Remote linking to media asset groups |
CA2742416A1 (en) | 2008-10-30 | 2010-05-06 | Nokia Corporation | Method and apparatus for interleaving a data block |
US8209609B2 (en) | 2008-12-23 | 2012-06-26 | Intel Corporation | Audio-visual search and browse interface (AVSBI) |
US20100169458A1 (en) | 2008-12-31 | 2010-07-01 | David Biderman | Real-Time or Near Real-Time Streaming |
US9281847B2 (en) | 2009-02-27 | 2016-03-08 | Qualcomm Incorporated | Mobile reception of digital video broadcasting—terrestrial services |
US8621044B2 (en) | 2009-03-16 | 2013-12-31 | Microsoft Corporation | Smooth, stateless client media streaming |
US8909806B2 (en) | 2009-03-16 | 2014-12-09 | Microsoft Corporation | Delivering cacheable streaming media presentations |
US8793282B2 (en) | 2009-04-14 | 2014-07-29 | Disney Enterprises, Inc. | Real-time media presentation using metadata clips |
US20130298170A1 (en) | 2009-06-12 | 2013-11-07 | Cygnus Broadband, Inc. | Video streaming quality of experience recovery using a video quality metric |
US9538220B2 (en) | 2009-06-12 | 2017-01-03 | Wi-Lan Labs, Inc. | Video streaming quality of experience degradation control using a video quality metric |
US20130290492A1 (en) | 2009-06-12 | 2013-10-31 | Cygnus Broadband, Inc. | State management for video streaming quality of experience degradation control and recovery using a video quality metric |
US8201204B2 (en) | 2009-07-31 | 2012-06-12 | Cisco Technology, Inc. | Minimizing black video segments during ad insertion |
US9015564B2 (en) | 2009-08-19 | 2015-04-21 | Qualcomm Incorporated | Content delivery system with allocation of source data and repair data among HTTP servers |
US20110096828A1 (en) | 2009-09-22 | 2011-04-28 | Qualcomm Incorporated | Enhanced block-request streaming using scalable encoding |
US9917874B2 (en) | 2009-09-22 | 2018-03-13 | Qualcomm Incorporated | Enhanced block-request streaming using block partitioning or request controls for improved client-side handling |
US9237387B2 (en) | 2009-10-06 | 2016-01-12 | Microsoft Technology Licensing, Llc | Low latency cacheable media streaming |
RU2622621C2 (en) | 2009-11-04 | 2017-06-16 | Амотек Ко., Лтд. | System and method for flow transfer of reproduced content |
EP2510669A4 (en) | 2009-12-11 | 2013-09-18 | Nokia Corp | Apparatus and methods for describing and timing representations in streaming media files |
CN102771134B (en) | 2010-01-18 | 2016-04-13 | 瑞典爱立信有限公司 | For supporting method and the device of play content |
RU2690755C2 (en) | 2010-02-19 | 2019-06-05 | Телефонактиеболагет Л М Эрикссон (Пабл) | Method and apparatus for switching playback in streaming via hypertext transfer protocol |
US9596522B2 (en) * | 2010-06-04 | 2017-03-14 | Mobitv, Inc. | Fragmented file structure for live media stream delivery |
US8918533B2 (en) | 2010-07-13 | 2014-12-23 | Qualcomm Incorporated | Video switching for streaming video data |
US9185439B2 (en) | 2010-07-15 | 2015-11-10 | Qualcomm Incorporated | Signaling data for multiplexing video components |
US9131033B2 (en) | 2010-07-20 | 2015-09-08 | Qualcomm Incoporated | Providing sequence data sets for streaming video data |
WO2012010928A1 (en) | 2010-07-20 | 2012-01-26 | Nokia Corporation | A media streaming apparatus |
WO2012011450A1 (en) | 2010-07-20 | 2012-01-26 | シャープ株式会社 | Content distribution device, content playback device, content distribution system, method for controlling a content distribution device, control program, and recording medium |
KR20120034550A (en) | 2010-07-20 | 2012-04-12 | 한국전자통신연구원 | Apparatus and method for providing streaming contents |
US8782268B2 (en) * | 2010-07-20 | 2014-07-15 | Microsoft Corporation | Dynamic composition of media |
TW201210325A (en) | 2010-07-21 | 2012-03-01 | Nokia Corp | Method and apparatus for indicating switching points in a streaming session |
US8190677B2 (en) * | 2010-07-23 | 2012-05-29 | Seawell Networks Inc. | Methods and systems for scalable video delivery |
US8806050B2 (en) | 2010-08-10 | 2014-08-12 | Qualcomm Incorporated | Manifest file updates for network streaming of coded multimedia data |
EP2604031B1 (en) | 2010-08-10 | 2017-03-08 | Google Technology Holdings LLC | Method and apparatus for streaming media content using variable duration media segments |
EP2615841B1 (en) * | 2010-09-06 | 2017-12-13 | Electronics And Telecommunications Research Institute | Apparatus and method for providing streaming content |
US9467493B2 (en) * | 2010-09-06 | 2016-10-11 | Electronics And Telecommunication Research Institute | Apparatus and method for providing streaming content |
WO2012032502A1 (en) | 2010-09-10 | 2012-03-15 | Nokia Corporation | A method and apparatus for adaptive streaming |
KR101206698B1 (en) * | 2010-10-06 | 2012-11-30 | 한국항공대학교산학협력단 | Apparatus and method for providing streaming contents |
WO2012065186A2 (en) | 2010-11-12 | 2012-05-18 | Realnetworks, Inc. | Traffic management in adaptive streaming protocols |
US8812621B2 (en) | 2011-05-03 | 2014-08-19 | Cisco Technology, Inc. | Reducing fetching load on cache servers in adaptive streaming |
JP2013038766A (en) | 2011-07-12 | 2013-02-21 | Sharp Corp | Transmitter, transmitter control method, control program, and recording medium |
US20130042100A1 (en) | 2011-08-09 | 2013-02-14 | Nokia Corporation | Method and apparatus for forced playback in http streaming |
US8468145B2 (en) * | 2011-09-16 | 2013-06-18 | Google Inc. | Indexing of URLs with fragments |
US20130182643A1 (en) | 2012-01-16 | 2013-07-18 | Qualcomm Incorporated | Method and system for transitions of broadcast dash service receptions between unicast and broadcast |
CN104040993A (en) | 2012-01-17 | 2014-09-10 | 瑞典爱立信有限公司 | Method for sending respectively receiving media stream |
US9264481B2 (en) | 2012-03-30 | 2016-02-16 | Qualcomm Incorporated | Responding to hypertext transfer protocol (HTTP) requests |
FR2996715A1 (en) * | 2012-10-09 | 2014-04-11 | France Telecom | HERITAGE OF UNIVERSAL RESOURCE IDENTIFIER PARAMETERS (URI) |
US20140258861A1 (en) | 2013-03-08 | 2014-09-11 | James A. Baldwin | Content presentation with secondary content skip |
KR20150012206A (en) * | 2013-07-24 | 2015-02-03 | 한국전자통신연구원 | Method and apparatus for encoding three dimensoional content |
CN106034262B (en) * | 2015-03-13 | 2021-01-22 | 中兴通讯股份有限公司 | Adaptive streaming media processing method and device |
-
2014
- 2014-01-02 US US14/146,500 patent/US9467493B2/en active Active
-
2016
- 2016-10-06 US US15/287,260 patent/US10027736B2/en active Active
-
2018
- 2018-07-16 US US16/036,703 patent/US20180324241A1/en not_active Abandoned
- 2018-12-20 US US16/228,097 patent/US10277660B1/en active Active
Also Published As
Publication number | Publication date |
---|---|
US20170026451A1 (en) | 2017-01-26 |
US10277660B1 (en) | 2019-04-30 |
US20180324241A1 (en) | 2018-11-08 |
US10027736B2 (en) | 2018-07-17 |
US20140122739A1 (en) | 2014-05-01 |
US9467493B2 (en) | 2016-10-11 |
US20160269461A9 (en) | 2016-09-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9338211B2 (en) | Apparatus and method for providing streaming content | |
US10819815B2 (en) | Apparatus and method for providing streaming content | |
US8909805B2 (en) | Apparatus and method for providing streaming content | |
US10277660B1 (en) | Apparatus and method for providing streaming content | |
US20180288125A1 (en) | Apparatus and method for providing streaming content | |
KR102042213B1 (en) | Apparatus and method for providing streaming contents | |
KR102272853B1 (en) | Apparatus and method for providing streaming contents |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: IDEAHUB INC., KOREA, REPUBLIC OF Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:THANG, TRUONG CONG;LEE, JIN YOUNG;BAE, SEONG JUN;AND OTHERS;REEL/FRAME:047835/0099 Effective date: 20140102 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: HELIOS STREAMING, LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IDEAHUB INC.;REEL/FRAME:058613/0191 Effective date: 20220105 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |