Video and digital multimedia aggregator

Description

TECHNICAL FIELD

The technical field is television program and digital multimedia delivery systems that incorporate intelligent and flexible program search and delivery mechanisms.

BACKGROUND

Cable television delivery systems greatly expanded the array of programs available to television viewers over that provided by over-the-air broadcast systems. Subsequently, satellite television delivery systems, and in particular, digital satellite broadcast systems further expanded the viewing choices for consumers. In the near future, digital broadcast television systems will provide many more programming choices for consumers.

In addition to television programming delivered through television program delivery systems, other programs and events may be sent to consumers. These other programs and events include streaming video sent over wired and unwired, narrowband to broadband services, digital audio programs, and other multimedia data.

Unfortunately, customers are still limited in their television viewing choices by the local and regional nature of television delivery systems. For example, a broadcaster in Boston may provide programming of local interests to people in Massachusetts while a broadcaster in Seattle may provide different programming to people in the Seattle area. A person in Boston generally cannot access Seattle programming, other than programming that is provided at a national level.

In addition to this local/regional market segregation, many other sources of programming and events may not be available in a specific viewing area. These other sources may include audio programming, streaming video, local or closed circuit television programming (e.g., education television programming provided by a state education department) and other programming.

Even if certain programming is available in a local viewing area, a viewer may not be aware of its existence. This situation may be the result of a large array of available programming coupled with a limited program menu or guide. The program guide may be limited in that not all available programming can be listed, some programming changes occur that are not reflected in the program guide, and errors may exist in the program guide. In addition, the more comprehensive the program guide, the harder it is for the viewer to search and navigate the program guide to find a desired program.

SUMMARY

The problems noted above are solved by the video and digital multimedia aggregator system and method described herein. Program content can be packaged and delivered by the system, including video, television, radio, audio, multimedia, computer software, and electronic books, or any content that can be delivered in digital format.

A system for searching, packaging and delivering content using an aggregator is described. The aggregator processes requests, searches, provides search results and acquires content.

The aggregator comprises a request and results processing server, a search engine server coupled to the request and results processing server and a content acquisition server coupled to the request and results processing server. The request and results processing server receives a request for a program, the search engine server searches for the program and the content acquisition server acquires a program for delivery to the user. The request and results processing server includes a search request processor that receives information related to the user's search request and provides the information to a search results form builder that creates an electronic search request. The search request may be augmented by using a content search suggestion engine to add additional search terms and descriptions to the search request. The aggregator may also include a decoder that decodes program content and program metadata from remote sources for storage at the aggregator, and an encoder that encodes content metadata and programs for delivery to the user. The aggregator may also comprise one or more crawlers, such as a content crawler, to look for program content in the digital communications network.

The search engine server searches at least a local content database. The local database typically comprises at least two file types, metadata and content. A content file includes a complete program content file. For example, the 1997 movie Titanic may exist in the local content database as a complete program content file. The complete program content file may also include a reference content or metadata that contains additional information related to the content. Such additional information in the reference content may include: a program description, including program rating, program description, video clips, program length, format (e.g., 4×3 television or 16×9 movies), and other information; billing information and digital rights management information; viewing statistics, including number of times viewed, dates/times viewed, identity of users viewing the program; advertisement information to allow ads to be inserted during viewing of the program; and other information.

The additional information in the reference file may be provided in whole or in part to the system users. For example, the aggregator may provide a program description and accompanying video clips to selected systems users. The reference file may also be used by the aggregator for system administration purposes. For example, billing and digital rights management information may be used to collect appropriate fees from system users and to provide such collected fees to the entities owning rights in the content.

A remote content crawler continually crawls the digital communication network looking for content to provide to the aggregator. The content provided to the aggregator may be stored in a form of an entire content file. For example, the content may include an entire movie, television program or electronic book. Alternatively, the content provided to the aggregator may be a reference to a content file that is stored at, or that will be available at one of the remote locations. For example, the content may be a reference to a future, scheduled live sports event that will be made available to system users. The sports event may be provided for a one time fee, as part of a sports package, for which a fee is collected, or as a free event. In the examples discussed above, the content may be stored at the aggregator, and may subsequently be provided to system users. For the example of the live sports event, the aggregator may store the live sports event and may then provide the sports event as a replay, in addition to facilitating live viewing of the sports event.

DESCRIPTION OF THE DRAWINGS

The detailed description will refer to the following drawings in which like numerals refer to like elements, and in which:

FIG. 1 is a block diagram of primary components of a content search, packaging, and delivery system;

FIG. 2 is a block diagram of the components of the content search, packaging, and delivery system configured to deliver content to a set top terminal;

FIG. 3 is a block diagram of the components of the content search, packaging, and delivery system configured to deliver content to a personal computer terminal;

FIG. 4 is a schematic of the components of the content search, packaging, and delivery system showing subsystems of an aggregator, a user terminal, and a remote content server;

FIG. 5 is a schematic of subsystems of a request and results processing server and components with which the processing server interacts as part of the content search, packaging, and delivery system;

FIG. 6 is a schematic of subsystems of a content search suggestion engine and components with which the content search suggestion engine interacts as part of the content search, packaging, and delivery system;

FIG. 7 is a schematic of subsystems of a search engine server and components with which the search engine server interacts as part of the content search, packaging, and delivery system;

FIG. 8 is a schematic of subsystems of a content acquisition server and components with which the content acquisition server interacts as part of a content search, packaging, and delivery system;

FIG. 9 is a schematic of subsystems of a content delivery server and components with which the content delivery server interacts as part of the content search, packaging, and delivery system;

FIG. 10 is a schematic of subsystems of a system administrator and components with which the system administrator interacts as part of the content search, packaging, and delivery system.

FIG. 11 is a schematic of subsystems of a database administrator as part of the content search, packaging, and delivery system;

FIG. 12 is a schematic of various user input devices that may be used with the user terminal of the content search, packaging, and delivery system;

FIGS. 13A and 13B show a flowchart describing a process of initiating a content search request using the user terminal that communicates with the aggregator;

FIGS. 14A and 14B show a flowchart describing processing of content search requests and search results performed within the aggregator;

FIGS. 15A and 15B show a flowchart describing a process at the user terminal for displaying programming search results and initiating content download requests;

FIGS. 16A and 16B show a flowchart describing processing of programming download requests by the aggregator;

FIGS. 17A-17C show a flowchart describing programming content delivery from the aggregator or a remote content server to the user terminal;

FIGS. 18A-18C show an embodiment of a search request form; and

FIGS. 19A-19B show an embodiment of a search results form.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a content search, packaging, and delivery system 200. The content to be packaged and delivered by the system 200 includes video, television, radio, audio, multimedia, computer software and electronic books. Components of the system 200 include an aggregator 201 and a user terminal 202, which are connected using a wide area distribution system 203. Other components are remote content servers 204 that exchange data with the aggregator 201 using a wide area network/Internet 205 connection. The user terminal 202 may incorporate a video display system 207, an audio playout system 208, an audio/video recording system 209, user input devices 214, an electronic book reader 230, and a connection to a home network 229 to interact with other devices in the user's home environment. Alternatively, one or more or all of the video display system 207, the audio playout system 208, the audio/video recording system 209, and the electronic book reader 230 may be separate components that are coupled to the user terminal 202.

The system 200 allows a user to enter search parameters, such as keywords and category headings, and have the aggregator 201 use these parameters to locate, package, and deliver content to the user terminal 202 from numerous sources. The requests and content deliveries can be sent over communications links including, but not limited to, telephone lines, coaxial cable, fiber-optic cable, wireless connections, wide area networks, the Internet, and other communication media collectively represented by the wide area distribution system 203. The numerous sources of content are shown in FIG. 4 and include, but are not limited to, an aggregator local storage 254, local streaming sources 262, remote content storage 258, and remote streaming sources 259. In an embodiment, the local streaming sources 262 are comprised of the audio and video channels being delivered using a cable headend system that may house the aggregator 201.

The system 200 will take a user's search request and may perform a search of virtually every active and scheduled radio and television channel in the world, as well as archived sources of video and audio programming such as movies and recorded audio sources and sources of other multimedia, software, and electronic book content. In an embodiment, the system 200 will also search Internet Web sites and other online databases. The user will then be able to select programming or other content for download based on the search results. In an embodiment, the download, or delivery, process can be fulfilled by making the content available on a specific channel of a cable television system, or by transmitting the content using a digital communications protocol, such as the Internet standard TCP/IP, for example. In addition, the content search, packaging, and delivery system 200 is capable of formulating and presenting a list of suggested content based on an analysis of the user's current search parameters, stored information about previous searches and previously selected content downloads and other user-specific or related information. The system 200 is also capable of notifying a user prior to the start time of selected programming and availability of other content using such notification as an electronic mail message and/or an on-screen message indicating that the scheduled program will be broadcast at a specified time. The system 200 may support one or more digital rights management (DRM) systems to track the usage and copyrights rights associated with downloaded content and bill the user's account as appropriate and provide any license and usage fees to the content provider. The system 200 may implement a users' privacy protection scheme allowing users to control what information is gathered, limit what is done with that information, and review and delete the user's profile if desired.

An overview of an embodiment of the system 200 is shown in FIG. 2 where the user terminal 202 is a set top terminal 206 that communicates with the aggregator 201 through a cable television system headend 210, thereby making use of the cable television system headend 210 high bandwidth concatenated cable system 216. Further, the set top terminal 206 system may include a tuner 228, a demultiplexer 231, the video display system 207, the audio playout system 208, the audio/video recording system 209, user input devices 214, an electronic book reader 230, and a connection to the user's home network 229. These components are used to tune, select, view, listen to, and store audio and video programming and other content delivered by the search, packaging, and delivery system 200. FIG. 2 also shows a communications path from one or more remote content servers 204 through the wide area network/Internet 205 directly to the set top terminal 206, which bypasses the aggregator 201 and cable television system headend 210. This path may be used in the case where the requested content is available in the required format from the remote content server 204 and is authorized for direct delivery to the user. In an alternative embodiment, the aggregator 201 is collocated with the cable television system headend 210 that is acting as the wide area distribution system 203 as is the case when a cable television system is also serving as the user's Internet service provider.

An overview of another embodiment of the system 200 is shown in FIG. 3, where the user terminal 202 is a personal computer terminal 211 that communicates with the aggregator 201 through an Internet service provider/cable television system headend 215. In this case, the content may be delivered by a cable headend that is operating as an Internet service provider (ISP). The personal computer terminal 211 also may include the video display system 207, the audio playout system 208, the audio/video recording system 209, user input devices 214, the electronic book reader 230, and the connection to the home network 229. A communications path also exists from one or more remote content servers 204 through the wide area network/Internet 205 directly to the personal computer terminal 211, which bypasses the aggregator 201 and the Internet service provider/cable television system headend 215 in the case where requested content is in the required format and is authorized for direct delivery to the user.

The user can receive video and audio programs (i.e., the content) in a number of different ways. First, the tuner 228 in the user terminal 202, shown in FIG. 2, can simply tune to the desired program, or the demultiplexer 231 can select a program from a digital multiplex, thereby displaying the program at the appropriate time. However, the desired program may not be broadcast by the user's cable television system headend 210, or the user would like to watch a program supplied by the local headend, but not subscribed to by the user, e.g., a boxing match broadcast by a premium channel that the user does not ordinarily receive. In these examples, the program can be delivered to the user by the aggregator 201 using the telephone lines, fiber-optic transmission lines, or other communication media, or using the cable television system headend 210. In an embodiment, the aggregator 201 can supply the desired program to the user by pulling programs from program delivery systems in the United States and abroad and delivering the program to system users. Therefore, a user can have access to programs outside the user's immediate viewing area.

FIG. 4 shows the system 200 and system components in more detail. At a user's location, the user terminal 202 includes the tuner 228, the demultiplexer 231, a user terminal processor 227, user local storage 212 and user local database 213. Coupled to the user terminal 202 may be user input devices 214, the video display system 207, the audio playout system 208, the audio/video recording system 209, an electronic book reader 230, and a connection to the home network 229.

The user terminal 202 is coupled through the wide area distribution system 203 to the aggregator 201 and further through the wide area network/Internet 205 to remote program sources. The remote program sources include remote streaming sources 259 and remote central storage 258. The remote program sources also include remote databases 261 and, through the remote content server 204, a remote server database 260.

The aggregator 201 may include a communications server 250 that communicates with the user terminal 202 through the wide area distribution system 203. The communications server 250 receives inputs from a request and results processing server 300, a content delivery server 450 and a system administrator 500. The content delivery server 450 receives inputs from a coder and content formatter 253 and a content acquisition server 400. The content delivery server 450 also accesses an aggregator local storage 254 and local streaming sources 262. Finally, the content delivery server 450 provides an output to the system administrator 500. The coder and coder formatter 253 receives inputs from the content acquisition server 400, the aggregator local storage 254 and local streaming sources 262. The system administrator 500 receives inputs from the content and delivery server 450, and communicates with the content acquisition server 400, the request and results processing server 300, a search engine server 350 and aggregator archives 255. A decoder and content formatter 252 is coupled to the content acquisition server 400. Finally, a network gateway 251 couples components of the aggregator 201 with the remote content server 204 through the wide area network/Internet 205.

Programs received at the aggregator 201 may be input to the formatter 253. The formatter 253 reformats all input content into a format that is readily received by all user terminals 202 operably connected to the delivery system 200 (not shown in FIG. 4). In addition, the formatter 253 can store full or partial copies of content in compressed form in the aggregator local storage 254. Furthermore, the aggregator 201 can provide real-time delivery of certain content, such as a boxing match. In an embodiment, if a large number of users want a particular live program, then the cable television system headend 210 can broadcast the program on a particular channel available to all the requestors instead of broadcasting the program to each individual user over the wide area distribution system 203. See U.S. patent application Ser. No. 09/191,520, entitled Digital Broadcast Program Ordering, hereby incorporated by reference, for additional details of broadcast program delivery.

The aggregator 201 can also implement a screening process for limiting the number of programs captured to those programs with a viewing audience above a predetermined threshold. In effect, the aggregator 201 contains a filter that will pass only programs meeting the predetermined selection criteria. The filter may include programming that screens the content to reject specific items, such as adult content, for example.

The system administrator 500 records what fees should be paid and to whom. For example, the aggregator 201 will determine to whom any copyright or other fees should be paid when a program is broadcast.

The user terminal 202 may be a television, a set top terminal 206, a personal computer terminal 211 (not shown), or any device capable of receiving digital or analog data, or some combination thereof. The user terminal 202 is equipped with the user input devices 214 that communicate search criteria to the system 200 as well as navigate through the user terminal menu system and control the user terminal's other various functions. The user local storage 212 is used to store and archive content onto one or more removable and/or non-removable storage devices or media for later access. Removable storage media may include, but is not limited to, magnetic tape, magnetic disks, optical disks and modules, and electronic memory cartridges. The user local database 213 is the repository of all relevant information about a user's profile and account. This information includes, but is not limited to, user name, password, personal information that the user has authorized for storage, billing information, other users allowed access to the account, past search criteria, past content download information, and library information about stored content. As a consumer protection, the user terminal 202 may enable the account user to view the information stored in the user local database 213 and modify certain data fields and select which data fields may be reported to a main system database (see FIG. 10) within the aggregator 201. Certain fields including, but not limited to, account numbers and billing information may not be allowed this level of user access.

The user terminal processor 227 may include a central processing unit and all associated hardware, software, and firmware modules to perform all operations within the user terminal 202. These operations include, but are not limited to, managing communications with the aggregator 201 and other networked devices, processing search and download requests, displaying search and download results, managing and controlling communications with the user local storage 212 and the user local database 213, responding to user interaction with presentation of graphical user interface (GUI) menus, playing out selected programming content using various audio and video output devices, implementing the user's part of the digital rights management schema, and administering the user's account and billing. The tuner 228 and the demultiplexer 231 are used to select an audio/video channel for playout from the channels available on the cable television system 216.

In an embodiment, the user terminal 202 may incorporate selected features of the aggregator 201. For example, the user terminal 202 may include a small metadata crawler, an aggregator, and program content and program metadata storage.

The user terminal 202 communicates with the aggregator 201 using the wide area distribution system 203. Within the aggregator 201, the communications server 250 acts as the interface point to the wide area distribution system 203 for the purpose of managing primary communications to system users. The communications server 250 routes incoming user requests and associated user information to the request and results processing server 300, routes search results and content downloads through the wide area distribution system 203 to end users, and routes billing information from the customer billing server 506 (see FIG. 10) to the end users. The request and results processing server 300 performs the basic processing and routing related to user search requests, content download requests, administrative information requests, search results, related content suggestions, and programming notification.

FIG. 5 shows individual subsystems of the request and results processing server 300. The types of requests from a system user include, but are not limited to, programming and other content search requests, content download requests based on results of an earlier search, and administrative information requests. Requests for administrative information may be automatically generated by the user terminal 202 or may be manually initiated by the system user. When an administrative request is received, a request receiver and router 301 opens a dialog with a database administrator 502 (see FIG. 10) within the system administrator 500, retrieves the requested system user's administrative data, and routes the data through the communications server 250 to the user terminal 202. Search requests and content download requests are routed to a search request processor 303 and a content download request processor 302, respectively. The processors 302 and 303 open a dialog with the database administrator 502 and verify that the user's request is authorized. If the user's request is not authorized, the processor (302 or 303) sends a message to the user through the request receiver and router 301 and the communications server 250 informing the user that the request is denied. The processor (302 or 303) then logs the event with the system administrator 500. If the request is authorized, the processor (302 or 303) formats the request as necessary and routes content download requests to the content acquisition server 400 and search requests to the search engine server 350.

For programming download requests, the content acquisition server 400 submits scheduling and availability information about the selected content to the database administrator 502 within the system administrator 500, which in turn routes this scheduling and availability information to a scheduled program and content availability prompt and notification processor 306 within the request and results processing server 300. The scheduled program and content availability prompt and notification processor 306 then initiates a form of prompt and/or notification to the user that the selected content is available at a particular time. This notification can be in various forms including, but not limited to, an on-screen pop-up window, audible notification, e-mail notification, instant message, and automated telephone notification. The exact form and timing of the prompt and/or notification may be customized by the user and may be based on whether the content is scheduled, continuously broadcast, stored, or available any time for download. In an embodiment, when a selected program is about to be broadcast or made available for viewing on television, a prompt will be sent by the server 300 notifying the user when the program is about to air. In the case of an on-screen prompt, a mechanism may be provided for enabling the user to hyperlink to the selected program from the prompt. For search requests, the search engine server 350 returns a data package to the request and results processing server 300 that contains scheduling, availability, and descriptive information about all content entries that have been determined to satisfy the search criteria.

