IP Library Granted Patent US 8,600,794
Granted Patent B2
US 8,600,794 · App. 11/396,175 · Granted Dec 3, 2013

Meeting notification and merging agents

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 8,600,794
App. No.
11/396,175
Granted
Dec 3, 2013
Kind
B2
Abstract

The present invention is directed generally to an information manager that identifies currently scheduled meetings satisfying selected search parameters, discloses, when permitted, details of the identified meetings to requestors, and merges requested and existing meetings when appropriate.

Claims (58)

1. A method, comprising:

(a) receiving a request, at a server, from a requestor to participate in a meeting with one or more of a specified plurality of participants about a selected matter, the requestor being a person;

(b) determining, based on a comparison to one or more other scheduled meetings, that a meeting is currently scheduled for the one or more of the specified plurality of participants and that a currently scheduled meeting is for the selected matter based on one or more of a common subject, agenda item, or attachment, wherein the comparison is based on a structured query of a subscriber database using, in one or more search fields, a subset of meeting information received in the request, the subset of meeting information being defined in a set of rules that define what degree of similarity is needed between the selected matter and the one or more other scheduled meetings; and

(c) before performing a meeting merger step, performing, by the server, one or more of the following steps:

(c1) notifying the requestor of at least one of the existence and details of the currently scheduled meeting, wherein notification of the requestor of the at least one of the existence and details depends on one or more of (i) an authority level of the requestor, wherein an authentication procedure is executed in which the requestor is asked to provide a password before the requestor is notified of the at least one of the existence and details of the currently scheduled meeting, and (ii) a stipulated level of restriction by a meeting organizer; and

(c2) forwarding a meeting merger invitation to the requestor to merge the requested meeting with the currently scheduled meeting, wherein the invitation is a graphical user interface presented to the requestor which includes a participant field, a scheduled at field, a location field, subject matter of matching meeting information, other information regarding the matching meeting information and user selectable icons for approving or rejecting the meeting merger invitation;

(d) receiving, from the requestor and the one or more of the plurality of participants, indications approving a meeting merger between the requested meeting and the currently scheduled meeting; and

(e) merging, by the server, based on the approving indications, the requested meeting and the currently scheduled meeting resulting in a merged meeting.

2. The method of claim 1 , wherein step (c1) is performed and further comprising:

(f) determining that the currently scheduled meeting is at least partially restricted and wherein step (c1) comprises the sub steps of:

determining that the currently scheduled meeting is at least partially restricted, and notifying the requestor of the existence of the currently scheduled meeting but not details regarding the meeting.

3. The method of claim 2 , wherein step (c1) comprises the sub steps of:

determining that the currently scheduled meeting is fully restricted, and not notifying the requestor of the existence of the currently scheduled meeting.

4. The method of claim 2 , wherein step (c1) comprises the sub steps of:

determining that the currently scheduled meeting is open, and notifying the requestor of the existence and details of the currently scheduled meeting.

5. The method of claim 1 , wherein step (c1) is performed, wherein the currently scheduled meeting is at least partially restricted, and further comprising:

(a) determining whether the requestor is authorized to receive the meeting notification; and wherein step (c1) comprises the sub steps of:

when the requester is authorized to receive the meeting notification, performing step (c1); and

when the requester is unauthorized to receive the meeting notification, not performing step (c1).

6. The method of claim 1 , wherein step (c1) is performed and further comprising:

(b) determining that the currently scheduled meeting is at least partially restricted

and notifying at least some of the participants of the currently scheduled meeting of the request seeking permission to provide to the requestor meeting information, which the requestor is otherwise not entitled to receive.

7. The method of claim 1 , wherein step (c2) is performed and further comprising:

determining that the currently scheduled meeting and requested meeting are substantially similar, wherein step (c2) is performed when the meetings are substantially similar based on the rules that define a degree of similarity needed to match the currently scheduled meeting and the requested meeting.

8. An information manager, comprising:

a server, wherein the server includes:

(a) a calendar module operable to maintain scheduling information for meetings involving at least one subscriber;

(b) a messaging module operable to send and receive electronic messages; and

(c) a meeting notification agent operable to:

(c1) receive a request from a requestor, the requestor being a person, to identify a currently scheduled meeting matching a set of selected parameters;

(c2) determine, based on a comparison to one or more other scheduled meetings, that a meeting matching the set of selected parameters exists wherein the matching matches one or more participants and one or more of a common subject, agenda item or attachment, wherein the matching is based on a structured query of a subscriber database using, in one or more search fields, a subset of meeting information received in the request, the subset of meeting information being defined in a set of rules that define what degree of similarity is needed between the set of selected parameters and the one or more other scheduled meetings;

(c3) determine that selected information regarding the matching meeting may be disclosed to the requestor, wherein the determination (c3) is based on one or more of (i) an authority level of the requestor, wherein an authentication procedure is executed in which the requestor is asked to provide a password before the meeting details will be disclosed to the requestor, and (ii) a stipulated level of restriction by a meeting organizer; and

(c4) before the merger agent performs a step of merging meetings, notifying the requestor of the selected information;

(d) a merger agent that cooperates with the processor, the merger agent receives, from the requestor and one or more of a plurality of participants, indications approving a meeting merger between a requested meeting and the currently scheduled meeting and the processor merges, based on the approving indications, the requested meeting and the currently scheduled meeting resulting in a merged meeting.

9. The manager of claim 8 , wherein the set of selected parameters comprises at least one of a set of participant identities, a time period during which eligible meetings are scheduled, a subject of the meeting, one or more agenda items for the meeting, an attachment for the meeting, a duration of the meeting, contact details for the meeting, and physical location.

