Video and digital multimedia aggregator content coding and formatting

Abstract
A video and digital multimedia aggregator includes a content decoder, coder (codec) and formatter. The codec formatter receives coding and formatting requests that characterize input source content and desired output target content. Data conveyed about the source and target content may include parameters such as physical and/or logical addresses, coding and compression parameters, format descriptions, content size, description of auxiliary services, and other metadata elements that may be required for coding and formatting.
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.


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 comprises at least two file types. 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.


To ensure the content is delivered to the correct addressee, in a format that is compatible with the addressee's equipment (i.e., hardware and software), the aggregator may include one or more content coders, decoders and formatters. In an embodiment, the coding, decoding and formatting functions may be executed by separate components, which may be embodied as hardware or software, or a combination of hardware and software. In another embodiment, two or more of the functions may be executed by a single device, comprising hardware and/or software.


In an embodiment, the formatting, decoding and coding functions are executed by a coder-decoder (codec) formatter. The codec formatter may comprise means for receiving a coding and formatting request, means for analyzing parameters contained in the coding and formatting request, means for decoding, formatting and coding target content, means for configuring the decoding, formatting and coding means, and means for routing coded target output content to one or more target addresses.


In another embodiment, the codec formatter may include means for processing auxiliary service requests. Such auxiliary service requests may be included in the coding and formatting request, or may be separately supplied. The auxiliary services may include closed captioning, descriptive video narration, alternative language audio, content rating, critical review information, device control and commands, future content schedules, advertising, targeted advertising, text and data services, interactive services, and content metadata. The means for processing auxiliary services includes means for analyzing the auxiliary service requests, means for configuring one or more auxiliary services processing means to supply the requested auxiliary services, and means for outputting the requested auxiliary services. The outputted auxiliary services may be combined with the coded target output content.





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 content acquisition server and components with which the content acquisition server interacts as part of a content search, packaging, and delivery system;



FIG. 6 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. 7 is a schematic of subsystems of a codec and content formatter and components with which the codec and content formatter interacts as part of the content search, packaging, and delivery system;



FIG. 8 is a diagram of components of a formatting codec used with the codec and content formatter of FIG. 7;



FIG. 9 shows a flowchart describing a process of decoding, formatting, and coding source content and outputting target content; and



FIG. 10 shows a flowchart describing a method of processing auxiliary services that may accompany source and/or target content.





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 within the aggregator 201. Certain fields including, but not limited to, account numbers and billing info nation 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 may route billing information from a customer billing server 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.


The content acquisition server 400, as shown in detail in FIG. 5 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 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 may be 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. 6. The content acquisition server 400 is described in more detail in co-pending patent application entitled “Video and Digital Multimedia Aggregator,” filed on Aug. 3, 2001, which is incorporated by reference.


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 file 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.


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 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 acquisition server 400 determines that the content does not meet the format requirements for local storage, the content stream and/or contents are routed to the decoder and content formatter 252 (see FIG. 4). The decoder and content formatter 252 decodes the incoming data and may extract digital and/or analog data representing the content and any metadata associated with the content. The decoder and content formatter 252 then reformats the content into the required formats and coding schemes for local storage. The properly formatted programming content may then be stored to the aggregator local storage 254.


Returning to FIG. 5, the remote content download processor 402 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 does not meet the format criteria, the content stream and/or contents are routed to the decoder and content formatter 252 along with the required formatting and coding parameters. 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.


If the programming download request is to be fulfilled by the local aggregator 201, the local content request processor 451 of the content delivery server 450 (see FIG. 6) 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 format and coding scheme is not correct, the local content request processor 451 retrieves the programming content from the aggregator local storage 254 or the appropriate local streaming sources 262 and routes the programming to the coder and content formatter 253 along with the required formatting and coding parameters. The coder and content formatter 253 then decodes the incoming data and may extract digital and/or analog data representing the content and its metadata. The coder and content formatter 253 then reformats the content into the required formats and coding schemes for delivery to the user. The correctly coded and formatted programming content file(s) and/or streams, whether directly from local sources or from the coder and content formatter 253, and routes this content to the content delivery server 450.


The coder and content formatter 253 may employ 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. For television and video content, 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 or a combination of two or more techniques. The coder and content formatter 253 of the content search, packaging, and delivery system 200 will be able to use any one or combination of two or more 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 and/or digital coding 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, the HDTV format 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.


The decoder and content formatter 252 and the coder and content formatter 253 may be similar or identical in functionality, software configuration, and/or hardware configuration. In an embodiment, the decoder and content formatter 252 and the coder and content formatter 253 may be embodied by a single subsystem represented by a codec and content formatter 270, which is shown in detail in FIG. 7. In an alternate embodiment, the decoder and content formatter 252 and the coder and content formatter 253 may each comprise one or more separate codec and content formatters 270. The codec and content formatter 270 includes a codec and content formatter processor 271 that may communicate with and control other components of the codec and content formatter 270. In particular, the formatter processor 271 communicates with one or more content routers 272, one or more formatting codecs 274, and one or more auxiliary services processors 276. The formatter processor 271 communicates with one or more content routers 272 in order to transmit routing connection parameters and paths for the transfer of content data between various source and target subsystems. The formatter processor 271 communicates with one or more formatting codecs 274 to identify and manage available codec processing resources, configure codec hardware and/or software parameters for decoding, formatting, and coding operations, and to transmit routing information and coding and formatting parameters necessary for the formatting codecs 274 to decode, format, and code content from various sources. The formatter processor 271 also communicates with one or more auxiliary services processors 276 to allocate resources and transmit parameters associated with requests for auxiliary services processing. Auxiliary services may include closed captioning, descriptive video services, advertising, interactive services, and other data services. The formatter processor 271 may also communicate with other components of the content search, packaging, and delivery system 200 including the content delivery server 450, the content acquisition server 400, the aggregator local storage 254, and the local streaming sources 262 (see FIG. 4). Communications with these other systems includes receiving coding and formatting requests, transmitting content routing data, and managing content flow between various content sources and one or more components of the codec and content formatter 270.


