Systems and Methods for Supporting Downloadable Applications on a Portable Client Device

• US 20140136640A1
• Filed: 01/17/2014
• Published: 05/15/2014
• Est. Priority Date: 11/02/2007
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Shih, Jimmy, McKinley, Joanne, Phillips, Derek, Nicolaou, Alex, Shamis, Zhanna, Beust, Cdric
• Granted Patent: US 9,497,147 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads

Abstract

Systems, methods, and computer readable storage mediums for providing message services from a server are described. In some embodiments, a server stores an attachment associated with a communication. The server sends the communication to a client device, with a representation of the attachment type that includes an indication of the attachment'"'"'s native file type. The server receives a request from the client device to view the attachment in the client device. The server retrieves the attachment in response to the request and transcodes the attachment from the attachment'"'"'s native file type to a viewable file type configured to display in the client device. The viewable file type is determined by the server based on metadata received from the client device. The server transmits at least a portion of the attachment in the viewable file type to the client device for display. Other embodiments are also described.

Claims

1. A method to provide message services, comprising:

at a server having one or more processors and memory storing programs executed by the one or more processors;

storing an attachment associated with a communication;

sending to a client device the communication, with a representation of the attachment type that includes an indication of the attachment'"'"'s native file type;

receiving a request from the client device to view the attachment in the client device,

retrieving the attachment in response to the request;

transcoding the attachment from the attachment'"'"'s native file type to a viewable file type configured to display in the client device, wherein the viewable file type is determined by the server based on metadata received from the client device; and

transmitting at least a portion of the attachment in the viewable file type to the client device for display.

2. The method of claim 1, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

3. The method of claim 1, wherein the appropriate viewable file type selected for transcoding from the native file type is determined by a user of the client device.

4. A system to provide message services, comprising:

one or more processors, a memory coupled to the one or more processors; and

one or more programs, stored in the memory, configured for execution by the one or more processors, the one or more programs comprising instructions for;

storing on the server an attachment associated with a communication;

sending to a client device the communication, with a representation of the attachment type that includes an indication of the attachment'"'"'s native file type;

receiving a request from the client device to view the attachment in the client device;

retrieving the attachment in response to the request;

transcoding the attachment from the attachment'"'"'s native file type to a viewable file type configured to display in the client device, wherein the viewable file type is determined by the server based on metadata received from the client device; and

transmitting at least a portion of the attachment in the viewable file type to the client device for display.

5. The system of claim 4, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

6. The system of claim 4, wherein the appropriate viewable file type selected for transcoding from the native file type is determined by a user of the client device.

7. A non-transitory computer readable storage medium storing one or more programs configured for execution by a server, the one or more programs comprising instructions for:

storing an attachment associated with a communication;

sending to a client device the communication, with a representation of the attachment type that includes an indication of the attachment'"'"'s native file type;

receiving a request from the client device to view the attachment in the client device,

retrieving the attachment in response to the request;

transcoding the attachment from the attachment'"'"'s native file type to a viewable file type configured to display in the client device, wherein the viewable file type is determined by the server based on metadata received from the client device; and

transmitting at least a portion of the attachment in the viewable file type to the client device for display.

8. The non-transitory computer readable storage medium of claim 7, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

9. The non-transitory computer readable storage medium of claim 7, wherein the appropriate viewable file type selected for transcoding from the native file type is determined by a user of the client device.

10. A method to display an attachment in a viewable file type, comprising:

at a client having one or more processors and memory storing programs executed by the one or more processors;

receiving a communication and a representation of an attachment associated with the communication, wherein the representation includes an indication of the attachment'"'"'s native file type;

requesting a server to send the attachment for display on the client device;

receiving at least a portion of a transcoded copy of the attachment in a viewable file type configured for display on the client device; and

displaying at least a portion of the received attachment in the viewable file type.

11. The method of claim 10, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

12. The method of claim 10, further comprising:

receiving a user selected appropriate viewable file type for transcoding from the native file type; and

requesting the server to send the attachment for display in the user selected appropriate viewable file type.

13. The method of claim 10, wherein the requesting further comprises providing metadata in the request for the viewable file type in which to transcode the attachment.

14. A client to display an attachment in a viewable file type, comprising:

one or more processors, a memory coupled to the one or more processors; and

one or more programs, stored in the memory, configured for execution by the one or more processors, the one or more programs comprising instructions for;

receiving a communication and a representation of an attachment associated with the communication, wherein the representation includes an indication of the attachment'"'"'s native file type;

requesting a server to send the attachment for display on the client device;

receiving at least a portion of a transcoded copy of the attachment in a viewable file type configured for display on the client device; and

displaying at least a portion of the received attachment in the viewable file type.

15. The client of claim 14, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

16. The client of claim 14, further comprising instructions for:

receiving a user selected appropriate viewable file type for transcoding from the native file type; and

requesting the server to send the attachment for display in the user selected appropriate viewable file type.

17. The client of claim 14, further comprising instructions for providing metadata in the request for the viewable file type in which to transcode the attachment.

18. A non-transitory computer readable storage medium storing one or more programs configured for execution by a server, the one or more programs comprising instructions for:

receiving a communication and a representation of an attachment associated with the communication, wherein the representation includes an indication of the attachment'"'"'s native file type;

requesting a server to send the attachment for display on the client device;

receiving at least a portion of a transcoded copy of the attachment in a viewable file type configured for display on the client device; and

displaying at least a portion of the received attachment in the viewable file type.

19. The non-transitory computer readable storage medium of claim 18, wherein the attachment in the viewable file type is smaller in size than the attachment in the native file type.

20. The non-transitory computer readable storage medium of claim 18, further comprising instructions for:

receiving a user selected appropriate viewable file type for transcoding from the native file type; and

requesting the server to send the attachment for display in the user selected appropriate viewable file type.

21. The non-transitory computer readable storage medium of claim 18, further comprising instructions for providing metadata in the request for the viewable file type in which to transcode the attachment.