REMOTELY CONTROLLING A MEDIA SERVER VIA A NETWORK

CROSS-REFERENCES TO RELATED APPLICATIONS

[0001] This Application claims priority to U.S. Non-Provisional Application Serial No. 12/645,870, filed December 23, 2009.

TECHNICAL FIELD

[0002] The present disclosure generally relates to systems and methods for controlling a media recorder, server and/or other device over a network. Such systems and techniques may be useful, for example, in remotely controlling set-top boxes, digital video recorders (DVRs), placeshifting devices and/or other types of media devices.

BACKGROUND

[0003] The Internet and other digital communications networks continue to have significant effects on every aspect of personal and professional life. Network communications are becoming increasingly ubiquitous due to the reduced cost and increased capability of portable computing devices, as well as the increasing prevalence and capability of mobile telephony and other wireless communications technologies. Additionally, more and more devices, including set top boxes (STBs), television receivers, personal or digital video recorders (DVRs), placeshifting devices and the like are becoming enabled for communications over digital networks. Consumers are therefore expecting convenient control of their media content from a wide range of locations and settings.

[0004] A challenge often arises, however, in remotely controlling network-enabled media devices such as STBs, DVRs, placeshifting devices, and the like. Firewalls and other security mechanisms, for example, can limit direct access to consumer devices that are located on a home network. As a result, difficulties can arise in contacting the device to record or view programming, to change settings on the device, to view content available via the device, or to perform other tasks. Although some have attempted to establish communications with media devices over the Internet or other networks, these limited solutions have typically relied upon periodic polling by the device to obtain any commands from a remote server. These polling schemes are prone to processing delays, as well as a lack of convenient feedback or confirmation when a user requests an action. Further, the types of actions that are available through polling schemes have, in practice, been severely limited.

[0005] As a result, it is now desirable to create systems and methods for controlling a DVR, STB, placeshifting device or other network-enabled media server device. Such systems and methods would ideally provide a rich set of control options that would be available from a wide array of client devices. These and other desirable features and characteristics will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and this background section.

BRIEF SUMMARY

[0006] According to various exemplary embodiments, systems and methods are described for remotely controlling a personal or digital video recorder (PVR/DVR), a set top box (STB), a placeshifting device or system that communicates with a PVR/DVR or the like, and/or another media server. In some embodiments, a realtime, semi-real-time or other communications session is established between a server host and the media server in response to a connection request received from the client. Information about the content processed at the media server is received via the session and provided to the client. In response to subsequent instructions received from the client, the media server can be controlled and/or other actions can be taken using the session. Programs stored on the media server may be deleted, for example, or additional programs can be recorded. Other embodiments may provide control instructions to change channels, to fast forward or rewind content, to adjust user preferences, and/or to take any other actions as desired.

[0007] Other embodiments relate to host systems that communicate via a network with a client and a media server having stored programming content. The system suitably comprises a message server configured to communicate with the media server via the network using a pre-existing connection, and a guide server. The guide server is appropriately configured to receive a request for a connection to the media server from the client via the network, to direct the message server to contact the media server in response to the request, to establish a session via the network with the media server, to receive information about the media content stored at the media server via the session, to provide the information about the media content to the client, to receive an instruction from the client to control the media server, and, in response to the instruction received from the client, and to direct the media server via the session to execute the instruction.

[0008] Still other embodiments provide a method executable by a guide server or other host communicating via a network with a client and with a media recorder having stored media content. A first message is received from the client at the host via the network, wherein the first message identifies the media recorder. In response to the first message, a second message is transmitted to a message server having a pre-existing connection with the identified media recorder. In response to a third message received from the media recorder, a session is created between the media recorder and the host via the network. Program guide information is provided from the host to the client via the network, and an instruction to record a program identified in the program guide information is received from the client at the host. In response to receiving the instruction, the media recorder is directed via the session to record the identified program.

[0009] Various other embodiments, aspects and features are described in more detail below.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

[0010] Exemplary embodiments will hereinafter be described in conjunction with the following drawing figures, wherein like numerals denote like elements, and

[0011] FIG. 1 is a block diagram of an exemplary guide server host system;

[0012] FIG. 2. is a diagram showing an exemplary processes for controlling a remote media server;

[0013] FIG. 3 shows one example of an interface with guide data and a media player that could be presented by a client in some embodiments;

[0014] FIG. 4 shows one example of an interface that could be used to remotely manage programs stored on a DVR or other media server in some embodiments; and [0015] FIG. 5 shows one example of an interface window that could be used to resolve program recording conflicts in some embodiments.

DETAILED DESCRIPTION

[0016] The following detailed description of the invention is merely exemplary in nature and is not intended to limit the invention or the application and uses of the invention. Furthermore, there is no intention to be bound by any theory presented in the preceding background or the following detailed description.

