MODES

FIELD OF THE INVENTION

[0002] The present invention is related generally to computer communications and, more particularly, to interactive television.

BACKGROUND OF THE INVENTION

[0003] As personal communications devices (e.g., cell phones) are developed to support greater and greater functionality, people are using them to do much more than talk. As is well known, these devices now usually allow their users to create media files (e.g., by taking a picture or by recording a video using a camera on the device), to download media files from remote servers (via a web interface supported by the device), and to access interactive applications.

[0004] However, even as people spend more time online, traditional media remain very important. Indeed, rather than simply replacing traditional media time with online time, many people are beginning to "multi-task," that is, to combine traditional and new media. For example, while they watch television, their personal communications device becomes a "companion device" displaying content often, but not always, related to the content shown on their television. Similarly, while they are engaged in an interactive application on their companion device, they remain at least peripherally aware of the content that the television is displaying.

[0005] Televisions and companion devices are not designed to optimize the same type of user interactions. Terminology reflects this distinction: Television programming is aimed at "viewers," while companion devices invite "users." That is, television programming is designed, for the most part, to be passively watched while the viewer "leans back" on his couch. Companion devices, supporting fully interactive applications, invite users who "lean forward" to more actively interact with the applications. BRIEF SUMMARY

[0006] The above considerations, and others, are addressed by the present invention, which can be understood by referring to the specification, drawings, and claims. The present invention monitors a user's activities to determine how much attention he is paying to one or more devices (e.g., a television and a companion device such as a smart phone, tablet computer, or game console). Based on the information gathered about the user's current "attention profile," a "user-interaction parameter" is set that reflects where the user's attention is focused and, ideally, how much of his attention is given to each device. Then, based on the user-interaction parameter, the user interface of at least one of the user's devices is configured to optimize the user's interactions, given the amount of attention he is currently giving to this user interface.

[0007] Many types of information may be used in setting the user-interaction parameter including an explicit setting by the user, a history of the user's interactions with various devices, and the user's recent interactions with the devices.

[0008] If the user is giving the majority of his attention to the television, for example, then the user interface of the companion device can be configured to emphasize the types of interactions available to a user who is not actively watching the companion device. That is, a touch or motion sensor could be emphasized over a keypad for user input. The screen presentation could be made less rich with fewer, but potentially brighter, icons to catch the user's eye if appropriate.

[0009] When, in contrast, the user's attention is mostly given to the companion device, that device's user interface could be configured to emphasize richer and more precise inputs and outputs such as a keyboard and a screen display presenting more detailed information.

[0010] When a user device receives media content (e.g., an advertisement or e-mail), the device's display of that content depends upon the user-interaction parameter. The device can even select content to display (or an application to run) based on the user's current attention profile.

[0011] Several device types are contemplated that embody aspects of the present invention. Some user devices are sophisticated enough to gather attention-profile information, set the user-interaction parameter, and then respond to the setting appropriately. Other devices may not be able to set the user-interaction parameter but can respond appropriately if another device sends it the parameter. If a remote server is told the parameter (and possibly other related information), it can respond by sending appropriate content (or a command) to the user's devices. Another type of remote server can gather attention-profile information from the user's devices and determine the user- interaction parameter itself. Devices of all of these types, and others, can work together to enhance the usefulness of the present invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0012] While the appended claims set forth the features of the present invention with particularity, the invention, together with its objects and advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which:

[0013] Figure 1 is an overview of a representational environment in which the present invention may be practiced;

[0014] Figure 2 is a generalized schematic of some of the devices shown in Figure 1;

[0015] Figures 3 a and 3b together form a flowchart of a representative method for an end-user device that sets the user-interaction parameter;

[0016] Figure 4 is a flowchart of a representative method for an end-user device that responds to a user-interaction parameter sent to it; [0017] Figure 5 is a flowchart of a representative method for a server that responds to a user-interaction parameter sent to it; and

[0018] Figure 6 is a flowchart of a representative method for a server that sets the user-interaction parameter.

DETAILED DESCRIPTION

[0019] Turning to the drawings, wherein like reference numerals refer to like elements, the invention is illustrated as being implemented in a suitable environment. The following description is based on embodiments of the invention and should not be taken as limiting the invention with regard to alternative embodiments that are not explicitly described herein.

[0020] Aspects of the present invention may be practiced in the representative communications environment 100 of Figure 1. Connected together via any or all of various known networking technologies 102 are servers 104, 106. Some of these servers 104, 106 may head-end a cable-television delivery system 110. Others may be web servers. For ease of illustration, only two servers 104, 106 are shown, but numerous servers 104, 106 can exist and can work together, as discussed below.

