Method and system for generating and processing electronic meeting communications for multiple formats

• US 8,086,673 B2
• Filed: 06/07/2006
• Issued: 12/27/2011
• Est. Priority Date: 06/07/2006
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Lam, Wing Young, Van, Anh Ngoc
• Primary Examiner(s): Dollinger, Tonia L M
• Assistant Examiner(s): John, Clarence
• Application Number:
  US11/447,895
• Publication Number:
  US 20070288658A1
• Time in Patent Office: 2,029 Days
• Field of Search: 709/206, 709/246
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

A method for generating electronic meeting communications for multiple formats and a messaging server for adapted in accordance with the method. The method comprises: receiving on the messaging server a first electronic meeting communication having a first meeting component in a first format, the first meeting component including event information; determining a second meeting component in a second format different from the first format, the second meeting component including substantially the same event information as the first meeting component; and sending a second electronic meeting communication comprising at least the first and second meeting components from the messaging server to one or more recipient devices.

Claims

1. A method for handling electronic meeting communications for multiple formats, the method comprising the steps of:

receiving on a messaging server a first electronic meeting communication having a first meeting component in a first format, the first meeting component including event information;

determining a second meeting component in a second format different from the first format, the second meeting component including substantially the same event information as the first meeting component;

creating a second electronic meeting communication comprising at least both the first and second meeting components by inserting the second meeting component into the first electronic meeting communication;

sending the second electronic meeting communication from the messaging server;

receiving the second electronic meeting communication on a recipient device;

determining a preferred one of the first meeting component and the second meeting component;

selecting the preferred one of the first meeting component and the second meeting component and disregarding the other one of the first meeting component and the second meeting component;

wherein the first meeting component and the second meeting component are one of;

an iCalendar message component in accordance with the iCalendar standard, a proprietary message header component in accordance with a proprietary message header format, and a text component readable by normal email clients;

wherein the first meeting component and the second meeting component are each in a different format; and

processing the selected meeting component.

2. The method as claimed in claim 1, wherein the first meeting component is one of at least two meeting components in one or more respective formats in the first electronic meeting communication.

3. The method as claimed in claim 1, further comprising determining a third meeting component in a third format different from both the first and second formats, the third meeting component including substantially the same event information as the first meeting component, wherein the second electronic meeting communication further comprises the third meeting component, wherein determining a preferred one comprises determining the preferred one of the first meeting component, the second meeting component and the third meeting components, and wherein selecting the preferred one comprises selecting the preferred one of the first meeting component, the second meeting component and the third meeting components and disregarding the other ones of the first meeting component, the second meeting component and the third meeting components.

4. The method as claimed in claim 3, wherein creating the second electronic meeting communication comprises inserting the second and third meeting components into the first electronic meeting communication received on the messaging server.

5. The method as claimed in claim 3, wherein the, third meeting component is one of:

an iCalendar message component in accordance with the iCalendar standard, a proprietary message header component in accordance with a proprietary message header format, and a text component readable by normal email clients, wherein the first component, second component, and third component are each in a different format.

6. The method of claim 1, wherein the proprietary message header format is compatible with one or more Lotus Notes proprietary message header formats.

7. The method of claim 1, wherein the proprietary message header component is positioned at the beginning of the second electronic meeting communication, the text component is positioned within the second electronic meeting communication after the proprietary message header component, and the iCalendar component is positioned within the second electronic meeting communication after the text component.

8. The method of claim 7, wherein the second electronic meeting communication is an email message.

9. The method of claim 6, wherein the second electronic meeting communication has a global content-type of multipart/alternative.

10. A non-transitory computer readable medium comprising program instructions recorded thereon executable on a computing device having a programmable processor for implementing the method as claimed in claim 1.

11. The method of claim 1, wherein the at least first and second meeting components are arranged according to a predetermined order.

12. The method of claim 11, wherein the predetermined order is in increasing order of preference.

13. The method of claim 1, further comprising one of formatting or reformatting the second electronic meeting communication in accordance with Multipurpose Internet Mail Extensions (MIME) standard.

14. A messaging server for generating electronic meeting communications for multiple formats, the messaging server being in communication with one or more client devices via a communications network, the messaging server comprising:

a communication subsystem for sending and receiving electronic communications;

a processor and memory, the memory including data and instructions to configure the processor to;

receive on the messaging server a first electronic meeting communication having a first meeting component in a first format, the first meeting component including event information;

determine a second meeting component in a second format different from the first format, the second meeting component including substantially the same event information as the first meeting component;

create a second electronic meeting communication comprising at least both the first and second meeting components by inserting the second meeting component into the first electronic meeting communication;

wherein one of the first meeting component and second meeting component is preferred for use by a recipient device configured to select one of the first meeting component and the second meeting component and disregard the other of the first meeting component and the second meeting component;

wherein the first meeting component and the second meeting component are one of;

an iCalendar message component in accordance with the iCalendar standard, a proprietary message header component in accordance with a proprietary message header format, and a text component readable by normal email clients;