[0017] According to various embodiments, a guide server or other host is able to establish a real-time session with a set top box (STB), television receiver, personal or digital video recorder (DVR), placeshifting device, file server or other media server that allows for direct and convenient control of the device using web or other network-based features. The networked host may be used in some embodiments to set preferences, to choose programs to be recorded by the server, to manage programs previously stored, and/or any other functions as appropriate. For example, in some embodiments the host is able to retrieve real-time (or near realtime) information about media content stored on the media server, thereby allowing for convenient search and management of the stored files, as well as the ability to direct new recordings of future programming, and/or to take other actions as desired. The host may also provide searching or other features; in some embodiments, searching may consider programming stored on the media server as well as program guide information, information about on-demand content and/or any other available information to create a very powerful search experience.

[0018] Unlike techniques that rely upon intermittent polling by the remote device to obtain instructions or other information, various embodiments are able to establish real-time connections with the remote media device through the use of a messaging server that maintains a pre-existing connection with the media server. When a user wants to open a control or other session with the remote media server, the pre-existing connection can be used to establish a relatively immediate session with the online host, thereby allowing commands and other messages to be "pushed" to the media server in real-time (or near real time) rather than waiting for the media server to "pull" the information from the host.

[0019] This relative immediacy provides a greatly improved user experience, as well as access to a much wider array of features. By providing direct, real-time access to the media server device, for example, some implementations of the host are able to provide access to most, if not all, of the functionality that would be available from a directly-connected client application, but in a convenient web interface. Various embodiments therefore provide a relatively robust set of functions and features to the viewer that can be conveniently accessed using conventional web or similar features. Other embodiments may provide alternate or additional features, as desired.

[0020] Turning now to the drawing figures and with initial reference to FIG. 1, an exemplary system 100 for remotely controlling a media server 104 suitably includes a client 102 that gains to access a guide server or other host 116 via a network 110. The client 102 may interact with the guide server host 116 using a conventional web browser 103 in some embodiments. Upon receiving a request from a client 102, host 116 is able to establish a session with the media server 104 to obtain information about programming or other media content 105 available to the server 104. This information may be appropriately processed and/or formatted (e.g., as a web page or the like) and provided to client 102 via network 110. Other information (e.g., program guide information 115) may also be provided to the client 102. In various embodiments, a user of client 102 provides an instruction to record an upcoming program, to delete a stored program, and/or to otherwise change the content 105 that is forwarded to host 116. Upon receipt of such an instruction from client 102, host 116 appropriately directs the server 104 to execute the instruction.

[0021] Other embodiments may provide other functions or features. Some implementations may provide robust searching of content 105, for example. Such searching may consider program guide information 115, information 112 about on- demand programming, and/or other information as desired in addition to information obtained from media server 104. Other embodiments may additionally or alternately provide the ability to change preferences or other settings on media server 104, to view media content 105 in a web browser or other window, and/or to take any other actions as may be desired.

[0022] Client 102 may be any device, component, module, hardware, software application and/or the like that is capable of communicating over network 110. To that end, many different types of clients 102 may be implemented with any sort of general or special purpose hardware, software and/or firmware. In some embodiments, client 102 may be a conventional personal computer, portable computer, workstation and/or other computing system. In still other embodiments, some types of clients 102 may include personal digital assistants, video game players, mobile telephones, network appliances, network-enabled remote controls and/or any other devices capable of communicating on network 110.

[0023] In the embodiment shown in FIG. 1, client 102 executes any sort of conventional browser application 103 that is compatible with standard Internet, world wide web (WWW) and/or other formats. Conventional web browsers available for a number of different computing platforms include the INTERNET EXPLORER, MOZILLA FIREFOX, SAFARI, CHROME, and OPERA browsers, as well as many others. Such browsers 103 are typically capable of displaying active or other documents formatted in accordance with published protocols (e.g., hypertext markup language (HTML), extensible markup language (XML), and/or the like). Many browsers 103 are also capable of executing "plugin" applications, applets or the like. Such plugins may be formatted in accordance with ActiveX, JAVA and/or any number of other formats.

[0024] In some embodiments, client 102 includes a media application 107. This application 107 may be a standalone media player that executes separately from browser 103 so that browser 103 may not be needed. In other embodiments, the media application 107 could be implemented as a plugin or other applet that runs within browser 103 as desired. In some embodiments, media application 107 is initially obtained from a networked host, such as host 116. The application may be retrieved on an as-needed basis in some embodiments, or may be stored at client 102 for subsequent execution. Some embodiments may not provide media viewing on client 102; such clients 102 may nevertheless be able to interact with host 116 to select programs to record, to change preferences, to control the operations of media server 104, and/or to take other actions related to media server 104.

