The features described herein relate generally to the delivery of content. Some aspects relate to fragmenting and delivering media content based upon metadata associated with the media content.
Media content is often transmitted via packet-switched networks, such as the Internet, and other small or large area networks. Most media content, including movies, television shows, and music are too large to be transmitted as a single fragment. Further, consumers often prefer to access content without downloading the complete asset Therefore, various algorithms are used to divide media and related data into individual fragments for transmission. Several factors may impact fragment size; however, it is primarily dictated by specific efficiencies for the utilized network(s). Delivering media according to network efficiency has several disadvantages. For example, it does not account for packets containing live content. Even if certain fragments are flagged as important or urgent, other disadvantages persist with current methodologies. For example, a minimum quantity of fragments may be required to be received in one or more caches associated with the end-user's playback device, before initiating playback of the content.
Delivery of content representing real-time or live events becomes increasingly unsatisfactory as the requirements for packets increase. Indeed, as content becomes more interactive, content is often consumed on a real-time basis. For example, many systems require a minimum of three or more fragments to be cached before playback of the media is initiated. If each fragment is three seconds in duration, then the viewer will be at least than nine seconds delayed from real-time. This results in an unsatisfactory experience for viewers of, for example, quick-paced sporting events, interactive shows, such as reality shows with voting options, as well as other types of media. This problem is compounded when a media player is located in a location with several other devices consuming the same or similar content. For example, an entity may transmit or present to viewers a sporting event in which several, (e.g., three) sources are utilized at different display devices throughout an establishment. Different network capabilities coupled with different fragment sizes often results with at least a portion of the devices showing the live event out of synchronization, for example, several seconds and up to a minute behind other devices. This is often distracting and undesirable to entities and users.
Further, other forms of content, such as media, movies, music, and teleconferencing entertainment multimedia is often transmitted using the same or similar sized fragments as media containing real-time and/or live media. In this regard, bandwidth requirements may be unduly elevated. Therefore, there is a need for a scalable solution that allows for different types of media content to be transmitted.
Aspects of the disclosure relate to identifying attributes of media content before access or transmission, such as via a content delivery system. The attributes may be received from metadata, which may be used to determine fragment length. In one embodiment, metadata generally attributable to the content as a whole (or with the entire portion of the content) may be utilized in the determination of fragment size. The metadata may be obtained from an external source, yet in other embodiments, the metadata may already be associated or otherwise linked to the media content. In one embodiment, the metadata, or a portion thereof, may be configured to be accessible from a user interface, such as, for example, an electronic program guide. In one such embodiment, additional resources or expenses of obtaining and/or formatting metadata may be avoided. In another aspect, a content descriptor, based on at least a portion of the metadata associated with the media content, may be utilized to determine a fragment size.
Further aspects relate to dividing or fragmenting the media content into a plurality of ordered fragments. The fragments may represent a linear portion (or representation thereof) of the of the media content. The fragmentation may be virtual, such as a digital flag or marker to identify locations in a single continuous file and/or on a non-transitory memory. Yet in other embodiments, the fragmentation may create individual discrete fragments, segments, or files before transmission of the media. In one embodiment, the content is divided into equally sized fragments as a function of time. The fragmentation may be based, at least in part, on a content descriptor value associated with the content. In certain embodiments, the content descriptor may apply to the whole content (e.g., a sporting event, a comedy show, etc.) and not independent to a portion thereof. In some embodiments, the content descriptor may be the sole basis for the fragment lengths of the content.
In one embodiment, the content descriptor value may relate to whether the media content comprises real-time (inclusive of on-demand and/or interactive content) or live material or relates to a live or ongoing event. In another embodiment, the content descriptor value may relate to one or more genres associated to the media content. Illustrative genres may include, but are not limited to: sports, news, sitcom, reality, action, talk show, teleconference multimedia, or the like. In other embodiments, genres or categories may distinguish between content comprising media relating to: live events, interactive events, and/or on-demand content. In certain embodiments, a first content descriptor value may be derived from multiple forms of metadata, such as for example, genre, sub-genre, presence of live media, and combinations thereof.
Further aspects relate to the structure of the fragments. In one embodiment, division of the media content may be conducted such that each resultant fragment comprises a single i-frame. Yet in further embodiments, fragments may comprise multiple i-frames. In certain embodiments, the content descriptor further determines the quantity of i-frames within each fragment. Various implementations may be performed on media content that has already been transcoded into packets, such as an existing MPEG-4 file.
Other details and features will also be described in the sections that follow. This summary is not intended to identify critical or essential features of the inventions claimed herein, but instead merely summarizes certain features and variations thereof.
Some features herein are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements.
In the following description of the various embodiments, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration various embodiments in which the invention may be practiced. For example, aspects described herein provide a content transcoding and/or delivery system through which content may automatically be fragmented and/or transcoded based upon a content descriptor value. Additionally, various systems and methods may perform the automatic fragmenting/transcoding based upon certain criteria, which in certain embodiments, may be performed without user instruction or specification from user devices. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope of the present disclosure.
Device 102 may be located external to the location 100, such as at a service provider's central server 150 or facility (e.g., a headend, a processing facility, etc.). Device 102 may communicate with one or more other servers 104, which may in turn be connected to an even larger communication network 105. Communication network 105 may be any desired type of network, such as a wide area network (WAN), cellular telephone, satellite network, Internet, Intranet, etc., and may offer connection to even more servers 106. Those other servers 106 may, in turn, provide various types of services such as delivery of media content, and Internet purchasing. As shown, links 103 may be part of communication network 105 in a configuration that does not require presence of central server 150.
In an embodiment, data corresponding to services may be transmitted and received from device 102, central server 150, and/or one or more servers 106. Service data may include broadcast data (e.g. television broadcast programming), narrowcast data (e.g. VOD and switched digital video (SDV) programming) and unicast data (e.g. high speed data (HSD) service providing Internet connectivity to users and VoIP or other type of telephone service). The backbone network may be, e.g. a service operator's national IP network, the Internet, and some combination of the Internet and a service operator's network.
Within location 100, gateway 101 may allow any device in the home to access device 102 and, in turn, any of the other servers 104/106 and network 105. To provide this connectivity, gateway 101 may be connected to one or more in-home communication networks 107 (e.g., in-home coaxial cable, MoCA (Multimedia Over Coax Alliance), Ethernet, power line network, etc.). Other devices, such as a media interface device 108 (e.g., set-top box, digital video recorder, mobile television, television, mobile terminal, etc.), computer 109, or wireless access point 110 may also be connected to the in-home network, and may use the network to communicate with gateway 101. In some embodiments, location 100 may be a home, yet in other embodiments it may be a business establishment. In still further embodiments, it may be any location capable of receiving and/or transmitting electronic data. Location 100 may have multiple gateways, and in other embodiments, some or all of the gateways may be integrated into the various devices described herein. So, for example, video interface device 108 may include gateway 101, but to simplify the present discussion,
The devices of location 100 may use gateway 101 for any variety of purposes, such as accessing the Internet, accessing servers 106, etc. Some devices, such as media interface device 108, may use gateway 101 to receive media content that is then displayed on a display device such as a television, mobile device, or computer monitor 111.
To provide secure access to that content, the supplier of the content (e.g., a content server 106, or server 104), may through the service provide a license to the user to receive and access various media content. In addition, the service provider may also encrypt the content when delivering it to gateway 101 and media interface device 108. Media interface device 108 may need to decrypt the content before displaying it on the display device 111 (which may be integrated with the media interface device 108 in some embodiments).
This decryption may be performed by media interface device 108 using a hierarchy of keys one of which may be a device key that is stored within media device 108. Alternatively, the decryption may be performed by an external security module 112, such as a smart card, that is provided separately to the user. Having the separate smart card 112 may allow customers to purchase media devices 108 from a source other than the content provider, and to merely obtain a small card from the content provider.
Block 204 may be implemented to associate the received content with content metadata/attribute information including, for example, information relating to: genre, sub-genre, time of the content creation (i.e., is it live?), time of scheduled delivery, format of the content (e.g., high definition (HD) vs. standard definition (SD), 1080i, 1080p, 720p) and the like. Such descriptive information may be retrieved from a separate or integral database such as programming guide database 154, located on server 152. The content metadata may be obtained from the media itself, such as metadata located within an MPEG stream, from a third party service, and/or from one or more users. In one embodiment, a metadata assignment module, such as module 104c of server 104 (within central server 150) may be utilized in on or more processes relating to associating metadata with media content, including any processes in relation to block 204. Module 104c may be operatively connected to processor 104a and memory (a non-transitory computer-readable medium) 104b. In one embodiment, memory 104b may store the associated metadata or a portion thereof. In other embodiments, memory 104b may store information linking metadata with the media content.
In one embodiment, information such as a description or commentary (which may be located on programming guide database 154) of the media may be parsed to extract keywords that may be used as the content descriptor, or in the assignment or formation of the content descriptor. Parsing may include removing articles, transition words and the like that are likely to be non-descriptive in nature. Remaining words may then be compared to a database of known descriptive words such as artist, actor or author names, content genres (e.g., sports, talk shows, sitcoms, reality shows, news), or subcategories of the such genres (e.g., types of sports like football or basketball). The known descriptive words may then be stored as keywords in association with the fragmented media content (or media content to be fragmented). Other methods of parsing and identifying keywords may be used to associate keywords and search terms with content items and content item fragments. For example, if the commentary includes audio description or comments, methods of speech recognition and parsing may be used to convert the audio to text, store the text and identify keywords from the converted text.
Looking to chart 300, column 304 provides an indication whether the media content comprises a live event, such as a sporting event. For example, both Sporting Event #1 (row 310) and Sporting Event #2 (row 312) are flagged under column 304 as containing media from a live or on-going event. Determination of whether the media content relates to a live event may be determined from a field indicating the time the media content was captured. Further metadata may include genre (see, e.g., column 306) which may categorize media content based upon a myriad of factors. In certain embodiments, metadata relating to a sub-genre (see, e.g., column 308) may be utilized. For example, if media content 310 and 312 each are categorized in the “Sports” genre, then using a sub-genre may further sub-classify media content 310 as being a football game and media content 312 as being a golf game. Those skilled in the art will readily understand that the genres and sub-genres are merely illustrative examples and that any other categories may be utilized without departing from the scope of this disclosure, including the claims. In this regard, a category that is listed as a “sub-genre” in one embodiment may be a “genre” in another embodiment. Furthermore, live events may be a type of genre or sub-genre. Additional features of
Aspects of this disclosure relate to assigning a content descriptor value to the media content (see block 206 of
The dividing of the media content into fragments may be based, at least in part, on a first content descriptor value associated with and generally attributable to the media content as a whole and not a content descriptor of a particular fragment that resulted from the division. For example, a live sporting event may have non-live advertising materials, such as commercials, inter-dispersed throughout the media content. Nonetheless, the entire media content may accurately be classified as both “live” and “sports”. Further, one or more fields of metadata may be utilized, either individually or in combination with each other or other factors, to divide or fragment the media content. In one embodiment, the content descriptor value assigned to media content may be directly obtained from a single field or value of metadata.
For example, because both Sporting Event #1 and #2 are within the “LIVE” category (see column 304) they may both receive the same content descriptor regardless of any other metadata (such as, for example, genre 306 or sub-genre 308). Therefore, column 330 shows that in one embodiment each of them receives the same content descriptor (“Live”). In contrast, media content 318 through 324 are not live and therefore, will receive a different content descriptor (see column 330). Although the illustrative content descriptor is alphabetic text, those skilled in the art will realize that any indicium that differentiates one descriptor from another descriptor is within the scope of this disclosure. Further, there is no requirement that the content descriptor be separately generated from existing metadata. Rather, existing metadata, such as information from column 304 may serve as the content descriptor. In other embodiments, the content descriptor may be separately generated from the metadata. This may be helpful in embodiments in which, for example, a higher level of categorization may be desired. Further examples and rules for associating a content descriptor with media content are discussed in relation to block 408 below.
Based upon the above examples shown in column 330, the media content (310-324) may be divided or fragmented into a plurality of ordered fragments representing a linear representation of the media content received at block 202 (see, e.g., block 208 of
In one embodiment, a fragmenter, such as fragmenter 104e of server 104 (which may be part of or within central server 150) may be utilized in one or more processes relating to fragmenting the media content, including any processes in relation to block 208 of
Module 104e may be operatively connected to processor 104a and memory (a non-transitory computer-readable medium) 104b. In one embodiment, memory 104b may be configured to store one or more of the fragments. In other embodiments, memory 104b may store information relating to locations within files or segments where “virtual” fragments are located. In yet further embodiments, memory 104b may store computer-executable instructions, that when executed by a processor, such as processor 104a, cause the processor to fragment the files or segments.
In various embodiments, the plurality of fragments of specific media content may exhibit a consistent packet length as a function of time.
Fragmented files 400 and 410 graphically illustrate certain aspects of various embodiments and, for clarity reasons, omit certain elements of files or segments of files, such as for example, headers and metadata. Further, although
As shown in
Before discussing further examples of different embodiments, certain advantages that may be realized from the using content descriptors to provide different sized fragments will be briefly discussed. As discussed previously, packetized video delivery systems generally require a predefined quantity of fragments to be cached before initiating playback of media though user devices, such as the user devices shown in
The fragmentation may be performed during the transcoding or conversion of the media content. In certain embodiments, the format and/or transcoding techniques may be conducted, based in part, on an appropriate content format for delivery to one or more user devices for consumption at a user's location such as a home, office or vehicle or a remote location. Converting the content may include encoding the content according to a content format such as MPEG-4, FLASH and the like and adapting the content to a predefined bit rate and/or resolution. The content delivery system may further process the content for delivery according to one or more transport protocols such as MPEG Transport Streams (TS), IP datastreams, mobile content delivery protocols and the like. The content may be processed according to multiple different transport protocols to account for different types of networks and devices (e.g., set-top boxes may receive MPEG TS transmissions while IP-enabled devices may be configured to receive IP datastreams).
As mentioned above, multiple fields or forms of metadata may be utilized in the assignment of the content descriptor. The following examples are explained in context with Descriptor #2 shown in column 332 of
Rule 1: If LIVE=YES and Genre=Sports, then Descriptor=1 second intervals.
Other rules, however, may utilize the sub-genre in combination with the Genre. For example, users who watch live football games may wish to watch the game as close to real time as possible, while those who watch rounds of golf may want to be a bit closer to real time but don't want to overly sacrifice possible consistencies in the broadcast, therefore, Rule 2 may be utilized:
Rule 2: If LIVE=YES and Genre=Sports, then look to Sports Sub-Genre. If Sub-Genre=Football, then Descriptor=1 second intervals. If Sub-Genre=Golf, then Descriptor=2.
This is shown in Column 332. Further, as shown in relation to media content 316-324, the content does not have to include live media for the fragment length to be adjusted. For example, both TV Programs #1 and #2 are reality TV programs (see, Column 306), however, content 314 comprises live content, whereas content 316 does not. Nonetheless, the sub-genre for media 316 indicates its “Interactive” and therefore, providing users the media a few seconds before traditional reception methods may have a more enjoyable experience.
Individuals receiving media content comprising movies (such as media content 320-324) generally are less adamant that their movie starts immediately and more concerned about the overall viewing experience when compared other media content, such as a sporting event or sitcom. Therefore, certain embodiments may utilize metadata providing such information in determining the fragment size.
Certain types of movies, such as for example, action movies (see, e.g., row 322), may be fragmented to have a longer fragment duration than other types of movies (see, e.g., rows 320 and 324). In this regard, this disclosure should not be limited to only decreasing the fragment size, but in certain embodiments, aspects of this disclosure may be utilized to increase fragment size for media content based on content descriptors. In the case of movies for example, expanding the fragment size from 2-3 second intervals to 5-8 second intervals may result in less network traffic as well as a better viewing experience for the user. Those skilled in the art will appreciate that media content fragments often include headers and other data packets in addition to the media that will be provided as audio and/or video. Thus, in certain implementations, using larger fragments decreases the overall quantity of bandwidth required to transmit the same movie or other media using a larger quantity of smaller fragments.
Further, certain protocols utilize different compression techniques. For example, video information of multimedia content is often compressed into a variety of “frames.” Some frames allow for greater compression, thus allowing for decreased bandwidth requirements. Other frames are not as compressible, however, offer certain advantages. For example, “i-frames” are less compressible than “p-frames”, however, i-frames don't require other frames for decoding purposes. Therefore, the user can randomly access points of the media at i-frame locations. P-frames (as well as B-frames) require other frames for decoding, but use less bandwidth to transmit. Certain aspects of this disclosure, relate to the placement of frames within fragments. This may be especially useful to conserve valuable bandwidth while ensuring an enjoyable experience for the user of the media content.
In one embodiment, users of the media content comprising the football game of Sporting Event #1 may wish to rewind a portion of the media content to see an instant replay. Having additional i-frames in the fragments may assist in permitting users to locate the exact position of a key play and be able to readily navigate to that locate. Therefore, using the content descriptor and/or other metadata to determine the frequency of i-frames may be beneficial. Other media for example, such as a teleconference, may not require nearly as many i-frames for user satisfaction, therefore, less frequent usage of i-frames results in more compression and reduced use of bandwidth. In certain embodiments, each fragment may be formed to have a single i-frame as the initial frame. Therefore, if the content descriptor for live events dictates that 1-second intervals are created, then there may be 1 i-frame per interval. Yet other embodiments may utilize multiple i-frames per fragment.
At block 210, multiple versions of specific media content (i.e., Sports Event #1 shown in row 310 of
Block 212 or similar method may be implemented to transmit the fragmented media content (i.e., fragmented files 300 and 310 shown in
In this regard, fragmentation of one or more files may be performed during the delivery or availability of the media. This would be especially advantageous, for example, when delivering live content, such as for example, sporting events. The content may be delivered to one or more requesting users through associated user devices. In other examples, the content may be delivered to all user devices known to a content delivery system, such through a multicast distribution system, or to user certain devices selected by the content delivery system based on parameters specified by the content source and/or a provider operating the content delivery system.
Prior to, concurrently with and/or after delivery of the content to user devices (such as those shown in
Further aspects of this disclosure relate to dynamically adjusting one or more buffers. In one embodiment, the dynamic adjustment may be performed based upon one or more descriptor values, such as for example, a content descriptor value. In certain embodiments, a content descriptor value may be automatically obtained from existing metadata associated with content. In one embodiment, a specific field or value utilized in an EPG may be utilized as the content descriptor. In one embodiment, central server 150 and/or server 152 may comprise information utilized for an EPG that contains at least a portion of the metadata utilized in the selection or creation of a content descriptor value. For example, programming guide database 154 may contain or otherwise receive or have access to metadata regarding the media content received at block 202. In yet other embodiments, at least a portion of metadata may be contained within a segmentation descriptor, such as for example a SCTE-35 segmentation descriptor that marks program boundaries. In another embodiment, a descriptor assignment module, such as module 104d of server 104 (within central server 150) may be utilized in one or more processes relating to assigning a content descriptor with the media content, including any processes in relation to block 206.
In certain embodiments, a communication pathway between a content source (i.e., non-transitory medium(s) comprising media content) and a destination of the content may have one or more buffers that may be dynamically adjusted. Dynamic adjustment one or more buffers may be performed in addition to and/or instead of fragmenting content according to descriptor values, such as described throughout this disclosure (see, e.g., optional block 214). In further embodiments, fragment length may be utilized in any determinations relating to adjusting one or more buffers. For example, as discussed above, block 208 may be utilized to create fragments of content. Thus, certain embodiment, may utilize the fragment lengths of the fragments created in block 208 in any determinations. Those skilled in the art, therefore, will understand that optional block 214 may be initiated before, during and/or after blocks 206 and/208 and that the illustrative embodiment is merely one example.
Regardless whether a content descriptor value, such as that obtained or derived from an EPG, fragment size, a combination thereof, or other inputs are utilized, exemplary adjustment may include but are not limited to: whether to adjust a buffer, which buffer(s) to adjust, an amount of adjustment, duration of an adjustment, and combinations thereof. In one embodiment, a device at user location 100, such as gateway 101 and/or an electronic device (e.g. computer 109) may have a default buffer value. Default buffers may be useful to deal with network latency/jitter. However, under certain embodiments, one or more default values may be adjusted for the reception of certain content. For example, upon requesting or receiving content, a content descriptor, fragment size, and/other variables may indicate that the content includes live content, for example a sporting event that is currently taking place. Therefore, in one embodiment, based upon the content descriptor value, the buffer on one at least one device, such as gateway 101 and/or computer 109, may be set to a lower value. For example, a default buffer value may be set to 20 seconds and may be adjusted to 2 seconds in accordance with one embodiment.
Although example embodiments are described above, the various features and steps may be combined, divided, omitted, and/or augmented in any desired manner, depending on the specific secure process desired. This patent should not be limited to the example embodiments described, but rather should have its scope determined by the claims that follow. For example, although the above-referenced examples provide illustrative examples in the content of media files and fragments, those skilled in the art with the benefit of this disclosure will realize that the teachings of this application is not limited to media. Rather, this disclosure encompasses implementation of the novel methods and systems disclosed herein for the transmission, reception, and utilization of any form of data.
This patent is a continuation of U.S. patent application Ser. No. 15/590,910, filed May 9, 2017, which is a continuation of U.S. patent application Ser. No. 13/767,524, filed Feb. 14, 2013 (now U.S. Pat. No. 9,680,689), each of which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
6502139 | Birk et al. | Dec 2002 | B1 |
6724933 | Lin et al. | Apr 2004 | B1 |
7725506 | Stringham | May 2010 | B1 |
8532171 | Narayanan et al. | Sep 2013 | B1 |
8572055 | Wu | Oct 2013 | B1 |
8949206 | Dhanapal | Feb 2015 | B2 |
9209934 | Luby et al. | Dec 2015 | B2 |
9264471 | Pichumani et al. | Feb 2016 | B2 |
9596522 | Odlund et al. | Mar 2017 | B2 |
20020107968 | Horn et al. | Aug 2002 | A1 |
20020136217 | Christensen | Sep 2002 | A1 |
20030069881 | Huttunen | Apr 2003 | A1 |
20030110286 | Antal et al. | Jun 2003 | A1 |
20030110501 | Rafey et al. | Jun 2003 | A1 |
20030123545 | Prakash et al. | Jul 2003 | A1 |
20030204670 | Holt et al. | Oct 2003 | A1 |
20030236904 | Walpole et al. | Dec 2003 | A1 |
20040161154 | Hua et al. | Aug 2004 | A1 |
20040202191 | Vrabel | Oct 2004 | A1 |
20040243643 | Hattrup et al. | Dec 2004 | A1 |
20050076136 | Cho et al. | Apr 2005 | A1 |
20050144305 | Fegan, II | Jun 2005 | A1 |
20060090036 | Zohar et al. | Apr 2006 | A1 |
20060143650 | Tanikawa et al. | Jun 2006 | A1 |
20070030391 | Kim et al. | Feb 2007 | A1 |
20070157226 | Misra | Jul 2007 | A1 |
20070239881 | Schneider et al. | Oct 2007 | A1 |
20070260637 | Shenfield | Nov 2007 | A1 |
20070299870 | Finch | Dec 2007 | A1 |
20080155087 | Blouin et al. | Jun 2008 | A1 |
20080184245 | St-Jean | Jul 2008 | A1 |
20090328103 | Morris | Dec 2009 | A1 |
20100020686 | Lee et al. | Jan 2010 | A1 |
20100161580 | Chipman et al. | Jun 2010 | A1 |
20100169303 | Biderman et al. | Jul 2010 | A1 |
20100205049 | Long et al. | Aug 2010 | A1 |
20100242079 | Riedl | Sep 2010 | A1 |
20100257146 | Memon | Oct 2010 | A1 |
20110058555 | Hashimoto | Mar 2011 | A1 |
20110103245 | Lu | May 2011 | A1 |
20110239078 | Luby et al. | Sep 2011 | A1 |
20120033612 | Jazra | Feb 2012 | A1 |
20120042091 | McCarthy et al. | Feb 2012 | A1 |
20120099672 | Wan et al. | Apr 2012 | A1 |
20120110138 | Zhang | May 2012 | A1 |
20120166868 | Volvovski et al. | Jun 2012 | A1 |
20120198089 | Dhruv et al. | Aug 2012 | A1 |
20120198335 | Huang | Aug 2012 | A1 |
20120233345 | Hannuksela | Sep 2012 | A1 |
20130054728 | Amir | Feb 2013 | A1 |
20130064283 | Sun et al. | Mar 2013 | A1 |
20130091251 | Walker et al. | Apr 2013 | A1 |
20130104024 | Rajkumar et al. | Apr 2013 | A1 |
20130124749 | Thang et al. | May 2013 | A1 |
20130132507 | Swaminathan et al. | May 2013 | A1 |
20130132836 | Ortiz | May 2013 | A1 |
20130159546 | Thang et al. | Jun 2013 | A1 |
20130166772 | Tapio Kekki | Jun 2013 | A1 |
20130185398 | Thang et al. | Jul 2013 | A1 |
20130223509 | Tweedale et al. | Aug 2013 | A1 |
20130232233 | Reza | Sep 2013 | A1 |
20130239145 | Broome et al. | Sep 2013 | A1 |
20130262693 | Phillips et al. | Oct 2013 | A1 |
20130346867 | Woods et al. | Dec 2013 | A1 |
20140025830 | Grinshpun et al. | Jan 2014 | A1 |
20140025835 | Gahm | Jan 2014 | A1 |
20140040970 | Alexander et al. | Feb 2014 | A1 |
20140059377 | Zhang et al. | Feb 2014 | A1 |
20140074961 | Liu et al. | Mar 2014 | A1 |
20140286316 | Park et al. | Sep 2014 | A1 |
20140310008 | Kang et al. | Oct 2014 | A1 |
20170191840 | Kuhne et al. | Jul 2017 | A1 |
Entry |
---|
Thorsten Lohmar et al: “Dynamic adaptive HTTP streaming of live content”, World of Wireless, Mobile and Multimedia Networks (WOWMOM), 2011 IEEE International Symposium on A, IEEE, Jun. 20, 2011 (Jun. 20, 2011), pp. 1-8. |
Stefan Lederer et al: “Dynamic adaptive streaming over HTTP dataset”, Proceeding MMSYS '12 Proceedings of the 3rd Multimedia Systems Conference, Jan. 1, 2012 (Jan. 1, 2012), p. 89. |
“Adaptive Streaming Ad Insertion—Modifying Playlists to Deliver Targeted Ads Using HTTP Adaptive Streaming”, RGB Networks, 2011, XP002722836, Retrieved from the Internet: URL:http://www.rgbnetworks.com/pdfs/Adaptive_Bitrate_Ad_Insertion_White_Paper_0911-0I.pdf [retrieved on Apr. 4, 2014]. |
Extended European Search Report—EP14155032.7—dated Apr. 22, 2014. |
European Office Action—EP Application 14155032.7—dated Sep. 28, 2015. |
Nov. 2, 2017—EP Decision to Refuse—EP 14155032.7. |
Feb. 18, 2020—Canadian Office Action—CA 2,842,810. |
Dec. 23, 2020—Canadian Office Action—CA 2,842,810. |
Aug. 3, 2022—CA Office Action—CA App. No. 2,842,810. |
Number | Date | Country | |
---|---|---|---|
20220070047 A1 | Mar 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15590910 | May 2017 | US |
Child | 17396363 | US | |
Parent | 13767524 | Feb 2013 | US |
Child | 15590910 | US |