wherein the first meeting component and the second meeting component are each in a different format; and

send the second electronic meeting communication from the messaging server to the recipient device.

15. The messaging server as claimed in claim 14, wherein the first meeting component is one of at least two meeting components in one or more respective formats in the first electronic meeting communication.

16. The messaging server as claimed in claim 14, wherein the memory includes data and instructions to further configure the processor to determine a third meeting component in a third format different from both the first and second formats, the third meeting component including substantially the same event information as the first meeting component, wherein the second electronic meeting communication further comprises the third meeting component, wherein one of the first meeting component, the second meeting component and the third meeting component is preferred for use by the recipient device, the recipient device being configured to select one of the first meeting component, the second meeting component and the third meeting component and disregard the others of the first meeting component, the second meeting component and the third meeting component.

17. The messaging server as claimed in claim 16, wherein the memory includes data and instructions to further configure the processor to create the second electronic meeting communication comprising inserting the second and third meeting components into the first electronic meeting communication received on the messaging server.

18. The messaging server as claimed in claim 16, wherein the third meeting component is one of:

an iCalendar message component in accordance with the iCalendar standard, a proprietary message header component in accordance with a proprietary message header format, and a text component readable by normal email clients, wherein the first component, second component, and third component are each in a different format.

19. The messaging server of claim 14, wherein the proprietary message header format is compatible with one or more Lotus Notes proprietary message header formats.

20. The messaging server of claim 19, wherein the second electronic meeting communication has a global content-type of multipart/alternative.

21. The messaging server of claim 14, wherein the proprietary message header component is positioned at the beginning of the second electronic meeting communication, the text component is positioned within the second electronic meeting communication after the proprietary message header component, and the iCalendar component is positioned within the second electronic meeting communication after the text component.

22. The messaging server of claim 21, wherein the second electronic meeting communication is an email message.

23. The messaging server of claim 14, wherein the at least first and second meeting components are arranged according to a predetermined order.

24. The messaging server of claim 23, the predetermined order is in increasing order of preference.

25. The messaging server of claim 14, wherein the memory includes data and instructions to further configure the processor to perform one of formatting or reformatting the second electronic meeting communication in accordance with Multipurpose Internet Mail Extensions (MIME) standard.

26. A method for use on a messaging server for generating electronic meeting communications for multiple formats, the method comprising the steps of:

receiving on the messaging server a first electronic meeting communication having a first meeting component in a first format, the first meeting component including event information;

determining a second meeting component in a second format different from the first format, the second meeting component including substantially the same event information as the first meeting component;

creating a second electronic meeting communication comprising at least both the first and second meeting components by inserting the second meeting component into the first electronic meeting communication;

wherein one of the first meeting component and second meeting component is preferred for use by a recipient device configured to select one of the first meeting component and the second meeting component and disregard the other of the first meeting component and the second meeting component;

wherein the first meeting component and the second meeting component are one of;

an iCalendar message component in accordance with the iCalendar standard, a proprietary message header component in accordance with a proprietary message header format, and a text component readable by normal email clients;

wherein the first meeting component and the second meeting component are each in a different format; and

sending the second electronic meeting communication from the messaging server to the recipient device.

27. The method as claimed in claim 26, wherein the first meeting component is one of at least two meeting components in one or more respective formats in the first electronic meeting communication.

28. The method as claimed in claim 26, further comprising determining a third meeting component in a third format different from both the first and second formats, the third meeting component including substantially the same event information as the first meeting component, wherein the second electronic meeting communication further comprises the third meeting component, wherein one of the first meeting component, the second meeting component and the third meeting component is preferred for use by the recipient device, the recipient device being configured to select one of the first meeting component, the second meeting component and the third meeting component and disregard the others of the first meeting component, the second meeting component and the third meeting component.

29. The method as claimed in claim 28, wherein creating the second electronic meeting communication comprises inserting the second and third meeting components into the first electronic meeting communication received on the messaging server.

30. The method as claimed in claim 28, wherein the, third meeting component is one of:

an iCalendar message component in accordance with the iCalendar standard, a proprietary message header component in accordance with a proprietary message header format, and a text component readable by normal email clients, wherein the first component, second component, and third component are each in a different format.

31. The method of claim 26, wherein the proprietary message header format is compatible with one or more Lotus Notes proprietary message header formats.

32. The method of claim 31, wherein the second electronic meeting communication has a global content-type of multipart/alternative.

33. The method of claim 26, wherein the proprietary message header component is positioned at the beginning of the second electronic meeting communication, the text component is positioned within the second electronic meeting communication after the proprietary message header component, and the iCalendar component is positioned within the second electronic meeting communication after the text component.

34. The method of claim 33, wherein the second electronic meeting communication is an email message.

35. The method of claim 26, wherein the at least first and second meeting components are arranged according to a predetermined order.

36. The method of claim 35, wherein the predetermined order is in increasing order of preference.

37. The method of claim 26, further comprising one of formatting or reformatting the second electronic meeting communication in accordance with Multipurpose Internet Mail Extensions (MIME) standard.