[0025] Network 110 is any digital or other communications network capable of transmitting messages between senders (e.g., media server 104) and receivers (e.g., media server 104). In various embodiments, network 110 includes any number of public or private data connections, links or networks supporting any number of communications protocols. Network 110 may include the Internet, for example, or any other network. Such networks may be based upon TCP/IP or other conventional protocols, although other embodiments may use any type of alternate or successor protocols, as desired. In various embodiments, network 110 may also incorporate a wireless and/or wired telephone network, such as a cellular communications network for communicating with mobile phones, personal digital assistants, and/or the like. Various embodiments of network no may also incorporate any sort of wireless or wired local area networks, such as one or more IEEE 802.3 and/or IEEE 802.11 networks.

[0026] Media server 104 is any device or system communicating on network 110 that is capable of receiving, recording, placeshifting and/or otherwise processing media content 105. In various embodiments, media server 104 includes a personal or digital video recorder (DVR) feature that allows the server 104 to record received programming for later viewing. A DVR may a standalone device, or may be integrated within any sort of receiver (e.g., a cable, direct broadcast satellite (DBS) or other set top box (STB)) that is capable of receiving and demodulating programming signals. Other embodiments of media server 104 may include any sort of standalone or hybrid media players, file servers and/or the like that are capable of receiving, storing or otherwise processing streaming or file-based content 105 of any sort. Still other embodiments of media server 104 could implement a networked gaming server or other media service as desired.

[0027] Content 105 is any sort of file-based programming or other content that is accessible to media server 104. In various embodiments, content 105 represents stored programming that is received from an internal or external television receiver. Content 105 may also represent programming received from a camera, network server and/or other source, as desired. Content may be stored in any media, including in memory, on a hard disk, on a networked server, and/or in any other digital, optical or other available storage medium. Content 105 may be stored in any sort of compressed or uncompressed format, as desired, and may be encoded or transcoded as desired for effective receipt, storage, retrieval and playing.

[0028] Some embodiments of system 100 may simply use host 116 to provide control of media server 104 for recording programs, to deleting stored content 105, changing settings or parameters, and/or performing any other desired tasks. Other embodiments, however, may allow for streaming or other playing of media content 105 from server 104 to client 102. To that end, various embodiments of media server 104 may incorporate placeshifting functionality to support viewing of content 105 over network 110 (e.g., by client 102). In some embodiments, media server 104 includes a separate placeshifting device that works in conjunction with a STB, receiver, DVR, media player or other device to shift the viewing experience from a home television to a viewing display that is accessed via network no. Examples of placeshifting devices that may be used in some embodiments of media server 104 could include any of the various SLINGBOX products available from Sling Media of Foster City, California, although other products or servers 104 could be used in other embodiments. Many different types of placeshifting devices are generally capable of receiving media content from an external source, such as any sort of DVR or STB, cable or satellite programming source, DVD player, and/or the like. In other embodiments, placeshifting features are incorporated within the same device that provides content-receiving or other capabilities. Server 104 may be a hybrid DVR and/or receiver, for example, that also provides transcoding and placeshifting features. Examples of conventional placeshifting functions, features, systems and structures are described in United States Patent Publication No. 2006/0095471, although the features described herein could be equivalently applied with any number of other techniques and structures in addition to those described in that particular publication.

[0029] Host 116 is any server or other network host capable of interacting with one or more clients 102 to provide instructions to one or more servers 104. In various embodiments, host 116 is a program guide server that also allows integration of program guide information 115 and/or information about available on-demand programming 112 or the like with information about content 105, as described more fully below.

[0030] FIG. 1 shows one example of a host 116 that could be used to provide a guide server that interacts with any number of clients 102 and servers 104. To that end, each host 116 within system 100 may be implemented with a server computer system or service that is based upon any processor, architecture and/or operating system. Each host 116 will typically by implemented using any sort of conventional processing hardware 122, memory 124 and input/output features 125. Various embodiments may be implemented using dedicated or shared hardware servers; other implementations may make use of virtual server features as part of a "cloud computing" service, such as any of the cloud computing services provided by AMAZON, GOOGLE, MICROSOFT, IBM, UBUNTU, SUN MICROSYSTEMS and/or any number of other providers. [0031] Although FIG. 1 shows a single host 116 for convenience, many practical embodiments may provide a cluster or other collection of multiple hosts 116 to support any desired number of simultaneous connections. This cluster may also incorporate appropriate routing, load balancing, access and security mechanisms and or any number of other features. In various embodiments, each host 116 is an actual or virtual computer system executing an operating system 126 such as any version of LINUX, UNIX, SOLARIS, NETWARE, WINDOWS, OS/X, AIX and/or the like. The various UNIX/LINUX operating systems typically provide a computing core that is capable of executing a guide server application 128, as well as any number of daemons, processes, applications or other instance modules as desired. For example, a guide server application 128 could execute as a daemon on host 116, with connections to separate clients 102 being managed as separate processes or instances that communicate with server application 128 using features provided by operating system 126.

