Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

System to Determine actions for related events

IP.com Disclosure Number: IPCOM000233916D
Publication Date: 2013-Dec-30
Document File: 2 page(s) / 16K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a system of using shared social information to determine actions a user might need to take due to related events of others. The implementation includes identifying a signature of an event with respect to a profiled path.

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

Page 01 of 2

System to Determine actions for related events

At times, one initial life event spawns a new path of events or actions for a person. For example, a friend coming to visit leads to preparatory actions such as shopping, boarding a dog, rearranging schedules, etc.. These actions, in turn might cause actions for others. The current solution involves manual notification of the situation and manual inputs and actions of the person to prepare for the activities of the related event.

The novel contribution presents a system of using shared social information to determine actions a user might need to take due to related events of others. The implementation includes identifying a signature of an event with respect to a profiled path.

The steps for implementing the method in a preferred embodiment follow:

1. User A posts to social networking site: "Attending Event X on May 5th, and stopping at User B's house for the night on the way".

2. System identifies user/group planning an event by trolling the user's social network to determine what events of others (e.g., User A) could indirectly affect User B. The system:

A. Pulls information from social networking posts and accepted events of others (e.g., User A is attending Event X, and stopping at User B's house on the way) Location of user who accepted event and location of event

B. Identifies the names of users that were mentioned in the post or event, and the association with or relationship to the user (e.g., User A is a relative of User B; therefore, User A's actions are likely to affect User B). If the system identifies the location as being nearby, this can increase the likelihood that the actions or events of one user can affect the other user.

3. System determines the event signature based on the identified user/group based on the following:

A. Previous events attended based on time of year

B. Typical travel patterns of the users or vacation days, availability of time, length of travel utilizing distance to events and user location

C. Level of confidence that the event might occur, to help dynamically update tasks, length of stay, etc. The system can utilize a heat map to indicate the accuracy of this level of confidence.

4. System utilizes the location of the event, the locations of User A and User B, and time stamps from the social network post to determine the actions that need to be taken. The extent of visit can be determined in the context of visit and length of time. The system can utilize the vacation days set in a calendar if acc...