Patent Application
20050210525
The systems and methods described herein relate to maintaining state information for a client device.
A client device in a television-based system can receive video and audio content from a program distributor in the form of broadcast programs, such as news programs, sitcoms, movies, sporting events, commercials, and any other type of television-based information. A client device may also receive other types of data, such as data associated with a remote application. A client device includes, for example, a set-top box, a digital satellite receiver, a cable box, a digital video recorder (DVR), and a television with a built-in receiver.
Existing client devices store user settings, preferences, and account information. For example, a persistent memory device may be included in client devices to store settings, preferences, and other information. Adding a persistent memory device to a client device increases the cost and complexity of the client device.
Television broadcasting systems (such as cable TV broadcasters or satellite broadcasters) originate and communicate signals to customers from a headend (or “head-end”). The headend contains equipment to broadcast signals and provide other services to multiple customers. A headend interacts with each client device to provide content that is appropriate for the client device based on the settings, preferences and account information associated with the client device. This arrangement can cause a loss of data if the client device malfunctions. Loss of data usually requires re-configuration of the client device by the user. Additionally, if a particular household has multiple client devices (e.g., coupled to multiple televisions), each client device is typically configured separately from the other client devices. This separate configuration of each client device can be tedious, especially when each client device is configured in a similar manner.
The systems and methods described herein maintain configuration information for a client device in a remote location. In a particular embodiment, a client device having an associated identifier is initialized. The identifier associated with the client device is communicated to a configuration server that contains configuration information associated with the client device. The configuration information is received from the configuration server and is applied to the client device. Data, such as video data, is then received from the configuration server.
Similar reference numbers are used throughout the figures to reference like components and/or features.
The systems and methods described herein store configuration information associated with a client device in a storage device, such as a server, associated with a headend system that provides content to the client device. By storing this configuration information remotely from the client device, the configuration information is not lost in the case of a client device malfunction. Additionally, the same configuration information can be downloaded into multiple client devices, thereby eliminating the need for users of multiple client devices to manually enter the same configuration information in each of the multiple client devices.
The systems and methods described herein also allow users or other systems to access the configuration information from the headend systems without requiring interaction with the client device with which the configuration information is associated. Additionally, by storing configuration information remotely, the remote system may customize data sent to the client device such that the customized data is limited to information that the client device can use. This customization of data reduces the amount of data that is sent to the client device as compared to systems that send large amounts of data to a client device, which filters out unnecessary data.
When utilizing the systems and methods discussed herein, the client device may have limited resources, such as no persistent memory, because the configuration information that needs to be persisted is stored remotely from the client device. By reducing resources in the client device, the cost and complexity of the client device is also reduced.
The systems and methods discussed herein are described with reference to an environment in which content is distributed to client devices via a data communication network, such as the Internet. These examples represent one possible environment in which the systems and methods can be implemented. In other embodiments, any type of system or architecture can be used to provide content to one or more client devices.
Client devices of the type discussed herein range from clients with substantial memory and processing resources, such as television-enabled personal computers and television recorders equipped with hard-disks, to clients with little or no memory and/or limited processing resources. Although particular examples of client devices are discussed herein, any client device can be used with the systems and methods described. Example client devices include personal computers, DVD players, digital video recorders (DVRs), set top boxes, cable boxes, satellite receivers, televisions, game consoles, and the like. As used herein, the term “user” may also be referred to as “viewer”. Also, as used herein, the terms “state information”, “configuration information”, and “configuration settings” are used interchangeably.
In a particular embodiment, client devices 102 communicate with one or more servers via network 104 using simple object access protocol (SOAP) messages transported using hypertext transfer protocol (http), a protocol commonly used by the World Wide Web. In other embodiments, any type of protocol and/or messaging format can be used to exchange data between client devices 102 and one or more servers.
Each client device 102 has a unique identifier stored within the client device. For example, the unique identifier may be stored in a non-volatile memory device or other component of the client device. Since each client device 102 has a unique identifier, each client device can be distinguished from the other client devices. Although not shown in
In the example of
An account server 110 and a database 112 are coupled to configuration server 108. Account server 108 maintains information regarding customer accounts, customer subscriptions, customer billing histories, and the like. For example, account server 108 can maintain information regarding one or more client devices associated with a customer's account and payment status of the customer's account invoices. Database 112 stores various information used by configuration server 108, such as configuration information related to client devices 102. Database 112 may also store information used by account server 110, such as billing information and customer account information.
A recommendation server 114 is coupled to configuration server 108 and network 104. Recommendation server 114 generates, for example, television program recommendations for one or more client devices 102. A marketing server 116 is also coupled to configuration server 108 and network 104. Marketing server 116 generates, for example, advertisements and other marketing content that is provided to one or more client devices 102. The advertisements and other marketing content may be targeted to particular client devices 102 based on known viewing habits or preferences of the users of those particular client devices. Various other servers (not shown) may be coupled to configuration server 108 and network 104 to communicate with configuration server 108 and client devices 102. These other servers can request configuration information regarding client devices 102 from configuration server 108 and use that information to generate content, advertisements, and the like that are communicated to client devices 102.
Examples of other servers that may be coupled to configuration server 108 include a customer service server that accesses configuration information to allow a customer service agent to help a customer configure their client device and servers that run remote applications. Remote applications can, for example, generate user interface data that is provided to the client device, thereby allowing the client device to display a high-quality user interface without requiring the client device to have the resources necessary to generate the user interface.
Traditional television broadcasting systems (such as cable TV broadcasters or satellite broadcasters) originate and communicate signals to customers from a headend, as discussed above. In the architecture of
In the example of
By providing persistent storage of client device configuration information on a remote device (e.g., configuration server/database), the configuration information is not lost if the client device malfunctions. Additionally, the storage reliability of the configuration information can be enhanced by providing redundant storage devices such as mirrored storage devices or tape backup systems. Multiple client devices can be configured to be identical to one another by associating the same configuration information with each client device. The architecture of
Although not shown in
As procedure 200 continues, the configuration server identifies the requested configuration information associated with the client device based on the identifier provided by the client device (block 208). For example, the configuration server may retrieve the configuration information from an attached database or other storage mechanism. The configuration server then formats the requested configuration information into an appropriate format (block 210), such as an html format. Alternate embodiments may use other formats, such as serialized binary objects, plain text, and the like. Procedure 200 continues as the configuration server communicates the formatted configuration information to the client device (block 212). The client device receives the configuration information and applies the configuration information (block 214). For example, if the configuration information includes last channel information, the client device tunes to the last channel.
In another embodiment, block 304 may also determine whether the configuration information is already stored in the client device (e.g., from a previous request for the configuration information). If the configuration information is already stored in the client device, the client devices uses the stored configuration information. Otherwise, the client device continues to block 306 as discussed below.
If additional configuration information is needed, the procedure continues from block 304 to block 306 where the client device communicates a request for the necessary configuration information to the configuration server. In one implementation, each request specifies the identifier associated with the client device communicating the request. Alternatively, the identifier associated with the client device communicating the request could be sent over a session that has been established with a specific client, which implies the client's identifier.
The configuration server then retrieves the requested configuration information associated with the client device (block 308). Next, the configuration server formats the requested configuration information into an appropriate format and communicates the formatted configuration information to the client device (block 310). The client device receives the requested configuration information and applies the configuration information (block 312). Finally, the client device performs the task requested by the user of the client device (block 314).
After the task is completed, the requested configuration information may be discarded by the client device. If the client device needs the same configuration information in the future, the client device can request the same configuration information again. When operating in this manner, the client device always receives a current copy of the configuration information.
In an alternate embodiment, the configuration information associated with one or more client devices is changed by a user interacting with the configuration server. For example, a user may access the configuration server via a Web browser application. The user then accesses a current version of the configuration information, makes any desired changes, and saves the modified configuration information on the configuration server. In one embodiment, these changes are communicated to the client device and applied by the client device as soon as they are entered by the user. In other embodiments, the updated configuration information is communicated to the client device after subsequent initializations of the client device.
In one embodiment, a household, business, or other organization may use multiple client devices of the type discussed herein. In this embodiment, there may be a single set of configuration information associated with the household that is applied to all client devices. Thus, a single set of configuration information is established and applied to all client devices. This set of configuration information may have an associated unique identifier.
Utilizing household configuration information eliminates the need to individually configure each of the client devices. Additionally, the household configuration information may be used as a default configuration for each client device, which can be overridden by configuration information associated with a particular client device. For example, the household configuration information may prohibit viewing of programs with a rating of PG-13 or higher. However, configuration information associated with a particular client device may override that prohibition by allowing the particular client device to display programs with any rating. In a particular embodiment, information regarding client devices associated with a common household is maintained by the account server.
Client device 600 also includes a communication interface 608, a modem 610, and an audio/video output 612. Communication interface 608 can be implemented as a serial and/or parallel interface, as a wireless interface, and/or any other type of network interface. A wireless interface allows client device 600 to receive control input commands 622 and other information from a user-operated input device, such as from a remote control device 624 or from another infrared (IR), 0802.11, Bluetooth, or similar RF input device. Input devices can include a wireless keyboard or another handheld input device 626 such as a personal digital assistant (PDA), handheld computer, wireless phone, or the like. A network interface and a serial and/or parallel interface enables client device 600 to interact and communicate with other electronic and computing devices via various communication links. Modem 610 facilitates client device 600 communicating with other electronic and computing devices via a data communication network, a conventional telephone line, a DSL connection, a cable connection, and/or other type of connection.
Audio/video output 612 provides audio, video, and/or display signals to a television 620 or to other devices that process and/or display, or otherwise render, the audio and video data. Video signals and audio signals can be communicated from client device 600 to television 620 via an RF (radio frequency) link, S-video link, composite video link, component video link, or other similar communication link.
Although shown separately, some of the components of client device 600 may be implemented in an application specific integrated circuit (ASIC). Additionally, a system bus (not shown) may connect the various components within client device 600. A system bus can be implemented as one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, or a local bus using any of a variety of bus architectures. By way of example, such architectures can include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnects (PCI) bus (also known as a Mezzanine bus).
Although the description above uses language that is specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the invention.
