Patent Grant
11182534
The disclosure is related to consumer goods and, more particularly, to methods, systems, products, features, services, and other items directed to media playback or some aspect thereof.
Digital music has become readily available due in part to the development of consumer level technology that has allowed people to listen to digital music on a personal audio device. The consumer's increasing preference for digital audio has also resulted in the integration of personal audio devices into PDAs, cellular phones, and other mobile devices. The portability of these mobile devices has enabled people to take the music listening experience with them and outside of the home. People have become able to consume digital music, like digital music files or even Internet radio, in the home through the use of their computer or similar devices. Now there are many different ways to consume digital music, in addition to other digital content including digital video and photos, stimulated in many ways by high-speed Internet access at home, mobile broadband Internet access, and the consumer's hunger for digital media.
Until recently, options for accessing and listening to digital audio in an out-loud setting were severely limited. In 2005, Sonos offered for sale its first digital audio system that enabled people to, among many other things, access virtually unlimited sources of audio via one or more networked connected zone players, dynamically group or ungroup zone players upon command, wirelessly send the audio over a local network amongst zone players, and play the digital audio out loud across multiple zone players in synchrony. The Sonos system can be controlled by software applications running on network capable mobile devices and computers.
Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings where:
In addition, the drawings are for the purpose of illustrating example embodiments, but it is understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings.
Embodiments are described herein that may allow for the remote creation of a playback queue of a media playback system in advance of an event. The playback queue may include identification of one or more media items (e.g., songs, videos, streaming data sources, etc.) that are intended to be played on the media playback system during the event.
The playback queue may be created or modified prior to an event where the playback queue may be played by a media playback system. For example, a person may be planning a celebration (e.g., a wedding, birthday party, etc.) for some time in the future and may want to allow guests to, prior to the celebration, add music, videos, etc. to a playback queue that will be played at the celebration.
In example embodiments, the playback queue may be created or modified by one or more remote computing devices that are in communication with the media playback system via at least a wide area network (WAN). The remote computing device may receive an electronic invitation prior to the event that permits a user of the remote computing device to add one or more media items to the playback queue.
A computing system communicatively coupled to the WAN may store, facilitate the creation of, and otherwise manage the playback queue. The computing system may receive annotation data before, during, and/or after the event that is associated with a media item from the playback queue. The annotation data may be used to tag annotations, such as messages, videos, photos, or social media statuses, to the media items. The computing system may provide the playback queue along with the tags for view by the guests, which may promote a more memorable event experience.
As indicated above, the present application involves remotely creating a playback queue of a media playback system by remote computing devices in communication with the media playback system via a WAN. In one aspect, a method is provided. The method involves receiving by a computing device an electronic invitation to add at least one media item to a playback queue of a media playback system, where the electronic invitation comprises a link to access information identifying a set of media items available for playback by the media playback system, and where the computing device and the media playback system are communicatively coupled via at least a WAN. The method further involves causing by the computing device a graphical display to display the information identifying the set of media items available for playback by the media playback system. The method further involves sending by the computing device selection data that indicates a selection of a particular media item from the set of media items to be added to the playback queue of the media playback system.
In another aspect, a non-transitory computer readable medium is provided. The non-transitory computer readable having instructions stored thereon that are executable by at least one processor. The instructions include instructions for receiving by a computing device an electronic invitation to add at least one media item to a playback queue of a media playback system, where the electronic invitation comprises a link to access information identifying a set of media items available for playback by the media playback system, and where the computing device and the media playback system are communicatively coupled via at least a WAN. The instructions further include instructions for causing by the computing device a graphical display to display the information identifying the set of media items available for playback by the media playback system. The instructions further include instructions for sending by the computing device selection data that indicates a selection of a particular media item from the set of media items to be added to the playback queue of the media playback system.
In one other aspect, a computing device is provided. The computing device includes a graphical display, a network interface, a non-transitory computer readable medium, and program instructions stored on the non-transitory computer readable medium. The program instructions are executable by at least one processor to cause the computing device to receive an electronic invitation to add at least one media item to a playback queue of a media playback system, where the electronic invitation comprises a link to access information identifying a set of media items available for playback by the media playback system, and where the computing device and the media playback system are communicatively coupled via at least a WAN. The program instructions are executable by the at least one processor to further cause the computing device to cause the graphical display to display the information identifying the set of media items available for playback by the media playback system. The program instructions are executable by the at least one processor to further cause the computing device to send selection data that indicates a selection of a particular media item from the set of media items to be added to the playback queue of the media playback system.
In another aspect, a method is provided. The method involves providing, by a computing system that is communicatively coupled to a media playback system via a WAN, a plurality of electronic invitations to a plurality of respective remote computing devices to add at least one media item to a playback queue of the media playback system, where each of the plurality of electronic invitations comprises a link to access information identifying one or more media items available for playback by the media playback system. The method further involves receiving by the computing system selection data that indicates one or more media item selections associated with one or more of the plurality of electronic invitations. The method further involves populating by the computing system the playback queue based on the one or more media item selections indicated by the received selection data.
In an additional aspect, a non-transitory computer readable medium is provided. The non-transitory computer readable having instructions stored thereon that are executable by at least one processor. The instructions include instructions for providing, by a computing system that is communicatively coupled to a media playback system via a WAN, a plurality of electronic invitations to a plurality of respective remote computing devices to add at least one media item to a playback queue of the media playback system, where each of the plurality of electronic invitations comprises a link to access information identifying one or more media items available for playback by the media playback system. The instructions further include instructions for receiving by the computing system selection data that indicates one or more media item selections associated with one or more of the plurality of electronic invitations. The instructions further include instructions for populating by the computing system the playback queue based on the one or more media item selections indicated by the received selection data.
In a further aspect, a computing system is provided. The computing device includes a network interface, a non-transitory computer readable medium, and program instructions stored on the non-transitory computer readable medium. The network interface communicatively couples the computing system to a media playback system via a WAN. The program instructions are executable by at least one processor to cause the computing system to provide a plurality of electronic invitations to a plurality of respective remote computing devices to add at least one media item to a playback queue of the media playback system, where each of the plurality of electronic invitations comprises a link to access information identifying one or more media items available for playback by the media playback system. The program instructions are executable by the at least one processor to further cause the computing device to receive selection data that indicates one or more media item selections associated with one or more of the plurality of electronic invitations. The program instructions are executable by the at least one processor to further cause the computing device to populate the playback queue based on the one or more media item selections indicated by the received selection data.
Other embodiments, as those discussed in the following and others as can be appreciated by one having ordinary skill in the art are also possible.
Referring now to the drawings, in which like numerals can refer to like parts throughout the figures,
The network configuration 100 may include a media playback system 110, one or more computing devices 120, 122, and 124, a media system server 130, and a wide area network (“WAN”) 140. The network configuration 100 may additionally include a computing device 126 that is associated with the media playback system 110 such that the computing device 126 may control access to information related to the media playback system 110. It should be understood that the network configuration 100 may include a plurality of the depicted components and/or may also include various other components, such as, content-provider servers (e.g., Internet radio servers), without departing from the present invention.
The WAN 140 may communicatively couple the various components of the network configuration 100. For example, in such an arrangement, any of the computing devices 120-124 may communicate with the media system server 130 and/or the media playback system 110 via the WAN 140. Similarly, the media playback system 110 and the media system server 130 may communicate via the WAN 140. The WAN 140 may include the Internet and/or a cellular network, among other networks. In example implementations that include the computing device 126, the computing device 126 may be communicatively coupled to the media playback system 110 via a local area network (e.g., via WiFi) or a personal area network (e.g., via Bluetooth), among other possibilities.
In order to distinguish between a computing device associated with the media playback system 110 (e.g., the computing device 126) and a computing device not associated with the media playback system 110 (e.g., the computing devices 120-124), and because the computing devices 120-124 are communicatively coupled to the media playback system 110 via at least the WAN 140, hereinafter the computing devices 120-124 may be referred to as “remote computing devices.”
Generally speaking, the media playback system 110 may be any media playback system configured to receive data over a WAN and playback media items. The media playback system 110 is discussed in further detail below with reference to example media playback system 200.
In general, each computing device 120-126 may be any computing device configured to communicate over a WAN. The computing devices 120-126 may include at least one processor, memory, a graphical display, an input interface, and a network interface, among other components. In some instances, the graphical display and the input interface may be part of the same component (e.g., a touchscreen). The network interface may facilitate data flow between the computing device and another device via the WAN 140. The computing devices 120-126 may also include a camera configured to capture image data. Example computing devices include, but are not limited to, cellular phones, smartphones, PDAs, tablets, laptops, desktop computers, video game consoles, and smart TVs.
The media system server 130 may include at least one processor, memory, and a network interface, among other components. The network interface may facilitate data flow between the media system server 130 and another device on the WAN 140.
The media system server 130 may store a database in memory that contains various data that may include, for example, one or more sets of media items, one or more playback queues, and/or account information associated with a particular media playback system, among other data.
A set of media items may include one or more media items that are available for playback by a particular media playback system. Example media items may include audio files, video files, audio-visual files, and streaming data sources (e.g., Internet radio stations), among other types of media items. In some implementations, the media items may be a collection of links or pointers (i.e., URI) to the underlying data for media items that are stored elsewhere, such as on a remote source on the WAN 140. Additionally or alternatively, the media items may include pointers to media content stored on a device local to a media playback system. Further, a media item may include one or more identifiers (e.g., a media-item title, an artist name, an album title, a genre, etc.) that are associated with the media item that is available to be played on a particular media playback system. As shown in
A playback queue (or simply “queue”) may include identification of one or more media items (e.g., songs, videos, Internet broadcasts, etc.) that are intended to be played on a particular media playback system. For example, as shown in
A media playback system may be configured to play media items from the queue according to a specific order (such as an order in which the media items were added), in a random order, or in some other order. A playback queue may be created or modified by receiving selection data from one or more computing devices (e.g., any of the computing devices 120-126). Playback queues are discussed in further detail below.
Account information may include associations between one or more computing devices, one or more media playback systems, one or more playback queues, and/or one or more sets of media items, among other associations. As shown in
By way of illustration, the media playback system 200 is associated with a home having multiple zones, although it should be understood that the home could be configured with only one zone. Additionally, one or more zones can be added to the media playback system 200 over time. Each zone may be assigned by a user to a different room or space, such as, for example, an office, bathroom, bedroom, kitchen, dining room, family room, home theater room, utility or laundry room, and patio. A single zone might also include multiple rooms or spaces if so configured. With respect to
The media playback system 200 illustrates an example whole house media system, though it is understood that the technology described herein is not limited to, among other things, its particular place of application or to an expansive system like the whole house media playback system 200 of
Referring back to
By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presently offers for sale zone players referred to as a “PLAY:5,” “PLAY:3,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/or future zone players can additionally or alternatively be used to implement the zone players of example embodiments disclosed herein. Additionally, it is understood that a zone player is not limited to the particular examples illustrated in
In some embodiments, if more than one controller is used in the media playback system 200 of
In addition, an application running on any network-enabled portable device, such as an iPhonep™, iPad™, Android™ powered phone or tablet, or any other smart phone or network-enabled device can be used as the controller 230. An application running on a laptop or desktop personal computer (PC) or Mac™ can also be used as the controller 230. Such controllers may connect to the media playback system 200 through an interface with the data network 228, a zone player, a wireless router, or using some other configured connection path. Example controllers offered by Sonos, Inc. of Santa Barbara, California include a “Controller 200,” “SONOS® CONTROL,” “SONOS® Controller for iPhone™,” “SONOS® Controller for iPad™,” “SONOS Controller for Android™,” “SONOS Controller for Mac™ or PC.”
The zone players 202-224 of
In some embodiments, connecting any of the zone players 202-224, or some other connecting device, to a broadband router, may create the data network 228. Other of the zone players 202-224 may then be added wired or wirelessly to the data network 228. For example, a zone player (e.g., any of the zone players 202-224) can be added to the media playback system 200 by simply pressing a button on the zone player itself (or perform some other action), which enables a connection to be made to the data network 228. The broadband router can be connected to an Internet Service Provider (ISP), for example. The broadband router can be used to form another data network within the media playback system 200, which can be used in other applications (e.g., web surfing). The data network 228 can also be used in other applications, if so programmed. An example second network may implement SONOSNET™ protocol, developed by SONOS, Inc. of Santa Barbara. SONOSNET™ represents a secure, AES-encrypted, peer-to-peer wireless mesh network. Alternatively, in certain embodiments, the data network 228 may be the same network, such as a traditional wired or wireless network, used for other applications in the household.
A particular zone can contain one or more zone players. For example, the family room of
In some embodiments, a “bonded zone” contains two or more zone players, such as the two zone players 206 and 208 in the family room, whereby the two zone players 206 and 208 can be configured to play the same audio source in synchrony. In one example, the two zone players 206 and 208 can be paired to play two separate sounds in left and right channels, for example. In other words, the stereo effects of a sound can be reproduced or enhanced through the two zone players 206 and 208, one for the left sound and the other for the right sound. In another example two or more zone players can be sonically consolidated to form a single, consolidated zone player. A consolidated zone player (though made up of multiple, separate devices) can be configured to process and reproduce sound differently than an unconsolidated zone player or zone players that are paired, because a consolidated zone player has additional speaker drivers from which sound can be passed. The consolidated zone player can further be paired with a single zone player or yet another consolidated zone player. Each playback device of a consolidated playback device can be set in a consolidated mode, for example.
In certain embodiments, paired zone players (also referred to as “bonded zone players”) can play audio in synchrony with other zone players in the same or different zones.
According to some embodiments, one can continue to do any of: group, consolidate, and pair zone players, for example, until a desired configuration is complete. The actions of grouping, consolidation, and pairing are preferably performed through a control interface, such as using the controller 230, and not by physically connecting and re-connecting speaker wire, for example, to individual, discrete speakers to create different configurations. As such, certain embodiments described herein provide a more flexible and dynamic platform through which sound reproduction can be offered to the end-user.
In some embodiments, each zone can play from the same audio source as another zone or each zone can play from a different audio source. For example, someone can be grilling on the patio and listening to jazz music via the zone player 224, while someone is preparing food in the kitchen and listening to classical music via the zone player 202. Further, someone can be in the office listening to the same jazz music via the zone player 210 that is playing on the patio via the zone player 224. In some embodiments, the jazz music played via the zone players 210 and 224 may be played in synchrony. Synchronizing playback amongst zones allows for an individual to pass through zones while seamlessly (or substantially seamlessly) listening to the audio. Further, zones can be put into a “party mode” such that all associated zones will play audio in synchrony.
Sources of audio content that may be played by the zone players 202-224 are numerous. In some embodiments, audio on a zone player itself may be accessed and played. In some embodiments, audio on a controller may be accessed via the data network 228 and played. In some embodiments, music from a personal library stored on a computer or networked-attached storage (NAS) may be accessed via the data network 228 and played. In some embodiments, Internet radio stations, shows, and podcasts may be accessed via the data network 228 and played. Music or cloud services that let a user stream and/or download music and audio content may be accessed via the data network 228 and played. Further, music may be obtained from traditional sources, such as a turntable or CD player, via a line-in connection to a zone player, for example. Audio content may also be accessed using a different protocol, such as Airplay™ which is a wireless technology by Apple, Inc., for example. Audio content received from one or more sources can be shared amongst the zone players 202 to 224 via the data network 228 and/or the controller 230. The above-disclosed sources of audio content are referred to herein as network-based audio information sources. However, network-based audio information sources are not limited thereto.
In some embodiments, the example home theater zone players 216, 218, 220 are coupled to an audio information source such as a television 232. In some examples, the television 232 may be used as a source of audio for the home theater zone players 216, 218, 220, while in other examples audio information from the television 232 may be shared with any of the zone players 202-224 in the media playback system 200.
Referring now to
In some embodiments, the network interface 502 facilitates a data flow between the zone player 500 and other devices on the data network 228. In some embodiments, in addition to getting audio from another zone player or device on the data network 228, the zone player 500 may access audio directly from the audio source, such as over a WAN (e.g., the WAN 140) or on the local network. In some embodiments, the network interface 502 can further handle the address part of each packet so that it gets to the right destination or intercepts packets destined for the zone player 500. Accordingly, in certain embodiments, each of the packets includes an Internet Protocol (IP)-based source address as well as an IP-based destination address.
In some embodiments, the network interface 502 can include one or both of a wireless interface 504 and a wired interface 506. The wireless interface 504, also referred to as a radio frequency (RF) interface, provides network interface functions for the zone player 500 to wirelessly communicate with other devices (e.g., other zone player(s), speaker(s), receiver(s), component(s) associated with the data network 228, and so on) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The wireless interface 504 may include one or more radios. To receive wireless signals and to provide the wireless signals to the wireless interface 504 and to transmit wireless signals, the zone player 500 includes one or more antennas 520. The wired interface 506 provides network interface functions for the zone player 500 to communicate over a wire with other devices in accordance with a communication protocol (e.g., IEEE 802.3). In some embodiments, a zone player may include multiple wireless 504 interfaces. In some embodiments, a zone player may include multiple wired 506 interfaces. In some embodiments, a zone player may include both of the interfaces 504 and 506. In some embodiments, a zone player may include only the wireless interface 504 or the wired interface 506.
In some embodiments, the at least one processor 508 is a clock-driven electronic device that is configured to process input data according to instructions stored in the memory 510. The memory 510 is data storage that can be loaded with the one or more software modules 514, which can be executed by the at least one processor 508 to achieve certain tasks. In the illustrated embodiment, the memory 510 is a tangible machine-readable medium storing instructions that can be executed by the at least one processor 508. In some embodiments, a task might be for the zone player 500 to retrieve audio data from another zone player or a device on a network (e.g., using a uniform resource locator (URL) or some other identifier). In some embodiments, a task may be for the zone player 500 to send audio data to another zone player or device on a network. In some embodiments, a task may be for the zone player 500 to synchronize playback of audio with one or more additional zone players. In some embodiments, a task may be to pair the zone player 500 with one or more zone players to create a multi-channel audio environment. Additional or alternative tasks (e.g., those discussed below) can be achieved via the one or more software modules 514 and the at least one processor 508.
The audio processing component 512 can include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor, and so on. In some embodiments, the audio processing component 512 may be part of the at least one processor 508. In some embodiments, the audio that is retrieved via the network interface 502 may be processed and/or intentionally altered by the audio processing component 512. Further, the audio processing component 512 can produce analog audio signals. The processed analog audio signals may then be provided to the audio amplifier 516 for playback through the speaker unit 518. In addition, the audio processing component 512 can include circuitry to process analog or digital signals as inputs to play from the zone player 500, send to another zone player on a network, or both play and send to another zone player on the network. An example input includes a line-in connection (e.g., an auto-detecting 3.5 mm audio line-in connection).
The audio amplifier 516 is a device(s) that amplifies audio signals to a level for driving one or more speakers of the speaker unit 518. The one or more speakers 518 can include an individual transducer (e.g., a “driver”) or a complete speaker system that includes an enclosure including one or more drivers. A particular driver can be a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and a tweeter (e.g., for high frequencies), for example. An enclosure can be sealed or ported, for example. Each transducer may be driven by its own individual amplifier.
A commercial example, presently known as the PLAY:5™, is a zone player with a built-in amplifier and speakers that is capable of retrieving audio directly from the source, such as on the Internet or on the local network, for example. In particular, the PLAY:5™ is a five-amp, five-driver speaker system that includes two tweeters, two mid-range drivers, and one woofer. When playing audio content via the PLAY:5, the left audio data of a track is sent out of the left tweeter and left mid-range driver, the right audio data of a track is sent out of the right tweeter and the right mid-range driver, and mono bass is sent out of the subwoofer. Further, both mid-range drivers and both tweeters have the same equalization (or substantially the same equalization). That is, they are both sent the same frequencies but from different channels of audio. Audio from Internet radio stations, online music and video services, downloaded music, analog audio inputs, television, DVD, and so on, can be played from the PLAY:5™.
Referring now to
The controller 600 may be provided with a screen 602 and an input interface 614 that may allow a user to interact with the controller 600, for example, to navigate a playlist of media items and to control operations of one or more zone players. The screen 602 on the controller 600 can be an LCD screen, for example. The screen 600 communicates with and is commanded by a screen driver 604 that is controlled by a microcontroller (e.g., a processor) 606. The controller memory 610 can be loaded with one or more application modules 612 that can be executed by the microcontroller 606 with or without a user input via the user interface 614 to achieve certain tasks. In some embodiments, the application module 612 may be configured to facilitate grouping a number of selected zone players into a zone group to facilitate synchronized playback amongst the zone players in the zone group. In some embodiments, the application module 612 may be configured to control the audio sounds (e.g., volume) of the zone players in a zone group. In operation, when the microcontroller 606 executes one or more of the application modules 612, the screen driver 604 may generate control signals to drive the screen 602 to display an application specific user interface accordingly.
The controller 600 includes a network interface 608 that may facilitate wired or wireless communication with a zone player. In some embodiments, the commands such as volume control and audio playback synchronization may be sent via the network interface 608. In some embodiments, a saved zone group configuration may be transmitted between a zone player and a controller via the network interface 608. The controller 600 can control one or more zone players, such as the zone players 202-224 of
It should be noted that other network-enabled devices such as an iPhone™, iPad™ or any other smartphone or network-enabled device (e.g., a networked computer such as a PC or Mac™) can also be used as a controller to interact or control zone players in a particular environment. In some embodiments, a software application or upgrade can be downloaded onto a network-enabled device to perform the functions described herein.
In certain embodiments, a user can create a zone group (also referred to as a bonded zone) including at least two zone players from the controller 600. The zone players in the zone group can play audio in a synchronized fashion, such that all of the zone players in the zone group playback an identical audio source or a list of identical audio sources in a synchronized manner such that no (or substantially no) audible delays or hiccups are to be heard. Similarly, in some embodiments, when a user increases the audio volume of the group from the controller 500, the signals or data of increasing the audio volume for the group are sent to one of the zone players and causes other zone players in the group to be increased together in volume.
A user via the controller 600 can group zone players into a zone group by activating a “Link Zones” or “Add Zone” soft button, or de-grouping a zone group by activating an “Unlink Zones” or “Drop Zone” button. For example, one mechanism for ‘joining’ zone players together for audio playback is to link a number of zone players together to form a group. To link a number of zone players together, a user can manually link each zone player or room one after the other. For example, assume that there is a multi-zone system that includes the following zones: Bathroom, Bedroom, Den, Dining Room, Family Room, and Foyer. In certain embodiments, a user can link any number of the six zone players, for example, by starting with a single zone and then manually linking each zone to that zone.
In certain embodiments, a set of zones can be dynamically linked together using a command to create a zone scene or theme (subsequent to first creating the zone scene). For instance, a “Morning” zone scene command can link the Bedroom, Office, and Kitchen zones together in one action. Without this single command, the user would manually and individually link each zone. The single command may include a mouse click, a double mouse click, a button press, a gesture, or some other programmed or learned action. Other kinds of zone scenes can be programmed or learned by the system over time.
In certain embodiments, a zone scene can be triggered based on time (e.g., an alarm clock function). For instance, a zone scene can be set to apply at 8:00 am. The system can link appropriate zones automatically, set specific music to play, and then stop the music after a defined duration and revert the zones to their prior configuration. Although any particular zone can be triggered to an “On” or “Off” state based on time, for example, a zone scene enables any zone(s) linked to the scene to play a predefined audio (e.g., a favorable song, a predefined playback queue) at a specific time and/or for a specific duration. If, for any reason, the scheduled music failed to be played (e.g., an empty playback queue, no connection to a share, failed Universal Plug and Play (UPnP), no Internet connection for an Internet Radio station, and so on), a backup buzzer can be programmed to sound. The buzzer can include a sound file that is stored in a zone player, for example.
As discussed above, in some embodiments, a media playback system may be associated with one or more playback queues that identify one or more media items for playback by the media playback system. The media items identified in a playback queue may be represented to a user via an interface on a controller (e.g., the controller 130) or other computing device (e.g., the computing devices 120-124). A playback queue that is displayed to a user may be referred herein as a playlist.
Each item in a playback queue may be represented on an interface by an element such as, for example, a media-item title, an artist name, an album title, an album art, a streaming data source name (e.g., an Internet radio station name), or other such representation. Further, the playlist may indicate how the media playback system is traversing the playback queue, such as by highlighting the “now playing” item, graying out the previously played item(s), highlighting the to-be-played item(s), and so on.
A playback queue of a media playback system may be created (populated) and/or modified via a local device within the media playback system (e.g., the controller 230) or a remote device/system (e.g., the media system server 130). In a local creation of a playback queue, a user of a local device may populate the playback queue with media items of interest, for example, by selecting media items from a set of media items available for playback by the media playback system. In a remote creation of a playback queue, one or more computing devices (e.g., the computing devices 120-124) may transmit selection data to a media system server (e.g., the media system server 130). The selection data may indicate a selection of a particular media item from the set of media items to be added to the playback queue of a particular media playback system. The media system server may then populate the playback queue according to the selections.
In implementations that involve a remote creation, a media system server (e.g., the media system 130) may transmit one or more playback queues to a media playback system (e.g., the media playback system 110) via one or more data networks (e.g., the WAN 140). Remote creation of playback queues is discussed in further detail below.
In some embodiments, a single zone player is assigned to a playback queue. For example, zone player 214 in the bathroom of
In some embodiments, a zone or zone group is assigned to a playback queue. For example, zone players 206 and 208 in the family room of
As such, when zones or zone groups are “grouped” or “ungrouped” dynamically by the user via a controller, the system will, in some embodiments, establish or remove/rename playback queues respectively, as each zone or zone group is to be assigned to a playback queue. In other words, the playback queue operates as a container that can be populated with media items for playback by the assigned zone. In some embodiments, the media items identified in a playback queue can be manipulated (e.g., re-arranged, added to, deleted from, and so on).
Particular examples are now provided in connection with
Using the Ad-Hoc network 710, the devices 702, 704, 706, and 708 can share or exchange one or more audio sources and be dynamically grouped (or ungrouped) to play the same or different audio sources. For example, the zone players 702 and 704 may be grouped to playback one piece of music, and at the same time, the zone player 706 may playback another piece of music. In other words, the devices 702, 704, 706 and 708, as shown in
In certain embodiments, a household identifier (HHID) is a short string or an identifier that is computer-generated to help ensure that it is unique. Accordingly, the Ad-Hoc network 710 can be characterized by a unique HHID and a unique set of configuration variables or parameters, such as channels (e.g., respective frequency bands), service set identifier (SSID) (a sequence of alphanumeric characters as a name of a wireless network), and WEP keys (wired equivalent privacy) or other security keys. In certain embodiments, SSID is set to be the same as HHID.
In certain embodiments, each HOUSEHOLD may include two types of network nodes: a control point (CP) and a zone player (ZP). The CP controls an overall network setup process and sequencing, including an automatic generation of required network parameters (e.g., security keys). In an embodiment, the CP also provides the user with a HOUSEHOLD configuration user interface. The CP function can be provided by a computer running a CP application module, or by a handheld controller (e.g., the controller 708) also running a CP application module, for example. The ZP is any other device on the network that is placed to participate in the automatic configuration process. In certain embodiments, the ZP, as a notation used herein, may include the controller 708 or a computing device, for example. In some embodiments, the functionality, or certain parts of the functionality, in both the CP and the ZP may be combined at a single node (e.g., a ZP contains a CP or vice-versa).
In certain embodiments, HOUSEHOLD configuration may involve multiple CPs and ZPs that rendezvous and establish a known configuration such that they can use a standard networking protocol (e.g., IP over Wired or Wireless Ethernet) for communication. In an embodiment, two types of networks/protocols may be employed: Ethernet 802.3 and Wireless 802.11g. Interconnections between a CP and a ZP can use either of the networks/protocols. A device in the system as a member of a HOUSEHOLD can connect to both networks simultaneously.
In an environment that has both networks in use, it is assumed that at least one device in a system is connected to both as a bridging device, thus providing bridging services between wired/wireless networks for others. The zone player 702 in
It is understood, however, that in some embodiments each zone player 702-706 may access the Internet when retrieving media from the cloud (e.g., the Internet) via the bridging device. For example, the zone player 702 may contain a uniform resource locator (URL) that specifies an address to a particular audio track in the cloud. Using the URL, the zone player 702 may retrieve the audio track from the cloud, and ultimately play the audio out of one or more of the other zone players.
As discussed above, a media playback system may be associated with a playback queue, and in some situations, it may be desirable to remotely create and/or modify the playback queue.
For clarity, the methods are described herein with reference to
Furthermore, those skilled in the art will understand that the flowcharts described herein depict functionality and operation of certain implementations of example embodiments. In this regard, each block of each flowchart may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by a processor for implementing specific logical functions or steps in the process. The program code may be stored on any type of computer readable medium, e.g., such as a storage device including a disk or hard drive. In addition, each block may represent circuitry that is wired to perform the specific logical functions in the process. Alternative implementations are included within the scope of the example embodiments of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrent or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
The method 800 may begin at block 802 with receiving by a computing device an electronic invitation to add at least one media item to a playback queue of a media playback system, where the electronic invitation includes a link to access information identifying a set of media items available for playback by the media playback system, and where the computing device and the media playback system are communicatively coupled via at least a WAN. At block 804, the method 800 may involve causing by the computing device a graphical display to display the information identifying the set of media items available for playback by the media playback system. At block 806, the method 800 may involve sending by the computing device selection data that indicates a selection of a particular media item from the set of media items to be added to the playback queue of the media playback system. At block 808, the method 800 may optionally or additionally involve sending by the computing device annotation data that indicates annotation information that is associated with the selection to be added to the playback queue. Each of the blocks shown with respect to
The method 800 may begin at block 802 with receiving by a computing device an electronic invitation to add at least one media item to a playback queue of a media playback system, where the electronic invitation includes a link to access information identifying a set of media items available for playback by the media playback system, and where the computing device and the media playback system are communicatively coupled via at least a WAN. In example implementations, receiving the electronic invitation may involve the computing device 120 receiving the electronic invitation from the media system server 130 via the WAN 140.
The electronic invitation may take several forms. For example, the electronic invitation may be an email, a text message (e.g., a SMS or MMS message), or a social media communication, among other possibilities.
Broadly speaking, the electronic invitation may include a request for the invitation recipient to attend an event at a future date and to, prior to the event, add media items to a playback queue that may be played at the event by a media playback system (e.g., the media playback system 110). The electronic invitation may include request data that indicates a request for the invitation recipient to add at least one media item to the playback queue. The request data may be text data, video data, and/or audio data that when output by the computing device 120 indicates a request that the invitation recipient add at least one media item to the playback queue.
The electronic invitation may further include a link that provides access to the information identifying a set of media items available for playback by the media playback system. For example, the link may provide access to certain data from the database 131 of
In example implementations, the link may include a uniform resource locator (URL) that identifies a particular resource (e.g., the media system server 130) that is associated with the electronic invitation and that stores the information identifying the set of media items. The URL may additionally or alternatively identify an Internet location of the particular resource. In some implementations, the link may be a hyperlink that is configured to direct the computing device 120 to the particular resource upon a user input indicating a selection of the hyperlink.
Further, the link may be configured such that tracking data may be sent to the particular resource when the link is accessed. The particular resource may use the tracking data to identify the number of users accessing the URL. Additionally or alternatively, the particular resource may limit the number of users that may access the URL and use the tracking data to determine whether a predefined threshold has been met. If the threshold has been met, the particular resource may prevent further access to the set of media items. Furthermore, the particular resource may additionally or alternatively limit a user to a threshold number of added media items. Once the particular user meets that threshold, the particular resource may prevent the user from adding any additional media items. Other examples are certainly possible.
In some implementations, the electronic invitation may further include a time element that indicates a time after which media items will not be available to be added to the playback queue. That is, the time element may define the lifetime of the electronic invitation during which invitation recipients may select media items to be added to the playback queue. In one example, the time element may include a countdown timer, and the media items will not be available to be added to the playback queue upon expiration of the countdown timer. In any event, after the time element indicates that the lifetime of the electronic invitation has expired, the link may expire or otherwise become inactive, or user permissions may be altered such that viewing a playlist may be allowed but adding additional media items to the playback queue is not allowed. Other examples are also possible.
Additionally, the electronic invitation may further include a queue profile that defines characteristics of the queue and how the playback queue will be played by the media playback system. The queue profile may include a start time indicating when the media playback system will begin playback of the queue, a play duration indicating a total amount of time that the media playback system will playback media items from the queue, zone groupings, a mood setting, and/or a queue genre. The queue profile might be stored in the database 131.
A mood setting may indicate a playback queue theme that guides or otherwise suggests the type of media items that invitation recipients should add to the playback queue. For example, a mood setting might be “slow romantic”, “dance party”, or “lights on . . . time to go home”, among other examples. The mood setting might transition throughout the queue, or the mood setting might be fixed. For instance, a mood setting might transition from “dance party” to “slow romantic” to “lights on . . . time to go home”, which might correspond to the various phases of the event (e.g., a party) where the playback queue will be played.
In some implementations, the mood setting might limit what media items can be added to the playback queue via a “mood filter.” The mood filter might filter a media item based on one or more attributes of the media item, such as the genre of the media item or one or more words from the media item title. For example, if the mood setting is “slow romantic”, the mood filter might reject the addition of a media item titled “Party Rock.” In example implementations, the mood filter might additionally or alternatively filter items based on the underlying content of the media item. For example, if the mood setting is set to “dance party”, the mood filter might reject the addition of media items that have a slow-tempo for instance. Other examples are possible as well.
A queue genre may indicate the genre of media items that invitation recipients are permitted to add to the playback queue. For example, the queue genre may be “Country” and thus the invitation recipients may be limited to add only Country media items to the playback queue. Other examples are certainly possible.
Once the electronic invitation is received, the computing device 120 may cause a graphical display of the computing device 120 to display the electronic invitation.
At block 804, the method 800 may involve causing by the computing device a graphical display to display the information identifying the set of media items available for playback by the media playback system. The displayed information may be configured to be interactive such that a user may add one or more media items to the playback queue by selecting an aspect of the displayed information.
In some implementations, the information identifying the set of media items may include one or more identifiers that are associated with one or more respective media items from the set of media items. In some examples, the identifiers may include: a media item title, an artist name, an album title, a genre, and a streaming source name, among other identifier types.
In example implementations, causing by the computing device the graphical display to display the information identifying the set of media items may involve causing the graphical display to display the information via a web interface. For example, a web browser may display on the graphical display of the computing device 120 a web page that includes a representation of the set of media items of the media playback system 110. The web page may be used to add media items to a playback queue without requiring the computing device 120 to be configured with an application associated with the media system server 130. As such, the web page may include one or more selectable aspects that are configured to, when selected, allow a user to add a media item to the playback queue.
The web interface may be searchable such that a user may enter search criteria to navigate the set of media items. For example, the web interface may allow a user to search the set of media items by one or more media-item identifiers. Further, the web interface may be configured to display a playlist in real-time as the playback queue is being created and/or modified. The web interface may also be configured to display the playlist after the event. Additionally, the web interface may be configured to permit a user to select one or more media items from a current playback queue and add the selected media items to another playback queue (e.g., a playback queue associated with a different media playback system).
Other information may be accessible from the web interface as well. For example, the other information may include event information (e.g., the date, the time, the location, the guest list of the event, etc.), a link to a map or a web page with directions to the event, and/or a link to add annotation information to the media items that a particular user added to the playback queue, among other additional information. The web interface may also be configured to allow a user to provide a comment regarding the event and/or tag an image from the event after the event has occurred.
In some implementations, where the computing device 120 is configured with an application associated with the media system server 130, causing by the computing device the graphical display to display the information identifying the set of media items may involve launching the application and causing the graphical display to display the information via an application interface. The application interface may be configured the same as or similar to the web interface herein described.
In example implementations, causing by the computing device the graphical display to display the information identifying the set of media items may involve receiving link-select data by the computing device that indicates a selection of the link. For example, the computing device 120 may receive input data via an input at an input interface of the computing device 120 that indicates a selection of the link in the electronic invitation.
In some implementations, the web interface may additionally or alternatively provide a mechanism by which a user may search for media items and/or services not currently available for playback by the media playback system and add such media items and/or services to the playback queue. That is, in such an implementation, a user might use the web interface to identify or otherwise suggest a media item for the media playback system to make available for playback.
At block 806, the method 800 may involve sending by the computing device selection data that indicates a selection of a particular media item from the set of media items to be added to the playback queue of the media playback system. In example implementations, sending the selection data might involve the computing device 120 sending the selection data to the media system server 130 via the WAN 140.
The selection of the particular media item may involve a selection of a media item title, an artist name, an album title, a genre, a streaming source name, or a selectable aspect associated with any of the former, or any combination thereof. Additionally or alternatively, the selection of the particular media item may involve a selection of a voting aspect associated with the particular media item.
In example implementations, sending by the computing device selection data may involve receiving a selection input by an input interface of the computing device that indicates a selection of one or more media items from the displayed information identifying the set of media items available for playback by the media playback system. For example, referring back to
In an implementation where a user may add a media item not currently available for playback by the media playback system, the selection data might include a URL or some other location mechanism that specifies an address to the particular media item not currently available for playback that is located at a resource that is connected to the WAN 140.
At block 808, the method 800 may optionally or additionally involve sending by the computing device annotation data that indicates annotation information that is associated with the selection to be added to the playback queue. Similar to sending the selection data, sending the annotation data might involve the computing device 120 sending the annotation data to the media system server 130 via the WAN 140.
As described above, in certain implementations other information may be accessible from the web interface, such as a link to add annotation information to the media items that a particular user added to the playback queue. That is, in addition to adding a media item to the playback queue, a user may add an annotation to let others know who added the media item and/or why the media item was added for instance. Example annotation information may include a message, an image, a video, and/or a social media status, among other possibilities. When a user adds annotation information to a media item, the computing device 120 may send corresponding annotation data (that indicates the annotation information) that may include message data, image data, and/or video data for example. Other annotation data is also possible.
In certain embodiments, the annotation data may be sent by a computing device during the event (e.g., while a media item is playing). For example, while a media playback system is playing back a media item, a computing device may capture image data and send the image data as annotation data associated with the media item. Other examples are certainly possible.
The annotation information may be displayed at a graphical display (e.g., of one or more of the computing devices 120-126 and/or a controller device of the media playback system 110) when the graphical display is displaying a representation of the media item that the annotation information is associated with. An example of displayed annotation information is discussed below with reference to
The method 900 may optionally begin at block 902 with receiving by a computing system from a given computing device instruction data that includes an instruction to provide a plurality of electronic invitations to a plurality of respective remote computing devices. At block 904, the method 900 may involve providing, by the computing system that is communicatively coupled to a media playback system via a WAN, the plurality of electronic invitations to the plurality of respective remote computing devices to add at least one media item to a playback queue of the media playback system, where each of the plurality of electronic invitations comprises a link to access information identifying one or more media items available for playback by the media playback system. In certain implementations, the method 900 may begin at block 904. At block 906, the method 900 may involve receiving by the computing system selection data that indicates one or more media item selections associated with one or more of the plurality of electronic invitations. At block 908, the method 900 may involve populating by the computing system the playback queue based on the one or more media item selections indicated by the received selection data. At block 910, the method 900 may optionally involve, responsive to the expiration of a predefined amount of time, preventing by the computing system any future media item selections. At block 912, the method 900 may optionally involve providing a media item to the media playback system for playback.
As mentioned above, blocks 902, 910 and 912 are optional. That is, the method 900 may involve blocks 904-908 without any additional blocks, or the method 900 may involve blocks 904-908 and one or more of the optional blocks 902, 910, and 912. Each of the blocks shown with respect to
The method 900 may optionally begin at block 902 with receiving by a computing system from a given computing device instruction data that includes an instruction to provide a plurality of electronic invitations to a plurality of respective remote computing devices. In example embodiments, the media system sever 130 may receive from the computing device 126 instruction data that includes an instruction to provide a plurality of electronic invitations to the remote computing devices 120-124. The instruction data may be based on one or more inputs at an input interface of the computing device 126. A graphical display of the computing device 126 may display prompts for a user to input invitation data to be sent to the plurality of remote computing devices 120-124.
In some embodiments, the given computing device may be associated with a media playback system. As described above with reference to
Generally speaking, the instruction data may include data that indicates the contents of the electronic invitations (e.g., a request to add at least one media item to a playback queue and a link to access the set of media items) and other information related to the event. In particular, the instruction data may include event data that may indicate a time, a date, and/or a location of the event. Further, the instruction data may include invitation data that may indicate a time element of the invitation (e.g., how long recipients may add media items to the playback queue), any queue addition limitations (e.g., a limited or unlimited number of media items each recipient is permitted to add to a playback queue), a queue name tied to the event, and/or a means to share the electronic invitations with the remote computing devices (e.g., via an email, a text message, or a social media network identifier associated with the remote computing devices). It should be understood that the above are just examples of data that the instruction data might include and should not be construed as limiting.
At block 904, the method 900 may involve providing, by the computing system that is communicatively coupled to a media playback system via a WAN, the plurality of electronic invitations to the plurality of respective remote computing devices to add at least one media item to a playback queue of the media playback system, where each of the plurality of electronic invitations comprises a link to access information identifying one or more media items available for playback by the media playback system. As noted above, in certain embodiments, the method 900 may begin at block 904.
In example embodiments, the media system server 130 may provide the plurality of electronic invitations to the remote computing devices 120-124 via the WAN 140. Each of the plurality of electronic invitations may include a link to access information identifying the set of media items available for playback by the media playback system 110. The electronic invitation and link may be the same as or similar to the electronic invitation and link discussed above with reference to block 802 of
At block 906, the method 900 may involve receiving by the computing system selection data that indicates one or more media item selections associated with one or more of the plurality of electronic invitations. In example embodiments, the media system server 130 may receive the selection data from one or more of the computing devices 120-124 via the WAN. The selection data may be the same as or similar to the selection data discussed above with reference to block 806 of
As discussed above, in some implementations, the selection data may include vote data that indicates an up or down vote for a media item currently in the playback queue. The computing system may also receive annotation information from a remote computing device that is associated with the selection data. For example, the annotation information may include a message, and/or an image, among other possibilities.
In an implementation where the selection data includes a location mechanism that specifies an address to a media item not currently available for playback, after receiving such selection data, the computing system may then verify that the media item located at the address is playable at the media playback system. If the computing system determines that the media item is not playable, the computing system may discard that media item and may send data back to the computing device from which the selection data originated indicating that the media item is not playable. Other possibilities also exist.
At block 908, the method 900 may involve populating by the computing system the playback queue based on the one or more media item selections indicated by the received selection data. That is, the computing system (e.g., the media system server 130) may create or modify the playback queue by adding, removing, and/or re-ordering one or more media items based on the selections.
Populating the playback queue may involve the computing system placing the media item corresponding to the selection at the bottom or the top of the playback queue as the computing system receives the selections. Alternatively, populating the playback queue may involve the computing system placing the media item corresponding to the selection at a random spot within the playback queue. Further, populating the playback queue may involve the computing system moving a media item up or down in the playback queue order based on vote data.
In an implementation where the playback queue includes a mood setting, populating the playback queue may involve the computing system automatically placing the media item corresponding to the selection at a spot within the playback queue based on the mood setting and one or more attributes of the media item and/or the underlying content of the media item. For instance, continuing from the above example where the playback queue has a transitioning mood setting of “dance party” to “slow romantic” to “lights on . . . time to go home”, the computing system might place a media item with a slow tempo in the portion of the playback queue that corresponds to the “slow romantic” mood setting. On the other hand, if the media item has a title such as “Closing Time”, the computing system might place the media item in the portion of the playback queue that corresponds to the “lights on . . . time to go home” mood setting. Other examples are certainly possible. In other such implementations, the computing system might order the selections based on a
At block 910, the method 900 may optionally or additionally involve, responsive to the expiration of a predefined amount of time, preventing by the computing system any future media item selections. That is, in certain embodiments where the electronic invitations include a time element, the computing system may no longer allow invitation recipients to add media items to the playback queue after the time element expires. The time element may be the same as or similar to the time element described above with reference to block 802 of
In example embodiments, after preventing any future media item selections, recipients may still be able to view the playback queue, and in some embodiments, recipients may still be able to vote on moving a particular media item up or down in the playlist order. Other examples are also possible.
At block 912, the method 900 may optionally or additionally involve providing a media item to the media playback system for playback. In example embodiments, providing the media item to the media playback system for playback may involve the media system server 130 sending the media item or a pointer (or other location mechanism) for the underlying content of the media item to the media playback system 110.
In certain implementations, the method 900 may optionally or additionally involve providing by the computing system a playlist that includes information that identifies the current media items in the playback queue. The computing device may provide the playlist to one or more of the computing devices 120-126 and/or a controller device of the media playback system 110.
In some implementations, the method 900 may optionally or additionally involve providing by the computing system annotation data that indicates annotation information that is associated with a particular media item identified in the playlist. The annotation data may include message data and/or image data that indicates a message or image, respectively, associated with a particular media item. The computing system may provide the annotation information (e.g., a remote computing device may display the annotation information via a graphical display) before the event, during the event while the corresponding media item is played, and/or after the event.
The descriptions above disclose various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. However, such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these firmware, hardware, and/or software components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, while the following describes example systems, methods, apparatus, and/or articles of manufacture, the examples provided are not the only way(s) to implement such systems, methods, apparatus, and/or articles of manufacture.
As provided in the embodiments discussed above, the present application may allow for remotely creating a playback queue of a media playback system by remote computing devices in communication with the media playback system via a WAN. In one aspect, a method is provided. The method involves receiving by a computing device an electronic invitation to add at least one media item to a playback queue of a media playback system, where the electronic invitation comprises a link to access information identifying a set of media items available for playback by the media playback system, and where the computing device and the media playback system are communicatively coupled via at least a WAN. The method further involves causing by the computing device a graphical display to display the information identifying the set of media items available for playback by the media playback system. The method further involves sending by the computing device selection data that indicates a selection of a particular media item from the set of media items to be added to the playback queue of the media playback system.
In another aspect, a non-transitory computer readable medium is provided. The non-transitory computer readable having instructions stored thereon that are executable by at least one processor. The instructions include instructions for receiving by a computing device an electronic invitation to add at least one media item to a playback queue of a media playback system, where the electronic invitation comprises a link to access information identifying a set of media items available for playback by the media playback system, and where the computing device and the media playback system are communicatively coupled via at least a WAN. The instructions further include instructions for causing by the computing device a graphical display to display the information identifying the set of media items available for playback by the media playback system. The instructions further include instructions for sending by the computing device selection data that indicates a selection of a particular media item from the set of media items to be added to the playback queue of the media playback system.
In one other aspect, a computing device is provided. The computing device includes a graphical display, a network interface, a non-transitory computer readable medium, and program instructions stored on the non-transitory computer readable medium. The program instructions are executable by at least one processor to cause the computing device to receive an electronic invitation to add at least one media item to a playback queue of a media playback system, where the electronic invitation comprises a link to access information identifying a set of media items available for playback by the media playback system, and where the computing device and the media playback system are communicatively coupled via at least a WAN. The program instructions are executable by the at least one processor to further cause the computing device to cause the graphical display to display the information identifying the set of media items available for playback by the media playback system. The program instructions are executable by the at least one processor to further cause the computing device to send selection data that indicates a selection of a particular media item from the set of media items to be added to the playback queue of the media playback system.
In another aspect, a method is provided. The method involves providing, by a computing system that is communicatively coupled to a media playback system via a WAN, a plurality of electronic invitations to a plurality of respective remote computing devices to add at least one media item to a playback queue of the media playback system, where each of the plurality of electronic invitations comprises a link to access information identifying one or more media items available for playback by the media playback system. The method further involves receiving by the computing system selection data that indicates one or more media item selections associated with one or more of the plurality of electronic invitations. The method further involves populating by the computing system the playback queue based on the one or more media item selections indicated by the received selection data.
In an additional aspect, a non-transitory computer readable medium is provided. The non-transitory computer readable having instructions stored thereon that are executable by at least one processor. The instructions include instructions for providing, by a computing system that is communicatively coupled to a media playback system via a WAN, a plurality of electronic invitations to a plurality of respective remote computing devices to add at least one media item to a playback queue of the media playback system, where each of the plurality of electronic invitations comprises a link to access information identifying one or more media items available for playback by the media playback system. The instructions further include instructions for receiving by the computing system selection data that indicates one or more media item selections associated with one or more of the plurality of electronic invitations. The instructions further include instructions for populating by the computing system the playback queue based on the one or more media item selections indicated by the received selection data.
In a further aspect, a computing system is provided. The computing device includes a network interface, a non-transitory computer readable medium, and program instructions stored on the non-transitory computer readable medium. The network interface communicatively couples the computing system to a media playback system via a WAN. The program instructions are executable by at least one processor to cause the computing system to provide a plurality of electronic invitations to a plurality of respective remote computing devices to add at least one media item to a playback queue of the media playback system, where each of the plurality of electronic invitations comprises a link to access information identifying one or more media items available for playback by the media playback system. The program instructions are executable by the at least one processor to further cause the computing device to receive selection data that indicates one or more media item selections associated with one or more of the plurality of electronic invitations. The program instructions are executable by the at least one processor to further cause the computing device to populate the playback queue based on the one or more media item selections indicated by the received selection data.
Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment of the invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.
The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.
When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.
This application claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. patent application Ser. No. 16/516,767, filed on Jul. 19, 2019, entitled “Remote Creation of a Playback Queue for a Future Event,” which is incorporated herein by reference in its entirety. U.S. patent application Ser. No. 16/516,767 claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. patent application Ser. No. 15/692,090, filed on Aug. 31, 2017, entitled “Remote Creation of a Playback Queue for a Future Event” and issued as U.S. Pat. No. 10,360,290 on Jul. 23, 2019, which is incorporated herein by reference in its entirety. U.S. patent application Ser. No. 15/692,090 claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. patent application Ser. No. 14/173,253, filed on Feb. 5, 2014, entitled “Remote Creation of a Playback Queue for a Future Event,” which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4296278 | Cullison et al. | Oct 1981 | A |
| 4816989 | Finn et al. | Mar 1989 | A |
| 5182552 | Paynting | Jan 1993 | A |
| 5239458 | Suzuki | Aug 1993 | A |
| 5299266 | Lumsden | Mar 1994 | A |
| 5406634 | Anderson et al. | Apr 1995 | A |
| 5440644 | Farinelli et al. | Aug 1995 | A |
| 5467342 | Logston et al. | Nov 1995 | A |
| 5491839 | Schotz | Feb 1996 | A |
| 5553222 | Milne et al. | Sep 1996 | A |
| 5563946 | Cooper et al. | Oct 1996 | A |
| 5668884 | Clair, Jr. | Sep 1997 | A |
| 5673323 | Schotz et al. | Sep 1997 | A |
| 5751819 | Dorrough | May 1998 | A |
| 5761320 | Farinelli et al. | Jun 1998 | A |
| 5774666 | Portuesi | Jun 1998 | A |
| 5808662 | Kinney et al. | Sep 1998 | A |
| 5815689 | Shaw et al. | Sep 1998 | A |
| 5856827 | Sudo | Jan 1999 | A |
| 5867691 | Shiraishi | Feb 1999 | A |
| 5875354 | Charlton et al. | Feb 1999 | A |
| 5887143 | Saito et al. | Mar 1999 | A |
| 5923902 | Inagaki | Jul 1999 | A |
| 5946343 | Schotz et al. | Aug 1999 | A |
| 5956088 | Shen et al. | Sep 1999 | A |
| 6002862 | Takaike | Dec 1999 | A |
| 6009457 | Moller | Dec 1999 | A |
| 6026150 | Frank et al. | Feb 2000 | A |
| 6031818 | Lo et al. | Feb 2000 | A |
| 6032202 | Lea et al. | Feb 2000 | A |
| 6108686 | Williams, Jr. | Aug 2000 | A |
| 6128318 | Sato | Oct 2000 | A |
| 6157957 | Berthaud | Dec 2000 | A |
| 6175872 | Neumann et al. | Jan 2001 | B1 |
| 6181316 | Little et al. | Jan 2001 | B1 |
| 6185737 | Northcutt et al. | Feb 2001 | B1 |
| 6195436 | Scibora et al. | Feb 2001 | B1 |
| 6199169 | Voth | Mar 2001 | B1 |
| 6255961 | Van et al. | Jul 2001 | B1 |
| 6256554 | DiLorenzo | Jul 2001 | B1 |
| 6308207 | Tseng et al. | Oct 2001 | B1 |
| 6324586 | Johnson | Nov 2001 | B1 |
| 6332147 | Moran et al. | Dec 2001 | B1 |
| 6349339 | Williams | Feb 2002 | B1 |
| 6351821 | Voth | Feb 2002 | B1 |
| 6404811 | Cvetko et al. | Jun 2002 | B1 |
| 6430353 | Honda et al. | Aug 2002 | B1 |
| 6469633 | Wachter | Oct 2002 | B1 |
| 6487296 | Allen et al. | Nov 2002 | B1 |
| 6522886 | Youngs et al. | Feb 2003 | B1 |
| 6526325 | Sussman et al. | Feb 2003 | B1 |
| 6587127 | Leeke et al. | Jul 2003 | B1 |
| 6594691 | McCollum et al. | Jul 2003 | B1 |
| 6598172 | Vandeusen et al. | Jul 2003 | B1 |
| 6611537 | Edens et al. | Aug 2003 | B1 |
| 6631410 | Kowalski et al. | Oct 2003 | B1 |
| 6674803 | Kesselring | Jan 2004 | B1 |
| 6728531 | Lee et al. | Apr 2004 | B1 |
| 6732155 | Meek | May 2004 | B2 |
| 6757517 | Chang | Jun 2004 | B2 |
| 6778869 | Champion | Aug 2004 | B2 |
| 6826283 | Wheeler et al. | Nov 2004 | B1 |
| 6836788 | Kim et al. | Dec 2004 | B2 |
| 6898642 | Chafle et al. | May 2005 | B2 |
| 6912610 | Spencer | Jun 2005 | B2 |
| 6920373 | Xi et al. | Jul 2005 | B2 |
| 6934766 | Russell | Aug 2005 | B1 |
| 6985694 | De Bonet et al. | Jan 2006 | B1 |
| 7007106 | Flood et al. | Feb 2006 | B1 |
| 7017118 | Carroll | Mar 2006 | B1 |
| 7020048 | Mccomas | Mar 2006 | B2 |
| 7020791 | Aweya et al. | Mar 2006 | B1 |
| 7043651 | Aweya et al. | May 2006 | B2 |
| 7047308 | Deshpande | May 2006 | B2 |
| 7113833 | Brown et al. | Sep 2006 | B1 |
| 7113999 | Pestoni et al. | Sep 2006 | B2 |
| 7115017 | Laursen et al. | Oct 2006 | B1 |
| 7117451 | Sielken | Oct 2006 | B2 |
| 7124125 | Cook et al. | Oct 2006 | B2 |
| 7130608 | Hollstrom et al. | Oct 2006 | B2 |
| 7130616 | Janik | Oct 2006 | B2 |
| 7143141 | Morgan et al. | Nov 2006 | B1 |
| 7143939 | Henzerling | Dec 2006 | B2 |
| 7162315 | Gilbert | Jan 2007 | B2 |
| 7185090 | Kowalski et al. | Feb 2007 | B2 |
| 7187947 | White et al. | Mar 2007 | B1 |
| 7206367 | Moore | Apr 2007 | B1 |
| 7209795 | Sullivan et al. | Apr 2007 | B2 |
| 7218708 | Berezowski et al. | May 2007 | B2 |
| 7236739 | Chang | Jun 2007 | B2 |
| 7236773 | Thomas | Jun 2007 | B2 |
| 7281034 | Eyal | Oct 2007 | B1 |
| 7293060 | Komsi | Nov 2007 | B2 |
| 7295548 | Blank et al. | Nov 2007 | B2 |
| 7302468 | Wijeratne | Nov 2007 | B2 |
| 7312785 | Tsuk et al. | Dec 2007 | B2 |
| 7324857 | Goddard | Jan 2008 | B2 |
| 7333519 | Sullivan et al. | Feb 2008 | B2 |
| 7358960 | Mak | Apr 2008 | B2 |
| 7372846 | Zwack | May 2008 | B2 |
| 7391791 | Balassanian et al. | Jun 2008 | B2 |
| 7392102 | Sullivan et al. | Jun 2008 | B2 |
| 7483538 | McCarty et al. | Jan 2009 | B2 |
| 7483958 | Elabbady et al. | Jan 2009 | B1 |
| 7496623 | Szeto et al. | Feb 2009 | B2 |
| 7496633 | Szeto et al. | Feb 2009 | B2 |
| 7571014 | Lambourne et al. | Aug 2009 | B1 |
| 7574274 | Holmes | Aug 2009 | B2 |
| 7599685 | Goldberg et al. | Oct 2009 | B2 |
| 7630501 | Blank et al. | Dec 2009 | B2 |
| 7643894 | Braithwaite et al. | Jan 2010 | B2 |
| 7657224 | Goldberg et al. | Feb 2010 | B2 |
| 7657644 | Zheng | Feb 2010 | B1 |
| 7657910 | McAulay et al. | Feb 2010 | B1 |
| 7668990 | Krzyzanowski et al. | Feb 2010 | B2 |
| 7669219 | Scott, III et al. | Feb 2010 | B2 |
| 7675943 | Mosig et al. | Mar 2010 | B2 |
| 7676142 | Hung | Mar 2010 | B1 |
| 7702279 | Ko et al. | Apr 2010 | B2 |
| 7720096 | Klemets | May 2010 | B2 |
| 7725533 | Szeto et al. | May 2010 | B2 |
| 7725551 | Szeto et al. | May 2010 | B2 |
| 7739271 | Cook et al. | Jun 2010 | B2 |
| 7742740 | Goldberg et al. | Jun 2010 | B2 |
| 7788138 | Viehmann et al. | Aug 2010 | B2 |
| 7805682 | Lambourne | Sep 2010 | B1 |
| 7835689 | Goldberg et al. | Nov 2010 | B2 |
| 7853341 | McCarty et al. | Dec 2010 | B2 |
| 7865137 | Goldberg et al. | Jan 2011 | B2 |
| 7885622 | Krampf et al. | Feb 2011 | B2 |
| 7916877 | Goldberg et al. | Mar 2011 | B2 |
| 7917082 | Goldberg et al. | Mar 2011 | B2 |
| 7921369 | Bill | Apr 2011 | B2 |
| 7934239 | Dagman | Apr 2011 | B1 |
| 7987294 | Bryce et al. | Jul 2011 | B2 |
| 7996566 | Sylvain et al. | Aug 2011 | B1 |
| 8014423 | Thaler et al. | Sep 2011 | B2 |
| 8023663 | Goldberg | Sep 2011 | B2 |
| 8028038 | Weel | Sep 2011 | B2 |
| 8028323 | Weel | Sep 2011 | B2 |
| 8045952 | Qureshey et al. | Oct 2011 | B2 |
| 8050652 | Qureshey et al. | Nov 2011 | B2 |
| 8074253 | Nathan | Dec 2011 | B1 |
| 8086752 | Millington et al. | Dec 2011 | B2 |
| 8103009 | McCarty et al. | Jan 2012 | B2 |
| 8112032 | Ko et al. | Feb 2012 | B2 |
| 8131390 | Braithwaite et al. | Mar 2012 | B2 |
| 8169938 | Duchscher et al. | May 2012 | B2 |
| 8200602 | Farrelly | Jun 2012 | B2 |
| 8214873 | Weel | Jul 2012 | B2 |
| 8230099 | Weel | Jul 2012 | B2 |
| 8234395 | Millington | Jul 2012 | B2 |
| 8271115 | Yoshida | Sep 2012 | B2 |
| 8290603 | Lambourne | Oct 2012 | B1 |
| 8315555 | Ko et al. | Nov 2012 | B2 |
| 8370678 | Millington et al. | Feb 2013 | B2 |
| 8423659 | Millington | Apr 2013 | B2 |
| 8483853 | Lambourne | Jul 2013 | B1 |
| 8521316 | Louboutin | Aug 2013 | B2 |
| 8588949 | Lambourne et al. | Nov 2013 | B2 |
| 8613385 | Hulet et al. | Dec 2013 | B1 |
| 8666826 | Narayanan et al. | Mar 2014 | B2 |
| 8775546 | Millington | Jul 2014 | B2 |
| 8826135 | Durham et al. | Sep 2014 | B1 |
| 8843500 | Nogues et al. | Sep 2014 | B2 |
| 8892648 | Durham et al. | Nov 2014 | B1 |
| 8910265 | Lang et al. | Dec 2014 | B2 |
| 8942252 | Balassanian et al. | Jan 2015 | B2 |
| 8990701 | Olofsson | Mar 2015 | B2 |
| 9052810 | Reimann et al. | Jun 2015 | B2 |
| 9137564 | Reimann | Sep 2015 | B2 |
| 9165255 | Shetty et al. | Oct 2015 | B1 |
| 9229938 | Jaini et al. | Jan 2016 | B1 |
| 9246866 | Sanders | Jan 2016 | B1 |
| 9247363 | Triplett et al. | Jan 2016 | B2 |
| 9286384 | Kuper et al. | Mar 2016 | B2 |
| 9344292 | Griffiths et al. | May 2016 | B2 |
| 9374607 | Bates et al. | Jun 2016 | B2 |
| 9478247 | Chen et al. | Oct 2016 | B2 |
| 9489383 | Hyman et al. | Nov 2016 | B2 |
| 9510055 | Kuper et al. | Nov 2016 | B2 |
| 9524338 | Van et al. | Dec 2016 | B2 |
| 9654821 | Coburn, IV et al. | May 2017 | B2 |
| 9665339 | Reimann et al. | May 2017 | B2 |
| 9674587 | Triplett et al. | Jun 2017 | B2 |
| 9680960 | Chen | Jun 2017 | B2 |
| 9696874 | Kulick et al. | Jul 2017 | B2 |
| 9703521 | Kumar et al. | Jul 2017 | B2 |
| 9715500 | Cue et al. | Jul 2017 | B2 |
| 9727219 | Kumar et al. | Aug 2017 | B2 |
| 9756092 | Zhang et al. | Sep 2017 | B2 |
| 9892118 | Kumar et al. | Feb 2018 | B2 |
| 9942335 | Schneider et al. | Apr 2018 | B2 |
| 9977561 | Bates et al. | May 2018 | B2 |
| 10032233 | Papakipos et al. | Jul 2018 | B2 |
| 10129599 | Van Der Heide | Nov 2018 | B2 |
| 10157033 | Millington | Dec 2018 | B2 |
| 10268352 | Coburn, IV et al. | Apr 2019 | B2 |
| 10275135 | Coburn, IV et al. | Apr 2019 | B2 |
| 10296884 | Lang et al. | May 2019 | B2 |
| 10469897 | Reimann et al. | Nov 2019 | B2 |
| 20010009604 | Ando et al. | Jul 2001 | A1 |
| 20010022823 | Renaud | Sep 2001 | A1 |
| 20010032188 | Miyabe et al. | Oct 2001 | A1 |
| 20010042107 | Palm | Nov 2001 | A1 |
| 20020002039 | Qureshey et al. | Jan 2002 | A1 |
| 20020002562 | Moran et al. | Jan 2002 | A1 |
| 20020003548 | Krusche et al. | Jan 2002 | A1 |
| 20020022453 | Balog et al. | Feb 2002 | A1 |
| 20020026442 | Lipscomb et al. | Feb 2002 | A1 |
| 20020034374 | Barton | Mar 2002 | A1 |
| 20020042844 | Chiazzese | Apr 2002 | A1 |
| 20020049843 | Barone et al. | Apr 2002 | A1 |
| 20020054134 | Kelts et al. | May 2002 | A1 |
| 20020056117 | Hasegawa et al. | May 2002 | A1 |
| 20020065926 | Hackney et al. | May 2002 | A1 |
| 20020072816 | Shdema et al. | Jun 2002 | A1 |
| 20020073228 | Cognet et al. | Jun 2002 | A1 |
| 20020090914 | Kang et al. | Jul 2002 | A1 |
| 20020093478 | Yeh | Jul 2002 | A1 |
| 20020109710 | Holtz et al. | Aug 2002 | A1 |
| 20020112244 | Liou et al. | Aug 2002 | A1 |
| 20020116476 | Eyal et al. | Aug 2002 | A1 |
| 20020124097 | Isely et al. | Sep 2002 | A1 |
| 20020129156 | Yoshikawa | Sep 2002 | A1 |
| 20020143998 | Rajagopal et al. | Oct 2002 | A1 |
| 20020163361 | Parkin | Nov 2002 | A1 |
| 20020165921 | Sapieyevski | Nov 2002 | A1 |
| 20020178191 | Sielken | Nov 2002 | A1 |
| 20020188762 | Tomassetti et al. | Dec 2002 | A1 |
| 20030002609 | Faller et al. | Jan 2003 | A1 |
| 20030020763 | Mayer et al. | Jan 2003 | A1 |
| 20030023741 | Tomassetti et al. | Jan 2003 | A1 |
| 20030035444 | Zwack | Feb 2003 | A1 |
| 20030041173 | Hoyle | Feb 2003 | A1 |
| 20030041174 | Wen et al. | Feb 2003 | A1 |
| 20030043924 | Haddad et al. | Mar 2003 | A1 |
| 20030066094 | Van Der Schaar et al. | Apr 2003 | A1 |
| 20030088875 | Gay et al. | May 2003 | A1 |
| 20030099212 | Anjum et al. | May 2003 | A1 |
| 20030099221 | Rhee | May 2003 | A1 |
| 20030105820 | Haims et al. | Jun 2003 | A1 |
| 20030126211 | Anttila et al. | Jul 2003 | A1 |
| 20030157951 | Hasty, Jr. | Aug 2003 | A1 |
| 20030195964 | Mane | Oct 2003 | A1 |
| 20030198257 | Sullivan et al. | Oct 2003 | A1 |
| 20030210796 | Mccarty et al. | Nov 2003 | A1 |
| 20030220973 | Zhu et al. | Nov 2003 | A1 |
| 20030231871 | Ushimaru | Dec 2003 | A1 |
| 20030235304 | Evans et al. | Dec 2003 | A1 |
| 20040001484 | Ozguner | Jan 2004 | A1 |
| 20040001591 | Mani et al. | Jan 2004 | A1 |
| 20040008852 | Also et al. | Jan 2004 | A1 |
| 20040010727 | Fujinami | Jan 2004 | A1 |
| 20040015252 | Aiso et al. | Jan 2004 | A1 |
| 20040024478 | Hans et al. | Feb 2004 | A1 |
| 20040024925 | Cypher et al. | Feb 2004 | A1 |
| 20040025185 | Goci et al. | Feb 2004 | A1 |
| 20040027166 | Mangum et al. | Feb 2004 | A1 |
| 20040032348 | Lai et al. | Feb 2004 | A1 |
| 20040066736 | Kroeger | Apr 2004 | A1 |
| 20040075767 | Neuman et al. | Apr 2004 | A1 |
| 20040078383 | Mercer et al. | Apr 2004 | A1 |
| 20040078812 | Calvert | Apr 2004 | A1 |
| 20040088328 | Cook et al. | May 2004 | A1 |
| 20040131192 | Metcalf | Jul 2004 | A1 |
| 20040170383 | Mazur | Sep 2004 | A1 |
| 20040203378 | Powers | Oct 2004 | A1 |
| 20040215611 | Jawa et al. | Oct 2004 | A1 |
| 20040249965 | Huggins et al. | Dec 2004 | A1 |
| 20040249982 | Arnold | Dec 2004 | A1 |
| 20040252400 | Blank et al. | Dec 2004 | A1 |
| 20040261040 | Radcliffe et al. | Dec 2004 | A1 |
| 20050010691 | Oyadomari et al. | Jan 2005 | A1 |
| 20050013394 | Rausch et al. | Jan 2005 | A1 |
| 20050021590 | Debique et al. | Jan 2005 | A1 |
| 20050047605 | Lee et al. | Mar 2005 | A1 |
| 20050058149 | Howe | Mar 2005 | A1 |
| 20050081213 | Suzuoki et al. | Apr 2005 | A1 |
| 20050108320 | Lord et al. | May 2005 | A1 |
| 20050114538 | Rose | May 2005 | A1 |
| 20050125357 | Saadat et al. | Jun 2005 | A1 |
| 20050155072 | Kaczowka et al. | Jul 2005 | A1 |
| 20050166157 | Ollis et al. | Jul 2005 | A1 |
| 20050166258 | Vasilevsky et al. | Jul 2005 | A1 |
| 20050177643 | Xu | Aug 2005 | A1 |
| 20050181348 | Carey et al. | Aug 2005 | A1 |
| 20050195205 | Abrams | Sep 2005 | A1 |
| 20050201254 | Looney et al. | Sep 2005 | A1 |
| 20050234875 | Auerbach et al. | Oct 2005 | A1 |
| 20050281255 | Davies et al. | Dec 2005 | A1 |
| 20050283820 | Richards et al. | Dec 2005 | A1 |
| 20050288805 | Moore et al. | Dec 2005 | A1 |
| 20050289224 | Deslippe et al. | Dec 2005 | A1 |
| 20060095516 | Wijeratne | May 2006 | A1 |
| 20060107237 | Kim | May 2006 | A1 |
| 20060119497 | Miller et al. | Jun 2006 | A1 |
| 20060143236 | Wu | Jun 2006 | A1 |
| 20060168340 | Heller et al. | Jul 2006 | A1 |
| 20060195462 | Rogers | Aug 2006 | A1 |
| 20060195479 | Spiegelman et al. | Aug 2006 | A1 |
| 20060195480 | Spiegelman et al. | Aug 2006 | A1 |
| 20060253436 | Cook et al. | Nov 2006 | A1 |
| 20060253782 | Stark et al. | Nov 2006 | A1 |
| 20060294074 | Chang | Dec 2006 | A1 |
| 20070033402 | Williams et al. | Feb 2007 | A1 |
| 20070038999 | Millington | Feb 2007 | A1 |
| 20070043847 | Carter et al. | Feb 2007 | A1 |
| 20070048713 | Plastina et al. | Mar 2007 | A1 |
| 20070049256 | Wassingbo | Mar 2007 | A1 |
| 20070054680 | Mo et al. | Mar 2007 | A1 |
| 20070088747 | Cheng et al. | Apr 2007 | A1 |
| 20070136778 | Birger et al. | Jun 2007 | A1 |
| 20070142022 | Madonna et al. | Jun 2007 | A1 |
| 20070142944 | Goldberg et al. | Jun 2007 | A1 |
| 20070143493 | Mullig et al. | Jun 2007 | A1 |
| 20070156883 | Thompson et al. | Jul 2007 | A1 |
| 20070169115 | Ko et al. | Jul 2007 | A1 |
| 20070180137 | Rajapakse | Aug 2007 | A1 |
| 20070214182 | Rosenberg | Sep 2007 | A1 |
| 20070224937 | Jung et al. | Sep 2007 | A1 |
| 20070271232 | Mattox et al. | Nov 2007 | A1 |
| 20070271388 | Bowra et al. | Nov 2007 | A1 |
| 20070288470 | Kauniskangas et al. | Dec 2007 | A1 |
| 20070294131 | Roman et al. | Dec 2007 | A1 |
| 20070299778 | Haveson et al. | Dec 2007 | A1 |
| 20080005690 | Van Vugt | Jan 2008 | A1 |
| 20080016465 | Foxenland | Jan 2008 | A1 |
| 20080022320 | Ver Steeg | Jan 2008 | A1 |
| 20080052371 | Partovi et al. | Feb 2008 | A1 |
| 20080059510 | Cardamore et al. | Mar 2008 | A1 |
| 20080077261 | Baudino et al. | Mar 2008 | A1 |
| 20080086368 | Bauman et al. | Apr 2008 | A1 |
| 20080091771 | Allen et al. | Apr 2008 | A1 |
| 20080109529 | Story | May 2008 | A1 |
| 20080120429 | Millington et al. | May 2008 | A1 |
| 20080144861 | Melanson et al. | Jun 2008 | A1 |
| 20080152165 | Zacchi | Jun 2008 | A1 |
| 20080154959 | Dunko | Jun 2008 | A1 |
| 20080194276 | Lin et al. | Aug 2008 | A1 |
| 20080301280 | Chasen et al. | Dec 2008 | A1 |
| 20080319833 | Svendsen | Dec 2008 | A1 |
| 20090005893 | Sugii et al. | Jan 2009 | A1 |
| 20090031336 | Chavez et al. | Jan 2009 | A1 |
| 20090041423 | Weber et al. | Feb 2009 | A1 |
| 20090063414 | White et al. | Mar 2009 | A1 |
| 20090076881 | Svendsen | Mar 2009 | A1 |
| 20090076917 | Jablokov et al. | Mar 2009 | A1 |
| 20090083117 | Svendsen et al. | Mar 2009 | A1 |
| 20090133069 | Conness et al. | May 2009 | A1 |
| 20090150806 | Evje et al. | Jun 2009 | A1 |
| 20090157905 | Davis | Jun 2009 | A1 |
| 20090175429 | Cohen et al. | Jul 2009 | A1 |
| 20090179867 | Shim et al. | Jul 2009 | A1 |
| 20090216855 | Lang et al. | Aug 2009 | A1 |
| 20090222115 | Malcolm et al. | Sep 2009 | A1 |
| 20090228919 | Zott et al. | Sep 2009 | A1 |
| 20090249222 | Schmidt | Oct 2009 | A1 |
| 20090265426 | Svendsen et al. | Oct 2009 | A1 |
| 20090307062 | Lutnick et al. | Dec 2009 | A1 |
| 20090313369 | Wormington et al. | Dec 2009 | A1 |
| 20100010648 | Bull et al. | Jan 2010 | A1 |
| 20100017366 | Robertson et al. | Jan 2010 | A1 |
| 20100017714 | Agarwal et al. | Jan 2010 | A1 |
| 20100023578 | Brant et al. | Jan 2010 | A1 |
| 20100031366 | Knight et al. | Feb 2010 | A1 |
| 20100036950 | Bae et al. | Feb 2010 | A1 |
| 20100049835 | Ko et al. | Feb 2010 | A1 |
| 20100054275 | Noonan et al. | Mar 2010 | A1 |
| 20100082731 | Haughay et al. | Apr 2010 | A1 |
| 20100094834 | Svendsen et al. | Apr 2010 | A1 |
| 20100095332 | Gran et al. | Apr 2010 | A1 |
| 20100131567 | Dorogusker et al. | May 2010 | A1 |
| 20100162324 | Mehta et al. | Jun 2010 | A1 |
| 20100205222 | Gajdos et al. | Aug 2010 | A1 |
| 20100228740 | Cannistraro et al. | Sep 2010 | A1 |
| 20100235520 | Attanasio et al. | Sep 2010 | A1 |
| 20100262909 | Hsieh | Oct 2010 | A1 |
| 20100284389 | Ramsay | Nov 2010 | A1 |
| 20100299391 | Demarta et al. | Nov 2010 | A1 |
| 20100299639 | Ramsay et al. | Nov 2010 | A1 |
| 20100318917 | Holladay et al. | Dec 2010 | A1 |
| 20100325218 | Castro et al. | Dec 2010 | A1 |
| 20100332326 | Ishai | Dec 2010 | A1 |
| 20110004330 | Rothkopf | Jan 2011 | A1 |
| 20110041080 | Fleischman et al. | Feb 2011 | A1 |
| 20110066941 | Chipchase et al. | Mar 2011 | A1 |
| 20110066943 | Brillon et al. | Mar 2011 | A1 |
| 20110087842 | Lu et al. | Apr 2011 | A1 |
| 20110119706 | Scott et al. | May 2011 | A1 |
| 20110154173 | Herlein | Jun 2011 | A1 |
| 20110196888 | Hanson et al. | Aug 2011 | A1 |
| 20110202430 | Narayanan et al. | Aug 2011 | A1 |
| 20110202842 | Weatherly et al. | Aug 2011 | A1 |
| 20110211534 | Schmidt et al. | Sep 2011 | A1 |
| 20110225417 | Maharajh et al. | Sep 2011 | A1 |
| 20110238755 | Khan et al. | Sep 2011 | A1 |
| 20110246383 | Gibson et al. | Oct 2011 | A1 |
| 20110264732 | Robbin et al. | Oct 2011 | A1 |
| 20110314388 | Wheatley | Dec 2011 | A1 |
| 20120029671 | Millington et al. | Feb 2012 | A1 |
| 20120030366 | Collart et al. | Feb 2012 | A1 |
| 20120054278 | Taleb et al. | Mar 2012 | A1 |
| 20120059495 | Weiss et al. | Mar 2012 | A1 |
| 20120060046 | Millington | Mar 2012 | A1 |
| 20120071996 | Svendsen | Mar 2012 | A1 |
| 20120096526 | Brahmanapalli et al. | Apr 2012 | A1 |
| 20120117168 | Sugiyama et al. | May 2012 | A1 |
| 20120117185 | Cassidy | May 2012 | A1 |
| 20120117586 | Mccoy et al. | May 2012 | A1 |
| 20120124176 | Curtis et al. | May 2012 | A1 |
| 20120129446 | Ko et al. | May 2012 | A1 |
| 20120151320 | McClements, IV | Jun 2012 | A1 |
| 20120158531 | Dion et al. | Jun 2012 | A1 |
| 20120159393 | Sethi et al. | Jun 2012 | A1 |
| 20120206623 | Nakama | Aug 2012 | A1 |
| 20120210205 | Sherwood et al. | Aug 2012 | A1 |
| 20120221951 | Kidron | Aug 2012 | A1 |
| 20120233067 | Matthew et al. | Sep 2012 | A1 |
| 20120233639 | Zott et al. | Sep 2012 | A1 |
| 20120272156 | Kerger et al. | Oct 2012 | A1 |
| 20120284423 | Weel et al. | Nov 2012 | A1 |
| 20120311635 | Mushkatblat et al. | Dec 2012 | A1 |
| 20120315884 | Forutanpour et al. | Dec 2012 | A1 |
| 20120331386 | Hicken et al. | Dec 2012 | A1 |
| 20130007617 | Mackenzie et al. | Jan 2013 | A1 |
| 20130024880 | Moloney-Egnatios et al. | Jan 2013 | A1 |
| 20130031162 | Willis et al. | Jan 2013 | A1 |
| 20130061296 | Reddy et al. | Mar 2013 | A1 |
| 20130070093 | Rivera et al. | Mar 2013 | A1 |
| 20130073584 | Kuper et al. | Mar 2013 | A1 |
| 20130073979 | Shepherd et al. | Mar 2013 | A1 |
| 20130080599 | Ko et al. | Mar 2013 | A1 |
| 20130080955 | Reimann et al. | Mar 2013 | A1 |
| 20130081110 | McGowan | Mar 2013 | A1 |
| 20130128038 | Cok et al. | May 2013 | A1 |
| 20130129232 | Cok et al. | May 2013 | A1 |
| 20130130729 | Cok et al. | May 2013 | A1 |
| 20130159858 | Joffray et al. | Jun 2013 | A1 |
| 20130166649 | Atzmon et al. | Jun 2013 | A1 |
| 20130173531 | Rinearson et al. | Jul 2013 | A1 |
| 20130173794 | Agerbak et al. | Jul 2013 | A1 |
| 20130174204 | Coburn, IV et al. | Jul 2013 | A1 |
| 20130191454 | Oliver | Jul 2013 | A1 |
| 20130198633 | Hyman | Aug 2013 | A1 |
| 20130221951 | Anderson et al. | Aug 2013 | A1 |
| 20130246522 | Bilinski et al. | Sep 2013 | A1 |
| 20130297686 | Bilinski et al. | Nov 2013 | A1 |
| 20130310316 | Hellstrom et al. | Nov 2013 | A1 |
| 20130339397 | Herasymchuk | Dec 2013 | A1 |
| 20130339589 | Qawami et al. | Dec 2013 | A1 |
| 20130343567 | Triplett et al. | Dec 2013 | A1 |
| 20130346859 | Bates et al. | Dec 2013 | A1 |
| 20140025688 | Andler et al. | Jan 2014 | A1 |
| 20140047074 | Chung et al. | Feb 2014 | A1 |
| 20140052770 | Gran et al. | Feb 2014 | A1 |
| 20140059431 | Svendsen et al. | Feb 2014 | A1 |
| 20140067828 | Archibong et al. | Mar 2014 | A1 |
| 20140067998 | Garcia et al. | Mar 2014 | A1 |
| 20140075308 | Sanders et al. | Mar 2014 | A1 |
| 20140075316 | Li | Mar 2014 | A1 |
| 20140081796 | Cohen | Mar 2014 | A1 |
| 20140093219 | Trivedi | Apr 2014 | A1 |
| 20140108528 | Papakipos et al. | Apr 2014 | A1 |
| 20140115061 | Reddy et al. | Apr 2014 | A1 |
| 20140122590 | Svendsen | May 2014 | A1 |
| 20140146982 | Pelosi | May 2014 | A1 |
| 20140201632 | Kunigita et al. | Jul 2014 | A1 |
| 20140204076 | Kuper et al. | Jul 2014 | A1 |
| 20140208205 | Bartholomew | Jul 2014 | A1 |
| 20140223099 | Kidron | Aug 2014 | A1 |
| 20140237361 | Martin et al. | Aug 2014 | A1 |
| 20140244863 | Bradley et al. | Aug 2014 | A1 |
| 20140310058 | Aral et al. | Oct 2014 | A1 |
| 20140310779 | Lof et al. | Oct 2014 | A1 |
| 20140330951 | Sukoff et al. | Nov 2014 | A1 |
| 20140337959 | Garmark et al. | Nov 2014 | A1 |
| 20140341528 | Mahate et al. | Nov 2014 | A1 |
| 20140359680 | Shivadas et al. | Dec 2014 | A1 |
| 20150039620 | Ning | Feb 2015 | A1 |
| 20150046458 | Hu | Feb 2015 | A1 |
| 20150066892 | Astore | Mar 2015 | A1 |
| 20150067054 | Yoo et al. | Mar 2015 | A1 |
| 20150067871 | Commons et al. | Mar 2015 | A1 |
| 20150074534 | Didomenico et al. | Mar 2015 | A1 |
| 20150095680 | Gossain et al. | Apr 2015 | A1 |
| 20150113058 | Zhang et al. | Apr 2015 | A1 |
| 20150121220 | Lee et al. | Apr 2015 | A1 |
| 20150128162 | Ionescu et al. | May 2015 | A1 |
| 20150185599 | Mullins | Jul 2015 | A1 |
| 20150186110 | Kannan | Jul 2015 | A1 |
| 20150220498 | Munoz et al. | Aug 2015 | A1 |
| 20150286360 | Wachter | Oct 2015 | A1 |
| 20150331940 | Manning | Nov 2015 | A1 |
| 20160063011 | Wehbi et al. | Mar 2016 | A1 |
| 20160077710 | Lewis et al. | Mar 2016 | A1 |
| 20160082348 | Kehoe et al. | Mar 2016 | A1 |
| 20160147501 | Gilbert | May 2016 | A1 |
| 20160180248 | Regan | Jun 2016 | A1 |
| 20160253145 | Lee et al. | Sep 2016 | A1 |
| 20170093943 | Alsina et al. | Mar 2017 | A1 |
| 20170161119 | Boyle et al. | Jun 2017 | A1 |
| 20170169522 | Hyman et al. | Jun 2017 | A1 |
| 20170236512 | Williams et al. | Aug 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 1818901 | Aug 2006 | CN |
| 101410773 | Apr 2009 | CN |
| 101427316 | May 2009 | CN |
| 101714156 | May 2010 | CN |
| 101910992 | Dec 2010 | CN |
| 102450032 | May 2012 | CN |
| 102656898 | Sep 2012 | CN |
| 102947827 | Feb 2013 | CN |
| 104126309 | Oct 2014 | CN |
| 0251584 | Jan 1988 | EP |
| 0672985 | Sep 1995 | EP |
| 1111527 | Jun 2001 | EP |
| 1389853 | Feb 2004 | EP |
| 2004354721 | Dec 2004 | JP |
| 2007520808 | Jul 2007 | JP |
| 2009540638 | Nov 2009 | JP |
| 2010141748 | Jun 2010 | JP |
| 2011128957 | Jun 2011 | JP |
| 2011223124 | Nov 2011 | JP |
| 20010090215 | Oct 2001 | KR |
| 20050051785 | Jun 2005 | KR |
| 1020070040592 | Apr 2007 | KR |
| 20070048922 | May 2007 | KR |
| 100890993 | Mar 2009 | KR |
| 20100060498 | Jun 2010 | KR |
| 20100071724 | Jun 2010 | KR |
| 20100134164 | Dec 2010 | KR |
| 20110064635 | Jun 2011 | KR |
| 20130083012 | Jul 2013 | KR |
| 199525313 | Sep 1995 | WO |
| 199961985 | Dec 1999 | WO |
| 200147248 | Jun 2001 | WO |
| 200153994 | Jul 2001 | WO |
| 2002052540 | Jul 2002 | WO |
| 2003093950 | Nov 2003 | WO |
| 2005013047 | Feb 2005 | WO |
| 2005079071 | Aug 2005 | WO |
| 2007023120 | Mar 2007 | WO |
| 2010018429 | Feb 2010 | WO |
| 2011100264 | Nov 2011 | WO |
| 2011157891 | Dec 2011 | WO |
| 2012050927 | Apr 2012 | WO |
| 2012056326 | May 2012 | WO |
| 2012106269 | Aug 2012 | WO |
| 2012170205 | Dec 2012 | WO |
| 2013139239 | Sep 2013 | WO |
| 2014004181 | Jan 2014 | WO |
| 2014116693 | Jul 2014 | WO |
| 2014145746 | Sep 2014 | WO |
| Entry |
|---|
| Final Office Action dated Nov. 2, 2017, issued in connection with U.S. Appl. No. 14/275,112, filed May 12, 2014, 20 pages. |
| Final Office Action dated Oct. 2, 2019, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 47 pages. |
| Final Office Action dated Nov. 3, 2016, issued in connection with U.S. Appl. No. 14/495,684, filed Sep. 24, 2014, 16 pages. |
| Final Office Action dated Oct. 3, 2019, issued in connection with U.S. Appl. No. 16/174,703, filed Oct. 30, 2018, 17 pages. |
| Final Office Action dated Apr. 6, 2016, issued in connection with U.S. Appl. No. 14/173,253, filed Feb. 5, 2014, 20 pages. |
| Final Office Action dated Feb. 7, 2017, issued in connection with U.S. Appl. No. 14/455,651, filed Aug. 8, 2014, 22 pages. |
| Final Office Action dated Oct. 7, 2016, issued in connection with U.S. Appl. No. 14/495,595, filed Sep. 24, 2014, 16 pages. |
| Final Office Action dated Nov. 8, 2016, issued in connection with U.S. Appl. No. 14/495,659, filed Sep. 24, 2014, 14 pages. |
| Final Office Action dated Feb. 10, 2016, issued in connection with U.S. Appl. No. 14/197,403, filed Mar. 5, 2014, 21 pages. |
| Final Office Action dated Feb. 11, 2020, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 15 pages. |
| Final Office Action dated Feb. 16, 2017, issued in connection with U.S. Appl. No. 14/495,633, filed Sep. 24, 2014, 15 pages. |
| Final Office Action dated Sep. 16, 2016, issued in connection with U.S. Appl. No. 14/275,112, filed May 12, 2014, 19 pages. |
| Final Office Action dated Jan. 19, 2018, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 32 pages. |
| Final Office Action dated Jan. 2, 2019, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 14 pages. |
| Final Office Action dated Aug. 20, 2019, issued in connection with U.S. Appl. No. 15/607,267, filed May 26, 2017, 19 pages. |
| Final Office Action dated Oct. 20, 2016, issued in connection with U.S. Appl. No. 14/197,403, filed Mar. 5, 2016, 17 pages. |
| Final Office Action dated Mar. 28, 2018, issued in connection with U.S. Appl. No. 14/495,633, filed Sep. 24, 2014, 21 pages. |
| Final Office Action dated Oct. 29, 2018, issued in connection with U.S. Appl. No. 15/607,267, filed May 26, 2017, 17 pages. |
| Final Office Action dated Sep. 3, 2020, issued in connection with U.S. Appl. No. 15/664,634, filed Jul. 31, 2017, 24 pages. |
| Final Office Action dated Sep. 30, 2016, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 34 pages. |
| Final Office Action dated Dec. 31, 2020, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 26 pages. |
| Final Office Action dated Jul. 31, 2019, issued in connection with U.S. Appl. No. 15/664,634, filed Jul. 31, 2017, 16 pages. |
| Final Office Action dated May 31, 2017, issued in connection with U.S. Appl. No. 14/173,253, filed Feb. 5, 2014, 22 pages. |
| Final Office Action dated May 31, 2017, issued in connection with U.S. Appl. No. 14/821,513, filed Aug. 7, 2015, 16 pages. |
| Final Office Action dated Jul. 5, 2019, issued in connection with U.S. Appl. No. 14/495,633, filed Sep. 24, 2014, 16 pages. |
| Final Office Action dated Jul. 5, 2019, issued in connection with U.S. Appl. No. 15/966,337, filed Apr. 30, 2018, 16 pages. |
| Final Office Action dated Jun. 7, 2021, issued in connection with U.S. Appl. No. 16/866,159, filed May 4, 2020, 14 pages. |
| First Action Interview Office Action dated Apr. 4, 2016, issued in connection with U.S. Appl. No. 14/275,112, filed May 12, 2014, 8 pages. |
| First Action Interview Office Action dated Jul. 7, 2016, issued in connection with U.S. Appl. No. 14/495,595, filed Sep. 24, 2014, 6 pages. |
| First Action Interview Office Action dated Jul. 11, 2016, issued in connection with U.S. Appl. No. 14/495,684, filed Sep. 24, 2014, 8 pages. |
| First Action Interview Office Action dated Jul. 13, 2016, issued in connection with U.S. Appl. No. 14/455,651, filed Aug. 8, 2014, 10 pages. |
| First Action Interview Office Action dated Oct. 13, 2016, issued in connection with U.S. Appl. No. 14/495,633, filed Sep. 24, 2014, 8 pages. |
| First Action Interview Office Action dated Dec. 14, 2016, issued in connection with U.S. Appl. No. 14/821,513, filed Aug. 7, 2015, 10 pages. |
| First Action Interview Office Action dated Nov. 14, 2019, issued in connection with U.S. Appl. No. 16/188,186, filed Nov. 12, 2018, 14 pages. |
| First Action Interview Office Action dated Jan. 17, 2020, issued in connection with U.S. Appl. No. 16/188,186, filed Nov. 12, 2018, 14 pages. |
| First Action Interview Office Action dated Jul. 22, 2016, issued in connection with U.S. Appl. No. 14/495,659, filed Sep. 24, 2014, 8 pages. |
| First Action Interview Pilot Program Pre-Interview Communication dated Oct. 28, 2015, issued in connection ith U.S. Appl. No. 14/275,112, filed May 12, 2014, 4 pages. |
| First Action Interview Pilot Program Pre-Interview Communication dated Apr. 3, 2017, issued in connection with U.S. Appl. No. 14/495,590, filed Sep. 24, 2014, 5 pages. |
| Huang C.M., et al., “A Synchronization Infrastructure for Multicast Multimedia at the Presentation Layer,” IEEE Transactions on Consumer Electronics, 1997, pp. 370-380, vol. 43, No. 3. |
| International Bureau, International Preliminary Report on Patentability dated Jan. 30, 2014, issued in connection with International Application No. PCT/US2012/047620, filed on Jul. 20, 2012, 7 pages. |
| International Bureau, International Preliminary Report on Patentability dated Apr. 3, 2014, issued in connection with International Application No. PCT/US2012/056467, filed on Sep. 21, 2011, 11 pages. |
| International Bureau, International Preliminary Report on Patentability, dated Aug. 6, 2015, issued in connection with International Application No. PCT/US2014/012534, filed on Jan. 22, 2014, 6 pages. |
| International Bureau, International Preliminary Report on Patentability dated Dec. 15, 2016, issued in connection with International Application No. PCT/US2015/031934, filed on May 21, 2015, 11 pages. |
| International Bureau, International Preliminary Report on Patentability dated Aug. 18, 2016, issued in connection with International Application No. PCT/US2015/014156, filed on Feb. 3, 2015, 10 pages. |
| International Bureau,International Preliminary Reporton Patentability dated Sep. 15, 2016, issued in connection with International Application No. PCT/US2015/018850, filed on Mar. 5, 2015, 10 pages. |
| International Searching Authority, International Preliminary Report on Patentability dated Apr. 6, 2017, issued in connection with International Application No. PCT/US2015/051968 filed on Sep. 24, 2015, 10 pages. |
| International Searching Authority, International Preliminary Report on Patentability dated Apr. 6, 2017, issued in connection with International Application No. PCT/US2015/051975 filed on Sep. 24, 2015, 9 pages. |
| International Searching Authority, International Preliminary Report on Patentability dated Apr. 6, 2017, issued in connection with International Application No. PCT/US2015/051983 filed on Sep. 24, 2015, 7 pages. |
| International Searching Authority, International Preliminary Report on Patentability dated Apr. 6, 2017, issued in connection with International Application No. PCT/US2015/051989 filed on Sep. 24, 2015, 7 pages. |
| International Searching Authority, International Preliminary Report on Patentability dated Apr. 6, 2017, issued in connection with International Application No. PCT/US2015/051993 filed on Sep. 24, 2015, 8 pages. |
| International Searching Authority, International Preliminary Report on Patentability dated Feb. 23, 2017, issued in connection with International Application No. PCT/US2015/044218, filed on Aug. 7, 2015, 10 pages. |
| International Searching Authority, International Search Report and Written Opinion dated Nov. 6, 2015, issued in connection with International Application No. PCT/US2015/051993, filed on Sep. 24, 2015, 10 pages. |
| International Searching Authority, International Search Report and Written Opinion dated Dec. 7, 2015, issued in connection with International Application No. PCT/US2015/051968, filed on Sep. 24, 2015, 14 pages. |
| International Searching Authority, International Search Report and Written Opinion dated Dec. 16, 2015, issued in connection with International Application No. PCT/US2015/051989 filed on Sep. 24, 2015, 11 pages. |
| International Searching Authority, International Search Report and Written Opinion dated Dec. 21, 2015, issued in connection with International Application No. PCT/US2015/051983 filed on Sep. 24, 2015, 11 pages. |
| International Searching Authority, International Search Report and Written Opinion dated Nov. 23, 2015, issued in connection with International Application No. PCT/US2015/051975, filed on Sep. 24, 2015, 14 pages. |
| International Searching Authority, International Search Report and Written Opinion dated Apr. 24, 2015, issued in connection with International Application No. PCT/US2015/014156, filed on Feb. 3, 2015, 13 pages. |
| International Searching Authority, International Search Report and Written Opinion dated Aug. 27, 2015, issued in connection with International Application No. PCT/US2015/031934, filed on May 21, 2015, 14 pages. |
| International Searching Authority, International Search Report and Written Opinion dated Nov. 27, 2015, issued in connection with International Application No. PCT/US2015/044218, filed on Aug. 7, 2015, 13 pages. |
| International Searching Authority, International Search Report and Written Opinion dated May 29, 2015, issued in connection with International Application No. PCT/US2015/018850, filed on Mar. 5, 2015, 13 pages. |
| International Searching Authority, International Search Report dated May 8, 2014, issued in connection with International Application No. PCT/US2014/012534, filed on Jan. 24, 2014, 3 pages. |
| International Searching Authority International Search Report dated Dec. 27, 2012, issued in connection with International Application No. PCT/US2012/047620, filed on Jul. 20, 2011, 3 pages. |
| International Searching Authority, Written Opinion dated Dec. 27, 2012, issued in connection with International Application No. PCT/US2012/047620, filed on Jul. 20, 2011, 5 pages. |
| International Searhing Authority, International Search Report and Written Opinion dated Feb. 28, 2013 issued in connection with International Application No. PCT/US2012/056467, filed on Sep. 21, 2012, 12 pages. |
| Ishibashi et al., “A Group Synchronization Mechanism for Live Media in Multicast Communications,” IEEE Global Telecommunications Conference, 1997, pp. 746-752, vol. 2. |
| Ishibashi et al., “A Group Synchronization Mechanism for Stored Media in Multicast Communications,” IEEE Information Revolution and Communications, 1997, pp. 692-700, vol. 2. |
| Japanese Patent Office, Full English Translation of Office Action dated Nov. 28, 2017, issued in connection with Japanese Patent Application No. 2016-555529, 2 pages. |
| Japanese Patent Office, Notice of Rejection dated Nov. 8, 2016, issued in connection with Japanese Application No. 2015-555237, 6 pages. |
| Japanese Patent Office, Office Action dated Nov. 28, 2017 issued in connection with Japanese Paten Application No. 2016-555529, 5 pages. |
| Japanese Patent Office, Office Action dated Nov. 7, 2017 issued in connection with Japanese Patent Application No. 2016-550231, 5 pages. |
| Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861. |
| Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 http://www.reviewsonline.com/articles/961906864.htm retrieved Jun. 18, 2014, 2 pages. |
| Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages. |
| Mills David L., “Network Time Protocol (Version 3) Specification, Implementation and Analysis,” Network Working Group, Mar. 1992, 7 pages. |
| Mills, David L., “Precision Synchronization of Computer Network Clocks,” ACM SIGCOMM Computer Communication Review, 1994, pp. 28-43, vol. 24, No. 2. |
| Motorola, “Sirnplefi, Wireless Digital Audio Receiver, Installation and User Guide,” Dec. 31, 2001, 111 pages. |
| Nilsson, M., “ID3 Tag Version 2,” Mar. 26, 1998, 28 pages. |
| Non-Final Office Action dated Nov. 1, 2016, issued in connection with U.S. Appl. No. 14/173,253, filed Feb. 5, 2014, 21 pages. |
| Non-Final Office Action dated Oct. 1, 2015, issued in connection with U.S. Appl. No. 13/748,357, filed Jan. 23, 2013, 18 pages. |
| Non-Final Office Action dated Oct. 3, 2017, issued in connection with U.S. Appl. No. 14/495,633, filed Sep. 24, 2014, 18 pages. |
| Non-Final Office Action dated Apr. 6, 2016, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 26 pages. |
| Non-Final Office Action dated May 6, 2015, issued in connection with U.S. Appl. No. 13/748,357, filed Jan. 23, 2013, 17 pages. |
| Non-Final Office Action dated Jul. 10, 2017, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 33 pages. |
| Non-Final Office Action dated Sep. 10, 2015, issued in connection with U.S. Appl. No. 14/197,403, filed Mar. 5, 2014, 16 pages. |
| Non-Final Office Action dated Jan. 12, 2017, issued in connection with U.S. Appl. No. 14/275,112, filed May 12, 2014, 25 pages. |
| Non-Final Office Action dated Jan. 12, 2021, issued in connection with U.S. Appl. No. 16/952,217, filed Nov. 19, 2020, 8 pages. |
| Non-Final Office Action dated May 12, 2020, issued in connection with U.S. Appl. No. 16/516,767, filed Jul. 19, 2019, 12 pages. |
| Non-Final Office Action dated Mar. 13, 2020, issued in connection with U.S. Appl. No. 15/664,634, filed Jul. 31, 02017, 20 pages. |
| Non-Final Office Action dated Nov. 13, 2018, issued in connection with U.S. Appl. No. 16/143,301, filed Sep. 26, 2018, 27 pages. |
| Non-Final Office Action dated Jan. 14, 2020, issued in connection with U.S. Appl. No. 15/966,337, filed Apr. 30, 2018, 16 pages. |
| Non-Final Office Action dated Jun. 14, 2017, issued in connection with U.S. Appl. No. 14/495,659, filed Sep. 24, 2014, 15 pages. |
| Non-Final Office Action dated Feb. 16, 2021, issued in connection with U.S. Appl. No. 16/866,159, filed May 4, 2020, 10 pages. |
| Non-Final Office Action dated Jan. 16, 2019, issued in connection with U.S. Appl. No. 15/664,634, filed Jul. 31, 2017, 17 pages. |
| Non-Final Office Action dated Dec. 17, 2015, issued in connection with U.S. Appl. No. 14/173,253, filed Feb. 5, 2014, 18 pages. |
| Non-Final Office Action dated Jun. 17, 2016, issued in connection with U.S. Appl. No. 14/495,706, filed Sep. 24, 2014, 19 pages. |
| Non-Final Office Action dated May 18, 2016, issued in connection with U.S. Appl. No. 14/197,403, filed Mar. 5, 2014, 21 pages. |
| Non-Final Office Action dated Feb. 19, 2019, issued in connection with U.S. Appl. No. 15/966,337, filed Apr. 30, 2018, 14 pages. |
| Non-Final Office Action dated Mar. 19, 2019, issued in connection with U.S. Appl. No. 15/607,267, filed May 26, 2017, 18 pages. |
| Non-Final Office Action dated Jun. 21, 2018, issued in connection with U.S. Appl. No. 15/692,090, filed Aug. 31, 2017, 20 pages. |
| Non-Final Office Action dated Jan. 22, 2019, issued in connection with U.S. Appl. No. 16/174,703, filed Oct. 30, 2018, 15 pages. |
| Presentations at WinHEC 2000, May 2000, 138 pages. |
| PRISMIQ, Inc., “PRISMIQ Media Player User Guide,” 2003, 44 pages. |
| Rothermel et al., “An Adaptive Stream Synchronization Protocol,” 5th International Workshop on Network and Operating System Support for Digital Audio and Video, 1995, 13 pages. |
| Schulzrinne H., et al., “RTP: A Transport Protocol for Real-Time Applications, RFC 3550,” Network Working Group, 2003, pp. 1-89. |
| United States Patent and Trademark Office, U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages. |
| United States Patent and Trademark Office, U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages. |
| UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54. |
| U.S. Appl. No. 12/070,933, filed Feb. 22, 2008. “System, Method, and Computer Program for Remotely Managing a Digital Device” Inventor: Jonathan Lang, et al. |
| U.S. Appl. No. 13/533,105, filed Jun. 26, 2012. “Systems, Methods, Apparatus, and Articles of Manufacture to Provide a Crowd-Sourced Playlist with Guess Access” Inventor: Paul Bates, et al. |
| U.S. Appl. No. 13/533,785, filed Jun. 26, 2012. “Networked Music Playback Including Remote Discovery and Odd to Queue” Inventor: Mark Triplett, et al. |
| U.S. Appl. No. 13/748,357, filed Jan. 23, 2013. “System and Method for a Media Experience Social nterface” Inventor: Ron Kuper, et al. |
| U.S. Appl. No. 13/871,785, filed Apr. 26, 2013. “Systems, Methods, Apparatus, and Articles of Manufacture to Provide Guest Access” Inventor: Paul Bates, et al. |
| U.S. Appl. No. 13/871,795, filed Jun. 20, 2013. “Systems, Methods, Apparatus, and Articles of Manufacture to Provide Guest Access” Inventor: Paul Bates, et al. |
| U.S. Appl. No. 14/173,253, filed Feb. 5, 2014. “Remote Creation of a Playback Queue for a Future Event” Inventor: Jaime Munoz, et al. |
| Van Buskirk, Eliot, “Music Needs ‘Connective Tissue’ and Facebook Wants to Build It,” E http://evolver.fm/2011/0901/music-needs-connective-tissue-and-facbook-wants-to-build-it, 2011, 6 pages. |
| Yamaha DME 32 manual: copyright 2001. |
| Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages. |
| Yamaha DME Designer 3.0 Owner's Manual; Copyright 2008, 501 pages. |
| Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages. |
| Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages. |
| Advisory Action dated Feb. 1, 2017, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 6 pages. |
| Advisory Action dated Feb. 3, 2017, issued in connection with U.S. Appl. No. 14/495,659, filed Sep. 24, 2014, 5 pages. |
| Advisory Action dated Sep. 11, 2019, issued in connection with U.S. Appl. No. 14/495,633, filed Sep. 24, 2014, 3 pages. |
| Advisory Action dated Jul. 12, 2016, issued in connection with U.S. Appl. No. 14/173,253, filed Feb. 5, 2014, 5 pages. |
| Advisory Action dated Mar. 19, 2019, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 3 pages. |
| Advisory Action dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/664,634, filed Jul. 31, 2017, 4 pages. |
| Advisory Action dated Aug. 22, 2017, issued in connection with U.S. Appl. No. 14/173,253, filed Feb. 5, 2014, 4 pages. |
| Advisory Action dated Nov. 25, 2019, issued in connection with U.S. Appl. No. 15/607,267, filed May 26, 2017, 5 pages. |
| Advisory Action dated Oct. 25, 2019, issued in connection with U.S. Appl. No. 15/966,337, filed Apr. 30, 2018, 4 pages. |
| Advisory Action dated May 29, 2020, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 2 pages. |
| Advisory Action dated Mar. 8, 2021, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 3 pages. |
| Akyildiz et al., “Multimedia Group Synchronization Protocols for Integrated Services Networks,” IEEE Journal on Selected Areas in Communications, 1996 pp. 162-173, vol. 14, No. 1. |
| Anonymous: “Email Parser Tool—customizable email parsing software by ITG,” May 17, 2014, [online] Retrieved from the Internet on Nov. 5, 2019: (URL:https//web.archive.org/web/20140517050139://emailparser.net/). |
| AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages. |
| AudioTron Reference Manual, Version 3.0, May 2002, 70 pages. |
| AudioTron Setup Guide, Version 3.0, May 2002, 38 pages. |
| Benslimane Abderrahim, “A Multimedia Synchronization Protocol for Multicast Groups,” Proceedings of the 26th Euromicro Conference, 2000, pp. 456-463, vol. 1. |
| Biersack et al., “Intra- and Inter-Stream Synchronization for Stored Multimedia Streams,” IEEE International Conference on Multimedia Computing and Systems, 1996, pp. 372-381. |
| Bluetooth. “Specification of the Bluetooth System: The ad hoc SCATTERNET for affordable and highly functional vireless connectivity,” Core, Version 1.0 A, Jul. 26, 1999, 1068 pages. |
| Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 pages. |
| Bretl W.E., et al., MPEG2 Tutorial [online], 2000 [retrieved on Jan. 13, 2009] Retrieved from the Internet:(http://wwwbretl.com/mpeghtml/MPEGindex.htm), pp. 1-23. |
| Chinese Patent Office, First Office Action and Translation dated Feb. 2, 2019, issued in connection with Chinese Application No. 201580011640.5, 12 pages. |
| Chinese Patent Office, First Office Action and Translation dated Aug. 26, 2020, issued in connection with Chinese Application No. 201910608857.4, 17 pages. |
| Chinese Patent Office, First Office Action dated Feb. 27, 2019, issued in connection with Chinese Application No. 201580007534.X, 9 pages. |
| Chinese Patent Office, First Office Action dated Sep. 4, 2017, issued in connection with Chinese Application No. 2014800172148.0, 16 pages. |
| Chinese Patent Office, Second Office Action dated Apr. 11, 2018, issued in connection with Chinese Application No. 201480017214.8, 7 pages. |
| Chinese Patent Office, Third Office Action dated Oct. 18, 2018, issued in connection with Chinese Application No. 2014800172148, 8 pages. |
| Corrected Notice of Allowability dated Jan. 19, 2017, issued in connection with U.S. Appl. No. 14/197,403, filed Mar. 5, 2014, 2 pages. |
| Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages. |
| Dell, Inc. “Start Here,” Jun. 2000, 2 pages. |
| “Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages. |
| European Patent Office, Decision to Refuse EP Application dated Oct. 16, 2018, issued in connection with European Application No. 157758970, 48 pages. |
| European Patent Office, Decision to Refuse EP Application dated Sep. 27, 2018, issued in connection with European Appl. No. 15781794.1, 54 pages. |
| European Patent Office, EP Supplemental Search dated Dec. 19, 2017, issued in connection with EP Application No. 15829058.5, 12 pages. |
| European Patent Office, European Extended Search Report dated Feb. 5, 2018, issued in connection with EP Application No. 15803430.6, 8 pages. |
| European Patent Office, European Office Action dated Nov. 13, 2019, issued in connection with European Application No. 15829058.5, 8 pages. |
| European Patent Office, European Office Action dated Jan. 2, 2019, issued in connection with European Application No. 15829058.5, 4 pages. |
| European Patent Office, European Office Action dated Aug. 3, 2017, issued in connection with EP Application No. 15781794.1, 6 pages. |
| European Patent Office, European Supplemental Search Report dated Sep. 18, 2017, issued in connection with EP Application No. 15829058.5, 13 pages. |
| European Patent Office, European Supplemental Search Report dated Jan. 27, 2016, issued in sonnection with European Application No. 14743335.3, 8 pages. |
| European Patent Office, Examination Report dated Feb. 3, 2017, issued in connection with European Application No. 14743335.3, 5 pages. |
| European Patent Office, Extended European Search Report dated Mar. 15, 2017, issued in connection with European Application No. 15758460.8, 9 pages. |
| European Patent Office, Extended European Search Report dated Dec. 23, 2016, issued in connection with European Application No. 15746781.2, 10 pages. |
| European Patent Office, Office Action dated Mar. 2, 2017, issued in connection with European Application No. 15775566.1, 7 pages. |
| European Patent Office, Office Action dated Apr. 4, 2017, issued in connection with European Application No. 15775897.0, 6 pages. |
| European Patent Office, Office Action dated Jan. 13, 2017, issued in connection with European Application No. 15781794.1, 8 pages. |
| European Patent Office, Office Action dated Mar. 13, 2017, issued in connection with European Application No. 15781200.9, 5 pages. |
| European Patent Office, Summons to Attend Oral Proceedings mailed on Jun. 11, 2019, issued in connection with European Application No. 14743335.3, 10 pages. |
| European Patent Office, Summons to Attend Oral Proceedings mailed on Nov. 20, 2020, issued in connection with European Application No. 15829058.5, 7 pages. |
| European Patent Office, Summons to Attend Oral Proceedings mailed on Mar. 27, 2018, issued in connection with European Patent Application No. 15781794.1, 11 pages. |
| Non-Final Office Action dated Mar. 23, 2018, issued in connection with U.S. Appl. No. 15/227,074, filed Aug. 3, 2016, 11 pages. |
| Non-Final Office Action dated Jan. 24, 2018, issued in connection with U.S. Appl. No. 15/607,267, filed May 26, 2017, 17 pages. |
| Non-Final Office Action dated Dec. 27, 2018, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 37 pages. |
| Non-Final Office Action dated Apr. 28, 2020, issued in connection with U.S. Appl. No. 14/297193, filed Jun. 5, 2014, 34 pages. |
| Non-Final Office Action dated Nov. 28, 2017, issued in connection with U.S. Appl. No. 14/821,513, filed Aug. 7, 2015, 17 pages. |
| Non-Final Office Action dated Sep. 30, 2020, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 18 pages. |
| Non-Final Office Action dated Jul. 31, 2019, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 14 pages. |
| Non-Final Office Action dated Apr. 4, 2019, issued in connection with U.S. Appl. No. 15/612,126, filed Jun. 2, 2017, 9 pages. |
| Non-Final Office Action dated Aug. 4, 2020, issued in connection with U.S. Appl. No. 16/812,638, filed Mar. 9, 2020, 13 pages. |
| Non-Final Office Action dated Dec. 6, 2018, issued in connection with U.S. Appl. No. 14/495,633, filed Sep. 24, 2014, 15 pages. |
| Non-Final Office Action dated May 7, 2021, issued in connection with U.S. Appl. No. 15/664,634, filed Jul. 31, 2017, 22 pages. |
| North American MPEG-2 Information, “The MPEG-2 Transport Stream,” Retrieved from the Internet: URL: http://www.coolstf.com/mpeg/#ts, 2006, pp. 1-5. |
| Notice of Allowance dated Jul. 9, 2021, issued in connection with U.S. Appl. No. 16/952,217, filed Nov. 19, 2020, 8 pages. |
| Notice of Allowance dated May 4, 2016, issued in connection with U.S. Appl. No. 13/748,357, filed Jan. 23, 2013, 11 pages. |
| Notice of Allowance dated Apr. 6, 2017, issued in connection with U.S. Appl. No. 14/197,403, filed Mar. 5, 2014, 5 pages. |
| Notice of Allowance dated Apr. 10, 2020, issued in connection with U.S. Appl. No. 16/188,186, filed Nov. 12, 2018, 10 pages. |
| Notice of Allowance dated Feb. 11, 2019, issued in connection with U.S. Appl. No. 15/692,090, filed Aug. 31, 2017, 8 pages. |
| Nlotice of Allowance dated Feb. 11, 2019, issued in connection with U.S. Appl. No. 16/143,301, filed Sep. 26, 2018, 15 pages. |
| Notice of Allowance dated Jan. 12, 2017, issued in connection with U.S. Appl. No. 14/495,595, filed Sep. 24, 2014, 5 pages. |
| Notice of Allowance dated Dec. 17, 2019, issued in connection with U.S. Appl. No. 16/174,703, filed Oct. 30, 2018, 11 pages. |
| Notice of Allowance dated Jan. 17, 2020, issued in connection with U.S. Appl. No. 15/612,126, filed Jun. 2, 2017, 5 pages. |
| Notice of Allowance dated Jul. 18, 2018, issued in connection with U.S. Appl. No. 15/227,074, filed Aug. 3, 2016, 8 pages. |
| Notice of Allowance dated Sep. 19, 2017, issued in connection with U.S. Appl. No. 14/455,651, filed Aug. 8, 2014, 12 pages. |
| Notice of Allowance dated Aug. 20, 2020, issued in connection with U.S. Appl. No. 15/607,267, filed May 26, 2017, 8 pages. |
| Notice of Allowance dated Jul. 21, 2020, issued in connection with U.S. Appl. No. 15/966,337, filed Apr. 30, 2018, 11 pages. |
| Notice of Allowance dated Aug. 24, 2017, issued in connection with U.S. Appl. No. 14/495,590, filed Sep. 24, 2014, 10 pages. |
| Notice of Allowance dated Aug. 24, 2020, issued in connection with U.S. Appl. No. 16/516,767, filed Jul. 19, 2019, 9 pages. |
| Notice of Allowance dated Jan. 26, 2017, issued in connection with U.S. Appl. No. 14/495,706, filed Sep. 24, 2014, 8 pages. |
| Notice of Allowance dated Dec. 27, 2017, issued in connection with U.S. Appl. No. 14/495,659, filed Sep. 24, 2014, 6 pages. |
| Notice of Allowance dated Dec. 27, 2019, issued in connection with U.S. Appl. No. 14/495,633, filed Sep. 24, 2014, 7 pages. |
| Notice of Allowance dated Apr. 28, 2020, issued in connection with U.S. Appl. No. 15/612,126, filed Jun. 2, 2017, 5 pages. |
| Notice of Allowance dated Dec. 29, 2016, issued in connection with U.S. Appl. No. 14/197,403, filed Mar. 5, 2014, 5 pages. |
| Notice of Allowance dated Aug. 30, 2018, issued in connection with U.S. Appl. No. 14/821,513, filed Aug. 7, 2015, 10 pages. |
| Notice of Allowance dated Oct. 30, 2019, issued in connection with U.S. Appl. No. 16/458,453, filed Jul. 1, 2019, 7 pages. |
| Notice of Allowance dated May 31, 2017, issued in connection with U.S. Appl. No. 14/495,684, filed Sep. 24, 2014, 5 pages. |
| Notice of Allowance dated Feb. 4, 2021, issued in connection with U.S. Appl. No. 16/812, 638, filed Mar. 9, 2020, 7 pages. |
| Notice of Allowance dated May 4, 2017, issued in connection with U.S. Appl. No. 14/495,595, filed Sep. 24, 2014, 5 pages. |
| Notice of Allowance dated Aug. 5, 2019, issued in connection with U.S. Appl. No. 15/612,126, filed Jun. 2, 2017, 5 pages. |
| Notice of Allowance dated Aug. 5, 2020, issued in connection with U.S. Appl. No. 16/188,186, filed Nov. 12, 2018, 11 pages. |
| Notice of Allowance dated May 5, 2021, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 7 pages. |
| Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages. |
| Park et al., “Group Synchronization in MultiCast Media Communications,” Proceedings of the 5th Research on Multicast Technology Workshop, 2003, 5 pages. |
| Polycom Conference Composer User Guide, copyright 2001, 29 pages. |
| Pre-Brief Conference Decision dated Sep. 7, 2018, issued in connection with U.S. Appl. No. 14/297,193, filed Jun. 5, 2014, 2 pages. |
| Preinterview First Office Action dated May 4, 2016, issued in connection with U.S. Appl. No. 14/455,651, filed Aug. 8, 2014, 7 pages. |
| Preinterview First Office Action dated May 4, 2016, issued in connection with U.S. Appl. No. 14/495,659, filed Sep. 24, 2014, 6 pages. |
| Preinterview First Office Action dated May 5, 2016, issued in connection with U.S. Appl. No. 14/495,595, filed Sep. 24, 2014, 6 pages. |
| Preinterview First Office Action dated May 16, 2016, issued in connection with U.S. Appl. No. 14/495,633, filed Sep. 24, 2014, 6 pages. |
| Preinterview First Office Action dated Oct. 19, 2016, issued in connection with U.S. Appl. No. 14/821,513, filed Aug. 7, 2016, 5 pages. |
| Preinterview First Office Action dated May 23, 2016, issued in connection with U.S. Appl. No. 14/495,684, filed Sep. 24, 2014, 6 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210279404 A1 | Sep 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16516767 | Jul 2019 | US |
| Child | 17129060 | US | |
| Parent | 15692090 | Aug 2017 | US |
| Child | 16516767 | US | |
| Parent | 14173253 | Feb 2014 | US |
| Child | 15692090 | US |
