TW201921239A - Interactive notifications between a media device and a secondary device - Google Patents

Abstract

A method includes obtaining an association of a client device with the secondary device. The method further includes identifying a triggering event related to an operation of the secondary device. The method also includes responsive to identifying the triggering event, sending, by the secondary device via a network, a message to the client device with a request for information related to the operation of the secondary device. The client device may have a client device interface configured to present the message and to receive input pertaining to the message. The method includes receiving, via a network, input pertaining to the information from the client device. The method further includes configuring the secondary device to perform the operation at the secondary device using the input received from the client device.

Description

Interactive notification between media devices and auxiliary devices

Embodiments discussed herein relate to interactive notifications between a media device and an auxiliary device.

As technology advances, newer devices may include additional features and functionality as compared to prior devices. However, an emphasis is placed on the release of such additional features and functionality at the expense of developing technological improvements to enable the use of such additional features and functionality.

The subject matter claimed herein is not limited to embodiments that solve any disadvantages or operate only in an environment such as those set forth above. Rather, the background art is merely illustrative of one exemplary technical field in which certain embodiments set forth herein may be practiced. In addition, the materials set forth in the Background section are not prior art to the scope of the patent application in the present application and are not admitted to the prior art.

The client device can be used to control other devices. Using a conventional system, the user can initiate control of an auxiliary device using a client device such as a set-top box, a smart device (eg, thermostat, freezer), an audio/video system, A game system or console or any other connected device, etc. However, under the conventional method, the device to be controlled (i.e., the auxiliary device) usually does not initiate the control program. Instead, the client device initiates control by sending a command to the accessory.

Aspects of the present invention address these and other deficiencies of conventional systems by providing a system and method for controlling an auxiliary device using a control device. The auxiliary device can initiate the control program.

An exemplary system can include a memory and operatively coupled to one or more of the memory devices. The one or more processing devices can be configured to perform an operation or control operation, the operations comprising: associating a client device with an auxiliary device; identifying one of the trigger events associated with operation of one of the auxiliary devices In response to identifying the triggering event, transmitting a message having one of the information related to the operation of the auxiliary device to the client device, the client device having a user interface configured to receive the information; The network receives information from the client device; and performs operations at the auxiliary device using information from the client device.

A method includes obtaining an association between a client device and an auxiliary device. The method further includes identifying a triggering event associated with operation of one of the auxiliary devices. The method also includes, in response to identifying the triggering event, transmitting, by the auxiliary device, a message having a request for information related to the operation of the auxiliary device to the client device via a network. The client device can have a client device interface configured to present the message and receive an input related to the message. The method includes receiving input related to the information from the client device via a network. The method further includes configuring the auxiliary device to perform the operation at the auxiliary device using the input received from the client device.

The present invention has been described in terms of a television, a set-top box, and a client device for purposes of illustration and ease of explanation. It should be understood that any type of auxiliary device may be used in place of or in addition to the set top box. For example, the techniques set forth herein can be used to send and receive messages between any two interconnected devices.

A set-top box can handle one of the signals for display on a television. Typically, control of an on-board box is performed using a handheld remote unit. Using a remote device and an on-screen interface on the TV, a user can browse the TV list, search for content, and otherwise consume media items. However, remote device typing with text generally provides limited functionality as well as other deficiencies. Using a conventional remote device, a user can spend a frustrating amount of time using the remote device to type text into the on-screen interface. Other auxiliary devices may have similar problems.

To overcome the problems associated with the prior art, the set-top box can use messages (eg, interactive notifications) to initiate and receive information from the client device. The techniques set forth herein can provide contextual awareness of when to send information to the client device from the set-top box at an appropriate time at the set-top box. In some instances, when a user encounters a text entry field at the set-top box, the set-top box can send a message to provide a virtual keyboard on one of the user-side devices to the client device. . The user can then use his client device to type in the text and the client device sends the typed text to the set-top box. In this manner, the present invention overcomes the deficiencies associated with conventional text entry on the set-top box.

The invention also describes the push-on message and recommendation for the user to watch and explore. The client device can present the message as an interactive notification: the user can interact with or without turning on a dedicated media application on the mobile device. The set-top box can use a location of the client device and known information about a user to formulate and send contextual messages to the user.

Other techniques, devices, and systems may also benefit from the present invention. For example, as the Internet of Things (IoT) became more widespread, more and more devices became interconnected. It may be beneficial to receive assistance from a client device, such as a smart phone, while certain IoT devices are operating. For example, some IoT devices may not have a screen that is large enough to present a complete keyboard. These IoT devices can send a message to a client device to request input. The client device can receive the input and send the input to the IoT device.

1 illustrates a block diagram of an example operating environment 100 in which certain embodiments may be implemented in accordance with at least one embodiment set forth herein. The example operating environment 100 can include a television 102, a set-top box (STB) 104, a client device 106, a network 108, a content server 110, a data store 112, and an account server 114.

Television 102 can include a device configured to present media content via a display device. For ease of explanation, "media content" may refer to video content, audio content, text content, video content, or a combination of at least two types of content. The media content can include one of the audio components simultaneously played with a video component. The media content can include an electronic file that can be executed or loaded using software, firmware or hardware that is configured to be directed to the television 102, the STB 104, and/or the client device 106 via the television 102, the STB 104, and/or the client device 106. The user presents the content. Media content can also include live streaming content and media items that are available on demand. Television 102 can receive media content from any source, such as downloading a broadcaster, satellite, cable, first-class transmission device (e.g., client device 106), content server 110, or capable of transmitting media content to television 102 from an over-the-air. Receive media content from any other source. Media content may include (or be supplemented with) one or more electronic advertisements. Electronic advertising can advertise any product or service and can be received from any source.

The STB 104 can include a device configured to convert video content into an analog or digital TV signal. In at least one embodiment, STB 104 includes a satellite TV receiver or an over-the-air digital to analog converter. In at least one other embodiment, the STB 104 can include a media hub connected to a local network (eg, the network 108) for Internet access and can be from an online media provider (eg, Video of Netflix®, Hulu®) is converted into TV signal. The STB 104 can also be coupled to the client device 106 and receive content from the client device 106. The STB 104 can send an analog or digital signal to the television 102 for playback. In at least one embodiment, the STB 104 is integrated with the television 102.

The client device 106 can include a computing device, which can include, but is not limited to, a desktop computer, a mobile device, a laptop computer, a tablet computer, a mobile phone, a smart phone, and a number of people. Assistant (PDA) or other suitable computing device. Client device 106 can include any number of applications that enable a user to perform various tasks. In at least some embodiments, the client device 106 can include an application (eg, application 120) that can transmit to and receive communications from the STB 104. The app can also include various ad and activity tracking components. In at least one embodiment, the client device 106 can include one or more sensors, receivers, and/or transceivers (not illustrated) that can be configured to detect activity. The sensor, receiver, and/or transceiver can include an audio sensor (eg, a microphone), a wireless digital signal transceiver (eg, Wi-Fi, Bluetooth, ZigBee, Z-Wave), a motion Sensors (eg, gyroscopes, accelerometers, GPS units) and the like.

In general, network 108 may include enabling television 102, STB 104, client device 106, content server 110, data store 112, and account server 114 to communicate with one or more wide area networks (WANs) and/or Or a local area network (LAN). In some embodiments, network 108 includes an internetwork that includes a global Internet path formed by logical and physical connections between multiple WANs and/or LANs. Alternatively or in addition, network 108 may include one or more cellular RF networks and/or one or more wired and/or wireless networks such as, but not limited to, 802.xx networks, Bluetooth storage Pick up, wireless access point, Long Term Evolution (LTE) or advanced LTE network, IP based network or the like. Network 108 may also include servers that enable one type of network to interface with another type of network.

