Queue identification

US9904730B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9904730-B2
Application numberUS-201615244219-A
CountryUS
Kind codeB2
Filing dateAug 23, 2016
Priority dateJul 14, 2014
Publication dateFeb 27, 2018
Grant dateFeb 27, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Example techniques relate to a playback device that facilitates queue identification. In an example implementation, a playback device stores an association between a playback queue and a first application identifier. After storing the association between the playback queue and the first application identifier, the playback device receives, from a first computing device, a first message comprising a second application identifier. The playback device determines that the second application identifier corresponds to the first application identifier, and responsive to determining that the second application identifier corresponds to the first application identifier, transmits, to the first computing device, a queue identifier associated with the playback queue.

First claim

Opening claim text (preview).

I claim: 1. A method comprising: storing, via a playback device, an association between a playback queue and a first application identifier, wherein the playback queue comprises one or more media items; after storing the association between the playback queue and the first application identifier, receiving, via the playback device from a first computing device, a first message comprising a second application identifier; determining, via the playback device, that the second application identifier corresponds to the first application identifier; and responsive to determining that the second application identifier corresponds to the first application identifier, transmitting, via the playback device to the first computing device, a queue identifier associated with the playback queue. 2. The method of claim 1 , further comprising: receiving, via the playback device from the first computing device, a second message comprising (i) a command to alter the playback queue and (ii) a second queue identifier. 3. The method of claim 2 , wherein the command to alter the playback queue comprises: a command to add one or more additional media items to the playback queue. 4. The method of claim 3 , wherein the command to add the one or more additional media items to the playback queue comprises: a command to add one or more identifiers associated with the one or more additional media items to the playback queue. 5. The method of claim 2 , further comprising: determining that the second queue identifier matches the queue identifier associated with the playback queue; and responsive to determining that the second queue identifier matches the queue identifier associated with the playback queue, altering the playback queue according to the command. 6. The method of claim 2 , further comprising: determining that the second queue identifier does not match the queue identifier associated with the playback queue; and transmitting, to the first computing device, an indication that the second queue identifier does not match the queue identifier associated with the playback queue. 7. The method of claim 1 , wherein receiving, via the playback device from the first computing device, the first message comprising the second application identifier comprises: after storing the association between the playback queue and the first application identifier, receiving, via the playback device from the first computing device over a local area network (LAN), the first message comprising the second application identifier. 8. The method of claim 1 , wherein storing the association between the playback queue and the first application identifier comprises: storing, in a memory of the playback device, the association between the playback queue and the first application identifier. 9. A tangible, non-transitory computer-readable medium storing instructions that when executed by a processor cause a playback device to perform functions comprising: storing an association between a playback queue and a first application identifier, wherein the playback queue comprises one or more media items; after storing the association between the playback queue and the first application identifier, receiving, from a first computing device, a first message comprising a second application identifier; determining that the second application identifier corresponds to the first application identifier; and responsive to determining that the second application identifier corresponds to the first application identifier, transmitting, to the first computing device, a queue identifier associated with the playback queue. 10. The tangible, non-transitory computer-readable medium of claim 9 , wherein the functions further comprise: receiving, from the first computing device, a second message comprising (i) a command to alter the playback queue and (ii) a second queue identifier. 11. The tangible, non-transitory computer-readable medium of claim 10 , wherein the command to alter the playback queue comprises: a command to add one or more identifiers associated with one or more additional media items to the playback queue. 12. The tangible, non-transitory computer-readable medium of claim 10 , wherein the functions further comprise: determining that the second queue identifier matches the queue identifier associated with the playback queue; and based on the determining, altering the playback queue according to the command. 13. The tangible, non-transitory computer-readable medium of claim 10 , wherein the functions further comprise: determining that the second queue identifier does not match the queue identifier associated with the playback queue; and transmitting, to the first computing device, an indication that the second queue identifier does not match the queue identifier associated with the playback queue. 14. The tangible, non-transitory computer-readable medium of claim 9 , wherein receiving the first message comprising the second application identifier comprises: after storing the association between the playback queue and the first application identifier, receiving, from the first computing device over a local area network (LAN), the first message comprising the second application identifier. 15. The tangible, non-transitory computer-readable medium of claim 9 , wherein storing the association between the playback queue and the first application identifier comprises: storing, in a memory of the playback device, the association between the playback queue and the first application identifier. 16. A playback device, comprising: a processor; and memory storing instructions that when executed by the processor cause the playback device to perform functions comprising: storing an association between a playback queue and a first application identifier, wherein the playback queue comprises one or more media items; after storing the association between the playback queue and the first application identifier, receiving, from a first computing device, a first message comprising a second application identifier; determining that the second application identifier corresponds to the first application identifier; and responsive to determining that the second application identifier corresponds to the first application identifier, transmitting, to the first computing device, a queue identifier associated with the playback queue. 17. The playback device of claim 16 , wherein the functions further comprise: receiving, from the first computing device, a second message comprising (i) a command to alter the playback queue and (ii) a second queue identifier. 18. The playback device of claim 17 , wherein the functions further comprise: determining that the second queue identifier matches the queue identifier associated with the playback queue; and based on the determining, altering the playback queue according to the command. 19. The playback device of claim 16 , wherein storing the association between the playback queue and the first application identifier comprises: storing, in a memory of the playback device, the association between the playback queue and the first application identifier. 20. The playback device of claim 16 , wherein receiving the first message comprising the second application identifier comprises: after storing the association between the playback queue and the first application identifier, receiving, from the first computing device over a local area network (LAN), the first message comprising the second application identifier.

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9904730B2 cover?
Example techniques relate to a playback device that facilitates queue identification. In an example implementation, a playback device stores an association between a playback queue and a first application identifier. After storing the association between the playback queue and the first application identifier, the playback device receives, from a first computing device, a first message comprisi…
Who is the assignee on this patent?
Sonos Inc
What technology area does this patent fall under?
Primary CPC classification G11B27/105. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 27 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).