Personalization of media streams

In some implementations, a user device can personalize a media stream by converting notifications into audio speech data and presenting the audio speech data at locations within the media stream that do not interrupt the enjoyment of the media stream by the user. In some implementations, the user device can receive notifications from various communication services, applications installed on the user device, and/or other sources, determine information describing the notifications, and present the information to the user using the audio speech data. In some implementations, the user device can generate personalized notifications based on the media stream and/or media items selected by the user. The user device can generate personalized notifications based on the user's context (e.g., environment, location, activity, etc.). The personalized notifications can then be presented to the user using audio speech data at appropriate locations in the media stream.

TECHNICAL FIELD

The disclosure generally relates to personalization of media streams.

BACKGROUND

Modern user devices provide a variety of features for users. For example, a user device can provide features that allow users to listen to audio streams (e.g., music, talk shows, audio books, etc.) through speakers and/or earphones. User devices can provide features that allow users to communicate with other people, receive news updates, receive social media updates, and/or use various software applications. Often, the user device will receive or generate notifications to the user indicating that the user has received a communication, news update, social media update, and/or application status update. These notifications may be presented simultaneously with the audio stream and may interrupt the user's enjoyment of the currently presented audio entertainment.

SUMMARY

In some implementations, a user device can personalize a media stream by converting notifications into audio notifications and presenting the audio notifications at locations within the media stream that do not interrupt the enjoyment of the media stream by the user. In some implementations, the user device can receive notifications from various communication services, applications installed on the user device, and/or other sources, determine information describing the notifications, and present the information to the user using an audio notification. In some implementations, the user device can generate personalized notifications that include information related to the media stream and/or media items selected by the user. The user device can generate personalized notifications that include information related to the user's context (e.g., environment, location, activity, device context, etc.). The personalized notifications can then be presented to the user using an audio notification at appropriate locations in the media stream.

Particular implementations provide at least the following advantages. The user can listen to a media item from a media stream without being interrupted by a notification. The notification can be short enough that the notification does not interrupt or impede the flow of the media stream while providing enough information to the user so that the user can determine whether to respond to the notification. The notification can provide information relevant to the user's current context (e.g., environment, activity, location, etc.). The notification can provide information relevant to the user's interests (e.g., type of music, artists, politics, etc.).

DETAILED DESCRIPTION

Overview

FIG. 1is a block diagram of an example system100for personalization of media streams. For example, a media stream can be a sequential transmission and/or presentation of media items. The media stream can be an audio stream (e.g., music, talk shows, audio book, etc.) that includes audio media items (e.g., songs, episodes, chapters, etc.) that are sequentially presented (e.g., played) by a computing device. The media stream can be a video stream (e.g., television shows, a series of movies, videos, etc.) that includes video media items (e.g., episodes, individual movies, individual videos, etc.) that are sequentially presented by the computing device. To make describing the present technology easier, this disclosure will describe features with reference to music media streams. However, the features of the technology described herein can also be applied to any other type of media stream.

In some implementations, system100can include user device102. For example, user device102can be a computing device, such as a desktop computer, laptop computer, smartphone, tablet computer, media streaming device, smart watch, smart glasses and/or other mobile or wearable device. User device102can be configured with different software applications that provide a variety of services and features for the user of user device102. These applications can be configured to present media items (e.g., movies, music, videos, etc.) and/or present informative notifications to the user by generating audio, video, and/or haptic representations of data, as described further below.

In some implementations, user device102can include media application104. For example, media application104can be a software application installed on user device102and configured to present (e.g., playback audio and/or video) media items. Media application104can present media items stored locally on user device102. Media application104can present media items received from a network source through network130. For example, network130can be a wide area network, local area network, and/or the Internet. Network130can be, for example, a direct peer-to-peer (e.g., ad-hoc) network using Bluetooth, Wi-Fi, near field communication, or some other direct peer-to-peer communication technology. Network130can be a wired network, wireless network, or a combination thereof.

In some implementations, media application104can receive media items and/or media streams from media server140through network130. For example, media server140can be configured to stream media items to media application104. For example, the user of user device102may have a subscriber account with media server140. The user can use media application104to connect to media server140, login the user user's subscriber account, and receive media items and/or media streams from media server140. For example, the user can provide input to media application104to select a music stream. Media application104can send a message to media server140requesting that media server140stream the selected music stream to media application104. After a portion of the music stream (e.g., a song or song portion) is received by media application104from media server140, media application104can present (e.g., playback) the portion of the music stream using an audio subsystem (e.g., speakers) of user device102. Media server140can continue streaming the music stream to media application104until the user provides input to stop streaming the music or until the connection to media server140is terminated. Thus, media server140may continuously stream a dynamically generated sequence of songs (e.g., music items) to media application104and media application104will continue to play the songs received in the media stream until the user provides input to stop the media stream or until the network connection between media application104and media server140is terminated.

In some implementations, user device102can include notification application106. For example, notification application106can manage notifications for user device102. Notification application106can receive notifications from various other applications on user device102and/or network services (e.g., notification server142, network service145, etc.). When notification application106receives a notification, notification application106can determine when and/or how to present the received notification. For example, notification application106may (e.g., by default) present notifications when media application104is not presenting a media stream and/or media item. However, the user may configure notification application106(e.g., through a settings GUI) to present received notifications while media application105is presenting a media stream and/or media item, as described below.

Timing of Notifications

In some implementations, notification application106can present a notification upon receipt of a notification. For example, the notification can be presented using audio, video, and/or haptic output. The notification can be presented using synthesized speech, as described further below.

In some implementations, notifications can be prioritized based on whether the notification can be delayed or not. In some implementations, notifications can be prioritized individually. For example, the originator (or source) of the notification (e.g., an application, network service, etc.) can include a priority identifier in the notification indicating whether the notification is a high or a low priority notification.

In some implementations, notifications can be prioritized based on the originator or source of the notification. For example, a notification from a calendar application116or navigation application110may always be a high priority notification, while a notification from social media application108may not be a high priority notification. When notification application106receives a high priority notification, notification application106can present the notification on user device102immediately or near immediately upon receipt of the notification.

In some implementations, notification application106can generate an audio notification based on a received textual notification. For example, notification application106can perform a text to speech operation (e.g., voice synthesis) to convert the textual data in a notification into audio speech data. Notification application106can generate the audio notification using the audio speech data. After converting the received notification into an audio notification, notification application106can present the high priority audio notification immediately using an audio subsystem (e.g., speakers) of user device102. For example, when media application104is playing music from a music stream, notification application106can dim (e.g., lower the volume) of the currently playing music and present the audio notification over the playing music.

In some implementations, notification application106can delay presentation of a notification. For example, notification application106can delay presentation of low priority audio notifications so that the presentation of the notification will not interfere with a currently playing media item (e.g., song, music item, podcast, video, etc.). Continuing the music streaming example above, in some implementations, media application104can share state information describing the current state of media application104with other processes on user device102.

