Referring initially to
It is to be further understood that all or parts of the Internet video service system 20 may be implemented in an adapter housing that is local to the TV 12 and indeed that may be integrated within the housing of the TV 12. Or, all or parts of the Internet video service system 20 may be implemented remotely from the TV 12 outside the dwelling in which the TV 12 is located and accessible by the TV 12 through wired or wireless network connections.
With the above overview in mind, attention is directed to the Internet video service system 20 of
The Internet video service system 20 may further include the following non-limiting elements. A content download processor 26 with associated data store 28 may be provided to download and store audio-video content from the Internet. Also, a TV electronic program guide (EPG) processor 30 with associated data store 32 may be provided to establish all or parts of a TV EPG that can include broadcasting times for both TV programming as well as A/V content in the content data store 28. A registration processor 34 with associated data store 36 can be provided to facilitate user registration with the system 20 using registration principles known in the art. Also, a billing processor 38 with data store 40 can be provided for billing purposes, e.g., to bill users based on each piece of content accessed from the system 20, or based on time accessing the system 20, etc., and a management processor 42 with data store 44 can be provided to coordinate the activities of the above-discussed processors. As mentioned previously, all or some of the above functions may be undertaken by a single processor if desired.
Concluding the description of
Now referring to
The other managers 46, 50, 52, 54, 56 of the net navigator 22 may each communicate with the TV 12 as shown. Also, the U/I manager 46, which provides user interface pages and style sheets to the TV 12, may communicate with a U/I data store 58, which also communicates with the management processor 42. The list manager 50, image manager 52, and tracking manager 54 may each communicate with a published content link data store, which is accessed by a link audit bot 62 under control of a processor for confirming which links (e.g., a uniform resource identifier (URI)) in a link record data store 60 are valid links. Content from the Internet is downloaded to a content submission server or component 64 and links to the content are stored in a candidate content link data store 66, which is also accessed by a net spider bot 68 for purposes to be shortly disclosed.
With the above description of
While not reflected in the logical drawing of
In essence, the net navigator may be conceptualized as being broken into two major operational elements, the six modules (“managers”) 46-56 and the enterprise backend shown at the left in
The UI manager 46 can execute on an Apache-based web server application handling incoming requests from TV clients. The purpose of the UI manager 46 is to deliver user interface templates that make up the look and feel of the Internet video provision product on the TV 12, such as the example screen shots shown in
In contrast, if the service 20 is selected, the UI manager 46 is accessed and in response, a combination of HTML, CSS and ECMAscrlpt (Javascript) payloads are delivered to the client. Execution of the scripts delivered by the UI manager 46 can result in the rendering of a user interface (“UI”, described further below) and the accessing of the content list manager 50 and image manager 52 to populate the UI with images of the A/V content that is available. The TV may query in hypertext transfer protocol (HTTP) and the manager 46 may respond in extensible markup language (XML).
The registration manager 48, which may be embodied by the registration processor 34 shown in
The list manager 50 can execute on an Apache-based web server handling incoming queries from the TV 12 for link record lists. The list manager 50 may execute a PhP script engine to create SQL queries to the link record database 60 and to format returned data for transmission to the TV 12 through the Apache web server. The TV may query in hypertext transfer protocol (HTTP) and the manager 50 may respond in extensible markup language (XML).
The image manager 52 may execute on an Apache-based web server handling incoming queries from the TV 12 for thumbnail images. The image manager 52 may execute a PhP script engine to create SQL queries to the link record database 60 for image retrieval and to format returned images for transmission to the TV 12 through the Apache web server. The TV may query in hypertext transfer protocol (HTTP) and the manager 50 may respond in extensible markup language (XML) and JPEG.
The tracking manager 54 provides a method for logging client usage of a service of access to a particular A/V content. Its purpose is to collect usage statistics for gauging content/service popularity, billing or other business processes. The TV may query in hypertext transfer protocol (HTTP) and the manager 54 may respond in HTTP.
When a client makes a request for a content link record, the record returned can include a URI for the target link. The listed URI can be a proxy URI which, when subsequently accessed, provides a redirect of the client to the real URI for the link. When the proxy URI is accessed, the manager script increments the usage count associated with the content or service. This allows usage tracking, billing, etc. in real time without resorting to cumbersome tracking methods such as client polling, etc.
Preferably, the target URI points to the tracking manager 54. The tracking manager 54, upon receiving the request, parses the request string to recover the actual service URI data contained within the parameter string of the request. The service URI can be obscured if desired when created and hosted by imposing the simple Caesar cipher known as “ROT13”, in which each alphabetic character in a string is replaced by the letter that is thirteen places further along in the alphabet, wrapping back to the beginning if necessary, preserving case. Numbers, symbols, whitespace, and all other characters may be left unchanged. Thus, the tracking manager 54 of the Internet video service system 20 acts as a gatekeeper between the TV 12 and the video provider to ensure incompatible content is filtered out and to abstract the URI of each video so the user does not have to enter long alphanumeric URIs.
The upgrade manager 56 provides two functions. The first function is to provide information regarding the current software version in response to queries by the TV 12. The second function is to host software images for download to the TV 12 upon request. The update manager 56 can execute on an Apache-based web server handling incoming queries from the TV 12 in HTTP for software version information that may be returned in XML.
Turning now to the various back end elements, the UI database 58 may be, without limitation, a “MySQL” database containing the HTML, CSS and ECMAscrlpt (Javascript) elements comprising various UI templates. The link database 60, on the other hand, contains all information regarding available A/V content or service aggregators. It may be implemented as a MySQL database. The two main data types accessible through client interaction are content link records and image thumbnails. Both data types can be used to describe specific A/V opportunities or external content aggregation services that may be promoted to the TV 12. Each data type can be accessed through a separate manager but held in a single common database. The images in the image manager 52 may be one-way indexed through a URI pointer field contained in the link record, and there need be no reverse linkage from an image to a content link record. In this way, one image may be multiply referenced by an arbitrary group of content link records, allowing flexibility and storage savings. An example for such a record might be a “not available” icon or “adult content” icon that would be chosen for use on certain content records in lieu of an actual Image from the content itself.
In non-limiting implementations each data record may contain the following fields.
Thumbnail PEG still image
Content Genre
Content Location URI
Content Type
Content Video Format
Content Audio Format
Content Title
Content Description
Content Rating
Popularity Index
Addition Date
Content Duration
Content Description (Short)
Content Description (Long)
Content Thumbnail URI (Points to image manager 52 location)
Content URI
Rating
Genre
Content Duration
Addition Date
Popularity Index
Content Type
Content Video Codec
Content Video Format
Content Video Bitrate
Video Interlace (Yes/No)
Video Frame Rate
Video Bit Rate
Content Audio Codec
Content Audio Format
Content Audio Bit Rate
A/V Synchronized Content Flag
Last audit timestamp
Viewable flag
Service flag
Turning to the candidate content links database 66, this database architecturally may be a mirror to the published content links database 60, but the purpose of the candidate content links database 66 is to act as an intermediate repository of content information that is identified, manually submitted, etc. and pending approval to be published as part of the service offering. The candidate content links database 66 also serves as a workplace to hold links while thumbnails (or other icons) are added, descriptions are created, etc. as part of the content link workflow.
The management system 42 may embody a MySQL database and manager that allows remote management of the entire infrastructure, collects usage information, monitors system health and throughput. It may generate reports based upon the collected statistics stored In the database.
The net spider 'bot (NSB) 68 can be an autonomous entity that continuously scans the world wide web looking for instances of publicly available A/V content meeting predefined criteria for stream format, codec type, duration, video format, etc. This process may include tunneling through the HTML source code to find embedded links to A/V content. When a potential match is found, the NSB 68 may create a new entry in the candidate content link database 66 and can populate the fields with the information it can determine. Some of this information may be contextual, such as adult terms used on the hosting page may default the rating to “adult”. The NSB 68 may further report the find to the management system 42 for review.
The link bot 62, when implemented, can be used to identify content owners and email them a link to a form requesting permission to host the content and soliciting information regarding genre, rating, title, description, etc. If the respondent grants permission, the page is reviewed and added to the published content link database 60. The publishing process can be completed upon the physical transfer of a record in the candidate content link database 66 to the published content link database 60.
Individuals, notified through advertising, promotions or word of mouth, can directly access the content submit server 64 to grant permission to content links they volunteer. They provide the location and other metadata, submit the thumbnail, etc. Links obtained in this manner can also be put into a pending state on the candidate content link server for the same review and approval process as content sifted by the NSB 68.
The link audit 'bot (LAB) 62 is an autonomous entity that periodically reviews the contents of the published content link database 60 to confirm that the content is still valid and available. The LAB 62, to reduce loading of the production managers, can directly interpret the URI for content location and extract/convert the ROT13 encoded return URI to ASCII clear text and then directly access the hosting site/manager without using the tracking manager 54. The LAB 62 can generate reports of published content/links that are unavailable and the information provided by the hosting manager when the unavailable determination was reached. The results may be provided to the management system 42 for human intervention and as necessary, delisting of expired content.
Now referring to
Thus, in the non-limiting XMB menu example shown in
Proceeding to block 76 in
Further and as mentioned above, in some implementations the user is permitted to navigate the Internet video service 20 using the remote control 13. The remote control 13 sends wireless commands to the TV 12, and the TV processor 14 interprets the commands and forwards the commands to the Internet video service system 20 so that the user can navigate URIs and other functions to cause Internet videos to be played on the TV 12.
Indeed and referring to
While the particular INTERNET ADAPTER SYSTEM AND METHOD FOR TELEVISION is herein shown and described in detail, it is to be understood that the subject matter which is encompassed by the present invention is limited only by the claims.
This application claims priority from U.S. provisional application 60/838,940, filed Aug. 18, 2006.
Number | Date | Country | |
---|---|---|---|
60838940 | Aug 2006 | US |