The present disclosure is directed to the remote synchronization of digital data.
According to some exemplary embodiments, the present disclosure is directed to a method for remote synchronization of digital data, including receiving a name of an event, a list of users, and a template, receiving from a plurality of remote computing devices digital data, each of the remote computing device associated with a user on the list of users, compositing the digital data onto the template, notifying the plurality of remote computing devices about the composited digital data and providing the plurality of remote computing devices with access to the composited digital data. Further methods include transmitting the digital data as a stream from each of the plurality of remote computing devices and the stream comprising digital data automatically captured by each of the plurality of remote computing devices after receiving a triggering signal. Additionally, the triggering signal may be initiated by one of the plurality of the remote computing devices and the digital data may be transmitted as a plurality of digital data images.
Additional methods include capturing audio digital data, compositing of the digital data onto the template within a predefined time limit, identifying a remote computing device unable to transmit the digital data within the predefined time limit and adjusting computing resources available to the identified remote computing device so that it can transmit the digital data within the predefined time limit. Also included is transmitting the composited digital data to a public display device and transmitting the captured audio digital data to a public address system. Methods may include continuing to transmit newly received audio digital data after the compositing and/or where the received audio digital data is associated with a performing entity at the event. A volume or a magnitude of the received audio digital data may be represented on the public address system.
Further methods may include the event being live and being viewed on television by the user on the list of users and transmitting the composited digital data to the live event. Additionally, the transmitting may be to a public display device at the live event and the public display device is viewable on the television by the user on the list of users. Moreover, the template may include content related to the live event. The transmitting of content from the live event may be made to the plurality of remote computing devices. The digital data may also comprise three to nine seconds of video digital data or may be a series of images displayed sequentially as a live picture. Additionally, the template may be dynamic and/or include an advertisement.
In some exemplary embodiments, a Bluetooth low energy signal may activate a program on a personal digital assistant to trigger a Social Cam. Also, content associated with the event may be included with the composited digital data. The Bluetooth low energy signal may also activate a secure key on the program evidencing a copyright license to a user for recording a portion of the event. The composited digital data may be printed or downloaded onto a thumb drive.
Certain embodiments of the present technology are illustrated by the accompanying figures. It will be understood that the figures are not necessarily to scale. It will be understood that the technology is not necessarily limited to the particular embodiments illustrated herein.
The Internet has changed everything. Users all belong to a distributed community. Users manage friendships through social networks. Users use the Internet to leave a trail of their existence. Most users enjoy a shared memory, online. Today, more than ever, pictures are the best and most used tool to share experiences.
Space is not the limit anymore. To the contrary, time has been stretched. Real-time rules. Users are happy when the first LIKE is added to a post, and users are nervous when they have to wait for such acknowledgement.
In this new world, where time and space have been bended by social networks, users share experiences more than ever. And the experiences users share tend to be remote experiences:
Users watch TV with a tablet in their lap.
Users attend online courses with remote classmates.
Users belong to the same gaming community.
Users chat on social networks through their smartphones, and much more.
In this new world, every second people create and share memories. Not that long ago, on Facebook, for example, 250 million pictures were uploaded daily. On Instagram, 4 million pictures were uploaded daily, which triggered 100 comments each. Instagram was acquired by Facebook for one billion dollars, and Instagram was just an app to shoot and share pictures.
Despite this enormous activity, all of the picture sharing is based on pictures that are not “shared.” Everybody can share their own picture, but this never represents a memory of a shared experience, such as a shared experience of friends who are geographically spread across the planet.
Provided herein is a tool that allows people to share a common experience, even if they are physically in different locations. A tool that creates a single picture by combining a set of pictures, each picture taken by a different individual on their camera. A truly shared picture. This tool enables a new way of sharing experiences online, which has key applications in many areas, including targeted advertising.
The “Social Cam” or multiple remote picture synchronization tool, is the answer to the evolution of internet social behaviors. It is extremely relevant to build more precise networks of user relations. The exemplary embodiments described herein solve the multiple remote picture synchronization problem.
Shown in environment 100 are user devices 105 through X, and network 120.
Multiple remote users connect via different devices to shoot pictures through the camera on their device. A cloud service controls the interaction of the different devices. The devices include, for example, but are not limited to:
Mobile phones.
Tablets.
Laptop and desktop personal computers with embedded cameras.
Televisions with embedded cameras.
Point and shoot connected cameras.
Picture frames with embedded cameras.
The “Social Cam” or multiple remote picture synchronization tool works on virtually any device with a camera and that has the capability to connect to a network. Network connectivity may be on a local area network (“LAN”) or the Internet, via a wired or wireless connection (e.g. Wi-Fi, 3G, 4G, satellite, etc.).
Shown in background picture 200 are three rectangles marked “SF” where digital data, such as images may be composited.
According to exemplary embodiments, creating the perfect “context” for shared experiences includes an event, a list of users and a template. In some exemplary embodiments, the event is a reason why users would like to have a shared memory (e.g. a baseball game or a private party). The users participate in the event, either in person (e.g. a wedding) or remotely (e.g. a baseball game watched in front of each user's TV). The users can be considered as actors in taking a picture and creating a collage, which can be shared later. The visual template, such as that shown in
As shown in
In various exemplary embodiments, Social Cam pictures are “live”, changing with time. For example, a picture from a baseball game could keep showing the real-time game score and then update itself with the final score, when the game is over.
Shown in the “pose with your friends” example 300 are dark silhouettes where digital data, such as images may be composited.
As shown in
Shown in the “pose with your hero” example 400 are two blurred faces on either side of the hero 405 where digital data, such as images may be composited.
Other preset templates may be prepared by sponsors who own the rights to the image.
Shown in the newborn example 500 are spots 510 through X where digital data, such as images may be composited.
In this example, the newborn is surrounded by a tree of “connected” love, and this tree is colored and takes shape according to the number of people that are included in the picture.
Shown on pregame yell screen 700 are four users via their respective social cam devices preparing to yell while connected to a cloud service.
Shown on game yell screen 800 is a “3-2-1 Yell NOW” countdown.
Shown on template 900 are various pictures forming a heart shape.
According to various exemplary embodiments, the “Social Cam” or the multiple remote picture synchronization tool operates under two different scenarios: real-time and off-line.
At step 1005, all users in a group connect their respective devices to a cloud service.
At step 1010, one of the users triggers the Social Cam feature on their device by selecting a specific template (which could be shared or hidden from the other users). The device of the user triggering the feature will request a Social Cam activity to the cloud service.
At step 1015, the cloud service notifies all of the other user devices in a group that a Social Cam event is about to happen.
At step 1020, on all of the user devices in the group, at the same time, the Social Cam feature will be activated. Alternatively, a request for a Social Cam event will be visually perceptible on all of the user devices in the group. In this case, only the devices of the users accepting the Social Cam event will be involved in the event.
At step 1025, a countdown will be triggered by the cloud service on each user device in the group.
At step 1030, a picture is taken simultaneously on all of the user devices in the group.
At step 1035, the template (from step 1010) is used to compose the final Social Cam picture, which can be shared or hidden from the other users in the group. Users with access to the Social Cam picture will be able to save it or share it via email, social networks, upload on photo sites and so on. Third party services can be integrated to allow printing (on paper, on clothing or on objects) or 3D printing of the Social Cam picture.
At step 1105, one of the users in the group of users triggers the Social Cam feature on their respective device, selecting a specific template (which could be shared or hidden from the other users).
At step 1110, the device of the user triggering the Social Cam feature requests a Social Cam event to a cloud service.
At step 1115, the cloud service notifies all of the other user devices in the group that a Social Cam event is about to happen.
At step 1120, the devices of the users in the group that are not connected to the cloud service are notified. If in response to the notification a user in the group activates their device, they will be able to participate in a real-time Social Cam event. If a user does not activate their device, they will still be able to add to the group picture at a later time.
At step 1125, the devices of the users in the group that are connected to the cloud service, will activate the Social Cam feature.
Alternatively, a request for a Social Cam event can be visualized on the user devices in the group. In this case, only the devices of the users accepting the Social Cam event will be involved in the event. For those users who do not accept the Social Cam event, the Social Cam will be available at a later time. According to some exemplary embodiments, the Social Cam event has an “expiration date”, after which it will not be possible for the invited users to add to their picture.
At step 1130, each of the devices of the users in the group that are connected and not connected to the cloud service receive a countdown.
At step 1135, a picture is simultaneously taken on all of the user devices that are connected to the cloud service, and all of the users in the group that are not connected to the cloud service will be allowed to add to the picture when they connect.
At step 1140, the template is used to compose the final Social Cam picture, which can be shared or hidden from the other users. Users with access to the Social Cam picture may save it or share it via email, social networks, upload on photo sites and so on. Third party services may be integrated to allow printing (on paper, on clothing or on objects) or 3D printing of the Social Cam picture.
One issue with remote synchronization is the timing of the synchronization, in order to make sure the pictures are all taken at the same time, without adding delays for individual users that are on a slower network. In some exemplary environments, the cloud service sends each user device in a group a ping command to evaluate the time needed by the cloud service to reach each user device in the group. The delay will then be used by the cloud service to properly time the photo shooting, to make sure it happens at the same exact time (or as close as possible). Considering that the time to transport the command “shoot now” over a network is measured in milliseconds, it should have a close to zero delay in most cases. This feature therefore generates a perfectly synced experience, which might be useful in some cases (e.g. when a home run is hit in a baseball game).
In exemplary further embodiments, additional features of the Social Cam include pick the best shot. This is where a user takes multiple shots in sequence, then picks the best picture. This would remove the surprised facial effect, and allow individual users to be more satisfied of the final result.
In exemplary further embodiments, additional features of the Social Cam include geotagging. Geotagging allows the Social Cam to extract the location of a user device (via GPS or other means), when available and authorized by the user. This information could be used to enhance the final Social Cam picture, including the location in the world of each participant. This would create the ability to put individual pictures on a map and more.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present technology has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the present technology in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present technology. Exemplary embodiments were chosen and described in order to best explain the principles of the present technology and its practical application, and to enable others of ordinary skill in the art to understand the present technology for various embodiments with various modifications as are suited to the particular use contemplated.
Aspects of the present technology are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present technology. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present technology. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In the description, for purposes of explanation and not limitation, specific details are set forth, such as particular embodiments, procedures, techniques, etc. in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details.
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” or “according to one embodiment” (or other phrases having similar import) at various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Furthermore, depending on the context of discussion herein, a singular term may include its plural forms and a plural term may include its singular form. Similarly, a hyphenated term (e.g., “on-demand”) may be occasionally interchangeably used with its non-hyphenated version (e.g., “on demand”), a capitalized entry (e.g., “Software”) may be interchangeably used with its non-capitalized version (e.g., “software”), a plural term may be indicated with or without an apostrophe (e.g., PE's or PEs), and an italicized term (e.g., “N+1”) may be interchangeably used with its non-italicized version (e.g., “N+1”). Such occasional interchangeable uses shall not be considered inconsistent with each other.
Also, some embodiments may be described in terms of “means for” performing a task or set of tasks. It will be understood that a “means for” may be expressed herein in terms of a structure, such as a processor, a memory, an I/O device such as a camera, or combinations thereof. Alternatively, the “means for” may include an algorithm that is descriptive of a function or method step, while in yet other embodiments the “means for” is expressed in terms of a mathematical formula, prose, or as a flow chart or signal diagram.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
If any disclosures are incorporated herein by reference and such incorporated disclosures conflict in part and/or in whole with the present disclosure, then to the extent of conflict, and/or broader disclosure, and/or broader definition of terms, the present disclosure controls. If such incorporated disclosures conflict in part and/or in whole with one another, then to the extent of conflict, the later-dated disclosure controls.
The terminology used herein can imply direct or indirect, full or partial, temporary or permanent, immediate or delayed, synchronous or asynchronous, action or inaction. For example, when an element is referred to as being “on,” “connected” or “coupled” to another element, then the element can be directly on, connected or coupled to the other element and/or intervening elements may be present, including indirect and/or direct variants. In contrast, when an element is referred to as being “directly connected” or “directly coupled” to another element, there are no intervening elements present. The description herein is illustrative and not restrictive. Many variations of the technology will become apparent to those of skill in the art upon review of this disclosure.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. The descriptions are not intended to limit the scope of the invention to the particular forms set forth herein. To the contrary, the present descriptions are intended to cover such alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims and otherwise appreciated by one of ordinary skill in the art. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments.
This application is a continuation in part of U.S. Non-Provisional application Ser. No. 13/857,994, filed on Apr. 6, 2013, titled “System and Methods of Synchronizing Program Reproduction on Multiple Geographically Remote Display Systems,” which claims the priority benefit of U.S. Provisional Application Ser. No. 61/621,464, filed on Apr. 6, 2012, titled “Voice-Enabled Social TV Experience” and also claims the priority benefit of U.S. Provisional Application Ser. No. 61/621,462, filed on Apr. 6, 2012, titled “Method to Synchronize Multiple TVs,” all of which [Fish] are hereby incorporated by reference in their entirety, including all references and appendices cited therein. This application is also a continuation in part of U.S. Non-Provisional application Ser. No. 13/857,995, filed on Apr. 6, 2013, titled “System and Methods of Communicating between Multiple Geographically Remote Sites to Enable a Shared, Social Viewing Experience,” which claims the priority benefit of U.S. Provisional Application Ser. No. 61/621,464, filed on Apr. 6, 2012, titled “Voice-Enabled Social TV Experience” and also claims the priority benefit of U.S. Provisional Application Ser. No. 61/621,462, filed on Apr. 6, 2012, titled “Method to Synchronize Multiple TVs,” all of which [Fish] are hereby incorporated by reference in their entirety, including all references and appendices cited therein. This application also claims the benefit and priority of U.S. Provisional Application Ser. No. 62/336,505, filed on May 13, 2016, titled “Method to Remotely Synchronize Photos” which is hereby incorporated by reference in its entirety, including all references and appendices cited therein.
Number | Name | Date | Kind |
---|---|---|---|
5508815 | Levine | Apr 1996 | A |
5517652 | Miyamoto et al. | May 1996 | A |
5544161 | Bigham et al. | Aug 1996 | A |
5557724 | Sampat et al. | Sep 1996 | A |
5565909 | Thibadeau et al. | Oct 1996 | A |
5600573 | Hendricks et al. | Feb 1997 | A |
5621456 | Florin et al. | Apr 1997 | A |
5652613 | Lazarus et al. | Jul 1997 | A |
5661516 | Carles | Aug 1997 | A |
5701383 | Russo et al. | Dec 1997 | A |
5701582 | DeBey | Dec 1997 | A |
5724521 | Dedrick | Mar 1998 | A |
5758259 | Lawler | May 1998 | A |
5805763 | Lawler et al. | Sep 1998 | A |
5861906 | Dunn et al. | Jan 1999 | A |
5880792 | Ward et al. | Mar 1999 | A |
5892535 | Allen et al. | Apr 1999 | A |
5973683 | Cragun et al. | Oct 1999 | A |
5978043 | Blonstein et al. | Nov 1999 | A |
6005631 | Anderson et al. | Dec 1999 | A |
6014184 | Knee et al. | Jan 2000 | A |
6014694 | Aharoni et al. | Jan 2000 | A |
6020930 | Legrand | Feb 2000 | A |
6049333 | Lajoie et al. | Apr 2000 | A |
6049831 | Gardell et al. | Apr 2000 | A |
6075575 | Schein et al. | Jun 2000 | A |
6083009 | Kim et al. | Jul 2000 | A |
6115740 | Mizutani | Sep 2000 | A |
6160545 | Eyer et al. | Dec 2000 | A |
6160546 | Thompson et al. | Dec 2000 | A |
6184878 | Alonso et al. | Feb 2001 | B1 |
6201536 | Hendricks et al. | Mar 2001 | B1 |
6229524 | Chernock et al. | May 2001 | B1 |
6246442 | Harada et al. | Jun 2001 | B1 |
6285685 | Bum | Sep 2001 | B1 |
6314569 | Chernock et al. | Nov 2001 | B1 |
6378129 | Zetts | Apr 2002 | B1 |
6400996 | Hoffberg et al. | Jun 2002 | B1 |
6442604 | Romine | Aug 2002 | B2 |
6470378 | Tracton et al. | Oct 2002 | B1 |
6567847 | Inoue | May 2003 | B1 |
6615244 | Singhal | Sep 2003 | B1 |
6738978 | Hendricks et al. | May 2004 | B1 |
6766526 | Ellis | Jul 2004 | B1 |
6769127 | Bonomi et al. | Jul 2004 | B1 |
6774926 | Ellis et al. | Aug 2004 | B1 |
6817028 | Jerding et al. | Nov 2004 | B1 |
6922843 | Herrington et al. | Jul 2005 | B1 |
6981045 | Brooks | Dec 2005 | B1 |
6991724 | Brodbeck et al. | Jan 2006 | B2 |
6993721 | Rosin | Jan 2006 | B2 |
7065342 | Rolf | Jun 2006 | B1 |
7143432 | Brooks et al. | Nov 2006 | B1 |
7343614 | Hendricks et al. | Mar 2008 | B1 |
8869222 | Winograd et al. | Oct 2014 | B2 |
9510044 | Pereira et al. | Nov 2016 | B1 |
9756397 | Bonomi et al. | Sep 2017 | B1 |
10321192 | Zaccone et al. | Jun 2019 | B2 |
20010001160 | Shoff et al. | May 2001 | A1 |
20010005903 | Goldschmidt Iki et al. | Jun 2001 | A1 |
20020007485 | Rodriguez et al. | Jan 2002 | A1 |
20020010917 | Srikantan et al. | Jan 2002 | A1 |
20020136335 | Liou et al. | Sep 2002 | A1 |
20030088872 | Maissel et al. | May 2003 | A1 |
20030110499 | Knudson et al. | Jun 2003 | A1 |
20030146940 | Ellis et al. | Aug 2003 | A1 |
20030149988 | Ellis et al. | Aug 2003 | A1 |
20030151621 | McEvilly et al. | Aug 2003 | A1 |
20030182659 | Ellis et al. | Sep 2003 | A1 |
20030195984 | Zisapel et al. | Oct 2003 | A1 |
20050028208 | Ellis et al. | Feb 2005 | A1 |
20050149988 | Grannan | Jul 2005 | A1 |
20050229213 | Ellis et al. | Oct 2005 | A1 |
20060031883 | Ellis et al. | Feb 2006 | A1 |
20060136965 | Ellis et al. | Jun 2006 | A1 |
20060156375 | Konetski | Jul 2006 | A1 |
20060161951 | Hindle et al. | Jul 2006 | A1 |
20060236352 | Scott | Oct 2006 | A1 |
20060244818 | Majors | Nov 2006 | A1 |
20070053513 | Hoffberg | Mar 2007 | A1 |
20070157253 | Ellis et al. | Jul 2007 | A1 |
20070288959 | Istvan et al. | Dec 2007 | A1 |
20080091845 | Mills et al. | Apr 2008 | A1 |
20080177557 | Saul | Jul 2008 | A1 |
20090077589 | Boyer et al. | Mar 2009 | A1 |
20090094365 | Orady et al. | Apr 2009 | A1 |
20090118018 | Perlman et al. | May 2009 | A1 |
20090119780 | Ham | May 2009 | A1 |
20090313671 | Gaughan et al. | Dec 2009 | A1 |
20100083324 | Smith et al. | Apr 2010 | A1 |
20100119208 | Davis et al. | May 2010 | A1 |
20100211975 | Boyer et al. | Aug 2010 | A1 |
20100235466 | Jung | Sep 2010 | A1 |
20110063503 | Brand et al. | Mar 2011 | A1 |
20110078303 | Li et al. | Mar 2011 | A1 |
20110099616 | Mazur et al. | Apr 2011 | A1 |
20110106883 | Gupta et al. | May 2011 | A1 |
20110145881 | Hartman | Jun 2011 | A1 |
20110246908 | Akram et al. | Oct 2011 | A1 |
20110247031 | Jacoby | Oct 2011 | A1 |
20110283203 | Periyannan | Nov 2011 | A1 |
20120072608 | Peters et al. | Mar 2012 | A1 |
20120098920 | Pennington et al. | Apr 2012 | A1 |
20120136988 | Jackson | May 2012 | A1 |
20120159348 | Stroomer | Jun 2012 | A1 |
20120192016 | Gotesdyner et al. | Jul 2012 | A1 |
20120210379 | McCoy et al. | Aug 2012 | A1 |
20120226769 | Basso et al. | Sep 2012 | A1 |
20120331476 | Saffre | Dec 2012 | A1 |
20130018978 | Crowe et al. | Jan 2013 | A1 |
20130076980 | Oren et al. | Mar 2013 | A1 |
20130091284 | Rothschild | Apr 2013 | A1 |
20130093648 | Im | Apr 2013 | A1 |
20130173710 | Seo | Jul 2013 | A1 |
20130222638 | Wheeler | Aug 2013 | A1 |
20130251329 | McCoy et al. | Sep 2013 | A1 |
20130254820 | Bonomi | Sep 2013 | A1 |
20130275582 | Gedam et al. | Oct 2013 | A1 |
20130290502 | Bilobrov et al. | Oct 2013 | A1 |
20130308818 | MacIntosh et al. | Nov 2013 | A1 |
20140071344 | Francisco | Mar 2014 | A1 |
20140108671 | Watson et al. | Apr 2014 | A1 |
20140169196 | Kay | Jun 2014 | A1 |
20140189042 | Chen | Jul 2014 | A1 |
20150038234 | Bojorquez et al. | Feb 2015 | A1 |
20150046591 | Zhu et al. | Feb 2015 | A1 |
20150089051 | Ojanpera | Mar 2015 | A1 |
20150146874 | Ojanpera | May 2015 | A1 |
20150288619 | Fritsch | Oct 2015 | A1 |
20160249081 | Capobianco | Aug 2016 | A1 |
20170150223 | Zaccone et al. | May 2017 | A9 |
Number | Date | Country |
---|---|---|
0909095 | Apr 1999 | EP |
1117050 | Jul 2001 | EP |
W01998000976 | Jan 1998 | WO |
W02000030354 | May 2000 | WO |
W02001006800 | Jan 2001 | WO |
W02001038960 | May 2001 | WO |
WO-2013029263 | Mar 2013 | WO |
WO2013079993 | Jun 2013 | WO |
WO2013144681 | Oct 2013 | WO |
Entry |
---|
Minerva Networks, Inc., “Minerva Impression: Interactive Video Authoring for DVD,” User's Manual, Version 1.0, 1998, pp. 1-102. |
Minerva Networks, Inc., “Media Demon™ Management Software for Rich-Media Delivery Services,” 2000, pp. 1-2. |
Minerva Networks, Inc., “Media Demon™ Management Software for Rich-Media Services”, [retrieved on May 1, 2000], Retrieved from the Internet: <URL:http://www.minervanetworks.com/video_over_networks/mediademon.html>, pp. 1-3. |
Minerva Networks, Inc.,“Minerva VNP,” [retrieved on May 1, 2000], Retrieved from the Internet: <URL:http://www.minervanetworks.com/video_over_networks/vnp.html>, pp. 1-4. |
Minerva Networks, Inc.,“Minerva VDK—Video Network Development Kit for VNP,” [retrieved on May 2, 2000], Retrieved from the Internet: <URL:http://www.minervanetworks.com/video_over_networks/von_vdk.html>, pp. 1-4. |
Ploskina, Brian, “Broadband TV? No Telephone Rewiring Necessary,” publication date unknown, 1 page. |
Smith, G.L. et al., “Design of Multimedia Services,” BT Technology Journal, vol. 13, No. 4, BT Laboratories, GB, Oct. 1995, pp. 21-31. |
Whyte, W.S., “The Many Dimensions of Multimedia Communications,” BT Technology Journal, vol. 13, No. 4, BT Laboratories, GB, Oct. 1995, pp. 9-20. |
Brull, Steve et al., “Sony's New World,” BusinessWeek, May 27, 1996. Issue 3477, p. 100-108, [retrieved on Feb. 8, 2011], Retrieved from the Internet: <URL:http://www.businessweek.com/1996/22/b3477134.hmt>, 10 pages. |
Krause, “HP Set-Top Maneuvers Accent NCTA,” Electronic News, May 30, 1994. vol. 40, No. 2016, 2 pages. |
Tedesco, Richard, “New Modems Ease Net Access,” Broadcasting & Cable, Jun. 21, 1999, vol. 129, No. 26, p. 64. |
Wilson, Carol, “Content Is Key,” Telephony, Jul. 18, 1994. vol. 227, No. 3, p. 21-28. |
Minerva Networks, Inc., Minerva Impression: Interactive Video Authoring, [retrieved on May 1, 2000], Retrieved from the Internet: <URL:http://www.minervanetworks.com/dvd_ solutions/Impression .html>, 3 pages. |
Hassel et al., “Electronic Program Guide With Digital Storage,” U.S. Appl. No. 09/157,256, filed Sep. 17, 1998, Incorporated by Reference in Ellis et al (US 200610136965), filed Sep. 21, 1998, 101 pages. |
Ellis et al., “Client Server Based Interactive Television Program Guide System for Remote Server Recorder,” U.S. Appl. No. 09/332,244, filed Jun. 11, 1999, Incorporated by Reference in Ellis et al (US 2006/0136965), 131 pages. |
Merriam Webster: “Personal”, [online], [retreived on Oct. 23, 2012], Retreived from the Internet: <https://www.merriam-webster.com/personal>, 2 pages. |
Dictionary.com: “Personal”[online], [retreived on Oct. 23, 2012], Retreived from the Internet: <http://dictionary.OAerence.com/browse/personal>, 3 pages. |
Cao, et al., “Method and System for Pausing and Replaying Scheduled Media Rich Broadcasts,” U.S. Appl. No. 09/585,707, filed May 31, 2000, Specification, Claims, Abstract, and Drawings, 32 pages. |
Cao, et al., Method and System for Recording Scheduled Programs Without Local Recording Equipment , U.S. Appl. No. 09/586,247, filed May 31, 2000, Specification, Claims, Abstract, and Drawings. |
Number | Date | Country | |
---|---|---|---|
20170257652 A1 | Sep 2017 | US |
Number | Date | Country | |
---|---|---|---|
61621462 | Apr 2012 | US | |
61621464 | Apr 2012 | US | |
62336505 | May 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13857994 | Apr 2013 | US |
Child | 15731249 | US | |
Parent | 13857995 | Apr 2013 | US |
Child | 13857994 | US |