[0032] Guide server application 128 is typically initiated when host 116 is booted or otherwise initialized. In various embodiments, application 128 suitably registers with any appropriate load balancers or other routers so that connections with clients 102 can be appropriately distributed. Application 128 then processes connection requests from clients 102 as appropriate. In the embodiment shown in FIG. 2, guide server application 128 contains control logic 132 for controlling remotely-located servers 104 and a web server or other presentation logic 136 for providing information to client 102 in a web-based or other format that can be conveniently presented to the user. Various embodiments may also provide search engine logic 134 as desired; this search engine may perform an integrated search of information about content 105 that is stored with the remote media server 104, as well as any program guide information 115 and/or information about on-demand programming 112 as desired. Such information 112, 115 may be obtained from any database or other source available to host 116, including any database executing on a separate server or the like.

[0033] Control module 132 contains any appropriate programming logic to establish sessions over network 110 with one or more media servers 104 in response to requests received from clients 102. Such sessions can be used to retrieve information from the media server 104 and/or to provide instructions to the media server as desired. As described below, sessions with media servers 104 may be initiated by through one or more message servers 114 that have pre-established connections with the particular message server 114 to be contacted.

[0034] Interactions between host 116 and client 102 may be managed in any manner. In various embodiments, client 102 interacts with host 116 using a conventional web browser 107 that can receive information from a conventional web server module 136 at host 116. Such information may be provide as part of dynamic or active web content (e.g., using ASP, JAVASCRIPT, Cold Fusion, PHP and/or other content, or using JAVA, ACTIVEX and/or other plugins), and/or as static content (e.g., using HTML, XML or similar constructs). In various embodiments, presentation module 136 provides a conventional web page or similar document with embedded active content that allows the user to interact with a program guide or other information using conventional graphical user interface (GUI) constructs. The web page(s) provided from presentation module 136 may also provide a media player application 107, or may simply accommodate and interact with a media player application 107 that resides on client 102.

[0035] Guide server application 128 may provide any alternate and/or additional functions and features as desired. Generally, guide server application 128 is at least partially implemented using conventional compiled object code derived from source code in any programming language (e.g., C, C++ or the like). Other embodiments may make use of an interpreted or other abstracted environment, such as the JAVA environment available from Sun Microsystems of Sunnyvale, California or the .NET environment available from Microsoft Corporation of Redmond, Washington. Other embodiments may implement the various components of guide server application 128 using any other programs, programming languages, scripting languages, development or execution environments, and/or the like. Such programming may be stored in source or object code form on any digital storage medium (e.g., memory 124, mass storage, removable media, or any other medium) that is accessible to guide server application 128.

[0036] As noted above, directly connecting to a media server 104 from a network service 116 or client 102 may not always be convenient due to the presence of one or more firewalls or other security mechanisms within network 110, or any number of other factors. Various embodiments therefore provide any number of message servers 114 that are each capable of maintaining pre-existing connections with one or more network server 104. Each message server 114 is implemented using conventional computer server hardware, software and/or services, such as any of the hardware or software features described above in connection with host 116.

[0037] Message server 114 suitably receives requests for connections from one or more servers 104 to initiate persistent connections with the servers 104 in any manner. In various embodiments, server 104 maintains a relatively constant connection with a messaging server 114 at a uniform resource locator (URL) or other network address that can be readily contacted on network 110. Messaging server 114 may simply be a TCP server, for example, that is automatically accessed when server 104 starts up, reboots, or otherwise initiates activity on network 110. In such cases, server 104 contacts the messaging server 114 (with the assistance of an appropriate routing or load balancing features), establishes a TCP or similar connection, and then awaits further action. This connection may be kept alive using relatively low bandwidth "keep alive" features that are part of the TCP protocol. By pre-establishing the connection from the server 104 to the messaging server 114, a pre-existing connection is maintained that can be used to send instructions or requests to the media server 104, even though the server is behind a firewall or other security mechanism. This is because many routers used in conventional firewalls will allow outgoing TCP connections that are originated within the trusted space while disallowing incoming TCP (and other) connections. After establishing a TCP or other connection from the server 104 to message server 114, that preexisting connection can be used to transmit an instruction to server 104 to establish a separate session with the host 116. This second session can be established as another outgoing TCP (or other protocol) communication from media server 104 that is not likely to be blocked by the firewall. That is, message server 114 can transmit an instruction over the pre-existing channel that directs server 104 to separately contact host 116 and to establish an appropriate communications session between host 116 and media server 104. This instruction may optionally include information about the host 116 or other party that is requesting the connection, although this information need not be present in all embodiments. When instructed to do so, server 104 suitably establishes a TCP or other session with the host 116 that can be used to exchange data and instructions, or to perform other tasks as described more fully below.