When the remote content download processor 402 within the content acquisition server 400 and/or the content delivery processor 453 within the content delivery server 450 determine that a particular content entity needs to be decoded, formatted, reformatted, and/or coded, the respective processors (402, 453) transmit a coding and formatting request to the codec and content formatter 270. Coding and formatting requests convey data to the codec and content formatter 270 characterizing the input source content and the desired output target content. Data conveyed about the source and target content may include parameters such as physical and/or logical addresses, coding and compression parameters, format descriptions, content sizes and/or lengths, description or location of auxiliary services combined with the source content, description or location of auxiliary services to be combined with the target content, and other metadata elements that may be required for coding, formatting, and routing. The codec and content formatter 270 may then use these parameters to identify available resources, establish content routing paths, configure formatting codecs 274, configure auxiliary services processors 276, and perform the required coding and formatting operations to fulfill the coding and formatting request. In an embodiment, a coding and formatting request may identify one or more target content coding and formatting schemes, as in the case where one type of formatting may be applied to the target content for storage and another type of formatting may be applied to the target content for delivery to system users, which may require the codec and content formatter 270 to configure and control one or more of the formatting codecs 274 and auxiliary services processors 276.


The codec and content formatter 270 may use one or more of the content routers 272 to dynamically establish logical and/or physical circuit connections for transmission of content data between the various subsystems shown in FIG. 7. A content router 272 may comprise one or more hardware systems and one or more software modules that may operate under the direction of the formatter processor 271 to establish and manage the interconnections between subsystems required to transfer content in support of one or more coding and formatting operations. In FIG. 7, several of the interconnections between subsystems are shown as two connection lines and a series of dots between the two lines. This convention is used to indicate that at any time there may exist one or more connections or circuits between one or more of the connected subsystems and that between two connected subsystems the number of connections may vary. Each collection of connections or circuits may comprise one or more logical and/or one or more physical connections between software and/or hardware modules. Physical routing configurations, such as may be required for the transfer of analog content, may be achieved using one or more industry standard and/or custom components such as circuit switching devices, matrix switches, distribution amplifiers, signal splitters, input and output ports, and patch bays. Logical routing, such as may be required for the transfer of digital content, may be achieved using one or more digital packet transport protocols that may operate on one or more local area networks supported by the system administrator 500 as part of the content search, packaging, and delivery system 200. In an embodiment, the functionality of the content routers 272 may be implemented by one or more subsystems and may be functionally and/or physically external to the codec and content formatter 270 and may be a subsystem (not shown in FIG. 4) of the aggregator 201. In another embodiment, the functionality of the content routers 272 may be implemented by one or more subsystems and may be functionally and/or physically external to the aggregator 201 so that the aggregator 201 and its subsystems may connect to the content routers 272, or equivalent systems, through external interfaces (not shown in FIG. 4). The number of connections and the logical and physical routing paths of such connections both within the codec and file formatter 270 and external to the codec and file formatter 270 may be changed as required to accommodate a smaller or larger number of content pathways and to accommodate various source and destination combinations required at any given time. These pathways may be created or modified on a demand basis by the formatter processor 271 and may be modified prior to a coding and formatting operation and/or during a coding and formatting operation as may be required.


Content that is stored locally by the system 200 and/or acquired remotely may exist in one or more of numerous standardized and/or proprietary formats with various coding and compression schemes applied and may need to be decoded, reformatted, and/or recoded to satisfy local storage requirements and requirements of delivery to one or more system users. The content decoding, formatting, and/or coding functions may be performed by one or more of the formatting codecs 274 as shown in FIG. 7. Decoding of a content file or stream may comprise several processing operations that may include performing a packet or frame alignment, reading and caching content metadata, reading embedded time code information, reading and caching auxiliary services data, and recovering and caching content payload data in digital form and/or analog baseband form. Formatting or reformatting of content payload data may comprise several processing operations that may include analog-to-digital conversion, digital-to-analog conversion, packetizing or framing digital data representing content into one or more standard and/or proprietary formats, translating digital data representing content from one or more standard and/or proprietary formats into one or more other standard and/or proprietary formats, modifications to existing auxiliary services that may be packaged with the content, addition of auxiliary services such as closed captioning and/or advertising, frame rate translation of video content, video aspect ratio format conversion (e.g., 4×3 television or 16×9 movies), and any required audio and/or video processing. Coding of a content file or stream may comprise several processing operations that may include applying varying levels of compression and various schemes of error correction coding to one or more content files and/or signals.


