IP Library Granted Patent US 8,738,718
Granted Patent B2
US 8,738,718 · App. 13/678,771 · Granted May 27, 2014

Systems and methods for facilitating creating calendar entries in client devices

Inventors: Tomas Soukup (Havirov, CZ); Stepan Potys (Klatovy, CZ); Otakar Leopold (Plzen, CZ)
Assignee: Kerio Technologies Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,738,718
App. No.
13/678,771
Granted
May 27, 2014
Kind
B2
Abstract

A method for facilitating creating one or more calendar entries in one or more client devices is provided. The method includes receiving an iTIP (iCalendar Transport-Independent Interoperability Protocol) message from a first client device. The method further includes generating an iMIP (iCalendar Message-Based Interoperability Protocol) message using the iTIP message. The method also includes providing at least one of a copy of the iTIP message and a copy of the iMIP message to a least one of the second client device and a second communication server device connected to the second client device for enabling the second calendar application to generate a calendar entry in the second client device. The method also includes determining whether one of a first action and a second action is to be taken. The method further includes performing one of said first action and said second action based on said determining.

Claims (80)

1. A method for facilitating creating one or more calendar entries in one or more client devices, the method comprising:

receiving, using a first communication server device, an iTIP (iCalendar Transport-Independent Interoperability Protocol) message from a first client device, the first client device being associated with a first user, the first client device having a first calendar application, the iTIP message being addressed to at least a second user, the second user being associated with a second client device, the second client device having a second calendar application;

generating, using the first communication server device, an iMIP (iCalendar Message-Based interoperability Protocol) message using the iTIP message;

providing at least one of a copy of the iTIP message and a copy of the iMIP message to a least one of the second client device and a second communication server device connected to the second client device for enabling the second calendar application to generate a calendar entry in the second client device;

determining, using a first communication device, whether one of a first action and a second action is to be taken, said first action including transmitting, using said first communication server device the copy of the iTIP message to deliver information in the iTIP message received from the first client device to a first destination client device, said second action including transmitting, using the first communication server device, a copy of the iMIP message to deliver the information in the iTIP message received from the first client device to a second destination client device;

performing one of said first action and said second action based on said determining;

generating a first-user identifier for the user using an email address of the first user;

generating the first-user identifier further using an attached phrase, the first-user identifier including at least the email address of the first user and the attached phrase; and

providing the first-user identifier to the first client device for the first client device to include the first-user identifier in the iTIP message.

2. The method of claim 1 further comprising:

using information stored in the first communication server device to determine one or more characteristics associated with at least one of the second user, the second client device, and the second calendar application; and

after determining that the second client device is connected to the first communication server device through a second communication server device, wrapping the copy of the iMIP message in a SMTP (Simple Mail Transfer Protocol) message and providing the SMTP message to the second communication server device for enabling the second calendar application to create the calendar entry based on content of at least one of the copy of the iTIP message and the copy of the iMIP message, the wrapping being performed using the first communication server device.

3. The method of claim 2 further comprising:

using the second communication server device to obtain the copy of the iTIP message by removing an SMTP envelope and removing at least one email envelope from the SMTP message; and

providing the copy of iTIP message from the second communication server device to the second client device.

4. The method of claim 1 further comprising:

using information stored in the first communication server device to determine one or more characteristics associated with at least one of the second user, the second client device, and the second calendar application; and

after determining that the second calendar application is compatible with iTIP, removing at least an email envelope from the copy of the iMIP message to obtain a copy of the iTIP message and providing the copy of the iTIP message to the second client device for enabling the second calendar application to create the calendar entry based on content of the copy of the iTIP message, the removing, being performed using the first communication server device.

5. The method of claim 1 further comprising:

using information stored in the first communication server device to determine one or more characteristics associated with at least one of the second user, the second client device, and the second calendar application; and

after determining that the second calendar application is compatible with iMIP, providing the copy of the iMIP message to the second client device for enabling the second calendar application to create the calendar entry based on content of the copy of the iMIP message, the providing being performed using the first communication server device.

6. The method of claim 1 further comprising:

receiving a synchronization request from the first client device; and

providing a synchronization response to the first client device, the synchronization response including the first-user identifier.

7. The method of claim 1