[0038] Moreover, messages sent from message server 114 can be provided to the media server 104 on a relatively immediate basis in some embodiments. That is, if a server 116 wishes to contact a particular media server 104, the server 116 need not wait until the media server 104 polls the server 116, but rather can provide a message over network 110 in real-time, or near real-time. "Real time" in this context refers to a communication or other action that occurs in response to a stimulus (e.g., a user input, network request or the like) without substantial delay between the stimulus and the action. "Real time" communications, while typically occurring on a generally immediate basis, may nevertheless encounter and account for network and processing delays and other delays that are inherent in practical data communications systems.

[0039] System 100 therefore allows host 116 to establish a real-time session with server 104 in response to requests received from clients 102. The user of client 102 contacts host 116 by directing a browser 103 or similar program to a URL or other address associated with host 116. Upon receiving a request from client 102, host 116 suitably contacts the appropriate media server 104 via message server 114. In various embodiments, message server 114 transmits a message to the media server 104 over a pre-established connection that directs the media server 104 to contact host 116 to establish a communications session. After the communication session is established, host 116 can obtain information about programming 105 available to media server 104, and to provide any instructions to media server 104 as desired. In various embodiments, host 116 is able to interact with client 102 using web constructs or the like to provide searching of content, remote control of server 104, viewing of programming stored at server 104, and/or any other features as desired.

[0040] Turning now to FIG. 2, an exemplary process 200 for establishing a control session between a client 102 and a media server 104 using host 116 over network 110 is shown. Generally speaking, process 200 involves establishing a session 212 between host 106 and media server 104 in response to a request 204 received from a client 102. The session 212 can be used to obtain information 213 from the media server 104, to provide instructions 216 that control the operations of media server 104, and/or for any other purpose. Host 116 also interacts with client 102 as desired to provide information, to receive instructions, and/or for any other purpose. Further embodiments may also provide streaming 218 or other sharing of media content from media server 104 to client 102, as appropriate.

[0041] Typically, media server 104 initially contacts a message server 114 at startup or any other initializing state to establish a pre-existing connection 202. As noted above, media server 104 may initialize a connection 202 with a message server 114 at startup, in response to a prior connection being dropped or reset, in response to a hard or soft re-boot of the media server 104, and/or at any other appropriate time. The connection 202 then persists as the media server 104 remains connected to network 110 to allow for subsequent real-time communications. As noted above, connection 202 may be useful in circumventing a router or other security mechanism that may prevent conventional communications between host 116 and a media server 104 that may be located on a home, office, campus or other network.

[0042] Client 102 provides an initial request 204 for an interactive session in any manner. In various embodiments, a user of client 102 activates a web browser application 103, a standalone media application and/or the like and provides a known URL or other address that is associated with the host 106. The client application then formats a hypertext transport protocol (HTTP) or other query that can be transported across network 110 for receipt and processing by host 116. Other embodiments may use other protocols or formats other than HTTP or other conventional web formats. In some embodiments, request 204 (and/or other communications between client 102 and host 116) contains an identifier that can be used to authenticate the user and/or to determine a particular media server 104 to be contacted. This identifier may directly identify the media server 104 in some embodiments, although other embodiments may instead identify a user or user's account based upon userid/password combinations, digital signatures or other credentials. Media servers 104 associated with the identified user or user account may be selected, as desired, for further activity. To that end, host 116 may provide any sort of authentication of client 102 or its users in some embodiments, or any other mechanisms for selecting particular media servers 104 for further activity. Such authentication and selection may be provided using any number of messages or other interactions between host 116 and client 102, as appropriate. Host 116 may further interact with a security database, authentication server and/or any other resources to identify and authenticate the user, as desired.

