Driver jukebox system

US10346471B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10346471-B2
Application numberUS-201615174802-A
CountryUS
Kind codeB2
Filing dateJun 6, 2016
Priority dateMar 26, 2014
Publication dateJul 9, 2019
Grant dateJul 9, 2019

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.

A system for a driver jukebox on a driver device includes a music server system interface, a ride server system, a playlist determiner, a ride started determiner, and a music player. The music server system interface is for providing a driver credential to a music server system. The ride server system interface is for receiving a rider music preference from a rider device. The playlist determiner is for determining a playlist based at least in part on the rider music preference. The ride started determiner is for determining that a ride for the rider has started. The music server system interface for indicating to play the playlist.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer-implemented method, comprising: receiving, from a first computing device, a ride request including at least one of a pickup location or a destination location associated with a user of the first computing device; receiving an indication from a second computing device that the ride request has been accepted; determining that a ride corresponding to the ride request has been initiated based on: receiving sensor data associated with the first computing device and sensor data associated with the second computing device to determine a location of the first computing device and a location of the second computing device; and determining, based on the received sensor data, that the first computing device and the second computing device are moving together; based on a response to the ride request being accepted and on determining that the ride corresponding to the ride request has been initiated, sending to the first computing device, first audio information corresponding to available audio data; receiving, from the first computing device, control data comprising an audio control command corresponding to an action to be taken with respect to the available audio data, wherein the available audio data is being streamed from a third-party audio service; and sending the control data to the second computing device, wherein the control data operates to cause the second computing device to send the audio control command to the third-party audio service. 2. The computer-implemented method of claim 1 , wherein determining that the ride corresponding to the ride request has been initiated further comprises receiving, from the second computing device, an indication that the ride corresponding to the ride request has been initiated based on a user interaction with a driver interface on the second computing device. 3. The computer-implemented method of claim 1 , further comprising: providing, to the third-party audio service, an access credential for the third-party audio service, the access credential being associated with a user of the second computing device, wherein at least a portion of the available audio data corresponds to audio accessible from the third-party audio service. 4. The computer-implemented method of claim 3 , wherein the user of the first computing device does not have an access credential for the third-party audio service. 5. The computer-implemented method of claim 3 , further comprising: receiving, from the first computing device, an indication that the user of the first computing device has an access credential for the third-party audio service; sending, to the first computing device, a request for second audio information corresponding to second available audio data, wherein the second available audio data is associated with the user of the first computing device; and determining at least one audio data selection common to the first audio information and the second audio information. 6. The computer-implemented method of claim 1 , wherein the first audio information comprises at least one of an audio type preference, an artist preference, a song preference, a genre preference, a playlist preference, or a subject preference. 7. The computer-implemented method of claim 1 , wherein the first audio information comprises an ordered playlist generated on the first computing device, and wherein the ordered playlist includes a plurality of audio data selections of the available audio data. 8. The computer-implemented method of claim 1 , further comprising automatically generating an indication to play at least one audio data selection upon determining that a ride corresponding to the ride request has been initiated. 9. The computer-implemented method of claim 1 , further comprising providing, to the second computing device, an indication to pre-buffer at least one audio data selection to the second computing device prior to the ride corresponding to the ride request being initiated. 10. The computer-implemented method of claim 1 further comprising: determining that the ride has concluded; and generating a ride receipt corresponding to the ride, wherein the ride receipt comprises information corresponding to one or more audio data selections played during the ride. 11. The computer-implemented method of claim 1 , wherein the available audio data comprises one or more of a song, a podcast, a radio station, live event audio, an audiobook, a playlist, or an audio track of an audio-visual work. 12. The computer-implemented method of claim 1 , wherein the first audio information comprises a subset of the available audio data. 13. The computer-implemented method of claim 12 , wherein the subset of the available audio data is ordered according to at least one criteria. 14. The computer-implemented method of claim 12 , wherein the first audio information is based at least upon location data. 15. A system, comprising: at least one processor; and at least one non-transitory memory device comprising instructions that, when executed by the at least one processor, cause a computer system to: receive, from a first computing device, a ride request including at least one of a pickup location or a destination location associated with a user of the first computing device; receive an indication from a second computing device that the ride request has been accepted; determine that a ride corresponding to the ride request has been initiated based on: receiving sensor data associated with the first computing device and sensor data associated with the second computing device to determine a location of the first computing device and a location of the second computing device; determining, based on the received sensor data, that the first computing device and the second computing device are moving together; and based on a response to the ride request being accepted and on determining that the ride corresponding to the ride request has been initiated, send to the first computing device, first audio information corresponding to available audio data; receive, from the first computing device, control data comprising an audio control command corresponding to an action to be taken with respect to the available audio data, wherein the available audio data is being streamed from a third-party audio service; and send the control data to the second computing device, wherein the control data operates to cause the second computing device to send the audio control command to the third-party audio service. 16. The system of claim 15 , further comprising instructions, that when executed by the at least one processor, cause the computer system to: provide, to the third-party audio service, an access credential for the third-party audio service, the access credential being associated with a user of the second computing device, wherein at least a portion of the available audio data corresponds to audio accessible from the third-party audio service. 17. The system of claim 15 , further comprising instructions that, when executed by the at least one processor, cause the computer system to provide, to the second computing device, an indication to pre-buffer at least one audio data selection to the second computing device prior to the ride corresponding to the ride request being initiated. 18. A non-transitory computer readable medium comprising instructions that, when executed by at least one processor, cause a computing device to: receive, from a first computing device, a ride request including at least one of a pickup location or a destin

Assignees

Inventors

Classifications

  • Filtering based on additional data, e.g. user or group profiles · CPC title

  • G06F16/639Primary

    using playlists · CPC title

  • H04W4/027Primary

    using movement velocity, acceleration information · CPC title

  • Management of the audio stream, e.g. setting of volume, audio stream path · CPC title

  • Transfer of user or subscriber data · CPC title

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 US10346471B2 cover?
A system for a driver jukebox on a driver device includes a music server system interface, a ride server system, a playlist determiner, a ride started determiner, and a music player. The music server system interface is for providing a driver credential to a music server system. The ride server system interface is for receiving a rider music preference from a rider device. The playlist determin…
Who is the assignee on this patent?
Lyft Inc
What technology area does this patent fall under?
Primary CPC classification G06F16/639. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jul 09 2019 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 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).