wherein the attached phrase is “mailto:”, the attached phrase preceding the email address of the first user in the first-user identifier.

8. The method of claim 1 thither comprising:

generating at least an email envelope for the iMIP message;

including at least an originator data field in the email envelope;

removing a copy of the attached phrase from a copy of the first-user identifier to obtain a copy of the email address of the first user;

including the copy of the email address of the first user in the originator data field of the iMIP message; and

including the email envelope and the iTIP message in the iMIP message.

9. The method of claim 1 further comprising:

generating a second-user identifier for the second user using an email address of the second user;

generating the second-user identifier further using the attached phrase, the second-user identifier including at least the email address of the second user and the attached phrase; and

providing the second-user identifier to the first client device for the first client device to include the second-user identifier in the iTIP message.

10. The method of claim 9 further comprising:

generating at least an email envelope for the iMIP message including at least an recipient data field in the email envelope;

removing a copy of the attached phrase from a copy of the second-user identifier to obtain a copy of the email address of the second user;

including the copy of the email address of the second user in the recipient data field of the iMIP message; and

including the email envelope and the iTIP message in the iMIP message.

11. The method of claim 1 further comprising:

identifying a calendar protocol that is compatible with the first calendar application to generate first-client calendar protocol information when the first client device registers with the first communication server device; and

storing the first-client calendar protocol information in the first communication server device.

12. The method of claim 1 further comprising:

receiving, using the first communication server device, a calendar message from the first client device; and

removing a HTTP (Hypertext Transfer Protocol) header from the calendar message to obtain the iTIP message.

13. The method of claim 1 further comprising:

transmitting a confirmation message to the first client device after performing the generating and before performing the providing; and

placing the iMIP message into a queue in the first communication server device after the generating and before the providing.

14. A communication server device composing a non-transitory program storage medium having computer readable code stored therein, the computer readable code being configured for facilitating creating one or more calendar entries in one or more client devices, the communication server device comprising:

code, stored in the non-transitory program storage medium in the communication server device, for receiving an iTIP (iCalendar Transport-Independent Interoperability Protocol) message from a first client device, the first client device being associated with a first user, the first client device having a first calendar application, the iTIP message being addressed to at least a second user, the second user being associated with a second client device, the second client device having a second calendar application;

code for generating an iMIP (iCalendar Message-Based interoperability Protocol) message using the iTIP message; and

code for providing at least one of a copy of the iTIP message and a copy of the iMIP message to the second client device for enabling the second calendar application to generate a calendar entry in the second client device;

code for determining, using a first communication device, whether one of a first action and a second action is to be taken, said first action including transmitting, using said first communication server device the copy of the iTIP message to deliver information in the iTIP message received from the first client device to a first destination client device, said second action including transmitting, using the first communication server device, a copy of the iMIP message to deliver the information in the iTIP message received from the first client device to a second destination client device;

code for performing one of said first action and said second action based on said determining;

code for determining whether, wherein the first communication server device transmits the copy of the iTIP message to deliver information in the iTIP message received from the first client device to a first destination client device and wherein the first communication server device transmits a copy of the iMIP message to deliver the information in the iTIP message received from the first client device to a second destination client device, whether the copy of the iTIP message or the copy of the iMIP message is transmitted by the first communication server device is determined by the first communication server device;

code for generating a first-user identifier for the first user using an email address of the first user;

code for generating the first-user identifier using an attached phrase, the first-user identifier including at least the email address of the first user and the attached phrase; and

code providing the first-user identifier to the first client device for the first client device to include the first-user identifier in the iTIP message.

15. The communication server device of claim 14 further comprising a storage unit for storing information pertaining to one or more characteristics associated with at least one of the second user, the second client device, and the second calendar application, the information including at least one of an email address of the second user and calendar protocol information pertaining to a calendar protocol that is compatible with the second calendar application.

16. The communication server device of claim 14 further comprising:

code for generating at least an email, envelope for the iMIP message;

code for including at least an originator data field in the email envelope;

code for removing a copy of the attached phrase from a copy of the first-user identifier to obtain as copy of the email address of the first user;

code for including the copy of the email address of the first user in the originator data field of the iMIP message; and

code for including the email envelope and the iTIP message in the iMIP message.