[0021] Head-end servers provide, via the networking technologies 102, media- download and television services to end-user devices. One example of an end-user device is a cellular telephone 108. This telephone 108 communicates wirelessly to a wireless base station (not shown but known in the art) to access the public switched telephone network, the Internet, or other networks to access the services provided by the head-end server and by web servers.

[0022] Non-wireless end-user devices are supported by "wireline" network technologies (e.g., fiber, wire, and cable) 110. For example, a set-top box 112 generally receives television programming from a head-end server and provides a user interface (e.g., an interactive program guide) for selecting and viewing content from the head-end server. A digital video recorder (not shown) can store programming for later viewing. Video content may be viewed on a television monitor 114. In some situations, a laptop computer 116 accesses web-based services either wirelessly or via the wireline network 110. A home gateway, kiosk, digital sign, or media-restreaming device (not shown) are other possible end-user devices.

[0023] (A media-restreaming device transfers content between disparate types of networks. For example, it receives content from a cable system 110 and then transmits that content over a local radio link such as WiFi to the cellular telephone 108. The media- restreaming device usually operates in both directions to carry messages between the networks. In some embodiments, aspects of the present invention are practiced by a media-restreaming device.)

[0024] A user may split his attention by interacting with any or all of the end-user devices 108, 112, 114, 116 at roughly the same time or in a temporally overlapping manner. Examples in the present discussion usually assume that the user is watching the television monitor 114 and possibly interacting with it through the set-top box 112. At least occasionally, some of the user's attention is also given to the smart phone 108.

[0025] Some of the end-user devices are sophisticated enough to gather information about the user's attention-profile, set an user-interaction parameter that represents that profile, and then respond to the setting appropriately. For purposes of the present discussion, these devices are called "Class A" devices, and, in a purely arbitrary assignment, the smart phone 108 is taken as representative of this class. (The flowchart of Figure 3 and the accompanying discussion illustrate the workings of a Class A device.)

[0026] Other end-user devices may not be able to set the user-interaction parameter but can respond appropriately if another device sends it the parameter. Again for purposes of the present discussion, these are called "Class B" devices, and the set-top box 112 is used to represent this class (illustrated by Figure 4). Yet other end-user devices can neither set the user-interaction parameter nor respond to it. Still, these prior art "Class C" devices are important in the communications environment 100 because they can take up some of the user's attention. The television monitor 114 is here portrayed as a Class C device.

[0027] "Class Y" servers, if told the user-interaction parameter (and possibly other related information), can respond by sending appropriate content (or a command) to the user's devices. (Server 104 represents Class Y which is illustrated by Figure 5.) A server that can gather attention-profile information from the end-user devices 108, 112, 114, 116 and determine the user-interaction parameter itself is a "Class Z" device and is illustrated by Figure 6.

[0028] Note that the distinctions between classes of devices, while useful for illustrating aspects of the present invention, are not so clear cut in the real world. A device may operate in one class in some situation and in other class in other situations.

[0029] Devices of all of these types, and others, can work together to enhance the usefulness of the present invention.

[0030] Figure 2 shows the major components of a representative server 104, 106 or end-user device 108, 112, 114, 116. Network interfaces 200 send and receive media presentations, related information, and download requests. A processor 202 controls the operations of the device and, in particular, supports aspects of the present invention as illustrated in Figures 3 through 6, discussed below. The user interface 204 supports a user's (or administrator's) interactions with the device. Specific uses of these components by specific devices are discussed as appropriate below.

[0031] Figure 3 presents a method for a Class A end-user device to set and use the user-interaction parameter. In step 300 of Figure 3a, the end-user device 108 collects information about the amount of attention that the user is currently giving to this device 108. Some of this information can be generated by the device 108 itself. If, for example, the device 108 detects a significant amount of interaction with its user interface 204 (e.g., a number of keystrokes entered during the past minute), then the user is paying significant attention to the device 108. Historical information or a user profile can also be useful here. In some embodiments, the user can explicitly set an attention parameter, e.g., by moving a software "slider" presented by the user interface 204: The slider gives the user's estimation of how much attention he is paying to each of two (or more) user devices.

