METHOD OF ENABLING DIGITAL MUSIC CONTENT TO BE DOWNLOADED TO AND USED ON A PORTABLE WIRELESS COMPUTING DEVICE

• US 20130304870A1
• Filed: 03/15/2013
• Published: 11/14/2013
• Est. Priority Date: 05/05/2006
• Status: Active Grant

• Current Assignee: TikTok Pte Ltd. (ByteDance Ltd.)
• Original Assignee: Omnifone Ltd.
• Inventors: Lamb, Michael Ian, Lewis, Robert John, Pocock, Stephen William, Sant, Philip Anthony, Sullivan, Mark Peter, Evans, Christopher John, KNIGHT, Mark Stephen
• Granted Patent: US 9,065,792 B2
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: G06F 16/637 Administration of user profiles, e.g. generation, initialization, adaptation or distribution
• CPC Class Codes: G06F 16/639 using playlists
• CPC Class Codes: G06F 16/64 Browsing; Visualisation therefor generation of a list or set of audio data G06F16/638
• CPC Class Codes: G06F 16/68 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/686 using information manually generated, e.g. tags, keywords, comments, title or artist information, time, location or usage information, user ratings
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 50/01 Social networking
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes
• CPC Class Codes: H04L 51/52 for supporting social networking services
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• 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/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/60 : Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04L 67/62 : Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/14 : Multichannel or multilink protocols
• CPC Class Codes: H04M 1/72436 : for text messaging, e.g. short messaging services [SMS] or e-mails
• CPC Class Codes: H04M 1/72442 : for playing music files
• CPC Class Codes: H04M 15/41 : Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/8005 : Flat-fee
• CPC Class Codes: H04M 2203/358 : Digital rights management
• CPC Class Codes: H04M 3/4872 : Non-interactive information services
• CPC Class Codes: H04W 12/082 : using revocation of authorisation
• CPC Class Codes: H04W 12/084 : using delegated authorisation, e.g. open authorisation [OAuth] protocol
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/24 : Accounting or billing
• CPC Class Codes: H04W 4/50 : Service provisioning or reconfiguring
• CPC Class Codes: H04W 8/20 : Transfer of user or subscriber data
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: Y04S 40/20 : Information technology specific aspects, e.g. CAD, simulation, modelling, system security

Abstract

The invention enables digital music content to be downloaded to and used on a portable wireless computing device. An application running on the wireless device has been automatically adapted to parameters associated with the wireless device without end-user input (e.g. the application has been configured in dependence on the device OS and firmware, related bugs, screen size, pixel number, security models, connection handling, memory etc. This application enables an end-user to browse and search music content on a remote server using a wireless network; to download music content from that remote server using the wireless network and to playback and manage that downloaded music content. The application also includes a digital rights management system that enables unlimited legal downloads of different music tracks to the device and also enables any of those tracks stored on the device to be played so long as a subscription service has not terminated.

Claims

1. A portable wireless computing device programmed with a software application that enables digital music content to be downloaded and used on the computing device;

in which

(a) the application enables an end-user to browse and search music content on a remote server using a wireless network; and

to download music content from that remote server using the wireless network; and

(b) the application includes or interacts with a digital rights management program whose operation can be remotely configured (i) to enable unlimited legal downloads of different music tracks to the device whilst a subscription service between the device and the remote server is valid for the device or user associated with that device and (ii) to enable any of those tracks stored on the device to be played so long as the subscription service has not terminated.

2. The device of claim 1 in which the application uses a multithreaded architecture to balance the computational demands of network and/or music track catalogue access;

and the computational demands of one or more of;

the user interface of the application;

the DRM program;

media operations.

3. The device of claim 2 in which the multithreaded architecture uses parallel download threads so that large objects can be downloaded to the device in parallel as a background process.

4. The device of claim 1 in which the application is adapted to handle latency inherent in mobile networks and intermittent connectivity by intelligently knowing how much of a file has been downloaded and to ask only for any residual part of a file that has not been downloaded.

5. The device of claim 1 in which the application includes a scheduler for requesting different objects and data from the server, with priority being automatically determined by the application.

6. The device of claim 1 in which the application uses track meta-data that is formed as a separate meta-data layer and defines attributes of tracks, the meta-data being external to a music track to enable sharing and browsing of track information without needing to distribute the related music track files.

7. The device of claim 1 in which intelligent memory management automatically deletes least used tracks to make space for newly downloaded tracks.

8. The device of claim 1 in which the digital rights management program can be remotely configured such that defined, downloaded music tracks can still be played even if the subscription service is terminated.

9. The device of claim 1 in which a billing infrastructure for the subscription service is part of the billing infrastructure provided by a network operator that controls the wireless network.

10. The device of claim 1 in which periodically rolling or one-off subscription (e.g. daily, weekly or monthly) is achieved by linking the remote configuration of the digital rights management program to the billing infrastructure provided by the network operator that controls the wireless network.

11. The device of claim 1 in which the application has been automatically adapted to parameters associated with the computing device without end-user input, in which the parameters define one or more of:

(a) computing capabilities of the device.

(b) a set of media files and formats that can be shown via Java, including audio, pictures, video, and animations on the device.

(c) memory limitations of the device.

(d) a set of media files and formats that the device'"'"'s operating system can handle.

(e) how the device handles a network connection.

(f) networking capabilities and handling of the device, including one or more of CSD, GPRS, 2G, 2.5G, 3G, WAP, SMS, Bluetooth, Infrared, Wi-Fi, WiMAX.

12. The device of claim 1 in which the application records, and feeds back to a remote server, detailed end-user listening data.

13. The device of claim 12 in which the data includes how long tracks have been listened to.

14. The device of claim 12 in which the data includes what tracks are skipped through and when.

15. The device of claim 12 in which the application displays targeted news filtered according to the end-user'"'"'s playback habits.

16. The device of claim 12 in which the data is locally cached on the device and then sent back to the server as a piggyback over a communication that happens anyway.

17. The device of claim 16 in which the device will pre-emptively send the data back without waiting for the communication expected to happen anyway, only if the user has not connected for more than a set time.

18. The device of claim 12 in which the data is used to enrich a music suggestion engine that provides music track suggestions for display on the device.

19. The device of claim 1 in which the application creates, manages and displays shared playlists.

20. The device of any claim 1 in which the application displays playlist charts generated by users based on play behaviour.

21. The device of claim 1 in which the application interacts with music recommendation systems.

22. The device of claim 1 in which multiple such devices can all be synchronised by wireless or wire via the server to give same view of metadata (e.g. playlists, friends, favourite artists, albums and tracks etc) irrespective of which device a user operates.

23. The device of claim 1 in which playlists are stored on the server as meta-data defining the tracks in the playlist, the meta-data being separate from the tracks themselves and being capable of being sent more efficiently over the wireless network than the tracks themselves.

24. A software application for a portable wireless computing device and that enables digital music content to be downloaded and used on the computing device;

in which;

(a) the application enables an end-user to browse and search music content on a remote server using a wireless network; and

to download music content from that remote server using the wireless network; and

(b) the application includes or interacts with a digital rights management program whose operation can be remotely configured (i) to enable unlimited legal downloads of different music tracks to the device whilst a subscription service between the device and the remote server is valid for the device or user associated with that device and (ii) to enable any of those tracks stored on the device to be played so long as the subscription service has not terminated.