[0043] Host 116 processes the received request 204 to establish a session 212 with the remotely-located media server 104. In the example process 200 shown in FIG. 2, host 116 suitably directs a message server 114 to contact the appropriate media server 104 using the pre-existing connection 202. To that end, host 116 provides a request 206 to the message server 114 or its associated load balancer, which appropriately forwards the request 206 to server 114 for further processing. Message server 114 then provides a request 208 to the media server 104 via the preexisting connection 202 that directs the media server 104 to respond to the requesting host 116. The media server 104 appropriately responds 210 to the requesting host 116, and the media server 104 and host 116 then establish a session 212 with each other over network 110. Session 212 may be a conventional TCP session, for example, that allows for bi-directional data transfers in any convenient manner. Other embodiments may provide different types of sessions 212, including any sort of stateful or non-stateful bi-directional interchanges according to any protocols or other formats. In various embodiments, session 212 is a permanent or semi-permanent bi-directional interchange that is established in response to request 208 and that persists throughout the period of time that client 102 continues to provide instructions for control of media server 104. To that end, various embodiments may allow multiple commands, responses and/or other messages to be exchanged between host 116 and server 104 using a single, common session 212.

[0044] After session 212 is established between host 116 and the media server 104, information and commands may be exchanged in any manner. Media server 104 may provide information 213 about content 105 to host 116, for example, to allow for searching or other processing of the transferred information. In various embodiments, host 116 requests a listing of the media content 105 stored at the media server 104, as well as any metadata or other descriptive information (e.g., time of broadcast, program guide information, current preferences or other settings and/or the like) about the stored content 105 that may be available. Such information 213 may then be processed at host 116 and/or relayed to client 102, as desired.

[0045] Host 106 also interacts with client 102 to provide relevant information 215 and/or to obtain instructions 216 from the user as appropriate. To that end, information 213 may be filtered or otherwise processed at host 116 for delivery as information 215 and eventual display by client 102. In various embodiments, interaction 214 between client 102 and host 116 is implemented within the context of a conventional web session that allows active and/or passive web content to be displayed from presentation module 136 to browser 103; other embodiments may use different structures or techniques as desired.

[0046] The particular processing performed by host 106 may vary from embodiment to embodiment. In some implementations, a search engine 134 or other module is able to search and/or filter information 213 received from media server 104. Various embodiments may further obtain and process program guide information 115, information 112 about on-demand programming, and/or any other information as appropriate to provide a hybrid search feature. For example, some embodiments could allow a user to search for a particular program to obtain combined search results identifying the particular program in content 105 stored on the media server, in an upcoming broadcast, and/or in on-demand content. Hence, the flexibility and power of the search can be greatly enhanced by providing a combined search tool that accounts for different types of data, including information 213 obtained from the user's unique media server 104.

[0047] Other embodiments provide some or all of the information 213 about content 105 to client 102 to allow the client 102 to perform any desired actions. In various embodiments, client 102 provides instructions 216 to host 116 that identify desired actions to be performed by the remotely-located media server 104. Such actions may include, for example, recording a particular program, deleting a particular program, updating a setting or preference, controlling the playback of live or pre-recorded programming, and/or the like. Various embodiments may also facilitate streaming or other viewing of content 105 stored with media server 104 on client 102. In such embodiments, host 116 suitably receives the media stream 218 from media server 104 and relays the stream 218 to client 102. Other embodiments may provide streaming in any other manner.

[0048] Instructions 216 may be received at host 116 via interaction 214 in any manner. Commands 217 are then provided from host 116 to the remote server 104 via session 212 or the like to control the operation and/or media processing functions of media server 104. Various interactions between client 102, host 116 and media server 104 that make use of commands 217 are described below with respect to interfaces 300, 400 and 500. Generally speaking, the various tasks shown in connection with process 200 may be carried out with any sort of hardware, software and/or firmware logic within system 100. In various embodiments, the various steps of process 200 are carried out in response to software or firmware instructions stored in a memory, or on a disk drive and/or other storage associated with host 116, message server 114, client 102 and/or media server 104 as shown. Such instructions may be executed by any processor and/or other processing features within host 116, message server 114, media server 104, client 102 and/or the like as indicated in FIG. 2. The particular means used to implement each of the various functions shown in FIG. 2, then, could be any sort of processing hardware executing conventional software logic in any format that implements the various algorithms and techniques described herein. Each of the messages shown in FIG. 2 may be formatted using any conventional or proprietary formats compatible with network 110, such as any sort of TCP/IP compatible formats or protocols, although other protocols could be used in other embodiments.

[0049] FIGS. 3-5 show exemplary interfaces 300, 400 and 500 illustrating various features that may be provided in some embodiments. The actual features implemented may vary from embodiment to embodiment, however, and the graphical or other interface elements used to implement these features may similarly vary significantly. The graphical and spatial layout of the interfaces 300, 400 and 500, then, are purely exemplary. Each of the interfaces 300, 400, 500 may be generated in any manner. In various embodiments, some or all of interfaces 300, 400 and 500 are presented by browser 103 or another application on a suitable display that is associated with client 102. Such interfaces may include active and/or static content that is provided by presentation module 135 or the like.

