Patent Application
20120023528
When an error occurs between a client and a server, a user may experience service interruption and/or delays. For example, when the user navigates, via the client, to various user interfaces or receives other content from the server and a device error occurs or a disconnection between the client and the server occurs, a reset process may be initiated. Thereafter, the client and the server may establish a new connection, and the user may navigate, via the client, from a default user interface or receive default content.
The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention.
According to an exemplary embodiment, a server may store state information associated with content provided to a client. For example, the server may store state information associated with a user's navigation through a graphical user interface (GUI) or media content. In this way, when an error occurs between the server and the client, a reset process may include automatically providing to the client a last user interface to which the user navigated or the last media content the user accessed before the error. This is in contrast to other reset processes that would require the user to navigate to the last user interface from a default user interface or to reselect the media content the user previously accessed.
According to an exemplary implementation, the server may identify a client. For example, the client may have a unique identifier (ID) (e.g., an equipment ID, a network address, etc.). The server may store the unique identifier. As the client requests content (e.g., media content, GUIs, etc.) from the server, the server may provide the requested content and store state information associated with the content provided. For example, the server may store the GUI content (e.g., an identifier of the GUI content) with the unique identifier of the client, or store the media content (e.g., an identifier of the media content) with the unique identifier of the client. According to other implementations, the state information may also include a navigation request associated with the GUI provided or a media content request associated with media content provided.
The server may overwrite the state information as content is requested by the client. In this way, when the client reconnects with the server after the error or recovers from the error, the server may provide the client with the last content received from the server before an error occurs based on the state information. For example, assume that an error occurs between the server and the client, and the reset process is performed. When the client recovers or reconnects to the server, the server may provide the client with the last user interface to which the user navigated or the last media content the user accessed before the error occurred.
The number of devices and configuration in environment 100 is exemplary and provided for simplicity. In practice, environment 100 may include more devices, different devices, and/or differently arranged devices, than those illustrated in
TCDN 105 may include a network that distributes television content. For example, although not illustrated, TCDN 105 may include television serving offices, television distribution sites, data centers, etc.
Home network 110 may include a customer site that receives content (e.g., television content) from TCDN 105. As illustrated, home network 110 may include exemplary customer premise equipment, such as, for example, server 115 that includes state information tracker 120, clients 125, TVs 130 and remote control 140.
Server 115 may include a device that provides services and/or other types of assets. For example, server 115 may provide content (e.g., television content) to clients 125. For example, the television content may include GUIs (e.g., television guides, weather information, sports information, games, digital video recording (DVR) information, or the like) and media content (e.g., television programming, movies, video-on-demand, or the like). As described further below, server 115 may include state information tracker 120. State information tracker 120 may track state information associated with content provided to client 125.
Client 125 may include a device that communicates with server 115 to obtain services and/or other types of assets. For example, client 125 may communicate with server 115 to obtain content (e.g., television content). Client 125 may correspond to a thin client. For example, client 125 may not include a hard drive and/or rely on server 115 to perform various processes. According to other implementations, client 125 may not correspond to a thin client. According to yet another implementation, client 125 may correspond to a set top box.
TV 130 may include a device to display content (e.g., television content). According to an exemplary implementation, TV 130 may include client 125. According to other exemplary implementations, TV 130 and client 125 may be separate devices, as illustrated in
Referring to
Referring to
As a result of the foregoing, a disruption of service to user 135 may be minimized when an error occurs between client 125 and server 115. Since an exemplary embodiment has been broadly described, a more detailed description is provided below, along with various implementations.
Processing system 205 may include one or multiple processors, microprocessors, data processors, co-processors, application specific integrated circuits (ASICs), controllers, programmable logic devices, chipsets, field programmable gate arrays (FPGAs), application specific instruction-set processors (ASIPs), system-on-chips (SOCs), and/or some other component that may interpret and/or execute instructions and/or data. Processing system 205 may control the overall operation or a portion of operation(s) performed by device 200. Processing system 205 may perform one or more operations based on an operating system and/or various applications (e.g., applications 215).
Processing system 205 may access instructions from memory/storage 210, from other components of device 200, and/or from a source external to device 200 (e.g., a network or another device).
Memory/storage 210 may comprise one or multiple memories and/or one or multiple secondary storages. For example, memory/storage 210 may comprise a random access memory (RAM), a dynamic random access memory (DRAM), a read only memory (ROM), a programmable read only memory (PROM), a flash memory, and/or some other type of memory. Memory/storage 210 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.) or some other type of computer-readable medium, along with a corresponding drive. Memory/storage 210 may include a memory and/or a secondary storage that is external to and/or removable from device 200, such as, for example, a Universal Serial Bus (USB) memory, a dongle, a hard disk, mass storage, off-line storage, etc.
The term “computer-readable medium,” as used herein, is intended to be broadly interpreted to comprise, for example, a memory, a secondary storage, a compact disc (CD), a digital versatile disc (DVD), or the like. The computer-readable medium may be implemented in a single device, in multiple devices, in a centralized manner, or in a distributed manner. Memory/storage 210 may store data, application(s), and/or instructions related to the operation of device 200.
Memory/storage 210 may store data, applications 215, and/or instructions related to the operation of device 200. For example, with reference to server 115, applications 215 may include one or multiple applications for providing a state-based recovery of content, as described further below.
Communication interface 220 may permit device 200 to communicate with other devices, networks, and/or systems, or the like. Communication interface 220 may include a wireless interface and/or a wired interface. Communication interface 220 may include a transmitter, a receiver, and/or a transceiver. Communication interface 220 may operate according to various protocols, standards, and the like.
Input 225 may permit an input into device 200. For example, input 225 may include a keyboard, a mouse, a microphone, a display, a touchpad, a button, a switch, an input port, voice recognition logic, fingerprint recognition logic, a web cam, and/or some other type of visual, auditory, tactile, etc., input component.
Output 230 may permit an output from device 200. For example, output 230 may include a speaker, a display, one or more light emitting diodes (LEDs), an output port, and/or some other type of visual, auditory, tactile, etc., output component.
As described herein, device 200 may perform processes in response to processing system 205 executing software instructions (e.g., applications 215) contained in a computer-readable medium, such as memory/storage 210. By way of example, the software instructions may be read into memory/storage 210 from another computer-readable medium or from another device via communication interface 220. The software instructions stored in memory/storage 210 may cause processing system 205 to perform processes described herein. Alternatively, device 200 may perform processes based on hardware (processing system 205, etc.), hardware and firmware, and/or hardware, software, and firmware.
As previously described, according to an exemplary embodiment, server 115 may track state information associated with content provided to client 125. For example, server 115 may include state information tracker 120.
Referring to
Referring to
Process 400 may include receiving a request for content (block 405). For example, as previously described, server 115 may receive a request for content from client 125. The content may correspond to television content. The television content may correspond to, for example, GUI content (e.g., a television guide, weather information, sports information, a game, digital video recording (DVR) information, or the like) or media content (e.g., television programming, video-on-demand, pay-per-view, or the like).
A response that includes the requested content may be sent (block 410). For example, as previously described, server 115 may provide the requested content to client 125. According to an exemplary implementation, server 115 may store the content and provide the content to client 125. According to other exemplary implementations, server 115 may obtain the content from TCDN 105 and then provide the content to client 125. According to an exemplary implementation, server 115 may receive a confirmation that the content was successfully received by client 125.
State information associated with the content and/or the request may be tracked (block 415). For example, as previously described, server 115 may store state information associated with the content provided. For example, server 115 may store a record that includes a client ID and GUI or media content information.
It may be determined whether an error occurred (block 420). For example, server 115 may recognize when an error (e.g., a connection error, a client error, etc.) occurs. Conversely, client 125 may recognize when an error (e.g., a connection error, a server error, etc.) occurs. When an error occurs, a reset process may be initiated (e.g., either by client 125 or server 115). The reset process may correspond to a soft reset or a hard reset.
When it is determined that an error did not occur (block 420—NO), server 115 may continue receiving requests from client 125 (return to block 405). When it is determined that an error occurred (block 420—YES), a reset process may be initiated (block 425). For example, server 115 or client 125 may initiate a reset process. The reset process may include re-establishing a connection (e.g., a communication link) between server 115 and client 125.
Content may be provided to the client based on state information (block 430). For example, as previously described, server 115 may select the last GUI or media content information provided to client 125 before the error occurred based on the state information. For example, server 115 may access a record 325 associated with client 125. Record 325 may include client ID information and GUI or media content information. Server 115 may provide the last GUI or media content information to client 125. Process 400 may continue to block 405.
Although
According to another exemplary embodiment, multiple servers may share state information associated with content provided to clients. When an error occurs between a server and a client, the client has the option to discover and connect to an alternate server. The alternate server may provide the client with the last content before the error occurred. According to an exemplary implementation, when the client connects to a server, the server may generate and send the client a token. As the server provides content to the client, the server may store state information. The server may also provide other servers with the token and the state information. When an error occurs, the client may connect to an alternate server and provide the alternate server with the token. The alternate server may use the token to identify the state information associated with the client. That is, for example, the token may act as an index or key to the state information. The alternate server may then provide the last content to the client.
Referring to
Referring to
Referring to
The foregoing description of implementations provides illustration, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Accordingly, modifications to the implementations described herein may be possible.
The terms “a,” “an,” and “the” are intended to be interpreted to include one or more items. Further, the phrase “based on” is intended to be interpreted as “based, at least in part, on,” unless explicitly stated otherwise. The term “and/or” is intended to be interpreted to include any and all combinations of one or more of the associated items.
In addition, while a series of blocks has been described with regard to the process illustrated in
It will be apparent that the embodiments described herein may be implemented in many different forms of software or firmware in combination with hardware in the implementations illustrated in the figures. The actual software code (executable by hardware) or specialized control hardware used to implement the device, method, and/or system does not limit the disclosure of the invention. Thus, the operation and behavior of the devices and/or systems, or the performing of the methods was described without reference to the specific software code—it being understood that software and control hardware can be designed to implement the device, method, and/or system based on the description herein.
Further certain features described above may be implemented as “logic” or a “component” that performs one or more functions. This logic or component may include hardware (e.g., processing system 205, etc.), a combination of hardware and software (e.g., applications 215), a combination of hardware and firmware, or a combination of hardware, firmware, and software, or software.
In the preceding specification, various embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded as illustrative rather than restrictive. For example, according to other embodiments, assume that the server receives a request for television content and an error occurs before a response is sent to the client. In such instances, the server may store the request as state information. When a new communication link is established, instead of the server resending the last television content successfully received by the client, the server may send the new television content associated with the request received by the server before the error occurred.
No element, act, or instruction used in the present application should be construed as critical or essential to the implementations described herein unless explicitly described as such.