In addition to searching for content containing criteria entered by a system user, a content search suggestion engine 304, in conjunction with the search engine server 350 will be able to suggest content to the user that is related in various ways, such as by category or theme. The content search suggestion engine 304 is shown in detail in FIG. 6. For example, if a user wishes to see programs about Titanic, the content search suggestion engine 304 may, in addition to suggesting programs about Titanic, suggest or inform the user of programs and other content such as electronic books about ships other than Titanic. Likewise, if the search criteria include Johnny Weismuller, an actor who starred in Tarzan movies, the content search suggestion engine 304 might suggest programs and other content about Tarzan featuring someone other than Johnny Weismuller. Furthermore, the content search suggestion engine 304 may suggest programs for viewing based on past search criteria entered by the user as well as information on content the user has actually downloaded. For example, if the search criteria includes Johnny Weismuller and the user has searched and/or downloaded numerous sports-related programming in the past, the content search suggestion engine 304 may suggest programming and other content including swimming competitions and sports history and biography programming as well as Tarzan movies and other content directly related to Johnny Weismuller such as the Jungle Patrol television series. If the user searched for and received Tarzan movies, the content search suggestion engine 304 might suggest electronic books by Edgar Rice Burroughs. Such electronic books could then be downloaded to the user terminal 202 using the wide area network/Intranet 205 bypassing the aggregator 201, or could be compiled at the aggregator 201 for delivery to the user terminal 202. Electronic book delivery systems are described in U.S. Pat. No. 5,986,690, entitled “Electronic Book Selection and Delivery System,” to Hendricks, and in co-pending patent application Ser. No. 09/289,957, entitled “Electronic Book Alternative Delivery Systems,” and Ser. No. 09/289,956, entitled “Electronic Book Alternative Delivery Methods,” all of which are hereby incorporated by reference.

During submission of a content search request, the user may have the option of disabling the return of suggested content results if desired. In order to retrieve results for suggested programming, the content search suggestion engine 304 analyzes a search request form 618 (see FIGS. 18A-18C) received from the user terminal 202, and performs a search within a suggestion database 308 for additional search criteria to be used to find suggested content related in some way to the original search request results. These suggested search criteria are appended to the search request form 618 forming an augmented search request form 620 (FIGS. 18A-18C) when the search request form 618 is forwarded to the search engine server 350 in order for a suggested content list to be returned. U.S. Pat. No. 5,798,785 entitled “Terminal for Suggesting Programs Offered on a Television Program Delivery System,” and co-pending patent application Ser. No. 08/906,469, filed Aug. 5, 1997, entitled “Reprogrammable Terminal for Suggesting Programs Offered on a Television Program Delivery System,” both of which are hereby incorporated by reference, provide additional details on program suggestion.

The suggestion database processor 307 (shown in FIG. 6) conducts a search of the suggestion database 308 to find related search criteria to use to locate suggested content. The processor 307 also performs management functions for the other subsystems of the content search suggestion engine 304. When prompted by the suggestion database processor 307, the content metadata crawler 309 crawls, or intensively searches, the metadata in the aggregator local database 501 and passes a listing of all content metadata to the suggestion keyword indexer 310, which indexes each metadata element and assigns each with a vector quantity that describes the metadata element as a suggestion keyword associated with a particular content entity. The indexer 310 then populates the suggestion database 308 with these indexed suggestion keywords, which are used by the suggestion database processor 307 along with historical data relevant to the user to supply a list of suggested search terms. The search terms are then added to the search request form 618 to create an augmented search request form that is returned to the search request processor 303 (see FIG. 5).

The search engine server 350, shown in FIG. 7, receives the augmented search request form 620 and performs a search of the database of all known programming content, both local and remote, and builds a hierarchical list of results based on how well each result compared to the search criteria. The search engine server 350 contains a replicated content database 357 to be able to perform searches more efficiently and maintains a list of active searches to which new content listings are compared. Periodically, the search engine server 350 thoroughly searches, or crawls using a remote content crawler 356, all available sources of programming and other content, retrieves all information about all content not previously logged into the system and enters that data into the aggregator local database 501 (see FIG. 4). In an embodiment, the search engine server 350 may directly access remotely stored content and analyze and retrieve metadata from the stored digital files.

In an embodiment, the aggregator local database 501 and the search engine server 350 reside on an array of distributed processing and storage devices in order to reduce database access time and perform searches in parallel on different sections of the database. In another embodiment, numerous aggregators 201 can be operated by various stakeholders such as cable television headend operators. These aggregators 201 will be capable of networking directly together using the wide area network/Internet 205. Within this network of aggregators 201, business models will support various relationships between operators such as a peer-to-peer network of content, advertising, and user sharing. The aggregator 201 software and hardware components may be of a modular nature in order to support various system architectures as well as be scalable and easily upgraded on a module or subsystem basis.

Returning to FIG. 5, all search results, based on user search criteria and suggested search criteria, may be forwarded by the search engine server 350 and then to the search results form builder 305 within the request and results processing server 300. The search results form builder 305 formats the results for transmission through the communications server 250 to the user terminal 202. The search results form builder 305 takes prioritized lists of user search results and suggested search results and populates a search results form 674 (see FIGS. 19A and B) with programming, scheduling and availability information. The request and results processing server 300 then encrypts and forwards the search results form 674 through the communications server 250 to the user terminal 202. At the user terminal 202, the search results form 674 is decrypted and stored in the user local database 213 and a prompt is displayed that allows the user to display the returned results on the video display system 207 or the electronic book reader 230.

The search results can then be displayed on the user's video display system 207 in various formats including, but not limited to, a hierarchical listing based on relevance to search criteria and a display similar to an electronic program guide based on time of availability and content source. The user will be able to select from the various results display formats and have the results data be reformatted upon request. In an embodiment, the user may be able to select one of the search criteria or an attribute of the programming and the results will be sorted based on that selection. For example, if numerous program types are returned, the user can select “documentaries” and the results will be listed with documentary programs occurring first. The results display will also indicate whether a particular programming choice is a result of the user-defined search criteria or was a result of the system's capability to suggest content. The user will have the ability to display only results from the user search, only results from the suggested content search, or both. In an embodiment, the entire menu system can be implemented using audible prompts and lists in order to accommodate users with visual impairments. In such a scenario, input methods can be by voice recognition, tactile recognition such as a remote control equipped with a Braille character input pad, or a combination of these methods.

As shown in FIG. 4, the network gateway 251 serves as the communications system between the aggregator 201 and the wide area network/Internet 205, and hence the remote content server 204. The network gateway 251 may support any protocol in widespread use for connection to the wide area network/Internet 205 and will serve as a security firewall between the aggregator 201 and the wide area network/Internet 205. The network gateway 251 will route search and content download information from the aggregator 201 to the remote content server 204 and route search results and content from the remote content server 204 and other Internet sources back to the aggregator 201.

The content acquisition server 400, as shown in detail in FIG. 8, receives content download requests from the request and results processing server 300. The content acquisition server 400 includes a content request processor and router 401 and a remote content download processor 402. A download request is made by the user for content selections from sources including, but not limited to, earlier programming searches, recurring scheduled events, an electronic program guide, lists of electronic books and computer software, advertisements, promotions, and affiliated Internet websites. In general, a download request will be accompanied by data indicating the source of the content and whether the content is local or remote. Requests for content that is available only from a remote site may be routed to the network gateway 251 and then to the appropriate remote source. Remote sources include, but are not limited to, the remote content storage 258 and 25 the remote streaming sources 259 shown in FIG. 4. The remote content server 204 verifies the request and returns the content through the wide area network/Internet 205. If the programming content is in the appropriate format and is authorized for direct delivery to the user, the content may be routed through the wide area network/Internet 205 and the wide area distribution system 203 directly to the user terminal 202. During this transfer, administrative data pertaining to billing and verification of delivery are sent back to the aggregator 201.

Programming that is not formatted and authorized for direct delivery from a remote source may be transmitted through the network gateway 251 to the remote content download processor 402 contained within the content acquisition server 400. The remote content download processor 402 buffers or caches the programming content while managing the download connection to the remote source. The programming content is then routed to the decoder and content formatter 252, which may be capable of decoding various industry formats and compression schemes and may reformat and encode the decoded data and associated metadata into one or more preferred content formats for delivery and for local storage. The processed programming content, along with user identification and routing data, is then routed to the content delivery server 450, which then manages the delivery of the content through the communications server 250 and wide area distribution system 203 to the user terminal 202. The content delivery server 450 is shown in detail in FIG. 9.

Requests for programming available from a local source are routed directly to a local content request processor 451 within the content delivery server 450. The local content request processor 451 initiates delivery of content from local sources including, but not limited to, the aggregator local storage 254 and aggregator local streaming sources 262, and routes the content to the coder and content formatter 253. In an embodiment, the local streaming sources 262 can include any of the cable television channels available at the cable television system headend 210 housing the aggregator 201. If the programming content is not already in the user-requested format and coding scheme, the coder and content formatter 253 (see FIG. 4) performs content formatting and coding of the programming for delivery to the user. The content is then forwarded to a content delivery processor 453, which manages the delivery of the content through the communications server 250 and wide area distribution system 203 to the user terminal 202.

During the content acquisition and delivery process, the content delivery processor 453 oversees and validates that the delivered programming content matches the original content download request. This is done by receiving program and user metadata from the content acquisition server 400 through the local content request processor 451 and comparing the received data to the metadata of the actual requested content and the actual delivered content as received during the program request and download process. A confirmation is then logged with the system administrator 500. In an embodiment, based on user information and content metadata, the content delivery processor 453 can command an advertisement processor 456 to insert specific advertising into certain programming content as it is delivered to a system user. The advertising can be retrieved from the aggregator local storage 254 or can already be resident at the user terminal 202. Methods for targeting advertisements to users are described in co-pending patent application Ser. No. 09/054,419, entitled “Targeted Advertising Using Television Delivery Systems,” and Ser. No. 08/160,280, entitled “Method and Apparatus for Targeted Advertising,” both of which are hereby incorporated by reference. Confirmation of the programming delivery is also sent to the database administrator 502 for logging into the aggregator local database 501.

Similarly, if content is copyright protected and the user is granted certain rights and denied others for use of copyright protected content, the content delivery processor 453 can command a digital rights management processor 454 to implement a digital rights management (DRM) scheme. The DRM scheme controls how digital content is used, including, but not limited to, whether or not the content can be stored on the user terminal 202, copied to another system, forwarded to another user, transferred to removable media, or translated into a different digital content format or coding scheme. The DRM scheme may be able to make use of digital encryption technology to enforce copyright protection if necessary. When this is the case, the digital rights management processor 454 will command the content delivery processor 453 to route the subject programming content along with encryption data to an encryption processor 455. The encryption processor 455 encrypts the programming content and returns the content to the content delivery processor 453 for transmission to the end user. Under this type of scenario, the authorized user terminal 202 will possess the necessary information to decrypt and output the programming content. The user terminal 202 will also contain the necessary information to enforce any DRM scheme that has been applied to a particular piece of content.

During the delivery of programming content other than broadcast programming over the concatenated cable television system 216, the user terminal 202 continuously responds to the content delivery processor 453 identifying the user terminal 202, verifying that the appropriate data is being delivered, and indicating that the delivery should continue. If the download is terminated by the user, the user terminal 202 informs the content delivery processor 453, which then terminates the delivery.

Upon successful delivery of the requested programming, the content delivery server 450 logs the results with a customer billing server 506 and content fee and copyright billing server 507 within the system administrator 500 (see FIG. 10). The customer billing server 506 determines if the content delivery requires additional charges to the customer's account and enters this into the billing record and logs it with a database administrator 502.

In addition to tracking billing for system end-users, the content search, packaging, and delivery system 200 also manages payments of royalties and fees to providers of certain content. This is done by the content fee and copyright billing server 507. The fee structure for payment for content to program providers is put into place between the system 200 and the programming content providers by a content provider registration server 505.

The system administrator 500 oversees the operations of the content search, packaging, and delivery system 200. A system administration server 503 serves as the top-level management function for the system 200. The system administration server 503 manages communications between the various subsystems of the aggregator 201 through a local area network and manages a list of authorized administration users to manage the system 200 through a set of system administration terminals 508. A user registration server 504 manages the signup procedure for new users and the termination of user accounts. The user registration server 504 interfaces with the communications server 250 to present the user with appropriate screen menus and prompts to gather user information and billing data to setup an account. A variety of information is requested of the user including, but not limited to, name, address, age, gender, television viewing habits, members of household, and equipment owned. Some of the information that is not required for billing, such as gender and other members of household, can be omitted by the user as part of the system's policy of privacy protection. Once billing information has been verified, the user registration server 504 downloads the required software and database information for the new user terminal 202 in order to allow access to the content search, packaging, and delivery system 200. During this process, the user registration server 504 exchanges information with the database administrator 502 to create the new user profile and billing account in an aggregator local database 501.

A database administrator 502, shown in detail in FIG. 11, maintains the aggregator local database 501 and interfaces with the various components of the aggregator 201 that retrieve information from and store information to the aggregator local database 501. The database administrator 502 controls several database servers. A group of individual databases maintained within the database administrator 502 constitutes the aggregator local database 501. An administrative database server 509 maintains an aggregator administrative database 510, which stores and processes information including, but not limited to, authorized system administrators, passwords, and administrator usage rights. The administrative database server 509 also governs replication of all databases to aggregator local storage 254 and backup of aggregator local storage 254 to the aggregator archives 255. A user database server 511 maintains an aggregator user database 512, which stores and processes information including, but not limited to, user account data, user profile information, user subscription services, user access rights, and past user search and download data (if authorized by the user).

A content provider database server 513 maintains a content provider database 514, which stores and processes information including, but not limited to, a roster of registered content providers and their administrative data, remote provider administrators and their passwords and access rights, and terms of agreements between providers and the operator of the particular aggregator 201. A content database server 515 maintains an aggregator local content database 516, an aggregator remote content database 517, and an aggregator scheduled content database 518. The aggregator local content database 516 stores and processes information including, but not limited to, the catalog of all content stored in the aggregator local storage 254 and all metadata associated with that content. The aggregator remote content database 517 stores and processes information including, but not limited to, the catalog of all content stored in each remote database 261 and all metadata associated with that content. The aggregator scheduled content database 518 stores and processes information including, but not limited to, scheduled broadcast programming content and scheduled streaming program content available to users, available live programming, recurring scheduled programming, and program schedule metadata information.

The system user can initiate content search requests by entering several different types of search criteria using several different options of input device or method. Search criteria can be entered via keywords that relate to certain aspects of programming content including, but not limited to, subject, author, title, cast members or performers, director, and/or content description. A search can be based on program type or format including, but not limited to, movies, television series, documentaries, sports programs, talk radio, and music radio. The user may input search criteria based on subject categories including, but not limited to, action, drama, history, educational, juvenile, adult, current events, nature, live events, and music categories such as classical, jazz, rock, consumer affairs, political content, and geographically specific content. Search criteria can also be entered based on time of day, channel, and/or content provider. The user may also input free form questions using plain speech patterns. In any case, the different search criteria can be used separately or in conjunction with one another to refine a content search. An example might be the entry of “Titanic” as a keyword, “Documentary” for program type, and the free form question “What company built Titanic?”.

The user can interact with the user terminal 202 to input search parameters using one or more of several user input devices 214 including, but not limited to, those shown in FIG. 12. The user input device 214 includes a keyboard 220, a keypad 221, a mouse or joystick 222, a handheld computer 223, a touch screen tablet 224, a handheld remote control 225, a user terminal voice recognition system 219, an input device voice recognition system 226, and an electronic book reader 230.

In an embodiment, keywords and free form question criteria can be entered with the keyboard 220 attached to the set top terminal 206 or the personal computer terminal 211 and content type and category criteria can be selected using the mouse or joystick 222, which controls a cursor on the screen. In another embodiment, text for keywords and free form questions can be entered using the keypad 221, which can be located on the set top terminal 206, in the handheld remote control 225, or in a dedicated wireless unit (not shown). The handheld remote control 225 may also incorporate a pointing control device or button to move a cursor on the screen and activate selections under said cursor and to navigate through a series of graphical user menus. In another embodiment, the handheld computer 223, electronic book reader 230, or the touchscreen tablet 224 can contain software programming enabling an input device to the user terminal 202 using an infrared or wireless link and allowing text input and on screen cursor and menu control. The handheld computer 223 refers to devices including, but not limited to, personal digital assistants, palm top computers, and multifunction devices such as wireless telephones and mobile Internet access devices capable of operating third party software. In yet another embodiment, voice recognition technology can be used to input text and to control onscreen navigation and selection functions. Voice recognition can be implemented by receiving and processing speech at the user terminal 202 through the user terminal voice recognition system 219. In another embodiment, voice recognition can be implemented by receiving speech by a remote input device using the input device voice recognition system 226. The input device would then convert the received speech to text and onscreen control commands and send those to the user terminal 202 using the infrared or wireless link.

In order for the user terminal 202 to communicate with the various remote input devices, the user terminal 202 may be equipped with an infrared wireless transceiver 217 and/or a radio frequency wireless transceiver 218. These systems will support various popular industry standards in use for device communication via infrared and radio frequency wireless links.

The user can also input search criteria by making selections from a graphical user interface (GUI). In an embodiment, the user terminal 202 generates a content search GUI containing menus that allow the user to select and enter various search criteria. The user can select a criterion to be searched by delineating areas of a GUI. For example, the user can select a criterion to be searched by putting a check in a box associated with the criterion or by placing the cursor over a hyperlinked criterion description and hitting an activation button that then causes a submenu GUI to be displayed that shows selections to be made within that search criterion. (See Ser. No. 07/991,074, filed Dec. 9, 1992, entitled “Television Program Packaging and Delivery System with Menu Driven Subscriber Access”, hereby incorporated by reference, for additional detail on using cursor keys.) For example, the user might select from programs based on general themes including, but not limited to, categories of programs, actors and actresses, musical performers, day and time, and channel or content provider. If the viewer then selects categories of programs, a submenu containing different categories of programs such as sports, drama, comedy and romance will appear. If the user then selects sports, another lower level submenu will appear listing different sports. Each of the menus will include a choice to enter keywords or free form text in addition to the menu-selected search criteria. Once the user has sufficiently narrowed the search criteria, the search can be executed by selecting an option to submit the search. For privacy protection, during this process, an option on the GUI menus allows the user to prevent the set of search criteria from being included in a local user profile as well as the user profile resident at the aggregator 201. If the user opts not to include a particular set of search criteria into the user profile, the search request will be tagged accordingly as it is processed through the system and when results are returned to the user, those results will also be omitted from the user profile, both locally and at the aggregator 201.

A process 600 for initiating a programming search request 600 is shown in FIGS. 13A and 13B. The process 600 starts when the user activates the search menu (routine 601) using one of the input devices 214 described above. In display routine 602, the user terminal 202 displays the top-level graphical user interface (GUI) search menu 603. In input routine 604, the user employs the user input devices 214 to navigate through the GUI search menu system and input various search criteria. During the search criteria input process, the user is also presented with the option to omit a particular search from being logged into the user's profile and the option to disable the return of suggested content based on the current search and prior searches recorded in the user's profile. When the user submits the search request, format routine 605 begins processing the search criteria in order to format the search criteria into a search request form 618.

