Patent Grant
11722745
The present disclosure generally relates to systems and methods for searching lists of media content.
Media content can now be received from any number of different sources. Broadcast television content, for example, can typically be received at set-top box (STB) or other receiver that receives a direct broadcast satellite (DBS), cable and/or terrestrial broadcast signal. Received content may be stored in a personal or digital video recorder (DVR) or the like for viewing at a later time (“time shifting”). Frequently, live or pre-recorded content can also be “placeshifted” over the Internet or another network to allow viewing at remote locations away from the viewer's primary television set. In addition to the wide variety of options in viewing broadcast media content, even more content is increasingly becoming available “on demand” from any number of file based or streaming sources, including various network-based services that provide access to a wealth of on-demand programming.
As content becomes available from a multitude of sources, however, it can be increasingly difficult to locate desired programming. If a viewer wishes to locate a particular program or episode, for example, he or she would typically conduct separate searches of broadcast program guides, on-demand libraries, DVR contents and/or the like to try and find the desired program. Moreover, the wealth of content available often makes broad searches impractical. That is, conventional searches for broad categories of programming (e.g., “comedy”) can be impractical, since the number of results returned from such searches often far exceeds the number of results that can be readily processed by the viewer.
As a result, it is now desirable to create systems and methods for improved searching of media content. Other desirable features and characteristics may also become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and this background section.
According to various exemplary embodiments, systems and/or methods for searching media content are provided. In some implementations, the user is able to provide search criteria (e.g., a program name, program genre, or the like) to a search engine executing at set-top box, digital video recorder or other media device, or at a network host communicating with the media device, to identify instances of the search criteria available from multiple programming sources. For example, a search of a particular program name may identify instances of the program available from an electronic guide of upcoming broadcasts, from programs stored on the user's digital video recorder, and/or from available on-demand content. In such embodiments, a combined search result can be provided that allows the viewer to identify the desired programming that can be obtained from any number of different sources. Various embodiments may additionally or alternately prioritize the search results obtained from one or more sources using content obtained from the user's digital video recorder and/or using any other information as desired.
Some embodiments provide a method executable by a set-top box, television receiver, placeshifting device, digital video recorder, network guide server and/or other data processing system to identify desired media programming. The method suitably comprises receiving, by the data processing system, search criteria provided by a user that indicates the desired media programming, searching, by the data processing system, for the search criteria in both of a first listing of media programming available from a first source and in a second listing of media programming available from a second source that is different from the first source, and providing a search result from the data processing system that identifies instances of the search criteria found in both the first and the second listings of media programming.
Other embodiments provide a network guide server or other system that communicates via a network with a client and with 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 configured to receive a request 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 receive search criteria from the client, to search for the search criteria in both program guide information associated with the media server and in the information about the media content stored at the media server, and to provide a search result to the client that identifies instances of the search criteria found in both the program guide information and in the media content stored at the media server.
Still other embodiments provide a set-top box, television receiver, placeshifting device and/or other system. The system suitably comprises a receiver, a digital video recorder configured to store a plurality of programs, and a controller. The receiver is configured to receive television programming and an electronic program guide, wherein the electronic program guide describes the television programming that is available to be received using the receiver. The controller is configured to receive search criteria from a user, to search for the search criteria in both the electronic program guide and in the plurality of programs stored on the digital video recorder, and to provide a combined search result to the user that identifies instances of the search criteria found in both the electronic program guide and in the plurality of programs stored on the digital video recorder.
Still other embodiments provide a method executable by a set-top box, television receiver, placeshifting device, digital video recorder, network guide server and/or other data processing system to prioritize search results. The method suitably comprises obtaining search results that identify a plurality of programs, determining a score for each of the plurality of programs based at least in part upon whether the program is associated with the content recorded by the digital video recorder, and ranking the plurality of programs according to the score determined for each program.
Various other embodiments, aspects and features are described in more detail below.
Exemplary embodiments will hereinafter be described in conjunction with the following drawing figures, wherein like numerals denote like elements, and
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.
Searching for media programming may consider real-time information about programs stored on the user's DVR, STB or other media server, as well as electronic program guide information, information about on-demand programming, information obtained from another DVR or other storage device, and/or any other information as desired. Searching may additionally or alternately use information about recorded programs (e.g., programs recorded on a DVR) as well as other information to prioritize search results so that the programs most likely to appeal to the viewer are given higher priority when the results are presented to the user. Although some embodiments provide local searching on a STB or similar media device, other embodiments provide searching though an online guide server or other host that communicates in real time with the media device. The various techniques and processes described below, then, may be equivalently performed on any sort of media device, or on any sort of networked server or other host that communicates with a remotely-located media device over a network.
Turning now to the drawing figures,
In other embodiments, media device 104 additionally or alternately interacts with a remotely-located guide server 116 that obtains information about programming stored at media device 104 and that is able to search for user-provided search criteria in program guide data, data about the programs stored with media device 104, on-demand data and/or the like. In such embodiments, the guide server 116 may be able to provide search results to a web browser 103, media player and/or other program executing on a personal computer, mobile telephone, network enabled display, network-enabled remote control or any other client 102.
Both local and remote processing of search features are described below. Some implementations may provide robust searching of content stored in DVR 105, as well as program guide information 115, information 112 about on-demand programming, and/or other information as desired in addition to information obtained from media device 104. Again, both local and remote processing need not be present in all embodiments.
As noted above, some embodiments may provide local searching of media programming at media device 104. This searching may consider, for example, program guide data stored at the media device 104, files stored on a DVR feature or the like at media device 104, and/or any other content that may be available to media device 104 via network 110 or any sort of receiver 136, as appropriate.
To that end, media device 104 is any component, hardware and/or the like capable of receiving and processing media content. In some embodiments, media device 104 is a set-top box (STB) or similar system that is able to receive television programming and/or to record certain programs that can be viewed on a display 106. Some embodiments of media device 104 will therefore include a receiver interface 136 for receiving satellite, cable and/or broadcast programming signals, as well as a personal or other digital video recorder (DVR) 105 feature, a display interface 143 for providing imagery to display 106, and a controller 130 that directs the operations of the device 104 as appropriate. Media device 104 may also include an interface 141 to network no and/or an input/output interface 137 to a remote control or other device for providing user inputs to media device 104, as appropriate. The components in media device 104 may be provided within a common chassis or housing as shown in
Media device 104 may be logically and physically implemented in any manner.
Controller 130 is any sort of hardware, software and/or firmware capable of directing the operations of media device 104. In various embodiments, controller 130 includes software or firmware logic residing in memory 133 and executing on any sort of processor 131, such as any sort of microprocessor, microcontroller, digital signal processor or the like. In various embodiments, media device 104 is based upon a “system on chip” (SoC) implementation that incorporates a hybrid microcontroller with memory, input/output and other features to perform the various signal processing and other actions of media device 104. Different types of SoC and other integrated hardware implementations are available from Texas Instruments, Conexant Systems, Broadcom Inc., and many other suppliers as appropriate. Other embodiments may implement controller 130 and/or the other features of media device 104 with any number of discrete and/or integrated processing components (e.g., any sort of microprocessor or microcontroller), memories, input/output features and/or other features as desired.
Content stored in DVR 105 may be any sort of file-based programming or other content that is accessible to media device 104. In various embodiments, DVR 105 stores programming that is received from an internal or external television receiver, such as receiver 136. DVR 105 may also store 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 in DVR 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.
In various embodiments, controller 130 executes a search program 135 that allows local searching of program guide content, content stored in DVR 105, on-demand content available via network 110 or receiver 136, and/or any other information as desired. Search program 135 may additionally or alternately prioritize search results in any manner. The various searching processes described below in conjunction with
In various embodiments, search program 135 is able to obtain search criteria provided by the user and to identify instances of programming meeting the search criteria that are available from any number of different sources. Search program 135 may locate particular programs, for example, that are stored on DVR 105 as well as programs that are identified in electronic program guide (EPG) data relating to broadcast content receivable via receiver 136. Many different types of media device 104 are able to receive EPG data via receiver 136 and/or network 110. This information may be readily searched at the media device 104, and search results can be combined with search results from DVR contents, on-demand sources and/or the like. In an exemplary STB implementation, for example, a user may search for a particular program, and search program 135 may be able to locate the particular program in content stored on DVR 105 and in current or upcoming broadcasts receivable by receiver 136, as well as in on-demand programming that could be received via network 110 or via receiver 136. Additional details about various searching techniques and processes are provided below.
Like the local processing described above, various remote processing embodiments allow programming from various sources to be simultaneously searched so that a combined result can be returned to the user. Such searching may be performed by a guide server or similar host 116 that obtains information about programming stored at a media device 104, and that combines information about the stored programming with information obtained from other sources (e.g., EPG information 115, information about on-demand programming 112, and/or the like). Guide server host 116 may be, for example, a server that is accessible via a network no to provide convenient access for any number of clients 102.
In various embodiments, the user is able to connect to the guide server host 116 using any appropriate client 102. The user may login or otherwise be authenticated by the host 116. Upon successful authentication, host 116 suitably establishes a connection 144 to a media device 104 that is associated with the user. This connection 144 can be used to obtain information about programming stored at device 104, or for any other purpose as described more fully below.
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, remote controls, networked displays and/or any other devices capable of communicating on network 110.
In the embodiment shown in
In some embodiments, client 102 further includes a media player application 107. This media player 107 may be a standalone player, or the media player 107 may be implemented as a plugin or other applet that runs within browser 103 as desired. In some embodiments, media player 107 is initially obtained from a networked host, such as host 116. The player 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 directly on client 102; such clients 102 may nevertheless be able to interact with host 116 to search for particular programming, to select programs to record, to change preferences, or to take other actions related to media device 104 as desired.
Network no is any digital or other communications network capable of transmitting messages between senders (e.g., media device 104) and receivers (e.g., media device 104). In various embodiments, network no includes any number of public or private data connections, links or networks supporting any number of communications protocols. Network no 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 no 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.
Remote processing may operate in conjunction with any sort of media device 104 as desired. In various embodiments, media device 104 may be any device or system communicating on network 110 that is capable of receiving, recording, placeshifting and/or otherwise processing media content. As noted above, various embodiments of media device 104 include a personal or digital video recorder (DVR) feature 105 that allows the media device 104 to record received programming for later viewing. A DVR may be 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 device 104 suitable for remote processing 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 of any sort. Still other embodiments of media device 104 could implement a networked gaming server or other media service as desired.
Some embodiments of system 100 may simply use host 116 to provide searching of media programming available from one or more sources. Other embodiments, however, may allow for streaming or other playing of media content 105 from media device 104 to client 102. To that end, various embodiments of media device 104 may incorporate placeshifting functionality to support viewing of content 105 over network 110 (e.g., by client 102). In some embodiments, media device 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 110. Examples of placeshifting devices that may be used in some embodiments of media device 104 could include any of the various SLINGBOX products available from Sling Media of Foster City, Calif., although other products or servers 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. Media device 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.
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 media devices 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.
Although
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
Various embodiments also provide search engine logic 134 as desired; this search engine may perform an integrated search of information about content that is stored with one or more remote media devices 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. Further information about exemplary search processes that may be implemented using search engine logic 134 is provided below, for example in conjunction with
Control module 132 contains any appropriate programming logic to establish sessions over network no with one or more media devices 104 in response to requests received from clients 102. Such sessions can be used to retrieve information from the media device 104 and/or to provide instructions to the media server as desired. As described below, sessions with media devices 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.
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.
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 media device 104, viewing of programming stored at media device 104, and/or any other features as desired. 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, Calif. or the .NET environment available from Microsoft Corporation of Redmond, Wash. 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, mass storage, removable media, or any other medium) that is accessible to guide server application 128.
Providing a network host that is able to perform searching that considers content stored on a remotely-located media server can present several challenges. Firewalls and other security mechanisms, for example, can make direct communications between the searching host and the media server difficult. As a result, various embodiments provide a system that includes a message server or the like that has established a pre-existing connection 140 with the media server. This pre-existing connection 140 can be leveraged to establish an online session between the host and the media server that allows the host to retrieve real-time (or near real-time) 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.
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 144 between the guide server host 116 and the remote media device 104 through the use of a messaging server 114 that maintains a pre-existing connection 140 with the media server. When a user wants to open a control or other session 144 with the remote media server 104, the pre-existing connection 140 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. Various embodiments therefore provide any number of message servers 114 that are each capable of maintaining pre-existing connections 140 over network 110 with one or more media devices 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.
Message server 114 suitably receives requests from one or more media devices 104 to initiate persistent connections 140 with the media devices 104 in any manner. In various embodiments, each device 104 maintains a relatively constant connection 140 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 media device 104 starts up, reboots, or otherwise initiates activity on network 110. In such cases, media device 104 contacts the messaging server 114 (with the assistance of an appropriate routing or load balancing features), establishes a TCP or similar connection 140, 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.
The pre-existing connection 140 that can be used to send instructions or requests to the media device 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 140 from the media device 104 to message server 114, that pre-existing connection can be used to transmit an instruction from message server 114 to media device 104 to establish a separate session 144 with the host 116. This second session 144 can be established as another outgoing TCP (or other protocol) communication from media device 104 that is not likely to be blocked by a firewall. That is, message server 114 can transmit an instruction over the pre-existing channel that directs media device 104 to separately contact host 116. 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, media device 104 suitably establishes a TCP or other session 144 with the host 116 that can be used to exchange data and instructions, or to perform other tasks as described more fully below.
Messages sent from message server 114 can then be provided to the media device 104 on a relatively immediate basis. That is, if a server 116 wishes to contact a particular media device 104, the server 116 need not wait until the media device 104 polls the server 116, but rather can provide a message over connection no in real-time, or near real-time. 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 device 104, for example, some implementations of the host 116 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. “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. Various examples of message servers 114 are described in co-pending application (cite to message server app), although other embodiments may incorporate different types of message servers or the like.
Various embodiments of system 100 therefore allow host 116 to establish a real-time or near-real-time session with media device 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 device 104 by providing an appropriate message 142 to message server 114. In various embodiments, message server 114 responds to message 142 by relaying or transmitting the message to the media device 104 over the pre-established connection 140. After receiving the message over connection 140, the media device 104 contacts host 116 to establish a real-time or other communications session 144. This session 144 is any bi-directional communication that allows messages to be sent and received between host 116 and media device 104, such as a conventional TCP session. After the communication session 144 is established, host 116 can obtain information about programming 105 available to media device 104 using the session 144. Host 116 can also provide any instructions to media device 104 as desired. In various embodiments, multiple messages are interchanged between host 116 and media device 104 using a common session 144 that persists throughout the duration of the interaction between host 116 and media device 104.
One example of a combined search process that is able to provide a combined result that identifies content from multiple sources is described in
Search process 200 may be implemented in any manner. In some embodiments, process 200 provides a local searching feature that can be implemented using search feature 135 of a set-top box or other media device 104. In other embodiments, process 200 may be executed by a search engine 134 executing within a guide server or other host 116 to provide remote searching as appropriate. Still other embodiments may provide integrated searching using the techniques shown in
Searchable information may be obtained in any manner (function 202). In various embodiments, process 200 attempts to locate particular search criteria in content received from a television source (e.g., receiver 136), content stored on a DVR (e.g., DVR 105), content available from an on-demand source 112, and/or the like. In various embodiments, some of the information searched may be stored locally with the engine or application that is performing the search. An STB, standalone DVR 105 and/or other media device 104 that performs a local search process 200, for example, may have locally-stored electronic program guide (EPG) data about current and upcoming programming, as well as a listing of content stored in the DVR 105. This EPG data may be obtained from a satellite, cable, broadcast or other source (e.g., signals received by receiver 136) in some cases, or EPG data may be alternately obtained from a server 115 operating on network 110, or from any other source.
A user of a search feature 134 and/or 135 may first authenticate with the guide server host 116 or any other authentication service using a userid/password combination or other credential so that the particular user can be identified and the search experience can be customized to the particular user by considering only content that is actually available to that particular user. This authentication may be readily implemented between client 102 and server host 116 using conventional techniques. After the user is authenticated, search feature 134 and/or 135 suitably obtains search information that corresponds to the particular user. Host 116 may obtain EPG information from a server 115 or other source, for example, that corresponds to the user's particular media device 104 so that the searching considers only the programming that is actually available to the user.
Further, search feature 134 and/or 135 may obtain the user's actual list of stored programs on one or more DVRs 105 and/or other sources, as appropriate. This information may be obtained in any manner; in various embodiments, the guide server host 116 provides a message 142 (
In either local or remote processing embodiments, on-demand content and guide information about the on-demand content may be obtained from any source 112. Such information may be obtained on a query-based basis (e.g., wherein search features 134 and/or 135 provide search criteria to a server 112 to obtain particular results regarding the provided criteria). Alternately, a database of available on-demand content may be provided on any regular or irregular basis so that the search feature 134 and/or 135 can search the database as desired.
Search criteria may be received in any manner (function 204). In local processing embodiments, search criteria may be received using an electronic program guide feature or other conventional user interface features of the STB, DVR or other local media device 104. In remote processing embodiments, search criteria may be obtained from the user via client 102, which may provide a text entry window or other user interface feature that allows entry of search criteria into browser 103 or the like. Information entered at browser 103 may be provided, using conventional network constructs, from client 102 to host 116 for further processing.
Search query information may be provided in any format, and may contain any desired information. In some embodiments, a viewer may be able to variously search for content by title, actor/actress name, channel number, network, genre and/or any other criteria as desired. A viewer may search for episodes of “The Colbert Report”, for example, by entering the words “Colbert” and “report” into a text window or other interface feature. Various embodiments of search engine 134/135 may also allow searching for “News”, “Comedy”, “channel 51”, “ESPN” or any other search criteria as desired.
Searching may be performed in any manner (function 206) that identifies the search criteria in the available content. In various embodiments, simple GREP-type keyword searching may be sufficient to identify the presence of some or all words in the search criteria in the lists of available content. In other embodiments, more advanced searching (e.g., searching that considers approximate matches or the like) may be performed. As noted above, some searching may involve transmitting a query to a remote server 112, 115 or the like.
Searching of multiple lists or databases (e.g., lists of EPG programming or contents of a DVR 105) may be searched sequentially or in parallel, or in any other convenient manner. The results of the search may then be integrated in any manner (function 208) to obtain a combined search result. Integrating may involve simply formatting the results of two or more searches in any manner.
Search results may also be prioritized, as desired. In some searches, the list of results may provide more options than the user can quickly digest. An open-ended search query (e.g., a search for “movies” or “comedy”), for example, could return dozens of results stored on a DVR or hundreds (or more) options in upcoming programming or on-demand choices. Similarly, some keywords may have different meanings in different contexts: a search for “bears”, for example, might produce results that identify nature programs in addition to Chicago Bears football games. Various embodiments therefore prioritize the search results in any manner so that the options most likely to appeal to the user are listed first, or otherwise made more prominent than results that are less likely to be appealing. One technique for optimizing search results is shown in
Search results may be provided to the user in any manner (function 212). In local processing embodiments, results may be simply provided on display 106 via interface 143. Remote processing embodiments could provide a web page or other interface from host 116 to client 102 to present the results to the user as desired.
An example of an interface 300 showing combined search result 300 is shown in
In the example shown in
After being presented with the combined information from multiple sources, the user is able to conveniently select desired programming from any of the available sources using a common search result 300, as shown. In various embodiments, the user may be able to play identified content, erase identified content, set timers for future recordings, and/or take any other actions as desired. A “play” feature 312 and/or an erase feature 310 may be provided for episodes 302 stored on DVR 105, for example. Upcoming episodes 304 may be recorded by selecting a “record” feature 314 as appropriate, and/or currently available content (e.g., current broadcasts from receiver 136 or on-demand programs 306) may be retrieved or played using a “play” feature 316, as desired. The particular features and interface elements used to implement the various features may vary from embodiment to embodiment, as appropriate.
In local processing implementations, the “play”, “record”, “erase” or other features may be processed locally by a STB or other media device 104. In remote processing implementations, guide server host 116 may respond to user inputs by directing the remote media device 104 through messages transmitted over session 144 (
Again, the particular appearance, layout, arrangement, content and features provided by interface 300 may vary significantly from embodiment to embodiment. In the illustrated example, however, the user is able to locally or remotely perform a simultaneous search for programming content available from a DVR 105, a broadcast, cable or satellite source 136, and/or an on-demand source 112, and to obtain a combined search result. This combined result may allow further actions to obtain, view, delete or otherwise process the content received from any number of different sources.
Various embodiments may provide additional or alternate features beyond integrated searching.
Generally speaking, process 400 assigns a numeric weight to each of the search results. The weight is assigned based upon various factors, such as viewer preferences and whether the viewer has previously expressed an interest in the particular program. If a viewer has previously recorded episodes of the program or set a timer for future episodes, for example, the weighting can be increased so that the program is made more prominent in the search results. Conversely, the weight can be reduced if the recorded programs remain relatively unwatched for any length of time.
The search process may be performed as described above, or in any other manner. In various embodiments, search information is obtained (function 402) in any manner. Search criteria may be received, for example, from a local or remote interface, and information about the programming content to be searched may be similarly processed using any sort of local or remote data processing system as desired. Various implementations, for example, could receive search criteria from the user as well as information about the contents of DVR 105, EPG data, on-demand data and/or the like in a manner similar to that described with respect to functions 202 and 204 above.
Search results are obtained in any manner (function 404), such as in a manner similar to function 206 above. Various embodiments of process 400 may be applied to search results obtained from a single source of programming data (e.g., EPG data, or information about programs stored on DVR 105), however. It is not necessary that the search results be obtained from multiple sources.
Search results may be prioritized in any manner, considering any type of factors or other criteria. In various embodiments, each program or other item identified in the search result is individually considered (function 406) to assign a numeric or similar weighting that indicates the priority of the particular result. Other embodiments may group items (e.g., different episodes of the same program) in any manner to expedite processing, to further streamline the information provided to the viewer, and/or for any other purpose. In the embodiment shown in
Various embodiments consider user preferences in adjusting the weight of the item (function 410). If a user has previously indicated a “like” or “dislike” of the program, for example, the weight can be correspondingly increased (function 414) or decreased (function 412). While
The weight assigned to the particular item may be further adjusted based upon whether the viewer has previously indicated an interest in the programming series associated with the item (function 416). If a viewer has previously recorded different episodes of the same program, for example, the weight assigned to that item can be increased (function 418).
Even if the user does not have current recordings of a program on his or her DVR 106, the user may still have a particular interest in the program or series if he or she has set a recording timer (function 422) for the item considered, or another program in the same series. In such embodiments, the weight for the item may be increased (function 424) by an appropriate amount to reflect the user's interest.
After weights have been determined for an appropriate number of results (function 406), the results can be ranked, sorted or otherwise ordered (function 426), and provided as an output (function 428) as desired. As noted above, results may be provided on a display 106, on a browser application 103 executing on a client 102, or in any other manner.
The particular process 400 and weighting values shown in
This application is a continuation of U.S. patent application Ser. No. 15/019,351, filed Feb. 9, 2016 and is incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8379926 | Kanhere | Feb 2013 | B2 |
| 20020042921 | Ellis | Apr 2002 | A1 |
| 20040105573 | Neumann | Jun 2004 | A1 |
| 20040194141 | Sanders | Sep 2004 | A1 |
| 20050155077 | Lawrence | Jul 2005 | A1 |
| 20090009513 | van den Hengel | Jan 2009 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20210368242 A1 | Nov 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16129431 | Sep 2018 | US |
| Child | 17444649 | US | |
| Parent | 15019351 | Feb 2016 | US |
| Child | 16129431 | US | |
| Parent | 12648024 | Dec 2009 | US |
| Child | 15019351 | US |
