WO2024242671A1

WO2024242671A1 - Method and apparatus for extremely low-power standby and cast-based wakeup for display devices

Info

Publication number: WO2024242671A1
Application number: PCT/US2023/023198
Authority: WO
Inventors: Gaurav Arora
Original assignee: Google LLC
Current assignee: Google LLC
Priority date: 2023-05-23
Filing date: 2023-05-23
Publication date: 2024-11-28
Anticipated expiration: 2025-11-23

Abstract

Apparatuses, systems, methods, and machine-readable media to present content may provide for extremely low-power standby and cast-based wakeup for display devices. A wake-on-cast functionality of a media playback device may be offloaded from the media playback device to a media casting device. The offloading the wake-on-cast functionality may allow the media playback device to transition from a default power state to a lower power state while the wake-on-cast functionality is preserved by the media casting device. While the media playback device is in the lower power state, a communication from a computing device may be received by the media casting device. Responsive to the communication, the media casting device may wake the media playback device from the lower power state to cause the media playback device to return to the default power state.

Description

METHOD AND APPARATUS FOR EXTREMELY LOW-POWER STANDBY AND CAST-BASED WAKEUP FOR DISPLAY DEVICES

TECHNICAL FIELD

[0001] Disclosed embodiments according to the present disclosure relate generally to presenting media content, and in particular to apparatuses, systems, methods, and computer-readable media for extremely low-power standby and cast-based wakeup for display devices.

BACKGROUND

[0002] With the ubiquity of display devices around the world, a great deal of power is consumed. There is a drive for responsible use and conservation of power as new technologies are developed. At the same time, while there is a need for avoiding power wastage, there is also a drive for providing new features for improved user experiences with display devices. The need for avoiding power wastage must be balanced with the need for providing better user experiences.

[0003] There is a need for apparatuses, systems, methods, and computer-readable media that address such issues. This and other needs are addressed by the present disclosure.

BRIEF SUMMARY

[0004] Certain embodiments according to the present disclosure relate generally to presenting media content, and in particular to apparatuses, systems, methods, and computer-readable media for extremely low-power standby and cast-based wakeup for display devices.

[0005] In one aspect, a system to present content is disclosed. The system may include one or more processing devices and memory communicatively coupled with and readable by the one or more processing devices and having stored therein machine-readable instructions which, when executed by the one or more processing devices, cause the one or more processing devices to perform one or a combination of the following operations. A wake-on-cast functionality of a media playback device may be offloaded from the media playback device to a media casting device. The offloading the wake-on-cast functionality may allow the media playback device to transition from a default power state to a lower power state while the wake-on-cast functionality is preserved by the media casting device. While the media playback device is in the lower power state, a communication from a computing device may be received by the media casting device. Responsive to the communication, the media casting device may wake the media playback device from the lower power state to cause the media playback device to return to the default power state.

[0006] In another aspect, one or more non-transitory, machine-readable media are disclosed. The one or more non-transitory, machine-readable media may have machine-readable instructions thereon which, when executed by one or more processing devices, cause the one or more processing devices to perform one or a combination of the following operations. A wake-on-cast functionality of a media playback device may be offloaded from the media playback device to a media casting device. The offloading the wake-on-cast functionality may allow the media playback device to transition from a default power state to a lower power state while the wake-on- cast functionality is preserved by the media casting device. While the media playback device is in the lower power state, a communication from a computing device may be received by the media casting device. Responsive to the communication, the media casting device may wake the media playback device from the lower power state to cause the media playback device to return to the default power state.

[0007] In yet another aspect, a method to present content is disclosed. The method may include one or a combination of the following. A wake-on-cast functionality of a media playback device may be offloaded from the media playback device to a media casting device. The offloading the wake-on-cast functionality may allow the media playback device to transition from a default power state to a lower power state while the wake-on-cast functionality is preserved by the media casting device. While the media playback device is in the lower power state, a communication from a computing device may be received by the media casting device. Responsive to the communication, the media casting device may wake the media playback device from the lower power state to cause the media playback device to return to the default power state.

[0008] In various embodiments, responsive to the communication, the media casting device may cause the media playback device to begin playing content consequent to the waking. In various embodiments, the lower power state may correspond to a standby-passive state. In various embodiments, while the media playback device is in the lower power state, the media casting device may masquerade as the media playback device to the computing device. In various embodiments, the media casting device may discontinue masquerading as the media playback device to the computing device after the waking the media playback device. In various embodiments, the media casting device may communicate with the media playback device to facilitate addition of a menu option corresponding to the lower power state with wake-on-cast offloading. In various embodiments, prior to the offloading, the media casting device may determine whether the media playback device is capable of having the wake-on-cast functionality offloaded to the media casting device.

[0009] Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating various embodiments, are intended for purposes of illustration only and are not intended to necessarily limit the scope of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A further understanding of the nature and advantages of various embodiments may be realized by reference to the following figures. In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

[0011] FIG. 1 illustrates an example of a system for presenting media content in accordance with some implementations of disclosed embodiments.

[0012] FIG. 2 illustrates an example of a system for presenting media content in accordance with some implementations of disclosed embodiments.

[0013] FIG. 3 illustrates an example embodiment of a method to facilitate extremely low-power standby and cast-based wakeup to present content for a media playback device in accordance with some implementations of disclosed embodiments.

[0014] FIG. 4 illustrates an example of a generalized schematic diagram of a system on which the mechanisms for presenting content as described herein can be implemented in accordance with some implementations of the disclosed subject matter.

[0015] FIG. 5 illustrates an example of hardware that can be used to implement a computing device, a media receiving device, and a content delivery server depicted in FIG. 9 in accordance with some implementations of the disclosed subject matter.

DETAILED DESCRIPTION