The search request form 618 shown generally in FIGS. 13A and 13B and in more detail in FIGS. 18A-18C is an electronic form standardized within the content search, packaging, and delivery system 200. The search request form 618 is populated with required user information and search criteria in order for the aggregator 201 to perform the search for relevant content. The search request form 618 contains data fields including, but not limited to: user identification, user authorization, password, digital rights management (DRM) information, user's encryption key if applicable, content format requirements, updates to the user's profile (if enabled by user), user network routing information, and the programming search criteria. The search criteria section of the search request form 618 will contain several hierarchical lists of criteria to accommodate the various types of search criteria that can be entered by the user. Search criteria entries include, but are not limited to, program type, content format, topic or subject, content description, date and time range, channel or content provider, and a list of keywords received from user input, and results derived from free form questions.

If criteria are input as a free form question, routine 605 applies a search criteria algorithm to parse the question and transform the question into relevant search request form 618 contents. The sentence structure is analyzed and, based on order and relative positions of the words within natural language sentence structure, significant terms are categorized and entered into appropriate fields of the search request form 618. In an embodiment, the search request processor 303 (see FIG. 5) will access a lexicon of all known English language words, terms, and names in order to augment the search request form 618 with various forms of words found in free form questions. For example, if the question is “Who assassinated Abraham Lincoln?” the search request processor 303 will access the lexicon and return other forms of the word “assassinated” such as “assassinate”, “assassin”, and “assassination”. In another embodiment, other similar words will be added to the search criteria such as “kill” and “murder”. The search request processing algorithm can also designate additional search parameters based on the type of query words used in the free form entry. For example, a question such as “Where does the largest land mammal live?” will cause the search process to prioritize results containing geographical information within the content metadata and description.

Once the search request form 618 has been formatted, routine 605 logs the search criteria into the user local database 213 associated with that particular user (if the search has not been selected for omission from the database). The search criteria may be kept as a part of the user's profile for suggesting content and for personalizing searches and advertising. The routine 605 then forwards the search request form 618 and matching routine 606 uses the search criteria within the search request form 618 to search the user local database 213 for matching or similar content that is stored in the user local storage 212. If no matching or similar content is found locally, the routine 606 routes the search request form 618 to routine 613. If the search yields matching or similar content that is available locally, the routine 606 routes the search request form 618 to routine 607, which formats the results of the local database search into a local results form, which is then presented on the video display system 207 by display results routine 608. Concurrently, the routine 607 forwards the search request form 618 to the routine 613, which opens communications with the communications server 250 at the aggregator 201, encrypts the search request form 618, and forwards an encrypted search request form 619 to the request and results processing server 300, which initiates processing of the search request represented by processing routine 650 as shown in FIG. 14A.

Once the encrypted search request form 619 has been sent to the aggregator 201, polling routine 614 initiates a periodic poll of the results inbox at the user terminal 202. When results are returned by the aggregator 201 in the form of a search results form 674 (see FIGS. 19A and B for a detailed structure of the search results form 674), the search results form 674 is delivered to the results inbox and a subsequent poll will initiate the display of the results to the user. After the periodic poll is started, the user terminal 202 prompts the user to perform another search (routine 615). If the user responds “yes,” the routine 615 routes the process flow back to the display routine 602, which again displays the search GUI menus 603. If the user chooses not to perform another search, processing moves to the routine 616, which resumes playout or display of programming that was in process when the search was first initiated. Execution of routine 617 results in a display of a small icon or window in a small portion of the video display indicating that the search is in progress. This icon is referred to as the “Performing Search” bug. If the local search found content and displayed the local search results to the user, the user inputs a selection using routine 609. If the user chooses not to view any of the local results, routine 610 routes processing to the routine 616. If the user chooses to playback programming from the local results, the chosen selection is retrieved by retrieval routine 611 from user local storage 212 and played back by playout routine 612 through the video display system 207 and/or the audio playout system 208. The routine 612 also displays the Performing Search bug on the display screen. The Performing Search bug may have an option to hide the icon, therefore removing the icon from the display.

FIGS. 14A and 14B show a flowchart for processing programming search requests and results 650. In a first stage, the encrypted search request form 619 is received from the programming search request initiation process 600, decrypted, and routed to the request and results processing server 300 (routine 651). Log routine 652 performs a call to the aggregator local database 501 to log the current request into the user's profile. If the user has indicated that the current search shall not be included into the user's profile, only administrative data pertaining to the search are recorded. Recorded information includes, but is not limited to, updates to the user profile (if enabled), changes to the user terminal 202 architecture, additional user identities, deleted user identities, and increments to the search counter for tracking and billing. Routine 653 also performs a call on the database to retrieve user identification and profile information. Routine 654 uses the user data in the search request form 618 and the information retrieved from the aggregator local database 501 to verify that the user is authorized to perform the particular search. A search can be designated as unauthorized under certain conditions including, but not limited to, if the user searches for specifically tiered channels that the user's account cannot access such as premium pay movies, if adult material or channels are designated in the search and the user is identified as being restricted from such access, or if the user's billing status is not in good standing but the account has not yet been terminated. If the search is deemed unauthorized, routine 655 notifies the user terminal 202 that the search request has been denied. The user terminal 202 displays the search request denial message along with any other relevant data such as the reason for denial. The process 650 then stops (routine 656).

If the user is authorized for the particular search, the search request form 618 is forwarded. In an embodiment, filter routine 657 filters the request based on the user's profile. In another embodiment, this filtering occurs within the user terminal 202 prior to the search request form 618 being sent to the aggregator 201. The filtering process narrows the range of sources that will be searched by eliminating types of content or content providers based on the user's preferences. For example, the user may designate that no children's programming or sources be returned in the search results. In this case, the routine 657 appends the search request form 618 to indicate that such programming and sources should not be included in the programming search. This not only allows the user to more finely tailor the search, but also allows the aggregator 201 to perform quicker and more efficient searches by reducing the range of sources and records that will be searched.

The routine 657 then routes the search request form 618 to the content search suggestion engine 304 (see FIG. 6), which uses the information in the search criteria and user profile to create a list of suggested search criteria. In an embodiment, the content search suggestion engine 304, maintains an indexed database of suggestion keywords in the suggestion database 308. The relevance of a given search keyword, which is obtained from the user's search request form 618, to a suggestion keyword is determined in vector difference routine 658 by calculating a vector quantity difference between the search keyword and indexed suggestion keywords. The vector quantity may be a measure of similarity between two words that is calculated by determining relative values of several categorical descriptions of each word including word type, part of speech of each word, and relative locations or linkage in a thesaurus. Suggestion keywords that fall within a predetermined range of relevance, i.e., that have vector quantities below a certain limit, are collected in execution of the routine 658 by the suggestion database processor 307. The routine 659 then weights, or ranks, the list of suggestion keywords based on information retrieved from the user's profile concerning earlier search and download requests. The suggestion database processor 307 then adds these suggested search criteria to the search request form 618 in routine 660, creating an augmented search request form, which is forwarded to the search engine server 350 by (routine 661).

To create and maintain the indexed suggestion database 308, the content metadata crawler 309 periodically crawls the content metadata entries of all listed content and programming in the aggregator local database 501 and retrieves all descriptive data for each entry. Crawling is a thorough scan and retrieval of all data pertaining to each content item that is listed in the content database server 515, which includes information about all registered content and information about programming that has been retrieved by crawling sources of content. The suggestion keyword indexer 310 then associates a unique numerical value to each term and enters this into the suggestion database 308 as indexed suggestion keywords. The index indicates the proximity of terms to one another within the metadata. This proximity within the metadata is then used by the suggestion database processor 307 to determine the vector relevance of suggestion keywords to search keywords and select a range of suggestion keywords to add to the search request form 618. See The Anatomy of a Large-Scale Hypertextual Web Search Engine, Sergey Brin and Lawrence Page; Computer Science Department, Stanford University, Stanford, Calif. 94305, USA, hereby incorporated by reference, for more detail about crawling of websites, indexing terms, and ranking of search results.

Using the example of Johnny Weismuller, the content metadata crawler 309 crawls the database and returns numerous descriptions of Tarzan movies and other content and collects data including, but not limited to, co-stars, directors, settings, authors, and plot lines or subjects. The suggestion keyword indexer 310 indexes Johnny Weismuller and all other information found and assigns a vector relevance based on type of information and proximity. Then other significant terms, such as Africa as the story setting, are then crawled and the process is repeated to populate the suggestion engine database. When a user searches for Johnny Weismuller, the suggestion database processor 307 returns an augmented search request form that contains suggested search criteria that will return related results such as other movies produced during that time period set in Africa, other movies based on stories by Edgar Rice Burroughs, novels by Edgar Rice Burroughs, and other movies with similar plot lines such as a child being isolated in the wilderness left to fend for itself while growing up. Search results returned based on suggested search criteria are labeled as such as they are processed by the search engine server 350.

In an embodiment, the search request processor 303 maintains a lexicon of all known English language words, terms, and names and will augment the search request form 618 with variations of words listed as keywords. For example, if the search request form 618 contains “sink” and “Titanic,” other forms of the word “sink” will be added to the search criteria such as “sunk” and “sinking” while ignoring the alternate definition of “water basin.” In yet another embodiment, the search request processor 303 also maintains lexicons for chosen non-English languages and will have the capability to perform language translation of search criteria for augmentation of the search request form 618.

The search engine server 350, as shown in FIG. 7, contains the subsystems necessary to perform searches of all available content, process the search results, and crawl remote content sources. A search is initiated when the request and results processing server 300 forwards an augmented search request form to the search engine processor 351 represented by routine 661 in FIG. 14A. In routine 662, the search engine processor 351 uses the criteria within the augmented search request form to perform a search for matching data within the replicated content database 357. The replicated content database 357 is a copy of the contents of the content database server 515 within the system administrator 500. The replicated content database 357 is periodically updated by the system administrator 500 and is maintained within the search engine processor 351 to allow quicker and more efficient return of search results. The search engine processor 351 uses retrieval routine 663 to retrieve a programming list for which any of the search criteria appeared in the content metadata. The programming list is forwarded to the search results processor 355, which, in routine 664, compares the relevancy of each returned result to the search criteria and ranks the results based on strength of the match using information including, but not limited to, key words, subject, content type, content category, author, and cast members. Relevancy and strength of match are determined by the number and type of matching criteria as well as the user's profile data such as preferred content providers and past download requests. If the user is searching for movies about Titanic, then movies with “Titanic” in the description will be ranked higher than documentaries about Titanic. In an embodiment, the search results processor 355 will also take into account such information as how many other users have downloaded the program and whether the program has received positive critical reviews and will improve the ranking of more popular and well reviewed programs. Therefore, for a search of content type “movie” and keyword “Titanic” the search engine server 350 would return the 1997 Academy Award winning movie Titanic as the top ranked content match. The second ranked result would likely be the audio soundtrack from the same film.

The search engine server 350 also crawls remote content sources in order to maintain an up-to-date listing of content available from independent providers that are not registered with the content search, packaging, and delivery system 200. The crawling is done by periodically searching sources of content using the wide area network/Internet 205 and returning available metadata about content that is not already listed in the aggregator local database 501 and adding these listings to the database 501. Subsequent replication of the content database to the search engine server 350 will include these updated listings.

Another function performed by the search engine processor 351 is maintaining a list of active searches. If a user's search request did not yield satisfactory results, or if the user wishes to receive future results based on a particular set of search criteria, the user can request that a particular search request remain active for a certain period or indefinitely. When this option is exercised, the user terminal 202 sends a message to the request and results processing server 300, which instructs the search engine processor 351 to keep the search active. When there are changes to the replicated content database 357, a delta report that describes content entries that have been changed and/or added to the database is sent to the search engine processor 351. The search engine processor 351 compares the data in the delta report to all active searches and generates a results list for any active search that matches new or changed content entries. The results are then forwarded to the request and results processing server 300 for routing to the respective system user.

Once the search engine processor 351 has ranked the search results, these results are sent to the search results form builder 305 (routine 665 in FIG. 14B). Routine 667 separates the results based on whether the results are in response to user defined search criteria or suggested criteria. Routine 668 reads the metadata of each result listing and enters the metadata into the data fields of a structured search results form 674. The search results form 674 shown in FIG. 19 contains data fields including, but not limited to, program title, scheduled time of availability, content provider or channel, program type, category, running time, production date, critical reviews or links to reviews, data concerning frequency and number of downloads by other users, target audience or content rating, and the general description including program description, plot line, and cast. The system 200 then accesses the user's profile and determines if based on user information, account type, and search type whether advertising is to be incorporated into the display of the search results. If so, select advertising routine 669 (see FIG. 14B) determines what targeted and general advertising is to be sent and retrieves from the aggregator local database 501 the advertisements that have not previously been sent to the user and stored in the user terminal 202 for playout. These advertisements are bundled with the search results form 674 and log results routine 670 logs the results form and which advertisements were chosen into the user's profile in the aggregator local database 501. The routine 670 then routes the advertisements and the search results form 674 through the communications server 250 to the user terminal 202, which stores and displays the results (display routine 700).

Based on the content search, the user terminal 202 receives the search results form 674 from the communications server 250. FIGS. 15A and 15B show a display programming search results process 700 with the search results fornl 674 being decrypted and routed to the results processing task internal to the user terminal processor 227, routine 701. The following tasks are all carried out by separate software and/or firmware modules that are subsystems of the user terminal processor 227. In storage routine 702, the processor 227 stores the search results form 674 in the user local database 213 with a logical link to, or association with, the search request form 618 that generated the search results. At the same time, if advertisements are sent to the user terminal 202 by the aggregator 201 for display with the results, the routine 702 saves the files to the user local storage 212. After receipt of the search request form 618, routine 703 displays a prompt and/or activates an audible notification that the results of a particular search have been received. Based on a user response to the prompt, routine 704 determines if the results should be displayed at that time. If the user does not wish to display the results at that time, routine 705 informs the user via the audio/visual playout systems 208/207 that the results have been stored for later display. The content displayed on the playout systems (208/207) is then returned to whatever content was previously being presented, routine 706. The user terminal processor 227 then stops processing of the results, routine 707.

If the user wishes to view the search results when prompted, translation routine 708 translates the search results form 674 into the default display format. The default display format can be customized by the user either by manipulating the display and saving the display as the default user format, or accessing and altering a default display template. At anytime, the user can revert to the system default format, which may list the program results in ranked order and may display program attributes including, but not limited to, title, program availability, program schedule, content provider or channel, content type, description, program rating, and options for download. In an embodiment, the default results display includes two sections displayed on-screen with one section displaying results that match the user's search criteria and the second section displaying suggested results based on criteria generated earlier in the process by the content search suggestion engine 304. In another embodiment, one or more sections of the display screen may be dedicated to static or dynamic advertising. In yet another embodiment, the advertisements may serve as hyperlinks to more information about a product or service, or directly to advertised content.

The search results display may be in the form of a GUI that will incorporate, in different sections of the display, various user options including, but not limited to, download and view a particular program, download program and save to user local storage 212 for later viewing, re-order results based on a particular attribute such as program type or content provider, modify or refine search, quit results display, and view other available GUIs. Routine 710 determines if the user wishes to display additional information about a certain content listing based on user input and display routine 711 displays the full content description and selected metadata for the selected content. When the user is finished reviewing the additional information, display is returned to the last screen to have been displayed (routine 711). Routine 712 executes when the user enters a request into the system 200 to download selected content from the results display. Once the request is entered, storage routine 713 stores the selection information in the user profile section of the user local database 213 and passes control to routine 714. Routine 714 then performs three actions: 1) it displays that the download request is being processed; 2) prompts the user to select another content listing for download; and 3) routes the first download request to format routine 715, which formats the content download request form 716 along with appropriate user information for transmission to the aggregator 201. The program download request form 716 is then encrypted and sent over the wide area distribution system 203 to the communications server 250.

Routine 717 monitors the user input and if the user elects to download more programming, the routine 717 returns control to the display routine 709, which once again displays the search results at the video display system 207. If the user does not wish to download more programming, the routine 717 routes control to routine 718, which determines from the user input if the user wants to view other on-screen GUI options. If the user elects to view other on-screen GUI options, display routine 719 displays a status message that the search results have been saved locally and routine 725 starts the process to display other system GUIs. If the user does not wish to view other GUIs, the routine 718 routes control to the routine 705, which resumes the programming playout that was interrupted for the preceding processes.

FIGS. 16A and 16B show a flowchart showing the processing content download requests process 750. Once the user terminal 202 has initiated transmission of a download request, the content download request form 716 is received by the communications server 250 and routed to the request and results processing server 300 (routine 751). Within the request and results processing server 300, log routine block 752, the request receiver and router 301 logs the download request with the database administrator 502 in the system administrator 500, entering the data as part of the user's profile. In routine 753, the system administrator 500 retrieves information from the user's profile pertaining to the user's rights to download certain content and execution of routine 754 compares the user data and the content download request in order to verify that the user is authorized to download the requested content. If the user is not authorized to download the requested information, the system administrator 500, in routine 755, sends a message through the request receiver and router 301 to the communications server 250 addressed to the user, informing the user that the request has been denied. The event is then logged with the system administrator 500. Then the process stops, routine 756.

If the content download request is authorized, execution of the routine 757 encrypts and routes an authorized download request form 758 to the content acquisition server 400. Routine 759 then analyzes the metadata associated with the requested content and calls on the aggregator local database 501 to retrieve appropriate data to verify that the content is referenced properly within the request and is still available for download from the indicated storage location or streaming source. Routine 760 then determines if the requested content is to be delivered from a local source or a remote source. If the content is available locally, processing moves to routine 761, which designates the request as an authorized local download request form 769 and routes the request to the content delivery server 450 for fulfillment of the download request, process 800.

If the requested content is only available from a remote source, the routine 760 routes the request to routine 762, which routes the request through the network gateway 251 to the remote content server 204 designated in the aggregator remote content database 517. The remote content server 204 then verifies, using routine 763, that the request is authorized and that the content is still available for delivery. If the content is authorized and available, then routine 763 returns what is now an authorized remote download request form 768 through the network gateway 251 to the content delivery server 450 for fulfillment of the download request, process 800. If the request is not authorized, or if the content is no longer available for download, routine 764 sends notification to that effect through the network gateway 251 to the system administrator 500 in the aggregator 201. In routine 765, the system administrator 500 logs the status of the request and the requested programming in the aggregator local database 501 and the remote content server 204 logs the same information in the remote server database 260. The aggregator 201 then sends a notification, routine 766, to the user informing the user that the request cannot be fulfilled and the reason. The process then terminates with routine 767.

Once a download request has been processed and authorized, the download request is forwarded to the content delivery server 450, which fulfills delivery of the content using the content delivery process 800 shown in FIGS. 17A, 17B and 17C. As an authorized remote download request form 768 or an authorized local download request form 769 is received, the content delivery server 450 determines, routine 801, if the request is local or remote, and routes the request form appropriately (routine 802 for a remote request and routine 819 for a local request).

