WO2025208089A1 - Multi-instance architecture for multi-player playback device - Google Patents

Multi-instance architecture for multi-player playback device

Info

Publication number
WO2025208089A1
WO2025208089A1 PCT/US2025/022134 US2025022134W WO2025208089A1 WO 2025208089 A1 WO2025208089 A1 WO 2025208089A1 US 2025022134 W US2025022134 W US 2025022134W WO 2025208089 A1 WO2025208089 A1 WO 2025208089A1
Authority
WO
WIPO (PCT)
Prior art keywords
player
logical
playback
playback device
audio
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2025/022134
Other languages
French (fr)
Inventor
Steve Beckhardt
Luis R. Vega Zayas
Ted Lin
Edwin Fitzpatrick
James M. DOLAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sonos Inc
Original Assignee
Sonos Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sonos Inc filed Critical Sonos Inc
Publication of WO2025208089A1 publication Critical patent/WO2025208089A1/en
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/64—Addressing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/2814—Exchanging control software or macros for controlling appliance services in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/43615—Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/81—Monomedia components thereof
    • H04N21/8106—Monomedia components thereof involving special audio data, e.g. different tracks for different languages

Definitions

  • the present disclosure is related to consumer goods and, in some more particular examples, to methods, systems, products, features, services, and other elements relating to media playback systems, media playback devices, methods of operating media playback systems and devices, and various features and aspects thereof.
  • Figure 1 A shows a partial cutaway view of an environment having a media playback system configured in accordance with aspects of the disclosed technology.
  • Figure IB shows a schematic diagram of the media playback system of Figure 1 A and one or more networks.
  • Figure 1C shows a block diagram of a playback device.
  • Figure ID shows a block diagram of a playback device.
  • Figure IE shows a block diagram of a network microphone device.
  • Figure IF shows a block diagram of a network microphone device.
  • Figure 1G shows a block diagram of a playback device.
  • Figure 1H shows a partially schematic diagram of a control device.
  • Figures 1-1 through IL show schematic diagrams of corresponding media playback system zones.
  • Figure 2A shows a front isometric view of a playback device configured in accordance with aspects of the disclosed technology.
  • Figure 2B shows a front isometric view of the playback device of Figure 3 A without a grille.
  • Figure 2C shows an exploded view of the playback device of Figure 2A.
  • Figure 3 A shows a front view of a network microphone device configured in accordance with aspects of the disclosed technology.
  • Figure 3B shows a side isometric view of the network microphone device of Figure 3A.
  • Figure 3C shows an exploded view of the network microphone device of Figures 3A and 3B.
  • Figure 3F shows a schematic diagram of an example voice input.
  • the player-specific media transport components enable the Multi-Player Playback Device to execute media transport commands (e.g., play, pause, stop, skip, fast-forward, rewind, and so on) for the first logical player independently of media transport commands for the second logical player, and vice versa.
  • media transport commands executed for the first logical player do not affect or otherwise change media transport activities of the second logical player
  • media transport commands executed for the second logical player do not affect or otherwise change media transport activities of the first logical player.
  • a playback device may be (or may include) a set of headphones.
  • a playback device may be (or may include) a smartphone, tablet computer, laptop / desktop computer, smart television, or other type of device configurable to play audio content.
  • a playback device comprises one or more microphones configured to receive voice commands.
  • playback devices with microphones are referred to herein as Networked Microphone Devices (NMDs).
  • NMDs Networked Microphone Devices
  • the NMD is configured to perform any (or all) of the playback device functions disclosed herein.
  • a logical player as used herein sometimes refers to a logical playback entity implemented by one or more physical playback devices (e.g., one or more Multi-Player Playback Devices) to act as a single entity to play one stream of audio.
  • the one stream of audio comprises multichannel audio having two or more channels and the physical playback device includes two or more channel outputs
  • playing the multichannel audio includes the physical playback device playing the two or more channels via two or more corresponding channel outputs.
  • playing the multichannel audio includes the physical playback device playing one or more (but not all) channels via one or more corresponding channel outputs and one or more additional players playing the one or more additional channels via one or more corresponding outputs.
  • a single physical playback device implements a single logical player.
  • several physical playback devices may be configured to implement a single logical player.
  • one physical playback device i.e., a Multi-Player Playback Device
  • three or more logical players implemented by one or more Multi-Player Playback Devices can be configured to play different channels of a single multichannel audio stream (e.g., home theater audio), where a first logical player plays a center channel, a second logical player plays a right front channel, a third logical player plays a left front channel, a fourth logical player plays a subwoofer channel, and so on.
  • a single multichannel audio stream e.g., home theater audio
  • a single logical player may be configured to play both channels of a stereo audio stream (perhaps via the same Multi-Player Playback Device or two different Multi-Player Playback Devices), or a single logical player may be configured to play all channels of a home theater audio stream (perhaps via the same Multi-Player Playback Device or via two or more Multi-Player Playback Devices).
  • a logical player may mix down a multi-channel audio stream for playback via one or more Multi-Player Playback Devices, e.g., by mixing down a 2-channel stereo stream into a 1- channel mono stream for playback via one or more audio outputs of one or more Multi-Player Playback Devices, or by mixing down a 5-channel home theater stream into a 2-channel stereo stream or a 1 -channel mono stream for playback via one or more outputs of one or more Multi-Player Playback Devices.
  • a Multi-Player Playback Device refers to a type of physical playback device comprising multiple configurable audio outputs, one or more processors, and tangible, non-transitory computer readable media storing program instructions that are executed by the one or more processors to cause the Multi-Player Playback Device to perform the Multi-Player Playback Device features and functions described herein.
  • the Multi-Player Playback Device may sometimes be referred to as a Multi-Zone Player.
  • the multiple audio outputs can be grouped together in different combinations to implement one or more logical players and play audio via one or more audio outputs.
  • a single Multi-Player Playback Device is configurable to implement from one to eight (or more) logical players.
  • Multi-Player Playback Devices may be configurable to implement fewer than eight logical players or more than eight logical players.
  • a Multi- Player Playback Device may be configurable to implement anywhere from one, two to six, eight, twelve, sixteen, eighteen, twenty four, or more logical players.
  • Multi-Player Playback Devices configurable to implement more or fewer logical players than those specifically identified herein are possible as well
  • Multi-Player Playback Devices include eight configurable audio outputs.
  • Multi-Player Playback Devices according to other embodiments include fewer than eight configurable audio outputs or more than eight configurable audio outputs.
  • a Multi-Player Playback Device may include anywhere from two to six, eight, twelve, sixteen, eighteen, twenty four, or more configurable audio outputs. Multi-Player Playback Devices with more or fewer audio outputs than those specifically identified herein are possible as well.
  • a playback entity as used herein sometimes refers to a logical or physical entity configured to play audio.
  • Playback entities include physical playback devices, physical Multi-Player Playback Devices, and logical players that are implemented via one or more Multi-Player Playback Devices.
  • a zone (sometimes referred to herein as a playback zone or a bonded zone) as used herein sometimes refers to a logical container of one or more physical playback devices that are managed together. But in some instances, and in some of the examples described herein, a zone may include only a single, physical playback device.
  • a zone may include any one or more playback devices managed as a logical zone entity, including, for example, (i) a single playback device managed as a logical zone entity, (ii) a group of playback devices managed as a logical zone entity, including but not limited to any of (a) a bonded zone that includes two or more playback devices configured to play the same audio, (b) a bonded pair of two playback devices configured to play the same audio, (c) a stereo pair of two playback devices where one of the playback devices is configured to play a left channel of stereo audio content and the other playback device is configured to play a right channel of stereo audio content, or (d) a home theater zone that includes two or more playback devices configured to play home theater and/or surround sound audio content.
  • a zone is a type of logical entity implemented by one or more playback devices.
  • the two or more playback devices play one stream of audio content.
  • the one stream of audio content played by the zone comprises multichannel audio.
  • each playback device (of the two or more physical playback devices) may be configured to play a different channel of the multichannel audio content.
  • a first physical playback device in the zone may be configured to play a left channel of the audio content and a second physical playback device in the zone may be configured to play a right channel of the audio content.
  • This type of example zone configuration is sometimes referred to as a stereo pair.
  • a first playback device in the zone may play a left channel
  • a second playback device in the zone may play a right channel
  • a third playback device in the zone may play a subwoofer channel.
  • This type of example zone configuration is sometimes referred to as a home theater zone.
  • each of the individual playback devices within the zone communicate with each other in a fully-connected control plane configuration to exchange commands, configuration information, events, and state information to each other via dedicated websocket connections between each pair of playback devices within the zone.
  • each of the individual playback devices within a playback group communicate with each other in a fully-connected configuration to exchange commands, configuration information, events, and state information with each other via dedicated websocket connections (or similar communication links / sessions) between each of the playback devices within the playback group.
  • a playback entity may also perform one or more functions of a controller.
  • a playback entity may be considered a controller device in scenarios where the playback entity performs one or more controller functions.
  • the Area Zone Primary creates the C&C group for the Area Zone (or joins the C&C group as a publisher), and provides information required to join and/or subscribe to the C&C group to each Area Zone Secondary.
  • the Area Zone Secondaries join and/or subscribe to the C&C group to receive control information.
  • the Area Zone Primary publishes commands, configuration information, events, and state information to the C&C group, and each Area Zone Secondary subscribed to the C&C group receives the commands, configuration information, events, and state information that the Area Zone Primary publishes to the C&C group.
  • Area Zone Secondaries may also publish certain command, configuration, event, and state information to the Area Zone C&C group. In operation, each when an Area Zone Secondary receives a command via the C&C group that requires some action on behalf of the Area Zone Secondary, the Area Zone Secondary executes the received command.
  • the Area Zone Primary publishes the audio content, playback timing, and clock timing to the M&T group
  • each Area Zone Secondary subscribed to the M&T group receives the audio content, playback timing, and clock timing that the Area Zone Primary publishes to the M&T group.
  • Area Zone configurations include storing the Area Zone configuration information in a single Area Zone configuration package.
  • the Area Zone configuration package includes separate Area Zone configuration files for each playback entity in the Area Zone.
  • the Area Zone configuration package is stored at one or more of (i) the Area Zone Primary, (ii) a controller device, and/or (iii) a cloud server system.
  • the Area Zone configuration information in some embodiments includes information about the Area Zone configuration, including but not limited to one or more (or all) of (i) a name that identifies the Area Zone, (ii) the name of the playback entity that is to function as the Area Zone Primary once the Area Zone is activated, (iii) the name of each playback entity in the Area Zone (i.e., the UUID of each playback device, the UUID of each Multi-Player Playback Device, the ULPI of each logical player, the zone name of each zone, and group name of each playback group in the Area Zone, as applicable), (iv) playback calibration settings for each playback entity in the Area Zone, (v) for Area Zones configured to play multichannel audio, a channel map that defines the channel or channels that each playback entity is configured to play once the Area Zone has been activated, including at least in some instances, which channel each output port of each playback entity is configured to play while the Area Zone is active, and (vi) for individual playback entities, one or
  • Examples of Area Zone specific behavior while the Area Zone is active include: (i) behavior of the playback entity in response to receiving a volume control command, a playback control command (e.g., play/pause/skip/etc.), and/or other user command via a physical interface on (or associated with) the playback entity, and (ii) behavior of the playback entity in response to receiving a voice command via an associated microphone.
  • U.S. App. 13/910,608 titled “Satellite Volume Control,” referred to as Docket No. 13-0413, filed on June. 5, 2013, and issued on Sep. 6, 2016, as U.S. Pat. 9,438, 193.
  • U.S. App. 13/910,608 discloses, inter alia, controlling playback volume of grouped playback devices, including propagating a volume adjustment received via a first playback device to other playback devices that have been grouped with the first playback device.
  • 13/910,608 does not describe does not describe the Area Zone configurations, Multi-Player Playback Devices, playback entity implementations, logical players, and/or the “multi-instance” software architecture described herein.
  • the entire contents of U.S. App. 13/910,608 are incorporated herein by reference.
  • U.S. App. 13/083,499 titled “Multi-Channel Pairing In A Media System,” referred to as Docket No. 11-0401, filed on Apr. 8, 2011, and issued on Jul. 22, 2014, as U.S. Pat. 8,788,080, describes, inter alia, configuring and operating multiple playback devices in a consolidated mode, where two or more playback devices can be grouped into a consolidated playback device which can then be further grouped with one or more other playback devices and/or one or more other consolidated playback devices.
  • U.S. App. 13/632,731 titled, “Providing A Multi-Channel And A Multi-Zone Audio Environment,” referred to as Docket No. 12-0802, filed on Oct. 1, 2012, and issued on Dec. 6, 2016, as U.S. Pat. 9,516,440, describes, inter alia, configuring playback devices to play different types of audio content (e.g., home theater audio vs. music) according to different playback timing arrangements (e.g., with low-latency vs. with ordinary latency).
  • audio content e.g., home theater audio vs. music
  • different playback timing arrangements e.g., with low-latency vs. with ordinary latency
  • U.S. App. 14/731,119 titled, “Dynamic Bonding of Playback Devices,” referred to as Docket No. 15-0301, filed on Jun. 4, 2015, and issued on Jan. 9, 2018, as U.S. Pat. 9,864,571, discloses, inter alia, dynamic bonding scenarios and playback devices that are “sharable” among different zones.
  • U.S. App. 14/997,269 titled, “System Limits Based on Known Triggers,” referred to as Docket 15-1104, filed on Jan. 15, 2016, and issued on Feb. 20, 2018, as U.S. Pat. 9,898,245, describes, inter alia, methods of setting up multiple playback devices.
  • the surround sound controller uses a first Modulation and Coding Scheme (MCS) to transmit first surround sound audio information to a first pair of headphones
  • MCS Modulation and Coding Scheme
  • the surround sound controller uses a second MCS to transmit (a) the first surround sound audio information to the first pair of headphones and (b) second surround sound audio information to a second pair of headphones.
  • U.S. Apps. 13/489,674; 14/042,001; 14/041,989; 14/988,524; 16/119,516; 16/119,642; 62/672,020; and 16/415,783 do not describe the Area Zone configurations, Multi-Player Playback Devices, playback entity implementations, logical players, and/or the “multi-instance” software architecture described herein.
  • the entire contents of U.S. Apps. 13/489,674; 14/042,001; 14/041,989; 14/988,524; 16/119,516; 16/119,642; 62/672,020; and 16/415,783 are incorporated herein by reference.
  • calibrating playback settings includes, inter alia, determining one or more acoustic characteristics of the listening environment, and adjusting one or more audio playback settings (e.g., equalization settings, relative loudness, playing timing delays, and/or perhaps other settings) based on the acoustic characteristics.
  • U.S. App. 15/211,822 titled, “Spatial Audio Correction,” referred to as Docket No. 16-0402, filed on Jul. 15, 2016, and issued on Oct. 17, 2017, as U.S. Pat. 9,794,710 describes, inter alia, determining a spatial and/or spectral calibration for one or more playback devices within a listening area.
  • 10,299,061 describes, inter alia, calibrating a playback device within a room so that the audio output by the playback device accounts for (e.g., offsets) acoustic characteristics of that room, thereby improving sound of the audio playback experienced by a listener within the room.
  • U.S. App. 15/630,214 titled, “Immersive Audio in a Media Playback System,” referred to as Docket No. 16-0504, filed on Jun. 22, 2017, and issued on Jul. 17, 2018, as U.S. Pat. 10,028,069 describes, inter alia, processes that include obtaining audio responses from several different playback devices in a media playback system. For example, a first playback device at a first time plays back calibration audio while a microphone device records the calibration audio being played back. A second playback device at a second time plays back the calibration audio while the microphone device records the calibration audio being played. The process is repeated until every playback device in the media playback system has played the calibration audio and had its response recorded.
  • Apps. 15/211,822; 16/115,524; 15/630,214; and PCT/US22/77233 do not describe the Area Zone configurations, Multi-Player Playback Devices, playback entity implementations, and/or the “multi-instance” software architecture described herein.
  • the entire contents of Apps. 15/211,822; 16/115,524; 15/630,214; and PCT/US22/77233 are incorporated herein by reference.
  • Figure 1 A is a partial cutaway view of a media playback system 100 distributed in an environment 101 (e.g., a house).
  • the media playback system 100 comprises one or more playback devices 110 (identified individually as playback devices 1 lOa-n), one or more network microphone devices (“NMDs”), 120 (identified individually as NMDs 120a- c), and one or more control devices 130 (identified individually as control devices 130a and 130b).
  • NMDs network microphone devices
  • a playback device can generally refer to a network device configured to receive, process, and output data of a media playback system.
  • a playback device can be a network device that receives and processes audio content.
  • a playback device includes one or more transducers or speakers powered by one or more amplifiers.
  • a playback device includes one of (or neither of) the speaker and the amplifier.
  • a playback device can comprise one or more amplifiers configured to drive one or more speakers external to the playback device via a corresponding wire or cable.
  • control device can generally refer to a network device configured to perform functions relevant to facilitating user access, control, and/or configuration of the media playback system 100.
  • Each of the playback devices 110 is configured to receive audio signals or data from one or more media sources (e.g., one or more remote servers, one or more local devices) and play back the received audio signals or data as sound.
  • the one or more NMDs 120 are configured to receive spoken word commands
  • the one or more control devices 130 are configured to receive user input.
  • the media playback system 100 can play back audio via one or more of the playback devices 110.
  • the playback devices 110 are configured to commence playback of media content in response to a trigger.
  • one or more of the playback devices 110 can be configured to play back a morning playlist upon detection of an associated trigger condition (e.g., presence of a user in a kitchen, detection of a coffee machine operation).
  • the media playback system 100 is configured to play back audio from a first playback device (e.g., the playback device 100a) in synchrony with a second playback device (e.g., the playback device 100b).
  • a first playback device e.g., the playback device 100a
  • a second playback device e.g., the playback device 100b
  • the environment 101 comprises a household having several rooms, spaces, and/or playback zones, including (clockwise from upper left) a master bathroom 101a, a master bedroom 101b, a second bedroom 101c, a family room or den 101 d, an office lOle, a living room 10 If, a dining room 101g, a kitchen lOlh, and an outdoor patio lOli. While certain example configurations and examples are described below in the context of a home environment, the technologies described herein may be implemented in other types of environments.
  • the media playback system 100 can be implemented in one or more commercial settings (e.g., a restaurant, mall, airport, hotel, a retail or other store), one or more vehicles (e.g., a sports utility vehicle, bus, car, a ship, a boat, an airplane), multiple environments (e.g., a combination of home and vehicle environments), and/or another suitable environment where multi-zone audio may be desirable.
  • a commercial setting e.g., a restaurant, mall, airport, hotel, a retail or other store
  • vehicles e.g., a sports utility vehicle, bus, car, a ship, a boat, an airplane
  • multiple environments e.g., a combination of home and vehicle environments
  • multi-zone audio may be desirable.
  • the media playback system 100 can comprise one or more playback zones, some of which may correspond to the rooms in the environment 101.
  • the media playback system 100 can be established with one or more playback zones, after which additional zones may be added, or removed to form, for example, the configuration shown in Figure 1 A.
  • Each zone may be given a name according to a different room or space such as the office lOle, master bathroom 101a, master bedroom 101b, the second bedroom 101c, kitchen lOlh, dining room 101g, living room lOlf, and/or the patio lOli.
  • a single playback zone may include multiple rooms or spaces.
  • a single room or space may include multiple playback zones.
  • the master bathroom 101a, the second bedroom 101c, the office lOle, the living room 10 If, the dining room 101g, the kitchen lOlh, and the outdoor patio lOli each include one playback device 110, and the master bedroom 101b and the den 101 d include a plurality of playback devices 110.
  • the playback devices 1101 and 110m may be configured, for example, to play back audio content in synchrony as individual ones of playback devices 110, as a bonded playback zone, as a consolidated playback device, and/or any combination thereof.
  • the playback devices 1 lOh-j can be configured, for instance, to play back audio content in synchrony as individual ones of playback devices 110, as one or more bonded playback devices, and/or as one or more consolidated playback devices. Additional details regarding bonded and consolidated playback devices are described below with respect to, for example, Figures IB and IE and 1I-1M.
  • one or more of the playback zones in the environment 101 may each be playing different audio content.
  • a user may be grilling on the patio lOli and listening to hip hop music being played by the playback device 110c while another user is preparing food in the kitchen lOlh and listening to classical music played by the playback device 110b.
  • a playback zone may play the same audio content in synchrony with another playback zone.
  • the user may be in the office lOle listening to the playback device 1 lOf playing back the same hip hop music being played back by playback device 110c on the patio lOli.
  • the playback devices 110c and 1 lOf play back the hip hop music in synchrony such that the user perceives that the audio content is being played seamlessly (or at least substantially seamlessly) while moving between different playback zones. Additional details regarding audio playback synchronization among playback devices and/or zones can be found, for example, in U.S. Patent No. 8,234,395 entitled, “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is incorporated herein by reference in its entirety. a. Suitable Media Playback System
  • Figure IB is a schematic diagram of the media playback system 100 and a cloud network 102. For ease of illustration, certain devices of the media playback system 100 and the cloud network 102 are omitted from Figure IB.
  • One or more communications links 103 (referred to hereinafter as “the links 103”) communicatively couple the media playback system 100 and the cloud network 102.
  • the links 103 can comprise, for example, one or more wired networks, one or more wireless networks, one or more wide area networks (WAN), one or more local area networks (LAN), one or more personal area networks (PAN), one or more telecommunication networks (e.g., one or more Global System for Mobiles (GSM) networks, Code Division Multiple Access (CDMA) networks, Long-Term Evolution (LTE) networks, 5G communication network networks, and/or other suitable data transmission protocol networks), etc.
  • GSM Global System for Mobiles
  • CDMA Code Division Multiple Access
  • LTE Long-Term Evolution
  • 5G communication network networks and/or other suitable data transmission protocol networks
  • the cloud network 102 is configured to deliver media content (e.g., audio content, video content, photographs, social media content) to the media playback system 100 in response to a request transmitted from the media playback system 100 via the links 103.
  • the cloud network 102 is further configured to receive data (e.g. voice input data) from the media playback system 100 and correspondingly transmit commands and/or media
  • the cloud network 102 comprises computing devices 106 (identified separately as a first computing device 106a, a second computing device 106b, and a third computing device 106c).
  • the computing devices 106 can comprise individual computers or servers, such as, for example, a media streaming service server storing audio and/or other media content, a voice service server, a social media server, a media playback system control server, etc.
  • one or more of the computing devices 106 comprise modules of a single computer or server.
  • one or more of the computing devices 106 comprise one or more modules, computers, and/or servers.
  • the cloud network 102 is described above in the context of a single cloud network, in some example configurations the cloud network 102 comprises a plurality of cloud networks comprising communicatively coupled computing devices. Furthermore, while the cloud network 102 is shown in Figure IB as having three of the computing devices 106, in some example configurations, the cloud network 102 comprises fewer (or more than) three computing devices 106.
  • the media playback system 100 is configured to receive media content from the networks 102 via the links 103.
  • the received media content can comprise, for example, a Uniform Resource Identifier (URI) and/or a Uniform Resource Locator (URL).
  • URI Uniform Resource Identifier
  • URL Uniform Resource Locator
  • the media playback system 100 can stream, download, or otherwise obtain data from a URI or a URL corresponding to the received media content.
  • a network 104 communicatively couples the links 103 and at least a portion of the devices (e.g., one or more of the playback devices 110, NMDs 120, and/or control devices 130) of the media playback system 100.
  • 802.11af, 802.11ah, 802.1 lai, 802.1 laj, 802.11aq, 802.11ax, 802.11ay, 802.15, etc. transmitted at 2.4 Gigahertz (GHz), 5 GHz, and/or another suitable frequency.
  • the network 104 comprises a dedicated communication network that the media playback system 100 uses to transmit messages between individual devices and/or to transmit media content to and from media content sources (e.g., one or more of the computing devices 106).
  • the network 104 is configured to be accessible only to devices in the media playback system 100, thereby reducing interference and competition with other household devices.
  • the network 104 comprises an existing household communication network (e.g., a household WiFi network).
  • the links 103 and the network 104 comprise one or more of the same networks.
  • the links 103 and the network 104 comprise a telecommunication network (e.g., an LTE network, a 5G network).
  • the media playback system 100 is implemented without the network 104, and devices comprising the media playback system 100 can communicate with each other, for example, via one or more direct connections, PANs, telecommunication networks, and/or other suitable communications links.
  • audio content sources may be regularly added or removed from the media playback system 100.
  • the media playback system 100 performs an indexing of media items when one or more media content sources are updated, added to, and/or removed from the media playback system 100.
  • the media playback system 100 can scan identifiable media items in some or all folders and/or directories accessible to the playback devices 110, and generate or update a media content database comprising metadata (e.g., title, artist, album, track length) and other associated information (e.g., URIs, URLs) for each identifiable media item found.
  • metadata e.g., title, artist, album, track length
  • other associated information e.g., URIs, URLs
  • the media content database is stored on one or more of the playback devices 110, network microphone devices 120, and/or control devices 130.
  • the playback devices 1101 and 110m comprise a group 107a.
  • the playback devices 1101 and 110m can be positioned in different rooms in a household and be grouped together in the group 107a on a temporary or permanent basis based on user input received at the control device 130a and/or another control device 130 in the media playback system 100.
  • the playback devices 1101 and 110m can be configured to play back the same or similar audio content in synchrony from one or more audio content sources.
  • the group 107a comprises a bonded zone in which the playback devices 1101 and 110m comprise left audio and right audio channels, respectively, of multichannel audio content, thereby producing or enhancing a stereo effect of the audio content.
  • the group 107a includes additional playback devices 110.
  • the media playback system 100 omits the group 107a and/or other grouped arrangements of the playback devices 110. Additional details regarding groups and other arrangements of playback devices are described in further detail below with respect to Figures 1-1 through IM.
  • the media playback system 100 includes the NMDs 120a and 120d, each comprising one or more microphones configured to receive voice utterances from a user.
  • the NMD 120a is a standalone device and the NMD 120d is integrated into the playback device 1 lOn.
  • the NMD 120a for example, is configured to receive voice input 121 from a user 123.
  • the NMD 120a transmits data associated with the received voice input 121 to a voice assistant service (VAS) configured to (i) process the received voice input data and (ii) transmit a corresponding command to the media playback system 100.
  • VAS voice assistant service
  • the computing device 106c comprises one or more modules and/or servers of a VAS (e.g., a VAS operated by one or more of SONOS®, AMAZON®, GOOGLE® APPLE®, MICROSOFT®).
  • the computing device 106c can receive the voice input data from the NMD 120a via the network 104 and the links 103.
  • the computing device 106c processes the voice input data (i.e., “Play Hey Jude by The Beatles”), and determines that the processed voice input includes a command to play a song (e.g., “Hey Jude”).
  • FIG. 1C is a block diagram of the playback device 110a comprising an input/output 111.
  • the input/output 111 can include an analog I/O I l la (e.g., one or more wires, cables, and/or other suitable communications links configured to carry analog signals) and/or a digital I/O 111b (e.g., one or more wires, cables, or other suitable communications links configured to carry digital signals).
  • the analog I/O 11 la is an audio line-in input connection comprising, for example, an auto-detecting 3.5mm audio line-in connection.
  • the digital I/O 111b comprises a Sony/Philips Digital Interface Format (S/PDIF) communication interface and/or cable and/or a Toshiba Link (TOSLINK) cable.
  • the digital I/O 111b comprises an High-Definition Multimedia Interface (HDMI) interface and/or cable.
  • the digital I/O 111b includes one or more wireless communications links comprising, for example, a radio frequency (RF), infrared, WiFi, Bluetooth, or another suitable communication protocol.
  • RF radio frequency
  • the analog I/O I l la and the digital I/O 111b comprise interfaces (e.g., ports, plugs, jacks) configured to receive connectors of cables transmitting analog and digital signals, respectively, without necessarily including cables.
  • the playback device 110a can receive media content (e.g., audio content comprising music and/or other sounds) from a local audio source 105 via the input/output 111 (e.g., a cable, a wire, a PAN, a Bluetooth connection, an ad hoc wired or wireless communication network, and/or another suitable communications link).
  • the local audio source 105 can comprise, for example, a mobile device (e.g., a smartphone, a tablet, a laptop computer) or another suitable audio component (e.g., a television, a desktop computer, an amplifier, a phonograph, a Blu-ray player, a memory storing digital media files).
  • the local audio source 105 includes local music libraries on a smartphone, a computer, a networked-attached storage (NAS), and/or another suitable device configured to store media files.
  • one or more of the playback devices 110, NMDs 120, and/or control devices 130 comprise the local audio source 105.
  • the media playback system omits the local audio source 105 altogether.
  • the playback device 110a does not include an input/output 111 and receives all audio content via the network 104.
  • the playback device 110a further comprises electronics 112, a user interface 113 (e.g., one or more buttons, knobs, dials, touch-sensitive surfaces, displays, touchscreens), and one or more transducers 114 (referred to hereinafter as “the transducers 114”).
  • the electronics 112 is configured to receive audio from an audio source (e.g., the local audio source 105) via the input/output 111, one or more of the computing devices 106a-c via the network 104 ( Figure IB)), amplify the received audio, and output the amplified audio for playback via one or more of the transducers 114.
  • the electronics 112 comprise one or more processors 112a (referred to hereinafter as “the processors 112a”), memory 112b, software components 112c, a network interface 112d, one or more audio processing components 112g (referred to hereinafter as “the audio components 112g”), one or more audio amplifiers 112h (referred to hereinafter as “the amplifiers 112h”), and power 112i (e.g., one or more power supplies, power cables, power receptacles, batteries, induction coils, Power-over Ethernet (POE) interfaces, and/or other suitable sources of electric power).
  • the electronics 112 optionally include one or more other components 112j (e.g., one or more sensors, video displays, touchscreens, battery charging bases).
  • the processors 112a can comprise clock-driven computing component(s) configured to process data
  • the memory 112b can comprise a computer-readable medium (e.g., a tangible, non-transitory computer-readable medium, data storage loaded with one or more of the software components 112c) configured to store instructions for performing various operations and/or functions.
  • the processors 112a are configured to execute the instructions stored on the memory 112b to perform one or more of the operations.
  • the operations can include, for example, causing the playback device 110a to retrieve audio information from an audio source (e.g., one or more of the computing devices 106a-c ( Figure IB)), and/or another one of the playback devices 110.
  • an audio source e.g., one or more of the computing devices 106a-c ( Figure IB)
  • the operations further include causing the playback device 110a to send audio information to another one of the playback devices 110a and/or another device (e.g., one of the NMDs 120).
  • Certain example configurations include operations causing the playback device 110a to pair with another of the one or more playback devices 110 to enable a multi-channel audio environment (e.g., a stereo pair, a bonded zone).
  • the processors 112a can be further configured to perform operations causing the playback device 110a to synchronize playback of audio content with another of the one or more playback devices 110.
  • a listener will preferably be unable to perceive time-delay differences between playback of the audio content by the playback device 110a and the other one or more other playback devices 110. Additional details regarding audio playback synchronization among playback devices can be found, for example, in U.S. Patent No. 8,234,395, which was incorporated by reference above.
  • the memory 112b is further configured to store data associated with the playback device 110a, such as one or more zones and/or zone groups of which the playback device 110a is a member, audio sources accessible to the playback device 110a, and/or a playback queue that the playback device 110a (and/or another of the one or more playback devices) can be associated with.
  • the stored data can comprise one or more state variables that are periodically updated and used to describe a state of the playback device 110a.
  • the memory 112b can also include data associated with a state of one or more of the other devices (e.g., the playback devices 110, NMDs 120, control devices 130) of the media playback system 100.
  • the state data is shared during predetermined intervals of time (e.g., every 5 seconds, every 10 seconds, every 60 seconds) among at least a portion of the devices of the media playback system 100, so that one or more of the devices have the most recent data associated with the media playback system 100.
  • the network interface 112d is configured to facilitate a transmission of data between the playback device 110a and one or more other devices on a data network such as, for example, the links 103 and/or the network 104 ( Figure IB).
  • the network interface 112d is configured to transmit and receive data corresponding to media content (e.g., audio content, video content, text, photographs) and other signals (e.g., non-transitory signals) comprising digital packet data including an Internet Protocol (IP)-based source address and/or an IPbased destination address.
  • IP Internet Protocol
  • the network interface 112d can parse the digital packet data such that the electronics 112 properly receives and processes the data destined for the playback device 110a.
  • the network interface 112d comprises one or more wireless interfaces 112e (referred to hereinafter as “the wireless interface 112e”).
  • the wireless interface 112e e.g., a suitable interface comprising one or more antennae
  • the wireless interface 112e can be configured to wirelessly communicate with one or more other devices (e.g., one or more of the other playback devices 110, NMDs 120, and/or control devices 130) that are communicatively coupled to the network 104 ( Figure IB) in accordance with a suitable wireless communication protocol (e.g., WiFi, Bluetooth, LTE).
  • a suitable wireless communication protocol e.g., WiFi, Bluetooth, LTE
  • the network interface 112d optionally includes a wired interface 112f (e.g., an interface or receptacle configured to receive a network cable such as an Ethernet, a USB-A, USB-C, and/or Thunderbolt cable) configured to communicate over a wired connection with other devices in accordance with a suitable wired communication protocol.
  • the network interface 112d includes the wired interface 112f and excludes the wireless interface 112e.
  • the electronics 112 excludes the network interface 112d altogether and transmits and receives media content and/or other data via another communication path (e.g., the input/output 111).
  • the audio processing components 112g are configured to process and/or filter data comprising media content received by the electronics 112 (e.g., via the input/output 111 and/or the network interface 112d) to produce output audio signals.
  • the audio processing components 112g comprise, for example, one or more digital-to-analog converters (DAC), audio preprocessing components, audio enhancement components, a digital signal processors (DSPs), and/or other suitable audio processing components, modules, circuits, etc.
  • one or more of the audio processing components 112g can comprise one or more subcomponents of the processors 112a.
  • the electronics 112 omits the audio processing components 112g.
  • the processors 112a execute instructions stored on the memory 112b to perform audio processing operations to produce the output audio signals.
  • the amplifiers 112h are configured to receive and amplify the audio output signals produced by the audio processing components 112g and/or the processors 112a.
  • the amplifiers 112h can comprise electronic devices and/or components configured to amplify audio signals to levels sufficient for driving one or more of the transducers 114.
  • the amplifiers 112h include one or more switching or class-D power amplifiers.
  • the amplifiers include one or more other types of power amplifiers (e.g., linear gain power amplifiers, class-A amplifiers, class-B amplifiers, class-AB amplifiers, class-C amplifiers, class-D amplifiers, class-E amplifiers, class-F amplifiers, class-G and/or class H amplifiers, and/or another suitable type of power amplifier).
  • the amplifiers 112h comprise a suitable combination of two or more of the foregoing types of power amplifiers.
  • individual ones of the amplifiers 112h correspond to individual ones of the transducers 114.
  • the electronics 112 includes a single one of the amplifiers 112h configured to output amplified audio signals to a plurality of the transducers 114. In some other example configurations, the electronics 112 omits the amplifiers 112h.
  • the transducers 114 e.g., one or more speakers and/or speaker drivers
  • the transducers 114 can comprise a single transducer.
  • low frequency can generally refer to audible frequencies below about 500 Hz
  • mid-range frequency can generally refer to audible frequencies between about 500 Hz and about 2 kHz
  • high frequency can generally refer to audible frequencies above 2 kHz.
  • one or more of the transducers 114 comprise transducers that do not adhere to the foregoing frequency ranges.
  • one of the transducers 114 may comprise a mid-woofer transducer configured to output sound at frequencies between about 200 Hz and about 5 kHz.
  • SONOS, Inc. presently offers (or has offered) for sale certain playback devices including, for example, a “SONOS ONE,” “PLAY:1,” “PLAY:3,” “PLAYA,” “PLAYBAR,” “PLAYBASE,” “CONNECT: AMP,” “CONNECT,” and “SUB.”
  • Other suitable playback devices may additionally or alternatively be used to implement the playback devices of example configurations disclosed herein.
  • a playback device is not limited to the examples described herein or to SONOS product offerings.
  • one or more playback devices 110 comprises wired or wireless headphones (e.g., over-the-ear headphones, on-ear headphones, in-ear earphones).
  • one or more of the playback devices 110 comprise a docking station and/or an interface configured to interact with a docking station for personal mobile media playback devices.
  • a playback device may be integral to another device or component such as a television, a lighting fixture, or some other device for indoor or outdoor use.
  • a playback device omits a user interface and/or one or more transducers. For example, FIG.
  • Figure ID is a block diagram of a playback device 1 lOp comprising the input/output 111 and electronics 112 without the user interface 113 or transducers 114.
  • Figure IE is a block diagram of a bonded playback device 1 lOq comprising the playback device 110a ( Figure 1C) sonically bonded with the playback device 1 lOi (e.g., a subwoofer) ( Figure 1 A).
  • the playback devices 110a and 1 lOi are separate ones of the playback devices 110 housed in separate enclosures.
  • the bonded playback device 1 lOq comprises a single enclosure housing both the playback devices 110a and 1 lOi.
  • the bonded playback device 1 lOq can be configured to process and reproduce sound differently than an unbonded playback device (e.g., the playback device 110a of Figure 1C) and/or paired or bonded playback devices (e.g., the playback devices 1101 and 110m of Figure IB).
  • the playback device 110a is full-range playback device configured to render low frequency, mid-range frequency, and high frequency audio content
  • the playback device 1 lOi is a subwoofer configured to render low frequency audio content.
  • the playback device 110a when bonded with the first playback device, is configured to render only the mid-range and high frequency components of a particular audio content, while the playback device 1 lOi renders the low frequency component of the particular audio content.
  • the bonded playback device 1 lOq includes additional playback devices and/or another bonded playback device. Additional playback device example configurations are described in further detail below with respect to Figures 2A-3D.
  • CMDs Suitable Network Microphone Devices
  • an activation word is a word or other audio cue that signifying a user voice input. For instance, in querying the AMAZON® VAS, a user might speak the activation word "Alexa.” Other examples include “Ok, Google” for invoking the GOOGLE® VAS and “Hey, Siri” for invoking the APPLE® VAS.
  • a plurality of fasteners 216g attaches a frame 216h to the housing 216.
  • a cavity 216j ( Figure 2C) in the housing 216 is configured to receive the frame 216h and electronics 212.
  • the frame 216h is configured to carry a plurality of transducers 214 (identified individually in Figure 2B as transducers 214a-f).
  • the electronics 212 e.g., the electronics 112 of Figure 1C) is configured to receive audio content from an audio source and send electrical signals corresponding to the audio content to the transducers 214 for playback.
  • Figures 3 A and 3B are front and right isometric side views, respectively, of an NMD 320 configured in accordance with example configurations of the disclosed technology.
  • Figure 3C is an exploded view of the NMD 320.
  • Figure 3D is an enlarged view of a portion of Figure 3B including a user interface 313 of the NMD 320.
  • the NMD 320 includes a housing 316 comprising an upper portion 316a, a lower portion 316b and an intermediate portion 316c (e.g., a grille).
  • a plurality of ports, holes or apertures 316d in the upper portion 316a allow sound to pass through to one or more microphones 315 ( Figure 3C) positioned within the housing 316.
  • the one or more microphones 315 are configured to received sound via the apertures 316d and produce electrical signals based on the received sound.
  • a frame 316e ( Figure 3C) of the housing 316 surrounds cavities 316f and 316g configured to house, respectively, a first transducer 314a (e.g., a tweeter) and a second transducer 314b (e.g., a mid-woofer, a midrange speaker, a woofer).
  • the NMD 320 includes a single transducer, or more than two (e.g., two, five, six) transducers. In certain example configurations, the NMD 320 omits the transducers 314a and 314b altogether.
  • Electronics 312 ( Figure 3C) includes components configured to drive the transducers 314a and 314b, and further configured to analyze audio information corresponding to the electrical signals produced by the one or more microphones 315.
  • the electronics 312 comprises many or all of the components of the electronics 112 described above with respect to Figure 1C.
  • the electronics 312 includes components described above with respect to Figure IF such as, for example, the one or more processors 112a, the memory 112b, the software components 112c, the network interface 112d, etc.
  • the electronics 312 includes additional suitable components (e.g., proximity or other sensors).
  • the user interface 313 includes a plurality of control surfaces (e.g., buttons, knobs, capacitive surfaces) including a first control surface 313a (e.g., a previous control), a second control surface 313b (e.g., a next control), and a third control surface 313c (e.g., a play and/or pause control).
  • a fourth control surface 313d is configured to receive touch input corresponding to activation and deactivation of the one or microphones 315.
  • a first indicator 313e e.g., one or more light emitting diodes (LEDs) or another suitable illuminator
  • LEDs light emitting diodes
  • a second indicator 313f (e.g., one or more LEDs) can be configured to remain solid during normal operation and to blink or otherwise change from solid to indicate a detection of voice activity.
  • the user interface 313 includes additional or fewer control surfaces and illuminators.
  • the user interface 313 includes the first indicator 313e, omitting the second indicator 313f.
  • the NMD 320 comprises a playback device and a control device, and the user interface 313 comprises the user interface of the control device
  • the NMD 320 is configured to receive voice commands from one or more adjacent users via the one or more microphones 315.
  • the one or more microphones 315 can acquire, capture, or record sound in a vicinity (e.g., a region within 10m or less of the NMD 320) and transmit electrical signals corresponding to the recorded sound to the electronics 312.
  • the electronics 312 can process the electrical signals and can analyze the resulting audio data to determine a presence of one or more voice commands (e.g., one or more activation words).
  • a user may speak “Sonos, play Michael Jackson.”
  • the NMD 320 can, via the one or more microphones 315, record the user’s voice utterance, determine the presence of a voice command, and transmit the audio data having the voice command to a remote server (e.g., one or more of the remote computing devices 106 of Figure IB, one or more servers of a VAS and/or another suitable service).
  • the remote server can analyze the audio data and determine an action corresponding to the command.
  • the remote server can then transmit a command to the NMD 320 to perform the determined action (e.g., play back audio content related to Michael Jackson).
  • the NMD 320 can receive the command and play back the audio content related to Michael Jackson from a media content source.
  • the activation word detector components 312n are configured to monitor and analyze received audio to determine if any activation words (e.g., wake words) are present in the received audio.
  • the activation word detector components 312n may analyze the received audio using an activation word detection algorithm. If the activation word detector 312n detects an activation word, the NMD 320 may process voice input contained in the received audio.
  • Example activation word detection algorithms accept audio as input and provide an indication of whether an activation word is present in the audio.
  • Many first- and third-party activation word detection algorithms are known and commercially available. For instance, operators of a voice service may make their algorithm available for use in third-party devices. Alternatively, an algorithm may be trained to detect certain activation words.
  • the activation word detector 312n runs multiple activation word detection algorithms on the received audio simultaneously (or substantially simultaneously).
  • different voice services e.g. AMAZON'S ALEXA®, APPLE'S SIRI®, or MICROSOFT'S CORTANA®
  • the activation word detector 312n may run the received audio through the activation word detection algorithm for each supported voice service in parallel.
  • the speech/text conversion components 312o may facilitate processing by converting speech in the voice input to text.
  • the electronics 312 can include voice recognition software that is trained to a particular user or a particular set of users associated with a household.
  • voice recognition software may implement voice-processing algorithms that are tuned to specific voice profile(s). Tuning to specific voice profiles may require less computationally intensive algorithms than traditional voice activity services, which typically sample from a broad base of users and diverse requests that are not targeted to media playback systems.
  • FIG. 3F is a schematic diagram of an example voice input 328 captured by the NMD 320 in accordance with aspects of the disclosure.
  • the voice input 328 can include a activation word portion 328a and a voice utterance portion 328b.
  • the activation word 557a can be a known activation word, such as “Alexa,” which is associated with AMAZON'S ALEXA®.
  • the voice input 328 may not include a activation word.
  • a network microphone device may output an audible and/or visible response upon detection of the activation word portion 328a.
  • an NMD may output an audible and/or visible response after processing a voice input and/or a series of voice inputs.
  • FIGS 4A-4D are schematic diagrams of a control device 430 (e.g., the control device 130a of Figure 1H, a smartphone, a tablet, a dedicated control device, an loT device, and/or another suitable device) showing corresponding user interface displays in various states of operation.
  • a first user interface display 43 la ( Figure 4A) includes a display name 433a (i.e., “Rooms”).
  • a selected group region 433b displays audio content information (e.g., artist name, track name, album art) of audio content played back in the selected group and/or zone.
  • Group regions 433c and 433d display corresponding group and/or zone name, and audio content information audio content played back or next in a playback queue of the respective group or zone.
  • An audio content region 433 e includes information related to audio content in the selected group and/or zone (i.e., the group and/or zone indicated in the selected group region 433b).
  • a lower display region 433f is configured to receive touch input to display one or more other user interface displays.
  • FIG. 5 is a schematic diagram of a control device 530 (e.g., a laptop computer, a desktop computer) .
  • the control device 530 includes transducers 534, a microphone 535, and a camera 536.
  • a user interface 531 includes a transport control region 533a, a playback status region 533b, a playback zone region 533c, a playback queue region 533d, and a media content source region 533e.
  • the transport control region comprises one or more controls for controlling media playback including, for example, volume, previous, play/pause, next, repeat, shuffle, track position, crossfade, equalization, etc.
  • the audio content source region 533e includes a listing of one or more media content sources from which a user can select media items for play back and/or adding to a playback queue.
  • the playback device 110a receives the message 651a and adds the selected media content to the playback queue for play back.
  • the control device 130a receives input corresponding to a command to play back the selected media content.
  • the control device 130a transmits a message 651b to the playback device 110a causing the playback device 110a to play back the selected media content.
  • the playback device 110a transmits a message 651c to the first computing device 106a requesting the selected media content.
  • the first computing device 106a in response to receiving the message 651c, transmits a message 65 Id comprising data (e.g., audio data, video data, a URL, a URI) corresponding to the requested media content.
  • the playback device 110a receives the message 65 Id with the data corresponding to the requested media content and plays back the associated media content.
  • the playback device 110a optionally causes one or more other devices to play back the selected media content.
  • the playback device 110a is one of a bonded zone of two or more players ( Figure IM).
  • the playback device 110a can receive the selected media content and transmit all or a portion of the media content to other devices in the bonded zone.
  • the playback device 110a is a coordinator of a group and is configured to transmit and receive timing information from one or more other devices in the group.
  • the other one or more devices in the group can receive the selected media content from the first computing device 106a, and begin playback of the selected media content in response to a message from the playback device 110a such that all of the devices in the group play back the selected media content in synchrony.
  • a Multi-Player Playback Device is a playback device comprising multiple configurable audio outputs, one or more processors, and tangible, non- transitory computer readable media storing program instructions that are executed by the one or more processors to cause the Multi-Player Playback Device to perform the Multi-Player Playback Device features and functions described herein.
  • the Multi-Player Playback Device 700 can be configured to operate in any of the grouped configurations described herein, including but not limited to, the Area Zone configurations disclosed above. Further, when configured in an Area Zone configuration, the Multi-Player Playback Device 700 can be configured to perform any of the Area Zone features disclosed above, including but not limited to performing the functions of an Area Zone Primary and/or Area Zone Secondary.
  • the example Multi-Player Playback Device 700 illustrated in Figure 7 includes one or more processors 702 and one or more tangible, non-transitory computer- readable memory 704.
  • the tangible, non-transitory computer-readable memory 704 is configured to store program instructions that are executable by the one or more processors 702. When executed by the one or more processors 702, the program instructions cause the Multi-Player Playback Device 700 to perform the Multi-Player Playback Device functions disclosed and described herein.
  • Multi-Player Playback Device 700 also includes one or more network interfaces 706.
  • the network interfaces may include any one or more (i) wired network interfaces, e.g., Ethernet, Universal Serial Bus, Firewire, Power-over-Ethemet, or any other type of wired network interface now known or later developed that is suitable for transmitting and receiving the types of data described herein and/or (ii) wireless network interfaces, e.g., WiFi, Bluetooth, 4G/5G, or any other type of wireless interface now known or later developed that is suitable for transmitting and receive the types of data described herein.
  • Multi-Player Playback Device 700 includes amplifiers 710-1, 710-2, 710-3, and 710-4, where each amplifier is connected to two audio outputs.
  • the router component 720 is also configured to route data from a logical player implemented by the Multi-Player Playback Device 700 to the one or more network interfaces 706 based at least in part on ULPI data, including in some instances, ULPI data in packet and/or frame headers.
  • the Multi-Player Playback Device 700 is configured to operate within any of several different operating modes.
  • the Multi- Player Playback Device 700 is reconfigurable to switch between operating in one mode to operating in a different mode.
  • the Multi-Player Playback Device 700 is configurable to operate in a first mode where the Multi-Player Playback Device 700 is configured to implement eight single-channel logical players, where each logical player is configured to output single-channel audio from one of the eight audio outputs.
  • each of the audio outputs 712-1 through 712-8 plays the same channel of audio.
  • the single-channel audio comprises a mono audio stream.
  • the single-channel audio comprises one channel from a multi-channel audio stream.
  • the Multi-Player Playback Device 700 is configurable to operate in a second mode where the Multi-Player Playback Device 700 is configured to implement four two-channel logical players, wherein each logical player is configured to output two-channel audio from two of the eight audio outputs.
  • a first logical player uses amp 710-1 to drive audio outputs 712-1 and 712-2 to output two channels of audio
  • a second logical player uses amp 710-2 to drive audio outputs 712-3 and 712-4 to output two channels of audio
  • a third logical player uses amp 710-3 to drive audio outputs 712-5 and 712-6 to output two channels of audio
  • a fourth logical player uses amp 710-4 to drive audio outputs 712-7 and 712-8 to output two channels of audio.
  • the two channels of audio could be left and right channels of a stereo audio stream. Alternatively, the two channels of audio could be any two different channels of a multichannel audio stream.
  • all four of the logical players are configured to output the same audio stream.
  • one or more of the logical players may be configured to output different audio than one or more other logical players.
  • the Multi-Player Playback Device 700 is configurable to operate in a third mode where the Multi-Player Playback Device 700 is configured to implement two four-channel logical players, wherein each logical player is configured to output four-channel audio from four of the eight audio outputs.
  • the Multi-Player Playback Device 700 is configurable to operate in a fourth mode where the Multi-Player Playback Device 700 is configured to implement one eight-channel logical player, where the logical player is configured to output eight-channel audio from the eight audio outputs.
  • a single logical player uses amps 710-1 through 710-4 to drive audio outputs 712-1 through 712-8 to output eight channels of audio.
  • the eight channels of audio could be front left, front center, front right, rear left, rear center, rear right, left subwoofer, and right subwoofer channels of a surround sound audio stream.
  • the eight channels of audio could be any eight different channels of a multichannel audio stream.
  • the logical player is configured to output the same channel of audio via each of the eight audio outputs.
  • the Multi-Player Playback Device 700 in some embodiments is configurable to operate in other operating modes that include combinations of differently-configured players.
  • the Multi-Player Playback Device 700 is configurable to operate in a mode that includes (i) a first logical player that uses amps 710-1, 710-2, and 710-3 to drive audio outputs 712-1, 712-2, and 712-3 to output three channels of audio, and (ii) a second logical player uses amp 710-4 to drive audio output 712-8 to output one channel of audio.
  • the Multi-Player Playback Device 700 can implement other combinations and configurations of amps and audio outputs to output different channels of audio content.
  • Multi-Player Playback Devices e.g., several Multi-Player Playback Devices like Multi-Player Playback Device 700
  • Multi-Player Playback Device 700 can be bonded together to implement more sophisticated configurations of one or more logical players.
  • the Multi-Player Playback Device 700 is configured to selectively operate in any of a plurality of bonded modes comprising a first bonded mode and a second bonded mode.
  • the Multi-Player Playback Device 700 is configured to operate in a bonded configuration with a second Multi-Player Playback Device that has eight audio outputs similar to Multi-Player Playback Device 700.
  • the Multi-Player Playback Device 700 and the second Multi-Player Playback Device are configured to implement a single logical player configured to output any of (i) one set of sixteen channels of audio, (ii) two sets of eight channels of audio, (iii) four sets of four channels of audio, (iv) eight sets of two channels of audio, (v) sixteen single channels of audio, or (vi) any other suitable combination (e.g., one set of eight channels, one set of six channels, and two single channels).
  • the Multi-Player Playback Device 700 operates in a bonded configuration with a second Multi-Player Playback Device and a third Multi-Player Playback Device, where the second Multi-Player Playback Device and the third Multi-Player Playback Device each have eight audio outputs similar to Multi-Player Playback Device 700.
  • the Multi-Player Playback Device 700, the second Multi-Player Playback Device, and the third Multi-Player Playback Device are configured to implement single logical player configured to output any of (i) one set of twenty four channels of audio, (ii) two sets of twelve channels of audio, (iii) three sets of eight channels of audio, (iv) four sets of six channels of audio, (v) six sets of four channels of audio, (v) eight sets of three channels of audio, (vi) twelve sets of two channels of audio, (vii) twenty four single channels of audio, or (viii) any other suitable combination (e.g., one set of twelve channels of audio, one set of six channels of audio, one set of two channels of audio, and four single channels of audio).
  • two or more Multi-Player Playback Devices can be configured to into a bonded configuration to implement more than one logical player.
  • the Multi-Player Playback Device 700 may be configured to operate in a first alternative bonded configuration with a second Multi-Player Playback Device that has eight audio outputs similar to Multi-Player Playback Device 700.
  • the Multi-Player Playback Device 700 and the second Multi-Player Playback Device are configured to implement two or more logical players configured to output any of (i) one set of sixteen channels of audio, (ii) two sets of eight channels of audio, (iii) four sets of four channels of audio, (iv) eight sets of two channels of audio, (v) sixteen single channels of audio, or (vi) any other suitable combination (e.g., one set of eight channels, one set of six channels, and two single channels).
  • the Player Playback Device 700 operates in a second bonded configuration with a second Multi-Player Playback Device and a third Multi-Player Playback Device, where the second Multi-Player Playback Device and the third Multi-Player Playback Device each have eight audio outputs similar to Multi-Player Playback Device 700.
  • the Multi-Player Playback Device 700, the second Multi- Player Playback Device, and the third Multi-Player Playback Device are configured to implement single logical player configured to output any of (i) one set of twenty four channels of audio, (ii) two sets of twelve channels of audio, (iii) three sets of eight channels of audio, (iv) four sets of six channels of audio, (v) six sets of four channels of audio, (v) eight sets of three channels of audio, (vi) twelve sets of two channels of audio, (vii) twenty four single channels of audio, or (viii) any other suitable combination (e.g., one set of twelve channels of audio, one set of six channels of audio, one set of two channels of audio, and four single channels of audio).
  • FIG. 8A shows a block diagram of an example multi-instance software architecture 800 for a Multi-Player Playback Device according to some embodiments.
  • the multi -instance software architecture 800 of Figure 8 A can be implemented by any of the Multi-Player Playback Device embodiments disclosed herein, including but not limited to Multi-Player Playback Device 700 shown and described with reference to Figure 7.
  • the Multi-Player Playback Device executes a single instance of a player application/process 801 on the Multi- Player Playback Device.
  • the player application/process 801 includes both (i) device specific code 802 that is specific to functions performed by the Multi-Player Playback Device at a device level, and (ii) logical player specific code 803.
  • the Multi-Player Playback Device implements the device specific code 802 to perform functions specific to the physical Multi-Player Playback Device, such as configuring physical network interfaces on the Multi-Player Playback Device, configuring the Multi-Player Playback Device to implement multiple logical players, activating light emitting diodes (LEDs) that indicate various operational statuses of the Multi-Player Playback Device, handling inputs received via a user interface of the Multi-Player Playback Device, etc.
  • LEDs light emitting diodes
  • the Multi-Player Playback Device is configured to implement three logical players.
  • the logical player specific code 803 includes a separate instance of the logical player specific components for each logical player implemented by the Multi-Player Playback Device.
  • the logical player specific code 803 includes (i) three instances of logical player specific audio sourcing components 804a, 804b, and 804c and (ii) three instances of logical player specific audio playback components 806a, 806b, 806c.
  • the logical player specific audio sourcing components 804a, 804b, and 804c and the logical player specific audio playback components 806a, 806b, 806c include software components that are specific to functions performed by each individual logical player implemented by the Multi-Player Playback Device.
  • one instance of the logical player specific audio sourcing components 804a includes (but is not necessarily limited to): (i) a CHSRC (Channel Source) component, (ii) a GM (Group Member) component, (iii) an AVT (Audio Video Transport) component, (iv) a VLI (Virtual Line In) component, and (v) a Transmit component.
  • the software components in the logical player specific audio sourcing components 804a operate in concert with each other (and perhaps other components not shown) to source audio content for playback by an individual logical player that is implemented by the Multi-Player Playback Device.
  • Figure 8B shows a block diagram of an example alternative multi-instance software architecture 850 for a Multi-Player Playback Device according to some embodiments.
  • the multi -instance software architecture 850 of Figure 8B can be implemented by any of the Multi-Player Playback Device embodiments disclosed herein, including but not limited to Multi-Player Playback Device 700 shown and described with reference to Figure 7.
  • the Multi-Player Playback Device executes a separate player/application process 801a, 801b, and 801c for each individual logical player implemented by the Multi-Player Playback Device.
  • the Multi-Player Playback Device is configured to implement three separate logical players.
  • Each of the separate player application/process includes both (i) device specific code 802 that is specific to functions performed by the Multi-Player Playback Device at a device level, and (ii) logical player specific code 803 that is specific to functions performed by the logical player.
  • At least part of the device specific code 802b and 802c is disabled, or perhaps just not called during operation of the Multi-Player Playback Device.
  • the example architecture 900 depicted in Figure 9 includes (i) Audio Streaming and Rendering 910 subsystem, (ii) Advertising, Discovery, and Topology 920 subsystem, (iii) Control Plane 930 subsystem, (iv) Web Server 940 subsystem, and (v) TServer 941 (Thread Server) subsystem.
  • Each of the subsystems has single-instance software components (sometimes alternatively known as single-instance “classes” or singleinstance “data structures” in the software arts).
  • the single-instance software components in the Audio Streaming and Rendering 910 subsystem include (i) Framers 911, (ii) Track Play Monitor 912, (iii) Simple Network Time Protocol (SNTP) Client 913, (iv) SNTP Server 914, (v) Channel Source (CHSRC) 915, (vi) Transmit 916, (vii) Receive 917, (viii) Channel Sink (CHSNK) 918, (ix) Audio Core 919, and (x) and Virtual Line In (VLI) 901.
  • the single-instance software components in the Audio Streaming and Rendering 910 subsystem operate in concert with each other (and perhaps with other components not shown) to source, process, and play audio content for a playback device.
  • the single-instance software components in the Advertising, Discovery, and Topology 920 subsystem include (i) Topology 921, (ii) Device Advertiser 922, (iii) Device Discovery 923, (iv) mDNS (Multicast Domain Name System) 924, and (v) SSDP (Simple Service Discovery Protocol) 925.
  • the single-instance software components in the set of Advertising, Discovery, and Topology 920 subsystem operate in concert with each other (and perhaps with other components not shown) to control how a playback device advertises its capabilities to other playback devices, how a playback device discovers capabilities of other playback devices, and the playback device’s configuration in a playback system and/or configured role in a playback group.
  • the single-instance software components in the Control Plane 930 subsystem include (i) Device Properties 931, (ii) Group Management 932, (iii) Universal Plug and Play (UPnP) 933, (iii) Audio Video Transport (AVTransport) 935, (iv) Rendering Control 936, and (v) control plane entity 934.
  • the single-instance software components in the Control Plane 930 subsystem operate in concert with each other (and perhaps with other components not shown) to facilitate the exchange of configuration and control information between the playback device and (i) other playback devices in the same playback system and (ii) controller devices/sy stems configured to control the playback device.
  • the webserver subsystem 940 includes a single-instance software component called a thread server (TServer) 941.
  • the TServer 941 is a software component (e.g., a data structure or class) that holds, among other data, context for certain worker threads.
  • One function performed by the single-instance TServer 941 software component is to listen for connection requests from other network devices, e.g., UPnP requests or other requests. As the playback device receives connection requests, the listen thread executed by the TServer 941 evaluates the request, accepts the request (if appropriate), and establishes a connection based on the connection request.
  • FIG. 10 shows a block diagram of an example multi-instance software architecture 1000 for a Multi-Player Playback Device according to some embodiments.
  • the multi -instance software architecture 1000 of Figure 10 can be implemented by any of the Multi-Player Playback Device embodiments disclosed herein, including but not limited to Multi-Player Playback Device 700 shown and described with reference to Figure 7.
  • any of the Multi-Player Playback Device embodiments disclosed herein can implement any of the of the embodiments of the multi -instance software architecture 1000 described herein to implement any of the Multi-Player Playback Device features disclosed herein, including but not limited to any of the grouped and/or Area Zone features and functions disclosed above.
  • the example multi-instance software architecture 1000 in Figure 10 includes many of the same software components as the single-instance software architecture 900 of Figure 9.
  • the multi -instance software architecture 1000 of Figure 10 also includes a similar (i) Audio Streaming and Rendering 1010 subsystem, (ii) Advertising, Discovery, and Topology 1020 subsystem, and (iii) Control Plane 1030 subsystem.
  • the multi -instance software architecture 1000 includes a new Media Player 1060 subsystem that includes several multi-instance variants of some of the single-instance software components implemented in the single-instance software architecture 900 ( Figure 9).
  • the multi -instance software architecture 1000 also includes a new multi -instance variant of the TServer 1041 software component.
  • the new multi -instance Media Player 1060 subsystem and multi-instance TServer 1041 software components are similar to the logical player specific code 803, whereas the other subsystems and their corresponding software components are akin to the device specific code 802.
  • Audio Streaming and Rendering 1010 the Audio Streaming and Rendering 1010
  • Advertising, Discovery, and Topology 1020 the Advertising, Discovery, and Topology 1020
  • Control Plane 1030 subsystems are adapted to provide features and functions that enable the Multi- Player Playback Device to support multiple logical players.
  • the multi-instance software architecture 1000 is configured in some embodiments to (i) instantiate a new multi -instance Media Player 1060 software subsystem and a new TServer 1041 software component as part of adding/implementing a new logical player, and (ii) delete an existing multi-instance Media Player 1060 software subsystem and an existing TServer 1041 software component as part of deleting/terminating a logical player.
  • the multi-instance software architecture 1000 is configured to statically allocate one or more instances of the Media Player 1060 software subsystem and TServer 1041 software components at startup based at least in part on how many logical players the multi-instance software architecture 1000 needs to implement.
  • the Multi-Player Playback Device is configured to implement three logical players.
  • the multi -instance software architecture 1000 includes a first instance 1060a of the Media Players software component for a first logical player, a second instance 1060b of the Media Players software component for a second logical player, and a third instance 1060c of the Media Players software component for a third logical player.
  • the multi-instance software architecture 1000 also includes a first TServer 1041a for the first logical player, a second TServer 1041b for the second logical player, and a third TServer 1041c for the third logical player.
  • a Multi-Player Playback Device can implement more or fewer than three logical players.
  • the multi-instance variants of the software components implemented in the multi -instance Media Player 1060 subsystem of multi-instance software architecture 1000 differ from their single-instance counterparts in single-instance software architecture 900 ( Figure 9) in that the multi -instance software components that the Multi-Player Playback Device instantiates for an individual logical player are configured to control one or more functions of that individual logical player.
  • the multi -instance software components are sometimes referred to as “logical player specific” or “player-specific” software components.
  • the one or more functions implemented by a player-specific software component for that individual logical player are isolated from any other logical player implemented by the physical playback device.
  • These player-specific software components for a particular logical player are considered isolated from other logical players because functions implemented by the player-specific software components for that particular logical player do not affect the configuration or operation of any other logical player implemented by the Multi-Player Playback Device.
  • the multi -instance software architecture 1000 depicted in Figure 10 reflects a Multi-Player Playback Device configured to implement three logical players.
  • some of the software components in the Audio Streaming and Rendering 1010 subsystem, the Advertising, Discovery, and Topology 1020 subsystem, and the Control Plane 1030 subsystem implement device-specific single-instance software components for the Multi-Player Playback Device.
  • the devicespecific single-instance software components implemented in subsystems 1010, 1020, and 1030 are configured to control one or more functions of the physical Multi-Player Playback Device at the device level.
  • the device-specific single-instance software components implemented in the multi -instance software architecture 1000 implement certain features and functions adapted to facilitate certain aspects of the player-specific software components as described further below.
  • the software components in the Audio Streaming and Rendering 1010 subsystem include (i) Framers 1011, (ii) SNTP Server 1014, (iii) Audio Core 1019, and (iv) and Virtual Line In (VLI) 1001.
  • the software components in the Audio Streaming and Rendering 1010 subsystem operate in concert with each other (and perhaps with other components not shown) to obtain audio content for the logical players implemented by the Multi-Player Playback Device.
  • the software components in the Advertising, Discovery, and Topology 1020 subsystem include (i) Topology 1021, (ii) Device Advertiser 1022, (iii) Device Discovery 1023, (iv) mDNS (Multicast Domain Name System) 1024, and (v) SSDP (Simple Service Discovery Protocol) 1025.
  • the software components in the set of Advertising, Discovery, and Topology 1020 subsystem operate in concert with each other (and perhaps with other components not shown) to control, among other features, (i) how the Multi-Player Playback Device advertises its capabilities to other devices in a network (e.g., playback devices, other Multi-Player Playback Devices, logical players, controller devices, and other network devices), and (ii) how other network devices in the network discover capabilities of the Multi-Player Playback Device, including the Multi-Player Playback Device’s configuration in a playback system (including the configurations of its logical players) and/or configured role in a playback group (including the configured roles of its logical players).
  • a network e.g., playback devices, other Multi-Player Playback Devices, logical players, controller devices, and other network devices
  • other network devices in the network discover capabilities of the Multi-Player Playback Device including the Multi-Player Playback Device’s configuration in a playback system (including the configurations of its logical players)
  • the device-specific single-instance software components executed in the multi -instance software architecture 1000 implement certain features and functions adapted to facilitate certain aspects of the player-specific software components.
  • the Multi-Player Playback Device In addition to device-specific advertising, discovery, and topology functions performed for the Multi-Player Playback Device at the device level, the Multi-Player Playback Device also handles player-specific advertising, discovery, and topology functions for each of its logical players on a logical player level.
  • the Multi-Player Playback Device executes software components in the Advertising, Discovery, and Topology 1020 subsystems in connection with advertising the Unique Logical Player Identifier (ULPI) (described further below) for each logical player implemented by the Multi-Player Playback Device.
  • ULPI Unique Logical Player Identifier
  • the Multi-Player Playback Device advertises the ULPI for each logical player via one or more (i) Simple Service Discovery Protocol (SSDP) messages or (ii) multicast Domain Name System (mDNS) messages.
  • SSDP Simple Service Discovery Protocol
  • mDNS multicast Domain Name System
  • advertising each logical player’s ULPI to the playback network via SSDP and/or mDNS messages enables other playback entities (i.e., playback devices, other Multi-Player Playback Devices, and/or other logical players) to update their topology information to include the logical player (and its corresponding ULPI).
  • other playback entities in the playback system include the logical players implemented by the Multi-Player Playback Device and their corresponding ULPIs in their topology tables, then the other playback entities can transmit packets to and/or receive packets from the logical players implemented by the Multi-Player Playback Device.
  • the topology information that the Multi- Player Playback Device manages for each logical player includes (but is not limited), for example, one or more (or all) of (i) networking and topology information for the Multi- Player Playback Device that implements the logical player, e.g., (ii) networking and topology information for the other logical players implemented by the Multi-Player Playback Device, (iii) networking and topology information for other physical playback devices configured to operate in a playback system with the Multi-Player Playback Device, (iv) networking and topology information for other logical players implemented by other Multi-Player Playback Devices configured to operate in the playback system with the Multi-Player Playback Device, and (v) networking and/or topology information for one or more controller devices configured to control playback entities in the playback system.
  • networking and topology information for the Multi- Player Playback Device that implements the logical player e.g., (ii) networking and topology information for the other logical players implemented by the Multi-Player Playback Device,
  • the multi-instance software architecture 1000 also includes Media Player 1060 subsystem.
  • Media Player 1060 subsystem includes multi-instance versions of certain software components that were implemented by the Audio Streaming and Rendering 910 subsystem ( Figure 9) and Control Plane 930 subsystem ( Figure 9).
  • media rendering control for an individual logical player implemented via a player-specific media rendering software component for that individual logical player does not affect how any other logical player implemented by the Multi-Player Playback Device renders media content.
  • the Media Player 1060a subsystem instantiated by the Multi-Player Playback Device for the first logical player includes a media rendering software component for controlling media rendering by the first logical player
  • the Media Player 1060b subsystem instantiated by the Multi-Player Playback Device for the second logical player includes a media rendering software component for controlling media rendering by the second logical player
  • the Media Player 1060c subsystem instantiated by the Multi- Player Playback Device for the third logical player includes a media rendering software component for controlling media rendering by the third logical player.
  • One advantage of using a single TServer instance for handling messaging for all of the logical players is that running a single TServer instance can be, in some scenarios, less computationally intensive than running several TServer instances.
  • using multiple TServer instances i.e., a separate TServer instance for each logical player
  • One challenge with implementing the above-described player-specific software components for logical players implemented by a Multi-Player Playback Device is how to address the various multi -instance software components executing processes for the different logical players implemented by a single Multi-Player Playback Device.
  • playback devices often include a unique identifier, sometimes referred to as a UUID (Unique Identifier) or UDN (Unique Device Name).
  • This UUID can include one or more components such as: (i) a prefix corresponding to the playback device manufacturer (e.g., “SONOS ”), (ii) the media access control (MAC) address of the playback device (e.g., “48A6B82E62E8”), and (iii) a suffix that includes the base port number that the Web Server software component listens on to process incoming packets addressed to the playback device (e.g., port 1400).
  • SONOS the media access control
  • MAC media access control
  • suffix that includes the base port number that the Web Server software component listens on to process incoming packets addressed to the playback device (e.g., port 1400).
  • the UUID for the playback device would be: SONOS 48A6B82E62E81400.
  • playback devices can implement different identification schemes, and even for playback devices that may implement the same (or a similar) identification scheme as the one described above, playback devices made by different manufacturers will have different manufacturer names, each playback device has a unique MAC address, and playback devices can be configured to listen to port numbers other than 1400 (e.g., 1443, 1843, or other ports).
  • the Multi-Player Playback Device can be associated with a UUID as described above.
  • the Multi-Player Playback Device can implement multiple logical players, there is a need to distinguish between each of the logical players implemented by the Multi-Player Playback Device.
  • other devices in a playback network need a way to send and receive data to and from each of the logical players implemented by the Multi-Player Playback Device.
  • each logical player implemented by a Multi- Player Playback Device has a Unique Logical Player Identifier (ULPI) that incorporates a corresponding unique interface identifier of a corresponding network interface of the Multi- Player Playback Device.
  • the ULPI for each logical player comprises the unique interface identifier of a network interface of the Multi-Player Playback Device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number.
  • the Multi-Player Playback Device could generate and assign (i) a ULPI of SONOS 48A6B82E62E81400.1 to the first logical player, (ii) a ULPI of SONOS 48A6B82E62E81400.2 to the second logical player, and (iii) a ULPI of SONOS 48A6B82E62E81400.3 to the third logical player.
  • each logical player implemented by the Multi-Player Playback Device is configured to listen on a different UPnP port, each logical player’s corresponding UPnP port can be combined with the devicespecific UUID of the Multi-Player Playback Device to create the ULPI for each logical player.
  • the Multi-Player Playback Device can generate a ULPI for each logical player by appending the UPnP port used by each logical player to the end of the UUID for the Multi-Player Playback Device. So if the first logical player is configured to listen on UPnP port 1400, the second logical player is configured to listen on UPnP port 1500, and the third logical player is configured to listen on UPnP port 1600, then in this
  • the Multi-Player Playback Device could generate and assign (i) a ULPI of SONOS 48A6B82E62E81400 (corresponding to port 1400) to the first logical player, (ii) a ULPI of SONOS 48A6B82E62E81500 (corresponding to port 1500) to the second logical player, and (iii) a ULPI of SONOS 48A6B82E62E81600 (corresponding to port 1600) to the third logical player.
  • Ports 1400, 1500, and 1600 are used in the example above for illustration purposes. In operation, embodiments may use any other suitable port numbers instead.
  • the ULPI for an individual logical player additionally or alternatively includes a compound key formed from one or more components or parts.
  • the compound key can be formed from one or more (or all) of (i) a port identifier, (ii) a Secure Services Client (SSC) port, (iii) Mutual Transport Layer Security (MTLS) port, (iv) a zone identifier that identifies a playback zone in which the logical player is configured to operate, (v) a group identifier that identifies a playback group in which the logical player is configured to operate, (vi) a network listening ports, and/or (vii) internal integer indexing.
  • the ULPI for a logical player can be formed by combining some or all of the foregoing data (or portions thereof) along with any other suitable data into a string that is sufficient to uniquely identify the logical player within the playback network.
  • individual logical players are additionally or alternatively (i) addressable by a digital signal processor (DSP) via a zone identifier associated with the logical player, (ii) addressable by devices implementing a control plane process (e.g., 1034) via a Unique Logical Player Identifier (ULPI) corresponding to the logical player, (iii) addressable by devices compliant with the Universal Plug and Play (UPnP) protocol via a port associated with the logical player.
  • DSP digital signal processor
  • ULPI Unique Logical Player Identifier
  • some Multi-Player Playback Device embodiments include a device-specific routing component (e.g., router component 720 shown and described with reference to Figure 7) that is configured to handle both (i) packets/frames containing data intended for the Multi-Player Playback Device (i.e., devicespecific packets) and (ii) packets/frames containing data intended for individual logical players implemented by the Multi-Player Playback Device (i.e., player-specific packets).
  • Data intended for individual logical players contained within player-specific packets/frames includes, for example, (i) control data for individual logical players implemented by the Multi-Player Playback Device and (ii) media content for individual logical players implemented by the Multi-Player Playback Device.
  • router component 720 (e.g., functioning as a logical player data routing component) is configured to route logical player data received via the one or more network interfaces 706 of the Multi-Player Playback Device 700 to one of a plurality of player-specific media transport components (e.g., in Media Player 1060 subsystem) based at least in part on the ULPI associated with the player-specific packets and/or frames.
  • a plurality of player-specific media transport components e.g., in Media Player 1060 subsystem
  • Method 1100 includes block 1102, which comprises implementing a plurality of logical players via a physical playback device, wherein each logical player has a unique player identifier, and wherein the unique player identifier for each logical player incorporates a corresponding unique interface identifier of a corresponding network interface of the physical playback device.
  • the physical playback device can be any of the Multi-Player Playback Device(s) disclosed herein.
  • each unique player identifier for each logical player comprises the unique interface identifier of a network interface of the physical playback device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number.
  • UFP Universal Plug and Play
  • the player-specific software components of block 1104 additionally or alternatively comprises a thread server component, wherein the thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player, and wherein context stored for use by worker threads executing tasks for the individual logical player is not shared with thread server components executing tasks for any other logical player implemented by the physical playback device
  • the player-specific software components of block 1104 additionally or alternatively comprises a media rendering component, wherein the media rendering component for an individual logical player is configured to render media content addressed to the unique player identifier of the individual logical player, and wherein the media content rendered by the media rendering component for the individual logical player is isolated from media content rendering of any other logical player implemented by the physical playback device.
  • Method 1100 further includes block 1106, which comprises executing a set of device-specific software components, wherein each device-specific software component is configured to control one or more functions of the physical playback device.
  • the device-specific software components of block 1106 comprises a logical player data routing component, wherein the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the physical playback device to one of a plurality of player-specific media transport components based at least in part on a unique player identifier associated with the logical player data.
  • the logical player data comprises one or more of (i) control data for individual logical players implemented by the physical playback device and (ii) media content for individual logical players implemented by the physical playback device.
  • the device-specific software components of block 1106 additionally or alternatively comprises a topology component accessible by logical players implemented by the physical playback device, wherein the topology component is configured to store network topology information relating to (i) the physical playback device, (ii) the logical players implemented by the physical playback device, (iii) other physical playback devices configured to operate in a playback system with the physical playback device, and (iv) other logical players implemented by the other physical playback devices configured to operate in the playback system with the physical playback device.
  • Example 1 A physical playback device comprising: (i) one or more network interfaces, wherein each network interface has a unique interface identifier; (ii) one or more processors; and (iii) tangible, non-transitory computer-readable media having program instructions stored therein.
  • Example 2 The physical playback device of Example 1, wherein each unique player identifier for each logical player comprises the unique interface identifier of a network interface of the physical playback device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number.
  • UFP Universal Plug and Play
  • Example 3 The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a volume control component, wherein the volume control component is configured to control a playback volume of the individual logical player, and wherein volume adjustments of the individual logical player implemented via the volume control component for the individual logical player do not affect a playback volume level of any other logical player implemented by the physical playback device.
  • the set of player-specific software components for an individual logical player comprises a volume control component, wherein the volume control component is configured to control a playback volume of the individual logical player, and wherein volume adjustments of the individual logical player implemented via the volume control component for the individual logical player do not affect a playback volume level of any other logical player implemented by the physical playback device.
  • Example 4 The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a thread server component, wherein the thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player, and wherein context stored for use by worker threads executing tasks for the individual logical player is not shared with thread server components executing tasks for any other logical player implemented by the physical playback device.
  • the set of player-specific software components for an individual logical player comprises a thread server component, wherein the thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player, and wherein context stored for use by worker threads executing tasks for the individual logical player is not shared with thread server components executing tasks for any other logical player implemented by the physical playback device.
  • Example 5 The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a media transport component, wherein the media transport component for an individual logical player is configured to execute media transport commands addressed to the unique player identifier of the individual logical player, and wherein media transport commands executed by the media transport component for the individual logical player do not affect media transport activity of any other logical player implemented by the physical playback device.
  • the set of player-specific software components for an individual logical player comprises a media transport component, wherein the media transport component for an individual logical player is configured to execute media transport commands addressed to the unique player identifier of the individual logical player, and wherein media transport commands executed by the media transport component for the individual logical player do not affect media transport activity of any other logical player implemented by the physical playback device.
  • Example 6 The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a media rendering component, wherein the media rendering component for an individual logical player is configured to render media content addressed to the unique player identifier of the individual logical player, and wherein the media content rendered by the media rendering component for the individual logical player is isolated from media content rendering of any other logical player implemented by the physical playback device.
  • the set of player-specific software components for an individual logical player comprises a media rendering component, wherein the media rendering component for an individual logical player is configured to render media content addressed to the unique player identifier of the individual logical player, and wherein the media content rendered by the media rendering component for the individual logical player is isolated from media content rendering of any other logical player implemented by the physical playback device.
  • Example 7 The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of device-specific software components comprises a logical player data routing component, wherein the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the physical playback device to one of a plurality of playerspecific media transport components based at least in part on a unique player identifier associated with the logical player data.
  • the set of device-specific software components comprises a logical player data routing component, wherein the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the physical playback device to one of a plurality of playerspecific media transport components based at least in part on a unique player identifier associated with the logical player data.
  • Example 8 The physical playback device of Example 7 (individually or in combination with any other suitable preceding Example), wherein the logical player data comprises one or more of (i) control data for individual logical players implemented by the physical playback device and (ii) media content for individual logical players implemented by the physical playback device.
  • Example 9 The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the tangible, non-transitory computer-readable media further has program instructions stored therein, wherein the program instructions, when executed by the one or more processors, cause the physical playback device to perform functions comprising for each logical player, advertising the unique player identifier of the logical player via on or more (i) Simple Service Discovery Protocol (SSDP) messages or (ii) multicast Domain Name System (mDNS) messages.
  • SSDP Simple Service Discovery Protocol
  • mDNS multicast Domain Name System
  • Example 10 The physical playback device of Example 7 (individually or in combination with any other suitable preceding Example), wherein the set of device-specific software components comprises a topology component accessible by logical players implemented by the physical playback device, wherein the topology component is configured to store network topology information relating to (i) the physical playback device, (ii) the logical players implemented by the physical playback device, (iii) other physical playback devices configured to operate in a playback system with the physical playback device, and (iv) other logical players implemented by the other physical playback devices configured to operate in the playback system with the physical playback device.
  • the set of device-specific software components comprises a topology component accessible by logical players implemented by the physical playback device, wherein the topology component is configured to store network topology information relating to (i) the physical playback device, (ii) the logical players implemented by the physical playback device, (iii) other physical playback devices configured to operate in a playback system with the physical playback device, and (iv
  • Example 11 The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the unique player identifier for an individual logical player comprises a compound key, wherein the compound key comprises one or more of (i) a port identifier, (ii) a Secure Services Client (SSC) port, (iii) Mutual Transport Layer Security (MTLS) port, (iv) zone identifier, or (v) group identifier.
  • SSC Secure Services Client
  • MTLS Mutual Transport Layer Security
  • Example 12 The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein an individual logical player is (i) addressable by digital signal processors (DSP) via a zone identifier associated with the logical player, (ii) addressable by control plane entities via a Unique Logical Player Identifier (LUPI) corresponding to the logical player, (iii) addressable by network devices compliant with a Universal Plug and Play (UPnP) protocol via a port associated with the logical player.
  • DSP digital signal processors
  • LUPI Unique Logical Player Identifier
  • UPN Universal Plug and Play
  • Example 13 Tangible, non-transitory computer-readable media comprising program instructions, wherein the program instructions, when executed by one or more processors, cause a physical playback device to perform functions comprising: (A) implementing a plurality of logical players via the physical playback device, wherein each logical player has a unique player identifier, and wherein the unique player identifier for each logical player incorporates a corresponding unique interface identifier of a corresponding network interface of the physical playback device; (B) for each logical player, executing a set of player-specific software components, wherein the set of player-specific software components for an individual logical player is configured to control one or more functions of that individual logical player, wherein functions implemented by a player-specific software component for that individual logical player are isolated from any other logical player implemented by the physical playback device; and (C) executing a set of device-specific software components, wherein each device-specific software component is configured to control one or more functions of the physical playback device.
  • Example 14 The tangible, non-transitory computer-readable media of Example 13, wherein each unique player identifier for each logical player comprises the unique interface identifier of a network interface of the physical playback device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number.
  • UFP Universal Plug and Play
  • Example 15 The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a volume control component, wherein the volume control component is configured to control a playback volume of the individual logical player, and wherein volume adjustments of the individual logical player implemented via the volume control component for the individual logical player do not affect a playback volume level of any other logical player implemented by the physical playback device.
  • the set of player-specific software components for an individual logical player comprises a volume control component, wherein the volume control component is configured to control a playback volume of the individual logical player, and wherein volume adjustments of the individual logical player implemented via the volume control component for the individual logical player do not affect a playback volume level of any other logical player implemented by the physical playback device.
  • Example 16 The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a thread server component, wherein the thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player, and wherein context stored for use by worker threads executing tasks for the individual logical player is not shared with thread server components executing tasks for any other logical player implemented by the physical playback device.
  • the set of player-specific software components for an individual logical player comprises a thread server component, wherein the thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player, and wherein context stored for use by worker threads executing tasks for the individual logical player is not shared with thread server components executing tasks for any other logical player implemented by the physical playback device.
  • Example 17 The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a media transport component, wherein the media transport component for an individual logical player is configured to execute media transport commands addressed to the unique player identifier of the individual logical player, and wherein media transport commands executed by the media transport component for the individual logical player do not affect media transport activity of any other logical player implemented by the physical playback device.
  • the set of player-specific software components for an individual logical player comprises a media transport component
  • the media transport component for an individual logical player is configured to execute media transport commands addressed to the unique player identifier of the individual logical player, and wherein media transport commands executed by the media transport component for the individual logical player do not affect media transport activity of any other logical player implemented by the physical playback device.
  • Example 18 The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a media rendering component, wherein the media rendering component for an individual logical player is configured to render media content addressed to the unique player identifier of the individual logical player, and wherein the media content rendered by the media rendering component for the individual logical player is isolated from media content rendering of any other logical player implemented by the physical playback device.
  • Example 19 The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of device-specific software components comprises a logical player data routing component, wherein the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the physical playback device to one of a plurality of player-specific media transport components based at least in part on a unique player identifier associated with the logical player data.
  • the set of device-specific software components comprises a logical player data routing component, wherein the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the physical playback device to one of a plurality of player-specific media transport components based at least in part on a unique player identifier associated with the logical player data.
  • Example 20 A method comprising: (A) implementing a plurality of logical players via a physical playback device, wherein each logical player has a unique player identifier, and wherein the unique player identifier for each logical player incorporates a corresponding unique interface identifier of a corresponding network interface of the physical playback device; (B) for each logical player, executing a set of player-specific software components, wherein the set of player-specific software components for an individual logical player is configured to control one or more functions of that individual logical player, wherein functions implemented by a player-specific software component for that individual logical player are isolated from any other logical player implemented by the physical playback device; and (C) executing a set of device-specific software components, wherein each device-specific software component is configured to control one or more functions of the physical playback device.
  • 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 an 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 example configurations mutually exclusive of other example configurations.
  • the example configurations described herein, explicitly and implicitly understood by one skilled in the art can be combined with other example configurations.
  • At least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing For Digital Recording And Reproducing (AREA)

Abstract

Disclosed embodiments relate to Multi-Player Playback Devices and logical players implemented thereby. Some examples include a Multi-Player Playback Device implementing a plurality of logical players. In some instances, the Multi-Player Playback Device executes (i) player-specific software components for each logical player that are configured to control one or more functions of that individual logical player, and (ii) device-specific software components that are configured to control one or more functions of the Multi-Player Playback Device at the device level.

Description

MULTI-INSTANCE ARCHITECTURE FOR MULTI-PLAYER PLAYBACK DEVICE
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional App. 63/571,312, titled “Multi-Instance Architecture for Multi-Player Playback Device” (23-1007p), filed on Mar. 28, 2024, and currently pending. The entire content of U.S. Provisional App. 63/571,312 are incorporated herein by reference
[0002] This application is related to and incorporates by reference the entire contents of the following applications: (i) Patent Cooperation Treaty (PCT) Application PCT/US2023/034170, titled “Playback System Architectures and Area Zone Configurations” (21-0703-PCT), filed on Sep. 29, 2023, and currently pending; (ii) U.S. Provisional App. 63/377,948, titled “Playback System Architecture” (21-0703p), filed on Sep. 30, 2022, and now expired; (iii) U.S. Provisional App. 63/377,899, titled “Multichannel Content Distribution” (22-0207p), filed on Sep. 30 2022, and now expired; (iv) U.S. Provisional App. 63/377,967, titled “Playback Systems with Dynamic Forward Error Correction” (22-0401p), filed on Sep. 30, 2022, and now expired; (v) U.S. Provisional App. 63/377,978, titled “Broker/ Sub scriber Model for Information Sharing and Management Among Connected Devices” (22-0606Ap), filed on Sep. 30, 2022, and now expired; (vi) U.S. Provisional App. 63/377,979, titled “Multiple Broker Deployment for Information Sharing and Management Among Connected Devices” (22-0606Bp), filed on Sep. 30, 2022, and now expired; (vii) U.S. Provisional App. 63/502,347, titled “Area Zones” (22-1002p), filed on May 15, 2023, and now expired; and (viii) U.S. Provisional App. 63/513,735, titled “State Information Exchange Among Connected Devices” (23-0306p), filed on Jul. 14, 2023, and now expired. The entire contents of Apps. PCT/US2023/034170; 63/377,948; 63/377,899; 63/377,967; 63/377,978; 63/377,979; 63/502,347; and 63/513,735 are incorporated herein by reference.
[0003] Aspects of the features and functions disclosed and described in the above-identified applications can be used in combination with the examples disclosed and described herein (and with each other in some instances) to improve the functionality and performance of playback devices, both individually and configured into playback systems comprising multiple playback devices, including but not limited to Multi-Player Playback Devices and systems comprising Multi-Player Playback Devices. FIELD OF THE DISCLOSURE
[0004] The present disclosure is related to consumer goods and, in some more particular examples, to methods, systems, products, features, services, and other elements relating to media playback systems, media playback devices, methods of operating media playback systems and devices, and various features and aspects thereof.
BACKGROUND
[0005] Options for accessing and listening to digital audio in an out-loud setting were limited until in 2002, when SONOS, Inc. began development of a new type of playback system. Sonos then filed one of its first patent applications in 2003, titled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering its first media playback systems for sale in 2005. The Sonos Wireless Home Sound System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a controller (e.g., smartphone, tablet, computer, voice input device), individuals can play most any music they like in any room having a networked playback device. Media content (e.g., songs, podcasts, video sound) can be streamed to playback devices such that each room with a playback device can play back corresponding different media content. In addition, rooms can be grouped together for synchronous playback of the same media content, and/or the same media content can be heard in all rooms synchronously.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings, as listed below. A person skilled in the relevant art will understand that the features shown in the drawings are for purposes of illustrations, and variations, including different and/or additional features and arrangements thereof, are possible.
[0007] Figure 1 A shows a partial cutaway view of an environment having a media playback system configured in accordance with aspects of the disclosed technology.
[0008] Figure IB shows a schematic diagram of the media playback system of Figure 1 A and one or more networks.
[0009] Figure 1C shows a block diagram of a playback device.
[0010] Figure ID shows a block diagram of a playback device.
[0011] Figure IE shows a block diagram of a network microphone device. [0012] Figure IF shows a block diagram of a network microphone device.
[0013] Figure 1G shows a block diagram of a playback device.
[0014] Figure 1H shows a partially schematic diagram of a control device.
[0015] Figures 1-1 through IL show schematic diagrams of corresponding media playback system zones.
[0016] Figure IM shows a schematic diagram of media playback system areas.
[0017] Figure 2A shows a front isometric view of a playback device configured in accordance with aspects of the disclosed technology.
[0018] Figure 2B shows a front isometric view of the playback device of Figure 3 A without a grille.
[0019] Figure 2C shows an exploded view of the playback device of Figure 2A.
[0020] Figure 3 A shows a front view of a network microphone device configured in accordance with aspects of the disclosed technology.
[0021] Figure 3B shows a side isometric view of the network microphone device of Figure 3A.
[0022] Figure 3C shows an exploded view of the network microphone device of Figures 3A and 3B.
[0023] Figure 3D shows an enlarged view of a portion of Figure 3B.
[0024] Figure 3E shows a block diagram of the network microphone device of
Figures 3A-3D
[0025] Figure 3F shows a schematic diagram of an example voice input.
[0026] Figures 4A-4D show schematic diagrams of a control device in various stages of operation in accordance with aspects of the disclosed technology.
[0027] Figure 5 shows front view of a control device.
[0028] Figure 6 shows a message flow diagram of a media playback system.
[0029] Figure 7 shows a functional block diagram of an example Multi-Player
Playback Device according to some embodiments.
[0030] Figure 8A shows a block diagram of an example multi-instance software architecture for a Multi-Player Playback Device according to some embodiments.
[0031] Figure 8B shows a block diagram of an example alternative multi-instance software architecture for a Multi-Player Playback Device according to some embodiments.
[0032] Figure 9 shows a block diagram of an example single-instance system architecture for a playback device. [0033] Figure 10 shows block diagram of an example multi -instance software architecture for a Multi-Player Playback Device according to some embodiments.
[0034] Figure 11 shows an example method implemented by a Multi-Player Playback Device according to some embodiments.
[0035] The drawings are for the purpose of illustrating example configurations, but those of ordinary skill in the art will understand that the technology disclosed herein is not limited to the arrangements and/or instrumentality shown in the drawings.
DETAILED DESCRIPTION
I. Overview
[0036] Existing playback devices, examples of which include Sonos’ s intelligent playback devices, can be used to implement different types of groupings of playback devices configured to play audio content together with each other in a groupwise fashion. Playback groupings implemented with intelligent playback devices such as the playback devices available from Sonos are very flexible in terms of configuration options and the ability to play many different types of audio content, thereby enabling many different groupwise configurations for listening to many different types of audio content in many different types of listening environments.
[0037] The present application discloses and describes aspects of a new type of physical playback device referred to herein as a “Multi-Player Playback Device.” The Multi- Player Playback Devices disclosed herein provide enhanced flexibility and scalability for individual and groupwise playback as compared to existing playback devices via, among other features, implementation of “logical players.”
[0038] Aspects of Multi-Player Playback Devices and the logical players implemented by Multi-Player Playback Devices are useful (although not strictly required) when implementing a new type of groupwise playback known as “Area Zones.” Some aspects of Area Zones that are relevant to Multi-Player Playback Devices and logical players are disclosed herein. Further aspects of Area Zones are disclosed and described in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the entire contents of which are incorporated herein by reference. Although Multi-Player Playback Devices and logical players implemented by Multi-Player Playback Devices provide several advantages for Area Zone configurations, Multi-Player Playback Devices and the logical players implemented by Multi-Player Playback Devices provide similar and additional advantages for individual playback configurations and other grouped configurations, too.
[0039] However, implementing logical players via Multi-Player Playback Devices presents several technical challenges that did not exist with traditional playback devices including but not necessarily limited to, advertisement and discovery, control, and audio playback.
[0040] For example, conventional playback devices are configured to play a single audio stream, and as a result, the software architecture is designed for a single playback device to play a single audio stream, sometimes referred to herein as a “single-instance” software architecture. From an advertisement and discovery standpoint, an individual playback device can advertise its playback capabilities to other playback devices and discover the playback capabilities of other playback devices. From a control standpoint, an individual playback device can exchange control information with a controller device (e.g., a smartphone running a controller application) configured to control the configuration and operation of the individual playback device. And from an audio playback standpoint, an individual playback device can receive, process, and play back a single audio stream (which may, in some instances, correspond to a multi-channel audio stream, but a single audio stream nonetheless).
[0041] However, and as described in more detail herein, a Multi-Player Playback Device is configured to support one or more “logical players,” where each player can be configured to play a different audio stream. So, from an advertisement and discovery standpoint, a Multi-Player Playback Device advertises the playback capabilities of each of its implemented logical players to other devices on the network, including other playback entities, e.g., playback devices, other Multi-Player Playback Devices, other logical players, and so on. From a control standpoint, a Multi-Player Playback Device exchanges control information with a controller device (e.g., a smartphone running a controller application or other controller device(s) or system(s)) configured to control the configuration and operation of each logical player implemented by the Multi-Player Playback Device. And from an audio playback standpoint, a Multi-Player Playback Device receives, processes, and plays back an audio stream for each logical player implemented by the Multi-Player Playback Device (or at least handles/manages the playback of audio streams for each logical player implemented by the Multi-Player Playback Device). For example, if a Multi-Player Playback Device is configured with eight different logical players that are each configured to play a different audio stream, then the Multi-Player Playback Device will need to receive, process, and play eight different audio streams (i.e., one audio stream for each of the eight logical players). In this respect, the Multi-Player Playback Device plays back (or at least handles/manages the playback) of audio streams for each of its configured logical players.
[0042] To support the complexities arising when a single physical Multi-Player Playback Device supports multiple logical players, some Multi-Player Playback Device embodiments disclosed herein implement a “multi-instance” software architecture that differs from the “single instance” software architecture implemented by conventional playback devices.
[0043] Accordingly, in some embodiments, a physical Multi-Player Playback Device comprises (i) one or more network interfaces, wherein each network interface has a unique interface identifier, (ii) one or more processors, and (iii) tangible, non-transitory computer- readable media having program instructions stored therein, wherein the program instructions, when executed by the one or more processors, cause the physical Multi-Player Playback Device to perform any of the Multi-Player Playback Device functions disclosed herein. [0044] For example, in some embodiments, the Multi-Player Playback Device is configured to perform functions comprising (i) implementing a plurality of logical players via the physical Multi-Player Playback Device, where each logical player has a Unique Logical Player Identifier (ULPI), and where the ULPI for each logical player incorporates a corresponding unique interface identifier of a corresponding network interface of the physical Multi-Player Playback Device, (ii) for each logical player, execute a set of player-specific software components, where the set of player-specific software components for an individual logical player is configured to control one or more functions of that individual logical player, and where functions implemented by a player-specific software component for that individual logical player are isolated from any other logical player implemented by the physical Multi- Player Playback Device, and (iii) execute a set of device-specific software components, where each device-specific software component is configured to control one or more functions of the physical Multi-Player Playback Device. In some embodiments, executing player-specific software components to control one or more functions of a specific individual logical player does not affect any other logical player implemented by the physical Multi- Player Playback Device.
[0045] In some examples, each ULPI for each logical player comprises the unique interface identifier of a network interface of the physical Multi-Player Playback Device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number. [0046] In some embodiments, the set of player-specific software components for an individual logical player comprises a player-specific volume control component that is configured to control a playback volume of the individual logical player. In operation, volume adjustments of the individual logical player implemented via the player-specific volume control component for the individual logical player do not affect a playback volume level of any other logical player implemented by the physical Multi-Player Playback Device. [0047] For example, for a Multi-Player Playback Device implementing two logical players (i.e., a first logical player and a second logical player), the player-specific volume control components (one for each of the first logical player and the second logical player) enable the Multi-Player Playback Device to adjust the volume of the first logical player independently of the volume of the second logical player, and vice versa. Since the volume levels of the first logical player and the second logical player are independently adjustable via the player-specific volume control components, adjustments to the volume level of the first logical player do not affect or otherwise change the volume level of the second logical player, and adjustments to the volume level of the second logical player do not affect or otherwise change the volume level of the first logical player.
[0048] In some embodiments, the set of player-specific software components for an individual logical player additionally or alternatively comprises a player-specific thread server component. The player-specific thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player. In operation, context stored for use by worker threads executing tasks for the individual logical player is isolated and/or not shared with player-specific thread server components executing tasks for any other logical player implemented by the physical playback device.
[0049] For example, for a Multi-Player Playback Device implementing two logical players (i.e., a first logical player and a second logical player), the player-specific thread server components (one for each of the first logical player and the second logical player) enable the Multi-Player Playback Device to store context for use by worker threads executing tasks for the first logical player independently of context for use by worker threads executing tasks for the second logical player, and vice versa. Since the context for use by worker threads executing tasks for the first logical player and the context for use by worker threads executing tasks for the second logical player are stored independently (e.g., separately), updates to the context data used by worker threads executing tasks for the first logical player do not affect or otherwise change the context data used by worker threads executing tasks for the second logical player, and updates to the context data used by worker threads executing tasks for the second logical player do not affect or otherwise change the context data used by worker threads executing tasks for the first logical player.
[0050] In some embodiments, the set of player-specific software components for an individual logical player additionally or alternatively comprises a player-specific media transport component. The player-specific media transport component for an individual logical player is configured to route and/or execute media transport commands addressed to the unique player identifier (e.g. ULPI) of the individual logical player. In operation, media transport commands executed by the player-specific media transport component for the individual logical player do not affect media transport activity of any other logical player implemented by the physical Multi-Player Playback Device.
[0051] For example, for a Multi-Player Playback Device implementing two logical players (i.e., a first logical player and a second logical player), the player-specific media transport components (one for each of the first logical player and the second logical player) enable the Multi-Player Playback Device to execute media transport commands (e.g., play, pause, stop, skip, fast-forward, rewind, and so on) for the first logical player independently of media transport commands for the second logical player, and vice versa. As a result, media transport commands executed for the first logical player do not affect or otherwise change media transport activities of the second logical player, and media transport commands executed for the second logical player do not affect or otherwise change media transport activities of the first logical player.
[0052] In some embodiments, the set of player-specific software components for an individual logical player additionally or alternatively comprises a player-specific media rendering component. The player-specific media rendering component for an individual logical player is configured to render media content addressed to the ULPI of the individual logical player. In operation, media content rendered by the player-specific media rendering component for the individual logical player is isolated from media content rendering of any other logical player implemented by the physical Multi-Player Playback Device.
[0053] For example, for a Multi-Player Playback Device implementing two logical players (i.e., a first logical player and a second logical player), the player-specific media rendering components (one for each of the first logical player and the second logical player) enable the Multi-Player Playback Device to render media (e.g., play media content such as audio, video, audio/video, and/or any other type of media content) for the first logical player independently of any media rendered for the second logical player, and vice versa. As a result, media rendered by the first logical player does not affect media rendered by the second logical player, and media rendered by the second logical player does not affect media rendered by the first logical player.
[0054] As mentioned earlier, in addition to the player-specific software components configured to control various functions of individual logical players separate from other logical players, some Multi-Player Playback Device embodiments also include devicespecific software components that are configured to control one or more functions of the physical Multi-Player Playback Device at the device level.
[0055] In some embodiments, the set of device-specific software components comprises a data routing component. The data routing component is configured to route (among other data) logical player data received via the one or more network interfaces of the physical Multi-Player Playback Device to the various logical players implemented by the physical Multi-Player Playback Device based at least in part on the ULPI associated with the received logical player data.
[0056] For example, when the Multi-Player Playback Device receives data packets (e.g., media packets, control packets, or other packets), the Multi-Player Playback Device inspects the data packets to determine whether the packets (and/or the data enclosed therein) should be routed to (i) a device-level process or (ii) a player-specific process implemented for a particular logical player by the Multi-Player Playback Device. When the packets (and/or data enclosed therein) should be routed to a player-specific process, the routing component of the Multi-Player Playback Device routes the packets (and/or the data enclosed therein) to the appropriate player-specific process based at least in part on the ULPI contained within the received data packets. In some instances, the logical player data comprises one or more of (i) control data for individual logical players implemented by the physical Multi-Player Playback Device and (ii) media content for individual logical players implemented by the physical Multi-Player Playback Device.
[0057] Additional aspects of the disclosed systems and methods and disclosed and described in further detail herein.
A. Relevant Nomenclature
[0058] Given the new concepts described herein, certain terminology is introduced and used for explaining various example features and embodiments. However, it should be understood that such terminology and the use thereof may be uniquely applicable in at least some respects to the examples described herein, such as when describing both existing concepts and new concepts. However, in other situations, the terminology may be more broadly applicable to other examples, depending on the context. i. Playback Device
[0059] To help illustrate aspects of some embodiments, a playback device as used herein sometimes refers to a single, physical hardware device that is configured to play audio. Such a playback device includes one or more network interfaces, one or more processors, and tangible, non-transitory computer-readable media storing program instructions that are executed by the one or more processors to cause the playback device to perform certain playback device features and functions.
[0060] In some embodiments, a playback device includes integrated speakers. In other embodiments, a playback device includes speaker outputs that connect to external speakers. In still further embodiments, a playback device includes a combination of integrated speakers and speaker outputs that connect to external speakers.
[0061] In some instances, a playback device may be (or may include) a set of headphones. In some instances, a playback device may be (or may include) a smartphone, tablet computer, laptop / desktop computer, smart television, or other type of device configurable to play audio content.
[0062] In some embodiments, a playback device comprises one or more microphones configured to receive voice commands. In some instances, playback devices with microphones are referred to herein as Networked Microphone Devices (NMDs). In some NMD embodiments, the NMD is configured to perform any (or all) of the playback device functions disclosed herein.
[0063] Additional details about playback devices consistent with some example embodiments are disclosed and described herein. ii. Logical Player
[0064] A logical player as used herein sometimes refers to a logical playback entity implemented by one or more physical playback devices (e.g., one or more Multi-Player Playback Devices) to act as a single entity to play one stream of audio. In some instances where the one stream of audio comprises multichannel audio having two or more channels and the physical playback device includes two or more channel outputs, playing the multichannel audio includes the physical playback device playing the two or more channels via two or more corresponding channel outputs. In some instances where the one stream of audio comprises multichannel audio having two or more channels and the physical playback device includes one or more channel outputs, playing the multichannel audio includes the physical playback device playing one or more (but not all) channels via one or more corresponding channel outputs and one or more additional players playing the one or more additional channels via one or more corresponding outputs. In some instances, a single physical playback device implements a single logical player. In other instances, several physical playback devices may be configured to implement a single logical player. In still further instances, one physical playback device (i.e., a Multi-Player Playback Device) may implement several logical players.
[0065] In another example, two or more logical players implemented by one or more Multi-Player Playback Devices can be configured to play different channels of a single audio stream. For example, two logical players could be configured to operate in a stereo pair type of configuration, where one logical player is configured to play a left channel of a two- channel audio stream, and the other logical player is configured to play a right channel of the two-channel audio stream. In another example, three or more logical players implemented by one or more Multi-Player Playback Devices can be configured to play different channels of a single multichannel audio stream (e.g., home theater audio), where a first logical player plays a center channel, a second logical player plays a right front channel, a third logical player plays a left front channel, a fourth logical player plays a subwoofer channel, and so on. However, in other embodiments, a single logical player may be configured to play both channels of a stereo audio stream (perhaps via the same Multi-Player Playback Device or two different Multi-Player Playback Devices), or a single logical player may be configured to play all channels of a home theater audio stream (perhaps via the same Multi-Player Playback Device or via two or more Multi-Player Playback Devices). Further, in some scenarios, a logical player may mix down a multi-channel audio stream for playback via one or more Multi-Player Playback Devices, e.g., by mixing down a 2-channel stereo stream into a 1- channel mono stream for playback via one or more audio outputs of one or more Multi-Player Playback Devices, or by mixing down a 5-channel home theater stream into a 2-channel stereo stream or a 1 -channel mono stream for playback via one or more outputs of one or more Multi-Player Playback Devices.
[0066] Additional details about logical players consistent with some example embodiments are disclosed and described herein. iii. Multi-Player Playback Device
[0067] A Multi-Player Playback Device as used herein refers to a type of physical playback device comprising multiple configurable audio outputs, one or more processors, and tangible, non-transitory computer readable media storing program instructions that are executed by the one or more processors to cause the Multi-Player Playback Device to perform the Multi-Player Playback Device features and functions described herein. In scenarios where a playback device might be referred to as a zone player, the Multi-Player Playback Device may sometimes be referred to as a Multi-Zone Player.
[0068] In operation, the multiple audio outputs can be grouped together in different combinations to implement one or more logical players and play audio via one or more audio outputs.
[0069] In some embodiments, a single Multi-Player Playback Device is configurable to implement from one to eight (or more) logical players. Multi-Player Playback Devices according to other embodiments may be configurable to implement fewer than eight logical players or more than eight logical players. For example, in some embodiments, a Multi- Player Playback Device may be configurable to implement anywhere from one, two to six, eight, twelve, sixteen, eighteen, twenty four, or more logical players. Multi-Player Playback Devices configurable to implement more or fewer logical players than those specifically identified herein are possible as well
[0070] Multi-Player Playback Devices according to some embodiments include eight configurable audio outputs. Multi-Player Playback Devices according to other embodiments include fewer than eight configurable audio outputs or more than eight configurable audio outputs. For example, in some embodiments, a Multi-Player Playback Device may include anywhere from two to six, eight, twelve, sixteen, eighteen, twenty four, or more configurable audio outputs. Multi-Player Playback Devices with more or fewer audio outputs than those specifically identified herein are possible as well.
[0071] Additional details about Multi-Player Playback Devices consistent with some example embodiments are disclosed and described herein and also in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference. iv. Playback Entity
[0072] A playback entity as used herein sometimes refers to a logical or physical entity configured to play audio. Playback entities include physical playback devices, physical Multi-Player Playback Devices, and logical players that are implemented via one or more Multi-Player Playback Devices.
[0073] Additional details about playback entities consistent with some example embodiments are disclosed and described herein and also in U.S. Provisional App.
63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference. v. Zone
[0074] As another example, a zone (sometimes referred to herein as a playback zone or a bonded zone) as used herein sometimes refers to a logical container of one or more physical playback devices that are managed together. But in some instances, and in some of the examples described herein, a zone may include only a single, physical playback device. Thus, in operation, a zone may include any one or more playback devices managed as a logical zone entity, including, for example, (i) a single playback device managed as a logical zone entity, (ii) a group of playback devices managed as a logical zone entity, including but not limited to any of (a) a bonded zone that includes two or more playback devices configured to play the same audio, (b) a bonded pair of two playback devices configured to play the same audio, (c) a stereo pair of two playback devices where one of the playback devices is configured to play a left channel of stereo audio content and the other playback device is configured to play a right channel of stereo audio content, or (d) a home theater zone that includes two or more playback devices configured to play home theater and/or surround sound audio content.
[0075] In this manner, in some examples, a zone is a type of logical entity implemented by one or more playback devices. When the zone includes two or more playback devices, the two or more playback devices play one stream of audio content. In some instances, the one stream of audio content played by the zone comprises multichannel audio. In some zone scenarios that include two or more playback devices where the one stream of audio content comprises multichannel audio, each playback device (of the two or more physical playback devices) may be configured to play a different channel of the multichannel audio content.
[0076] For example, a first physical playback device in the zone may be configured to play a left channel of the audio content and a second physical playback device in the zone may be configured to play a right channel of the audio content. This type of example zone configuration is sometimes referred to as a stereo pair. [0077] In another example, a first playback device in the zone may play a left channel, a second playback device in the zone may play a right channel, and a third playback device in the zone may play a subwoofer channel. This type of example zone configuration is sometimes referred to as a home theater zone.
[0078] In some existing zone configurations, each of the individual playback devices within the zone communicate with each other in a fully-connected control plane configuration to exchange commands, configuration information, events, and state information to each other via dedicated websocket connections between each pair of playback devices within the zone.
[0079] Additional details about zones consistent with some example embodiments are disclosed and described herein and in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference. vi. Playback Group
[0080] A playback group (sometimes referred to herein simply as a group) is a logical container of two or more logical or physical playback entities. Logical and physical entities that can be grouped into a playback group include: (i) a zone, (ii) a playback device, (iii) a Multi-Player Playback Device, and/or (iii) a logical player.
[0081] A playback group differs from a zone in a few ways. First, a zone includes one or more playback devices, whereas a playback group includes two or more logical or physical playback entities (i.e., zones, playback devices, Multi-Player Playback Device, or logical players). Second, when one or more playback devices are configured into a zone, the playback system treats the zone as a single logical entity even though the zone may include several physical playback devices. By contrast, when two or more playback devices are configured into a group, the playback system manages each playback device separately even though each of the playback entities within the playback group are playing the same audio stream.
[0082] Similar to playback devices configured into a zone, all of the playback entities within a playback group are configured to play the same audio stream. In some instances, the audio stream comprises multichannel audio. In some scenarios where the audio stream comprises multichannel audio, each zone, playback device, Multi-Player Playback Device, or logical player in the playback group is configured to play the same set of audio channels. [0083] In some example playback group implementations, the playback group includes a group coordinator and one or more group members. The group coordinator sources audio for the playback group and manages certain configuration and control functions for the group member(s) in the playback group. However, other playback group implementations may distribute audio among the group and handle configuration and control functions differently.
[0084] Similar to a zone configuration (described above), and in contrast to an Area Zone configuration (described further herein), each of the individual playback devices within a playback group communicate with each other in a fully-connected configuration to exchange commands, configuration information, events, and state information with each other via dedicated websocket connections (or similar communication links / sessions) between each of the playback devices within the playback group. For example, a playback group with four playback devices in some playback group configurations would include six dedicated websocket connections (or similar communication links / sessions) for a fully- connected mesh between all four playback devices, e.g., dedicated connections between (i) playback device 1 and playback 2, (ii) playback device 1 and playback device 3, (iii) playback device 1 and playback device 4, (iv) playback device 2 and playback device 3, (v) playback device 2 and playback device 4, and (v) playback device 3 and playback device 4. [0085] Additional details about playback groups consistent with some example embodiments are disclosed and described herein and in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference. vii. Area Zone
[0086] An Area Zone is a new type of playback grouping. An Area Zone includes a set of two or more logical or physical playback entities grouped together. The playback entities that can be grouped together into an Area Zone include: (i) a zone, (ii) a playback device, (iii) a Multi-Player Playback Device, (iv) a logical player, and/or (iv) a playback group.
[0087] Similar to some zone and a playback group configurations (described above), all of the playback entities within an Area Zone are configured to play one audio stream. In some instances, the one audio stream comprises a multichannel audio stream. In some embodiments described herein, an Area Zone includes an Area Zone Primary and one or more Area Zone Secondaries, each of which is described further herein. [0088] In some embodiments, and similar to some zone configurations (described above), the playback system manages all of the playback entities within an Area Zone as a single logical playback entity. And similar to some playback group configurations (described above), in some embodiments, the individual playback entities can be managed and configured independently of each other.
[0089] One difference between some zone implementations (described above) on the one hand, and an Area Zone on the other, is that in some existing systems, prior zone configurations cannot be saved, and then activated or deactivated during operation of the playback system. With some prior zone implementations, the zone is configured typically when the playback devices forming the zone are added to the playback system. In contrast to those prior zone implementations, with some Area Zone embodiments, an individual playback entity can save several different Area Zone configurations and switch between operating in each of the different saved Area Zone configurations.
[0090] Another difference between zones and playback groups (described above) on the one hand, and an Area Zone on the other, is that unlike prior zone and playback group configurations, the playback entities within an Area Zone do not all communicate with each other in a fully-connected control plane configuration to exchange commands, configuration information, events, and state information with each other. In some examples, this fully- connected control plane is implemented via dedicated websocket connections between each pair of playback entities within the Area Zone.
[0091] Instead, the Area Zone Primary communicates with each Area Zone Secondary (and each Area Zone Secondary communicates with the Area Zone Primary) to exchange commands, configuration information, events, and state information in a hierarchical control plane. In contrast to how group members within a playback group maintain a fully-connected mesh between each other (e.g., via dedicated websocket connections in some instances) to facilitate communication between the different group members, in normal operation, the Area Zone Secondaries within the same Area Zone typically do not communicate with each other, and Area Zone Secondaries typically do not communicate with any other playback entity in a playback system other than their corresponding Area Zone Primary. Instead, the Area Zone Secondaries communicate with the Area Zone Primary which can, in turn, facilitate any exchange of commands, configuration information, events, or state information that may need to occur between two Area Zone Secondaries. [0092] Additional details about Area Zones consistent with some example embodiments are disclosed and described herein and in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference. viii. Area Zone Primary
[0093] An Area Zone Primary is a player (e.g., a playback device or Multi-Player Playback Device) that is configured to handle audio sourcing and control signaling on behalf of itself and all of the Area Zone Secondaries within an Area Zone. In some embodiments, the Area Zone Primary may also perform one or more (or all) functions of a Global State Aggregator as described in U.S. Provisional App. 63/377,978, titled “Global State Service,” referred to as Docket No. 23-0306p, filed on Sep. 30, 2022.
[0094] For media, in some implementations, the Area Zone Primary is configured to function as an audio sourcing device for itself and all of the Area Zone Secondaries within the Area Zone.
[0095] For control signaling, in some implementations, the Area Zone Primary communicates with each Area Zone Secondary to exchange commands, configuration information, events, and state information to implement playback, configuration, and control functions (e.g., volume, mute, playback start/stop, queue management, configuration management and updates) for the Area Zone.
[0096] In addition to exchanging commands, configuration information, events, and state information with each Area Zone Secondary within the Area Zone, each Area Zone Primary in some implementations is also configured to exchange commands, configuration information, events, and state information with (i) each (and every) other Area Zone Primary in the playback system and (ii) any controller device(s) or controller system(s) configured for controlling operation of the playback system. However, rather than exchanging commands, configuration information, events, and state information with each (and every) other Area Zone Primary in the playback system, in some embodiments each Area Zone Primary in some implementations is configured to exchange commands, configuration information, events, and state information with one or more Brokers (not every other Area Zone Primary) in the playback system. The use of Brokers in this and other manners is described in more detail in U.S. Provisional App. 63/377,978, titled “Global State Service,” referred to as Docket No. 23-0306p, filed on Sep. 30, 2022. [0097] One example scenario that illustrates how an Area Zone Primary exchanges commands, configuration information, events, and state information with Area Zone Secondaries and/or controller device(s) and/or controller system(s) is where, after a playback entity configured as the Area Zone Primary receives a request for configuration or operational information about one or more playback entities within the Area Zone from a requesting device (e.g., a controller device, a controller system, or perhaps another playback entity in the playback system), the playback entity configured as the Area Zone Primary provides the requested information to the requesting device on behalf of the Area Zone. [0098] For example, in response to a request for a listing of playback entities in the Area Zone received from a requesting device, the Area Zone Primary transmits a listing of playback entities within the Area Zone to the requesting device. In another example, in response to a request for configuration information about a particular Area Zone Secondary received from a requesting device, and to the extent that the Area Zone Primary does not already have the requested configuration information for the particular Area Zone Secondary, the Area Zone Primary obtains the requested configuration information from the Area Zone Secondary. And regardless of whether the Area Zone Primary already had the configuration information for the particular Area Zone Secondary or acquired the requested configuration information from the particular Area Zone Secondary, the Area Zone Primary provides the requested configuration information for the particular Area Zone Secondary to the requesting device.
[0099] Additional details about Area Zone primaries consistent with some example embodiments are disclosed and described herein and in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference. ix. Area Zone Secondary
[0100] An Area Zone Secondary is a logical or physical entity in the Area Zone that is not the Area Zone Primary for the Area Zone. In operation, each Area Zone Secondary within an Area Zone is configured to communicate with the Area Zone Primary to exchange commands, configuration information, events, and state information to implement playback, configuration, and control functions (e.g., volume, mute, playback start/stop, queue management, configuration management and updates) for the Area Zone.
[0101] As mentioned earlier, in normal operation, an Area Zone Secondary typically does not communicate with any other Area Zone Secondary within the Area Zone or any other playback entity within a playback system. However, an Area Zone Secondary in some instances may receive commands and/or inquiries from a controller device, and in some instances can establish a communication session with another Area Zone Secondary to exchange data in some circumstances.
[0102] One example scenario that illustrates how an Area Zone Secondary exchanges commands, configuration information, events, and state information with its Area Zone Primary is where, after a playback entity configured as an Area Zone Secondary receives a request for configuration or operational information about one or more playback entities within the Area Zone from a requesting device (e.g., a controller device, a controller system, or perhaps another playback entity in the playback system), the playback entity configured as the Area Zone Secondary forwards the received request to the Area Zone Primary. In some instances, the Area Zone Primary responds to the requesting device to provide the requested information.
[0103] For example, in response to a request for a listing of playback entities in the Area Zone received from a requesting device, the Area Zone Secondary forwards the request to the Area Zone Primary, and the Area Zone Primary transmits a listing of playback entities within the Area Zone to the requesting device. In another example, in response to a request for configuration information about a particular Area Zone Secondary received from a requesting device (including a request about itself), the Area Zone Secondary forwards the request to the Area Zone Primary, and the Area Zone Primary provides the requested information to the requesting device.
[0104] Additional details about Area Zone secondaries consistent with some example embodiments are disclosed and described herein and in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference. x. Controller Device
[0105] A controller device (sometimes referred to herein as a controller or a control device) is a computing device or computing system with one or more processors and tangible, non-transitory computer readable media storing program instructions executable by the one or more processors to execute the controller device features and functions described herein. In some scenarios, a controller device is a smartphone, tablet computer, laptop computer, desktop computer, smartwatch, or similar computing device configured to execute a software user interface for configuring and controlling playback entities within a playback system. In some scenarios, a controller device may include one or more cloud server systems configured to communicate with one or more playback entities to configure and control the playback system. In some examples, a playback entity (e.g., a playback device, Multi-Player Playback Device, or logical player) may also perform one or more functions of a controller. Thus, a playback entity may be considered a controller device in scenarios where the playback entity performs one or more controller functions.
[0106] In operation, user inputs associated with commands for configuring and controlling playback entities within a playback system can take a variety of forms, including but not limited to (i) physical inputs (e.g., actuating physical controls like knobs, sliders, buttons and so forth) (ii) software user interface inputs (e.g., inputs on a touch screen or similar graphical user interface), (iii) voice inputs, (iv) inputs received from another playback entity in the playback system (e.g., in the form of signaling from the playback entity to the controller in connection with effectuating configuration and control commands) and/or (v) any other type of input in any other form now known or later developed that is sufficient for conveying commands for configuring and controlling playback entities.
[0107] Additional details about area controller devices consistent with some example embodiments are disclosed and described herein and in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference.
B. Hierarchical Control Plane for Command and Control Signaling
[0108] As mentioned above, one aspect of the Area Zone embodiments disclosed herein is a hierarchical control plane.
[0109] Exchanging command and control information via control plane implementations disclosed herein differs from prior command and control distribution schemes such as the ones disclosed in U.S. App. 13/489,674, titled “Device Playback Failure Recovery and Redistribution,” filed on Jun. 6, 2012, and issued on Dec. 2, 2014, as U.S. Pat. 8,903,526, the entire contents of which are incorporated herein by reference. The ‘674 application describes a command and control distribution scheme where a confirmed communication list (CCL) is generated to facilitate communication between playback devices within a playback system. In one example, the CCL is a list of all playback devices in a zone configuration, where the CCL is ordered according to an optimal routing using the least number of hops or transition points through the network between the playback devices. In another case, the CCL is generated without consideration of network routing metrics. In either case, command and control data is passed from playback device to playback device within the zone configuration following the order in the CCL in a linear or serial manner. In one example, a first playback device sends a command to a second playback device in the CCL, and the second playback device in the CCL sends the command to a third playback device in the CCL, and so on until the command reaches its destination (i.e., a playback device in the CCL). For commands to be processed by all playback devices in the zone configuration, the commands are routed from playback device to playback device in the order specified in the CCL until every playback device in the CCL has received the commands. This arrangement is simple to execute, provides reliable transmission of information from playback device to playback device, and tends to work quite well for zones with a few playback devices.
[0110] However, for Area Zones with a lot of playback entities, the CCL-based approach can become impractical because it can take too long to distribute commands to a large number of playback entities or even to send a command to a single playback entity since every command is routed through the group on a serial, hop-by-hop basis according the CCL.
[OHl] In contrast to the above-described CCL approach and flat control plane implementations where many (or all) playback entities within a playback system communicate directly with each other to exchange configuration and control information throughout the playback system, some Area Zone embodiments disclosed herein employ a hierarchical control plane where commands, configuration information, events, and state information are exchanged only between the Area Zone Primary and each Area Zone Secondary within the Area Zone. For playback systems that may include several Area Zones, the Area Zone Primaries may exchange commands, configuration information, events, and state information with each other.
[0112] In the Area Zone embodiments disclosed herein, and in contrast to flat, fully- meshed control plane implementations, the Area Zone Secondaries typically do not exchange commands, configuration information, events, and state information to each other via dedicated websocket connections (or similar communications links or sessions) with each other, except perhaps in a few rare instances described herein.
[0113] In some scenarios, any commands, configuration information, events, and state information to be sent from a first Area Zone Secondary to a second Area Zone Secondary are sent from the first Area Zone Secondary to the Area Zone Primary. The Area Zone Primary then, in turn, (i) processes the command(s), configuration information, event(s), and/or state information received from the first Area Zone Secondary and instructs and/or updates the second Area Zone Secondary accordingly, or (ii) forwards the command(s), configuration information, event(s), and/or state information to the second Area Zone Secondary, as necessary.
[0114] Some Area Zone embodiments additionally or alternatively employ a Configuration and Command (C&C) group (e.g., a multicast group) for distributing commands, configuration information, events, and state information to playback entities within the Area Zone.
[0115] In some instances, the Area Zone Primary creates the C&C group for the Area Zone (or joins the C&C group as a publisher), and provides information required to join and/or subscribe to the C&C group to each Area Zone Secondary. The Area Zone Secondaries join and/or subscribe to the C&C group to receive control information. In such embodiments, the Area Zone Primary publishes commands, configuration information, events, and state information to the C&C group, and each Area Zone Secondary subscribed to the C&C group receives the commands, configuration information, events, and state information that the Area Zone Primary publishes to the C&C group. In some embodiments, Area Zone Secondaries may also publish certain command, configuration, event, and state information to the Area Zone C&C group. In operation, each when an Area Zone Secondary receives a command via the C&C group that requires some action on behalf of the Area Zone Secondary, the Area Zone Secondary executes the received command.
[0116] Additional details about hierarchical control plane features and functionality for Area Zone configurations consistent with some example embodiments are disclosed and described herein and in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference.
C. Media and Timing Distribution
[0117] Another aspect of some Area Zone embodiments disclosed herein is how audio content and playback timing are distributed to individual playback entities within the Area Zone. In some existing zone or playback group configurations, the playback device designated as the audio sourcing device is configured to transmit audio content and playback timing for the audio content to each other playback device in the zone or playback group via unicast transmissions from the audio sourcing device to each other playback device in the zone or playback group. [0118] However, in some Area Zone embodiments disclosed herein, the Area Zone Primary is configured to transmit audio content and playback timing for the audio content to a media distribution group (e.g., a multicast group), and Area Zone Secondaries subscribe to the media group to receive the audio content and playback timing, e.g., each Area Zone Secondary joins the media multicast group and receives audio content and playback timing via the media multicast group.
[0119] Some embodiments employ a hybrid unicast / multicast approach where the Area Zone Primary is configured to (i) distribute audio content and playback timing via unicast transmissions to Area Zone Secondaries that are wirelessly connected to the playback system, e.g., via WiFi, Bluetooth, or other suitable wireless connection, and (ii) distribute audio content and playback timing via multicast transmissions to Area Zone Secondaries that are connected to the playback system via wired connections, e.g., Ethernet, Power over Ethernet (PoE), Universal Serial Bus (USB), or other suitable wired connection.
[0120] Some Area Zone embodiments employ a Media and Timing (M&T) group (e.g., a multicast group) for distributing audio content and playback timing to playback entities within the Area Zone. In some Area Zone embodiments, clock timing is also distributed to the playback entities within the Area Zone via the M&T group. In some instances, the Area Zone Primary creates the M&T group for the Area Zone (or joins the M&T group as a publisher), and provides information required to join and/or subscribe to the M&T group to each Area Zone Secondary. The Area Zone Secondaries join and/or subscribe to the M&T group to receive audio content, playback timing, and in some instances, clock timing. In such embodiments, the Area Zone Primary publishes the audio content, playback timing, and clock timing to the M&T group, and each Area Zone Secondary subscribed to the M&T group receives the audio content, playback timing, and clock timing that the Area Zone Primary publishes to the M&T group.
[0121] Additional details about media and timing data for Area Zone configurations consistent with some example embodiments are disclosed and described herein and in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22-1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference.
D. Storing and Recalling Area Zone Configuration Information
[0122] Another aspect of some Area Zone embodiments disclosed herein includes the Area Zone configuration data and how the Area Zone configuration data is stored and recalled to activate an Area Zone configuration. [0123] In contrast to some prior playback group configurations and zone configurations where every playback device maintains an up-to-date version of the group/zone configuration data, Area Zone configurations according to some embodiments include storing the Area Zone configuration information in a single Area Zone configuration package. In some instances, the Area Zone configuration package includes separate Area Zone configuration files for each playback entity in the Area Zone. In some instances, the Area Zone configuration package is stored at one or more of (i) the Area Zone Primary, (ii) a controller device, and/or (iii) a cloud server system.
[0124] The Area Zone configuration information in some embodiments includes information about the Area Zone configuration, including but not limited to one or more (or all) of (i) a name that identifies the Area Zone, (ii) the name of the playback entity that is to function as the Area Zone Primary once the Area Zone is activated, (iii) the name of each playback entity in the Area Zone (i.e., the UUID of each playback device, the UUID of each Multi-Player Playback Device, the ULPI of each logical player, the zone name of each zone, and group name of each playback group in the Area Zone, as applicable), (iv) playback calibration settings for each playback entity in the Area Zone, (v) for Area Zones configured to play multichannel audio, a channel map that defines the channel or channels that each playback entity is configured to play once the Area Zone has been activated, including at least in some instances, which channel each output port of each playback entity is configured to play while the Area Zone is active, and (vi) for individual playback entities, one or more configuration setting(s) that define certain Area Zone specific behavior of the playback entity while the Area Zone is active.
[0125] Examples of Area Zone specific behavior while the Area Zone is active include: (i) behavior of the playback entity in response to receiving a volume control command, a playback control command (e.g., play/pause/skip/etc.), and/or other user command via a physical interface on (or associated with) the playback entity, and (ii) behavior of the playback entity in response to receiving a voice command via an associated microphone.
[0126] Additional details about storing and recalling Area Zone configuration consistent with some example embodiments information are disclosed and described herein and in U.S. Provisional App. 63/502,347, titled “Area Zones,” referred to as Docket No. 22- 1002p, filed on May 15, 2023, the contents of which are incorporated herein by reference. E. Related Art
[0127] The above-described example configurations as well as additional and alternative example configurations are described in more detail herein. Aspects of the features and functions implemented in the example configurations disclosed herein differ from prior implementations in several ways.
[0128] For example, with respect to streaming audio content and playback timing to individual playback devices, U.S. App. 10/816,217, titled “System And Method For Synchronizing Operations Among A Plurality Of Independently Clocked Digital Data Processing Devices,” referred to as Docket No. 04-0401, filed on Apr. 1, 2004, and issued on Jul. 31, 2012, as U.S. Pat. 8,234,395, describes, inter alia, independently-clocked playback devices that are configured to play audio content in synchrony with each other based on playback timing and clock timing information. However, U.S. App. 10/816,217 does not describe the Area Zone configurations, Multi-Player Playback Devices, playback entity implementations, logical players, and/or the “multi-instance” software architecture described herein. The entire contents of U.S. App. 10/816,217 are incorporated herein by reference. [0129] Similarly, with respect to groupwise control of groups of playback devices within a playback system, U.S. App. 10/861,653, titled “Method And Apparatus For Controlling Multimedia Players In A Multi -Zone System,” referred to as Docket No. 04- 0601, filed on Jun. 5, 2004, and issued on Aug. 4, 2009, as U.S. Pat. 7,571,014, describes, inter alia, groupwise control of multiple playback devices, including groupwise volume control of playback devices configured within a group of playback devices configured to play audio content in synchrony with each other, sometimes referred to as a synchrony group. However, U.S. App. 10/861,653 does not describe does not describe the Area Zone configurations, Multi-Player Playback Devices, playback entity implementations, logical players, and/or the “multi-instance” software architecture described herein. The entire contents of U.S. App. 10/861,653 are incorporated herein by reference.
[0130] Other aspects of groupwise control of groups of playback devices are described in U.S. App. 13/910,608, titled “Satellite Volume Control,” referred to as Docket No. 13-0413, filed on June. 5, 2013, and issued on Sep. 6, 2016, as U.S. Pat. 9,438, 193. For example, U.S. App. 13/910,608 discloses, inter alia, controlling playback volume of grouped playback devices, including propagating a volume adjustment received via a first playback device to other playback devices that have been grouped with the first playback device. However, U.S. App. 13/910,608 does not describe does not describe the Area Zone configurations, Multi-Player Playback Devices, playback entity implementations, logical players, and/or the “multi-instance” software architecture described herein. The entire contents of U.S. App. 13/910,608 are incorporated herein by reference.
[0131] Further, several earlier-filed applications describe aspects of specialized groupings of playback devices within a playback system. For example, U.S. App. 13/013,740, titled “Controlling and grouping in a multi-zone media system,” referred to as Docket No. 11-0101, filed on Jan. 25, 2011, and issued on Dec. 1, 2015, as U.S. Pat. 9,202,509, describes, inter alia, configuring and operating two playback devices in a “paired” configuration such as a “stereo pair” configuration, where one playback device is configured to play a right stereo channel of audio content and the other playback device is configured to play a left stereo channel of audio content.
[0132] Similarly, U.S. App. 13/083,499, titled “Multi-Channel Pairing In A Media System,” referred to as Docket No. 11-0401, filed on Apr. 8, 2011, and issued on Jul. 22, 2014, as U.S. Pat. 8,788,080, describes, inter alia, configuring and operating multiple playback devices in a consolidated mode, where two or more playback devices can be grouped into a consolidated playback device which can then be further grouped with one or more other playback devices and/or one or more other consolidated playback devices.
[0133] Further, U.S. App. 13/632,731, titled, “Providing A Multi-Channel And A Multi-Zone Audio Environment,” referred to as Docket No. 12-0802, filed on Oct. 1, 2012, and issued on Dec. 6, 2016, as U.S. Pat. 9,516,440, describes, inter alia, configuring playback devices to play different types of audio content (e.g., home theater audio vs. music) according to different playback timing arrangements (e.g., with low-latency vs. with ordinary latency).
[0134] Additionally, U.S. App. 14/731,119, titled, “Dynamic Bonding of Playback Devices,” referred to as Docket No. 15-0301, filed on Jun. 4, 2015, and issued on Jan. 9, 2018, as U.S. Pat. 9,864,571, discloses, inter alia, dynamic bonding scenarios and playback devices that are “sharable” among different zones. And U.S. App. 14/997,269, titled, “System Limits Based on Known Triggers,” referred to as Docket 15-1104, filed on Jan. 15, 2016, and issued on Feb. 20, 2018, as U.S. Pat. 9,898,245, describes, inter alia, methods of setting up multiple playback devices.
[0135] Further still, U.S. Provisional App. 63/377,948, titled “Playback System Architecture,” referred to as Docket No. 21-0703p, filed on Sep. 30, 2022, describes, inter alia, multi-tier hierarchical playback systems comprising several playback devices, including methods and processes of distributing audio and control signaling between and among playback devices with the multi-tier hierarchical playback system. [0136] However, U.S. Apps. 13/013,740; 13/083,499; 13/632,731; 14/731,119; 14/997,269; and 63/377,948 do not describe the Area Zone configurations, Multi-Player Playback Devices, playback entity implementations, logical players, and/or the “multiinstance” software architecture described herein. The entire contents of U.S. Apps. 13/013,740; 13/083,499; 13/632,731; 14/731,119; 14/997,269; and 63/377,948 are incorporated herein by reference.
[0137] Additionally, several other advancements over time have improved the overall functionality and usability of playback devices configured in groups for synchronous playback of audio content.
[0138] With respect to managing groups of playback devices configured for groupwise playback of audio content, U.S. App. 14/042,001, titled “Coordinator Device for Paired or Consolidated Players,” referred to as Docket No. 13-0812, filed on Dep. 30, 2013, and issued on Mar. 15, 2016, as U.S. Pat. 9,288,596, and U.S. App. 14/041,989, titled “Group Coordinator Device Selection,” referred to as Docket No. 13-0815, filed on Sep. 30, 2013, and issued on May 16, 2017, as U.S. Pat. 9,654,545 disclose, inter alia, certain techniques whereby individual playback devices configured to operate in a groupwise manner decide which playback device should function as a group coordinator for the group of playback devices.
[0139] U.S. App. 14/988,524, titled, “Multiple-Device Setup,” referred to as Docket No. 15-1103, filed Jan. 5, 2016, and issued May 28, 2019, as U.S. Pat. 10,303,422, discloses, inter alia, techniques for adding several new playback devices to a playback system at the same time, including, in scenarios when two or more of the same type of playback devices are detected during setup, causing one of the two or more playback devices to emit a sound that enables a user to identify the one playback device in connection with playback system configuration and setup.
[0140] U.S. App. 16/119,516, titled, “Media Playback System with Virtual Line-In,” referred to as Docket No. 18-0406, filed on Aug. 31, 2018, and issued on Oct. 22, 2019, as U.S. Pat. 10,452,345, and U.S. App. 16/119,642, titled, “Interoperability Of Native Media Playback System With Virtual Line-In,” referred to as Docket No. 18-0503, filed on Aug. 31, 2018, and issued on May 12, 2020, as U.S. Pat. 10,649,718, (both of which claim priority to U.S. Prov. App. 62/672,020, titled “Media Playback System with Virtual Line-In,” referred to as Docket No. 18-0406p, filed on May 15, 2018, and now expired) describe, inter alia, scenarios where one playback device in one playback system coordinates aspects of playback and control of another playback device in a different playback system in connection with facilitating interoperability between to two different playback systems.
[0141] U.S. App. 16/415,783, titled, “Wireless Multi-Channel Headphone Systems and Methods,” referred to as Docket No. 19-0303, filed on May 17, 2019, and issued on Nov.
16, 2021, as U.S. Pat. 11,178,504, describes, inter alia, a surround sound controller and one or more wireless headphones that switch between operating in various modes that have different latency characteristics. For example, in a first mode, the surround sound controller uses a first Modulation and Coding Scheme (MCS) to transmit first surround sound audio information to a first pair of headphones, and in a second mode, the surround sound controller uses a second MCS to transmit (a) the first surround sound audio information to the first pair of headphones and (b) second surround sound audio information to a second pair of headphones.
[0142] However, U.S. Apps. 13/489,674; 14/042,001; 14/041,989; 14/988,524; 16/119,516; 16/119,642; 62/672,020; and 16/415,783 do not describe the Area Zone configurations, Multi-Player Playback Devices, playback entity implementations, logical players, and/or the “multi-instance” software architecture described herein. The entire contents of U.S. Apps. 13/489,674; 14/042,001; 14/041,989; 14/988,524; 16/119,516; 16/119,642; 62/672,020; and 16/415,783 are incorporated herein by reference.
[0143] Further, some advancements over time have improved the sound quality of audio content played by playback devices via methods of calibrating playback settings (e.g., audio playback settings) for playback devices based on acoustic characteristics of the listening environment in which the playback devices are situated. At a high level, calibrating playback settings includes, inter alia, determining one or more acoustic characteristics of the listening environment, and adjusting one or more audio playback settings (e.g., equalization settings, relative loudness, playing timing delays, and/or perhaps other settings) based on the acoustic characteristics.
[0144] For example, U.S. App. 15/211,822, titled, “Spatial Audio Correction,” referred to as Docket No. 16-0402, filed on Jul. 15, 2016, and issued on Oct. 17, 2017, as U.S. Pat. 9,794,710 describes, inter alia, determining a spatial and/or spectral calibration for one or more playback devices within a listening area. Similarly, U.S. App. 16/115,524, titled “Playback Device Calibration,” referred to as Docket No. 18-0401, filed on Aug. 28, 2018, and issued on May 21, 2019, as U.S. Pat. 10,299,061 describes, inter alia, calibrating a playback device within a room so that the audio output by the playback device accounts for (e.g., offsets) acoustic characteristics of that room, thereby improving sound of the audio playback experienced by a listener within the room.
[0145] Additionally, U.S. App. 15/630,214, titled, “Immersive Audio in a Media Playback System,” referred to as Docket No. 16-0504, filed on Jun. 22, 2017, and issued on Jul. 17, 2018, as U.S. Pat. 10,028,069 describes, inter alia, processes that include obtaining audio responses from several different playback devices in a media playback system. For example, a first playback device at a first time plays back calibration audio while a microphone device records the calibration audio being played back. A second playback device at a second time plays back the calibration audio while the microphone device records the calibration audio being played. The process is repeated until every playback device in the media playback system has played the calibration audio and had its response recorded.
[0146] Further, IntT App. PCT/US22/77233, titled “Audio Parameter Adjustment Based on Playback Device Separation Distance,” referred to as Docket No. 21-0605-PCT, and published as WO 2023/056336 on Apr. 6, 2023, disclosed, inter alia, applying a low frequency filter to two or more devices in a zone based on a distance between the devices. [0147] However, Apps. 15/211,822; 16/115,524; 15/630,214; and PCT/US22/77233 do not describe the Area Zone configurations, Multi-Player Playback Devices, playback entity implementations, and/or the “multi-instance” software architecture described herein. The entire contents of Apps. 15/211,822; 16/115,524; 15/630,214; and PCT/US22/77233 are incorporated herein by reference.
[0148] While some examples described herein may refer to functions performed by given actors such as “users,” “listeners,” and/or other entities, it should be understood that this is for purposes of explanation only. The claims should not be interpreted to require action by any such example actor unless explicitly required by the language of the claims themselves.
[0149] In the Figures, identical reference numbers identify generally similar, and/or identical, elements. To facilitate the discussion of any particular element, the most significant digit or digits of a reference number refers to the Figure in which that element is first introduced. For example, element 110a is first introduced and discussed with reference to Figure 1 A. Many of the details, dimensions, angles and other features shown in the Figures are merely illustrative of particular example configurations of the disclosed technology. Accordingly, other example configurations can have other details, dimensions, angles and features without departing from the spirit or scope of the disclosure. In addition, those of ordinary skill in the art will appreciate that further example configurations of the various disclosed technologies can be practiced without several of the details described below.
II. Suitable Operating Environment
[0150] Figure 1 A is a partial cutaway view of a media playback system 100 distributed in an environment 101 (e.g., a house). The media playback system 100 comprises one or more playback devices 110 (identified individually as playback devices 1 lOa-n), one or more network microphone devices (“NMDs”), 120 (identified individually as NMDs 120a- c), and one or more control devices 130 (identified individually as control devices 130a and 130b).
[0151] As used herein the term “playback device” can generally refer to a network device configured to receive, process, and output data of a media playback system. For example, a playback device can be a network device that receives and processes audio content. In some example configurations, a playback device includes one or more transducers or speakers powered by one or more amplifiers. In other example configurations, however, a playback device includes one of (or neither of) the speaker and the amplifier. For instance, a playback device can comprise one or more amplifiers configured to drive one or more speakers external to the playback device via a corresponding wire or cable.
[0152] Moreover, as used herein the term NMD (i.e., a “network microphone device”) can generally refer to a network device that is configured for audio detection. In some example configurations, an NMD is a stand-alone device configured primarily for audio detection. In other example configurations, an NMD is incorporated into a playback device (or vice versa).
[0153] The term “control device” can generally refer to a network device configured to perform functions relevant to facilitating user access, control, and/or configuration of the media playback system 100.
[0154] Each of the playback devices 110 is configured to receive audio signals or data from one or more media sources (e.g., one or more remote servers, one or more local devices) and play back the received audio signals or data as sound. The one or more NMDs 120 are configured to receive spoken word commands, and the one or more control devices 130 are configured to receive user input. In response to the received spoken word commands and/or user input, the media playback system 100 can play back audio via one or more of the playback devices 110. In certain example configurations, the playback devices 110 are configured to commence playback of media content in response to a trigger. For instance, one or more of the playback devices 110 can be configured to play back a morning playlist upon detection of an associated trigger condition (e.g., presence of a user in a kitchen, detection of a coffee machine operation). In some example configurations, for example, the media playback system 100 is configured to play back audio from a first playback device (e.g., the playback device 100a) in synchrony with a second playback device (e.g., the playback device 100b). Interactions between the playback devices 110, NMDs 120, and/or control devices 130 of the media playback system 100 configured in accordance with the various example configurations of the disclosure are described in greater detail below with respect to Figures 1B-1L.
[0155] In the illustrated embodiment of Figure 1A, the environment 101 comprises a household having several rooms, spaces, and/or playback zones, including (clockwise from upper left) a master bathroom 101a, a master bedroom 101b, a second bedroom 101c, a family room or den 101 d, an office lOle, a living room 10 If, a dining room 101g, a kitchen lOlh, and an outdoor patio lOli. While certain example configurations and examples are described below in the context of a home environment, the technologies described herein may be implemented in other types of environments. In some example configurations, for example, the media playback system 100 can be implemented in one or more commercial settings (e.g., a restaurant, mall, airport, hotel, a retail or other store), one or more vehicles (e.g., a sports utility vehicle, bus, car, a ship, a boat, an airplane), multiple environments (e.g., a combination of home and vehicle environments), and/or another suitable environment where multi-zone audio may be desirable.
[0156] The media playback system 100 can comprise one or more playback zones, some of which may correspond to the rooms in the environment 101. The media playback system 100 can be established with one or more playback zones, after which additional zones may be added, or removed to form, for example, the configuration shown in Figure 1 A. Each zone may be given a name according to a different room or space such as the office lOle, master bathroom 101a, master bedroom 101b, the second bedroom 101c, kitchen lOlh, dining room 101g, living room lOlf, and/or the patio lOli. In some aspects, a single playback zone may include multiple rooms or spaces. In certain aspects, a single room or space may include multiple playback zones.
[0157] In the illustrated embodiment of Figure 1A, the master bathroom 101a, the second bedroom 101c, the office lOle, the living room 10 If, the dining room 101g, the kitchen lOlh, and the outdoor patio lOli each include one playback device 110, and the master bedroom 101b and the den 101 d include a plurality of playback devices 110. In the master bedroom 101b, the playback devices 1101 and 110m may be configured, for example, to play back audio content in synchrony as individual ones of playback devices 110, as a bonded playback zone, as a consolidated playback device, and/or any combination thereof. Similarly, in the den 101 d, the playback devices 1 lOh-j can be configured, for instance, to play back audio content in synchrony as individual ones of playback devices 110, as one or more bonded playback devices, and/or as one or more consolidated playback devices. Additional details regarding bonded and consolidated playback devices are described below with respect to, for example, Figures IB and IE and 1I-1M.
[0158] In some aspects, one or more of the playback zones in the environment 101 may each be playing different audio content. For instance, a user may be grilling on the patio lOli and listening to hip hop music being played by the playback device 110c while another user is preparing food in the kitchen lOlh and listening to classical music played by the playback device 110b. In another example, a playback zone may play the same audio content in synchrony with another playback zone. For instance, the user may be in the office lOle listening to the playback device 1 lOf playing back the same hip hop music being played back by playback device 110c on the patio lOli. In some aspects, the playback devices 110c and 1 lOf play back the hip hop music in synchrony such that the user perceives that the audio content is being played seamlessly (or at least substantially seamlessly) while moving between different playback zones. Additional details regarding audio playback synchronization among playback devices and/or zones can be found, for example, in U.S. Patent No. 8,234,395 entitled, “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is incorporated herein by reference in its entirety. a. Suitable Media Playback System
[0159] Figure IB is a schematic diagram of the media playback system 100 and a cloud network 102. For ease of illustration, certain devices of the media playback system 100 and the cloud network 102 are omitted from Figure IB. One or more communications links 103 (referred to hereinafter as “the links 103”) communicatively couple the media playback system 100 and the cloud network 102.
[0160] The links 103 can comprise, for example, one or more wired networks, one or more wireless networks, one or more wide area networks (WAN), one or more local area networks (LAN), one or more personal area networks (PAN), one or more telecommunication networks (e.g., one or more Global System for Mobiles (GSM) networks, Code Division Multiple Access (CDMA) networks, Long-Term Evolution (LTE) networks, 5G communication network networks, and/or other suitable data transmission protocol networks), etc. The cloud network 102 is configured to deliver media content (e.g., audio content, video content, photographs, social media content) to the media playback system 100 in response to a request transmitted from the media playback system 100 via the links 103. In some example configurations, the cloud network 102 is further configured to receive data (e.g. voice input data) from the media playback system 100 and correspondingly transmit commands and/or media content to the media playback system 100.
[0161] The cloud network 102 comprises computing devices 106 (identified separately as a first computing device 106a, a second computing device 106b, and a third computing device 106c). The computing devices 106 can comprise individual computers or servers, such as, for example, a media streaming service server storing audio and/or other media content, a voice service server, a social media server, a media playback system control server, etc. In some example configurations, one or more of the computing devices 106 comprise modules of a single computer or server. In certain example configurations, one or more of the computing devices 106 comprise one or more modules, computers, and/or servers. Moreover, while the cloud network 102 is described above in the context of a single cloud network, in some example configurations the cloud network 102 comprises a plurality of cloud networks comprising communicatively coupled computing devices. Furthermore, while the cloud network 102 is shown in Figure IB as having three of the computing devices 106, in some example configurations, the cloud network 102 comprises fewer (or more than) three computing devices 106.
[0162] The media playback system 100 is configured to receive media content from the networks 102 via the links 103. The received media content can comprise, for example, a Uniform Resource Identifier (URI) and/or a Uniform Resource Locator (URL). For instance, in some examples, the media playback system 100 can stream, download, or otherwise obtain data from a URI or a URL corresponding to the received media content. A network 104 communicatively couples the links 103 and at least a portion of the devices (e.g., one or more of the playback devices 110, NMDs 120, and/or control devices 130) of the media playback system 100. The network 104 can include, for example, a wireless network (e.g., a WiFi network, a Bluetooth, a Z-Wave network, a ZigBee, and/or other suitable wireless communication protocol network) and/or a wired network (e.g., a network comprising Ethernet, Universal Serial Bus (USB), and/or another suitable wired communication). As those of ordinary skill in the art will appreciate, as used herein, “WiFi” can refer to several different communication protocols including, for example, Institute of Electrical and Electronics Engineers (IEEE) 802.11a, 802.11b, 802.11g, 802.1 In, 802.1 lac, 802.1 lac, 802. Had, 802.11af, 802.11ah, 802.1 lai, 802.1 laj, 802.11aq, 802.11ax, 802.11ay, 802.15, etc. transmitted at 2.4 Gigahertz (GHz), 5 GHz, and/or another suitable frequency.
[0163] In some example configurations, the network 104 comprises a dedicated communication network that the media playback system 100 uses to transmit messages between individual devices and/or to transmit media content to and from media content sources (e.g., one or more of the computing devices 106). In certain example configurations, the network 104 is configured to be accessible only to devices in the media playback system 100, thereby reducing interference and competition with other household devices. In other example configurations, however, the network 104 comprises an existing household communication network (e.g., a household WiFi network). In some example configurations, the links 103 and the network 104 comprise one or more of the same networks. In some aspects, for example, the links 103 and the network 104 comprise a telecommunication network (e.g., an LTE network, a 5G network). Moreover, in some example configurations, the media playback system 100 is implemented without the network 104, and devices comprising the media playback system 100 can communicate with each other, for example, via one or more direct connections, PANs, telecommunication networks, and/or other suitable communications links.
[0164] In some example configurations, audio content sources may be regularly added or removed from the media playback system 100. In some example configurations, for example, the media playback system 100 performs an indexing of media items when one or more media content sources are updated, added to, and/or removed from the media playback system 100. The media playback system 100 can scan identifiable media items in some or all folders and/or directories accessible to the playback devices 110, and generate or update a media content database comprising metadata (e.g., title, artist, album, track length) and other associated information (e.g., URIs, URLs) for each identifiable media item found. In some example configurations, for example, the media content database is stored on one or more of the playback devices 110, network microphone devices 120, and/or control devices 130. [0165] In the illustrated embodiment of Figure IB, the playback devices 1101 and 110m comprise a group 107a. The playback devices 1101 and 110m can be positioned in different rooms in a household and be grouped together in the group 107a on a temporary or permanent basis based on user input received at the control device 130a and/or another control device 130 in the media playback system 100. When arranged in the group 107a, the playback devices 1101 and 110m can be configured to play back the same or similar audio content in synchrony from one or more audio content sources. In certain example configurations, for example, the group 107a comprises a bonded zone in which the playback devices 1101 and 110m comprise left audio and right audio channels, respectively, of multichannel audio content, thereby producing or enhancing a stereo effect of the audio content. In some example configurations, the group 107a includes additional playback devices 110. In other example configurations, however, the media playback system 100 omits the group 107a and/or other grouped arrangements of the playback devices 110. Additional details regarding groups and other arrangements of playback devices are described in further detail below with respect to Figures 1-1 through IM.
[0166] The media playback system 100 includes the NMDs 120a and 120d, each comprising one or more microphones configured to receive voice utterances from a user. In the illustrated embodiment of Figure IB, the NMD 120a is a standalone device and the NMD 120d is integrated into the playback device 1 lOn. The NMD 120a, for example, is configured to receive voice input 121 from a user 123. In some example configurations, the NMD 120a transmits data associated with the received voice input 121 to a voice assistant service (VAS) configured to (i) process the received voice input data and (ii) transmit a corresponding command to the media playback system 100. In some aspects, for example, the computing device 106c comprises one or more modules and/or servers of a VAS (e.g., a VAS operated by one or more of SONOS®, AMAZON®, GOOGLE® APPLE®, MICROSOFT®). The computing device 106c can receive the voice input data from the NMD 120a via the network 104 and the links 103. In response to receiving the voice input data, the computing device 106c processes the voice input data (i.e., “Play Hey Jude by The Beatles”), and determines that the processed voice input includes a command to play a song (e.g., “Hey Jude”). The computing device 106c accordingly transmits commands to the media playback system 100 to play back “Hey Jude” by the Beatles from a suitable media service (e.g., via one or more of the computing devices 106) on one or more of the playback devices 110. b. Suitable Playback Devices
[0167] Figure 1C is a block diagram of the playback device 110a comprising an input/output 111. The input/output 111 can include an analog I/O I l la (e.g., one or more wires, cables, and/or other suitable communications links configured to carry analog signals) and/or a digital I/O 111b (e.g., one or more wires, cables, or other suitable communications links configured to carry digital signals). In some example configurations, the analog I/O 11 la is an audio line-in input connection comprising, for example, an auto-detecting 3.5mm audio line-in connection. In some example configurations, the digital I/O 111b comprises a Sony/Philips Digital Interface Format (S/PDIF) communication interface and/or cable and/or a Toshiba Link (TOSLINK) cable. In some example configurations, the digital I/O 111b comprises an High-Definition Multimedia Interface (HDMI) interface and/or cable. In some example configurations, the digital I/O 111b includes one or more wireless communications links comprising, for example, a radio frequency (RF), infrared, WiFi, Bluetooth, or another suitable communication protocol. In certain example configurations, the analog I/O I l la and the digital I/O 111b comprise interfaces (e.g., ports, plugs, jacks) configured to receive connectors of cables transmitting analog and digital signals, respectively, without necessarily including cables.
[0168] The playback device 110a, for example, can receive media content (e.g., audio content comprising music and/or other sounds) from a local audio source 105 via the input/output 111 (e.g., a cable, a wire, a PAN, a Bluetooth connection, an ad hoc wired or wireless communication network, and/or another suitable communications link). The local audio source 105 can comprise, for example, a mobile device (e.g., a smartphone, a tablet, a laptop computer) or another suitable audio component (e.g., a television, a desktop computer, an amplifier, a phonograph, a Blu-ray player, a memory storing digital media files). In some aspects, the local audio source 105 includes local music libraries on a smartphone, a computer, a networked-attached storage (NAS), and/or another suitable device configured to store media files. In certain example configurations, one or more of the playback devices 110, NMDs 120, and/or control devices 130 comprise the local audio source 105. In other example configurations, however, the media playback system omits the local audio source 105 altogether. In some example configurations, the playback device 110a does not include an input/output 111 and receives all audio content via the network 104.
[0169] The playback device 110a further comprises electronics 112, a user interface 113 (e.g., one or more buttons, knobs, dials, touch-sensitive surfaces, displays, touchscreens), and one or more transducers 114 (referred to hereinafter as “the transducers 114”). The electronics 112 is configured to receive audio from an audio source (e.g., the local audio source 105) via the input/output 111, one or more of the computing devices 106a-c via the network 104 (Figure IB)), amplify the received audio, and output the amplified audio for playback via one or more of the transducers 114. In some example configurations, the playback device 110a optionally includes one or more microphones 115 (e.g., a single microphone, a plurality of microphones, a microphone array) (hereinafter referred to as “the microphones 115”). In certain example configurations, for example, the playback device 110a having one or more of the optional microphones 115 can operate as an NMD configured to receive voice input from a user and correspondingly perform one or more operations based on the received voice input.
[0170] In the illustrated embodiment of Figure 1C, the electronics 112 comprise one or more processors 112a (referred to hereinafter as “the processors 112a”), memory 112b, software components 112c, a network interface 112d, one or more audio processing components 112g (referred to hereinafter as “the audio components 112g”), one or more audio amplifiers 112h (referred to hereinafter as “the amplifiers 112h”), and power 112i (e.g., one or more power supplies, power cables, power receptacles, batteries, induction coils, Power-over Ethernet (POE) interfaces, and/or other suitable sources of electric power). In some example configurations, the electronics 112 optionally include one or more other components 112j (e.g., one or more sensors, video displays, touchscreens, battery charging bases).
[0171] The processors 112a can comprise clock-driven computing component(s) configured to process data, and the memory 112b can comprise a computer-readable medium (e.g., a tangible, non-transitory computer-readable medium, data storage loaded with one or more of the software components 112c) configured to store instructions for performing various operations and/or functions. The processors 112a are configured to execute the instructions stored on the memory 112b to perform one or more of the operations. The operations can include, for example, causing the playback device 110a to retrieve audio information from an audio source (e.g., one or more of the computing devices 106a-c (Figure IB)), and/or another one of the playback devices 110. In some example configurations, the operations further include causing the playback device 110a to send audio information to another one of the playback devices 110a and/or another device (e.g., one of the NMDs 120). Certain example configurations include operations causing the playback device 110a to pair with another of the one or more playback devices 110 to enable a multi-channel audio environment (e.g., a stereo pair, a bonded zone).
[0172] The processors 112a can be further configured to perform operations causing the playback device 110a to synchronize playback of audio content with another of the one or more playback devices 110. As those of ordinary skill in the art will appreciate, during synchronous playback of audio content on a plurality of playback devices, a listener will preferably be unable to perceive time-delay differences between playback of the audio content by the playback device 110a and the other one or more other playback devices 110. Additional details regarding audio playback synchronization among playback devices can be found, for example, in U.S. Patent No. 8,234,395, which was incorporated by reference above.
[0173] In some example configurations, the memory 112b is further configured to store data associated with the playback device 110a, such as one or more zones and/or zone groups of which the playback device 110a is a member, audio sources accessible to the playback device 110a, and/or a playback queue that the playback device 110a (and/or another of the one or more playback devices) can be associated with. The stored data can comprise one or more state variables that are periodically updated and used to describe a state of the playback device 110a. The memory 112b can also include data associated with a state of one or more of the other devices (e.g., the playback devices 110, NMDs 120, control devices 130) of the media playback system 100. In some aspects, for example, the state data is shared during predetermined intervals of time (e.g., every 5 seconds, every 10 seconds, every 60 seconds) among at least a portion of the devices of the media playback system 100, so that one or more of the devices have the most recent data associated with the media playback system 100.
[0174] The network interface 112d is configured to facilitate a transmission of data between the playback device 110a and one or more other devices on a data network such as, for example, the links 103 and/or the network 104 (Figure IB). The network interface 112d is configured to transmit and receive data corresponding to media content (e.g., audio content, video content, text, photographs) and other signals (e.g., non-transitory signals) comprising digital packet data including an Internet Protocol (IP)-based source address and/or an IPbased destination address. The network interface 112d can parse the digital packet data such that the electronics 112 properly receives and processes the data destined for the playback device 110a.
[0175] In the illustrated embodiment of Figure 1C, the network interface 112d comprises one or more wireless interfaces 112e (referred to hereinafter as “the wireless interface 112e”). The wireless interface 112e (e.g., a suitable interface comprising one or more antennae) can be configured to wirelessly communicate with one or more other devices (e.g., one or more of the other playback devices 110, NMDs 120, and/or control devices 130) that are communicatively coupled to the network 104 (Figure IB) in accordance with a suitable wireless communication protocol (e.g., WiFi, Bluetooth, LTE). In some example configurations, the network interface 112d optionally includes a wired interface 112f (e.g., an interface or receptacle configured to receive a network cable such as an Ethernet, a USB-A, USB-C, and/or Thunderbolt cable) configured to communicate over a wired connection with other devices in accordance with a suitable wired communication protocol. In certain example configurations, the network interface 112d includes the wired interface 112f and excludes the wireless interface 112e. In some example configurations, the electronics 112 excludes the network interface 112d altogether and transmits and receives media content and/or other data via another communication path (e.g., the input/output 111).
[0176] The audio processing components 112g are configured to process and/or filter data comprising media content received by the electronics 112 (e.g., via the input/output 111 and/or the network interface 112d) to produce output audio signals. In some example configurations, the audio processing components 112g comprise, for example, one or more digital-to-analog converters (DAC), audio preprocessing components, audio enhancement components, a digital signal processors (DSPs), and/or other suitable audio processing components, modules, circuits, etc. In certain example configurations, one or more of the audio processing components 112g can comprise one or more subcomponents of the processors 112a. In some example configurations, the electronics 112 omits the audio processing components 112g. In some aspects, for example, the processors 112a execute instructions stored on the memory 112b to perform audio processing operations to produce the output audio signals.
[0177] The amplifiers 112h are configured to receive and amplify the audio output signals produced by the audio processing components 112g and/or the processors 112a. The amplifiers 112h can comprise electronic devices and/or components configured to amplify audio signals to levels sufficient for driving one or more of the transducers 114. In some example configurations, for example, the amplifiers 112h include one or more switching or class-D power amplifiers. In other example configurations, however, the amplifiers include one or more other types of power amplifiers (e.g., linear gain power amplifiers, class-A amplifiers, class-B amplifiers, class-AB amplifiers, class-C amplifiers, class-D amplifiers, class-E amplifiers, class-F amplifiers, class-G and/or class H amplifiers, and/or another suitable type of power amplifier). In certain example configurations, the amplifiers 112h comprise a suitable combination of two or more of the foregoing types of power amplifiers. Moreover, in some example configurations, individual ones of the amplifiers 112h correspond to individual ones of the transducers 114. In other example configurations, however, the electronics 112 includes a single one of the amplifiers 112h configured to output amplified audio signals to a plurality of the transducers 114. In some other example configurations, the electronics 112 omits the amplifiers 112h. [0178] The transducers 114 (e.g., one or more speakers and/or speaker drivers) receive the amplified audio signals from the amplifier 112h and render or output the amplified audio signals as sound (e.g., audible sound waves having a frequency between about 20 Hertz (Hz) and 20 kilohertz (kHz)). In some example configurations, the transducers 114 can comprise a single transducer. In other example configurations, however, the transducers 114 comprise a plurality of audio transducers. In some example configurations, the transducers 114 comprise more than one type of transducer. For example, the transducers 114 can include one or more low frequency transducers (e.g., subwoofers, woofers), midrange frequency transducers (e.g., mid-range transducers, mid-woofers), and one or more high frequency transducers (e.g., one or more tweeters). As used herein, “low frequency” can generally refer to audible frequencies below about 500 Hz, “mid-range frequency” can generally refer to audible frequencies between about 500 Hz and about 2 kHz, and “high frequency” can generally refer to audible frequencies above 2 kHz. In certain example configurations, however, one or more of the transducers 114 comprise transducers that do not adhere to the foregoing frequency ranges. For example, one of the transducers 114 may comprise a mid-woofer transducer configured to output sound at frequencies between about 200 Hz and about 5 kHz.
[0179] By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including, for example, a “SONOS ONE,” “PLAY:1,” “PLAY:3,” “PLAYA,” “PLAYBAR,” “PLAYBASE,” “CONNECT: AMP,” “CONNECT,” and “SUB.” Other suitable playback devices may additionally or alternatively be used to implement the playback devices of example configurations disclosed herein. Additionally, one of ordinary skilled in the art will appreciate that a playback device is not limited to the examples described herein or to SONOS product offerings. In some example configurations, for example, one or more playback devices 110 comprises wired or wireless headphones (e.g., over-the-ear headphones, on-ear headphones, in-ear earphones). In other example configurations, one or more of the playback devices 110 comprise a docking station and/or an interface configured to interact with a docking station for personal mobile media playback devices. In certain example configurations, a playback device may be integral to another device or component such as a television, a lighting fixture, or some other device for indoor or outdoor use. In some example configurations, a playback device omits a user interface and/or one or more transducers. For example, FIG. ID is a block diagram of a playback device 1 lOp comprising the input/output 111 and electronics 112 without the user interface 113 or transducers 114. [0180] Figure IE is a block diagram of a bonded playback device 1 lOq comprising the playback device 110a (Figure 1C) sonically bonded with the playback device 1 lOi (e.g., a subwoofer) (Figure 1 A). In the illustrated embodiment, the playback devices 110a and 1 lOi are separate ones of the playback devices 110 housed in separate enclosures. In some example configurations, however, the bonded playback device 1 lOq comprises a single enclosure housing both the playback devices 110a and 1 lOi. The bonded playback device 1 lOq can be configured to process and reproduce sound differently than an unbonded playback device (e.g., the playback device 110a of Figure 1C) and/or paired or bonded playback devices (e.g., the playback devices 1101 and 110m of Figure IB). In some example configurations, for example, the playback device 110a is full-range playback device configured to render low frequency, mid-range frequency, and high frequency audio content, and the playback device 1 lOi is a subwoofer configured to render low frequency audio content. In some aspects, the playback device 110a, when bonded with the first playback device, is configured to render only the mid-range and high frequency components of a particular audio content, while the playback device 1 lOi renders the low frequency component of the particular audio content. In some example configurations, the bonded playback device 1 lOq includes additional playback devices and/or another bonded playback device. Additional playback device example configurations are described in further detail below with respect to Figures 2A-3D. c. Suitable Network Microphone Devices (NMDs) [0181] Figure IF is a block diagram of the NMD 120a (Figures 1 A and IB). The NMD 120a includes one or more voice processing components 124 (hereinafter “the voice components 124”) and several components described with respect to the playback device 110a (Figure 1C) including the processors 112a, the memory 112b, and the microphones 115. The NMD 120a optionally comprises other components also included in the playback device 110a (Figure 1C), such as the user interface 113 and/or the transducers 114. In some example configurations, the NMD 120a is configured as a media playback device (e.g., one or more of the playback devices 110), and further includes, for example, one or more of the audio processing components 112g (Figure 1C), the transducers 114, and/or other playback device components. In certain example configurations, the NMD 120a comprises an Internet of Things (loT) device such as, for example, a thermostat, alarm panel, fire and/or smoke detector, etc. In some example configurations, the NMD 120a comprises the microphones 115, the voice processing 124, and only a portion of the components of the electronics 112 described above with respect to Figure IB. In some aspects, for example, the NMD 120a includes the processor 112a and the memory 112b (Figure IB), while omitting one or more other components of the electronics 112. In some example configurations, the NMD 120a includes additional components (e.g., one or more sensors, cameras, thermometers, barometers, hygrometers).
[0182] In some example configurations, an NMD can be integrated into a playback device. Figure 1G is a block diagram of a playback device 1 lOr comprising an NMD 120d. The playback device 1 lOr can comprise many or all of the components of the playback device 110a and further include the microphones 115 and voice processing 124 (Figure IF). The playback device 1 lOr optionally includes an integrated control device 130c. The control device 130c can comprise, for example, a user interface (e.g., the user interface 113 of Figure IB) configured to receive user input (e.g., touch input, voice input) without a separate control device. In other example configurations, however, the playback device 1 lOr receives commands from another control device (e.g., the control device 130a of Figure IB).
Additional NMD example configurations are described in further detail below with respect to Figures 3A-3F.
[0183] Referring again to Figure IF, the microphones 115 are configured to acquire, capture, and/or receive sound from an environment (e.g., the environment 101 of Figure 1 A) and/or a room in which the NMD 120a is positioned. The received sound can include, for example, vocal utterances, audio played back by the NMD 120a and/or another playback device, background voices, ambient sounds, etc. The microphones 115 convert the received sound into electrical signals to produce microphone data. The voice processing 124 receives and analyzes the microphone data to determine whether a voice input is present in the microphone data. The voice input can comprise, for example, an activation word followed by an utterance including a user request. As those of ordinary skill in the art will appreciate, an activation word is a word or other audio cue that signifying a user voice input. For instance, in querying the AMAZON® VAS, a user might speak the activation word "Alexa." Other examples include "Ok, Google" for invoking the GOOGLE® VAS and "Hey, Siri" for invoking the APPLE® VAS.
[0184] After detecting the activation word, voice processing 124 monitors the microphone data for an accompanying user request in the voice input. The user request may include, for example, a command to control a third-party device, such as a thermostat (e.g., NEST® thermostat), an illumination device (e.g., a PHILIPS HUE ® lighting device), or a media playback device (e.g., a Sonos® playback device). For example, a user might speak the activation word “Alexa” followed by the utterance “set the thermostat to 68 degrees” to set a temperature in a home (e.g., the environment 101 of Figure 1 A). The user might speak the same activation word followed by the utterance “turn on the living room” to turn on illumination devices in a living room area of the home. The user may similarly speak an activation word followed by a request to play a particular song, an album, or a playlist of music on a playback device in the home. Additional description regarding receiving and processing voice input data can be found in further detail below with respect to Figures 3 A- 3F. d. Suitable Control Devices
[0185] Figure 1H is a partially schematic diagram of the control device 130a (Figures 1 A and IB). As used herein, the term “control device” can be used interchangeably with “controller” or “control system.” Among other features, the control device 130a is configured to receive user input related to the media playback system 100 and, in response, cause one or more devices in the media playback system 100 to perform an action(s) or operation(s) corresponding to the user input. In the illustrated embodiment, the control device 130a comprises a smartphone (e.g., an iPhone™ an Android phone) on which media playback system controller application software is installed. In some example configurations, the control device 130a comprises, for example, a tablet (e.g., an iPad™), a computer (e.g., a laptop computer, a desktop computer), and/or another suitable device (e.g., a television, an automobile audio head unit, an loT device). In certain example configurations, the control device 130a comprises a dedicated controller for the media playback system 100. In other example configurations, as described above with respect to Figure 1G, the control device 130a is integrated into another device in the media playback system 100 (e.g., one more of the playback devices 110, NMDs 120, and/or other suitable devices configured to communicate over a network).
[0186] The control device 130a includes electronics 132, a user interface 133, one or more speakers 134, and one or more microphones 135. The electronics 132 comprise one or more processors 132a (referred to hereinafter as “the processors 132a”), a memory 132b, software components 132c, and a network interface 132d. The processor 132a can be configured to perform functions relevant to facilitating user access, control, and configuration of the media playback system 100. The memory 132b can comprise data storage that can be loaded with one or more of the software components executable by the processor 302 to perform those functions. The software components 132c can comprise applications and/or other executable software configured to facilitate control of the media playback system 100. The memory 112b can be configured to store, for example, the software components 132c, media playback system controller application software, and/or other data associated with the media playback system 100 and the user.
[0187] The network interface 132d is configured to facilitate network communications between the control device 130a and one or more other devices in the media playback system 100, and/or one or more remote devices. In some example configurations, the network interface 132d is configured to operate according to one or more suitable communication industry standards (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.1 In, 802.1 lac, 802.15, 4G, LTE). The network interface 132d can be configured, for example, to transmit data to and/or receive data from the playback devices 110, the NMDs 120, other ones of the control devices 130, one of the computing devices 106 of Figure IB, devices comprising one or more other media playback systems, etc. The transmitted and/or received data can include, for example, playback device control commands, state variables, playback zone and/or zone group configurations. For instance, based on user input received at the user interface 133, the network interface 132d can transmit a playback device control command (e.g., volume control, audio playback control, audio content selection) from the control device 304 to one or more of playback devices. The network interface 132d can also transmit and/or receive configuration changes such as, for example, adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, separating one or more playback devices from a bonded or consolidated player, among others. Additional description of zones and groups can be found below with respect to Figures 1-1 through IM.
[0188] The user interface 133 is configured to receive user input and can facilitate 'control of the media playback system 100. The user interface 133 includes media content art 133a (e.g., album art, lyrics, videos), a playback status indicator 133b (e.g., an elapsed and/or remaining time indicator), media content information region 133c, a playback control region 133d, and a zone indicator 133e. The media content information region 133c can include a display of relevant information (e.g., title, artist, album, genre, release year) about media content currently playing and/or media content in a queue or playlist. The playback control region 133d can include selectable (e.g., via touch input and/or via a cursor or another suitable selector) icons to cause one or more playback devices in a selected playback zone or zone group to perform playback actions such as, for example, play or pause, fast forward, rewind, skip to next, skip to previous, enter/exit shuffle mode, enter/exit repeat mode, enter/exit cross fade mode, etc. The playback control region 133d may also include selectable icons to modify equalization settings, playback volume, and/or other suitable playback actions. In the illustrated embodiment, the user interface 133 comprises a display presented on a touch screen interface of a smartphone (e.g., an iPhone™ an Android phone). In some example configurations, however, user interfaces of varying formats, styles, and interactive sequences may alternatively be implemented on one or more network devices to provide comparable control access to a media playback system.
[0189] The one or more speakers 134 (e.g., one or more transducers) can be configured to output sound to the user of the control device 130a. In some example configurations, the one or more speakers comprise individual transducers configured to correspondingly output low frequencies, mid-range frequencies, and/or high frequencies. In some aspects, for example, the control device 130a is configured as a playback device (e.g., one of the playback devices 110). Similarly, in some example configurations the control device 130a is configured as an NMD (e.g., one of the NMDs 120), receiving voice commands and other sounds via the one or more microphones 135.
[0190] The one or more microphones 135 can comprise, for example, one or more condenser microphones, electret condenser microphones, dynamic microphones, and/or other suitable types of microphones or transducers. In some example configurations, two or more of the microphones 135 are arranged to capture location information of an audio source (e.g., voice, audible sound) and/or configured to facilitate filtering of background noise. Moreover, in certain example configurations, the control device 130a is configured to operate as playback device and an NMD. In other example configurations, however, the control device 130a omits the one or more speakers 134 and/or the one or more microphones 135. For instance, the control device 130a may comprise a device (e.g., a thermostat, an loT device, a network device) comprising a portion of the electronics 132 and the user interface 133 (e.g., a touch screen) without any speakers or microphones. Additional control device example configurations are described in further detail below with respect to Figures 4A-4D and 5. e. Suitable Playback Device Configurations
[0191] Figures 1-1 through IM show example configurations of playback devices in zones and zone groups. Referring first to Figure IM, in one example, a single playback device may belong to a zone. For example, the playback device 110g in the second bedroom 101c (FIG. 1A) may belong to Zone C. In some implementations described below, multiple playback devices may be “bonded” to form a “bonded pair” which together form a single zone. For example, the playback device 1101 (e.g., a left playback device) can be bonded to the playback device 1101 (e.g., a left playback device) to form Zone A. Bonded playback devices may have different playback responsibilities (e.g., channel responsibilities). In another implementation described below, multiple playback devices may be merged to form a single zone. For example, the playback device 1 lOh (e.g., a front playback device) may be merged with the playback device 1 lOi (e.g., a subwoofer), and the playback devices 1 lOj and 110k (e.g., left and right surround speakers, respectively) to form a single Zone D. In another example, the playback devices 110g and 1 lOh can be merged to form a merged group or a zone group 108b. The merged playback devices 110g and 1 lOh may not be specifically assigned different playback responsibilities. That is, the merged playback devices 1 lOh and 1 lOi may, aside from playing audio content in synchrony, each play audio content as they would if they were not merged.
[0192] Each zone in the media playback system 100 may be provided for control as a single user interface (UI) entity. For example, Zone A may be provided as a single entity named Master Bathroom. Zone B may be provided as a single entity named Master Bedroom. Zone C may be provided as a single entity named Second Bedroom.
[0193] Playback devices that are bonded may have different playback responsibilities, such as responsibilities for certain audio channels. For example, as shown in Figure 1 -I, the playback devices 1101 and 110m may be bonded so as to produce or enhance a stereo effect of audio content. In this example, the playback device 1101 may be configured to play a left channel audio component, while the playback device 110k may be configured to play a right channel audio component. In some implementations, such stereo bonding may be referred to as “pairing.”
[0194] Additionally, bonded playback devices may have additional and/or different respective speaker drivers. As shown in Figure 1 J, the playback device 1 lOh named Front may be bonded with the playback device 1 lOi named SUB. The Front device 1 lOh can be configured to render a range of mid to high frequencies and the SUB device 1 lOi can be configured render low frequencies. When unbonded, however, the Front device 1 lOh can be configured render a full range of frequencies. As another example, Figure IK shows the Front and SUB devices 1 lOh and 1 lOi further bonded with Left and Right playback devices 1 lOj and 110k, respectively. In some implementations, the Right and Left devices 1 lOj and 102k can be configured to form surround or “satellite” channels of a home theater system. The bonded playback devices 1 lOh, 1 lOi, 1 lOj, and 110k may form a single Zone D (FIG. IM). [0195] Playback devices that are merged may not have assigned playback responsibilities, and may each render the full range of audio content the respective playback device is capable of. Nevertheless, merged devices may be represented as a single UI entity (i.e., a zone, as discussed above). For instance, the playback devices 110a and 1 lOn the master bathroom have the single UI entity of Zone A. In one embodiment, the playback devices 110a and 1 lOn may each output the full range of audio content each respective playback devices 110a and 1 lOn are capable of, in synchrony.
[0196] In some example configurations, an NMD is bonded or merged with another device so as to form a zone. For example, the NMD 120b may be bonded with the playback device 1 lOe, which together form Zone F, named Living Room. In other example configurations, a stand-alone network microphone device may be in a zone by itself. In other example configurations, however, a stand-alone network microphone device may not be associated with a zone. Additional details regarding associating network microphone devices and playback devices as designated or default devices may be found, for example, in previously referenced U.S. Patent Application No. 15/438,749.
[0197] Zones of individual, bonded, and/or merged devices may be grouped to form a zone group. For example, referring to Figure IM, Zone A may be grouped with Zone B to form a zone group 108a that includes the two zones. Similarly, Zone G may be grouped with Zone H to form the zone group 108b. As another example, Zone A may be grouped with one or more other Zones C-I. The Zones A-I may be grouped and ungrouped in numerous ways. For example, three, four, five, or more (e.g., all) of the Zones A-I may be grouped. When grouped, the zones of individual and/or bonded playback devices may play back audio in synchrony with one another, as described in previously referenced U.S. Patent No. 8,234,395. Playback devices may be dynamically grouped and ungrouped to form new or different groups that synchronously play back audio content.
[0198] In various implementations, the zones in an environment may be the default name of a zone within the group or a combination of the names of the zones within a zone group. For example, Zone Group 108b can have be assigned a name such as “Dining + Kitchen”, as shown in Figure IM. In some example configurations, a zone group may be given a unique name selected by a user.
[0199] Certain data may be stored in a memory of a playback device (e.g., the memory 112b of Figure 1C) as one or more state variables that are periodically updated and used to describe the state of a playback zone, the playback device(s), and/or a zone group associated therewith. The memory may also include the data associated with the state of the other devices of the media system, and shared from time to time among the devices so that one or more of the devices have the most recent data associated with the system.
[0200] In some example configurations, the memory may store instances of various variable types associated with the states. Variables instances may be stored with identifiers (e.g., tags) corresponding to type. For example, certain identifiers may be a first type “al” to identify playback device(s) of a zone, a second type “bl” to identify playback device(s) that may be bonded in the zone, and a third type “cl” to identify a zone group to which the zone may belong. As a related example, identifiers associated with the second bedroom 101c may indicate that the playback device is the only playback device of the Zone C and not in a zone group. Identifiers associated with the Den may indicate that the Den is not grouped with other zones but includes bonded playback devices 11 Oh- 110k. Identifiers associated with the Dining Room may indicate that the Dining Room is part of the Dining + Kitchen zone group 108b and that devices 110b and 1 lOd are grouped (FIG. IL). Identifiers associated with the Kitchen may indicate the same or similar information by virtue of the Kitchen being part of the Dining + Kitchen zone group 108b. Other example zone variables and identifiers are described below.
[0201] In yet another example, the media playback system 100 may variables or identifiers representing other associations of zones and zone groups, such as identifiers associated with Areas, as shown in Figure IM. An area may involve a cluster of zone groups and/or zones not within a zone group. For instance, Figure IM shows an Upper Area 109a including Zones A-D, and a Lower Area 109b including Zones E-I. In one aspect, an Area may be used to invoke a cluster of zone groups and/or zones that share one or more zones and/or zone groups of another cluster. In another aspect, this differs from a zone group, which does not share a zone with another zone group. Further examples of techniques for implementing Areas may be found, for example, in U.S. Application No. 15/682,506 filed August 21, 2017 and titled “Room Association Based on Name,” and U.S. Patent No. 8,483,853 filed September 11, 2007, and titled “Controlling and manipulating groupings in a multi-zone media system.” Each of these applications is incorporated herein by reference in its entirety. In some example configurations, the media playback system 100 may not implement Areas, in which case the system may not store variables associated with Areas.
III. Example Systems and Devices
[0202] Figure 2A is a front isometric view of a playback device 210 configured in accordance with aspects of the disclosed technology. Figure 2B is a front isometric view of the playback device 210 without a grille 216e. Figure 2C is an exploded view of the playback device 210. Referring to Figures 2A-2C together, the playback device 210 comprises a housing 216 that includes an upper portion 216a, a right or first side portion 216b, a lower portion 216c, a left or second side portion 216d, the grille 216e, and a rear portion 216f. A plurality of fasteners 216g (e.g., one or more screws, rivets, clips) attaches a frame 216h to the housing 216. A cavity 216j (Figure 2C) in the housing 216 is configured to receive the frame 216h and electronics 212. The frame 216h is configured to carry a plurality of transducers 214 (identified individually in Figure 2B as transducers 214a-f). The electronics 212 (e.g., the electronics 112 of Figure 1C) is configured to receive audio content from an audio source and send electrical signals corresponding to the audio content to the transducers 214 for playback.
[0203] The transducers 214 are configured to receive the electrical signals from the electronics 112, and further configured to convert the received electrical signals into audible sound during playback. For instance, the transducers 214a-c (e.g., tweeters) can be configured to output high frequency sound (e.g., sound waves having a frequency greater than about 2 kHz). The transducers 214d-f (e.g., mid-woofers, woofers, midrange speakers) can be configured output sound at frequencies lower than the transducers 214a-c (e.g., sound waves having a frequency lower than about 2 kHz). In some example configurations, the playback device 210 includes a number of transducers different than those illustrated in Figures 2A-2C. For example, as described in further detail below with respect to Figures 3 A- 3C, the playback device 210 can include fewer than six transducers (e.g., one, two, three). In other example configurations, however, the playback device 210 includes more than six transducers (e.g., nine, ten). Moreover, in some example configurations, all or a portion of the transducers 214 are configured to operate as a phased array to desirably adjust (e.g., narrow or widen) a radiation pattern of the transducers 214, thereby altering a user’s perception of the sound emitted from the playback device 210.
[0204] In the illustrated embodiment of Figures 2A-2C, a filter 216i is axially aligned with the transducer 214b. The filter 216i can be configured to desirably attenuate a predetermined range of frequencies that the transducer 214b outputs to improve sound quality and a perceived sound stage output collectively by the transducers 214. In some example configurations, however, the playback device 210 omits the filter 216i. In other example configurations, the playback device 210 includes one or more additional filters aligned with the transducers 214b and/or at least another of the transducers 214. [0205] Figures 3 A and 3B are front and right isometric side views, respectively, of an NMD 320 configured in accordance with example configurations of the disclosed technology. Figure 3C is an exploded view of the NMD 320. Figure 3D is an enlarged view of a portion of Figure 3B including a user interface 313 of the NMD 320. Referring first to Figures 3 A- 3C, the NMD 320 includes a housing 316 comprising an upper portion 316a, a lower portion 316b and an intermediate portion 316c (e.g., a grille). A plurality of ports, holes or apertures 316d in the upper portion 316a allow sound to pass through to one or more microphones 315 (Figure 3C) positioned within the housing 316. The one or more microphones 315 are configured to received sound via the apertures 316d and produce electrical signals based on the received sound. In the illustrated embodiment, a frame 316e (Figure 3C) of the housing 316 surrounds cavities 316f and 316g configured to house, respectively, a first transducer 314a (e.g., a tweeter) and a second transducer 314b (e.g., a mid-woofer, a midrange speaker, a woofer). In other example configurations, however, the NMD 320 includes a single transducer, or more than two (e.g., two, five, six) transducers. In certain example configurations, the NMD 320 omits the transducers 314a and 314b altogether.
[0206] Electronics 312 (Figure 3C) includes components configured to drive the transducers 314a and 314b, and further configured to analyze audio information corresponding to the electrical signals produced by the one or more microphones 315. In some example configurations, for example, the electronics 312 comprises many or all of the components of the electronics 112 described above with respect to Figure 1C. In certain example configurations, the electronics 312 includes components described above with respect to Figure IF such as, for example, the one or more processors 112a, the memory 112b, the software components 112c, the network interface 112d, etc. In some example configurations, the electronics 312 includes additional suitable components (e.g., proximity or other sensors).
[0207] Referring to Figure 3D, the user interface 313 includes a plurality of control surfaces (e.g., buttons, knobs, capacitive surfaces) including a first control surface 313a (e.g., a previous control), a second control surface 313b (e.g., a next control), and a third control surface 313c (e.g., a play and/or pause control). A fourth control surface 313d is configured to receive touch input corresponding to activation and deactivation of the one or microphones 315. A first indicator 313e (e.g., one or more light emitting diodes (LEDs) or another suitable illuminator) can be configured to illuminate only when the one or more microphones 315 are activated. A second indicator 313f (e.g., one or more LEDs) can be configured to remain solid during normal operation and to blink or otherwise change from solid to indicate a detection of voice activity. In some example configurations, the user interface 313 includes additional or fewer control surfaces and illuminators. In one embodiment, for example, the user interface 313 includes the first indicator 313e, omitting the second indicator 313f. Moreover, in certain example configurations, the NMD 320 comprises a playback device and a control device, and the user interface 313 comprises the user interface of the control device
[0208] Referring to Figures 3A-3D together, the NMD 320 is configured to receive voice commands from one or more adjacent users via the one or more microphones 315. As described above with respect to Figure IB, the one or more microphones 315 can acquire, capture, or record sound in a vicinity (e.g., a region within 10m or less of the NMD 320) and transmit electrical signals corresponding to the recorded sound to the electronics 312. The electronics 312 can process the electrical signals and can analyze the resulting audio data to determine a presence of one or more voice commands (e.g., one or more activation words). In some example configurations, for example, after detection of one or more suitable voice commands, the NMD 320 is configured to transmit a portion of the recorded audio data to another device and/or a remote server (e.g., one or more of the computing devices 106 of Figure IB) for further analysis. The remote server can analyze the audio data, determine an appropriate action based on the voice command, and transmit a message to the NMD 320 to perform the appropriate action. For instance, a user may speak “Sonos, play Michael Jackson.” The NMD 320 can, via the one or more microphones 315, record the user’s voice utterance, determine the presence of a voice command, and transmit the audio data having the voice command to a remote server (e.g., one or more of the remote computing devices 106 of Figure IB, one or more servers of a VAS and/or another suitable service). The remote server can analyze the audio data and determine an action corresponding to the command. The remote server can then transmit a command to the NMD 320 to perform the determined action (e.g., play back audio content related to Michael Jackson). The NMD 320 can receive the command and play back the audio content related to Michael Jackson from a media content source. As described above with respect to Figure IB, suitable content sources can include a device or storage communicatively coupled to the NMD 320 via a LAN (e.g., the network 104 of Figure IB), a remote server (e.g., one or more of the remote computing devices 106 of Figure IB), etc. In certain example configurations, however, the NMD 320 determines and/or performs one or more actions corresponding to the one or more voice commands without intervention or involvement of an external device, computer, or server. [0209] Figure 3E is a functional block diagram showing additional features of the NMD 320 in accordance with aspects of the disclosure. The NMD 320 includes components configured to facilitate voice command capture including voice activity detector component s) 312k, beam former components 3121, acoustic echo cancellation (AEC) and/or self-sound suppression components 312m, activation word detector components 312n, and voice/speech conversion components 312o (e.g., voice-to-text and text-to-voice). In the illustrated embodiment of Figure 3E, the foregoing components 312k-312o are shown as separate components. In some example configurations, however, one or more of the components 312k-312o are subcomponents of the processors 112a.
[0210] The beamforming and self-sound suppression components 3121 and 312m are configured to detect an audio signal and determine aspects of voice input represented in the detected audio signal, such as the direction, amplitude, frequency spectrum, etc. The voice activity detector activity components 312k are operably coupled with the beamforming and AEC components 3121 and 312m and are configured to determine a direction and/or directions from which voice activity is likely to have occurred in the detected audio signal. Potential speech directions can be identified by monitoring metrics which distinguish speech from other sounds. Such metrics can include, for example, energy within the speech band relative to background noise and entropy within the speech band, which is measure of spectral structure. As those of ordinary skill in the art will appreciate, speech typically has a lower entropy than most common background noise.
[0211] The activation word detector components 312n are configured to monitor and analyze received audio to determine if any activation words (e.g., wake words) are present in the received audio. The activation word detector components 312n may analyze the received audio using an activation word detection algorithm. If the activation word detector 312n detects an activation word, the NMD 320 may process voice input contained in the received audio. Example activation word detection algorithms accept audio as input and provide an indication of whether an activation word is present in the audio. Many first- and third-party activation word detection algorithms are known and commercially available. For instance, operators of a voice service may make their algorithm available for use in third-party devices. Alternatively, an algorithm may be trained to detect certain activation words. In some example configurations, the activation word detector 312n runs multiple activation word detection algorithms on the received audio simultaneously (or substantially simultaneously). As noted above, different voice services (e.g. AMAZON'S ALEXA®, APPLE'S SIRI®, or MICROSOFT'S CORTANA®) can each use a different activation word for invoking their respective voice service. To support multiple services, the activation word detector 312n may run the received audio through the activation word detection algorithm for each supported voice service in parallel.
[0212] The speech/text conversion components 312o may facilitate processing by converting speech in the voice input to text. In some example configurations, the electronics 312 can include voice recognition software that is trained to a particular user or a particular set of users associated with a household. Such voice recognition software may implement voice-processing algorithms that are tuned to specific voice profile(s). Tuning to specific voice profiles may require less computationally intensive algorithms than traditional voice activity services, which typically sample from a broad base of users and diverse requests that are not targeted to media playback systems.
[0213] Figure 3F is a schematic diagram of an example voice input 328 captured by the NMD 320 in accordance with aspects of the disclosure. The voice input 328 can include a activation word portion 328a and a voice utterance portion 328b. In some example configurations, the activation word 557a can be a known activation word, such as “Alexa,” which is associated with AMAZON'S ALEXA®. In other example configurations, however, the voice input 328 may not include a activation word. In some example configurations, a network microphone device may output an audible and/or visible response upon detection of the activation word portion 328a. In addition or alternately, an NMD may output an audible and/or visible response after processing a voice input and/or a series of voice inputs.
[0214] The voice utterance portion 328b may include, for example, one or more spoken commands (identified individually as a first command 328c and a second command 328e) and one or more spoken keywords (identified individually as a first keyword 328d and a second keyword 328f). In one example, the first command 328c can be a command to play music, such as a specific song, album, playlist, etc. In this example, the keywords may be one or words identifying one or more zones in which the music is to be played, such as the Living Room and the Dining Room shown in Figure 1 A. In some examples, the voice utterance portion 328b can include other information, such as detected pauses (e.g., periods of nonspeech) between words spoken by a user, as shown in Figure 3F. The pauses may demarcate the locations of separate commands, keywords, or other information spoke by the user within the voice utterance portion 328b.
[0215] In some example configurations, the media playback system 100 is configured to temporarily reduce the volume of audio content that it is playing while detecting the activation word portion 557a. The media playback system 100 may restore the volume after processing the voice input 328, as shown in Figure 3F. Such a process can be referred to as ducking, examples of which are disclosed in U.S. Patent Application No. 15/438,749, incorporated by reference herein in its entirety.
[0216] Figures 4A-4D are schematic diagrams of a control device 430 (e.g., the control device 130a of Figure 1H, a smartphone, a tablet, a dedicated control device, an loT device, and/or another suitable device) showing corresponding user interface displays in various states of operation. A first user interface display 43 la (Figure 4A) includes a display name 433a (i.e., “Rooms”). A selected group region 433b displays audio content information (e.g., artist name, track name, album art) of audio content played back in the selected group and/or zone. Group regions 433c and 433d display corresponding group and/or zone name, and audio content information audio content played back or next in a playback queue of the respective group or zone. An audio content region 433 e includes information related to audio content in the selected group and/or zone (i.e., the group and/or zone indicated in the selected group region 433b). A lower display region 433f is configured to receive touch input to display one or more other user interface displays. For example, if a user selects “Browse” in the lower display region 433f, the control device 430 can be configured to output a second user interface display 431b (Figure 4B) comprising a plurality of music services 433g (e.g., Spotify, Radio by Tunein, Apple Music, Pandora, Amazon, TV, local music, line-in) through which the user can browse and from which the user can select media content for play back via one or more playback devices (e.g., one of the playback devices 110 of Figure 1A). Alternatively, if the user selects “My Sonos” in the lower display region 433f, the control device 430 can be configured to output a third user interface display 431c (Figure 4C). A first media content region 433h can include graphical representations (e.g., album art) corresponding to individual albums, stations, or playlists. A second media content region 433i can include graphical representations (e.g., album art) corresponding to individual songs, tracks, or other media content. If the user selections a graphical representation 433j (Figure 4C), the control device 430 can be configured to begin play back of audio content corresponding to the graphical representation 433j and output a fourth user interface display 43 Id fourth user interface display 43 Id includes an enlarged version of the graphical representation 433j , media content information 433k (e.g., track name, artist, album), transport controls 433m (e.g., play, previous, next, pause, volume), and indication 433n of the currently selected group and/or zone name.
[0217] Figure 5 is a schematic diagram of a control device 530 (e.g., a laptop computer, a desktop computer) . The control device 530 includes transducers 534, a microphone 535, and a camera 536. A user interface 531 includes a transport control region 533a, a playback status region 533b, a playback zone region 533c, a playback queue region 533d, and a media content source region 533e. The transport control region comprises one or more controls for controlling media playback including, for example, volume, previous, play/pause, next, repeat, shuffle, track position, crossfade, equalization, etc. The audio content source region 533e includes a listing of one or more media content sources from which a user can select media items for play back and/or adding to a playback queue.
[0218] The playback zone region 533b can include representations of playback zones within the media playback system 100 (Figures 1A and IB). In some example configurations, the graphical representations of playback zones may be selectable to bring up additional selectable icons to manage or configure the playback zones in the media playback system, such as a creation of bonded zones, creation of zone groups, separation of zone groups, renaming of zone groups, etc. In the illustrated embodiment, a “group” icon is provided within each of the graphical representations of playback zones. The “group” icon provided within a graphical representation of a particular zone may be selectable to bring up options to select one or more other zones in the media playback system to be grouped with the particular zone. Once grouped, playback devices in the zones that have been grouped with the particular zone can be configured to play audio content in synchrony with the playback device(s) in the particular zone. Analogously, a “group” icon may be provided within a graphical representation of a zone group. In the illustrated embodiment, the “group” icon may be selectable to bring up options to deselect one or more zones in the zone group to be removed from the zone group. In some example configurations, the control device 530 includes other interactions and implementations for grouping and ungrouping zones via the user interface 531. In certain example configurations, the representations of playback zones in the playback zone region 533b can be dynamically updated as playback zone or zone group configurations are modified.
[0219] The playback status region 533c includes graphical representations of audio content that is presently being played, previously played, or scheduled to play next in the selected playback zone or zone group. The selected playback zone or zone group may be visually distinguished on the user interface, such as within the playback zone region 533b and/or the playback queue region 533d. The graphical representations may include track title, artist name, album name, album year, track length, and other relevant information that may be useful for the user to know when controlling the media playback system 100 via the user interface 531. [0220] The playback queue region 533d includes graphical representations of audio content in a playback queue associated with the selected playback zone or zone group. In some example configurations, each playback zone or zone group may be associated with a playback queue containing information corresponding to zero or more audio items for playback by the playback zone or zone group. For instance, each audio item in the playback queue may comprise a uniform resource identifier (URI), a uniform resource locator (URL) or some other identifier that may be used by a playback device in the playback zone or zone group to find and/or retrieve the audio item from a local audio content source or a networked audio content source, possibly for playback by the playback device. In some example configurations, for example, a playlist can be added to a playback queue, in which information corresponding to each audio item in the playlist may be added to the playback queue. In some example configurations, audio items in a playback queue may be saved as a playlist. In certain example configurations, a playback queue may be empty, or populated but “not in use” when the playback zone or zone group is playing continuously streaming audio content, such as Internet radio that may continue to play until otherwise stopped, rather than discrete audio items that have playback durations. In some example configurations, a playback queue can include Internet radio and/or other streaming audio content items and be “in use” when the playback zone or zone group is playing those items.
[0221] When playback zones or zone groups are “grouped” or “ungrouped,” playback queues associated with the affected playback zones or zone groups may be cleared or reassociated. For example, if a first playback zone including a first playback queue is grouped with a second playback zone including a second playback queue, the established zone group may have an associated playback queue that is initially empty, that contains audio items from the first playback queue (such as if the second playback zone was added to the first playback zone), that contains audio items from the second playback queue (such as if the first playback zone was added to the second playback zone), or a combination of audio items from both the first and second playback queues. Subsequently, if the established zone group is ungrouped, the resulting first playback zone may be re-associated with the previous first playback queue, or be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Similarly, the resulting second playback zone may be re-associated with the previous second playback queue, or be associated with a new playback queue that is empty, or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. [0222] Figure 6 is a message flow diagram illustrating data exchanges between devices of the media playback system 100 (Figures 1A-1M).
[0223] At step 650a, the media playback system 100 receives an indication of selected media content (e.g., one or more songs, albums, playlists, podcasts, videos, stations) via the control device 130a. The selected media content can comprise, for example, media items stored locally on or more devices (e.g., the audio source 105 of Figure 1C) connected to the media playback system and/or media items stored on one or more media service servers (one or more of the remote computing devices 106 of Figure IB). In response to receiving the indication of the selected media content, the control device 130a transmits a message 651a to the playback device 110a (Figures 1 A-1C) to add the selected media content to a playback queue on the playback device 110a.
[0224] At step 650b, the playback device 110a receives the message 651a and adds the selected media content to the playback queue for play back.
[0225] At step 650c, the control device 130a receives input corresponding to a command to play back the selected media content. In response to receiving the input corresponding to the command to play back the selected media content, the control device 130a transmits a message 651b to the playback device 110a causing the playback device 110a to play back the selected media content. In response to receiving the message 651b, the playback device 110a transmits a message 651c to the first computing device 106a requesting the selected media content. The first computing device 106a, in response to receiving the message 651c, transmits a message 65 Id comprising data (e.g., audio data, video data, a URL, a URI) corresponding to the requested media content.
[0226] At step 650d, the playback device 110a receives the message 65 Id with the data corresponding to the requested media content and plays back the associated media content.
[0227] At step 650e, the playback device 110a optionally causes one or more other devices to play back the selected media content. In one example, the playback device 110a is one of a bonded zone of two or more players (Figure IM). The playback device 110a can receive the selected media content and transmit all or a portion of the media content to other devices in the bonded zone. In another example, the playback device 110a is a coordinator of a group and is configured to transmit and receive timing information from one or more other devices in the group. The other one or more devices in the group can receive the selected media content from the first computing device 106a, and begin playback of the selected media content in response to a message from the playback device 110a such that all of the devices in the group play back the selected media content in synchrony.
IV. Example Multi-Player Playback Device
[0228] Figure 7 shows an example block diagram of a Multi-Player Playback Device 700 configurable to implement from one to eight logical players according to some example embodiments.
[0229] As mentioned earlier, a Multi-Player Playback Device is a playback device comprising multiple configurable audio outputs, one or more processors, and tangible, non- transitory computer readable media storing program instructions that are executed by the one or more processors to cause the Multi-Player Playback Device to perform the Multi-Player Playback Device features and functions described herein. The Multi-Player Playback Device 700 can be configured to operate in any of the grouped configurations described herein, including but not limited to, the Area Zone configurations disclosed above. Further, when configured in an Area Zone configuration, the Multi-Player Playback Device 700 can be configured to perform any of the Area Zone features disclosed above, including but not limited to performing the functions of an Area Zone Primary and/or Area Zone Secondary. [0230] The example Multi-Player Playback Device 700 illustrated in Figure 7 includes one or more processors 702 and one or more tangible, non-transitory computer- readable memory 704. The tangible, non-transitory computer-readable memory 704 is configured to store program instructions that are executable by the one or more processors 702. When executed by the one or more processors 702, the program instructions cause the Multi-Player Playback Device 700 to perform the Multi-Player Playback Device functions disclosed and described herein.
[0231] Multi-Player Playback Device 700 also includes one or more network interfaces 706. The network interfaces may include any one or more (i) wired network interfaces, e.g., Ethernet, Universal Serial Bus, Firewire, Power-over-Ethemet, or any other type of wired network interface now known or later developed that is suitable for transmitting and receiving the types of data described herein and/or (ii) wireless network interfaces, e.g., WiFi, Bluetooth, 4G/5G, or any other type of wireless interface now known or later developed that is suitable for transmitting and receive the types of data described herein. [0232] Multi-Player Playback Device 700 includes amplifiers 710-1, 710-2, 710-3, and 710-4, where each amplifier is connected to two audio outputs. In particular, (i) amplifier 710-1 is connected to audio outputs 712-1 and 712-2, (ii) amplifier 710-2 is connected to audio outputs 712-3 and 712-4, (iii) amplifier 710-3 is connected to audio outputs 712-5 and 712-6; and (iv) amplifier 710-4 is connected to audio outputs 712-7 and 712-8. Multi-Player Playback Device 700 includes four amplifiers 710-1 through 710-4 and eight audio outputs 712-1 through 712-8 as an illustrative example. Other embodiments may have a different number of amplifiers, a different number of audio outputs, and/or a different ratio of amplifiers to audio outputs.
[0233] In operation, the Multi-Player Playback Device 700 is configurable to implement from one to eight “logical” players. Each logical player (sometimes referred to herein as simply a player) can be addressed and managed within a playback system as a distinct playback entity. With respect to addressing each logical player as a distinct entity, and as described further herein, each logical entity implemented by the Multi-Player Playback Device 700 is addressable via a Unique Logical Player Identifier (ULPI). In operation, the Multi-Player Playback Device 700 includes a router component 720 (e.g., hardware, firmware, software, or any combination thereof) configured to route data (including audio data and control data) to and from individual logical players based at least in part upon ULPI data. For example, the router component 720 is configured to route packets and/or frames received at the one or more network interfaces 706 and to individual logical players based at least in part on ULPI data, including in some instances, ULPI data contained in packet and/or frame headers. Similarly, in some instances, the router component 720 is configured to route data (including audio and/or control data) between different logical players implemented by the Multi-Player Playback Device 700 based at least in part on ULPI data, including in some instances, ULPI in packet and/or frame headers. And the router component 720 is also configured to route data from a logical player implemented by the Multi-Player Playback Device 700 to the one or more network interfaces 706 based at least in part on ULPI data, including in some instances, ULPI data in packet and/or frame headers. [0234] In some embodiments, the Multi-Player Playback Device 700 is configured to operate within any of several different operating modes. In some embodiments, the Multi- Player Playback Device 700 is reconfigurable to switch between operating in one mode to operating in a different mode.
[0235] For example, in some embodiments, the Multi-Player Playback Device 700 is configurable to operate in a first mode where the Multi-Player Playback Device 700 is configured to implement eight single-channel logical players, where each logical player is configured to output single-channel audio from one of the eight audio outputs. [0236] In this first mode of operation, each of the audio outputs 712-1 through 712-8 plays the same channel of audio. In some embodiments, the single-channel audio comprises a mono audio stream. In some embodiments, the single-channel audio comprises one channel from a multi-channel audio stream. In some scenarios, each of the eight logical players can be connected to a different speaker (e.g., free-standing speakers, speakers mounted in walls or ceilings, and so on) so that each connected speaker plays the same channel of audio. In some embodiments, all eight of the logical players are configured to output the same audio stream. In other embodiments, one or more of the logical players may be configured to output different audio than one or more other logical players.
[0237] In some embodiments, the Multi-Player Playback Device 700 is configurable to operate in a second mode where the Multi-Player Playback Device 700 is configured to implement four two-channel logical players, wherein each logical player is configured to output two-channel audio from two of the eight audio outputs.
[0238] In this second mode of operation, (i) a first logical player uses amp 710-1 to drive audio outputs 712-1 and 712-2 to output two channels of audio, (ii) a second logical player uses amp 710-2 to drive audio outputs 712-3 and 712-4 to output two channels of audio, (ii) a third logical player uses amp 710-3 to drive audio outputs 712-5 and 712-6 to output two channels of audio, and (iv) a fourth logical player uses amp 710-4 to drive audio outputs 712-7 and 712-8 to output two channels of audio. The two channels of audio could be left and right channels of a stereo audio stream. Alternatively, the two channels of audio could be any two different channels of a multichannel audio stream. In some embodiments, all four of the logical players are configured to output the same audio stream. In other embodiments, one or more of the logical players may be configured to output different audio than one or more other logical players.
[0239] In some embodiments, the Multi-Player Playback Device 700 is configurable to operate in a third mode where the Multi-Player Playback Device 700 is configured to implement two four-channel logical players, wherein each logical player is configured to output four-channel audio from four of the eight audio outputs.
[0240] In this third mode of operation, (i) a first logical player uses amps 710-1 and 710-2 to drive audio outputs 712-1, 712-2, 712-3, and 712-4 to output four channels of audio, and (ii) a second logical player uses amps 710-3 and 710-4 to drive audio outputs 712-5, 712- 6, 712-7, and 712-8 to output four channels of audio. The four channels of audio could be front left, front right, rear left, and rear right channels of a surround sound audio stream. Alternatively, the four channels of audio could be any four different channels of a multichannel audio stream. In some embodiments, both of the logical players are configured to output the same audio stream. In other embodiments, one of the logical players may be configured to output different audio than the other logical player.
[0241] In some embodiments, the Multi-Player Playback Device 700 is configurable to operate in a fourth mode where the Multi-Player Playback Device 700 is configured to implement one eight-channel logical player, where the logical player is configured to output eight-channel audio from the eight audio outputs.
[0242] In this fourth mode of operation, a single logical player uses amps 710-1 through 710-4 to drive audio outputs 712-1 through 712-8 to output eight channels of audio. The eight channels of audio could be front left, front center, front right, rear left, rear center, rear right, left subwoofer, and right subwoofer channels of a surround sound audio stream. Alternatively, the eight channels of audio could be any eight different channels of a multichannel audio stream. In some embodiments, the logical player is configured to output the same channel of audio via each of the eight audio outputs.
[0243] Although four operating modes are described here for illustrative purposes, the Multi-Player Playback Device 700 in some embodiments is configurable to operate in other operating modes that include combinations of differently-configured players. For example, in some embodiments, the Multi-Player Playback Device 700 is configurable to operate in a mode that includes (i) a first logical player that uses amps 710-1, 710-2, and 710-3 to drive audio outputs 712-1, 712-2, and 712-3 to output three channels of audio, and (ii) a second logical player uses amp 710-4 to drive audio output 712-8 to output one channel of audio.
The Multi-Player Playback Device 700 can implement other combinations and configurations of amps and audio outputs to output different channels of audio content.
[0244] In some embodiments, several Multi-Player Playback Devices (e.g., several Multi-Player Playback Devices like Multi-Player Playback Device 700) can be bonded together to implement more sophisticated configurations of one or more logical players.
[0245] For example, in some embodiments, the Multi-Player Playback Device 700 is configured to selectively operate in any of a plurality of bonded modes comprising a first bonded mode and a second bonded mode.
[0246] In the first bonded mode, the Multi-Player Playback Device 700 is configured to operate in a bonded configuration with a second Multi-Player Playback Device that has eight audio outputs similar to Multi-Player Playback Device 700. In the first bonded mode, the Multi-Player Playback Device 700 and the second Multi-Player Playback Device are configured to implement a single logical player configured to output any of (i) one set of sixteen channels of audio, (ii) two sets of eight channels of audio, (iii) four sets of four channels of audio, (iv) eight sets of two channels of audio, (v) sixteen single channels of audio, or (vi) any other suitable combination (e.g., one set of eight channels, one set of six channels, and two single channels).
[0247] In the second bonded mode, the Multi-Player Playback Device 700 operates in a bonded configuration with a second Multi-Player Playback Device and a third Multi-Player Playback Device, where the second Multi-Player Playback Device and the third Multi-Player Playback Device each have eight audio outputs similar to Multi-Player Playback Device 700. In the second bonded mode, the Multi-Player Playback Device 700, the second Multi-Player Playback Device, and the third Multi-Player Playback Device are configured to implement single logical player configured to output any of (i) one set of twenty four channels of audio, (ii) two sets of twelve channels of audio, (iii) three sets of eight channels of audio, (iv) four sets of six channels of audio, (v) six sets of four channels of audio, (v) eight sets of three channels of audio, (vi) twelve sets of two channels of audio, (vii) twenty four single channels of audio, or (viii) any other suitable combination (e.g., one set of twelve channels of audio, one set of six channels of audio, one set of two channels of audio, and four single channels of audio).
[0248] In some embodiments, two or more Multi-Player Playback Devices can be configured to into a bonded configuration to implement more than one logical player. For example, the Multi-Player Playback Device 700 may be configured to operate in a first alternative bonded configuration with a second Multi-Player Playback Device that has eight audio outputs similar to Multi-Player Playback Device 700. In this first alternative bonded configuration, the Multi-Player Playback Device 700 and the second Multi-Player Playback Device are configured to implement two or more logical players configured to output any of (i) one set of sixteen channels of audio, (ii) two sets of eight channels of audio, (iii) four sets of four channels of audio, (iv) eight sets of two channels of audio, (v) sixteen single channels of audio, or (vi) any other suitable combination (e.g., one set of eight channels, one set of six channels, and two single channels).
[0249] In another alternative bonded configuration for implementing more than one logical player, the Player Playback Device 700 operates in a second bonded configuration with a second Multi-Player Playback Device and a third Multi-Player Playback Device, where the second Multi-Player Playback Device and the third Multi-Player Playback Device each have eight audio outputs similar to Multi-Player Playback Device 700. In this second alternative bonded configuration, the Multi-Player Playback Device 700, the second Multi- Player Playback Device, and the third Multi-Player Playback Device are configured to implement single logical player configured to output any of (i) one set of twenty four channels of audio, (ii) two sets of twelve channels of audio, (iii) three sets of eight channels of audio, (iv) four sets of six channels of audio, (v) six sets of four channels of audio, (v) eight sets of three channels of audio, (vi) twelve sets of two channels of audio, (vii) twenty four single channels of audio, or (viii) any other suitable combination (e.g., one set of twelve channels of audio, one set of six channels of audio, one set of two channels of audio, and four single channels of audio).
V. Example Multi-Instance Software Architectures for Multi-Player Playback Devices
[0250] Figure 8A shows a block diagram of an example multi-instance software architecture 800 for a Multi-Player Playback Device according to some embodiments. In operation, the multi -instance software architecture 800 of Figure 8 A can be implemented by any of the Multi-Player Playback Device embodiments disclosed herein, including but not limited to Multi-Player Playback Device 700 shown and described with reference to Figure 7. [0251] In the example multi-instance software architecture 800, the Multi-Player Playback Device executes a single instance of a player application/process 801 on the Multi- Player Playback Device. The player application/process 801 includes both (i) device specific code 802 that is specific to functions performed by the Multi-Player Playback Device at a device level, and (ii) logical player specific code 803.
[0252] In operation, the Multi-Player Playback Device implements the device specific code 802 to perform functions specific to the physical Multi-Player Playback Device, such as configuring physical network interfaces on the Multi-Player Playback Device, configuring the Multi-Player Playback Device to implement multiple logical players, activating light emitting diodes (LEDs) that indicate various operational statuses of the Multi-Player Playback Device, handling inputs received via a user interface of the Multi-Player Playback Device, etc.
[0253] In the example shown in Figure 8A, the Multi-Player Playback Device is configured to implement three logical players. The logical player specific code 803 includes a separate instance of the logical player specific components for each logical player implemented by the Multi-Player Playback Device. For example, in the embodiment depicted in Figure 8A, the logical player specific code 803 includes (i) three instances of logical player specific audio sourcing components 804a, 804b, and 804c and (ii) three instances of logical player specific audio playback components 806a, 806b, 806c.
[0254] The logical player specific audio sourcing components 804a, 804b, and 804c and the logical player specific audio playback components 806a, 806b, 806c include software components that are specific to functions performed by each individual logical player implemented by the Multi-Player Playback Device.
[0255] For example, one instance of the logical player specific audio sourcing components 804a includes (but is not necessarily limited to): (i) a CHSRC (Channel Source) component, (ii) a GM (Group Member) component, (iii) an AVT (Audio Video Transport) component, (iv) a VLI (Virtual Line In) component, and (v) a Transmit component. The software components in the logical player specific audio sourcing components 804a operate in concert with each other (and perhaps other components not shown) to source audio content for playback by an individual logical player that is implemented by the Multi-Player Playback Device.
[0256] Further, one instance of the logical player specific audio playback components 806a includes (but is not necessarily limited to): (i) a Receive component and a (ii) CHSNK (Channel Sink) component. The software components in the logical player specific audio playback components 806a operate in concert with each other (and perhaps other components not shown) to output audio content sourced by the corresponding logical player specific audio sourcing components 804a for an individual logical player implemented by the Multi-Player Playback Device. In operation, the audio content output from each of the logical player specific audio playback components 806a, 806b, and 806c is routed to the signal output device (SOD) 820 of the Multi-Player Playback Device for playback.
[0257] Figure 8B shows a block diagram of an example alternative multi-instance software architecture 850 for a Multi-Player Playback Device according to some embodiments. In operation, the multi -instance software architecture 850 of Figure 8B can be implemented by any of the Multi-Player Playback Device embodiments disclosed herein, including but not limited to Multi-Player Playback Device 700 shown and described with reference to Figure 7.
[0258] In the alternative multi -instance software architecture 850, the Multi-Player Playback Device executes a separate player/application process 801a, 801b, and 801c for each individual logical player implemented by the Multi-Player Playback Device.
[0259] In the example shown in Figure 8B, the Multi-Player Playback Device is configured to implement three separate logical players. Each of the separate player application/process includes both (i) device specific code 802 that is specific to functions performed by the Multi-Player Playback Device at a device level, and (ii) logical player specific code 803 that is specific to functions performed by the logical player.
[0260] For example, separate player application/process 801a includes both (i) device specific code 802a that is specific to functions performed by the Multi-Player Playback Device at a device level, and (ii) logical player specific code 803a that is specific to functions performed by the logical player. Similarly, the player application/process 801b includes both device specific code 802b (not shown) and logical player specific code 803b (not shown), and the player application/process 801c includes both device specific code 802c (not shown) and logical player specific code 803c (not shown).
[0261] In some embodiments, at least part of the device specific code 802b and 802c is disabled, or perhaps just not called during operation of the Multi-Player Playback Device.
[0262] Figure 9 shows a block diagram of an example single-instance software architecture 900 for a playback device.
[0263] The example architecture 900 depicted in Figure 9 includes (i) Audio Streaming and Rendering 910 subsystem, (ii) Advertising, Discovery, and Topology 920 subsystem, (iii) Control Plane 930 subsystem, (iv) Web Server 940 subsystem, and (v) TServer 941 (Thread Server) subsystem. Each of the subsystems has single-instance software components (sometimes alternatively known as single-instance “classes” or singleinstance “data structures” in the software arts).
[0264] The single-instance software components in the Audio Streaming and Rendering 910 subsystem include (i) Framers 911, (ii) Track Play Monitor 912, (iii) Simple Network Time Protocol (SNTP) Client 913, (iv) SNTP Server 914, (v) Channel Source (CHSRC) 915, (vi) Transmit 916, (vii) Receive 917, (viii) Channel Sink (CHSNK) 918, (ix) Audio Core 919, and (x) and Virtual Line In (VLI) 901. In operation, the single-instance software components in the Audio Streaming and Rendering 910 subsystem operate in concert with each other (and perhaps with other components not shown) to source, process, and play audio content for a playback device.
[0265] The single-instance software components in the Advertising, Discovery, and Topology 920 subsystem include (i) Topology 921, (ii) Device Advertiser 922, (iii) Device Discovery 923, (iv) mDNS (Multicast Domain Name System) 924, and (v) SSDP (Simple Service Discovery Protocol) 925. In operation, the single-instance software components in the set of Advertising, Discovery, and Topology 920 subsystem operate in concert with each other (and perhaps with other components not shown) to control how a playback device advertises its capabilities to other playback devices, how a playback device discovers capabilities of other playback devices, and the playback device’s configuration in a playback system and/or configured role in a playback group.
[0266] The single-instance software components in the Control Plane 930 subsystem include (i) Device Properties 931, (ii) Group Management 932, (iii) Universal Plug and Play (UPnP) 933, (iii) Audio Video Transport (AVTransport) 935, (iv) Rendering Control 936, and (v) control plane entity 934. In operation, the single-instance software components in the Control Plane 930 subsystem operate in concert with each other (and perhaps with other components not shown) to facilitate the exchange of configuration and control information between the playback device and (i) other playback devices in the same playback system and (ii) controller devices/sy stems configured to control the playback device.
[0267] The webserver subsystem 940 includes a single-instance software component called a thread server (TServer) 941. The TServer 941 is a software component (e.g., a data structure or class) that holds, among other data, context for certain worker threads. One function performed by the single-instance TServer 941 software component is to listen for connection requests from other network devices, e.g., UPnP requests or other requests. As the playback device receives connection requests, the listen thread executed by the TServer 941 evaluates the request, accepts the request (if appropriate), and establishes a connection based on the connection request.
[0268] Figure 10 shows a block diagram of an example multi-instance software architecture 1000 for a Multi-Player Playback Device according to some embodiments. In operation, the multi -instance software architecture 1000 of Figure 10 can be implemented by any of the Multi-Player Playback Device embodiments disclosed herein, including but not limited to Multi-Player Playback Device 700 shown and described with reference to Figure 7. Further, any of the Multi-Player Playback Device embodiments disclosed herein can implement any of the of the embodiments of the multi -instance software architecture 1000 described herein to implement any of the Multi-Player Playback Device features disclosed herein, including but not limited to any of the grouped and/or Area Zone features and functions disclosed above.
[0269] The example multi-instance software architecture 1000 in Figure 10 includes many of the same software components as the single-instance software architecture 900 of Figure 9. For example, like the single-instance software architecture 900 in Figure 9, the multi -instance software architecture 1000 of Figure 10 also includes a similar (i) Audio Streaming and Rendering 1010 subsystem, (ii) Advertising, Discovery, and Topology 1020 subsystem, and (iii) Control Plane 1030 subsystem.
[0270] However, the example multi-instance software architecture 1000 for a Multi- Player Playback Device depicted in Figure 10 is different from the single-instance system architecture 900 for a playback device depicted in Figure 9 in several ways.
[0271] For example, the multi -instance software architecture 1000 includes a new Media Player 1060 subsystem that includes several multi-instance variants of some of the single-instance software components implemented in the single-instance software architecture 900 (Figure 9). The multi -instance software architecture 1000 also includes a new multi -instance variant of the TServer 1041 software component. Referring back to the example multi-instance software architecture 800 in Figure 8A, the new multi -instance Media Player 1060 subsystem and multi-instance TServer 1041 software components are similar to the logical player specific code 803, whereas the other subsystems and their corresponding software components are akin to the device specific code 802. Further, and as described in more detail below, certain single-instance software components implemented by the Audio Streaming and Rendering 1010, Advertising, Discovery, and Topology 1020, and Control Plane 1030 subsystems are adapted to provide features and functions that enable the Multi- Player Playback Device to support multiple logical players.
[0272] With respect to logical player specific code, the multi-instance software architecture 1000 is configured in some embodiments to (i) instantiate a new multi -instance Media Player 1060 software subsystem and a new TServer 1041 software component as part of adding/implementing a new logical player, and (ii) delete an existing multi-instance Media Player 1060 software subsystem and an existing TServer 1041 software component as part of deleting/terminating a logical player. In other embodiments, the multi-instance software architecture 1000 is configured to statically allocate one or more instances of the Media Player 1060 software subsystem and TServer 1041 software components at startup based at least in part on how many logical players the multi-instance software architecture 1000 needs to implement.
[0273] In the example shown in Figure 10, the Multi-Player Playback Device is configured to implement three logical players. So, the multi -instance software architecture 1000 includes a first instance 1060a of the Media Players software component for a first logical player, a second instance 1060b of the Media Players software component for a second logical player, and a third instance 1060c of the Media Players software component for a third logical player. The multi-instance software architecture 1000 also includes a first TServer 1041a for the first logical player, a second TServer 1041b for the second logical player, and a third TServer 1041c for the third logical player. In operation, and as described earlier, a Multi-Player Playback Device can implement more or fewer than three logical players.
[0274] The multi-instance variants of the software components implemented in the multi -instance Media Player 1060 subsystem of multi-instance software architecture 1000 differ from their single-instance counterparts in single-instance software architecture 900 (Figure 9) in that the multi -instance software components that the Multi-Player Playback Device instantiates for an individual logical player are configured to control one or more functions of that individual logical player. In this respect, the multi -instance software components are sometimes referred to as “logical player specific” or “player-specific” software components.
[0275] In operation, the one or more functions implemented by a player-specific software component for that individual logical player are isolated from any other logical player implemented by the physical playback device. These player-specific software components for a particular logical player are considered isolated from other logical players because functions implemented by the player-specific software components for that particular logical player do not affect the configuration or operation of any other logical player implemented by the Multi-Player Playback Device.
[0276] For example, the multi -instance software architecture 1000 depicted in Figure 10 reflects a Multi-Player Playback Device configured to implement three logical players.
The functions performed by the multi -instance software components in the first Media Player 1060a software subsystem for the first logical player do not affect the configuration and/or operation of the second or third logical players. Similarly, functions performed by the multiinstance software components in the second Media Player 1060b software subsystem for the second logical player do not affect the configuration and/or operation of the first or third logical players.
[0277] With respect to the device specific code, some of the software components in the Audio Streaming and Rendering 1010 subsystem, the Advertising, Discovery, and Topology 1020 subsystem, and the Control Plane 1030 subsystem implement device-specific single-instance software components for the Multi-Player Playback Device.
[0278] In contrast to the player-specific software components implemented in the multi -instance Media Player 1060 and TServer 1041 software components, the devicespecific single-instance software components implemented in subsystems 1010, 1020, and 1030 are configured to control one or more functions of the physical Multi-Player Playback Device at the device level. However, unlike the similarly-named single-instance counterparts in the single-instance software architecture 900, the device-specific single-instance software components implemented in the multi -instance software architecture 1000 implement certain features and functions adapted to facilitate certain aspects of the player-specific software components as described further below.
[0279] The software components in the Audio Streaming and Rendering 1010 subsystem include (i) Framers 1011, (ii) SNTP Server 1014, (iii) Audio Core 1019, and (iv) and Virtual Line In (VLI) 1001. In operation, the software components in the Audio Streaming and Rendering 1010 subsystem operate in concert with each other (and perhaps with other components not shown) to obtain audio content for the logical players implemented by the Multi-Player Playback Device. In practice, the Framers 1011, SNTP Server 1014, Audio Core 1019, and VLI 1001 in the multi -instance software architecture 1000 perform similar functions as the Framers 911, SNTP Server 914, Audio Core 919, and VLI 901 of the single-instance software architecture 900 (Figure 9).
[0280] The software components in the Advertising, Discovery, and Topology 1020 subsystem include (i) Topology 1021, (ii) Device Advertiser 1022, (iii) Device Discovery 1023, (iv) mDNS (Multicast Domain Name System) 1024, and (v) SSDP (Simple Service Discovery Protocol) 1025.
[0281] In operation, the software components in the set of Advertising, Discovery, and Topology 1020 subsystem operate in concert with each other (and perhaps with other components not shown) to control, among other features, (i) how the Multi-Player Playback Device advertises its capabilities to other devices in a network (e.g., playback devices, other Multi-Player Playback Devices, logical players, controller devices, and other network devices), and (ii) how other network devices in the network discover capabilities of the Multi-Player Playback Device, including the Multi-Player Playback Device’s configuration in a playback system (including the configurations of its logical players) and/or configured role in a playback group (including the configured roles of its logical players).
[0282] As mentioned earlier, the device-specific single-instance software components executed in the multi -instance software architecture 1000 implement certain features and functions adapted to facilitate certain aspects of the player-specific software components. In addition to device-specific advertising, discovery, and topology functions performed for the Multi-Player Playback Device at the device level, the Multi-Player Playback Device also handles player-specific advertising, discovery, and topology functions for each of its logical players on a logical player level.
[0283] For example, in some embodiments, the Multi-Player Playback Device executes software components in the Advertising, Discovery, and Topology 1020 subsystems in connection with advertising the Unique Logical Player Identifier (ULPI) (described further below) for each logical player implemented by the Multi-Player Playback Device. In some instances, the Multi-Player Playback Device advertises the ULPI for each logical player via one or more (i) Simple Service Discovery Protocol (SSDP) messages or (ii) multicast Domain Name System (mDNS) messages.
[0284] In operation, advertising each logical player’s ULPI to the playback network via SSDP and/or mDNS messages enables other playback entities (i.e., playback devices, other Multi-Player Playback Devices, and/or other logical players) to update their topology information to include the logical player (and its corresponding ULPI). When the other playback entities in the playback system include the logical players implemented by the Multi-Player Playback Device and their corresponding ULPIs in their topology tables, then the other playback entities can transmit packets to and/or receive packets from the logical players implemented by the Multi-Player Playback Device.
[0285] Additionally, in some embodiments, the Multi-Player Playback Device executes software components in the Advertising, Discovery, and Topology 1020 subsystems in connection with managing topology information for each logical player implemented by the Multi-Player Playback Device. Managing the topology information for a logical player includes, for example, requesting, receiving, storing, updating, and deleting topology information from other playback entities in the same playback system as the logical player, including but not limited to any one or more (or all) of the UUIDs of the other playback devices and Multi-Player Playback Devices, ULPIs of other logical players, IP addresses, Bluetooth address(es), MAC addresses, routing tables, and other networking and network topology data used by the logical players to exchange data with other playback entities and perhaps other network devices.
[0286] For example, in some embodiments, the topology information that the Multi- Player Playback Device manages for each logical player includes (but is not limited), for example, one or more (or all) of (i) networking and topology information for the Multi- Player Playback Device that implements the logical player, e.g., (ii) networking and topology information for the other logical players implemented by the Multi-Player Playback Device, (iii) networking and topology information for other physical playback devices configured to operate in a playback system with the Multi-Player Playback Device, (iv) networking and topology information for other logical players implemented by other Multi-Player Playback Devices configured to operate in the playback system with the Multi-Player Playback Device, and (v) networking and/or topology information for one or more controller devices configured to control playback entities in the playback system.
[0287] The software components in the Control Plane 1030 subsystem include (i) Device Properties 1031, (ii) Universal Plug and Play (UPnP) 1033, and (iii) a control plane entity 1034. In operation, the software components in the Control Plane 1030 subsystem operate in concert with each other (and perhaps with other components not shown) to facilitate the exchange of configuration and control information between the Multi-Player Playback Device and (i) other devices in the same playback system (e.g., playback devices, other Multi-Player Playback Devices, other logical players) and (ii) controller devices/sy stems configured to control the Multi-Player Playback Device.
[0288] In addition to subsystems 1010, 1020, and 1030, the multi-instance software architecture 1000 also includes Media Player 1060 subsystem. Media Player 1060 subsystem includes multi-instance versions of certain software components that were implemented by the Audio Streaming and Rendering 910 subsystem (Figure 9) and Control Plane 930 subsystem (Figure 9).
[0289] For example, the multi -instance versions of the software components in the Media Players subsystem of the multi-instance software architecture 1000 include (i) Track Play Monitor (TPM) 1012, (ii) Simple Network Time Protocol (SNTP) Client 1013, (iii) Channel Source (CHSRC) 1015, (iv) Transmit 1016, (v) Receive 1017, (vi) Channel Sink (CHSNK) 1018, (vii) Group Rendering Control 1037, (viii) Group Management 1032, (ix) AudioVideo Transport (AVTransport) 1035, and (x) Rendering Control 1036. Figure 10 shows certain multi -instance software components for illustration purpose. However, some embodiments may include additional multi-instance software components not depicted in Figure 10. Further, in some embodiments, one or more of the software components shown in the Audio Streaming and Rendering 1010 subsystem, Advertising, Discovery, and Topology 1020 subsystem, and Control Plane 1030 may be implemented as multi-instance versions in the Media Player 1060 system.
[0290] In operation, these software components in the Media Player 1060 subsystem operate in concert with each other (and perhaps with other components not shown) to source, process, and control playback of audio content for an individual logical player. [0291] For example, one player-specific feature implemented by the software component s) of the Media Player 1060 subsystem includes logical player volume control. Accordingly, some embodiments include a player-specific volume control software component that is configured to control a playback volume of an individual logical player. [0292] In operation, volume adjustments for an individual logical player implemented via a player-specific volume control software component for that individual logical player do not affect the playback volume level of any other logical player implemented by the Multi- Player Playback Device. For example, for a Multi-Player Playback Device implementing three logical players, (i) the Media Player 1060a subsystem instantiated by the Multi-Player Playback Device for the first logical player includes a volume control software component for controlling the volume level of the first logical player, (ii) the Media Player 1060b subsystem instantiated by the Multi-Player Playback Device for the second logical player includes a volume control software component for controlling the volume level of the second logical player, and (iii) the Media Player 1060c subsystem instantiated by the Multi-Player Playback Device for the third logical player includes a volume control software component for controlling the volume level of the third logical player. In operation, changes to the volume of the first logical player implemented via the player-specific volume control software component for the first logical player do not affect the volume levels of the second logical player or the third logical player. Similarly, changes to the volume of the second logical player implemented via the player-specific volume control software component for the second logical player do not affect the volume levels of the first logical player or the third logical player. And changes to the volume of the third logical player implemented via the player-specific volume control software component for the third logical player do not affect the volume levels of the first logical player or the second logical player.
[0293] Another player-specific feature implemented by the software component(s) of the Media Player 1060 subsystem includes logical player media transport, including but not limited to, the AudioVideo Transport (AVTransport) 1035 software component.
Accordingly, some embodiments include a player-specific media transport software component (or perhaps multiple media transport software components) that is configured to control media transport for a logical player, such as play, stop, pause, skip, fast-forward, rewind, and so on.
[0294] In operation, media transport control for an individual logical player implemented via a player-specific media transport software component for that individual logical player does not affect the media transport of any other logical player implemented by the Multi-Player Playback Device. For example, for a Multi-Player Playback Device implementing three logical players, (i) the Media Player 1060a subsystem instantiated by the Multi-Player Playback Device for the first logical player includes a media transport software component for controlling the media transport of the first logical player, (ii) the Media Player 1060b subsystem instantiated by the Multi-Player Playback Device for the second logical player includes a media transport software component for controlling the media transport of the second logical player, and (iii) the Media Player 1060c subsystem instantiated by the Multi-Player Playback Device for the third logical player includes a media transport software component for controlling the media transport of the third logical player. In operation, starting/ stopping playback of media content, skipping playback of media content, and/or other media transport controls implemented via the player-specific media transport software component for the first logical player does not affect media playback by the second logical player or the third logical player. Similarly, starting/stopping playback of media content, skipping playback of media content, or other media transport controls implemented via the player-specific media transport software component for the second logical player does not affect media playback by the first logical player or the third logical player. And starting/stopping playback of media content, skipping playback of media content, or other media transport controls implemented via the player-specific media transport software component for the third logical player do not affect media playback by the first logical player or the second logical player.
[0295] Another player-specific feature implemented by the software component(s) of the Media Player 1060 subsystem includes logical player media rendering, such as the Rendering Control 1036 software component. Accordingly, some embodiments include a player-specific media rendering software component that is configured to control media rendering for a logical player, such as how that logical player renders media content.
[0296] In operation, media rendering control for an individual logical player implemented via a player-specific media rendering software component for that individual logical player does not affect how any other logical player implemented by the Multi-Player Playback Device renders media content. For example, for a Multi-Player Playback Device implementing three logical players, (i) the Media Player 1060a subsystem instantiated by the Multi-Player Playback Device for the first logical player includes a media rendering software component for controlling media rendering by the first logical player, (ii) the Media Player 1060b subsystem instantiated by the Multi-Player Playback Device for the second logical player includes a media rendering software component for controlling media rendering by the second logical player, and (iii) the Media Player 1060c subsystem instantiated by the Multi- Player Playback Device for the third logical player includes a media rendering software component for controlling media rendering by the third logical player. In operation, media rendering features such as time delays (e.g., for surround sound or for steering sound to a particular listening location), dialog enhancement (e.g., to make spoken word content in a movie soundtrack more intelligible), equalization levels, or other media rendering features applied to media content rendered by the first logical player do not affect time delays, dialog enhancements, equalization levels, or other media rendering features applied to media content rendered by the second logical player or the third logical player. Similarly, media rendering features applied to media content rendered by the second logical player do not affect media rendering features applied to media content rendered by the first logical player or the third logical player. And media rendering features applied to media content rendered by the third logical player do not affect media rendering features applied to media content rendered by the first logical player or the second logical player.
[0297] In addition to the player-specific software components implemented by the Media Player 1060 subsystem, the webserver subsystem 1040 also implements a playerspecific variant of the Thread Server (TServer) 1041. The TServer 1041 is a software component (e.g., a data structure or class) that holds, among other data, context for certain worker threads. One function performed by the TServer 1041 software component is to listen for messages (e.g., UPnP messaging) from other network devices. As the Multi-Player Playback Device receives messages, the listener thread executed by the TServer 1041 evaluates the messages, processes the messages (if appropriate), and (if applicable) establishes connections for individual logical players based on the messages and/or performs other functions in response to the received messages.
[0298] More particularly, in some embodiments, the set of player-specific software components that a Multi-Player Playback Device implements for an individual logical player includes a player-specific thread server component for each logical player. In the example depicted in Figure 10, the Multi-Player Playback Device is configured to implement three logical players, and thus, the Multi-Player Playback Device implements a separate TServer software component for each logical player, i.e., a first TServer 1041a for the first logical player, a second TServer 1041b for the second logical player, and a third TServer 1041c for the third logical player.
[0299] In operation, each TServer software component is configured to store context for use by worker threads executing tasks for its corresponding logical player. For example, TServer 1041a is configured to store context for use by worker threads executing tasks for the first logical player, TServer 1041b is configured to store context for use by worker threads executing tasks for the second logical player, and TServer 1041c is configured to store context for use by worker threads executing tasks for the third logical player. Context stored by the TServer component for an individual logical player can include, for example, the ULPI of the logical player, one or more network ports used by the logical player, and/or any other context that is useful and/or necessary for operating the logical player.
[0300] The TServer software components for the different logical players operate independently of each other. In operation, context stored for worker threads executed by one TServer software component for one logical player is not shared with other TServer software components running for other logical players. For example, context stored in TServer 1041a for use by worker threads executing tasks for the first logical player is not shared with TServer 1041b or TServer 1041c. Similarly, context stored in TServer 1041b for use by worker threads executing tasks for the second logical player is not shared with TServer 1041a or TServer 1041c. And context stored in TServer 1041c for use by worker threads executing tasks for the third logical player is not shared with TServer 1041a or TServer 1041b.
Similarly, worker threads associated with each logical player can be dedicated to the corresponding logical players and independent from worker threads associated with any other logical player. In this way, each logical player can be associated with a dedicated set of worker threads, which could provide isolation between processes and/or optimize resource distribution/utilization by preventing one logical player from utilizing all available worker threads.
[0301] Rather than implementing a separate TServer software component for each logical player, some embodiments alternatively implement a single TServer software component that is configured to listen for messages (including UPnP messaging) on all of the ports being used by all of the logical players implemented by the Multi-Player Playback Device.
[0302] One advantage of using a single TServer instance for handling messaging for all of the logical players is that running a single TServer instance can be, in some scenarios, less computationally intensive than running several TServer instances. However, using multiple TServer instances (i.e., a separate TServer instance for each logical player) has advantages over using a single TServer instance to process all messages for all logical players at least in some scenarios. For example, with multiple TServer instances, a failure or fault in one TServer instance is less likely to affect other TServer instances. Similarly, using separate TServer instances (a separate instance for each logical player) avoids a scenario where a single logical player monopolizes all (or most) of the available worker threads, and thus, potentially disrupting one or more operational features/functions of one or more other logical players implemented by the Multi-Player Playback Device.
[0303] One challenge with implementing the above-described player-specific software components for logical players implemented by a Multi-Player Playback Device is how to address the various multi -instance software components executing processes for the different logical players implemented by a single Multi-Player Playback Device.
[0304] For example, playback devices often include a unique identifier, sometimes referred to as a UUID (Unique Identifier) or UDN (Unique Device Name). This UUID can include one or more components such as: (i) a prefix corresponding to the playback device manufacturer (e.g., “SONOS ”), (ii) the media access control (MAC) address of the playback device (e.g., “48A6B82E62E8”), and (iii) a suffix that includes the base port number that the Web Server software component listens on to process incoming packets addressed to the playback device (e.g., port 1400). So, in this example, the UUID for the playback device would be: SONOS 48A6B82E62E81400. Persons skilled in the art will understand that playback devices can implement different identification schemes, and even for playback devices that may implement the same (or a similar) identification scheme as the one described above, playback devices made by different manufacturers will have different manufacturer names, each playback device has a unique MAC address, and playback devices can be configured to listen to port numbers other than 1400 (e.g., 1443, 1843, or other ports). [0305] The Multi-Player Playback Device can be associated with a UUID as described above. However, because the Multi-Player Playback Device can implement multiple logical players, there is a need to distinguish between each of the logical players implemented by the Multi-Player Playback Device. In particular, other devices in a playback network need a way to send and receive data to and from each of the logical players implemented by the Multi-Player Playback Device.
[0306] Therefore, in some embodiments, each logical player implemented by a Multi- Player Playback Device has a Unique Logical Player Identifier (ULPI) that incorporates a corresponding unique interface identifier of a corresponding network interface of the Multi- Player Playback Device. In some embodiments, the ULPI for each logical player comprises the unique interface identifier of a network interface of the Multi-Player Playback Device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number. [0307] For embodiments where each logical player’s ULPI incorporates an instance number, the Multi-Player Playback Device can have a device-specific UUID like the UUID of a current playback device as described above, e.g., with one or more components such as (i) a prefix corresponding to the playback device manufacturer’s name, (ii) the media access control (MAC) address of the playback device, and (iii) a suffix that includes a base port number that the Web Server software component listens on. Further, each logical player implemented by the Multi-Player Playback Device can have a player-specific instance number that can be combined with the device-specific UUID of the Multi-Player Playback Device to create the ULPI for each logical player.
[0308] For example, for a Multi-Player Playback Device with a device-specific UUID implemented according to the above-described example (e.g., SONOS 48A6B82E62E81400) that implements three logical players, the Multi-Player Playback Device can generate a ULPI for each logical player by appending an “instance” number for the logical player to the end of the UUID of the Multi-Player Playback Device. In this example, the Multi-Player Playback Device could generate and assign (i) a ULPI of SONOS 48A6B82E62E81400.1 to the first logical player, (ii) a ULPI of SONOS 48A6B82E62E81400.2 to the second logical player, and (iii) a ULPI of SONOS 48A6B82E62E81400.3 to the third logical player.
[0309] For embodiments where each logical player’s ULPI incorporates a UPnP port number, the Multi-Player Playback Device can have a device-specific UUID like the UUID of a current playback device as described above, e.g., with one or more components such as (i) a prefix corresponding to the playback device manufacturer’s name, (ii) the media access control (MAC) address of the playback device, and (iii) a suffix that includes base port number that the Web Server software component listens on. And since each logical player implemented by the Multi-Player Playback Device is configured to listen on a different UPnP port, each logical player’s corresponding UPnP port can be combined with the devicespecific UUID of the Multi-Player Playback Device to create the ULPI for each logical player.
[0310] For example, for a Multi-Player Playback Device with a device-specific UUID implemented according to the above-described example (e.g., SONOS 48A6B82E62E81400) that implements three logical players, the Multi-Player Playback Device can generate a ULPI for each logical player by appending the UPnP port used by each logical player to the end of the UUID for the Multi-Player Playback Device. So if the first logical player is configured to listen on UPnP port 1400, the second logical player is configured to listen on UPnP port 1500, and the third logical player is configured to listen on UPnP port 1600, then in this
-n - example, the Multi-Player Playback Device could generate and assign (i) a ULPI of SONOS 48A6B82E62E81400 (corresponding to port 1400) to the first logical player, (ii) a ULPI of SONOS 48A6B82E62E81500 (corresponding to port 1500) to the second logical player, and (iii) a ULPI of SONOS 48A6B82E62E81600 (corresponding to port 1600) to the third logical player. Ports 1400, 1500, and 1600 are used in the example above for illustration purposes. In operation, embodiments may use any other suitable port numbers instead.
[0311] In some embodiments, the ULPI for an individual logical player additionally or alternatively includes a compound key formed from one or more components or parts. For example, the compound key can be formed from one or more (or all) of (i) a port identifier, (ii) a Secure Services Client (SSC) port, (iii) Mutual Transport Layer Security (MTLS) port, (iv) a zone identifier that identifies a playback zone in which the logical player is configured to operate, (v) a group identifier that identifies a playback group in which the logical player is configured to operate, (vi) a network listening ports, and/or (vii) internal integer indexing. In such embodiments, the ULPI for a logical player can be formed by combining some or all of the foregoing data (or portions thereof) along with any other suitable data into a string that is sufficient to uniquely identify the logical player within the playback network.
[0312] Further, in some embodiments, individual logical players are additionally or alternatively (i) addressable by a digital signal processor (DSP) via a zone identifier associated with the logical player, (ii) addressable by devices implementing a control plane process (e.g., 1034) via a Unique Logical Player Identifier (ULPI) corresponding to the logical player, (iii) addressable by devices compliant with the Universal Plug and Play (UPnP) protocol via a port associated with the logical player.
[0313] Regardless of the ULPI addressing scheme, all the packets (or frames) intended for individual logical players are received by the same one or more physical network interfaces of the Multi-Player Playback Device. So, the Multi-Player Playback Device needs a way to route packets and/or frames that contain data intended for its various logical players to the appropriate logical player. Therefore, some Multi-Player Playback Device embodiments include a device-specific routing component (e.g., router component 720 shown and described with reference to Figure 7) that is configured to handle both (i) packets/frames containing data intended for the Multi-Player Playback Device (i.e., devicespecific packets) and (ii) packets/frames containing data intended for individual logical players implemented by the Multi-Player Playback Device (i.e., player-specific packets). Data intended for individual logical players contained within player-specific packets/frames includes, for example, (i) control data for individual logical players implemented by the Multi-Player Playback Device and (ii) media content for individual logical players implemented by the Multi-Player Playback Device.
[0314] Since the device-specific routing component is configured to route packets/frames containing data intended for individual logical players, the routing component is sometimes referred to herein as a logical player data routing component. In operation, the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the Multi-Player Playback Device to one of a plurality of player-specific media transport components based at least in part on the Unique Logical Player Identifier (ULPI) associated with the player-specific packets/frames. For example, with reference to Figures 7 and 10, router component 720 (e.g., functioning as a logical player data routing component) is configured to route logical player data received via the one or more network interfaces 706 of the Multi-Player Playback Device 700 to one of a plurality of player-specific media transport components (e.g., in Media Player 1060 subsystem) based at least in part on the ULPI associated with the player-specific packets and/or frames.
[0315] In other embodiments, the logical player data routing component may be configured to route logical player data received via the one or more network interfaces of the Multi-Player Playback Device to one of the plurality of player-specific media transport components based on any other information contained within the player-specific packets that is suitable for routing the player-specific packets (or the data contained therein) to its intended logical player (or process implemented by the Multi-Player Playback Device on behalf of the logical player).
VI. Example Methods
[0316] Figure 11 shows an example method 1100 implemented by a Multi-Player Playback Device according to some embodiments. Method 1100 may be performed by any of the Multi-Player Playback Device embodiments disclosed herein, including but not limited to Multi-Player Playback Device 700 shown and described with reference to Figure 7. In operation, any of the Multi-Player Playback Device embodiments disclosed herein may be configured to implement one or more (or all) of the features and functions of method 1100 via execution of any of the multi-instance software architecture embodiments described herein, including but not limited to multi-instance software architecture 800, 850, and/or 1000 or portions thereof. [0317] Method 1100 is illustrated in different functional blocks for ease of explanation. In operation, the functions described in each block can be performed in any order and/or concurrently with each other, without limitation. Additionally, one or more (or all) of the additional/al ternative embodiments can be performed in any combination, any order, and/or concurrently with each other, without limitation.
[0318] Method 1100 includes block 1102, which comprises implementing a plurality of logical players via a physical playback device, wherein each logical player has a unique player identifier, and wherein the unique player identifier for each logical player incorporates a corresponding unique interface identifier of a corresponding network interface of the physical playback device. The physical playback device can be any of the Multi-Player Playback Device(s) disclosed herein.
[0319] Method 1100 also includes block 1104, which comprises for each logical player, executing a set of player-specific software components, wherein the set of playerspecific software components for an individual logical player is configured to control one or more functions of that individual logical player, wherein functions implemented by a playerspecific software component for that individual logical player are isolated from any other logical player implemented by the physical playback device.
[0320] In some embodiments, each unique player identifier for each logical player comprises the unique interface identifier of a network interface of the physical playback device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number.
[0321] In some embodiments, the unique player identifier for an individual logical player comprises a compound key that includes one or more (or all) of (i) a port identifier, (ii) a Secure Services Client (SSC) port, (iii) Mutual Transport Layer Security (MTLS) port, (iv) zone identifier, or (v) group identifier.
[0322] Some embodiments of method 1100 additionally include, for each logical player implemented by the physical playback device, the physical playback device advertising the unique player identifier of the logical player via on or more (i) Simple Service Discovery Protocol (SSDP) messages or (ii) multicast Domain Name System (mDNS) messages. In some instances, individual logical players are addressable by one or more (or all) of (i) a digital signal processor (DSP) via a zone identifier associated with the logical player, (ii) devices and processes implementing a control plane process via a Unique Logical Player Identifier (LUPI) corresponding to the logical player, and (iii) Universal Plug and Play (UPnP) compliant devices via a port number associated with the logical player. [0323] In some embodiments, the player-specific software components of block 1104 comprises a volume control component, wherein the volume control component is configured to control a playback volume of the individual logical player, and wherein volume adjustments of the individual logical player implemented via the volume control component for the individual logical player do not affect a playback volume level of any other logical player implemented by the physical playback device.
[0324] In some embodiments, the player-specific software components of block 1104 additionally or alternatively comprises a thread server component, wherein the thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player, and wherein context stored for use by worker threads executing tasks for the individual logical player is not shared with thread server components executing tasks for any other logical player implemented by the physical playback device
[0325] In some embodiments, the player-specific software components of block 1104 additionally or alternatively comprises a media transport component, wherein the media transport component for an individual logical player is configured to execute media transport commands addressed to the unique player identifier of the individual logical player, and wherein media transport commands executed by the media transport component for the individual logical player do not affect media transport activity of any other logical player implemented by the physical playback device.
[0326] In some embodiments, the player-specific software components of block 1104 additionally or alternatively comprises a media rendering component, wherein the media rendering component for an individual logical player is configured to render media content addressed to the unique player identifier of the individual logical player, and wherein the media content rendered by the media rendering component for the individual logical player is isolated from media content rendering of any other logical player implemented by the physical playback device.
[0327] Method 1100 further includes block 1106, which comprises executing a set of device-specific software components, wherein each device-specific software component is configured to control one or more functions of the physical playback device.
[0328] In some embodiments, the device-specific software components of block 1106 comprises a logical player data routing component, wherein the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the physical playback device to one of a plurality of player-specific media transport components based at least in part on a unique player identifier associated with the logical player data. In some examples, the logical player data comprises one or more of (i) control data for individual logical players implemented by the physical playback device and (ii) media content for individual logical players implemented by the physical playback device.
[0329] In some embodiments, the device-specific software components of block 1106 additionally or alternatively comprises a topology component accessible by logical players implemented by the physical playback device, wherein the topology component is configured to store network topology information relating to (i) the physical playback device, (ii) the logical players implemented by the physical playback device, (iii) other physical playback devices configured to operate in a playback system with the physical playback device, and (iv) other logical players implemented by the other physical playback devices configured to operate in the playback system with the physical playback device.
VII. Example Embodiments
[0330] The following section summarizes several examples. The examples (and features thereof) summarized in this section are for illustration purposes. The invention(s) disclosed and described herein are not limited to the examples summarized in this section or to any other example disclosed elsewhere herein. Any of the examples disclosed in this section, and any features of any of the examples, may be used together with each other in any combination, so long as the example (or feature(s) thereof) are not mutually exclusive. Further, any example (or feature(s) thereof) disclosed in any other section of this disclosure may be combined with any other example (or feature(s) thereof) disclosed in this section and/or any other section, in any combination, so long as the example (or feature(s) thereof) are not mutually exclusive.
[0331] Example 1: A physical playback device comprising: (i) one or more network interfaces, wherein each network interface has a unique interface identifier; (ii) one or more processors; and (iii) tangible, non-transitory computer-readable media having program instructions stored therein. In some embodiments, the program instructions, when executed by the one or more processors, cause the physical playback device to perform functions comprising: (A) implementing a plurality of logical players via the physical playback device, wherein each logical player has a unique player identifier, and wherein the unique player identifier for each logical player incorporates a corresponding unique interface identifier of a corresponding network interface of the physical playback device; (B) for each logical player, executing a set of player-specific software components, wherein the set of player-specific software components for an individual logical player is configured to control one or more functions of that individual logical player, wherein functions implemented by a player-specific software component for that individual logical player are isolated from any other logical player implemented by the physical playback device; and (C) executing a set of device-specific software components, wherein each device-specific software component is configured to control one or more functions of the physical playback device.
[0332] Example 2: The physical playback device of Example 1, wherein each unique player identifier for each logical player comprises the unique interface identifier of a network interface of the physical playback device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number.
[0333] Example 3: The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a volume control component, wherein the volume control component is configured to control a playback volume of the individual logical player, and wherein volume adjustments of the individual logical player implemented via the volume control component for the individual logical player do not affect a playback volume level of any other logical player implemented by the physical playback device.
[0334] Example 4: The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a thread server component, wherein the thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player, and wherein context stored for use by worker threads executing tasks for the individual logical player is not shared with thread server components executing tasks for any other logical player implemented by the physical playback device.
[0335] Example 5: The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a media transport component, wherein the media transport component for an individual logical player is configured to execute media transport commands addressed to the unique player identifier of the individual logical player, and wherein media transport commands executed by the media transport component for the individual logical player do not affect media transport activity of any other logical player implemented by the physical playback device.
[0336] Example 6: The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a media rendering component, wherein the media rendering component for an individual logical player is configured to render media content addressed to the unique player identifier of the individual logical player, and wherein the media content rendered by the media rendering component for the individual logical player is isolated from media content rendering of any other logical player implemented by the physical playback device.
[0337] Example 7: The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the set of device-specific software components comprises a logical player data routing component, wherein the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the physical playback device to one of a plurality of playerspecific media transport components based at least in part on a unique player identifier associated with the logical player data.
[0338] Example 8: The physical playback device of Example 7 (individually or in combination with any other suitable preceding Example), wherein the logical player data comprises one or more of (i) control data for individual logical players implemented by the physical playback device and (ii) media content for individual logical players implemented by the physical playback device.
[0339] Example 9: The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the tangible, non-transitory computer-readable media further has program instructions stored therein, wherein the program instructions, when executed by the one or more processors, cause the physical playback device to perform functions comprising for each logical player, advertising the unique player identifier of the logical player via on or more (i) Simple Service Discovery Protocol (SSDP) messages or (ii) multicast Domain Name System (mDNS) messages.
[0340] Example 10: The physical playback device of Example 7 (individually or in combination with any other suitable preceding Example), wherein the set of device-specific software components comprises a topology component accessible by logical players implemented by the physical playback device, wherein the topology component is configured to store network topology information relating to (i) the physical playback device, (ii) the logical players implemented by the physical playback device, (iii) other physical playback devices configured to operate in a playback system with the physical playback device, and (iv) other logical players implemented by the other physical playback devices configured to operate in the playback system with the physical playback device.
[0341] Example 11: The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein the unique player identifier for an individual logical player comprises a compound key, wherein the compound key comprises one or more of (i) a port identifier, (ii) a Secure Services Client (SSC) port, (iii) Mutual Transport Layer Security (MTLS) port, (iv) zone identifier, or (v) group identifier. [0342] Example 12: The physical playback device of Example 1 (individually or in combination with any other suitable preceding Example), wherein an individual logical player is (i) addressable by digital signal processors (DSP) via a zone identifier associated with the logical player, (ii) addressable by control plane entities via a Unique Logical Player Identifier (LUPI) corresponding to the logical player, (iii) addressable by network devices compliant with a Universal Plug and Play (UPnP) protocol via a port associated with the logical player.
[0343] Example 13: Tangible, non-transitory computer-readable media comprising program instructions, wherein the program instructions, when executed by one or more processors, cause a physical playback device to perform functions comprising: (A) implementing a plurality of logical players via the physical playback device, wherein each logical player has a unique player identifier, and wherein the unique player identifier for each logical player incorporates a corresponding unique interface identifier of a corresponding network interface of the physical playback device; (B) for each logical player, executing a set of player-specific software components, wherein the set of player-specific software components for an individual logical player is configured to control one or more functions of that individual logical player, wherein functions implemented by a player-specific software component for that individual logical player are isolated from any other logical player implemented by the physical playback device; and (C) executing a set of device-specific software components, wherein each device-specific software component is configured to control one or more functions of the physical playback device.
[0344] Example 14: The tangible, non-transitory computer-readable media of Example 13, wherein each unique player identifier for each logical player comprises the unique interface identifier of a network interface of the physical playback device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number. [0345] Example 15: The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a volume control component, wherein the volume control component is configured to control a playback volume of the individual logical player, and wherein volume adjustments of the individual logical player implemented via the volume control component for the individual logical player do not affect a playback volume level of any other logical player implemented by the physical playback device.
[0346] Example 16: The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a thread server component, wherein the thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player, and wherein context stored for use by worker threads executing tasks for the individual logical player is not shared with thread server components executing tasks for any other logical player implemented by the physical playback device.
[0347] Example 17: The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a media transport component, wherein the media transport component for an individual logical player is configured to execute media transport commands addressed to the unique player identifier of the individual logical player, and wherein media transport commands executed by the media transport component for the individual logical player do not affect media transport activity of any other logical player implemented by the physical playback device.
[0348] Example 18: The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of player-specific software components for an individual logical player comprises a media rendering component, wherein the media rendering component for an individual logical player is configured to render media content addressed to the unique player identifier of the individual logical player, and wherein the media content rendered by the media rendering component for the individual logical player is isolated from media content rendering of any other logical player implemented by the physical playback device. [0349] Example 19: The tangible, non-transitory computer-readable media of Example 13 (individually or in combination with any other suitable preceding Example), wherein the set of device-specific software components comprises a logical player data routing component, wherein the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the physical playback device to one of a plurality of player-specific media transport components based at least in part on a unique player identifier associated with the logical player data.
[0350] Example 20: A method comprising: (A) implementing a plurality of logical players via a physical playback device, wherein each logical player has a unique player identifier, and wherein the unique player identifier for each logical player incorporates a corresponding unique interface identifier of a corresponding network interface of the physical playback device; (B) for each logical player, executing a set of player-specific software components, wherein the set of player-specific software components for an individual logical player is configured to control one or more functions of that individual logical player, wherein functions implemented by a player-specific software component for that individual logical player are isolated from any other logical player implemented by the physical playback device; and (C) executing a set of device-specific software components, wherein each device-specific software component is configured to control one or more functions of the physical playback device.
VIII. Conclusions
[0351] The above discussions relating to playback devices, controller devices, playback zone configurations, and media/audio content sources provide only some examples of operating environments within which functions and methods described below may be implemented. Other operating environments and configurations of media playback systems, playback devices, and network devices not explicitly described herein may also be applicable and suitable for implementation of the functions and methods.
[0352] The description above discloses, among other things, various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. It is understood that such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the firmware, hardware, and/or software aspects or components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, the examples provided are not the only ways) to implement such systems, methods, apparatus, and/or articles of manufacture.
[0353] 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 an 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 example configurations mutually exclusive of other example configurations. As such, the example configurations described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other example configurations.
[0354] 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 example configurations 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 example configurations. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the foregoing description of example configurations.
[0355] When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.

Claims

CLAIMS What is claimed is:
1. A method comprising: implementing a plurality of logical players via a physical playback device, wherein each logical player has a unique player identifier, and wherein the unique player identifier for each logical player incorporates a corresponding unique interface identifier of a corresponding network interface of the physical playback device; for each logical player, executing a set of player-specific software components, wherein the set of player-specific software components for an individual logical player is configured to control one or more functions of that individual logical player, wherein functions implemented by a player-specific software component for that individual logical player are isolated from any other logical player implemented by the physical playback device; and executing a set of device-specific software components, wherein each device-specific software component is configured to control one or more functions of the physical playback device.
2. The method of claim 1, wherein each unique player identifier for each logical player comprises the unique interface identifier of a network interface of the physical playback device and at least one of (i) an instance number or (ii) a Universal Plug and Play (UPnP) port number.
3. The method of any preceding claim, wherein the set of player-specific software components for an individual logical player comprises a volume control component, wherein the volume control component is configured to control a playback volume of the individual logical player, and wherein volume adjustments of the individual logical player implemented via the volume control component for the individual logical player do not affect a playback volume level of any other logical player implemented by the physical playback device.
4. The method of any preceding claim, wherein the set of player-specific software components for an individual logical player comprises a thread server component, wherein the thread server component for an individual logical player is configured to store context for use by worker threads executing tasks for the individual logical player, and wherein context stored for use by worker threads executing tasks for the individual logical player is not shared with thread server components executing tasks for any other logical player implemented by the physical playback device.
5. The method of any preceding claim, wherein the set of player-specific software components for an individual logical player comprises a media transport component, wherein the media transport component for an individual logical player is configured to execute media transport commands addressed to the unique player identifier of the individual logical player, and wherein media transport commands executed by the media transport component for the individual logical player do not affect media transport activity of any other logical player implemented by the physical playback device.
6. The method of any preceding claim, wherein the set of player-specific software components for an individual logical player comprises a media rendering component, wherein the media rendering component for an individual logical player is configured to render media content addressed to the unique player identifier of the individual logical player, and wherein the media content rendered by the media rendering component for the individual logical player is isolated from media content rendering of any other logical player implemented by the physical playback device.
7. The method of any preceding claim, wherein the set of device-specific software components comprises a logical player data routing component, wherein the logical player data routing component is configured to route logical player data received via the one or more network interfaces of the physical playback device to one of a plurality of playerspecific media transport components based at least in part on a unique player identifier associated with the logical player data.
8. The method of claim 7, wherein the logical player data comprises one or more of (i) control data for individual logical players implemented by the physical playback device and (ii) media content for individual logical players implemented by the physical playback device.
9. The method of any preceding claim, further comprising: for each logical player, advertising the unique player identifier of the logical player via on or more (i) Simple Service Discovery Protocol (SSDP) messages or (ii) multicast Domain Name System (mDNS) messages.
10. The method of any preceding claim, wherein the set of device-specific software components comprises a topology component accessible by logical players implemented by the physical playback device, wherein the topology component is configured to store network topology information relating to (i) the physical playback device, (ii) the logical players implemented by the physical playback device, (iii) other physical playback devices configured to operate in a playback system with the physical playback device, and (iv) other logical players implemented by the other physical playback devices configured to operate in the playback system with the physical playback device.
11. The method of any preceding claim, wherein the unique player identifier for an individual logical player comprises a compound key, wherein the compound key comprises one or more of (i) a port identifier, (ii) a Secure Services Client (SSC) port, (iii) Mutual Transport Layer Security (MTLS) port, (iv) zone identifier, or (v) group identifier.
12. The method of any preceding claim, wherein an individual logical player is (i) addressable by digital signal processors (DSP) via a zone identifier associated with the logical player, (ii) addressable by control plane entities via a Unique Logical Player Identifier (LUPI) corresponding to the logical player, (iii) addressable by network devices compliant with a Universal Plug and Play (UPnP) protocol via a port associated with the logical player.
13. Tangible, non-transitory computer-readable media comprising program instructions, wherein the program instructions, when executed by one or more processors, cause a physical playback device to perform the method of any of claims 1 through 12.
14. A physical playback device comprising: one or more network interfaces, wherein each network interface has a unique interface identifier; one or more processors; and tangible, non-transitory computer-readable media having program instructions stored therein, wherein the program instructions, when executed by the one or more processors, cause the physical playback device to perform the method of any of claims 1 through 12.
PCT/US2025/022134 2024-03-28 2025-03-28 Multi-instance architecture for multi-player playback device Pending WO2025208089A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463571312P 2024-03-28 2024-03-28
US63/571,312 2024-03-28