[0016] The ensuing description provides preferred exemplary embodiment(s) only, and is not intended to limit the scope, applicability or configuration of the disclosure. Rather, the ensuing description of the preferred exemplary embodiment s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment of the disclosure. It should be understood that various changes may be made in the function and arrangement of elements without departing from the scope of the disclosure as set forth in the appended claims. Various embodiments will now be discussed in greater detail with reference to the accompanying figures, beginning with FIG. 1. [0017] FIGS. 1 and 2 illustrate an example of a system 100 for presenting media content in accordance with some implementations of disclosed embodiments. In some embodiments, the system 100 may include a media receiving and casting device 102 (“media casting device 102”). The media casting device 102 may include an input/output connector 104. The input/output connector 104 may be any suitable input and/or output connector for communicating with a media playback device 106. For example, the input/output connector 104 may be a High-Definition Multimedia Interface (HDMI) port, a Universal Serial Bus (USB) connector (e.g., a USB 3.0 connector), a THUNDERBOLT connector, a Digital Visual Interface (DVI) connector, a TOSLINK connector (e.g., a fiber optic audio connector), a Separate Video (S-Video) Connector, any other suitable connector and/or any suitable combination of connectors.

[0018] In some embodiments, the media playback device 106 may be a device that includes hardware and/or software for presenting media received from one or more sources of media content. For example, the media playback device 106 may include a television (TV) such as any panel TV, a smart television (which may be built on a proprietary operating system), a monitor, a set-top box or other streaming device, an audio video (AV) receiver, any other suitable the media playback device and/or any suitable combination thereof. More particularly, the media playback device 106 may include a display 108, speakers, hardware and/or software for rendering media content such as analog and/or digital video and/or audio data, a power supply, etc. The media playback device 106 may include various input ports for receiving video and/or audio data from various sources. Such input ports may include one or more HDMI ports, one or more component video ports, one or more composite video ports, one or more USB ports, one or more S-Video ports, one or more TOSLINK ports, one or more coaxial ports, one or more Ethernet ports (whether wired or wireless), etc.

[0019] In some embodiments, the media casting device 102 (e.g., Chromecast by Google Inc.) may be connected to the media playback device 106 by a connection 110. The media casting device 102 and the media playback device 106 may be connected using any suitable technique(s). For example, the connection 110 may include a plug of input/output connector 104 of the media casting device 102 inserted in a corresponding receptacle port of the media playback device 106. As another example, a suitable cable, such as an HDMI cable, may be connected between the input/output connector 104 and a port of the media playback device 106. In some embodiments, the media casting device 102 may correspond to a dongle-type structure. Additionally or alternatively, the media casting device 102 may be included as hardware and/or software of the media playback device 106. [0020] In some embodiments, the media casting device 102 may be coupled to a computing device 112 using a communication link 114. The computing device 112 may be any suitable computing device, such as a smartphone, a tablet computer, a wearable computer, a laptop computer, a personal computer, an electronic reader, a digital media receiver, a smart television, a game console, any other suitable computing device, or any suitable combination thereof. In some embodiments, the communication link 114 may include any suitable communication link, for example, as described below in connection with FIG. 4. Additionally, the communication link 114 may include a network, such as a local area network (LAN) having wired and/or wireless connections. Additionally or alternatively, the communication link 114 may include a wireless connection between computing device 112 and the media casting device 102, such as an ad hoc wireless network. In some embodiments, communications between the computing device 112 and the media casting device 102 over communication link may be encrypted using any suitable encryption technique(s). For example, messages sent from the computing device 112 to the media receiving device 114 may be encrypted using any suitable encryption scheme, for example, using a public key-private key pair for encryption and decryption of messages. As another example, communications over the communication link 114 may be encrypted using Transport Layer Security (TLS).

[0021] In some embodiments, the computing device 112 may include a display 116 for presenting a user interface to a user. In some examples, the computing device 112 may be a mobile computing device such as a smartphone or a tablet computer, and the display 116 may include a touchscreen for receiving input and displaying a user interface and/or media content to a user. In some embodiments, the computing device 112 may further include volume controls 118 for controlling a volume of the computing device 112.

[0022] In some embodiments, the computing device 112 may communicate with a content discovery server 121 over a communication link 122. The computing device 112 may be used to discover and/or browse content made available by a content delivery server 120. For example, a user may use the computing device 112 to find media content to be presented. In some embodiments, such media content may be presented using the display 116 of the computing device 112. In some embodiments, the computing device 112 may present a media content item that was selected using the content discovery server 121, by requesting the media content item from the content delivery server 120 and receiving the media content item over a communication link 123. In some embodiments, each of the content delivery server 120 and/or the content discovery server 121 may be implemented on any suitable number and type of servers. Additionally or alternatively, in some embodiments, the functions performed by the content delivery server 120 and the content discovery server 121 may be performed by the same device (e.g., by a common server computer).

[0023] In some embodiments, the communication links 122 and/or 123 may include a local area network (e.g., a home network) and/or a non-local network (e.g., the Internet). For example, the computing device 112 may be connected to a common LAN such as a home network and may connect to the content discovery server 121 and/or the content delivery server 120 through the Internet. As another example, the content delivery server 120 and/or the content discovery server 121 may be connected to a LAN that is common to the computing device 112. In a more particular example, the content delivery server 120 and/or the content discovery server 121 may be located remotely from the computing device 112, and the communication links 122 and/or 123 may include a non-local network such as the Internet for accessing content from the content delivery server 120 and/or discovering content using the content discovery server 121. In another more particular example, the content delivery server 120 and/or the content discovery server 121 may be located locally to the computing device 112, and the communication links 122 and/or 123 may include a local network, such as a home network, to which the content delivery server 120 and/or the content discovery server 121 are connected. In such an example, a non-local network of the communication links 122 and/or 123 (if it exists) may not be used when accessing content from the content delivery server 120 and/or discovering content using the content discovery server 121.