If the request is to be fulfilled remotely, execution of the routine 802 transmits a message to the remote content server 204 to begin delivery of the programming content. In routine 803, the download request is analyzed and the remote content server 204 determines if the content can be delivered directly to the user without going back through the aggregator 201.

If the content is not designated for delivery directly to the user, routine 804 is executed, which establishes a communications link with the content acquisition server 400 through the network gateway 251 and starts transmitting the requested programming. In the case of programming that is airing in real-time, the programming can be in the form of an audio/video stream from various remote streaming sources 259. Non-real-time programming can be in the form of compressed audio/video files delivered from remote content storage 258. When the content delivery process commences, execution of routine 806 initiates a process in the system administrator 500 that analyzes the content metadata and determines if the programming should be stored at the aggregator local storage 254. The system administrator 500 may determine to store a particular program locally based on reasons including, but not limited to, the program being a live event such as a sports event or a musical concert that will likely be requested for download in the future. Alternatively, the programming is not stored locally and the current request represents a predetermined number of users that have requested the content requiring remote delivery.

If the programming being delivered from a remote content server 204 will be stored to the aggregator local storage 254, the programming metadata is analyzed (routine 807) to determine if the content is in an acceptable format for local storage. The aggregator 201 may be configured to store content in one or more specific formats that will balance the highest quality of programming content to be delivered to the users versus available storage space. In an embodiment, one or more of the selected storage formats will make the most efficient use of the aggregator local storage 254 resources as well as support high-speed delivery to system users. If the content is determined to meet the format requirements for local storage, processing passes on to routine 810. If the content does not meet the format requirements, the content stream and/or files are routed to the decoder and content formatter 252, routine 808. At routine 809, the decoder and content formatter 252 decodes the incoming data and may extract digital and/or analog data representing the content and its metadata. The decoder and content formatter 252 then reformats the content into the required formats and coding schemes for local storage. Upon execution of storage routine 810, the properly formatted programming content is stored to the aggregator local storage 254. The process and the new location of the content is then logged into the aggregator local database 501.

Whether or not the content was stored locally, routine 811 analyzes the programming content's metadata and determines if the content is in the appropriate format and coding scheme for delivery to the user. The format and coding scheme for delivery may be different from that used for local storage in order to accommodate particular parameters of a user's download request. The user may request specific formats and coding schemes due to considerations including, but not limited to, the method of playback, the type of programming, whether the user intends to store the content, or the type and bandwidth of the connection the user terminal 202 has to the aggregator 201 or the remote content server 204. If the content is determined to meet the format requirements for delivery to the user, processing moves to routine 814. If the content does not meet the format criteria, the content stream and/or files are routed to the decoder and content formatter 252 by (routine 812) along with the required formatting and coding parameters. At routine 813, the decoder and content formatter 252 decodes the incoming data and may extract digital and/or analog data representing the content and its metadata. The decoder and content formatter 252 then reformats the content into the required formats and coding schemes for delivery to the user. Processing then moves to routine 823 for delivery, which is discussed below when that processing path becomes common to both remote and local content delivery.

Returning to block 803 in FIG. 17 A, if the programming content is designated for direct delivery to the user's terminal, the remote content server 204 establishes a communications link with the user terminal 202 (routine 815) and delivers the content files or streams the broadcast program directly to the user terminal 202 (routine 816). After the completed delivery is validated during routine 816, routine 817 logs the delivery fulfillment in the remote server database 260 and notifies the content acquisition server 400 at the aggregator 201 that the requested programming content has been successfully delivered to the user. Processing is then moved to the system administrator 500 (routine 826), which is discussed below, when that processing path becomes common to each delivery type.

If the programming download request is to be fulfilled by the local aggregator 201, execution of the routine 801 passes processing to routine 819 in the local content request processor 451 of the content delivery server 450, which analyzes the programming content's metadata and determines if the content is in the appropriate format and coding scheme for delivery to the user. If the content is determined to meet the format requirements for delivery to the user, processing moves to routine 822. If the format and coding scheme is not correct, execution of the routine 820 retrieves the programming content from the aggregator local storage 254 or the appropriate local streaming sources 262 and routes the programming to the decoder and content formatter 252 along with the required formatting and coding parameters. In routine 821, the decoder and content formatter 252 decodes the incoming data and may extract digital and/or analog data representing the content and its metadata. The decoder and content formatter 252 then reformats the content into the required formats and coding schemes for delivery to the user. Execution of routine 822 takes the correctly coded and formatted programming content file(s) and/or streams, whether directly from local sources or from the decoder and content formatter 252, and routes this content to the content delivery server 450.

Whether the programming content is being delivered by the local aggregator 201 from a remote source or a local source, upon execution of routine 823, the content delivery server 450 analyzes the user's profile information and the content metadata and, if applicable, instructs the digital rights management processor 454 to apply the appropriate DRM scheme to the content delivery. If the DRM scheme involves encrypting the programming content for delivery, the programming content is routed to the encryption processor 455, which processes the digital content data through an encryption algorithm using the appropriate user encryption key and routes the encrypted data back to the content delivery server 450.

The content delivery server 450 then analyzes the metadata and user information, routine 824 and, if applicable, instructs the advertisement processor 456 to incorporate any advertising into the delivery that is appropriate. The advertising is then retrieved from the aggregator local database 501 and packaged with the programming content delivery. In an embodiment, the advertisement processor 456 may have already delivered particular advertising to the user terminal 202 for storage, and having determined this from the user data, may insert a placeholder for an advertisement that will instruct the user terminal 202 to retrieve and display the advertisement at the appropriate time.

Upon execution of routine 825, the content delivery server 450 instructs the communications server 250 to establish a communications link with the user terminal 202 through the wide area distribution system 203, initiating a content reception process 850. The content delivery processor 453 delivers the content to the user terminal 202 (routine 826) through the communications server 250 and wide area distribution system 203. Execution of routine 827 verifies the correct delivery of the programming content to the user, and when the delivery is complete, logs the successful delivery with the system administrator 500. The delivery of content may be done in real-time in the case of broadcast programs and live or scheduled program streams or can be done in non-real-time where the content is delivered at a rate higher than that required for real-time viewing and is stored by the user terminal 202 for playback at a time chosen by the user. (See DAVIC 1.5 Specifications, TV Anytime and TV Anywhere, Revision 6.0; copyright Digital Audio-Visual Council (DAVIC), hereby incorporated by reference, for more detail about concurrent viewing and storing, non-linear playback, non-real-time delivery, and content storage and management.)

Whether the programming was delivered by the local aggregator 201 or by a remote content server 204, processing moves to routine 828 in the system administrator 500, which analyzes the user profile and the content metadata to determine whether the user will be billed or if the content provider is due a fee for the content delivery. If no bills are due, processing ends, routine 829. If billing or fees are applicable, routine 830 routes user informATIon, appropriate content metadata, and content provider information to the system administrator 500, which enters this data into the billing process represented by routine 900.

Prior to content delivery, the programming content may be processed by the coder and content formatter 253 if required to deliver the content in an appropriate digital coding scheme, compression, and content format to the user. The coder and content formatter 253 employs digital compression techniques to increase existing transmission capacity. A number of digital compression algorithms currently exist or may be developed in the future that can achieve the resultant increase in capacity and improved signal quality desired for the system 200. The algorithms generally use one or more of three basic digital compression techniques: (1) within-frame (intraframe) compression, (2) frame-to-frame (interframe) compression, and (3) within carrier compression. The coder and content formatter 253 of the content search, packaging, and delivery system 200 will be able to use any of these techniques in addition to being able to have its capabilities modularly expanded to include any emerging and future techniques that are determined to be desirable.

In an embodiment, although a single digital compression standard may be used for the delivery system 200, different levels of compression can be utilized when delivering programs to a user requesting a particular program. For example, if the program is sent out using an HDTV format, then less compression is used as opposed to sending out the program using a standard video format. The reason is that the HDTV format requires more digital data per portion of content. Since the HDTV format requires more digital data, it will also require more bandwidth to transmit, possibly increasing the cost of delivery. Therefore, the quality of the video delivered may be a variable in the fees charged to users of the system 200.

Since programming content can be delivered in more than one way, the user may also consume the programming in more than one way. Audio/Video Content can be viewed and/or listened to concurrently with the delivery in the case of a broadcast delivery over the cable television system as well as during an Internet delivery of a data stream or file that contains the programming. The user can also store the content as the content is delivered, whether or not the user consumes the content during the delivery, allowing for non-linear playback of content at the user terminal 202 either during delivery or at a later time. Non-linear playback refers to the ability of a user to stop, start, pause, rewind, slowdown, and speedup the playout of a piece of video or audio content. In an embodiment, programming is delivered from the system 200 in less time that it would take to consume the programming and is saved in user local storage 212 for use at any time thereafter. In the case of a real-time broadcast, the storage method may be onto magnetic tape using an audio/video recording

system 209 such as a video cassette recorder, or into user local storage 212 as a digital file such as onto a computer hard disk drive or other digital data storage medium. Once the user has numerous programs stored in the user local storage 212, the user terminal 202 will provide the ability for the user to manage content storage and organization through a series of simple GUIs approximating an audio-video library collection. Storage management may also be automated using either user-defined or pre-set rules, or both. (See DAVIC 1.5 Specifications, TV Anytime and TV Anywhere, Revision 6.0; copyright Digital Audio-Visual Council (DA VIC), hereby incorporated by reference, for more detail about concurrent viewing and storing, non-linear playback, non-real-time delivery, and content storage and management.)

In an embodiment, the user terminal 202, whether is comprised of a set top terminal 206, a personal computer terminal 211, or some combination thereof, is integrated into a home network 229 serving the user's home. This will enable the consumption of programming content at numerous nodes in the home which may consist of auxiliary user terminals and/or personal computers with various combinations of video display system 207, audio playout system 208, and audio/video recording system 209. The primary user terminal 202 can route programming search and download requests from other network nodes and route subsequent downloaded programming to the requesting node either an a baseband video network or a digital data network such as an Ethernet network. Auxiliary nodes may also have a combination of user input devices 214 to control the system and initiate programming requests and downloads. In an embodiment, a handheld remote control 225 using wireless radio frequency transmission may control the primary user terminal 202 from a remote location to deliver programming to a remote video display system 207.

The search, packaging, and delivery system 200 may be a revenue generating system for its operators and for registered content providers. In addition to revenue that can be generated from various advertising schemes within the system 200, the system 200 may optionally support a customer-billing model in which users can be billed in different ways. Customer billing schemes include, but are not limited to, term fees for basic services, i.e., monthly billing; subscriptions to various service packages; fees per content download; and total quantity of downloaded material for a given time period. The customer billing server 506 within the system administrator 500 may track services rendered, maintain a user billing account, and track user payments for services. In addition, authorization levels can be set to prevent unauthorized usage. In an embodiment, a single account can have multiple users with different levels of authorization and content access rights. An example is a large family with a single account with each family member having a user profile and attendant usage rights. These usage rights will be administered by the primary user of the account, typically the head of the household.

In order to provide high quality programming content to the user, many of the content providers will be entitled to fees for access to premium content, especially copyrighted content. These fees will be tracked by the content fee and copyright billing server 507 within the system administrator 500. Content providers will be able to register with the 200 using software hosted by the content provider registration server 505 within the system administrator 500. The registration software may collect all relevant data about the content provider and the content provider's proposed content to be made available to users. Using a pre-existing fee table, the provider may be informed of the fees to be made available for the various programming content to be provided. In addition, fees for sufficiently unique content may be negotiated outside the automated registration process. In an embodiment, the content fee and copyright billing server 507 may initiate compensation to content providers at scheduled intervals based on the distribution of content for the prior period.

Part of the registration may include furnishing the content provider with software tools to assist in populating the appropriate metadata fields for new content. For example, an original television show may need to have its program type, description, cast, and other information entered into the metadata database in a manner consistent with that in use by the aggregator 201. In an embodiment, the content provider registration server 505 will run various algorithms to collect this information automatically from differing content providers' databases. In another preferred embodiment, the automatic collection may be augmented by a series of prompt screens for the content provider to manually input the data into the system.

During content registration, and at any time that additional content is made available by the content provider, the content provider can use the content provider registration server 505 services to designate usage rights for programming content. These rights can be assigned to individual pieces of content or to groups or classes of content. Usage rights define how a specific user, or tier of users, can use the digital content when it is delivered to the user terminal 202. The defined usage rights for content are then incorporated into the digital rights management (DRM) scheme that is applied to the content by the content delivery server 450 and may require encryption as part of a secure delivery process. Usage rights either prevent or enable a user to perform certain actions with the digital programming content including, but not limited to, whether content can be recorded or stored, whether the user can make copies of stored content and onto what types of media, whether the content can be played back a finite number of times or indefinitely, whether the content can be spliced, edited, or imported into another digital processing environment, and whether the content can be exported from the system for distribution to a third party.

When content is downloaded to a user, the content delivery server 450 logs the delivery with the database administrator 502, the customer billing server 506, and the content fee and copyright billing server 507. The database administrator 502 incorporates the information into the user profile and the billing servers determine if the user will be charged a fee for the particular content and whether the provider is entitled to a fee for the content.

Users will be able to register with the system 200 using software hosted by the user registration server 504 within the system administrator 500. The user registration software will allow the user to perform numerous tasks including, but not limited to, set up the user's account, choose a billing scheme, select premium content tiers, enter user profile information and preferences, set up multiple user profiles and administer usage rights. At any time in the future, the user can access data that is collected for the user profile and can review and revise user data, opt out of or terminate data collection, request deletion of user data, and review how this data is being used by the system 200.

Claims

1. A method comprising: receiving, from a first user device, a search request;searching, based on the search request, for content of at least one content source in a distributed digital communication network;determining that the searching was unsuccessful;storing the search request;after determining that the searching was unsuccessful, determining, based on at least one change in the at least one content source, available content associated with the search request;sending, to a second user device, data indicative of the available content; andreceiving a selection of a content item associated with the available content.
2. The method of claim 1, further comprising: sending, to the second user device, the selected content item.
3. The method of claim 1, further comprising: causing storage, at the first user device, of the selected content item.
4. The method of claim 1, further comprising: encoding the selected content item for delivery to the second user device; andsending, to the second user device, the encoded content item.
5. The method of claim 1, wherein the selected content item is associated with a digital rights management (DRM) scheme that allows delivery of the selected content item to the second user device.
6. The method of claim 1, wherein the search request comprises: search request criteria;a user identification information;an authorization code;a requested content format; anduser network routing information.
7. The method of claim 1, wherein the first user device comprises a first node of a home network and the second user device comprises a second node of the home network.
8. The method of claim 1, wherein the at least one content source in the distributed digital communication network comprises one or more of local streaming sources or remote streaming sources.
9. The method of claim 1, wherein the search request is received via a wide area network.
10. A method comprising: receiving, from a first user device, a search request;searching, based on the search request, for content of at least one content source in a distributed digital communication network;determining that the searching was unsuccessful;storing the search request;after determining that the searching was unsuccessful, determining, based on at least one change in the at least one content source, available content associated with the search request;determining whether a digital rights management (DRM) scheme allows delivery, to a second user device, of the available content; andafter determining that the DRM scheme allows delivery, to the second user device, of at least one content item associated with the available content, sending, to the second user device, the at least one content item associated with the available content.
11. The method of claim 10, further comprising: after determining that the DRM scheme allows storing, at the second user device, the at least one content item associated with the available content, causing storage, at the second user device, of the at least one content item associated with the available content.
12. The method of claim 10, further comprising: after determining that the DRM scheme allows encoding the at least one content item associated with the available content: encoding the at least one content item for delivery to the second user device; andsending, to the second user device, the encoded at least one content item.
13. The method of claim 10, wherein the search request comprises: search request criteria;a user identification information;an authorization code;a digital rights management parameter;a requested content format; anduser network routing information.
14. The method of claim 10, wherein the first user device is located in a first node of a home network and the second user device is located in a second node of the home network.
15. The method of claim 10, wherein the at least one content source in the distributed digital communication network comprises one or more of local streaming sources or remote streaming sources.
16. The method of claim 10, wherein the search request is received via a wide area network.
17. A method comprising: receiving, from a first user device, a search request;searching, based on the search request, for content in at least one content source in a distributed digital communication network;determining that the searching was unsuccessful;storing the search request;after determining that the searching was unsuccessful, receiving, based on at least one change in the at least one content source, data indicative of available content associated with the search request;validating, based on the search request, the available content;receiving a selection of a content item associated with the available content; andencoding the selected content item for delivery to a second user device.
18. The method of claim 17, further comprising: sending, to the second user device, the encoded content item.
19. The method of claim 17, further comprising: causing storage, at the second user device, of the encoded content item.
20. The method of claim 17, wherein the first user device is located in a first node of a home network and the second user device is located in a second node of the home network.

RELATED APPLICATIONS

The present application is a continuation of U.S. application Ser. No. 14/093,807, filed on Dec. 2, 2013, which is a continuation of U.S. application Ser. No. 13/544,423, filed on Jul. 9, 2012, now U.S. Pat. No. 8,621,521, which is a continuation of U.S. application Ser. No. 12/856,830, filed on Aug. 16, 2010, now U.S. Pat. No. 8,245,259, which is a continuation of U.S. application Ser. No. 09/920,723, filed Aug. 3, 2001, now U.S. Pat. No. 7,793,326. The contents of each of these applications are incorporated herein by reference for all purposes. The following U.S. patents also are incorporated by reference: U.S. Pat. No. 5,798,785, entitled “Terminal for Suggesting Programs Offered on a Television Program Delivery System;” U.S. Pat. No. 5,986,690, entitled “Electronic Book Selection and Delivery System;” The following co-pending U.S. patent applications also are incorporated by reference: Patent application Ser. No. 07/991,074, filed Dec. 9, 1992, entitled “Remote Control for Menu Driven Subscriber Access to Television Programming;” Patent application Ser. No. 08/906,469, filed Aug. 5, 1997, entitled “Reprogrammable Terminal for Suggesting Programs Offered on a Television Program Delivery System;” Patent application Ser. No. 09/191,520, filed Nov. 13, 1998, entitled “Digital Broadcast Program Ordering;” Patent application Ser. No. 09/289,957, filed Apr. 13, 1999, entitled “Electronic Book Alternative Delivery Systems;” Patent application Ser. No. 09/289,956, filed Apr. 13, 1999, entitled “Electronic Book Alternative Delivery Methods;” Patent application Ser. No. 09/921,057, filed Aug. 3, 2001, entitled “Video and Digital Multimedia Aggregator Content Suggestion Engine;” and Patent application Ser. No. 09/920,615, filed Aug. 3, 2001, entitled “Video and Digital Multimedia Aggregator Remote Content Crawler.”

US Referenced Citations (1303)