The example operating environment 100 can include any number of content servers 110. The content server 110 can include one or more computing devices (such as a rack server, a router computer, a server computer, a personal computer, a large computer, a laptop, a web server, a A proxy server, a desktop computer, etc., a data storage device (eg, a hard drive, a memory, a database), a network, a software component, and/or a hardware component. The content server 110 can provide media content (eg, digital video, streaming video, video, digital music, streaming music, social media information, etc.) to the television 102 and/or the STB 104. For example, to provide media content, the content server 110 can determine whether to permit a user to access content selected by the user (eg, whether the user is a subscriber). Content server 110 may also provide advertisements to television 102 and/or STB 104.

In at least one embodiment, the data store 112 can include a memory (eg, random access memory), a cache memory, a disk drive (eg, a hard disk drive), a flash magnet. A disk drive, a database system, or another type of component or device capable of storing data. Data store 112 may also include multiple storage components (eg, multiple disk drives or multiple databases) that may span multiple computing devices (eg, multiple server computers). The data store 112 can store client device information, client device association information, information related to one or more client devices and one or more STBs, including one or more associated with one or more STBs Group information of a plurality of client devices, one or more user profiles, one or more user accounts, one or more program schedules associated with one or more user accounts, by one use The record set by the account, the user's viewing history, social activities (eg, like, share), consumer activities (eg, one purchase, one save, one watch, one listen), and the like. Although each of the STB 104 and the data store 112 is depicted as a single distinct component in FIG. 1, the components can be implemented together in a single device or in a network of different devices operating together. In various combinations.

The example operating environment 100 can include any number of account servers 114. The account server 114 can include one or more computing devices (such as a rack server, a router computer, a server computer, a personal computer, a large computer, a laptop, a web server, a A proxy server, a desktop computer, etc., a data storage device (eg, a hard drive, a memory, a database), a network, a software component, and/or a hardware component. The account server 114 can provide account information to the STB 104. In at least some embodiments, account server 114 can cause account information to be stored in data store 112 or in another data store. Account information may include one or more usernames, one or more subscription levels, one or more user accounts, one or more devices associated with each user account, and one or more user accounts Relevant location information, etc. The STB 104 can request account information from the account server 114. Alternatively or in addition, the account server 114 can push account information to the STB 104.

The client device 106 can include a media application 120 that allows an end user to interact with the STB 104 via the client device 106. The media application 120 can receive messages from the STB 104. In response to the received message, the media application 120 can cause various user interface tools to be displayed on one of the display devices at the client device 106. In at least some embodiments, the user interface tool can be configured to provide at least one interactive notification. The user interface tool can include one of the tools configured to receive input via the client device 106. For example, the STB 104 can interactively notify one of the instructions to cause the client device 106 to present a screen or virtual keyboard. Send to the client device 106. The client device 106 can cause the virtual keyboard to be presented on the display device. The display device can include a touch sensitive feature (eg, a capacitive sensing system) configured to receive touch input from a user. For example, the display device can receive keyboard input from a user. The client device 106 can send a keyboard input to the STB 104. The STB 104 can use keyboard input as an input for an STB function, such as the STB functions illustrated in Figures 4, 5, 6, 7, and 10. For example, the STB function can include searching for one of various media items. Using keyboard input received from the client device 106, the STB 104 can initiate a query. For example, the STB 104 can send a query to the content server 110. The content server 110 can send the query results to the STB 104, and the STB 104 can cause the query results to be presented on the television 102. In this manner, the client device 106 can be used to receive input on behalf of the STB 104. The user interface tool can include any tool configured to receive any type of input via the client device 106. For example, the user interface tool can be configured to present different voting options via the client device 106 (eg, one of the favorite singers in a singing game TV program). The user interface tool can receive a selection of one of the voting options, and the client device can send the selection of the voting option to a voting server (which can include the content server 110 or any other server). In another example, the user interface tool can be configured to present information about one of the items available for purchase. The project can include any item, such as any physical item, any virtual item, any electronic item, any media item, and the like. For example, an item available for purchase may include one item associated with a media item. For example, one of the characters in a movie can wear a particular hat in one of the movies currently being played. The user interface tool can present information about the particular hat, including price, color options, size options, shipping options, and the like. The user interface tool can receive input indicating that the user will purchase one of the items. The client device 106 can send a purchase request to a server relating to an input indicating that the user intends to purchase the item.

In at least some embodiments, the media application 120 can be used to select and/or view content on the television 102 via the STB 104. For example, the media application 120 can be a web browser that can present a list of one of the media content items to the end user. As a web browser, the media application 120 can also access, retrieve, present, and/or navigate content served by a web server (eg, web pages such as Hypertext Markup Language (HTML) pages, digital media items. Wait). The media application 120 can render, display, and/or present the listing content to the end user. The media application 120 can also provide an embedded media player (eg, a Flash® player or an HTML5 player) embedded in a web page (eg, one that provides information about one of the products sold by an online merchant). Device). In another example, the media application 120 can be a standalone application (eg, a mobile application or mobile app) that allows a user to consume digital media items (eg, digital video, digital video, e-book, website, etc.) And various inputs are sent to the STB 104. The media application 120 can be provided to the client device 106 by the content server 110 or via an application store. The media application 120 can enable the client device 106 to receive messages from the STB 104. In at least some embodiments, when the media application 120 is installed on the client device 106, the STB 104 can send a message to the client device 106. Whether the media application 120 is running in the foreground, running in the background, or disabled, the client device 106 can present the message as a notification. In at least some embodiments, in addition to having the media application 120 installed on the client device 106, the STB 104 can send a message to the client when both the client device 106 and the STB 104 are on the same network. Device 106. Alternatively or in the alternative, when both the client device 106 and the STB 104 are on a same network, the STB 104 can send a message of a first type to the client device 106, and when the client device 106 and the STB 104 When not on a same network, the STB 104 can send a second type of message to the client device 106. Initial setting and configuration

In at least some embodiments, a user can establish a user account with a content provider, such as a cable television provider. In at least some embodiments, the account server 114 is associated with a content provider. To create an account, for example, a user can navigate to a website and provide registration information to the content provider. In at least some embodiments, during a user account setup procedure, the user can identify one or more client devices to register with the service provider. The service provider can register such devices with the user account, including one of the device identifiers for each of the client devices. In at least some embodiments, the service provider can register one of the unique identifiers (e.g., UUIDs) of each of the client devices with the user account. Alternatively or in the alternative, the user can provide an identifier. For example, a father can register his mobile phone by describing "Daddy's Phone", registering his wife's mobile phone with a description of "Mother's Phone", and registering a child with a description of "Children's Device". Mobile device. The account server 114 can store the identifiers of the various client devices in the data store 112 in association with the user account. The content provider may also assign an STB to the user account and register one of the STB identifiers in association with the user account. One of the user accounts records may include one or more STBs associated with the user account and one or more client devices associated with the user account. In at least some embodiments, the user may obtain one or more options or account preferences, such as one of the notifications or messages to send only a particular client device, device type, and the like. In at least some embodiments, an option or preference can include setting one of the one or more client devices to select or not to receive the notification. For example, a user can set "Daddy's Phone" and "Mother's Phone" to receive notifications and set "Children's Device" to not receive notifications.

In at least some embodiments, the portion of the user account creation program includes downloading the media application 120 to the client device 106. The media application 120 can present a registration interface that can be configured to receive various information (such as user information, STB information, etc.). Using the media application 120, the user can initiate a user account creation procedure and associate the STB 104 with the client device 106. For example, using the media application 120, the user can enter one of the STBs 104 identifiers (eg, one of the STB's MAC addresses or other identifiers). The STB 104 or the client device 106 or both may send a verification message to the account server 114, which may be associated with the content provider to confirm the association of the STB 104 with the client device 106.

In at least some embodiments, the STB 104 can be initialized for use by the media application 120. For example, the STB 104 can be Wi-Fi enabled, and the media application 120 can be used to provide network authentication to the STB 104, as further illustrated in connection with FIG. The STB 104 can also send an interactive notification to configure the STB 104 to the client device 106 and/or the media application 120. For example, the STB 104 can send a message to the client device 106 to present a user interface tool to receive one of the configuration details for the STB 104. The client device 106 can receive configuration details for the STB 104 via a user interface tool. The client device 106 can send configuration details for the STB 104 to the STB 104 or to any other device that can apply the configuration details for the STB 104 to the STB 104. The media application 120 can also be used to adjust any of the STB 104 configurations or settings, such as language selection, image quality, resolution, etc., using the techniques described. STB and user equipment in operation

In operation, the STB 104 can push a message to the client device 106. This message can include a request for one of the inputs. For example, the message can include a request for one of a textual element, tactile input, voice input, or any other type of input that can be received by the client device 106. In at least some embodiments, the message can include a request for one of a particular type of input and/or an input method from the client device 106. For example, the message from the STB 104 to the client device 106 can include a request for one of a username and a password. The message may also include an instruction to retrieve the user name via a text box and to retrieve the password from a text box. When the character of the password is provided to the client device 106, the character of the password is The text box can be obscured or hidden. Any type of input method can be used, such as a keyboard, numeric keypad, on-screen gestures, off-screen gestures, and the like.

In an exemplary embodiment, STB 104 can receive an input. For example, a user can use an STB remote device to navigate the various graphical interfaces of the STB 104. The STB remote device can include a button that, when pressed, sends a request to the STB 104 to provide input using the client device 106. Alternatively or in addition, the user's navigation using the STB remote device can arrive at one of the STB input fields in one of the specific graphical interfaces of the STB 104. The STB 104 can determine if the STB input field can be controlled or supplemented by a client device. The STB 104 can identify available client devices. In at least some embodiments, the STB 104 can examine the network 108 to find available client devices that are also connected to the network 108. Alternatively or in addition, the STB 104 can check a user account for available client devices. In at least some embodiments, the STB 104 examines a local storage to find devices associated with the user account. The STB 104 can query the account server 114 to find the device associated with the user account. If a client device (e.g., client device 106) is identified, the STB 104 can determine a communication mechanism with which the client device 106 is contacted. For example, the communication mechanism can include the network 108 or another network. The STB 104 can then send a message to the client device 106 using the communication mechanism. The message may include an instruction to cause the client device 106 to open a user interface on the client device, the user interface including a user input field corresponding to one of the STB input fields at the STB interface. For example, when the STB input field is associated with an alphanumeric element, the user input field can include a keyboard. The message may include an instruction to cause the client device 106 to present a virtual keyboard on one of the displays of the client device 106. The user can provide user input to the client device 106 via the user input field (eg, by tapping the virtual keyboard). Client device 106 can send user input to STB 104. The STB 104 can use the received user input to perform an operation, such as starting a search for one of the one or more media items using the received user input as a keyword for searching in the STB input field.

The message may contain different instructions based on one of the STB input fields and/or one of the STB input fields. For example, the message may indicate that an STB input field is a text box, a user name field, a password field, etc., and the client device 106 will present an input field similar to the STB input field. In addition, the message can indicate multiple input fields. For example, the message may indicate that the client device will provide both a username field and a password field to receive user input. Without further interaction with the STB 104, the client device 106 can provide the user with the functionality to toggle between two or more STB input fields.

In at least some embodiments, the STB 104 can send a message to the client device 106 in response to a triggering event. As in the above example, the triggering event may include a user navigation at the STB input field in one of the graphical interfaces of the STB 104. Selecting one of the text fields or navigating to one of the text fields can trigger a trigger event. Other trigger events may include a time, a user state, or a user device location and other events.

For example, a time-based triggering event can include a scheduled time, such as one of the calendar times at the beginning of a particular program. For example, the message may include a reminder to start the program and cause the client device 106 to provide an option via one of the user interfaces at the user device, the option to power up the STB 104 and/or to the STB 104 One of the channels is adjusted to schedule one of the channels for the program.

For example, a trigger event based on a user state may be based on one or more past or current user activities and/or user characteristics. For example, the user status can include the user watching one of the programs on the television 102 and then can begin playing an advertisement. For example, a play advertisement may be for a different program. In response to the play advertisement (trigger event based on the user status), the STB 104 can send a message to the client device, the message including the interactive means for causing the client device 106 to present the user with one of the records for setting different programs. Notify one of the instructions. In another example, the advertisement may be for a new car. The message may include an instruction to cause the client device 106 to present more information about the new car, the information including one of the options for signing up for a new car at the regional dealership. In another example, a user may be watching a program and a product placement advertisement appears in the program. The message may include an instruction to cause the client device 106 to provide more information about the product in which the product is placed in the advertisement, the information including price, description, how to purchase, and to one of the stores that sold the product. In this manner, when a commercial is being broadcast on television 102, the user can receive a notification on the client device 106 that is capable of acting on one of the commercials.

In another example of a triggering event based on a user state, the user may be watching a program on television 102 and may be approaching the end of the program. At a predetermined time (e.g., the previous 30 seconds) prior to the end of the program, the STB 104 can send a message to the client device 106 having one of the information that causes the client device 106 to present one of the different programs to be viewed next. instruction. The client device 106 can also present an interface tool that the user can activate to begin playing different programs (which can include changing a channel to a different program). In one example, the user can watch a baseball game. Based on the user watching the baseball game and based on the user's past frequent viewing of the baseball game (and based on the user's subscription to a baseball content package), the STB 104 may determine that the user may wish to continue watching after the current game is over. More baseball content. Prior to the end of the current game, the STB 104 may send a message to the client device 106 with an instruction to present information regarding one or more other baseball games that may be currently being broadcast. The client device 106 can present one or more interface tools that the user can launch to select one of one or more other baseball games to view. The client device 106 can send the user selection to the STB 104, and the STB 104 can change the channel to another selected baseball game.

In another example of a triggering event based on a user state, the user can watch a particular program. The STB 104 can identify one or more social contacts of the user, such as by querying a social networking service or querying in the data store 112. The STB 104 can identify one of the user or a plurality of social contacts that is also viewing a social contact of the same program as the user, such as by querying the content for one of the user's social contacts. Server 110 or account server 114. The STB 104 can send a message to the client device 106 having an instruction to present the message to the user, wherein the message indicates that the user's social contact is also viewing the program. The STB 104 may also instruct the client device 106 to present a notification to the user as to whether they want to communicate with the social contact. The message can also contain contact information for social contacts. The client device 106 can present the contact information of the social contact in a display. The user can select contact information to initiate a conversation with one of the social contacts.

In one example, interactive notifications can be used at various points and in response to various activities. For example, the triggering event can include a request to log into one of the STBs 104. When the user is attempting to log into the STB 104, the STB 104 can send a message to the client device 106 for presenting a user interface tool configured to receive user login details regarding the STB 104. A triggering event can also include a request to log into a user account. When the user is attempting to log into an account, such as via the STB 104, the STB 104 can send a message to the client device 106 for presenting the user login configured to receive the user account. One of the details of the user interface tool. A triggering event can also include activation of one of the buttons on one of the STB remote devices. In response to the button on the STB being pressed, the STB can send an input indicating that the button has been pressed to the STB 104. The STB 104 can then send a message (which can include an interactive notification) to one or more of the client devices associated with the STB 104 or one of the accounts currently logged into the STB 104.

Interactive notifications can be sent to the client devices 106, 116 using different technologies and protocols. For example, interactive notifications can be sent using one of the message-oriented intermediate software's open standard application layer protocols, such as the Advanced Message Queue Agreement (AMQP). In another example, the interactive notification can be sent using a message queue system or message broker. The interactive notification can be queued to a central node or server before the interactive notification is sent to the client device. In at least one embodiment, the central node or server can provide routing, load balancing, persistent message queues, negative acknowledgement (NACK), re-arrangement, delay, and scheduling services when providing interactive notifications. In at least one embodiment, the interactive notification can be sent using a cross-platform runtime environment, such as Node.js. The cross-platform runtime environment improves the throughput and scalability of various applications, such as for web applications. In at least one embodiment, the interactive notification can be sent as a server send event (SSE). When using SSE, all client devices can be connected to a server with the same base URL and an identical port. The SSE can include one-way messaging, where the interactive notification can be sent to the client device without being sent to the server. In at least one embodiment, the interactive notification is sent on a subscription basis, wherein the client device can subscribe to messages about a particular service or server. The service or server can send an interactive notification to the subscribed client device.

In at least one embodiment, the client device 106 can include a text-to-speech converter that can convert text-based messages into an audio message. The client device 106 can play the audio message in an audio manner. The client device 106 can receive any type of input in response to playing the audio message in an audio manner. In at least one embodiment, the input can include an audio input that can be received by one of the microphones at the client device 106. The client device 106 can also include a voice-to-text converter that can convert the audio input into an electronic input (which can include an alphanumeric input). In this manner, a user can speak the voice input and the client can translate the voice input into an electronic input that can be used for any action at the STB 104. Client device presence detection

The STB 104 can use presence detection when sending a message to one or more client devices. When performing presence detection, the STB 104 can determine the location of at least one of the client devices. The location of a client device can include an approximate location. The location of a particular client device can be one of the locations of a particular client device relative to other client devices.

To detect the presence of the client device 106, the STB 104 can use one or more location detection technologies such as Wi-Fi, Bluetooth®, Global Positioning System (GPS), trembling of a user holding a client device, voice Far field and other technologies.

In certain example embodiments, the STB 104 may determine a location of the client device 106 based on identifying that the client device 106 is connected to one of the Wi-Fi networks. The STB 104 can also determine the location of the client device 106 based on the proximity of the client device 106 to one of the routers or access points. In at least some embodiments, the client device 106 can inherit a location from one of the networks to which it is connected. For example, a network device (e.g., a modem, router) can be associated with a particular external Internet Protocol (IP) address, which is also associated with a geographic location. The client device 106 can inherit the geographic location associated with the IP address of the network device.

In certain example embodiments, the STB 104 may use triangulation to determine the location of the client device 106. For example, the STB 104 can identify multiple points (eg, three points or more) that allow the STB 104 to triangulate or pinpoint the low-power Bluetooth where the client device 106 is located in one of the rooms associated with the STB 104 (eg, three points or more) a point).