[0032] The slider can, in fact, be used to override the other information gathered about the user's current attention profile. That is, with the slider the user can direct the end-user device 108 to act as if he is splitting his attention in a given way, regardless of whether he is actually doing so. (This same overriding effect can be achieved by the user setting preferences or a policy.) Reasons why a user would like to do this are discussed below in relation to step 306 where the user-interaction parameter is used.

[0033] In step 300, the device 108 may also receive information from "off the device" 108 itself. If, for example, the set-top box 112 notes that the user is actively interacting with an electronic program guide presented on the television monitor 114, the set-top box 112 can send this information to the device 108. A camera on any of the end- user devices 108, 112, 114, 116 may see the user's eyes and note where he is looking. Even when no such direct information is available, indirect information can help. For example, the set-top box 112 reports that, responding to a previous command from the user, it is rendering a movie on the television monitor 114. Online ratings show that the current scene is considered by many people to be very exciting. When this information is made available to the end-user device 108, that device 108 may conclude, in the absence of any countervailing information, that the user's attention is probably focused on the monitor 114. In sum, any information that can be used to determine, or even speculate about, the user's attention profile can be used in step 300.

[0034] The end-user device 108 gathers in step 302 information about the amount of attention the user is paying to a device (or devices) other than the end-user device 108. Again, any type of information that is obtainable and that may be useful is pertinent here. Even "negative" information may have a place. If, for example, the device 108 has not received any information recently that the user is focusing any attention on it, then it might assume that the user is focusing his attention on the television monitor 114. Of course, negative information is usually very weak, as the user might not be paying any attention to any of the end-user device 108, 112, 1 14, 116. In many situations, the end- user device 108 when applying the method of Figure 3 does the best it can with limited information.

[0035] Based on all of the information it has been able to gather in steps 300 and 302, the end-user device 108 sets the user-interaction parameter in step 304. In the simplest scenario with only two devices 108, 114, the end-user device 108 may, if the gathered information does not contradict this, assume that the user's entire attention is divided between these two devices 108, 114. As mentioned above, this simple assumption can be incorrect as when the user is not paying much attention to any of the end-user devices 108, 112, 114, 116. That is, the user may be giving much or all of his attention to an "uninstrumented" Class C device, but there is not enough information for the end-user device 108 to determine that this is the case.

[0036] With more information or more devices, the end-user device 108 can create a multi-dimensional user-interaction parameter that represents how the user's attention is spread to multiple devices. The quality of the user-interaction parameter is based on the quality and amount of information gathered and especially on the number of end-user devices 108, 112, 114, 116 that contribute some information.

[0037] After doing the best job it can in setting the user-interaction parameter in step 304, the end-user device 108 uses that parameter in step 306 to configure its user interface 204 in some manner thought to be appropriate for the amount of attention that the user is currently giving to the device 108. Many variations are possible here, and a few examples serve to illustrate a range of possibilities.

[0038] Consider first the situation where, as far as the end-user device 108 can determine, the entirety of the user's attention is divided between the television monitor 114 and the smart phone 108. The user-interaction parameter can then be a one- dimensional quantity, even, in the simplest case, a one-bit quantity that says whether the bulk of the user's attention is on the monitor 114 or the phone 108. If the user is primarily focused on the monitor 114, then this is the classic "lean-back" scenario. That is, the user is "leaning back" into his couch and watching television. In this case, the user interface 204 of the phone 108 can be made very simple so as not to distract the user. The user interface 204 of the phone 108 is configured to emphasize inputs that the user can comfortably use without taking his primary attention away from the monitor 114. These inputs can include a motion sensor (for shaking or gestural input), a microphone for speech input, and a camera that watches for other user inputs. Keyboard and mouse input (which require some degree of concentration) are de-emphasized or turned off entirely. Outputs for the phone 108 are also configured so as not to needlessly distract the user. Small icons on the screen of the phone 108 will probably not be noticed at all, so nonurgent displays or messages can be simply discarded or stored for later review. Modalities of the user interface 204 can be also be altered: If, for example, a tornado- warning message comes in, requiring the user's immediate action, then rather than displaying a static icon on the screen of the phone 108, the user's attention can be "grabbed" by displaying a large, pulsating icon or by playing an alert through the speaker of the phone 108. (This is an example of optional step 308.)

[0039] Consider next the same physical layout as above, but where the smart phone 108 determines that the user's primary attention is given to it with only secondary attention given to the television monitor 114. This is called "lean-forward," and, because the user is actively watching the screen of the phone 108, a much richer interface is appropriate. Smaller icons, and more of them, can be displayed with the expectation that the user will notice them. The keyboard and mouse interfaces, which allow finer control than gestures, are emphasized.