Number	Name	Date	Kind
3639686	Walker et al.	Feb 1972	A
3733430	Thompson et al.	May 1973	A
3754211	Rocher et al.	Aug 1973	A
3993955	Belcher et al.	Nov 1976	A
4197590	Sukonick et al.	Apr 1980	A
4213124	Barda et al.	Jul 1980	A
4225884	Block et al.	Sep 1980	A
4250356	Hammer, Jr. et al.	Feb 1981	A
4250521	Wright	Feb 1981	A
4264924	Freeman	Apr 1981	A
4264964	Berger	Apr 1981	A
4279035	Skerlos	Jul 1981	A
4290063	Traster	Sep 1981	A
4318522	Appleberry	Mar 1982	A
4331794	D'Alelio et al.	May 1982	A
4331974	Cogswell et al.	May 1982	A
4334245	Michael	Jun 1982	A
4361848	Poignet et al.	Nov 1982	A
4381522	Lambert	Apr 1983	A
4398216	Field et al.	Aug 1983	A
4402279	Witte et al.	Sep 1983	A
4437093	Bradley	Mar 1984	A
4450481	Dickinson	May 1984	A
4451701	Bendig	May 1984	A
4455548	Burnett	Jun 1984	A
4455570	Saeki et al.	Jun 1984	A
4456925	Skerlos et al.	Jun 1984	A
4479142	Buschman et al.	Oct 1984	A
4484217	Block et al.	Nov 1984	A
4484218	Boland et al.	Nov 1984	A
4488179	Kru/ ger et al.	Dec 1984	A
4496976	Swanson et al.	Jan 1985	A
4507680	Freeman	Mar 1985	A
4509198	Nagatomi	Apr 1985	A
4513315	Dekker et al.	Apr 1985	A
4517598	Van Valkenburg et al.	May 1985	A
4520356	O'Keefe et al.	May 1985	A
4520921	Vissing	Jun 1985	A
4528589	Block et al.	Jul 1985	A
4528643	Freeny, Jr.	Jul 1985	A
D280099	Topp	Aug 1985	S
4533948	McNamara et al.	Aug 1985	A
4546382	McKenna et al.	Oct 1985	A
4558464	O'Brien, Jr.	Dec 1985	A
4567512	Abraham	Jan 1986	A
4573072	Freeman	Feb 1986	A
4581484	Bendig	Apr 1986	A
4587520	Astle	May 1986	A
RE32187	Barda et al.	Jun 1986	E
4600921	Thomas	Jul 1986	A
4602278	Pritchard et al.	Jul 1986	A
4602279	Freeman	Jul 1986	A
4605964	Chard	Aug 1986	A
4620289	Chauvel	Oct 1986	A
4621282	Ahem	Nov 1986	A
4633297	Skerlos et al.	Dec 1986	A
4633462	Stifle et al.	Dec 1986	A
4639225	Washizuka	Jan 1987	A
4641205	Beyers, Jr.	Feb 1987	A
4646150	Robbins et al.	Feb 1987	A
4647964	Weinblatt	Mar 1987	A
4658290	McKenna et al.	Apr 1987	A
4665559	Benun	May 1987	A
4673976	Wreford-Howard	Jun 1987	A
4674085	Aranguren et al.	Jun 1987	A
4677685	Kurisu	Jun 1987	A
4688218	Blineau et al.	Aug 1987	A
4688246	Eilers et al.	Aug 1987	A
4691340	Maeda et al.	Sep 1987	A
4694490	Harvey et al.	Sep 1987	A
4695880	Johnson et al.	Sep 1987	A
4695975	Bedrij	Sep 1987	A
4697209	Kiewit et al.	Sep 1987	A
4706121	Young	Nov 1987	A
4712105	Kohler	Dec 1987	A
4712130	Casey	Dec 1987	A
4712239	Frezza et al.	Dec 1987	A
4724491	Lambert	Feb 1988	A
4725694	Auer et al.	Feb 1988	A
4734764	Pocock et al.	Mar 1988	A
4739318	Cohen	Apr 1988	A
4739510	Jeffers et al.	Apr 1988	A
4740834	Mobarry	Apr 1988	A
4742344	Nakagawa et al.	May 1988	A
4745468	Von Kohorn	May 1988	A
4745479	Waehner	May 1988	A
4747785	Roberts et al.	May 1988	A
4751578	Reiter et al.	Jun 1988	A
4775935	Yourick	Oct 1988	A
4779138	Nomura et al.	Oct 1988	A
RE32776	Saylor	Nov 1988	E
4792848	Nussrallah et al.	Dec 1988	A
4792849	McCalley et al.	Dec 1988	A
4792972	Cook, Jr.	Dec 1988	A
4797568	Gumbs	Jan 1989	A
4797918	Lee et al.	Jan 1989	A
4802008	Walling	Jan 1989	A
4805014	Sahara et al.	Feb 1989	A
4816901	Music et al.	Mar 1989	A
4816904	McKenna et al.	Mar 1989	A
4825200	Evans et al.	Apr 1989	A
4825220	Edward et al.	Apr 1989	A
D301037	Matsuda	May 1989	S
4829372	McCalley et al.	May 1989	A
4829558	Welsh	May 1989	A
4829569	Seth-Smith et al.	May 1989	A
4835607	Keith	May 1989	A
4845662	Tokumitsu	Jul 1989	A
4847825	Levine	Jul 1989	A
4860123	McCalley et al.	Aug 1989	A
4860379	Schoeneberger et al.	Aug 1989	A
4866770	Seth-Smith et al.	Sep 1989	A
4876592	Von Kohorn	Oct 1989	A
4876736	Kiewit	Oct 1989	A
4878048	Gottesman et al.	Oct 1989	A
4884267	Miyamoto et al.	Nov 1989	A
4885775	Lucas	Dec 1989	A
4885803	Hermann et al.	Dec 1989	A
4887308	Dutton	Dec 1989	A
4888638	Bohn	Dec 1989	A
4890321	Seth-Smith et al.	Dec 1989	A
4896354	Inagaki et al.	Jan 1990	A
4896370	Kasparian et al.	Jan 1990	A
4905094	Pocock et al.	Feb 1990	A
4907082	Richards	Mar 1990	A
4908713	Levine	Mar 1990	A
4916441	Gombrich	Apr 1990	A
4918516	Freeman	Apr 1990	A
4920432	Eggers et al.	Apr 1990	A
4922529	Kiel	May 1990	A
4924303	Brandon et al.	May 1990	A
4926255	Von Kohorn	May 1990	A
4928168	Iwashita	May 1990	A
4930160	Vogel	May 1990	A
4931872	Stoddard et al.	Jun 1990	A
4935924	Baxter	Jun 1990	A
4941040	Pocock et al.	Jul 1990	A
4943963	Waechter et al.	Jul 1990	A
4947429	Bestler et al.	Aug 1990	A
4949187	Cohen	Aug 1990	A
4956725	Kozuki et al.	Sep 1990	A
4959810	Darbee et al.	Sep 1990	A
4961109	Tanaka	Oct 1990	A
4963994	Levine	Oct 1990	A
4965825	Harvey et al.	Oct 1990	A
4974252	Osborne	Nov 1990	A
4975771	Kassatly	Dec 1990	A
4975951	Bennett	Dec 1990	A
4977455	Young	Dec 1990	A
4985697	Boulton	Jan 1991	A
4985761	Adams	Jan 1991	A
4991011	Johnson et al.	Feb 1991	A
4994908	Kuban et al.	Feb 1991	A
4994909	Graves et al.	Feb 1991	A
4995074	Goldman et al.	Feb 1991	A
4995078	Monslow et al.	Feb 1991	A
4996597	Duffield	Feb 1991	A
5001554	Johnson et al.	Mar 1991	A
5003384	Durden et al.	Mar 1991	A
5003591	Kauffman et al.	Mar 1991	A
5014125	Pocock et al.	May 1991	A
5014267	Tompkins et al.	May 1991	A
5015829	Eilert et al.	May 1991	A
5020129	Martin et al.	May 1991	A
5027400	Baji et al.	Jun 1991	A
5029014	Lindstrom	Jul 1991	A
5029232	Nall	Jul 1991	A
5034807	Von Kohorn	Jul 1991	A
5036394	Morii et al.	Jul 1991	A
5036537	Jeffers et al.	Jul 1991	A
5038211	Hallenbeck	Aug 1991	A
5038402	Robbins	Aug 1991	A
5040067	Yamazaki	Aug 1991	A
5046093	Wachob	Sep 1991	A
5047858	Aimonoya	Sep 1991	A
5047867	Strubbe et al.	Sep 1991	A
5047887	Boshek	Sep 1991	A
5049990	Kondo et al.	Sep 1991	A
5054071	Bacon	Oct 1991	A
5055924	Skutta	Oct 1991	A
5056138	Tyson, Sr.	Oct 1991	A
5057915	Von Kohorn	Oct 1991	A
5057917	Shalkauser et al.	Oct 1991	A
5058160	Banker et al.	Oct 1991	A
5066319	Lippold	Nov 1991	A
5070400	Lieberman	Dec 1991	A
5073930	Green et al.	Dec 1991	A
5075771	Hashimoto	Dec 1991	A
5077607	Johnson et al.	Dec 1991	A
5078019	Aoki	Jan 1992	A
5083205	Arai	Jan 1992	A
5091782	Krause et al.	Feb 1992	A
5093718	Hoarty et al.	Mar 1992	A
5099319	Esch et al.	Mar 1992	A
D325581	Schwartz	Apr 1992	S
5103314	Keenan	Apr 1992	A
5105268	Yamanouchi et al.	Apr 1992	A
5109279	Ando	Apr 1992	A
5113496	McCalley et al.	May 1992	A
5115309	Hang	May 1992	A
5115426	Spanke	May 1992	A
5119188	McCalley et al.	Jun 1992	A
5121205	Ng et al.	Jun 1992	A
5123046	Levine	Jun 1992	A
5124980	Maki	Jun 1992	A
5128752	Von Kohorn	Jul 1992	A
5130792	Tindell et al.	Jul 1992	A
5130794	Ritchey	Jul 1992	A
5132789	Ammon et al.	Jul 1992	A
5132992	Yurt et al.	Jul 1992	A
5133079	Ballantyne et al.	Jul 1992	A
5134712	Yamamoto	Jul 1992	A
5142690	McMullan, Jr. et al.	Aug 1992	A
D329238	Grasso et al.	Sep 1992	S
5144445	Higashitsutsumi	Sep 1992	A
5144663	Kudelski et al.	Sep 1992	A
5146210	Heberle	Sep 1992	A
5150118	Finkle et al.	Sep 1992	A
5151782	Ferraro	Sep 1992	A
5151785	Citta	Sep 1992	A
5151789	Young	Sep 1992	A
5152011	Schwob	Sep 1992	A
5153763	Pidgeon	Oct 1992	A
5155591	Wachob	Oct 1992	A
5157717	Hitchcock	Oct 1992	A
5161012	Choi	Nov 1992	A
5161019	Emanuel	Nov 1992	A
5166886	Molnar et al.	Nov 1992	A
D331760	Renk, Jr.	Dec 1992	S
5168372	Sweetser	Dec 1992	A
5172413	Bradley et al.	Dec 1992	A
5172423	France	Dec 1992	A
5182639	Jutamulia et al.	Jan 1993	A
5182640	Takano	Jan 1993	A
5187710	Chau et al.	Feb 1993	A
5187735	Herrero Garcia et al.	Feb 1993	A
5191410	McCalley et al.	Mar 1993	A
5192999	Graczyk et al.	Mar 1993	A
5195022	Hoppal et al.	Mar 1993	A
5195092	Wilson et al.	Mar 1993	A
5202817	Koenck et al.	Apr 1993	A
5206722	Kwan	Apr 1993	A
5206929	Langford et al.	Apr 1993	A
5206954	Inoue et al.	Apr 1993	A
5208660	Yoshida	May 1993	A
5208665	McCalley et al.	May 1993	A
5212553	Maruoka	May 1993	A
5216515	Steele et al.	Jun 1993	A
5221962	Backus et al.	Jun 1993	A
5223924	Strubbe	Jun 1993	A
5227874	Von Kohorn	Jul 1993	A
5229852	Maietta et al.	Jul 1993	A
5231494	Wachob	Jul 1993	A
5231516	Kamon et al.	Jul 1993	A
5231665	Auld et al.	Jul 1993	A
5233654	Harvey et al.	Aug 1993	A
5235328	Kurita	Aug 1993	A
5235419	Krause	Aug 1993	A
5236199	Thompson, Jr.	Aug 1993	A
5237311	Mailey et al.	Aug 1993	A
5237610	Gammie et al.	Aug 1993	A
5239540	Rovira et al.	Aug 1993	A
5241428	Goldwasser et al.	Aug 1993	A
5241659	Parulski et al.	Aug 1993	A
5247347	Litteral et al.	Sep 1993	A
5247364	Banker et al.	Sep 1993	A
5247575	Sprague et al.	Sep 1993	A
5249044	Von Kohorn	Sep 1993	A
5251324	McMullan, Jr.	Oct 1993	A
5253066	Vogel	Oct 1993	A
5253275	Yurt et al.	Oct 1993	A
5253341	Rozmanith et al.	Oct 1993	A
5255086	McMullan, Jr. et al.	Oct 1993	A
D341383	London et al.	Nov 1993	S
5260778	Kauffman et al.	Nov 1993	A
5260788	Takano et al.	Nov 1993	A
5264933	Rosser et al.	Nov 1993	A
5270809	Gammie et al.	Dec 1993	A
5274700	Gechter et al.	Dec 1993	A
5276731	Arbel et al.	Jan 1994	A
5282028	Johnson et al.	Jan 1994	A
5283561	Lumelsky et al.	Feb 1994	A
5283639	Esch et al.	Feb 1994	A
5283734	Von Kohorn	Feb 1994	A
5285272	Bradley et al.	Feb 1994	A
5289271	Watson	Feb 1994	A
5289288	Silverman et al.	Feb 1994	A
5293357	Hallenbeck	Mar 1994	A
5293540	Trani et al.	Mar 1994	A
5293633	Robbins	Mar 1994	A
5297204	Levine	Mar 1994	A
5301028	Banker et al.	Apr 1994	A
5301050	Czerwiec et al.	Apr 1994	A
5303295	West et al.	Apr 1994	A
5303361	Colwell et al.	Apr 1994	A
5307173	Yuen et al.	Apr 1994	A
5307481	Shimazaki et al.	Apr 1994	A
5311423	Clark	May 1994	A
5311425	Inada	May 1994	A
5315584	Savary et al.	May 1994	A
5317391	Banker et al.	May 1994	A
5319454	Schutte	Jun 1994	A
5319455	Hoarty et al.	Jun 1994	A
5319707	Wasilewski et al.	Jun 1994	A
5323240	Amano et al.	Jun 1994	A
5327554	Palazzi, III et al.	Jul 1994	A
5329590	Pond	Jul 1994	A
5335079	Yuen et al.	Aug 1994	A
5335276	Thompson et al.	Aug 1994	A
5335313	Douglas	Aug 1994	A
5339239	Manabe et al.	Aug 1994	A
5339315	Maeda et al.	Aug 1994	A
5341166	Garr et al.	Aug 1994	A
5341425	Wasilewski et al.	Aug 1994	A
5341426	Barney et al.	Aug 1994	A
5341474	Gelman et al.	Aug 1994	A
5343239	Lappington et al.	Aug 1994	A
5343516	Callele et al.	Aug 1994	A
5345594	Tsuda	Sep 1994	A
5347304	Moura et al.	Sep 1994	A
5349638	Pitroda et al.	Sep 1994	A
5351075	Herz et al.	Sep 1994	A
5353121	Young et al.	Oct 1994	A
5355162	Yazolino et al.	Oct 1994	A
5357276	Banker et al.	Oct 1994	A
5359601	Wasilewski et al.	Oct 1994	A
5361091	Hoarty et al.	Nov 1994	A
5363431	Schull et al.	Nov 1994	A
5365265	Shibata et al.	Nov 1994	A
5365282	Levine	Nov 1994	A
5367330	Haave et al.	Nov 1994	A
5367571	Bowen et al.	Nov 1994	A
5373330	Levine	Dec 1994	A
5374951	Welsh	Dec 1994	A
5375068	Palmer et al.	Dec 1994	A
5375161	Fuller et al.	Dec 1994	A
5376969	Zdepski	Dec 1994	A
5381477	Beyers, II et al.	Jan 1995	A
5382983	Kwoh et al.	Jan 1995	A
5384588	Martin et al.	Jan 1995	A
5386241	Park	Jan 1995	A
5387941	Montgomery et al.	Feb 1995	A
5389964	Oberle et al.	Feb 1995	A
5390348	Magin et al.	Feb 1995	A
5393964	Hamilton et al.	Feb 1995	A
5396546	Remillard	Mar 1995	A
5398074	Duffield et al.	Mar 1995	A
5400401	Wasilewski et al.	Mar 1995	A
5400402	Garfinkle	Mar 1995	A
5404393	Remillard	Apr 1995	A
5404505	Levinson	Apr 1995	A
5406557	Baudoin	Apr 1995	A
5406558	Rovira et al.	Apr 1995	A
5406564	Okita	Apr 1995	A
5406615	Miller, II et al.	Apr 1995	A
5408258	Kolessar	Apr 1995	A
5410326	Goldstein	Apr 1995	A
5410344	Graves et al.	Apr 1995	A
5410367	Zahavi et al.	Apr 1995	A
5412416	Nemirofsky	May 1995	A
5412720	Hoarty	May 1995	A
5414426	O'Donnell et al.	May 1995	A
5414448	Wada et al.	May 1995	A
5414756	Levine	May 1995	A
5416508	Sakuma et al.	May 1995	A
5420647	Levine	May 1995	A
5420866	Wasilewski	May 1995	A
5421031	De Bey	May 1995	A
5422674	Hooper et al.	Jun 1995	A
5424770	Schmelzer et al.	Jun 1995	A
5426699	Wunderlich et al.	Jun 1995	A
5428404	Ingram et al.	Jun 1995	A
5428608	Freeman et al.	Jun 1995	A
5432542	Thibadeau et al.	Jul 1995	A
5432561	Strubbe	Jul 1995	A
5438370	Primiano et al.	Aug 1995	A
5438372	Tsumori et al.	Aug 1995	A
5440632	Bacon et al.	Aug 1995	A
5442389	Blahut et al.	Aug 1995	A
5442452	Ryu	Aug 1995	A
5442626	Wei	Aug 1995	A
5446490	Blahut et al.	Aug 1995	A
5446919	Wilkins	Aug 1995	A
5448313	Kim et al.	Sep 1995	A
5448568	Delpuch et al.	Sep 1995	A
5449970	Kumar et al.	Sep 1995	A
5461667	Remillard	Oct 1995	A
5467144	Saeger et al.	Nov 1995	A
5467402	Okuyama et al.	Nov 1995	A
5469206	Strubbe et al.	Nov 1995	A
5473362	Fitzgerald et al.	Dec 1995	A
5473609	Chaney	Dec 1995	A
5473704	Abe	Dec 1995	A
5475382	Yuen et al.	Dec 1995	A
5477262	Banker et al.	Dec 1995	A
5477263	O'Callaghan et al.	Dec 1995	A
5479266	Young et al.	Dec 1995	A
5479268	Young et al.	Dec 1995	A
5479411	Klein	Dec 1995	A
5479508	Bestler et al.	Dec 1995	A
5481294	Thomas et al.	Jan 1996	A
5481296	Cragun et al.	Jan 1996	A
5481542	Logston et al.	Jan 1996	A
5483277	Granger	Jan 1996	A
5483278	Strubbe et al.	Jan 1996	A
5483287	Siracusa	Jan 1996	A
5483588	Eaton et al.	Jan 1996	A
5485197	Hoarty	Jan 1996	A
5485221	Banker et al.	Jan 1996	A
5488409	Yuen et al.	Jan 1996	A
5488412	Majeti et al.	Jan 1996	A
5490247	Tung et al.	Feb 1996	A
5493339	Birch et al.	Feb 1996	A
5493568	Sampat et al.	Feb 1996	A
5493638	Hooper et al.	Feb 1996	A
5493677	Balogh et al.	Feb 1996	A
5497187	Banker et al.	Mar 1996	A
5500794	Fujita et al.	Mar 1996	A
5500933	Schnorf	Mar 1996	A
5502504	Marshall et al.	Mar 1996	A
5508733	Kassatly	Apr 1996	A
5508815	Levine	Apr 1996	A
5512934	Kochanski	Apr 1996	A
5512935	Majeti et al.	Apr 1996	A
5515098	Carles	May 1996	A
5515106	Chaney et al.	May 1996	A
5515173	Mankovitz et al.	May 1996	A
5517257	Dunn et al.	May 1996	A
5517502	Bestler et al.	May 1996	A
5523794	Mankovitz et al.	Jun 1996	A
5523796	Marshall et al.	Jun 1996	A
5526034	Hoarty et al.	Jun 1996	A
5528281	Grady et al.	Jun 1996	A
5530754	Garfinkle	Jun 1996	A
5532732	Yuen et al.	Jul 1996	A
5532754	Young et al.	Jul 1996	A
5533110	Pinard et al.	Jul 1996	A
5534913	Majeti et al.	Jul 1996	A
5534944	Egawa et al.	Jul 1996	A
5537141	Harper et al.	Jul 1996	A
5537153	Shigihara	Jul 1996	A
5537157	Washino et al.	Jul 1996	A
5539391	Yuen	Jul 1996	A
5539449	Blahut et al.	Jul 1996	A
5539822	Lett	Jul 1996	A
5539871	Gibson	Jul 1996	A
5543852	Yuen et al.	Aug 1996	A
5543853	Haskell et al.	Aug 1996	A
5544161	Bigham et al.	Aug 1996	A
5546316	Buckley et al.	Aug 1996	A
5546447	Skarbo et al.	Aug 1996	A
5550576	Klosterman	Aug 1996	A
5550863	Yurt et al.	Aug 1996	A
5552837	Mankovitz	Sep 1996	A
5553123	Chan et al.	Sep 1996	A
5557316	Hoarty et al.	Sep 1996	A
5559548	Davis et al.	Sep 1996	A
5559549	Hendricks et al.	Sep 1996	A
5559550	Mankovitz	Sep 1996	A
5559800	Mousseau et al.	Sep 1996	A
5559870	Patton et al.	Sep 1996	A
5561604	Buckley et al.	Oct 1996	A
5561708	Remillard	Oct 1996	A
5561709	Remillard	Oct 1996	A
5568272	Levine	Oct 1996	A
5570126	Blahut et al.	Oct 1996	A
5572005	Hamilton et al.	Nov 1996	A
5579055	Hamilton et al.	Nov 1996	A
5579057	Banker et al.	Nov 1996	A
5579522	Christeson et al.	Nov 1996	A
5581614	Ng et al.	Dec 1996	A
5583560	Florin et al.	Dec 1996	A
5583576	Perlman et al.	Dec 1996	A
5583965	Douma et al.	Dec 1996	A
5584054	Tyneski et al.	Dec 1996	A
5585838	Lawler et al.	Dec 1996	A
5585865	Amano et al.	Dec 1996	A
5585866	Miller et al.	Dec 1996	A
5587735	Ishida et al.	Dec 1996	A
5588104	Lanier et al.	Dec 1996	A
5588139	Lanier et al.	Dec 1996	A
5589892	Knee et al.	Dec 1996	A
5592529	Linsker	Jan 1997	A
5592551	Lett et al.	Jan 1997	A
5594509	Florin et al.	Jan 1997	A
5596373	White et al.	Jan 1997	A
5598415	Nuber et al.	Jan 1997	A
5598525	Nally et al.	Jan 1997	A
5600364	Hendricks et al.	Feb 1997	A
5600368	Matthews, III	Feb 1997	A
5600378	Wasilewski	Feb 1997	A
5600573	Hendricks et al.	Feb 1997	A
5600711	Yuen	Feb 1997	A
5600775	King et al.	Feb 1997	A
5604528	Edwards et al.	Feb 1997	A
5608447	Farry et al.	Mar 1997	A
5610910	Focsaneanu et al.	Mar 1997	A
5612997	Vallelonga, Sr. et al.	Mar 1997	A
5615252	Sizer, II et al.	Mar 1997	A
5619247	Russo	Apr 1997	A
5619249	Billock et al.	Apr 1997	A
5619269	Lee et al.	Apr 1997	A
5619274	Roop et al.	Apr 1997	A
5619337	Naimpally	Apr 1997	A
5619383	Ngai	Apr 1997	A
5619684	Goodwin et al.	Apr 1997	A
5621456	Florin et al.	Apr 1997	A
5621579	Yuen	Apr 1997	A
5621793	Bednarek et al.	Apr 1997	A
5623308	Civanlar et al.	Apr 1997	A
5625405	DuLac et al.	Apr 1997	A
5625406	Newberry et al.	Apr 1997	A
5628005	Hurvig	May 1997	A
5629733	Youman et al.	May 1997	A
5629978	Blumhardt et al.	May 1997	A
5630103	Smith et al.	May 1997	A
5630119	Aristides et al.	May 1997	A
5633683	Rosengren et al.	May 1997	A
5633810	Mandal et al.	May 1997	A
5635978	Alten et al.	Jun 1997	A
5635989	Rothmuller	Jun 1997	A
5636346	Saxe	Jun 1997	A
5638505	Hemenway et al.	Jun 1997	A
5639350	Aula et al.	Jun 1997	A
5640196	Behrens et al.	Jun 1997	A
5642348	Barzegar et al.	Jun 1997	A
5644354	Thompson et al.	Jul 1997	A
5644628	Schwarzer et al.	Jul 1997	A
5652614	Okabayashi	Jul 1997	A
5652615	Bryant et al.	Jul 1997	A
5652789	Miner et al.	Jul 1997	A
5657072	Aristides et al.	Aug 1997	A
5659350	Hendricks et al.	Aug 1997	A
5659367	Yuen	Aug 1997	A
5661516	Cartes	Aug 1997	A
5663757	Morales	Sep 1997	A
5666487	Goodman et al.	Sep 1997	A
5666645	Thomas et al.	Sep 1997	A
5668599	Cheney et al.	Sep 1997	A
5671267	August et al.	Sep 1997	A
5673089	Yuen et al.	Sep 1997	A
5675390	Schindler et al.	Oct 1997	A
5675575	Wall, Jr. et al.	Oct 1997	A
5682195	Hendricks et al.	Oct 1997	A
5682511	Sposato et al.	Oct 1997	A
5684525	Klosterman	Nov 1997	A
5684918	Abecassis	Nov 1997	A
5687331	Volk et al.	Nov 1997	A
5689501	Takase et al.	Nov 1997	A
5689553	Ahuja et al.	Nov 1997	A
5689555	Sonnenberg	Nov 1997	A
5689663	Williams	Nov 1997	A
5692214	Levine	Nov 1997	A
5694176	Bruette et al.	Dec 1997	A
5696815	Smyk	Dec 1997	A
5696906	Peters et al.	Dec 1997	A
5699107	Lawler et al.	Dec 1997	A
5701383	Russo et al.	Dec 1997	A
5701610	Hsu	Dec 1997	A
5703877	Nuber et al.	Dec 1997	A
5703965	Fu et al.	Dec 1997	A
5706342	Baeder et al.	Jan 1998	A
5708961	Hylton et al.	Jan 1998	A
5710601	Marshall et al.	Jan 1998	A
5710610	Kim	Jan 1998	A
5712907	Wegner et al.	Jan 1998	A
5714273	Wake et al.	Feb 1998	A
5715315	Handelman	Feb 1998	A
5715515	Akins, III et al.	Feb 1998	A
5716273	Yuen	Feb 1998	A
5719646	Kikuchi et al.	Feb 1998	A
5721956	Martin et al.	Feb 1998	A
5724091	Freeman et al.	Mar 1998	A
5724203	Kwoh et al.	Mar 1998	A
5724355	Bruno et al.	Mar 1998	A
5724411	Eisdorfer et al.	Mar 1998	A
5724412	Srinivasan	Mar 1998	A
5724521	Dedrick	Mar 1998	A
5724525	Beyers, II et al.	Mar 1998	A
5724543	Ozden et al.	Mar 1998	A
5724646	Ganek et al.	Mar 1998	A
5727060	Young	Mar 1998	A
5727065	Dillon	Mar 1998	A
5729471	Jain et al.	Mar 1998	A
5729549	Kostreski et al.	Mar 1998	A
5731844	Rauch et al.	Mar 1998	A
5732217	Emura	Mar 1998	A
5734589	Kostreski et al.	Mar 1998	A
5734853	Hendricks et al.	Mar 1998	A
5737333	Civanlar et al.	Apr 1998	A
5737533	de Hond	Apr 1998	A
5737725	Case	Apr 1998	A
5740230	Vaudreuil	Apr 1998	A
5740231	Cohn et al.	Apr 1998	A
5742596	Baratz et al.	Apr 1998	A
5742680	Wilson	Apr 1998	A
5742905	Pepe et al.	Apr 1998	A
5744170	Hall	Apr 1998	A
5745556	Ronen	Apr 1998	A
5745710	Clanton, III et al.	Apr 1998	A
5745882	Bixler et al.	Apr 1998	A
5751282	Girard et al.	May 1998	A
5751706	Land et al.	May 1998	A
5751760	Fuller et al.	May 1998	A
5754775	Adamson et al.	May 1998	A
5754783	Mendelson et al.	May 1998	A
5754938	Herz et al.	May 1998	A
5754940	Smith et al.	May 1998	A
5757416	Birch et al.	May 1998	A
5758257	Herz et al.	May 1998	A
5758259	Lawler	May 1998	A
5764276	Martin et al.	Jun 1998	A
5764739	Patton et al.	Jun 1998	A
5764752	Waite et al.	Jun 1998	A
5768491	Lobodzinski et al.	Jun 1998	A
5768513	Kuthyar et al.	Jun 1998	A
5768539	Metz et al.	Jun 1998	A
5768551	Bleiweiss et al.	Jun 1998	A
5771064	Lett	Jun 1998	A
5774122	Kojima	Jun 1998	A
5774170	Hite et al.	Jun 1998	A
5778173	Apte	Jul 1998	A
5780474	Peglion et al.	Jul 1998	A
5781228	Sposato	Jul 1998	A
5784095	Robbins et al.	Jul 1998	A
5784444	Snyder et al.	Jul 1998	A
5787171	Kubota et al.	Jul 1998	A
5790172	Imanaka	Aug 1998	A
5790198	Roop et al.	Aug 1998	A
5790806	Koperda	Aug 1998	A
5793364	Bolanos et al.	Aug 1998	A
5793410	Rao	Aug 1998	A
5793413	Hylton et al.	Aug 1998	A
5793438	Bedard	Aug 1998	A
5793872	Hirayama et al.	Aug 1998	A
5796394	Wicks et al.	Aug 1998	A
5796424	Ely et al.	Aug 1998	A
5796718	Caterisano	Aug 1998	A
5796952	Davis et al.	Aug 1998	A
5798785	Hendricks et al.	Aug 1998	A
5798795	Glenn et al.	Aug 1998	A
5799157	Escallon	Aug 1998	A
5801747	Bedard	Sep 1998	A
5801753	Eyer et al.	Sep 1998	A
5801787	Schein et al.	Sep 1998	A
5802045	Kos et al.	Sep 1998	A
5802063	Deiss	Sep 1998	A
5802160	Kugell et al.	Sep 1998	A
5802510	Jones	Sep 1998	A
5805155	Allibhoy et al.	Sep 1998	A
5805204	Thompson et al.	Sep 1998	A
5805587	Norris et al.	Sep 1998	A
5805677	Ferry et al.	Sep 1998	A
5805762	Boyce et al.	Sep 1998	A
5805763	Lawler et al.	Sep 1998	A
5806061	Chaudhuri et al.	Sep 1998	A
5808608	Young et al.	Sep 1998	A
5809128	McMullin	Sep 1998	A
5809204	Young et al.	Sep 1998	A
5812123	Rowe et al.	Sep 1998	A
5812205	Milnes et al.	Sep 1998	A
5812754	Lui et al.	Sep 1998	A
5812786	Seazholtz et al.	Sep 1998	A
5815145	Matthews, III	Sep 1998	A
5815196	Alshawi	Sep 1998	A
5815671	Morrison	Sep 1998	A
5818438	Howe et al.	Oct 1998	A
5818439	Nagasaka et al.	Oct 1998	A
5818441	Throckmorton et al.	Oct 1998	A
5818511	Farry et al.	Oct 1998	A
5819301	Rowe et al.	Oct 1998	A
5822123	Davis et al.	Oct 1998	A
5822324	Kostresti et al.	Oct 1998	A
5825829	Borazjani et al.	Oct 1998	A
5825862	Voit et al.	Oct 1998	A
5826110	Ozden et al.	Oct 1998	A
5828420	Marshall et al.	Oct 1998	A
5828945	Klosterman	Oct 1998	A
RE35954	Levine	Nov 1998	E
5829733	Becker	Nov 1998	A
5832221	Jones	Nov 1998	A
5833468	Guy et al.	Nov 1998	A
5835087	Herz et al.	Nov 1998	A
5835792	Wise et al.	Nov 1998	A
5838368	Masunaga et al.	Nov 1998	A
5838383	Chimoto et al.	Nov 1998	A
5838678	Davis et al.	Nov 1998	A
5838873	Blatter et al.	Nov 1998	A
5841433	Chaney	Nov 1998	A
5844600	Kerr	Dec 1998	A
5844620	Coleman et al.	Dec 1998	A
5844890	Delp et al.	Dec 1998	A
5847771	Cloutier et al.	Dec 1998	A
5848396	Gerace	Dec 1998	A
5850218	LaJoie et al.	Dec 1998	A
5850232	Engstrom et al.	Dec 1998	A
5850340	York	Dec 1998	A
5850429	Joyce et al.	Dec 1998	A
5852478	Kwoh	Dec 1998	A
5854840	Cannella, Jr.	Dec 1998	A
5855020	Kirsch	Dec 1998	A
5859660	Perkins et al.	Jan 1999	A
5859895	Pomp et al.	Jan 1999	A
5859902	Freedman	Jan 1999	A
5859949	Yanagihara	Jan 1999	A
5861881	Freeman et al.	Jan 1999	A
5861906	Dunn et al.	Jan 1999	A
5864546	Campanella	Jan 1999	A
5867208	McLaren	Feb 1999	A
5867495	Elliott et al.	Feb 1999	A
5870150	Yuen	Feb 1999	A
5870474	Wasilewski et al.	Feb 1999	A
5870565	Glitho	Feb 1999	A
5877801	Martin et al.	Mar 1999	A
5880768	Lemmons et al.	Mar 1999	A
5880769	Nemirofsky et al.	Mar 1999	A
5883677	Hofmann	Mar 1999	A
5883942	Lim et al.	Mar 1999	A
5887259	Ticker et al.	Mar 1999	A
5890122	Van Kleeck et al.	Mar 1999	A
5892508	Howe et al.	Apr 1999	A
5894328	Negishi	Apr 1999	A
5894504	Alfred et al.	Apr 1999	A
5896444	Perlman et al.	Apr 1999	A
5898668	Shaffer	Apr 1999	A
5898780	Liu et al.	Apr 1999	A
RE36207	Zimmermann et al.	May 1999	E
5903314	Niijima et al.	May 1999	A
5903319	Busko et al.	May 1999	A
5903816	Broadwin et al.	May 1999	A
5907323	Lawler et al.	May 1999	A
5907547	Foladare et al.	May 1999	A
5907598	Mandalia et al.	May 1999	A
5907604	Hsu	May 1999	A
5909638	Allen	Jun 1999	A
5912952	Brendzel	Jun 1999	A
5912962	Bosco	Jun 1999	A
5914757	Dean et al.	Jun 1999	A
5915068	Levine	Jun 1999	A
5916302	Dunn et al.	Jun 1999	A
5917537	Lightfoot et al.	Jun 1999	A
5917553	Honey et al.	Jun 1999	A
5917624	Wagner	Jun 1999	A
5917830	Chen et al.	Jun 1999	A
5917915	Hirose	Jun 1999	A
5920705	Lyon et al.	Jul 1999	A
5923731	McClure	Jul 1999	A
5926230	Niijima et al.	Jul 1999	A
5928335	Morita	Jul 1999	A
5929849	Kikinis	Jul 1999	A
5929932	Otsuki et al.	Jul 1999	A
5930340	Bell	Jul 1999	A
5933141	Smith	Aug 1999	A
5940073	Klosterman et al.	Aug 1999	A
5940738	Rao	Aug 1999	A
5944795	Civanlar	Aug 1999	A
5945987	Dunn	Aug 1999	A
5946381	Danne et al.	Aug 1999	A
5946386	Rogers et al.	Aug 1999	A
5949476	Pocock et al.	Sep 1999	A
5949792	Yasuda et al.	Sep 1999	A
5951639	MacInnis	Sep 1999	A
5953458	Pirson et al.	Sep 1999	A
5956088	Shen et al.	Sep 1999	A
5956716	Kenner et al.	Sep 1999	A
5956717	Kraay et al.	Sep 1999	A
5957695	Redford et al.	Sep 1999	A
5965088	Lever et al.	Oct 1999	A
5966120	Arazi	Oct 1999	A
5966162	Goode et al.	Oct 1999	A
5970072	Gammenthaler, Jr. et al.	Oct 1999	A
5970473	Gerszberg et al.	Oct 1999	A
5978043	Blonstein et al.	Nov 1999	A
5978470	Shaffer et al.	Nov 1999	A
5978855	Metz et al.	Nov 1999	A
5982445	Eyer et al.	Nov 1999	A
5982774	Foladare et al.	Nov 1999	A
5982784	Bell	Nov 1999	A
5983176	Hoffert et al.	Nov 1999	A
5986650	Ellis et al.	Nov 1999	A
5986690	Hendricks	Nov 1999	A
5987100	Fortman et al.	Nov 1999	A
5987245	Gish	Nov 1999	A
5987508	Agraharam et al.	Nov 1999	A
5990927	Hendricks et al.	Nov 1999	A
5990972	Bond-Harris et al.	Nov 1999	A
5991380	Bruno et al.	Nov 1999	A
5991735	Gerace	Nov 1999	A
5991799	Yen et al.	Nov 1999	A
5995095	Ratakonda	Nov 1999	A
5995606	Civanlar et al.	Nov 1999	A
5999173	Ubillos	Dec 1999	A
5999525	Krishnaswamy et al.	Dec 1999	A
5999598	Henrick et al.	Dec 1999	A
5999602	Yang et al.	Dec 1999	A
5999612	Dunn et al.	Dec 1999	A
6002394	Schein et al.	Dec 1999	A
6002444	Marshall et al.	Dec 1999	A
6005561	Hawkins et al.	Dec 1999	A
6005562	Shiga et al.	Dec 1999	A
6005565	Legall et al.	Dec 1999	A
6005601	Ohkura et al.	Dec 1999	A
6005631	Anderson et al.	Dec 1999	A
6005861	Humpleman	Dec 1999	A
6005873	Amit	Dec 1999	A
6006225	Bowman et al.	Dec 1999	A
6006253	Kumar et al.	Dec 1999	A
6006256	Zdepski et al.	Dec 1999	A
6008803	Rowe et al.	Dec 1999	A
6009410	LeMole et al.	Dec 1999	A
6011909	Newlin et al.	Jan 2000	A
6014184	Knee et al.	Jan 2000	A
6014368	Sanami	Jan 2000	A
6014427	Hanson et al.	Jan 2000	A
6016141	Knudson et al.	Jan 2000	A
6016144	Blonstein et al.	Jan 2000	A
6016336	Hanson	Jan 2000	A
6018372	Etheredge	Jan 2000	A
6020915	Bruno et al.	Feb 2000	A
6022223	Taniguchi et al.	Feb 2000	A
6023724	Bhatia et al.	Feb 2000	A
6025637	Mehta	Feb 2000	A
6025837	Matthews, III et al.	Feb 2000	A
6026441	Ronen	Feb 2000	A
6028848	Bhatia et al.	Feb 2000	A
6028867	Rawson et al.	Feb 2000	A
6029045	Picco et al.	Feb 2000	A
6031680	Chainer et al.	Feb 2000	A
6031896	Gardell et al.	Feb 2000	A
6031899	Wu	Feb 2000	A
6031906	Rao	Feb 2000	A
6034677	Noguchi et al.	Mar 2000	A
6038000	Hurst, Jr.	Mar 2000	A
6038233	Hamamoto et al.	Mar 2000	A
6040867	Bando et al.	Mar 2000	A
6044396	Adams	Mar 2000	A
6044403	Gerszberg et al.	Mar 2000	A
6047063	Perry	Apr 2000	A
6049594	Furman et al.	Apr 2000	A
6049831	Gardell et al.	Apr 2000	A
6052444	Ferry et al.	Apr 2000	A
6052594	Chuang et al.	Apr 2000	A
6052717	Reynolds et al.	Apr 2000	A
6052725	McCann et al.	Apr 2000	A
6061097	Satterfield	May 2000	A
6061399	Lyons et al.	May 2000	A
6061434	Corbel	May 2000	A
6061451	Muratani et al.	May 2000	A
6062868	Toriumi	May 2000	A
6064376	Berezowski et al.	May 2000	A
6069879	Chatter	May 2000	A
6075575	Schein et al.	Jun 2000	A
6075796	Katseff et al.	Jun 2000	A
6078886	Dragosh et al.	Jun 2000	A
6084292	Shinohara	Jul 2000	A
6085231	Agraharam et al.	Jul 2000	A
6088368	Rubinstain et al.	Jul 2000	A
6088732	Smith et al.	Jul 2000	A
6094680	Hokanson	Jul 2000	A
6099320	Papadopoulos	Aug 2000	A
6101246	Heinmiller et al.	Aug 2000	A
6101324	Connell et al.	Aug 2000	A
6104391	Johnston, Jr. et al.	Aug 2000	A
6104704	Buhler et al.	Aug 2000	A
6104800	Benson	Aug 2000	A
6108330	Bhatia et al.	Aug 2000	A
6115393	Engel et al.	Sep 2000	A
6118432	Kotorov et al.	Sep 2000	A
6118768	Bhatia et al.	Sep 2000	A
6118778	Amin	Sep 2000	A
6118784	Tsuchiya et al.	Sep 2000	A
6119154	Weaver et al.	Sep 2000	A
6119454	Valisko	Sep 2000	A
6122357	Farris et al.	Sep 2000	A
6125376	Klarlund et al.	Sep 2000	A
6128009	Ohkura et al.	Oct 2000	A
6128304	Gardell et al.	Oct 2000	A
6130898	Kostreski et al.	Oct 2000	A
6131161	Linnartz	Oct 2000	A
6134235	Goldman et al.	Oct 2000	A
6137870	Scherer	Oct 2000	A
6138100	Dutton et al.	Oct 2000	A
6138147	Weaver et al.	Oct 2000	A
6141003	Chor et al.	Oct 2000	A
6141385	Yamaji	Oct 2000	A
6141448	Khansari et al.	Oct 2000	A
6141693	Perlman et al.	Oct 2000	A
6144401	Casement et al.	Nov 2000	A
6144667	Doshi et al.	Nov 2000	A
6144944	Kurtzman, II et al.	Nov 2000	A
6147714	Terasawa et al.	Nov 2000	A
6148067	Leipow	Nov 2000	A
6151059	Schein et al.	Nov 2000	A
6154531	Clapper	Nov 2000	A
6154633	Landgraf et al.	Nov 2000	A
RE36988	Johnson et al.	Dec 2000	E
6157673	Cuccia	Dec 2000	A
6160545	Eyer et al.	Dec 2000	A
6160546	Thompson et al.	Dec 2000	A
6160880	Allen	Dec 2000	A
6163316	Killian	Dec 2000	A
6163345	Noguchi et al.	Dec 2000	A
6163531	Kumar	Dec 2000	A
6166778	Yamamoto et al.	Dec 2000	A
6167043	Frantz	Dec 2000	A
6167188	Young et al.	Dec 2000	A
6169843	Lenihan et al.	Jan 2001	B1
6172674	Etheredge	Jan 2001	B1
6172677	Stautner et al.	Jan 2001	B1
6172687	Kitamura et al.	Jan 2001	B1
6173250	Jong	Jan 2001	B1
6173330	Guo et al.	Jan 2001	B1
6175619	DeSimone	Jan 2001	B1
6177930	Chernock et al.	Jan 2001	B1
6177931	Alexander et al.	Jan 2001	B1
6178446	Gerszberg et al.	Jan 2001	B1
6182028	Karaali et al.	Jan 2001	B1
6182050	Ballard	Jan 2001	B1
6182072	Leak et al.	Jan 2001	B1
6182287	Schneidewend et al.	Jan 2001	B1
6185288	Wong	Feb 2001	B1
6188725	Sugiyama	Feb 2001	B1
6188756	Mashinsky	Feb 2001	B1
6191782	Mori et al.	Feb 2001	B1
6192116	Mayak	Feb 2001	B1
6198478	Ota et al.	Mar 2001	B1
6201536	Hendricks et al.	Mar 2001	B1
6201797	Leuca et al.	Mar 2001	B1
6204885	Kwoh	Mar 2001	B1
6208335	Gordon et al.	Mar 2001	B1
6209028	Walker et al.	Mar 2001	B1
6209129	Carr et al.	Mar 2001	B1
6209130	Rector, Jr. et al.	Mar 2001	B1
6212680	Tsinberg et al.	Apr 2001	B1
6212860	Preisner et al.	Apr 2001	B1
6219839	Sampsell	Apr 2001	B1
6222531	Smith	Apr 2001	B1
6229810	Gerszberg et al.	May 2001	B1
6229887	Albers et al.	May 2001	B1
6230322	Saib et al.	May 2001	B1
6230324	Tomita et al.	May 2001	B1
6233226	Gringeri et al.	May 2001	B1
6233235	Burke et al.	May 2001	B1
6233313	Farris et al.	May 2001	B1
6239794	Yuen et al.	May 2001	B1
6240555	Shoff et al.	May 2001	B1
6243142	Mugura et al.	Jun 2001	B1
6243388	Mussman et al.	Jun 2001	B1
6243445	Begeja et al.	Jun 2001	B1
6243713	Nelson et al.	Jun 2001	B1
6252690	Laine	Jun 2001	B1
6252952	Kung et al.	Jun 2001	B1
6256785	Klappert et al.	Jul 2001	B1
6259487	Bril	Jul 2001	B1
6260192	Rosin et al.	Jul 2001	B1
6262722	Allison et al.	Jul 2001	B1
6262979	Anderson et al.	Jul 2001	B1
6263065	Durinovic-Johri et al.	Jul 2001	B1
6263501	Schein et al.	Jul 2001	B1
6263503	Margulis	Jul 2001	B1
6266340	Pickett et al.	Jul 2001	B1
6266405	Madour et al.	Jul 2001	B1
6268849	Boyer et al.	Jul 2001	B1
6279112	O'Toole, Jr. et al.	Aug 2001	B1
6282713	Kitsukawa et al.	Aug 2001	B1
6285750	Brachman et al.	Sep 2001	B1
6286006	Bharat et al.	Sep 2001	B1
6288738	Dureau et al.	Sep 2001	B1
6288753	DeNicola et al.	Sep 2001	B1
6289025	Pang et al.	Sep 2001	B1
6292553	Fellingham et al.	Sep 2001	B1
6295298	Hrastar et al.	Sep 2001	B1
6298120	Civanlar et al.	Oct 2001	B1
6298482	Seidman et al.	Oct 2001	B1
6300947	Kanevsky	Oct 2001	B1
6304566	Schessel	Oct 2001	B1
6304573	Hicks, III	Oct 2001	B1
6304636	Goldberg et al.	Oct 2001	B1
6305016	Marshall et al.	Oct 2001	B1
6310889	Parsons et al.	Oct 2001	B1
6312336	Handelman et al.	Nov 2001	B1
6317684	Roeseler et al.	Nov 2001	B1
6317884	Eames et al.	Nov 2001	B1
6324279	Kalmanek, Jr. et al.	Nov 2001	B1
6327346	Infosino	Dec 2001	B1
6327574	Kramer et al.	Dec 2001	B1
6331877	Bennington et al.	Dec 2001	B1
6332139	Kaneko et al.	Dec 2001	B1
6333931	LaPier et al.	Dec 2001	B1
6339594	Civanlar et al.	Jan 2002	B1
6343074	Pickett	Jan 2002	B1
6343115	Foladare et al.	Jan 2002	B1
6347075	Barzegar et al.	Feb 2002	B1
6351464	Galvin et al.	Feb 2002	B1
6353611	Norris et al.	Mar 2002	B1
6356546	Beshai	Mar 2002	B1
6357043	Ellis et al.	Mar 2002	B1
6357046	Thompson et al.	Mar 2002	B1
6359881	Gerszberg et al.	Mar 2002	B1
6359910	Takahashi	Mar 2002	B1
6363411	Dugan et al.	Mar 2002	B1
6366578	Johnson	Apr 2002	B1
6370543	Hoffert et al.	Apr 2002	B2
6373817	Kung et al.	Apr 2002	B1
6374124	Slabinski	Apr 2002	B1
6385202	Katseff et al.	May 2002	B1
6385646	Brown et al.	May 2002	B1
6385771	Gordon	May 2002	B1
6388714	Schein et al.	May 2002	B1
6389114	Dowens et al.	May 2002	B1
6389477	Simmon et al.	May 2002	B1
6393014	Daly et al.	May 2002	B1
6393017	Galvin et al.	May 2002	B1
6401242	Eyer et al.	Jun 2002	B1
6404735	Beshai et al.	Jun 2002	B1
6404818	Obikane	Jun 2002	B1
6405371	Oosterhout et al.	Jun 2002	B1
6414970	Negishi et al.	Jul 2002	B1
6415437	Ludvig et al.	Jul 2002	B1
6418139	Akhtar	Jul 2002	B1
6418146	Miloslavsky	Jul 2002	B1
6418433	Chakrabarti et al.	Jul 2002	B1
6421067	Kamen et al.	Jul 2002	B1
6421359	Bennett et al.	Jul 2002	B1
6421425	Bossi et al.	Jul 2002	B1
6424646	Gerszberg et al.	Jul 2002	B1
6425131	Crandall et al.	Jul 2002	B2
6425133	Leary	Jul 2002	B1
6426779	Noguchi et al.	Jul 2002	B1
6437692	Petite et al.	Aug 2002	B1
6438222	Burg	Aug 2002	B1
6438223	Eskafi et al.	Aug 2002	B1
6442266	Wu	Aug 2002	B1
6442755	Lemmons et al.	Aug 2002	B1
6446261	Rosser	Sep 2002	B1
6449654	Blackwell et al.	Sep 2002	B1
6449766	Fleming	Sep 2002	B1
6452923	Gerszberg et al.	Sep 2002	B1
6453471	Klosterman	Sep 2002	B1
6456699	Burg et al.	Sep 2002	B1
6456782	Kubota et al.	Sep 2002	B1
6457010	Eldering et al.	Sep 2002	B1
6459427	Mao et al.	Oct 2002	B1
6459913	Cloutier	Oct 2002	B2
6460018	Kasai et al.	Oct 2002	B1
6460181	Donnelly	Oct 2002	B1
6463468	Buch et al.	Oct 2002	B1
6463585	Hendricks et al.	Oct 2002	B1
6463586	Jerding	Oct 2002	B1
6466970	Lee et al.	Oct 2002	B1
6467090	Brodigan	Oct 2002	B1
6469753	Klosterman et al.	Oct 2002	B1
6470460	Kashiwagi et al.	Oct 2002	B1
6473425	Bellaton et al.	Oct 2002	B1
6473804	Kaiser et al.	Oct 2002	B1
6477705	Yuen et al.	Nov 2002	B1
6480748	Gerszberg et al.	Nov 2002	B1
6481010	Nishikawa et al.	Nov 2002	B2
6481011	Lemmons	Nov 2002	B1
6481012	Gordon et al.	Nov 2002	B1
6486892	Stern	Nov 2002	B1
6487722	Okura et al.	Nov 2002	B1
6490274	Kim	Dec 2002	B1
6490728	Kitazato et al.	Dec 2002	B1
6493324	Truetken	Dec 2002	B1
6493872	Rangan et al.	Dec 2002	B1
6501740	Sun et al.	Dec 2002	B1
6505348	Knowles et al.	Jan 2003	B1
6510152	Gerszberg et al.	Jan 2003	B1
6510555	Tsurumoto	Jan 2003	B1
6515680	Hendricks et al.	Feb 2003	B1
6518986	Mugura	Feb 2003	B1
6519009	Hanaya et al.	Feb 2003	B1
6519246	Strahs	Feb 2003	B1
6519249	Bennefeld et al.	Feb 2003	B1
6522628	Patel	Feb 2003	B1
6526577	Knudson et al.	Feb 2003	B1
6530082	Del Sesto et al.	Mar 2003	B1
6532286	Burg	Mar 2003	B1
6532590	Chimoto	Mar 2003	B1
6539548	Hendricks et al.	Mar 2003	B1
6542500	Gerszberg et al.	Apr 2003	B1
6542518	Miyazawa	Apr 2003	B1
6547829	Meyerzon et al.	Apr 2003	B1
6560222	Pounds et al.	May 2003	B1
6567106	Wugofski	May 2003	B1
6570855	Kung et al.	May 2003	B1
6570974	Gerszberg et al.	May 2003	B1
6573942	Crinon	Jun 2003	B1
6577350	Proehl et al.	Jun 2003	B1
6578201	LaRocca et al.	Jun 2003	B1
6580441	Schileru-Key	Jun 2003	B2
6584125	Katto	Jun 2003	B1
6584153	Gordon et al.	Jun 2003	B1
6588014	Hayashi	Jul 2003	B1
6590867	Ash et al.	Jul 2003	B1
6594271	Wu et al.	Jul 2003	B1
6606746	Zdepski et al.	Aug 2003	B1
6618717	Karadimitriou et al.	Sep 2003	B1
6621870	Gordon et al.	Sep 2003	B1
6625810	Murphy et al.	Sep 2003	B1
6633635	Kung et al.	Oct 2003	B2
6633848	Johnson et al.	Oct 2003	B1
6637029	Maissel et al.	Oct 2003	B1
6638314	Meyerzon et al.	Oct 2003	B1
6640239	Gidwani	Oct 2003	B1
6650901	Schuster et al.	Nov 2003	B1
6651252	Gordon et al.	Nov 2003	B1
6651253	Dudkiewicz et al.	Nov 2003	B2
6671882	Murphy et al.	Dec 2003	B1
6675385	Wang	Jan 2004	B1
6675387	Boucher et al.	Jan 2004	B1
6681395	Nishi	Jan 2004	B1
6687360	Kung et al.	Feb 2004	B2
6690675	Kung et al.	Feb 2004	B1
6694352	Omoigui	Feb 2004	B1
6698020	Zigmond et al.	Feb 2004	B1
6704028	Wugofski	Mar 2004	B2
6704359	Bayrakeri et al.	Mar 2004	B1
6715129	Hind et al.	Mar 2004	B1
6741617	Rosengren et al.	May 2004	B2
6744767	Chiu et al.	Jun 2004	B1
6751612	Schuetze et al.	Jun 2004	B1
6754905	Gordon et al.	Jun 2004	B2
6763522	Kondo et al.	Jul 2004	B1
6771742	McCalmont et al.	Aug 2004	B2
6772150	Whitman et al.	Aug 2004	B1
6775267	Kung et al.	Aug 2004	B1
6782132	Fogg	Aug 2004	B1
6791561	Dawson	Sep 2004	B1
6801575	Crinon	Oct 2004	B1
6807528	Truman et al.	Oct 2004	B1
6826173	Kung et al.	Nov 2004	B1
6828993	Hendricks et al.	Dec 2004	B1
6836476	Dunn et al.	Dec 2004	B1
6839705	Grooters	Jan 2005	B1
6874129	Smith	Mar 2005	B2
6918131	Rautila et al.	Jul 2005	B1
6940950	Dickinson et al.	Sep 2005	B2
6954897	Noguchi et al.	Oct 2005	B1
6968567	Gordon et al.	Nov 2005	B1
6973436	Shkedi	Dec 2005	B1
6986154	Price et al.	Jan 2006	B1
6999476	Lerman et al.	Feb 2006	B2
7006614	Feinberg et al.	Feb 2006	B2
7027564	James	Apr 2006	B2
7042985	Wright	May 2006	B1
7054313	Gerszberg et al.	May 2006	B1
7062777	Alba et al.	Jun 2006	B2
7065709	Ellis et al.	Jun 2006	B2
7075919	Wendt et al.	Jul 2006	B1
7082427	Seibel et al.	Jul 2006	B1
7096484	Mao et al.	Aug 2006	B2
7099443	Phillips et al.	Aug 2006	B2
7100185	Bennington et al.	Aug 2006	B2
7110006	MacInnis et al.	Sep 2006	B2
7110395	Blair	Sep 2006	B1
7117440	Gordon et al.	Oct 2006	B2
7127044	Becker et al.	Oct 2006	B1
7134133	Wugofski	Nov 2006	B1
7137135	Schein et al.	Nov 2006	B2
7143428	Bruck et al.	Nov 2006	B1
7143430	Fingerman et al.	Nov 2006	B1
7149499	Oran et al.	Dec 2006	B1
7150029	Ebling et al.	Dec 2006	B1
7150031	Rodriguez et al.	Dec 2006	B1
7174084	Edmonds et al.	Feb 2007	B2
7177399	Dawson et al.	Feb 2007	B2
7178158	Nishina et al.	Feb 2007	B2
7180988	Phillips et al.	Feb 2007	B2
7181401	Johnson et al.	Feb 2007	B2
7194032	Easwar et al.	Mar 2007	B1
7239698	Phillips et al.	Jul 2007	B2
7257387	Laliberte	Aug 2007	B2
7260186	Zhu et al.	Aug 2007	B2
7315881	Menez	Jan 2008	B2
7343614	Hendricks et al.	Mar 2008	B1
7363645	Hendricks	Apr 2008	B1
7366157	Valentine et al.	Apr 2008	B1
7370342	Ismail et al.	May 2008	B2
7379436	Jiang	May 2008	B2
7379455	Pickett	May 2008	B2
7391761	Ruckart et al.	Jun 2008	B1
7404200	Hailey et al.	Jul 2008	B1
7424439	Fayyad et al.	Sep 2008	B1
7453990	Welenson et al.	Nov 2008	B2
7474742	Cook	Jan 2009	B2
7496360	Sindhwani et al.	Feb 2009	B2
7503003	Kamen et al.	Mar 2009	B2
7505919	Richardson	Mar 2009	B2
7508928	Everson et al.	Mar 2009	B1
7573988	Lee et al.	Aug 2009	B2
7580405	Laliberte	Aug 2009	B2
7586902	Epley	Sep 2009	B2
7685619	Herz	Mar 2010	B1
7746905	Binder	Jun 2010	B2
7793326	McCoskey et al.	Sep 2010	B2
7796738	Wright	Sep 2010	B2
7836467	Gordon et al.	Nov 2010	B2
7838467	Jones et al.	Nov 2010	B2
7843923	Baum	Nov 2010	B2
7843934	Baum et al.	Nov 2010	B2
7940746	Livingood	May 2011	B2
8032906	Gordon et al.	Oct 2011	B2
8060905	Hendricks	Nov 2011	B1
8265587	D'Evelyn et al.	Sep 2012	B2
20010004382	Van Wonterghem	Jun 2001	A1
20010010095	Ellis et al.	Jul 2001	A1
20010012022	Smith	Aug 2001	A1
20010013123	Freeman et al.	Aug 2001	A1
20010025304	Keith	Sep 2001	A1
20010027493	Wallace	Oct 2001	A1
20010027557	Shinkawa et al.	Oct 2001	A1
20010037498	Johansson	Nov 2001	A1
20010039546	Moore et al.	Nov 2001	A1
20010056577	Gordon et al.	Dec 2001	A1
20020007493	Butler et al.	Jan 2002	A1
20020010682	Johnson	Jan 2002	A1
20020012353	Gerszberg et al.	Jan 2002	A1
20020013941	Ward et al.	Jan 2002	A1
20020026496	Boyer et al.	Feb 2002	A1
20020032740	Stern et al.	Mar 2002	A1
20020032907	Daniels	Mar 2002	A1
20020035728	Fries	Mar 2002	A1
20020038308	Cappi	Mar 2002	A1
20020049679	Russell	Apr 2002	A1
20020049971	Augenbraun et al.	Apr 2002	A1
20020056112	Dureau et al.	May 2002	A1
20020056129	Blackketter et al.	May 2002	A1
20020059610	Ellis	May 2002	A1
20020065812	Keith	May 2002	A1
20020065935	Koperda et al.	May 2002	A1
20020066102	Chapman et al.	May 2002	A1
20020066103	Gagnon et al.	May 2002	A1
20020087980	Eldering et al.	Jul 2002	A1
20020099697	Jensen-Grey	Jul 2002	A1
20020100046	Dudkiewicz	Jul 2002	A1
20020120933	Knudson et al.	Aug 2002	A1
20020129062	Luparello	Sep 2002	A1
20020147880	Wang Baldonado	Oct 2002	A1
20030020744	Ellis et al.	Jan 2003	A1
20030033299	Sundaresan	Feb 2003	A1
20030034982	Talayssat et al.	Feb 2003	A1
20030035007	Wugofski	Feb 2003	A1
20030052905	Gordon et al.	Mar 2003	A1
20030056216	Wugofski et al.	Mar 2003	A1
20030066085	Boyer et al.	Apr 2003	A1
20030081377	Lin	May 2003	A1
20030083533	Gerba et al.	May 2003	A1
20030091339	Isozaki	May 2003	A1
20030115603	Lemmons et al.	Jun 2003	A1
20030149988	Ellis et al.	Aug 2003	A1
20030200544	Ellis et al.	Oct 2003	A1
20030204393	Czerwiec et al.	Oct 2003	A1
20030206717	Yogeshwar et al.	Nov 2003	A1
20030209599	Gatto	Nov 2003	A1
20030214939	Eldumiati et al.	Nov 2003	A1
20040001479	Pounds et al.	Jan 2004	A1
20040001501	Delveaux et al.	Jan 2004	A1
20040057425	Brouwer et al.	Mar 2004	A1
20040073597	Caveney et al.	Apr 2004	A1
20040078824	Krisbergh et al.	Apr 2004	A1
20040096110	Yogeshwar et al.	May 2004	A1
20040107439	Hassell et al.	Jun 2004	A1
20040117831	Ellis et al.	Jun 2004	A1
20040125819	Binder	Jul 2004	A1
20040128686	Boyer et al.	Jul 2004	A1
20040140928	Cleghorn	Jul 2004	A1
20040151168	Phillips et al.	Aug 2004	A1
20040151290	Magarasevic et al.	Aug 2004	A1
20040153577	Phillips et al.	Aug 2004	A1
20040176085	Phillips et al.	Sep 2004	A1
20040203896	Deigin et al.	Oct 2004	A1
20040261105	Marshall et al.	Dec 2004	A1
20040261127	Freeman et al.	Dec 2004	A1
20050028208	Ellis et al.	Feb 2005	A1
20050083912	Afshar et al.	Apr 2005	A1
20050138660	Boyer et al.	Jun 2005	A1
20050141431	Caveney et al.	Jun 2005	A1
20050144645	Casey et al.	Jun 2005	A1
20050213565	Barclay et al.	Sep 2005	A1
20050213716	Zhu et al.	Sep 2005	A1
20050235200	Goldberg	Oct 2005	A1
20050235320	Maze et al.	Oct 2005	A1
20050243973	Laliberte	Nov 2005	A1
20050278741	Robarts et al.	Dec 2005	A1
20060056388	Livingood	Mar 2006	A1
20060120517	Moon et al.	Jun 2006	A1
20060188073	Wright	Aug 2006	A1
20060282852	Purpura et al.	Dec 2006	A1
20060293024	Benco et al.	Dec 2006	A1
20070011702	Vaysman	Jan 2007	A1
20070013516	Freitag et al.	Jan 2007	A1
20070089135	Qureshey et al.	Apr 2007	A1
20070092070	Croy et al.	Apr 2007	A1
20070147345	Lowmaster	Jun 2007	A1
20070259645	Laliberte	Nov 2007	A1
20090028153	Koster et al.	Jan 2009	A1
20090274145	Laliberte	Nov 2009	A1
20100029246	Binning	Feb 2010	A1
20110069183	Edwards et al.	Mar 2011	A1
20110116420	Livingood	May 2011	A1
20120013702	Livingood	Jan 2012	A1