[0024] In some embodiments, a user of the computing device 112 may cause media content made available by the content delivery server 120 to be transmitted to the media casting device 102, which may in turn cause the media content to be presented on the display 108 of the media playback device 106 to which the media casting device 102 is connected. In some embodiments, the media casting device 102 may receive power from the media playback device 106 through connection 110 (e.g., when a port to which the media casting device 102 is connected is selected as an active input port). For example, the media casting device 102 may receive power through its HDMI connection. The media casting device 102 may correspond to any suitable casting device configured to provide features disclosed herein, that has lower power consumption than the media playback device 106, and may remain on when the media playback device 106 is in passivestandby mode (i.e., the mode corresponding to the lowest power state, which may also be referenced as standby-passive mode). When the media casting device 102 is connected to the media playback device 106, the media casting device 102 may always be in on state and never turned off. In some embodiments, the media casting device 102 may not have an off button. In some embodiments, if a user has selected a media content item to be presented from the content delivery server 120, the user may select an icon presented to the user in connection with the selected media content item to cause the media content item to be presented using the media casting device 102.

[0025] In some embodiments, when a media content item is to be presented from the content delivery server 120 using the media casting device 102, the media content item may be transmitted to the media casting device 102 over a communication link 124. The communication link 124 may include a local area network (e.g., a home network) and/or a non-local network (e.g., the Internet). For example, the media casting device 102 and the computing device 112 may both be connected to a common LAN such as a home network and may connect to the content delivery server 120 through the Internet. As another example, the content delivery server 120 may be connected to a LAN that is common to the computing device 112 and/or the media casting device 102. In a more particular example, the content delivery server 120 may be located remotely from the media casting device 102 and/or the computing device 112, and communication link 124 may include a non-local network such as the Internet for accessing content from the content delivery server 120. In another more particular example, the content delivery server may be located locally to the media casting device 102 and/or the computing device 112, and the communication link 124 may include a local network, such as a home network, to which both the media casting device 102 and the content delivery server 120 are connected. In such an example, a non-local network of communication link 124 (if it exists) may not be used when accessing content from the content delivery server 120.

[0026] In some embodiments, a user may choose a media content item to be presented using the media casting device 102 from a memory of the computing device 112 (e.g., the user may choose a video that is stored locally on the computing device 112). Additionally or alternatively, a user may choose a media content item to be presented using the media casting device 102 that is stored on another computing device present on the same local area network (e.g., network attached storage, a memory of a personal computer on a home network, memory on a server on the same network, etc.). Such a media content item stored on a computing device connected to a local area network may be transmitted from the computing device 112 to the media casting device 102 over the communication link 114 (or any other suitable communication link), without being transmitted through the content delivery server 120.

[0027] To facilitate the casting features provided by the system 100, the computing device 112 may be configured with one or more applications to allow for selective casting of content to the media playback device 106 via the media casting device 102. The one or more applications may provide one or more user-selectable interface options 119 (e.g., one or more soft buttons on a touch screen of the computing device 112 that correspond to a cast option) to allow for casting of content to the media playback device 106. A user of the mobile computing device 112 may be playing content on the computing device 112 and then may select the one or more user-selectable interface options 119 to transition content play to the media playback device 106 (e.g., as illustrated in FIG. 2).

[0028] In various embodiments, the content may be cast to the media playback device 106 so that the content continues to be played on the media playback device 106 from a point in the presentation of the content corresponding to when the one or more user-selectable interface options 119 are selected, or from earlier in the presentation (e.g., 30 seconds before that point, the previous scene, etc.). Alternatively, the one or more user-selectable interface options 119 may be presented and selected so that content is cast to the media playback device 106 even if no content is currently being displayed on the mobile computing device 112. If the media playback device 106 is already running when casting is initiated, then the cast operations may be performed seamlessly because the hardware and software of the media playback device 106 are already running. The media playback device 106 may receive one or more signals, which may be received from the media casting device 102, and the media playback device 106 may start pulling the content from the cloud, decoding the content, and playing the content.

[0029] Media playback devices 106 be configured to have multiple power modes. The multiple power modes may include an active play/on mode and multiple low-power modes. Conventional media playback devices 106 may not maintain a true low-power mode while being ready to provide one or more functionalities, but instead may consume more power (e.g., approximately 2-4 watts (W) of consumption) than that which would correspond to a true low-power mode (e.g., passive-standby). For example, an unused TV plugged into the wall would still consume and waste that power.

[0030] Networked devices like panel TVs may tend to have a high active-standby state power consumption (e.g., it may tend to be 2+ W and, in some cases, as high as 20 W), especially if they must keep features like wake-on-cast enabled in standby states (e.g., when the screen is off). Most TVs may not support an extremely low power mode and still provide casting in that low-power state. TVs may go into an extremely low-power state if features like wake-on-cast are not enabled. This state may be called passive-standby and may correspond to power consumption of less than 0.5 W (e.g., 700 mW). For example, when a TV goes into passive-standby state, it loses the functionality of being able to be awakened via a mobile phone such that the TV could only be manually turned on with a remote or a power button the TV. With sustainability requirements and goals, when a device is not used, it desirable for the device to consume the least amount of leakage power possible so that power is not wasted. Yet, it also desirable that, when the device is wanted to be used, it always available.

[0031] In accordance with disclosed embodiments, even when the media playback device 106 is off, a desirable user experience may still be provided such that, with the touch of a cast button (e.g., user-selectable interface option 119) on the computing device 112, the media playback device 106 is turned on and the content is displayed on the media playback device 106. When the media playback device 106 is in a true low-power mode, the media casting device 102 may enable the media playback device 106 to have a fast wakeup functionality. Accordingly, features to wake the media playback device 106 and allow for casting may be provided (i.e., wake-on-cast features). The wake-on-cast features in accordance with disclosed embodiments may be important for consumers as it allows them to seamlessly cast media for viewing on media playback devices 106 from their computing devices 112, even when a media playback device 106 is in an off state (e.g., the lowest power state corresponding to passive-standby mode).