In some example embodiments, STB 104 may use dizziness detection to determine the location of client device 106. A person may have a unique hand trembling pattern when he picks up a remote device or client device 106. The remote device or client device 106 can send a detected dither pattern to the STB 104. The STB 104 can use the detected dither pattern to determine who actually controls the remote device or client device 106. In at least some embodiments, the STB 104 can record trembling patterns in association with various activities over time, such as user registration, login, media item selection, and the like. The STB 104 can generate a trembling pattern profile, which can include the use of machine learning techniques and can associate the pattern with a particular user. The STB 104 can store the trembling pattern profile in association with one of the user accounts of a particular user.

In certain example embodiments, STB 104 may use far field speech techniques to determine the location of client device 106. For example, the STB 104 can periodically use far field speech techniques to detect speech from a user near the STB 104. In at least some embodiments, the remote device for one of the STBs 104 can also turn on the far field speech at a particular interval to identify a speech. Identification of a particular voice may indicate that a user is in the vicinity of the STB 104 and is watching the television 102. In at least some embodiments, the STB 104 can check the detected speech against a database of speech to determine a particular user. In response to identifying one of a particular user, the STB 104 can identify one of the user accounts of the user and/or one or more client devices associated with the particular user or user account. For example, the STB 104 can determine that the client device 106 is associated with the user based on the detected voice of the user. The STB 104 can send a message that can be directed or formulated for the user to the client device 106.

The presence can be determined at different levels. Four levels are set forth, but any number of levels can be used. A first level can be described as "associated with an account." At this level, one or more users may be associated with a single account with one of the content providers. One or more users may be associated with one or more STB devices (e.g., STB 104) on the account. Each of the one or more users may have their own profile within a person profile. Each of the one or more users may have its own client device associated with a single account having a content provider. The STB 104 can send a message to each of these client devices.

A second level can be referred to as a "location" level. The second level can be built based on the first level. Under this second level, a particular user may be located in the home where the device is connected or commonly used (or at an alternate location). When a user's client device is connected to a Wi-Fi network in their home, the user can be recognized as "at home." For example, detection of one or more of the client devices associated with a single account connected to the same network as STB 104 may indicate "presence" at the second level. Additionally or alternatively, a geofence (or any other technique) that indicates a particular behavior that typically occurs within the field, such as a user viewing short form content on their way to and from work.

A third level may indicate actual perception of one of the users in front of the television 102 and/or the STB 104. The third level can be constructed based on the first level and/or the second level. This type of presence detection can be performed by far field speech technology, an STB camera, infrared detection technology, face recognition technology, etc. as explained above to actually detect proximity to television 102 and/or STB 104. user. In another embodiment, television 102 may present content that includes a sound-sounding soundbite, such as a sound outside of the normal hearing range of a human. The client device 106 can detect the watermark with the watermark, and can send a message indicating that the client device detects the sounding with the watermark to the STB 104. The STB 104 can use one of the messages to determine the actual presence of the client device 106.

One of the fourth levels of presence detection can be referred to as "direct intent." Regarding this level, a user may have explicitly indicated that they want to take an action on the STB 104 using the client device 106.

Additionally, the STB 104 can use presence detection to determine the type of message that will be sent to the client device 106. For example, the STB 104 can determine the identity of the user, the recommendation information for the user, the location data of the client device associated with the user, the proximity of the client device 106 to the STB 104, and the STB 104. The current activity and other information that will send a message to the client device 106. For example, the STB 104 can know the identity of the user, know that the user likes the luxury car, knows that the user has recently searched the Internet for the luxury car, knows that the STB 104 is currently playing one of the programs including the fast car, and knows the user terminal. Device 106 is proximate to STB 104. The STB 104 can use this information to send a target message (e.g., a car advertisement) to the client device 106.

In at least one embodiment, the STB 104 can detect that the user is within an area of interest. For example, the area of interest may include a store, a shopping mall, a sports facility, or any other area of interest. For example, the STB 104 can determine that the client device 106 is connected to one of the wireless networks associated with a particular store. The STB 104 can then send a message to the client device 106. For example, the message may include a coupon, a discount code, or another piece of information related to the store.

In another example, the proximity of the client device 106 to the STB 104 can affect the message that the STB 104 sends to the client device 106. For example, when the client device 106 is nearby, the STB 104 can transmit information regarding the content currently being played in the set-top box. When the client device 106 is not near the STB 104 or is connected to one of the different networks than the STB 104, the STB 104 can send other information, such as promotional information. The STB 104 can also change the context of the promotional message based on the location of a user or proximity to the STB 104.