10. The manager of claim 8 , wherein operation (c3) comprises the sub-operation of determining that disclosure of information regarding the matching meeting has been restricted by at least one of the participants of the matching meeting.

11. The manager of claim 8 , wherein operation (c3) comprises the sub-operation of determining that the requestor is authorized to receive information regarding the matching meeting.

12. The manager of claim 8 , wherein the request comprises a set of search fields corresponding to the set of selected parameters and a set of update fields providing desired changes to any matching meeting.

13. The manager of claim 8 , wherein, determining that the matching meeting is partially restricted, and disclosing to the requestor the selected information comprising the existence of the meeting but excluding at least a plurality of the set of matching meeting participants, the scheduled time for the matching meeting, the subject matter of the matching meeting, and the location of the matching meeting.

14. The manager of claim 8 , wherein, determining that the matching meeting is fully restricted and not disclosing the selected information to a requestor.

15. An information manager, comprising:

a server, wherein the server includes:

(a) a calendar module, associated with a server, operable to maintain scheduling information for meetings involving at least one subscriber;

(b) a messaging module operable to send and receive electronic messages; and

(c) a meeting merge agent running on the server that is operable to:

(c1) receive a request from a requestor, the requestor being a person, to participate in a meeting about a selected matter;

(c2) determine, based on a comparison to one or more other scheduled meetings, that a currently scheduled meeting is sufficiently similar to the meeting identified in the request based on matching one or more participants and the selected matter based on one or more of a common subject, agenda item, or attachment, wherein the comparison is based on a structured query of a subscriber database using, in one or more search fields, a subset of meeting information received in the request, the subset of information being defined in a set of rules that define what degree of similarity is sufficient to match the selected matter and the one or more other scheduled meetings; and

(c3) before merging meetings, providing a meeting merge request to at least one of the requestor and a participant of the currently scheduled meeting seeking permission to merge the identified meeting and the currently scheduled meeting, wherein the meeting merge request is a graphical user interface which includes a participant field, a scheduled at field, a location field, subject matter of the matching meeting information, other information regarding the matching meeting information and user selectable icons for approving or rejecting the meeting merge request;

(c4) receive, from the requestor and one or more participants, indications approving a meeting merger between the requested meeting and the currently scheduled meeting; and

(c5) merge, by the meeting merge agent, based on the approving indications, the requested meeting and the currently scheduled meeting resulting in a merged meeting.

16. The manager of claim 15 , wherein the merge agent is operable to form a subset of the meeting information contained in the request, the subset defining when a currently scheduled meeting is substantially similar to the identified meeting based on a set of rules that define what degree of similarity is sufficient to match the selected matter and the one or more other scheduled meetings, and is used to search for a currently scheduled meeting.

17. The manager of claim 15 , wherein, when the meetings are merged, at least one of the following is true: a start time for the merged meeting is a start time of at least one of the currently scheduled and identified meetings, a duration of the merged meeting is a sum of durations of the currently scheduled and identified meetings, a set of participants of the merged meeting comprises participants of the currently scheduled and identified meetings, and an agenda for the merged meeting comprises items in agendas for the currently scheduled and identified meetings.

18. The manager of claim 15 , further comprising:

(d) a meeting notification agent operable to:

(d1) receive a second request from a second requestor to identify a currently scheduled meeting matching a set of selected search parameters;

(d2) determining that a meeting matching the set of selected search parameters exists based on the currently scheduled meeting matching the set of selected search parameters;

(d3) determining that selected information regarding the meeting may be disclosed to the second requestor; and

(d4) notifying the second requestor of the selected information.

Assignments (25)
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
BANKRUPTCY COURT ORDER RELEASING THE SECURITY INTEREST RECORDED AT REEL/FRAME 020156/0149 Recorded Jul 25, 2022
From: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
To: AVAYA, INC.; AVAYA TECHNOLOGY LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES
Reel/Frame 060953/0412 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
RELEASE OF SECURITY INTEREST Recorded Jan 9, 2018
From: CITICORP USA, INC.
To: AVAYA, INC.; SIERRA HOLDINGS CORP.; AVAYA TECHNOLOGY, LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
Reel/Frame 045032/0213 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 029608/0256 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 044891/0801 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST, NA
To: AVAYA INC.
Reel/Frame 044892/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Mar 13, 2013
From: AVAYA, INC.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE
Reel/Frame 030083/0639 →
SECURITY AGREEMENT Recorded Jan 10, 2013
From: AVAYA, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 029608/0256 →
SECURITY AGREEMENT Recorded Feb 22, 2011
From: AVAYA INC., A DELAWARE CORPORATION
To: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE
Reel/Frame 025863/0535 →
REASSIGNMENT Recorded Jun 26, 2008
From: AVAYA TECHNOLOGY LLC
To: AVAYA INC
Reel/Frame 021156/0689 →
SECURITY AGREEMENT Recorded Nov 28, 2007
From: AVAYA, INC.; AVAYA TECHNOLOGY LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
To: CITICORP USA, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 020166/0705 →
SECURITY AGREEMENT Recorded Nov 27, 2007
From: AVAYA, INC.; AVAYA TECHNOLOGY LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 020156/0149 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 18, 2006
From: BLAIR, COLIN; MICHAELIS, PAUL ROLLER; WAN, JAMES K.
To: AVAYA TECHNOLOGY LLC
Reel/Frame 017487/0264 →