[0032] The media casting devices 102 may be configured to have much lower idle power consumption (e.g., 0.5 W or less) relative to media playback devices 106, such as panel TVs. For example, media casting devices 102 may be configured with SoCs that are mobile-grade chipsets and may have smaller and more efficient electronics than TVs. In accordance with disclosed embodiments, a media playback device 106 may delegate waking up on cast while the media playback device 106 is in its lowest power mode (passive-standby) to the media casting device 102, which may be configured to have an even lower power consumption (e.g., approximately 200-300 mW). Accordingly, power consumption in standby state is reduced for media playback devices 106 while still maintaining the wake-on-cast functionality, which is a win-win for consumers and product sustainability goals. The net power consumption may drop from 2-20 W to 1 W or less, with the functionality of wake-on-cast still provided. At scale, considering millions of media playback devices 106 around the world, the power savings may be quite significant, with the global power savings being roughly comparable to the power saving of taking a million or more cars off the road per year.

[0033] FIG. 3 illustrates an example embodiment of a method 300 to facilitate extremely low- power standby and cast-based wakeup to present content for a media playback device 106, in accordance with embodiments disclosed herein. However, teachings of the present disclosure may be implemented in a variety of configurations. As such, the order of the steps comprising the method 300 and/or other methods, processes, and operations disclosed herein may be shuffled or combined in any suitable manner and may depend on the implementation chosen. Moreover, while the steps disclosed herein may be separated for the sake of description, it should be understood that certain steps may be performed simultaneously or substantially simultaneously.

[0034] In some embodiments, the method 300 may begin with establishing communications connections between the media casting device 102 and the media playback device 106, as indicated by block 302. The media casting device 102 may initially connect to the media playback device 106 via a plug of input/output connector 104 of the media casting device 102 inserted in a corresponding receptacle port of the media playback device 106. The communication link 110 may be established.

[0035] As indicated by block 304, credentials information of the media playback device 106 may be determined by the media casting device 102. To configure the media casting device 102 to facilitate passive standby with cast offload, the media casting device 102 may obtain the cast address of the media playback device 106 so that the media casting device 102 may masquerade as a cast-receiver with media playback device 106 credentials. When the media casting device 102 is initially connected to the media playback device 106, the media casting device 102 may communicate with the media playback device 106 to obtain one or more identifiers and/or other descriptors for the media playback device 106. For example, the media casting device 102 may read the make and model identifiers/descriptors using the HDMI Extended Display Identification Data (ED ID) field for the media playback device 106. Additionally or alternatively, the media casting device 102 may pull credentials information from the media playback device 106 using an out-of-band communication protocol (e.g., via a consumer electronics control (CEC) command, via the cloud, or via LAN through BLE, Wi-Fi or Thread/Matter). The credentials information may include any suitable identifiers and/or descriptors for the media playback device 106, including, for example, one or a combination of alphanumeric strings, some other data structure, make, model, device serial number, cast address, IP address, MAC address, nickname, location, and/or the like.

[0036] As indicated by block 306, capabilities of the media playback device 106 may be determined by the media casting device 102. When the media casting device 102 is initially connected to the media playback device 106, the media casting device 102 may communicate with the media playback device 106 to identify capabilities of the media playback device 106. Such communications may be a part of the communications described above with respect to block 304 such that credentials information and capabilities information are exchanged. For example, at the initial handshake, the media casting device 102 may communicate to the media playback device 106 that the media casting device 102 is capable of receiving an offload of wake-on-cast to allow the media playback device 106 to go into deep sleep.

[0037] In some embodiments, the determination may be based at least in part on a whitelist of media playback devices 106 that the media casting device 102 can access for media playback devices 106 that have been tested to provide the wake-on-cast functionality to the media casting device 102. Using the credentials information obtained, the media casting device 102 may determine from the whitelist that the particular media playback device 106 is capable of offloading the wake-on-cast functionality to the media casting device 102. Additionally or alternatively, the media playback device 106 may communicate indication to the media casting device 102 that the media playback device 106 is capable of offloading the wake-on-cast functionality to the media casting device 102. Accordingly, the media casting device 102 may determine that it can offload wake-on-cast functionality from the media playback device 106 so the media playback device 106 could default to a lower power state (i.e., passive-standby state).

[0038] As indicated by block 308, the media casting device 102 may facilitate in addition of a menu option for the media playback device 106 that corresponds to a lower power state with wake-on-cast offloading. The media casting device may communicate with the media playback device 106 to cause the media playback device 106 to offer users another user-selectable option 130 in a menu 131 for standby modes: the media playback device 106 can go into a lowest-power state (passive standby) but still offer wake-on-cast by offloading this feature to the plugged-in media casting device 102. This mode may, for example, be referenced as passive standby with cast offload.

[0039] The option 130 for passive standby with cast offload may be additional to other menu choices corresponding to when the media playback device 106 stays in active standby mode, consuming more power but providing wake-on-cast, or to when the media playback device 106 goes into passive standby mode, saving power but not providing wake-on-cast. Passive standby with cast offload may provide the wake-on-cast user experience with less power. In some embodiments, the media playback device 106 may be configured to provide the passive standby with cast offload by default. In some embodiments, when the media playback device 106 is configured to provide the passive standby with cast offload by default or via user selection, the media playback device 106 may communicate to the media casting device 102 to indicate that the media playback device 106 is configured to provide the passive standby with cast offload. [0040] As indicated by block 310, the wake-on-cast functionality of the media playback device 106 may be offloaded from the media playback device 106 to the media casting device 102 so that the media playback device 106 may shift into a lower power state. There may be a handshake between the media casting device 102 and the media playback device 106 when the media playback device 106 goes into passive standby, as there may likewise be a handshake between the media casting device 102 and the media playback device 106 when the media playback device 106 later out a passive standby. The media playback device 106 may communicate to the media casting device 102 to indicate that the media playback device 106 is transferring the wake-on-cast capability to the media casting device 102 and/or is transitioning to passive standby. In some embodiments, the media playback device 106 may communicate its identifier (ID) or other credentials information to the media casting device 102 as part of the offloading. Such a transfer may be specified only for limited time, for example, only while the media playback device 106 is in deep standby, only until midnight when the media playback device 106 is to be awakened, only until the particular user-initiated event occurs, only until a government-triggered communication is received, and in /or the like.

