Method and system for determining the location for performing file-format conversions of electronics message attachments

• US 6,092,114 A
• Filed: 04/17/1998
• Issued: 07/18/2000
• Est. Priority Date: 04/17/1998
• Status: Expired due to Term

• Current Assignee: Unify Inc. (Atos SE)
• Original Assignee: Siemens Information And Communication Networks, Inc. (Siemens AG)
• Inventors: Shaffer, Shmuel, Beyda, William Joseph, Bonomo, Paul
• Primary Examiner(s): Lim, Krisna
• Application Number:
  US09/062,294
• Time in Patent Office: 823 Days
• Field of Search: 709/232, 709/246, 707/1, 707/10
• US Class Current: 709/232
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: Y10S 707/99931 Database or file accessing

Abstract

A method and system for exchanging electronic messages, such as email messages, include isolating personal computers and other client devices from the process of converting a message attachment from one file format to a second file format. File-format conversions are out-tasked to enhance file accessibility, free computer resources, and conserve a user'"'"'s time. The access requirements of each attachment to electronic messages are compared to the capabilities of a target client device. If it is determined that a file-format conversion is required, the conversion operation is assigned to a server that supports the process of reformatting the attachments. In an email environment, the server is substantially equivalent to the conventional email server, but includes enhanced conversion capabilities. In one embodiment, the determination of whether an attachment is accessible without conversion occurs at the server level. In another embodiment, the determination is implemented at the client device level. Preferably, if a local email server is incapable of reformatting the attachment, a request is transmitted to a remote server to perform the conversion. Typically, the remote server is the email server that supports message exchanges for the person who originated the message.

Claims

1. A method of providing message exchange capability for a plurality of users comprising steps of:

receiving electronic messages at a server that supports message access by said users, including receiving first electronic messages having attachments in file formats that are each specific to one of a plurality of applications;

identifying capabilities of client devices with respect to accessing said attachments without conversion from an original file format to a second file format;

determining whether said attachments are accessible without conversion by specific client devices to which said attachments are transferred;

converting first attachments from original file formats to selected second file formats at said server in response to determinations that said first attachments of said first electronic messages are inaccessible without conversion by said specific client devices to which said first attachments are transferred, including selecting said second file formats based upon said capabilities of said specific client devices; and

selectively transferring said electronic messages to said client devices, including transferring said first attachments to said specific client devices in said selected second file formats.

2. The method of claim 1 wherein said step of identifying said capabilities of said client devices includes maintaining a register of applications at said server, said register having data indicative of application programs that are stored at individual client devices.

3. The method of claim 1 wherein said step of determining whether said attachments are accessible without conversion includes comparing application requirements of each said attachment to said capabilities of said specific client devices to which said attachments are transferred, said step of comparing being implemented at said server such that said step of converting is executed prior to said first attachments being transferred.

4. The method of claim 1 wherein said step of identifying said capabilities of said client devices includes maintaining a register of applications at each client device, each register having data indicative of application programs stored at said client device at which said register is maintained, said step of determining whether said attachments are accessible without conversion being executed at said client devices.

5. The method of claim 4 further comprising a step of transmitting a client-to-server message from a first client device to said server in response to determining that an attachment of one of said first electronic messages is inaccessible by said first client device without conversion, said message being a request to convert said attachment at said server.

6. The method of claim 1 further comprising a step of determining whether said server has a capability of converting said attachments to file formats that is are accessible by said specific client devices to which said attachments are transferred, said method further comprising a step of generating and transmitting a request to a remote server from which a particular electronic message was received as a response to determining that said particular electronic message includes an attachment which said server is incapable of converting to a file format that is accessible by a client device to which said particular electronic message is to be transferred, said request including instructions to convert said attachment at said remote server to an accessible file format, said electronic messages being email messages.

7. The method of claim 6 further comprising transmitting a second request from said remote server to a remote client device at which said particular electronic message was generated in response to determining that said remote server is incapable of converting said particular electronic message to said accessible file format, said second request including instructions to retransmit said attachment in an accessible file format.

8. The method of claim 1 wherein said step of determining whether said attachments are accessible without conversion includes accessing text information of said first electronic messages, said text information being indicative of said original file formats of said first electronic messages.

9. The method of claim 1 wherein said step of receiving said first electronic messages includes receiving said attachments in video and graphics file formats, said first electronic messages being email messages, said step of converting said first attachments including converting video files and graphics files from original viewing file formats to alternative viewing file formats.

10. The method of claim 9 wherein said step of receiving said first electronic messages includes receiving said attachments in audio file formats, said first electronic messages being email messages, said step of converting said first attachments including converting audio files from original playing file formats to at least one alternative playing file format.

11. A method of accessing email attachments comprising steps of:

receiving an email message at a local server, said email message having an attachment having an original application-specific file format, said email message further having a text portion in a file format different than said attachment;

comparing access requirements of said attachment in said application-specific file format to format capabilities of a client device to which said email message is directed for access by a user, said format capabilities being indicative of an ability to access said attachment in said original application-specific file format;

converting said attachment to a second application-specific file format in response to determining that said attachment is inaccessible at said client device while in said original application-specific file format, said converting being implemented at a site remote from said client device;

leaving said attachment in said original application-specific file format in response to determining that said attachment is accessible at said client device while in said original application-specific file format; and

transferring said attachment from said local server to said client device.

12. The method of claim 11 wherein said step of comparing said access requirements to said format capabilities is executed at said local server and includes maintaining a register of applications at said local server, said register having data indicative of said format capabilities of said client device.

13. The method of claim 11 wherein said step of comparing said access requirements to said format capabilities is executed at said client device, said method further comprising transmitting a message to said local server to request said conversion of said attachment by said local server when it is determined that said attachment is inaccessible by said client device without said conversion.

14. The method of claim 13 further comprising transmitting a second message to a remote server to request said conversion of said attachment by said remote server when it is determined that said local server is incapable of said conversion.

15. The method of claim 11 wherein said step of receiving said attachment is a step of receiving a video or graphics file.

16. The method of claim 11 wherein said step of comparing said access requirements to said file capabilities and said step of converting said attachment are implemented such that said client device is free to execute other tasks during said converting.

17. An email delivery system comprising:

a local email server connected to a network to receive email messages, including first email messages having attachments in original file formats that are each specific to one of a plurality of applications, said local email server having memory for storing said email messages;

a plurality of client devices connected to said local email server to selectively access said email messages;

register means for identifying first attachments that are inaccessible by a specific one of said client devices in an absence of converting said first attachments from said original file format, said first attachments being discrete file attachments of said first email messages, said register means being connected to one of said local email server and said plurality of client devices; and

converter means responsive to said register means and located at said local email server for converting each said first attachment to a second file format that is selected to accommodate access without conversion by said specific one of said client devices.

18. The system of claim 17 wherein said register means is a register stored at said local email server, said register having data indicative of a plurality of applications that are stored at each one of said client devices.

19. The system of claim 18 wherein said converter means is a conversion program stored in said memory of said local email server.

20. The system of claim 19 further comprising means for transmitting a request to a remote server to convert a particular one of said first attachments in response to a determination that said local email server lacks resources for converting said particular first attachment to said selected second file format.