[0040] If the smart phone 108 can estimate how the user's attention is split between the television monitor 114 and the phone 108, then it can configure its interface 204 somewhere between the extremes of "lean-back" and "lean- forward." Similarly, if the phone 108 is aware (or suspects) that the user's attention is split among more than the two devices 108, 114, it can accordingly present an appropriate user interface 204.

[0041] In the discussion of step 300 above, it was noted that the user can set a "slider" (or otherwise interact with the user interface 204 of the end-user device 108) to force a particular value for the user-interaction parameter. This option is especially useful when, through lack of information, the procedure of Figure 3 calculates a user-interaction parameter that does not reflect the user's actual attention profile. The user may also wish to "lock down" the parameter if he is constantly changing the focus of his attention and would rather adapt himself to the devices 108, 112, 114, 116 rather than having the devices 108, 112, 114, 116 attempt to adapt themselves to him. While this explicit setting essentially nullifies (or makes trivially easy) the operations of step 304, aspects of the present invention, including especially the user-interface configuration of step 306, are still applicable and useful.

[0042] Note that the above examples only discuss how the interface 204 of the end- user device 108 (a Class A device) is configured. Configuration of other (non-Class A) devices are discussed below.

[0043] The end-user device 108 can apply the user-interaction parameter for purposes other than configuring its user interface 204. As another example of step 308, when media content is received, the device 108 can analyze the urgency of the content and then, based on the user-interaction parameter, direct the content to the most appropriate end-user device 108, 112, 114, 116. Returning to the example of the tornado warning, the warning can be sent to whichever device 108, 112, 114, 116 is currently receiving the bulk of the user's attention, or even to all possible devices 108, 112, 114, 116 so that the user becomes aware of the warning as quickly as possible. Other uses of the user- interaction parameter, such as re-mapping the meaning of gestural inputs, are also contemplated. [0044] The user-interaction parameter can be used in selecting a particular media presentation to render or an application to run in optional step 310. If, for example, the user is primarily focusing on a football game displayed on the television monitor 114, then content relating to that game (e.g., advertisements, players' biographies, a commentary track) could be displayed on the end-user device 108.

[0045] Figure 3b presents other optional uses of the user-interaction parameter. Because current applications are not written to consider how to use the user-interaction parameter, the above step 306 would generally be performed by the operating system of the end-user device 108. It is expected that in the future at least some applications would be able to accept the user-interaction parameter in step 312 and to configure their operations accordingly.

[0046] In step 314, the end-user device 108, after having calculated the user- interaction parameter, sends that parameter to another device. The other device would probably be a Class B end-user device (discussed below in relation to Figure 4) or a Class Y server (Figure 5). In some situations, the device 108 does not send the actual user- interaction parameter in step 314 but instead sends a value based on that parameter. For example, the device 108 can review the information contained in the user-interaction parameter and send a value tailored to a Class B end-user device.

[0047] In addition to sending the user-interaction parameter to a server in step 314, the end-user device 108 could send further information in step 316. Generally, this further information allows the recipient server to better understand the user's current attention profile. Specific examples are discussed below in reference to step 502 of Figure 5 and step 604 of Figure 6 where the server receives and applies the further information.

[0048] In step 318, a server sends a command to the end-user device 108, and the device 108 responds. This step is relevant because the command may be based on the user-interaction parameter (sent to the server in step 314), and the specific response by the device 108 may also be based on the user-interaction parameter.

[0049] Note that in an actual scenario, the steps of Figure 3 are performed repeatedly and possibly in an overlapping fashion. The user's attention profile is constantly monitored, and, as changes are noted, those changes are reflected in a change to the user- interaction parameter which could result in changes to user interfaces 204 and applications. For example, the end-user device 108 may note that the user has just changed from a lean-back mode to a lean-forward mode. In addition to configuring the user interface 204 of the device 108 to optimize the user's interaction in the lean- forward mode, the device 108 can take specific actions based on the change in modes. The device 108 may, for example, recommend that the media playing on the television monitor 114 (to which the user is now paying less attention) be paused or recorded for future playback. The particular lean-back configuration settings can be stored so that they can be re -instituted if the user goes back to focusing his attention on the monitor 114.

[0050] Figure 4 presents a method of operation applicable to a Class B device. If the set-top box 112 is such a device, then it would receive, in step 400, the user-interaction parameter (or a value based on that parameter) from another device, possibly from the Class A end-user device 108 that set the parameter (or from a server: see the discussion of Figures 5 and 6, below). The value received could be tailored for the particular recipient device 112. For example, rather than telling the device 112 the entire profile of the user's attention, the value could simply say that the user is giving, say, 30% of his attention to the device 112.