[0041] In other embodiments, the media playback device 106 may communicate its ID to the media casting device 102 as part of the offloading, instead relying on the previously transferred credentials information. Thus, the ID transfer could be a one-time transfer when the media casting device 102 is initially plugged into the media playback device 106 one the media casting device 102 syncs to the address and/or other credentials (and can re-sync if plugged into a different device later). Then, when the media playback device 106 transitions into deep sleep/passive standby, the media playback device 106 may just indicate the state transition to the media casting device 102 that the media playback device 106 is now going into passive standby.

[0042] In some embodiments, other types of wake functionalities may be likewise transferred to the media casting device 102. The media playback device 106 may request via the descriptor wake-up upon other events. For example, the media playback device 106 may request wake-up at midnight so the media playback device 106 can communicate with the server to perform checks, upload data, receive software updates, etc. As another example, the media playback device 106 may be made use of as a primary communication device for governmental authorities to provide governmental communications to citizens. The media casting device 102 may be configured to receive government information, public announcements, emergency alert messages, and/or the like that may be sent over IP networks. Upon reception of such communications, the media casting device 102 may be configured to wake the media playback device 106 and cause presentation of corresponding content as disclosed herein. [0043] As indicated by block 312, the media playback device 106 may transition from its current power state to a lower power state while the wake-on-cast functionality is preserved by the media casting device 102. As indicated by block 314, while the media playback device 106 is in the lower power state, the media casting device 102 may masquerade as the media playback device 106. In some embodiments, the media casting device 102 may masquerade as the media playback device 106 with at least some of the media playback device 106 credentials (e.g., a TV ID). The media casting device 102 may respond to any inquiry that would otherwise have been directed to the media playback device 106.

[0044] As indicated by block 316, in some embodiments, the computing device 112 may identify the media casting device 102 as the media playback device 106. The computing device 112, configured as a cast-source device, may be configured to scan the network, querying the networked devices to determine which of the devices are capable of cast as a cast receiver. Responsive to the query, networked devices (media playback devices 106) may identify their ability to receive cast and may provide their ID. Thus, the media casting device 102, masquerading as the media playback device 106, may respond to the computing device 112, indicating that the media playback device 106 is available to play. The computing device 112 may display a list of cast devices, and the media casting device 102, masquerading as the media playback device 106, may be indicated on the list of potential cast-receivers. In some embodiments, the computer device 112 may display one or more user-selectable interface options to select the media casting device 102, masquerading as the media playback device 106, as a cast receiver. In some embodiments, the computer device 112 may select the media casting device 102, masquerading as the media playback device 106, as a cast receiver by default without user selection, for example, when it is so preconfigured, when there is only one potential cast receiver devices, etc.

[0045] As indicated by block 318, in some embodiments, while the media playback device 106 is in the lower power state, the computing device 112 may receive one or more communications directly or indirectly from the computing device 112. A user may have selected a cast button 119 on the computing device 112 and/or another option corresponding to selecting as a cast receiver the media casting device 102 masquerading with the media playback device 106 ID displayed on the competing device 112, and the computing device 112 may consequently initiate casting to the media playback device 106. In some embodiments, this may correspond to communicating via the network to the content delivery server 120, which may then communicate with the media casting device 102. In some embodiments, this may correspond to communicating via the network or otherwise directly to the media casting device 102. [0046] As indicated by block 320, the media casting device 102 may wake the media playback device 106 from the lower power state to cause the media playback device 106 to return to the default power state and to begin playing content. In some embodiments, this may be responsive to the one or more communications from the computing device 112, for example, when the cast button 119 is selected. However, in some embodiments, when the media casting device 102 receives a communication from another source (e.g., a government authority) or when the media casting device identifies another trigger event (e.g., a specified time of day), the computing device 112 may not necessarily be involved. In such embodiments, the aforementioned steps involved in the computing device 112 may not necessarily be involved as a predicate to the media casting device 102 waking the media playback device 106.

[0047] In some embodiments, the media casting device 102 may use one or more commands (e.g., one or more HDMI CEC commands, such as one-touch play) to turn on the media playback device 106 and may start receiving, decoding, and rendering the content (e.g., over HDMI) to the media playback device 106. Thus, the media casting device 102, being connected to the media playback device 106 via HDMI, may utilize a CEC protocol to turn on the media playback device 106 and cause the media playback device 106 to start displaying content. The HDMI CEC protocol has a wake command called the One Touch Play (OTP) command. When you send that from a source device to a sink device over HDMI, the sink device turns on. With one command, the sink device is turned on to active/play state. When the media playback device 106 is in passive standby, Wi-Fi and Bluetooth may be turned off, while HDMI is always on.

[0048] In some embodiments, the media casting device 102 may customize commands to the media playback device 106. For example, the OTP command could be customized with an appended descriptor specifying the reason for the wake-up (e.g., wake-on cast, emergency alert message, predetermined wake time, etc.). The descriptor may be appended to the wake command with any suitable data structure. In some embodiments, the descriptor may include any suitable content to be displayed by the media playback device 106. Media playback devices 106 that do not support custom commands may still be awakened but may not be immediately information about the reason and may have to perform out-of-band communications to query about the reason, and the media casting device 102 may responsively communicate the reason why there was a wake-up to the media playback device 106.

[0049] As indicated by block 322, the media casting device 102 may discontinue masquerading as the media playback device 106 to the computing device 112 after waking the media playback device 106. In some embodiments, when the media playback device 106 returns to its default power state, the media playback device 106 may inform the media casting device 102 to stop masquerading as the media playback device 106 and may reclaim its native cast-receiver capability as it is now in the active state. Accordingly, the media playback device 106 may inform that it can receive cast messages and content directly instead of relying solely on an indirect type of casting modes where the media casting device 102 receives the cast for the media playback device 106.

