Patent Grant
11997413
Examples of the disclosure relate generally to systems and methods for presenting media content to a user of a computing device, and more specifically, to systems and methods for presenting media content including video to a user of a mobile computing device.
With the growth of video-capable mobile devices, such as smartphones, tablets, and wearable devices, users' media viewing habits have gradually shifted out of the living room, and into the outside world—into every corner and crevice where these devices can be used. Similarly, this shift has displaced the traditional television set—a bulky screen designed to be mounted semi-permanently in a single place, such as on a wall or on a flat surface—in favor of small, portable screens that can be viewed in virtually any position, and in virtually any orientation.
Such mobile devices place new demands on video content. One such demand relates to the aspect ratio (e.g., the ratio of a display width to a display height) of the video content. Under desired viewing conditions, a native aspect ratio of a video asset (e.g., a source file containing video content) matches the aspect ratio of the display on which the video asset is presented. For example, when viewing a video asset on a display having a 16:9 aspect ratio, it is desirable that the video asset itself have a 16:9 aspect ratio. If the video asset has an aspect ratio that differs from the aspect ratio of the display, one of two conventional solutions can be used to format the video asset for the display: either the video asset can be cropped to fit the display (e.g., via “pan and scan” techniques); or the video asset can be “letterboxed” by adding dummy content (e.g., black bars) to fill the regions of the display unoccupied by the video asset. Neither solution is desirable: cropping the video asset results in the cropped content being unviewable on the display (which can affect the viewer's understanding or appreciation of the video asset); and letterboxing the video asset results in regions of the display being effectively unused (which can impair visibility, especially on mobile devices with limited display space).
A preferred solution is to anticipate the aspect ratio of the display on which video content will be viewed, and to provide to the display a video asset that matches that aspect ratio. But this approach is frustrated by mobile device displays that change aspect ratios as the user changes the orientation of the device. For instance, a display may be in a “portrait” mode (e.g., in which the aspect ratio is less than unity) when a device is held upright, but may shift to a “landscape” mode (e.g., in which the aspect ratio is greater than unity) when the device is rotated 90 degrees to the left or the right. A solution is needed for seamlessly switching between aspect ratios of video content without resorting to cropping or letterboxing techniques.
Further, users of mobile devices demand that video content be data-efficient: that is, that the video content respect the limited data storage capacity of many mobile devices, and the cost and overhead of downloading large files on consumer data plans; and that it accommodate the high latency, low bandwidth network conditions in which mobile devices may operate. The present disclosure describes such one or more solutions, which improve on conventional approaches by providing a data-efficient mechanism for quickly and seamlessly changing an aspect ratio of video content on a mobile device display.
Examples of the disclosure describe systems and methods of presenting media content. According to examples of the disclosure, a plurality of assets is received at a device comprising a display and an orientation sensor. The plurality of assets comprises a first video asset associated with a first aspect ratio, and a second video asset associated with a second aspect ratio, different from the first aspect ratio. A desired aspect ratio is determined based on an output of the orientation sensor.
In accordance with a determination that the desired aspect ratio is closer to the first aspect ratio than to the second aspect ratio, the first video asset is selected. In accordance with a determination that the desired aspect ratio is closer to the second aspect ratio than to the first aspect ratio, the second video asset is selected. The selected video is presented at the desired aspect ratio via the display.
In the following description of examples, reference is made to the accompanying drawings which form a part hereof, and in which it is shown by way of illustration specific examples that can be practiced. It is to be understood that other examples can be used and structural changes can be made without departing from the scope of the disclosed examples.
Displays, such as those that can be included in the example devices described above with respect to
In
In some examples, such as shown in
The first and second video assets 502 and 512 can be provided by a creative entity with creative control over the video assets. The creative entity can author (e.g., produce and edit) the first video asset 502 such that it is creatively suited for presentation in the first orientation (e.g., landscape orientation); for example, the creative entity can select camera shots, control scene placement, and position graphical elements such that the video content is understandable and engaging in a landscape orientation. The creative entity can similarly author the second video asset 512 such that it is creatively suited for presentation in the second orientation (e.g., portrait orientation). Viewability differences between the first orientation and the second orientation may result in significantly different creative demands of the first video asset 502 and the second video asset 512. For example, a full-body camera shot of a standing actor may be well suited for a portrait orientation, because the proportions of an actor standing upright may resemble the proportions of a portrait display. But the same full-body shot may be inappropriate for a landscape display, whose proportions vary significantly from those of the actor. Conversely, a wide-angle camera shot of a basketball court may present well on a landscape display, but may be entirely unsuited for a portrait display. Such differences may be especially pronounced on mobile devices, which may have small screens that make it difficult for a viewer to resolve small visual details (such as facial features). Accordingly, the creative entity may elect to produce a first video asset 502 that differs (even significantly) from the second video asset 512, even though the two video assets may relate to the same general content. For example, the first and second video assets may comprise entire separate camera shots and sequences, transitions, focal points, post-processing effects, overlays, or other video elements, as appropriate. Providing separate first and second video assets, where those assets may differ creatively, offers an advantage over processes in which a single video asset is manipulated (e.g., via cropping or letterboxing) for presentation at multiple different aspect ratios. The creative entity can make human authorship decisions based on what the entity decides would look best when presented at a particular aspect ratio.
With respect to
In some examples, audio assets 504 and 514 may be identical assets, such as where identical audio tracks are to be presented regardless of whether a device is in a portrait orientation or a landscape orientation. In other examples, audio assets 504 and 514 may have different audio characteristics, such as a where it is desirable to present different audio tracks based on whether the device is in a portrait orientation or a landscape orientation. For instance, during a scene of a video, first video asset 502 (e.g., in landscape orientation) may feature a distant camera shot on an actor's face, while a corresponding scene in second video asset 512 (e.g., in portrait orientation) may feature a close-up camera shot on the same actor's face. It may be desirable for the actor's dialogue to be louder in the second audio asset 514 than in the first audio asset 504, to correspond with the close-up shot in portrait orientation; and for consistency with the user's expectation that sounds originating closer to the camera will be relatively louder in an audio mix than those originating farther from the camera. As with the first and second video assets described above, a creative entity can exercise creative control over the first audio asset and the second audio asset, such that the audio assets reflect human judgment of what will sound best to the listener.
With respect to
Encoder 530 can accept as input any suitable number of type of assets. In the example process 500 shown in
Encoder 530 can encode its input assets according to one or more suitable processes, which may be selected depending on criteria such as network conditions (e.g., latency, available bandwidth), content type, user preferences, or display type (including display aspect ratios), such as described below. Depending on which encoding processes are used, encoder 530 can output one or more streams 540 of encoded data. For example, data streams 540 can include a first encoded data stream 542, a second encoded data stream 544, and a third encoded data stream 546 (and potentially other data streams). A data stream may correspond to any suitable combination of video data, audio data, or data associated with any other suitable type of asset (e.g., haptic data). Further, the disclosure is not limited to any particular correlation of data streams to assets (such as assets 502, 504, 512, 514, and 520 described above); a data stream can include data for any suitable number or type of assets.
Data streams 540 can be delivered to device 550, which may correspond to the example devices in
In presenting the assets, media player application 560 can select between two or more presentations of video content, such as described above with respect to
In the example shown in
In the examples shown in
Data efficiencies can be realized by encoding multiple assets in a single data stream, such as data stream 622 shown in
In the example data stream shown in
In the example data stream shown in
In the example data stream shown in
In the example data stream 740 shown in
In the example data stream shown in
In the examples shown in
In some examples, a first video asset may be oriented at a same angle as a second video asset. This may be necessary when, for example, technical requirements demand that a video asset be encoded with a particular orientation. For instance, a video playback application may require that a video asset be oriented at a particular angle in order to present that video asset to a viewer. In some cases, DRM or other content protection mechanisms may require encoding of a video asset in a particular orientation.
Certain encoding schemes, such as described above, may be more desirable than others depending on variables such as network conditions; user habits; or the type of content to be presented. In some examples, machine learning techniques (e.g., neural network techniques) or probabilistic models can be used to identify and predict which encoding scheme is preferable in a particular circumstance.
In some examples described and shown above, video assets are encoded adjacent to one another, e.g., in a data stream. In some examples, adjacent video assets may share a common pixel boundary. However, it is within the scope of this disclosure that adjacent video assets may be separated by an insubstantial region of space. For example, it is contemplated that adjacent video assets may be separated by a row or column of 1 or 2 pixels.
While the above examples are described with respect to video assets, it will be understood that aspects of the disclosure can be applied to audio-only assets (e.g., music, podcasts) that may not have a video component. Further, the disclosure can be applied to assets comprising still images, GIF files, or other suitable types of media.
As described above, a user of a display device may switch between a first video asset, e.g., a video in a portrait orientation, and a second video asset, e.g., a video in a landscape orientation, by rotating the display device. In some examples a data stream may include both a first video asset and a second video asset, such as described above. Playback of a video asset can comprise a user interface with a “scrubber” element for graphically representing temporal locations of the video asset (e.g., via a position of a playback head). For example, a scrubber element can depict a video asset as a line, with a first time (e.g., the beginning) of the video asset at one end of the line, and a second time (e.g., the end) of the video asset at the other end of the line. During video playback or editing, a user can change the frame of a video, or a time corresponding to a playback position by dragging a slider or playhead across a scrubber bar or timeline. (The timeline may, but need not, be represented as a straight line.) On touch-sensitive devices, a user can manipulate the scrubber using touch controls; for example, dragging a playhead along a timeline with one's finger on a touch screen can move the playback position accordingly. On non-touch-sensitive devices, the user can manipulate the scrubber using a mouse, a remote control, a gamepad, or another suitable input device.
The usability of a scrubber can depend on various factors. For example, it is desirable that a scrubber be easily accessible (e.g., via one's dominant thumb while holding a touch screen device with the dominant hand). It is further desirable that the scrubber not overlap or obscure important information on a display screen. However, it is also desirable that the scrubber be sufficiently large to allow for fine and coarse inputs; a scrubber that is too small may frustrate a user's ability to make fine adjustments to the playhead, particular when viewing lengthy video assets. When a scrubber is used to manipulate one or multiple video assets—for example, either a portrait orientation video asset or a landscape orientation video asset, such as in the examples described above—a one-size-fits-all scrubber design may be unsuitable. For instance, a scrubber that is sufficiently large, easily accessible to the user, and does not overlap important video content when viewing a portrait orientation video may suddenly become unsuitable when the user switches to a landscape orientation video; for example, the landscape orientation video may place important information in a different location on the display, and if the user holds a mobile device in a landscape orientation, the scrubber may no longer be within easy reach of the user.
It can be desirable that a scrubber tool comprise an adaptive scrubber; that is, a scrubber whose appearance or functionality may adapt to the video asset being played, and/or to the orientation of the display device. This can be particularly desirable when a user (e.g., of a mobile display device) wishes to switch between two video modes or video assets (e.g., portrait and landscape), such as described above, and control them with a common scrubber tool. In embodiments described herein, an adaptive scrubber may adopt one or more first characteristics (e.g., appearance, display location, dimensions, functionality) when viewing a first video asset or a first video mode, and may adopt one or more second characteristics when viewing a second video asset or a second video mode. For example, a video asset corresponding to a portrait orientation may be associated with an playback interface or an adaptive scrubber having a vertically oriented layout, while a video asset corresponding to a landscape orientation may be associated with a playback interface or an adaptive scrubber having a horizontally oriented layout. In this manner, the adaptive scrubber can adopt an appearance or functionality suited to the video at hand. This may enhance ease of use of the scrubber and enhance the overall viewing experience for the user. In some examples, other aspects of video playback may adapt to the video asset being played; one example is adaptive closed captioning, where the location and/or the content of the closed captioning may differ between a first video asset and a second video asset.
The adaptive scrubber may also include playback controls 912. The playback controls 912 may include a fast-forward, a rewind, and a play/pause icon. Selecting an icon can have a corresponding effect on the video as well as the position of the slider 904 on the scrubber bar 902. For example, selecting (e.g., clicking or tapping) the play/pause icon on the playback controls 912 may cause a playing video to pause. The slider 904 can remain in place along the scrubber bar 902 at the time the selection was made, i.e., playback of the currently displayed video asset will stop. If the play command is selected, the presented video asset will resume playing at a real time speed. Selecting the fast-forward icon on the playback controls 912 may cause the video to fast-forward, i.e., advance the current video asset at a rate quicker than real-time. The slider 904 can similarly advance along the scrubber bar 902 at a rate quicker than real-time corresponding to the video. In some embodiments, there may be more than one fast-forward speed. For example, selecting the fast-forward icon once may result in a fast-forward rate corresponding to 1.5× the speed of the original video. Selecting the fast-forward icon a second time may result in a fast-forward rate of 2.0× the speed of the original video. Selecting the fast-forward icon a third time may result in a fast-forward rate of 3.0× the speed of the original video. The rewind icon of the playback controls 912 may be used to rewind the video, i.e., present frames of the selected video asset in a reverse order starting from the current frame. The rewind icon may have multiple speeds as described with respect to the fast-forward icon.
The user interface elements associated with the adaptive scrubber may be positioned based on the video asset currently being played by the device, e.g., may depend on the orientation of the device. In
Referring to both
Referring to
With respect to
According to some examples, a handheld device may detect a location of a hand of the user grasping the device to automatically determine which side of the screen to position the scrubber bar. In
In
In some examples, locations of the adaptive scrubber user interface elements, e.g., scrubber bar, slider, and playback controls may depend on the content of the video asset being played. For example, the adaptive scrubber user interface elements may be presented in areas of the display that do not correspond to, or overlap with, a focal region of the video asset. A focal region may be a region of interest, such as an area of the screen that a creative entity would expect a user's gaze to be directed. For example, the focal region for a video may correspond to an area where a person is delivering dialogue. Referring back to
Rotating the device 1100 from a portrait orientation in
The chapters may indicate different sections of the video asset. According to one example, if the video is a news show, the chapters may correspond to different news segments. According to another example, if the video is a movie, the chapters may correspond to shorter narrative arcs within the movie and/or suggest a recommended location for a viewer to pause while watching the video. In some examples a creative entity and/or distributor of the content may determine the placement of the chapters. In some examples, a user may create their own chapters, as described below with respect to bookmarking and
In some examples, a first video asset, e.g., having a portrait orientation, may be different a second video asset, e.g., having a landscape orientation, as described above, e.g.,
A user that desires to share a link to the video asset on playing on a device 1200 may select one of the social media icons 1216. Referring to
The content of the pop-up can be tailored to the social media icon selected. For example, if a user selects the Facebook icon, the user may be given the option to post on their personal wall, a friend's wall, or send the link over Facebook Messenger. In some examples, the link sent through the social media capabilities may require the intended recipient to watch the same video asset that the user was watching before sending the link. For instance, if the user is watching a first video asset in portrait orientation and sends a link, the intended recipient can receive a link to the same video asset, e.g., to watch the video in portrait orientation. In this manner, the user can ensure that the intended recipient will have a similar experience with the video content by watching the video in the same orientation. In other examples, the intended recipient may have an option to watch the same or a different video asset. For example, an intended recipient may receive a link to both video assets and depending on the detected orientation of the device, the appropriate video asset will play, e.g., if the device is in a portrait orientation, the video asset corresponding to the portrait orientation will play. In this example, a user may rotate the device during playback and the video asset should switch accordingly, e.g., from a first video asset in portrait orientation to a second video asset in landscape orientation. In some examples where an intended recipient can choose to watch the first or second video asset, the message accompanying the link may suggest a preferred orientation.
A user that desires to bookmark a start of a video segment along the scrubber bar 1302 may select the bookmarking icon 1348. Referring to
Referring to
In some examples, the bookmark icon 1346 may be rectangular, oval, circular, triangular, or any shape that a user may easily recognize without confusing the bookmark icon 1346 for a chapter head or the slider 1304. In some examples, the bookmark icon may be the same shape as the chapter head or slider, but be a different color. In some examples, the bookmarks may have a similar function as chapters and use the same icon as a chapter head. In some examples, a user may have an option to designate a selected time location as a bookmark or a chapter. In some examples, there may be a bookmarking icon as well as a separate chapter icon. In such examples, the chapter icon may work as described above with respect to the bookmarking icon. One skilled in the art would understand that a user may save multiple bookmarks for a video asset.
According to some examples, the adaptive scrubber may include a movable scrubber bar.
While the user can move the location of touch in both a horizontal and vertical direction, the movement of the scrubber bar will track the horizontal position of the location of touch. In other words, according to this example, moving the scrubber bar will not change its vertical position.
In some examples, the scrubber bar 1402 may stay put once the scrubber bar has been dragged to a new location. For example, referring to
In some examples, the scrubber bar 1402 may snap to a location depending on the final location of touch (e.g., the location of touch preceding the user removing a finger or stylus from the screen). For example, still referring to
According to some examples the second location of touch may be located to the left of the centerline of the device. For example, in
In some examples, the media content application may prompt a user to select a preferred amount of mobility for the scrubber bar, e.g., no movement, free movement, snap to location, rubber band effect. In some examples, a user may be able to configure the mobility of the scrubber bar in the settings of the video application.
The examples described above may operate on one or more computers (e.g., one or more servers), including non-transitory computer readable recording media on a computer. This readable media contains the program instructions for accomplishing various steps described above. In the context of this disclosure, a computer-readable recording medium can be any medium that can contain or store programming for use by or in connection with an instruction execution system, apparatus, or device. Such computer readable media may be stored on a memory, where a memory is any device capable of storing a computer readable medium and capable of being accessed by a computer. A memory may include additional features. As used herein, a computer can comprise a conventional computer or one or more mobile devices. A computer may include a processor. A processor can be any device suitable to access a memory and execute a program stored thereon.
Communications may be transmitted between nodes over a communications network, such as the Internet. Other communications technology may include, but is not limited to, any combination of wired or wireless digital or analog communications channels, such as instant messaging (IM), short message service (SMS), multimedia messaging service (MMS) or a phone system (e.g., cellular, landline, or IP-based). These communications technologies can include Wi-Fi, Bluetooth, or other wireless radio technologies.
Examples of the disclosure may be implemented in any suitable form, including hardware, software, firmware, or any combination of these. Examples of the disclosure may optionally be implemented partly as computer software running on one or more data processors and/or digital signal processors. The elements and components of an example of the disclosure may be physically, functionally, and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in multiple units, or as part of other functional units. As such, examples of the disclosure may be implemented in a single unit or may be physically and functionally distributed between different units and processors.
Memory 802 may include volatile and non-volatile storage. For example, memory storage may include read only memory (ROM) in a hard disk device (HDD), random access memory (RAM), flash memory, and the like. The Operating System (OS) and application programs may be stored in ROM.
Specific software modules that implement embodiments of the described systems and methods may be incorporated in application programs on a server. The software may execute under control of an OS.
Processor 804 may include any device suitable to access a memory and execute a program stored thereon.
Input interface 806 may include a keyboard or mouse, for example. Output interface 808 may include a conventional color monitor and printer, such as a conventional laser printer. Output interface 808 may provide requisite circuitry to electrically connect and interface the display and printer to the computer system.
Communications interface 810 may allow the network and nodes to connect directly, or over another network, to other nodes or networks. The network can include, for example, a local area network (LAN), a wide area network (WAN), or the Internet. In some examples, the network, modules, and nodes can be connected to another client, server, or device via a wireless interface.
In some examples, the input interface, processor, memory, communications interface, output interface, or combinations thereof, are interconnected by a bus.
The disclosed examples could be embodied as a JAVA tool, which means it can run on any platform that is JAVA enabled. Examples can run on a web server that provides a website for administrators to monitor the system results remotely. Anyone with administrative access to the web server can connect to and use visualization tools to take actions within a visualization. The examples can run on any type of server, including virtual servers or an actual machine. While JAVA is provided as an example, any suitable programming language or technology can be used to implement the examples of the disclosure.
The disclosed examples may be embodied on a distributed processing system to break processing apart into smaller jobs that can be executed by different processors in parallel. The results of the parallel processing could then be combined once completed.
Although the present invention has been fully described in connection with examples thereof with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the claimed subject matter. The various examples of the invention should be understood that they have been presented by way of example only, and not by way of limitation. Although the invention is described above in terms of various examples and implementations, it should be understood that the various features and functionality described in one or more of the individual examples are not limited in their applicability to the particular example with which they are described. They instead can, be applied, alone or in some combination, to one or more of the other examples of the invention, whether or not such examples are described, and whether or not such features are presented as being a part of a described example. Thus the breadth and scope of the claimed subject matter should not be limited by any of the above-described examples.
Terms and phrases used in this document, and variations thereof, unless otherwise expressly stated, should be construed as open ended as opposed to limiting. As examples of the foregoing, the term “including” should be read as meaning “including, without limitation” or the like; the term “example” is used to provide exemplary instances of the item in discussion, not an exhaustive or limiting list thereof; and adjectives such as “conventional,” “traditional,” “normal,” “standard,” “known,” and terms of similar meaning, should not be construed as limiting the item described to a given time period, or to an item available as of a given time. These terms should instead be read to encompass conventional, traditional, normal, or standard technologies that may be available, known now, or at any time in the future. Likewise, a group of items linked with the conjunction “and” should not be read as requiring that each and every one of those items be present in the grouping, but rather should be read as “and/or” unless expressly stated otherwise. Similarly, a group of items linked with the conjunction “or” should not be read as requiring mutual exclusivity among that group, but rather should also be read as “and/or” unless expressly stated otherwise. Furthermore, although items, elements or components of the invention may be described or claimed in the singular, the plural is contemplated to be within the scope thereof unless limitation to the singular is explicitly stated. For example, “at least one” may refer to a single or plural and is not limited to either. The presence of broadening words and phrases such as “one or more,” “at least,” “but not limited to,” or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent. The word “exemplary” is used herein to mean “serving as an example or illustration.” Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs.
It will be appreciated that, for clarity purposes, the above description has described examples of the invention with reference to different functional units and modules. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the invention. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization. It should be understood that the specific order or hierarchy of steps in the processes disclosed herein is an example of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the claimed subject matter. Further, in some examples, some steps in the processes disclosed herein may be forgone altogether while remaining within the scope of the claimed subject matter.
This application is a continuation of U.S. patent application Ser. No. 16/735,511, filed Jan. 6, 2020 which is a continuation-in-part of U.S. patent application Ser. No. 16/405,648, filed May 7, 2019, which claims priority to U.S. Provisional Application Serial No. 62/816,884, filed Mar. 11, 2019, both of which applications are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4305131 | Best | Dec 1981 | A |
| 5045844 | Takano et al. | Sep 1991 | A |
| 5396590 | Kreegar | Mar 1995 | A |
| 5400077 | Cookson | Mar 1995 | A |
| 5465384 | Bejan et al. | Nov 1995 | A |
| 5559999 | Maturi et al. | Sep 1996 | A |
| 5600368 | Matthews, III | Feb 1997 | A |
| 5640388 | Woodhead et al. | Jun 1997 | A |
| 5727129 | Barrett et al. | Mar 1998 | A |
| 5751953 | Shiels et al. | May 1998 | A |
| 5894320 | Vancelette | Apr 1999 | A |
| 6128712 | Hunt et al. | Oct 2000 | A |
| 6137468 | Martinez et al. | Oct 2000 | A |
| 6144375 | Jain et al. | Nov 2000 | A |
| 6161115 | Ohanian | Dec 2000 | A |
| 6326978 | Robbins | Dec 2001 | B1 |
| 6505169 | Bhagavath et al. | Jan 2003 | B1 |
| 6615270 | Gould et al. | Sep 2003 | B2 |
| 6621980 | Gould et al. | Sep 2003 | B1 |
| 6738427 | Zetts | May 2004 | B2 |
| 6907570 | Amir et al. | Jun 2005 | B2 |
| 7487468 | Tanaka et al. | Feb 2009 | B2 |
| 7577963 | Ofarrell et al. | Aug 2009 | B2 |
| 7594025 | Colville et al. | Sep 2009 | B2 |
| 7642442 | Adam et al. | Jan 2010 | B2 |
| 7707273 | Jones | Apr 2010 | B2 |
| 7743183 | Virdi et al. | Jun 2010 | B2 |
| 7877690 | Margulis | Jan 2011 | B2 |
| 7889975 | Slone | Feb 2011 | B2 |
| 7890648 | Gould et al. | Feb 2011 | B2 |
| 7952569 | Hunt | May 2011 | B2 |
| 8001471 | Shaver et al. | Aug 2011 | B2 |
| 8015167 | Riggs et al. | Sep 2011 | B1 |
| 8112711 | Ackley | Feb 2012 | B2 |
| 8174628 | Matsushita | May 2012 | B2 |
| 8176425 | Wallace et al. | May 2012 | B2 |
| 8201202 | Ota | Jun 2012 | B2 |
| 8229287 | Duggal et al. | Jul 2012 | B1 |
| 8238419 | Chui et al. | Aug 2012 | B2 |
| 8265167 | Lynch et al. | Sep 2012 | B2 |
| 8301794 | Salomons | Oct 2012 | B2 |
| 8392600 | Outlaw | Mar 2013 | B2 |
| 8402492 | Amira et al. | Mar 2013 | B2 |
| 8458595 | Margulis | Jun 2013 | B1 |
| 8482635 | Peters et al. | Jul 2013 | B2 |
| 8484369 | Jones | Jul 2013 | B2 |
| 8489760 | Visharam et al. | Jul 2013 | B2 |
| 8510459 | Parker et al. | Aug 2013 | B2 |
| 8526782 | Kaiser et al. | Sep 2013 | B2 |
| 8549571 | Loher et al. | Oct 2013 | B2 |
| 8600220 | Bloch et al. | Dec 2013 | B2 |
| 8670072 | Liang | Mar 2014 | B1 |
| 8683350 | Lahr et al. | Mar 2014 | B2 |
| 8693553 | Vaquero et al. | Apr 2014 | B2 |
| 8750682 | Nicksay et al. | Jun 2014 | B1 |
| 8752100 | Ramakrishnan et al. | Jun 2014 | B2 |
| 8842971 | Pontual et al. | Sep 2014 | B2 |
| 8860882 | Bloch et al. | Oct 2014 | B2 |
| 8868772 | Major et al. | Oct 2014 | B2 |
| 8873928 | Lim et al. | Oct 2014 | B2 |
| 8886752 | Styles | Nov 2014 | B2 |
| 8898311 | Kikkawa et al. | Nov 2014 | B2 |
| 8953079 | Raju | Feb 2015 | B2 |
| 8954596 | Ronca et al. | Feb 2015 | B2 |
| 9009337 | Ronca | Apr 2015 | B2 |
| 9009619 | Bloch et al. | Apr 2015 | B2 |
| 9106627 | Campbell et al. | Aug 2015 | B2 |
| 9118814 | Janardhan et al. | Aug 2015 | B2 |
| 9143826 | Vestergaard et al. | Sep 2015 | B2 |
| 9153031 | El-saban | Oct 2015 | B2 |
| 9190110 | Bloch | Nov 2015 | B2 |
| 9215262 | Oyman | Dec 2015 | B2 |
| 9229230 | Scales et al. | Jan 2016 | B2 |
| 9253229 | Strothmann | Feb 2016 | B1 |
| 9257148 | Bloch et al. | Feb 2016 | B2 |
| 9271015 | Bloch et al. | Feb 2016 | B2 |
| 9294526 | George | Mar 2016 | B2 |
| 9330172 | Elsner et al. | May 2016 | B2 |
| 9357272 | Oyman | May 2016 | B2 |
| 9418012 | De Vleeschauwer et al. | Aug 2016 | B2 |
| 9430115 | Yun | Aug 2016 | B1 |
| 9432433 | Luby et al. | Aug 2016 | B2 |
| 9436767 | Gordon | Sep 2016 | B2 |
| 9449648 | Lagemann et al. | Sep 2016 | B2 |
| 9520155 | Bloch et al. | Dec 2016 | B2 |
| 9530454 | Bloch et al. | Dec 2016 | B2 |
| 9607655 | Bloch et al. | Mar 2017 | B2 |
| 9609275 | Kuusela | Mar 2017 | B2 |
| 9620172 | Knight et al. | Apr 2017 | B2 |
| 9641898 | Bloch et al. | May 2017 | B2 |
| 9653115 | Bloch et al. | May 2017 | B2 |
| 9672868 | Bloch et al. | Jun 2017 | B2 |
| 9792026 | Bloch et al. | Oct 2017 | B2 |
| 9792957 | Bloch et al. | Oct 2017 | B2 |
| 9817549 | Chandrasekaran | Nov 2017 | B2 |
| 9832516 | Bloch et al. | Nov 2017 | B2 |
| 9860477 | Kummer | Jan 2018 | B2 |
| 10069898 | Jones | Sep 2018 | B2 |
| 10108274 | Nicholls | Oct 2018 | B2 |
| 10178304 | Tudor | Jan 2019 | B1 |
| 10218760 | Vishnia et al. | Feb 2019 | B2 |
| 10237595 | Mccue et al. | Mar 2019 | B2 |
| 10257578 | Bloch et al. | Apr 2019 | B1 |
| 10418066 | Bloch et al. | Sep 2019 | B2 |
| 10448119 | Bloch et al. | Oct 2019 | B2 |
| 10460765 | Bloch et al. | Oct 2019 | B2 |
| 10462202 | Bloch et al. | Oct 2019 | B2 |
| 10474334 | Bloch et al. | Nov 2019 | B2 |
| 10523982 | Oyman | Dec 2019 | B2 |
| 10554926 | Post, Jr. | Feb 2020 | B1 |
| 10582265 | Bloch et al. | Mar 2020 | B2 |
| 10585546 | Basapur et al. | Mar 2020 | B2 |
| 10692540 | Bloch et al. | Jun 2020 | B2 |
| 10755747 | Bloch et al. | Aug 2020 | B2 |
| 10856049 | Bloch et al. | Dec 2020 | B2 |
| 10885944 | Bloch et al. | Jan 2021 | B2 |
| 20020133247 | Smith | Sep 2002 | A1 |
| 20020194595 | Miller et al. | Dec 2002 | A1 |
| 20030055995 | Ala-honkola | Mar 2003 | A1 |
| 20060064733 | Norton et al. | Mar 2006 | A1 |
| 20060153537 | Kaneko | Jul 2006 | A1 |
| 20070024705 | Richter | Feb 2007 | A1 |
| 20070085759 | Lee | Apr 2007 | A1 |
| 20070122786 | Relan et al. | May 2007 | A1 |
| 20070253677 | Wang | Nov 2007 | A1 |
| 20080195546 | Lilley | Aug 2008 | A1 |
| 20090022165 | Candelore et al. | Jan 2009 | A1 |
| 20090037972 | Pontual et al. | Feb 2009 | A1 |
| 20090044128 | Baumgarten | Feb 2009 | A1 |
| 20090055880 | Batteram et al. | Feb 2009 | A1 |
| 20090063681 | Ramakrishnan et al. | Mar 2009 | A1 |
| 20090100188 | Li et al. | Apr 2009 | A1 |
| 20090168903 | Vaquero et al. | Jul 2009 | A1 |
| 20090225026 | Sheba | Sep 2009 | A1 |
| 20090256859 | Komorowski | Oct 2009 | A1 |
| 20100082635 | Elsner et al. | Apr 2010 | A1 |
| 20100234007 | Shao | Sep 2010 | A1 |
| 20100299630 | Mccutchen | Nov 2010 | A1 |
| 20110007797 | Palmer et al. | Jan 2011 | A1 |
| 20110096225 | Candelore | Apr 2011 | A1 |
| 20110182366 | Frojdh et al. | Jul 2011 | A1 |
| 20110193982 | Kook | Aug 2011 | A1 |
| 20110200116 | Bloch et al. | Aug 2011 | A1 |
| 20110202562 | Bloch et al. | Aug 2011 | A1 |
| 20110276333 | Wang et al. | Nov 2011 | A1 |
| 20120032979 | Blow | Feb 2012 | A1 |
| 20120094768 | Mccaddon et al. | Apr 2012 | A1 |
| 20120110317 | Scheer et al. | May 2012 | A1 |
| 20120110618 | Kilar et al. | May 2012 | A1 |
| 20120147954 | Kasai | Jun 2012 | A1 |
| 20120178070 | Wiegand et al. | Jul 2012 | A1 |
| 20120229370 | Stroffolino | Sep 2012 | A1 |
| 20120278497 | Hsu | Nov 2012 | A1 |
| 20130028446 | Krzyzanowski | Jan 2013 | A1 |
| 20130047074 | Vestergaard et al. | Feb 2013 | A1 |
| 20130054728 | Amir et al. | Feb 2013 | A1 |
| 20130055321 | Cline et al. | Feb 2013 | A1 |
| 20130097643 | Stone et al. | Apr 2013 | A1 |
| 20130129304 | Feinson | May 2013 | A1 |
| 20130202265 | Arrasvuori | Aug 2013 | A1 |
| 20130235152 | Hannuksela et al. | Sep 2013 | A1 |
| 20130235270 | Sasaki et al. | Sep 2013 | A1 |
| 20130290818 | Arrasvuori et al. | Oct 2013 | A1 |
| 20130291002 | Rothschild et al. | Oct 2013 | A1 |
| 20130301918 | Frenkel | Nov 2013 | A1 |
| 20140015940 | Yoshida | Jan 2014 | A1 |
| 20140040959 | Oyman | Feb 2014 | A1 |
| 20140108622 | Guo | Apr 2014 | A1 |
| 20140152564 | Gulezian | Jun 2014 | A1 |
| 20140210860 | Caissy | Jul 2014 | A1 |
| 20140279032 | Roever | Sep 2014 | A1 |
| 20140314239 | Meyer | Oct 2014 | A1 |
| 20140368669 | Talvala et al. | Dec 2014 | A1 |
| 20150035750 | Bailey | Feb 2015 | A1 |
| 20150042704 | Smith et al. | Feb 2015 | A1 |
| 20150058115 | Iwaki et al. | Feb 2015 | A1 |
| 20150063781 | Silverman et al. | Mar 2015 | A1 |
| 20150070458 | Kim | Mar 2015 | A1 |
| 20150089074 | Oyman | Mar 2015 | A1 |
| 20150124171 | King | May 2015 | A1 |
| 20150201187 | Ryo | Jul 2015 | A1 |
| 20150208103 | Guntur | Jul 2015 | A1 |
| 20150256861 | Oyman | Sep 2015 | A1 |
| 20150326912 | Casagrande | Nov 2015 | A1 |
| 20150331933 | Tocchini, IV | Nov 2015 | A1 |
| 20150348325 | Voss | Dec 2015 | A1 |
| 20160063529 | Roeding et al. | Mar 2016 | A1 |
| 20160065831 | Howard | Mar 2016 | A1 |
| 20160105724 | Bloch et al. | Apr 2016 | A1 |
| 20160142889 | O'Connor | May 2016 | A1 |
| 20160170948 | Bloch | Jun 2016 | A1 |
| 20160173944 | Kilar | Jun 2016 | A1 |
| 20160241617 | Jelley | Aug 2016 | A1 |
| 20160323608 | Bloch et al. | Nov 2016 | A1 |
| 20160365117 | Boliek | Dec 2016 | A1 |
| 20170171275 | Bloch et al. | Jun 2017 | A1 |
| 20170178409 | Bloch et al. | Jun 2017 | A1 |
| 20170178601 | Bloch et al. | Jun 2017 | A1 |
| 20170201779 | Publicover | Jul 2017 | A1 |
| 20170223083 | Maze | Aug 2017 | A1 |
| 20170295410 | Bloch et al. | Oct 2017 | A1 |
| 20170345460 | Bloch et al. | Nov 2017 | A1 |
| 20180014049 | Griffin | Jan 2018 | A1 |
| 20180130501 | Bloch et al. | May 2018 | A1 |
| 20180191574 | Vishnia et al. | Jul 2018 | A1 |
| 20180254067 | Elder | Sep 2018 | A1 |
| 20180367840 | Kleinerman | Dec 2018 | A1 |
| 20190005549 | Goldshtein et al. | Jan 2019 | A1 |
| 20190075340 | Hochart | Mar 2019 | A1 |
| 20190090002 | Ramadorai | Mar 2019 | A1 |
| 20190349637 | Bloch et al. | Nov 2019 | A1 |
| 20190373330 | Bloch et al. | Dec 2019 | A1 |
| 20190392868 | Bloch et al. | Dec 2019 | A1 |
| 20200016746 | Yap | Jan 2020 | A1 |
| 20200194037 | Bloch et al. | Jun 2020 | A1 |
| 20200296316 | Post, Jr. | Sep 2020 | A1 |
| 20200296317 | Post, Jr. et al. | Sep 2020 | A1 |
| 20200296325 | Post, Jr. | Sep 2020 | A1 |
| 20200296462 | Post, Jr. | Sep 2020 | A1 |
| 20200365187 | Bloch et al. | Nov 2020 | A1 |
| 20200404382 | Bloch et al. | Dec 2020 | A1 |
| 20210045713 | Poland | Feb 2021 | A1 |
| 20210105433 | Bloch et al. | Apr 2021 | A1 |
| 20210209655 | Post, Jr. | Jul 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 2878329 | Jun 2018 | CA |
| 104685894 | Feb 2020 | CN |
| 2430631 | Mar 2012 | EP |
| 2678862 | Jan 2014 | EP |
| 2712206 | Mar 2014 | EP |
| 3013064 | Mar 2019 | EP |
| 2558086 | Feb 2019 | GB |
| 2010258732 | Nov 2010 | JP |
| 6516766 | May 2019 | JP |
| 100619034 | Aug 2006 | KR |
| 101773689 | Aug 2017 | KR |
| 201218770 | May 2012 | TW |
| 2005071683 | Aug 2005 | WO |
| 2007117298 | Oct 2007 | WO |
| 2010078281 | Jul 2010 | WO |
| 2010131244 | Nov 2010 | WO |
| 2012114329 | Aug 2012 | WO |
| 2012114330 | Aug 2012 | WO |
| 2012168365 | Dec 2012 | WO |
| 2013016707 | Jan 2013 | WO |
| 2013150378 | Oct 2013 | WO |
| 2014022018 | Feb 2014 | WO |
| 2015144735 | Oct 2015 | WO |
| Entry |
|---|
| Non-Final Office Action dated Feb. 27, 2020, for U.S. Appl. No. 16/742,642, filed Jan. 14, 2020, 15 pages. |
| International Search Report and Written Opinion dated Apr. 21, 2020, for PCT Application No. PCT/US2020/021932, six pages. |
| Non-Final Office Action dated Aug. 18, 2020, for U.S. Appl. No. 16/735,511, filed Jan. 6, 2020, nine pages. |
| Non-Final Office Action dated Dec. 30, 2019, for U.S. Appl. No. 16/405,648, filed May 7, 2019, 14 pages. |
| Non-Final Office Action dated Jul. 25, 2019, for U.S. Appl. No. 16/416,081, filed May 17, 2019, nine pages. |
| Notice of Allowance dated Sep. 19, 2019, for U.S. Appl. No. 16/416,081, filed May 17, 2019, 8 pages. |
| DASH Industry Forum. (Nov. 15, 2018). “Guidelines for Implementation:DASH-IF Interoperability Points,” Version 4.3, 254 pages. (submitted in 3 parts). |
| Dungate, Scott. (2014). “HONDA: The Other Side,” located at: www.scottdungate.com/honda-the-other-side-gallery, retrieved on May 6, 2020, three pages. |
| D'Acuntotno, Lucia, et al. (2016). “Using MPEG DASH SRD for zoomable and navigable video,” MMSys'16 May 10-13, 2016, Klagenfurt, Austria, located at: DOI: http://dx.doi.org/10.1145/2910017.2910634 , 4 pages. |
| FFMPEG. (2016). “Video grid with vstack and hstack [duplicate],” located at: https://stackoverflow.com/questions/36268431/video-grid-with-vstack-and-hstack retrieved Jan. 27, 2021, three pages. |
| FFMPEG. (2018). “How to Stitch Videos Together, Horizontally and Vertically Stitching,” located at: https://github.com/stoyanovgeorge/ffmpeg/wiki/How-to-Stitch-Videos-Together , retrieved Jan. 27, 2021, four pages. |
| FFMPEG. (date unknown). “man ffmpeg (1): ffmpeg video converter,” located at: www.manpages.org/ffmpeg , retrieved Jan. 27, 2021, 657 pages. |
| Final Office Action dated May 4, 2021, for U.S. Appl. No. 16/735,511, filed Jan. 6, 2020, 12 pages. |
| Final Office Action dated Oct. 27, 2020, for U.S. Appl. No. 16/405,648, filed May 7, 2019, 13 pages. |
| HTTP Live Streaming. (date unknown). “HLS Authoring Specification for Apple Devices,” Apple Developer Documentation, located at: https://developer.apple.com/documentation/http_live_streaming/hls_authoring_specification_for_apple_devices retrieved Jan. 27, 2021, thirty pages. |
| International Search Report and Written Opinion dated Mar. 11, 2021, for PCT Application No. PCT/US2021/012376, eight pages. |
| International Search Report and Written Opinion dated Mar. 25, 2021, for PCT/US21/12378, filed Jan. 6, 2021, twelve pages. |
| Khiem, et al. (2011). Tiled Streaming Presentation “Adaptive Encoding , Zoomable Video Streams based on User Access Pattern,”, National University of Singapore, 31 pages. |
| Khiem, et al. (2011). “Adaptive Encoding , Zoomable Video Streams based on User Access Pattern,” MMSys'11, Feb. 23-25, 2011, San Jose, California, USA, 12 pages. |
| Lürzer's Archive (Nov. 20, 2014). “Honda's clever spot lets you switch between parallel storylines,” located at: https://www.luerzersarchive.com/en/features/digital/hondas-clever-spot-lets-you-switch-between-parallel-storylines-711.html, retrieved Jan. 27, 2021, ten pages. |
| Miller, G. et al. (2009). “MiniDiver: A Novel Mobile Media Playback Interface for Rich Video Content on an iPhoneTM,” IFIP International Federation for Information Processing 2, ICEC 5709, pp. 98-109. |
| MPEG2TS Stream—Transport Stream. (Dec. 17, 2014). “Rusty Techie,” located at: http://rustytechie.blogspot.com/2014/12/mpeg2ts-stream-transport-stream.html retrieved Jan. 27, 2021, six pages. |
| Notice of Allowability dated Feb. 12, 2021, for U.S. Appl. No. 16/742,642, filed Jan. 14, 2020, eight pages. |
| Notice of Allowance dated Oct. 27, 2020, for U.S. Appl. No. 16/742,642, filed Jan. 14, 2020, seven pages. |
| Paul B Mahol . (2015). “[FFMPEG-user] mosaic video 2×2, 3×3 etc.,” located at: https://lists.ffmpeg.org/pipermail/ffmpeg-user/2015-December/029493.html, retrieved Jan. 27, 2021, three pages. |
| Prins, M. J. et al. (2013). “A Hybrid Architecture for Delivery of Panoramic Video,” EurolTV'13, Jun. 24-26, 2013, Como, Italy., 8 pages. |
| Takacs, B. (Mar. 10, 2010). “Immersive interactive reality: Internet-based on-demand VR for cultural presentation,” Cultural Technology, Springer-Verlag London Limited 2010, thirteen pages. |
| Xu, Y. et al. (2018), “Omnidirectional Media Format and Its Application to Immersive Video Streaming: An Overview,” located at: https://docplayer.net/151550752-Omnidirectional-media-format-and-its-application-to-immersive-video-streaming-an-overview.html 11 pages. |
| Adobe Systems Incorporated, (1998). “Adobe Photoshop, version 5.0,” User Guide, 400 pages. |
| Barrett, Rob, et al. (1997). “How to Personalize the Web,” CHI 97, Atlanta, GA, USA, eight pages. |
| Barthel, Ralph, et al. (Feb. 2012). “Collaborative knowledge building with shared video representations,” EISEVIER, available at: www.sciencedirect.com, 17 pages. |
| Broida, Rick (Nov. 3, 2006). “Download of the Day Fasterfox (Firefox),” three pages. |
| CTA Bulletin. (Jul. 2009). “AV Synchronization Processing Recommended Practice,” Consumer Technology Association, 21 pages. |
| Decision. (Oct. 23, 2017). “Radware, Inc., Petitioner, v. F5 Networks, Inc., Patent Owner.”, Case IPR2017-01249 U.S. Pat. No. 6,311,278 B1. |
| Decision. (Dec. 21, 2016). “Global Tel Link Corporation, Petitioner, v. Securus Technologies, Inc., Patent Owner,” Case IPR2015-01226, U.S. Pat. No. 8,135,115 B1. |
| Decision. (Feb. 27, 2020). “Stephanie Barnard Designs, Inc., Petitioner, v. Ellison Educational Equipment, Inc., Patent Owner,” IPR2020-00150, U.S. Pat. No. 9,079,325 B2. |
| Decision. (Jan. 19, 2016). “Daifuku Co., Ltd. and Daifuku America Corp., Petitioner, v. Murata Machinery, Ltd., Patent Owner.”, Case IPR2015-01538, U.S. Pat. No. 6,113,341. |
| Decision. (Jul. 7, 2017). “Vizio, Inc., Petitioner, v. Nichia Corporation, Patent Owner,” Case IPR2017-00551, U.S. Pat. No. 7,915,631 B2. |
| Decision. (May 11, 2016). “Enovate Medical, LLC, Petitioner, v. Intermetro Industries Corporation, Patent Owner,” Case IPR2015-00300, U.S. Pat. No. 6,721,178 B1. |
| Decision. (Sep. 6, 2018). “Sirius XM Radio, Inc., Petitioner, v. Fraunhofer-Gesellschaft Zur Förderung Der Angewandten Forschung E.V., Patent Owner,” Case IPR2018-00681 U.S. Pat. No. 7,061,997 B1. |
| Edgar, Edmund. (2006). Prefetching Hints-Helping Firefox and Google Speed up your site, The Prefetching Problem, 3 pages. |
| Fisher. (2003). “Link prefetching FAQ,” MDN web docs, 6 pages. |
| Gao, Zhenhuan et al. (Nov. 3-7, 2014). “FreeViewer: An Intelligent Director for 3D Tele-Immersion System,” Orlando, Florida, USA, located at: http://dx.doi.org/10.1145/2647868.2654873. |
| Gao, Zhenhuan et al. (Oct. 2015). “OmniViewer: Enabling Multi-modal 3D DASH,” Brisbane, Australia, located at: http://dx.doi.org/10.1145/2733373.2807971. |
| GPAC, Multimedia Open Source Project, located at: https://gpac.wp.imt.fr/home/gpac-features/ retrieved May 24, 2021, two pages. |
| Hailin Xie, et al. (2009). “An Efficient Caching Mechanism for Video-on-Demand Service over Peer-to-Peer Network,” IEEE Computer Society,The Eighth IEEE International Conference on Embedded Computing, 6 pages. |
| IAB. (Apr. 10, 2012). “Video Player-Ad Interface Definition (VPAID), Version 2.0” located: http://www.iab.net/videosuite/vpaid, 58 pages. |
| IAB. (Nov. 2009). “Digital Video Ad Serving Template (VAST) Version 2.0,” located at: http://www.iab.net/vast, 16 pages. |
| International Search Report dated Jul. 31, 2013, for PCT Application No. PCT/IB2013/001000, eleven pages. |
| International Standard, (2005). “Information technology—Generic coding of moving pictures and associated audio information: Systems,” Second edition Dec. 1, 2000, ISO/IEC. |
| International Standard, (2005). “Information technology—Coding of audio-visual objects,” Part 12: ISO base media file format, ISO/IEC 14496-12. |
| ITU-T. (Apr. 2015). “High efficiency video coding,” H.265, Rec. ITU-T H.265 v3 (Apr. 2015). |
| Jan van der Meer, (2014). “Fundamentals and Evolution of MPEG 2 Systems,” 2014 John Wiley & Sons, Ltd. |
| Kaspar, Dominik, et al. (2010). “Enhancing Video-on-Demand Playout over Multiple Heterogeneous Access Networks,” 2010 IEEE , 5 pages. |
| Kaspar, Dominik, et al. (2010). “Using HTTP Pipelining to Improve ProgressiveDownload over Multiple Heterogeneous Interfaces,” IEEE Communications Society, 5 pages. |
| Khemmarat, Samamon, et al. (2011). “Watching User Generated Videos with Prefetching,” Feb. 23-25, 2011, San Jose, CA, USA, 12 pages. |
| Lieberman, Henry. (Aug. 1995). “Letizia: An Agent That Assists Web Browsing,” Proceedings of the 14th International joint conference on Artificial intelligence—vol. 1, pp. 924-929. |
| Lourdes Beloqui, et al. (2015). “Understanding Timelines within MPEG Standards,” IEEE Communications Surveys & Tutorials, 33 pages. |
| MDialog. (Apr. 7, 2010). “mDialog Debuts First Dynamic Ad-Insertion and Video Solution Platform for HTML5 VOD and Live Streaming on iPad and iPhone,” mDialog, located at: https://www.globenewswire.com/news-release/2010/04/07/1062211/0/en/mDialog-Debuts-First-Dynamic-Ad-Insertion-and-Video-Solution-Platform-for-HTML5-VOD-and-Live-Streaming-on-iPad-and-iPhone.html. |
| NAB. (Aug. 3, 2009). “CEA Publishes Recommended Practice on A/V Synchronization Implementation in Receivers,” TV TechCheck, 3 pages. |
| Pantos, R. et al. (Mar. 23, 2012). “HTTP Live Streaming draft-pantos-http-live-streaming-08,” Apple Inc. 33 pages. |
| Riiser, Haakon, et al. (2011). “Video Streaming Using a Location-based Bandwidth-Lookup Service for Bitrate Planning,” ACM Transactions on Multimedia Computing, Communications and Applications, vol. 0, No. 0, Article 0, twenty four pages. |
| Robert Skupin, et al. (2016). “Tile Based HEVC Video for Head Mounted Displays,” 2016 IEEE International Symposium on Multimedia, Exhibit A, Case 2:20-cv-02299-JAK-SK Document 64-18 Filed Apr. 24, 2020 p. 1 of 3 p. ID #:4064. |
| Romulus Grigoras, et al. (2002). “Optimizing Hypervideo Navigation using a Markov Decision Process Approach,” 10 pages. |
| SMIL. (Date Unknown). “SMIL 3.0 Content Control,” https://www.w3.org/TR/REC-smil/smil-content.html. |
| SMIL. (Dec. 1, 2008). “Synchronized Multimedia Integration Language (SMIL 3.0),” W3C, 20 pages. http://www.w3.org/TR/2008/REC-SMIL3-20081201/. |
| Sodagar, Iraj, (2011). “The MPEG-DASH Standard for Multimedia Streaming Over the Internet,” Industry and Standards, IEEE Computer Society. |
| Taylor, Jim, et al. (2001). “DVD Demystified,” Second Edition, The McGraw-Hill Companies. |
| Taylor, Jim, et al. (2006). “DVD Demystified,” Third Edition, The McGraw-Hill Companies. |
| Tektronix, (2012). “A Guide to MPEG Fundamentals and Protocol Analysis,” Updated with QoS/QoE Diagnostics and Troubleshooting Primer, www.tektronix.com/video_audio. |
| U.S. Appl. No. 61/732,536, filed Dec. 3, 2012. |
| Wei Zhang, et al. (2003). “Personalized Web Prefetching in Mozilla,” Department of Computer Science and Engineering, Lehigh University, Bethlehem, PA. |
| Williams_Decl_Exhibit_D_PUBLIC, (Apr. 13, 2020). “Merge two video clips into one, placing them next to each other,”—Unix & Linux Stack Exchange, Exhibit D, Case 2:20-cv-02299-JAK-SK Document 42-40 Filed Apr. 14, 2020 p. 1 of 5 p. ID #:3125, located at: https://unix.stackexchange.com/questions/233832/merge-tw, o-video-clips-into-one-placing-them-next-to-each other. |
| Williams_Decl_Exihibit_C_PUBLIC, (Apr. 13, 2020). “How do I make videos side by side (both playing at the same time) in Premiere Pro or After Effects,” Exhibit C, Case 2:20-cv-02299-JAK-SK Document 42-39 Filed Apr. 14, 2020 p. 1 of 8 p. ID #:3117, located at: https://www.quora.com/How-do-I-make-videos-side-by-side-both-playing-at-the-same-time-in-Premiere-Pro-or-After-Effects. |
| U.S. Appl. No. 16/405,648 Published as US2020/0296462, Media Content Presentation, filed May 7, 2019. |
| U.S. Appl. No. 16/416,081 U.S. Pat. No. 10,554,926, Media Content Presentation, filed May 17, 2019. |
| U.S. Appl. No. 16/742,642 Published as US2020/0296325, Media Content Presentation, filed Jan. 14, 2020. |
| U.S. Appl. No. 16/735,511 Published as US2020/0296316, Media Content Presentation, filed Jan. 6, 2020. |
| Non-Final Office Action dated Nov. 19, 2020, for U.S. Appl. No. 16/791,568, filed Feb. 14, 2020, 10 pages. |
| Yuste, L. B., et al. (2015) “Understanding Timelines within MPEG Standards”, IEEE Communications Surveys & Tutorials, 33 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20200296317 A1 | Sep 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62816884 | Mar 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16735511 | Jan 2020 | US |
| Child | 16791568 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16405648 | May 2019 | US |
| Child | 16735511 | US |