Foreign Referenced Citations (149)

Number	Date	Country
2414183	Dec 2001	CA
3423846	Jan 1986	DE
3935294	Apr 1991	DE
4214184	Nov 1992	DE
19755742	Jun 1999	DE
103438	Mar 1984	EP
145063	Jun 1985	EP
149536	Jul 1985	EP
158548	Oct 1985	EP
0158767	Oct 1985	EP
167237	Jan 1986	EP
187961	Jul 1986	EP
243312	Oct 1987	EP
0277014	Aug 1988	EP
0281293	Sep 1988	EP
0299830	Jan 1989	EP
0314572	May 1989	EP
0328440	Aug 1989	EP
0340643	Nov 1989	EP
0355697	Feb 1990	EP
0377334	Jul 1990	EP
0390041	Oct 1990	EP
0396186	Nov 1990	EP
399200	Nov 1990	EP
0402809	Dec 1990	EP
0420123	Apr 1991	EP
0424648	May 1991	EP
425834	May 1991	EP
450841	Oct 1991	EP
0486989	May 1992	EP
0488379	Jun 1992	EP
0506435	Sep 1992	EP
0513553	Nov 1992	EP
513763	Nov 1992	EP
0570785	Nov 1993	EP
0586954	Mar 1994	EP
0620689	Oct 1994	EP
0646856	Apr 1995	EP
0691787	Jan 1996	EP
0702491	Mar 1996	EP
0721253	Jul 1996	EP
0725539	Aug 1996	EP
0734157	Sep 1996	EP
0821522	Jan 1998	EP
0838958	Apr 1998	EP
0835915	Apr 1998	EP
0838798	Apr 1998	EP
0845904	Jun 1998	EP
0892388	Jan 1999	EP
0924629	Jun 1999	EP
0924687	Jun 1999	EP
0961490	Dec 1999	EP
0966164	Dec 1999	EP
0992 922	Apr 2000	EP
1049305	Nov 2000	EP
1133088	Sep 2001	EP
1143728	Oct 2001	EP
1444825	Aug 2004	EP
235095	Jun 1925	GB
2168227	Jun 1986	GB
2177873	Jan 1987	GB
2255214	Oct 1992	GB
2259830	Mar 1993	GB
2269302	Feb 1994	GB
2330429	Apr 1999	GB
2343095	Apr 2000	GB
2344009	May 2000	GB
2353095	Feb 2001	GB
2358938	Aug 2001	GB
60143086	Jul 1985	JP
61-202587	Sep 1986	JP
S64-020454	Jan 1989	JP
1130683	May 1989	JP
1142918	Jun 1989	JP
3029456	Feb 1991	JP
3114375	May 1991	JP
3198119	Aug 1991	JP
4233886	Aug 1992	JP
5250106	Sep 1993	JP
6-134489	May 1994	JP
6224777	Aug 1994	JP
7-235909	Sep 1995	JP
09227193	Sep 1997	JP
9-284571	Oct 1997	JP
2000-013779	Jan 2000	JP
2001-119681	Apr 2001	JP
9828906	Jul 1998	NO
8000209	Feb 1980	WO
8801463	Feb 1988	WO
8909528	Oct 1989	WO
8912370	Dec 1989	WO
9010988	Sep 1990	WO
9100670	Jan 1991	WO
9103112	Mar 1991	WO
9204801	Mar 1992	WO
9210040	Jun 1992	WO
9211713	Jul 1992	WO
9212599	Jul 1992	WO
9217027	Oct 1992	WO
9221206	Nov 1992	WO
9311637	Jun 1993	WO
9322877	Nov 1993	WO
9407327	Mar 1994	WO
9413107	Jun 1994	WO
9414282	Jun 1994	WO
9416527	Jul 1994	WO
9430008	Dec 1994	WO
9515658	Jun 1995	WO
9608109	Mar 1996	WO
9617306	Jun 1996	WO
9625006	Aug 1996	WO
9641473	Dec 1996	WO
9712486	Apr 1997	WO
9713368	Apr 1997	WO
9720274	Jun 1997	WO
9722110	Jun 1997	WO
9722112	Jun 1997	WO
9741688	Nov 1997	WO
9746007	Dec 1997	WO
9802836	Jan 1998	WO
9808344	Feb 1998	WO
9810997	Mar 1998	WO
9818086	Apr 1998	WO
9848566	Oct 1998	WO
9853581	Nov 1998	WO
9853611	Nov 1998	WO
9914947	Mar 1999	WO
9917549	Apr 1999	WO
9918701	Apr 1999	WO
9926415	May 1999	WO
9945491	Sep 1999	WO
9952285	Oct 1999	WO
9966719	Dec 1999	WO
0008855	Feb 2000	WO
0005890	Feb 2000	WO
0005892	Feb 2000	WO
0027122	May 2000	WO
0028733	May 2000	WO
0064164	Oct 2000	WO
0064169	Oct 2000	WO
0079794	Dec 2000	WO
0101689	Jan 2001	WO
0111874	Feb 2001	WO
0118665	Mar 2001	WO
0124083	Apr 2001	WO
0167207	Sep 2001	WO
0167763	Sep 2001	WO
0175649	Oct 2001	WO
0199426	Dec 2001	WO

