Browse Prior Art Database

A Method and System for Setting Alarms across Devices based on Relationships Associated with a Calendar Event

IP.com Disclosure Number: IPCOM000238339D
Publication Date: 2014-Aug-18
Document File: 3 page(s) / 76K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method and system for setting alarms across devices based on relationships associated with a calendar event.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

A Method and System for Setting Alarms across Devices based on Relationships Associated with a Calendar Event

In general, calendar events are specific to relationships such as family, soccer team,

work group etc. For example, when a user has an upcoming event, the user will generally set an alarm on a device as a reminder to prepare for and attend the event. However, there is no way for an event owner to ensure that each member associated by a relationship with the event has appropriate alarms set that would remind the corresponding members of the event. Also, the members may not have calendar entries for the event on corresponding devices. The members however still need an alarm, even though the calendar invite does not exist on a device.

Conventionally, if an event owner has set the alarm for the calendar event, there is no

way to automatically set and synchronize the alarms of others in the relationship for that

event. If a user schedules an event for a group (relationship), the user can only hope that the participants will remember to set device alarms that will remind the participants to show up for the event. Also, if there is any change in event timing, users must remember to reset alarms, and if the users forget to do so, the users face the risk of missing or being late for the scheduled events.

Disclosed is a method and system for setting alarms across devices based on relationships associated with a calendar event. Even if a member in a relationship does not have a calendar event on the respective device, the method and system automatically enables an alarm across devices such as tablets, mobile devices etc., based on the relationship that is specified in the calendar event.

The method and system also enables a user to schedule a calendar event with an associated relationship. The details for scheduling the calendar event may include, but need not be limited to, date, time, duration, location, and participants (relationship) for an appointment or meeting. Subsequently, the user or event owner sets the alarm for the event. Then, the alarms for each member listed as part of the relationship for the event are also enabled and synchronized with the alarm of the event owner. Further, any changes made in the calendar schedule forces the alarm to change across all the member devices listed in the relationship.

The method and system enables a user to set a profile to synchronize the alarm appropriately across each member's device. The profile may indicate the time needed to get ready for and travel to the event for each member in the relationship of that particular event. For example, if a user 1 takes one hour to get ready for the event and a user 2 takes only 30 minutes to get ready for the same event, then the alarm is staggered when set on user 2's device.

The profile set by the user can also indicate a synchronization period for which the alarm shou...