In some implementations, media application104can share the current playback state of the received media stream with data collection daemon114that can store the state information of media application104in a database on user device102. For example, the playback state data can include information identifying or describing the current media item (e.g., song title, identification number, etc.) being played, the current position or location (e.g., elapsed time) in the playing media item, whether the media stream is transitioning between media items, whether the user has stopped or paused playback, etc. Another application, such as notification application106, can register interest with data collection daemon114in the current playback state of the media stream and/or state of media application104so that the application can perform an operation in response to a state change.

In some implementations, notification application106can register interest in media application104state changes so that notification application106will be notified by data collection daemon114when the playback state of the media stream changes (e.g., is stopped, started, transitions between media items, etc.). While media application104plays a song from the music stream received from media server140, notification application106can receive a low priority notification. Notification application106can store the low priority notification in a low priority notification collection (e.g., queue, list, etc.) and wait for a callback from data collection daemon114indicating that the currently playing song is finished (e.g., the media stream is between songs) or that the playback of the media stream has been stopped (e.g., paused) by the user.

In some implementations, notification application106can present an audio notification based on the current state of media application104. For example, notification application106can receive a callback from data collection daemon114indicating that the music stream presented by media application104is between songs (e.g., just finished one song and has not started playing the next song). In response to receiving the callback, notification application106can determine whether notification application106has delayed presentation of any notifications. For example, notification application106can determine whether there are any notifications in the notification collection that have not been presented or reviewed by the user yet. If there are delayed notifications in the notification collection that have not been reviewed by the user, notification application110can send a command to media application104to pause playback of the media stream, generate an audio notification representing one or more of the delayed notifications, and present the audio notification using an audio subsystem of user device102. After notification application106presents the audio notification representing the delayed notification, notification application106can send a command to media application104to resume playback of the media stream.

In some implementations, notification application106can present an audio notification while a media item is being presented by media application104. For example, notification application106can receive a callback from data collection daemon114identifying a currently playing song and the current position in the currently playing song. Notification application106can use the song identifier to request metadata for the playing song from media server140. For example, the metadata can include information identifying portions of the song that might be appropriate for presenting an audio notification. For example, a song may have a long lead in (“intro”), a long conclusion (“outro”), pauses, or other lulls in the song. The song metadata can include information identifying the location (e.g., timing) of these lulls. Notification application106can use this lull information to determine when to present an audio notification. For example, the song metadata can indicate that a long outtro begins at 3:10 minutes in a 3:30 minute song. If notification application106has delayed the presentation of a notification (e.g., a low priority notification exists in the notification collection), then notification application106can generate an audio notification for the notification (or notifications) in the notification collection and present the audio notification at the 3:10 minute mark during the playback of the song. By presenting the audio notification during a lull in a song, notification application106can reduce the impact the audio notification has on the user's listening enjoyment.

In some implementations, notification application106can present an audio notification in response to user input or the occurrence of an event during the presentation of a media item. For example, notification application106can receive a callback from data collection daemon114indicating that the user has paused, stopped, skipped playback of a song in a music stream. Notification application106can receive a callback from data collection daemon114indicating that the user has connected or disconnected an accessory (e.g., headphones, speaker, car stereo, etc.). Notification application106can receive a callback from data collection daemon114indicating that the user has changed locations (e.g., entered a car, building, geofence, etc.). In response to receiving the callback, notification application106can determine whether notification application106has delayed presentation of a notification. When notification application106has delayed the presentation of a notification (e.g., a low priority notification exists in the notification collection), then notification application106can generate an audio notification for the notification (or notifications) in the notification collection and present the audio notification in response to the user input or event.

In some implementations, notification application106can present a graphical notification in response to user input indicating that the user is looking at the display of user device102. For example, notification application106can receive a callback from data collection daemon114indicating that the user has started interacting with a touch-sensitive display or using a graphical application of user device102. In response to receiving the callback, notification application106can determine whether notification application106has delayed presentation of a notification. When notification application106has delayed the presentation of a notification (e.g., a low priority notification exists in the notification collection), then notification application106can present a graphical notification for the notification (or notifications) in the notification collection and present the graphical notification in response to the user looking at or interacting with the display of user device102.

Alternatively, notification application106can provide an audio notification to media application104for presentation during playback of an audio stream. For example, instead of notification application106determining when to present an audio notification during playback of a media stream, notification application106can select a notification to present next, generate an audio notification based on the selected notification (or obtained information, search results, etc.), and send the audio notification to media application104. Media application104can then determine when to present the audio notification during playback of the media stream using similar logic as described above and below for notification application106and inject (e.g., present, playback, etc.) the notification into the media stream (e.g., between media items, during lulls in media items, etc.) for presentation to the user.

Selecting Notifications to Present

In some implementations, notification application106can present audio notifications representing notifications received by notification application106during presentation of a media stream. As described above, notification application106can receive a notification, or multiple notifications from sources internal and/or external to user device102. In some implementations, notification application106can generate notifications, as described further below. Since notification application106will present the audio notifications during the presentation (e.g., playback) of a media stream, the audio notification should be short enough that the audio notification does not interrupt the flow of the playback of the media stream (e.g., is not jarring, annoying, etc.) and does not reduce the user's enjoyment of the media stream. Thus, in some implementations, notification application106may be selective about which notifications are presented during the playback of a media stream and/or may summarize (e.g., aggregate, combine, roll-up, etc.) notifications so that the length or duration of the audio notification does not negatively affect the users enjoyment of the media stream, as described further below.

In some implementations, notification application106can be selective with respect to which notifications are presented during the presentation of a media stream. For example, while media application104is playing back a media item from a media stream, notification application106may receive multiple notifications from different sources. In order to present notifications within a limited time window (e.g., 8 seconds, 10 seconds, 13 seconds, etc.) so as to not affect (e.g., detract from) the user's enjoyment of the media stream, notification application106can select one or more notifications out of the multiple notifications received by notification application106for presentation during presentation of the audio stream.

In some implementations, notification application106can select a notification for presentation based on how important the message is to the user. For example, a notification for an email message, text message, instant message, etc. that has been marked as urgent (e.g., the email may be marked as urgent) by the sender may be selected over other non-urgent notifications, such as notifications related to social media posts. The notification for the urgent message can be presented individually and before other messages so that notification application106can draw the user's attention to the urgent message.