17. The communication server device of claim 14 further comprising:

code for removing at least one email envelope from a copy of a second iMIP message to obtain a copy of a second iTIP message; and

code for providing the copy of the second iTIP message to a third client device that has a third calendar application for enabling the third calendar application to update the third client device.

18. A method for facilitating creating one or more calendar entries in one or more client devices, the method comprising:

receiving, using a first communication server device, an iTIP (iCalendar Transport-Independent Interoperability Protocol) message from a first client device, the first client device being associated with a first user, the first client device having a first calendar application, the iTIP message being addressed to at least a second user, the second user being associated with a second client device, the second client device having a second calendar application;

generating, using the first communication server device, an iMIP (iCalendar Message-Based Interoperability Protocol) message using the iTIP message; and

providing at least one of a copy of the iTIP message and a copy of the iMIP message to a least one of the second client: device and a second communication server device connected to the second client device for enabling the second calendar application to generate a calendar entry in the second client device, wherein the first communication server device transmits the copy of the iTIP message to deliver information in the iTIP message received from the first client device to a first destination client device and wherein the first communication server device transmits a copy of the iMIP message to deliver the information in the iTIP message received from the first client device to a second destination client device, whether the copy of the iTIP message or the iMIP message is transmitted by the first communication server device is determined by the first communication server device, wherein the iTIP message includes a first-user identifier generated for the first user using an e-mail address of the first user and further using an attached phrase.

19. The method of claim 18 further comprising:

using information stored in the first communication server device to determine one or more characteristics associated with at least one of the second user, the second client device, and the second calendar application; and

after determining that the second calendar application is compatible with iTIP, removing at least an email envelope from the copy of the iMIP message to obtain a copy of the iTIP message and providing the copy of the iTIP message to the second client device for enabling the second calendar application to create the calendar entry based on content of the copy of the iTIP message, the removing being performed using the first communication server device.

20. The method of claim 18 further comprising:

using information stored in the first communication server device to determine one or more characteristics associated with at least one of the second user, the second client device, and the second calendar application; and

after determining that the second calendar application is compatible with iMIP, providing the copy of the iMIP message to the second client device for enabling the second calendar application to create the calendar entry based on content of the copy of the iMIP message, the providing being performed using the first communication server device.

Assignments (9)
SECURITY INTEREST Recorded Mar 6, 2023
From: GFI USA, LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 062888/0560 →
RELEASE OF SECURITY INTEREST Recorded Feb 23, 2023
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: AUREA SOFTWARE, INC.; KERIO TECHNOLOGIES INC.; NEXTDOCS CORPORATION; EXINDA INC.
Reel/Frame 062787/0550 →
RELEASE OF SECURITY INTEREST Recorded Feb 23, 2023
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: AUREA SOFTWARE, INC.; NEXTDOCS CORPORATION; MESSAGEONE, LLC
Reel/Frame 062787/0207 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 13, 2023
From: AUREA SOFTWARE, INC.
To: GFI USA, INC.
Reel/Frame 062676/0718 →
CHANGE OF NAME Recorded Feb 13, 2023
From: GFI USA, INC.
To: GFI USA, LLC
Reel/Frame 062743/0205 →
SECURITY INTEREST Recorded May 31, 2022
From: AUREA SOFTWARE, INC.; NEXTDOCS CORPORATION,; MESSAGEONE, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 060220/0673 →
MERGER AND CHANGE OF NAME Recorded Nov 17, 2020
From: KERIO TECHNOLOGIES, LLC; AUREA SOFTWARE, INC.
To: AUREA SOFTWARE, INC.
Reel/Frame 054395/0264 →
PATENT SECURITY AGREEMENT Recorded Mar 30, 2018
From: AUREA SOFTWARE, INC.; KERIO TECHNOLOGIES INC.; NEXTDOCS CORPORATION; EXINDA INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 045789/0445 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 12, 2014
From: SOUKUP, TOMAS; POTYS, STEPAN; LEOPOLD, OTAKAR
To: KERIO TECHNOLOGIES INC.
Reel/Frame 032208/0808 →
Continuity (2)
Continuation 12275113 · Nov 20, 2008
Related Publication 20130073664A1 · Mar 21, 2013