[0050] FIG. 3 shows an exemplary interface 300 that may be used to provide guide information 115 to client 102, and to allow interactions with remote media server 104 based upon the guide information 115. As shown in FIG. 3, the exemplary interface 300 includes a media player 302, a guide window 308, a window 304 displaying information about the currently-viewed program, and/or any other interface features as desired.

[0051] Guide window 308 provides information about programming that is available from one or more sources. Such information may be obtained via interaction 214 with host 116, and may include program guide information 115 about upcoming broadcast programs, information about content 105 stored with media server 104, information 112 about on-demand programming, and any other information as desired. FIG. 3, for example, shows program guide information 115 for programming that can be received by an STB or other receiver associated with media server 104. In various embodiments, the viewer can simply select a currently-broadcast program to direct the remote server 104 to tune to the particular program and provide the program in a media stream 218 to client 102. In other embodiments, clicking on or otherwise selecting a program in window 308 could result in additional information about the program being displayed (e.g., in window 304), or any other actions as desired. The exemplary embodiment shown in FIG. 3 provides a "new" label on each of the programs that are believed to be first run (as opposed to re-runs) for viewer convenience. Other embodiments may not provide this feature, however, or the label may be activated/deactivated in response to a viewer preference, as appropriate.

[0052] Although the particular view of window 308 illustrated in FIG. 3 shows program guide information corresponding to a broadcast source, other views of window 308 may show information about stored programming 105 available to media server 104, on-demand content 112 available from a website or other source, and/or other content from any other source. Guide window 308 could equivalently display search results or any other listings of available programming, as desired. The different guide views may be selected using, for example, buttons 314, 316, 318 or the like. One or more scrolling buttons, sliders or other navigation features 312 may also be provided to allow viewing of additional information as desired.

