Apparatus and method to provide mobile music appliance with subscription-based play-list service

• US 20060056324A1
• Filed: 09/10/2004
• Published: 03/16/2006
• Est. Priority Date: 09/10/2004
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Makipaa, Mikko, Aaltonen, Janne, Salo, Juha, Kopra, Toni, Nihtila, Jukka, Muhonen, Ahti, Hannikainen, Ari, Pajusalo, Ari, Antola, Janne, Levine, Oren Haim, Hyyppa, Timo
• Application Number:
  US10/937,944
• Publication Number:
  US 20060056324A1
• Time in Patent Office: Days
• US Class Current: 370/310
• CPC Class Codes: G06Q 20/123 Shopping for digital content
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests

Abstract

Disclosed is a method to deliver a set of song-related information to a terminal associated with a subscriber of a content provisioning system. The method includes establishing a subscriber profile for specifying at least a frequency at which the content provisioning system is to download to the subscriber at least one list of content, in the preferred invention at least one list of songs, that is updated in accordance with at least one criterion. The method further downloads the at least one song list to the terminal at a time that is based on the subscriber profile. Also disclosed is a content provisioning system, a network server and a terminal that operate in accordance with the method.

Claims

1. A method to deliver a set of content to a terminal associated with a subscriber of a content provisioning system, comprising:

establishing a subscriber profile for specifying at least a frequency at which the content provisioning system is to download to the subscriber at least one list that is updated in accordance with at least one criterion;

creating at least one rights object; and

downloading the at least one content list to the terminal at a time that is based on the subscriber profile.

2. A method as in claim 1, where the content comprises songs, further comprising previewing at least one song that forms a part of a downloaded song list.

3. A method as in claim 1, where the content comprises songs, further comprising purchasing at least one downloaded song, and storing the purchased song in a collection of songs associated with the subscriber.

4. A method as in claim 1, where downloading occurs at least in part through a wireless cellular network.

5. A method as in claim 1, where downloading occurs at least in part through the Internet.

6. A method as in claim 1, where downloading occurs at least in part through a cellular communications network.

7. A method as in claim 1, where downloading occurs at least in part through a wireless local area network.

8. A method as in claim 1, where the criterion comprises a user preference e.g. location.

9. A method as in claim 1, where the criterion comprises content usage data.

10. A method as in claim 1, where the criterion comprises content ratings.

11. A method as in claim 1, where the content comprises songs, further comprising purchasing at least one downloaded song, and storing the purchased song in a collection of songs that is selected automatically based on at least one subscriber-preferred criterion.

12. A method as in claim 1, where the content comprises songs, further comprising purchasing at least one downloaded song, and storing the purchased song in a collection of songs that is selected manually by the subscriber.

13. A method as in claim 1, further comprising billing the subscriber automatically at least for maintaining and managing the subscription.

14. A method as in claim 1, where downloading comprises sending to the subscriber content list-related metadata.

15. A method as in claim 1, where downloading comprises sending to the subscriber Play-list related content.

16. A method as in claim 1, where there is one digital rights management (DRM) rights object (RO) for the entire content list.

17. A method as in claim 1, where the content list is downloaded in response to a download request and comprises a list of URLs that identify what files to download.

18. A method as in claim 17, where the URLs point to download descriptor (DD) files used by the terminal to initiate a download sequence.

19. A method as in claim 1, where there is one digital rights management (DRM) rights object (RO) for the entire content list, and comprises a contentIDs for all content in the content list.

20. A system comprising a content provisioning system and at least one terminal associated with a subscriber of the content provisioning system, comprising:

a user interface to establishing a subscriber profile for specifying at least a frequency at which the content provisioning system is to download to the subscriber at least one content list that is updated in accordance with at least one criterion;

a rights management subsystem operable to create at least one required rights object; and

a download subsystem to download the at least one content list to the terminal at a time that is based on the subscriber profile.

21. A system as in claim 20, where said terminal comprises functionality to preview at least one content that forms a part of the downloaded content list.

22. A system as in claim 20, where the content comprises songs, further comprising a purchasing application that cooperates with said terminal to purchase at least one song, and to store the purchased song in a collection of songs associated with the subscriber.

23. A system as in claim 20, where the download subsystem is coupled to the Internet.

24. A system as in claim 20, where the download subsystem is coupled to a cellular communications network.

25. A system as in claim 20, where the download subsystem is coupled to a wireless local area network.

26. A system as in claim 20, where the criterion comprises a user preference.

27. A system as in claim 20, where the criterion comprises content usage data.

28. A system as in claim 20, where the criterion comprises content ratings.

29. A system as in claim 20, where the content comprises songs, where a purchased song is stored in a collection of songs that is selected automatically based on at least one subscriber-preferred criterion entered through said user interface.

30. A system as in claim 20, where the content comprises songs, where a purchased song is stored in a collection of songs that is selected manually by the subscriber via said user interface.

31. A system as in claim 20, further comprising a billing subsystem to automatically generate billing for the subscriber at least for maintaining and managing the subscription.

32. A system as in claim 20, where said download subsystem sends content list related metadata to the subscriber.

33. A system as in claim 20, where said download subsystem sends content list related content to the subscriber.

34. A system as in claim 20, where there is one digital rights management (DRM) rights object (RO) for the entire content list.

35. A system as in claim 20, where the content list is downloaded in response to a download request and comprises a list of URLs that identify what files to download.

36. A system as in claim 35, where the URLs point to download descriptor (DD) files used by the terminal to initiate a download sequence.

37. A system as in claim 20, where there is one digital rights management (DRM) rights object (RO) for the entire content list, and comprises a contentIDs for all content in the content list.

38. A network server comprising at least a part of a content provisioning system, comprising:

a subscription subsystem that is responsive to information received from a terminal associated with a subscriber of the content provisioning system, to establish a subscriber profile for specifying at least a frequency at which the content provisioning system is to download to the subscriber at least one list of content that is updated in accordance with at least one criterion;

a rights management subsystem operable to download a list of content in association with a rights object for the list of content; and

a download subsystem to download the at least one list of content to the terminal at a time that is based on the subscriber profile.

39. A network server as in claim 38, further comprising a purchasing application that cooperates with said terminal to purchase content identified by said terminal.

40. A network server as in claim 38, where there is one digital rights management (DRM) rights object (RO) for the entire content list.

41. A network server as in claim 38, where the content list is downloaded in response to a download request from the terminal and comprises a list of URLs that identify what files to download.

42. A network server as in claim 41, where the URLs point to download descriptor (DD) files used by the terminal to initiate a download sequence.

43. A network server as in claim 38, where there is one digital rights management (DRM) rights object (RO) for the entire content list, and comprises a contentIDs for all content in the content list.

44. A network server as in claim 38, where the download subsystem is coupled to the Internet.

45. A network server as in claim 38, where the download subsystem is coupled to at least one of a cellular communications network and a wireless local area network.

46. A network server as in claim 38, where the criterion comprises at least one of a user preference, usage data, ratings and location.

47. A network server as in claim 38, further comprising a billing subsystem to automatically generate billing for the subscriber at least for maintaining and managing the subscription.

48. A network server as in claim 38, where the list of content comprises a list of songs.

49. A terminal associated with a subscriber to a content provisioning system, comprising a transceiver for communication with the content provisioning system, a user interface, a content provisioning system subscription application, a content application, a content download manager and a rights management subsystem for downloaded content, said user interface operable to establish a subscriber profile for specifying at least a frequency at which the content provisioning system is to download to the subscriber at least one list of content that is updated in accordance with at least one criterion;

said rights management subsystem cooperating with a content provisioning system rights management subsystem, via said transceiver, to download at least one list of content in association with a rights object for the list of content;

where said download manager is operable to receive the at least one list of content at a time that is based on the subscriber profile.

50. A terminal as in claim 49, where the content comprises songs, and where said user interface comprises functionality to preview at least one song that forms a part of the downloaded list of content.

51. A terminal as in claim 50, further comprising a purchasing application to purchase at least one song, and to store the purchased song in a collection of songs associated with the subscriber.

52. A terminal as in claim 49, where the transceiver is for coupling to the Internet.

53. A terminal as in claim 49, where the transceiver is comprised of an RF transceiver for coupling to a cellular communications network.

54. A terminal as in claim 49, where the transceiver is for coupling to a wireless local area network.

