IP Library Granted Patent US 9,554,248
Granted Patent B2
US 9,554,248 · App. 12/485,082 · Granted Jan 24, 2017

Music diary processor

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,554,248
App. No.
12/485,082
Granted
Jan 24, 2017
Kind
B2
Abstract

A music diary processor for generating an electronic music diary. The music diary processor receives a plurality of event identifiers from a user, wherein each event identifier identifies a respective life event associated with the user. The user can also provide a date identifier identifying a date associated with the life event, a song identifier identifying one or more songs identified by the user as being associated with the live event. The event identifiers, song identifiers and the date identifiers are stored in an electronic storage medium wherein each song identifier and date identifier is coupled with at least one respective event identifier, and a plurality of event identifiers are coupled with each other. The music diary processor can serve as a music discovery vehicle, wherein the music diary processor can use data entered by a user to locate songs and other data associated with other music diaries.

Claims (50)

1. A method for a music diary processor to generate a first electronic music diary comprising:

receiving a first plurality of event identifiers from a user device, wherein each event identifier identifies a respective life event associated with a life of a first user;

for each of the first plurality of event identifiers, receiving a first date identifier identifying a date associated with the life event;

for each of the first plurality of event identifiers, receiving a first song identifier identifying one or more songs identified by the first user as being associated with the life event;

generating the first electronic music diary by storing the first plurality of event identifiers, the first song identifiers, and the first date identifiers in an electronic storage medium wherein each first song identifier and each first date identifier is coupled with at least one respective first event identifier and the first plurality of event identifiers are coupled with each other;

receiving a request for a second electronic music diary;

identifying the second electronic music diary, wherein the second electronic music diary is associated with a second user different from the first user;

providing a second plurality of event identifiers associated with the second user, wherein each of the second plurality of event identifiers identifies a respective life event associated with a life of the second user;

associating the first electronic music diary with the second electronic music diary because at least one of the first plurality of event identifiers is substantially similar to at least one of the second plurality of event identifiers;

for at least one of the first plurality of event identifiers, receiving a first location identifier identifying a location associated with the life event, wherein each of the second plurality of event identifiers is coupled to a second location identifier that identifies a location within a predetermined distance of the location identified by the first location identifier;

obtaining from the electronic storage medium a plurality of second song identifiers, wherein each of the plurality of second song identifiers is coupled to at least one of the second plurality of event identifiers; and

providing the plurality of second song identifiers to the user device.

2. A method for a music diary processor to generate a first electronic music diary comprising:

receiving a first plurality of event identifiers from a user device, wherein each event identifier identifies a respective life event associated with a life of a first user;

for each of the first plurality of event identifiers, receiving a first date identifier identifying a date associated with the life event;

for each of the first plurality of event identifiers, receiving a first song identifier identifying one or more songs identified by the first user as being associated with the life event;

generating the first electronic music diary by storing the first plurality of event identifiers, the first song identifiers, and the first date identifiers in an electronic storage medium wherein each first song identifier and each first date identifier is coupled with at least one respective first event identifier and the first plurality of event identifiers are coupled with each other;

receiving a request for a second electronic music diary;

identifying the second electronic music diary, wherein the second electronic music diary is associated with a second user different from the first user;

providing a second plurality of event identifiers associated with the second user, wherein each of the second plurality of event identifiers identifies a respective life event associated with a life of the second user;

associating the first electronic music diary with the second electronic music diary because at least one of the first plurality of event identifiers is substantially similar to at least one of the second plurality of event identifiers;

for at least one of the first plurality of event identifiers, receiving a first location identifier identifying a location associated with the life event, wherein each of the second plurality of event identifiers is coupled to a second location identifier that identifies a location within a predetermined distance of the location identified by the first location identifier and a second date identifier that identifies a date within a predetermined date range of the date identified by the first date identifier;

obtaining from the electronic storage medium a plurality of second song identifiers, wherein each of the plurality of second song identifiers is coupled to at least one of the second plurality of event identifiers; and

providing the plurality of second song identifiers to the user device.

3. A music diary system having a hardware processor for generating an electronic music diary comprising:

a communications interface adapted to communicate with a network; and