The client device 106 can include an activity manager 122 that identifies one or more activities of the user and/or the client device 106. An example activity may include exposure to an advertisement, a move (eg, a physical location or location move), a consumer activity (eg, browsing a web page, making a purchase), an activity that is not of interest (eg, may indicate The user has one of the low interest levels for one of the ads, etc.).

In one instance related to activity manager 122 detecting a mobile activity, example operating environment 100 can include an area. The area can be geographically defined, such as a building, a room within a building, and the like. In at least one embodiment, the region can be defined by a sensor based on characteristics of the video content, characteristics of the television 102, and/or one of the user devices 106. For example, the area can be defined by the current volume level of one of the video content being played on the television 102, as detected by a microphone of the client device 106. The client device 106 can move in and out of the area. The activity manager 122 can determine when the client device 106 has moved in and out of the area. For example, when the client device 106 moves far enough away from the television 102 that the microphone no longer detects the sound from the television 102 (or the detected sound drops below a sound threshold), then the activity manager 122 may determine that the client device 106 may have moved out of the area. In at least one embodiment, the activity manager 122 can use a detected volume level to determine a user distance from one of the televisions 102. The activity manager 122 can send information about the user device 106 moving in and out of the area to the STB 104.

In another example, the client device 106 can connect to the STB 104 via a wireless link, such as Bluetooth®. The wireless link can be disconnected when the client device 106 moves away from the STB 104 to a greater distance than a threshold distance. In at least one embodiment, a wireless radio is configurable to cover a user selected distance. The STB 104 can detect that the connection to the client device 106 has been lost in response to the connection being disconnected.

In at least one embodiment, the example operating environment 100 can include a plurality of client devices, such as another client device 116. The STB 104 can detect client devices (e.g., client device 106 and client device 116) that can be in or near the region. The STB 104 can detect a first user profile associated with the client device 106 and a second user profile associated with the client device 116. For example, the STB 104 can detect one of the device identifiers (eg, MAC address, UUID) of each of the client devices, and then determine that one of the first UUIDs of the client device 106 is associated with the first user profile. And one of the second UUIDs of the client device 116 is associated with the second user profile. The STB 104 can send a message to the client device 106 based on the first user profile. The STB 104 can send a message to the client device 106 based on the second user profile. In at least one embodiment, the client device 116 can include any connected device, including an appliance, an IoT device, and the like. The STB 104 can detect an event at the client device 116 and can send a message to the client device 106 based on the event at the client device 116. For example, the client device 116 can include a doorbell. In response to detecting a ringtone, the STB 104 can send a message to the client device 106, the message can include one of the currently playing media items that has been notified by one of the ringing bells and/or used to pause, stop, or mute the playing. Options, etc.

The STB 104 can also perform presence detection for multiple client devices. The STB 104 can send a message to each of the client devices. For example, "Daddy's Phone", "Mother's Phone" and "Kid's Device" are each detected by STB 104. The STB 104 can send a message to each of these client devices.

In at least some embodiments, the STB 104 can send a message to at least all of the detected client devices. The STB 104 can use presence detection to determine which of the user devices the message will be sent to. For example, the STB 104 can determine which of the client devices is closest to the STB 104 and only send a message to the client device. In at least some embodiments, STB 104 can determine that "Daddy's Phone" is the primary client device on a single account, and STB 104 can select "Daddy's Phone" as the recipient of the STB message.

In at least one embodiment, the STB 104 can send a message according to a control policy, which can include a long control policy. For example, the policy can use parental controls to block specific elements of a media item (rather than unnecessarily blocking an entire media item). For example, certain restrictions can be imposed on a media item. When the STB 104 receives a request to play one of the media items containing the restrictive content, the STB 104 can send a message to the client device 106. For example, the message may include a notification in the next scene or a next portion of the media item that contains restrictive content. For example, the STB 104 can automatically pause the media item before reaching the restricted content and send a message to alert the user that the next scene or the next portion contains restrictive content. The message can include an interactive notification that includes at least one user interface tool. The user interface tool can include one of the user selectable to continue viewing (or later viewing), skip this particular scene/part or stop viewing content selection options, and other options. The user interface tool can include selectable options to review explicit words, requests, and only "child-friendly" advertisements from audio, letter, and content descriptions (post-data).

The STB 104 may send a message to unlock a content requested by a second client device (eg, the client device 106) or a content requested by a second client device (eg, the client device 106) to the first A client device (e.g., client device 116). In at least one embodiment, certain restrictions on media items may be applied to some or all of the client devices 106, 116. For example, a "children's device" 106 can send a request to play the STB 104 to play a content containing restricted content. The STB 104 may determine that the "child's device" 106 is not authorized to view or request to play the requested content (e.g., on the client device 106 or the television 102). The STB 104 may send a message to the "Daddy's Phone" 116 to notify the father that his child has attempted to play the restricted content. The message may also include an option for the dad to permit the child to consume the restricted content on the client device 106 or the television 102.

The dad's phone 116 may provide a user interface tool configured to receive input to permit the child's device 106 to view the restricted content. In at least one embodiment, the user interface tool can provide additional information, such as previewing one of the restrictive content, information about who else can view the restricted content, or who is watching the restricted content, one of the children past View history (eg, content items, genre, viewing time), hot topics, recommendations, or other social information about restricted content. The dad's phone 116 can send input to the STB 104. The STB 104 may authorize the child's device 106 or television 102 to present the restricted content in response to receiving the input from the dad's phone 116 that allows the child's device 106 to view the restricted content. In at least one embodiment, the input can include a consent, a selection of one of the options for adding content to a custom "Allow" playlist, a disagreement, adding content to a custom One of the options of the "block" playlist is selected to select an alternate content to view one of the options, which may be sent to the child's device 106 and/or television 102.

In another example, the STB 104 can determine the length of time elapsed since the media application 120 was opened on the client device 106. In at least some embodiments, the STB 104 can request the client device 106 to send this information. In at least some embodiments, the client device 106 can send this information to the STB 104 without receiving a request from the STB 104 for this information. For a plurality of detected client devices, the STB 104 can determine which of the client devices has recently turned on the media application 120. For example, if a first client device has a running media application 120 and other devices do not launch the media application within a few days, then the first client device is more likely to be associated with one of the currently being consumed content. The STB 104 can select the first client device and send a message to the first client device.

In some example embodiments, STB 104 may determine that there is a detection score for one of the client devices. The presence detection score may indicate the likely proximity of the client device 106 to the STB 104. The presence detection score may also take into account one of the users associated with the client device 106. The presence detection score may indicate that a client device 106 (and one of the user devices 106) may be in the vicinity of the STB 104 and that the user of the client device 106 may be sitting and watching content on the television 102 or with the client. Device 106 interacts. The presence detection score can be used to select one or more client devices from a group of available client devices. For example, the STB 104 can determine a score for each of the client devices 106, 114 and can select one of the client devices based on the scores of the client devices 106, 114.

Modifications, additions, or omissions may be made to the example operating environment 100 without departing from the scope of the invention. In particular, an embodiment of an example operating environment 100 is illustrated in FIG. 1 as including a television 102, a set-top box 104, a network 108, a content server 110, a data store 112, and an account server. 114. However, the present invention is applicable to one or more televisions 102, one or more set-top boxes 104, one or more networks 108, one or more servers 110, one or more data stores 112, or any One of the example operating environments 100 is combined.

Moreover, the separation of various components of the embodiments set forth herein is not intended to indicate that the separation occurs in all embodiments. Additionally, with respect to the benefits of the present invention, the illustrated components can be integrated together in a single component or separated into multiple components.

In cases where the system discussed herein collects personal information about the user or may utilize personal information, the user may be provided with useful control over whether the system in question collects user information (eg, about a user's social network) Road, social action or activity, occupation, a user's preference or information about the current location of a user) or an opportunity to control whether and/or how to receive content that is more user-related from the content server. In addition, certain materials may be processed in one or more ways before they are stored or used, such that personally identifiable information is removed. For example, the identity of a user may be processed such that the personal identifiable information of the user is not determinable, or in the case of obtaining location information, the geographic location of a user may be used for generalization (such as generalization to one). City, ZIP code or state level makes it impossible to determine a specific location of a user. Thus, the user may have control over how to collect information about the user and use it by the system in question.

2A illustrates an exemplary client graphical user interface (GUI) 200 having at least one message received from an auxiliary device. In response to an action of an auxiliary device (eg, STB 104 of FIG. 1) or a user making an action (eg, making a selection, typing a text box), an STB may send a message (eg, a notification) ) is sent to a client device (eg, client device 106 of FIG. 1). As illustrated, the GUI 200 illustrates two notifications 205, 210 on a locked screen on the client device.

A message can include an application name, a small icon, a small image, and a short message. A message can be used when a phone is locked and used. 2B illustrates a GUI 250 having a notification 255 on the client device when the client device is in use.

The auxiliary device can send a message to the client device at any time, such as when a content provider pushes a notification about a particular event or promotion, when a content provider generates various recommendation notifications (eg, a live sports event), and When a user has previously set a program reminder, as well as other scenarios. In at least one embodiment, a user toggles to the right to cancel the notification, and a leftward toggle causes one of the media cards to be initiated.

FIG. 3 illustrates an example GUI 300 having an action form 305 for one of the media items. For example, the action form can include a program image 310, a program title 315, one or more lines of program descriptions or promotional messages from the notification 320, an action option 325, a web logo, and a channel number. In at least one embodiment, a black gradient mask can be applied over the program image 310 to enhance the legibility of the textual information.

Some client devices may be force-click enabled, which may allow a user to force a different option in a GUI. When you force a notification, you can display the action form. An example behavior in this state may include a hard click to obtain the following option: "Play on TV" (if the client device and the STB are close to each other, they can be enabled by the STB), "play on the phone" And "Program Information", which can start a media card. Another exemplary behavior in this state may include a hard click to obtain the following options: "Play on the phone" (such as when the STB is turned off or when the client device is not close to the STB) and "Program Information." A user tapping "Play on TV" can send a message to cause the program to be played on a television (eg, TV 102 of FIG. 1) to the STB. A user taps "Program Information" to access the media card of the item on the TV on the client device or via the STB.