[0050] When the media playback device 106 is an active mode, the offloading is not necessary and not performed. The procedure of transferring the cast capability to the media casting device 102 may execute next when the media playback device 106 is put back into standby mode by the user. Accordingly, the process flow may transition back to block 310.

[0051] FIG. 4 illustrates an example of a generalized schematic diagram of a system 400 on which the mechanisms for presenting content as described herein can be implemented in accordance with some embodiments. As illustrated, the system 400 may include one or more computing devices 112. The computing devices 112 may be local to each other or remote from each other. The computing devices 112 may be connected by one or more communications links 402 to a communications network 404 that may be linked via a communications link 406 to the media casting device(s) 52, via a communication link 408 to content delivery server 120, via communication link 412 to content discovery server 121, and via communication links 402 to other computing devices 112.

[0052] In some implementations, each of the computing devices 112, the content delivery server 120, the content discovery server 121, and the media casting device 52 may be any of a general- purpose device such as a computer or a special purpose device such as a client, a server, etc. Any of these general or special purpose devices may include any suitable components such as a hardware processor (which may be a microprocessor, digital signal processor, a controller, etc.), memory, communication interfaces, display controllers, input devices, etc. For example, the computing device 112 may be implemented as a smartphone, a tablet computer, a wearable computer, a personal computer, a laptop computer, a gaming console, a digital media receiver, a set-top box, a smart television, a server, etc.

[0053] The communications network 404 may be any suitable computer network or combination of such networks including the Internet, an intranet, a wide-area network (WAN), a local-area network (LAN), a wireless network, a digital subscriber line (DSL) network, a frame relay network, an asynchronous transfer mode (ATM) network, a virtual private network (VPN), etc. The communications links 402, 406, 408, and 412 may be any communications links suitable for communicating data among the computing devices 112, the media casting device 52, the content delivery server 120, and the content discovery server 121, such as network links, dial-up links, wireless links, hard-wired links, any other suitable communications links, or any suitable combination of such links. The computing devices 112 may discover, browser, download, stream, store, playback, transmit, and/or otherwise present content stored locally at the computing device 112 or stored remotely at the content delivery server 120 using any suitable technique(s).

[0054] The system 400 may include the media casting device 52 as described above in connection with, for example, FIG. 1, and may include a media receiving application 410 installed on and/or running on one or more of the computing devices 112, which may replicate the functions of media casting device 52 using a computing device 112. The system 400 may include one or more content delivery servers 120. The content delivery server 120 may be any suitable server for providing access to media content items in accordance with the mechanisms described herein for presenting content, such as a processor, a computer, a data processing device, and/or any suitable combination of such devices. The system 400 may include one or more content discovery servers 121. The content discovery server 121 may be any suitable server for facilitating discovery and/or browsing of media content items accessible on the content delivery server 120 in accordance with the mechanisms described herein for presenting content, such as a processor, a computer, a data processing device, and/or any suitable combination of such devices. In some embodiments, the communications link 114 described above in connection with FIG. 1 may include the communication link 402, the communication network 404, and the communication link 406; communications link 122 described above in connection with FIG. 1 may include the communication link 402, the communication network 404, and the communication link 408; and the communications link 124 described above in connection with FIG. 1 may include the communication link 406, the communication network 404, and the communication link 408.

[0055] FIG. 5 illustrates an example of hardware 500 that may be used to implement one of the computing devices 112, the media casting device 52, and the content delivery server 120 depicted in FIG. 4 in accordance with some implementations of the disclosed embodiments. Referring to FIG. 5, the computing device 112 may include a hardware processor 512, a display/input device 514, memory 516, and a transmitter/receiver 518, which may be interconnected. In some implementations, the memory 516 may include a storage device (such as a non-transitory computer-readable medium) for storing a computer program for controlling the hardware processor 512.

[0056] The hardware processor 512 may use the computer program to present on the display/input device 514 media content and/or an interface that allows a user to, among other things, cause media content presented on the display/input device 514 to be presented on a media receiving device, such as the media casting device 52. It should also be noted that data received through the communications link 402 or any other communications links may be received from any suitable source. In some implementations, the hardware processor 512 may send and receive data through the communications link 402 or any other communication links using, for example, a transmitter, receiver, transmitter/receiver, transceiver, or any other suitable communication device, such as the transmitter/receiver 518. The display/input device 514 may include a touchscreen, a flat panel display, a cathode ray tube display, a projector, a speaker(s), and/or any other suitable display and/or presentation devices, and may further include a computer keyboard, a computer mouse, a microphone, a touchpad, a voice recognition circuit, a touch interface of a touchscreen, and/or any other suitable input device. The transmitter/receiver 518 may include any suitable transmitter and/or receiver for transmitting and/or receiving, among other things, media content including audio and/or video content.

[0057] The media casting device 52 may include a hardware processor 522, a display output 524, memory 526, and a transmitter/receiver 528, which may be interconnected. In some implementations, the memory 526 may include a storage device (such as a non-transitory computer-readable medium) for storing a computer program for controlling the hardware processor 522. The hardware processor 522 may use the computer program to provide media content and/or a user interface to display output 524 for presenting the media content and/or user interface on a media playback device. It should also be noted that data received through the communications link 406 or any other communications links may be received from any suitable source. In some implementations, the hardware processor 522 may send and receive data through the communications link 406 or any other communication links using, for example, a transmitter, receiver, transmitter/receiver, transceiver, or any other suitable communication device, such as the transmitter/receiver 528. The display output 524 may include hardware, software and/or firmware for outputting media content to a media playback device in any suitable format, and may include the input/output connector 54 as described above in connection with FIG. 1. The transmitter/receiver 528 may include any suitable transmitter and/or receiver for transmitting and/or receiving, among other things, media content including audio and/or video content.