a control system coupled to the communications interface and adapted to:

receive a first plurality of event identifiers from a user device, wherein each event identifier identifies a respective life event associated with a life of a first user;

for each of the first plurality of event identifiers, receive a first date identifier identifying a date associated with the life event;

for each of the plurality of first event identifiers, receive a first song identifier identifying one or more songs identified by the first user as being associated with the life event;

store the first plurality of event identifiers, the first song identifiers, and the first date identifiers in an electronic storage medium wherein each first song identifier and first date identifier is coupled with at least one respective first event identifier and the plurality of first event identifiers are coupled with each other;

receive a request for a second electronic music diary associated with a second user different from the first user;

provide a second plurality of event identifiers associated with the second user, wherein each of the second plurality of event identifiers identifies a respective life event associated with a life of the second user; and

associate the first electronic music diary with the second electronic music diary because at least one of the first plurality of event identifiers is substantially similar to at least one of the second plurality of event identifiers;

for at least one of the first plurality of event identifiers, receive a first location identifier identifying a location associated with the life event, wherein each of the second plurality of event identifiers is coupled to a second location identifier that identifies a location within a predetermined distance of the location identified by the first location identifier;

obtain from the electronic storage medium a plurality of second song identifiers, wherein each of the plurality of second song identifiers is coupled to at least one of the second plurality of event identifiers; and

provide the plurality of second song identifiers to the user device.

4. A music diary system having a hardware processor for generating an electronic music diary comprising:

a communications interface adapted to communicate with a network; and

a control system coupled to the communications interface and adapted to:

receive a first plurality of event identifiers from a user device, wherein each event identifier identifies a respective life event associated with a life of a first user;

for each of the first plurality of event identifiers, receive a first date identifier identifying a date associated with the life event;

for each of the plurality of first event identifiers, receive a first song identifier identifying one or more songs identified by the first user as being associated with the life event;

store the first plurality of event identifiers, the first song identifiers, and the first date identifiers in an electronic storage medium wherein each first song identifier and first date identifier is coupled with at least one respective first event identifier and the plurality of first event identifiers are coupled with each other;

receive a request for a second electronic music diary associated with a second user different from the first user;

provide a second plurality of event identifiers associated with the second user, wherein each of the second plurality of event identifiers identifies a respective life event associated with a life of the second user; and

associate the first electronic music diary with the second electronic music diary because at least one of the first plurality of event identifiers is substantially similar to at least one of the second plurality of event identifiers;

for at least one of the first plurality of event identifiers, receive a first location identifier identifying a location associated with the life event, wherein each of the second plurality of event identifiers is coupled to a second location identifier that identifies a location within a predetermined distance of the location identified by the first location identifier and a second date identifier that identifies a date within a predetermined date range of the date identified by the first date identifier;

obtain from the electronic storage medium a plurality of second song identifiers, wherein each of the plurality of second song identifiers is coupled to at least one of the second plurality of event identifiers; and

provide the plurality of second song identifiers to the user device.

Assignments (7)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 2, 2021
From: CRIA, INC.
To: STRIPE, INC.
Reel/Frame 057044/0753 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 16, 2019
From: IP3 2017, SERIES 200 OF ALLIED SECURITY TRUST I
To: CRIA, INC.
Reel/Frame 048082/0767 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 28, 2018
From: WALDECK TECHNOLOGY, LLC
To: IP3 2017, SERIES 200 OF ALLIED SECURITY TRUST I
Reel/Frame 045061/0144 →
RELEASE OF SECURITY INTEREST Recorded Jan 11, 2018
From: CONCERT DEBT, LLC
To: WALDECK TECHNOLOGY, LLC
Reel/Frame 044591/0845 →
RELEASE OF SECURITY INTEREST Recorded Jan 11, 2018
From: CONCERT DEBT, LLC
To: CONCERT TECHNOLOGY CORPORATION
Reel/Frame 044591/0775 →
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2017
From: CONCERT DEBT, LLC
To: CONCERT TECHNOLOGY CORPORATION
Reel/Frame 044391/0438 →
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2017
From: CONCERT DEBT, LLC
To: WALDECK TECHNOLOGY, LLC
Reel/Frame 044391/0407 →