The codec and content formatter 270 may contain one or more banks of one or more formatting codecs 274 that may comprise one or more separate software and/or hardware modules. The hardware and/or software modules may exist as a flexible group of resources that may be accessed on a demand basis and may be dynamically assigned and configured to accommodate virtually any content decoding, formatting, and coding operation. When the formatter processor 271 receives a coding and formatting task request from the content acquisition server 400 or the content delivery server 450, the formatter processor 271 may poll the group of formatting codec 274 resources, identify available resources required for the requested task, configure those resources to perform the requested task thereby configuring a formatting codec 274, and transmit the required decoding, formatting, and coding parameters as well as routing information to the newly configured formatting codec 274. In an embodiment, the formatter processor 271 may configure and activate one or more available hardware and/or software modules by downloading appropriate software modules to perform particular decoding, formatting, and coding tasks as required by a user content download request or other content acquisition task. The ability of the formatting codecs 274 to be software configurable may allow a high degree of configuration flexibility as well as the ability to accommodate coding and formatting schemes yet to be developed.


An example of a formatting codec 274 configuration is shown in detail in FIG. 8. The formatting codec 274 includes a master codec processing module 315 that is coupled to one or more other processing modules and that may manage the configuration and operation of one or more other processing modules within the formatting codec 274. In an embodiment, the processing modules within the formatting codec 274 may be interconnected using a bus topology that may allow dynamic interconnectivity between up to all of the processing modules and may support logical addressing of modules for communications routing. The master codec processing module 315 may be coupled to a memory management module 319 and a codec memory module 320. The memory management module 319 may dynamically assign and manage resources within the codec memory 320 for use by one or more other processing modules within the formatting codec 274.


The master codec processing module 315 is coupled to a content decoding module 316 that may manage the configuration and operation of one or more processing modules in order to perform content decoding operations. Coupled to the content decoding module 316 is a frame alignment module 321 that may use decoding parameters received from the formatter processor 271 to synchronize and align the formatting codec 274 with the incoming content data packets and/or frames. Also coupled to the content decoding module 316 is a metadata collection module 322 that may read any metadata information contained in one or more content files and content transport streams and may temporarily store this data in the codec memory 320. A time code processing module 323 is also coupled to the content decoding module 316 and may extract any time code data that may be embedded in one or more content files and/or content transport streams and may store and/or process the time code as required to support coding and formatting operations. The content decoding module 316 is further coupled to a format translation module 324, which may perform the actual translation of the incoming source content data to the desired output target content format. An example of format translation may involve reading a source video file in a proprietary digital format and translating the content data into a standardized format. The content decoding module 316 is also coupled to an auxiliary services divider module 328 and an auxiliary services routing module 329. The auxiliary services divider module 328 may read any auxiliary services that may be a part of the source content files and/or transport stream and may separate, or parse, these data services from the content data and metadata. The auxiliary services routing module 329 may then route the auxiliary services data to one or more of the codec memory 320 and/or auxiliary services processors 276.


The master codec processing module 315 is coupled to a content formatting module 317 that may perform content formatting operations and/or manage the configuration and operation of one or more processing modules in order to perform content formatting operations. Coupled to the content formatting module 317 is a format translation module 324 that may perform translation of incoming source content data into desired output target content format. Processing steps to accomplish content formatting and format translation may be optimized to minimize degradation of the content data and/or signal. The content formatting module 317 is also coupled to a digital-to-analog and analog-to-digital conversion module 325 that may perform any required conversion of audio and video content between analog and digital formats to support source content that may exist in various digital and/or analog formats and may be delivered to system users in various digital and/or analog formats. The content formatting module 317 is also coupled to an auxiliary services combiner module 330, which may combine and/or recombine any previously existing and/or newly established auxiliary services with the target content files and/or transport stream. The auxiliary services combiner 330 is in turn coupled to the auxiliary services routing module 329 in order to receive appropriate auxiliary services data. The content formatting module 317 is further coupled to an audio/video processing module 331 that may perform various processing functions on the audio and video signals of the source content to meet target content requirements. The audio/video processing functions may include adjusting audio levels, combining and/or splitting audio signals, and adjusting video luminance and chrominance.


The master codec processing module 315 may also be coupled to a content coding module 318 that may perform content coding operations and/or manage the configuration and operation of one or more processing modules in order to perform content coding operations. Coupled to the content coding module 318 is a digital compression module 326 that, as required, may apply various digital compression schemes to the target content that was not previously digitally compressed during content formatting and or translation. Different levels of digital compression may be applied to one or more target content files and/or transport streams. The different compression levels may be based on requirements such as those regarding content delivery quality and available content delivery bandwidth and/or storage capacities. An error correction coding module 327 is also coupled to the content coding module 318 and may apply one or more of various digital forward error correction coding schemes to one or more of the target content files and/or transport streams to reduce digital errors during content delivery and allow correction of data containing a certain level of errors.


The codec and content formatter 270 may contain one or more banks of auxiliary services processors 276. The auxiliary services processors may comprise one or more separate software and/or hardware modules. The auxiliary services processors 276 may process and/or generate auxiliary services to be included with target content. Such auxiliary services may include closed captioning services, descriptive video services, advertising, interactive services, and other data services. The hardware and/or software modules may exist as a flexible group of resources that may be accessed on a demand basis and that may be dynamically assigned and configured to accommodate various auxiliary services processing operations. When the codec and content formatter processor 271 receives a coding and formatting request that includes auxiliary services processing requests from the content acquisition server 400 or the content delivery server 450, the formatter processor 271 may analyze the auxiliary processing parameters contained in the coding and formatting request. The analyzed parameters are then used to determine the required configuration of one or more auxiliary services processors 276 necessary to perform the requested operations. The formatter processor 271 may then poll the group of auxiliary services processing resources, identify the available resources required for the requested task, configure those resources to perform the requested task, and transmit the required auxiliary services parameters as well as routing information to the auxiliary services processor 276. In an embodiment, the formatter processor 271 may configure and activate one or more available hardware and/or software modules by downloading appropriate software modules to perform particular auxiliary services processing tasks as required by a user content download request or other content acquisition task. The ability of the formatting codecs 274 to be software configurable allows a high degree of configuration flexibility as well as the ability to accommodate auxiliary services yet to be developed.