In some implementations, notification application106can select a notification for presentation based on the user's current application usage. For example, data collection daemon114can collect information describing the user's current application usage. When notification application106determines that a delayed notification in the notification collection should be presented, notification application106can send a message to data collection daemon114requesting information identifying applications currently used by the user on user device102. When notification application106receives the application identifiers from data collection daemon114, notification application106can compare the notification source information (e.g., application identifiers, service identifiers, server identifiers, etc.) in the notifications stored in the notification collection to the application identifiers of the applications currently being used by the user on user device102. Notification application106can select a notification for presentation during playback of a media stream when the notification source information corresponds to an application identifier of an application currently being used by the user on user device102. Stated differently, notification application106can determine which stored notification corresponds to an application being used by the user and select a notification for presentation when the notification corresponds to an application currently in use by the user.

For example, the user may be listening to a music stream while using exercise application118or navigation application110. While the user is exercising and listening to the music stream, exercise application118may generate a notification describing a metric corresponding to the user's progress in the current exercise (e.g., distance covered, calories burned, etc.) as detected by sensors on user device102and/or another device (e.g., a wearable device such as a watch, pedometer, etc.) and send the notification to notification application106. The exercise notification may be one of many notifications received by notification application106, for example. However, notification application106can select the exercise application notification over other notifications based on the user's current use of exercise application118.

Similarly, when the user is using navigation application110to navigate (e.g., while driving), navigation application110can generate navigation notifications that guide the user along a selected route. Navigation application110can prioritize notifications according to how quickly the instruction should be presented to the user. For example, navigation notifications that provide instructions about an action that the user (driver) must take immediately or near immediately (e.g., within a threshold period of time, within a threshold distance, etc.) can be marked as high priority notifications. When navigation application110sends these high priority navigation notifications to notification application106, notification application106can immediately present these high priority notifications, as described above.

Navigation notifications that provide informational instructions (e.g., continue on highway 101, 10 miles until your next turn, etc.) can be marked as low priority notifications by navigation application110. When navigation application110sends these low priority navigation notifications to notification application106, notification application106can store these low priority notifications in the notification collection and wait for the next opportunity (e.g., between media items) to present a notification in the notification collection, as described above. Notification application106can select the low priority navigation notification stored in the notification collection for presentation over other notifications in the notification collection when the user is currently using navigation application110.

In some implementations, notification application106can select notifications to present based on the subject matter of the notification. For example, a notification corresponding to communications directed to the user (e.g., an email application, instant messaging application, telephone application, voicemail application, text messaging application, etc.) can be selected for presentation before a notification from a social media source (e.g., social media application108). A notification regarding an application currently being used by the user (e.g., exercise application118, navigation application110, as described above) can be selected over an email notification or other communication directed to the user. A notification regarding time sensitive information (e.g., a calendar reminder) can be selected over other types of notifications.

In some implementations, notification application106can select notifications to present based on location. For example, when the user is at a work location, notification application106can select notifications related to the user's work (e.g., work email account notifications, calendar events, instant messages from work contacts, etc.) for presentation over other non-work related notifications. Thus, when multiple notifications are available for presentation to the user, notification application106can intelligently select which notification to present based on the various factors described above.

In some implementations, notification application106can present a notification summary for a group of notifications. For example, instead of selecting a single notification to present to the user, notification application106can summarize multiple related notifications and present the notification summary to the user. For example, when notification application106receives multiple notifications from a single source, notification application106can combine the notifications into a single audio notification. For example, notification application106may receive multiple notifications indicating that new electronic messages (e.g., email, instant message, text message, SMS message, etc.) have been sent to the user of user device102. Instead of presenting individual notifications for each message, notification application106can summarize the notifications by source, notification type, etc. For example, if five new email notifications have been received by user device102, notification application106can generate a single audio notification telling the user that five new email messages are waiting for the user to review. Similarly, when the user receives three email notifications and two text message notifications, notification application106can generate a single audio notification telling the user that three new email messages and two new text messages are available for the user to review.

Generating Notifications

In some implementations, notification application106can generate audio notifications based on received notifications. As described above, notification application106can receive notifications that include textual content and translate the text into speech audio data for presentation to the user while the user is listening to a media stream. In some implementations, notification application106can augment a received notification with additional content. For example, notification application106may receive a notification indicating that messaging application112(e.g., an email application, SMS message application, instant message application, telephone application, etc.) has received a new message for the user. Instead of merely presenting an audio notification that tells the user a new message is available for review, notification application106can summarize the received message. For example, notification application106can receive the content of the received message from messaging application112, determine portions of the message that best represent the content of the message, and generate an audio notification that summarizes of the received message. For example, notification application106can determine who sent the message (e.g., Bob) and the purpose of the message (e.g., wants to meet for dinner at 6 pm) and present an audio notification that says “You received a new message from Bob: Bob wants to meet for dinner at 6 pm.” Notification application106can summarize the received message so that the message is shorter than a predefined maximum message length so as to not interrupt the user's enjoyment of the playing audio stream, as described above.

In some implementations, the audio notification can be mixed with other audio data to improve the presentation of the audio notification. For example, to make the audio notification fit in better with a playing media stream, notification application106can mix the audio notification with samples of the media items from the media stream. When the media stream is a music media stream associated with the Jazz genre, for example, notification application106can mix the audio notification with samples of Jazz music so that the audio notification is played over music that fits with the music played by the current media stream. Notification application106can obtain the media item samples for mixing with the audio notification from recently played media items from the currently playing media stream, for example.

Generating Notifications Based on Selected Media

In some implementations, notification application106can generate new notifications based on media presented by media application104, user context, device context, and/or general information that might be interesting to the user. For example, at times, notification application106may not have any delayed received notifications to present to the user. In these situations, notification application106can generate an audio notification based on data collected by notification application106(e.g., as opposed to generating audio notifications based on notifications received by notification application106). Notification application106can, for example, request information related to the user's media selection, user's context, device context, and/or general interests from various network resources, such as media server140, search server144(e.g., internet search engine), network service145(e.g., weather service, traffic service, social media service, etc.). After the information is received, notification application106can select an item of information, generate an audio notification, and present the audio notification to the user at an appropriate time (e.g., in between songs), as described above and below.

In some implementations, notification application106can generate audio notifications based on the currently playing media stream. For example, notification application106can obtain information describing the currently playing media stream and/or currently playing media item from data collection daemon114. Media application104can, as described above, report the current state of media application104, including identification of the currently playing media stream and/or currently playing media item to data collection daemon114. Notification application106can register interest in the state of media application104with data collection daemon114and data collection114can send information describing and/or identifying the currently playing media stream and/or currently playing media item to notification application106when the media stream and/or media item is presented (e.g., played) by media application104.

When notification application106receives the information identifying or describing the currently playing media stream and/or media item, notification application106can initiate a search to obtain additional information about the media stream and/or media item. For example, the media stream and/or media item can be related to an artist or artists, genre, and/or other media characteristic. Notification application106can send a search request to media server140, search server144, and/or network service (e.g., social media service) to obtain more information about the media item, media genre, artists, etc., associated with the media stream and/or media item. The search request can, for example, include search parameters, such as an artist name, media item name, genre, etc., associated with the media stream and/or media item. Upon receiving the search request, the receiving server (e.g., media server140, search server144, network service145, etc.) can perform a search for information based on the search parameters.