[0053] In some implementations, information presented in window 308 may be selected and/or filtered in any manner. Filtering feature 322, for example, could allow a viewer to set a content filter that would prevent certain programming from being displayed in window 308 and/or viewed by media player 302. Filtering may be useful in establishing parental controls, for example, or other filters based upon content ratings, other guide data, or the like. Filters could be applied to block any programming that meets certain criteria (e.g., adult or violent content during certain hours). Other filters may be affirmatively applied such that only programming that meets certain criteria (e.g., only children's programming during certain hours) is displayed or viewed. Such filters may be established and/or modified using any sort of convenient interface. Further, filtering 322 may not be limited to viewing of programs on client 102; to the contrary, any filters established using client 102 may be provided to media server 104 via session 212 and applied across other displays, as desired. [0054] Interface 300 could also be used to set or change any settings or other preferences 320 associated with client 102 or media server 104. Such settings may allow the viewer to select, for example, preferences for particular programming genres, sports, networks, channels, actors/actresses or other viewing choices. Such information may be used to optimize (or at least improve) search results, or for any other purpose. Preferences may be set using any interface feature 320 or the like.

[0055] As noted above, searching may be provided through a search feature 324 or the like. In such embodiments, the viewer enters a keyword, title or other search term. Client 102 suitably forwards the search terms to host 116 via interaction 214, and host 116 processes the search (e.g., using search engine 134) to identify available programming that meets the search criteria. In various embodiments, host 116 is able to search for programming from multiple sources so that a complete result can be provided to client 102. For example, if the viewer searches for a particular program, host 116 may be able to identify one or more episodes of the program in stored content 105, in upcoming broadcasts (as identified by program guide information 115), in on-demand programming, and/or in any other available sources. These results can be returned from host 116 to client 102 for display in window 308 or elsewhere to allow the viewer to take any desired action. If the program is identified in a future broadcast, for example, the viewer may opt to direct the media server 104 to record the upcoming showing. If the program is available in content 105 from media server 104 and/or any other on-demand source, then the viewer may select the program for immediate viewing. These results may be inter-combined in any manner. For example, a search result could indicate that certain episodes of a program are stored on media server 104, that other episodes are available from an on-demand source for free or fee-based viewing, and/or that other episodes will be available to media server 104 in an upcoming broadcast. Other embodiments may provide different results or features, as desired.

[0056] Media player window 302 may correspond to media player 107 described above. In such embodiments, media player 107 renders and presents a media stream to the viewer based upon selected content. Content may be selected from programs listed in window 308, if such programs are currently available from media server 104 or another source. As noted above, various embodiments allow the viewer to select programs from guide window 308. The client 102 then provides an instruction 216 to host 116 via session 212 to appropriately direct media server 104 to begin streaming the selected programming or to take any other appropriate action. Media player 302 may also provide navigation controls 303 to rewind, stop, play, fast forward or otherwise modify the playback of the media stream 218. User commands received with respect to navigation controls 303 may be similarly relayed to media server 104 via host 116 and session 212, as appropriate.

[0057] Window 304, as shown in FIG. 3, presents information about the currently- selected content. The currently-selected program may correspond to content currently viewed in media player window 302, if the selected program is immediately available. Alternately, the currently-selected program could correspond to an upcoming program shown in a program guide, an on-demand program, or any other content within window 308 or elsewhere. In the example shown in FIG. 3, the currently-selected program is currently received at media server 104 and streamed to client 102 for immediate viewing. If the viewer wanted to record the program, a record button 306 is provided that would allow an instruction 216 to be sent to host 116, which in turn would direct media server 104 to record the program. Upcoming programs could be similarly recorded by simply selecting the upcoming program in a guide window 308, search result or the like, and then activating a record button 306 or other record feature within interface 300. Because such directions 217 could be provided to media server 104 in realtime across the current session 212, recording could be initiated on a relatively immediate basis in some embodiments.

[0058] FIG. 4 shows an exemplary interface 400 that could be used in some implementations to manage the content 105 stored with media server 104. Interface 400, as illustrated in FIG. 4, includes a listing 408 of programming content 105 stored on media server 104, as well as an information window 404 that provides a current status of a disk, solid state drive and/or other data storage medium associated with media server 104. In the particular example shown in FIG. 4, programs are grouped by program title, with the number of available episodes 414 indicated as well. Other embodiments may organize and present programming listing 408 in any desired manner. A search feature 324 as described above may also be provided, as may any number of other additional or alternate features.

[0059] Interface 400 allows the viewer to manage the contents of the DVR or other repository of content 105 from client 102. Particular programs may be played from server 104, for example, by selecting a "play" feature 412 in interface 400. Selecting such a feature would result in an instruction 216 being sent to host 116, which in turn would send an appropriate message 217 via session 212 to direct the remote media server 104 to begin streaming the selected program. Messages 217 could also be generated using "erase" features 410, which would result in an instruction 216 to be provided to host 116, which in turn would direct media server 104 to erase the indicated program. Media server 104 may then provide updated information 213 in some embodiments so that listing 408 and information 404 remain accurate. Still other instructions 216 may be used, in some embodiments, to control the operation of media server 104. A mobile phone, computer or network-enabled remote control, for example, could interact with host 116 to select programming, to play, pause, record, forward/rewind or to perform other control functions as desired. Other features and functions may be provided in any number of alternate embodiments.

[0060] FIG. 5 shows an exemplary interface 500 that allows a user to select from conflicting recordings. In various embodiments, the media server 104 may be able to record only a limited number of simultaneous programs. Many conventional STBs, for example, may have tuner capabilities to receive and record two simultaneous programs, but not a third. Hence, if an instruction is received to record a third program, the viewer may be requested to select which program would not be recorded. Interface 500 shows one example of a window that could be provided that would allow the viewer to select which of program would not be recorded by activating an appropriate feature 502, 504, 506 that corresponds to the program to be skipped. Identification of recording conflicts could occur in any manner. In various embodiments, media server 104 provides a listing of currently- planned recordings as part of information 213. Such information may be provided in response to a request by host 116, or may be automatically provided as desired. In such embodiments, host 116 identifies when conflicting recordings are requested in instructions 216 from client 102, and provides interface 500 or the like in response. In other embodiments, interface 500 is generated in response to a message from media server 104 indicating that a recording conflict exists, and providing sufficient information for the viewer to resolve the conflict. Other processes and techniques may be formulated in any number of alternate embodiments. [0061] FIGS. 1-5 therefore illustrate at least one example of a system 100 that could be used to remotely control a DVR, STB or other receiver, placeshifting device, file server or other media server 104 via a network 110. In some embodiments, the media server 104 is contacted using a persistent connection that the media server 104 previously established with a messaging server 114 to create a network session 212 with host 116; because this session allows for real-time (or near real-time) interaction between the host 116 and server 104, any number of commands 217 can be provided from host 116 to be executed on media server 104. Such commands 217 can be provided in response to user inputs at a client 102 using, for example, conventional active or static interface techniques implemented within a web browser 103 or the like. Various embodiments could use commands 217 to direct the recording, erasing, playing or other processing of programming content 105 stored at the media server 104. Other embodiments may use commands 217 to update settings or preferences, to control the operation of media server 104, and/or to take any other actions as desired.

[0062] While several exemplary embodiments have been presented in the foregoing detailed description, it should be appreciated that a vast number of alternate but equivalent variations exist, and the examples presented herein are not intended to limit the scope, applicability, or configuration of the invention in any way. To the contrary, various changes may be made in the function and arrangement of elements described without departing from the scope of the claims and their legal equivalents. The term "exemplary" is used herein to represent one example, instance or illustration that may have any number of alternates. Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations.