Browse Prior Art Database

Location Based Presence Management Service (LBPMS)

IP.com Disclosure Number: IPCOM000131911D
Publication Date: 2005-Nov-21
Document File: 2 page(s) / 30K

Publishing Venue

The IP.com Prior Art Database

Abstract

Mobile device users are always present with a status of available. Clearly no person will always be available to a business or any other organization. If the presence indicator is to be of any use, we need to have algorithms that automatically and accurately manage the individual's presence based on rules defined by the user. If these rules are not available for the mobile user define and update quickly, then presence will become a useless indicator. The Location Based Presence Management Service (LBPMS) allows a user to build rules that manage presence based on location coordinates. The presence status can be regularly communicated to other presence management servers (e.g. Instant Messaging servers such as LCS or Sametime) The Location based presence management service has several inputs and outputs: Inputs: - Location coordinates (e.g. longitude & latitude) - Presence management rules - Presence status options Output: - Presence status at specified intervals The engine would have several components: - Rule creation and management interface - Rule testing engine - Status API to external applications Detailed Description: A mobile user defines a one or more rule that will control presence based on location. Examples include: 1) Presence is AWAY unless current location is more than 2 meters from the last location. If location has changed by more than 2 meters then presence is changed to AVAILABLE (this allows a user to quickly specify that they cannot be reached while at a meeting location or while their mobile device is sitting on the table at home. As soon as they leave the meeting or pick up the device to go to work, they become available) 2) Presence shall be AVAILABLE when current location is within 1 kilometer of a specific coordinate. (This allows a user to automatically become available when they get close to their desk, or on the train as they commute to and from work.) There are numerous other rule examples. At specified time intervals (e.g. once a minute, every 15 minutes) the rule-testing engine would recalculate the presence status of the mobile user and send the presence to specific applications (Instant Messaging buddy lists, email applications, etc.)

This text was extracted from a Microsoft Word document.
This is the abbreviated version, containing approximately 65% of the total text.

Location-Based Presence Management Service (Lbpms)

Location Based Presence Management Service (LBPMS)

Disclosed Anonymously

Mobile device users are always present with a status of available. Clearly no person will always be available to a business or any other organization. If the presence indicator is to be of any use, we need to have algorithms that automatically and accurately manage the individual's presence based on rules defined by the user.

If these rules are not available for the mobile user define and update quickly, then presence will become a useless indicator.

The Location Based Presence Management Service (LBPMS) allows a user to build rules that manage presence based on location coordinates. The presence status can be regularly communicated to other presence management servers (e.g. Instant Messaging servers such as LCS or Sametime)

The Location based presence management service has several inputs and outputs: 

Inputs:

- Location coordinates (e.g. longitude & latitude)

- Presence management rules

- Presence status options

Output:

- Presence status at specified intervals

The engine would have several components:

- Rule creation and management interface

- Rule testing engine

- Status API to external applications

Detailed Description:

A mobile user defines a one or more rule that will control presence based on location. Examples include:

1)  Presence is AWAY unless current location is more than 2 meters from the last location. If location has changed by more tha...