The disclosure is related to consumer goods and, more particularly, to methods, systems, products, features, services, and other elements directed to media playback or some aspect thereof.
Options for accessing and listening to digital audio in an out-loud setting were limited until in 2003, when SONOS, Inc. filed for one of its first patent applications, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering a media playback system for sale in 2005. The Sonos Wireless HiFi System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a smartphone, tablet, or computer, one can play what he or she wants in any room that has a networked playback device. Additionally, using the controller, for example, different songs can be streamed to each room with a playback device, rooms can be grouped together for synchronous playback, or the same song can be heard in all rooms synchronously.
Given the ever growing interest in digital media, there continues to be a need to develop consumer-accessible technologies to further enhance the listening experience.
Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings where:
The drawings are for the purpose of illustrating example embodiments, but it is understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings.
Embodiments described herein involve, inter alia, a playback device of a media playback system acquiring a zone property from a device base. Zone properties may define how a playback device operates as part of a given zone of a media playback system. For instance, a playback device may acquire a zone property that causes the playback device to join a particular zone when the playback device is placed on a particular device base. Conversely, the playback device may lose the zone property and leave the zone when the playback device is removed from the device base. Such functionality of a playback device with respect to a device base may facilitate a playback device operating both at times as a stationary playback device and at other times as a portable playback device.
A device of a media playback system, such as a playback device or a control device, may assign a zone property to a device base. For instance, a given device base may be assigned the characteristic of “right” channel in a stereo pair that belongs to the “Den” zone. Upon being placed on the given device base, a playback device may acquire this zone property such that the playback device operates as the “right” channel in the stereo pair that belongs to the “Den” zone. As another example, a given device base may be assigned the zone property of the “Living Room” zone such that a playback device placed on that device base will assign itself that zone property and join the “Living Room” zone. As a member of the Living Room zone, the playback device may playback media in synchrony with other playback devices that are members of other zones that have been grouped into a zone group with the Living Room zone.
As noted above, assigning a zone property to a playback device may cause a playback device to join a particular zone. Further, by acquiring a particular zone property, a playback device may assume a particular role within that zone, such as a channel of a stereo pair, or possibly a channel of a surround sound configuration. Yet further, in some examples, an example zone may be associated with a pre-existing queue of media items such that by acquiring the particular zone property of the example zone, the playback device adopts the pre-existing queue of media items as its queue. In some cases, the example zone may be grouped with one or more additional zones into a zone group that is associated with a pre-existing queue of media items. Then, the playback device may play back the adopted queue of media items in synchrony with other playback devices of the grouped zones.
When a playback device is removed from a given device base, the playback device may lose the zone property that the device acquired from the device base. Further, the playback device may be assigned another zone property, which might be a zone property that is associated with playback devices that are not docked (e.g., a portable device zone). Upon being replaced onto the given device base, the playback device may be assigned the original zone property that the device acquired from the device base.
In one example, two playback devices are placed on a first device base and a second device base, respectively. These devices acquire respective first zone properties from these bases that configure the playback devices as channels of a stereo pair in a “Living Room” zone. Later, the playback devices might be removed from their respective bases and as a result, lose the “Living Room” zone configuration and be assigned second zone properties that cause the playback devices to join a different zone (e.g., a “Portable” zone). After use as portable speakers, the playback devices are returned to the bases and acquire again the zone properties that configure the playback devices as respective channels of the stereo pair in the “Living Room” zone.
As noted above, some example playback device may be used as portable speakers when removed from a device base. To facilitate such use, such playback devices may include a power storage system, which may include one or more batteries. Some devices bases may operate as charging bases such that a playback device charges its battery(s) from current delivered by the charging base while the playback device is placed on the charging base.
In some cases, a playback device may modify the zone property of a device base. For example, a device base may be moved from a den to a kitchen. In this situation, a control device may send a command indicating this change to a playback device that is placed on the device base. In this situation, the playback device placed upon the device base in the Kitchen zone may assign to the device base a zone property that is associated with a “Kitchen” zone. Thereafter, playback devices placed on that device base may acquire the zone property of the “Kitchen” zone and responsively join the Kitchen zone.
As indicated above, example techniques may involve a playback device acquiring a zone property from a device base. In one aspect, a method is provided. The method may involve identifying a particular base onto which the playback device is placed. The method may further involve determining that the particular base is assigned a zone property that is associated with a first zone of a media playback system. The method may also involve assigning, to the playback device, the zone property that is assigned to the particular base. Assigning the zone property to the playback device may involve joining the playback device into the first zone of the media playback system.
In another aspect, a device is provided. The device includes one or more processors; and a data storage having stored therein instructions executable by the one or more processors to cause the playback device to perform operations. The operations may include identifying a particular base onto which the playback device is placed. The operations may further include determining that the particular base is assigned a zone property that is associated with a first zone of a media playback system. The operations may also include assigning, to the playback device, the zone property that is assigned to the particular base. Assigning the zone property to the playback device may involve joining the playback device into the first zone of the media playback system.
In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include identifying a particular base onto which the playback device is placed. The operations may further include determining that the particular base is assigned a zone property that is associated with a first zone of a media playback system. The operations may also include assigning, to the playback device, the zone property that is assigned to the particular base. Assigning the zone property to the playback device may involve joining the playback device into the first zone of the media playback system.
As also indicated above, example techniques may involve a playback device assigning a zone property to a device base. In one aspect, a method is provided. The method may involve receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may involve joining the playback device into a first zone of a media playback system. The method may further involve identifying a base onto which the playback device is placed. The method may also involve determining that a zone property is not assigned to the identified base, and, upon determining that a zone property is not assigned to the identified base, assigning the first zone property to the identified base.
In another aspect, a device is provided. The device includes one or more processors; and a data storage having stored therein instructions executable by the one or more processors to cause the playback device to perform operations. The operations may include receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may involve joining the playback device into a first zone of a media playback system. The operations may further include identifying a base onto which the playback device is placed. The operations may also include determining that a zone property is not assigned to the identified base, and, upon determining that a zone property is not assigned to the identified base, assigning the first zone property to the identified base.
In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may involve joining the playback device into a first zone of a media playback system. The operations may further include identifying a base onto which the playback device is placed. The operations may also include determining that a zone property is not assigned to the identified base, and, upon determining that a zone property is not assigned to the identified base, assigning the first zone property to the identified base.
As further indicated above, example techniques may involve a playback device modifying a zone property of a device base. In one aspect, a method is provided. The method may involve receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may involve joining the playback device into a first zone of a media playback system. The method may further involve identifying a base onto which the playback device is placed. The method may involve receiving an instruction that assigns a second zone property to the playback device. Assigning the second zone property to the playback device may involve withdrawing the playback device from the first zone and joining the playback device into a second zone of the media playback system. The method may also include assigning the second zone property to the identified base onto which the playback device is placed.
In another aspect, a device is provided. The device includes one or more processors; and a data storage having stored therein instructions executable by the one or more processors to cause the playback device to perform operations. The operations may include receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may include joining the playback device into a first zone of a media playback system. The operations may further include identifying a base onto which the playback device is placed. The operations may include receiving an instruction that assigns a second zone property to the playback device. Assigning the second zone property to the playback device may include withdrawing the playback device from the first zone and joining the playback device into a second zone of the media playback system. The operations may also include assigning the second zone property to the identified base onto which the playback device is placed.
In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may include joining the playback device into a first zone of a media playback system. The operations may further include identifying a base onto which the playback device is placed. The operations may include receiving an instruction that assigns a second zone property to the playback device. Assigning the second zone property to the playback device may include withdrawing the playback device from the first zone and joining the playback device into a second zone of the media playback system. The operations may also include assigning the second zone property to the identified base onto which the playback device is placed.
It will be understood by one of ordinary skill in the art that this disclosure includes numerous other embodiments. It will be understood by one of ordinary skill in the art that this disclosure includes numerous other embodiments. While some examples described herein may refer to functions performed by given actors such as “users” and/or other entities, it should be understood that this description is for purposes of explanation only. The claims should not be interpreted to require action by any such example actor unless explicitly required by the language of the claims themselves.
Further discussions relating to the different components of the example media playback system 100A and how the different components may interact to provide a user with a media experience may be found in the following sections. While discussions herein may generally refer to the example media playback system 100A, technologies described herein are not limited to applications within, among other things, the home environment as shown in
a. Example Playback Devices
In one case, the playback device 200 may not include the speaker(s) 212, but rather a speaker interface for connecting the playback device 200 to external speakers. In another case, the playback device 200 may include neither the speaker(s) 212 nor the audio amplifier(s) 210, but rather an audio interface for connecting the playback device 200 to an external audio amplifier or audio-visual receiver.
In one example, the processor 202 may be a clock-driven computing component configured to process input data according to instructions stored in the memory 206. The memory 206 may be a tangible computer-readable medium configured to store instructions executable by the processor 202. For instance, the memory 206 may be data storage that can be loaded with one or more of the software components 204 executable by the processor 202 to achieve certain functions. In one example, the functions may involve the playback device 200 retrieving audio data from an audio source or another playback device. In another example, the functions may involve the playback device 200 sending audio data to another device or playback device on a network. In yet another example, the functions may involve pairing of the playback device 200 with one or more playback devices to create a multi-channel audio environment.
Certain functions may involve the playback device 200 synchronizing playback of audio content with one or more other playback devices. During synchronous playback, a listener will preferably not be able to perceive time-delay differences between playback of the audio content by the playback device 200 and the one or more other playback devices. U.S. Pat. No. 8,234,395 entitled, “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is hereby incorporated by reference, provides in more detail some examples for audio playback synchronization among playback devices.
The memory 206 may further be configured to store data associated with the playback device 200, such as one or more zones and/or zone groups the playback device 200 is a part of, audio sources accessible by the playback device 200, or a playback queue that the playback device 200 (or some other playback device) may be associated with. The data may be stored as one or more state variables that are periodically updated and used to describe the state of the playback device 200. The memory 206 may also include the data associated with the state of the other devices of the media system, and shared from time to time among the devices so that one or more of the devices have the most recent data associated with the system. Other embodiments are also possible.
The audio processing components 208 may include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor (DSP), and so on. In one embodiment, one or more of the audio processing components 208 may be a subcomponent of the processor 202. In one example, audio content may be processed and/or intentionally altered by the audio processing components 208 to produce audio signals. The produced audio signals may then be provided to the audio amplifier(s) 210 for amplification and playback through speaker(s) 212. Particularly, the audio amplifier(s) 210 may include devices configured to amplify audio signals to a level for driving one or more of the speakers 212. The speaker(s) 212 may include an individual transducer (e.g., a “driver”) or a complete speaker system involving an enclosure with one or more drivers. A particular driver of the speaker(s) 212 may include, for example, a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and/or a tweeter (e.g., for high frequencies). In some cases, each transducer in the one or more speakers 212 may be driven by an individual corresponding audio amplifier of the audio amplifier(s) 210. In addition to producing analog signals for playback by the playback device 200, the audio processing components 208 may be configured to process audio content to be sent to one or more other playback devices for playback.
Audio content to be processed and/or played back by the playback device 200 may be received from an external source, such as via an audio line-in input connection (e.g., an auto-detecting 3.5 mm audio line-in connection) or the network interface 214.
The network interface 214 may be configured to facilitate a data flow between the playback device 200 and one or more other devices on a data network. As such, the playback device 200 may be configured to receive audio content over the data network from one or more other playback devices in communication with the playback device 200, network devices within a local area network, or audio content sources over a wide area network such as the Internet. In one example, the audio content and other signals transmitted and received by the playback device 200 may be transmitted in the form of digital packet data containing an Internet Protocol (IP)-based source address and IP-based destination addresses. In such a case, the network interface 214 may be configured to parse the digital packet data such that the data destined for the playback device 200 is properly received and processed by the playback device 200.
As shown, the network interface 214 may include wireless interface(s) 216 and wired interface(s) 218. The wireless interface(s) 216 may provide network interface functions for the playback device 200 to wirelessly communicate with other devices (e.g., other playback device(s), speaker(s), receiver(s), network device(s), control device(s) within a data network the playback device 200 is associated with) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The wired interface(s) 218 may provide network interface functions for the playback device 200 to communicate over a wired connection with other devices in accordance with a communication protocol (e.g., IEEE 802.3). While the network interface 214 shown in
The power supply 220 may supply current to the various other components of the playback device 200. The power supply 220 may include an AC/DC converter 222, which may convert supplied alternating current to direct current used by the component of playback device 220. In some cases, playback 220 may include one or more batteries 224, which may store charge that the playback device 200 draws during portable operation.
In one example, the playback device 200 and one other playback device may be paired to play two separate audio components of audio content. For instance, playback device 200 may be configured to play a left channel audio component, while the other playback device may be configured to play a right channel audio component, thereby producing or enhancing a stereo effect of the audio content. The paired playback devices (also referred to as “bonded playback devices”) may further play audio content in synchrony with other playback devices.
In another example, the playback device 200 may be sonically consolidated with one or more other playback devices to form a single, consolidated playback device. A consolidated playback device may be configured to process and reproduce sound differently than an unconsolidated playback device or playback devices that are paired, because a consolidated playback device may have additional speaker drivers through which audio content may be rendered. For instance, if the playback device 200 is a playback device designed to render low frequency range audio content (i.e. a subwoofer), the playback device 200 may be consolidated with a playback device designed to render full frequency range audio content. In such a case, the full frequency range playback device, when consolidated with the low frequency playback device 200, may be configured to render only the mid and high frequency components of audio content, while the low frequency range playback device 200 renders the low frequency component of the audio content. The consolidated playback device may further be paired with a single playback device or yet another consolidated playback device.
By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including a “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/or future playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, it is understood that a playback device is not limited to the example illustrated in
b. Example Playback Zone Configurations
Referring back to the media playback system 100A of
As shown in
In one example, one or more playback zones in the environment of
As suggested above, the zone configurations of the media playback system 100A may be dynamically modified, and in some embodiments, the media playback system 100A supports numerous configurations. For instance, if a user physically moves one or more playback devices to or from a zone, the media playback system 100A may be reconfigured to accommodate the change(s). For instance, if the user physically moves the playback device 102 from the balcony zone to the office zone, the office zone may now include both the playback device 118 and the playback device 102. The playback device 102 may be paired or grouped with the office zone and/or renamed if so desired via a control device such as the control devices 126 and 128. On the other hand, if the one or more playback devices are moved to a particular area in the home environment that is not already configured with a playback zone, a new playback zone may be created for the particular area.
Further, different playback zones of the media playback system 100A may be dynamically combined into zone groups or split up into individual playback zones. For instance, the Dining Room zone and the Kitchen zone 114 may be combined into a zone group for a dinner party such that playback devices 112 and 114 may render audio content in synchrony. On the other hand, the living room zone may be split into a television zone including playback device 104, and a listening zone including playback devices 106, 108, and 110, if the user wishes to listen to music in the living room space while another user wishes to watch television.
c. Example Control Devices
The processor 302 may be configured to perform functions relevant to facilitating user access, control, and configuration of the media playback system 100A. The memory 304 may be configured to store instructions executable by the processor 302 to perform those functions. The memory 304 may also be configured to store the media playback system controller application software and other data associated with the media playback system 100A and the user.
In one example, the network interface 306 may be based on an industry standard (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The network interface 306 may provide a means for the control device 300 to communicate with other devices in the media playback system 100A. In one example, data and information (e.g., such as a state variable) may be communicated between control device 300 and other devices via the network interface 306. For instance, playback zone and zone group configurations in the media playback system 100A may be received by the control device 300 from a playback device or another network device, or transmitted by the control device 300 to another playback device or network device via the network interface 306. In some cases, the other network device may be another control device.
Playback device control commands such as volume control and audio playback control may also be communicated from the control device 300 to a playback device via the network interface 306. As suggested above, changes to configurations of the media playback system 100A may also be performed by a user using the control device 300. The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, separating one or more playback devices from a bonded or consolidated player, among others. Accordingly, the control device 300 may sometimes be referred to as a controller, whether the control device 300 is a dedicated controller or a network device on which media playback system controller application software is installed.
The user interface 308 of the control device 300 may be configured to facilitate user access and control of the media playback system 100A, by providing a controller interface such as the controller interface 400 shown in
The playback control region 410 may include selectable (e.g., by way of touch or by using a cursor) icons to cause playback devices in a selected playback zone or zone group to play or pause, fast forward, rewind, skip to next, skip to previous, enter/exit shuffle mode, enter/exit repeat mode, enter/exit cross fade mode. The playback control region 410 may also include selectable icons to modify equalization settings, and playback volume, among other possibilities.
The playback zone region 420 may include representations of playback zones within the media playback system 100A. In some embodiments, the graphical representations of playback zones may be selectable to bring up additional selectable icons to manage or configure the playback zones in the media playback system, such as a creation of bonded zones, creation of zone groups, separation of zone groups, and renaming of zone groups, among other possibilities.
For example, as shown, a “group” icon may be provided within each of the graphical representations of playback zones. The “group” icon provided within a graphical representation of a particular zone may be selectable to bring up options to select one or more other zones in the media playback system to be grouped with the particular zone. Once grouped, playback devices in the zones that have been grouped with the particular zone will be configured to play audio content in synchrony with the playback device(s) in the particular zone. Analogously, a “group” icon may be provided within a graphical representation of a zone group. In this case, the “group” icon may be selectable to bring up options to deselect one or more zones in the zone group to be removed from the zone group. Other interactions and implementations for grouping and ungrouping zones via a user interface such as the user interface 400 are also possible. The representations of playback zones in the playback zone region 420 may be dynamically updated as playback zone or zone group configurations are modified.
The playback status region 430 may include graphical representations of audio content that is presently being played, previously played, or scheduled to play next in the selected playback zone or zone group. The selected playback zone or zone group may be visually distinguished on the user interface, such as within the playback zone region 420 and/or the playback status region 430. The graphical representations may include track title, artist name, album name, album year, track length, and other relevant information that may be useful for the user to know when controlling the media playback system via the user interface 400.
The playback queue region 440 may include graphical representations of audio content in a playback queue associated with the selected playback zone or zone group. In some embodiments, each playback zone or zone group may be associated with a playback queue containing information corresponding to zero or more audio items for playback by the playback zone or zone group. For instance, each audio item in the playback queue may comprise a uniform resource identifier (URI), a uniform resource locator (URL) or some other identifier that may be used by a playback device in the playback zone or zone group to find and/or retrieve the audio item from a local audio content source or a networked audio content source, possibly for playback by the playback device.
In one example, a playlist may be added to a playback queue, in which case information corresponding to each audio item in the playlist may be added to the playback queue. In another example, audio items in a playback queue may be saved as a playlist. In a further example, a playback queue may be empty, or populated but “not in use” when the playback zone or zone group is playing continuously streaming audio content, such as Internet radio that may continue to play until otherwise stopped, rather than discrete audio items that have playback durations. In an alternative embodiment, a playback queue can include Internet radio and/or other streaming audio content items and be “in use” when the playback zone or zone group is playing those items. Other examples are also possible.
When playback zones or zone groups are “grouped” or “ungrouped,” playback queues associated with the affected playback zones or zone groups may be cleared or re-associated. For example, if a first playback zone including a first playback queue is grouped with a second playback zone including a second playback queue, the established zone group may have an associated playback queue that is initially empty, that contains audio items from the first playback queue (such as if the second playback zone was added to the first playback zone), that contains audio items from the second playback queue (such as if the first playback zone was added to the second playback zone), or a combination of audio items from both the first and second playback queues. Subsequently, if the established zone group is ungrouped, the resulting first playback zone may be re-associated with the previous first playback queue, or be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Similarly, the resulting second playback zone may be re-associated with the previous second playback queue, or be associated with a new playback queue that is empty, or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Other examples are also possible.
Referring back to the user interface 400 of
The audio content sources region 450 may include graphical representations of selectable audio content sources from which audio content may be retrieved and played by the selected playback zone or zone group. Discussions pertaining to audio content sources may be found in the following section.
d. Example Audio Content Sources
As indicated previously, one or more playback devices in a zone or zone group may be configured to retrieve for playback audio content (e.g., according to a corresponding URI or URL for the audio content) from a variety of available audio content sources. In one example, audio content may be retrieved by a playback device directly from a corresponding audio content source (e.g., a line-in connection). In another example, audio content may be provided to a playback device over a network via one or more other playback devices or network devices.
Example audio content sources may include a memory of one or more playback devices in a media playback system such as the media playback system 100A of
In some embodiments, audio content sources may be regularly added or removed from a media playback system such as the media playback system 100A of
e. Example Device Base
Some device bases may include device charging systems. For instance, device base 502 includes charging system 508. When a playback device, such as playback device 500, is placed on device base 502, the playback device may draw current from charging system 508 to charge one or more of its batteries. In some embodiments, charging system 508 may include an inductive charging circuit (e.g., a coil that induces a current in a corresponding coil in the playback device that wirelessly charges one or more batteries of the playback device). Alternatively, charging system 508 may include conductive terminals by which playback device 500 may draw current from the device base 502.
In some embodiments, a device base may carry an identifier that distinguishes that device base from at least some other device bases (e.g., other device bases of a given media playback system, or perhaps other devices bases more broadly). In some implementations, the device base may passively communicate this identifier to a playback device that is placed upon the device base. For instance, a charging circuit may include a current or voltage signature (i.e., a pattern) that is unique as compared to other device bases. A playback device may use this unique signature to identify the charging base. Alternatively, a charging circuit may superimpose a signal onto the current delivered from the device base (e.g., current from the device base may include a higher frequency signal carrying the identifier of the device base). In further examples, a device base may include an RFID tag, QR code, or other identifying component that is read by the playback device when the playback device is placed upon the device base.
In some implementations, a device base includes a control system. For example, device base 502 includes control system 510. Control system 510 includes one or more processors and a memory. The processor(s) may be clock-driven computing components that process input data according to instructions stored in the memory. The memory may be a tangible computer-readable medium configured to store instructions executable by the processor(s) to cause the device base to carry out operations. Example operations include communicating via a communications interface (e.g., a BLUETOOTH® interface) with playback device 500 and causing charging system 508 to supply current to playback device 500, among other examples.
Moving now to several example implementations, implementations 600, 1000, and 1100 shown in
In addition, for the implementations disclosed herein, the flowcharts show functionality and operation of one possible implementation of present embodiments. In this regard, each block may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by a processor for implementing specific logical functions or steps in the process. The program code may be stored on any type of computer readable medium, for example, such as a storage device including a disk or hard drive. The computer readable medium may include non-transitory computer readable medium, for example, such as computer-readable media that stores data for short periods of time like register memory, processor cache, and Random Access Memory (RAM). The computer readable medium may also include non-transitory media, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. The computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device. In addition, for the implementations disclosed herein, each block may represent circuitry that is wired to perform the specific logical functions in the process.
As discussed above, embodiments described herein may facilitate a playback device acquiring a zone property from a device base. By assigning a zone property to the playback device, a playback device may join a particular zone that is associated with the zone property and adopt certain characteristics of that zone.
a. Identify a Base onto which a Playback Device is Placed
At block 602, implementation 600 involves identifying a base onto which the playback device is placed. For instance, referring to
In some embodiments, a playback device may identify the device base by way of an identifier that uniquely identifies a particular base among devices of a media playback system (and possibly among all device bases from a particular manufacturer). Each device base may have such an identifier, which may be communicated to a playback device when that playback device is placed on the base. Within examples, the identifier may be stored in a data storage of the device base (e.g., a memory of control system 510 of device base 502), or the identifier may be coded into the device base (e.g., by way of a DIP switch or other logical circuitry). While several example techniques for identifying a device base are noted, other techniques for identifying a device base are contemplated as well, such as an RFID tag or QR code.
In some implementations, the identifier of the device base may be transmitted to the playback device using a radio interface (e.g., a near-field wireless communications interface such as NFC (near field communications) or BLUETOOTH® LE. For instance, while playback device 500 is placed on device base 502, control system 510 may cause a radio interface to periodically transmit the identifier of device base 502 to a corresponding radio interface of playback device 500. As noted above, a device base may use a near-field wireless communications interface, which may have a limited range such that the playback device is in range of the device base when the playback device is placed on or nearby the device base. Shielding the antenna of such a communications interface may further limit and orient its communications range, which may prevent communications between a playback device and a device base when the playback device is not on the device base.
Alternatively, the identifier of the device base may be communicated to the playback device via the charging circuit of the device base. For instance, a charging circuit may include a current or voltage signature (i.e., a pattern) that is unique as compared to other device bases. A playback device may use this unique signature to identify the charging base. Alternatively, a charging circuit may superimpose a communications signal onto the current delivered from the device base (e.g., current from the device base may include a higher frequency communications signal carrying the identifier).
b. Determine that the Base is Assigned a Zone Property that is Associated with a First Zone of a Media Playback System
Referring back to
In some embodiments, a correlation between a device base and a zone property that is assigned to that device base may be stored as a state variable. A media playback system may maintain or have access to state variables that correlate device bases to assigned zone properties. To determine whether a zone property is assigned to the identified base, a playback device may refer to such state variables. For example, a playback device may access state variables stored by a media playback system to identify which zone property is assigned to a particular device base (and ultimately the zone (and/or role) of the particular device base). The media playback system may update its state variables to reflect changes to the zone or role of a device base. Similarly, correlations between playback devices and zone properties that are assigned to those playback devices may also be stored as a state variable (or multiple state variables).
Other devices (e.g., playback devices 106, 108, 112, and 114) might not be assigned a zone property. In some embodiments, playback devices that do not have a zone property may be considered to be in a group of their own (i.e., a portable device zone). Within examples, a playback device that is in such a group may operate independently, or perhaps may operate jointly with other playback devices that are not assigned a zone property.
State variables indicating device bases of a media playback system and their respective assigned zone properties may be stored on various devices that are accessible to the media playback system. For instance, in some cases, the media playback system itself may store the state variables, perhaps in data storage of one or more playback device(s) or control device(s) of a media playback system, perhaps within a database. Alternatively, a remote server (e.g., a server that provides a cloud service) may store the state variables. Other examples are possible as well.
In some embodiments, the state variable(s) may be stored concurrently on multiple devices (e.g., on multiple devices within the media playback system), which may provide various advantages, such as redundancy and quicker access, among others. For instance, updates to the state variables stored on one playback device may be transmitted to other devices within the media playback system, so as to maintain an up-to-date instance of the state variables on multiple devices. In such cases, to determine whether a particular base is assigned a zone property that is associated with a given zone of a media playback system, a playback device may request (and receive) a state variable from one (or more) playback devices of the media playback system, perhaps by way of its network interface.
In some embodiments, determining whether a zone property is assigned to the identified base may involve querying a database for a zone property is assigned to an identifier received from the device base. For instance, playback device 500 may query a database for a zone property that is assigned to an identifier received from device base 502. In response, the playback device may receive an indication that a zone property is not assigned to the identifier received from device base 502 and responsively determine that a zone property is not assigned to device base 502. The database may include data (e.g., one or more state variables) that indicates one or more correlations between playback device and respective zone properties that are assigned to those playback devices. Within examples, the database may be stored on the playback device itself, or on another playback device of the media playback system itself. Alternatively, the database might be stored on a server that is accessible to the media playback system (e.g., a server that provides a cloud service).
c. Assign the Zone Property that is Assigned to the Base to the Playback Device
In
As noted above, assigning the zone property of the base to the playback device may cause the playback device to join a zone of a media playback system. More generally, assigning a particular zone property to a playback device may cause the playback device to join the zone that is associated with the particular zone property. For instance, a given zone property may be associated with a Living Room zone such that acquiring the given zone property causes the playback device to join the Living Room zone.
As a member of a zone, a playback device may operate as a functional unit of that zone. For instance, the zone may have its own pre-existing queue, which the playback device may adopt as its own queue. The zone may also have a pre-existing configuration defining certain operating parameters, which the playback device may adopt. For instance, the zone may have a particular equalization, which the playback device adopts upon joining the zone.
In some cases, a zone may include multiple playback devices. A zone property may define a particular role in a zone such that a playback device that is assigned the zone property assumes the particular role within the zone. For example, a given zone property may define a role as a left channel of a stereo pair such that a playback device that is assigned the zone property may begin operating as the left channel of the stereo pair. As another example, another zone property might define a role as a surround channel of a surround sound configuration such that a playback device that inherits that zone property begins operation as the surround channel.
As a member of a zone, a playback device may operate as a functional unit with other playback devices of one or more additional zones that have been joined together into a zone that a group of zones, each including respective playback device. For instance, a Living Room zone and a Den zone may be joined together into a “Living Room+Den” zone group. As a zone group, the playback devices of both zones may play media in synchrony with one another. These playback devices may share the same queue and may also adopt the same configuration.
As noted above, some playback devices may implement a queue, such that they are configured to playback media items from the queue. Further, a zone of a media playback system may be associated with a queue such the playback device of the zone plays back media items from that queue of the zone. In such embodiments, by acquiring a zone property (and joining the zone that is associated with the zone property), the playback device may adopt the pre-existing queue of the zone that is associated with the zone property. Adopting the queue may involve populating the queue of the playback device with the media items that are queued in the queue of the zone, perhaps by receiving an indication of the zone's queue from another playback device of the zone. In some instances, the playback device may remove any media items that were previously queued in its queue as part of adopting the queue of the zone, such that the playback device has a queue that matches the queue of the zone.
As noted above, in joining the zone that is associated with the zone property by acquiring the zone property, a playback device may begin to perform operations jointly with other playback devices of the zone. For instance, the playback device may play back a queue (e.g., an adopted queue) of media items in synchrony with one or more additional playback devices of the zone. Further, a playback device may perform operations jointly with playback devices of other zones that have been grouped into a zone group with the zone of the playback device. As a member of a zone or zone group, commands directed to the zone or zone group may be carried out by the playback device. For instance, commands to initiate or pause playback by the zone or zone group may be carried out by the playback device. Likewise, changes to the queue of the zone or zone group may be propagated to the playback device (e.g., if a media item is queued in the zone's queue, the playback device may playback that media item when playback of the queue reaches that media item).
Referring back to
Upon being removed from a device base, a playback device may lose the zone property that is assigned to the device base. For instance, referring to
In some cases, a playback device may acquire a zone property that is associated with a zone that does not currently include any other playback devices. In a sense, by assigning that particular zone property to the playback device, the playback device can be considered to have formed the zone that is associated with that particular zone property. By extension, when that playback device loses that zone property, the playback device may leave the zone, causing the zone to have no playback devices (given that no other playback devices had joined the zone since the playback device had joined that zone). However, the device base may retain the zone property, such that when a playback device is placed again on the device base, the zone may be formed again by that playback device when the playback device is assigned the zone property.
Referring back to
At some time thereafter, playback device 114 may be brought back in from the patio and placed back onto device base 136. Upon being placed on device base 136, playback device 114 re-joins the Kitchen zone. As a member of the Kitchen zone, playback device 114 adopts the queue of the Kitchen zone, and may also adopt a role within the Kitchen zone, as defined by the zone property assigned to device base 136. In some embodiments, upon playback device 114 re-joining the Kitchen zone, the Kitchen zone and the Dining Room zone may re-form the zone group in which playback device 112 (of the Dining Room zone) and playback device 114 (of the Kitchen zone) operate jointly that existed before playback device 114 was removed from the zone.
In another example, at some point, playback devices 122 and 124 are removed from device bases 140 and 142, perhaps to be taken out to a deck for a barbeque. As noted above in connection with other examples, upon removal from their respective device bases, playback devices 122 and 124 disinherit the zone properties that are assigned to those bases and become portable speakers.
After use as portable speakers (e.g., after the barbeque), playback devices 122 and 124 are placed back upon device bases to recharge. However, as shown in
In some embodiments, assigning a zone property to a playback device may change the name of that playback device (perhaps by causing the playback device to join a zone having a different name). As noted above, in some implementations, zones of a media playback system may be assigned respective names. Such names may correspond to a different room or space such as an office, bathroom, master bedroom, bedroom, kitchen, dining room, living room, and/or balcony, which may help to identify a particular zone. A control device may display such a name in association with controls corresponding to that zone. For example, in playback zone region 420 of
By placing a playback device onto a device base and causing the playback device to be assigned a zone property associated with a particular zone, the name of the playback device may be changed to the name of that particular zone. For example, a given device base may be associated with a Living Room zone. Upon being placed on that device base, a playback device may join the Living Room zone, which may cause the name of the playback device to be changed to “Living Room.” When the playback device is removed from that device base, the playback device may change its name again (e.g., to “Portable”). Such name changes may indicate that the playback device is a member of a particular zone, or that the playback device is operating as a portable device, among other examples.
As noted above, in some embodiments, while removed from a device base, a playback device may operate as a portable (e.g., battery powered) device, perhaps as part of a “Portable” zone. Upon being removed from a device base (and beginning to operate as a portable device), the playback device may adopt certain settings consistent with portable operations. For instance, upon being removed from a device base, the playback device may adjust its equalization to be relatively more bass focused, which may increase sound propagation in environments where the playback device is more likely to be used as a portable device (e.g., outdoors). As another example, the playback device may limit its maximum volume to a sound intensity level that is lower than the playback device is capable of emitting, which may prolong battery life of the playback device. Such a portable volume limit may be lower than a volume limit set when the playback device is placed on a device base, as operating time of the playback device might not be limited by battery capacity while on a device base. Other example settings that are consistent with portable operation might be automatically changed as well.
Example playback devices described herein may undergo a calibration procedure, which may adjust operation of a playback device for a particular location within a given environment. Some calibration procedures contemplated herein involve a control device of a media playback system detecting and analyzing sound waves (e.g., one or more calibration sounds) which were emitted by one or more playback devices of the media playback system. In some cases, such calibration sounds may facilitate the control device determining respective frequency responses of the one or more playback devices within a given environment. After determining such a response for a given playback device, the control device may instruct the given playback device to adopt a certain calibration profile (e.g., an equalization) that offsets the acoustics of the given environment. Acoustics may vary from location to location within an environment, so such a calibration procedure may tune the playback device for the particular location in the environment that the playback device was located during calibration.
In some embodiments, a calibration procedure may be performed while a given playback device is placed on a device base. This calibration may tune the playback device for the particular location in the environment at which the device base is located. Accordingly, the calibration profile determined by the calibration procedure may be attributed to the device base, as the device base may remain relatively stationary within the environment (as compared with a portable playback device). Then, when a playback device is placed upon the device base, the playback device may adopt a certain calibration profile that offsets the acoustics of the given environment at the location of the device base.
When a playback device is removed from the device base, the playback device may lose the calibration profile associated with the device base, as that calibration profile may be inapplicable for locations other than that of the device base. Further, the playback device may revert to default settings (e.g., a profile associated with portable device operation). Such a profile may include an equalization associated with operation as a portable device.
While in some cases, a playback device may be assigned a zone property upon being placed on a device base, the playback device might not immediately adopt the operating parameters or settings of the zone that is associated with the assigned zone property. Instead, the playback device may time adoption of such parameters in accordance with operations being performed by the playback device and/or the zone that the playback device is joining. For instance, the playback device might be in the process of playing a particular media item when the playback device is placed upon a device base. In such an example, the playback device might time joining the zone (or adopting operating parameters of the zone) with when the particular media item finishes playing. As another example, a given zone may include one or more other playback devices that are playing a media item, and the playback device that is joining that zone may wait to join the zone until the particular media item finishes playing.
In further examples, operating parameters or settings of the zone may be gradually applied to the device over a period of a few seconds to a minute or so. For example, upon being placed on a device base, a playback device may gradually shift from a default or portable profile (e.g. equalization) to a calibration profile associated with the device base. Such a gradual shift may prevent possibly unpleasant artifacts caused by the changing in operating parameters or settings, among other possible benefits.
Similarly, upon being removed from a device base, a playback device might not immediately adopt operating parameters or settings consistent with portable operation. Instead, the playback device may wait until the playback device stop moving (as indicated by a sensor, such as an accelerometer) to adjust operating parameters or settings. For instance, in some cases, the playback device may be removed from a first device base only to stop moving when the playback device is placed on a second device base. In such an example, the playback device might not adjust its operating parameters to be consistent with portable operation during the transition period between successive device bases. In other cases, the playback device may be removed from a device base and be placed down without being set on a device base. The playback device might then adopt settings that are consistent with portable operation.
As discussed above, embodiments described herein may facilitate a playback device assigning a zone property to a device base. A playback device may assign a zone property to a device base in various circumstances. For instance, a new (i.e., not yet configured) device base might not be assigned a zone property. Alternatively, a reset procedure (e.g., a “factory reset”) might clear zone properties that have been assigned to the device base.
a. Receive Instruction that Assigns a First Zone Property to a Playback Device
At block 1002, implementation 1000 involves receiving an instruction that assigns a first zone property to a playback device. For instance, a control device, such as control device 300 of
Assigning the first zone property to the playback device may involve joining the playback device into a first zone of a media playback system. As indicated above, assigning a particular zone property to a playback device may cause the playback device to join the zone that is associated with the particular zone property. For instance, a given zone property may be associated with an Office zone such that assigning the given zone property to a playback device causes the playback device to join the Office zone. Further, a zone property may define a particular role in a zone such that a playback device that is assigned the zone property assumes the particular role within the zone. For example, a given zone property may define a role as a surround channel of a surround sound configuration such that a playback device that is assigned the zone property may begin operating as a surround channel of the surround sound configuration.
As noted above, a correlation between a playback device and a zone property that is assigned to that playback device may be stored as a state variable. The media playback system may refer to the state variable to identify which zone property is assigned to a particular playback device (and ultimately the zone (and/or role) of the particular playback device). The state variable may be updated to reflect changes to the zone or role of a playback device.
Like other state variables, state variables indicating devices of a media playback system and their respective assigned zone properties may be stored in data storage of playback device(s) or control device(s) of a media playback system, perhaps within a database. In some embodiments, the state variable(s) may be stored concurrently on multiple devices within the media playback system, which may provide various advantages, such as redundancy and quicker access, among others. Updates to the state variables stored on one playback device may be transmitted to other devices within the media playback system, so as to maintain an up-to-date instance of the state variables on multiple devices. Also, as noted above, in some embodiments, the state variables may be stored on a remote server, perhaps in addition to one or more devices of the media playback system.
Within examples, the control device may send such an instruction based on detecting input indicating a request to assign the first zone property to a particular zone. For instance, a control device may cause a graphical interface to display a control interface (e.g., control interface 400 of
Referring back to
b. Identify a Base onto which the Playback Device is Placed
Referring back to
In
In some embodiments, a playback device may identify the device base by way of an identifier that uniquely identifies a particular base among devices of a media playback system (and possibly among all device bases from a particular manufacturer). Each device base may have such an identifier, which may be communicated to a playback device when that playback device is placed on the base. Within examples, the identifier may be stored in a data storage of the device base (e.g., a memory of control system 510 of device base 502), or the identifier may be coded into the device base (e.g., by way of a DIP switch or other logical circuitry).
In some implementations, the identifier of the device base may be transmitted to the playback device using a radio interface (e.g., a near-field wireless communications interface such as NFC (near field communications) or BLUETOOTH® LE. For instance, while playback device 500 is placed on device base 502, control system 510 may cause a radio interface to periodically transmit the identifier of device base 502 to a corresponding radio interface of playback device 500. As noted above, a device base may use a near-field wireless communications interface, which may have a limited range such that the playback device is in range of the device base when the playback device is placed on or nearby the device base. Shielding the antenna of such a communications interface may further limit and orient its communications range, which may prevent communications between a playback device and a device base when the playback device is not on the device base.
Alternatively, the identifier of the device base may be communicated to the playback device via the charging circuit of the device base. For instance, a charging circuit may include a current or voltage signature (i.e., a pattern) that is unique as compared to other device bases. A playback device may use this unique signature to identify the charging base. Alternatively, a charging circuit may superimpose a communications signal onto the current delivered from the device base (e.g., current from the device base may include a high frequency communications signal).
c. Determine that a Zone Property is not Assigned to the Identified Base
In
To determine whether a zone property is assigned to the identified base, a playback device may refer to a state variable. A media playback system may maintain one or more state variables that indicate one or more correlations between device bases and respective zone properties that are assigned to those playback devices. The lack of a correlation between a given device base and a zone property may indicate that a zone property is not assigned to the given device base, as such a correlation may be stored in the state variable upon a zone property being assigned to a device base.
In some embodiments, determining whether a zone property is assigned to the identified base may involve querying a database for a zone property is assigned to an identifier received from the device base. For instance, playback device 500 may query a database for a zone property that is assigned to an identifier received from device base 502. In response, the playback device may receive an indication that a zone property is not assigned to the identifier received from device base 502 and responsively determine that a zone property is not assigned to device base 502. The database may include data (e.g., one or more state variables) that indicates one or more correlations between playback device and respective zone properties that are assigned to those playback devices. Within examples, the database may be stored on the playback device itself, or on another playback device of the media playback system itself. Alternatively, the database might be stored on a server that is accessible to the media playback system (e.g., a server that provides a cloud service).
d. Assign the First Zone Property to the Identified Base
Referring again to
The playback device may perform different operations depending on whether (or not) a zone property has been assigned to the device base. As noted above, if a playback device determines that a zone property is not assigned to the device base, the playback device may assign its zone property to the device base. Conversely, if a playback device determines that a zone property is assigned to the device base, the playback device may acquire the zone property of the device base.
In some embodiments, assigning a zone property to the identified base comprises updating a state variable so as to assign a zone property to the device base. For instance, the playback device may update a state variable that is stored in data storage of the playback device. In some cases, the playback device may send an indication of the update to the state variable to one or more additional playback devices of the media playback system or to a server, so as to maintain an up-to-date instance of the state variable(s) on multiple devices.
As noted above, in some cases, an identifier may uniquely identify a given base among one or more bases of the media playback system. In such cases, to assign a zone property to given base, the playback device may update a database of the playback device to associate the zone property with the identifier.
As discussed above, embodiments described herein may facilitate a playback device assigning a zone property to a device base. In some cases, a playback device may modify the zone property of a device base. For instance, a device base may be moved to another area of the house, which might suggest configuring the device base with a zone property that is associated with a different zone.
a. Receive Instruction that Assigns a First Zone Property to a Playback Device
At block 1102, implementation 1100 involves receiving an instruction that assigns a first zone property to a playback device. For instance, referring back to
b. Identify a Base onto which the Playback Device is Placed
At block 1104, implementation 1100 involves identifying a base onto which the playback device is placed. For instance, playback device 114 of media playback system 100C may identify device base 136, using, for example, any of the techniques to identify a device base that are noted above. Playback device 114 of media playback system 100C may determine whether a zone property is assigned to device base 136. In some cases, a zone property might not have been assigned to device base 136 and playback device 114 may proceed to assign a zone property to device base 136 as described above. In other cases, a zone property may have been assigned to device base 136, which may lead to playback device 114 acquiring a zone property from device base 136. However, in further cases, playback device 114 and device base 136 may already have the same zone property (i.e., the first zone property).
c. Receive Instruction that Assigns a Second Zone Property to a Playback Device
At block 1108, implementation 1100 involves receiving an instruction that assigns a second zone property to a playback device. The second zone property is different from the first zone property that was previously assigned to the playback device. For instance, control device 126 may send an instruction that assigns a new zone property to playback device 114. For example, playback device 114 of media playback system 100C may be moved into the dining room, and may be assigned a zone property that is associated with the Dining Room zone (rather than the Kitchen zone).
To illustrate,
d. Assign the Second Zone Property to the Identified Base
At block 1110, implementation 1100 involves assigning the second zone property to the identified base onto which the playback device is placed. For instance, playback device 114 may assign the zone property that is associated with the Dining Room zone to device base 136. Playback device 114 may use any of the example techniques to assign a zone property described above, among other possible examples.
At some point in time thereafter, playback device 114 may be removed from device base 136. Playback device 114 may detect removal from device base 136, and responsively assign itself a third zone property (e.g., a zone property that is associated with a Portable zone). As described above, acquiring such a zone property may cause playback device 114 to join the zone that is associated with that zone property.
Subsequently, playback device 114 may be replaced onto device base 136. Playback device 140 may detect this replacement and responsively lose the third zone property (e.g., the zone property that is associated with a Portable zone) and acquire the second zone property (e.g., the zone property that is associated with the Dining Room zone). By assigning this zone property to playback device 114, playback device 114 may re-join the Dining Room zone.
In one example, control device 126 (or perhaps another control device, such as control device 128) may send an instruction to re-assign device base 136 from the second zone property (e.g., the zone property that is associated with the Dining Room zone) to another zone property (e.g., the zone property that is associated with the Kitchen zone). Playback device 114 may receive such an instruction and responsively assign to device base 136 the indicated zone property. If the zone property assigned to device base 136 is different from the zone property assigned to playback device 114, playback device 114 may acquire this zone property from the device base.
In further examples, a control device, such as control device 126, may assign or modify a zone property of a device base, perhaps without a playback device being placed on the device base. The control device may make such changes by updating the state variable and/or database that indicates the zone property assigned to the device base. For instance, a control device may send an instruction via its network interface to a playback device or server that is storing state variable(s) of the media playback system. The instruction may request that a particular zone property be assigned to the device base, perhaps by associated the identifier of the device base with the particular zone property.
In some cases, the device base might not be assigned a zone property. When neither the playback device nor the device base has a zone property, the playback device may wait for a zone property to be assigned to either the playback device or to the device base, perhaps by a control device. After a zone property is assigned to a device base, the playback device may be assigned that zone property. Alternatively, after a zone property is assigned to the playback device, the playback device may assign that zone property to the device base.
The following examples set out further or alternative aspects of the disclosure. The device in any of the following examples may be a component of any of the devices described herein or any configuration of a device described herein.
The description above discloses, among other things, various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. It is understood that such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the firmware, hardware, and/or software aspects or components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, the examples provided are not the only way(s) to implement such systems, methods, apparatus, and/or articles of manufacture.
As indicated above, example techniques may involve a playback device acquiring a zone property from a device base. In one aspect, a method is provided. The method may involve identifying a particular base onto which the playback device is placed. The method may further involve determining that the particular base is assigned a zone property that is associated with a first zone of a media playback system. The method may also involve assigning, to the playback device, the zone property that is assigned to the particular base. Assigning the zone property to the playback device may involve joining the playback device into the first zone of the media playback system.
In another aspect, a device is provided. The device includes one or more processors; and a data storage having stored therein instructions executable by the one or more processors to cause the playback device to perform operations. The operations may include identifying a particular base onto which the playback device is placed. The operations may further include determining that the particular base is assigned a zone property that is associated with a first zone of a media playback system. The operations may also include assigning, to the playback device, the zone property that is assigned to the particular base. Assigning the zone property to the playback device may involve joining the playback device into the first zone of the media playback system.
In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include identifying a particular base onto which the playback device is placed. The operations may further include determining that the particular base is assigned a zone property that is associated with a first zone of a media playback system. The operations may also include assigning, to the playback device, the zone property that is assigned to the particular base. Assigning the zone property to the playback device may involve joining the playback device into the first zone of the media playback system.
As also indicated above, example techniques may involve a playback device assigning a zone property to a device base. In one aspect, a method is provided. The method may involve receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may involve joining the playback device into a first zone of a media playback system. The method may further involve identifying a base onto which the playback device is placed. The method may also involve determining that a zone property is not assigned to the identified base, and, upon determining that a zone property is not assigned to the identified base, assigning the first zone property to the identified base.
In another aspect, a device is provided. The device includes one or more processors; and a data storage having stored therein instructions executable by the one or more processors to cause the playback device to perform operations. The operations may include receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may involve joining the playback device into a first zone of a media playback system. The operations may further include identifying a base onto which the playback device is placed. The operations may also include determining that a zone property is not assigned to the identified base, and, upon determining that a zone property is not assigned to the identified base, assigning the first zone property to the identified base.
In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may involve joining the playback device into a first zone of a media playback system. The operations may further include identifying a base onto which the playback device is placed. The operations may also include determining that a zone property is not assigned to the identified base, and, upon determining that a zone property is not assigned to the identified base, assigning the first zone property to the identified base.
As further indicated above, example techniques may involve a playback device modifying a zone property of a device base. In one aspect, a method is provided. The method may involve receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may involve joining the playback device into a first zone of a media playback system. The method may further involve identifying a base onto which the playback device is placed. The method may also involve determining that the first zone property is assigned to the identified base. The method may involve receiving an instruction that assigns a second zone property to the playback device. Assigning the second zone property to the playback device may involve withdrawing the playback device from the first zone and joining the playback device into a second zone of the media playback system. The method may also include assigning the second zone property to the identified base onto which the playback device is placed.
In another aspect, a device is provided. The device includes one or more processors; and a data storage having stored therein instructions executable by the one or more processors to cause the playback device to perform operations. The operations may include receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may include joining the playback device into a first zone of a media playback system. The operations may further include identifying a base onto which the playback device is placed. The operations may also include determining that the first zone property is assigned to the identified base. The operations may include receiving an instruction that assigns a second zone property to the playback device. Assigning the second zone property to the playback device may include withdrawing the playback device from the first zone and joining the playback device into a second zone of the media playback system. The operations may also include assigning the second zone property to the identified base onto which the playback device is placed.
In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include receiving an instruction that assigns a first zone property to the playback device. Assigning the first zone property to the playback device may include joining the playback device into a first zone of a media playback system. The operations may further include identifying a base onto which the playback device is placed. The operations may also include determining that the first zone property is assigned to the identified base. The operations may include receiving an instruction that assigns a second zone property to the playback device. Assigning the second zone property to the playback device may include withdrawing the playback device from the first zone and joining the playback device into a second zone of the media playback system. The operations may also include assigning the second zone property to the identified base onto which the playback device is placed.
The specification 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 can 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. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.
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, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.
This application is a continuation of U.S. application Ser. No. 16/944,797, titled “Playback Device Base,” filed on Jul. 31, 2020, and currently pending; U.S. application Ser. No. 16/944,797 is a continuation of U.S. application Ser. No. 16/367,808, titled “Stereo Pairing With Device Base,” filed on Mar. 28, 2019, and issued as U.S. Pat. No. 10,735,878, on Aug. 4, 2020; U.S. application Ser. No. 16/367,808 is a continuation of U.S. application Ser. No. 16/180,952, titled “Properties Based on Device Base,” filed on Nov. 5, 2018, and issued as U.S. Pat. No. 10,264,376 on Apr. 16, 2019; U.S. application Ser. No. 16/180,952 is a continuation of U.S. application Ser. No. 15/688,137, titled “Base Properties in a Media Playback System,” filed on Aug. 28, 2017, and issued as U.S. Pat. No. 10,129,673 on Nov. 13, 2018; U.S. application Ser. No. 15/688,137 is a continuation of U.S. application Ser. No. 15/357,548, titled “Base Properties in a Media Playback System,” filed on Nov. 21, 2016, and issued as U.S. Pat. No. 9,749,761 on Aug. 29, 2017; and U.S. application Ser. No. 15/357,548 is a continuation of U.S. application Ser. No. 14/803,094, titled “Base Properties in a Media Playback System,” filed on Jul. 19, 2015, and issued as U.S. Pat. No. 9,544,701 on Jan. 10, 2017. The entire contents of U.S. application Ser. Nos. 16/944,797; 16/367,808; 16/180,952; 15/688,137; 15/357,548; and 14/803,094 are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4696037 | Fierens | Sep 1987 | A |
5440644 | Farinelli et al. | Aug 1995 | A |
5553147 | Pineau | Sep 1996 | A |
5761320 | Farinelli et al. | Jun 1998 | A |
5923902 | Inagaki | Jul 1999 | A |
6032202 | Lea et al. | Feb 2000 | A |
6256554 | DiLorenzo | Jul 2001 | B1 |
6404811 | Cvetko et al. | Jun 2002 | B1 |
6469633 | Wachter | Oct 2002 | B1 |
6522886 | Youngs et al. | Feb 2003 | B1 |
6611537 | Edens et al. | Aug 2003 | B1 |
6631410 | Kowalski et al. | Oct 2003 | B1 |
6757517 | Chang | Jun 2004 | B2 |
6778869 | Champion | Aug 2004 | B2 |
6809635 | Kaaresoja | Oct 2004 | B1 |
6882335 | Saarinen | Apr 2005 | B2 |
7130608 | Hollstrom et al. | Oct 2006 | B2 |
7130616 | Janik | Oct 2006 | B2 |
7143939 | Henzerling | Dec 2006 | B2 |
7236773 | Thomas | Jun 2007 | B2 |
7295548 | Blank et al. | Nov 2007 | B2 |
7311526 | Rohrbach et al. | Dec 2007 | B2 |
7483538 | McCarty et al. | Jan 2009 | B2 |
7494098 | Fulda | Feb 2009 | B1 |
7571014 | Lambourne et al. | Aug 2009 | B1 |
7630501 | Blank et al. | Dec 2009 | B2 |
7643894 | Braithwaite et al. | Jan 2010 | B2 |
7657910 | McAulay et al. | Feb 2010 | B1 |
7853341 | McCarty et al. | Dec 2010 | B2 |
7987294 | Bryce et al. | Jul 2011 | B2 |
8014423 | Thaler et al. | Sep 2011 | B2 |
8045952 | Qureshey et al. | Oct 2011 | B2 |
8090317 | Burge et al. | Jan 2012 | B2 |
8103009 | McCarty et al. | Jan 2012 | B2 |
8214447 | Deslippe et al. | Jul 2012 | B2 |
8234395 | Millington | Jul 2012 | B2 |
8326951 | Millington et al. | Dec 2012 | B1 |
8483853 | Lambourne | Jul 2013 | B1 |
8788080 | Kallai et al. | Jul 2014 | B1 |
8867776 | Schul | Oct 2014 | B2 |
8903526 | Beckhardt et al. | Dec 2014 | B2 |
8910265 | Lang et al. | Dec 2014 | B2 |
8995240 | Erven et al. | Mar 2015 | B1 |
9042556 | Kallai et al. | May 2015 | B2 |
9137564 | Reimann | Sep 2015 | B2 |
9213762 | Erven et al. | Dec 2015 | B1 |
9223862 | Beckhardt | Dec 2015 | B2 |
9226072 | Bender et al. | Dec 2015 | B2 |
9232277 | Vega-Zayas et al. | Jan 2016 | B2 |
9247492 | Millington et al. | Jan 2016 | B2 |
9285886 | Reilly et al. | Mar 2016 | B2 |
9286384 | Kuper et al. | Mar 2016 | B2 |
9300647 | Triplett | Mar 2016 | B2 |
9329831 | Fullerton et al. | May 2016 | B1 |
9330096 | Fullerton et al. | May 2016 | B1 |
9361371 | Coburn, IV et al. | Jun 2016 | B2 |
9374607 | Bates et al. | Jun 2016 | B2 |
9450446 | Baker et al. | Sep 2016 | B2 |
9460755 | Coburn, IV | Oct 2016 | B2 |
9501533 | Coburn, IV et al. | Nov 2016 | B2 |
9544701 | Rappoport | Jan 2017 | B1 |
9554201 | Williams et al. | Jan 2017 | B2 |
9560449 | Carlsson et al. | Jan 2017 | B2 |
9608475 | Karanikos et al. | Mar 2017 | B1 |
9665339 | Reimann et al. | May 2017 | B2 |
9671997 | Triplett | Jun 2017 | B2 |
9686282 | Pollock | Jun 2017 | B2 |
9715365 | Kusano et al. | Jul 2017 | B2 |
9735978 | Kumar et al. | Aug 2017 | B2 |
9820039 | Lang | Nov 2017 | B2 |
9826306 | Lang | Nov 2017 | B2 |
9952825 | Sheen | Apr 2018 | B2 |
9961463 | Wilberding et al. | May 2018 | B2 |
10001965 | Lang et al. | Jun 2018 | B1 |
10003881 | Cousins et al. | Jun 2018 | B2 |
10114605 | Gossain et al. | Oct 2018 | B2 |
10209947 | Morganstern et al. | Feb 2019 | B2 |
10275138 | Vega et al. | Apr 2019 | B2 |
10462505 | Coburn, IV et al. | Oct 2019 | B2 |
10483786 | Moussaoui et al. | Nov 2019 | B2 |
10587693 | Beckhardt | Mar 2020 | B2 |
10715973 | Kumar et al. | Jul 2020 | B2 |
11200024 | Lang et al. | Dec 2021 | B2 |
20010042107 | Palm | Nov 2001 | A1 |
20020022453 | Balog et al. | Feb 2002 | A1 |
20020026442 | Lipscomb et al. | Feb 2002 | A1 |
20020124097 | Isely et al. | Sep 2002 | A1 |
20020127812 | Matsunaga et al. | Sep 2002 | A1 |
20030157951 | Hasty, Jr. | Aug 2003 | A1 |
20040024478 | Hans et al. | Feb 2004 | A1 |
20050201549 | Dedieu et al. | Sep 2005 | A1 |
20050286546 | Bassoli et al. | Dec 2005 | A1 |
20070003067 | Gierl et al. | Jan 2007 | A1 |
20070021137 | Kokkonen et al. | Jan 2007 | A1 |
20070038999 | Millington | Feb 2007 | A1 |
20070142944 | Goldberg et al. | Jun 2007 | A1 |
20070265031 | Koizumi et al. | Nov 2007 | A1 |
20080144864 | Huon et al. | Jun 2008 | A1 |
20080146289 | Korneluk et al. | Jun 2008 | A1 |
20090164600 | Issa et al. | Jun 2009 | A1 |
20090168760 | Katis et al. | Jul 2009 | A1 |
20090171487 | Wilhelm | Jul 2009 | A1 |
20090217036 | Irwin et al. | Aug 2009 | A1 |
20090312849 | Cosgrove et al. | Dec 2009 | A1 |
20110002487 | Panther et al. | Jan 2011 | A1 |
20110289157 | Pirnazar | Nov 2011 | A1 |
20120051567 | Castor-Perry | Mar 2012 | A1 |
20120206319 | Lucero et al. | Aug 2012 | A1 |
20120317487 | Lieb et al. | Dec 2012 | A1 |
20130129122 | Johnson et al. | May 2013 | A1 |
20130216071 | Maher | Aug 2013 | A1 |
20130248678 | Kramer | Sep 2013 | A1 |
20130305152 | Griffiths et al. | Nov 2013 | A1 |
20130316686 | Subbaramoo et al. | Nov 2013 | A1 |
20130331970 | Beckhardt et al. | Dec 2013 | A1 |
20140006587 | Kusano | Jan 2014 | A1 |
20140030980 | D'Ambrosio | Jan 2014 | A1 |
20140192986 | Lee et al. | Jul 2014 | A1 |
20140195587 | Sukoff et al. | Jul 2014 | A1 |
20140229959 | Beckhardt et al. | Aug 2014 | A1 |
20140230015 | Pollock | Aug 2014 | A1 |
20140270284 | Luna | Sep 2014 | A1 |
20140323036 | Daley et al. | Oct 2014 | A1 |
20150091691 | Calatayud | Apr 2015 | A1 |
20150092947 | Gossain et al. | Apr 2015 | A1 |
20150100991 | Risberg et al. | Apr 2015 | A1 |
20150135108 | Pope et al. | May 2015 | A1 |
20150163788 | Karunakaran | Jun 2015 | A1 |
20150212788 | Lang | Jul 2015 | A1 |
20150237424 | Wilker | Aug 2015 | A1 |
20150264509 | Oishi et al. | Sep 2015 | A1 |
20150312608 | Higa et al. | Oct 2015 | A1 |
20160011590 | Griffiths et al. | Jan 2016 | A1 |
20160011848 | Wilberding et al. | Jan 2016 | A1 |
20160011850 | Sheen et al. | Jan 2016 | A1 |
20160014512 | Wilberding et al. | Jan 2016 | A1 |
20160014535 | Wilberding et al. | Jan 2016 | A1 |
20160014536 | Sheen | Jan 2016 | A1 |
20160026428 | Morganstern et al. | Jan 2016 | A1 |
20160026429 | Triplett | Jan 2016 | A1 |
20160162252 | Di Censo et al. | Jun 2016 | A1 |
20160191584 | Dickow et al. | Jun 2016 | A1 |
20160212178 | Zhang et al. | Jul 2016 | A1 |
20170019742 | Rappoport | Jan 2017 | A1 |
20170034648 | Hutchings et al. | Feb 2017 | A1 |
20170090134 | Williams et al. | Mar 2017 | A1 |
20170117754 | Noori et al. | Apr 2017 | A1 |
20170134871 | Rappoport | May 2017 | A1 |
20170285788 | Park et al. | Oct 2017 | A1 |
20170366937 | Lee et al. | Dec 2017 | A1 |
20170373537 | Dayal et al. | Dec 2017 | A1 |
Number | Date | Country |
---|---|---|
1389853 | Feb 2004 | EP |
2180727 | Apr 2010 | EP |
3320698 | May 2018 | EP |
200153994 | Jul 2001 | WO |
2003093950 | Nov 2003 | WO |
Entry |
---|
Notice of Allowance mailed on Nov. 16, 2016, issued in connection with U.S. Appl. No. 14/803,094, filed Jul. 19, 2015, 7 pages. |
Notice of Allowance mailed on Jul. 19, 2017, issued in connection with U.S. Appl. No. 15/338,785, filed Oct. 31, 2016, 10 pages. |
Notice of Allowance mailed on Oct. 20, 2021, issued in connection with U.S. Appl. No. 17/228,114, filed Apr. 12, 2021, 12 pages. |
Notice of Allowance mailed on Jun. 21, 2017, issued in connection with U.S. Appl. No. 15/357,548, filed Nov. 21, 2016, 7 pages. |
Notice of Allowance mailed on Sep. 21, 2022, issued in connection with U.S. Appl. No. 16/944,797, filed Jul. 31, 2020, 9 pages. |
Notice of Allowance mailed on Mar. 23, 2020, issued in connection with U.S. Appl. No. 16/367,808, filed Mar. 28, 2019, 7 pages. |
Notice of Allowance mailed on Jan. 25, 2018, issued in connection with U.S. Appl. No. 15/078,300, filed Jan. 25, 2018, 5 pages. |
Notice of Allowance mailed on Aug. 27, 2018, issued in connection with U.S. Appl. No. 15/688,137, filed Aug. 28, 2017, 7 pages. |
Notice of Allowance mailed on Jan. 27, 2023, issued in connection with U.S. Appl. No. 17/548,878, filed Dec. 13, 2021, 7 pages. |
Notice of Allowance mailed on Jan. 28, 2016, issued in U.S. Appl. No. 14/631,713, filed Feb. 25, 2015,6 pages. |
Notice of Allowance mailed on Jan. 28, 2016, issued in U.S. Appl. No. 14/631,723, filed Feb. 25, 2015, 6 pages. |
Notice of Allowance mailed on Aug. 29, 2019, issued in connection with U.S. Appl. No. 16/011,273, filed Jun. 18, 2018, 11 pages. |
Notice of Allowance mailed on Dec. 31, 2018, issued in connection with U.S. Appl. No. 16/180,952, filed Nov. 5, 2018, 8 pages. |
Notice of Allowance mailed on Aug. 6, 2020, issued in connection with U.S. Appl. No. 15/078,006, filed Mar. 23, 2016, 7 pages. |
Notice of Allowance mailed on Dec. 7, 2020, issued in connection with U.S. Appl. No. 16/693,560, filed Nov. 25, 2019, 7 pages. |
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages. |
Preinterview First Office Action mailed on Sep. 23, 2016, issued in connection with U.S. Appl. No. 14/803,094, filed Jul. 19, 2015, 5 pages. |
Presentations at WinHEC 2000, May 2000, 138 pages. |
Roland Corporation, “Roland announces BA-55 Portable PA System,” press release, Apr. 6, 2011, 2 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. |
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 Jul. 13, 2017, issued in connection with U.S. Appl. No. 15/078,300, filed Mar. 23, 2016, 3 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. |
Dempsey, Paul. The Teardown Apple Watch. Apple makes every square inch of real estate in the Watch do a job. Engineering & Technology: Reviews Consumer Technology. Jul. 2015, 2 pages. |
“Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages. |
European Patent Office, European EPC Article 94.3 mailed on Mar. 7, 2022, issued in connection with European Application No. 20163524.0, 6 pages. |
European Patent Office, European Extended Search Report mailed on May 18, 2020, issued in connection with European Application No. 20163524.0, 9 pages. |
European Patent Office, European Office Action mailed on Jun. 4, 2019, issued in connection with European Application No. 16748400.5, 6 pages. |
European Patent Office, European Office Action mailed on Aug. 9, 2018, issued in connection with European Application No. 16748400.5, 4 pages. |
European Patent Office, European Search Report mailed on Nov. 11, 2022, issued in connection with European Application No. 21210296.6, 10 pages. |
European Patent Office, Office Action mailed on Jan. 18, 2018, issued in connection with European Patent Application No. 16711922.1, 6 pages. |
European Patent Office, Summons to Attend Oral Proceedings mailed on Nov. 7, 2018, issued in connection with European Application No. 16711922.1, 13 pages. |
Final Office Action mailed on May 1, 2017, issued in connection with U.S. Appl. No. 15/078,300, filed Mar. 23, 2016, 13 pages. |
First Action Interview Office Action mailed on Oct. 16, 2015, issued in U.S. Appl. No. 14/631,713, filed Feb. 25, 2015, 5 pages. |
First Action Interview Office Action mailed on Oct. 23, 2015, issued in U.S. Appl. No. 14/631,723, filed Feb. 25, 2015, 5 pages. |
Goldheart, Andrew. Apple Watch X-ray Teardown. IFIXIT, May 6, 2015, 19 pages. |
Horwitz, Jeremy, “Logic3 i-Station25,” retrieved from the internet: http://www.ilounge.com/index.php/reviews/entry/logic3-i-station25/, last visited Dec. 17, 2013, 5 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Jan. 23, 2018, issued in connection with International Application No. PCT/US2016/042822, filed on Jul. 18, 2016, 8 pages. |
International Bureau, International Preliminary Report on Patentability mailed on Jan. 30, 2014, issued in connection with International Application No. PCT/US2012/045894, filed on Jul. 9, 2012, 6 pages. |
International Bureau, International Search Report and Written Opinion mailed on Sep. 3, 2020, issued in connection with International Application No. PCT/US2020/036409, filed on Jun. 5, 2020, 20 pages. |
International Search Authority, International Search Report and Written Opinion mailed on Oct. 18, 2016, issued in connection with International Application No. PCT/US2016/042822, filed on Jul. 18, 2016, 13 pages. |
International Searching Authority, International Search Report and Written Opinion mailed on May 25, 2016, issued in connection with International Application No. PCT/US2016/019325, filed on Feb. 24, 2016, 11 pages. |
International Searching Authority, International Search Report mailed on Dec. 26, 2012, issued in connection with International Application No. PCT/US2012/045894, filed on Jul. 9, 2012, 3 pages. |
International Searching Authority, Written Opinion mailed on Dec. 26, 2012, issued in connection with International Application No. PCT/US2012/045894, filed on Jul. 9, 2012, 4 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 Feb. 1, 2016, issued in connection with U.S. Appl. No. 14/337,536, filed Jul. 22, 2014, 9 pages. |
Non-Final Office Action mailed on Jul. 7, 2022, issued in connection with U.S. Appl. No. 17/548,878, filed Dec. 13, 2021, 6 pages. |
Non-Final Office Action mailed on Mar. 10, 2017, issued in connection with U.S. Appl. No. 15/357,548, filed Nov. 21, 2016, 6 pages. |
Non-Final Office Action mailed on Feb. 14, 2017, issued in connection with U.S. Appl. No. 15/338,785, filed Oct. 31, 2016, 7 pages. |
Non-Final Office action mailed on Nov. 15, 2016, issued in connection with U.S. Appl. No. 15/078,300, filed Mar. 23, 2016, 8 pages. |
Non-Final Office Action mailed on Feb. 16, 2022, issued in connection with U.S. Appl. No. 17/114,010, filed Dec. 7, 2020, 8 pages. |
Non-Final Office Action mailed on May 16, 2018, issued in connection with U.S. Appl. No. 15/078,006, filed Mar. 23, 2016, 10 pages. |
Non-Final Office Action mailed on Apr. 2, 2018, issued in connection with U.S. Appl. No. 15/688,137, filed Aug. 28, 2017, 8 pages. |
Non-Final Office Action mailed on Aug. 22, 2017, issued in connection with U.S. Appl. No. 15/078,300, filed Mar. 23, 2016, 9 pages. |
Non-Final Office Action mailed on Apr. 27, 2023, issued in connection with U.S. Appl. No. 17/938,601, filed Oct. 6, 2022, 8 pages. |
Non-Final Office Action mailed on Jul. 29, 2020, issued in connection with U.S. Appl. No. 16/693,560, filed Nov. 25, 2019, 8 pages. |
Non-Final Office Action mailed on Sep. 29, 2017, issued in connection with U.S. Appl. No. 14/844,253, filed Sep. 3, 2015, 17 pages. |
Non-Final Office Action mailed on Feb. 4, 2019, issued in connection with U.S. Appl. No. 15/078,006, filed Mar. 23, 2016, 13 pages. |
Non-Final Office Action mailed on Feb. 4, 2020, issued in connection with U.S. Appl. No. 15/078,006, filed Mar. 23, 2016, 10 pages. |
Non-Final Office Action mailed on Aug. 6, 2019, issued in connection with U.S. Appl. No. 15/078,006, filed Mar. 23, 2016, 7 pages. |
Notice of Allowance mailed on Aug. 1, 2016, issued in connection with U.S. Appl. No. 14/337,536, filed Jul. 22, 2014, 9 pages. |
Notice of Allowance mailed on Jun. 8, 2022, issued in connection with U.S. Appl. No. 17/114,010, filed Dec. 7, 2020, 9 pages. |
Notice of Allowance mailed on Feb. 16, 2018, issued in connection with U.S. Appl. No. 14/844,253, filed Sep. 3, 2015, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20230292068 A1 | Sep 2023 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16944797 | Jul 2020 | US |
Child | 18064379 | US | |
Parent | 16367808 | Mar 2019 | US |
Child | 16944797 | US | |
Parent | 16180952 | Nov 2018 | US |
Child | 16367808 | US | |
Parent | 15688137 | Aug 2017 | US |
Child | 16180952 | US | |
Parent | 15357548 | Nov 2016 | US |
Child | 15688137 | US | |
Parent | 14803094 | Jul 2015 | US |
Child | 15357548 | US |