Yahoo! Inc.

Jelli, Inc.

Sun Microsystems, Inc.

Yahoo Holdings, Inc.

Torsten Schulz

Marco Boerries

Venkatachary Srinivasan

John Paul LeFlohic

Markus Meyer

Matthias Breuer

Sreeharsha Kamireddy

Stephen King Dougherty

Jateen P Parekh

Michael S Dougherty

Stephanie Shieh

Trevor Price

Meher Tendjoukian

Thomas Pfohe

Bernd Scheibe

Em Huynh

Bernd Eilers

Ralf Hofmann

Iain Andrew Huxley

Torsten Both

Jerald J Singh

Rahim Ismail Adatia

Alexander Nickolas Linde

Tajinder Singh

Travis Scott Young

Bjørn Ebbesen

Christian Lindholm

Joseph J Martin

Inventory data is stored, wherein the inventory data represents for each of a plurality of broadcast stations a corresponding inventory of audio advertising spots available from that broadcast station to be filled by an advertising placement system. An advertising campaign data representing a set of advertising objectives of an advertising campaign is received. The inventory data is used to iteratively select advertising spots to be associated with the advertising campaign, based at least in part on a respective computed fitness of match between each selected advertising spot and said advertising objectives.

Dynamic broadcast lineups based on local and third-party data sources

A selection of a broadcast media ad network and a set of parameters including one or both of a goal and a constraint associated with an advertising campaign is received. Based at least in part on said selection and said set of parameters an advertising proposal, the advertising proposal is determined including an identification of a set of broadcasters associated with the selected broadcast media ad network and for each a corresponding advertising plan portion of the advertising proposal. Information representing the advertising proposal is caused to be displayed at a node from which said selection and set of parameters were received.

Self service demand side platform for broadcast media ad exchange

A new RFP specification is received for a new broadcast ad campaign. A placement is determined for a new broadcast ad in a suitable position within an ad network inventory based at least in part on the new RFP specification. A transfer of an existing placement for an existing broadcast ad campaign out of the suitable position to a newer position based at least in part on an existing RFP specification is determined.

Placement and adaptive transfer of advertising spots in a broadcast network

Inventory data representing for each of a plurality of broadcast stations a corresponding inventory of audio advertising spots available from that broadcast station to be filled by an advertising exchange system is stored. One or more sets of advertising campaign data, each representing a set of advertising objectives of an advertising campaign, is received via a demand side interface. The inventory data is received via a supply side interface. The inventory data is used to determine for each advertising campaign a corresponding set of advertising spots to be associated with that advertising campaign.

Ad exchange on ad server for linear broadcast playout system

Audience data received from a plurality of audience data sources is stored. An advertising goal defined at least in part by reference to one or more audience attributes is received. Audience data from two or more of said audience data sources is used to determine an advertising plan to meet the advertising goal.

Audience data in audio advertising

In one example, a content navigation interface apparatus includes display logic for displaying selections for accessing a first entry of a content structure and a second entry of the content structure, wherein the second entry is a sub-entry of the first entry. The apparatus further including selection logic for determining the second entry for display based on a user characteristic (e.g., history, user profile, etc.). The first entry may be associated with a first level of a hierarchical content structure, and the second entry associated with a second level of the hierarchical content structure. In one example, the first entry is associated with a broad content category and the second entry associated with content, such as a media object.

Content structures and content navigation interfaces

For providing synchronization of image data among diverse devices and applications, exemplary systems include a direct client application providing a user interface operable to allow a user to organize image data according to albums, and to select one or more albums for synchronization with one or more server interfaces that provide various image data manipulation, sharing, and features related thereto. Systems also include an intermediary system to assist in synchronization of select albums with handheld devices, and a notification server to provide scalable notifications of album updates made at server interfaces by users. Exemplary methods include steps providing for selection, from direct client applications, of albums to synchronize with devices, including handheld devices, and various steps of providing updates and notifications among appropriate system components.

Synchronizing image data among applications and devices

Embodiments are directed towards SMS-initiated mobile registration. A mobile device sends an SMS message to a mobile registration device. In response, the mobile registration device generates a random identifier and associates it with the mobile device identifier of the mobile device. Then, the mobile registration device sends a response SMS message to the mobile device, the response SMS message containing a Uniform Resource Identifier (URI) to a mobile registration web page, where the URI contains the generated random identifier. The mobile device uses the URI to navigate to the mobile registration web page, where additional registration information is provided. The mobile registration device associates the additional registration information with the mobile device based on the generated random identifier included in the URI, and creates a user account based on the mobile number from which the SMS message was received and the additional registration information.

SMS-initiated mobile registration

System and method for handling calendar events among a plurality of user devices in a communication network are disclosed. The system includes a device manager for interfacing with the plurality of user devices, where the plurality of user devices use different calendar applications and have calendar events in different data formats, and the plurality of user devices include at least a meeting organizer device and one or more attendee devices. The system further includes a calendar gateway for processing the calendar events to form a corresponding connected calendar-data-set for each connected user, where the connected calendar-data-set is stored in a calendar backend server and is shared among one or more devices of each connected user, and an email gateway for communicating the calendar events between the calendar gateway and the plurality of user devices.

Universal calendar event handling

System and method for notifying a user status of communications between a server and the user having one or more user devices in a communication network are disclosed. The system includes a server for communicating with the user, where the server includes a connected-data-set and the one or more user devices share portions of the connected-data-set, logic for monitoring communications between the server and the one or more user devices for a predetermined set of notification conditions, and logic for sending a notification message to the one or more user devices when a notification condition is detected.

Alert mechanism for notifying multiple user devices sharing a connected-data-set

A system and method for servicing user accounts are disclosed. The system includes one or more blades for servicing the user accounts, where each blade includes software components and hardware components, and each blade serves a group of user accounts, a blade manager for managing states of the one or more blades, and logic for incrementally adding one or more new blades in response to increase in the number of new user accounts.

Scalable software blade architecture

A system and method for sharing data between two users on different blades in scalable software blade architecture are disclosed. The system includes a plurality of blades, where each blade includes software components and hardware components, each blade serves a predefined group of users, and each user is associated with one or more user devices. The system further includes a first blade and a second blade, where the first blade connects a first user to a first connected dataset and the second blade connects a second user to a second connected dataset, and the first blade and the second blade operate independent of each other, a blade manager for managing the first and second blades, a pipe device for connecting the first and second blades, and logic for sharing portions of the first connected dataset of the first user with the second user using the pipe device.

Growing community of inventors

Pinneberg, Germany

Torsten Schulz