[0058] The content delivery server 120 may include a hardware processor 532, a display/input device 534, memory 536, and a transmitter/receiver 528, which may be interconnected. In some implementations, the memory 536 may include a storage device for storing data received through communications link 408 or through other links. The storage device (such as a non-transitory computer-readable medium) may further include a server program for controlling the hardware processor 532.

[0059] The hardware processor 532 may use the server program to communicate with the computing device 112 and/or the media casting device 52, as well as provide access to media content. It should also be noted that data received through the communications link 408 or any other communications links may be received from any suitable source. In some implementations, the hardware processor 532 may send and receive data through the communications link 408 or any other communication links using, for example, a transmitter, receiver, transmitter/receiver, transceiver, or any other suitable communication device, such as transmitter/receiver 538. In some implementations, the hardware processor 532 may receive commands and/or values transmitted by one or more users. The display/input device 534 may include a touchscreen, a flat panel display, a cathode ray tube display, a projector, a speaker(s), and/or any other suitable display and/or presentation devices, and may further include a computer keyboard, a computer mouse, a microphone, a touchpad, a voice recognition circuit, a touch interface of a touchscreen, and/or any other suitable input device. The transmitter/receiver 518 may include any suitable transmitter and/or receiver for transmitting and/or receiving, among other things, media content including audio and/or video content.

[0060] In some implementations, the content delivery server 120 may be implemented in one servers or may be distributed as any suitable number of servers. For example, multiple servers 120 may be implemented in various locations to increase reliability and/or increase the speed at which the server 120 may communicate with the computing devices 112 and/or the media casting device 52. In some implementations, the content discovery server 121 may be implemented using similar hardware to the content delivery server 120 but may include a server program for facilitating discovery and/or browsing of media content items accessible from the content delivery server 120.

[0061] In one particular implementation, the mechanisms described herein including the sender application, the receiver application, the content presentation application, and/or the content streaming application may include server-side software, server-side hardware, client-side software, client-side hardware, or any suitable combination thereof. For example, the sender application, the receiver application, the content presentation application and/or the content streaming application may encompass a computer program written in a programming language recognizable by the hardware processor 512, the hardware processor 522, and/or the hardware processor 532 (e.g., a program written in a programming language, such as, Java, C, Objective-C, C++, C#, Javascript, Visual Basic, or any other suitable approaches). As another example, the sender application, the receiver application, the content presentation application and/or the content streaming application may encompass code corresponding to one or more Web pages or Web page portions (e.g., via any suitable encoding, such as Hyper Text Markup Language (“HTML”), Dynamic Hyper Text Markup Language (“DHTML”), Extensible Markup Language (“XML”), JavaServer Pages (“JSP”), Active Server Pages (“ASP”), Cold Fusion, or any other suitable approaches).

[0062] In some implementations, any suitable computer/processor-readable media may be used for storing instructions for performing the functions and/or processes described herein. For example, in some implementations, one or more processor-readable media may be transitory or non-transitory. For example, non-transitory, processor-readable media may include media such as magnetic media (such as hard disks, floppy disks, etc.), optical media (such as compact discs, digital video discs, Blu-ray discs, etc.), semiconductor media (such as flash memory, electrically programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), etc.), any suitable media that is not fleeting or devoid of any semblance of permanence during transmission, and/or any suitable tangible media. As another example, transitory computer readable media may include signals on networks, in wires, conductors, optical fibers, circuits, any suitable media that is fleeting and devoid of any semblance of permanence during transmission, and/or any suitable intangible media.

[0063] The memory of the device 52 may, for example, include high-speed random-access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. The memory may, optionally, include one or more storage devices remotely located from one or more processing units 522. The memory, or alternatively the non-volatile memory within memory, may include a non-transitory, processor-readable storage medium.

[0064] In some implementations of the device 52, memory, or the non-transitory, processor- readable storage medium of memory, may store the following programs, modules, and data structures, or a subset or superset thereof: an operating system including procedures for handling various basic system services and for performing hardware dependent tasks; a network communication module for connecting the casting device 52 to other devices (e.g., 1202, 121, 112, 56, etc.) via one or more network interfaces (wired or wireless) and one or more networks 404, such as the Internet, other wide area networks, local area networks, metropolitan area networks, and so on; a user interface module for enabling presentation of information at the casting device 52 via one or more output devices 524 (e.g., displays, speakers, etc.); an input processing module for processing one or more user inputs or interactions captured or received by the one or more input devices and interpreting the input or interaction; a voice assistant module for processing verbal inputs, providing the verbal inputs to the server(s), receiving responses from the server(s), and outputting the responses; and client data for storing at least data associated with the voice assistant module. Such client data may include one or a combination of: voice assistant settings for storing information associated with settings and configurations for the voice assistant module and voice assistant functionality; content/information sources and categories for storing predefined and/or user-specified sources and categories of content or information; usage history for storing information associated with the operation and usage of the voice assistant module (e.g., logs), such as commands and requests received, responses to the commands and requests, operations performed in response to commands and requests, and so on; and user accounts and authorizations for storing one or more users' authorizations and authentication information to access the users' respective accounts at content/information sources and account information for those authorized accounts; and receiver module for operating the casting functionality of the casting device 52, including communicating with content sources to receive content for playback.

[0065] The methods, systems, and devices discussed above are examples. Various configurations may omit, substitute, or add various procedures or components as appropriate. For instance, in alternative configurations, the methods may be performed in an order different from that described, and/or various stages may be added, omitted, and/or combined. Also, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of the configurations may be combined in a similar manner. Also, technology evolves and, thus, many of the elements are examples and do not limit the scope of the disclosure or claims.

