The disclosure is related to consumer goods and, more particularly, to methods, systems, products, features, services, and other items directed to media playback or some aspect thereof.
Digital music has become readily available due in part to the development of consumer level technology that has allowed people to listen to digital music on a personal audio device. The consumer's increasing preference for digital audio has also resulted in the integration of personal audio devices into PDAs, cellular phones, and other mobile devices. The portability of these mobile devices has enabled people to take the music listening experience with them and outside of the home. People have become able to consume digital music, like digital music files or even Internet radio, in the home through the use of their computer or similar devices. Now there are many different ways to consume digital music, in addition to other digital content including digital video and photos, stimulated in many ways by high-speed Internet access at home, mobile broadband Internet access, and the consumer's hunger for digital media.
Until recently, options for accessing and listening to digital audio in an out-loud setting were severely limited. In 2005, Sonos offered for sale its first digital audio system that enabled people to, among many other things, access virtually unlimited sources of audio via one or more networked connected zone players, dynamically group or ungroup zone players upon command, wirelessly send the audio over a local network amongst zone players, and play the digital audio out loud across multiple zone players in synchrony. The Sonos system can be controlled by software applications running on network capable mobile devices and computers.
Given the insatiable appetite of consumers towards digital media, there continues to be a need to develop consumer technology that revolutionizes the way people access and consume digital media.
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:
In addition, 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 mechanisms to wake-up a media playback device that is interconnected with other media playback devices to form a networked media system from a standby mode using a network message. For example, the network message, referred to hereafter as a “wake-up packet”, may be received by a media playback device, cause the media playback device to exit a standby mode, and then be forwarded by the media playback device to one or more additional media playback devices in the networked media system. In some embodiments, this process is repeated at additional media playback devices in the networked media system so as to cause the additional devices to exit the standby mode. In other embodiments, the wake-up packet may cause only a single media playback device, or a group of media playback devices, to wake-up from the standby mode. The embodiments described herein may thereby provide “wake” functionality for media playback devices in a network.
Wake-on-LAN (WOL) is a computer networking mechanism that allows a device to be turned on or awakened by a network message sent by another device on the same local area network (LAN). The WOL mechanism is known as Wake-on-Wireless (WoW) when the device being awakened is communicating over a wireless medium. As will be appreciated by those having skill in the art, conventional WOL or WoW techniques require that devices within the network be directly reachable by the source of the network message. When devices are configured in an ad-hoc or mesh network such that one or more indirect routes between devices exist within the network, a different mechanism is needed.
In some embodiments, a networked media playback system may be configured in an ad-hoc (or mesh) network, such that each media playback device may participate in network routing with other media playback devices. In some embodiments, the ad-hoc network may be configured as a layer-2 mesh network using a spanning tree protocol (STP) for network routing. The mesh network may comprise both wired and wireless links between devices, whereby one or more point-to-point routes exist between media playback devices. To prevent routing loops, conventional STP protocols generally utilize non-direct routes instead of direct routes to support communication between playback devices. Based on this STP protocol, a networked media playback system may include one or more non-direct routes between media playback devices. For example, a source device that is sending a wake-up packet to media playback device may be prevented from communicating directly with the media playback device because the route between the source device and the media playback device is through another intermediary media playback device. Therefore, to send the wake-up packet to the media playback device, the source device may communicate via a non-direct route through the intermediary media playback device.
Further, as described above, in some embodiments, the one or more media playback devices may include a standby mode. In the standby mode, one or more components of a media playback device may be disabled or put into a sleep mode. For example, one embodiment of standby mode might involve disabling an audio stage of the media playback device. As another example, standby mode might involve putting a wireless network interface into a sleep mode.
In some embodiments, the various device modes may include an active mode. In the active mode, one or more components of a media playback system may be enabled or taken out of a sleep mode. For example, active mode might involve taking a processor out of a sleep mode.
In some embodiments, a wake-up packet may be sent as an IP broadcast message having a payload that may cause a media playback device to wake-up from standby mode. In some embodiments, the payload may include a broadcast destination MAC address. The broadcast destination MAC address may be used to target all devices within the networked media playback system. This mechanism may be used to wake-up multiple devices within the networked media playback system or a subset of devices based on certain conditions. In other embodiments, the payload may include a unicast destination MAC address. This mechanism may be used to wake-up a single media playback device and the media playback devices needed to form a playback path (i.e., a network path or route used to forward audio packets from an audio source to the single media playback device).
As indicated above, the present application involves mechanisms to wake-up a media playback device from a standby mode using a network message known as a wake-up packet, wherein the media playback device is interconnected with other media playback devices to form a networked media playback system. In one aspect, a method is provided. The method involves receiving, by a first media playback device, while the first media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a MAC broadcast address. In response to receiving the first wake-up packet, the method further involves exiting, by the first media playback device, the standby mode and entering an active mode, and broadcasting, by the first media playback device a second wake-up packet that includes a second payload that is associated with the MAC broadcast address.
In another aspect, a non-transitory computer readable memory is provided. The non-transitory computer-readable storage medium includes a set of instructions for execution by a processor. The set of instructions, when executed, cause a first media playback device to receive, by a first media playback device, while the first media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a MAC broadcast address. In response to receiving the first wake-up packet, the set of instructions, when executed, further cause the first media playback device to exit, by the first media playback device, the standby mode, and enter an active mode; and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC broadcast address.
In a further aspect, a media playback device is provided. The device includes a network interface, a processor, a data storage, and a program logic stored in the data storage and executable by the processor to receive, by the first media playback device, while the media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a MAC broadcast address. In response to receiving the first wake-up packet, the program logic is further executable by the processor to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC broadcast address.
In yet another aspect, a media playback system is provided. The system includes a first media playback device and a second media playback device. The first media playback device includes a network interface, a processor, a data storage and executable by the processor to receive, by the first media playback device, while the media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a MAC broadcast address. In response to receiving the first wake-up packet, the program logic is further executable by the processor to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC broadcast address.
In another aspect, a method is provided in a local area network comprising a plurality of devices, including at least a first media playback device and a second media playback device. The method includes receiving, by a first media playback device, while the first media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a first MAC address. In response to receiving the first wake-up packet, the method further includes determining, by the first media playback device, whether the first MAC address is included in a list of MAC addresses maintained by the first media playback device. When the first MAC address is included in the list of MAC addresses, the method further includes exiting, by the first media playback device, the standby mode, and entering an active mode, and broadcasting, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the first MAC address.
In a further aspect, a non-transitory computer readable memory is provided. The non-transitory computer-readable storage medium includes a set of instructions for execution by a processor. The set of instructions, when executed, cause a first media playback device to receive, by a first media playback device while the first media playback device is in standby mode, a first wake-up packet that includes a first payload that is associated with a first MAC address. In response to receiving the first wake-up packet, the set of instructions further cause the first media playback device to determine, by the first media playback device, whether the first MAC address is included in a list of MAC addresses maintained by the first media playback device. When the first MAC address is included in the list of MAC addresses, the set of instructions further cause the first media playback device to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the first MAC address.
In yet another aspect, a media playback device is provided. The device includes a network interface, a processor, a data storage, and a program logic stored in the data storage and executable by the processor to receive, by the first media playback device is in standby mode, a first wake-up packet that includes a first payload that is associated with a first MAC address. In response to receiving the first wake-up packet, the program logic is further executable by the processor to determine, by the first media playback device, whether the first MAC address is included in a list of MAC addresses maintained by the first media playback device. When the first MAC address is included in the list of MAC addresses, the program logic is further executable by the processor to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC address.
In a further aspect, a media playback system is provided. The system includes a first media playback device and a second media playback device. The first media playback device includes a network interface, a processor, a data storage and executable by the processor to receive, by the first media playback device is in standby mode, a first wake-up packet that includes a first payload that is associated with a first MAC address. In response to receiving the first wake-up packet, the program logic is further executable by the processor to determine, by the first media playback device, whether the first MAC address is included in a list of MAC addresses maintained by the first media playback device. When the first MAC address is included in the list of MAC addresses, the program logic is further executable by the processor to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC address.
Other embodiments, as those discussed in the following and others as can be appreciated by one having ordinary skill in the art are also possible.
Referring now to the drawings, in which like numerals can refer to like parts throughout the figures,
By way of illustration, the media system configuration 100 is associated with a home having multiple zones, although it should be understood that the home could be configured with only one zone. Additionally, one or more zones can be added to the configuration 100 over time. Each zone may be assigned by a user to a different room or space, such as, for example, an office, bathroom, bedroom, kitchen, dining room, family room, home theater room, utility or laundry room, and patio. A single zone might also include multiple rooms or spaces if so configured. With respect to
The media system configuration 100 illustrates an example whole house media system, though it is understood that the technology described herein is not limited to, among other things, its particular place of application or to an expansive system like a whole house media system 100 of
a. Example Zone Players
Referring back to
By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presently offers for sale zone players referred to as a “PLAY:5,” “PLAY:3,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/or future zone players can additionally or alternatively be used to implement the zone players of example embodiments disclosed herein. Additionally, it is understood that a zone player is not limited to the particular examples illustrated in
b. Example Controllers
In some embodiments, if more than one controller is used in system 100 of
In addition, an application running on any network-enabled portable device, such as an iPhone™, iPad™, Android™ powered phone or tablet, or any other smart phone or network-enabled device can be used as controller 130. An application running on a laptop or desktop personal computer (PC) or Mac™ can also be used as controller 130. Such controllers may connect to system 100 through an interface with data network 128, a zone player, a wireless router, or using some other configured connection path. Example controllers offered by Sonos, Inc. of Santa Barbara, Calif. include a “Controller 200,” “SONOS® CONTROL,” “SONOS®Controller for iPhone™,” “SONOS® Controller for iPad™,” “SONOS® Controller for Android™,” “SONOS®” Controller for Mac™ or PC.”
c. Example Data Connection
Zone players 102-124 of
In some embodiments, connecting any of the zone players 102-124, or some other connecting device, to a broadband router, can create data network 128. Other zone players 102-124 can then be added wired or wirelessly to the data network 128. For example, a zone player (e.g., any of zone players 102-124) can be added to the system configuration 100 by simply pressing a button on the zone player itself (or perform some other action), which enables a connection to be made to data network 128. The broadband router can be connected to an Internet Service Provider (ISP), for example. The broadband router can be used to form another data network within the system configuration 100, which can be used in other applications (e.g., web surfing). Data network 128 can also be used in other applications, if so programmed. An example, second network may implement SONOSNET™ protocol, developed by SONOS, Inc. of Santa Barbara. SONOSNET™ represents a secure, AES-encrypted, peer-to-peer wireless mesh network. Alternatively, in certain embodiments, the data network 128 is the same network, such as a traditional wired or wireless network, used for other applications in the household.
d. Example Zone Configurations
A particular zone can contain one or more zone players. For example, the family room of
In some embodiments, a “bonded zone” contains two or more zone players, such as the two zone players 106 and 108 in the family room whereby the two zone players 106 and 108 can be configured to play the same audio source in synchrony. In one example, the two zone players 106 and 108 can be paired to play two separate sounds in left and right channels, for example. In other words, the stereo effects of a sound can be reproduced or enhanced through the two zone players 106 and 108, one for the left sound and the other for the right sound. In another example two or more zone players can be sonically consolidated to form a single, consolidated zone player. A consolidated zone player (though made up of multiple, separate devices) can be configured to process and reproduce sound differently than an unconsolidated zone player or zone players that are paired, because a consolidated zone player has additional speaker drivers from which sound can be passed. The consolidated zone player can further be paired with a single zone player or yet another consolidated zone player. Each playback device of a consolidated playback device can be set in a consolidated mode, for example.
In certain embodiments, paired or consolidated zone players (also referred to as “bonded zone players”) can play audio in synchrony with other zone players in the same or different zones.
According to some embodiments, one can continue to do any of: group, consolidate, and pair zone players, for example, until a desired configuration is complete. The actions of grouping, consolidation, and pairing are preferably performed through a control interface, such as using controller 130, and not by physically connecting and re-connecting speaker wire, for example, to individual, discrete speakers to create different configurations. As such, certain embodiments described herein provide a more flexible and dynamic platform through which sound reproduction can be offered to the end-user.
e. Example Audio Sources
In some embodiments, each zone can play from the same audio source as another zone or each zone can play from a different audio source. For example, someone can be grilling on the patio and listening to jazz music via zone player 124, while someone is preparing food in the kitchen and listening to classical music via zone player 102. Further, someone can be in the office listening to the same jazz music via zone player 110 that is playing on the patio via zone player 124. In some embodiments, the jazz music played via zone players 110 and 124 is played in synchrony. Synchronizing playback amongst zones allows for an individual to pass through zones while seamlessly (or substantially seamlessly) listening to the audio. Further, zones can be put into a “party mode” such that all associated zones will play audio in synchrony.
Sources of audio content to be played by zone players 102-124 are numerous. In some embodiments, audio on a zone player itself may be accessed and played. In some embodiments, audio on a controller may be accessed via the data network 128 and played. In some embodiments, music from a personal library stored on a computer or networked-attached storage (NAS) may be accessed via the data network 128 and played. In some embodiments, Internet radio stations, shows, and podcasts may be accessed via the data network 128 and played. Music or cloud services that let a user stream and/or download music and audio content may be accessed via the data network 128 and played. Further, music may be obtained from traditional sources, such as a turntable or CD player, via a line-in connection to a zone player, for example. Audio content may also be accessed using a different protocol, such as Airplay™, which is a wireless technology by Apple, Inc., for example. Audio content received from one or more sources can be shared amongst the zone players 102 to 124 via data network 128 and/or controller 130. The above-disclosed sources of audio content are referred to herein as network-based audio information sources. However, network-based audio information sources are not limited thereto.
In some embodiments, the example home theater zone players 116, 118, 120 are coupled to an audio information source such as a television 132. In some examples, the television 132 is used as a source of audio for the home theater zone players 116, 118, 120, while in other examples audio information from the television 132 may be shared with any of the zone players 102-124 in the audio system 100.
Referring now to
In some embodiments, network interface 402 facilitates a data flow between zone player 400 and other devices on a data network 128. In some embodiments, in addition to getting audio from another zone player or device on data network 128, zone player 400 may access audio directly from the audio source, such as over a wide area network or on the local network. In some embodiments, the network interface 402 can further handle the address part of each packet so that it gets to the right destination or intercepts packets destined for the zone player 400. Accordingly, in certain embodiments, each of the packets includes an Internet Protocol (IP)-based source address as well as an IP-based destination address.
In some embodiments, network interface 402 can include one or both of a wireless interface 404 and a wired interface 406. The wireless interface 404, also referred to as a radio frequency (RF) interface, provides network interface functions for the zone player 400 to wirelessly communicate with other devices (e.g., other zone player(s), speaker(s), receiver(s), component(s) associated with the data network 128, and so on) 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). Wireless interface 404 may include one or more radios. To receive wireless signals and to provide the wireless signals to the wireless interface 404 and to transmit wireless signals, the zone player 400 includes one or more antennas 420. The wired interface 406 provides network interface functions for the zone player 400 to communicate over a wire with other devices in accordance with a communication protocol (e.g., IEEE 802.3). In some embodiments, a zone player includes multiple wireless 404 interfaces. In some embodiments, a zone player includes multiple wired 406 interfaces. In some embodiments, a zone player includes both of the interfaces 404 and 406. In some embodiments, a zone player 400 includes only the wireless interface 404 or the wired interface 406.
In some embodiments, the processor 408 is a clock-driven electronic device that is configured to process input data according to instructions stored in memory 410. The memory 410 is data storage that can be loaded with one or more software module(s) 414, which can be executed by the processor 408 to achieve certain tasks. In the illustrated embodiment, the memory 410 is a tangible machine-readable medium storing instructions that can be executed by the processor 408. In some embodiments, a task might be for the zone player 400 to retrieve audio data from another zone player or a device on a network (e.g., using a uniform resource locator (URL) or some other identifier). In some embodiments, a task may be for the zone player 400 to send audio data to another zone player or device on a network. In some embodiments, a task may be for the zone player 400 to synchronize playback of audio with one or more additional zone players. In some embodiments, a task may be to pair the zone player 400 with one or more zone players to create a multi-channel audio environment. Additional or alternative tasks can be achieved via the one or more software module(s) 414 and the processor 408.
The audio stage is a system for producing processed amplified analog audio signals for playback through speakers. The audio stage 424 can include an audio processing component 412 and an audio amplifier 416, or it may include only one of these components.
The audio processing component 412 can include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor, and so on. In some embodiments, the audio processing component 412 may be part of processor 408. In some embodiments, the audio that is retrieved via the network interface 402 is processed and/or intentionally altered by the audio processing component 412. Further, the audio processing component 412 can produce analog audio signals. The processed analog audio signals are then provided to the audio amplifier 416 for playback through speakers 418. In addition, the audio processing component 412 can include circuitry to process analog or digital signals as inputs to play from zone player 400, send to another zone player on a network, or both play and send to another zone player on the network. An example input includes a line-in connection (e.g., an auto-detecting 3.5 mm audio line-in connection).
The audio amplifier 416 is a device(s) that amplifies audio signals to a level for driving one or more speakers 418. The one or more speakers 418 can include an individual transducer (e.g., a “driver”) or a complete speaker system that includes an enclosure including one or more drivers. A particular driver can be a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and a tweeter (e.g., for high frequencies), for example. An enclosure can be sealed or ported, for example. Each transducer may be driven by its own individual amplifier.
Further, in some instances, zone player 400 may be a powered by a direct current (DC) power supply, e.g., a battery 426. Yet further, power indicator 422 may identify the level of power in battery 426 of zone player 400. Based on the level of power in battery 426, controller 500 may adjust the payload of the wake-up packet to wake-up a different subset of zone players 400 to conserve the power remaining in battery 426.
A commercial example, presently known as the PLAY:5™, is a zone player with a built-in amplifier and speakers that is capable of retrieving audio directly from the source, such as on the Internet or on the local network, for example. In particular, the PLAY:5™ is a five-amp, five-driver speaker system that includes two tweeters, two mid-range drivers, and one woofer. When playing audio content via the PLAY:5, the left audio data of a track is sent out of the left tweeter and left mid-range driver, the right audio data of a track is sent out of the right tweeter and the right mid-range driver, and mono bass is sent out of the subwoofer. Further, both mid-range drivers and both tweeters have the same equalization (or substantially the same equalization). That is, they are both sent the same frequencies but from different channels of audio. Audio from Internet radio stations, online music and video services, downloaded music, analog audio inputs, television, DVD, and so on, can be played from the PLAY:5™.
Referring now to
Controller 500 is provided with a screen 502 and an input interface 514 that allows a user to interact with the controller 500, for example, to navigate a playlist of many multimedia items and to control operations of one or more zone players. The screen 502 on the controller 500 can be an LCD screen, for example. The screen 500 communicates with and is commanded by a screen driver 504 that is controlled by a microcontroller (e.g., a processor) 506. The memory 510 can be loaded with one or more application modules 512 that can be executed by the microcontroller 506 with or without a user input via the user interface 514 to achieve certain tasks. In some embodiments, an application module 512 is configured to facilitate grouping a number of selected zone players into a zone group to facilitate synchronized playback amongst the zone players in the zone group. In some embodiments, an application module 512 is configured to control the audio sounds (e.g., volume) of the zone players in a zone group. In operation, when the microcontroller 506 executes one or more of the application modules 512, the screen driver 504 generates control signals to drive the screen 502 to display an application specific user interface accordingly.
The controller 500 includes a network interface 508 that facilitates wired or wireless communication with a zone player. In some embodiments, the commands such as volume control and audio playback synchronization are sent via the network interface 508. In some embodiments, a saved zone group configuration is transmitted between a zone player and a controller via the network interface 508. The controller 500 can control one or more zone players, such as 102-124 of
It should be noted that other network-enabled devices such as an iPhone™, iPad™ or any other smart phone or network-enabled device (e.g., a networked computer such as a PC or Mac™) can also be used as a controller to interact or control zone players in a particular environment. In some embodiments, a software application or upgrade can be downloaded onto a network-enabled device to perform the functions described herein.
In certain embodiments, a user can create a zone group (also referred to as a bonded zone) including at least two zone players from the controller 500. The zone players in the zone group can play audio in a synchronized fashion, such that all of the zone players in the zone group playback an identical audio source or a list of identical audio sources in a synchronized manner such that no (or substantially no) audible delays or hiccups are to be heard. Similarly, in some embodiments, when a user increases the audio volume of the group from the controller 500, the signals or data of increasing the audio volume for the group are sent to one of the zone players and causes other zone players in the group to be increased together in volume.
A user via the controller 500 can group zone players into a zone group by activating a “Link Zones” or “Add Zone” soft button, or de-grouping a zone group by activating an “Unlink Zones” or “Drop Zone” button. For example, one mechanism for ‘joining’ zone players together for audio playback is to link a number of zone players together to form a group. To link a number of zone players together, a user can manually link each zone player or room one after the other. For example, assume that there is a multi-zone system that includes the following zones: Bathroom, Bedroom, Den, Dining Room, Family Room, and Foyer. In certain embodiments, a user can link any number of the six zone players, for example, by starting with a single zone and then manually linking each zone to that zone.
In certain embodiments, a set of zones can be dynamically linked together using a command to create a zone scene or theme (subsequent to first creating the zone scene). For instance, a “Morning” zone scene command can link the Bedroom, Office, and Kitchen zones together in one action. Without this single command, the user would manually and individually link each zone. The single command may include a mouse click, a double mouse click, a button press, a gesture, or some other programmed or learned action. Other kinds of zone scenes can be programmed or learned by the system over time.
In certain embodiments, a zone scene can be triggered based on time (e.g., an alarm clock function). For instance, a zone scene can be set to apply at 8:00 am. The system can link appropriate zones automatically, set specific music to play, and then stop the music after a defined duration and revert the zones to their prior configuration. Although any particular zone can be triggered to an “On” or “Off” state based on time, for example, a zone scene enables any zone(s) linked to the scene to play a predefined audio (e.g., a favorable song, a predefined playlist) at a specific time and/or for a specific duration. If, for any reason, the scheduled music failed to be played (e.g., an empty playlist, no connection to a share, failed Universal Plug and Play (UPnP), no Internet connection for an Internet Radio station, and so on), a backup buzzer can be programmed to sound. The buzzer can include a sound file that is stored in a zone player, for example.
As discussed above, in some embodiments, a zone player may be assigned to a playback queue identifying zero or more media items for playback by the zone player. The media items identified in a playback queue may be represented to the user via an interface on a controller. For instance, the representation may show the user (or users if more than one controller is connected to the system) how the zone player is traversing the playback queue, such as by highlighting the “now playing” item, graying out the previously played item(s), highlighting the to-be-played item(s), and so on.
In some embodiments, a single zone player is assigned to a playback queue. For example, zone player 114 in the bathroom of
In some embodiments, a zone or zone group is assigned to a playback queue. For example, zone players 106 and 108 in the family room of
As such, when zones or zone groups are “grouped” or “ungrouped” dynamically by the user via a controller, the system will, in some embodiments, establish or remove/rename playback queues respectively, as each zone or zone group is to be assigned to a playback queue. In other words, the playback queue operates as a container that can be populated with media items for playback by the assigned zone. In some embodiments, the media items identified in a playback queue can be manipulated (e.g., re-arranged, added to, deleted from, and so on).
By way of illustration,
In one example, the example audio sources 662 and 664, and example media items 620 may be partially stored on a cloud network, discussed more below in connection to
Each of the example media items 620 may be a list of media items playable by a zone player(s). In one embodiment, the example media items may be a collection of links or pointers (i.e., URI) to the underlying data for media items that are stored elsewhere, such as the audio sources 662 and 664. In another embodiment, the media items may include pointers to media content stored on the local zone player, another zone player over a local network, or a controller device connected to the local network.
As shown, the example network 600 may also include an example queue 602 associated with the zone player 612, and an example queue 604 associated with the zone player 614. Queue 606 may be associated with a group, when in existence, comprising zone players 612 and 614. Queue 606 might comprise a new queue or exist as a renamed version of queue 602 or 604. In some embodiments, in a group, the zone players 612 and 614 would be assigned to queue 606 and queue 602 and 604 would not be available at that time. In some embodiments, when the group is no longer in existence, queue 606 is no longer available. Each zone player and each combination of zone players in a network of zone players, such as those shown in
A playback queue, such as playback queues 602-606, may include identification of media content to be played by the corresponding zone player or combination of zone players. As such, media items added to the playback queue are to be played by the corresponding zone player or combination of zone players. The zone player may be configured to play items in the queue according to a specific order (such as an order in which the items were added), in a random order, or in some other order.
The playback queue may include a combination of playlists and other media items added to the queue. In one embodiment, the items in playback queue 602 to be played by the zone player 612 may include items from the audio sources 662, 664, or any of the media items 622-632. The playback queue 602 may also include items stored locally on the zone player 612, or items accessible from the zone player 614. For instance, the playback queue 602 may include Internet radio 626 and album 632 items from audio source 662, and items stored on the zone player 612.
When a media item is added to the queue via an interface of a controller, a link to the item may be added to the queue. In a case of adding a playlist to the queue, links to the media items in the playlist may be provided to the queue. For example, the playback queue 602 may include pointers from the Internet radio 626 and album 632, pointers to items on the audio source 662, and pointers to items on the zone player 612. In another case, a link to the playlist, for example, rather than a link to the media items in the playlist may be provided to the queue, and the zone player or combination of zone players may play the media items in the playlist by accessing the media items via the playlist. For example, the album 632 may include pointers to items stored on audio source 662. Rather than adding links to the items on audio source 662, a link to the album 632 may be added to the playback queue 602, such that the zone player 612 may play the items on the audio source 662 by accessing the items via pointers in the album 632.
In some cases, contents as they exist at a point in time within a playback queue may be stored as a playlist, and subsequently added to the same queue later or added to another queue. For example, contents of the playback queue 602, at a particular point in time, may be saved as a playlist, stored locally on the zone player 612 and/or on the cloud network. The saved playlist may then be added to playback queue 604 to be played by zone player 614.
Particular examples are now provided in connection with
Using the Ad-Hoc network 710, the devices 702, 704, 706, and 708 can share or exchange one or more audio sources and be dynamically grouped (or ungrouped) to play the same or different audio sources. For example, the devices 702 and 704 are grouped to playback one piece of music, and at the same time, the device 706 plays back another piece of music. In other words, the devices 702, 704, 706 and 708, as shown in
In certain embodiments, a household identifier (HHID) is a short string or an identifier that is computer-generated to help ensure that it is unique. Accordingly, the network 710 can be characterized by a unique HHID and a unique set of configuration variables or parameters, such as channels (e.g., respective frequency bands), service set identifier (SSID) (a sequence of alphanumeric characters as a name of a wireless network), and WEP keys (wired equivalent privacy) or other security keys. In certain embodiments, SSID is set to be the same as HHID.
In certain embodiments, each HOUSEHOLD includes two types of network nodes: a control point (CP) and a zone player (ZP). The control point controls an overall network setup process and sequencing, including an automatic generation of required network parameters (e.g., security keys). In an embodiment, the CP also provides the user with a HOUSEHOLD configuration user interface. The CP function can be provided by a computer running a CP application module, or by a handheld controller (e.g., the controller 308) also running a CP application module, for example. The zone player is any other device on the network that is placed to participate in the automatic configuration process. The ZP, as a notation used herein, includes the controller 308 or a computing device, for example. In some embodiments, the functionality, or certain parts of the functionality, in both the CP and the ZP are combined at a single node (e.g., a ZP contains a CP or vice-versa).
In certain embodiments, configuration of a HOUSEHOLD involves multiple CPs and ZPs that rendezvous and establish a known configuration such that they can use a standard networking protocol (e.g., IP over Wired or Wireless Ethernet) for communication. In an embodiment, two types of networks/protocols are employed: Ethernet 802.3 and Wireless 802.11g. Interconnections between a CP and a ZP can use either of the networks/protocols. A device in the system as a member of a HOUSEHOLD can connect to both networks simultaneously.
In an environment that has both networks in use, it is assumed that at least one device in a system is connected to both as a bridging device, thus providing bridging services between wired/wireless networks for others. The zone player 706 in
It is understood, however, that in some embodiments each zone player 706, 704, 702 may access the Internet when retrieving media from the cloud (e.g., the Internet) via the bridging device. For example, zone player 702 may contain a uniform resource locator (URL) that specifies an address to a particular audio track in the cloud. Using the URL, the zone player 702 may retrieve the audio track from the cloud, and ultimately play the audio out of one or more zone players.
As illustrated by the example system 800 of
As discussed above, embodiments described herein may involve mechanisms to wake-up a media playback device that is interconnected with other media playback devices to form a networked media playback system from a standby mode using a network message known as a wake-up packet. Further, as noted above, the wake-up packet may have various payloads depending on the media playback devices that are targeted by the wake-up packet. In some embodiments, the wake-up packet may have a broadcast destination address in the payload. These embodiments may be used to wake multiple media playback devices within the networked media playback system, or they may be used to wake a subset of media playback devices according to certain conditions.
In some embodiments, two or more media playback devices may be interconnected in a network to form a media playback system.
As a general matter, each of blocks 902-906 and 1102-1106 may be carried out by one or more media playback devices. Media playback devices may include any one or more of zone players 102-124 of
Methods 900 and 1100 may include one or more operations, functions, or actions as illustrated by one or more of blocks 902-906 and 1102-1106. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.
In addition, for the methods 900, 1100, and other processes and methods disclosed herein, the flowchart shows 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 method 900 and other processes and methods disclosed herein, each block in
a. Receiving, while the First Media Playback Device is in a Standby Mode, a First Wake-Up Packet
At block 902, the method 900 may involve receiving, by a first media playback device, while the first media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a MAC broadcast address. As described above, the first media playback device may have a network interface. For example, a first media playback device might be a first zone player 400 of
The first wake-up packet includes a first payload that is associated with a MAC broadcast address. Consider
MAC address 1008 may be a unique identifier assigned to network interfaces for network communications. For example, wireless network interface 404 may have a unique MAC address to identify the wireless network interface 404 on network 710, 712, 850, or 860. The MAC address may conform to the IEEE 802 standard format having a 48-bit address space.
The first payload 1006 may be associated with media access control (MAC) address 1008. The first payload 1006 may include sixteen repetitions of a MAC address 1008. Sixteen repetitions of a MAC address 1008 may be recognized by the first media playback device as a signal to enter or exit a device mode, such as a standby mode. In some embodiments, MAC address 1008 might be the broadcast destination address. In some embodiments, the broadcast destination address may be the MAC address FF:FF:FF:FF:FF:FF, otherwise known as the “all F” address.
The control information 1004 may include, along with other information, a destination address. In some embodiments, the destination address will be the broadcast destination address. In some embodiments, the broadcast destination address may be the MAC address FF:FF:FF:FF:FF:FF, otherwise known as the “all F” address.
In some embodiments, such as wherein a first media playback device and a second media playback device are interconnected to form a media playback system, a second media playback device may receive, by the second media playback device while the second media playback device is in standby mode, a second wake-up packet. For example, media playback device 1206 in
The first wake-up packet 1002 may be sent from any device within the network 710, 712, 850, or 860. For example, the first wake-up packet 1002 may be sent from controller 500 using network interface 508 when a user initiates the playback of an audio track using input interface 514. Or, the wake-up packet 1002 may be sent from an additional zone player 400 using network interface 402. Alternatively, the first wake-up packet 1002 may originate at a controller 500 and be routed through one or more additional intermediary zone players 400 before being received by the first zone player 400. For example, the first wake-up packet may originate at controller 1216 or 1218 and be routed through intermediary media playback device 1206 before being received by media playback device 1208. In some embodiments, the first wake-up packet may originate at a wireless media playback device, such as media playback device 1206.
In method 900, the first media playback device may be configured to be initially in a standby mode, e.g., before executing block 902 in method 900. For example, the first zone player 400 may be configured to be in standby mode. For example, media playback device 1206 may be in a standby mode. Standby mode may involve disabling one or more components of the media playback device. Further, standby mode may involve putting one or more components in a sleep mode, a standby mode, or the like. In some embodiments, standby mode may involve disabling one or more audio playback components. Standby mode may reduce overall power consumption by the first media playback device as compared to other device modes.
In some embodiments, such as wherein a first media playback device and a second media playback device are interconnected to form a media playback system, the second media playback device may be configured to be initially in a standby mode. For example, the first media playback device 1206 may be may be configured to be initially in a standby mode and the second media playback device 1208 may be configured to be initially in a standby mode.
In further embodiments, standby mode may involve one or more of the following: disabling an audio playback stage of the first media playback device; enabling a processor sleep mode for a processor of the first media playback device; or enabling a network interface sleep mode for at least one network interface of the first media playback device. For example, standby mode for zone player 400 might involve disabling audio stage 424 or components thereof, such as audio processing component 412 or audio amplifier 416. Standby mode for zone player 400 might additionally or alternatively involve enabling a sleep mode for processor 408 or network interface 402. Sleep mode for processor 408 may be, for example, a device mode in which the processor does not execute instructions. Sleep mode for network interface 402 may be, for example, a device mode in which the network interface is not actively communicating, but instead periodically checking for an incoming message, such as a wake-up packet 1002. The examples described above are provided to illustrate possible embodiments of standby mode. Other embodiments not described here are contemplated.
b. Exiting the Standby Mode and Entering an Active Mode
At block 904, method 900 may involve the first media playback device responding to receiving the first wake-up packet by exiting the standby mode and entering an active mode. For example, the first zone player 400 may respond to receiving the first wake-up packet by exiting the standby mode and enter the active mode. For example, media playback device 1206 may respond to receiving the first wake-up packet by exiting the standby mode and entering the active mode. Active mode may involve enabling one or more components of the media playback device. Further, active mode may involve taking one or more components out of a sleep mode, a standby mode, or the like. In some embodiments, active mode may involve enabling one or more audio playback components.
In some embodiments, such as wherein a first media playback device and a second media playback device are interconnected to form a media playback system, the second media playback device may respond to receiving the first wake-up packet by exiting the standby mode and entering the active mode.
In some embodiments, active mode may involve one or more of the following: enabling an audio playback stage of the first media playback device; disabling a processor sleep mode for a processor of the first media playback device; or disabling a network interface sleep mode for at least one network interface of the first media playback device. For example, active mode for zone player 400 might involve enabling audio stage 424 or components thereof, such as audio processing component 412 or audio amplifier 416. Additionally or alternatively, active mode for zone player 400 might involve disabling a sleep mode for processor 408 or network interface 402. Active mode might also be referred to as the normal operating mode for the first media playback device. In some embodiments, the first media playback device may consume more power in active mode as compared with at least one other device mode, such as standby mode.
c. Broadcasting a Second Wake-Up Packet that Includes a Second Payload that is Associated with the MAC Broadcast Address
At block 906, method 900 may involve the first media playback device responding to receiving the first wake-up packet by broadcasting a second wake-up packet that includes a second payload that is associated with the MAC broadcast address. In some embodiments, broadcasting the second wake-up packet will involve creating a second wake-up packet and transmitting the second wake-up packet on a network interface. For example, the first zone player 400 may create a second wake-up packet 1002 and transmit the second wake-up packet 1002 on network interface 402 using either wireless network interface 404 or wired interface 406. The second wake-up packet 1002 may include the broadcast address as the destination address in the control information 1004. Moreover, the second wake-up packet 1002 may include a second payload 1006 that includes the broadcast destination address. In some embodiments, the second payload 1006 may have sixteen repetitions of the broadcast destination address. However, the second payload 1006 may have other data in addition to the broadcast destination address or repetitions thereof.
As another example, media playback device 1206 in
The method 900 may be repeated at additional media playback devices within the media playback system until so as to cause additional media playback devices in the system to be woken up. For example, each of media playback devices 1206, 1208, 1210, 1212, and 1214 may receive a wake-up packet, exit standby mode and enter active mode, and broadcast a wake-up packet.
Further, in some embodiments, the second payload 1006 included in the second wake-up packet 1002 may be the same payload 1006 as the first payload included in the first wake-up packet 1002. For example, the first zone player 400 may copy the first payload 1006 from the first wake-up packet 1002 to the second wake-up packet 1002. Or, the first zone player 400 may translate the information in the first payload 1006 from the first wake-up packet 1002 to the second payload 1006 in the second wake-up packet 1002.
Further, in some embodiments, additional functions may be carried out in addition to method 900. These functions may involve the first media playback device, after broadcasting the second wake-up packet, exiting the active mode, and entering the standby mode. For example, the first zone player 400, after broadcasting second wake-up packet 1102 on network interface 402, may exit the active mode and enter the standby mode. Yet, further, in some embodiments, the first media playback device exits the active mode and enters the standby mode when certain conditions are met.
Consider method 1100 including blocks 1102, 1104, and 1106, any or all of which may be used in conjunction with method 900 such that blocks 1102-1106 occur before, after, or concurrently with any of blocks 902-906. For example, at block 1102 in
In some embodiments, the first media playback device may determine whether the first media playback device is forwarding playback packets to a second media playback device by counting, for a predetermined period of time, the number of packets received during that period by the first media playback device. If the number of packets received during the period is more than a threshold, the first media playback device may determine that it is forwarding packets. For example, zone player 400 may count packets received on network interface 402 during a predetermined period of time.
Other methods of determining whether the first media playback device is forwarding playback packets are possible as well. Moreover, the determination of whether the first media playback device is forwarding playback packets may be repeated periodically to determine whether the forwarding of playback packets continues or whether forwarding has ended.
In some embodiments, additional actions based upon the determination of whether or not the first media playback device is forwarding playback packets to a second media device may be taken. Consider, at block 1104, when the first media playback device is not forwarding playback packets to the second media playback device, the first media playback device may exit the active mode and enter the standby mode. For example, the first zone player 400 may exit the active mode and enter the standby mode when the first zone player 400 is not forwarding packets on network interface 402. Or, at block 1106, when the first media playback device is forwarding playback packets to the second media playback device, the first media playback device may remain in the active mode. For example, first zone player 400 may remain in the active mode so that playback packets may be forwarded on network interface 402.
Moreover, method 1100 may be repeated for the additional media playback devices such that only a subset of media playback devices within the media playback system that are within a playback path remain in the active mode. For example, each media playback device 1206-1214 determines whether it is forwarding playback packets to at least one additional media playback device 1206-1214. If any media playback device 1206-1214 is not forwarding playback packets, then that media playback device 1206-1214 exits the active mode and enters the standby mode. In some embodiments, if any media playback device 1206-1214 is forwarding playback packets, then each media playback device 1206-1214 may remain in the active mode.
As discussed above, embodiments described herein may involve mechanisms to wake-up a media playback device from a standby mode using a network message known as a wake-up packet wherein the media playback device is interconnected with other media playback devices to form a networked media playback system. Further, as noted above, the wake-up packet may have various payloads depending on the media playback devices that are targeted by the wake-up packet. In some embodiments, the wake-up packet may have a unicast destination address in the payload. These embodiments may be used to wake a subset of media playback devices, such as a destination media playback device and additional media playback devices forming a playback path to the destination media playback device.
In some embodiments, two or more media playback devices may be interconnected in a network to form a media playback system.
As a general matter, each of blocks 1302-1308 and 1502-1504 may be carried out by one or more media playback devices. Media playback devices may include any one or more of zone players 102-124 of
Methods 1300 and 1500 may include one or more operations, functions, or actions as illustrated by one or more of blocks 1302-1308 and 1502-1504. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.
In addition, for the methods 1300, 1500, and other processes and methods disclosed herein, the flowchart shows 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 method 1200 and other processes and methods disclosed herein, each block in
a. Receiving, while the First Media Playback Device is in a Standby Mode, a First Wake-Up Packet
At block 1302, the method 1300 may involve receiving, by a first media playback device, while the first media playback device is in a standby mode, a first wake-up packet that is that includes a first payload associated with a MAC address. As described above, a first media playback device may have a network interface. For example, a first media playback device might be a first zone player 400 of
The first wake-up packet includes a first payload that is associated with a MAC address. Consider
MAC address 1408 may be a unique identifier assigned to network interfaces for network communications. For example, wireless network interface 404 may have a unique MAC address to identify the wireless network interface 404 on network 710, 712, 850, or 860. The MAC address may conform to the IEEE 802 standard format having a 48-bit address space.
The first wake-up packet 1402 may have a first payload 1406 that includes a MAC address 1408. The first payload 1406 may include sixteen repetitions of a MAC address 1408. Sixteen repetitions of the MAC address 1408 may be recognized by the first media playback device as a signal to enter or exit a device mode, such as a standby mode. In some embodiments, the MAC address 1408 included in the payload may be a unicast destination address that refers to a media playback device. For example, the unicast destination address may refer to a network interface of a media playback device such as network interface 402 of zone player 400. In another example, the unicast destination address may refer to a network interface of media playback device 1206 in
The control information 1404 may include, along with other information, a destination address. In some embodiments, the destination address may be the broadcast destination address. In some embodiments, the broadcast destination address may be the MAC address FF:FF:FF:FF:FF:FF, otherwise known as the “all F” address. In other embodiments, the destination address may be a unicast destination address that refers to a media playback device. For example, the unicast destination address may refer to a network interface of a media playback device such as network interface 402 of zone player 400. In another example, the unicast destination address may refer to a network interface of media playback device 1206 in
In some embodiments, such as wherein a first media playback device and a second media playback device are interconnected to form a media playback system, a second media playback device may receive, by the second media playback device while the second media playback device is in standby mode, a second wake-up packet. For example, media playback device 1206 in
The first wake-up packet 1402 may be sent from any device within the network 710, 712, 850, or 860. For example, the first wake-up packet 1402 may be sent from controller 500 using network interface 508 when a user initiates the playback of an audio track using input interface 514. Or, the first wake-up packet 1402 may be sent from an additional zone player 400 using network interface 402. Alternatively, the wake-up packet 1402 may originate at a controller 500 and travel through one or more additional intermediary zone players 400 before being received by the first zone player 400.
In method 1400, the first media playback device may be configured to be initially in a standby mode. For example, the first zone player 400 may be configured to be in standby mode, e.g., before executing block 1402 in method 1400. For example, the first zone player 400 may be configured to be in standby mode. Or, media playback device 1206 may be in a standby mode. Standby mode may involve disabling one or more components of the media playback device. Further, standby mode may involve putting one or more components in a sleep mode, a standby mode, or the like. In some embodiments, standby mode may involve disabling one or more audio playback components. Standby mode may reduce overall power consumption by the first media playback device as compared to other device modes.
In some embodiments, such as wherein a first media playback device and a second media playback device are interconnected to form a media playback system, the second media playback device may be configured to be initially in a standby mode. For example, the first media playback device 1206 may be may be configured to be initially in a standby mode and the second media playback device 1208 may be configured to be initially in a standby mode.
In further embodiments, standby mode may involve one or more of the following: disabling an audio playback stage of the first media playback device; enabling a processor sleep mode for a processor of the first media playback device; or enabling a network interface sleep mode for at least one network interface of the first media playback device. For example, standby mode for zone player 400 might involve disabling audio stage 424 or components thereof, such as audio processing component 412 or audio amplifier 416. Standby mode for zone player 400 might additionally or alternatively involve enabling a sleep mode for processor 408 or network interface 402. Sleep mode for processor 408 may be, for example, a device mode in which the processor is not executing instructions. Sleep mode for network interface 402 may be, for example, a device mode in which the network interface is not actively communicating, but instead periodically checking for an incoming message, such as a wake-up packet 1402. Standby mode may reduce overall power consumption by the first media playback device as compared to other device modes.
b. Determining Whether the First MAC Address is Included in a List of MAC Addresses Maintained by the First Media Playback Device
At block 1304, the method 1300 may involve determining whether the first MAC address is included in a list of MAC addresses maintained by the first media playback device. For example, first zone player 400 may determine whether MAC address 1408 in wake-up packet 1402 is included in a list of MAC addresses maintained by the first zone player 400. The list of MAC addresses may include the MAC address of the first media playback device along with any additional media playback devices. Referring to
The first media playback device may determine whether the first MAC address is included in the list of MAC addresses maintained by the first media playback device using a plurality of embodiments. For example, the first media playback device may compare the first MAC address to each MAC address in the list of MAC addresses maintained by the first media playback device. Other embodiments not described here are contemplated as well.
In some embodiments, a second media playback device may determine whether the first MAC address is included in a list of MAC addresses maintained by the second media playback device. For example, media playback device 1206 in
The list of MAC addresses may include the MAC addresses of additional media playback devices for which the first media playback device is acting as a proxy. Referring to
At block 1504, method 1500 may further involve the first media device adding the second MAC address to the list of MAC addresses wherein the second MAC address is associated with the second media playback device. For example this may involve a first zone player 400 adding the MAC address of a second zone player 400 to the list of MAC addresses wherein the MAC address of the second zone player 400. As another example, media playback device 1208 may receive the request to proxy from media playback 1212 and add the MAC address of the network interface of media playback device 1212 to the list of MAC addresses maintained by media playback device 1208.
In some embodiments, additional functions may be performed in addition to method 1500. These functions may involve sending, to the first media playback device, a request to proxy for the second media device, wherein the request to proxy includes a second MAC address associated with the second media playback device and a third MAC address associated with a third media playback device, wherein the second media playback device is a proxy for the third media playback device. For example, media playback device 1208 may receive the request to proxy from media playback 1212 and add the MAC address of the network interface of media playback device 1212 to the list of MAC addresses maintained by media playback device 1208. If media playback device 1208 goes into standby mode, then it must send a request to proxy to media playback device 1206. However, since media playback device 1208 is already a proxy for media playback device 1212, the request to proxy sent by media playback device 1208 to media playback device 1206 may also include the MAC address of media playback 1212 in addition to the MAC address of media playback device 1208.
These functions may involve the first media playback device adding a third MAC addresses to the list of MAC addresses maintained by the first media playback device. For example, continuing the example above, when media playback device 1206 receives the request to proxy sent by media playback device 1208 to media playback device 1206 that may also include the MAC address of media playback 1212 in addition to the MAC address of media playback device 1208, media playback device 1206 may add the MAC address of media playback device 1212 to the list of MAC addresses maintained by media playback device 1206. In some embodiments, both the MAC address of media playback device 1208 and 1212 may be added to the list of MAC addresses maintained by media playback device 1206. Moreover, this process may be repeated for additional downstream media playback devices such as media playback devices 1210 and 1214 such that media playback device 1206 may have a list of MAC addresses corresponding to downstream devices for which it is acting as a proxy.
c. Exiting the Standby Mode and Entering an Active Mode
At block 1306, method 1300 may involve the first media playback device exiting the standby mode and entering an active mode when the first MAC address is included in the list of MAC addresses. For example, the first zone player 400 may exit the standby mode and enter the active mode when the first MAC address is included in the list of MAC addresses. Or, media playback device 1206 may exit the standby mode and enter the active mode when the first MAC address is included in the list of MAC addresses. Active mode may involve enabling one or more components of the media playback device. Further, active mode may involve taking one or more components out of a sleep mode, a standby mode, or the like. In some embodiments, active mode may involve enabling one or more audio playback components.
In some embodiments, such as wherein a first media playback device and a second media playback device are interconnected to form a media playback system, the second media playback device may exit the standby mode and enter the active mode when the first MAC address is included in the list of MAC addresses maintained by the second media playback device. For example, the second media playback device 1208 may exit the standby mode and enter the active mode when the first MAC address is included in the list of MAC addresses maintained by the second media playback device 1208.
In some embodiments, active mode may involve one or more of the following: enabling an audio playback stage of the first media playback device; disabling a processor sleep mode for a processor of the first media playback device; and disabling a network interface sleep mode for at least one network interface of the first media playback device. For example, active mode for zone player 400 might involve enabling audio stage 424 or components thereof, such as audio processing component 412 or audio amplifier 416. Additionally or alternatively, active mode for zone player 400 might involve disabling a sleep mode for processor 408 or network interface 402. Active mode might also be referred to as the normal operating mode for the first media playback device. In some embodiments, the first media playback device may consume more power in active mode as compared with at least one other device mode, such as standby mode.
d. Broadcasting a Second Wake-Up Packet that Includes a Second Payload that is Associated with a Unicast MAC Address
At block 1308, method 1300 may involve, when the first MAC address is included in the list of MAC addresses, the first media playback device broadcasting a second wake-up packet that includes a second payload that is associated with the MAC address. In some embodiments, broadcasting the second wake-up packet may involve creating a second wake-up packet and transmitting the second wake-up packet on a network interface. For example, the first zone player 400 may create a second wake-up packet 1402 and transmit the second wake-up packet 1402 on network interface 402 using either wireless network interface 404 or wired interface 406. In some embodiments, the second wake-up packet 1402 may include the broadcast address as the destination address in the control information 1404. In other embodiments, the second wake-up packet 1402 may include a unicast destination address as the destination address in the control information 1404. Moreover, the second wake-up packet 1402 may include a second payload 1406 that includes the unicast destination MAC address 1408. In some embodiments, the second payload 1406 may have sixteen repetitions of the unicast destination MAC address 1408. In some embodiments, the payload 1406 may have other data in addition to the repetitions of a MAC address 1408.
As another example, media playback device 1206 in
The method 1300 may be repeated at additional media playback devices within the media playback system until so as to cause additional media playback devices in the system to be woken up. For example, each of media playback devices 1206, 1208, 1210, 1212, and 1214 may receive a wake-up packet, exit standby mode and enter active mode, and broadcast a wake-up packet when the MAC address in the wake-up packet received by each respective media playback device 1206-1214 is included in the list of MAC addresses maintained by the respective media playback device 1206-1214.
Further, in some embodiments, the second payload 1406 included in the second wake-up packet 1402 may be the same payload 1406 as the first payload included in the first wake-up packet 1402. For example, the first zone player 400 may copy the first payload 1406 from the first wake-up packet 1402 to the second wake-up packet 1402. Or, the first zone player 400 may translate the information in the first payload 1406 from the first wake-up packet 1402 to the second payload 1406 in the second wake-up packet 1402.
Further, in some embodiments, the first wake-up packet may have a unicast destination address as its destination address in the control information. For example, first wake-up packet 1402 with control information 1404 that includes a unicast destination address as the destination address. In this embodiment, the unicast destination address is translated from the control information 1404 in the first wake-up packet 1402 to the control information 1404 in the second wake-up packet. The second wake-up packet is sent as a unicast message to the destination media playback device or to the next intermediary device that is acting as a proxy for the destination media playback device.
Further, in some embodiments, additional functions may be carried out in addition to method 1300. These functions may involve the first media playback device remaining in the standby mode when the first MAC address is not included in the list of MAC addresses. In this embodiment, the first MAC address 1408 is not associated with the MAC address of the first media playback or any device that the first media playback device for which the first media playback device may be acting as a proxy.
In some embodiments, as described above, two or more media playback devices may be interconnected in a network to form a media playback system. Moreover, as described above, the first media playback device may carry out the steps of method 1300. For example, referring to
The method 1300 may be repeated at additional media playback devices within the media playback system until all media playback devices in the system are woken up. For example, each of media playback devices 1206, 1208, 1210, 1212, and 1214 may receive a wake-up packet, and determine whether the MAC address in the wake-up packet is within the list of MAC addresses maintained by the respective media playback device. Upon making the determination that the MAC address in the wake-up packet is within the list of MAC addresses, each media playback device 1206, 1208, 1210, 1212, and 1214 may exit standby mode and enter active mode and broadcast a wake-up packet. In some embodiments, when the MAC address in the wake-up packet is within not the list of MAC addresses maintained by the each media playback device, the media playback device remains in the standby mode.
The descriptions above disclose various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. However, such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these firmware, hardware, and/or software components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, while the following describes example systems, methods, apparatus, and/or articles of manufacture, the examples provided are not the only way(s) to implement such systems, methods, apparatus, and/or articles of manufacture.
As indicated above, the present application involves mechanisms to wake-up a media playback device from a standby mode using a network message known as a wake-up packet, wherein the media playback device is interconnected with other media playback devices to form a networked media playback system. In one aspect, a method is provided. The method involves receiving, by a first media playback device, while the first media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a MAC broadcast address. In response to receiving the first wake-up packet, the method further involves exiting, by the first media playback device, the standby mode and entering an active mode, and broadcasting, by the first media playback device a second wake-up packet that includes a second payload that is associated with the MAC broadcast address.
In another aspect, a non-transitory computer readable memory is provided. The non-transitory computer-readable storage medium includes a set of instructions for execution by a processor. The set of instructions, when executed, cause a first media playback device to receive, by a first media playback device, while the first media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a MAC broadcast address. In response to receiving the first wake-up packet, the set of instructions, when executed, further cause the first media playback device to exit, by the first media playback device, the standby mode, and enter an active mode; and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC broadcast address.
In a further aspect, a media playback device is provided. The device includes a network interface, a processor, a data storage, and a program logic stored in the data storage and executable by the processor to receive, by the first media playback device, while the media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a MAC broadcast address. In response to receiving the first wake-up packet, the program logic is further executable by the processor to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC broadcast address.
In yet another aspect, a media playback system is provided. The system includes a first media playback device and a second media playback device. The first media playback device includes a network interface, a processor, a data storage and executable by the processor to receive, by the first media playback device, while the media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a MAC broadcast address. In response to receiving the first wake-up packet, the program logic is further executable by the processor to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC broadcast address.
In another aspect, a method is provided in a local area network comprising a plurality of devices, including at least a first media playback device and a second media playback device. The method includes receiving, by a first media playback device, while the first media playback device is in a standby mode, a first wake-up packet that includes a first payload that is associated with a first MAC address. In response to receiving the first wake-up packet, the method further includes determining, by the first media playback device, whether the first MAC address is included in a list of MAC addresses maintained by the first media playback device. When the first MAC address is included in the list of MAC addresses, the method further includes exiting, by the first media playback device, the standby mode, and entering an active mode, and broadcasting, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the first MAC address.
In a further aspect, a non-transitory computer readable memory is provided. The non-transitory computer-readable storage medium includes a set of instructions for execution by a processor. The set of instructions, when executed, cause a first media playback device to receive, by a first media playback device while the first media playback device is in standby mode, a first wake-up packet that includes a first payload that is associated with a first MAC address. In response to receiving the first wake-up packet, the set of instructions further cause the first media playback device to determine, by the first media playback device, whether the first MAC address is included in a list of MAC addresses maintained by the first media playback device. When the first MAC address is included in the list of MAC addresses, the set of instructions further cause the first media playback device to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the first MAC address.
In yet another aspect, a media playback device is provided. The device includes a network interface, a processor, a data storage, and a program logic stored in the data storage and executable by the processor to receive, by the first media playback device is in standby mode, a first wake-up packet that includes a first payload that is associated with a first MAC address. In response to receiving the first wake-up packet, the program logic is further executable by the processor to determine, by the first media playback device, whether the first MAC address is included in a list of MAC addresses maintained by the first media playback device. When the first MAC address is included in the list of MAC addresses, the program logic is further executable by the processor to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC address.
In a further aspect, a media playback system is provided. The system includes a first media playback device and a second media playback device. The first media playback device includes a network interface, a processor, a data storage and executable by the processor to receive, by the first media playback device is in standby mode, a first wake-up packet that includes a first payload that is associated with a first MAC address. In response to receiving the first wake-up packet, the program logic is further executable by the processor to determine, by the first media playback device, whether the first MAC address is included in a list of MAC addresses maintained by the first media playback device. When the first MAC address is included in the list of MAC addresses, the program logic is further executable by the processor to exit, by the first media playback device, the standby mode and enter an active mode, and broadcast, by the first media playback device, a second wake-up packet that includes a second payload that is associated with the MAC broadcast address.
Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment of the invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.
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 medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.
This application claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. non provisional patent application Ser. No. 14/042,098, filed on Sep. 30, 2013, entitled “Media Playback System Using Standby Mode In A Mesh Network,” which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3956591 | Gates, Jr. | May 1976 | A |
4105974 | Rogers | Aug 1978 | A |
D260764 | Castagna et al. | Sep 1981 | S |
4296278 | Cullison et al. | Oct 1981 | A |
4306114 | Callahan | Dec 1981 | A |
4509211 | Robbins | Apr 1985 | A |
D279779 | Taylor | Jul 1985 | S |
4530091 | Crockett | Jul 1985 | A |
4701629 | Citroen | Oct 1987 | A |
4712105 | Koehler | Dec 1987 | A |
D293671 | Beaumont | Jan 1988 | S |
4731814 | Becker et al. | Mar 1988 | A |
4824059 | Butler | Apr 1989 | A |
D301037 | Matsuda | May 1989 | S |
4845751 | Schwab | Jul 1989 | A |
D304443 | Grinyer et al. | Nov 1989 | S |
D313023 | Kolenda et al. | Dec 1990 | S |
D313398 | Gilchrist | Jan 1991 | S |
D313600 | Weber | Jan 1991 | S |
4994908 | Kuban et al. | Feb 1991 | A |
D320598 | Auerbach et al. | Oct 1991 | S |
D322609 | Patton | Dec 1991 | S |
5086385 | Launey et al. | Feb 1992 | A |
D326450 | Watanabe | May 1992 | S |
D327060 | Wachob et al. | Jun 1992 | S |
5151922 | Weiss | Sep 1992 | A |
D331388 | Dahnert et al. | Dec 1992 | S |
5182552 | Paynting | Jan 1993 | A |
D333135 | Wachob et al. | Feb 1993 | S |
5237327 | Saitoh et al. | Aug 1993 | A |
5255094 | Yong et al. | Oct 1993 | A |
5272757 | Scofield et al. | Dec 1993 | A |
D350531 | Tsuji | Sep 1994 | S |
D350962 | Reardon et al. | Sep 1994 | S |
5361381 | Short | Nov 1994 | A |
5372441 | Louis | Dec 1994 | A |
D354059 | Hendricks | Jan 1995 | S |
D354751 | Hersh et al. | Jan 1995 | S |
D356093 | McCauley et al. | Mar 1995 | S |
D356312 | Althans | Mar 1995 | S |
D357024 | Tokiyama et al. | Apr 1995 | S |
5406634 | Anderson et al. | Apr 1995 | A |
5430485 | Lankford et al. | Jul 1995 | A |
5440644 | Farinelli et al. | Aug 1995 | A |
D362446 | Gasiorek et al. | Sep 1995 | S |
5457448 | Totsuka et al. | Oct 1995 | A |
D363933 | Starck | Nov 1995 | S |
D364877 | Tokiyama et al. | Dec 1995 | S |
D364878 | Green et al. | Dec 1995 | S |
D365102 | Gioscia | Dec 1995 | S |
D366044 | Hara et al. | Jan 1996 | S |
5481251 | Buys et al. | Jan 1996 | A |
5515345 | Barreira et al. | May 1996 | A |
D372716 | Thorne | Aug 1996 | S |
5553314 | Grube et al. | Sep 1996 | A |
D377651 | Biasotti et al. | Jan 1997 | S |
5625350 | Fukatsu et al. | Apr 1997 | A |
D379816 | Laituri et al. | Jun 1997 | S |
5640388 | Woodhead et al. | Jun 1997 | A |
D380752 | Hanson | Jul 1997 | S |
D382271 | Akwiwu | Aug 1997 | S |
5661665 | Glass et al. | Aug 1997 | A |
5668884 | Clair, Jr. et al. | Sep 1997 | A |
5673323 | Schotz et al. | Sep 1997 | A |
D384940 | Kono et al. | Oct 1997 | S |
D387352 | Kaneko et al. | Dec 1997 | S |
D388792 | Nykerk | Jan 1998 | S |
D389143 | Wicks | Jan 1998 | S |
D392641 | Fenner | Mar 1998 | S |
D393628 | Ledbetter et al. | Apr 1998 | S |
5740235 | Lester et al. | Apr 1998 | A |
5742623 | Nuber et al. | Apr 1998 | A |
D394659 | Biasotti et al. | May 1998 | S |
5761320 | Farinelli et al. | Jun 1998 | A |
5774016 | Ketterer | Jun 1998 | A |
D395889 | Gerba et al. | Jul 1998 | S |
5790543 | Cloutier | Aug 1998 | A |
D397996 | Smith | Sep 1998 | S |
5812201 | Yoo | Sep 1998 | A |
5818948 | Gulick | Oct 1998 | A |
5822598 | Lam | Oct 1998 | A |
D401587 | Rudolph | Nov 1998 | S |
5832024 | Schotz et al. | Nov 1998 | A |
5848152 | Slipy et al. | Dec 1998 | A |
5852722 | Hamilton | Dec 1998 | A |
D404741 | Schumaker et al. | Jan 1999 | S |
5857115 | Tanaka | Jan 1999 | A |
D405071 | Gambaro | Feb 1999 | S |
5875233 | Cox | Feb 1999 | A |
D406847 | Gerba et al. | Mar 1999 | S |
D407071 | Keating | Mar 1999 | S |
5900026 | Ryu | May 1999 | A |
5905768 | Maturi et al. | May 1999 | A |
D410927 | Yamagishi | Jun 1999 | S |
D412337 | Hamano | Jul 1999 | S |
5923902 | Inagaki | Jul 1999 | A |
5946343 | Schotz et al. | Aug 1999 | A |
5949776 | Mahany et al. | Sep 1999 | A |
5956025 | Goulden et al. | Sep 1999 | A |
5960006 | Maturi et al. | Sep 1999 | A |
D415496 | Gerba et al. | Oct 1999 | S |
D416021 | Godette et al. | Nov 1999 | S |
5984512 | Jones et al. | Nov 1999 | A |
5987611 | Freund | Nov 1999 | A |
5990884 | Douma et al. | Nov 1999 | A |
5991307 | Komuro et al. | Nov 1999 | A |
5999906 | Mercs et al. | Dec 1999 | A |
6018376 | Nakatani | Jan 2000 | A |
D420006 | Tonino | Feb 2000 | S |
6029196 | Lenz | Feb 2000 | A |
6032202 | Lea et al. | Feb 2000 | A |
6038614 | Chan et al. | Mar 2000 | A |
6046550 | Ference et al. | Apr 2000 | A |
6061457 | Stockhamer | May 2000 | A |
6081266 | Sciammarella | Jun 2000 | A |
6088063 | Shiba | Jul 2000 | A |
D429246 | Holma | Aug 2000 | S |
D430143 | Renk | Aug 2000 | S |
6101195 | Lyons et al. | Aug 2000 | A |
6122749 | Gulick | Sep 2000 | A |
D431552 | Backs et al. | Oct 2000 | S |
D432525 | Beecroft | Oct 2000 | S |
6127941 | Van Ryzin | Oct 2000 | A |
6148205 | Cotton | Nov 2000 | A |
6148345 | Yamaki | Nov 2000 | A |
6154488 | Hunt | Nov 2000 | A |
6157726 | Carroll et al. | Dec 2000 | A |
6169725 | Gibbs et al. | Jan 2001 | B1 |
6181383 | Fox et al. | Jan 2001 | B1 |
6195435 | Kitamura | Feb 2001 | B1 |
6212282 | Mershon | Apr 2001 | B1 |
6246701 | Slattery | Jun 2001 | B1 |
D444475 | Levey et al. | Jul 2001 | S |
6256554 | Dilorenzo | Jul 2001 | B1 |
6269406 | Dutcher et al. | Jul 2001 | B1 |
6295356 | De Nicolo | Sep 2001 | B1 |
6301012 | White et al. | Oct 2001 | B1 |
6310652 | Li et al. | Oct 2001 | B1 |
6311279 | Nguyen | Oct 2001 | B1 |
6313879 | Kubo et al. | Nov 2001 | B1 |
6316992 | Miao et al. | Nov 2001 | B1 |
6317789 | Rakavy et al. | Nov 2001 | B1 |
6321252 | Bhola et al. | Nov 2001 | B1 |
D452520 | Gotham et al. | Dec 2001 | S |
6353172 | Fay et al. | Mar 2002 | B1 |
6356871 | Hemkumar et al. | Mar 2002 | B1 |
6359872 | Mahany et al. | Mar 2002 | B1 |
6366582 | Nishikado et al. | Apr 2002 | B1 |
6388514 | King et al. | May 2002 | B1 |
6404811 | Cvetko et al. | Jun 2002 | B1 |
6418150 | Staats | Jul 2002 | B1 |
6442443 | Fujii et al. | Aug 2002 | B1 |
D462339 | Allen et al. | Sep 2002 | S |
D462340 | Allen et al. | Sep 2002 | S |
D462945 | Skulley | Sep 2002 | S |
6449642 | Bourke-Dunphy et al. | Sep 2002 | B2 |
6456783 | Ando et al. | Sep 2002 | B1 |
6463474 | Fuh et al. | Oct 2002 | B1 |
6466832 | Zuqert et al. | Oct 2002 | B1 |
6469633 | Wachter | Oct 2002 | B1 |
D466108 | Glodava et al. | Nov 2002 | S |
6487296 | Allen et al. | Nov 2002 | B1 |
6493824 | Novoa | Dec 2002 | B1 |
6493832 | Itakura et al. | Dec 2002 | B1 |
D468297 | Ikeda | Jan 2003 | S |
6522886 | Youngs et al. | Feb 2003 | B1 |
6535121 | Matheny et al. | Mar 2003 | B2 |
D474763 | Tozaki et al. | May 2003 | S |
D475993 | Meyer | Jun 2003 | S |
D476643 | Yamagishi | Jul 2003 | S |
D477310 | Moransais | Jul 2003 | S |
6590982 | Chen | Jul 2003 | B1 |
D478051 | Sagawa | Aug 2003 | S |
D478069 | Beck et al. | Aug 2003 | S |
D478896 | Summers | Aug 2003 | S |
6611537 | Edens et al. | Aug 2003 | B1 |
D479520 | De Saulees | Sep 2003 | S |
D481056 | Kawasaki et al. | Oct 2003 | S |
6631410 | Kowalski | Oct 2003 | B1 |
6636269 | Baldwin | Oct 2003 | B1 |
6653899 | Organvidez et al. | Nov 2003 | B2 |
6654720 | Graham et al. | Nov 2003 | B1 |
6654956 | Trinh et al. | Nov 2003 | B1 |
6684060 | Curtin | Jan 2004 | B1 |
D486145 | Kaminski et al. | Feb 2004 | S |
6690431 | Yang et al. | Feb 2004 | B1 |
6704421 | Kitamura | Mar 2004 | B1 |
6741961 | Lim | May 2004 | B2 |
D491925 | Griesau et al. | Jun 2004 | S |
6757517 | Chang | Jun 2004 | B2 |
D493148 | Shibata et al. | Jul 2004 | S |
D495333 | Borsboom | Aug 2004 | S |
6778073 | Lutter et al. | Aug 2004 | B2 |
6778869 | Champion | Aug 2004 | B2 |
D496003 | Spira | Sep 2004 | S |
D496005 | Wang | Sep 2004 | S |
D496335 | Spira | Sep 2004 | S |
D497363 | Olson et al. | Oct 2004 | S |
6804351 | Karam | Oct 2004 | B1 |
D499086 | Polito | Nov 2004 | S |
6816510 | Banerjee | Nov 2004 | B1 |
6826283 | Wheeler et al. | Nov 2004 | B1 |
D499395 | Hsu | Dec 2004 | S |
D499718 | Chen | Dec 2004 | S |
D500015 | Gubbe | Dec 2004 | S |
D501477 | Hall | Feb 2005 | S |
6859460 | Chen | Feb 2005 | B1 |
6859538 | Voltz | Feb 2005 | B1 |
6873862 | Reshefsky | Mar 2005 | B2 |
D504872 | Uehara et al. | May 2005 | S |
D504885 | Zhang et al. | May 2005 | S |
6901439 | Bonasia et al. | May 2005 | B1 |
D506463 | Daniels | Jun 2005 | S |
6915347 | Hanko et al. | Jul 2005 | B2 |
6919771 | Nakajima | Jul 2005 | B2 |
6931557 | Togawa | Aug 2005 | B2 |
6937988 | Hemkumar et al. | Aug 2005 | B1 |
6970940 | Vogel et al. | Nov 2005 | B1 |
6975211 | Atsuta et al. | Dec 2005 | B2 |
6987767 | Saito | Jan 2006 | B2 |
D515072 | Lee | Feb 2006 | S |
D515557 | Okuley | Feb 2006 | S |
D518475 | Yang et al. | Apr 2006 | S |
7046677 | Monta et al. | May 2006 | B2 |
D524296 | Kita | Jul 2006 | S |
D527375 | Flora et al. | Aug 2006 | S |
7092528 | Patrick et al. | Aug 2006 | B2 |
7092694 | Griep et al. | Aug 2006 | B2 |
7096169 | Crutchfield et al. | Aug 2006 | B2 |
7120168 | Zimmermann | Oct 2006 | B2 |
7126945 | Beach | Oct 2006 | B2 |
7130316 | Kovacevic | Oct 2006 | B2 |
7130608 | Hollstrom et al. | Oct 2006 | B2 |
7130616 | Janik | Oct 2006 | B2 |
7136934 | Carter et al. | Nov 2006 | B2 |
7139981 | Mayer et al. | Nov 2006 | B2 |
7143939 | Henzerling | Dec 2006 | B2 |
7146260 | Preston et al. | Dec 2006 | B2 |
7161939 | Israel et al. | Jan 2007 | B2 |
7196584 | Harris | Mar 2007 | B2 |
7197148 | Nourse et al. | Mar 2007 | B2 |
7206618 | Latto et al. | Apr 2007 | B2 |
7236461 | Sonti et al. | Jun 2007 | B1 |
7236773 | Thomas | Jun 2007 | B2 |
7260616 | Cook | Aug 2007 | B1 |
7263110 | Fujishiro | Aug 2007 | B2 |
7277547 | Delker et al. | Oct 2007 | B1 |
7289631 | Ishidoshiro | Oct 2007 | B2 |
7295548 | Blank et al. | Nov 2007 | B2 |
7305694 | Commons et al. | Dec 2007 | B2 |
7308188 | Namatame | Dec 2007 | B2 |
7324857 | Goddard | Jan 2008 | B2 |
7356011 | Waters | Apr 2008 | B1 |
7366206 | Lockridge | Apr 2008 | B2 |
7378903 | Bates et al. | May 2008 | B2 |
7391791 | Balassanian et al. | Jun 2008 | B2 |
7428310 | Park | Sep 2008 | B2 |
7430181 | Hong | Sep 2008 | B1 |
7457948 | Bilicksa et al. | Nov 2008 | B1 |
7472058 | Tseng et al. | Dec 2008 | B2 |
7483538 | McCarty et al. | Jan 2009 | B2 |
7492912 | Chung et al. | Feb 2009 | B2 |
7505889 | Salmonsen et al. | Mar 2009 | B2 |
7548744 | Oesterling et al. | Jun 2009 | B2 |
7548851 | Lau et al. | Jun 2009 | B1 |
7558224 | Surazski et al. | Jul 2009 | B1 |
7558635 | Thiel et al. | Jul 2009 | B1 |
7571014 | Lambourne et al. | Aug 2009 | B1 |
7627825 | Kakuda | Dec 2009 | B2 |
7630501 | Blank et al. | Dec 2009 | B2 |
7643894 | Braithwaite et al. | Jan 2010 | B2 |
7653344 | Feldman et al. | Jan 2010 | B1 |
7657910 | McAulay et al. | Feb 2010 | B1 |
7668925 | Liao et al. | Feb 2010 | B1 |
7672463 | Park et al. | Mar 2010 | B2 |
7675943 | Mosig et al. | Mar 2010 | B2 |
7676044 | Sasaki et al. | Mar 2010 | B2 |
7676142 | Hung | Mar 2010 | B1 |
7688306 | Wehrenberg et al. | Mar 2010 | B2 |
7696816 | Bates | Apr 2010 | B2 |
7710941 | Rietschel et al. | May 2010 | B2 |
7721032 | Bushell et al. | May 2010 | B2 |
7746906 | Jinzaki et al. | Jun 2010 | B2 |
7761176 | Ben-Yaacov et al. | Jul 2010 | B2 |
7831054 | Ball et al. | Nov 2010 | B2 |
7853341 | McCarty et al. | Dec 2010 | B2 |
7881755 | Mishra | Feb 2011 | B1 |
7882234 | Watanabe et al. | Feb 2011 | B2 |
7933418 | Morishima | Apr 2011 | B2 |
7945636 | Nelson et al. | May 2011 | B2 |
7945708 | Ohkita | May 2011 | B2 |
7966388 | Pugaczewski et al. | Jun 2011 | B1 |
7987294 | Bryce et al. | Jul 2011 | B2 |
7995732 | Koch et al. | Aug 2011 | B2 |
8014423 | Thaler et al. | Sep 2011 | B2 |
8024055 | Holmgren et al. | Sep 2011 | B1 |
8041062 | Cohen et al. | Oct 2011 | B2 |
8045952 | Qureshey et al. | Oct 2011 | B2 |
8050203 | Jacobsen et al. | Nov 2011 | B2 |
8103009 | McCarty et al. | Jan 2012 | B2 |
8150079 | Maeda et al. | Apr 2012 | B2 |
8156360 | Paljug | Apr 2012 | B2 |
8170222 | Dunko | May 2012 | B2 |
8189816 | Solow | May 2012 | B2 |
8233029 | Yoshida et al. | Jul 2012 | B2 |
8234395 | Millington et al. | Jul 2012 | B2 |
8311226 | Lorgeoux et al. | Nov 2012 | B2 |
8374595 | Chien et al. | Feb 2013 | B2 |
8411883 | Matsumoto | Apr 2013 | B2 |
8442239 | Bruelle-Drews et al. | May 2013 | B2 |
8477958 | Moeller et al. | Jul 2013 | B2 |
8483853 | Lambourne | Jul 2013 | B1 |
8565455 | Worrell et al. | Oct 2013 | B2 |
8600084 | Garrett | Dec 2013 | B1 |
8654995 | Silber et al. | Feb 2014 | B2 |
8843224 | Holmgren et al. | Sep 2014 | B2 |
8861739 | Ojanpera | Oct 2014 | B2 |
8942252 | Balassanian et al. | Jan 2015 | B2 |
8942395 | Lissaman et al. | Jan 2015 | B2 |
9179197 | Beckhardt et al. | Nov 2015 | B2 |
9246442 | Holmgren et al. | Jan 2016 | B2 |
9252721 | Holmgren et al. | Feb 2016 | B2 |
9319225 | Garg | Apr 2016 | B2 |
20010042107 | Palm | Nov 2001 | A1 |
20010043456 | Atkinson | Nov 2001 | A1 |
20010050991 | Eves | Dec 2001 | A1 |
20020022453 | Balog et al. | Feb 2002 | A1 |
20020026442 | Lipscomb et al. | Feb 2002 | A1 |
20020072816 | Shdema et al. | Jun 2002 | A1 |
20020072817 | Champion | Jun 2002 | A1 |
20020078293 | Kou et al. | Jun 2002 | A1 |
20020083351 | Brabenac | Jun 2002 | A1 |
20020101357 | Gharapetian | Aug 2002 | A1 |
20020101651 | Dugan et al. | Aug 2002 | A1 |
20020124097 | Isely et al. | Sep 2002 | A1 |
20020131761 | Kawasaki et al. | Sep 2002 | A1 |
20020137505 | Eiche et al. | Sep 2002 | A1 |
20020165921 | Sapieyevski | Nov 2002 | A1 |
20030014486 | May | Jan 2003 | A1 |
20030043856 | Lakaniemi et al. | Mar 2003 | A1 |
20030063755 | Nourse et al. | Apr 2003 | A1 |
20030103088 | Dresti et al. | Jun 2003 | A1 |
20030157951 | Hasty | Aug 2003 | A1 |
20030167335 | Alexander | Sep 2003 | A1 |
20030179780 | Walker et al. | Sep 2003 | A1 |
20030185400 | Yoshizawa et al. | Oct 2003 | A1 |
20030198257 | Sullivan et al. | Oct 2003 | A1 |
20030210796 | McCarty et al. | Nov 2003 | A1 |
20030212802 | Rector et al. | Nov 2003 | A1 |
20030219007 | Barrack et al. | Nov 2003 | A1 |
20030231208 | Hanon et al. | Dec 2003 | A1 |
20040001591 | Mani et al. | Jan 2004 | A1 |
20040014426 | Moore | Jan 2004 | A1 |
20040019807 | Freund et al. | Jan 2004 | A1 |
20040024478 | Hans et al. | Feb 2004 | A1 |
20040037433 | Chen | Feb 2004 | A1 |
20040042629 | Mellone et al. | Mar 2004 | A1 |
20040059842 | Hanson et al. | Mar 2004 | A1 |
20040117462 | Bodin et al. | Jun 2004 | A1 |
20040168081 | Ladas et al. | Aug 2004 | A1 |
20040171346 | Lin | Sep 2004 | A1 |
20040177167 | Iwamura et al. | Sep 2004 | A1 |
20040183827 | Putterman et al. | Sep 2004 | A1 |
20040185773 | Gerber et al. | Sep 2004 | A1 |
20040203590 | Shteyn | Oct 2004 | A1 |
20040223622 | Lindemann et al. | Nov 2004 | A1 |
20040249490 | Sakai | Dec 2004 | A1 |
20040253969 | Nguyen et al. | Dec 2004 | A1 |
20050060435 | Xue et al. | Mar 2005 | A1 |
20050131558 | Braithwaite et al. | Jun 2005 | A1 |
20050135304 | Wentink et al. | Jun 2005 | A1 |
20050154766 | Huang et al. | Jul 2005 | A1 |
20050160270 | Goldberg et al. | Jul 2005 | A1 |
20050177256 | Shintani et al. | Aug 2005 | A1 |
20050197725 | Alexander et al. | Sep 2005 | A1 |
20050198219 | Banerjee et al. | Sep 2005 | A1 |
20060072489 | Toyoshima | Apr 2006 | A1 |
20060158168 | Yoshida et al. | Jul 2006 | A1 |
20060173844 | Zhang et al. | Aug 2006 | A1 |
20060209785 | Iovanna et al. | Sep 2006 | A1 |
20060222186 | Paige et al. | Oct 2006 | A1 |
20060227985 | Kawanami | Oct 2006 | A1 |
20060259649 | Hsieh et al. | Nov 2006 | A1 |
20060270395 | Dhawan et al. | Nov 2006 | A1 |
20070087686 | Holm et al. | Apr 2007 | A1 |
20070142944 | Goldberg et al. | Jun 2007 | A1 |
20080075295 | Mayman et al. | Mar 2008 | A1 |
20080089338 | Campbell | Apr 2008 | A1 |
20080170511 | Shorty et al. | Jul 2008 | A1 |
20080205070 | Osada | Aug 2008 | A1 |
20080303947 | Ohnishi et al. | Dec 2008 | A1 |
20090011798 | Yamada | Jan 2009 | A1 |
20090070434 | Himmelstein | Mar 2009 | A1 |
20090122737 | Twitchell, Jr. | May 2009 | A1 |
20090124289 | Nishida | May 2009 | A1 |
20090133040 | Stevens, IV | May 2009 | A1 |
20100087089 | Struthers et al. | Apr 2010 | A1 |
20100171587 | Yoon et al. | Jul 2010 | A1 |
20100216524 | Thomas et al. | Aug 2010 | A1 |
20110001632 | Hohorst | Jan 2011 | A1 |
20110299696 | Holmgren et al. | Dec 2011 | A1 |
20110316768 | McRae | Dec 2011 | A1 |
20120051567 | Castor-Perry | Mar 2012 | A1 |
20120120958 | Mahadevan | May 2012 | A1 |
20120237059 | Saito | Sep 2012 | A1 |
20120320793 | Balbierer et al. | Dec 2012 | A1 |
20130301429 | Peters et al. | Nov 2013 | A1 |
20140146832 | Pohlmann | May 2014 | A1 |
20150365987 | Weel | Dec 2015 | A1 |
Number | Date | Country |
---|---|---|
2320451 | Mar 2001 | CA |
1598767 | Mar 2005 | CN |
1312188 | May 2003 | EP |
1389853 | Feb 2004 | EP |
1517464 | Mar 2005 | EP |
1416687 | Aug 2006 | EP |
1410686 | Mar 2008 | EP |
0742674 | Apr 2014 | EP |
2379533 | Mar 2003 | GB |
63269633 | Nov 1988 | JP |
2000149391 | May 2000 | JP |
439027 | Jun 2001 | TW |
1999023560 | May 1999 | WO |
0019693 | Apr 2000 | WO |
200153994 | Jul 2001 | WO |
2003093950 | Nov 2003 | WO |
2007135581 | Nov 2007 | WO |
2008082350 | Jul 2008 | WO |
2009038687 | Mar 2009 | WO |
Entry |
---|
“884+ Automatic Matrix Mixer Control System,” Ivie Technologies, Inc., 2000, pp. 1-4. |
Advanced Driver Tab User Interface WaveLan GUI Guide, AVAGO0009, Agere Systems, Feb. 2004, 4 pages. |
Agere Systems' Voice-over-Wireless LAN (VoWLAN) Station Quality of Service, AVAGO0015, Agere Systems, Jan. 2005, 5 pages. |
Akyildiz et al., “Multimedia Group Synchronization Protocols for Integrated Services Networks,” IEEE Journal on Selected Areas in Communications, 1996 pp. 162-173, vol. 14, No. 1. |
Audio Authority: How to Install and Use the Model 1154 Signal Sensing Auto Selector, 2002, 4 pages. |
Audio Authority: Model 1154B High Definition AV Auto Selector, 2008, 8 pages. |
AudioSource: AMP 100 User Manual, 2003, 4 pages. |
Automatic Profile Hunting Functional Description, AVAGO0013, Agere Systems, Feb. 2004, 2 pages. |
AXIS Communication: AXIS P8221 Network I/O Audio Module, 2009, 41 pages. |
Balfanz et al., “Network-in-a-Box: How to Set Up a Secure Wireless Network in Under a Minute,” 13th USENIX Security Symposium—Technical Paper, 2002, 23 pages. |
Balfanz et al., “Talking to Strangers: Authentication in Ad-Hoc Wireless Networks,” Xerox Palo Alto Research Center, 2002, 13 pages. |
Barham et al., “Wide Area Audio Synchronisation,” University of Cambridge Computer Laboratory, 1995, 5 pages. |
Bogen Communications, Inc., ProMatrix Digitally Matrixed Amplifier Model PM3180, Copyright 1996, 2 pages. |
Brassil et al., “Enhancing Internet Streaming Media with Cueing Protocols,” 2000, 9 pages. |
Breebaart et al., “Multi-Channel Goes Mobile: MPEG Surround Binaural Rendering,” AES 29th International Conference, Sep. 2-4, 2006, 1-13. |
Cen et al., “A Distributed Real-Time MPEG Video Audio Player,” Department of Computer Science and Engineering. Oregon Graduate Institute of Science and Technology, 1995, 12 pages. |
Change Notification: Agere Systems WaveLan Multimode Reference Design (D2 to D3), AVAGO0042, Agere Systems, Nov. 2004, 2 pages. |
Dannenberg et al., “A. System Supporting Flexible Distributed Real-Time Music Processing,” Proceedings of the 2001 International Computer Music Conference, 2001, 4 pages. |
Dannenberg; Roger B., “Remote Access to Interactive Media,” Proceedings of the SPIE 1785, 1993, 230-237. |
Day, Rebecca, “Going Elan!” Primedia Inc., 2003, 4 pages. |
Deep-Sleep Implementation in WL60011 for IEEE 802.11b Applications, AVAGO0020, Agere Systems, Jul. 2004, 22 pages. |
Denon AV Surround Receiver AVR-1604/684 User's Manual, 2004, 128 pages. |
Denon AV Surround Receiver AVR-5800 Operating Instructions, Copyright 2000, 67 pages. |
Faller, Christof, “Coding of Spatial Audio Compatible with Different Playback Formats,” Audio Engineering Society Convention Paper (Presented at the 117th Convention), Oct. 28-31, 2004, 12 pages. |
Fireball DVD and Music Manager DVDM-100 Installation and User's Guide, Copyright 2003, 185 pages. |
Fireball MP-200 User's Manual, Copyright 2006, 93 pages. |
Fireball Remote Control Guide WD006-1-1, Copyright 2003, 19 pages. |
Fireball SE-D1 User's Manual, Copyright 2005, 90 pages. |
Fober et al., “Clock Skew Compensation over a High Latency Network,” Proceedings of the ICMC, 2002, pp. 548-552. |
Gaston et al., “Methods for Sharing Stereo and Multichannel Recordings Among Planetariums,” Audio Engineering Society Convention Paper 7474, 2008, 15 pages. |
Herre et al., “The Reference Model Architecture for MPEG Spatial Audio Coding,” Audio Engineering Society Convention Paper (Presented at the 118th Convention), May 28-31, 2005, 13 pages. |
IBM Home Director Installation and Service Manual, Copyright 1998, 124 pages. |
IBM Home Director Owner's Manual, Copyright 1999, 67 pages. |
Integra Audio Network Receiver NAC 2.3 Instruction Manual, 68 pages. |
Integra Audio Network Server NAS 2.3 Instruction Manual, pp. 1-32. |
Integra Service Manual, Audio Network Receiver Model NAC-2.3, Dec. 2002, 44 pages. |
Ishibashi et al., “A Comparison of Media Synchronization Quality Among Reactive Control Schemes,” IEEE Infocom, 2001, pp. 77-84. |
Issues with Mixed IEEE 802.b/802.11g Networks, AVAGO0058, Agere Systems, Feb. 2004, 5 pages. |
Lake Processors: Lake® LM Series Digital Audio Processors Operation Manual, 2011, 71 pages. |
“A/V Surround Receiver AVR-5800,” Denon Electronics, 2000, 2 pages. |
“A/V System Controller, Owner's Manual,” B&K Compontents, Ltd., 1998, 52 pages. |
“Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages. |
“DP-0206 Digital Signal Processor,” TOA Electronics, Inc., 2001, pp. 1-12. |
“Home Theater Control Systems,” Cinema Source, 2002, 19 pages. |
“Model MRC44 Four Zone—Four Source Audio/Video Controller/Amplifier System,” Xantech Corporation, 2002, 52 pages. |
“NexSys Software v. 3 Manual,” Crest Audio, Inc., 1997, 76 pages. |
“Residential Distributed Audio Wiring Practices,” Leviton Network Solutions, 2001, 13 pages. |
“RVL-6 Modular Multi-Room Controller, Installation & Operation Guide,” Nile Audio Corporations, 1999, 46 pages. |
“Systemline Modular Installation Guide, Multiroom System,” Systemline, 2003, pp. 1-22. |
“ZR-8630AV MultiZone Audio/Video Receiver, Installation and Operation Guide,” Niles Audio Corporation, 2003, 86 pages. |
Non-Final Office Action dated Sep. 8, 2016, issued in connection with U.S. Appl. No. 14/977,612, filed Dec. 21, 2015, 7 pages. |
Non-Final Office Action dated Sep. 9, 2016, issued in connection with U.S. Appl. No. 14/977,597, filed Dec. 21, 2015, 7 pages. |
AVTransport:1 Service Template Version 1.01 for UPnP, Version 1.0 (Jun. 25, 2002) (66 pages). |
Connection Manager: 1 Service Template Version 1.01 for UPnP, Version 1.0 (Jun. 25, 2002) (25 pages). |
ContentDirectory:1 Service Template Version 1.01 for UPnP, Version 1.0 (Jun. 25, 2002) (89 pages). |
Designing a UPnP AV MediaServer, Nelson Kidd (2003) (SONDM000115062-116) (55 pages). |
General Event Notification Architecture Base: Client to Arbiter (Apr. 2000) (23 pages). |
Home Networking with Universal Plug and Play, IEEE Communications Magazine, vol. 39 No. 12 (Dec. 2001) (D+M_0402025-40) (16 pages). |
Intel Designing a UPnP AV Media Renderer, v. 1.0 (“Intel AV Media Renderer”) (May 20, 2003) (SONDM000115117-62) (46 pages). |
Intel Media Renderer Device Interface (“Intel Media Renderer”) (Sep. 6, 2002) (62 pages). |
Intel SDK for UPnP Devices Programming Guide, Version 1.2.1, (Nov. 2002) (30 pages). |
Linux SDK for UPnP Devices v. 1.2 (Sep. 6, 2002) (101 pages). |
MediaRenderer:1 Device Template Version 1.01 for UPnP, Version 1.0 (Jun. 25, 2002) (12 pages). |
MediaServer:1 Device Template Version 1.01 for UPnP, Version 1.0 (Jun. 25, 2002) (12 pages). |
Microsoft, Universal Plug and Play (UPnP) Client Support (“Microsoft UPnP”) (Aug. 2001) (D+M_0402007-24) (18 pages). |
Microsoft Window's XP Reviewer's Guide (Aug. 2001) (D+M_0402225-85) (61 pages). |
Network Time Protocol (NTP), RFC 1305 (Mar. 1992) (D+M_0397417-536) (120 pages). |
Real Time Control Protocol (RTCP) and Realtime Transfer Protocol (RTP), RFC 1889 (Jan. 1996) (D+M_0397810-84) (75 pages). |
Realtime Streaming Protocol (RTSP), RFC 2326 (Apr. 1998) (D+M_0397945-8036) (92 pages). |
Realtime Transport Protocol (RTP), RFC 3550 (Jul. 2003) (D+M_0398235-323) (89 pages). |
RenderingControl:1 Service Template Version 1.01 for UPnP, Version 1.0, (Jun. 25, 2002) (SONDM000115187-249) (63 pages). |
Simple Network Time Protocol (SNTPI), RFC 1361 (Aug. 1992) (D+M_0397537-46) (10 pages). |
Simple Network Time Protocol (SNTPII), RFC 1769 (Mar. 1995) (D+M_0397663-76) (14 pages). |
Simple Service Discovery Protocol/1.0 Operating without an Arbiter (Oct. 28, 1999) (24 pages). |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 206-1, Transcript of 101 Hearing (Nov. 28, 2016) (28 pages). |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 207, Public Joint Claim Construction Brief (Nov. 30, 2016) (88 pages). |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 214, D&M Post-Markman Letter (Dec. 22, 2016) (13 pages). |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 215, Sonos Post-Markman Letter (Dec. 22, 2016) (15 pages). |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 219, Claim Construction Opinion (Jan. 12, 2017) (24 pages). |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 221, Claim Construction Order (Jan. 18 2017) (2 pages). |
Sonos, Inc. v. D& M Holdings (No. 14-1330-RGA), Markman Hearing Transcript (Dec. 14, 2016) (69 pages). |
Understanding Universal Plug and Play, Microsoft White Paper (Jun. 2000) (D+M_0402074-118) (45 pages). |
Universal Plug and Play Device Architecture V. 1.0, (Jun. 8, 2000) (54 pages). |
Universal Plug and Play in Windows XP, Tom Fout. Microsoft Corporation (Jul. 2001) (D+M_0402041-73) (33 pages). |
Universal Plug and Play (“UPnP”) AV Architecture:1 for UPnP, Version 1.0, (Jun. 25, 2002) (D+M_0298151-72) (22 pages). |
Universal Plug and Play Vendor's Implementation Guide (Jan. 5, 2000) (7 pages). |
UPnP AV Architecture:0.83 (Jun. 12, 2002) (SONDM000115483-504) (22 pages). |
UPnP Design by Example, A Software Developers Guide to Universal Plug and Play Michael Jeronimo and JackWeast, Intel Press (D+M_0401307-818) (Apr. 2003) (511 pages). |
WANCommonInterfaceConfig:1 Service Template Version 1.01 for UPnP, Ver. 1.0 (Nov. 12, 2001) (D+M_0401820-43) (24 pages). |
WANIPConnection:1 Service Template Version 1.01 for UPnP Ver. 1 .0 (Nov. 12, 2001) (D+M_0401844-917) (74 pages). |
WANPPPConnection:1 Service Template Version 1.01 for UPnP, Version 1.0 (Nov. 12, 2001) (D+M_0401918-2006) (89 pages). |
Windows Media Connect Device Compatibility Specification (Apr. 12, 2004) (16 pages). |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 226, Opinion Denying Inequitable Conduct Defenses, Feb. 6, 2017, 5 pages. |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 227, Order Denying Inequitable Conduct Defenses, Feb. 6, 2017, 1 page. |
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, 2003, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages. |
Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages. |
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages. |
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 1: Defendants' Invalidity Contentions for U.S. Pat. No. 7,571,014 filed Sep. 16, 2016, 270 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 10: Defendants' Invalidity Contentions for U.S. Pat. No. 9,219,959 filed Sep. 27, 2016, 236 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 11: Defendants' Invalidity Contentions for Design U.S. Pat. No. D. 559,197 filed Sep. 27, 2016, 52 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 2: Defendants' Invalidity Contentions for U.S. Pat. No. 8,588,949 filed Sep. 27, 2016, 224 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 3: Defendants' Invalidity Contentions for U.S. Pat. No. 8,843,224 filed Sep. 27, 2016, 147 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 4: Defendants' Invalidity Contentions for U.S. Pat. No. 8,938,312 filed Sep. 27, 2016, 229 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 5: Defendants' Invalidity Contentions for U.S. Pat. No. 8,938,637 filed Sep. 27, 2016, 213 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 6: Defendants' Invalidity Contentions for U.S. Pat. No. 9,042,556 filed Sep. 27, 2016, 162 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 7: Defendants' Invalidity Contentions for U.S. Pat. No. 9,195,258 filed Sep. 27, 2016, 418 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 8: Defendants' Invalidity Contentions for U.S. Pat. No. 9,202,509 filed Sep. 27, 2016, 331 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 9: Defendants' Invalidity Contentions for U.S. Pat. No. 9,213,357 filed Sep. 27, 2016, 251 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Brief in Support of their Motion for Leave to Amend their Answer to Add the Defense of Inequitable Conduct, provided Oct. 12, 2016, 24 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Opposition to Sonos's Motion to Strike Defendants' New Amended Answer Submitted with their Reply, provided Oct. 3, 2016, 15 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit A: Defendants' First Amended Answer to Plaintiffs' Third Amended Complaint, provided Aug. 1, 2016, 26 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit A: Defendants' Second Amended Answer to Plaintiffs' Third Amended Complaint, provided Oct. 12, 2016, 43 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit A: Defendants' Second Amended Answer to Plaintiffs' Third Amended Complaint, provided Sep. 9, 2016, 88 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit B: Defendants' Second Amended Answer to Plaintiffs' Third Amended Complaint, provided Oct. 12, 2016, 43 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Opening Brief in Support of Defendants' Motion for Leave to Amend Their Answer to Add the Defense of Inequitable Conduct, provided Aug. 1, 2016, 11 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Order, provided Oct. 7, 2016, 2 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Plaintiff's Opposition to Defendants' Motion for Leave to Amend Their Answer to Add the Defense of Inequitable Conduct, provided Aug. 26, 2016, 25 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Redlined Exhibit B: Defendants' First Amended Answer to Plaintiffs' Third Amended Complaint, provided Aug. 1, 2016, 27 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Reply Brief in Support of Defendants' Motion for Leave to Amend their Answer to Add the Defense of Inequitable Conduct, provided Nov. 10, 2016, 16 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Reply Brief in Support of Defendants' Motion for Leave to Amend their Answer to Add the Defense of Inequitable Conduct, provided Sep. 9, 2016, 16 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Sonos's Motion to Strike Defendants' New Amended Answer Submitted with their Reply Brief, provided Sep. 15, 2016, 10 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Sonos's Opposition to Defendants' Motion for Leave to Amend their Answer to Add the Defense of Inequitable Conduct, provided Oct. 31, 2016, 26 pages. |
Corrected Notice of Allowability dated Jan. 6, 2016, issued in connection with U.S. Appl. No. 14/465,417, filed Aug. 21, 2014, 3 pages. |
Corrected Notice of Allowability dated Dec. 22, 2015, issued in connection with U.S. Appl. No. 14/486,648, filed Sep. 15, 2014, 3 pages. |
Notice of Allowance dated Dec. 7, 2015, issued in connection with U.S. Appl. No. 14/465,417, filed Aug. 21, 2014, 6 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Opening Brief in Support of Defendants' Partial Motion for Judgment on the Pleadings for Lack of Patent-Eligible Subject Matter, filed May 6, 2016, 27 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Plaintiff Sonos, Inc.'s Opening Claim Construction Brief, filed Sep. 9, 2016, 26 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Plaintiff Sonos, Inc.'s Response in Opposition to Defendants' Partial Motion for Judgment on the Pleadings, filed May 27, 2016, 24 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Second Amended Complaint for Patent Infringement, filed Feb. 27, 2015, 19 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Third Amended Complaint for Patent Infringement, filed Jan. 29, 2016, 47 pages. |
Sony: AIR-SA 50R Wireless Speaker, Copyright 2009, 2 pages. |
Sony: Altus Quick Setup Guide ALT-SA32PC, Copyright 2009, 2 pages. |
Sony: BD/DVD Home Theatre System Operating Instructions for BDV-E300, E301 and E801, Copyright 2009, 115 pages. |
Sony: BD/DVD Home Theatre System Operating Instructions for BDV-IT1000/BDV-IS1000, Copyright 2008, 159 pages. |
Sony: Blu-ray Disc/DVD Home Theatre System Operating Instructions for BDV-IZ1000W, Copyright 2010, 88 pages. |
Sony: DVD Home Theatre System Operating Instructions for DAV-DZ380W/DZ680W/DZ880W, Copyright 2009, 136 pages. |
Sony: DVD Home Theatre System Operating Instructions for DAV-DZ870W, Copyright 2008, 128 pages. |
Sony Ericsson MS500 User Guide, Copyright 2009, 2 pages. |
Sony: Home Theatre System Operating Instructions for HT-IS100, Copyright 2008, 168 pages. |
Sony: HT-IS100, 5.1 Channel Audio System, last updated Nov. 2009, 2 pages. |
Sony: Multi Channel AV Receiver Operating Instructions, 2007, 80 pages. |
Sony: Multi Channel AV Receiver Operating Instructions for STR-DN1000, Copyright 2009, 136 pages. |
Sony: STR-DN1000, Audio Video Receiver, last updated Aug. 2009, 2 pages. |
Sony: Wireless Surround Kit Operating Instructions for WHAT-SA2, Copyright 2010, 56 pages. |
Taylor, Marilou, “Long Island Sound,” Audio Video Interiors, Apr. 2000, 8 pages. |
TOA Corporation, Digital Processor DP-0206 DACsys2000 Version 2.00 Software Instruction Manual, Copyright 2001,67 pages. |
NaveLan High-Speed Multimode Chip Set, AVAGO0003, Agere Systems, Feb. 2003, 4 pages. |
WaveLan High-Speed Multimode Chip Set, AVAGO0005, Agere Systems, Feb. 2003, 4 pages. |
WaveLAN Wireless Integration Developer Kit (WI-DK) for Access Point Developers, AVAGO0054, Agere Systems, Jul. 2003, 2 pages. |
WaveLAN Wireless Integration-Developer Kit (WI-DK) Hardware Control Function (HCF), AVAGO0052, Agere Systems, Jul. 2003, 2 pages. |
WI-DK Release 2 WaveLan Embedded Drivers for VxWorks and Linux, AVAGO0056, Agere Systems, Jul. 2003, 2 pages. |
WI-DK Release 2 WaveLan END Reference Driver for VxWorks, AVAGO0044, Agere Systems, Jul. 2003, 2 pages. |
WI-DK Release 2 WaveLan LKM Reference Drivers for Linux, AVAGO0048, Agere Systems, Jul. 2003, 4 pages. |
WPA Reauthentication Rates, AVAGO0063, Agere Systems, Feb. 2004, 3 pages. |
“AudioTron Quick Start Guide, Version 1.0”, Voyetra Turtle Beach, Inc., Mar. 2001, 24 pages. |
“AudioTron Reference Manual, Version 3.0”, Voyetra Turtle Beach, Inc., May 2002, 70 pages. |
“AudioTron Setup Guide, Version 3.0”, Voyetra Turtle Beach, Inc., 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. |
Levi et al., “Request for Comments 4318, Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol”, Dec. 2005, 14 pages. |
Dell, Inc. “Dell Digital Audio Receiver: Reference Guide” Jun. 2000, 70 pages. |
Dell, Inc. “Start Here” Jun. 2000, 2 pages. |
Decker et al., “RFC 1493, Definitions of Managed Objects for Bridges”, Network Working Group, Jul. 1993, 35 pages. |
Final Office Action dated Feb. 4, 2011, issued in connection with U.S. Appl. No. 10/845,805, filed May 15, 2004, 18 pages. |
Final Office Action dated Sep. 5, 2008, issued in connection with U.S. Appl. No. 10/845,805, filed May 15, 2004, 17 pages. |
Final Office Action dated Nov. 15, 2007, issued in connection with U.S. Appl. No. 10/845,805, filed May 15, 2004, 15 pages. |
Final Office Action dated Jan. 29, 2014, issued in connection with U.S. Appl. No. 13/212,889, filed Aug. 18, 2011, 13 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 retrieved Jun. 18, 2014, 2 pages. |
Kim et al., “Optimal Anycast Technique for Delay-Sensitive Energy-Constrained Asynchronous Sensor Networks,” Apr. 2011, 23 pages. |
LG Musicflow, http://www.lg.com/uk/musicflow/av/MusicFlow_faq#a4, “LG Hi-Fi Audio”, Sep. 20, 2015, 22 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 dated Jul. 17, 2015, issued in connection with U.S. Appl. No. 14/465,417, filed Aug. 21, 2014, 13 pages. |
Non-Final Office Action dated Apr. 9, 2008, issued in connection with U.S. Appl. No. 10/845,805, filed May 15, 2004, 16 pages. |
Non-Final Office Action dated Jul. 16, 2011, issued in connection with U.S. Appl. No. 13/212,889, filed Aug. 18, 2011, 11 pages. |
Non-Final Office Action dated Aug. 17, 2010, issued in connection with U.S. Appl. No. 10/845,805, filed May 15, 2004, 19 pages. |
Non-Final Office Action dated Jul. 17, 2015, issued in connection with U.S. Appl. No. 14/486,648, filed Sep. 15, 2014, 12 pages. |
Non-Final Office Action dated Jun. 22, 2007,issued in connection with U.S. Appl. No. 10/845,805, filed May 15, 2004, 16 pages. |
Notice of Allowance dated Dec. 2, 2015, issued in connection with U.S. Appl. No. 14/486,648, filed Sep. 15, 2014, 6 pages. |
Notice of Allowance dated Oct. 21, 2015, issued in connection with U.S. Appl. No. 14/042,098, filed Sep. 30, 2013, 17 pages. |
Notice of Allowance dated May 23, 2014, issued in connection with U.S. Appl. No. 13/212,889, filed Aug. 18, 2011, 14 pages. |
Notice of Allowance dated May 26, 2011, issued in connection with U.S. Appl. No. 10/845,805, filed May 15, 2004, 14 pages. |
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages. |
Presentations at WinHEC 2000, May 2000, 138 pages. |
UPnP; “Universal Plug and Play Device Architecture”; Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54. |
ZX135: Installation Manual, LA Audio, Apr. 2003, 44 pages. |
LG: RJP-201M Remote Jack Pack Installation and Setup Guide, 2010, 24 pages. |
Lienhart et al., “On the Importance of Exact Synchronization for Distributed Audio Signal Processing,” Session L: Poster Session II—ICASSP'03 Papers, 2002, 1 page. |
LinkSys by Cisco, Wireless Home Audio Controller, Wireless-N Touchscreen Remote DMRW1000 Datasheet, Copyright 2008, 2 pages. |
LinkSys by Cisco, Wireless Home Audio Controller, Wireless-N Touchscreen Remote DMRW1000 User Guide, Copyright 2008, 64 pages. |
LinkSys by Cisco, Wireless Home Audio Player, Wireless-N Music Extender DMP100 Quick Installation Guide, Copyright 2009, 32 pages. |
LinkSys by Cisco, Wireless Home Audio Player, Wireless-N Music Extender DMP100 User Guide, Copyright 2008, 65 pages. |
Liu et al., “A synchronization control scheme for real-time streaming multimedia applications,” Packet Video. 2003, 10 pages, vol. 2003. |
Liu et al., “Adaptive Delay Concealment for Internet Voice Applications with Packet-Based Time-Scale Modification.” Information Technologies 2000, pp. 91-102. |
Parasound Zpre2 Zone Preamplifier with PTZI Remote Control, 2005, 16 pages. |
Pillai et al., “A Method to Improve the Robustness of MPEG Video Applications over Wireless Networks,” Kent Ridge Digital Labs, 2000, 15 pages. |
Proficient Audio Systems M6 Quick Start Guide, 2011, 5 pages. |
Proficient Audio Systems: Proficient Editor Advanced Programming Guide, 2007, 40 pages. |
Programming Interface for WL54040 Dual-Band Wireless Transceiver, AVAGO0066, Agere Systems, May 2004, 16 pages. |
Radio Shack, “Auto-Sensing 4-Way Audio/Video Selector Switch,” 2004, 1 page. |
RadioShack, Pro-2053 Scanner, 2002 Catalog, part 1, 100 pages. |
RadioShack, Pro-2053 Scanner, 2002 Catalog, part 2, 100 pages. |
RadioShack, Pro-2053 Scanner, 2002 Catalog, part 3, 100 pages. |
RadioShack, Pro-2053 Scanner, 2002 Catalog, part 4, 100 pages. |
RadioShack, Pro-2053 Scanner, 2002 Catalog, part 5, 46 pages. |
Rangan et al., “Feedback Techniques for Continuity and Synchronization in Multimedia Information Retrieval,” ACM Transactions on Information Systems, 1995, pp. 145-176, vol. 13, No. 2. |
Reid, Mark, “Multimedia conferencing over ISDN and IP networks using ITU-T H-series recommendations: architecture, control and coordination,” Computer Networks, 1999, pp. 225-235, vol. 31. |
Rothermel et al., “An Adaptive Protocol for Synchronizing Media Streams,” Institute of Parallel and Distributed High-Performance Systems (IPVR), 1997, 26 pages. |
Rothermel et al., “An Adaptive Stream Synchronization Protocol,” 5th International Workshop on Network and Operating System Support for Digital Audio and Video, Apr. 18-21, 1995, 12 pages. |
Rothermel et al., “Synchronization in Joint-Viewing Environments,” University of Stuttgart Institute of Parallel and Distributed High-Performance Systems, 1992, 13 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Complaint for Patent Infringement, filed Oct. 21, 2014, 20 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Declaration of Steven C. Visser, executed Sep. 9, 2016, 40 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions, filed Sep. 14, 2016, 100 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 1: Defendants' Invalidity Contentions for U.S. Pat. No. 7,571,014 filed Apr. 15, 2016, 161 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 10: Defendants' Invalidity Contentions for U.S. Pat. No. 9,213,357 filed Apr. 15, 2016, 244 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 11: Defendants' Invalidity Contentions for U.S. Pat. No. 9,219,959 filed Apr. 15, 2016, 172 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 12: Defendants' Invalidity Contentions for Design U.S. Pat. No. D. 559,197 filed Apr. 15, 2016, 36 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 2: Defendants' Invalidity Contentions for U.S. Pat. No. 8,588,949 filed Apr. 15, 2016, 112 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 3: Defendants' Invalidity Contentions for U.S. Pat. No. 8,843,224 filed Apr. 15, 2016, 118 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 4: Defendants' Invalidity Contentions for U.S. Pat. No. 8,938,312 filed Apr. 15, 2016, 217 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 5: Defendants' Invalidity Contentions for U.S. Pat. No. 8,938,637 filed Apr. 15, 2016, 177 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 6: Defendants' Invalidity Contentions for U.S. Pat. No. 9,042,556 filed Apr. 15, 2016, 86 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 7: Defendants' Invalidity Contentions for U.S. Pat. No. 9,130,771 filed Apr. 15, 2016, 203 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 8: Defendants' Invalidity Contentions for U.S. Pat. No. 9,195,258 filed Apr. 15, 2016, 400 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 9: Defendants' Invalidity Contentions for U.S. Pat. No. 9,202,509 filed Apr. 15, 2016, 163 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions, filed Apr. 15, 2016, 97 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Preliminary Identification of Indefinite Terms, provided Jul. 29, 2016, 8 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Preliminary Identification of Prior Art References, provided Jul. 29, 2016, 5 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Amended Answer, Defenses, and Counterclaims for Patent Infringement, filed Nov. 30, 2015, 47 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Answer to Plaintiff's Second Amended Complaint, filed Apr. 30, 2015, 19 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' First Amended Answer to Plaintiffs' Third Amended Complaint, filed Sep. 7, 2016, 23 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Reply in Support of Partial Motion for Judgment on the Pleadings, filed Jun. 10, 2016, 15 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit A: Defendants' Second Amended Answer to Plaintiffs' Third Amended Complaint, filed Sep. 9, 2016, 43 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., First Amended Complaint for Patent Infringement, filed Dec. 17, 2014, 26 pages. |
Sonos, Inc. v. D&M Holdings Inc. et al., Joint Claim Construction Chart, vol. 1 of 3 with Exhibits A-O, filed Aug. 17, 2016, 30 pages. |
Non-Final Office Action dated Feb. 8, 2017, issued in connection with U.S. Appl. No. 15/245,501, filed Aug. 24, 2016, 12 pages. |
Non-Final Office Action dated Feb. 8, 2017, issued in connection with U.S. Appl. No. 15/245,591, filed Aug. 24, 2016, 12 pages. |
Non-Final Office Action dated Feb. 10, 2017, issued in connection with U.S. Appl. No. 14/977,612, filed Dec. 21, 2015, 15 pages. |
Non-Final Office Action dated Feb. 24, 2017, issued in connection with U.S. Appl. No. 14/977,597, filed Dec. 21, 2015, 14 pages. |
Sonos, Inc. v D&M Holdings, D&M Supp Opposition Brief including Exhibits, Mar. 17, 2017, 23 pages. |
Sonos, Inc. v. D&M Holdings, Expert Report of Jay P. Kesan including Appendices A-P, Feb. 20, 2017, 776 pages. |
Sonos, Inc. v. D&M Holdings, (No. 14-1330-RGA), Defendants' Final Invalidity Contentions (Jan. 18, 2017) (106 pages). |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 226, Opinion Denying Inequitable Conduct Defenses, Feb. 6, 2017, updated, 5 pages. |
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 242, US District Judge Andrews 101 Opinion, Mar. 13, 2017, 16 pages. |
Sonos, Inc. v D&M Holdings, Sonos Supp Opening Markman Brief including Exhibits, Mar. 3, 2017, 17 pages. |
Sonos, Inc. v. D&M Holdings, Sonos Supp Reply Markman Brief including Exhibits, Mar. 29, 2017, 36 pages. |
Number | Date | Country | |
---|---|---|---|
20160077791 A1 | Mar 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14042098 | Sep 2013 | US |
Child | 14950233 | US |