Publications (1)

Publication Number Publication Date
WO2025208089A1 true WO2025208089A1 (en) 2025-10-02

Family

ID=95559103

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/022134 Pending WO2025208089A1 (en) 2024-03-28 2025-03-28 Multi-instance architecture for multi-player playback device

Country Status (1)

Country Link
WO (1) WO2025208089A1 (en)

Citations (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7571014B1 (en) 2004-04-01 2009-08-04 Sonos, Inc. Method and apparatus for controlling multimedia players in a multi-zone system
US8234395B2 (en) 2003-07-28 2012-07-31 Sonos, Inc. System and method for synchronizing operations among a plurality of independently clocked digital data processing devices
US8483853B1 (en) 2006-09-12 2013-07-09 Sonos, Inc. Controlling and manipulating groupings in a multi-zone media system
US8788080B1 (en) 2006-09-12 2014-07-22 Sonos, Inc. Multi-channel pairing in a media system
US8903526B2 (en) 2012-06-06 2014-12-02 Sonos, Inc. Device playback failure recovery and redistribution
US9202509B2 (en) 2006-09-12 2015-12-01 Sonos, Inc. Controlling and grouping in a multi-zone media system
US9288596B2 (en) 2013-09-30 2016-03-15 Sonos, Inc. Coordinator device for paired or consolidated players
US9438193B2 (en) 2013-06-05 2016-09-06 Sonos, Inc. Satellite volume control
US9516440B2 (en) 2012-10-01 2016-12-06 Sonos Providing a multi-channel and a multi-zone audio environment
US9654545B2 (en) 2013-09-30 2017-05-16 Sonos, Inc. Group coordinator device selection
US9794710B1 (en) 2016-07-15 2017-10-17 Sonos, Inc. Spatial audio correction
US9864571B2 (en) 2015-06-04 2018-01-09 Sonos, Inc. Dynamic bonding of playback devices
US9898245B1 (en) 2016-01-15 2018-02-20 Sonos, Inc. System limits based on known triggers
US10028069B1 (en) 2017-06-22 2018-07-17 Sonos, Inc. Immersive audio in a media playback system
US10299061B1 (en) 2018-08-28 2019-05-21 Sonos, Inc. Playback device calibration
US10303422B1 (en) 2016-01-05 2019-05-28 Sonos, Inc. Multiple-device setup
US10452345B1 (en) 2018-05-15 2019-10-22 Sonos, Inc. Media playback system with virtual line-in
US11178504B2 (en) 2019-05-17 2021-11-16 Sonos, Inc. Wireless multi-channel headphone systems and methods
WO2023056336A1 (en) 2021-09-30 2023-04-06 Sonos, Inc. Audio parameter adjustment based on playback device separation distance
US11720319B2 (en) * 2014-01-15 2023-08-08 Sonos, Inc. Playback queue with software components

Patent Citations (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8234395B2 (en) 2003-07-28 2012-07-31 Sonos, Inc. System and method for synchronizing operations among a plurality of independently clocked digital data processing devices
US7571014B1 (en) 2004-04-01 2009-08-04 Sonos, Inc. Method and apparatus for controlling multimedia players in a multi-zone system
US8483853B1 (en) 2006-09-12 2013-07-09 Sonos, Inc. Controlling and manipulating groupings in a multi-zone media system
US8788080B1 (en) 2006-09-12 2014-07-22 Sonos, Inc. Multi-channel pairing in a media system
US9202509B2 (en) 2006-09-12 2015-12-01 Sonos, Inc. Controlling and grouping in a multi-zone media system
US8903526B2 (en) 2012-06-06 2014-12-02 Sonos, Inc. Device playback failure recovery and redistribution
US9516440B2 (en) 2012-10-01 2016-12-06 Sonos Providing a multi-channel and a multi-zone audio environment
US9438193B2 (en) 2013-06-05 2016-09-06 Sonos, Inc. Satellite volume control
US9288596B2 (en) 2013-09-30 2016-03-15 Sonos, Inc. Coordinator device for paired or consolidated players
US9654545B2 (en) 2013-09-30 2017-05-16 Sonos, Inc. Group coordinator device selection
US11720319B2 (en) * 2014-01-15 2023-08-08 Sonos, Inc. Playback queue with software components
US9864571B2 (en) 2015-06-04 2018-01-09 Sonos, Inc. Dynamic bonding of playback devices
US10303422B1 (en) 2016-01-05 2019-05-28 Sonos, Inc. Multiple-device setup
US9898245B1 (en) 2016-01-15 2018-02-20 Sonos, Inc. System limits based on known triggers
US9794710B1 (en) 2016-07-15 2017-10-17 Sonos, Inc. Spatial audio correction
US10028069B1 (en) 2017-06-22 2018-07-17 Sonos, Inc. Immersive audio in a media playback system
US10452345B1 (en) 2018-05-15 2019-10-22 Sonos, Inc. Media playback system with virtual line-in
US10649718B2 (en) 2018-05-15 2020-05-12 Sonos, Inc. Interoperability of native media playback system with virtual line-in
US10299061B1 (en) 2018-08-28 2019-05-21 Sonos, Inc. Playback device calibration
US11178504B2 (en) 2019-05-17 2021-11-16 Sonos, Inc. Wireless multi-channel headphone systems and methods
WO2023056336A1 (en) 2021-09-30 2023-04-06 Sonos, Inc. Audio parameter adjustment based on playback device separation distance

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Information technology - UPnP Device Architecture - Part 1-2: UPnP Device Architecture Version 2.0", 2 June 2017 (2017-06-02), pages 1 - 180, XP082099613, Retrieved from the Internet <URL:https://api.iec.ch/harmonized/publications/download/3614306> [retrieved on 20170602] *
METHOD FOR SYNCHRONIZING AUDIO PLAYBACK BETWEEN MULTIPLE NETWORKED DEVICES, 2003

Similar Documents

Publication Publication Date Title
US11178504B2 (en) Wireless multi-channel headphone systems and methods
AU2020221824A1 (en) Methods for calibrating passive speakers with a graphical user interface
EP3891597A1 (en) Systems and methods of operating media playback systems having multiple voice assistant services
CA3116544A1 (en) Distributed synchronization
EP3970390A1 (en) Wireless transmission to satellites for multichannel audio system
WO2020247811A1 (en) Automatically allocating audio portions to playback devices
US20240111485A1 (en) Multichannel Content Distribution
WO2021096943A1 (en) Playback queues for shared experiences
US12506629B2 (en) Mixed-mode synchronous playback
US20250094120A1 (en) Networking in a media playback system
WO2025208089A1 (en) Multi-instance architecture for multi-player playback device
WO2025208094A1 (en) Multi-stream audio routing for multi-player playback device
WO2025111229A1 (en) Calibrating playback entities in playback networks comprising multiple playback entities
WO2024059058A1 (en) Bluetooth line-in stereo
WO2025064375A1 (en) Wireless communication profile management
EP4385217A1 (en) Techniques for re-bonding playback devices
WO2025240889A1 (en) Pairing of audio devices via an intermediary
WO2024206437A1 (en) Content-aware multi-channel multi-device time alignment
WO2023055742A1 (en) Synchronous playback of media content by off-net portable playback devices
WO2025217383A1 (en) Connection and network setup for playback devices using selectable communication interface
EP4285600A1 (en) Synchronization via out-of-band clock timing signaling

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25721986

Country of ref document: EP

Kind code of ref document: A1