[0066] Specific details are given in the description to provide a thorough understanding of example configurations (including implementations). However, configurations may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail in order to avoid obscuring the configurations. This description provides example configurations only, and does not limit the scope, applicability, or configurations of the claims. Rather, the preceding description of the configurations will provide those skilled in the art with an enabling description for implementing described techniques. Various changes may be made in the function and arrangement of elements. [0067] Also, configurations may be described as a process which is depicted as a flow diagram or block diagram. Although each may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. A process may have additional steps not included in the figure. Furthermore, examples of the methods may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks may be stored in a non-transitory computer-readable medium such as a storage medium. Processors may perform the described tasks.

[0068] Having described several example configurations, various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the disclosure. For example, the above elements may be components of a larger system, wherein other rules may take precedence over or otherwise modify the application of the invention. Also, a number of steps may be undertaken before, during, or after the above elements are considered.

[0069] Furthermore, the example embodiments described herein may be implemented as logical operations in a computing device in a networked computing system environment. The logical operations may be implemented as: (i) a sequence of computer implemented instructions, steps, or program modules running on a computing device; and (ii) interconnected logic or hardware modules running within a computing device.

[0070] Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0071] Also, the terms in the claims have their plain, ordinary meaning unless otherwise explicitly and clearly defined by the patentee. The indefinite articles “a” or “an,” as used in the claims, are defined herein to mean one or more than one of the element that the particular article introduces; and subsequent use of the definite article “the” is not intended to negate that meaning. Furthermore, the use of ordinal number terms, such as “first,” “second,” etc., to clarify different elements in the claims is not intended to impart a particular position in a series, or any other sequential character or order, to the elements to which the ordinal number terms have been applied.

Claims

WHAT IS CLAIMED:

1. A system to present content, the system comprising: one or more processing devices; and memory communicatively coupled with and readable by the one or more processing devices and having stored therein machine-readable instructions which, when executed by the one or more processing devices, cause the one or more processing devices to perform operations comprising: offloading a wake-on-cast functionality of a media playback device from the media playback device to a media casting device, wherein the offloading the wake-on-cast functionality allows the media playback device to transition from a default power state to a lower power state while the wake-on-cast functionality is preserved by the media casting device; while the media playback device is in the lower power state, receiving, by the media casting device, a communication from a computing device; and responsive to the communication, waking, by the media casting device, the media playback device from the lower power state to cause the media playback device to return to the default power state.

2. The system to present content as recited in claim 1, the operations further comprising: responsive to the communication, causing, by the media casting device, the media playback device to begin playing content consequent to the waking.

3. The system to present content as recited in claim 1, where the lower power state corresponds to a standby-passive state.

4. The system to present content as recited in claim 1, the operations further comprising: while the media playback device is in the lower power state, the media casting device masquerades as the media playback device to the computing device.

5. The system to present content as recited in claim 4, the operations further comprising: discontinuing, by the media casting device, masquerading as the media playback device to the computing device after the waking the media playback device.

6. The system to present content as recited in claim 1, the operations further comprising: communicating, by the media casting device, with the media playback device to facilitate addition of a menu option corresponding to the lower power state with wake-on-cast offloading.

7. The system to present content as recited in claim 1, the operations further comprising: prior to the offloading, determining, by the media casting device, whether the media playback device is capable of having the wake-on-cast functionality offloaded to the media casting device.

8. One or more non-transitory, machine-readable media having machine- readable instructions thereon which, when executed by one or more processing devices, cause the one or more processing devices to perform operations comprising: offloading a wake-on-cast functionality of a media playback device from the media playback device to a media casting device, wherein the offloading the wake-on-cast functionality allows the media playback device to transition from a default power state to a lower power state while the wake-on-cast functionality is preserved by the media casting device; while the media playback device is in the lower power state, receiving, by the media casting device, a communication from a computing device; and responsive to the communication, waking, by the media casting device, the media playback device from the lower power state to cause the media playback device to return to the default power state.

9. The one or more non-transitory, machine-readable media as recited in claim 8, the operations further comprising: responsive to the communication, causing, by the media casting device, the media playback device to begin playing content consequent to the waking.

10. The one or more non-transitory, machine-readable media as recited in claim, where the lower power state corresponds to a standby-passive state.

11. The one or more non-transitory, machine-readable media as recited in claim, the operations further comprising: while the media playback device is in the lower power state, the media casting device masquerades as the media playback device to the computing device.

12. The one or more non-transitory, machine-readable media as recited in claim 1, the operations further comprising: discontinuing, by the media casting device, masquerading as the media playback device to the computing device after the waking the media playback device.

13. The one or more non-transitory, machine-readable media as recited in claim, the operations further comprising: communicating, by the media casting device, with the media playback device to facilitate addition of a menu option corresponding to the lower power state with wake-on-cast offloading.

14. The one or more non-transitory, machine-readable media as recited in claim, the operations further comprising: prior to the offloading, determining, by the media casting device, whether the media playback device is capable of having the wake-on-cast functionality offloaded to the media casting device.

15. A method to present content, the method comprising: offloading a wake-on-cast functionality of a media playback device from the media playback device to a media casting device, wherein the offloading the wake-on-cast functionality allows the media playback device to transition from a default power state to a lower power state while the wake-on-cast functionality is preserved by the media casting device; while the media playback device is in the lower power state, receiving, by the media casting device, a communication from a computing device; and responsive to the communication, waking, by the media casting device, the media playback device from the lower power state to cause the media playback device to return to the default power state.

16. The method to present content as recited in claim 15, further comprising: responsive to the communication, causing, by the media casting device, the media playback device to begin playing content consequent to the waking.

17. The method to present content as recited in claim 15, where the lower power state corresponds to a standby-passive state.

18. The method to present content as recited in claim 15, further comprising: while the media playback device is in the lower power state, the media casting device masquerades as the media playback device to the computing device.

19. The method to present content as recited in claim 18, further comprising: discontinuing, by the media casting device, masquerading as the media playback device to the computing device after the waking the media playback device.

20. The method to present content as recited in claim 15, further comprising: communicating, by the media casting device, with the media playback device to facilitate addition of a menu option corresponding to the lower power state with wake-on-cast offloading.