IP Library Granted Patent US 7,184,524
Granted Patent B2
US 7,184,524 · App. 10/367,617 · Granted Feb 27, 2007

Rules based real-time communication system

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 7,184,524
App. No.
10/367,617
Granted
Feb 27, 2007
Kind
B2
Abstract

A rules-based real-time messaging system for groups of users, in which an availability status may be maintained in association with each user. Clients are communicably coupled to a real-time messaging server, which maintains indications of the online/offline presence status of each user, as well as other user attributes. Rules and a rules engine are maintained in the real-time messaging server for controlling the delivery of messages to users, and for controlling how the availability of users is provided to other users. Based on the specific rules stored on the real-time messaging server, the rules engine determines the state of various relevant conditions, such as the availability status of users of the system, and also detects the occurrence of various real-time events, such as a user logging-on to or logging-off from the system, in order to control the delivery of various types of messages and/or performance of resulting actions.

Claims (32)

1. A method of supporting real-time communication between at least two users, comprising the steps of:

receiving at least one request for at least one real-time action, wherein said request includes a list of participant users to participate in said real-time action;

in a first determining step, determining, responsive to said at least one request, a status of at least one condition, wherein said status of said at least one condition indicates whether at least one of said participant users is available to participate in said real-time action, and wherein said status of said at least one condition is responsive to an online presence of said at least one of said participant users;

in a second determining step, determining whether said at least one real-time action can be performed responsive to said status of said at least one condition; and

performing said real-time action in the event that a determination is made that said real-time action can be performed,

wherein said second determining step and said performing step are responsive to a processing of at least one rule, said at least one rule having a logical structure defined by at least one of at least one condition and at least one event notification, said at least one rule defining a specified relationship between said at least one condition, said at least one event notification, and said real-time action.

2. The method of claim 1 , wherein said request is a request to convene an automated meeting activity, wherein said request includes a list of participant users for said automated meeting activity, and wherein said determining whether said at least one real-time action can be performed includes determining whether at least one of said participant users is available for said automated meeting activity.

3. The method of claim 2 , wherein said determining whether at least one of said participant users is available for said automated meeting is responsive to at least one event notification indicating that said at least one of said participant users is presently using at least one software program on a client system.

4. The method of claim 3 , wherein said at least one event notification indicates that said at least one of said participant users is currently using instant messaging client software on said at least one client system.

5. The method of claim 2 , further comprising determining a stand-in participant user if, in the first determining step, it is determined that at least one of said participant users is not available for said automated meeting activity.

6. The method of claim 1 , wherein said list of participant users to participate in said real time action includes a name of a group of users, and further comprising selecting one of said group of users to participate in said real time action.

7. The method of claim 6 , wherein said selecting said one of said group of users to participate in said real time action includes applying a predetermined selection technique associated with said group of users.

8. The method of claim 2 , wherein said automated meeting activity comprises an online meeting.

9. The method of claim 2 , wherein said automated meeting activity comprises a teleconference.

10. The method of claim 2 , wherein said automated meeting activity comprises a shared whiteboard.

11. The method of claim 2 , wherein said automated meeting activity comprises a remote presentation.

12. The method of claim 2 , wherein said automated meeting activity comprises a video conference.

13. A system for supporting communication between at least two users, comprising:

at least one processor;

a computer program storage memory communicably coupled with said at least one processor, said computer storage memory including at least one computer program executable on said at least one processor, said computer program including

program code for receiving at least one request for at least one real-time action, wherein said request includes a list of participant users to participate in said real-time action;

program code for determining, responsive to said at least one request, a status of at least one condition, wherein said status of said at least one condition indicates whether at least one of said participant users is available to participate in said real-time action, and wherein said status of said at least one condition is responsive to an online presence of said at least one of said participant users;

program code for determining whether said at least one real-time action can be performed responsive to said status of said at least condition; and

program code for performing said real-time action in the event that a determination is made that said real-time action can be performed,

wherein said program code for determining whether said at least one real-time action can be performed and said program code for performing said real-time action are responsive to a processing of at least one rule, said at least one rule having a logical structure defined by at least one of at least one condition and at least one event notification, said at least one rule defining a specified relationship between said at least one condition, said at least one event notification, and said real-time action.

14. A method of supporting communication between at least two users, comprising the steps of:

in a first receiving step, receiving at least one request, wherein said request is a request to convene an automated meeting activity, wherein said request includes a list of user participants for said automated meeting activity;

in a second receiving step, receiving at least one event notification;

in a first determining step, determining a status of at least one condition;

in a second determining step, determining whether at least one action can be performed responsive to said event notification and said status of said at least one event notification, wherein said determining whether said at least one action can be performed includes determining whether at least one of said user participants is available for said automated meeting activity, and wherein said determining whether at least one of said user participants is available for said automated meeting is responsive to at least one event notification indicating that said at least one of said user participants is presently using at least one client system; and

performing said at least one action if, in said second determining step, it is determined that said at least one action can be performed,

wherein said determining whether said at least one action can be performed in said second determining step, and said performing said at least one action, are responsive to a processing of at least one rule, said at least one rule having a logical structure defined by at least one of at least one condition and at least one event notification, said at least one rule defining a specified relationship between said at least one condition, said at least one event notification, and said action.

Assignments (11)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 21, 2023
From: MIND FUSION, LLC
To: THINKLOGIX, LLC
Reel/Frame 064357/0554 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 13, 2023
From: INTELLECTUAL VENTURES ASSETS 191 LLC
To: MIND FUSION, LLC
Reel/Frame 064270/0685 →
SECURITY INTEREST Recorded Mar 23, 2023
From: MIND FUSION, LLC
To: INTELLECTUAL VENTURES ASSETS 191 LLC
Reel/Frame 063155/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 12, 2023
From: RATEZE REMOTE MGMT. L.L.C.
To: INTELLECTUAL VENTURES ASSETS 191 LLC
Reel/Frame 062666/0696 →
MERGER Recorded Nov 24, 2015
From: DEVEREUX RESEARCH AB LLC
To: RATEZE REMOTE MGMT. L.L.C.
Reel/Frame 037131/0942 →
CORRECTIVE CHANGE OF NAME, SUBMITTING OMITTED DOCUMENTS PREVIOUSLY RECORDED ON REEL: 019805 AND FRAME: 0296 Recorded Mar 8, 2012
From: CONVOQ, INC.
To: ZINGDOM COMMUNICATIONS, INC.
Reel/Frame 027831/0293 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 26, 2008
From: ZINGDOM COMMUNICATIONS, INC.
To: DEVEREUX RESEARCH AB LLC
Reel/Frame 021147/0717 →
CORRECTION TO PREVIOUSLY RECORDED REEL 019649 FRAME 0152 Recorded Sep 10, 2007
From: CONVOQ, INC.
To: ZINGDOM COMMUNICATIONS, INC.
Reel/Frame 019805/0296 →
CHANGE OF NAME Recorded Aug 3, 2007
From: CONVOQ, INC.
To: ZINGDOM COMMUNICATIONS, INC.
Reel/Frame 019649/0152 →
CHANGE OF NAME Recorded Dec 5, 2003
From: APPLIED MESSAGING CORPORATION
To: CONVOQ, INC.
Reel/Frame 014759/0321 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2003
From: DIGATE, CHARLES J.; HEROT, CHRISTOPHER F.; KETUDAT, TONYTIP; KOPIKIS, ALEXIS M.
To: APPLIED MESSAGING CORPORATION
Reel/Frame 014063/0626 →