Cloud hosted multimedia file handling on mobile devices

• US 10,469,423 B2
• Filed: 06/15/2018
• Issued: 11/05/2019
• Est. Priority Date: 02/14/2014
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Pokharel, Anurodh
• Primary Examiner(s): Kincaid, Lester G
• Assistant Examiner(s): Bassett, Daniel G.
• Application Number:
  US16/009,513
• Publication Number:
  US 20180295082A1
• Time in Patent Office: 508 Days
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: G06F 3/00 Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
• CPC Class Codes: H04L 51/10 Multimedia information
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04M 1/7243 with interactive means for internal management of messages
• CPC Class Codes: H04M 2250/64 file transfer between terminals download of applications H04M1/72406; transfer of messages, e.g. SMS, e-mail or MMS H04M1/7243
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Abstract

A method for handling a cloud hosted multimedia file on mobile devices includes receiving a message with a link to multimedia file, extracting the link and determining an address of multimedia server, contacting the multimedia server to determine a file type and determining whether the file type is supported.

Claims

1. A method for handling a cloud hosted multimedia file on mobile devices comprising:

receiving a message with a link to multimedia file;

extracting the link and determining an address of multimedia server;

contacting the multimedia server to determine a file type using a HEAD command;

determining whether the file type is supported; and

determining that the message is spam by detecting that a file size of the multimedia file as reported in a response to the HEAD command is not within a predetermined range for the file type as reported in the response to the HEAD command.

2. The method of claim 1 further comprising displaying the link in response to determining that the file type is not supported.

3. The method of claim 1 further comprising determining whether the multimedia file is oversized.

4. The method of claim 1 further comprising downloading the multimedia file as a thumbnail in response to determining that the file type is supported.

5. The method of claim 1 further comprising displaying playback controls for an audio multimedia file in response to determining that the file type is supported.

6. The method of claim 1 further comprising:

receiving a user request via a tap on icon; and

displaying the multimedia file.

7. The method of claim 1 further comprising determining that the message is spam by detecting that an ETag of the multimedia file as reported in a response to the HEAD command is being used in an attempt to repeatedly send the multimedia file with different URLs.

8. A non-transitory computer readable storage medium for storing thereon computer readable instructions for a method for:

receiving a message with a link to multimedia file;

extracting the link and determining an address of multimedia server;

contacting the multimedia server to determine a file type using a HEAD command;

determining whether the file type is supported; and

determining that the message is spam by detecting that a file size of the multimedia file as reported in a response to the HEAD command is not within a predetermined range for the file type as reported in the response to the HEAD command.

9. The non-transitory computer readable storage medium of claim 8, further comprising computer readable instructions for a method for:

displaying the link in response to determining that the file type is not supported.

10. The non-transitory computer readable storage medium of claim 8, further comprising computer readable instructions for a method for:

determining whether the multimedia file is oversized.

11. The non-transitory computer readable storage medium of claim 8, further comprising computer readable instructions for a method for:

downloading the multimedia file as a thumbnail in response to determining that the file type is supported.

12. The non-transitory computer readable storage medium of claim 8, further comprising computer readable instructions for a method for:

displaying playback controls for an audio multimedia file in response to determining that the file type is supported.

13. The non-transitory computer readable storage medium of claim 8, further comprising computer readable instructions for a method for:

receiving a user request via a tap on icon; and

displaying the multimedia file.

14. The non-transitory computer readable storage medium of claim 10, further comprising computer readable instructions for a method for:

determining that the message is spam by detecting that an ETag of the multimedia file as reported in a response to the HEAD command is being used in an attempt to repeatedly send the multimedia file with different URLs.