Auxiliary services may accompany both analog and digital content deliveries and may be embedded in one or more content files and/or transport streams. Auxiliary services accompanying video programming content may include closed captioning services for users with hearing impairments, descriptive video services for system users with visual impairments, alternative language audio service, v-chip program rating information, critical review information, device control parameters and commands, future programming schedules, advertising, advertising insert tags, other text and data services, and interactive services data such as browser pages, menus, icons, and links. Auxiliary services accompanying audio programming content may include extended metadata such as graphics files, in-depth data about the producers of the content, critical reviews, future programming schedules, device control parameters and commands, advertising, advertising insert tags, other text and data services, and interactive services data such as browser pages, menus, icons, and links. Auxiliary services processed by the formatter 270 may be pre-existing services recovered from source content and routed from one or more formatting codecs 274 to one or more auxiliary services processors 276 and/or newly established services transferred from one or more other content search, packaging, and delivery system 200 resources through the codec and content formatter processor 271 to one or more auxiliary services processors 276. In an embodiment, one or more auxiliary services processors 276 may comprise an audio closed captioning processor that may receive audio and time code data for a particular video content entity from a formatting codec 274, perform speech-recognition and other processing on the audio data, and output one or more files and/or transport streams that contain time-code-synchronized closed captioning text and data to be combined with the target content as an auxiliary service.



FIG. 9 shows an overview of the content formatting and coding process 360 performed by the codec and content formatter 270. The codec and content formatter processor 271 (see FIG. 8) first receives a coding and formatting request from the content acquisition server 400 and/or the content delivery server 450, routine 361. The formatter processor 271 then uses routine 363 to analyze the coding and formatting request parameters contained in the coding and formatting request in order to determine the required configuration of one or more formatting codecs 274 necessary to perform the requested operations. The formatter processor 271 may then poll formatting and coding resources, routine 365, and identify available formatting codec hardware and/or software modules necessary to realize the required configuration. Routine 367 may then configure one or more formatting codecs 274 using the coding and formatting request parameters and required configuration data to access and configure one or more formatting codec 274 hardware and/or software modules. The formatter processor 271 may then use source content and target content routing address information from a decoding and formatting request to configure one or more content routers 272, routine 369. Routine 371 may then initiate and manage the transfer of source content through one or more content routers 272 from one or more source locations to one or more formatting codecs 274. Source locations may include the content acquisition server 400, the content delivery server 450, aggregator local storage 254, and local streaming sources 262. One or more formatting codecs 274 may then execute routine 373, which may make use of the hardware and/or software modules shown in detail in FIG. 8 to perform the requested decoding, formatting, and coding operations to produce the target output content. Routine 374 may then perform processing of auxiliary services as outlined in the content coding and formatting request. Auxiliary services processing starts at the formatting codec 274, which parses existing auxiliary services from the source content and routes those services to one or more auxiliary services processors 276, which perform appropriate processing on existing auxiliary services as well as establish new auxiliary services as required. The auxiliary services processors 276 may then route the appropriate auxiliary services to one or more formatting codecs 274 for combination with one or more target output content files and/or data transport streams.


Once the one or more target content files and/or transports streams have been assembled, routine 375 within the formatter processor 271 transfers the formatted target content through one or more content routers 272 to one or more target addresses residing in one or more components external to the codec and content formatter 270 which may include the content acquisition server 400, the content delivery server 450, aggregator local storage 254, and/or local streaming sources 262. The formatter processor 271 may then clear content routing connections using routine 377. Content routing connections to be cleared may include one or more physical routing connections and/or one or more logical routing connections. Physical routing connections may be cleared by returning routing circuitry to an idle or standby state and logical routing connections may be cleared by removing logical address information from appropriate memory registers within one or more content routers 272. The formatter processor 271 may then return one or more configured formatting codecs 274 and/or auxiliary services processors 276 to a standby and/or default state, routine 379, and return the one or more formatting codec 274 and or auxiliary services processor 276 hardware and/or software modules to the available pools of formatting resources and/or auxiliary services processing resources, respectively. Routine 381 within the formatter processor 271 may then log appropriate administrative data with the content acquisition server 400 and/or the content delivery server 450. Routine 383 may then stop processing.



FIG. 10 shows the auxiliary services processing of routine 374 in more detail. If existing auxiliary services and/or newly established auxiliary services are to be combined with target output content, then routine 385 within one or more of the formatter processor 271 and/or formatting codecs 274 analyzes any auxiliary services processing request parameters that may be part of the coding and formatting request and determines the necessary configuration of one or more auxiliary services processors 276. Routine 387 within the formatter processor 271 may then poll available auxiliary processing resources and configure one or more auxiliary services processors 276 required to perform the requested processing operations. One or more formatting codecs 274 may parse, or separate, existing auxiliary services and time code data that may be combined with one or more source content files and/or transport streams, routine 389. Routine 391 may then transfer these auxiliary services as well as the source content time code data to one or more auxiliary services processors 276. Routine 391 may also transfer data from sources external to the codec and content formatter 270 that may be required to establish new auxiliary services to be combined with the target output content. These external sources may include the content acquisition server 400, the content delivery server 450, and the aggregator local storage 254. One or more auxiliary services processors 276 may then perform one or more processing and formatting operations on one or more sources of auxiliary services data in accordance with processing request parameters in order to output one or more target auxiliary services to be combined with target output content, routine 393. Routine 395, which may reside within the formatter processor 271 and/or one or more auxiliary services processors 276, may then transmit these output auxiliary services to one or more formatting codecs 274. Routine 397 may then be executed by one or more formatting codecs 274 to combine the auxiliary services with one or more target output content files and/or data streams. Processing is then continued with routine 375 as shown in FIG. 9 and as described above.