55. A terminal as in claim 49, where the criterion comprises at least one of a user preference, usage data, ratings and location.

56. A terminal as in claim 51, where a purchased song is stored in a collection of songs that is selected automatically based on at least one subscriber-preferred criterion entered through said user interface.

57. A terminal as in claim 51, where a purchased song is stored in a collection of songs that is selected manually by the subscriber via said user interface.

58. A terminal as in claim 49, where said download manager receives content list related metadata from the content provisioning system.

59. A terminal as in claim 49, where the content is comprised of songs, and where said download manager receives song list related content from the content provisioning system.

60. A terminal as in claim 49, where there is one digital rights management (DRM) rights object (RO) for an entire list of content.

61. A terminal as in claim 49, where the list of content is downloaded in response to a download request from the download manager and comprises a list of URLs that identify to the download manager what files to download.

62. A terminal as in claim 61, where the URLs point to download descriptor (DD) files used by the download manager to initiate a download sequence.

63. A terminal as in claim 49, where there is one digital rights management (DRM) rights object (RO) for the entire list of content, and comprises a contentIDs for all content in the content list.

64. A terminal as in claim 49, where said terminal comprises a cellular telephone.

65. A terminal as in claim 49, where said terminal comprises a personal computer.

66. A terminal as in claim 49, where said terminal comprises a WLAN-enabled data processor.

67. A terminal as in claim 49, where said terminal comprises a WLAN-enabled communications device.

68. A terminal as in claim 49, where said terminal comprises a digital content storage and playback device.

69. A terminal as in claim 49, where said terminal comprises a music storage and playback device.

70. A terminal as in claim 49, where said terminal comprises a content storage for image album and/or video and games catalog plus a playback device.

71. A computer program product comprising a computer useable medium including a computer readable program, wherein the computer readable program when executed on the computer causes the computer to perform operations comprising:

establishing a subscriber profile for specifying at least a frequency at which the content provisioning system is to download to the subscriber at least one list that is updated in accordance with at least one criterion;

creating at least one rights object; and

downloading the at least one content list to the terminal at a time that is based on the subscriber profile.

72. A computer program product as in claim 71, where the content comprises songs, further comprising previewing at least one song that forms a part of a downloaded song list.

73. A computer program product as in claim 71, where the content comprises songs, further comprising purchasing at least one downloaded song, and storing the purchased song in a collection of songs associated with the subscriber.

74. A computer program product as in claim 71, where downloading occurs at least in part through a wireless cellular network.

75. A computer program product as in claim 71, where downloading occurs at least in part through the Internet.

76. A computer program product as in claim 71, where downloading occurs at least in part through a cellular communications network.

77. A computer program product as in claim 71, where downloading occurs at least in part through a wireless local area network.

78. A computer program product as in claim 71, where the criterion comprises a user preference.

79. A computer program product as in claim 71, where the criterion comprises content usage data.

80. A computer program product as in claim 71, where the criterion comprises content ratings.

81. A computer program product as in claim 71, where the content comprises songs, further comprising purchasing at least one downloaded song, and storing the purchased song in a collection of songs that is selected automatically based on at least one subscriber-preferred criterion.

82. A computer program product as in claim 71, where the content comprises songs, further comprising purchasing at least one downloaded song, and storing the purchased song in a collection of songs that is selected manually by the subscriber.

83. A computer program product as in claim 71, further comprising billing the subscriber automatically at least for maintaining and managing the subscription.

84. A computer program product as in claim 71, where downloading comprises sending to the subscriber content list-related metadata.

85. A computer program product as in claim 71, where downloading comprises sending to the subscriber Play-list related content.

86. A computer program product as in claim 71, where there is one digital rights management (DRM) rights object (RO) for the entire content list.

87. A computer program product as in claim 71, where the content list is downloaded in response to a download request and comprises a list of URLs that identify what files to download.

88. A computer program product as in claim 87, where the URLs point to download descriptor (DD) files used by the terminal to initiate a download sequence.

89. A computer program product as in claim 71, where there is one digital rights management (DRM) rights object (RO) for the entire content list, and comprises a contentIDs for all content in the content list.

90. A computer program product as in claim 78, where the user preference comprises location.