Patent Grant
12124768
The disclosure is related to digital content and, more particularly, to methods and systems to select an audio track.
Technological advancements have increased the accessibility of audio tracks such as, for example, music content. For example, a user can access audio content over the Internet through an online store, an Internet radio station, an online music service, an online movie service, and the like, in addition to the more traditional avenues of accessing audio content. Commonly a user selects the music he or she wishes to hear, and new music is discovered through friends or other associates or via advertisements such as television advertisements.
Features, aspects, and advantages of the presently disclosed technology are better understood with regard to the following description, appended claims, and accompanying drawings where:
In addition, the drawings are for the purpose of illustrating example embodiments, but it is understood that the present disclosure is not limited to the arrangements and instrumentality shown in the drawings.
I. Overview
Certain embodiments disclosed herein enable the selection of particular audio sources or tracks such as, for example, specific songs, playlists, artists, albums and/or genres. Music listeners have a variety of listening habits that depend on many conditions (e.g., playback conditions) and music properties. A playback condition may be any condition, state, attribute, characteristic and/or other situation or metric related to the playing of an audio track. The playback conditions may include time related conditions, location related conditions, and/or listener or user related conditions. A music property may include a tempo, a rhythm, a genre, an artist and/or a tagging to any of the conditions disclosed herein.
A time related playback condition may include, for example, a time of day. For example, some music listeners prefer to listen to a talk show in the morning. Others prefer lower tempo or “chill out” music in the morning. Also, some music listeners prefer faster music with a more upbeat tempo in an afternoon or during, for example, a Friday evening. Example time playback conditions may include a specific hour, a morning, an afternoon, an evening, a night, a day of the week, a month, a year, a time of year, a holiday, an event, a birthday, a wedding anniversary, an anniversary of a world or historical event, a date related to a milestone, a date related to what tracks were played last year or at specific past events, and/or any other time related metric. These time related events are correlated to different music desires for different music listeners. Time related playback conditions also may include, for example, a frequency of a play of a particular audio track and/or a recentness of a particular play of a track.
A location related playback condition may include, for example, a geographic location, a particular zone in a house or other building, a zone group, a zone room, a particular zone player in a room, a particular room, an outdoor location, an indoor location, a presence of a vehicle and/or any other location. Music listeners may listen to different tracks of music in different locations. A music listener may want to hear a particular set of songs if located, for example, poolside and a different set of songs if located, for example, in a child's nursery.
The playback conditions may also be related to the user (e.g., the listener). The user related playback conditions could be who the user is, e.g., the user's identity, a demographic group and/or an interest. Different people prefer to listen to different types of music. In addition, generalizations may be made about the musical tastes of certain demographic groups. For example, baby boomers may prefer to listen to classic rock. Teenagers may prefer, for example, to listen to the Billboard Top 40.
In addition, the playback conditions may be related to social relationships between the user and other listeners. If the user has “friended” or otherwise subscribed to another user's music listening patterns, the user may receive recommendations (e.g., selected audio tracks) based on the user's friends' listening habits. Additionally, audio track selection(s) based on social network connections also may be correlated with temporal and/or other conditions. Furthermore, in some examples, audio track selection(s) based on social network connections may be presented to two or more users to enable the users to engage in co-listening of the selected audio track(s).
Other condition(s) may include weather-related conditions such as, for example, playing particular song(s) when it is sunny and/or other song(s) when it is rainy. Any condition(s) may be defined by the user of the example systems disclosed herein.
Typically when a user wants to hear one or more particular audio track(s) based on, for example, a time, location or user related playback condition, the user has to manually obtain and play a song that has properties that satisfies one or more of the condition(s). In some situations, the user may be unaware of suitable audio tracks with properties that meet the conditions because, for example, an audio track is newly released, the user has not been exposed to the track and/or the user otherwise does not remember or have knowledge of the track to be able to choose it for playback. In other examples, the user may be unaware of the conditions.
The examples disclosed herein enable automatic selection of audio tracks for presentation to a user based on playback conditions such as, for example, time, location, user characteristics and/or other conditions. The examples disclosed herein match one or more properties of one or more audio tracks with the playback conditions and selects those tracks with properties that satisfy the conditions for presentation to the user for playback. Thus, certain embodiments disclosed herein use time, location and/or other conditions to provide relevant music without the user doing anything other than listening to what they listen to, and the example system disclosed herein further associates the music with zone groups, rooms, zone players and time slots. Additional embodiments are described herein.
As used herein, “audio track” or “track” refers to an audio source, audio file, music, a song and/or any other sound-based file.
Moving on from the above illustration, an example embodiment of a method of selecting an audio track is disclosed herein. The example method includes that includes detecting a first playback condition and detecting a second playback condition. In addition, the example method includes comparing, using a processor, a first audio track property of a first audio track to the first playback condition and the second playback condition to determine if the first audio track property matches one or more of the first playback condition or the second playback condition. The example also includes comparing, with the processor, a second audio track property of the first audio track to the first playback condition and the second playback condition to determine if the second audio track property matches one or more of the first playback condition or the second playback condition. In addition, the example method includes selecting the first audio track for presentation to a user when the first playback condition matches one or more of the first audio track property or the second audio track property and the second playback condition matches one or more of the first audio track property or the second audio track property.
In some embodiments, the first condition is a time and the second condition is a location and the first property is a time and the second property is a location. In some examples, the time is one or more of an hour, a day, a portion of a day, a timeslot, a frequency of two or more prior playbacks and/or a recentness of a prior playback.
In some embodiments, the location is one or more of a geographic location, an outdoor location, a vehicle location, a room and/or a zone.
In some embodiments, the first condition and the first property are a characteristic of the user. In some embodiments, the characteristic of the user is one or more of an identity of the user, a demographic group and/or an interest. In some embodiments, the method includes identifying the user based on a profile associated with a playback device. In some embodiments, the method includes identifying the user based on an operation history of a playback device.
In some embodiments, the first condition and the first property are defined by the user.
In some embodiments, the first condition and the first property comprise one or more of a rhythm, a tempo and/or a genre.
In some embodiments, the method also includes presenting the audio track for playback to the user by one or more of playing the audio track, queuing the audio track for playback and/or presenting the user with a link to obtain the audio track.
The method also includes, in some examples, comparing, using the processor, a third audio track property of a second audio track to the first playback condition and the second playback condition to determine if the third audio track property matches one or more of the first playback condition or the second playback condition. In addition, the example method includes comparing, with the processor, a fourth audio track property of the second audio track to the first playback condition and the second playback condition to determine if the fourth audio track property matches one or more of the first playback condition or the second playback condition. In addition, the example method includes selecting the second audio track for presentation to a user when the first playback condition matches one or more of the third audio track property or the fourth audio track property and the second playback condition matches one or more of the third audio track property or the fourth audio track property.
Example systems to select an audio track also are disclosed. An embodiments of an example system includes a detector to detect a first playback condition and a second playback condition. The example system also includes a comparator to compare a first audio track property of a first audio track to the first playback condition and the second playback condition to determine if the first audio track property matches one or more of the first playback condition or the second playback condition, and to compare a second audio track property of the first audio track to the first playback condition and the second playback condition to determine if the second audio track property matches one or more of the first playback condition or the second playback condition. In addition, the example system includes a selector to select the first audio track for presentation to the user when the first playback condition matches one or more of the first audio track property or the second audio track property and the second playback condition matches one or more of the first audio track property or the second audio track property.
In some embodiments, the detector is to identify the user based on one or more of a profile associated with a playback device and/or an operation history of the playback device.
In some embodiments, the system includes a display to present the audio track for playback to the user by one or more of playing the audio track, queuing the audio track for playback and/or presenting the user with a link to obtain the audio track. In some embodiments, the display is a graphical user interface to visually present one or more of the audio track or other information to the user. In some embodiments, the display is integrated with a playback device such as, for example, with a controller of the playback device.
In some embodiments, the comparator is to compare a third audio track property of a second audio track to the first playback condition and the second playback condition to determine if the third audio track property matches one or more of the first playback condition or the second playback condition, and to compare a fourth audio track property of the second audio track to the first playback condition and the second playback condition to determine if the fourth audio track property matches one or more of the first playback condition or the second playback condition. In addition, in such embodiments, the selector is to select the second audio track for presentation to the user when the first playback condition matches one or more of the third audio track property or the fourth audio track property and the second playback condition matches one or more of the third audio track property or the fourth audio track property.
Example tangible machine readable media are disclosed herein. In some embodiments, an example machine readable medium has instructions stored therein, which when executed, cause the machine to at least detect a first playback condition and detect a second playback condition. The example medium also causes the machine to compare a first audio track property of a first audio track to the first playback condition and the second playback condition to determine if the first audio track property matches one or more of the first playback condition or the second playback condition, and compare a second audio track property of the first audio track to the first playback condition and the second playback condition to determine if the second audio track property matches one or more of the first playback condition or the second playback condition. In addition, the example medium causes the machine to select the first audio track for presentation to a user when the first playback condition matches one or more of the first audio track property or the second audio track property and the second playback condition matches one or more of the first audio track property or the second audio track property.
In some embodiments, the machine is further caused to identify an identity of the user based on one or more of a profile associated with a playback device and/or an operation history of the playback device, wherein the first condition and the first property are the identity of the user.
Although the following discloses example methods, apparatus, systems, and articles of manufacture including, among other components, firmware and/or software executed on hardware, it should be noted that such methods, apparatus, systems, and/or articles of manufacture are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these firmware, hardware, and/or software components could be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, while the following describes example methods, apparatus, systems, and/or articles of manufacture, the examples provided are not the only way(s) to implement such methods, apparatus, systems, and/or articles of manufacture.
When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible medium such as a memory, DVD, CD, Blu-ray, etc., storing the software and/or firmware, as discussed in greater detail below.
These embodiments and many additional embodiments are described more below. Further, the detailed description is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure may be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments.
Reference herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment disclosed herein. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, may be combined with other embodiments.
II. Example Environment
Referring now to the drawings, in which like numerals may refer to like parts throughout the figures.
As used herein, unless explicitly stated otherwise, audio source(s) or audio track(s) are in digital format and can be transported or streamed over a data network. In the examples disclosed herein, the system 100 will be described as a home. Thus, the zone player 102 and 104 may be located in two bedrooms respectively while the zone player 106 may be installed in a living room. All of the zone players 102, 104 and 106 are coupled directly or indirectly to a data network 108. In addition, a computing device 110 is shown to be coupled on the network 108. In reality, any other devices such as a home gateway device, a storage device, or an MP3 player may be coupled to the network 108 as well.
Example zone players include a “Sonos® S5,” “Sonos Play:5,” “ZonePlayer 120,” and “ZonePlayer 90,” which are offered by Sonos, Inc. of Santa Barbara, California. A zone player may also be referred to herein as a playback device, and a zone player is not limited to the particular examples illustrated herein. For example, a zone player may include a wired or wireless headphone. In another example, a zone player might include a subwoofer. In an example, a zone player may include or interact with a docking station for an Apple iPod™ or similar device. In some embodiments, a zone player may relay one or more signals received from, for example, a first zone player to another playback device. In some embodiments, a zone player may receive a first signal and generate an output corresponding to the first signal and, simultaneously or separately, may receive a second signal and transmit or relay the second signal to another zone player(s), speaker(s), receiver(s), etc. Thus, an example zone player described herein can act as a playback device and, at the same time, operate as a hub in a network of zone players. In such instances, media content corresponding to the first signal may be different from the media content corresponding to the second signal.
The network 108 may be a wired network, a wireless network or a combination of both. In one example, all devices including the zone players 102, 104 and 106 are coupled to the network 108 by wireless means based on an industry standard such as IEEE 802.11. In yet another example, all devices including the zone players 102, 104 and 106 are part of a local area network that communicates with a wide area network (e.g., the Internet).
Many devices on the network 108 are configured to download and store audio sources. For example, the computing device 110 can download audio sources from the Internet and store the downloaded sources locally for sharing with other devices on the Internet or the network 108. The computing device 110 or any of the zone players 102, 104 and 106 can also be configured to receive streaming audio. Shown as a stereo system, the device 112 is configured to receive an analog audio source (e.g., from broadcasting) or retrieve a digital audio source (e.g., from a compact disk). The analog audio sources can be converted to digital audio sources. In some examples, the audio source may be shared among the devices on the network 108.
Two or more zone players may be grouped together to form a new zone group. Any combinations of zone players 102, 104 and 106 and an existing zone group may be grouped together. In one instance, a new zone group is formed by adding one zone player to another zone player or an existing zone group.
The network interface 202 may include one or both of a wireless interface 216 and a wired interface 217. The wireless interface 216, also referred to as an RF interface, provides network interface functions by a wireless means for the zone player 200 to communicate with other devices in accordance with a communication protocol (such as the wireless standard IEEE 802.11 a, 802.11 b or 802.11 g). The wired interface 217 provides network interface functions by a wired means (e.g., an Ethernet cable). In one embodiment, a zone player includes both of the interfaces 216 and 217, and other zone players include only a RF or wired interface. Thus these other zone players communicate with other devices on a network or retrieve audio sources via the zone player 200.
The processor 204 is configured to control the operation of other parts in the zone player 200. The memory 206 may be loaded with one or more software modules 212 that can be executed by the processor 204 to achieve desired tasks. In some examples, the processor 204 operates in accordance with the software module 212 to configure, characterize and/or save a zone group created by a user. Also, in some examples, the processor 204 operates in conjunction with the software module 212 to retrieve an audio source or track from another zone player or a device on the network.
In some embodiments, the memory 206 stores one or more saved zone configuration files that may be retrieved for modification at any time. Typically, a saved zone group configuration file is transmitted to a controller (e.g., the controlling device 140 or 142 of
The audio processing circuit 210 resembles most of the circuitry in an audio playback device and includes one or more digital-to-analog converters (DAC), an audio preprocessing part, an audio enhancement part or a digital signal processor and others. In operation, when an audio source is retrieved via the network interface 202, the audio source is processed in the audio processing circuit 210 to produce analog audio signals. The processed analog audio signals are then provided to the audio amplifier 214 for playback on speakers. In addition, the audio processing circuit 210 may include necessary circuitry to process analog signals as inputs to produce digital signals for sharing with other devices on a network.
Depending on an exact implementation, the module 212 may be implemented as a combination of hardware and software. In one embodiment, the module 212 is used to save a scene. The audio amplifier 214 is typically an analog circuit that powers the provided analog audio signals to drive one or more speakers.
The scroll wheel 250 is used for selecting an item within a list, whenever a list is presented on the screen 242. When the items in the list are too many to be accommodated in one screen display, a scroll indicator such as a scroll bar or a scroll arrow is displayed beside the list. When the scroll indicator is displayed, a user may rotate the scroll wheel 250 to either choose a displayed item or display a hidden item in the list. The “ok” button 252 is used to confirm the user selection on the screen 242.
There are three transport buttons 254, which are used to control the effect of the currently playing song. For example, the functions of the transport buttons may include play/pause and forward/rewind a song, move forward to a next song track, or move backward to a previous track. According to one embodiment, pressing one of the volume control buttons such as the mute button 262 or the volume up/down button 264 activates a volume panel. In addition, there are three soft buttons 266 that can be activated in accordance with the labels 268 on the screen 242. It can be understood that, in a multi-zone system, there may be multiple audio sources being played respectively in more than one zone players. The music transport functions described herein shall apply selectively to one of the sources when a corresponding one of the zone players or zone groups is selected.
The controller 270 includes a network interface 280 referred to as a RF interface 280 that facilitates wireless communication with a zone player via a corresponding RF interface thereof. In one embodiment, the commands such as volume control and audio playback synchronization are sent via the RF interfaces. In another embodiment, a saved zone group configuration is transmitted between a zone player and a controller via the RF interfaces. The controller 270 may control one or more zone players, such as 102, 104 and 106 of
In one embodiment, a user creates a zone group including at least two zone players from the controller 240 that sends signals or data to one of the zone players. As all the zone players are coupled on a network, the received signals in one zone player can cause other zone players in the group to be synchronized so that all the zone players in the group playback an identical audio source or a list of identical audio sources in a timely synchronized manner. Similarly, when a user increases the audio volume of the group from the controller, the signals or data of increasing the audio volume for the group are sent to one of the zone players and causes other zone players in the group to be increased together in volume and in scale.
According to one implementation, an application module is loaded in memory 282 for zone group management. When a predetermined key (e.g. the “zones” button 244) is activated on the controller 240, the application module is executed in the microcontroller 276. The input interface 278 coupled to and controlled by the microcontroller 276 receives inputs from a user. A “Zone Menu” is then displayed on the screen 272. The user may start grouping zone players into a zone group by activating a “Link Zones” or “Add Zone” soft button, or de-grouping a zone group by activating an “Unlink Zones” or “Drop Zone” button. The detail of the zone group manipulation will be further discussed below.
As described above, the input interface 278 includes a number of function buttons as well as a screen graphical user interface. Additionally or alternatively, devices other than the controller 240 that provide the equivalent control functions (e.g., a computing device, a hand-held device) may also be configured to practice the examples disclosed herein. In addition, the controller 240 may provide a social portal through which users can share, among other things, playlists with users of other households. In certain embodiments, any number of controllers may be used to control the system configuration 100. In certain embodiments, there may be a limit on the number of controllers that can control the system configuration 100. The controllers might be wireless like wireless controller 240 or wired to the data network 108. Furthermore, an application running on any network-enabled portable devices, such as an iPhone™, iPad™, Android™ powered phone, or any other smart phone or network-enabled device may be used as a controller by connecting to the data network 108. An application running on a laptop or desktop PC or Mac may also be used as a controller. Example controllers include a “Sonos® Controller 200,” “Sonos® Controller for iPhone,” “Sonos® Controller for iPad,” “Sonos® Controller for Android, “Sonos® Controller for Mac or PC,” which are offered by Sonos, Inc. of Santa Barbara, California.
One mechanism for ‘joining’ zone players together for music playback is to link a number of zone players together to form a group. To link a number of zone players together, a user may manually link each zone player or room one after the other. For example, a multi-zone system may include the following zones: Bathroom, Bedroom, Den, Dining Room, Family Room and/or Foyer. The user can dynamically link one or more of the zone players with a single command. Using what is referred to herein as a “theme” or a “zone scene”, zones can be configured in a particular scene (e.g., morning, afternoon, or garden), where a predefined zone grouping and setting of attributes for the grouping are automatically effectuated.
For instance, a “Morning” zone scene/configuration command would link the Bedroom, Den and Dining Room together in one action. Without this single command, the user would need to manually and individually link each zone. Other examples are disclosed in U.S. patent application Ser. No. 12/035,112, which is hereby incorporated by reference in its entirety.
In certain embodiments, two or more zone players may be sonically consolidated to form a single, consolidated zone player. A consolidated zone player (though made up of multiple, separate devices) may be configured to process and reproduce sound differently than an unconsolidated zone player or zone players that are paired, because a consolidated zone player will have additional speaker drivers from which sound may be passed. The consolidated zone player may further be paired with a single zone player or yet another consolidated zone player. Each playback device of a consolidated playback device is preferably set in a consolidated mode.
According to some embodiments, one can continue to do any of: group, consolidate, and pair zone players, for example, until a desired configuration is complete. The actions of grouping, consolidation, and pairing are preferably performed through a control interface, such as using controller 130, and not by physically connecting and re-connecting speaker wire, for example, to individual, discrete speakers to create different configurations. As such, certain embodiments described herein provide a more flexible and dynamic platform through which sound reproduction can be offered to the end-user.
Sources of audio content to be played by zone players 102-110 are numerous. Music from a personal library stored on a computer or networked-attached storage (NAS) may be accessed via the data network 108 and played. Internet radio stations, shows, and podcasts may be accessed via the data network 108. Music services that let a user stream and download music and audio content may be accessed via the data network 108. Further, music may be obtained from traditional sources, such as a turntable or CD player, via a line-in connection to a zone player, for example. Audio content may also be accessed through AirPlay™ wireless technology by Apple, Inc., for example. Audio content received from one or more sources may be shared amongst the zone players 102-110 via the data network 108 and/or the controller 240.
Regardless of where a user of the system configuration 100 obtains access to his or her audio, the user may share his or her listening experience with a user of a different system configuration, such as a different household. As such, an account holder on a subscription service may share songs with account holders of other subscriptions services. In addition, search capabilities allow songs to be shared across music services or in a local library, by searching for the artist, album, and/or title.
III. Example Audio Track Selection System
Referring now to
The example system 300 includes a detector 302. The example detector 302 detects a first playback condition and a second playback condition. In some examples, the detector 302 detects any number of additional conditions such as for example, three, four, etc. As detailed above, a playback condition may be any condition, state, attribute, characteristic and/or other situation or metric related to the playing of an audio track. For example, the condition may be a time related condition, a location related condition a user related condition and/or any other suitable condition.
The detector 302 detects a condition using, for example, an internal clock and/or calendar to determine a time related condition. The detector 302 may include a GPS unit and/or any other type of sensor that may be used to determine a location related condition. In some examples, the playback device is mobile (e.g., a mobile phone), and the device may include a location sensor to determine a location of the device. In addition, the detector 302 may review previously recorded location data including, for example, a room or a zone corresponding to a playback device.
The example system 300 also includes a comparator 304. The comparator 304 is communicatively coupled to the detector 302 and to other components of the example system 300 via communication links 306. The communication links 306 may be any type of wired (e.g., a databus, a USB connection, etc.) or wireless communication mechanism (e.g., radio frequency, infrared, etc.) using any past, present or future communication protocol (e.g., Bluetooth, USB 2.0, etc.). Also, the components of the example system 400 may be integrated in one device or distributed over two or more devices.
The example comparator 304 compares an audio track property of an audio track to a first playback condition and the second playback condition. The audio track may be stored for example, in a database 308. The database 308 may be, for example, any storage structure including, for example, a local storage memory such as, for example in any of the zone players 102-110 of
The example audio track(s) are associated with related properties. The properties may include for example, the artist, genre, rhythm, tempo, past play history, popularity with each of a number of users, popularity with a demographic group, rating on a ranking chart (e.g., Billboard Top 40, Top 100, etc.), a characteristic to match a condition and/or any other suitable characteristic or metric.
In certain embodiments, track(s) are be tagged with metadata related to the properties. The metadata may be provided by the distributor of the track including, for example, metadata related to the artist, album, genre, etc. In addition, metadata may be added by a user including, for example, an indication that the user likes a certain song, that the user likes a certain song at a certain time of day, likes a certain song while driving, likes to awake to a certain song, that a certain song reminds the user of a certain person or event. Users can tagged a track with metadata related to any type of condition and such metadata becomes part of the property of the track. In certain embodiments, the metadata is tagged to a song automatically. For example, the detector 302 may detect that a specific track is played frequently in the morning and, in such example, the track may be tagged automatically as a morning song. In some examples, the detector 302 detects that a particular user listens to a particular track, and the track may be tagged automatically as related to that user. In some embodiments the metadata may also include information such as, for example, a recentness of a playback of a track and/or a frequency of playback. In addition, the recentness and/or frequency metadata may include a weighting metric to weigh the associated track. For example, a more frequently played track may be more heavily weighed as an indication that the track and/or similar tracks should be selected for playback as described below. Particular artists, albums, genres and other properties may also be weighed. All metadata and other properties may be stored with the tracks in the database 308. In some examples, the audio property is tied to the condition and not necessarily tagged or otherwise tied with the song. For example, a track may be desired to be played at a certain time of day, and the audio track may not necessarily be tagged with the specific time of day. However, if the time of day during the operation of the playback device and/or the selection of the track is, in fact, the time of day specified in the condition, the “audio property” will be deemed to have met the condition.
Based on the comparison of the first audio track property and the first and second playback conditions, the example comparator 304 determines if the first audio track property matches one or more of the first playback condition or the second playback condition. In addition, the example comparator compares a second audio track property of the first audio track to the first playback condition and the second playback condition, and determines if the second audio track property matches one or more of the first playback condition or the second playback condition.
The example system 300 also includes a selector 310. The selector 310 selects an audio track for presentation to the user when the first playback condition matches one or more of the first audio track property or the second audio track property and the second playback condition matches one or more of the first audio track property or the second audio track property.
For example, a particular user's listening habits indicate that he typically listens to bossa nova and jazz in the morning. In this example, a first condition would be the morning time, and the second condition would be the genre bossa nova/jazz. When the user turns on a playback device to listen to music, the example system 300 uses the detector 302 to determine that it is the morning and that the user likes to hear bossa nova/jazz. The comparator 304 compares audio tracks in the database 308 and the associated properties. When a track is analyzed that has properties that indicate that the genre is bossa nova/jazz and the song is suitable or desirable for play in the morning, the selector 310 may choose the track and/or related track(s) (e.g., a playlist) for presentation to the user. For example, the recording artist Thievery Corporation may have properties that include tags from the record label that indicate that the genre of music is bossa nova/jazz and metadata entered by the user or other users, for example, that indicate that they like to hear Thievery Corporation music in the morning. Additionally or alternatively, the system 300 may detect that the user frequently listens to Thievery Corporation in the morning and tags Thievery Corporation tracks as suitable and/or desirable for morning play. In other examples, if the Thievery Corporation track is not specifically tagged as morning-suitable, the track may nonetheless meet the conditions if the time of day is the morning. Thus, the “audio properties” may extend beyond what is actually tagged to a particular track, as noted above.
Also, in this example, if only one of the two conditions is met, for example, if an audio track is tagged as appropriate for the morning, but the genre is country, the comparator 304 would indicate that the track does not match or meet the conditions, and the track would not be selected for presentation to the user.
In some examples, the system 300 may analyze several tracks such that the comparator 304 compares a third audio track property of a second audio track to the first playback condition and the second playback condition to determine if the third audio track property matches one or more of the first playback condition or the second playback condition, and compares a fourth audio track property of the second audio track to the first playback condition and the second playback condition to determine if the fourth audio track property matches one or more of the first playback condition or the second playback condition. In such examples, the selector 310 selects the second audio track for presentation to the user when the first playback condition matches one or more of the third audio track property or the fourth audio track property and the second playback condition matches one or more of the third audio track property or the fourth audio track property.
In some examples, the condition and the related property are related to the user of the playback device. For example, the condition and/or property may be the user's identity, a demographic group and/or an interest of the user. In some embodiments, the detector 302 may detect who the user is based on the registration of the playback device. For example, who registered an iPhone, iPad or other controller that is controlling the zone group, zone room, zone player, etc. The detector 302 may also detect other users controlling other players in other rooms. In such examples, the detector 302 may review account or profile information associated with the device. In other examples, the user may establish an account or profile to operate the device such as, for example, a Sonos® profile or a profile with a free or subscription-based music and/or radio services including, for example, Pandora®, Spotify™, Rhapsody™, MOG, Napster™ and/or any other existing or future music service.
In some embodiments, the system 300 asks the user for his or her identity or for the identity of the person for whom the music for. In some examples, the system 300 can determine who the user is based on an operational history of the playback device. For example, if a user selects a specific genre, skips certain songs, repeats other songs, etc., the system 300 can deduce who is operating the playback device.
In certain embodiments, the example system 300 data mines for further information about the user to better characterize the user and his or her preferences. For example, the system 300 may look to what friends and/or associates of the user are listening to. The friends and/or associates of the user may be people that use the same playback device as the user, people the user has indicated music is intended to be played for, people connected to the user in a social network such as, for example, Facebook, Google+, Myspace, Yelp, LinkedIn, Friendster, Flickr, Twitter, Spotify, Bebo, Renren, Weibo, any other online network and/or any non-internet-based network (e.g., friends, relatives, neighbors, etc.) and/or people who belong to the same demographic groups as the user.
Data may also be gathered about a user or a group of users by analyzing how a user's music selection has changed over time and/or over different locations (e.g., the Beatles were playing in the living last year and this year Bocelli is playing). The system 300 may determine trends such as, for example, trends identifiable on a social network site (e.g., Facebook), a search engine (e.g., Google) and/or a file sharing service (e.g., YouTube). The system 300 may gather and/or analyze data regarding what a user or a group of users liked or disliked on social networks and/or music services. In other examples, the user may be queried for additional demographic and/or personal information including age (e.g., a younger person may like pop music and an older person may like classic country music), where the user was raised, when the user was raised, where the user is currently living (e.g., country music is more popular in certain regions such as the Southern U.S. or rural areas as opposed to the urban coasts of the U.S.), or geographic or regional affinities the user may have (e.g., a user may be a Francophile and, thus, interested in French electronica), memories of world event during childhood and/or adulthood (e.g., users who grew up in the 1940s may have different tastes in music than people who grew up in the 1960s due to cultural and historical events of the time), what music the user likes, what instruments the user likes, and/or any other information including, for example, information seemingly unrelated to music. For example, the user may be asked if he or she would participate in a fox hunt, the response to which may be used to indicate if the user would be interested in listening to classical music.
In some examples, the ser may tag a portion of music that is playing such as, for example, a lyric, a chorus, a riff, etc. The tagged portion may be shared with friends and/or associates via, for example, a link (and via, for example, the controller 240). The tagged portions of tracks may be used to gather further information about a user's taste.
When the selector 310 selects one or more audio track(s) for presentation to the user, the system 300 automatically play the track for the user or may automatically put the track into a playlist or queue for playback. The playlist may be updated over time, including, for example removing unplayed track(s). In addition, in some examples, the track(s) may be presented under a tab visible on a display of the playback device (e.g., the display 242 of
In some examples, the playback device may have a smart play button (e.g., another purpose for the music button 248 of
In some examples disclosed herein, the playback of a track may be included with an alarm. For example, a user who likes surfing may set conditions for a playback device to being playing surf music such as surf rock in the morning (i.e., as an alarm) based on further conditions such as, for example, if an outdoor temperature and/or a water temperature of the ocean exceed a threshold (e.g., 65° F.) and a surf report indicates swells greater than a threshold (e.g., three feet). In this example, there are four conditions, time, genre, weather, and ocean conditions. The first two conditions (time and genre) may be used to select the music for playing as the alarm. The last two conditions (weather and ocean conditions) are not related to the music selection itself, in this example. In other examples, weather and/or ocean conditions may be defined by the user as conditions for song selection. In addition, in this example, the first, third and fourth conditions (time, weather and ocean conditions) are used to determine if the alarm will sound at all. In addition, in certain embodiments, there may be a portal associated with the controller to enable the user to create conditions related to music selection and/or music play.
In another example, an alarm may have conditions tied to a plurality of users. For example, an alarm may sound but require two or more people to shut it off (e.g., a group of Boy Scouts waking up together for a camping trip or a group of employees or peers invited to the same morning meeting).
While example manners of implementing the example systems 100 and 300 to play, match and/or select audio track(s) have been illustrated in
As mentioned above, the example processes of
The example process 400 determines if at least two conditions are met by the audio track properties (block 408). For example, if the conditions are (1) playing a specific genre at (2) a specific time of day, the process 400 reviews the properties of an audio track to determine if the audio track matches the genre and if the audio track has been tagged as music for a particular time of day and/or if the time of day is, in fact, the selected time of day. If the audio properties do not match at least two conditions (block 408), the example process 400 returns to identify another audio track to evaluate (block 404). If the audio properties do match at least two conditions (block 408), the example process 400 determines if additional track(s) are to be evaluated (block 410). If additional track(s) are to be evaluated (block 410), the example process 400 returns to identify another audio track to evaluate (block 404). If additional track(s) are not to be evaluated (block 410), the example process 400 presents the track(s) to the user (block 412) using, for example the displays and presentation described above. The process 400 then ends (block 414).
The computer 500 of the instant example includes a processor 512. For example, the processor 512 can be implemented by one or more Intel® microprocessors from the Pentium® family, the Itanium® family or the XScale® family. Of course, other processors from other families are also appropriate.
The processor 512 is in communication with a main memory including a volatile memory 514 and a non-volatile memory 516 via a bus 518. The volatile memory 514 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/or any other type of random access memory device. The non-volatile memory 516 may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory 514, 516 is typically controlled by a memory controller (not shown).
The computer 500 also includes an interface circuit 520. The interface circuit 520 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface.
One or more input devices 522 are connected to the interface circuit 520. The input device(s) 522 permit a user to enter data and commands into the processor 512. The input device(s) can be implemented by, for example, a keyboard, a mouse, a touchscreen, a track-pad, a trackball, isopoint and/or a voice recognition system.
One or more output devices 524 are also connected to the interface circuit 520. The output devices 524 can be implemented, for example, by display devices (e.g., a liquid crystal display, a cathode ray tube display (CRT), a printer and/or speakers). The interface circuit 520, thus, typically includes a graphics driver card.
The interface circuit 520 also includes a communication device (e.g., the request servicer) such as a modem or network interface card to facilitate exchange of data with external computers via a network (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, coaxial cable, a cellular telephone system, etc.).
The computer 500 also includes one or more mass storage devices 528 for storing software and data. Examples of such mass storage devices 528 include floppy disk drives, hard drive disks, compact disk drives, and digital versatile disk (DVD) drives. The mass storage device 528 may implement the storage database 308.
The coded instructions 532 of
Various inventions have been described in sufficient detail with a certain degree of particularity. It is understood to those skilled in the art that the present disclosure of embodiments has been made by way of examples only and that numerous changes in the arrangement and combination of parts may be resorted without departing from the spirit and scope of the present disclosure as claimed. While the embodiments discussed herein may appear to include some limitations as to the presentation of the information units, in terms of the format and arrangement, the embodiments have applicability well beyond such embodiment, which can be appreciated by those skilled in the art. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.
This application claims the benefit of priority under 35 USC § 120 as a continuation of U.S. patent application Ser. No. 17/967,645 filed on Oct. 17, 2022, and entitled “Audio Track Selection and Playback”, which is a continuation of U.S. patent application Ser. No. 17/570,858 filed on Jan. 7, 2022, issued as U.S. Pat. No. 11,474,778, and entitled “Audio Track Selection and Playback”, which is a continuation of U.S. patent application Ser. No. 17/347,031 filed on Jun. 14, 2021, issued as U.S. Pat. No. 11,474,777, and entitled “Audio Track Selection and Playback”, which is a continuation of U.S. patent application Ser. No. 16/895,747 filed on Jun. 8, 2020, issued as U.S. Pat. No. 11,036,467, and entitled “Audio Track Selection and Playback”, which is a continuation of U.S. patent application Ser. No. 16/447,644 filed on Jun. 20, 2019, issued as U.S. Pat. No. 10,678,500, and entitled “Audio Track Selection and Playback”, which is a continuation of U.S. patent application Ser. No. 15/205,479 filed on Jul. 8, 2016, issued as U.S. Pat. No. 10,359,990, and entitled “Audio Track Selection and Playback”, which is a continuation of U.S. patent application Ser. No. 13/338,724 filed on Dec. 28, 2011, issued as U.S. Pat. No. 9,665,339, and entitled “Methods and Systems to Select an Audio Track”, the contents of each of which are herein incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5406634 | Anderson et al. | Apr 1995 | A |
| 5440644 | Farinelli et al. | Aug 1995 | A |
| 5761320 | Farinelli et al. | Jun 1998 | A |
| 5856827 | Sudo | Jan 1999 | A |
| 5923902 | Inagaki | Jul 1999 | A |
| 6002862 | Takaike | Dec 1999 | A |
| 6029195 | Herz | Feb 2000 | A |
| 6032202 | Lea et al. | Feb 2000 | A |
| 6108686 | Williams, Jr. | Aug 2000 | A |
| 6181316 | Little et al. | Jan 2001 | B1 |
| 6255961 | Van et al. | Jul 2001 | B1 |
| 6256554 | DiLorenzo | Jul 2001 | B1 |
| 6349339 | Williams | Feb 2002 | B1 |
| 6404811 | Cvetko et al. | Jun 2002 | B1 |
| 6469633 | Wachter | Oct 2002 | B1 |
| 6522886 | Youngs et al. | Feb 2003 | B1 |
| 6587127 | Leeke et al. | Jul 2003 | B1 |
| 6611537 | Edens et al. | Aug 2003 | B1 |
| 6631410 | Kowalski et al. | Oct 2003 | B1 |
| 6728531 | Lee et al. | Apr 2004 | B1 |
| 6732155 | Meek | May 2004 | B2 |
| 6757517 | Chang | Jun 2004 | B2 |
| 6778869 | Champion | Aug 2004 | B2 |
| 6826283 | Wheeler et al. | Nov 2004 | B1 |
| 6985694 | De Bonet et al. | Jan 2006 | B1 |
| 7017118 | Carroll | Mar 2006 | B1 |
| 7020048 | McComas | Mar 2006 | B2 |
| 7113833 | Brown et al. | Sep 2006 | B1 |
| 7117451 | Sielken | Oct 2006 | B2 |
| 7124125 | Cook et al. | Oct 2006 | B2 |
| 7130608 | Hollstrom et al. | Oct 2006 | B2 |
| 7130616 | Janik | Oct 2006 | B2 |
| 7143939 | Henzerling | Dec 2006 | B2 |
| 7187947 | White et al. | Mar 2007 | B1 |
| 7236739 | Chang | Jun 2007 | B2 |
| 7236773 | Thomas | Jun 2007 | B2 |
| 7295548 | Blank et al. | Nov 2007 | B2 |
| 7312785 | Tsuk et al. | Dec 2007 | B2 |
| 7358960 | Mak | Apr 2008 | B2 |
| 7391791 | Balassanian et al. | Jun 2008 | B2 |
| 7483538 | McCarty et al. | Jan 2009 | B2 |
| 7496623 | Szeto et al. | Feb 2009 | B2 |
| 7496633 | Szeto et al. | Feb 2009 | B2 |
| 7571014 | Lambourne | Aug 2009 | B1 |
| 7580325 | Welk et al. | Aug 2009 | B2 |
| 7599685 | Goldberg et al. | Oct 2009 | B2 |
| 7630501 | Blank et al. | Dec 2009 | B2 |
| 7643894 | Braithwaite et al. | Jan 2010 | B2 |
| 7657224 | Goldberg et al. | Feb 2010 | B2 |
| 7657910 | McAulay et al. | Feb 2010 | B1 |
| 7698009 | Cotey | Apr 2010 | B2 |
| 7725533 | Szeto et al. | May 2010 | B2 |
| 7725551 | Szeto et al. | May 2010 | B2 |
| 7739271 | Cook et al. | Jun 2010 | B2 |
| 7739596 | Clarke-Martin et al. | Jun 2010 | B2 |
| 7742740 | Goldberg et al. | Jun 2010 | B2 |
| 7774078 | Booth et al. | Aug 2010 | B2 |
| 7805682 | Lambourne | Sep 2010 | B1 |
| 7835689 | Goldberg et al. | Nov 2010 | B2 |
| 7853341 | McCarty et al. | Dec 2010 | B2 |
| 7865137 | Goldberg et al. | Jan 2011 | B2 |
| 7912565 | Tazine et al. | Mar 2011 | B2 |
| 7916877 | Goldberg et al. | Mar 2011 | B2 |
| 7917082 | Goldberg et al. | Mar 2011 | B2 |
| 7962482 | Handman et al. | Jun 2011 | B2 |
| 7987294 | Bryce et al. | Jul 2011 | B2 |
| 7987426 | Cotter et al. | Jul 2011 | B2 |
| 8014423 | Thaler et al. | Sep 2011 | B2 |
| 8023663 | Goldberg | Sep 2011 | B2 |
| 8028038 | Weel | Sep 2011 | B2 |
| 8028323 | Weel | Sep 2011 | B2 |
| 8045952 | Qureshey et al. | Oct 2011 | B2 |
| 8050652 | Qureshey et al. | Nov 2011 | B2 |
| 8074253 | Nathan | Dec 2011 | B1 |
| 8103009 | McCarty et al. | Jan 2012 | B2 |
| 8131390 | Braithwaite et al. | Mar 2012 | B2 |
| 8135669 | Olstad et al. | Mar 2012 | B2 |
| 8214873 | Weel | Jul 2012 | B2 |
| 8230099 | Weel | Jul 2012 | B2 |
| 8234395 | Millington | Jul 2012 | B2 |
| 8392468 | Sato | Mar 2013 | B2 |
| 8483853 | Lambourne | Jul 2013 | B1 |
| 8762843 | Morse et al. | Jun 2014 | B2 |
| 8910265 | Lang et al. | Dec 2014 | B2 |
| 8942252 | Balassanian et al. | Jan 2015 | B2 |
| 9137564 | Reimann | Sep 2015 | B2 |
| 9232277 | Vega-Zayas et al. | Jan 2016 | B2 |
| 9245020 | Joffray et al. | Jan 2016 | B2 |
| 9247363 | Triplett et al. | Jan 2016 | B2 |
| 9286384 | Kuper et al. | Mar 2016 | B2 |
| 9338514 | Kumar et al. | May 2016 | B2 |
| 9374607 | Bates et al. | Jun 2016 | B2 |
| 9478247 | Chen et al. | Oct 2016 | B2 |
| 9491499 | Wagenaar et al. | Nov 2016 | B2 |
| 9501533 | Coburn, IV et al. | Nov 2016 | B2 |
| 9524338 | Van Der Heide et al. | Dec 2016 | B2 |
| 9547647 | Badaskar et al. | Jan 2017 | B2 |
| 9665339 | Reimann et al. | May 2017 | B2 |
| 9672213 | Brown et al. | Jun 2017 | B2 |
| 9674587 | Triplett et al. | Jun 2017 | B2 |
| 9680960 | Chen et al. | Jun 2017 | B2 |
| 9690466 | Coburn | Jun 2017 | B2 |
| 9703521 | Kumar et al. | Jul 2017 | B2 |
| 9705950 | Trammell | Jul 2017 | B2 |
| 9735978 | Kumar et al. | Aug 2017 | B2 |
| 9947316 | Millington | Apr 2018 | B2 |
| 10028028 | Kumar | Jul 2018 | B2 |
| 10095469 | Reimann et al. | Oct 2018 | B2 |
| 10102855 | Sindhwani | Oct 2018 | B1 |
| 10129599 | Van Der Heide | Nov 2018 | B2 |
| 10268352 | Coburn, IV et al. | Apr 2019 | B2 |
| 10296884 | Lang et al. | May 2019 | B2 |
| 10359990 | Reimann et al. | Jul 2019 | B2 |
| 10592086 | Bates | Mar 2020 | B2 |
| 10678500 | Reimann et al. | Jun 2020 | B2 |
| 10715973 | Kumar et al. | Jul 2020 | B2 |
| 10877637 | Antos et al. | Dec 2020 | B1 |
| 11016727 | Reimann | May 2021 | B2 |
| 11036467 | Reimann | Jun 2021 | B2 |
| 11068528 | Brown et al. | Jul 2021 | B2 |
| 11100922 | Mutagi et al. | Aug 2021 | B1 |
| 11178716 | Baik et al. | Nov 2021 | B2 |
| 11474778 | Reimann | Oct 2022 | B2 |
| 11513763 | Lang | Nov 2022 | B2 |
| 20010042107 | Palm | Nov 2001 | A1 |
| 20020002039 | Qureshey et al. | Jan 2002 | A1 |
| 20020022453 | Balog et al. | Feb 2002 | A1 |
| 20020026442 | Lipscomb et al. | Feb 2002 | A1 |
| 20020040352 | McCormick | Apr 2002 | A1 |
| 20020056117 | Hasegawa et al. | May 2002 | A1 |
| 20020124097 | Isely et al. | Sep 2002 | A1 |
| 20020163361 | Parkin | Nov 2002 | A1 |
| 20020165921 | Sapieyevski | Nov 2002 | A1 |
| 20020178191 | Sielken | Nov 2002 | A1 |
| 20030023741 | Tomassetti et al. | Jan 2003 | A1 |
| 20030073432 | Meade | Apr 2003 | A1 |
| 20030157951 | Hasty, Jr. | Aug 2003 | A1 |
| 20030210796 | McCarty et al. | Nov 2003 | A1 |
| 20030221541 | Platt | Dec 2003 | A1 |
| 20040024478 | Hans et al. | Feb 2004 | A1 |
| 20040025185 | Goci et al. | Feb 2004 | A1 |
| 20040078383 | Mercer et al. | Apr 2004 | A1 |
| 20040078812 | Calvert | Apr 2004 | A1 |
| 20040088328 | Cook et al. | May 2004 | A1 |
| 20040215611 | Jawa et al. | Oct 2004 | A1 |
| 20040261040 | Radcliffe et al. | Dec 2004 | A1 |
| 20050108320 | Lord et al. | May 2005 | A1 |
| 20050166157 | Ollis et al. | Jul 2005 | A1 |
| 20060107237 | Kim | May 2006 | A1 |
| 20060168340 | Heller et al. | Jul 2006 | A1 |
| 20060253436 | Cook et al. | Nov 2006 | A1 |
| 20060253782 | Stark et al. | Nov 2006 | A1 |
| 20070025194 | Morse et al. | Feb 2007 | A1 |
| 20070038999 | Millington | Feb 2007 | A1 |
| 20070088747 | Cheng et al. | Apr 2007 | A1 |
| 20070142944 | Goldberg et al. | Jun 2007 | A1 |
| 20070214106 | Johnston et al. | Sep 2007 | A1 |
| 20070239562 | Lawson | Oct 2007 | A1 |
| 20070266843 | Schneider | Nov 2007 | A1 |
| 20070288470 | Kauniskangas et al. | Dec 2007 | A1 |
| 20070294131 | Roman et al. | Dec 2007 | A1 |
| 20080005690 | Van Vugt | Jan 2008 | A1 |
| 20080016465 | Foxenland | Jan 2008 | A1 |
| 20080052371 | Partovi et al. | Feb 2008 | A1 |
| 20080066102 | Abraham et al. | Mar 2008 | A1 |
| 20080086750 | Yasrebi et al. | Apr 2008 | A1 |
| 20080131085 | Ikeda et al. | Jun 2008 | A1 |
| 20080155588 | Roberts et al. | Jun 2008 | A1 |
| 20080211661 | Gifford et al. | Sep 2008 | A1 |
| 20080250328 | Konttinen | Oct 2008 | A1 |
| 20090031254 | Herpel et al. | Jan 2009 | A1 |
| 20090063975 | Bull et al. | Mar 2009 | A1 |
| 20090106297 | Wright et al. | Apr 2009 | A1 |
| 20090157680 | Crossley et al. | Jun 2009 | A1 |
| 20090171715 | Conley et al. | Jul 2009 | A1 |
| 20090228919 | Zott et al. | Sep 2009 | A1 |
| 20090234878 | Herz et al. | Sep 2009 | A1 |
| 20090249222 | Schmidt et al. | Oct 2009 | A1 |
| 20090292819 | Kandekar et al. | Nov 2009 | A1 |
| 20090307062 | Lutnick et al. | Dec 2009 | A1 |
| 20100017366 | Robertson et al. | Jan 2010 | A1 |
| 20100082641 | Rinckes et al. | Apr 2010 | A1 |
| 20100205222 | Gajdos et al. | Aug 2010 | A1 |
| 20100235741 | Newman et al. | Sep 2010 | A1 |
| 20100262909 | Hsieh | Oct 2010 | A1 |
| 20100268360 | Ingrassia et al. | Oct 2010 | A1 |
| 20100281369 | Bell et al. | Nov 2010 | A1 |
| 20100293187 | Biehn et al. | Nov 2010 | A1 |
| 20100299639 | Ramsay | Nov 2010 | A1 |
| 20110004330 | Rothkopf et al. | Jan 2011 | A1 |
| 20110106954 | Chatterjee et al. | May 2011 | A1 |
| 20110131272 | Littlejohn et al. | Jun 2011 | A1 |
| 20110154198 | Bachman et al. | Jun 2011 | A1 |
| 20110161348 | Oron | Jun 2011 | A1 |
| 20120023099 | Crossley et al. | Jan 2012 | A1 |
| 20120054233 | Svendsen et al. | Mar 2012 | A1 |
| 20120059914 | Banger et al. | Mar 2012 | A1 |
| 20120071996 | Svendsen | Mar 2012 | A1 |
| 20120089910 | Cassidy | Apr 2012 | A1 |
| 20120117017 | Phillips et al. | May 2012 | A1 |
| 20120117586 | McCoy et al. | May 2012 | A1 |
| 20120150614 | Dion et al. | Jun 2012 | A1 |
| 20120254256 | Martin | Oct 2012 | A1 |
| 20120254363 | Martin et al. | Oct 2012 | A1 |
| 20120272266 | Ou et al. | Oct 2012 | A1 |
| 20130076651 | Reimann | Mar 2013 | A1 |
| 20130148720 | Rabii | Jun 2013 | A1 |
| 20130347018 | Limp et al. | Dec 2013 | A1 |
| 20140005813 | Reimann | Jan 2014 | A1 |
| 20140129015 | Lindahl et al. | May 2014 | A1 |
| 20140149553 | Bank et al. | May 2014 | A1 |
| 20140277639 | Gomes-Casseres et al. | Sep 2014 | A1 |
| 20140368737 | Hoffert et al. | Dec 2014 | A1 |
| 20150095323 | Bates | Apr 2015 | A1 |
| 20150253960 | Lin et al. | Sep 2015 | A1 |
| 20150277851 | Kumar et al. | Oct 2015 | A1 |
| 20150355879 | Beckhardt et al. | Dec 2015 | A1 |
| 20170330429 | Tak et al. | Nov 2017 | A1 |
| 20180316958 | Anschutz | Nov 2018 | A1 |
| 20200275250 | Choi et al. | Aug 2020 | A1 |
| 20200412822 | Allen | Dec 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 1389853 | Feb 2004 | EP |
| 100890993 | Mar 2009 | KR |
| 200153994 | Jul 2001 | WO |
| 2003093950 | Nov 2003 | WO |
| 2012030006 | Mar 2012 | WO |
| Entry |
|---|
| Notice of Allowance mailed on Feb. 9, 2021, issued in connection with U.S. Appl. No. 16/895,747, filed Jun. 8, 2020, 7 pages. |
| Office Communicaiton mailed on Nov. 8, 2016, issued in connection with U.S. Appl. No. 14/300,564, filed Jun. 10, 2014, 3 pages. |
| Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages. |
| Preinterview First Office Action mailed on Nov. 1, 2016, issued in connection with U.S. Appl. No. 14/300,564, filed Jun. 10, 2014, 5 pages. |
| Presentations at WinHEC 2000, May 2000, 138 pages. |
| PRISMIQ, Inc., “PRISMIQ Media Player User Guide,” 2003, 44 pages. |
| United States Patent and Trademark Office, U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages. |
| United States Patent and Trademark Office, U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages. |
| UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54. |
| Van Buskirk, Eliot, “Music Needs ‘Connective Tissue’ and Facebook Wants to Build It,” E http://evolver.fm/2011/09/01/music-needs-connective-tissue-and-facebook-wants-to-build-it, 2011, 6 pages. |
| Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages. |
| Yamaha DME Designer 3.0 Owner's Manual; Copyright 2008, 501 pages. |
| Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages. |
| Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages. |
| Advisory Action mailed on Sep. 16, 2015, issued in connection with U.S. Appl. No. 13/338,724, filed Dec. 28, 2011, 3 pages. |
| Advisory Action mailed on Aug. 8, 2018, issued in connection with U.S. Appl. No. 15/205,479, filed Jul. 8, 2016, 2 pages. |
| AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages. |
| AudioTron Reference Manual, Version 3.0, May 2002, 70 pages. |
| AudioTron Setup Guide, Version 3.0, May 2002, 38 pages. |
| Bluetooth. “Specification of the Bluetooth System: The ad hoc SCATTERNET for affordable and highly functional wireless connectivity,” Core, Version 1.0 A, Jul. 26, 1999, 1068 pages. |
| Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 pages. |
| Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages. |
| Dell, Inc. “Start Here,” Jun. 2000, 2 pages. |
| “Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages. |
| European Patent Office, European Office Action mailed on Aug. 5, 2019, issued in connection with European Application No. 15806449.3, 6 pages. |
| European Patent Office, European Search Report mailed on Oct. 6, 2021, issued in connection with European Application No. 21187081.1, 5 pages. |
| European Patent Office, European Search Report mailed on Oct. 5, 2017, issued in connection with EP Application No. 15806449.3, 10 pages. |
| Final Office Action mailed on Jul. 8, 2015, issued in connection with U.S. Appl. No. 13/338,724, filed Dec. 28, 2011, 15 pages. |
| Final Office Action mailed on May 31, 2018, issued in connection with U.S. Appl. No. 15/205,479, filed Jul. 8, 2016, 10 pages. |
| First Action Interview Office Action mailed on Nov. 17, 2016, issued in connection with U.S. Appl. No. 14/300,564, filed Jun. 10, 2014, 3 pages. |
| International Bureau, International Preliminary Report on Patentability mailed on Apr. 3, 2014, issued in connection with International Application No. PCT/US2012/056467, filed on Sep. 21, 2011, 11 pages. |
| International Bureau, International Preliminary Report on Patentability mailed on Dec. 22, 2016, issued in connection with International Application No. PCT/US2015/032169, filed on May 22, 2015, 7 pages. |
| International Searching Authority, International Search Report and Written Opinion mailed on Oct. 8, 2015, issued in connection with International Application No. PCT/US2015/032169, filed on May 22, 2015, 10 pages. |
| International Searhing Authority, International Search Report and Written Opinion mailed on Feb. 28, 2013, issued in connection with International Application No. PCT/US2012/056467, filed on Sep. 21, 2012, 12 pages. |
| Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861. |
| Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 http://www.reviewsonline.com/articles/961906864.htm retrieved Jun. 18, 2014, 2 pages. |
| Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages. |
| Non-Final Office Action mailed on Nov. 1, 2017, issued in connection with U.S. Appl. No. 15/205,479, filed Jul. 8, 2016, 7 pages. |
| Non-Final Office Action mailed on Oct. 6, 2016, issued in connection with U.S. Appl. No. 13/338,724, filed Dec. 28, 2011, 15 pages. |
| Non-Final Office Action mailed on Aug. 14, 2023, issued in connection with U.S. Appl. No. 17/967,645, filed Oct. 17, 2022, 11 pages. |
| Non-Final Office Action mailed on Nov. 16, 2018, issued in connection with U.S. Appl. No. 15/205,479, filed Jul. 8, 2016, 8 pages. |
| Non-Final Office Action mailed on Oct. 17, 2017, issued in connection with U.S. Appl. No. 15/613,762, filed Jun. 5, 2017, 13 pages. |
| Non-Final Office Action mailed on Oct. 17, 2019, issued in connection with U.S. Appl. No. 16/447,644, filed Jun. 20, 2019, 8 pages. |
| Non-Final Office Action mailed on Aug. 18, 2023, issued in connection with U.S. Appl. No. 18/330,900, filed Jun. 7, 2023, 10 pages. |
| Non-Final Office Action mailed on Nov. 21, 2014, issued in connection with U.S. Appl. No. 13/338,724, filed Dec. 28, 2011, 18 pages. |
| Non-Final Office Action mailed on Dec. 28, 2017, issued in connection with U.S. Appl. No. 15/205,753, filed Jul. 8, 2016, 7 pages. |
| Non-Final Office Action mailed on Sep. 28, 2023, issued in connection with U.S. Appl. No. 17/378,849, filed Jul. 19, 2021, 18 pages. |
| Non-Final Office Action mailed on Mar. 30, 2022, issued in connection with U.S. Appl. No. 17/347,031, filed Jun. 14, 2021, 10 pages. |
| Non-Final Office Action mailed on Mar. 31, 2022, issued in connection with U.S. Appl. No. 17/570,858, filed Jan. 7, 2022, 11 pages. |
| Non-Final Office Action mailed on Mar. 4, 2021, issued in connection with U.S. Appl. No. 17/132,661, filed Dec. 23, 2020, 11 pages. |
| Non-Final Office Action mailed on Aug. 5, 2020, issued in connection with U.S. Appl. No. 15/999,400, filed Aug. 20, 2018, 12 pages. |
| Non-Final Office Action mailed on Jul. 9, 2020, issued in connection with U.S. Appl. No. 16/895,747, filed Jun. 8, 2020, 9 pages. |
| Notice of Allowance mailed on Apr. 11, 2017, issued in connection with U.S. Appl. No. 13/338,724, filed Dec. 28, 2011, 8 pages. |
| Notice of Allowance mailed on Mar. 11, 2021, issued in connection with U.S. Appl. No. 15/999,400, filed Aug. 20, 2018, 9 pages. |
| Notice of Allowance mailed on Jul. 13, 2018, issued in connection with U.S. Appl. No. 15/205,753, filed Jul. 3, 2016, 5 pages. |
| Notice of Allowance mailed on Mar. 13, 2019, issued in connection with U.S. Appl. No. 15/205,479, filed Jul. 8, 2016, 8 pages. |
| Notice of Allowance mailed on Dec. 14, 2022, issued in connection with U.S. Appl. No. 16/680,232, filed Nov. 11, 2019, 9 pages. |
| Notice of Allowance mailed on Apr. 16, 2021, issued in connection with U.S. Appl. No. 17/132,661, filed Dec. 23, 2020, 9 pages. |
| Notice of Allowance mailed on Jun. 17, 2022, issued in connection with U.S. Appl. No. 17/347,031, filed Jun. 14, 2021, 7 pages. |
| Notice of Allowance mailed on Jun. 23, 2022, issued in connection with U.S. Appl. No. 17/570,858, filed Jan. 7, 2022, 7 pages. |
| Notice of Allowance mailed on Mar. 23, 2017, issued in connection with U.S. Appl. No. 14/300,564, filed Jun. 10, 2014, 14 pages. |
| Notice of Allowance mailed on Apr. 27, 2018, issued in connection with U.S. Appl. No. 15/613,762, filed Jun. 6, 2017, 11 pages. |
| Notice of Allowance mailed on Sep. 27, 2023, issued in connection with U.S. Appl. No. 18/330,900, filed Jun. 7, 2023, 7 pages. |
| Notice of Allowance mailed on Jan. 30, 2020, issued in connection with U.S. Appl. No. 16/447,644, filed Jun. 20, 2019, 7 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230359431 A1 | Nov 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17967645 | Oct 2022 | US |
| Child | 18355000 | US | |
| Parent | 17570858 | Jan 2022 | US |
| Child | 17967645 | US | |
| Parent | 17347031 | Jun 2021 | US |
| Child | 17570858 | US | |
| Parent | 16895747 | Jun 2020 | US |
| Child | 17347031 | US | |
| Parent | 16447644 | Jun 2019 | US |
| Child | 16895747 | US | |
| Parent | 15205479 | Jul 2016 | US |
| Child | 16447644 | US | |
| Parent | 13338724 | Dec 2011 | US |
| Child | 15205479 | US |