For example, when the search request is sent to media server140, media server140can respond to the request by sending notification application106information describing media items (e.g., songs, albums, movies, new releases, other artists, etc.) related to the playing media stream and/or media item. For example, when the user is listening to a “Popular Music” music stream, notification application106can receive information describing new song releases by popular artists from media sever140, generate an audio notification identifying a new song release and/or artist, and present the audio notification to the user while the user is listening to the media stream.

When the search request is sent to search server144, search server144can respond to the request by sending notification application106information describing concerts, appearances, and/or general news about the artists, media items, genre, etc., associated with the currently playing media stream and/or media item. For example, when the user is listening to a “Heavy Metal” music stream, notification application106can receive information describing concert dates for heavy metal bands, news about heavy metal music artists, and/or other general search results for heavy metal music. Notification application106can then generate an audio notification describing the search results (e.g., “Metallica suing George Jetson for copyright infringement.”) and present the audio notification to the user at an appropriate time while the user is listening to the “Heavy Metal” music stream.

When the search request is sent to network service145(e.g., a social media server), network service145can respond to the request by sending notification application106information describing social media posts by the artist identified in the search request and/or social media posts made by others about the artist, media item, genre, etc. For example, when the user is listening to a song by the band U2, notification application106can receive search results from network service145that describe social media posts made by U2, made by fans about U2, describing U2 events, concerts, etc. Notification application106can then generate an audio notification for presenting the information (e.g., “U2 posted a message on social media in favor of protecting the environment.”) and present the audio notification when media application104is finished playing the current U2 song.

Generating Notifications Based on User Context

In some implementations, notification application106can generate notifications based on user context. For example, notification application106can determine the user's context based on sensor data, application usage, and/or other data. As described above, data collection daemon114can collect data from various hardware and/or software components of user device102to determine the current context or state of user device102. The state or context of user device102can be used by notification application106(and other applications) to infer or derive the user's context. The data can, for example, describe which applications the user is currently using. The data can describe the user's current physical activity. Notification application106can request application usage information, sensor data, activity information, etc., from data collection daemon114to determine the current context of user device102and/or the user and generate informational notifications based on the current context of the device and/or user.

In some implementations, data collection daemon114can collect sensor data and/or interpretations of sensor data generated by user device102. For example, user device102can be configured with a motion sensor that generates data describing the motion of user device102. User device102can be configured with software that interprets the motion sensor data to determine what user activity corresponds to the motion sensor data. For example, the motion sensor data can generate motion data that user device102can interpret to be motion associated with the user walking or running. The motion sensor data and/or the interpreted user activity (e.g., walking, running, etc.) can be reported to data collection daemon114so that other processes (e.g., notification application106) can use the data to determine the current user context. Other sensors and context can include, for example, a location determination subsystem (e.g., satellite location system, Wi-Fi location system, cellular location system, etc.) that can determine the user's current location.

In some implementations, notification application106can generate notifications based on the current activity and/or location of the user. For example, motion sensor data can be used by user device102to determine that the user is walking, running, biking, etc. Notification application106can receive information from data collection daemon114that indicates that the user is walking or running, for example. Notification application106can receive information from data collection daemon114indicating the user's current geographic location. Based on the determination that the user is walking, for example, notification application106can initiate an Internet search with search server114for popular walking or running paths near the user's current location. Upon receipt of the search results, notification application106can generate an audio notification suggesting a popular walking path near the user's current location based on the search results received from search server144and present the audio notification at an appropriate time during the presentation of the media stream.

As another example, the location subsystem of user device102can be used to determine that the user is driving. For example, when the user changes location at a speed consistent with driving, user device102can determine that the user is driving. The user's current location (e.g., and location history) and the determination that the user is driving can be reported to data collection daemon114. Notification application106can request and receive data from data collection daemon114that indicates the user is driving and is located at a specific location. Based on this information, notification application106can initiate a search with search server144for traffic information describing the current traffic conditions at the user's current location. Upon receipt of the traffic information, notification application106can generate an notification describing the traffic conditions at the user's current location and present the notification at an appropriate time (e.g., between media items), as described above and below.

Similarly, notification application106can generate various other notifications based on the user's current context. For example, notification application106can use the user's current location to initiate a search for weather information, local news, local sports, or other information related to the user's current location. When the user is using a camera function of user device102, notification application106can determine the user's location and initiate a search with search server144for popular or famous places to take pictures near the user's current location. When the user is listening to music, for example, notification application106can use a microphone on user device102to monitor ambient noise or sounds and detect when someone speaks the user's name. When somebody speaks the user's name (e.g., “Hey, Bob.”), notification application106can generate an audio notification that tells the user that somebody is trying to get the user's attention. For example, the audio notification can be presented immediately so that the user can respond to the person who spoke the user's name.

Selecting Search Results to Present

In some implementations, notification application106can select a particular search result item for presentation on user device102. For example, to avoid interrupting the user's enjoyment of the currently playing media stream for too long, notification application106can select a portion (e.g., one item, two items, less than all) of the search results for presentation to the user. Notification application106can select a search result item or items for presentation such that the generated audio notification is less than a maximum duration (e.g., 30 seconds, 25 seconds, etc.).

Notification application106can select search results items for presentation based on user context and/or interests. For example, when the user is currently running, then notification application106can select to present search results related to running. When the user is driving, then notification application106can select to present search results related to driving. When the user is just hanging out (e.g., user device102cannot determine a particular activity that the user is performing), then notification application106can select to present search results related to the user's favorite social media website, local news, politics, etc.

Responding to Audio Notifications

In some implementations, notification application106can receive speech input from the user in response to presenting a notification. For example, when notification application106presents an audio notification, notification application106can use a microphone of user device102to monitor for a speech (e.g., audio, voice, etc.) input response. Notification application106can turn on the microphone for a period of time (e.g., 5 seconds, 10 seconds, etc.) after presenting the audio notification, collect sound data generated by the microphone (or sound subsystem), and run speech recognition algorithms on the sound data to determine what speech input is being provided by the user.

For example, if notification application106presents an audio notification describing an upcoming concert, the user can respond to the audio notification by saying “add the concert to my calendar” or “purchase tickets.” Notification application106can receive the speech input and perform the appropriate action. For example, notification application106can add the concert date/time to the user's calendar (e.g., calendar application116) or initiate a process for purchasing concert tickets from an online ticket vendor (e.g., network service145). Similarly, if notification application106presents an audio notification describing a new song release, the user can say “I wanna hear it” or “play it” to cause notification application106to initiate a process to play or preview (e.g., from media server140) a portion of the song new release. Thus, the user's natural or automatic spoken reaction to a notification can cause notification application106to perform a corresponding action without the user providing express or explicit input to notification application106.

