Global Media Lists For Mobile Devices

• US 20140059059A1
• Filed: 08/21/2013
• Published: 02/27/2014
• Est. Priority Date: 08/21/2012
• Status: Active Grant

• Current Assignee: Roovy, Inc.
• Original Assignee: Roovy, Inc.
• Inventors: Barman, Touradj, Webb, Wyatt, Webber, Scott
• Granted Patent: US 9,501,477 B2
• Time in Patent Office: Days
• US Class Current: 707/752
• CPC Class Codes: G06F 16/40 of multimedia data, e.g. slideshows comprising image and additional audio data retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04N 21/23109 by placing content in organized collections, e.g. EPG data repository details of retrieval of video data and associated meta data in video databases G06F16/739
• CPC Class Codes: H04N 21/25891 being end-user preferences retrieval of video data in a video database based on user preferences G06F16/739; arrangements for recognizing users' preferences H04H60/46; user profiles in network data switching protocols H04L67/306; processing of user preferences or user profiles in wireless networks H04W8/18
• CPC Class Codes: H04N 21/2743 Video hosting of uploaded data from client
• CPC Class Codes: H04N 21/41407 embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop constructional details of equipment or arrangements specially adapted for portable computer application G06F1/1626; arrangements specially adapted for mobile receivers in broadcast systems H04H20/57
• CPC Class Codes: H04N 21/4431 characterized by the use of Application Program Interface [API] libraries
• CPC Class Codes: H04N 21/6581 Reference data, e.g. a movie identifier for ordering a movie or a product identifier in a home shopping application
• CPC Class Codes: H04N 21/8352 involving content or source identification data, e.g. Unique Material Identifier [UMID]
• CPC Class Codes: H04N 21/84 Generation or processing of descriptive data, e.g. content descriptors systems specially adapted for using meta-information in broadcast systems H04H60/73

Abstract

Systems and methods are disclosed for sharing global lists of media content among multiple apps executing on various client devices. A global list can include a plurality of records for media, each of which can include pointers to media stored elsewhere, a unique identifier for the media, a list identifier for the media, and/or metadata for the media. The global list can be accessed, modified, shared, aggregated, organized, etc. using different apps. These different apps may include apps developed by different developers, apps produced by different companies, apps offered for download by different companies, apps that perform different functions, etc.

Claims

1. A method comprising:

receiving, at a server from a first client application executing on a client device, a first media link to media, a first user identifier, and an indication of a media list where the first media link will be stored, wherein the media list is associated with the user identifier, and wherein the first media link points to an image, music, or a video stored on a server;

organizing in a database at the server the first media link in the media list;

receiving, at the server from a second client application, the first user identifier along with a request for one or more media lists associated with the first user identifier, wherein the second client application is a different application than the first client application, and wherein each of the one or more media lists associated with the user identifier include one or more media links; and

sending, from the server to the second client application, the one or more media lists associated with the user identifier.

2. The method according to claim 1, wherein neither the first client application nor the second client application is a web browser application.

3. The method according to claim 1, wherein the second client application is executing on the client device.

4. The method according to claim 1, wherein the first application and the second application are the same application.

5. The method according to claim 1, further comprising creating, at the server, a unique identifier for the media associated with the first media link, and associating the unique identifier with the first media link in the media list.

6. The method according to claim 1, further comprising receiving, at the server, a unique identifier associated with the media from the first application.

7. The method according to claim 1, further comprising:

receiving metadata associated with the media from the first application; and

organizing in the database at the server the metadata with the media in the media list.

8. The method according to claim 1, further comprising.

receiving an indication of the order of the first media link relative to other media links in the media list;

and

wherein the organizing in a database at the server the first media link in the media list further comprises;

organizing the first media link in an order relative to other media links in the media list as specified by the indication of the order of the first media.

9. The method according to claim 1, further comprising receiving a request from the first application executing on the client device to create the media list prior to receiving the first media link.

10. The method according to claim 1, further comprising:

receiving a first identifier associated with the first client application from the first client application; and

receiving a second identifier associated with the second client application from the second client application.

11. The method according to claim 1, further comprising:

determining a plurality of clients associated with the media list; and

sending the media list to the plurality of clients associated with the media list.

12. The method according to claim 1, further comprising:

determining a plurality of client applications associated with the media list;

sending a notification to the plurality of client applications associated with the media list specifying that the media list has been updated;

receiving a request for the media list from a third client application that is one of the plurality of client applications; and

sending the media list to the third client application.

13. The method according to claim 1, wherein the media list includes a media sub-list, and wherein the organizing the media into the media list includes organizing the media into the media sub-list.

14. A method comprising:

receiving, at a server from a first client application executing on a client device, media content, a user identifier, and an indication of a first media list where the media will be stored;

storing the media content in a database at a server;

associating a media link to the media content in the database at the server that can be used to retrieve the media content through a communication network;

organizing in a database at the server the media link to the media in the first media list;

receiving, at the server from a second client application, the user identifier along with a request for one or more media lists associated with the first user identifier, wherein the second client application is a different application than the first client application; and

sending, from the server to the second client application, the media lists associated with the user identifier.

15. The method according to claim 14, wherein neither the first client application nor the second client application is a web browser application.

16. The method according to claim 14, wherein the first media list includes a media sub-list, and wherein the organizing the media into the media list includes organizing the media into the media sub-list.

17. A method comprising:

maintaining in storage at a server a plurality of media lists where each media list of the plurality of media lists comprises a plurality of media links to media, a list identifier and a plurality of unique media identifiers;

receiving at the server from a first app executing on a first mobile device a request for a first media list of the plurality of media lists;

sending from the server to the first app executing on the first mobile device the first media list;

receiving at the server from a second app executing on a second mobile device a request for the second media list of the plurality of media lists, wherein the second app is different than the first app; and

sending from the server to the second app executing on the second mobile device the second media list.

18. The method according to claim 17, wherein neither the first app nor the second app are web browser applications.

19. The method according to claim 17, wherein the first mobile device and the second mobile device comprise the same mobile device.

20. The method according to claim 17, wherein the first mobile device and the second mobile device comprise different mobile devices.

21. The method according to claim 17, wherein the first media list and the second media list comprise different media lists.

22. The method according to claim 17, wherein the first media list and the second media list comprise the same media list.

23. The method according to claim 17, wherein a first media link of the plurality of media links link to media in the first media list points to an image, music, calendar, document, or a video and a second media link of the plurality of media links link to media in the first media list points to media different than the media pointed to by the first media link.

24. A global list server comprising:

a database;

a communication interface; and

a processor communicatively coupled with the database and the communication interface, wherein the processor is configured to;

maintain a plurality of media lists within the database, wherein each media list of the plurality of media lists comprises a plurality of media links, a list identifier and a plurality of unique media identifiers associated with each of the plurality of media links;

receive from a first app executing on a first mobile device a request for a first media list of the plurality of media lists;

send the first media list to the first app executing on the first mobile device;

receive from a second app executing on the first mobile device a request for the first media list of the plurality of media lists, wherein the second app is a different and an independent app from the first app; and

send the first media list to the second app executing on the second mobile device.

25. The global list server according to claim 24, wherein the processor is further configured to:

receive from a third app executing on a second mobile device a request for the first media list of the plurality of media lists, wherein the third app is a different and an independent app from at least one of the first app and the second app; and

send from the server to the third app executing on the second mobile device the first media list.