Systems and methods for routing and redirecting keystroke commands received from a remote control device are disclosed.
Increasingly, video entertainment, such as movies and television shows, is delivered to users on demand over digital networks. In addition, the distribution of content has expanded to include user devices, such as smartphones. These user devices have the ability to interface with content delivery systems and to output video and other content to users and various output devices. However, because of the need for mobility, the output capabilities of user devices are necessarily limited. Therefore, it is desirable to direct content streams associated with a user device to televisions or home theater systems.
In many hospitality settings, there is a desire to provide entertainment services to guests using applications and devices that are familiar to guests. However, making such entertainment services, such as Netflix®, available to guests while maintaining security and implementing device isolation has proved to be difficult. Moreover, there is often a desire to utilize components familiar to guests and further to implement such components in a commercial off-the-shelf configuration, where existing components are utilized in various hospitality settings and configurations. However, as access and control of media content displayed in hospitality settings becomes more of a combination of user-provided devices and content and hospitality operator-provided devices and content, there becomes a need to provide configurations where such devices operate together in a cohesive manner.
Embodiments of the present disclosure are directed to systems and methods for receiving a key, or command, from a remote-control device and redirecting the received key, or command, to a system network controller. Within the context of a hospitality environment, where a guest room may include an output device, such as a television, and local player capable of supporting one or more streaming protocols, a system network controller may receive a first key value from a remote-control device or other device, and change the value of the key so that an application executing on the local player associated with an output device correctly registers the value, or meaning, of the received key. More specifically, and as a first non-limiting example, pressing an INFO button on a remote control may cause the remote control to send a key or command representative of the INFO button. A device generally associated with the remote control, such as a television, may receive the key or command representative of the INFO button and cause an information screen to be displayed at the television. However, where the remote is also to be used to control a local player for example, the local player may not have the necessary mapping to receive the specific key or command and cause an appropriate action to be performed.
For example, the local player, if capable, may receive the key or command associated with the INFO button; however, if an appropriate mapping is not established, the local player may not respond accordingly. Moreover, in instances where the communication medium of the remote control is incompatible with the local player, the local player cannot receive the key or command. In accordance embodiments of the present disclosure, the key or command may be redirected to a device that is compatible with the local player. Thus, the key or command representative of the INFO button for example, may change from a first value/character to a second value/character, such as a “?” or other character, by the system network controller so that the key can be natively digested by an application running on the local player. An up arrow may still be the equivalent of an up arrow, but might have a different representation code.
In accordance with an embodiment of the present disclosure, a method for routing key commands received from a remote-control device is provided. The method may include receiving, at a device, a key command from the remote-control device, generating a first message that includes the key command, sending, from the device, the first message to a keystroke router, and determining, at the keystroke router, a system network controller associated with the device. Moreover, the keystroke router may send the key command to the system network controller.
In accordance with another embodiment of the present disclosure, a communication system is provided. The communication system may include a local player, an output device configured to receive a key command from a remote-control device and to generate a first message that includes the key command, and a keystroke router configured to receive the first message from the output device, determine a system network controller associated with the output device, and send the key command to the system network controller.
In accordance with another embodiment of the present disclosure, a communication system is provided. The communication system may include a local player, a device configured to receive a key command from a remote-control device and to generate a first message that includes the key command, and a keystroke router configured to receive the first message from the output device, determine a system network controller associated with the output device, and send the key command to the system network controller.
Additional features and advantages of embodiments of the present disclosure will become more readily apparent from the following description, particularly when taken together with the accompanying drawings.
In some embodiments, the output device 112 may be in communication with a local player 124, such as a Chromecast device or other device capable of supporting one or more multimedia streaming sessions. The local player 124 may be connected to the output device 112 via an HDMI port. Power may be supplied to the local player 124 through a USB port associated with the output device 112. The USB port may be one that supplies power when the output device 112 is itself powered on, or can be configured to supply power continuously. In accordance with other embodiments, power may be supplied to the local player 124 through other means. For example, the local player 124 can be connected to a wall outlet providing power. Alternatively, or in addition, the local player 124 may reside within the output device 112. That is, the output device 112 may include the functionality of the local player 124. In accordance with embodiments of the present disclosure, the local player 124 may receive content, such as multimedia content, to be rendered or otherwise output to the output device 112 at the direction of the mobile device 110. Moreover, a pairing procedure may ensure security and sufficiently maintain device isolation such that the mobile device 110 is confined to or otherwise restricted from communicating with or accessing restricted hospitality devices and/or components that are inside and/or outside the guest room 104. That is, once paired, the mobile device 110 may communicate with authorized devices connected to the hospitality network. The local player 124, output device 112, and/or the mobile device 110 may be connected to a system network controller (SNC) 140 through a communication network 132 via a wireless access point 128. The SNC 140 may perform registration functions with respect to local players 124, output devices 112, mobile device 110, and other devices capable of providing content, such as multimedia content, to the output device 112. More particularly, the SNC 140 may maintain a table of information associating the local player 124 to the guest room 104, the mobile device 110 to the guest room 104, and/or the local player 124 to the mobile device 110.
In accordance with embodiments of the present disclosure, the system 100A may include various other devices and network nodes, located locally or remotely with respect to the output devices 112. For example, the local premises or hotel headend system 120 may be provided and may include the SNC 140 and a local area network switch, router, and/or Internet access core 136, which may be associated with a wireless or wireline (e.g., Ethernet) network or networks. As a further example, an application server 144 can be provided as part of the headend system 120 for hosting or otherwise making applications accessible to the local player 124. The headend system 120 may generally include a control center in an entertainment system where various signals are brought together and monitored before being introduced into the local entertainment network. The reference to headend system 120 is not limited to video entertainment providers, such as cable tv systems, but may also include various monitoring and control features associated with Internet access, wireless Internet access, output devices 112, local players 124, and other devices and services a guest of a hospitality establishment may use. Various other devices may be connected to the headend system 120 via the Internet 148. Examples of such systems include, but are not limited to, an application server 144B accessible by the local player 124.
An application on the local player 124 can be launched via a command from the SNC server 140 when the SNC server 140 detects that a local player 124 has powered up. A local player app or application, such as a default app at power up, communicates with the local SNC server 140 to get information regarding in what room and site the player app or application is installed. The information from the local SNC server 140 also contains the URL for an app, such as a second app, to launch. Once this information is retrieved, the currently executing app on the local player (the default app for instance) calls the specified URL and loads the requested application from a server. The URL for the requested application may point to the application server 144A, the application server 144B, the SNC 140 and/or another location having an accessible app, such as a receiver app, that runs on the local player 124. The SNC server 140 may use the room number and IP/MAC address of the user device 110 to create a pairing between the local player 124 in the guest room and the user device 110. In addition to providing convenient pairing of a user device 110 in the form of a smartphone, such embodiments also enable laptop computers, tablets, or other devices that may support casting through the chrome browser or other applications to an output device 112.
The local player 124 generally receives one or more commands from the guest mobile device 110 and/or the SNC 140; such commands may direct the local player 124 to one or more specific URLs or other locations where one or more receiver apps may be hosted. The local player 124 then renders, or executes, the receiver app located at the specified URL. In accordance with embodiments of the present disclosure, the local player 124 may be configured to render content consistent with one or more key commands from the guest remote-control 108. That is, both the mobile device 110 and the guest remote-control 108 may be used to control content accessed by the local player 124. Accordingly, and as depicted in at least
In accordance with at least one embodiment of the present disclosure, the guest mobile device 208 may run an application having the ability to route key codes over the network 132 to the Internet access core 136 and directly to the SNC 140. Alternatively, or in addition, the guest mobile device 208 may run an application having the ability to route key codes over the network 132 to the Internet access core 136 and out to an external server. Accordingly, an external server (RCI 160 for example) would send the key code to the SNC 140 in a manner previously discussed.
The keystroke router 152 may include data storage 612. In accordance with embodiments of the present invention, data storage 612 may contain program code or instructions 616 implementing various applications or functions executed by the keystroke router 152. Like the memory 608, the data storage 612 may comprise a solid-state memory device. In addition, in certain applications, the data storage 612 can be integrated with and/or indistinguishable from the memory 608. Alternatively, or in addition, the data storage 612 may comprise a hard disk drive or other random access memory and/or can be interconnected to the keystroke router 152, for example as network-attached storage. Programming or modules stored in the data storage and executed by the processor 604 may include, as examples and without limitation, keystroke routing associations 620. That is, the keystroke routing associations 620 may associate an originating (or sending) address (or identifier), such as an IP address (or other identifier) of the output device 112 or keystroke detector 106, to an SNC 140. For example, a table 632, or other data association structure, may include the originating (or sending) address (or identifier), such as an IP address (or other identifier) of the output device 112 or keystroke detector 106, and an SNC 140. Of course additional fields may be included in the table 632. The keystroke router 152 may also include one or more communication interfaces 624A-B. For example, a first communication interface 624A may provide a connection to a first communication network, such as network 132, while the second communication interface 624B may provide a connection to the output device 112 via the b-LAN 102. One or more components for the keystroke router 152 may be coupled to and/or communication with one another via the bus 628.
The keystroke detector 106 may include the same or similar components as the keystroke router 152. That is, the keystroke detector 106 may include a processor, memory, one or more communication interfaces, and/or data storage and/or associations associating a received key or command to a respective keystroke router 152.
The SNC 140 can also include data storage 712. In accordance with embodiments of the present invention, data storage 712 can contain program code or instructions implementing various applications or functions executed by the SNC server 140. Like the memory 708, the data storage 712 can comprise a solid-state memory device. In addition, in certain applications, the data storage 712 can be integrated with and/or indistinguishable from the memory 708. Alternatively, or in addition, the data storage 712 may comprise a hard disk drive or other random-access memory and/or can be interconnected to the SNC server 140, for example as network-attached storage. Programming or modules 716 stored in the data storage 712 and executed by the processor 704 can include, as examples and without limitation, one or more sender applications 720, and one or more keystroke/application associations 724. The one or more keystroke/application associations 724 may associate a keystroke to an application. For example, a table 736, or other data association structure, may include the originating key command, (or a key command received from a keystroke router), an identifier of the sending application, an identifier of a receiver application, and one or more transformed keys. Of course additional fields may be included in the table 736. The sender application 720 may allow the SNC 140 to direct the local player 124 to a specified location, such as a URL. Further, the SNC 140 sender application 720 may receive the keystroke from the keystroke router 152 and interact with a receiver application located at an application server 144 for example. Thus, the keystroke/application association 724 including instructions and associations ensure that a change associated with a keystroke received from a keystroke router 152 is reflected at the local player 112 and ultimately the output device 108.
The SNC server 140 may also include one or more communication interfaces 728A-B. For example, a first communication interface 728A may provide a connection to the first communication network 132 while a second communication interface 728B may provide a connection to a device virtual local area network (VLAN), such as one or more VLANs in which the local player 124 resides. One or more components fo the SNC server 140 may be coupled to one another via the bus 732.
In accordance with some embodiments, the value of the key received from the remote-control device may be changed. For example, an SNC 140 may receive a first key value from the remote-control device 108, output device 112, keystroke router 152, and/or keystroke detector 106/204 and change the value of the key so that the application executing on the local player 124 correctly registers the value, or meaning, of the received key. For example, if a remote control 108 has an INFO button, the key representative of the INFO button may change from a first value/character to a second value/character, such as a “?” or other character so that the key can be natively digested by an app. An up arrow may still be the equivalent of an up arrow, but might have a different representation code.
In accordance with an embodiment of the present disclosure, a method for routing key commands received from a remote-control device is provided. The method may include receiving, at a device, a key command from the remote-control device, generating a first message that includes the key command, sending, from the device, the first message to a keystroke router, and determining, at the keystroke router, a system network controller associated with the device. Moreover, the keystroke router may send the key command to the system network controller.
At least one aspect of the above embodiment may include where the keystroke router sends the key command to the system network controller. An additional aspect may include where the first message is communicated across a broadband local area network. At least one aspect of the above embodiment may include where the key command sent from the keystroke router to the system network controller is sent in a second message. An additional aspect of the may include where determining a system network controller associated with the device is based on one or more of information included in the first message and an association between the device and the determined system network controller. At least one aspect of the above embodiment may include providing, by the system network controller, a second message indicative of the key command received from the remote-control device, to an application associated with a local player. Yet, another aspect may include where the device is a keystroke detector. At least one aspect of the above embodiment may include providing, by the system network controller, a second message indicative of the key command received at the device, to an application associated with a local player. An additional aspect of the may include displaying, at an output device associated with the local player, an action indicative of the key command received at the device. At least one aspect of the above embodiment may include displaying, at the device, an action indicative of the key command received at the device.
In accordance with an embodiment of the present disclosure, a communication system is provided. The communication system may include a local player, an output device configured to receive a key command from a remote-control device and to generate a first message that includes the key command, and a keystroke router configured to receive the first message from the output device, determine a system network controller associated with the output device, and send the key command to the system network controller.
In accordance with at least one aspect of the above embodiment, the first message is communicated across a broadband local area network. In accordance with another aspect of the above embodiment, the system network controller is configured to receive the key command in a second message. Further still, the system network controller is configured to provide a second message indicative of the key command received from the remote-control device to an application associated with the local player. Moreover, the output device is configured to display an action indicative of the key command received at the device. In accordance with at least one aspect of the above embodiment, the keystroke router is configured to determine the system network controller associated with the output device based on one or more of information included in the first message and an association between the output device and the determined system network controller.
In accordance with an embodiment of the present disclosure, a communication system is provided. The communication system may include a local player, a device configured to receive a key command from a remote-control device and to generate a first message that includes the key command, and a keystroke router configured to receive the first message from the output device, determine a system network controller associated with the output device, and send the key command to the system network controller.
In accordance with at least one aspect of the above embodiment, the communication system may include an output device configured to display an action indicative of the key command received at the device. Further, the first message may be communicated across a broadband local area network. In accordance with at least one aspect, the system network controller is configured to provide a second message indicative of the key command received from the remote-control device to an application associated with the local player. At least one aspect includes where the keystroke router is configured to determine the system network controller associated with the device based on one or more of information included in the first message and an association between the output device and the determined system network controller.
Accordingly, the present invention has been described with some degree of particularity directed to the exemplary embodiments of the present invention. It should however be appreciated that modifications or changes may be made to the exemplary embodiments of the present invention without departing from the inventive concepts contained herein.
This application claims the benefit of U.S. patent application Ser. No. 15/853,221, filed Dec. 22, 2017, which claims priority to U.S. Provisional Patent Application Ser. No. 62/438,236, filed Dec. 22, 2016, the entire disclosures of which are each hereby incorporated herein by reference for all that it teaches and for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
4198870 | Barker et al. | Apr 1980 | A |
4564732 | Lancaster et al. | Jan 1986 | A |
5374952 | Flohr | Dec 1994 | A |
5455619 | Truckenmiller et al. | Oct 1995 | A |
5506572 | Hills et al. | Apr 1996 | A |
5641319 | Stoel et al. | Jun 1997 | A |
5675828 | Stoel et al. | Oct 1997 | A |
5905942 | Stoel et al. | May 1999 | A |
5907715 | Stoel et al. | May 1999 | A |
5990885 | Gopinath | Nov 1999 | A |
6226677 | Slemmer | May 2001 | B1 |
6240533 | Slemmer | May 2001 | B1 |
6343315 | Stoel et al. | Jan 2002 | B1 |
6377990 | Slemmer et al. | Apr 2002 | B1 |
6594692 | Reisman | Jul 2003 | B1 |
7251329 | Ikonen et al. | Jul 2007 | B2 |
7272844 | Bankers et al. | Sep 2007 | B1 |
7380031 | Jones et al. | May 2008 | B2 |
7444663 | Fenwick, Jr. et al. | Oct 2008 | B2 |
7895630 | McKenna et al. | Feb 2011 | B2 |
7930721 | Hernes | Apr 2011 | B1 |
7971782 | Shams | Jul 2011 | B1 |
8214429 | Chidel et al. | Jul 2012 | B2 |
8250612 | Kim et al. | Aug 2012 | B2 |
8272561 | Shin et al. | Sep 2012 | B2 |
8356251 | Strober | Jan 2013 | B2 |
8370879 | Zerr et al. | Feb 2013 | B2 |
8374127 | Woo et al. | Feb 2013 | B2 |
8434111 | Levy et al. | Apr 2013 | B2 |
8490127 | Vantalon et al. | Jul 2013 | B2 |
8539524 | Woo et al. | Sep 2013 | B2 |
8572662 | Cassidy et al. | Oct 2013 | B2 |
8578418 | Levy et al. | Nov 2013 | B2 |
8655345 | Gold | Feb 2014 | B2 |
8713612 | Levy et al. | Apr 2014 | B2 |
8732753 | Warrick | May 2014 | B2 |
8854195 | West et al. | Oct 2014 | B2 |
8855622 | Gold | Oct 2014 | B2 |
8903978 | Zerr et al. | Dec 2014 | B2 |
9003455 | Hulse et al. | Apr 2015 | B2 |
9032451 | Cansino et al. | May 2015 | B2 |
9060011 | Gold | Jun 2015 | B2 |
9060197 | Warick et al. | Jun 2015 | B2 |
9107055 | Zerr et al. | Aug 2015 | B2 |
9326095 | Yu et al. | Apr 2016 | B2 |
9369829 | Zerr et al. | Jun 2016 | B2 |
9602864 | Cholas et al. | Mar 2017 | B2 |
9787756 | Gold | Oct 2017 | B2 |
9854388 | Zerr et al. | Dec 2017 | B2 |
9942304 | Gold | Apr 2018 | B2 |
10244375 | Zerr et al. | Mar 2019 | B2 |
10291956 | Zdepski et al. | May 2019 | B2 |
10326823 | Gold | Jun 2019 | B2 |
10327035 | Zerr et al. | Jun 2019 | B2 |
10602212 | Zerr et al. | Mar 2020 | B2 |
10631042 | Zerr et al. | Apr 2020 | B2 |
10743075 | Zerr et al. | Aug 2020 | B2 |
20020052965 | Dowling | May 2002 | A1 |
20030071792 | Safadi | Apr 2003 | A1 |
20030090386 | Giraldin et al. | May 2003 | A1 |
20030202006 | Callway | Oct 2003 | A1 |
20030229900 | Reisman | Dec 2003 | A1 |
20040261110 | Kolbeck | Dec 2004 | A1 |
20050283791 | McCarthy et al. | Dec 2005 | A1 |
20060107299 | Bartfeld et al. | May 2006 | A1 |
20060117379 | Bennett et al. | Jun 2006 | A1 |
20060123053 | Scannell, Jr. | Jun 2006 | A1 |
20060153122 | Hinman et al. | Jul 2006 | A1 |
20060277312 | Hirsch | Dec 2006 | A1 |
20070080934 | Chen et al. | Apr 2007 | A1 |
20070155326 | Lin et al. | Jul 2007 | A1 |
20070157281 | Ellis et al. | Jul 2007 | A1 |
20080060081 | Van Den Heuvel | Mar 2008 | A1 |
20080130595 | Abdel-Kader | Jun 2008 | A1 |
20080141313 | Kato et al. | Jun 2008 | A1 |
20080151847 | Abujbara | Jun 2008 | A1 |
20080168129 | Robbin et al. | Jul 2008 | A1 |
20080207170 | Khetawat et al. | Aug 2008 | A1 |
20090007240 | Vantalon et al. | Jan 2009 | A1 |
20090083824 | McCarthy et al. | Mar 2009 | A1 |
20090102983 | Malone et al. | Apr 2009 | A1 |
20090125971 | Belz et al. | May 2009 | A1 |
20090144815 | Vrielink et al. | Jun 2009 | A1 |
20090158404 | Hahn et al. | Jun 2009 | A1 |
20090172780 | Sukeda et al. | Jul 2009 | A1 |
20090180614 | Rajagopal et al. | Jul 2009 | A1 |
20090320055 | Langille et al. | Dec 2009 | A1 |
20100058485 | Gonzalez et al. | Mar 2010 | A1 |
20100069115 | Liu | Mar 2010 | A1 |
20100070997 | Friedman | Mar 2010 | A1 |
20100145859 | Murakami et al. | Jun 2010 | A1 |
20100162294 | Yin et al. | Jun 2010 | A1 |
20100165879 | Gupta et al. | Jul 2010 | A1 |
20100176919 | Myers et al. | Jul 2010 | A1 |
20100278345 | Alsina et al. | Nov 2010 | A1 |
20100330979 | Harris | Dec 2010 | A1 |
20110099598 | Shin et al. | Apr 2011 | A1 |
20110116452 | Welch et al. | May 2011 | A1 |
20110167486 | Ayloo et al. | Jul 2011 | A1 |
20110244829 | Kase | Oct 2011 | A1 |
20110290893 | Steinberg | Dec 2011 | A1 |
20110295502 | Faenger | Dec 2011 | A1 |
20110302607 | Warrick et al. | Dec 2011 | A1 |
20110314497 | Warrick et al. | Dec 2011 | A1 |
20120027374 | Lipkind | Feb 2012 | A1 |
20120072951 | King | Mar 2012 | A1 |
20120075538 | Okuda | Mar 2012 | A1 |
20120096503 | Slothouber et al. | Apr 2012 | A1 |
20120159472 | Hong et al. | Jun 2012 | A1 |
20120159538 | Phillips et al. | Jun 2012 | A1 |
20120166628 | Kullos | Jun 2012 | A1 |
20120166655 | Maddali et al. | Jun 2012 | A1 |
20120243444 | Hillier et al. | Sep 2012 | A1 |
20120249890 | Chardon et al. | Oct 2012 | A1 |
20120260268 | Mirkin | Oct 2012 | A1 |
20120272147 | Strober | Oct 2012 | A1 |
20130051237 | Ong | Feb 2013 | A1 |
20130081093 | Cassidy et al. | Mar 2013 | A1 |
20130091309 | Bjontegard et al. | Apr 2013 | A1 |
20130097286 | Robbin et al. | Apr 2013 | A1 |
20130124759 | Strober | May 2013 | A1 |
20130142181 | Makim et al. | Jun 2013 | A1 |
20130239199 | Ong | Sep 2013 | A1 |
20130297723 | Iwaniszyn | Nov 2013 | A1 |
20130298020 | Stoikos | Nov 2013 | A1 |
20130305320 | Warrick et al. | Nov 2013 | A1 |
20130305341 | Baker et al. | Nov 2013 | A1 |
20130339533 | Neerinex et al. | Dec 2013 | A1 |
20130339865 | Oslund et al. | Dec 2013 | A1 |
20130346564 | Warrick et al. | Dec 2013 | A1 |
20130346808 | Gyorffy | Dec 2013 | A1 |
20130347028 | Warrick et al. | Dec 2013 | A1 |
20140006474 | White et al. | Jan 2014 | A1 |
20140026162 | Cassidy et al. | Jan 2014 | A1 |
20140051362 | Ding | Feb 2014 | A1 |
20140053246 | Huang et al. | Feb 2014 | A1 |
20140053282 | Court | Feb 2014 | A1 |
20140067828 | Archibong et al. | Mar 2014 | A1 |
20140089524 | Carriere | Mar 2014 | A1 |
20140090030 | Ong | Mar 2014 | A1 |
20140114919 | Woods | Apr 2014 | A1 |
20140143380 | Warrick et al. | May 2014 | A1 |
20140150031 | Kumar et al. | May 2014 | A1 |
20140189758 | Kozlowski | Jul 2014 | A1 |
20140189759 | Warrick et al. | Jul 2014 | A1 |
20140245395 | Hulse et al. | Aug 2014 | A1 |
20140250460 | Hulse et al. | Sep 2014 | A1 |
20140250470 | Warrick | Sep 2014 | A1 |
20140282751 | Lee et al. | Sep 2014 | A1 |
20140282921 | Filman et al. | Sep 2014 | A1 |
20140289410 | Smith et al. | Sep 2014 | A1 |
20140304722 | Ostlund | Oct 2014 | A1 |
20140331135 | Sukoff et al. | Nov 2014 | A1 |
20140347181 | Luna et al. | Nov 2014 | A1 |
20150089222 | White et al. | Mar 2015 | A1 |
20150147972 | Motto | May 2015 | A1 |
20150254726 | Cassidy et al. | Sep 2015 | A1 |
20150334245 | Lin et al. | Nov 2015 | A1 |
20150339274 | Pappu et al. | Nov 2015 | A1 |
20150350690 | Zerr et al. | Dec 2015 | A1 |
20150365512 | MacKenzi et al. | Dec 2015 | A1 |
20150373123 | Warrick et al. | Dec 2015 | A1 |
20150373401 | Kwon et al. | Dec 2015 | A1 |
20150382195 | Grim et al. | Dec 2015 | A1 |
20160027399 | Wilde et al. | Jan 2016 | A1 |
20160073440 | Palten et al. | Mar 2016 | A1 |
20160192191 | Lee et al. | Jun 2016 | A1 |
20160249158 | Tredoux et al. | Aug 2016 | A1 |
20160285877 | Anderson et al. | Sep 2016 | A1 |
20160323433 | Anderson et al. | Nov 2016 | A1 |
20170206593 | Zolotov | Jul 2017 | A1 |
20170229009 | Foster et al. | Aug 2017 | A1 |
20180121150 | Lin et al. | May 2018 | A1 |
20190297134 | Gold | Sep 2019 | A1 |
20200228863 | Zerr et al. | Jul 2020 | A1 |
Number | Date | Country |
---|---|---|
2788573 | Nov 2012 | CA |
2790354 | Mar 2013 | CA |
2817932 | Dec 2013 | CA |
2820654 | Dec 2013 | CA |
203590374 | May 2014 | CN |
0094839 | Nov 1983 | EP |
WO 2007002604 | Jan 2007 | WO |
WO 2009137247 | Nov 2009 | WO |
WO 2012145227 | Oct 2012 | WO |
Entry |
---|
U.S. Appl. No. 13/243,491, filed Sep. 23, 2011 now U.S. Pat. No. 9,107,055. |
U.S. Appl. No. 13/488,809, filed Jun. 5, 2012 now U.S. Pat. No. 8,903,978. |
U.S. Appl. No. 14/486,888, filed Sep. 15, 2014 now U.S. Pat. No. 9,369,829. |
U.S. Appl. No. 15/152,243, filed May 11, 2016 now U.S. Pat. No. 9,854,388. |
U.S. Appl. No. 15/812,652, filed Nov. 14, 2017 now U.S. Pat. No. 10,244,375. |
U.S. Appl. No. 14/503,858, filed Oct. 1, 2014. |
U.S. Appl. No. 14/728,831, filed Jun. 2, 2015. |
U.S. Appl. No. 15/144,492, filed May 2, 2016. |
U.S. Appl. No. 15/082,064, filed Mar. 28, 2016. |
U.S. Appl. No. 15/282,556, filed Sep. 30, 2016 now U.S. Pat. No. 10,631,042. |
U.S. Appl. No. 15/282,676, filed Sep. 30, 2016 now U.S. Pat. No. 10,291,956. |
U.S. Appl. No. 16/828,660, filed Mar. 24, 2020. |
U.S. Appl. No. 15/459,394, filed Mar. 15, 2017 now U.S. Pat. No. 10,327,035. |
U.S. Appl. No. 16/418,763, filed May 21, 2019 now U.S. Pat. No. 10,743,075. |
U.S. Appl. No. 16/912,817, filed Jun. 26, 2020. |
U.S. Appl. No. 15/853,221, filed Dec. 22, 2017 now U.S. Pat. No. 10,602,212. |
“Commercial Requirements for Companion Screen in the DVB-GEM Specification,” DVB Organization, Apr. 2013, Version R 6.9.1, 40 pages. |
“Dial Discovery and Launch protocol specification,” Netflix, Inc., 2012, Version 1.6.4, 16 pages. |
“DIAL: DIscovery And Launch protocol specification,” Netflix, Inc., 2014, Version 1.7.2, 30 pages. |
“Specification of the Bluetooth® System Version 4.2. Manual,” Bluetooth SIG, Inc., Dec. 2014, 40 pages [retrieved on May 21, 2016 from https://www.bluetooth.com/specifications/adopted-specifications]. |
Erman et al. “Over the Top Video: The Gorilla in the Cellular Networks,” IMC11, Nov. 24, 2011 [retrieved from the internet May 9, 2017 from URL: www.cs.columbia.edu/˜lierranli/coms6998-7Spring2014/papers/videocellular_imc2011.pdf]. |
Montpetit et al. “IPTV: An End to End Perspective,” Journal of Communications, May 2010, vol. 5, No. 5, pp. 358-373. |
Xia et al. “A Survey on Software-Defined Networking,” IEEE Communication Surveys & Tutorials, First Quarter 2015, vol. 17, No. 1, pp. 27-51. |
International Search Report and Written Opinion for International (PCT) Patent Application No. PCT/US2016/030437, dated Sep. 7, 2016, 12 pages. |
International Preliminary Report on Patentability for International (PCT) Patent Application No. PCT/US2016/030437, dated Nov. 16, 2017 9 pages. |
Official Action for Canada Patent Application No. 2,983,161, dated Aug. 13, 2018 3 pages. |
Extended Search Report for European Patent Application No. 16789899.8, dated Sep. 28, 2018 7 pages. |
International Search Report and Written Opinion for International (PCT) Patent Application No. PCT/US17/68339, dated Mar. 26, 2018 8 pages. |
International Preliminary Report on Patentability for International (PCT) Patent Application No. PCT/US2017/068339, dated Jun. 25, 2019 6 pages. |
Official Action for U.S. Appl. No. 14/728,831, dated Feb. 25, 2016, 15 pages. |
Official Action for U.S. Appl. No. 14/728,831, dated Oct. 6, 2016, 15 pages 15 pages. |
Official Action for U.S. Appl. No. 14/728,831, dated Jul. 12, 2017, 19 pages. |
Official Action for U.S. Appl. No. 14/728,831, dated Feb. 22, 2018 20 pages. |
Official Action for U.S. Appl. No. 14/728,831, dated Dec. 28, 2018 21 pages. |
Official Action with U.S. Appl. No. 15/853,221, dated Sep. 5, 2018 8 pages. |
Official Action for U.S. Appl. No. 15/853,221, dated Feb. 14, 2019 9 pages. |
Official Action for U.S. Appl. No. 15/853,221, dated Jun. 10, 2019 10 pages. |
Notice of Allowance for U.S. Appl. No. 15/853,221, dated Nov. 4, 2019, 9 pages. |
Extended Search Report for European Patent Application No. 17884682.0, dated Jun. 19, 2020 7 pages. |
Number | Date | Country | |
---|---|---|---|
20200228858 A1 | Jul 2020 | US |
Number | Date | Country | |
---|---|---|---|
62438236 | Dec 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15853221 | Dec 2017 | US |
Child | 16781238 | US |