Similarly, notification application106can detect when the user expresses interest in or approval of the content of a notification (e.g., “That's cool!”, “Awesome!”, etc.) and prioritize future notifications having similar content (e.g., related to an artist, type of music, type of event, politics, etc.) or from a similar source (e.g., social media website, news source, etc.). Notification application106can detect when the user expresses disinterest in or disapproval of the content of a notification (e.g., “Boring!”, “I hate country music!”, etc.) and deprioritize future notifications having similar content (e.g., related to an artist, type of music, type of event, politics, etc.) or from a similar source (e.g., social media website, news source, etc.). Thus, notification application106can receive the (e.g., passive, indirect, undirected, etc.) speech input, determine that the input relates to the audio notification that was just presented, determine the appropriate action to take in response to the speech input and take the determined action.

FIG. 2Aillustrates a media stream200where a notification is presented between presentation of media items. For example, media application104can receive media stream200from media server140. Media application104can present media stream200through a display and/or audio subsystem of user device102. For example, if media stream200is a music stream, media application104can present the media stream200using speakers of user device102.

While presenting media stream200, media application104can report state information to data collection daemon114, as described above. For example, media application104can send state information to data collection daemon114identifying the currently presented (e.g., playing) media item204, the current playback location within media item204, and/or the current playback location within media stream200. For example, the state information can indicate that media item204is being played by media application104, media application104is currently between songs, and/or other state information.

In some implementations, notification application106can register with data collection daemon114to receive state information for media application104from data collection daemon114. For example, data collection daemon114can send notification application106state information associated with media application104when data collection daemon114receives information indicating that the state of media application104has changed (e.g., started playing a different media item, between media items, started playing a different media stream, etc.)

In some implementations, while media application104is presenting media item204, notification application106can receive notification206(e.g., an email notification, an instant message notification, an application notification, etc.). For example, notification application106can receive notification206at time212. Notification application106can determine whether notification206is a high priority notification or a low priority notification, as described above. When notification206is a high priority notification, notification application106can present an audio notification corresponding to notification206immediately at time212. When notification application106determines that notification206is a low priority notification, notification can delay presentation of notification206. For example, notification application106can delay presentation of notification206until a break between media item204and media item208in media stream200. For example, notification application106can receive notification206at time212on timeline210. Notification application106can determine based on the state information for media application104received from data collection daemon114that media application104is currently presenting media item204. When media application104is currently playing media item204, notification application106can delay presentation of notification206and store notification206in the low priority notification collection, as described above.

Later, at time214, notification application106can receive state information for media application104from data collection daemon114indicating that playback of media item104has ended. In response to receiving the state information and determining that playback of media item204has ended (e.g., playback of media stream200is between media items), notification application106can generate an audio notification corresponding to notification206and present the audio notification on user device102. For example, notification application106can send a message to media application104at time214to cause media application104to pause playback of media stream200while notification application106presents the audio notification. After presentation of the audio notification is completed at time216, notification application106can send a message to media application104to cause media application104to resume presentation of media stream200(e.g., initiate presentation of media item208at time216). Thus, notification application106can delay presentation of notification206so that the presentation of notification206does not interrupt the user's enjoyment of media item204.

FIG. 2Billustrates a media stream220where a notification is presented during a lull at the end of a media item. For example, media application104can receive media stream220from media server140. Media application104can present media stream220through a display and/or audio subsystem of user device102. For example, if media stream220is a music stream, media application104can present the media stream220using speakers of user device102or headphones connected to user device102.

In some implementations, while media application104is presenting media item224, notification application106can receive notification226(e.g., an email notification, an instant message notification, an application notification, etc.). Notification application106can determine that notification226is a low priority notification and delay presentation of notification226until a lull (e.g., long intro, long outtro, long instrumental, pause, etc.) in media item224. For example, notification application106can receive notification226at time232on timeline230. Notification application106can determine based on the state information for media application104received from data collection daemon114that media application104is currently presenting media item224. When media application104is currently playing media item224, notification application106can delay presentation of notification226and store notification226in the low priority notification collection, as described above.

Later, at time234, notification application106present notification226during a lull in playback of media item224. For example, notification application106can receive state information for media application104from data collection daemon114identifying media item224. Notification application106can send a message to media server140that identifies media item224and requests metadata corresponding to media item224. Notification application106can receive from media server140metadata that describes locations and durations in media item224where lulls occur. For example, media item224may be a three minute long song that has an outtro starting at 2:30 minutes and a duration of 30 seconds. Thus, the metadata for media item224can indicate a lull starting at 2:30 minutes and having a duration of 30 seconds. Notification application106can obtain the start time and duration of the lull from the metadata and present an audio notification corresponding to notification226at 2:30 minutes (e.g., time234) into media item224. Since notification application106presented notification226while media item224was playing, upon completion of media item224at time236media application104can begin playback of the next media item (e.g., media item228) in media stream220. Thus, even though the audio notification is presented by notification application106during the presentation of media item224, the audio notification can be presented at a time during the presentation of media item224that does not interfere with the user's enjoyment of media item224.

FIG. 2Cillustrates a media stream240where a notification is presented during a lull at the beginning of a media item. For example, media application104can receive media stream240from media server140. Media application104can present media stream240through a display and/or audio subsystem of user device102. For example, when media stream240is a music stream, media application104can present the media stream240using speakers of user device102or headphones connected to user device102.

In some implementations, while media application104is presenting media item244, notification application106can receive notification246(e.g., an email notification, an instant message notification, an application notification, etc.). Notification application106can determine that the notification is a low priority notification and delay presentation of notification246until a lull (e.g., long intro, long outtro, long instrumental, pause, etc.) in media item244. For example, notification application106can receive notification246at time252on timeline250. Notification application106can determine based on the state information for media application104received from data collection daemon114that media application104is currently presenting media item244. When media application104is currently playing media item244, notification application106can delay presentation of notification246and store notification246in the low priority notification collection, as described above.

Later, at time254, notification application106present notification226during a lull in playback of media item248. For example, while media application104is presenting media item244, notification application106can receive state information for media application104from data collection daemon114identifying the currently playing media item244and the next media item (e.g., media item248) in media stream240. Notification application106can send a message to media server140that identifies media item244and media item248and requests metadata corresponding to media items244and248. Notification application106can receive from media server140metadata that describes locations and durations in media items244and248where lulls occur, as described above. For example, media item244may be a three minute long song that has no lulls. Media item248may be a three minute long song that has an intro starting at 0 minutes and a duration of 20 seconds. Thus, the metadata for media item248can indicate a lull starting at 0 minutes and having a duration of 20 seconds. Notification application106can obtain the start time and duration of the lull from the metadata and present an audio notification corresponding to notification246at 0 minutes (e.g., time254) into media item248. Thus, even though the audio notification is presented by notification application106during the presentation of media item248, the audio notification can be presented at a time during the presentation of media item248that does not interfere with the user's enjoyment of media item248.

In some implementations, notification application106can present a notification at the earliest opportunity. For example, referring back toFIG. 2A, when notification application106receives notification206at time212, notification application can analyze the metadata for media item204and media item208to determine the locations of any lulls in the media items. If a lull occurs in media item204before the end of media item204at time214, then notification application106can present notification206during the lull. If media item204does not have any lulls between the receipt of notification206and the end of the media item at time214, then notification application106can present notification206at the end of media item204at time214(e.g., between media items, songs, etc.). Thus, notification application106can present notification206as early as possible but without interfering with the user's enjoyment of media stream200.

FIG. 3Aillustrates adjusting a media stream300based on a scheduled notification. For example, while media application104is presenting media stream300(e.g., media item302), notification application106can determine that notification306is scheduled for presentation at a future time (e.g., time314). For example, notification306can correspond to a reminder for a calendar entry in calendar application116. Notification application106can, for example, receive state information from calendar application116(e.g., through data collection daemon116) that indicates future scheduled notifications, reminders, etc. Notification application106can determine that scheduled notification206will occur within a threshold period of time of the current time and determine whether to adjust scheduled notification306(e.g., to present the reminder earlier) or adjust media stream300.

In some implementations and as depicted byFIG. 3A, notification application106can adjust media stream300based on scheduled notification306. For example, notification application106can determine the next notification (e.g., notification306) scheduled for presentation to the user. As media application104is presenting media stream300, notification application106can receive state information describing the playback of media stream300. As playback of media stream300approaches the end of media item302(e.g., at or around time312on timeline310), notification application106can determine the amount of time between the end of media item302(e.g., at time312) and scheduled notification306at time314. After determining the amount of time, notification application106can send a message to media application104requesting that duration of the next media item be no greater than the determined amount of time. Media application104can then select (or request from media server140) a media item (e.g., media item304) for presentation in media stream300that fits within the requested amount of time and present the selected media item. Thus, notification application106can adjust media stream300to accommodate the timing of a scheduled notification.

FIG. 3Billustrates adjusting a scheduled notification to fit within media stream340. For example, while media application104is presenting media stream340(e.g., media item342), notification application106can determine that notification348is scheduled for presentation at a future time (e.g., time336). For example, notification348can correspond to a reminder for a calendar entry in calendar application116. Notification application106can, for example, receive state information from calendar application116(e.g., through data collection daemon116) that indicates future scheduled notifications, reminders, etc. Notification application106can determine that scheduled notification348will occur within a threshold period of time of the current time and determine whether to adjust scheduled notification348(e.g., to present the reminder earlier) or adjust media stream340.

In some implementations and as depicted byFIG. 3B, notification application106can adjust scheduled notification348so that scheduled notification348occurs at a time during the presentation of media stream340that minimizes the impact of the notification on the user's enjoyment of media stream340. For example, notification application106can move scheduled notification348so that the notification is presented earlier or later based on the type of notification. For example, if scheduled notification348is a time-critical reminder (e.g., a reminder for a later event, a meeting, etc.), then notification application106can adjust scheduled notification348so that it is presented earlier (e.g., at time332). If scheduled notification348is not a time-critical reminder (e.g., a reminder to walk the dog), then notification application106can adjust scheduled notification348forward (e.g., at time332) or backward (e.g., after media item346) in time based on the closest break between media items or lulls in playback of media items.

For example, when notification348is a time-critical notification and is scheduled less than a threshold period of time (e.g., the average length of a media item type in media stream340, song, podcast, etc.) from the end of media item342, notification application106can adjust the scheduled time for presenting notification348so that an audio notification corresponding to notification348is presented earlier and near the end (e.g., around time332) of media item342. Alternatively, notification application106can present the audio notification corresponding to notification348during a lull in media item342or media item346, as described above.

When notification348is not a time-critical notification, notification application106can adjust the presentation time of scheduled notification348so that the corresponding audio notification is presented during the closest (e.g., to scheduled time336) break between media items or during the closest (e.g., to scheduled time336) lull in media item342or media item346.

Example Processes

FIG. 4is flow diagram of an example process400for personalizing a media stream with received notifications. For example, notification application106can personalize the playback of a media stream by presenting received notifications during the playback of the media stream in such a way as to minimize the impact of the notifications on the user's enjoyment of the media stream.

At step402, user device102can present a media item from a media stream. For example, media application104on user device102can receive a media stream from media server140and present the media items in the media stream using audio and/or video components (e.g., display, speakers, etc.) of user device102.

At step404, user device102can receive a notification. For example, the notification can be received by notification application106from a communication service, social networking service, an application running on user device102or other notification source.

At step406, user device102can determine whether presentation of the notification can be delayed. For example, notification application106can determine whether the received notification is a high or low priority notification, as described above. Notification application106can immediately (or near immediately) present high priority notifications. Notification application106can delay presentation of low priority notifications.

At step408, user device102can store the delayed notification. For example, when notification application106determines that a received notification can be delayed, notification application106can store the delayed notification in a delayed notification collection (e.g., list, queue, etc.).

At step410, user device102can determine a location in the playing media stream for presenting the delayed notification. For example, notification application106can determine the location (e.g., time, event, etc.) based on when the media stream transitions between media items, when the user pauses the media stream, when lulls occur within media items in the media stream, etc., as described above.

At step412, user device102can present the delayed notification at the determined location. For example, when notification application106determines that playback of the media stream has reached the determined location (e.g., a break between songs, a lull in a song, a user initiated playback event has occurred, etc.), notification application can generate an audio notification (e.g., text-to-speech synthesized notification) corresponding to the received notification and present the audio notification at the determined location in the media stream.

FIG. 5is a flow diagram of an example process500for personalizing a media stream by presenting information relevant to the media items in the media stream. For example, notification application106can personalize the playback of a media stream by searching for information of related to the media stream selected by the user of user device102, generating audio notifications that describe the search results, and presenting generated audio notifications during the playback of the media stream in such a way as to minimize the impact of the notifications on the user's enjoyment of the media stream.

At step502, user device102can present a media item from a media stream. For example, media application104on user device102can receive a media stream from media server140and present the media items in the media stream using audio and/or video components (e.g., display, speakers, etc.) of user device102.

At step504, user device102can determine a characteristic of the media item or media item stream. For example, notification application106can determine a genre, artist, etc., associated with the media item and/or media item stream.

At step506, user device102can obtain information related to the determined characteristic. For example, notification application106can initiate a search with music server140, search server144(e.g., internet search engine), and/or network service145(e.g., social media service), for information related to the genre, artists, etc., related to the media item and/or media stream.

At step508, user device102can select an item of information for presentation. For example, notification application106can receive the search results from the search initiated at step506and select an item of information (or multiple items of information) for presentation during playback of the media stream. For example, notification application106may receive a large number of items of information related to the determined characteristic in the search results. However, notifications presented during playback of the media stream should be short enough so that the impact of the notifications on the user's enjoyment of the media stream is minimized. Thus, notification application106can select an item of information from the search results for presentation during the presentation of the media stream based on various criteria, as described above.

At step510, user device102can generate a notification that includes the selected item of information. For example, notification application106can generate an audio notification that describes the selected item of information from the search results.

At step512, user device102can determine a location in the media stream for presenting the generated notification. For example, the location can correspond to break between media items, a lull in a media item, a user event that causes the media stream or media item to pause, or other location or event.

At step514, user device102can present the audio notification at the determined location. For example, notification application106can present the generated notification between media items, during a lull in a media item, or in response to the user pausing, rewinding, skipping a media item or otherwise modifying playback of the media stream.

FIG. 6is a flow diagram of an example process600for personalizing a media stream by presenting information relevant to the user's interests. For example, notification application106can personalize the playback of a media stream by searching for information of interest to the user of user device102, generating audio notifications that describe the search results, and presenting generated audio notifications during the playback of the media stream in such a way as to minimize the impact of the notifications on the user's enjoyment of the media stream.

At step602, user device102can present a media item from a media stream. For example, media application104on user device102can receive a media stream from media server140and present the media items in the media stream using audio and/or video components (e.g., display, speakers, etc.) of user device102.

At step604, user device102can determine a user context. For example, notification application106can receive information from data collection daemon114describing the sensor readings, device state, application state, etc. In some implementations, the information can include inferences about the user's current activities or context (e.g., the user is running, walking, sleeping, etc.) made by other applications or processes. In some implementations, notification application106can make inferences about the user's context based on the sensor data, application data, and/or device state. For example, notification application106can determine that the user is listening to an audio stream at work (e.g., based on location system data) and the current time (e.g., clock signal) is approaching the time when the user typically goes home (e.g., historical data collected by data collection daemon114), then notification application106can determine that the user's context is that the user is about to drive home.

At step606, user device102can obtain information related to the determined user context. For example, notification application106can initiate a search with music server140, search server144(e.g., internet search engine), and/or network service145(e.g., social media service), for information related to the determined user context. For example, when the user context is that the user is about to drive home from work, notification application106can initiate a search for traffic conditions along the user's typical route home from work or suggest alternate routes to avoid particularly bad traffic.

At step608, user device102can select an item of information for presentation. For example, notification application106can receive the search results from the search initiated at step606and select an item of information (or multiple items of information) for presentation during playback of the media stream. For example, notification application106may receive a large number of items of information related to the determined user context in the search results. However, notifications presented during playback of the media stream should be short enough so that the impact of presenting the notifications on the user's enjoyment of the media stream is minimized. Thus, notification application106can select an item of information from the search results for presentation during the presentation of the media stream based on various criteria, as described above.

At step610, user device102can generate a notification that includes the selected item of information. For example, notification application106can generate an audio notification (e.g., using text to speech algorithms) that describes using synthesized speech the selected item of information from the search results.

At step612, user device102can determine a location in the media stream for presenting the generated notification. For example, the location can correspond to break between media items, a lull in a media item, a user event that causes the media stream or media item to pause, or other location or event.

At step614, user device102can present the audio notification at the determined location. For example, notification application106can present the generated audio notification between media items, during a lull in a media item, or in response to the user pausing, rewinding, skipping a media item or otherwise modifying playback of the media stream.

FIG. 7is a flow diagram of an example process700for personalizing a media stream to accommodate a scheduled notification. For example, notification application106can personalize the playback of a media stream by determining that a notification is scheduled at a future time and causing media application104or music server140to select songs for the media stream that fit within a time window prior to the scheduled notification.

At step702, user device102can present a first media item in from a media stream. For example, media application104on user device102can receive a media stream from media server140and present the media items in the media stream using audio and/or video components (e.g., display, speakers, etc.) of user device102.

At step704, user device102can determine that a notification is scheduled for presentation at a scheduled time. For example, notification application106can receive information (e.g., from calendar application116, data collection daemon114, etc.) describing a scheduled notification (e.g., the next scheduled notification from the current time). The information can, for example, include a title, description, or label for the notification. The information can include the date (e.g., today) and time (e.g., 1:30 pm) when the notification is scheduled to be presented.

At step706, user device102can determine the completion time for the presentation of the first media item. For example, notification application106can obtain information identifying the first media item, the length (e.g., time duration) of the first media item, and/or the current playback location of the first media item. Notification application106can determine the completion time by subtracting the current playback location (e.g., time index 1:30 minutes) from the length (e.g., 2:30 minutes) of the first media application adding the difference to the current time. For example, if the length of the first media item is 2:30 minutes, the current playback location is 1:30 minutes, and the current time is 1:25 pm, then the completion time is 1:00 minute from the current time or 1:26 pm.

At step708, user device102can calculate the time period between the completion time and the scheduled time for the notification. For example, if the scheduled time for the notification is 1:30 pm and the completion time for the first media item is 1:26 pm, then notification application106can calculate the time period between the end of the first media item and the scheduled notification is 4 minutes.

At step710, user device102can select a second media item for presentation based on the calculated time period. For example, notification application106can send a message to media application104requesting that the next media item (e.g., the second media item) played by media application104is less than 4 minutes long so that the next media item will end before the scheduled notification is scheduled to be presented. Media application104can then select a media item that is less than 4 minutes long (and that is associated with the currently playing media stream) to playback for the user. Alternatively, media application104can send a message to media server140requesting that the next media item in the media stream be less than 4 minutes long so that playback of the next media item is not interrupted by the scheduled notification.

At step712, user device102can present the second media item in the media stream between the first media item and the scheduled notification. For example, media application104can present the second media item after completing the playback of the first media item and before notification application106presents the scheduled notification. Thus, the media stream can be adjusted so that a scheduled notification does not interfere with the user's enjoyment of the media items in the media stream.

FIG. 8is a flow diagram of an example process700for personalizing a media stream by adjusting a scheduled notification to fit within the media stream. For example, notification application106can personalize the playback of a media stream by determining that a notification is scheduled at a future time and adjusting the schedule for presentation of the notification so that the notification is presented at a time during playback of the media stream when the notification will not interrupt the user's enjoyment of media items in the media stream.

At step802, user device102can present a first media item in from a media stream. For example, media application104on user device102can receive a media stream from media server140and present the media items in the media stream using audio and/or video components (e.g., display, speakers, etc.) of user device102.

At step804, user device102can determine that a notification is scheduled for presentation at a scheduled time. For example, notification application106can receive information (e.g., from calendar application116, data collection daemon114, etc.) describing a scheduled notification (e.g., the next scheduled notification from the current time). The information can, for example, include a title, description, or label for the notification. The information can include the date (e.g., today) and time (e.g., 1:30 pm) when the notification is scheduled to be presented.

At step806, user device102can determine the completion time for the presentation of the first media item. For example, notification application106can obtain information identifying the first media item, the length (e.g., time duration) of the first media item, and/or the current playback location of the first media item. Notification application106can determine the completion time by subtracting the current playback location (e.g., time index 1:30 minutes) from the length (e.g., 2:30 minutes) of the first media application adding the difference to the current time. For example, if the length of the first media item is 2:30 minutes, the current playback location is 1:30 minutes, and the current time is 1:25 pm, then the completion time is 1:00 minute from the current time or 1:26 pm.

At step808, user device102can determine the difference between the completion time and the scheduled time for the notification is less than a threshold period of time. For example, if the scheduled time for the notification is 1:30 pm and the completion time for the first media item is 1:26 pm, then notification application106can calculate the time period between the end of the first media item and the scheduled notification is 4 minutes. Notification application106can compare the time period (e.g., 4 minutes) to a threshold amount of time (e.g., the average length of a media item, song, movie, podcast, etc.). For example, when the time period between the end of the current media item and the scheduled notification is less than the threshold amount of time, then notification application106can adjust the schedule for presenting the scheduled notification.

At step810, user device102can determine a location in the media stream for presenting the scheduled notification. For example, the location can correspond to break between media items, a lull in a media item, a user event that causes the media stream or media item to pause, or other location or event.

At step812, user device102can generate an audio notification corresponding to the scheduled notification. For example, notification application106can generate an audio notification (e.g., using text to speech algorithms) that describes using synthesized speech the generated notification.

At step814, user device102can present the audio notification at the determined location in the media stream. For example, notification application106can present the generated audio notification between media items, during a lull in a media item, or in response to the user pausing, rewinding, skipping a media item or otherwise modifying playback of the media stream, as described above.

Privacy

The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For example, by monitoring the user's speech for a short period of time after presenting an audio notification, user device102can respond to automatic voice responses generated by the user is response to presented notifications thereby providing a more natural (e.g., human) interaction between the user and the device. Moreover, this speech monitoring feature can be implemented in way that ensures the user's privacy. For example, when no speech is detected within the short period of time (e.g., 5 seconds) the device can stop monitoring speech. When speech is detected, the device can determine whether the speech is relevant to the presented notification. If the detected speech is not relevant to the presented notification, the device can stop monitoring for speech and delete any speech data collected for the detected speech. Thus, the user's privacy can be protected even when briefly monitoring for a speech response to a presented notification.

Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information.

Example System Architecture

FIG. 9is a block diagram of an example computing device900that can implement the features and processes ofFIGS. 1-8. The computing device900can include a memory interface902, one or more data processors, image processors and/or central processing units904, and a peripherals interface906. The memory interface902, the one or more processors904and/or the peripherals interface906can be separate components or can be integrated in one or more integrated circuits. The various components in the computing device900can be coupled by one or more communication buses or signal lines.

Sensors, devices, and subsystems can be coupled to the peripherals interface906to facilitate multiple functionalities. For example, a motion sensor910, a light sensor912, and a proximity sensor914can be coupled to the peripherals interface906to facilitate orientation, lighting, and proximity functions. Other sensors916can also be connected to the peripherals interface906, such as a global navigation satellite system (GNSS) (e.g., GPS receiver), a temperature sensor, a biometric sensor, magnetometer or other sensing device, to facilitate related functionalities.

A camera subsystem920and an optical sensor922, e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips. The camera subsystem920and the optical sensor922can be used to collect images of a user to be used during authentication of a user, e.g., by performing facial recognition analysis.

Communication functions can be facilitated through one or more wireless communication subsystems924, which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem924can depend on the communication network(s) over which the computing device900is intended to operate. For example, the computing device900can include communication subsystems924designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and a Bluetooth™ network. In particular, the wireless communication subsystems924can include hosting protocols such that the device100can be configured as a base station for other wireless devices.

An audio subsystem926can be coupled to a speaker928and a microphone930to facilitate voice-enabled functions, such as speaker recognition, voice replication, digital recording, and telephony functions. The audio subsystem926can be configured to facilitate processing voice commands, voice printing and voice authentication, for example.

The I/O subsystem940can include a touch-surface controller942and/or other input controller(s)944. The touch-surface controller942can be coupled to a touch surface946. The touch surface946and touch-surface controller942can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch surface946.

The other input controller(s)944can be coupled to other input/control devices948, such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of the speaker928and/or the microphone930.

In one implementation, a pressing of the button for a first duration can disengage a lock of the touch surface946; and a pressing of the button for a second duration that is longer than the first duration can turn power to the computing device900on or off. Pressing the button for a third duration can activate a voice control, or voice command, module that enables the user to speak commands into the microphone930to cause the device to execute the spoken command. The user can customize a functionality of one or more of the buttons. The touch surface946can, for example, also be used to implement virtual or soft buttons and/or a keyboard.

In some implementations, the computing device900can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, the computing device900can include the functionality of an MP3 player, such as an iPod™. The computing device900can, therefore, include a 36-pin connector that is compatible with the iPod. Other input/output and control devices can also be used.

The memory interface902can be coupled to memory950. The memory950can include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). The memory950can store an operating system952, such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks.

The operating system952can include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, the operating system952can be a kernel (e.g., UNIX kernel). In some implementations, the operating system952can include instructions for performing voice authentication. For example, operating system952can implement the media stream personalization features as described with reference toFIGS. 1-8.

The memory950can also store communication instructions954to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. The memory950can include graphical user interface instructions956to facilitate graphic user interface processing; sensor processing instructions958to facilitate sensor-related processing and functions; phone instructions960to facilitate phone-related processes and functions; electronic messaging instructions962to facilitate electronic-messaging related processes and functions; web browsing instructions964to facilitate web browsing-related processes and functions; media processing instructions966to facilitate media processing-related processes and functions; GNSS/Navigation instructions968to facilitate GNSS and navigation-related processes and instructions; and/or camera instructions970to facilitate camera-related processes and functions.

The memory950can store other software instructions972to facilitate other processes and functions, such as the media stream personalization processes and functions as described with reference toFIGS. 1-8.

The memory950can also store other software instructions974, such as web video instructions to facilitate web video-related processes and functions; and/or web shopping instructions to facilitate web shopping-related processes and functions. In some implementations, the media processing instructions966are divided into audio processing instructions and video processing instructions to facilitate audio processing-related processes and functions and video processing-related processes and functions, respectively.