Scheduling Events

• US 20160366078A1
• Filed: 06/09/2015
• Published: 12/15/2016
• Est. Priority Date: 06/09/2015
• Status: Active Grant

• Current Assignee: AirWatch LLC (Broadcom, Inc.)
• Original Assignee: AirWatch LLC (Broadcom, Inc.)
• Inventors: Razavian, Joseph Nickolas, Ramachandran, Suja
• Granted Patent: US 10,084,737 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 51/18 Commands or executable codes

Abstract

Disclosed are examples relating to scheduling events using devices in communication through a network. In some examples, an email message comprising an encoded data element is obtained. The encoded data element includes data that specifies a proposed time for an event. The data that specifies the proposed time for the event is extracted from the encoded data element. Content from the email message is rendered in a user interface. A user interface element is rendered within the user interface. The user interface element represents the proposed time for the event and an availability for the event at the proposed time.

Claims

1. A non-transitory computer-readable medium storing a plurality of computer instructions executable by a computing device, the plurality of computer instructions being configured to cause the computing device to at least:

obtain an email message comprising an encoded data element, wherein the encoded data element comprises data that specifies a proposed time for an event;

extract the data that specifies the proposed time for the event from the encoded data element;

determine an availability for the event at the proposed time;

render content from the email message in a user interface;

render a user interface element within the user interface, wherein the user interface element represents the proposed time for the event and displays an indication of the availability for the event;

generate an event entry for an electronic calendar, wherein the event entry specifies that the event is scheduled at the proposed time; and

transmit a response to a sender device associated with the email message.

2. The non-transitory computer-readable medium of claim 1, wherein the plurality of computer instructions are further configured to cause the computing device to at least:

obtain calendar data associated with a user of the computing device; and

determine the availability for the event at the proposed time based on the calendar data.

3. The non-transitory computer-readable medium of claim 1, wherein the plurality of computer instructions are configured to generate the event entry and transmit the response after a selection of the proposed time by a user of the computing device.

4. The non-transitory computer-readable medium of claim 1, wherein the encoded data element further specifies a plurality of proposed times for the event.

5. The non-transitory computer-readable medium of claim 1, wherein the encoded data element is embedded in a header of the email message.

6. The non-transitory computer-readable medium of claim 1, wherein the encoded data element is embedded in a body of the email message.

7. A system, comprising:

a computing device; and

a client application executable by the computing device, wherein the client application, when executed by the computing device, is configured to cause the computing device to at least;

obtain an email message comprising an encoded data element, wherein the encoded data element comprises data that specifies a proposed time for an event;

extract the data that specifies the proposed time for the event from the encoded data element;

determine an availability for the event at the proposed time;

render content from the email message in a user interface;

render a user interface element within the user interface, wherein the user interface element represents the proposed time for the event and displays an indication of the availability for the event; and

generate an event entry for an electronic calendar, wherein the event entry specifies that the event is scheduled at the proposed time.

8. The system of claim 7, wherein the client application is further configured to cause the computing device to at least transmit an invitation for the event to a sender device associated with the email message.

9. The system of claim 7, wherein the client application is further configured to cause the computing device to at least determine whether the encoded data element is present in the email message.

10. The system of claim 7, wherein the encoded data element comprises email header data.

11. The system of claim 7, wherein the encoded data element comprises extensible markup language code in a body of the email message.

12. The system of claim 7, wherein the encoded data element comprises data that specifies a plurality of proposed times for the event.

13. The system of claim 12, wherein the client application is further configured to cause the computing device to at least represent the plurality of proposed times in the user interface element.

14. A method, comprising:

obtaining an email message comprising an encoded data element, wherein the encoded data element comprises data that specifies a proposed time for an event;

extracting the data that specifies the proposed time for the event from the encoded data element;

determining an availability for the event at the proposed time;

rendering content from the email message in a user interface; and

rendering a user interface element within the user interface, wherein the user interface element represents the proposed time for the event and the availability for the event at the proposed time.

15. The method of claim 14, further comprising:

obtaining calendar data associated with a user; and

determining the availability for the event at the proposed time based on the calendar data.

16. The method of claim 15, further comprising:

obtaining a selection of the proposed time for the event from a user of a client device;

generating an event entry for an electronic calendar in response to the selection, wherein the event entry specifies that the event is scheduled at the proposed time; and

transmitting an invitation for the event to a sender device associated with the email message in response to the selection.

17. The method of claim 14, further comprising determining whether the email message includes the encoded data element.

18. The method of claim 17, wherein determining whether the email message includes the encoded data element comprises determining whether the email message comprises an encoded data element marker.

19. The method of claim 14, wherein the encoded data element comprises email header data.

20. The method of claim 14, wherein the encoded data element comprises hypertext markup language code.