FIG. 4 illustrates an example STB search GUI 400 and an example client GUI 450. When the STB is in proximity to the client device, such as when the STB is connected to the same network as the client device, a user can use one of the mobile devices on the client device as one of the input devices for the STB.

In one example, a user may be using an STB remote device to navigate the STB GUI. The user can navigate to an STB search GUI 400. In response to navigating to the STB search GUI 400, the STB may send a message indicating that the current state of the STB is at the STB search GUI 400 to the client device. The message may also include an instruction to cause the client device to present a client search GUI, and the client search GUI may include one or more input boxes and/or a virtual keyboard.

The client device can display some or all of the messages in a notification 455. The notification 455 can include text to enable the user to know that they can control the STB via the client device and/or provide input to the STB. After the notification 455 is initiated, the client device can immediately present a virtual keyboard.

FIG. 5 illustrates the example client GUI 450 of FIG. 4 and an example client search GUI 500. The example client search GUI 500 can include a search input box 505 and a virtual keyboard 510 that can be used to provide input to an STB. The example client search GUI 500 can be presented in response to a user pressing a touch screen of one of the user devices. The various behaviors of the virtual keyboard 510 can be as follows: tap any key to input an applicable letter or special character to the client device and cause the same result to be displayed on the search text input box on the STB; when on the user device When typing any letter in the search box, the "type" button switches to "OK" or a suitable label, and also displays a confirmation on the STB; tap the text to enter a "cancel" icon in the box. The letter can be deleted and the text can be reset by typing a box; tapping a "off" icon can eliminate the virtual keyboard 510. In at least one embodiment, the search results can be displayed on the STB and not on the client device. Alternatively or additionally, the search results can be displayed on both the STB and the client device. The virtual keyboard 510 can include a "typ" or "complete" or similar button that causes the STB to perform or confirm an action upon startup. If the user takes over control with his STB (such as via an STB remote device), the STB can send a message to cancel the virtual keyboard 510 to the client device.

FIG. 6 illustrates the example client GUI 450 of FIG. 4 and another example client search GUI 600. The example client search GUI 600 can include a search input box 605 and a virtual keyboard 510 that can be used to provide input to an STB. The example client search GUI 500 can be presented in response to a user tapping one of the touch screens of the client device.

There may be a variety of ways to activate virtual keyboard 510, depending on the button behavior, such as a hard click (e.g., press, hold) or tap notification to open virtual keyboard 510 within a media application. For example, a user receives a notification on their phone while they navigate to the STB search GUI 400 as illustrated in FIG. Selecting a notification activates a virtual keyboard 510, as illustrated in Figures 5 and 6. When the user provides input to the client device via the virtual keyboard 510, the text input can be simultaneously presented on the STB search GUI 400 and the client search GUI 600, as illustrated in FIG.

FIG. 8 illustrates an example STB password GUI 800 and an example client password GUI 850. For example, the STB password GUI 800 and the client password GUI 850 can request a password from the user. In one example, a user can navigate to the STB password GUI 800 requesting a user password. In response to the user navigating to the STB password GUI 800, the STB can send a message to the client device. The client device can display a notification to one of the messages. A user can respond by tapping the notification. In response, the client password GUI 850 can present a virtual keyboard 510. The user can tap any key to type the applicable letter or special character into the user device. The typed characters can be presented on the STB password GUI 800. In at least some embodiments, the STB password GUI 800 and the client password GUI 850 can obscure or hide the characters typed into the password field. After typing the correct password, a "typing" label on the virtual keyboard 510 and on the STB password GUI 800 can be switched to "complete". The user taps "Done" to eliminate the client password GUI 850 and the STB password GUI 800, and then proceeds to another GUI on the STB.

Figure 9 illustrates one of the example STB GUIs 900 for user name and password entry and one of the usernames and passwords for the user-side GUI 950. The client GUI 950 includes a virtual keyboard 510, a username input field 955, and a password entry field 960. As discussed, text entry to the client GUI 950 can be presented simultaneously at the STB GUI 900.

FIG. 10 illustrates another example STB GUI 1000 and corresponding client GUI 1050. The STB GUI 1000 can contain two or more than two input fields. As illustrated, the STB GUI 1000 includes a username entry field 1005 and a password entry field 1010. The client GUI 1050 can include a single input field 1055 and a virtual keyboard 510. The user can toggle between the user name input field 1005 and a password input field 1010, and can use a single input field 1055 to type text into the user name input field 1005 and a password input field. 1010.