[0051] With the parameter in hand, the device 112 configures its user interface 204 in step 306. This step uses the same numbering as the equivalent step in the procedure of the Class A device 108 (Figure 3a), because the present Class B device 1 12 applies the same considerations when setting its user interface 204. To emphasize that point, the Class B device 112 can then, in step 402, perform any or all of the optional steps 308 through 318 of Figures 3 a and 3b. [0052] In sum, the Class B device 112 of Figure 4 may be able to do everything that the Class A device 108 of Figure 3 does with the exception of actually deriving the user- interaction parameter. Of course, different devices are built with different limitations, so that not all Class B devices 112 (and not all Class A devices 108, for that matter) can perform all of the optional steps 308 through 318.

[0053] Note also that, in general, this Class B device 112 gathers whatever information it can that is relevant to the user's attention profile and sends that information to the Class A device 108. This information can include explicit user settings, profile information, historical and current user-interaction patterns, and user preferences and policies. This is discussed above in relation to step 302 of Figure 3a. The Class A device 108 uses this information when setting the user-interaction parameter in step 304 of Figure 3 a.

[0054] A Class Y server 104 can operate according to the exemplary method of Figure 5. In step 500, the server 104 receives the user-interaction parameter (or a value based on it), probably from the Class A end-user device 108 that calculated the parameter (or from a Class Z server: see Figure 6 and accompanying discussion). In some situations, more than one end-user device 108, 112, 114, 116 is a Class A device, and in that case the server 104 can receive multiple user-interaction parameters in step 500.

[0055] The server 104 can also receive other relevant information in step 502 such as an identification of the device sending the user-interaction parameter, contextual information, and information about how the sending device responded to the user- interaction parameter. (See the discussion of step 316 of Figure 3b.)

[0056] Based on the information received in steps 500 and 502, the server 104 sends a message to an end-user device 108, 112, 114, 116 in step 504. For example, the message can give a Class B device 112 enough information so that the device 112 can configure its user interface 204. For a Class C end-user device, the message can be more explicit, telling the device exactly how to configure its user interface 204. (Class C devices, remember, do not know how to respond to the user-interaction parameter, but their user interface 204 may still be appropriately configurable.) That is, a Class B device 112 can be told that the user is in lean-back mode, and the Class B device 112 then configures its user interface 204 accordingly. The Class C device, on the other hand, is given explicit instructions that configure its user interface 204 to accommodate the user's lean-back. Different Class B and C devices have different limitations, but in the most general case, they can be configured in as many ways as a Class A device 108 configures itself. (See the discussion of step 306 of Figure 3a.)

[0057] The server 104 can send messages other than configuration messages in step 504. The server 104 may select media content or an application based on the information it received in steps 500 and 502 and send it out in step 504.

[0058] Finally, Figure 6 presents a method for a Class Z server 106. The method begins with steps 600 and 602 where the server 106 receives attention information from multiple user devices 108, 112, 114, 116. This is the same kind of information that the Class A device 108 receives in step 302 of Figure 3a. In step 604, the server 106 can also receive further information from an end-user device 108, 112, 114, 116, such as the information described above in relation to step 502 of Figure 5.

[0059] Then in step 606, the server 106 sets a user-interaction parameter based on all of the information available to it. Here, the server 106 can use much of the procedure that the Class A device 108 uses in step 304 of Figure 3a.

[0060] Now that the user-interaction parameter has been set, the server 106 proceeds, in step 608, to communicate with one or more of the end-user devices 108, 112, 114, 116 just as the Class Y server 104 did in step 504 of Figure 5 (discussed above).

[0061] The above discussion clearly separates devices into the A, B, C, Y, and Z Classes. It is important to remember that while a device operates in one class in one situation, in another situation the same device may operate in another class. Also, any information available from any device may, in theory, become useful as input in setting the user-interaction parameter.

[0062] In view of the many possible embodiments to which the principles of the present invention may be applied, it should be recognized that the embodiments described herein with respect to the drawing figures are meant to be illustrative only and should not be taken as limiting the scope of the invention. For example, multiple devices of various classes can all work together to set the user-interaction parameter and to respond to that parameter once set. Therefore, the invention as described herein contemplates all such embodiments as may come within the scope of the following claims and equivalents thereof.