Claims
  • 1. A method comprising: receiving content combined with data of at least one auxiliary service, the content received being in a first format;receiving, at a computing device, a request for the content, wherein the request includes an identification of a second format in which the content is requested and an identification of the at least one auxiliary service,separating the data of the at least one auxiliary service from the content in the first format;coding the content from the first format into the second format;combining the data of the at least one auxiliary service with the content in the second format; andoutputting, responsive to the request, the content in the second format combined with the data of the at least one auxiliary service.
  • 2. The method of claim 1, further comprising combining the data of the at least one auxiliary service and the content in the second format into a single file.
  • 3. The method of claim 1, further comprising: parsing time code data from the content in the first format; andsynchronizing the data of the at least one auxiliary service with the content in the second format using the time code data.
  • 4. The method of claim 1, wherein the second format employs a different level of data compression from the first format.
  • 5. The method of claim 1, wherein the data of the at least one auxiliary service comprises one or more of: closed captioning, descriptive video narration, alternative language audio, content rating, critical review information, device control, a future content schedule, untargeted advertising, targeted advertising, a text service, a data service, an interactive service, and content metadata.
  • 6. The method of claim 1, wherein the content in the first format is received combined with data of a plurality of auxiliary services including the data of the at least one auxiliary service, the method further comprising: separating the data of the plurality of auxiliary services from the content in the first format.
  • 7. The method of claim 1, wherein the request is received from a user terminal.
  • 8. The method of claim 1, further comprising: polling resources capable of coding the content into the second format from the first format;identifying one or more available resources based on the polling; andutilizing at least one of the one or more available resources to code the content from the first format into the second format.
  • 9. The method of claim 1, further comprising combining the data of the at least one auxiliary service and the content in the second format into a single transport stream.
  • 10. A system comprising: one or more processors configured with software that when executed by the one or more processors causes the system to:receive content combined with data of at least one auxiliary service, the content received being in a first format;receive a request for the content, wherein the request includes an identification of a second format;separate the data of the at least one auxiliary service from the content in the first format;code the content from the first format into the second format;combine the data of the at least one auxiliary service with the content in the second format; andoutput, responsive to the request, the content in the second format combined with the data of the at least one auxiliary service.
  • 11. The system of claim 10, wherein the software, when executed by the one or more processors, causes the system to: combine the data of the at least one auxiliary service and the content in the second format into a single file.
  • 12. The system of claim 10, wherein the content in the first format is received combined with data of a plurality of auxiliary services including the data of the at least one auxiliary service, and wherein the software, when executed by the one or more processors, causes the system to: separate the data of the plurality of auxiliary services from the content in the first format.
  • 13. The system of claim 10, wherein the data of the at least one auxiliary service comprises one or more of closed captioning, descriptive video narration, alternative language audio, content rating, critical review information, device control, a future content schedule, untargeted advertising, targeted advertising, a text service, a data service, an interactive service, and content metadata.
  • 14. The system of claim 10, wherein the software, when executed by the one or more processors, causes the system to: poll resources capable of coding the content from the first format into the second format;identify one or more available resources based on the polling; andutilize at least one of the one or more available resources to code the content from the first format into the second format.
  • 15. The system of claim 10, wherein the software, when executed by the one or more processors, causes the system to: combine the data of the at least one auxiliary service and the content in the second format into a single transport stream.
  • 16. The system of claim 10, wherein the software, when executed by the one or more processors, causes the system to: parse time code data from the content in the first format; andsynchronize the data of the at least one auxiliary service with the content in the second format using the time code data.
  • 17. The system of claim 10, wherein the second format is identified in the request by a set of parameters, which includes a parameter indicating a level of data compression.
  • 18. A system comprising: a plurality of user terminals; andan apparatus comprising one or more processors configured with software, that when executed by the one or more processors, causes the apparatus to: receive content combined with data of at least one auxiliary service, the content received being in a first format;receive, from a first user terminal of the plurality of user terminals, a request for content, the request including an identification of a second format; andresponsive to the request: separate the data of the at least one auxiliary service from the content in the first format,code the content from the first format into the second format, andoutput the content in the second format combined with the data of the at least one auxiliary service.
  • 19. The system of claim 18, wherein the plurality of user terminals comprises at least one of a set top terminal and a personal computer terminal.
  • 20. The system of claim 18, further comprising: a second apparatus comprising one or more second processors configured with second software, that when executed by the one or more second processors, causes the second apparatus to provide, to the apparatus, at least one of the content in the first format and a reference to the content stored in the first format at a location remote from the apparatus.
RELATED APPLICATIONS

This application is a continuation of patent application Ser. No. 09/973,067, entitled “Video And Digital Multimedia Aggregator Content Coding And Formatting,” filed on Oct. 10, 2001, which is a continuation-in-part of patent application Ser. No. 09/920,723, entitled “Video and Digital Multimedia Aggregator,” filed on Aug. 3, 2001 and patent application Ser. No. 09/920,615, entitled “Video and Digital Multimedia Aggregator Remote Content Crawler,” filed on Aug. 3, 2001. These patent applications are hereby incorporated by reference. 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;” and patent application entitled “Video and Digital Multimedia Aggregator;” and patent application entitled “Video and Digital Multimedia Aggregator Remote Content Crawler,” filed on date herein.