FIG. 11A illustrates an exemplary client GUI 1100 having an interface tool set 1105 that can receive input from a set-top box. Interface tool set 1105 can include program pictures, a play icon, a program title, time information, a web logo and a channel, among other items. For example, when a content provider pushes a message, the client device can display an interface tool set 1105 that includes a program, a special event or promotion, a group of recommended items, or a static category recommendation (such as " Prime time or hot topics, etc.) and other information. The interface toolset 1105 can display a plurality of content items, each of which can be clicked to play the content item on the STB and/or on the client device. The user can expand the interface toolset 1105 to display more content or other categories. The GUI 1100 illustrates the media notification in a collapsed mode. FIG. 11B illustrates another example client GUI 1150 in which the interface toolset 1105 is in an expanded mode.

FIG. 12 illustrates an example client GUI 1100 with an interface tool set 1105 and different regions that may include a bootable boot tool. Any number of zones can include a launcher. As illustrated, the interface tool set 1105 includes two startup tools 1205 and 1210. The activation behavior of the interface tool set 1105 can include the user tapping the launch tool 1205 (which is illustrated by a "play" icon on the program picture). If the STB is turned on, the user can start the STB by tapping the startup tool 1205. Play the content of the upper interface tool set. If the interface tool set content video is not available, then one of the launch tools 1205 selects one of the media cards that can cause the client device to initiate entry into the project (eg, for a future event in which the user has previously set a reminder or Once scheduled events). The user taps the second activation tool 1210 (which is illustrated by a "play" icon on the program picture) to enable a media player, and if the STB is turned off, the interface tool set content is played. The user taps the second activation tool 1210 to enter the media card of the item. The interface toolset can also include a "show more" option. A user can click on "Show More" on the interface tool set 1105, which causes the interface toolset to expand to the bottom and show more content.

FIG. 13A illustrates an example client GUI 1300 that includes an interface tool set 1105 and different selectable options 1305. The interface tool set 1105 can be launched with a forced start input. After launching the interface toolset, such as with the launch tool 1205, the launch tool 1210, or another launch tool (eg, the "show more" launch tool on the interface toolset 1105), the client GUI 1300 can immediately present different selectable options. 1305. When the STB is turned on and the content is being played, the different selectable options 1305 can include a "watch on TV" option, a "watch on phone" option, a "program information" option, and a "remote control" option. Other selectable options are available. The action may include: the user taps "watch on TV", which causes the STB to play the program; the user taps "watch on the phone", which causes the user device to play the program; the user taps "program information" To view more information about the program; and the user taps "Remote Control" to initiate a remote control interface.

FIG. 13B illustrates an example client GUI 1350 including an interface tool set 1105 and different selectable options 1355 in the event that the client device is not close to the STB. When the STB is turned on and the content is being played, the different selectable options 1355 may include a "view here" option, a "program information" option, and a "remote control" option. Other selectable options are available. The behavior may include: the user taps "watch here", which causes the user device to play the program; the user taps "program information" to view more information about the program; and the user taps "remote control" Start with a remote control interface.

14-15 illustrate flow diagrams of various methods associated with device control using interactive notifications. The methods can be performed by processing logic, which can include hardware (circuitry, dedicated logic, etc.), software (such as software running on a computer system or a dedicated machine), or a combination of the two. It is included in the television 102, the STB 104, the client device 106, the content server 110, the account server 114, or another computer system or device. To simplify the explanation, the methods set forth herein are illustrated and described as a series of acts. However, the actions in accordance with the present invention can occur in various orders and/or concurrently, and occur with other acts not presented and described herein. In addition, not all illustrated acts may be required to implement a method according to the disclosed subject matter. In addition, those skilled in the art will understand and appreciate that the method can alternatively be represented as a series of associated states via a state diagram or event. Additionally, the methods disclosed herein can be stored on an article, such as a non-transitory computer readable medium, to facilitate the transport and delivery of such methods to a computing device. As used herein, the term article is intended to encompass a computer program that can be accessed from any computer-readable device or storage medium. Although illustrated as discrete blocks, individual blocks may be divided into additional blocks, combined into fewer blocks, or removed, depending on the desired implementation.

14 illustrates an exemplary flow diagram of one method for a set-top box to send a message to a client device and receive a message from a client device, the client device being executable in accordance with at least one of the items set forth in the present invention. The operating environment of Figure 1 configured in an embodiment.

Method 1400 can begin at block 1405, where processing logic can obtain a correlation between a client device and an auxiliary device. Obtaining the association between the client device and the auxiliary device may include adding the auxiliary device and the client device to a user account. In at least some embodiments, obtaining the association of the client device with the auxiliary device includes: searching for available devices on a network; discovering one or both of the auxiliary device and the client device on the network; and responding to the discovery One or both of the auxiliary device and the client device on the network associate the auxiliary device with the client device. In at least some embodiments, obtaining the association of the client device with the auxiliary device can include receiving a selection or confirmation of one of the associated client device and the auxiliary device.

At block 1410, the processing logic can identify one of the trigger events associated with one of the operations of the auxiliary device. In at least some embodiments, identifying a triggering event associated with operation of the auxiliary device can include receiving an input at the auxiliary device to perform an operation. The triggering event associated with the operation of the auxiliary device can include a time based event, an event based on the user state, or an event based on the location of the user device. In at least some embodiments, identifying a triggering event associated with operation of the auxiliary device includes: providing a selectable on-screen button on the auxiliary device to provide information to the auxiliary device using a keyboard on the user device; and receiving the pair One of the on-screen buttons can be selected to activate to provide information to the accessory using the keyboard on the client device.

At block 1415, processing logic may send a message to the client device in response to identifying the triggering event, the message having one of the information related to the operation of the auxiliary device. The client device can have a user interface configured to receive information. In at least some embodiments, transmitting the message to the client device can include identifying the client by identifying the client device to connect to the same network as the accessory device or by querying a user account for the associated device The device determines the location at which the message is sent to the client device. The message may include an instruction to cause the client device to provide an interactive notification via the user interface. The interactive notification can include at least one of an application name, an icon, and an image associated with operation of the auxiliary device.

At block 1420, processing logic can receive input related to the information from the client device. The information-related input can include at least one of a text input, a selection of a media item, a scroll, a reverse, a fast forward, a pause, a stop, or a play. In at least some embodiments, receiving information related input from the client device can include presenting information related input from the client device on an auxiliary device interface. In at least some embodiments, the information related input from the client device can be presented in the user interface at the accessory device interface and the client device at substantially the same time.

At block 1425, the processing logic can configure or cause the auxiliary device to perform operations at the auxiliary device using information related inputs from the client device. In at least some embodiments, configuring or causing the auxiliary device to perform an operation can include at least one of: typing an alphanumeric input in an auxiliary device interface; selecting a media item in the auxiliary device interface; Scrolling in the device interface; reversing media items; making media items fast; pausing media items; stopping media items; or playing media items.

With regard to this and other procedures and methods disclosed herein, the functions performed in such procedures and methods can be implemented in a different order. In addition, the steps and operations are merely provided as examples, and some of the steps and operations may be optional and combined into fewer steps without detracting from the nature of the disclosed embodiments. Operate or expand into additional steps and operations.

15 illustrates an exemplary flow diagram of one method of receiving a message from an auxiliary device by a client device, which may be implemented in the operating environment of FIG. 1 configured in accordance with at least one embodiment set forth in the present disclosure. .

Method 1500 can begin at block 1505, where processing logic can receive a message from an auxiliary device at a client device that includes a request for one of information related to operation of one of the auxiliary devices. In at least some embodiments, receiving information related to the notification via the graphical interface can include receiving an instruction to open an application or a media card associated with the notification.

At block 1510, processing logic can provide at least a portion of the message as a notification in a graphical interface via a display device. In at least some embodiments, providing at least a portion of the message in the graphical interface via the display device as the notification can include providing a media item to be played at the auxiliary device when the client device and the auxiliary device are connected to the network An option.

At block 1515, processing logic can receive input related to the information via the graphical interface. In at least some embodiments, the information-related input can include at least one of a text input, a selection of a media item, a scroll, a reverse, a fast forward, a pause, a stop, or a play. By. At block 1520, processing logic may send an information related input to the auxiliary device to perform the auxiliary device operation.

With regard to this and other procedures and methods disclosed herein, the functions performed in such procedures and methods can be implemented in a different order. In addition, the steps and operations are merely provided as examples, and some of the steps and operations may be optional and combined into fewer steps without detracting from the nature of the disclosed embodiments. Operate or expand into additional steps and operations.

16 illustrates a graphical representation of one of the machines in an exemplary form of a computing device 1600 in which a set of any one or more of the methods discussed herein for causing a machine to perform the methods discussed herein can be performed. instruction. The computing device 1600 can include a mobile phone, a smart phone, a mini notebook computer, a rack server, a router computer, a server computer, a personal computer, a large computer, a laptop computer, and a computer. A tablet, a desktop, etc., may execute within the computing device a set of instructions for causing the machine to perform any one or more of the methods discussed herein. In an alternate embodiment, the machine can be connected (e.g., networked) to a LAN, an internal network, an external network, or other machine in the Internet. The machine can operate as a server machine in a client-server network environment. The machine may comprise a personal computer (PC), a set-top box (STB), a server, a network router, a switch or a bridge or capable of performing (sequentially or in any other form) one of the actions specified to be taken by the machine Any machine that groups instructions. Moreover, although illustrated as a single machine, the term "machine" can also include any machine that individually or jointly performs a set (or sets) of instructions to perform any one or more of the methods discussed herein. set.

The example computing device 1600 includes a processing device (eg, a processor) 1602, a main memory 1604 (eg, read only memory (ROM), flash memory, dynamic random access such as synchronous DRAM (SDRAM). Memory (DRAM), a static memory 1606 (eg, flash memory, static random access memory (SRAM)), and a data storage device 1616 that communicate with each other via a bus 1608.

Processing device 1602 represents one or more general purpose processing devices, such as a microprocessor, central processing unit, or the like. More particularly, the processing device 1602 can include a Complex Instruction Set Computing (CISC) microprocessor, a Reduced Instruction Set Computing (RISC) microprocessor, a Very Long Instruction Word (VLIW) microprocessor, or one of the other instruction sets. A processor or processor that implements a combination of one of the instruction sets. Processing device 1602 can also include one or more special purpose processing devices, such as an application specific integrated circuit (ASIC), a programmable gate array (FPGA), a digital signal processor (DSP), a network processor, or And so on. Processing device 1602 is configured to execute instructions 1626 for performing the operations and steps discussed herein.

Computing device 1600 can further include a network interface device 1622 that can communicate with a network 1618. The computing device 1600 can also include a display device 1610 (eg, a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 1612 (eg, a keyboard), and a cursor control device 1614 (eg, a A mouse) and a signal generating device 1620 (eg, a speaker). In one embodiment, display device 1610, alphanumeric input device 1612, and cursor control device 1614 can be combined into a single component or device (eg, an LCD touch screen).

The data storage device 1616 can include a computer readable storage medium 1624 having stored thereon one or more sets of instructions 1626 (eg, software) embodying any one or more of the methods or functions set forth herein. ). The instructions 1626 may also reside entirely or at least partially within the main memory 1604 and/or the processing device 1602 during execution by the computing device 1600. The main memory 1604 and the processing device 1602 also constitute a computer readable medium. The instructions can be further transmitted or received over a network 1618 via the network interface device 1622.

Although the computer readable storage medium 1626 is shown as a single medium in an exemplary embodiment, the term "computer readable storage medium" can include storing one or more sets of instructions for a single medium or multiple media (eg, one Centralized or distributed repositories and/or associated caches and servers). The term "computer-readable storage medium" can also include any medium that can store, encode, or carry any one or more of the methods for executing a set of instructions by a machine and causing the machine to perform the invention. Thus, the term "computer readable storage medium" can be considered to include, but is not limited to, solid state memory, optical media, and magnetic media.

FIG. 17 illustrates an example architecture 1700 for providing a message to one or more devices in a platform-independent environment. The architecture 1700 can include a client 1702 that can communicate with a back end 1706 on a network 1704.

For example, the client 1702 can include any type of client device (including the client device 106 of FIG. 1), and the client 1702 can also include an STB/application 1708, an iOS® or Android® based client device. 1710 or an STB 1712. Client device 1702 can communicate with backend 1706 with or without a push notification service (PNS) 1714 (eg, Apple® PNS, Google Cloud Messaging®, etc.). Client device 1702 can communicate with backend 1706 with or without an agent 1716 (e.g., a proxy server, a reverse proxy).

Backend 1706 can include a cross-platform runtime environment 1720, such as Node.js. The cross-platform runtime environment 1720 can use and support any number of protocols (eg, agreement 1, agreement n, agreement n+1). The cross-platform runtime environment 1720 can be coupled to a data store 1722, such as an in-memory data structure storage device (eg, redis).

Backend 1706 can also include a message broker 1724 that can be coupled to any number of backend clients 1726. The message broker can also be coupled to a group management suite (GRM) 1728. The GRM 1728 can receive a request to add, delete, or update a group definition or a client management parameter. In response to the request, GRM 1728 can add, delete, or update group definitions or client management parameters. The GRM 1728 can be coupled to a data store 1730. In at least one embodiment, GRM 1728 and/or storage 1732 can be coupled to an agent 1732.

The cross-platform runtime environment 1720 can receive input from a first client device (e.g., client device 1710) and can send input to the cross-platform runtime environment 1720 via the network 1704. In at least one embodiment, the first client device can send input via PNS 1714 and/or proxy 1716. In at least one embodiment, the input can be provided in accordance with a first agreement (e.g., agreement 1) or in a format of a first agreement (e.g., agreement 1). The cross-platform runtime environment 1720 can translate or convert the input into a second agreement that is compatible with a second client device (eg, an auxiliary device, STB 1712). The cross-platform runtime environment 1720 can send the input as a message 1740 to the second client device.

FIG. 18 illustrates an example flow diagram 1800 of an interactive notification. A triggering event can occur at an STB 1805 (which can be the same or similar to STB 104 of Figure 1). For example, the triggering event can include a user logging into the STB 1805 using an account. As part of the triggering event or in response to the triggering event, the STB 1805 can send a message to a web service 1810. The web service 1810 can include any web-based service that can receive messages and can coordinate the provision of interactive notifications.

The web service 1810 can identify one of the push notification services 1815 that can be used to send a message to a client device 1820 (which can be the same as or similar to the client device 106 of FIG. 1). The web service 1810 can forward the message to the push notification service 1815. The web service 1810 can also change, modify, or add to the message before sending it to the push notification service 1815. The push notification service 1815 can send a message to the client device 1820. The message may contain a request for one of the information related to the operation of the STB 1805.

Client device 1820 can include a client device interface configured to present a message and receive input related to the message. In response to receiving input via the client device interface, the client device 1820 can send the input to a CAF module 1825, which can then send the input to the STB 1805. Alternatively or in addition, the client device 1820 can send the input directly to the STB 1805. In this manner, an interactive notification (eg, a message) can be sent to the client device 1820, and the input related to the interactive notification can be received at the client device 1820 and sent to the STB 1805.

Figure 19 illustrates a sequence diagram 1900 of one of the program flows of an interactive notification. 19 may include STB 1805 of FIG. 18, web service 1810, push notification service (PNS) 1815, client device 1820, and CAF module 1825.

At 1905, a user of the client device 1820 can initiate an application on the client device 1820. At 1910, the user can press one of the buttons on one of the remote controls of the STB 1805. At 1915, the STB can subscribe to the message of the CAF module 1825. For example, using one of the user interfaces of the STB 1805, a user can select one of the options for subscribing to the CAF module 1825. In at least one embodiment, the user can register an account to automatically subscribe the user account to the CAF module 1825.

At 1920, a triggering event (such as any triggering event) may cause the STB 1805 to send a message to the web service 1810. At 1925, web service 1810 can send a message to PNS 1815. At 1930, the PNS 1815 can send a message to the client device 1820. At 1935, the client device 1820 can display or present the message as an interactive notification. At 1940, the client device 1820 can receive input from the user via a client device interface. At 1945, the client device can send the input to the CAF module 1825.

At 1950, the CAF module 1825 can send an input to the STB 1805. In at least one embodiment, the CAF module 1825 can reformat the data, supplement the material, or input the data to an input, such as an advertisement, recommendation material, and the like.

At 1955, the STB 1805 can display input via an STB interface. In an example, the input can include text for a search field. The client device 1820 can receive the text for searching for the field and send the text for the search field to the CAF module 1825. The CAF module 1825 can send the text for the search field to the STB 1805. The STB 1805 displays the text used to search for fields in the search field.

In the present specification, a detailed description has been given with reference to specific exemplary embodiments. It will be apparent, however, that various modifications and changes can be made in the present invention without departing from the spirit and scope of the invention. Therefore, the specification and drawings are to be regarded as illustrative and not restrictive. In addition, the use of the embodiments and other exemplary language does not necessarily refer to the same embodiment or the same examples, but may refer to different and different embodiments and potentially the same embodiments.

The following examples are related to other embodiments.

In one aspect, a method includes obtaining, by an auxiliary device, a correlation between a client device and the accessory device. The method further includes identifying, by the auxiliary device, one of the trigger events associated with operation of one of the auxiliary devices. The method further includes, in response to identifying the triggering event, by the auxiliary device transmitting, via a network, a message having a request for information related to the operation of the auxiliary device to the client device. The client device can have a client device interface configured to present the message and receive an input related to the message. The method further includes receiving, by the auxiliary device, input related to the information from the client device via a network. The input is received via the client device interface in response to one of the messages being presented. The method further includes configuring the auxiliary device to perform the operation at the auxiliary device using the input received from the client device.

The association of the client device with the accessory device can include a user account associated with the accessory device and the client device. The association of the client device with the auxiliary device can include an association based on one of the discovery of the client device and the auxiliary device on a same network. The association of the client device with the auxiliary device may be based on a determination of one of the locations of the client device. Identifying the triggering event associated with the operation of the auxiliary device can include receiving, at the auxiliary device, a request to perform the operation. The triggering event associated with the operation of the auxiliary device can include a time based event, a user state based event, or an event based on the location of the client device. The method may further include: in response to identifying the triggering event, providing an optional on-screen element via the auxiliary device via one of the auxiliary device interfaces; and in response to activation of one of the selectable on-screen elements The message from the auxiliary device having the request for the information related to the operation of the auxiliary device is sent to the client device via the network. Sending the message to the client device can include configuring the accessory to receive the input entered in the client device interface in response to receiving the message. The input can include at least one of a text input, a selection of a media item, a scroll, a reverse, a fast forward, a pause, a stop, or a play.

Performing the operation at the auxiliary device using the input from the client device can include at least one of: typing an alphanumeric input in an auxiliary device interface; selecting a media item in the auxiliary device interface; Scrolling in the auxiliary device interface; reversing the media item; making the media item fast forward; pausing the media item; stopping the media item; or playing the media item. Receiving the input from the client device via the network can include presenting the input from the client device in an auxiliary device interface. The input from the client device can be presented in the accessory device interface and the client device interface at substantially the same time. The message can include an instruction to cause the client device to provide an interactive notification via the client device interface. The auxiliary device may comprise one of a set-top box, a smart device, an audio/video controller or a gaming system.

In one aspect, a method includes receiving, at a client device, a message associated with an auxiliary device, the message including a request for one of information related to operation of one of the auxiliary devices. The method further includes providing at least a portion of the message as a notification to a graphical interface via a display device. The method further includes receiving an input related to the information via the graphical interface. The method further includes transmitting the input related to the information to the auxiliary device via a network to perform the auxiliary device operation.

Receiving the information related to the notification via the graphical interface can include receiving an instruction to open an application or a media card associated with the notification. Providing at least a portion of the message as the notification to the graphical interface via the display device can include providing a media to play at the auxiliary device when the client device and the auxiliary device are connectable to the network One of the options for the project. The information may include at least one of a text input, a selection of a media item, a scroll, a reverse, a fast forward, a pause, a stop, or a play.

In one aspect, a non-transitory computer readable medium encoded with a program code executable by a processor to perform an operation or control operation, the operations including any of the operations set forth above One.

In one aspect, a system includes a memory and a processing device operatively coupled to the memory, the processing device configured to perform an operation or control operation, the operations including the Any of the operations.

In one aspect, a non-transitory computer readable medium, wherein a coded code executable by a processor to perform an operation or control operation is encoded, the program code being used to identify one of an auxiliary device One of the actions related to the trigger event. The program code executable by the processor to perform an operation or control operation is used to obtain a correlation between a client device and the auxiliary device by the auxiliary device. The program code executable by the processor to perform an operation or control operation for responding to the triggering event by the auxiliary device via a network to have information related to the operation of the auxiliary device A request message is sent to the client device. The client device can have a client device interface configured to present the message and receive an input related to the message. The program code executable by the processor to perform an operation or control operation is configured to receive input related to the information from the client device via the network via the auxiliary device. The input is received via the client device interface in response to one of the messages being presented. The program code executable by the processor to perform an operation or control operation to cause the operation to be performed at the auxiliary device using the information from the client device.

Identifying the triggering event associated with the operation of the auxiliary device can include receiving an input at the auxiliary device to perform the operation. Enabling the use of the information from the client device to perform the operation at the auxiliary device can include at least one of: typing an alphanumeric input in an auxiliary device interface; selecting a media item in the auxiliary device interface Scrolling in the auxiliary device interface; reversing the media item; making the media item fast forward; pausing the media item; stopping the media item; or playing the media item.

The terms used herein, and especially in the scope of the accompanying claims (e.g., the subject matter of the accompanying claims) are generally intended to be "open" (for example, the term "including" can be interpreted as "including. Without being limited to, the term "having" may be interpreted as "having at least" and the term "includes" may be interpreted as "including but not limited to".

In addition, if an intention is made to claim a specific number of patents, the intent is expressly stated in the scope of the claims, and without this statement, the intent is not. For example, as an aid to one of the following, the scope of the accompanying claims may include the use of the introductory phrase "at least one" and "one or more" to introduce the scope of the patent application. statement. However, the use of these phrases is not to be construed as implying that the indefinite article "a" or "an" is used to claim any claim. The scope is limited to the embodiment containing only one such statement, even when the same patent application scope includes the introductory phrase "one or more" or "at least one" and such as "a (a)" or "an" The indefinite article (for example, "a" or "an" can be interpreted to mean "at least one" or "one or more"; the same applies to the application. Use of the definite article of the patent scope statement.

In addition, even if a particular number of statements in the scope of the patent application is explicitly stated, those skilled in the art will recognize that this statement can be construed to mean at least the stated number (for example, without other modifiers) An unmodified statement of "two statements" means at least two statements or two or more than two statements). Further, in the examples in which one of the conventions of "at least one of A, B, and C, etc." is used, in general, the configuration is intended to include only A, only B, only C, A and B together, A together with C, B with C or A, B and C together. For example, the use of the term "and/or" is intended to be interpreted in this manner.

In addition, any one of the two or more alternative terms, whether expressed in the specification, in the scope of the claims, or in the drawings, is understood to include one of the terms. The possibility of either or both of these terms. For example, the phrase "A or B" can be understood to include the possibility of "A" or "B" or "A and B".

Embodiments set forth herein may be implemented using a computer readable medium for carrying or having computer executable instructions or data structures stored thereon. Such computer readable media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may comprise non-transitory computer-readable storage media, non-transitory computer-readable storage media including random access memory (RAM), read-only memory (ROM) ), electrically erasable programmable read only memory (EEPROM), compact disc read only memory (CD-ROM) or other optical disc storage, disk storage or other magnetic storage device, flash memory device (e.g., a solid state memory device), or any other storage medium that can be used to carry or store the desired code in the form of computer executable instructions or data structures accessible by a computer. Combinations of the above may also be included within the scope of computer readable media.

For example, machine-executable instructions can include instructions and materials that cause a computer, special purpose computer, or special purpose processing device (eg, one or more processors) to perform a particular function or group of functions. Although the subject matter has been described in language specific to structural features and/or methods, it is understood that the subject matter defined in the appended claims Instead, the specific features and acts set forth above are disclosed as example forms of the scope of the patent application.

As used herein, the term "module" or "component" may refer to a particular hardware implementation configured to perform the operation of a module or component and/or hardware that can be stored in a computing system (eg, a computer) A soft object or software routine is executed on and/or by a hardware (eg, computer readable medium, processing device, etc.) of the computing system. In some embodiments, the various components, modules, engines, and services set forth herein can be implemented as objects or programs that execute on a computing system (eg, as a separate thread). Although some of the systems and methods described herein are generally described as being implemented in software (stored on hardware and/or executed by hardware), specific hardware implementations or software and specific hardware implementations A combination of the options is also possible and covered. In this description, a "computing entity" can be any computing system as previously defined herein or any combination of modules or modules running on a computing system.

All of the examples and conditional language set forth herein are intended to be used for teaching purposes to assist the reader in understanding the present invention and the inventor's contribution to the teachings of the present invention, and should not be construed as limiting the examples and conditions. Although the embodiments of the present invention have been described in detail, it is understood that various modifications, changes and changes may be made in the invention without departing from the spirit and scope of the invention.

100‧‧‧Example operating environment

102‧‧‧TV

104‧‧‧Machine box

106‧‧‧User device/child device

108‧‧‧Network

110‧‧‧Content Server

112‧‧‧Data storage

114‧‧‧Account Server

116‧‧‧User device/Dad's phone

120‧‧‧Applications/Media Apps

122‧‧‧Activity Manager

200‧‧‧Executive client-side graphical user interface/graphical user interface

205‧‧ Notice

210‧‧‧Notice

250‧‧‧ graphical user interface

255‧‧‧Notice

305‧‧‧Action Form

310‧‧‧Program image

315‧‧‧Program title

320‧‧‧Notice

325‧‧‧Action options

400‧‧‧Executive set-top box search graphical user interface/set-up box search graphical user interface

450‧‧‧Executive client-side graphical user interface

455‧‧ Notice

500‧‧‧Instance client search graphical user interface

505‧‧‧Search input box

510‧‧‧Virtual keyboard

600‧‧‧ Instance-based client search graphical user interface / client search graphical user interface

605‧‧‧Search input box

800‧‧‧Instance on-board box password graphic user interface/set-up box password graphic user interface

850‧‧‧Instance Client Password Graphic User Interface/Client Password Graphic User Interface

900‧‧‧Executive set-top box graphic user interface / set-top box graphic user interface

950‧‧‧ corresponding to the user-side graphical user interface / client-side graphical user interface

955‧‧‧user name input field

960‧‧‧ password input field

1000‧‧‧Executive set-top box graphic user interface / set-top box graphic user interface

1005‧‧‧user name input field

1010‧‧‧ password input field

1050‧‧‧ corresponding to the user-side graphical user interface / client-side graphical user interface

1055‧‧‧Input field

1100‧‧‧Executive client-side graphical user interface/graphical user interface

1105‧‧‧Interface toolset

1150‧‧‧Executive client-side graphical user interface

1205‧‧‧Startup tool

1210‧‧‧Starting tool/second starter

1300‧‧‧ Instance-based client-side graphical user interface/user-side graphical user interface

1305‧‧‧ different options

1350‧‧‧Executive client-side graphical user interface

1355‧‧‧ different options

1400‧‧‧ method

1405‧‧‧ square

1410‧‧‧ square

1415‧‧‧ square

1420‧‧‧ square

1425‧‧‧ square

1500‧‧‧ method

1505‧‧‧ square

1510‧‧‧ square

1515‧‧‧ square

1520‧‧‧ square

1600‧‧‧Computational Devices/Instanceal Computing Devices

1602‧‧‧Processing device

1604‧‧‧ main memory

1606‧‧‧ Static memory

1608‧‧‧ Busbar

1610‧‧‧Display device

1612‧‧‧Text input device

1614‧‧‧ cursor control device

1616‧‧‧Data storage device

1618‧‧‧Network

1620‧‧‧Signal generator

1622‧‧‧Network interface device

1624‧‧‧Computer-readable storage media

1626‧‧‧ directive

1700‧‧‧Instance Architecture/Architecture

1702‧‧‧User/Client devices

1704‧‧‧Network

1706‧‧‧ Backend

1708‧‧‧Set-top box/application

1710‧‧‧Customer device

1712‧‧‧Set-top box

1714‧‧‧Feed notification service

1716‧‧‧Agent

1720‧‧‧Cross-platform runtime environment

1722‧‧‧Data storage

1724‧‧‧Information broker

1726‧‧‧Backend client

1728‧‧‧Group Management Suite

1730‧‧‧Data storage

1732‧‧‧Agent

1740‧‧‧Message

1800‧‧‧Example flow chart

1805‧‧‧Set-top box

1810‧‧‧web service

1815‧‧‧Feed notification service

1820‧‧‧Customer device

1825‧‧‧CAF module

1905‧‧‧ operation

1910‧‧‧ operation

1915‧‧‧ operation

1920‧‧‧ operation

1925‧‧‧ operation

1930‧‧‧ operation

1935‧‧‧ operation

1940‧‧‧ operation

1945‧‧‧ operation

1950‧‧‧ operation

1955‧‧‧ operation

The exemplary embodiments will be explained and illustrated with additional specificity and details in the drawings,

1 is a block diagram of an exemplary operating environment in which certain embodiments may be implemented;

2A illustrates an exemplary client graphical user interface (GUI) having at least one message received from an auxiliary device;

2B illustrates a GUI having a notification on the client device when the client device is in use;

Figure 3 illustrates an example GUI having an action form for one of the media items;

4 illustrates an exemplary set-top box search GUI and an example client GUI;

Figure 5 illustrates the example client GUI of Figure 4 and an example client search GUI;

6 illustrates the example client GUI of FIG. 4 and another example client search GUI;

Figure 7 illustrates another example client user interface having a virtual keyboard that simultaneously updates one of the user interfaces associated with a set-top box;

Figure 8 illustrates an exemplary set-top box password GUI and an exemplary client-side password GUI;

Figure 9 illustrates an example set-top box GUI for user name and password entry and one of the user-side GUIs for user name and password entry;

Figure 10 illustrates another example set-top box GUI and corresponding client-side GUI;

11A illustrates an exemplary client GUI having an interface tool set that can receive input from a set-top box;

11B illustrates another example client GUI in which the interface toolset is in an expanded mode;

Figure 12 illustrates an example client GUI with an interface tool set that can include a launch tool and different regions;

Figure 13A illustrates an exemplary client GUI including an interface tool set and different selectable options;

Figure 13B illustrates an example client GUI including an interface tool set and different selectable options in the event that the client device is not in proximity to a set-top box;

14 illustrates an exemplary flow chart of one method for a set-top box to send a message to a client device and receive a message from a client device;

Figure 15 illustrates an exemplary flow chart of one method of receiving a message from a set-top box by a client device;

16 illustrates a graphical representation of one of the machines in an exemplary form of a computing device in which a set of instructions for causing a machine to perform any one or more of the methods discussed herein may be performed. ;

17 illustrates an example architecture for providing a message to one or more devices in a platform-independent environment;

Figure 18 illustrates an example flow diagram of an interactive notification;

Figure 19 illustrates a sequence diagram of one of the program flows of an interactive notification.

Claims (20)

A method comprising: obtaining, by an auxiliary device, a correlation between a client device and one of the auxiliary devices; identifying, by the auxiliary device, a trigger event associated with operation of one of the auxiliary devices; responding to identifying the Triggering an event by the auxiliary device transmitting, via a network, a message having a request for information related to the operation of the auxiliary device to the client device, the client device having a configuration configured to present the message And receiving, by the user device, an input of the user equipment interface, wherein the input device receives an input related to the information via the network, wherein the input is responsive to the user equipment interface One of the messages is presented and received; and the auxiliary device is configured to perform the operation at the auxiliary device using the input received from the client device. The method of claim 1, wherein the association of the client device with the auxiliary device comprises a user account associated with the auxiliary device and the client device. The method of claim 1, wherein the association between the client device and the auxiliary device comprises: associating one of the ones on the same network based on both the client device and the auxiliary device. The method of claim 1, wherein the association of the client device with the auxiliary device is based on determining one of the locations of the client device. The method of claim 1, wherein the identifying the triggering event associated with the operation of the auxiliary device comprises receiving, at the auxiliary device, a request to perform the operation. The method of claim 1, wherein the triggering event associated with the operation of the auxiliary device comprises a time-based event, an event based on a user state, or an event based on a location of the user device. The method of claim 1, further comprising: responsive to identifying the triggering event, by the auxiliary device providing an optional on-screen element via one of the auxiliary device auxiliary device interfaces; and responding to the selectable on-screen element And initiating, by the auxiliary device, the message having the request for the information related to the operation of the auxiliary device is sent to the client device via the network. The method of claim 1, wherein the transmitting the message to the client device comprises configuring the accessory to receive the input entered in the client device interface in response to receiving the message. The method of claim 1, wherein the input comprises at least one of a text input, a selection of a media item, a scroll, a reverse, a fast forward, a pause, a stop, or a play. The method of claim 1, wherein the performing the operation at the auxiliary device using the input from the client device comprises at least one of: typing an alphanumeric input in an auxiliary device interface; at the auxiliary device Selecting a media item in the interface; scrolling in the auxiliary device interface; reversing the media item; making the media item fast forward; pausing the media item; stopping the media item; or playing the media item. The method of claim 1, wherein receiving the input from the client device via the network comprises presenting the input from the client device in an auxiliary device interface. The method of claim 12, wherein the input from the client device is presented in the accessory device interface and the client device interface at substantially the same time. The method of claim 1, wherein the message includes an instruction to cause the client device to provide an interactive notification via the client device interface. The method of claim 1, wherein the auxiliary device comprises one of a set-top box, a smart device, an audio/video controller, or a gaming system. A method, comprising: receiving, at a client device, a message associated with an auxiliary device, the message including a request for one of information related to operation of one of the auxiliary devices; at least the message is displayed via a display device The portion is provided as a notification in a graphical interface; the input related to the information is received via the graphical interface; and the input related to the information is sent to the auxiliary device via a network to perform the auxiliary device operation. The method of claim 14, wherein the receiving the message associated with the auxiliary device comprises: receiving an instruction to open an application or a media card associated with the notification, wherein the at least part of the message is Providing the notification in the graphical interface includes providing the application or a media card in the graphical interface via the display device. The method of claim 14, wherein the providing, by the display device, the at least part of the message as the notification in the graphical interface comprises: providing, when the client device and the auxiliary device are connected to the network One of the options for playing a media item at the auxiliary device. A non-transitory computer readable medium encoded with a program code executable by a processor to perform an operation or control operation, the operations comprising: identifying, by an auxiliary device, an operation associated with an auxiliary device a triggering event; obtaining, by the auxiliary device, a relationship between the client device and the auxiliary device; in response to identifying the trigger event, the auxiliary device via the network will have the pair and the auxiliary device One of the operational related information requests a message to the client device having a client device interface configured to present the message and receive an input associated with the message; Receiving, by the network device, input related to the information from the client device, wherein the input is received via the user device interface in response to one of the messages; and causing the information received from the user device to be used This operation is performed at the auxiliary device. The non-transitory computer readable medium of claim 18, wherein the identifying the triggering event associated with the operation of the auxiliary device comprises receiving, at the auxiliary device, a request to perform the operation. The non-transitory computer readable medium of claim 18, wherein causing the input from the client device to perform the operation at the auxiliary device comprises at least one of: typing in an auxiliary device interface Digital input; selecting a media item in the auxiliary device interface; scrolling in the auxiliary device interface; reversing the media item; making the media item fast forward; pausing the media item; stopping the media item; or playing the media project.