Patent Grant
9147198
The placement of advertisements and promotions have traditionally relied on extrapolation of a small data panel of viewing behavior and other demographic information from research companies, such as the Nielsen Company, to inform these placements. These panels are limited to robustly measuring the exposure of fairly wide, mostly demographically-based audience targets, such as “women age 25-54”, and reporting is generally limited to an aggregate metric for each program aired or the commercial minutes aired within a program.
Planning and placing TV advertising using these metrics alone, however, introduces significant inefficiencies into the placement process. In general, advertisers have a narrower, more specific target than the wide demographic measure produced by data panels. For example, a health cereal manufacturer may be more interested in reaching “women who are health conscious shoppers” instead of “women age 25-54”, but present systems are unable to distinguish between these two groups, or at least narrow the scope of the broader demographic. In addition, advertisers establish reach and frequency targets for their advertising campaigns, but current metrics and systems are unable to distinguish which viewers the advertisements are being delivered to in each advertising placement, and thus many spot placements are simply wasted by exposing viewers who have already seen the advertisement many times while other viewers, who are part of the target, go unexposed. Such methods further lack comprehensive placement and optimization algorithms to help advertisers choose available advertising slots to more effectively reach their target audiences.
These and other objects are accomplished in accordance with the principles of the present invention by providing an interface for developing and optimizing a media placement plan for an advertising campaign.
In some embodiments, an audience management system allows a user to select advertising slots in an advertising campaign. The audience management system generates a plurality of cells for display in a grid arrangement in at least two dimensions. In some embodiments, a plurality of cells may be generated for display in a three-dimensional arrangement. Each of the plurality of cells is associated with an advertising slot corresponding to a content source, time period, particular program, and/or a type of programming. For example, the content source may be a television channel and the time period may be a time of day for which the advertisement is to be aired. Each of the plurality of cells also includes a representation of an audience of the associated advertising slot. For example, the representation of the audience may be an audience composition, an audience size, a projected number of audience impressions, or any combination thereof.
In some embodiments, the audience management system may identify a first cell, for example, by selecting cells. For example, the audience management system may receive a user selection of a first cell of the plurality of cells. In some embodiments, the audience management system may automatically select cells, for example, in response to running an optimization algorithm. The cells may be selected by the system to show the user which advertising slots are recommended for the media plan. The audience management system may be implemented on a user device as an interactive interface application for which the user can input various selections and choose various functions to perform. The functions may include adding a cell to a media plan, removing a cell from a media plan, retrieving more information related to an associated advertising slot, updating audience-related information contained in the cell, assigning a weight value to the first cell, or any suitable combination thereof. The audience management system may execute a function with respect to a first advertising slot associated with the first cell.
In some embodiments, the user may select a content source or a time period. In response, the audience management system may identify a subset of the plurality of cells corresponding to the selected content source or time period, and the subset may include the first cell. A function is then executed on the subset of cells. For example, the function may update a weight value related to an associated advertising slot of each cell in the subset. The weight value may be user-specified, and may relate to a relative importance of the advertising slots to an advertiser or user of the system such that, should a placement function be executed, the placement function takes the weight value into account when optimizing the media plan.
In some embodiments, the audience management system may implement a placement function to recommend advertising slots for an advertising campaign. For example, the system may receive a user selection of a budget value, which may correspond to a fixed budget for the advertising campaign. The audience management system may then allocate the budget value in one or more ways. For example, the audience management system may partition the budget value into a first partition value and a second partition value. For example, the audience management system may make the first partition value correspond to 70% of the total budget and make the second partition value correspond to 30% of the total budget. In another example, the audience management system may allocate the budget value based by various time periods, content providers, programming types, and/or selected advertising universes.
In some embodiments, the audience management system defines a plurality of data structures for storage in memory, in which each data structure may correspond to a particular advertising slot. The system also defines a plurality of groups, and associates each of the plurality of data structures with one of the plurality of groups. For example, the groups may correspond to days in an advertising campaign, and each of the plurality of data structures may represent an advertising slot for a particular day. The audience management system then allocates a portion of the first partition value to each of the plurality of groups. For example, if the first partition value corresponds to 70% of the total budget, the audience management system may allocate that each day receives a portion of the 70%. In some embodiments, each day will receive an equal allocation of the 70% (e.g. for a seven-day advertising plan, each day receives 10% of the total budget).
In some embodiments, the audience management system flags, for each of the plurality of groups, at least one data structure associated with the group based on the portion of the first partition value allocated to the group. For example, the audience management system may identify a list of advertising slots for a particular day of the week that should be added to the media plan, as long as the list of advertising slots does not exceed the allocated budget for that day. In some embodiments, each data structure associated with a particular group is ranked by the audience management system based on audience-related criteria, including audience composition, audience size, audience index, impressions, user-specified weight, campaign goals and parameters, such as total impressions, budget constraints, inventory restrictions, reach, frequency, or any suitable combination thereof. A plurality of ranked data structures may be identified by the audience management system, in which each of the plurality has the highest rankings of the data structures associated with a particular group. The audience management system may then flag the identified data structures. For example, the audience management system ranks each advertising slot for a particular day, and then purchases the most highly ranked advertising slots until the budget allocated for that day is reached. The audience management system performs this selection for each day in the advertising campaign.
In some embodiments, the audience management system identifies a remainder of data structures within the plurality of data structures that are unflagged regardless of the group that the data structures are associated with. For example, the audience management system will search through all available advertising slots through each day of the advertising campaign to identify advertising slots that were not purchased. The audience management system will then rank each advertising slot based on an audience-related criteria, and purchase the highest ranked advertising slots as long as the second budget portion (e.g. 30% of the total budget) is not exceeded.
In some embodiments, the audience management system allows a user to set prices for individual advertising slots or for pricing tiers of groups of advertising slots. The audience management system defines a plurality of data structures and stores the data structures in a memory. Each data structure is representative of one of a plurality of advertising slots. The audience management system then stores, in each of the plurality of data structures, a price value associated with a respective advertising slot. For example, the audience management system may receive pricing information for advertising slots from various publishers, service providers, and content sources.
In some embodiments, the audience management system receives a user selection of a fixed price value. The fixed price value is then stored as the fixed price value of a first data structure of the plurality of data structures. For example, the user may designate a particular advertising slot to have a fixed price. The audience management system then automatically updates the fixed price value of each of the plurality of data structures without changing the fixed price value of the first data structure. For example, once the price is fixed for a first advertising slot, the audience management system may update the pricing information associated with a remainder of the advertising slots based on a projected demand of each of the remainder of the advertising slots. In some embodiments, the projected demand may be based on the fixed price (e.g. setting a high fixed price may be predicted to increase the demand of “nearby” advertising slots on the same television channel). The audience management system may determine projected demand by analyzing historical inventory data, projected inventory data, current demand, audience estimates, or any suitable combination thereof.
In some embodiments, the audience management system may allow the user to set a fixed price for a pricing tier. Pricing tiers may be used to set the prices of a plurality of advertising slots belonging to a particular group associated with the pricing tier. Once the user sets the fixed price for the pricing tier, the audience management system may update a fixed price value for each of the plurality of pricing tiers without changing the fixed price value of the fixed pricing tier. The audience management system then updates each price value of the plurality of advertising slots based on an updated price value of an associated pricing tier.
The above and other features of the present invention, its nature and various advantages will be more apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, and in which:
Over the course of the last two decades, the amount and variety of large data sets has grown exponentially and will only continue to grow. As additional data has become available, this data has been used to inform media placement on a largely ad hoc basis through the use of research reports to manually place advertisements. The systems and methods described herein relate to a platform that enables optimization of media placement (which may also be referred to as “advertisement placement”, “ad placement”, or “spot ad placement”) through coupling of media activation with audience based analytics and targeting that are now possible with large scale datasets and scaled computing resources.
While TV remains a medium where a single advertising spot is seen by somewhere between a few hundred up to millions of people, a different subset of the population is exposed by each spot ad placement. The systems and methods described herein use granular data to understand the members of this subset and the overlap of each subset with each other, enabling the selection of advertisement and promotional placements that most efficiently meet an advertiser's goals. Moreover, the systems and methods described herein are applicable to other embodiments (e.g. online embodiments) aside form television. The system, referred to herein as an “audience management system”, provides a common platform that can ingest data from multiple sources (e.g. panels, set-tops, SmartTVs, etc.), generate future estimates of delivery for ad inventory using these data sources, and enable the delivery of media weight as measured by one or more of these data sources. The system utilizes an optimization algorithm that serves to optimize the delivery of one or more of these metrics, depending on the user's inputs and selections in building the media plan.
The system provides an inventory owner with the ability to build an optimized media plan based on a specific target for the advertiser. Using targeting segments matched to set-top or other viewership data at a viewer, household, or other viewing group level, the system will assemble an optimized media plan to reach the advertiser's target at the desired frequency, going beyond traditional age/sex demographics which are primarily used to plan and drive ad placement today.
Once an audience media plan has been generated by the system and approved by an advertiser, the system will create linear traffic orders to execute the media plan. As these traffic orders are executed, the system will update placements to ensure that the media plan delivers on the contracted commitments to the advertiser.
The system further enables the inventory owner to evaluate the inventory usage, pricing, and sellout rates for their existing linear business and establish rules which define inventory availability and pricing policies for sales through the system. As referred to herein, the term “inventory” refers to any available medium through which an advertiser can have an advertisement made available to an audience for a period of time (e.g. a television advertisement slot, a billboard, a magazine, or any other suitable medium). The system optimizes the use of inventory across all of the active media plans, enabling a publisher or other inventory owner to sell audience targeting commitments to many advertisers on an optimized basis. For example, the embodiments disclosed herein may also be applied to multiple media plans and advertiser criteria. In such cases, the audience management system may allocate amongst all advertisers in a responsive manner in order to provide user feedback related to recommended media plans. In each embodiment, the audience management system may rank available inventory based on whether it is more suitable for one advertising campaign over another, and may optimize the allocation so as to avoid an unbalanced distribution of inventory among advertisers.
The foregoing will be apparent from the following description of example embodiments and implementations, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are illustrative of the systems and methods described herein and are not to be interpreted as limiting.
Using console 114, which can be a web-based console or other interface that enables access to audience management platform 102, users can create an optimized media plan based on an input that can include the advertiser's desired target (typically defined by one or more attributes from a third party data source and/or a viewership or other behavior), impression delivery goals, reach to target audience, budget constraints, and a media plan external to the systems. Once a proposal has been approved by the inventory owner, the advertiser, or user of the system, audience management platform 102 generates traffic orders using traffic order module 112 to process through media traffic system 108 via data path 110. For example, traffic system 108 may be the inventory owner's media traffic system (e.g. the NOVAR system). With multiple advertisers in the system, traffic order module 112 will optimize across advertisers and produce traffic orders that maximize revenue or such other parameters dictated by the system user (e.g., sell out rates, breadth of media plan across multiple networks, etc.). As an advertiser's order is executed and media is placed, the verified results are picked up by the system through the data transfer discussed in regard to sales history source 106. The system will then adjust future order output to complete the contracted audience delivery for the advertiser.
System 100 may receive inputs from a user through console 114 using a suitable interactive interface application, which may take various forms depending on the options provided to a user of console 114. Interactive interface applications may generate graphical user interface screens that enable a user to navigate among, locate, and select various options such inventory selections, weighting values, price setting, and optimization settings used in conjunction with data driven media placement. As referred to herein, the terms “media content” and “media” should be understood to mean an electronically consumable user asset, such as television programming, as well as pay-per-view programs, on-demand programs (as in video-on-demand (VOD) systems), Internet content (e.g., streaming content, downloadable content, Webcasts, etc.), video clips, audio, content information, pictures, rotating images, documents, playlists, websites, articles, books, electronic books, blogs, advertisements, chat sessions, social media, applications, games, and/or any other media or multimedia and/or combination of the same.
The interactive interface applications and/or any instructions for performing any of the embodiments described herein may be encoded on computer readable media. Computer readable media includes any media capable of storing data. The computer readable media may be transitory, including, but not limited to, propagating electrical or electromagnetic signals, or may be non-transitory including, but not limited to, volatile and non-volatile computer memory or storage devices such as a hard disk, floppy disk, USB drive, DVD, CD, media cards, register memory, processor caches, Random Access Memory (“RAM”), etc.
As referred to herein, the phrase “user equipment device,” “user equipment,” “user device,” “electronic device,” “electronic equipment,” “media equipment device,” or “media device” should be understood to mean any device for accessing, viewing, selecting options, or any combination thereof, including, but not limited to, a television, a Smart TV, a set-top box, an integrated receiver decoder (IRD) for handling satellite television, a digital storage device, a digital media receiver (DMR), a digital media adapter (DMA), a streaming media device, a DVD player, a DVD recorder, a connected DVD, a local media server, a BLU-RAY player, a BLU-RAY recorder, a personal computer (PC), a laptop computer, a tablet computer, a WebTV box, a personal computer television (PC/TV), a PC media server, a PC media center, a hand-held computer, a stationary telephone, a personal digital assistant (PDA), a mobile telephone, a portable video player, a portable music player, a portable gaming machine, a smart phone, or any other television equipment, computing equipment, or wireless device, and/or combination of the same. It is to be understood that any of the foregoing devices may be used by an advertiser, inventory owner, publisher, or any user of the audience management system to perform the methods or operate the systems described herein.
In some embodiments, the user equipment device may have a front facing screen and a rear facing screen, multiple front screens, or multiple angled screens. In some embodiments, the user equipment device may have a front facing camera and/or a rear facing camera. The user equipment device may be configured to implement an interactive interface application. The interactive interface application may be provided as on-line applications (i.e., provided on a web-site), or as stand-alone applications or clients on user equipment devices. Various devices and platforms that may implement interactive interface applications are described in more detail below.
Control circuitry 204 may be based on any suitable processing circuitry such as processing circuitry 206. As referred to herein, processing circuitry should be understood to mean circuitry based on one or more microprocessors, microcontrollers, digital signal processors, programmable logic devices, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc., and may include a multi-core processor (e.g., dual-core, quad-core, hexa-core, or any suitable number of cores) or supercomputer. Any component described herein that is used in the audience management system (e.g. user television equipment, a PC, a laptop, wireless portable devices, a media content server, a media guidance server, a user profile server, an audience management module, etc.), may have its own control circuitry 204 and processing circuitry 206. In some embodiments, processing circuitry may be distributed across multiple separate processors or processing units, for example, multiple of the same type of processing units (e.g., two Intel Core i7 processors) or multiple different processors (e.g., an Intel Core i5 processor and an Intel Core i7 processor). In some embodiments, control circuitry 204 executes instructions for a interactive interface application stored in memory (i.e., storage 208). Specifically, control circuitry 204 may be instructed by the interactive interface application to perform the functions discussed above and below. For example, the interactive interface application may provide instructions to control circuitry 204 to generate the media guidance displays. In some implementations, any action performed by control circuitry 204 may be based on instructions received from the interactive interface application.
In client-server based embodiments, control circuitry 204 may include communications circuitry suitable for communicating with a guidance application server or other networks or servers. The instructions for carrying out the above mentioned functionality may be stored on the guidance application server. Communications circuitry may include a cable modem, an integrated services digital network (ISDN) modem, a digital subscriber line (DSL) modem, a telephone modem, Ethernet card, or a wireless modem for communications with other equipment, or any other suitable communications circuitry. Such communications may involve the Internet or any other suitable communications networks or paths (which is described in more detail in connection with
Memory may be an electronic storage device provided as storage 208 that is part of control circuitry 204. As referred to herein, the phrase “electronic storage device” or “storage device” should be understood to mean any device for storing electronic data, computer software, or firmware, such as random-access memory, read-only memory, hard drives, optical drives, digital video disc (DVD) recorders, compact disc (CD) recorders, BLU-RAY disc (BD) recorders, BLU-RAY 3D disc recorders, digital video recorders (DVR, sometimes called a personal video recorder, or PVR), solid state devices, quantum storage devices, gaming consoles, gaming media, or any other suitable fixed or removable storage devices, and/or any combination of the same. Storage 208 may be used to store various types of content described herein as well as media guidance information, described above, and guidance application data, described above. Nonvolatile memory may also be used (e.g., to launch a boot-up routine and other instructions). Cloud-based storage, described in relation to
Control circuitry 204 may include video generating circuitry and tuning circuitry, such as one or more analog tuners, one or more MPEG-2 decoders or other digital decoding circuitry, high-definition tuners, or any other suitable tuning or video circuits or combinations of such circuits. Encoding circuitry (e.g., for converting over-the-air, analog, or digital signals to MPEG signals for storage) may also be provided. Control circuitry 204 may also include scaler circuitry for upconverting and downconverting content into the preferred output format of the user equipment 200. Circuitry 204 may also include digital-to-analog converter circuitry and analog-to-digital converter circuitry for converting between digital and analog signals. The tuning and encoding circuitry may be used by the user equipment device to receive and to display, to play, or to record content. The tuning and encoding circuitry may also be used to receive guidance data. The circuitry described herein, including for example, the tuning, video generating, encoding, decoding, encrypting, decrypting, scaler, and analog/digital circuitry, may be implemented using software running on one or more general purpose or specialized processors. Multiple tuners may be provided to handle simultaneous tuning functions (e.g., watch and record functions, picture-in-picture (PIP) functions, multiple-tuner recording, etc.). If storage 208 is provided as a separate device from user equipment 200, the tuning and encoding circuitry (including multiple tuners) may be associated with storage 208.
A user may send instructions to control circuitry 204 using user input interface 210. User input interface 210 may be any suitable user interface, such as a remote control, mouse, trackball, keypad, keyboard, touch screen, touchpad, stylus input, joystick, voice recognition interface, or other user input interfaces. Display 212 may be provided as a stand-alone device or integrated with other elements of user equipment device 200. Display 212 may be one or more of a monitor, a television, a liquid crystal display (LCD) for a mobile device, or any other suitable equipment for displaying visual images. In some embodiments, display 212 may be HDTV-capable. In some embodiments, display 212 may be a 3D display, and the interactive interface application and any suitable content may be displayed in 3D. A video card or graphics card may generate the output to the display 212. The video card may offer various functions such as accelerated rendering of 3D scenes and 2D graphics, MPEG-2/MPEG-4 decoding, TV output, or the ability to connect multiple monitors. The video card may be any processing circuitry described above in relation to control circuitry 204. The video card may be integrated with the control circuitry 204. Speakers 214 may be provided as integrated with other elements of user equipment device 200 or may be stand-alone units. The audio component of videos and other content displayed on display 212 may be played through speakers 214. In some embodiments, the audio may be distributed to a receiver (not shown), which processes and outputs the audio via speakers 214.
The guidance application may be implemented using any suitable architecture. For example, it may be a stand-alone application wholly implemented on user equipment device 200. In such an approach, instructions of the application are stored locally, and data for use by the application is downloaded on a periodic basis (e.g., from an out-of-band feed, from an Internet resource, or using another suitable approach). In some embodiments, the interactive interface application is a client-server based application. Data for use by a thick or thin client implemented on user equipment device 200 is retrieved on-demand by issuing requests to a server remote to the user equipment device 200. In one example of a client-server based guidance application, control circuitry 204 runs a web browser that interprets web pages provided by a remote server.
In some embodiments, the interactive interface application is downloaded and interpreted or otherwise run by an interpreter or virtual machine (run by control circuitry 204). In some embodiments, the guidance application may be encoded in the ETV Binary Interchange Format (EBIF), received by control circuitry 204 as part of a suitable feed, and interpreted by a user agent running on control circuitry 204. For example, the guidance application may be an EBIF application. In some embodiments, the guidance application may be defined by a series of JAVA-based files that are received and run by a local virtual machine or other suitable middleware executed by control circuitry 204. In some of such embodiments (e.g., those employing MPEG-2 or other digital media encoding schemes), the guidance application may be, for example, encoded and transmitted in an MPEG-2 object carousel with the MPEG audio and video packets of a program.
A user equipment device utilizing at least some of the system features described above in connection with
In audience management system 300, there is typically more than one of each type of user equipment device but only one of each is shown in
In some embodiments, a user equipment device (e.g., user television equipment 302, user computer equipment 304, wireless user communications device 306) may be referred to as a “second screen device.” For example, a second screen device may supplement content presented on a first user equipment device. The content presented on the second screen device may be any suitable content that supplements the content presented on the first device. In some embodiments, the second screen device provides an interface for adjusting settings and display preferences of the first device. In some embodiments, the second screen device is configured for interacting with other second screen devices or for interacting with a social network. The second screen device can be located in the same room as the first device, a different room from the first device but in the same house or building, or in a different building from the first device.
The user may also set various settings to maintain consistent interactive interface application settings across in-home devices and remote devices. Settings include those described herein, as well as channel and program favorites, programming preferences that the guidance application utilizes to make programming recommendations, display preferences, and other desirable guidance settings. For example, if a user sets a channel as a favorite on, for example, the web site www.allrovi.com on their personal computer at their office, the same channel would appear as a favorite on the user's in-home devices (e.g., user television equipment and user computer equipment) as well as the user's mobile devices, if desired. Therefore, changes made on one user equipment device can change the guidance experience on another user equipment device, regardless of whether they are the same or a different type of user equipment device. In addition, the changes made may be based on settings input by a user, as well as user activity monitored by the guidance application.
The user equipment devices may be coupled to communications network 314. Namely, user television equipment 302, user computer equipment 304, and wireless user communications device 306 are coupled to communications network 314 via communications paths 308, 310, and 312, respectively. Communications network 314 may be one or more networks including the Internet, a mobile phone network, mobile voice or data network (e.g., a 4G or LTE network), cable network, public switched telephone network, or other types of communications network or combinations of communications networks. Paths 308, 310, and 312 may separately or together include one or more communications paths, such as, a satellite path, a fiber-optic path, a cable path, a path that supports Internet communications (e.g., IPTV), free-space connections (e.g., for broadcast or other wireless signals), or any other suitable wired or wireless communications path or combination of such paths. Path 312 is drawn with dotted lines to indicate that in the exemplary embodiment shown in
Although communications paths are not drawn between user equipment devices, these devices may communicate directly with each other via communication paths, such as those described above in connection with paths 308, 310, and 312, as well as other short-range point-to-point communication paths, such as USB cables, IEEE 1394 cables, wireless paths (e.g., Bluetooth, infrared, IEEE 802-11x, etc.), or other short-range communication via wired or wireless paths. BLUETOOTH is a certification mark owned by Bluetooth SIG, INC. The user equipment devices may also communicate with each other directly through an indirect path via communications network 314.
Audience management system 300 includes content source 316 and media guidance data source 318 coupled to communications network 314 via communication paths 320 and 322, respectively. Paths 320 and 322 may include any of the communication paths described above in connection with paths 308, 310, and 312. Communications with the content source 316 and media guidance data source 318 may be exchanged over one or more communications paths, but are shown as a single path in
If desired, content source 316 and media guidance data source 318 may be integrated as one source device. Although communications between sources 316 and 318 with user equipment devices 302, 304, and 306 are shown as through communications network 314, in some embodiments, sources 316 and 318 may communicate directly with user equipment devices 302, 304, and 306 via communication paths (not shown) such as those described above in connection with paths 308, 310, and 312.
Content source 316 may include one or more types of content distribution equipment including a television distribution facility, cable system headend, satellite distribution facility, programming sources (e.g., television broadcasters, such as NBC, ABC, HBO, etc.), intermediate distribution facilities and/or servers, Internet providers, on-demand media servers, and other content providers. NBC is a trademark owned by the National Broadcasting Company, Inc., ABC is a trademark owned by the American Broadcasting Company, Inc., and HBO is a trademark owned by the Home Box Office, Inc. Content source 316 may be the originator of content (e.g., a television broadcaster, a Webcast provider, etc.) or may not be the originator of content (e.g., an on-demand content provider, an Internet provider of content of broadcast programs for downloading, etc.). Content source 316 may include cable sources, satellite providers, on-demand providers, Internet providers, over-the-top content providers, or other providers of content. Content source 316 may also include a remote media server used to store different types of content (including video content selected by a user), in a location remote from any of the user equipment devices. Systems and methods for remote storage of content, and providing remotely stored content to user equipment are discussed in greater detail in connection with Ellis et al., U.S. Pat. No. 7,761,892, issued Jul. 20, 2010, which is hereby incorporated by reference herein in its entirety.
Media guidance data source 418 may provide media guidance data, such as the media guidance data described above. Interactive interface application data may be provided to the user equipment devices using any suitable approach. In some embodiments, the guidance application may be a stand-alone interactive television program guide that receives program guide data via a data feed (e.g., a continuous feed or trickle feed). Program schedule data and other guidance data may be provided to the user equipment on a television channel sideband, using an in-band digital signal, using an out-of-band digital signal, or by any other suitable data transmission technique. Program schedule data and other media guidance data may be provided to user equipment on multiple analog or digital television channels.
In some embodiments, guidance data from media guidance data source 318 may be provided to users' equipment using a client-server approach. For example, a user equipment device may pull media guidance data from a server, or a server may push media guidance data to a user equipment device. In some embodiments, a guidance application client residing on the user's equipment may initiate sessions with source 318 to obtain guidance data when needed, e.g., when the guidance data is out of date or when the user equipment device receives a request from the user to receive data. Media guidance may be provided to the user equipment with any suitable frequency (e.g., continuously, daily, a user-specified period of time, a system-specified period of time, in response to a request from user equipment, etc.). Media guidance data source 318 may provide user equipment devices 302, 304, and 306 the interactive interface application itself or software updates for the interactive interface application.
User profile information including user settings, user personalization, user preference, and user media content information may be stored on user equipment devices and/or on user profile server 324. User profile server 324 may be in communication with user equipment devices 302, 304 and 306 through communications path 326 and communications network 314. User profile server 324 may include storage devices for storing user profile information associated with user media networks. User profile server 324 may also include storage devices for storing media content information associated with user media networks including recordings of media content and/or lists of selected media content. User profile server 324 may include processors and communications circuits for managing user profile information, remotely controlling and communicating with user equipment devices, and exchanging user profile information with user equipment devices. Media content source 316 may communicate with user profile service 324 to obtain information on a particular user to which media recommendations may be sent, or may have its own user profile server for maintaining user profile information.
Interactive interface applications may be, for example, stand-alone applications implemented on user equipment devices. For example, the interactive interface application may be implemented as software or a set of executable instructions which may be stored in storage 208, and executed by control circuitry 204 of user equipment device 200. In some embodiments, interactive interface applications may be client-server applications where only a client application resides on the user equipment device, and server application resides on a remote server. For example, interactive interface applications may be implemented partially as a client application on control circuitry 204 of user equipment device 200 and partially on a remote server as a server application (e.g., media guidance data source 318) running on control circuitry of the remote server. When executed by control circuitry of the remote server (such as media guidance data source 318), the interactive interface application may instruct the control circuitry to generate the guidance application displays and transmit the generated displays to the user equipment devices. The server application may instruct the control circuitry of the media guidance data source 318 to transmit data for storage on the user equipment. The client application may instruct control circuitry of the receiving user equipment to generate the guidance application displays.
Content and/or media guidance data delivered to user equipment devices 302, 304, and 306 may be over-the-top (OTT) content. OTT content delivery allows Internet-enabled user devices, including any user equipment device described above, to receive content that is transferred over the Internet, including any content described above, in addition to content received over cable or satellite connections. OTT content is delivered via an Internet connection provided by an Internet service provider (ISP), but a third party distributes the content. The ISP may not be responsible for the viewing abilities, copyrights, or redistribution of the content, and may only transfer IP packets provided by the OTT content provider. Examples of OTT content providers include YOUTUBE, NETFLIX, and HULU, which provide audio and video via IP packets. Youtube is a trademark owned by Google Inc., Netflix is a trademark owned by Netflix Inc., and Hulu is a trademark owned by Hulu, LLC. OTT content providers may additionally or alternatively provide media guidance data described above. In addition to content and/or media guidance data, providers of OTT content can distribute interactive interface applications (e.g., web-based applications or cloud-based applications), or the content can be displayed by interactive interface applications stored on the user equipment device.
Audience management system 300 is intended to illustrate a number of approaches, or network configurations, by which user equipment devices and sources of content and guidance data may communicate with each other for the purpose of accessing content and providing media guidance. The embodiments described herein may be applied in any one or a subset of these approaches, or in a system employing other approaches for delivering content and providing media guidance. The following four approaches provide specific illustrations of the generalized example of
In one approach, user equipment devices may communicate with each other within a home network. User equipment devices can communicate with each other directly via short-range point-to-point communication schemes described above, via indirect paths through a hub or other similar device provided on a home network, or via communications network 314. Each of the multiple individuals in a single home may operate different user equipment devices on the home network. As a result, it may be desirable for various media guidance information or settings to be communicated between the different user equipment devices. For example, it may be desirable for users to maintain consistent interactive interface application settings on different user equipment devices within a home network, as described in greater detail in Ellis et al., U.S. patent application Ser. No. 11/179,410, filed Jul. 11, 2005. Different types of user equipment devices in a home network may also communicate with each other to transmit content. For example, a user may transmit content from user computer equipment to a portable video player or portable music player.
In a second approach, users may have multiple types of user equipment by which they access content and obtain media guidance. For example, some users may have home networks that are accessed by in-home and mobile devices. Users may control in-home devices via a interactive interface application implemented on a remote device. For example, users may access an online interactive interface application on a website via a personal computer at their office, or a mobile device such as a PDA or web-enabled mobile telephone. The user may set various settings (e.g., recordings, reminders, or other settings) on the online guidance application to control the user's in-home equipment. The online guide may control the user's equipment directly, or by communicating with a interactive interface application on the user's in-home equipment. Various systems and methods for user equipment devices communicating, where the user equipment devices are in locations remote from each other, is discussed in, for example, Ellis et al., U.S. Pat. No. 8,046,801, issued Oct. 25, 2011, which is hereby incorporated by reference herein in its entirety.
In a third approach, users of user equipment devices inside and outside a home can use their interactive interface application to communicate directly with content source 316 to access content. Specifically, within a home, users of user television equipment 302 and user computer equipment 304 may access the interactive interface application to navigate among and locate desirable content. Users may also access the interactive interface application outside of the home using wireless user communications devices 306 to navigate among and locate desirable content.
In a fourth approach, user equipment devices may operate in a cloud computing environment to access cloud services. In a cloud computing environment, various types of computing services for content sharing, storage or distribution (e.g., video sharing sites or social networking sites) are provided by a collection of network-accessible computing and storage resources, referred to as “the cloud.” For example, the cloud can include a collection of server computing devices, which may be located centrally or at distributed locations, that provide cloud-based services to various types of users and devices connected via a network such as the Internet via communications network 314. These cloud resources may include one or more content sources 316 and one or more media guidance data sources 318. In addition or in the alternative, the remote computing sites may include other user equipment devices, such as user television equipment 302, user computer equipment 304, and wireless user communications device 306. For example, the other user equipment devices may provide access to a stored copy of a video or a streamed video. In such embodiments, user equipment devices may operate in a peer-to-peer manner without communicating with a central server.
The cloud provides access to services, such as content storage, content sharing, or social networking services, among other examples, as well as access to any content described above, for user equipment devices. Services can be provided in the cloud through cloud computing service providers, or through other providers of online services. For example, the cloud-based services can include a content storage service, a content sharing site, a social networking site, or other services via which user-sourced content is distributed for viewing by others on connected devices. These cloud-based services may allow a user equipment device to store content to the cloud and to receive content from the cloud rather than storing content locally and accessing locally-stored content.
A user may use various content capture devices, such as camcorders, digital cameras with video mode, audio recorders, mobile phones, and handheld computing devices, to record content. The user can upload content to a content storage service on the cloud either directly, for example, from user computer equipment 304 or wireless user communications device 306 having content capture feature. Alternatively, the user can first transfer the content to a user equipment device, such as user computer equipment 304. The user equipment device storing the content uploads the content to the cloud using a data transmission service on communications network 314. In some embodiments, the user equipment device itself is a cloud resource, and other user equipment devices can access the content directly from the user equipment device on which the user stored the content.
Cloud resources may be accessed by a user equipment device using, for example, a web browser, a interactive interface application, a desktop application, a mobile application, and/or any combination of access applications of the same. The user equipment device may be a cloud client that relies on cloud computing for application delivery, or the user equipment device may have some functionality without access to cloud resources. For example, some applications running on the user equipment device may be cloud applications, i.e., applications delivered as a service over the Internet, while other applications may be stored and run on the user equipment device. In some embodiments, a user device may receive content from multiple cloud resources simultaneously. For example, a user device can stream audio from one cloud resource while downloading content from a second cloud resource. Or a user device can download content from multiple cloud resources for more efficient downloading. In some embodiments, user equipment devices can use cloud resources for processing operations such as the processing operations performed by processing circuitry described in relation to
Once the account is created, the process proceeds to step 404. At step 404, the user identifies a target segment to be used for the media plan that identifies a group of viewers or households with certain characteristics to be targeted through the system. These may include specific target segments created by third parties available to audience management system 300 and matched with the viewership data or behavioral segments accessible through audience management system 300 or created by the user. For example, a media content source, such as NBC, may be able to provide a pre-defined target segment, such as “has viewed Saturday Night Live 3 times in the last 6 months”, to the user. In some embodiments, audience management module 328 may query media content source 316 to retrieve a list of pre-defined target segments based on viewership data. In some embodiments, audience management module 328 may query user profile server 324 to retrieve viewership data to enable the user to produce his/her own target segments. In addition, unions or intersections of existing targets may be defined as new targets using a target creation function of the audience management module 328.
Once the user has established one or more target segments that he/she would like to reach in the advertising campaign, the process may then proceed to step 406. In step 406, the user may utilize placement functions of audience management module 328 that enable the user to build an optimized media plan to reach the earlier established target segments established. The term “placement” should be understood to mean the adding or allocation of inventory, such as in the form of available advertising slots, to an advertising campaign of an advertiser, such that advertising media is made available to an audience within a scheduled time period upon execution of the advertising campaign. In some embodiments, placement functions may relate setting campaign goals and parameters, such as total impressions, budget constraints, inventory restrictions, reach, frequency, or any suitable combination thereof, as will be described in greater detail with respect to
Once a media plan is created by the placement function and approved by the user, the process then proceeds to step 408. Step 408 may be optionally performed in the scenario in which the user is not the advertiser, but is acting on behalf of the advertiser. At step 408, the user will be able to generate a proposal to share with the advertiser. Proposals are formatted reports that provide a summary of the goals and media being delivered for the campaign, and may be transferred to a device of the advertiser over communications network 314. If the advertiser requests changes to the proposal/campaign, the placement function will allow the user to make updates to the campaign parameters, save a new version and generate a new proposal. In some embodiments, the user may authorize access to the advertiser to edit the parameters of the media plan directly, for example, through a web interface. In some embodiments, the proposal may be in the form of an interactive interface application implemented on a user equipment device of the advertiser. For example, the advertiser may be able to view the parameters and proposed media plan in the interactive interface application. In some embodiments, the advertiser may propose changes to the parameters of the proposed media plan, and simulate the placement function in order to see how the advertiser's proposed changes affect the media plan.
If the advertiser and/or user are satisfied with the media plan projections made using the placement function, the user may then save the current state of the media plan and proposal, for example, by storing the media plan and proposal in storage 208 of audience management module 328. The process proceeds to step 410. At step 410, audience management module 328 generates a specific set of advertisement placements in accordance with available advertising slots, or spots, for particular content providers. These placements are based on the optimization parameters discussed in connection with the various embodiments disclosed herein. In some embodiments, the placement may require a specific time to run the advertisement. In some embodiments, the placement may designate a time period for running the advertisement, and a “fuzzy” schedule may be generated in which the advertisement is required to appear within the time period, but at a specific time designated by the content source that runs the advertisement. Concurrently with step 410, or alternatively, the order may be transferred to and ingested by a traffic/promotion scheduling system in step 412.
The process proceeds to step 414. At step 414, media placements for the advertiser are executed via the traffic system and ad inserters as the advertisement is placed. The process then proceeds to step 416, where the verified placements are fed back into the system via verification or as-run logs. Using this data and collected viewership data, audience management module 328 can update estimates of audience for the placements with actual verified impression delivery, and will update future placements based on performance to-date. Audience management module 328 then provides the user with the ability to generate reports on actual delivery metrics based on verified spot placements against impressions calculated from set-top impressions, as accessible through communications network 314.
In some embodiments, viewing data, which has been edited to remove viewing attributed to TV-off events or other boundary parameters, is aggregated by audience management module 328 into blocks bounded by the start and end times of the programming being aired. A set of data for training the model is extracted from a superset of all edited viewing data. This extracted data will include as much data as can be feasibly processed by the model. In some embodiments, this extracted data is at least a year's worth of data in order to include seasonal effects on viewership, although the system can operate effectively with less data. Using the extracted data, machine learning algorithms are applied to generate a predictive model which uses the various attributes associated with relevant programming (e.g., start time, day of week, genre, keyword, local interest, lead-in status of the program, etc.) to predict the average audience (average number of viewers) and total reach (total unique viewers for that program over a period of time) for each programming block. For example, in some embodiments, the audience management system may receive one or more inputs for use in estimating data associated with future audience inventory for media plans. In some embodiments, the received inputs may be used in conjunction with data retrieved from other various sources, such as databases 604, 606, 652, and 654, as described below with respect to
In some embodiments, currently available inventory blocks are evaluated by pulling data from various databases, including viewership database 602 (which is filtered through module 608 to generate a universe projection), third party metrics database 604, and sales database 606 feed data to module 610. In some embodiments, projected inventory blocks are evaluated by pulling data from third party database 652 (in which universe estimates may be generated by a third party) and inventory database 654 (in which projected estimates for inventory availability are maintained) feed data to module 656. Depending on the scope of the inventory, the audience estimates used for metric calculations may be different. For example, spot (unit) inventory from an individual zone will require universe projections, and future estimates based on the population of that zone. Spot (unit) inventory from an interconnect will require universe projections for the entire interconnect, while national inventory will require universe projections for the total carriage of the channel. In some embodiments, inventory analysis performed by audience management module 328. In some embodiments, the metrics are computed via a third part and transmitted to audience management module 328 over communications network 314.
Once the metrics are determined and audience information has been suitably processed, audience management system 300 may provide a visual interface (e.g. a media plan interface) to allow easily design and edit a media plan.
Grid arrangement 702 contains a plurality of cells representative of a proposed media plan for placement of advertisements. In display 700, each cell contains representative audience data, and each cell may correspond to a particular inventory unit, such as an advertising slot for a content source and a time period, as shown in
Television advertising is merely illustrative, and the media plan need not be limited to television or other electronic content sources. For example, audience management module 328 may be implemented in the context of advertising in general, such as newspaper, magazine, billboards, posters, or other suitable forms of advertising. In such embodiments, display 700 may display a plurality of cells arranged according to a particular advertising venue and a particular day of the week for which the advertisement is to be run. For example, content source axis 406 may be replaceable by an axis indicative of a printed publication, and time period axis 404 may be indicative of a particular publication month.
In some embodiments, each content source or time period may have an associated weight value. For example, weight options 708 and 714 appear beside a content source and time period, respectively. Processing circuitry 206 may receive user inputs to adjust a weight associated with the content source or time period. In some embodiments, the value of “100” may indicate a default weight. The user has the option of selecting different weights, which may affect a scoring algorithm, as will be discussed in greater detail with respect to
In some embodiments, processing circuitry 206 may receive user selections of options 710 and 716, which provide increased granularity for the content source or time period that each represents. In some embodiments, options 710 and 716 may appear in response to a user selection on a content source of content source axis 706 and a time period of time period axis 704, respectively. For example, a selection of option 710 may cause processing circuitry 206 to generate for display content source related information within the cells in the row corresponding to option 710, such as the programs that will be airing or the availability of advertising slots. In response to a user selection of option 716, for example, processing circuitry 206 may generate for display additional time period related information within the cells in the column corresponding to option 716. Additional time period related information may include additional columns corresponding to the hours within a particular daypart, such as columns representing each of “5 am”, “6 am”, and “7 am” instead of a single column representing “Early Morning”.
If processing circuitry 206 receives a user selection of sort option 726, rows of grid arrangement 702 may be sorted according to a property of the content sources within content source axis 706. For example, content sources may be sorted in forward or reverse alphabetical order, by popularity, by average cost to advertise, by assigned weight values, or by any other suitable quantity.
If processing circuitry 206 receives a user selection of time period option 724, processing circuitry 206 may generate for display a suitable time period representation for time period axis 704. For example, display 700, as depicted in
Density indicator 720 provides an indication to a user of the magnitude or relative value of a visual indicator of an audience-related parameter. For example, density indicator 720, as depicted in
A user selection of zoom option 728 may result in a relative increase or decrease in size of elements appearing in display 700, or a relative increase or decrease in granularity of the information appearing in display 700. Zoom option 728 may be implemented in any suitable fashion, such as a slider, buttons of various sizes, a percentage indicator, or any suitable combination thereof. In some embodiments, if the user slides zoom option 728 to the right, this may cause processing circuitry 206 to increase the granularity of the information displayed by, for example, replacing existing time period columns with time period columns corresponding to shorter time periods. A display with increased granularity is discussed in greater detail with respect to
In some embodiments, processing circuitry 206 may receive a user selection of a cell of the plurality of cells in grid arrangement 700. Once the cell is selected, the user may take an action suggestive of a particular function to execute with the respective cell. For example, using user input interface 210, the user may select an available option through the interactive interface application implemented on user equipment device 200. The function may be executed locally or remotely. For example, if user equipment device 200 is located remotely from audience management module 328 and the function requires audience management module 328 to perform a placement function, the message may be transmitted, along with any additional required information, from user equipment device 200 to audience management module 328. After executing the function, audience management module 328 may then transmit updated information back to user equipment device 300 that reflects the results of the placement function, and this updated information may then be generated for display by processing circuitry 206. The function executed by processing circuitry 206 may be, for example, adding one or more advertising slots to a media plan, removing one or more advertising slots from media plan, displaying additional information for each cell in the form of pop-up overlay, generating for display media content from a corresponding content source, updating a weight value related to an associated advertising slot of each of the selected cells, updating an audience representation for each of the plurality of cells, transmitting an order to place advertisements, refreshing the display, assigning a fixed price value to an advertising slot, or any other suitable function in accordance with the embodiments described herein.
In some embodiments, functions may be performed locally on user equipment device 300. For example, a weight adjustment function, such as a user selection of option 708, may affect weight values stored locally at user equipment device 300. The weight value, among other parameters, may be transmitted to audience management module 328 as needed, for example, when a placement function is to be performed.
Advertising slots that have been added to or removed from the media plan may be visually distinguishable.
Cell 806 is representative of an advertising slot that has been added to an advertiser's media plan, or may be part of a proposed media plan for the advertiser. Cell 806 includes background indicator 808, which may be representative of an audience-related parameter, such as audience composition as in display 700. In addition to background indicator 808, bar 812 may also be indicative of the same audience-related parameter as background indicator 808, thereby providing the user with two types of visual indications. Bar 812 may scale the length of the cell 806, with a minimum and maximum bar length corresponding to a minimum and maximum value of the audience-related parameter. For example, the length of the bar may be indicative of a percentage of actual or projected viewers that fall within a target segment (e.g. “Seinfeld fans ages 25-35”). In some embodiments, bar 812 may be indicative of a different value than background indicator 808. For example, bar 812 may be representative of an audience size, in which zero width represents zero audience available, and a maximum width represents 1.65 standard deviations above a mean value of audience sizes represented. Beyond a particular audience size, bar 812 may max out at this value. This may provide an indication to the user that the advertising slot represented by the cell corresponds to a period in which a highly rated program was or will be aired.
Cell 806 also includes index indicator 810, which may be representative of an actual or projected audience-related parameter, such as audience index (which relates to average audience size and variance), impressions, or gross rating points. In general, index indicator 810 may represent any audience-related parameter that is not confined to a range (such as a percentage).
Cell 814 is representative of an advertising slot that has been not been added to, or has been removed from, an advertiser's media plan. When an available advertising slot is manually selected to be part of, or recommended by audience management system 300 to be part of, an advertising campaign, the advertising slot is referred to herein as being “part of the media plan”. Unlike cell 806, cell 814 is missing a background indicator and an index indicator. Displaying a cell such that audience-related parameters appear to be missing from the cell may serve as an indication to the user that the advertising slot corresponding to the cell is not part of the media plan. Cell 814 still contains at least a minimal amount of information, namely bar 816, which provides an indication of a relative audience size and/or composition. Any suitable method for displaying an indicator that a cell is part of or not part of the media plan may be used. For example, each of the plurality of cells in grid arrangement 802 may all show representations of audiences in the same way, but may contain an additional flag within each cell that indicates whether or not the associated advertising slot is part of the media plan, such as a border around the cell, a checkmark within the cell, a particular shading of the cell, or any suitable combination thereof.
In some embodiments, the user may manually select a particular cell to add or remove its associated advertising slot to the media plan. For example, processing circuitry 206 may receive a user selection of cell 814 from display 800, which causes processing circuitry 206 to generate for display a suitable indicator that cell 814 is selected. The user may then select an “add” function, which adds the advertising slot associated with cell 814 to the media plan. In response, cell 814 may then take on a similar appearance to cell 806, and display a background indicator and an index indicator. Once the advertising slot associated with cell 814 is added to the media plan, processing circuitry may generate a message to be communicated to audience management module 328 that the advertising slot is to be added to the plan. In some embodiments, the manual addition of an advertising slot may override a recommended media plan generated by audience management module 328.
If processing circuitry 206 receives a user selection of, for example, cell 806 from display 800, processing circuitry 206 may generate for display a suitable indicator that cell 806 is selected. Processing circuitry 206 may receive a user selection of a “remove” function, which removes the advertising slot associated with cell 814 to the media plan. In response, cell 806 may then take on a similar appearance to cell 814, in which information is removed from the cell to indicate that it is no longer part of the media plan. Once the advertising slot associated with cell 806 is removed from the media plan, processing circuitry may generate a message to be communicated to audience management module 328 that the advertising slot is to be removed to the plan. In some embodiments, the manual removal of an advertising slot may override a recommended media plan generated by audience management module 328.
In some embodiments, the user may select multiple cells by manually selecting cells in succession. In some embodiments, processing circuitry 206 may receive a user selection of a content source or a time period, which in turn causes processing circuitry 206 to select each cell associated with the content source or time period. For example, a user selection of “Early Fringe” from time period axis 804 may cause processing circuitry 206 to select all cells in that column for that time period, including cells 806 and 814. Processing circuitry 206 may also generate for display a suitable indicator for each of the selected cells indicating that each cell is selected. Processing circuitry 206 may then receive a user selection of a particular function to perform on each of the selected cells. Processing circuitry 206 may execute a function on each of the selected cells, such as adding all cells to the media plan (unless they have been added already), removing all cells from the media plan (unless they have been removed already), displaying additional information for each cell in the form of pop-up overlay, updating a weight value related to an associated advertising slot of each of the selected cells, updating an audience representation for each of the plurality of cells (for example, but receiving more current audience information from audience management module 328), assigning a fixed price value, or any other suitable function in accordance with the embodiments described herein. It is to be understood that each of these functions may also be executed on single cell in response to a user selection of a single cell.
In some embodiments, the user may desire to perform a placement function on less than all available advertising slots. For example, processing circuitry 206 may receive a user selection of a group of cells using any of the method described herein, and indicate that a placement function should be performed on the group of cells. The placement function is performed by audience management module 328, and will be described in greater detail with respect to
In some embodiments, only the highest ranked advertising slots will be added to the media plan. Prior to performing the placement function, the user may specify a weight value or budget limit such that cells are added to the subset in a way that avoid exceeding the weight value or budget limit. For example, audience management module 328 may automatically, without user input, add advertising slots to the subset in order of highest rank, until the budget limit is exceeded by any further additions. Each advertising slot may have an associated cost (e.g. CPM), which is used to determine a total budget for all associated cells added to the subset. Processing circuitry 206 may then indicate to the user, using any suitable indicator, which cells have been automatically selected by the placement function. The user may then confirm the selection of these cells for adding to the media plan, and processing circuitry 206 may then transmit this information back to audience management module 328.
The media plan interface provides the user with additional viewing options to see information that is not shown in the default view.
Display 900 shows additional information related to cell 902 displayed in the form of pop-up overlay 904. Pop-up overlay 904 contains source/time indicator 906, which indicates to the user the content source and time period to which cell 902 corresponds. Pop-up overlay 904 contains information indicators 908, which may provide information relating to the media plan and audience-related parameters pertaining the advertising slot associated with cell 902, the corresponding source, the corresponding time period, or any suitable combination thereof. Pop-up overlay 904 displays an indication of the audience composition for the associated advertising slot, an audience index related to a relative audience size, and a plan weight percentage for the content source “BRAVO” (indicating a total a relative amount of plan weight or budget allocated to advertising slots in of that content source). In general, pop-up overlay 904 provides the user with information about the advertising slot that is otherwise not shown in cell 902.
The media plan interface may provide additional options for adjusting parameters and viewing detailed information related to a media plan.
If processing circuitry 206 receives a user selection of a weight value for a content source other than the default value, element 1004 may be replaced with a value reflecting the weight value. For example, weight values 1008 and 1014 appear instead of the default element. In some embodiments, display 1000 may also display an in-plan weight for a particular content source, such as indicator 1010. For example, indicator 1010 may represent the recommended plan weight for channel 1006, as determined by audience management module 328, and may be displayed in response to a user adding or removing advertising manually.
In some embodiments, a combination of different time periods may be used. For example, daypart indicator 1022 shows cells/advertising slots for “Early Morning”. Hour indicator 1026 shows an hourly breakdown for daypart indicator 1024. For example, in response to a user selection of daypart indicator 1024, processing circuitry 206 may generate for display columns corresponding to hours during “Morning” as an alternative to selecting all cells for that time period. In some embodiments, the user may select advertising slots for individual hours to add to or remove from the plan. Depending on the granularity of the display, a user selection may add all or remove all advertising slots. In other words, a selection of a daypart indicator or a cell corresponding to a daypart/content source combination may be treated as a selection of all time periods within the daypart. Any function executed with respect to the time period (daypart) will affect all shorter time periods (hours) within. In some embodiments, the user may lock a particular advertising slot to prevent a group function from affecting the status of the advertising slot.
The media plan interface may also allow a user view pricing information with respect to available inventory for a media plan.
In some embodiments, the user may select options 1108 and 1112, which provide increased granularity for the content source or time period that each represents. In some embodiments, options 1108 and 1112 may appear in response to a user selection on a content source of content source axis 1106 and a time period of time period axis 1104, respectively. For example, a selection of option 1112 may cause processing circuitry 206 to generate for display an hour view corresponding to “Early Morning”, as described above with respect to
In some embodiments, the user may select display option 1118 to display a particular type of price (e.g. premium rate card, based on standard rates for underlying units in a particular pricing tier, clearance CPM, based on a rate required to clear remaining units to be cleared by a publisher, and fixed CPM, based on a fixed CPM for all impressions in the tier).
A user selection of zoom option 1124 may result in a relative increase or decrease in size of elements appearing in display 1100, or a relative increase or decrease in granularity of the information appearing in display 1100. Zoom option 1124 may be implemented in any suitable fashion, such as a slider, buttons of various sizes, a percentage indicator, or any suitable combination thereof. In some embodiments, if the user selects a “zoom-in” option, this may cause processing circuitry 206 to increase the granularity of the information displayed by, for example, replacing existing time period columns with time period columns corresponding to shorter time periods, as discussed with respect to
To navigate to information that is not currently visible, the user may select scroll options 1128 and 1130 to scroll the display along content source axis 1106 and time period axis 1104, respectively. If the user selects refresh option 1126, processing circuitry may retrieve updated information from audience management module 328, and update the display 1100 with this information as necessary. In some embodiments, the user may select display range option 1122 to show time periods within a particular time range. This may have a similar effect to selecting zoom option 1124 by adjusting the granularity of the plurality of cells in display 1100.
In some embodiments, the user may directly select a cell of the plurality of cells in display 1100. Once the cell is selected, the user may take an action suggestive of a particular function to execute with the respective cell, as discussed above with respect to
At step 1202, the audience management system initiates process 1200. For example, in some embodiments, the audience management system may initiate process 1200 in response to a user request (e.g., received via user input interface 210 (
In some embodiments, the audience management system may be located remotely from a user equipment device (e.g., user equipment devices 302, 304, and/or 306 (
In some embodiments, the audience management system may be located locally. For example, the audience management module may be implemented on a user equipment device (e.g., user equipment device 200 (
In some embodiments, the local audience management system may receive (e.g., via communications network 314) data (e.g., values associated with one or more cells featured in the media plan interface, graphical elements for visual indicators of an audience-related parameter, and/or any other data necessary for generating/performing the embodiments described herein) from one or more remote sources (e.g., media content source 316, media guidance data source 318, user profile server 324, audience management module 328, and/or any location accessible via communications network 314 (
At step 1206, the audience management system identifies a first cell of the plurality of cells. In some embodiments, identifying a first cell may include receiving a user selection of a first cell. For example, the audience management system may detect that a user (e.g., via user input interface 210 (
In some embodiments, as discussed above, the audience management system may be located locally. In such cases, the user input parameter received (e.g., via user input interface 210 (
At step 1208, the audience management system executes a function with respect to a first advertising slot associated with the cell. For example, in response to receiving a user selection (e.g., via user input interface 210 (
For example, in some embodiments, the function may add or remove an advertising slot from an advertiser's media plan and/or otherwise modify a characteristic of the advertising slot associated with the selected cell. As discussed above, in some embodiments, a user may manually select (e.g., via user input interface 210 (
In some embodiments, based on the function executed with respect to the select cell, the audience management system may modify the visual or graphical properties, such as the background indicator and/or index indicator discussed in relation to
In some embodiments, the function may be executed locally (e.g., at user equipment devices 302, 304, and/or 306 (
At step 1210, the audience management system ends process 1200. In some embodiments, the audience management system may return to step 1204 and generate for display a plurality of cells in a grid arrangement in which each cell is associated with an advertising slot as updated by the executed function in step 1208.
In some embodiments, the audience management system may update an audience representation for each of the plurality of cells based on selections associated with different advertising campaigns. Multiple media plans/advertising campaigns may created by the user or generated by the audience management system and stored (e.g., at audience management module 328 (
It is contemplated that the steps or descriptions of
It should also be noted that process 1300 may also be adapted to allocate budget values in numerous ways. For example, in some embodiments, the audience management system may allocate the budget value to various groups such as time periods, content providers, programming types, and/or selected advertising universes. Moreover, in some embodiments, groups may be defined using Boolean expressions (e.g., allocating a portion of a budget value to only a particular time period and a particular content provider).
At step 1302, the audience management system initiates process 1300. For example, in some embodiments, audience management system may initiate process 1300 in response to a user request (e.g., received via user input interface 210 (
At step 1304, the audience management system receives a user selection of a budget value. For example, the user selection may indicate a numerical value (e.g., in monetary units and/or any other suitable measurement standard) that indicate a maximum value for which advertising slots in a media plan must correspond. In some embodiments, the value may be manually entered by a user (e.g., via user input interface 210 (
In some embodiments, the user selection may be received automatically. For example, the advertisement management system may retrieve (e.g., from user profile server 324 (
At step 1306, the media guidance application stores the budget value in memory. For example, the advertisement management system may store the budget value in memory (e.g., located locally at storage 208 (
At step 1308, the media guidance application partitions the budget value into a first partition value and a second partition value, in which each of the first and second partition values is stored in the memory. For example, the audience management system may receive (e.g., via user input interface 210 (
The ratio, percentage, and/or other numerical relationship between the partitions may be based on numerous criteria. For example, the audience management system may receive (e.g., via user input interface 210 (
In some embodiments, the audience management module may retrieve (e.g., via control circuitry 204 (
At step 1310, the audience management system stores a plurality of data structures in the memory. In some embodiments, the audience management system may store (e.g., in storage 204 (
At step 1312, the audience management module defines a plurality of groups, in which each of the plurality of data structures is associated with one or the plurality of groups. For example, the audience management system defines (e.g., via processing circuitry 306 (
At step 1314, the audience management system allocates a portion of the first portion value to each of the plurality of groups. The audience management system allocates (e.g., via processing circuitry 304 (
At step 1316, the audience management system flags, for each of the plurality of groups, at least one data structure associated with the group based on the portion of the first partition value allocated to the group. Flagging may be achieved by storing a particular value in the data structure that indicates to processing circuitry 204 that the data structure is flagged. For example, the audience management system may determine (e.g., via processing circuitry 204 (
In some embodiments, the audience management systems ranks each data structure associated with a particular group based on audience-related criteria, including audience composition, audience size, audience index, impressions, user-specified weight, or any suitable combination thereof. In some embodiments, the audience-related criteria may be included in the data structure associated with each advertising slot. For example, the audience management system may (e.g., via processing circuitry 204 (
At step 1318, the audience management system identifies a subset of unflagged data structures within the plurality of data structures. In some embodiments, the audience management system (e.g., via processing circuitry 204 (
At step 1320, the audience management system flags at least on data structure within the subset based on the second partition value. For example, in some embodiments, the audience management system may search (e.g., via processing circuitry 204 (
In some embodiments, the audience management system may perform (e.g., via processing circuitry 204 (
At step 1322, the audience management system ends process 1300. In some embodiments, the audience management system may return to step 1304 and receive a new budget value associated with a different advertiser (or user, if the advertiser is the user). For example, the audience management system may perform multiple iterations of process 1300 until each budget value for a plurality of advertisers is partitioned and allocated.
It is contemplated that the steps or descriptions of
At step 1402, the audience management system initiates process 1400. For example, in some embodiments, audience management system may initiate process 1400 in response to a user request (e.g., received via user input interface 210 (
At step 1404, the audience management system receives a user selection of a budget value. For example, in some embodiments, step 1404 may correspond to step 1304 (
At step 1406, the media guidance application partitions the budget value into a first budget portion and a second portion. For example, in some embodiments, step 1406 may correspond to step 1308 (
At step 1408, the audience management system allocates the first budget portion across each day in an advertising campaign. In some embodiments, step 1408 may correspond to step 1314 (
At step 1410, the audience management system selects a day in the advertising campaign. For example, the number of days in the advertising campaign and an identification of the individual days in the advertising campaign may be retrieved from a profile associated with the user or with the advertising campaign. For example, the audience management system may cross-reference an identifier (e.g., a serial number, order number, etc.) associated with a user or an advertising campaign in a database (e.g., storage 208 (
The audience management system may input (e.g., via processing circuitry 206 (
At step 1412, the audience management system ranks available advertising slots for the selected day. For example, the audience management system may retrieve (e.g., via processing circuitry 206 (
At step 1414, the audience management system selects the top ranked advertising slot for the selected day. For example, the audience management system may compare each advertising slot available on the selected day to each other to determine (e.g., via processing circuitry 204 (
In some embodiments, the system optimizes the use of inventory across all of the active media plans, enabling the system to optimize selections of advertising slots for multiple advertisers concurrently. In such cases in which a user is preparing media plans for more than one advertiser, the system may rank advertising slots for each media plan based on parameters associated with each media plan (e.g., via processing circuitry 204 (
In some embodiments, the system may generate a single ranked list of advertising slots (e.g., via processing circuitry 204 (FIG. 2)), in which each advertising slot in the list is associated with a particular advertiser. The audience management system may proceed to add advertising slots to a respective media plan of the associated advertiser in order from highest ranking advertising slots to lowest ranking advertising slots.
At step 1416, the audience management system determines whether or not purchasing the selected advertising slot exceeds the allocated budget for the selected day. For example, the audience management system may determine (e.g., via processing circuitry 204 (
In some embodiments, the costs associated with each advertising slot may be continuously monitored and updated. For example, the audience management system may receive a real-time feed indicating the current cost associated with each advertising slot. Additionally or alternatively, the audience management may have access to an algorithm that determines the current cost of the advertising slot based on one or more criteria. For example, an algorithm may indicate that as fewer advertising slots for a particular day remain, the cost to purchase an advertising slot on that day may increase. In such cases, the audience management system (e.g., via processing circuitry 204 (
If the audience management system determines that the cost to purchase the selected advertising slot does not exceed the allocated budget for the selected day, the audience management system proceeds to step 1418. At step 1418, the audience management system purchases (or flags for potential purchasing, depending on user preferences) the selected advertising slot and selects the next highest ranking advertising slot (e.g., as determined in step 1412) before returning to step 1416. If the audience management system determines to that the cost to purchase the selected advertising slot exceeds the allocated budget for the selected day, the audience management system proceeds to step 1420.
At step 1420, the audience management system determines whether or not every day in the advertising campaign has been selected. If not, the audience management system proceeds to step 1422, selects a different day, and returns to step 1412. For example, the audience management system may ensure that the allocation of the first budget portion for each day is used. The audience management system may ensure this by performing multiple iterations of one or more steps of process 1400 (e.g., corresponding to each day of the advertising campaign). If the audience management system determines that every day in the advertising campaign has been selected, the audience management system proceeds to step 1424.
At step 1424, the audience management system ranks all available advertising slots remaining regardless of the day. For example, after the audience management system has allocated the first budget portion to each day, week, or user-specified period of the campaign (e.g., ensuring that at least one advertising slot has been purchased (or flagged for potential purchasing) for each day of the campaign). The audience management system ranks (e.g., via processing circuitry 204 (
At step 1426, the audience management system selects the top ranked advertising slot of any available advertising slot. For example, the audience management system may compare each advertising slot available to all other available advertising slots to determine (e.g., via processing circuitry 204 (
At step 1428, the audience management system determines whether or not purchasing the selected advertising slot exceeds the second budget portion. For example, the audience management system may determine (e.g., via processing circuitry 204 (
At step 1432, the audience management system ends process 1400. In some embodiments, the audience management system may return to step 1404 and receive a new budget value associated with a different user. For example, the audience management system may perform multiple iterations of process 1400 until each budget value for a plurality of users is partitioned and allocated.
It is contemplated that the steps or descriptions of
At step 1502, the audience management system initiates process 1500. For example, in some embodiments, audience management system may initiate process 1500 in response to a user request (e.g., received via user input interface 210 (
At step 1504, the audience management system stores, in a memory, a plurality of data structures, each data structure representing one a plurality of advertising slots. As discussed above in relation to
At step 1506, the audience management system stores, in each of the plurality of data structures a price value associated with a respective advertising slot. For example, as discussed in relation to
At step 1508, the audience management system receives a user selection of a fixed price value. For example, the audience management system may receive (e.g., via user input interface 210 (
At step 1510, the audience management system stores the fixed price value as the price value of a first data structure of the plurality of data structures. For example, the fixed price value associated with the data structure may be stored (e.g., in storage 204 (
At step 1512, the audience management system automatically updates the price value of each of the plurality of data structures without changing the price value of the first data structure. For example, a user (e.g., via user input interface 210 (
For example, once the price is fixed for a first advertising slot, the audience management system may update (e.g., via processing circuitry 204 (
In some embodiments, the projected demand and/or the historical inventory data, projected inventory data, current demand, audience estimates, or any suitable combination thereof may be retrieve from local storage (e.g., storage 208 (
At step 1514, the audience management system ends process 1500. In some embodiments, the audience management system may return to step 1504 and perform another iteration of process 1500 (e.g., associated with another user selection of a fixed price value).
It is contemplated that the steps or descriptions of
At step 1602, the audience management system initiates process 1600. For example, in some embodiments, audience management system may initiate process 1600 in response to a user request (e.g., received via user input interface 210 (
At step 1604, the audience management system associates (e.g., via processing circuitry 204 (
At step 1606, the audience management system receives a user selection of a fixed price value of a first pricing tier. For example, the audience management system may receive (e.g., via user input interface 210 (
At step 1608, the audience management system update a price value for each of the plurality of pricing tiers without changing the price value of the first pricing tier. For example, once the user sets the fixed price for the pricing tier, the audience management system may update a price value for each of the plurality of pricing tiers without changing the price value of the fixed pricing tier.
At step 1610, the audience management system updates each price of the plurality of advertising slots based on an updated price value of an associated pricing tier. The audience management system then updates (e.g., via control circuitry 204 (
At step 1612, the audience management system ends process 1600. In some embodiments, the audience management system may return to step 1604 and perform another iteration of process 1600 (e.g., associated with another user selection of a fixed price value of a first pricing tier).
It is contemplated that the steps or descriptions of
The above-described embodiments of the present disclosure are presented for purposes of illustration and not of limitation, and the present disclosure is limited only by the claims which follow. Furthermore, it should be noted that the features and limitations described in any one embodiment may be applied to any other embodiment herein, and flowcharts or examples relating to one embodiment may be combined with any other embodiment in a suitable manner, done in different orders, or done in parallel. In addition, the systems and methods described herein may be performed in real-time. It should also be noted, the systems and/or methods described above may be applied to, or used in accordance with, other systems and/or methods.
It should be understood that the above steps of the flow diagrams of
The above-described embodiments of the present disclosure are presented for purposes of illustration and not of limitation, and the present disclosure is limited only by the claims which follow.
This application claims the benefit of priority of U.S. Provisional Patent Application No. 61/750,809, filed Jan. 10, 2013, which is hereby incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3440427 | Kammer | Apr 1969 | A |
| 3492577 | Reiter et al. | Jan 1970 | A |
| 3493674 | Houghton | Feb 1970 | A |
| 3729581 | Anderson | Apr 1973 | A |
| 3833757 | Kirk, Jr. et al. | Sep 1974 | A |
| 3891792 | Kimura | Jun 1975 | A |
| 3936868 | Thorpe | Feb 1976 | A |
| 3996583 | Hutt et al. | Dec 1976 | A |
| 4004085 | Makino et al. | Jan 1977 | A |
| 4016361 | Pandey | Apr 1977 | A |
| 4026555 | Kirschner et al. | May 1977 | A |
| 4031548 | Kato et al. | Jun 1977 | A |
| 4052719 | Hutt et al. | Oct 1977 | A |
| 4058830 | Guinet et al. | Nov 1977 | A |
| 4079419 | Siegle et al. | Mar 1978 | A |
| 4081753 | Miller | Mar 1978 | A |
| 4081754 | Jackson | Mar 1978 | A |
| 4096524 | Scott | Jun 1978 | A |
| 4134127 | Campioni | Jan 1979 | A |
| 4139860 | Micic et al. | Feb 1979 | A |
| 4150254 | Schussler et al. | Apr 1979 | A |
| 4156850 | Beyers, Jr. | May 1979 | A |
| 4161728 | Insam | Jul 1979 | A |
| 4162513 | Beyers, Jr. et al. | Jul 1979 | A |
| 4170782 | Miller | Oct 1979 | A |
| 4186413 | Mortimer | Jan 1980 | A |
| 4203130 | Doumit et al. | May 1980 | A |
| 4205343 | Barrett | May 1980 | A |
| 4218698 | Bart et al. | Aug 1980 | A |
| 4228543 | Jackson | Oct 1980 | A |
| 4231031 | Crowther et al. | Oct 1980 | A |
| 4233628 | Ciciora | Nov 1980 | A |
| 4249211 | Baba et al. | Feb 1981 | A |
| 4249213 | Imaide et al. | Feb 1981 | A |
| 4261006 | Weintraub et al. | Apr 1981 | A |
| 4264924 | Freeman | Apr 1981 | A |
| 4264925 | Freeman et al. | Apr 1981 | A |
| 4270145 | Farina | May 1981 | A |
| 4271532 | Wine | Jun 1981 | A |
| 4276597 | Dissly et al. | Jun 1981 | A |
| 4283787 | Chambers | Aug 1981 | A |
| 4288809 | Yabe | Sep 1981 | A |
| 4290142 | Schnee et al. | Sep 1981 | A |
| 4305101 | Yarbrough et al. | Dec 1981 | A |
| 4329684 | Monteath et al. | May 1982 | A |
| 4331974 | Cogswell et al. | May 1982 | A |
| 4337480 | Bourassin et al. | Jun 1982 | A |
| 4337483 | Guillou | Jun 1982 | A |
| 4344090 | Belisomi et al. | Aug 1982 | A |
| 4367559 | Tults | Jan 1983 | A |
| 4375651 | Templin et al. | Mar 1983 | A |
| 4381522 | Lambert | Apr 1983 | A |
| 4388645 | Cox et al. | Jun 1983 | A |
| 4390901 | Keiser | Jun 1983 | A |
| 4393376 | Thomas | Jul 1983 | A |
| 4405946 | Knight | Sep 1983 | A |
| 4412244 | Shanley, II | Oct 1983 | A |
| 4413281 | Thonnart | Nov 1983 | A |
| 4420769 | Novak | Dec 1983 | A |
| 4425579 | Merrell | Jan 1984 | A |
| 4425581 | Schweppe et al. | Jan 1984 | A |
| 4429385 | Cichelli et al. | Jan 1984 | A |
| 4439784 | Furukawa et al. | Mar 1984 | A |
| 4449249 | Price | May 1984 | A |
| 4456925 | Skerlos et al. | Jun 1984 | A |
| 4466017 | Banker | Aug 1984 | A |
| 4477830 | Lindman et al. | Oct 1984 | A |
| 4488179 | Kru/ ger et al. | Dec 1984 | A |
| 4495654 | Deiss | Jan 1985 | A |
| 4496171 | Cherry | Jan 1985 | A |
| 4496976 | Swanson et al. | Jan 1985 | A |
| 4510623 | Bonneau et al. | Apr 1985 | A |
| 4520404 | Von Kohorn | May 1985 | A |
| 4523228 | Banker | Jun 1985 | A |
| 4527194 | Sirazi | Jul 1985 | A |
| 4531020 | Wechselberger et al. | Jul 1985 | A |
| 4533910 | Sukonick et al. | Aug 1985 | A |
| 4536791 | Campbell et al. | Aug 1985 | A |
| 4547804 | Greenberg | Oct 1985 | A |
| 4554584 | Elam et al. | Nov 1985 | A |
| 4555775 | Pike | Nov 1985 | A |
| 4566034 | Harger et al. | Jan 1986 | A |
| 4573072 | Freeman | Feb 1986 | A |
| 4587520 | Astle | May 1986 | A |
| 4595951 | Filliman | Jun 1986 | A |
| 4595952 | Filliman | Jun 1986 | A |
| 4598288 | Yarbrough et al. | Jul 1986 | A |
| 4602279 | Freeman | Jul 1986 | A |
| 4605964 | Chard | Aug 1986 | A |
| 4605973 | Von Kohorn | Aug 1986 | A |
| 4620229 | Amano et al. | Oct 1986 | A |
| 4622545 | Atkinson | Nov 1986 | A |
| 4635109 | Comeau | Jan 1987 | A |
| 4635121 | Hoffman et al. | Jan 1987 | A |
| 4641205 | Beyers, Jr. | Feb 1987 | A |
| 4677466 | Lert, Jr. et al. | Jun 1987 | A |
| 4685131 | Horne | Aug 1987 | A |
| 4689022 | Peers et al. | Aug 1987 | A |
| 4691351 | Hayashi et al. | Sep 1987 | A |
| 4694490 | Harvey et al. | Sep 1987 | A |
| 4701794 | Froling et al. | Oct 1987 | A |
| 4704725 | Harvey et al. | Nov 1987 | A |
| 4706121 | Young | Nov 1987 | A |
| 4712105 | Kohler | Dec 1987 | A |
| 4714919 | Foster | Dec 1987 | A |
| 4718107 | Hayes | Jan 1988 | A |
| RE32632 | Atkinson | Mar 1988 | E |
| 4745549 | Hashimoto | May 1988 | A |
| 4748618 | Brown et al. | May 1988 | A |
| 4750036 | Martinez | Jun 1988 | A |
| 4750213 | Novak | Jun 1988 | A |
| 4751578 | Reiter et al. | Jun 1988 | A |
| 4754326 | Kram et al. | Jun 1988 | A |
| 4768228 | Clupper et al. | Aug 1988 | A |
| 4772882 | Mical | Sep 1988 | A |
| 4775935 | Yourick | Oct 1988 | A |
| 4785408 | Britton et al. | Nov 1988 | A |
| 4787063 | Muguet | Nov 1988 | A |
| 4812834 | Wells | Mar 1989 | A |
| 4814883 | Perine et al. | Mar 1989 | A |
| 4821102 | Ichikawa et al. | Apr 1989 | A |
| 4821211 | Torres | Apr 1989 | A |
| 4829558 | Welsh | May 1989 | A |
| 4847604 | Doyle | Jul 1989 | A |
| 4847700 | Freeman | Jul 1989 | A |
| 4857999 | Welsh | Aug 1989 | A |
| 4862268 | Campbell et al. | Aug 1989 | A |
| 4864429 | Eigeldinger et al. | Sep 1989 | A |
| 4873623 | Lane et al. | Oct 1989 | A |
| 4882732 | Kaminaga | Nov 1989 | A |
| 4884223 | Ingle et al. | Nov 1989 | A |
| 4888796 | Olivo, Jr. | Dec 1989 | A |
| 4890320 | Monslow et al. | Dec 1989 | A |
| 4890321 | Seth-Smith et al. | Dec 1989 | A |
| 4894789 | Yee | Jan 1990 | A |
| 4899136 | Beard et al. | Feb 1990 | A |
| 4899139 | Ishimochi et al. | Feb 1990 | A |
| 4905094 | Pocock et al. | Feb 1990 | A |
| 4908707 | Kinghorn | Mar 1990 | A |
| 4908713 | Levine | Mar 1990 | A |
| 4908859 | Bennett et al. | Mar 1990 | A |
| 4914517 | Duffield | Apr 1990 | A |
| 4914732 | Henderson et al. | Apr 1990 | A |
| 4930158 | Vogel | May 1990 | A |
| 4930160 | Vogel | May 1990 | A |
| 4931783 | Atkinson | Jun 1990 | A |
| 4935865 | Rowe et al. | Jun 1990 | A |
| 4937821 | Boulton | Jun 1990 | A |
| 4937863 | Robert et al. | Jun 1990 | A |
| 4939507 | Beard et al. | Jul 1990 | A |
| 4942391 | Kikuta | Jul 1990 | A |
| 4959720 | Duffield et al. | Sep 1990 | A |
| 4963994 | Levine | Oct 1990 | A |
| 4977455 | Young | Dec 1990 | A |
| 4987486 | Johnson et al. | Jan 1991 | A |
| 4991011 | Johnson et al. | Feb 1991 | A |
| 4991012 | Yoshino | Feb 1991 | A |
| 4992940 | Dworkin | Feb 1991 | A |
| 4995078 | Monslow et al. | Feb 1991 | A |
| 4996642 | Hey | Feb 1991 | A |
| 4998171 | Kim et al. | Mar 1991 | A |
| 5008853 | Bly et al. | Apr 1991 | A |
| 5014125 | Pocock et al. | May 1991 | A |
| 5027400 | Baji et al. | Jun 1991 | A |
| 5036314 | Barillari et al. | Jul 1991 | A |
| 5038211 | Hallenbeck | Aug 1991 | A |
| 5045947 | Beery | Sep 1991 | A |
| 5047867 | Strubbe et al. | Sep 1991 | A |
| 5058160 | Banker et al. | Oct 1991 | A |
| 5062060 | Kolnick | Oct 1991 | A |
| 5068734 | Beery | Nov 1991 | A |
| 5072412 | Henderson, Jr. et al. | Dec 1991 | A |
| 5075771 | Hashimoto | Dec 1991 | A |
| 5083800 | Lockton | Jan 1992 | A |
| 5091785 | Canfield et al. | Feb 1992 | A |
| 5093921 | Bevins, Jr. | Mar 1992 | A |
| 5099319 | Esch et al. | Mar 1992 | A |
| 5103314 | Keenan | Apr 1992 | A |
| 5105184 | Pirani et al. | Apr 1992 | A |
| 5119188 | McCalley et al. | Jun 1992 | A |
| 5121476 | Yee | Jun 1992 | A |
| 5123046 | Levine | Jun 1992 | A |
| 5126851 | Yoshimura et al. | Jun 1992 | A |
| 5148154 | MacKay et al. | Sep 1992 | A |
| 5151782 | Ferraro | Sep 1992 | A |
| 5151789 | Young | Sep 1992 | A |
| 5155591 | Wachob | Oct 1992 | A |
| 5155806 | Hoeber et al. | Oct 1992 | A |
| 5157768 | Hoeber et al. | Oct 1992 | A |
| 5161023 | Keenan | Nov 1992 | A |
| 5162905 | Itoh et al. | Nov 1992 | A |
| 5170388 | Endoh | Dec 1992 | A |
| 5172111 | Olivo, Jr. | Dec 1992 | A |
| 5172413 | Bradley et al. | Dec 1992 | A |
| 5177604 | Martinez | Jan 1993 | A |
| 5179654 | Richards et al. | Jan 1993 | A |
| 5195092 | Wilson et al. | Mar 1993 | A |
| 5200823 | Yoneda et al. | Apr 1993 | A |
| 5204897 | Wyman | Apr 1993 | A |
| 5206722 | Kwan | Apr 1993 | A |
| 5210611 | Yee et al. | May 1993 | A |
| 5212553 | Maruoka | May 1993 | A |
| 5214622 | Nemoto et al. | May 1993 | A |
| 5216515 | Steele et al. | Jun 1993 | A |
| 5220420 | Hoarty et al. | Jun 1993 | A |
| 5223924 | Strubbe | Jun 1993 | A |
| 5227874 | Von Kohorn | Jul 1993 | A |
| 5231493 | Apitz | Jul 1993 | A |
| RE34340 | Freeman | Aug 1993 | E |
| 5233423 | Jernigan et al. | Aug 1993 | A |
| 5233654 | Harvey et al. | Aug 1993 | A |
| 5235415 | Bonicel et al. | Aug 1993 | A |
| 5236199 | Thompson, Jr. | Aug 1993 | A |
| 5237411 | Fink et al. | Aug 1993 | A |
| 5237417 | Hayashi et al. | Aug 1993 | A |
| 5237418 | Kaneko | Aug 1993 | A |
| 5239540 | Rovira et al. | Aug 1993 | A |
| 5245420 | Harney et al. | Sep 1993 | A |
| 5247347 | Litteral et al. | Sep 1993 | A |
| 5247364 | Banker et al. | Sep 1993 | A |
| 5247580 | Kimura et al. | Sep 1993 | A |
| 5253066 | Vogel | Oct 1993 | A |
| 5253067 | Chaney et al. | Oct 1993 | A |
| 5260778 | Kauffman et al. | Nov 1993 | A |
| 5260788 | Takano et al. | Nov 1993 | A |
| 5260999 | Wyman | Nov 1993 | A |
| 5283639 | Esch et al. | Feb 1994 | A |
| 5283819 | Glick et al. | Feb 1994 | A |
| 5285278 | Holman | Feb 1994 | A |
| 5301028 | Banker et al. | Apr 1994 | A |
| 5307173 | Yuen et al. | Apr 1994 | A |
| 5311423 | Clark | May 1994 | A |
| 5313282 | Hayashi | May 1994 | A |
| 5317403 | Keenan | May 1994 | A |
| 5319445 | Fitts | Jun 1994 | A |
| 5323234 | Kawasaki | Jun 1994 | A |
| 5323240 | Amano et al. | Jun 1994 | A |
| 5325183 | Rhee | Jun 1994 | A |
| 5325423 | Lewis | Jun 1994 | A |
| 5335277 | Harvey et al. | Aug 1994 | A |
| 5343239 | Lappington et al. | Aug 1994 | A |
| 5347167 | Singh | Sep 1994 | A |
| 5347632 | Filepp et al. | Sep 1994 | A |
| 5351075 | Herz et al. | Sep 1994 | A |
| 5353121 | Young et al. | Oct 1994 | A |
| 5357276 | Banker et al. | Oct 1994 | A |
| 5359367 | Stockill | Oct 1994 | A |
| 5359601 | Wasilewski et al. | Oct 1994 | A |
| 5365282 | Levine | Nov 1994 | A |
| 5367316 | Ikezaki | Nov 1994 | A |
| 5367330 | Haave et al. | Nov 1994 | A |
| 5373288 | Blahut | Dec 1994 | A |
| 5374942 | Gilligan et al. | Dec 1994 | A |
| 5374951 | Welsh | Dec 1994 | A |
| 5377317 | Bates et al. | Dec 1994 | A |
| 5377319 | Kitahara et al. | Dec 1994 | A |
| 5382983 | Kwoh et al. | Jan 1995 | A |
| 5384910 | Torres | Jan 1995 | A |
| 5387945 | Takeuchi | Feb 1995 | A |
| 5398074 | Duffield et al. | Mar 1995 | A |
| 5404393 | Remillard | Apr 1995 | A |
| 5410326 | Goldstein | Apr 1995 | A |
| 5410343 | Coddington et al. | Apr 1995 | A |
| 5410344 | Graves et al. | Apr 1995 | A |
| 5410367 | Zahavi et al. | Apr 1995 | A |
| 5412720 | Hoarty | May 1995 | A |
| 5416508 | Sakuma et al. | May 1995 | A |
| 5424770 | Schmelzer et al. | Jun 1995 | A |
| 5425101 | Woo et al. | Jun 1995 | A |
| 5432561 | Strubbe | Jul 1995 | A |
| 5434626 | Hayashi et al. | Jul 1995 | A |
| 5436676 | Pint et al. | Jul 1995 | A |
| 5438372 | Tsumori et al. | Aug 1995 | A |
| 5440678 | Eisen et al. | Aug 1995 | A |
| 5444499 | Saitoh | Aug 1995 | A |
| 5446919 | Wilkins | Aug 1995 | A |
| 5452012 | Saitoh | Sep 1995 | A |
| 5459522 | Pint | Oct 1995 | A |
| 5461415 | Wolf et al. | Oct 1995 | A |
| 5465113 | Gilboy | Nov 1995 | A |
| 5465385 | Ohga et al. | Nov 1995 | A |
| 5469206 | Strubbe et al. | Nov 1995 | A |
| 5477262 | Banker et al. | Dec 1995 | A |
| 5479266 | Young et al. | Dec 1995 | A |
| 5479268 | Young et al. | Dec 1995 | A |
| 5479497 | Kovarik | Dec 1995 | A |
| 5481296 | Cragun et al. | Jan 1996 | A |
| 5483278 | Strubbe et al. | Jan 1996 | A |
| 5485197 | Hoarty | Jan 1996 | A |
| 5485219 | Woo | Jan 1996 | A |
| 5485221 | Banker et al. | Jan 1996 | A |
| 5488409 | Yuen et al. | Jan 1996 | A |
| 5495295 | Long | Feb 1996 | A |
| 5502504 | Marshall et al. | Mar 1996 | A |
| 5515098 | Carles | May 1996 | A |
| 5523794 | Mankovitz et al. | Jun 1996 | A |
| 5523796 | Marshall et al. | Jun 1996 | A |
| 5524195 | Clanton, III et al. | Jun 1996 | A |
| 5526034 | Hoarty et al. | Jun 1996 | A |
| 5528304 | Cherrick et al. | Jun 1996 | A |
| 5532735 | Blahut et al. | Jul 1996 | A |
| 5532754 | Young et al. | Jul 1996 | A |
| 5534911 | Levitan | Jul 1996 | A |
| 5537141 | Harper et al. | Jul 1996 | A |
| 5539822 | Lett | Jul 1996 | A |
| 5541662 | Adams et al. | Jul 1996 | A |
| 5541738 | Mankovitz | Jul 1996 | A |
| 5550576 | Klosterman | Aug 1996 | A |
| 5557338 | Maze et al. | Sep 1996 | A |
| 5557721 | Fite et al. | Sep 1996 | A |
| 5559548 | Davis et al. | Sep 1996 | A |
| 5559549 | Hendricks et al. | Sep 1996 | A |
| 5559550 | Mankovitz | Sep 1996 | A |
| 5559942 | Gough et al. | Sep 1996 | A |
| 5561471 | Kim | Oct 1996 | A |
| 5570295 | Isenberg et al. | Oct 1996 | A |
| 5572442 | Schulhof et al. | Nov 1996 | A |
| 5574962 | Fardeau et al. | Nov 1996 | A |
| 5579055 | Hamilton et al. | Nov 1996 | A |
| 5581479 | McLaughlin et al. | Dec 1996 | A |
| 5582364 | Trulin et al. | Dec 1996 | A |
| 5583560 | Florin et al. | Dec 1996 | A |
| 5583563 | Wanderscheid 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 |
| 5589892 | Knee et al. | Dec 1996 | A |
| 5592551 | Lett et al. | Jan 1997 | A |
| 5594509 | Florin et al. | Jan 1997 | A |
| 5596373 | White et al. | Jan 1997 | A |
| 5600364 | Hendricks et al. | Feb 1997 | A |
| 5600366 | Schulman | Feb 1997 | A |
| 5600573 | Hendricks et al. | Feb 1997 | A |
| 5602582 | Wanderscheid et al. | Feb 1997 | A |
| 5602596 | Claussen et al. | Feb 1997 | A |
| 5602597 | Bertram | Feb 1997 | A |
| 5606374 | Bertram | Feb 1997 | A |
| 5610653 | Abecassis | Mar 1997 | A |
| 5617565 | Augenbraun et al. | Apr 1997 | A |
| 5619247 | Russo | Apr 1997 | A |
| 5619249 | Billock et al. | Apr 1997 | A |
| 5619274 | Roop et al. | Apr 1997 | A |
| 5621456 | Florin et al. | Apr 1997 | A |
| 5623613 | Rowe et al. | Apr 1997 | A |
| 5627940 | Rohra et al. | May 1997 | A |
| 5629733 | Youman et al. | May 1997 | A |
| 5630119 | Aristides et al. | May 1997 | A |
| 5631995 | Weissensteiner et al. | May 1997 | A |
| 5633683 | Rosengren et al. | May 1997 | A |
| 5635978 | Alten et al. | Jun 1997 | A |
| 5635979 | Kostreski et al. | Jun 1997 | A |
| 5635989 | Rothmuller | Jun 1997 | A |
| 5636346 | Saxe | Jun 1997 | A |
| 5640501 | Turpin | Jun 1997 | A |
| 5640577 | Scharmer | Jun 1997 | A |
| 5642153 | Chaney et al. | Jun 1997 | A |
| 5648813 | Tanigawa et al. | Jul 1997 | A |
| 5648824 | Dunn et al. | Jul 1997 | A |
| 5650826 | Eitz | Jul 1997 | A |
| 5650831 | Farwell | Jul 1997 | A |
| 5652613 | Lazarus et al. | Jul 1997 | A |
| 5652615 | Bryant et al. | Jul 1997 | A |
| 5654748 | Matthews, III | Aug 1997 | A |
| 5654886 | Zereski, Jr. et al. | Aug 1997 | A |
| 5657072 | Aristides et al. | Aug 1997 | A |
| 5657091 | Bertram | Aug 1997 | A |
| 5659350 | Hendricks et al. | Aug 1997 | A |
| 5659366 | Kerman | Aug 1997 | A |
| 5661516 | Carles | Aug 1997 | A |
| 5661517 | Budow et al. | Aug 1997 | A |
| 5663757 | Morales | Sep 1997 | A |
| 5664111 | Nahan et al. | Sep 1997 | A |
| 5666293 | Metz et al. | Sep 1997 | A |
| 5666498 | Amro | Sep 1997 | A |
| 5666645 | Thomas et al. | Sep 1997 | A |
| 5671276 | Eyer et al. | Sep 1997 | A |
| 5671411 | Watts et al. | Sep 1997 | A |
| 5675390 | Schindler et al. | Oct 1997 | A |
| 5675752 | Scott et al. | Oct 1997 | A |
| 5677708 | Matthews, III et al. | Oct 1997 | A |
| 5682195 | Hendricks et al. | Oct 1997 | A |
| 5682206 | Wehmeyer et al. | Oct 1997 | A |
| 5687331 | Volk et al. | Nov 1997 | A |
| 5689648 | Diaz et al. | Nov 1997 | A |
| 5689666 | Berquist et al. | Nov 1997 | A |
| 5692214 | Levine | Nov 1997 | A |
| 5694163 | Harrison | Dec 1997 | A |
| 5694176 | Bruette et al. | Dec 1997 | A |
| 5694381 | Sako | Dec 1997 | A |
| 5696905 | Reimer et al. | Dec 1997 | A |
| 5699107 | Lawler et al. | Dec 1997 | A |
| 5699125 | Rzeszewski et al. | Dec 1997 | A |
| 5708478 | Tognazzini | Jan 1998 | A |
| 5710601 | Marshall et al. | Jan 1998 | A |
| 5710815 | Ming et al. | Jan 1998 | A |
| 5715314 | Payne et al. | Feb 1998 | A |
| 5715399 | Bezos | Feb 1998 | A |
| 5717452 | Janin et al. | Feb 1998 | A |
| 5721829 | Dunn et al. | Feb 1998 | A |
| 5724521 | Dedrick | Mar 1998 | A |
| 5724525 | Beyers, II et al. | Mar 1998 | A |
| 5727060 | Young | Mar 1998 | A |
| 5727163 | Bezos | Mar 1998 | A |
| 5731844 | Rauch et al. | Mar 1998 | A |
| 5734444 | Yoshinobu | Mar 1998 | A |
| 5734853 | Hendricks et al. | Mar 1998 | A |
| 5734893 | Li et al. | Mar 1998 | A |
| 5737028 | Bertram et al. | Apr 1998 | A |
| 5737030 | Hong et al. | Apr 1998 | A |
| 5740549 | Reilly et al. | Apr 1998 | A |
| 5751282 | Girard et al. | May 1998 | A |
| 5752159 | Faust et al. | May 1998 | A |
| 5752160 | Dunn | May 1998 | A |
| 5754258 | Hanaya et al. | May 1998 | A |
| 5754771 | Epperson et al. | May 1998 | A |
| 5754939 | Herz et al. | May 1998 | A |
| 5757417 | Aras et al. | May 1998 | A |
| 5758257 | Herz et al. | May 1998 | A |
| 5758259 | Lawler | May 1998 | A |
| 5760821 | Ellis et al. | Jun 1998 | A |
| 5761372 | Yoshinobu et al. | Jun 1998 | A |
| 5761601 | Nemirofsky et al. | Jun 1998 | A |
| 5768528 | Stumm | Jun 1998 | A |
| 5774170 | Hite et al. | Jun 1998 | A |
| 5774357 | Hoffberg et al. | Jun 1998 | A |
| 5774534 | Mayer | Jun 1998 | A |
| 5774887 | Wolff et al. | Jun 1998 | A |
| 5778182 | Cathey et al. | Jul 1998 | A |
| 5781226 | Sheehan | Jul 1998 | A |
| 5781245 | Van Der Weij et al. | Jul 1998 | A |
| 5781246 | Alten et al. | Jul 1998 | A |
| 5784258 | Quinn | Jul 1998 | A |
| 5790202 | Kummer et al. | Aug 1998 | A |
| 5790426 | Robinson | Aug 1998 | A |
| 5793438 | Bedard | Aug 1998 | A |
| 5793964 | Rogers et al. | Aug 1998 | A |
| 5798785 | Hendricks et al. | Aug 1998 | A |
| 5801747 | Bedard | Sep 1998 | A |
| 5801785 | Crump et al. | Sep 1998 | A |
| 5801787 | Schein et al. | Sep 1998 | A |
| 5802284 | Karlton et al. | Sep 1998 | A |
| 5805154 | Brown | Sep 1998 | A |
| 5805167 | van Cruyningen | Sep 1998 | A |
| 5805235 | Bedard | Sep 1998 | A |
| 5805763 | Lawler et al. | Sep 1998 | A |
| 5805804 | Laursen et al. | Sep 1998 | A |
| 5808608 | Young et al. | Sep 1998 | A |
| 5808694 | Usui et al. | Sep 1998 | A |
| 5809204 | Young et al. | Sep 1998 | A |
| 5812205 | Milnes et al. | Sep 1998 | A |
| 5815145 | Matthews, III | 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 |
| 5818541 | Matsuura et al. | Oct 1998 | A |
| 5819019 | Nelson | Oct 1998 | A |
| 5819156 | Belmont | Oct 1998 | A |
| 5819284 | Farber et al. | Oct 1998 | A |
| 5822123 | Davis et al. | Oct 1998 | A |
| 5828402 | Collings | Oct 1998 | A |
| 5828420 | Marshall et al. | Oct 1998 | A |
| 5828839 | Moncreiff | Oct 1998 | A |
| 5828945 | Klosterman | Oct 1998 | A |
| 5830068 | Brenner et al. | Nov 1998 | A |
| 5838314 | Neel et al. | Nov 1998 | A |
| 5842010 | Jain et al. | Nov 1998 | A |
| 5842199 | Miller et al. | Nov 1998 | A |
| 5844620 | Coleman et al. | Dec 1998 | A |
| 5848352 | Dougherty et al. | Dec 1998 | A |
| 5848396 | Gerace | Dec 1998 | A |
| 5848397 | Marsh et al. | Dec 1998 | A |
| 5850218 | LaJoie et al. | Dec 1998 | A |
| 5862292 | Kubota et al. | Jan 1999 | A |
| 5867226 | Wehmeyer et al. | Feb 1999 | A |
| 5867227 | Yamaguchi | Feb 1999 | A |
| 5872588 | Aras et al. | Feb 1999 | A |
| 5874985 | Matthews, III | Feb 1999 | A |
| 5875108 | Hoffberg et al. | Feb 1999 | A |
| 5880768 | Lemmons et al. | Mar 1999 | A |
| 5883677 | Hofmann | Mar 1999 | A |
| 5886691 | Furuya et al. | Mar 1999 | A |
| 5886731 | Ebisawa | Mar 1999 | A |
| 5892498 | Marshall et al. | Apr 1999 | A |
| 5892535 | Allen et al. | Apr 1999 | A |
| 5900905 | Shoff et al. | May 1999 | A |
| 5903314 | Niijima et al. | May 1999 | A |
| 5903545 | Sabourin et al. | May 1999 | A |
| 5903816 | Broadwin et al. | May 1999 | A |
| 5905497 | Vaughan et al. | May 1999 | A |
| 5907323 | Lawler et al. | May 1999 | A |
| 5907366 | Farmer et al. | May 1999 | A |
| 5914746 | Matthews, III et al. | Jun 1999 | A |
| 5917481 | Rzeszewski et al. | Jun 1999 | A |
| 5917830 | Chen et al. | Jun 1999 | A |
| 5918014 | Robinson | Jun 1999 | A |
| 5920700 | Gordon et al. | Jul 1999 | A |
| 5929849 | Kikinis | Jul 1999 | A |
| 5929850 | Broadwin et al. | Jul 1999 | A |
| 5936679 | Kasahara et al. | Aug 1999 | A |
| 5940073 | Klosterman et al. | Aug 1999 | A |
| 5940572 | Balaban et al. | Aug 1999 | A |
| 5945988 | Williams et al. | Aug 1999 | A |
| 5951642 | Onoe et al. | Sep 1999 | A |
| 5959688 | Schein et al. | Sep 1999 | A |
| 5960411 | Hartman et al. | Sep 1999 | A |
| 5973683 | Cragun et al. | Oct 1999 | A |
| 5974222 | Yuen et al. | Oct 1999 | A |
| 5977964 | Williams et al. | Nov 1999 | A |
| 5986650 | Ellis et al. | Nov 1999 | A |
| 5988078 | Levine | Nov 1999 | A |
| 5990890 | Etheredge | Nov 1999 | A |
| 5990927 | Hendricks et al. | Nov 1999 | A |
| 5999912 | Wodarz et al. | Dec 1999 | A |
| 6002393 | Hite et al. | Dec 1999 | A |
| 6002394 | Schein et al. | Dec 1999 | A |
| 6005562 | Shiga et al. | Dec 1999 | A |
| 6005565 | Legall et al. | Dec 1999 | A |
| 6005597 | Barrett et al. | Dec 1999 | A |
| 6006257 | Slezak | Dec 1999 | A |
| 6008802 | Iki et al. | Dec 1999 | A |
| 6011546 | Bertram | Jan 2000 | A |
| 6014137 | Burns | Jan 2000 | A |
| 6014502 | Moraes | Jan 2000 | A |
| 6016141 | Knudson et al. | Jan 2000 | A |
| 6018372 | Etheredge | Jan 2000 | A |
| 6018768 | Ullman et al. | Jan 2000 | A |
| 6020883 | Herz et al. | Feb 2000 | A |
| 6020929 | Marshall et al. | Feb 2000 | A |
| 6025837 | Matthews, III et al. | Feb 2000 | A |
| 6025886 | Koda | Feb 2000 | A |
| 6028599 | Yuen et al. | Feb 2000 | A |
| 6029045 | Picco et al. | Feb 2000 | A |
| 6029195 | Herz | Feb 2000 | A |
| 6035304 | Machida et al. | Mar 2000 | A |
| 6047317 | Bisdikian et al. | Apr 2000 | A |
| 6049824 | Simonin | Apr 2000 | A |
| 6052145 | Macrae et al. | Apr 2000 | A |
| 6061060 | Berry et al. | May 2000 | A |
| 6061097 | Satterfield | May 2000 | A |
| 6064376 | Berezowski et al. | May 2000 | A |
| 6064980 | Jacobi et al. | May 2000 | A |
| 6067303 | Aaker et al. | May 2000 | A |
| 6072460 | Marshall et al. | Jun 2000 | A |
| 6075526 | Rothmuller | Jun 2000 | A |
| 6075551 | Berezowski et al. | Jun 2000 | A |
| 6075575 | Schein et al. | Jun 2000 | A |
| 6078348 | Klosterman et al. | Jun 2000 | A |
| 6081750 | Hoffberg et al. | Jun 2000 | A |
| 6088722 | Herz et al. | Jul 2000 | A |
| 6091883 | Artigalas et al. | Jul 2000 | A |
| 6098065 | Skillen et al. | Aug 2000 | A |
| 6108042 | Adams et al. | Aug 2000 | A |
| 6111614 | Mugura et al. | Aug 2000 | A |
| 6112186 | Bergh et al. | Aug 2000 | A |
| 6115057 | Kwoh et al. | Sep 2000 | A |
| 6118492 | Milnes et al. | Sep 2000 | A |
| 6119098 | Guyot et al. | Sep 2000 | A |
| 6119101 | Peckover | Sep 2000 | A |
| 6122011 | Dias et al. | Sep 2000 | A |
| 6125230 | Yaginuma | Sep 2000 | A |
| 6133909 | Schein et al. | Oct 2000 | A |
| 6141003 | Chor et al. | Oct 2000 | A |
| 6147714 | Terasawa et al. | Nov 2000 | A |
| 6151059 | Schein et al. | Nov 2000 | A |
| 6154203 | Yuen et al. | Nov 2000 | A |
| 6157413 | Hanafee et al. | Dec 2000 | A |
| 6160545 | Eyer et al. | Dec 2000 | A |
| 6160546 | Thompson et al. | Dec 2000 | A |
| 6160570 | Sitnik | Dec 2000 | A |
| 6163316 | Killian | Dec 2000 | A |
| 6169542 | Hooks et al. | Jan 2001 | B1 |
| 6172674 | Etheredge | Jan 2001 | B1 |
| 6172677 | Stautner et al. | Jan 2001 | B1 |
| 6173271 | Goodman et al. | Jan 2001 | B1 |
| 6177931 | Alexander et al. | Jan 2001 | B1 |
| 6178446 | Gerszberg et al. | Jan 2001 | B1 |
| 6181335 | Hendricks et al. | Jan 2001 | B1 |
| 6186443 | Shaffer | Feb 2001 | B1 |
| 6191780 | Martin et al. | Feb 2001 | B1 |
| 6202212 | Sturgeon et al. | Mar 2001 | B1 |
| 6209129 | Carr et al. | Mar 2001 | B1 |
| 6209130 | Rector, Jr. et al. | Mar 2001 | B1 |
| 6216264 | Maze et al. | Apr 2001 | B1 |
| 6239794 | Yuen et al. | May 2001 | B1 |
| 6240555 | Shoff et al. | May 2001 | B1 |
| 6253203 | O'Flaherty et al. | Jun 2001 | B1 |
| 6256071 | Hiroi | Jul 2001 | B1 |
| 6256785 | Klappert et al. | Jul 2001 | B1 |
| 6257268 | Hope et al. | Jul 2001 | B1 |
| 6262721 | Tsukidate et al. | Jul 2001 | B1 |
| 6263501 | Schein et al. | Jul 2001 | B1 |
| 6263507 | Ahmad et al. | Jul 2001 | B1 |
| 6268849 | Boyer et al. | Jul 2001 | B1 |
| 6269361 | Davis et al. | Jul 2001 | B1 |
| 6275268 | Ellis et al. | Aug 2001 | B1 |
| 6279157 | Takasu | Aug 2001 | B1 |
| 6285713 | Nakaya et al. | Sep 2001 | B1 |
| 6286140 | Ivanyi | Sep 2001 | B1 |
| 6289346 | Milewski et al. | Sep 2001 | B1 |
| 6298482 | Seidman et al. | Oct 2001 | B1 |
| 6311877 | Yang | Nov 2001 | B1 |
| 6312336 | Handelman et al. | Nov 2001 | B1 |
| 6320588 | Palmer et al. | Nov 2001 | B1 |
| 6323911 | Schein et al. | Nov 2001 | B1 |
| 6331877 | Bennington et al. | Dec 2001 | B1 |
| 6341195 | Mankovitz et al. | Jan 2002 | B1 |
| 6342926 | Hanafee et al. | Jan 2002 | B1 |
| 6357042 | Srinivasan et al. | Mar 2002 | B2 |
| 6363525 | Dougherty et al. | Mar 2002 | B1 |
| 6381582 | Walker et al. | Apr 2002 | B1 |
| 6388714 | Schein et al. | May 2002 | B1 |
| 6389403 | Dorak, Jr. | May 2002 | B1 |
| 6389593 | Yamagishi | May 2002 | B1 |
| 6392710 | Gonsalves et al. | May 2002 | B1 |
| 6396546 | Alten et al. | May 2002 | B1 |
| 6400407 | Zigmond et al. | Jun 2002 | B1 |
| 6405371 | Oosterhout et al. | Jun 2002 | B1 |
| 6408437 | Hendricks et al. | Jun 2002 | B1 |
| 6411308 | Blonstein et al. | Jun 2002 | B1 |
| 6412110 | Schein et al. | Jun 2002 | B1 |
| 6418556 | Bennington et al. | Jul 2002 | B1 |
| 6421067 | Kamen et al. | Jul 2002 | B1 |
| 6437836 | Huang et al. | Aug 2002 | B1 |
| 6446261 | Rosser | Sep 2002 | B1 |
| 6453471 | Klosterman | Sep 2002 | B1 |
| 6456331 | Kwoh | Sep 2002 | B2 |
| 6463585 | Hendricks et al. | Oct 2002 | B1 |
| 6469753 | Klosterman et al. | Oct 2002 | B1 |
| 6470497 | Ellis et al. | Oct 2002 | B1 |
| 6477579 | Kunkel et al. | Nov 2002 | B1 |
| 6477705 | Yuen et al. | Nov 2002 | B1 |
| 6486920 | Arai et al. | Nov 2002 | B2 |
| 6498895 | Young et al. | Dec 2002 | B2 |
| 6505348 | Knowles et al. | Jan 2003 | B1 |
| 6515680 | Hendricks et al. | Feb 2003 | B1 |
| 6539548 | Hendricks et al. | Mar 2003 | B1 |
| 6542169 | Marshall et al. | Apr 2003 | B1 |
| 6546556 | Kataoka et al. | Apr 2003 | B1 |
| 6564378 | Satterfield et al. | May 2003 | B1 |
| 6564379 | Knudson et al. | May 2003 | B1 |
| 6574424 | Dimitri et al. | Jun 2003 | B1 |
| 6588013 | Lumley et al. | Jul 2003 | B1 |
| 6600364 | Liang et al. | Jul 2003 | B1 |
| 6600503 | Stautner et al. | Jul 2003 | B2 |
| 6604138 | Virine et al. | Aug 2003 | B1 |
| 6606128 | Hanafee et al. | Aug 2003 | B2 |
| 6622306 | Kamada | Sep 2003 | B1 |
| 6631523 | Matthews, III et al. | Oct 2003 | B1 |
| 6651251 | Shoff et al. | Nov 2003 | B1 |
| 6660503 | Kierulff | Dec 2003 | B2 |
| 6665869 | Ellis et al. | Dec 2003 | B1 |
| 6687906 | Yuen et al. | Feb 2004 | B1 |
| 6698020 | Zigmond et al. | Feb 2004 | B1 |
| 6732369 | Schein et al. | May 2004 | B1 |
| 6738978 | Hendricks et al. | May 2004 | B1 |
| 6742183 | Reynolds et al. | May 2004 | B1 |
| 6751800 | Fukuda et al. | Jun 2004 | B1 |
| 6756997 | Ward, III et al. | Jun 2004 | B1 |
| 6757906 | Look et al. | Jun 2004 | B1 |
| 6799326 | Boylan, III et al. | Sep 2004 | B2 |
| 6799327 | Reynolds et al. | Sep 2004 | B1 |
| 6828993 | Hendricks et al. | Dec 2004 | B1 |
| 6868551 | Lawler et al. | Mar 2005 | B1 |
| 6938208 | Reichardt | Aug 2005 | B2 |
| 6973669 | Daniels | Dec 2005 | B2 |
| 6983478 | Grauch et al. | Jan 2006 | B1 |
| 7003792 | Yuen | Feb 2006 | B1 |
| 7028326 | Westlake et al. | Apr 2006 | B1 |
| 7047550 | Yasukawa et al. | May 2006 | B1 |
| 7069576 | Knudson et al. | Jun 2006 | B1 |
| 7136871 | Ozer et al. | Nov 2006 | B2 |
| 7185355 | Ellis et al. | Feb 2007 | B1 |
| 7266833 | Ward, III et al. | Sep 2007 | B2 |
| 7293276 | Phillips et al. | Nov 2007 | B2 |
| 7328450 | Macrae et al. | Feb 2008 | B2 |
| 7392532 | White et al. | Jun 2008 | B2 |
| 7480929 | Klosterman et al. | Jan 2009 | B2 |
| 7668832 | Yeh et al. | Feb 2010 | B2 |
| 7861261 | Haberman et al. | Dec 2010 | B2 |
| 8326685 | Schepers et al. | Dec 2012 | B2 |
| 20010001160 | Shoff et al. | May 2001 | A1 |
| 20010029610 | Corvin et al. | Oct 2001 | A1 |
| 20010042246 | Yuen et al. | Nov 2001 | A1 |
| 20010047298 | Moore et al. | Nov 2001 | A1 |
| 20010049820 | Barton | Dec 2001 | A1 |
| 20010054181 | Corvin | Dec 2001 | A1 |
| 20020007310 | Long | Jan 2002 | A1 |
| 20020023263 | Ahn et al. | Feb 2002 | A1 |
| 20020042913 | Ellis et al. | Apr 2002 | A1 |
| 20020042914 | Walker et al. | Apr 2002 | A1 |
| 20020042918 | Townsend et al. | Apr 2002 | A1 |
| 20020049973 | Alten et al. | Apr 2002 | A1 |
| 20020059602 | Macrae et al. | May 2002 | A1 |
| 20020073424 | Ward et al. | Jun 2002 | A1 |
| 20020083439 | Eldering | Jun 2002 | A1 |
| 20020092017 | Klosterman et al. | Jul 2002 | A1 |
| 20020116717 | Eller et al. | Aug 2002 | A1 |
| 20020120933 | Knudson et al. | Aug 2002 | A1 |
| 20020124249 | Shintani et al. | Sep 2002 | A1 |
| 20030005432 | Ellis et al. | Jan 2003 | A1 |
| 20030005445 | Schein et al. | Jan 2003 | A1 |
| 20030110499 | Knudson et al. | Jun 2003 | A1 |
| 20030163813 | Klosterman et al. | Aug 2003 | A1 |
| 20030164858 | Klosterman et al. | Sep 2003 | A1 |
| 20030188310 | Klosterman et al. | Oct 2003 | A1 |
| 20030188311 | Yuen et al. | Oct 2003 | A1 |
| 20030196201 | Schein et al. | Oct 2003 | A1 |
| 20030196203 | Ellis et al. | Oct 2003 | A1 |
| 20030204847 | Ellis et al. | Oct 2003 | A1 |
| 20030208756 | Macrae et al. | Nov 2003 | A1 |
| 20030208758 | Schein et al. | Nov 2003 | A1 |
| 20030220866 | Pisaris-Henderson et al. | Nov 2003 | A1 |
| 20040003407 | Hanafee et al. | Jan 2004 | A1 |
| 20040049787 | Maissel et al. | Mar 2004 | A1 |
| 20040078809 | Drazin | Apr 2004 | A1 |
| 20040103024 | Patel et al. | May 2004 | A1 |
| 20040103439 | Macrae et al. | May 2004 | A1 |
| 20040111742 | Hendricks et al. | Jun 2004 | A1 |
| 20040139465 | Matthews et al. | Jul 2004 | A1 |
| 20040168189 | Reynolds et al. | Aug 2004 | A1 |
| 20040194131 | Ellis et al. | Sep 2004 | A1 |
| 20040194138 | Boylan et al. | Sep 2004 | A1 |
| 20050010949 | Ward et al. | Jan 2005 | A1 |
| 20050015800 | Holcomb | Jan 2005 | A1 |
| 20050015804 | LaJoie et al. | Jan 2005 | A1 |
| 20050050027 | Yeh et al. | Mar 2005 | A1 |
| 20050097622 | Zigmond et al. | May 2005 | A1 |
| 20050155056 | Knee et al. | Jul 2005 | A1 |
| 20050157217 | Hendricks | Jul 2005 | A1 |
| 20050198668 | Yuen et al. | Sep 2005 | A1 |
| 20050204382 | Ellis | Sep 2005 | A1 |
| 20050216936 | Knudson et al. | Sep 2005 | A1 |
| 20050229214 | Young et al. | Oct 2005 | A1 |
| 20050235321 | Ahmad-Taylor | Oct 2005 | A1 |
| 20050244138 | O'Connor et al. | Nov 2005 | A1 |
| 20050283796 | Flickinger | Dec 2005 | A1 |
| 20060118619 | Hulst et al. | Jun 2006 | A1 |
| 20060184960 | Horton et al. | Aug 2006 | A1 |
| 20060205510 | Lauper et al. | Sep 2006 | A1 |
| 20060248555 | Eldering | Nov 2006 | A1 |
| 20070016926 | Ward et al. | Jan 2007 | A1 |
| 20070033613 | Ward et al. | Feb 2007 | A1 |
| 20070038509 | Jain et al. | Feb 2007 | A1 |
| 20070162934 | Roop et al. | Jul 2007 | A1 |
| 20070186240 | Ward et al. | Aug 2007 | A1 |
| 20070217762 | Yahata | Sep 2007 | A1 |
| 20080127265 | Ward et al. | May 2008 | A1 |
| 20080127266 | Ward et al. | May 2008 | A1 |
| 20080178221 | Schein et al. | Jul 2008 | A1 |
| 20080184315 | Ellis et al. | Jul 2008 | A1 |
| 20080189734 | Schepers et al. | Aug 2008 | A1 |
| 20080189744 | Schein et al. | Aug 2008 | A1 |
| 20080228893 | MacDonald et al. | Sep 2008 | A1 |
| 20080235725 | Hendricks | Sep 2008 | A1 |
| 20080256056 | Chang et al. | Oct 2008 | A1 |
| 20090055268 | Knoller et al. | Feb 2009 | A1 |
| 20090089131 | Moukas et al. | Apr 2009 | A1 |
| 20100191600 | Sideman | Jul 2010 | A1 |
| 20100241516 | Kim et al. | Sep 2010 | A1 |
| 20110035255 | Dasher et al. | Feb 2011 | A1 |
| Number | Date | Country |
|---|---|---|
| 731010 | Mar 2001 | AU |
| 733993 | May 2001 | AU |
| 1030505 | May 1978 | CA |
| 1187197 | May 1985 | CA |
| 1188811 | Jun 1985 | CA |
| 1196082 | Oct 1985 | CA |
| 1200911 | Feb 1986 | CA |
| 2151458 | Jun 1994 | CA |
| 2164608 | Dec 1994 | CA |
| 2297039 | Jan 1999 | CA |
| 2312326 | Jun 1999 | CA |
| 1555191 | Dec 2004 | CN |
| 29 18 846 | Nov 1980 | DE |
| 3246225 | Jun 1984 | DE |
| 3337204 | Apr 1985 | DE |
| 36 21 263 | Jan 1988 | DE |
| 3909334 | Sep 1990 | DE |
| 4201031 | Jul 1993 | DE |
| 19 531 121 | Feb 1997 | DE |
| 19 740 079 | Mar 1999 | DE |
| 19 931 046 | Jan 2001 | DE |
| 0 239 884 | Oct 1987 | EP |
| 0396062 | Nov 1990 | EP |
| 0401930 | Dec 1990 | EP |
| 0408892 | Jan 1991 | EP |
| 0420123 | Apr 1991 | EP |
| 0424648 | May 1991 | EP |
| 0444496 | Sep 1991 | EP |
| 0447968 | Sep 1991 | EP |
| 0532322 | Mar 1993 | EP |
| 0550911 | Jul 1993 | EP |
| 0 560 593 | Sep 1993 | EP |
| 0 572 090 | Dec 1993 | EP |
| 0 682 452 | Nov 1995 | EP |
| 0721253 | Jul 1996 | EP |
| 0725539 | Aug 1996 | EP |
| 0752767 | Jan 1997 | EP |
| 0753964 | Jan 1997 | EP |
| 0762751 | Mar 1997 | EP |
| 0772360 | May 1997 | EP |
| 0774866 | May 1997 | EP |
| 0775417 | May 1997 | EP |
| 0784405 | Jul 1997 | EP |
| 0805594 | Nov 1997 | EP |
| 0822718 | Feb 1998 | EP |
| 0827340 | Mar 1998 | EP |
| 0834798 | Apr 1998 | EP |
| 0848554 | Jun 1998 | EP |
| 0849948 | Jun 1998 | EP |
| 0 854645 | Jul 1998 | EP |
| 0851681 | Jul 1998 | EP |
| 0852442 | Jul 1998 | EP |
| 0854654 | Jul 1998 | EP |
| 0880856 | Dec 1998 | EP |
| 0905985 | Mar 1999 | EP |
| 0924927 | Jun 1999 | EP |
| 0935393 | Aug 1999 | EP |
| 0944253 | Sep 1999 | EP |
| 0963119 | Dec 1999 | EP |
| 0988876 | Mar 2000 | EP |
| 1095504 | May 2001 | EP |
| 1036466 | Mar 2003 | EP |
| 2662895 | Dec 1991 | FR |
| 1 554 411 | Oct 1979 | GB |
| 2034995 | Jun 1980 | GB |
| 2126002 | Mar 1984 | GB |
| 2185670 | Jul 1987 | GB |
| 2256546 | Dec 1992 | GB |
| 2264409 | Aug 1993 | GB |
| 2309134 | Jul 1997 | GB |
| 1035285 | Mar 2005 | HK |
| 58137334 | Aug 1983 | JP |
| 58196738 | Nov 1983 | JP |
| 58210776 | Dec 1983 | JP |
| 59141878 | Aug 1984 | JP |
| 61050470 | Mar 1986 | JP |
| 61074476 | Apr 1986 | JP |
| 62-060370 | Mar 1987 | JP |
| 62060384 | Mar 1987 | JP |
| 63234679 | Sep 1988 | JP |
| 01307944 | Dec 1989 | JP |
| 02048879 | Feb 1990 | JP |
| 03063990 | Mar 1991 | JP |
| 04227380 | Aug 1992 | JP |
| 04-335395 | Nov 1992 | JP |
| 05-183826 | Jul 1993 | JP |
| 05284437 | Oct 1993 | JP |
| 06021907 | Jan 1994 | JP |
| 60-61935 | Mar 1994 | JP |
| 07020254 | Jan 1995 | JP |
| 07-050259 | Feb 1995 | JP |
| 07-076592 | Mar 1995 | JP |
| 07123326 | May 1995 | JP |
| 07147657 | Jun 1995 | JP |
| 07-288759 | Oct 1995 | JP |
| 07-321748 | Dec 1995 | JP |
| 08-32528 | Feb 1996 | JP |
| 0832538 | Feb 1996 | JP |
| 08125497 | May 1996 | JP |
| 08251122 | Sep 1996 | JP |
| 08275077 | Oct 1996 | JP |
| 09-37168 | Feb 1997 | JP |
| 09037151 | Feb 1997 | JP |
| 09037172 | Feb 1997 | JP |
| 09-102827 | Apr 1997 | JP |
| 10-143340 | May 1998 | JP |
| 10-143349 | May 1998 | JP |
| 2838892 | Oct 1998 | JP |
| 10-512420 | Nov 1998 | JP |
| 3101704 | Oct 2000 | JP |
| 2001-213595 | Aug 2001 | JP |
| 2001-1513595 | Aug 2001 | JP |
| 2002-024525 | Jan 2002 | JP |
| 2002-279969 | Sep 2002 | JP |
| 2005216035 | Aug 2005 | JP |
| 4062577 | Mar 2008 | JP |
| WO-8601359 | Feb 1986 | WO |
| WO-8601962 | Mar 1986 | WO |
| WO-8703766 | Jun 1987 | WO |
| WO-8804057 | Jun 1988 | WO |
| WO-8804507 | Jun 1988 | WO |
| WO-8902682 | Mar 1989 | WO |
| WO-8903085 | Apr 1989 | WO |
| WO-8912370 | Dec 1989 | WO |
| WO-9001243 | Feb 1990 | WO |
| WO-9015507 | Dec 1990 | WO |
| WO-9100670 | Jan 1991 | WO |
| WO-9105436 | Apr 1991 | WO |
| WO-9118476 | Nov 1991 | WO |
| WO-9204801 | Mar 1992 | WO |
| WO-9304473 | Mar 1993 | WO |
| WO-9305452 | Mar 1993 | WO |
| WO-9311638 | Jun 1993 | WO |
| WO-9311639 | Jun 1993 | WO |
| WO-9311640 | Jun 1993 | WO |
| WO-9323957 | Nov 1993 | WO |
| WO-9413107 | Jun 1994 | WO |
| WO-9414282 | Jun 1994 | WO |
| WO-9414283 | Jun 1994 | WO |
| WO-9414284 | Jun 1994 | WO |
| WO-9414281 | Jun 1994 | WO |
| WO-9421085 | Sep 1994 | WO |
| WO-9423383 | Oct 1994 | WO |
| WO-9429811 | Dec 1994 | WO |
| WO-9501056 | Jan 1995 | WO |
| WO-9501057 | Jan 1995 | WO |
| WO-9501058 | Jan 1995 | WO |
| WO-9501059 | Jan 1995 | WO |
| WO-9506389 | Mar 1995 | WO |
| WO-9507003 | Mar 1995 | WO |
| WO-9510910 | Apr 1995 | WO |
| WO-9515658 | Jun 1995 | WO |
| WO-9516568 | Jun 1995 | WO |
| WO-9515649 | Jun 1995 | WO |
| WO-9515657 | Jun 1995 | WO |
| WO-9519092 | Jul 1995 | WO |
| WO-9526608 | Oct 1995 | WO |
| WO-9528055 | Oct 1995 | WO |
| WO-9528799 | Oct 1995 | WO |
| WO-9530961 | Nov 1995 | WO |
| WO-9532585 | Nov 1995 | WO |
| WO-9531069 | Nov 1995 | WO |
| WO-9532583 | Nov 1995 | WO |
| WO-9607270 | Mar 1996 | WO |
| WO-9608109 | Mar 1996 | WO |
| WO-9609721 | Mar 1996 | WO |
| WO-9608113 | Mar 1996 | WO |
| WO-9613932 | May 1996 | WO |
| WO-9613935 | May 1996 | WO |
| WO-9617467 | Jun 1996 | WO |
| WO-9617473 | Jun 1996 | WO |
| WO-9621990 | Jul 1996 | WO |
| WO-9626605 | Aug 1996 | WO |
| WO-9627270 | Sep 1996 | WO |
| WO-9627982 | Sep 1996 | WO |
| WO-9631980 | Oct 1996 | WO |
| WO-9634467 | Oct 1996 | WO |
| WO-9634486 | Oct 1996 | WO |
| WO-9634491 | Oct 1996 | WO |
| WO-9638799 | Dec 1996 | WO |
| WO-9641477 | Dec 1996 | WO |
| WO-9641478 | Dec 1996 | WO |
| WO-9641471 | Dec 1996 | WO |
| WO-9702702 | Jan 1997 | WO |
| WO-9704595 | Feb 1997 | WO |
| WO-9707656 | Mar 1997 | WO |
| WO-9713368 | Apr 1997 | WO |
| WO-9717774 | May 1997 | WO |
| WO-9718675 | May 1997 | WO |
| WO-9726612 | Jul 1997 | WO |
| WO-9731480 | Aug 1997 | WO |
| WO-9741673 | Nov 1997 | WO |
| WO-9742763 | Nov 1997 | WO |
| WO-9748230 | Dec 1997 | WO |
| WO-9749237 | Dec 1997 | WO |
| WO-9749241 | Dec 1997 | WO |
| WO-9749242 | Dec 1997 | WO |
| WO-9806219 | Feb 1998 | WO |
| WO-9810589 | Mar 1998 | WO |
| WO-9816062 | Apr 1998 | WO |
| WO-9817064 | Apr 1998 | WO |
| WO-9820675 | May 1998 | WO |
| WO-9826584 | Jun 1998 | WO |
| WO-9827723 | Jun 1998 | WO |
| WO-9826569 | Jun 1998 | WO |
| WO-9828906 | Jul 1998 | WO |
| WO-9831148 | Jul 1998 | WO |
| WO-9841020 | Sep 1998 | WO |
| WO-9843183 | Oct 1998 | WO |
| WO-9847279 | Oct 1998 | WO |
| WO-9848566 | Oct 1998 | WO |
| WO-9856172 | Dec 1998 | WO |
| WO-9901984 | Jan 1999 | WO |
| WO-9904561 | Jan 1999 | WO |
| WO-9907142 | Feb 1999 | WO |
| WO-9914947 | Mar 1999 | WO |
| WO-9918722 | Apr 1999 | WO |
| WO-9929109 | Jun 1999 | WO |
| WO-9930491 | Jun 1999 | WO |
| WO-9931480 | Jun 1999 | WO |
| WO-9945700 | Sep 1999 | WO |
| WO-9945701 | Sep 1999 | WO |
| WO-9945702 | Sep 1999 | WO |
| WO-9952285 | Oct 1999 | WO |
| WO-9956466 | Nov 1999 | WO |
| WO-9956473 | Nov 1999 | WO |
| WO-9960783 | Nov 1999 | WO |
| WO-9960789 | Nov 1999 | WO |
| WO-0004706 | Jan 2000 | WO |
| WO-0004708 | Jan 2000 | WO |
| WO-0005889 | Feb 2000 | WO |
| WO-0011865 | Mar 2000 | WO |
| WO-0013415 | Mar 2000 | WO |
| WO-0016548 | Mar 2000 | WO |
| WO-0028734 | May 2000 | WO |
| WO-0027122 | May 2000 | WO |
| WO-0033560 | Jun 2000 | WO |
| WO-0033573 | Jun 2000 | WO |
| WO-0033160 | Jun 2000 | WO |
| WO-0033224 | Jun 2000 | WO |
| WO-0049801 | Aug 2000 | WO |
| WO-0079798 | Dec 2000 | WO |
| WO-0101677 | Jan 2001 | WO |
| WO-0106784 | Jan 2001 | WO |
| WO-0115438 | Mar 2001 | WO |
| WO-0135662 | May 2001 | WO |
| WO-0189213 | Nov 2001 | WO |
| WO-0203227 | Jan 2002 | WO |
| WO-0231731 | Apr 2002 | WO |
| WO-02057934 | Jul 2002 | WO |
| WO-02084992 | Oct 2002 | WO |
| Entry |
|---|
| International Search Report and Written Opinion dated Jan. 7, 2015 in International Application No. PCT/US2014/010842. |
| U.S. Appl. No. 14/142,226, filed Dec. 27, 2013 titled “Systems and Methods for Optimizing Data Driven Media Placement”. |
| U.S. Appl. No. 14/142,120, filed Dec. 27, 2013 titled “Systems and Methods for Setting Prices in Data Driven Media Placement”. |
| U.S. Appl. No. 09/330,792, filed Jun. 11, 1999, Knudson et al. |
| U.S. Appl. No. 09/332,244, filed Jun. 11, 1999, Ellis et al. |
| “‘Duck Tales,’(1987)[TV Series 1987-1990],” Internet Movie Database (IMDB) [Retrieved on Apr. 7, 2007]. |
| “272OR Satellite Receiver User's Guide,” General Instrument, 1991, pp. 58-61. |
| “Addressable Converters: A New Development at CableData,” Via Cable, vol. 1, No. 12, Dec. 1981. |
| “Bell Atlantic Buys Cable TV Company for $22bn,” Financial Times (London), Oct. 14, 1993 p. 65. |
| “Cable Television Equipment,” Jerrold Communications Publication, dated 1992 and 1993, pp. 8-2.1 to 8-6 and 8-14.1 to 8-14.3. |
| “Computer Network: Current Status and Outlook on Leading Science and Technology,” Bureau of Science & Technology (Japan), vol. 1, Dec. 1986. |
| Creation/Modification of the Audio Signal Processor Setup for a PC Audio Editor, IBM Technical Disclosure Bulletin, vol. 30, No. 10, Mar. 1988, pp. 367-376. |
| “D2B-Home Bus Fur Audio and Video,” Selektor, Apr. 1990, pp. 10, 12. |
| “Dial M for Movie”, Funkschau Nov. 1994 Perspektiven, Video on Demand, pp. 78-79. (English language translation attached). |
| “Digital Video Broadcasting (DVB); DVB specification for data broadcasting,” European Telecommunication Standards Institute, Draft EN 301 192 V1.2.1 (Jan. 1999). |
| “Electronic Programme Guide (EPG); Protocol for a TV Guide using electronic data transmission,” by European Telecommunication Standards Institute, May 1997, Valbonne, France, publication No. ETS 300 707. |
| “Enhanced Content Specification,” “ATVEF,” from the internet at http://www.atvef.com/library/spec.html, printed Aug. 22, 2001, the document bears a Copyright date of 1998, 1999, 2000. |
| “Facsimile Transmission,” NHK Research Monthly Report, Dec. 1987(Unknown author). |
| “Getting Started” Installation Guide, “Using StarSight 1” Manual, and Remote Control “Quick Reference Guide.”. |
| “Interactive Computer Conference Server,” IBM Technical Bulletin, vol. 34, No. 7A, Dec. 1991, pp. 375-377. |
| “Interface Device for Conventional TVs to Improve Functionality,” IBM Technical Disclosure Bulletin, vol. 36, No. 7, Jul. 1993, pp. 53-54. |
| James Sorce, David Fay, Brian Raila and Robert Virzi, “Designing a Broadband Residential Entertainment Service: A Case Study,” GTE Laboratories Incorporated, undated, pp. 141-148. |
| “Lists> What's on Tonite! TV Listings (fwd),” Internet article (On line), Jan. 28, 1995, XP 002378869 [Retrieved on Apr. 28, 2006]. |
| “MSI Datacasting Systems,” TV Communications Journal, Jan. 1973. |
| “Open TV fur interaktives Fernsehen,” Trend and Technik, 9-95 RFE, p. 100. (English language translation attached). |
| “Open TV Launches OpenStreamer™ Technology for Broadcasters to Deliver First Ever Real-Time Digital Interactive Television,” from the internet at http://www.opentv.com/news/openstreamer—press—final.htm, printed on Jun. 28, 1999, the document bears a copyright date of 1999. |
| “Prevue Networks and OpenTV(R) Agree to Work Together on Deploying Interactive Program Guides Worldwide,” from the internet at http://www.opentv.com/news/prevuefinal.htm, printed on Jun. 28, 1999. |
| “Probe XL Brochure, Auto Tote Systems Inc.,” (Newark, Delaware) (undated) 57 pgs. |
| “Prodigy Launches Interactive TV Listing”, Apr. 22, 1994 public Broadcasting Report. |
| “Rewind, reply and unwind with new high-tech TV devices,” by Lawrence J. Magid, LA Times. This document was printed from the internet on Jun. 6, 1999 and bears a date of May 19, 1999. |
| “StarSight Interactive Television Program Guide III” Jim Leftwich and Steve Schein, Functional/Interactional Architecture Specification Document, Orbit Interaction, Palo alto, California, Published before Apr. 19, 1995. |
| “StarSight Interactive Television Program Guide IV” Jim Leftwich and Steve Schein, Functional/Interactional Architecture Specification Document, Orbit Interaction, Palo Alto, California, Published before Apr. 19, 1995. |
| “StarSight Interactive Television Program Guide” Jim Leftwich, Willy Lai & Steve Schein Published before Apr. 19, 1995. |
| “Technological Examination & Basic Investigative Research Report on Image Databases,” Japan Mechanical Engineering Organization Int'l Society for the Advancement of Image Software, Japan, Mar. 1988. |
| “Technology: Turn on, tune in and print out—An experimental interactive television service is set to alter our viewing habits,” Financial Times (London), Oct. 14, 1993, p. 11. |
| “The New Media and Broadcast Policy: An Investigation & Research Conference Report on Broadcasting Diversification,” Radio Regulatory Bureau, Japan Ministry of Posts & Telecommunications, Mar. 1982. |
| “TV Guide Online Set for Fall”, Entertainment Marketing Letter, Aug. 1994. |
| “TV Listings Functional Spec.,” Time Video Information Services, Inc., undated. |
| “Using StarSight 2,” Instruction Manual, StarSight Telecast, Inc., Starsight CB 1500 Customer Letter, 1994. |
| “Windows 98 Feature Combines TV, Terminal and the Internet,” New York Times, Aug. 18, 1998. |
| Advertisement for “TV Decisions,” Cable Vision, Aug. 4, 1986. |
| Alexander, Michael “Visualizing cleared-off desktops,” Computerworld, May 6, 1991, p. 20. |
| Antonoff, M., “Stay Tuned for Smart TV,” Popular Science, Nov. 1990, pp. 62-65. |
| Bach, U. et al., “Multimedia TV Set, Part 1” Radio-Fernsehen Elektronik (RFE), Sep. 1996, pp. 28, 30, 31. (English language translation attached.). |
| Bach, U. et al., “Multimedia TV Set, Part 2 and Conclusion,” Radio-Fernsehen Elektronik (RFE), Oct. 1996, pp. 38-40. (English language translation attached.). |
| Baer, R.H, “Innovative Add-On TV Products,” IEEE Transactions on Consumer Electronics, vol. CE-25, Nov. 1979, pp. 765-771. |
| Bensch, U., “VPV Videotext Programs Videorecorder,” IEEE Paper, Jun. 1988, pp. 788-792. |
| Bestler, Caitlin “Flexible Data Structures and Interface Rituals for Rapid Development of OSD Applications,” Proceedings from the Eleven Technical Sessions, 42nd Annual Convention and Exposition and Exploration of the NCTA, San Francisco, CA Jun. 6-9, 1993, pp. 223-236. Jun. 6, 1993. |
| Brochure, “A New Approach to Addressability,” CableData, undated. |
| Brochure, “Westar and Videotoken Network Present The CableComputer,” Revised Aug. 15, 1985 (Plaintiff's 334). |
| Brochure, Time Inc., “Now, Through the Advances of the Computer Age, You Can Get the Information You Want, When You Want It. Instantly and Conveniently, On Your Home TV Screen,” Time Teletext, Time Video Information Services, Inc., undated (V 79167-79175). |
| Brochure, VTN “Videotoken Network, New Dimension Television,” Dec. 1985 (Plaintiff's Exhibit 313). |
| Brugliera, Vito., “Digital On-Screen Display—A New Technology for the Consumer Interface,” Symposium Record Cable TV Sessions of the 18th International Television Symposium & Technical Exhibition—Montreux, Switzerland, Jun. 10-15, 1993, pp. 571-586. |
| Cable Computer User's Guide, Rev. 1, Dec. 1985 (Plaintiff's Exhibit 289). |
| CableData, Roseville Consumer Presentation, Mar. 1985. |
| Came, E.B., “The Wired Household,” IEEE Spectrum, vol. 16 No. 10, Oct. 1979, pp. 61-66. |
| Chan, Patrick P., “Learning Considerations In User Interface Design: The Room Model,” Publication of the Software Portability Laboratory, University of Waterloo, Ontario, Canada, Jul. 1984. |
| Christodoulakis, Steven and Graham, Stephen “Browsing Within Time-Driven Multimedia Documents,” publication of the Institute for Computer Research, University of Waterloo, Waterloo, Ontario, Canada Jul. 1988 pp. 219-227. |
| Office Actions and Replies from U.S. Appl. No. 10/453,388. |
| Cox, J. et al, “Extended Services in a Digital Compression System,” Proceedings from Eleven Technical Sessions: 42nd Annual Convention and Exposition of the National Cable Television Association, Jun. 1993, pp. 185-191. |
| Damouny, N.G., “Teletext Decoders-Keeping Up With the Latest Advances,” IEEE Transactions on Consumer Electronics, vol. CE-30, No. 3, Aug. 1984, pp. 429-435. |
| Declaration Under 37 C.F.R. § 1.132 of Richard E. Glassberg, signed Oct. 20, 2006, filed Oct. 24, 2006, from U.S. Appl. No. 10/346,266. |
| DiRosa, S. “BIGSURF Netguide”, Jul. 1995, vol. 3.1 (Sections 18,21, and 28—renumbered as pp. 1-27). |
| Edwardson, S.M., & Gee, A., “CEEFAX: A Proposed New Broadcasting Service,” Journal of the SMPTE, Jan. 1974, vol. 83 No. 1, pp. 14-19. |
| Eitz, Gerhard, “Zukünftige Informations-und Datenangebote beim digitalen Femsehen-EPG Und ‘Lesezeichen’,” RTM Rundfunktechnische Mitteilungen, Jun. 1997, vol. 41, pp. 67-72. |
| European Search Report dated Nov. 19, 2002 from European Application No. 989446111.7. |
| European Telecommunication Standard, “Electronic Programme Guide (EPG); Protocol for a TV Guide using electronic data transmission,” pp. 1-45, sections 1-11.12.7 and annex A-P, bearing a date of May 1997. |
| Hartwig, Rautenberg, Bollmann, “Broadcasting and Processing of Program Guides for Digital TV,” SMPTE Journal, pp. 727-732, Oct. 1997. |
| Hedger, J., “Telesoftware: Home Computing Via Broadcast Teletext,” IEEE Transactions on Consumer Electronics, vol. CE-25, No. 3, Jul. 1979, pp. 279-287. |
| Hiroshi Ishii et al, “Clearface: Translucent Multiuser Interface for TeamWorkStation,” ECSCW, Sep. 1991, pp. 6-10. |
| Hiroshi Ishii et al, “Toward an Open Shared Workspace: Computer and Video Fusion Approach of Team Workstation,” Communications of the ACM, Dec. 1991, vol. 34 No. 12, pp. 37-50. |
| Hirotada Ueda et al, “Impact: An Interactive Natural-Motion-Picture Dedicated Multi-Media Authoring System,” Communications of the ACM, Mar. 1991, pp. 343-350. |
| Hofmann, Neumann, Oberlies & Schadwinkel, “Videotext Programmiert Videorecorder,” Rundfunktechnischen Mitteilungen, (Broadcast Engineering Reports), vol. 26 No. 6, pp. 254-257, Nov.-Dec. 1982. |
| Installation Guide, “Getting Started 1” Manual, and Remote Control “Quick Reference Guide.” |
| Instruction Manual, “Using StarSight 2,” StarSight Telecast, Inc., StarSight CB 1500 Customer Letter, 1994. |
| Instructional Manual, “Sonic the Hedgehog,” Sega of America, 1992. |
| International Search Report for International application No. PCT/US06/30073 mailed Jul. 7, 2008, 1 page. |
| James, A., “Oracle—Broadcasting the Written Word,” Wireless World, Jul. 1973, vol. 79 No. 1453, pp. 314-316. |
| Judice, C.N., “Move Over Cable, Here Comes Video Via Voice Lines,” Network World, Sep. 1986, p. 26. |
| Kai et al “Development of a Simulation System for Integrated Services Television,” Report from Information Processing Society of Japan, Japan, Sep. 13, 1996, vol. 96, No. 90 pgs. |
| Karstad, K., “Microprocessor Control for Color-TV Receivers,” IEEE Transactions on Consumer Electronics, vol. CE-26, May 1980, pp. 149-155. |
| Kornhaas, W., “Von der Textprogrammierung uber TOP zum Archivsystem,” Radio Fernsehen Elektronik, vol. 40, No. 8, Aug. 30, 1991, pp. 465-468, XP 000240875 Veb Verlag Technik. Berlin, DE ISSN: 1436-1574. |
| Listing of computer code for operating system within the Cable Computer in 1985 (Plaintiff's Exhibit 298). |
| Listing of computer code for Video HTU Program (Plaintiff's Exhibit 299). |
| Lowenstein, R.L. and Alter, H.E., “The Inevitable March of Videotex,” Technology Review, vol. 88, Oct. 1985, p. 22. |
| M/A-COM, Inc., “Videocipher II Satellite Descrambler Owner's Manual,” dated Prior Feb. 1986, pp. 1-17. |
| Mack Daily, “Addressable Decoder with Downloadable Operation,” Proceedings from the Eleven Technical Sessions, 42nd Annual Convention and Exposition of the NCTA, Jun. 6-9, 1993, pp. 82-89. |
| Mannes, G., “Smart Screens: Development of Personal Navigation Systems for TV Viewers,” Video Magazine, Dec. 1993. |
| Mar. 19, 1985 letter from G. Knapp of CableData to R. Hansen of Weststar Communications, Inc. (Plaintiffs Exhibit 325). |
| Markowitz, A. “Companies Jump on Interactive Bandwagon,” Discount Store News, Dec. 6, 1993, pp. 4 and 131. |
| McKenzie, G.A., “Oracle—An Information Broadcasting Service Using Data Transmission in the Vertical Interval,” Journal of the SMPTE, Jan. 1974, vol. 83 No. 1, pp. 6-10. |
| Merrell, R.G., “Tac Timer,” 1986 NCTA Technical Papers, pp. 203-206. |
| Neumann, Andreas, “WDR Online Aufbau and Perspektiven Automatisierter Online-Dienste im WDR,” RTM Rundfunktechnische Mitteilungen, vol. 41, pp. 56-66, Jun. 1997. |
| No subject, “Tom Schauer (tschauer@moscow.com)Thu, Sep. 28, 1995 16:46:48-700,” XP-002378870 [Retrieved from the Internet Apr. 28, 2006]. |
| Pfister, Larry T., “Teletext: Its Time Has Come,” Prepared for the IGC Videotext / Teletext Conference, Andover, Massachusetts, Dec. 14, 1982, pp. 1-11. |
| Prevue Guide Brochure, Spring 1984. |
| Prevue Guide Brochure, Spring 1994. |
| Rayers, D.J., “Telesoftware by Teletext,” 1984 IEEE Conference Papers, vol. 240, p. 323. |
| Rogers, “Telcos vs. Cable TV : The Global View With Markets Converging and Regulatory Barriers Falling, Service Carriers Are Ready to Rumble,” Data Communications, Sep. 21, 1995, vol. 24, No. 13, pp. 75-76, 78, 80, XP000526196. |
| Roizen, Joseph “Teletext in the USA,” Society of Motion Picture and Television Engineers Journal, Jul. 1981, pp. 602-610. |
| Roseville City Council Presentation, Mar. 13, 1985 (Defendant's Exhibit 226). |
| Ross Peddicord, “New on TV: You Bet Your Horse,” The Sun, Baltimore Maryland Dec. 15, 1994, 1 pg. |
| Schlender, B.R., “Couch Potatoes! Now It's Smart TV,” Fortune, Nov. 20, 1989, pp. 111-116. |
| Schmuckler, Eric “A marriage that's made in cyberspace (television networks pursue links with online information services),” May 16, 1994 Mediaweek, v. 4, No. 20, p. 22(3). |
| Sealfon, Peggy, “High Tech TV,” Photographic, Dec. 1984. |
| Sunada, K. et al, “Teletext Color Television Receiver Model C-29M950, C26M940,” NEC Home Electronics , NEC Giho, 1987. |
| Supplementary European Search Report for Application No. EP 98 93 5889, completed on Sep. 28, 2001. |
| Sussman, A. “GTE Tunes in to Home TV Shopping,”PC Week, Jun. 28, 1988, p. C15. |
| Tech Notes: Product Updates from M/A-COM Cable Home Group, “Videocipher Owner's Manual Update,” Issue No. 6, Feb. 1986. |
| Technical White Paper, “Open TV™ Operating Environment,” (© 1998 OpenTV Inc.), pp. 1-12. |
| Transcript of the Deposition of John Roop, Oct. 1996, pp. 186-187. |
| Trial testimony of Michael Axford, Prevue Interactive, Inc. and United Video Satellite Group, Inc. v. Starsight Telecast, Inc., May 9, 1998, pp. 186-187, 295-315, and 352-357. |
| Various publications of Insight Telecast, 1992 and 1993. |
| Veith, R.H., “Television's Teletext,” Elsevier Science Publishing Co., Inc, 1983, pp. 13-20, 41-51. |
| Videocipher Stipulation, May 1996. |
| VideoGuide, “VideoGuide User's Manual,” pp. 1-27 (p. 11 is the most relevant). |
| W. Leo Hoarty, “Multimedia on Cable Television Systems,” Symposium Record Table TV Sessions, 18th International Television Symposium and Technical Exhibition, Montreux, Switzerland, Jun. 10, 1993, pp. 555-567. |
| Wittig et al, “Intelligent Media Agents in Interactive Television Systems,” Proceedings of the International Conference on Multimedia Computing and Systems, Los Alamitos, CA, US, May 15-18, 1995, pp. 182-189, XP 000603484. |
| Yee Hsiang Chang et al., “An Open-Systems Approach to Video on Demand,” IEEE Communications Magazine, May 1994, pp. 68-80. |
| Number | Date | Country | |
|---|---|---|---|
| 20140196081 A1 | Jul 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61750809 | Jan 2013 | US |