US Referenced Citations (495)
Number Name Date Kind
3639686 Walker et al. Feb 1972 A
3733430 Thompson et al. May 1973 A
3993955 Belcher et al. Nov 1976 A
4197590 Sukonick et al. Apr 1980 A
4225884 Block et al. Sep 1980 A
4264924 Freeman Apr 1981 A
4264964 Berger Apr 1981 A
4279035 Skerlos Jul 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
4450481 Dickinson May 1984 A
4451701 Bendig May 1984 A
4455548 Burnett Jun 1984 A
4455570 Saeki et al. Jun 1984 A
4484217 Block et al. Nov 1984 A
4484218 Boland et al. Nov 1984 A
4488179 Krüger et al. Dec 1984 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
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
4573072 Freeman Feb 1986 A
4581484 Bendig Apr 1986 A
4587520 Astle May 1986 A
4602278 Pritchard et al. Jul 1986 A
4602279 Freeman Jul 1986 A
4605964 Chard Aug 1986 A
4621282 Ahern Nov 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
4724491 Lambert Feb 1988 A
4739510 Jeffers et al. Apr 1988 A
4740834 Mobarry Apr 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
4792972 Cook, Jr. Dec 1988 A
4797568 Gumbs Jan 1989 A
4797918 Lee 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
4860379 Schoeneberger Aug 1989 A
4876736 Kiewit Oct 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
4907082 Richards Mar 1990 A
4918516 Freeman Apr 1990 A
4920432 Eggers et al. Apr 1990 A
4924303 Brandon et al. 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
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
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
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
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
5036394 Morii et al. Jul 1991 A
5036537 Jeffers et al. Jul 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
5057917 Shalkauser et al. Oct 1991 A
5066319 Lippold Nov 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
5115309 Hang May 1992 A
5115426 Spanke May 1992 A
5121205 Ng et al. Jun 1992 A
5124980 Maki Jun 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
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
5155591 Wachob 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
5187735 Herrero Garcia et al. Feb 1993 A
5192999 Graczyk et al. Mar 1993 A
5195022 Hoppal 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
5212553 Maruoka May 1993 A
5216515 Steele et al. Jun 1993 A
5221962 Backus et al. Jun 1993 A
5223924 Strubbe Jun 1993 A
5229852 Maietta et al. Jul 1993 A
5231494 Wachob Jul 1993 A
5231516 Kamon 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
5241428 Goldwasser et al. Aug 1993 A
5241659 Parulski et al. Aug 1993 A
5247347 Litteral et al. Sep 1993 A
5247575 Sprague et al. Sep 1993 A
5251324 McMullan, Jr. Oct 1993 A
5253066 Vogel Oct 1993 A
5253275 Yurt 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
5270809 Gammie Dec 1993 A
5282028 Johnson et al. Jan 1994 A
5283561 Lumelsky et al. Feb 1994 A
5283639 Esch et al. Feb 1994 A
5285272 Bradley et al. Feb 1994 A
5289271 Watson Feb 1994 A
5289288 Silverman et al. Feb 1994 A
5293540 Trani et al. Mar 1994 A
5293633 Robbins Mar 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 May 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
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
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
5361091 Hoarty et al. Nov 1994 A
5365265 Shibata et al. Nov 1994 A
5367330 Haave et al. Nov 1994 A
5367571 Bowen et al. Nov 1994 A
5374951 Welsh Dec 1994 A
5375068 Palmer et al. Dec 1994 A
5381477 Beyers, II 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
5396546 Remillard Mar 1995 A
5398074 Duffield et al. Mar 1995 A
5400401 Wasilewski et al. Mar 1995 A
5404393 Remillard Apr 1995 A
5404505 Levinson Apr 1995 A
5408258 Kolessar Apr 1995 A
5410326 Goldstein Apr 1995 A
5410344 Graves et al. Apr 1995 A
5412416 Nemirofsky May 1995 A
5412720 Hoarty May 1995 A
5414426 O'Donnell et al. May 1995 A
5416508 Sakuma et al. May 1995 A
5421031 De Bey May 1995 A
5424770 Schmelzer et al. Jun 1995 A
5426699 Wunderlich et al. Jun 1995 A
5432542 Thibadeau et al. Jul 1995 A
5432561 Strubbe Jul 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
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
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
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
5485197 Hoarty Jan 1996 A
5488409 Yuen et al. Jan 1996 A
5490247 Tung et al. Feb 1996 A
5493568 Sampat 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
5508733 Kassatly Apr 1996 A
5512934 Kochanski Apr 1996 A
5515098 Carles May 1996 A
5517502 Bestler et al. May 1996 A
5526034 Hoarty et al. Jun 1996 A
5528281 Grady et al. Jun 1996 A
5537141 Harper et al. Jul 1996 A
5537153 Shigihara Jul 1996 A
5539449 Blahut et al. Jul 1996 A
5539871 Gibson Jul 1996 A
5550863 Yurt Aug 1996 A
5557316 Hoarty et al. Sep 1996 A
5559549 Hendricks et al. Sep 1996 A
5561708 Remillard Oct 1996 A
5561709 Remillard Oct 1996 A
5570126 Blahut et al. Oct 1996 A
5579522 Christeson et al. Nov 1996 A
5583560 Florin et al. Dec 1996 A
5588104 Lanier et al. Dec 1996 A
5588139 Lanier et al. Dec 1996 A
5594509 Florin et al. Jan 1997 A
5600364 Hendricks Feb 1997 A
5600368 Matthews, III Feb 1997 A
5600573 Hendricks et al. Feb 1997 A
5600775 King et al. Feb 1997 A
5608447 Farry Mar 1997 A
5621456 Florin et al. Apr 1997 A
5621793 Bednarek et al. Apr 1997 A
5629733 Youman et al. May 1997 A
5630103 Smith et al. May 1997 A
5635989 Rothmuller Jun 1997 A
5636346 Saxe Jun 1997 A
5638505 Hemenway et al. Jun 1997 A
5640196 Behrens et al. Jun 1997 A
5644354 Thompson et al. Jul 1997 A
5659350 Hendricks et al. Aug 1997 A
5661516 Carles Aug 1997 A
5663757 Morales Sep 1997 A
5675390 Schindler et al. Oct 1997 A
5689663 Williams Nov 1997 A
5696906 Peters et al. Dec 1997 A
5703965 Fu et al. Dec 1997 A
5715315 Handelman Feb 1998 A
5721956 Martin et al. Feb 1998 A
5724091 Freeman et al. Mar 1998 A
5724521 Dedrick Mar 1998 A
5727065 Dillon Mar 1998 A
5729471 Jain et al. Mar 1998 A
5737533 de Hond Apr 1998 A
5737725 Case Apr 1998 A
5742680 Wilson 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
5754938 Herz et al. May 1998 A
5758257 Herz May 1998 A
5764276 Martin et al. Jun 1998 A
5774122 Kojima et al. Jun 1998 A
5774170 Hite et al. Jun 1998 A
5787171 Kubota et al. Jul 1998 A
5793872 Hirayama et al. Aug 1998 A
5798785 Hendricks Aug 1998 A
5798795 Glenn et al. Aug 1998 A
5799157 Escallon Aug 1998 A
5805204 Thompson et al. Sep 1998 A
5805677 Ferry et al. Sep 1998 A
5806061 Chaudhuri et al. Sep 1998 A
5808608 Young et al. Sep 1998 A
5809204 Young et al. Sep 1998 A
5815671 Morrison Sep 1998 A
5818441 Throckmorton et al. Oct 1998 A
5818511 Farry Oct 1998 A
5819301 Rowe et al. Oct 1998 A
5829733 Becker Nov 1998 A
5833468 Guy et al. Nov 1998 A
5835087 Herz Nov 1998 A
5838368 Masunaga et al. Nov 1998 A
5844600 Kerr Dec 1998 A
5844890 Delp et al. Dec 1998 A
5848396 Gerace Dec 1998 A
5850218 LaJoie et al. Dec 1998 A
5855020 Kirsch Dec 1998 A
5864546 Campanella Jan 1999 A
5877801 Martin et al. Mar 1999 A
5880769 Nemirofsky et al. Mar 1999 A
5890122 Van Kleeck et al. Mar 1999 A
RE36207 Zimmermann et al. May 1999 E
5903319 Busko et al. May 1999 A
5909638 Allen Jun 1999 A
5917537 Lightfoot Jun 1999 A
5917553 Honey et al. Jun 1999 A
5917915 Hirose Jun 1999 A
5929849 Kikinis Jul 1999 A
5929932 Otsuki et al. Jul 1999 A
5940073 Klosterman et al. Aug 1999 A
5953458 Pirson et al. Sep 1999 A
5956716 Kenner et al. Sep 1999 A
5957695 Redford et al. Sep 1999 A
5983176 Hoffert Nov 1999 A
5986690 Hendricks Nov 1999 A
5990927 Hendricks et al. Nov 1999 A
5991735 Gerace Nov 1999 A
6006225 Bowman et al. Dec 1999 A
6016141 Knudson et al. Jan 2000 A
6025637 Mehta Feb 2000 A
6025837 Matthews, III et al. Feb 2000 A
6029045 Picco et al. Feb 2000 A
6031680 Chainer et al. Feb 2000 A
6052717 Reynolds et al. Apr 2000 A
6088732 Smith Jul 2000 A
6094680 Hokanson Jul 2000 A
6099320 Papadopoulos Aug 2000 A
6101324 Connell et al. Aug 2000 A
6119154 Weaver Sep 2000 A
6119454 Valisko Sep 2000 A
6138147 Weaver et al. Oct 2000 A
6141693 Perlman et al. Oct 2000 A
6144944 Kurtzman, II et al. Nov 2000 A
6154633 Landgraf et al. Nov 2000 A
RE36988 Johnson et al. Dec 2000 E
6163316 Killian Dec 2000 A
6166778 Yamamoto et al. Dec 2000 A
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 Jan 2001 B1
6201536 Hendricks Mar 2001 B1
6204885 Kwoh Mar 2001 B1
6209028 Walker et al. Mar 2001 B1
6219839 Sampsell Apr 2001 B1
6243713 Nelson et al. Jun 2001 B1
6252690 Laine Jun 2001 B1
6279112 O'Toole, Jr. et al. Aug 2001 B1
6282713 Kitsukawa et al. Aug 2001 B1
6286006 Bharat et al. Sep 2001 B1
6288753 DeNicola et al. Sep 2001 B1
6312336 Handelman et al. Nov 2001 B1
6327574 Kramer et al. Dec 2001 B1
6331877 Bennington Dec 2001 B1
6370543 Hoffert et al. Apr 2002 B2
6446261 Rosser Sep 2002 B1
6463468 Buch et al. Oct 2002 B1
6463585 Hendricks et al. Oct 2002 B1
6486892 Stern Nov 2002 B1
6493872 Rangan et al. Dec 2002 B1
6515680 Hendricks et al. Feb 2003 B1
6530082 Del Sesto et al. Mar 2003 B1
6539548 Hendricks et al. Mar 2003 B1
6547829 Meyerzon Apr 2003 B1
6618717 Karadimitriou et al. Sep 2003 B1
6651253 Dudkiewicz et al. Nov 2003 B2
6694352 Omoigui Feb 2004 B1
6698020 Zigmond et al. Feb 2004 B1
6751612 Schuetze Jun 2004 B1
6772150 Whitman et al. Aug 2004 B1
6839705 Grooters Jan 2005 B1
6918131 Rautila et al. Jul 2005 B1
6973436 Shkedi Dec 2005 B1
7075919 Wendt et al. Jul 2006 B1
7082427 Seibel et al. Jul 2006 B1
7143430 Fingerman et al. Nov 2006 B1
7150031 Rodriguez Dec 2006 B1
7315881 Menez Jan 2008 B2
7363645 Hendricks Apr 2008 B1
7424439 Fayyad et al. Sep 2008 B1
7505919 Richardson Mar 2009 B2
20010013123 Freeman et al. Aug 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
20020010682 Johnson Jan 2002 A1
20020026496 Boyer et al. Feb 2002 A1
20020032740 Stern Mar 2002 A1
20020038308 Cappi Mar 2002 A1
20020056129 Blackketter et al. May 2002 A1
20020059610 Ellis May 2002 A1
20020065812 Keith May 2002 A1
20020087980 Eldering et al. Jul 2002 A1
20020099697 Jensen-Grey Jul 2002 A1
20020129062 Luparello Sep 2002 A1
20030033299 Sundaresan Feb 2003 A1
20040096110 Yogeshwar et al. May 2004 A1
20040261127 Freeman et al. Dec 2004 A1
20050138660 Boyer et al. Jun 2005 A1
20050235200 Goldberg Oct 2005 A1
20050235320 Maze et al. Oct 2005 A1
Foreign Referenced Citations (137)
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
0734157 Sep 1996 EP
0821522 Jan 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
0961490 Dec 1999 EP
0992922 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
2353095 Apr 2000 GB
2344009 May 2000 GB
2358938 Aug 2001 GB
60143086 Jul 1985 JP
61-202587 Sep 1986 JP
01-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
2001119681 Apr 2001 JP
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
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
9802836 Jan 1998 WO
9808344 Feb 1998 WO
9810997 Mar 1998 WO
9818086 Apr 1998 WO
9828906 Jul 1998 WO
9848566 Oct 1998 WO
9853581 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
0027122 May 2000 WO
0028733 May 2000 WO
0079794 Dec 2000 WO
0101689 Jan 2001 WO
0111874 Feb 2001 WO
0118665 Mar 2001 WO
0124083 Apr 2001 WO
0167763 Sep 2001 WO
0175649 Oct 2001 WO
Non-Patent Literature Citations (25)
Entry
Office Action in JP Application No. P2003-535456, dated Mar. 17, 2009, with translation.
Supplementary Partial EP Search Report in EP Application No. 02778473, dated Oct. 25, 2005.
Supplementary EP Search Report in EP Application No. 02784096, dated Oct. 13, 2005.
Written Opinion in PCT Application No. PCT/US02/32756, dated Aug. 13, 2004.
International Preliminary Examination Report in PCT Application No. PCT/US02/32756, dated Feb. 17, 2005.
Office Action in JP Application No. P2003-537297, dated Nov. 24, 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. 02778472, dated Oct. 7, 2005.
Office Action in EP Application No. 02778472.7, dated Feb. 15, 2010.
Office Action in EP Application No. 02784096.6, dated Mar. 26, 2010.
Chadwick, Henry et al., “DAVIC-Digital Audio-Visual Council”, TV Anytime and TV anywhere, Dec. 1999, pp. 1-140.
Brin, Sergey et al., “The Anatomy of a Large Scale Hypertextual Web Search Engine”, Aug. 3, 3001, pp. 1-19.
Office Action in Canadian Patent Application No. 2462159, dated Aug. 2, 2010.
Office Action in U.S. Appl. No. 09/920,615, dated Apr. 11, 2011.
Office Action in Canadian Patent Application No. 2462161, dated Feb. 1, 2011.
European Office Action dated Jan. 30, 2012 in EP Application No. 02 778 473.5.
Notice of Reasons for Rejection dated Jan. 31, 2012 in Japanese Application No. P2009-188618 and English translation thereof.
Office Action in Canadian Patent Application No. 2,414,717, dated May 7, 2010.
Office Action in JP Application No. P2003-537297, dated Mar. 17, 2009, with translation.
Supplementary EP Search Report in EP Application No. 02 80 0962 dated Jul. 26, 2010.
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-0pening New Frontiers to Broadcast Services”, EBU Technical Review, Spring 1999, pp. 28-35.
European Search Report for EP 02776187.3 dated Apr. 11, 2005.
Related Publications (1)
Number Date Country
20110085080 A1 Apr 2011 US
Continuations (1)
Number Date Country
Parent 09973067 Oct 2001 US
Child 12971033 US
Continuation in Parts (2)
Number Date Country
Parent 09920723 Aug 2001 US
Child 09973067 US
Parent 09920615 Aug 2001 US
Child 09920723 US