Non-Patent Literature Citations (49)

Entry
Office Action in Canadian Patent Application No. 2,414,717, dated May 7, 2010.
Brin, Sergey et al., “The Anatomy of a Large Scale Hypertextual Web Search Engine”, Aug. 3, 2001, pp. 1-19.
Chadwick, Henry, et al., “DAVIC-Digital Audio-Visual Council”, TV Anytime and TV anywhere, Dec. 1999, pp. 1-140.
European Office Action dated Jan. 30, 2012 in EP Application No. 02778473.5.
International Preliminary Examination Report in PCT Application No. PCT/US02/32756, dated Feb. 17, 2005.
Notice of Reasons for Rejection dated Jan. 31, 2012 in Japanese Application No. P2009-188618 and English translation hereof.
Office Action in Canadian Patent Application No. 2462159, dated Aug. 2, 2010.
Office Action in Canadian Patent Application No. 2462161, dated Feb. 1, 2011.
Office Action in EP Application No. 02778472.7, dated Feb. 15, 2010.
Office Action in EP Application No. 02784096.6, dated Mar. 26, 2010.
Office Action in JP Application No. P2003-535456, dated Mar. 17, 2009, with translation.
Office Action in JP Application No. P2003-537297, dated Mar. 17, 2009, with translation.
Office Action in JP Application No. P2003-537297, dated Nov. 24, 2009, with translation.
Supplementary EP Search Report in EP Application No. 02 80 0962 dated Jul. 26, 2010.
Supplementary EP Search Report in EP Application No. 02778472, dated Oct. 7, 2005.
Supplementary EP Search Report in EP Application No. 02784096, dated Oct. 13, 2005.
Supplementary Partial EP Search Report in EP Application No. 02778473, dated Oct. 25, 2005.
Written Opinion in PCT Application No. PCT/US02/32756, dated Aug. 13, 2004.
Supplementary European Search Report for EP 02800962 dated Jul. 26. 2010.
Koenen, et al., “MPEG-4: Context and Objectives”, Signal Processing Image Communication 9 (1997), pp. 295-304.
Examiner's Report for Canadian Application No. 2,462,160 dated Jan. 20, 2009.
Pereira, et al., “MGEG-4-Opening New Frontiers to Broadcast Services”, EBU Technical Review, Spring 1999, pp. 28-35.
European Search Report for EP 02776187.3 dated Apr. 11, 2005.
Office Action in Canadian Patent Application No. 2680673, dated Oct. 7, 2010.
Office Action in Canadian patent application No. 2680673. dated May 24. 2011.
Office Action in European Patent Application No. 07007019.8, dated Oct. 21, 2011.
Rule 69 EPC Communication in European Patent Application No. 07016891.9, dated Aug. 9, 2010.
Search Report and Written Opinion in European Patent Application No. 07016891.9-2202, dated Jul. 5, 2010.
Search Report in European Patent Application No. 07007019.8, dated Feb. 11, 2011.
Freier, Alan 0. et al., “The SSL Protocol Version 3.0,” Mar. 1996, pp. 1-52, Netscape.
Kaliski. Burton S .. “A Layman's Guide to a Subset of ASN.1, BER and DER,” Nov. 1, 1993, pp. 1-38, RSA Laboratories.
Malpani, AM Barish et al., “Simple Certificate Validation Protocol (SCVP),” Jul. 2001, pp. 1-23.
PKCS #7: Cryptographic Message Syntax Standard, Nov. 1993, pp. 1-29, RSA Laboratories.
Office Action in European Application No. 07016891.9-2202, dated Apr. 21, 2010.
Extended European Search Report—EP 11007278.2—dated Jan. 8, 2014.
CA Office Action—CA App. 2,462,161—dated Nov. 27, 2014.
Response to Canadian Office Action—CA Application 2,462,161—dated May 26, 2015.
Canadian Office Action—CA Appl. 2,462,161—dated Jul. 16, 2015.
Video and Digital Multimedia Aggregator Remote Content Crawler, U.S. Appl. No. 13/606,670, filed Sep. 7, 2012.
Video and Digital Multimedia Aggregator Content Coding and Formatting, U.S. Appl. No. 14/065,850, filed Oct. 29, 2013.
Method and apparatus for targeting of interactive virtual objects, U.S. Appl. No. 14/729,794, filed Jun. 3, 2015.
Video and Digital Multimedia Aggregator Content Suggestion Engine, U.S. Appl. No. 15/017,103, filed Feb. 5, 2016.
Nov. 18, 2016—European Office Action—EP 02776187.3.
Jul. 13, 2017—European Summons to Oral Proceedings—EP App. 02778472.7.
Jul. 12, 2017—European Office Action—EP 02778473.5.
European Office Action—EP. App 06004531.7—dated Oct. 10, 2016.
Pereira F Et al.: “MPEG-4-Opening New Frontiers to Broadcast Services”, EBU Review—Technical, European Broadcasting Union. Brussels, BE, No. 279, Mar. 21, 1999 (Mar. 21, 1999), pp. 28-35, XP000848408, ISSN: 0251-0936.
Oct. 16, 2017—European Office Action—EP 02776187.3.
Jan. 3, 2018—European Final Rejection—EP 02778472.7.

Related Publications (1)

	Number	Date	Country
	20160203298 A1	Jul 2016	US

Continuations (4)

	Number	Date	Country
Parent	14093807	Dec 2013	US
Child	15077464		US
Parent	13544423	Jul 2012	US
Child	14093807		US
Parent	12856830	Aug 2010	US
Child	13544423		US
Parent	09920723	Aug 2001	US
Child	12856830		US

Video and digital multimedia aggregator

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Disclaimer

Abstract