IP Library Granted Patent US 10,510,026
Granted Patent B1
US 10,510,026 · App. 15/136,779 · Granted Dec 17, 2019

Electronic calendaring system and method determining redundant meeting invitees based on a meeting composition score

Inventors: Dal Adamson (Salt Lake City, UT); Ron Ross (Salt Lake City, UT); Zachary Dean Holmquist (Salt Lake City, UT); Joe Reis (Salt Lake City, UT); Ken Myers (Salt Lake City, UT); Dylan Gregersen (Salt Lake City, UT)
Assignee: WeWork Companies Inc.
G06Q10/06311G06F9/543G06N20/00
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 10,510,026
App. No.
15/136,779
Granted
Dec 17, 2019
Kind
B1
Abstract

This disclosure describes, according to some implementations, a method for scoring electronic meeting requests for attendee redundancy. In an example method, the method includes retrieving, using one or more processors, user IDs of meeting attendees; retrieving, using the one or more processors, one or more characteristics associated with the user IDs; retrieving, using the one or more processors, a rule having one or more parameters for scoring meeting composition; comparing, using the one or more processors, the one or more characteristics associated with the user IDs based on the one or more parameters of the rule; and generating, using the one or more processors, a meeting score based on the comparison.

Claims (82)

1. A computer-implemented method for determining redundancy in a meeting, the method comprising:

exposing, at a first computing system having one or more processors, access via a computer network to a scheduling application program interface (API) for scheduling meetings;

receiving, at the first computing system via the computer network, a meeting request from a second computing system associated with a meeting organizer via the API, the meeting request being a request to schedule the meeting at a particular time and place;

scheduling the meeting based on the meeting request by at least storing a corresponding data entry in a meeting data store;

tracking attendance confirmation transmitted via the computer network from third computing systems associated with attendees of the meeting, the attendance confirmation including user IDs respectively associated with the attendees;

retrieving characteristics associated with the user IDs from a user data store;

determining, using the one or more processors, a meeting purpose;

based on the meeting purpose, retrieving from a rule data store a rule having one or more parameters for scoring meeting composition;

comparing, using the one or more processors, the characteristics associated with the user IDs using the one or more parameters of the rule, wherein one of the characteristics is a domain category, and wherein comparing the characteristics using the one or more parameters of the rule comprises determining whether a quantity of similar domain categories exceeds the one or more parameters;

generating, using the one or more processors, a meeting composition score based on the comparison;

identifying, using the one or more processors, redundant user IDs included in the meeting using the meeting composition score;

causing to be provided, in a graphical user interface of the second computing system, an indication of the identified redundant user IDs included in the meeting; and

causing to be provided, in graphical user interfaces of the third computing systems, an opt-out function to one or more users associated with the redundant user IDs.

2. The method of claim 1 , wherein determining the meeting purpose further comprises:

identifying, using the one or more processors, a meeting objective included in the meeting request; and

determining, using the one or more processors, a rule related to the meeting objective.

3. The method of claim 1 , further comprising:

comparing, using the one or more processors, the meeting composition score to a previously generated meeting composition score; and

determining, using the one or more processors, an insight based on the comparison.

4. The method of claim 3 , wherein the insight is one of a cost, a frequency, and a domain.

5. A computer-implemented method for scoring a composition of a meeting, the method comprising:

exposing, at a first computing system having one or more processors, access via a computer network to a scheduling application program interface (API) for scheduling meetings;

receiving, at the first computing system via the computer network, a meeting request from a second computing system associated with a meeting organizer via the API, the meeting request being a request to schedule the meeting at a particular time and place;

scheduling the meeting based on the meeting request;

retrieving user IDs of meeting attendees;

retrieving one or more characteristics associated with the user IDs;

retrieving a rule having one or more parameters for scoring meeting composition;

comparing, using the one or more processors, the one or more retrieved characteristics associated with the user IDs based on the one or more parameters of the rule, wherein one of the characteristics is a domain category, and wherein comparing the characteristics based on the one or more parameters of the rule comprises determining whether the domain category satisfies the one or more parameters;

generating, using the one or more processors, a meeting score based on the comparison;

identifying, using the one or more processors, redundant user IDs included in the meeting using the meeting score;

causing to be provided, in a graphical user interface of the second computing system, an indication of the identified redundant user IDs included in the meeting; and

causing to be provided, in graphical user interfaces of third computing systems, an opt-out function to one or more users associated with the redundant user IDs.

6. The method of claim 5 , wherein generating the meeting score is performed as part of scheduling the meeting and wherein retrieving user IDs of meeting attendees further comprises:

receiving the meeting request including the user IDs.

7. The method of claim 5 , wherein retrieving the rule further comprises:

identifying, using the one or more processors, a meeting objective; and

determining, using the one or more processors, the rule based on the meeting objective.

8. The method of claim 5 , further comprising:

comparing, using the one or more processors, the meeting score to a previously generated meeting score; and

determining, using the one or more processors, an insight based on the comparison.

9. The method of claim 5 , further comprising:

providing the indication of the identified redundant user IDs included in the meeting attendees.

10. The method of claim 9 , further comprising:

providing the opt-out function to the one or more users associated with the redundant user IDs.

11. A system comprising:

one or more computer processors; and

one or more memories storing instructions that, when executed by the one or more processors, cause the system to perform operations including:

exposing, at a first computing system having one or more processors, access via a computer network to a scheduling application program interface (API) for scheduling meetings;

receiving, at the first computing system via the computer network, a meeting request from a second computing system associated with a meeting organizer via the API, the meeting request being a request to schedule a meeting at a particular time and place;

scheduling the meeting based on the meeting request;

retrieving user IDs of meeting attendees;

retrieving one or more characteristics associated with the user IDs;

retrieving a rule having one or more parameters for scoring meeting composition;

comparing the one or more retrieved characteristics associated with the user IDs based on the one or more parameters of the rule, wherein one of the characteristics is a domain category, and wherein comparing the characteristics based on the one or more parameters of the rule comprises determining whether the domain category satisfies the one or more parameters; and

generating a meeting score based on the comparison;

identifying redundant user IDs included in the meeting using the meeting score; and

causing to be provided, in a graphical user interface of the second computing system, an indication of the identified redundant user IDs included in the meeting; and

causing to be provided, in graphical user interfaces, an opt-out function to one or more users associated with the redundant user IDs.

12. The system of claim 11 , wherein generating the meeting score is performed as part of scheduling the meeting and wherein retrieving user IDs of meeting attendees further comprises:

receiving the meeting request including the user IDs.

13. The system of claim 11 , wherein retrieving the rule further comprises:

identifying a meeting objective; and

determining the rule based on the meeting objective.

14. The system of claim 11 , further comprising:

comparing the meeting score to a previously generated meeting score; and

determining an insight based on the comparison.

15. The system of claim 11 , further comprising:

providing the indication of the identified redundant user IDs included in the meeting attendees.

16. The system of claim 15 , further comprising:

providing the opt-out function to the one or more users associated with the redundant user IDs.

17. One or more instances of computer-readable media collectively having contents configured to cause a input system to perform a method, the method comprising:

exposing, at a first computing system having one or more processors, access via a computer network to a scheduling application program interface (API) for scheduling meetings;

receiving, at the first computing system via the computer network, a meeting request from a second computing system associated with a meeting organizer via the API, the meeting request being a request to schedule a meeting at a particular time and place;

scheduling the meeting based on the meeting request;

retrieving user IDs of meeting attendees;

retrieving one or more characteristics associated with the user IDs;

retrieving a rule having one or more parameters for scoring meeting composition;

comparing, using the one or more processors, the one or more retrieved characteristics associated with the user IDs based on the one or more parameters of the rule, wherein one of the characteristics is a domain category, and wherein comparing the characteristics based on the one or more parameters of the rule comprises determining whether a quantity of similar domain categories exceeds the one or more parameters;

generating, using the one or more processors, a meeting score based on the comparison;

identifying, using the one or more processors, redundant user IDs included in the meeting using the meeting score;

causing to be provided, in a graphical user interface of the second computing system, an indication of the identified redundant user IDs included in the meeting; and

causing to be provided an opt-out function to one or more users associated with the redundant user IDs.

Assignments (18)
MERGER AND CHANGE OF NAME Recorded Jun 25, 2025
From: TEEM TECHNOLOGIES LLC; EPTURA, INC.
To: EPTURA, INC.
Reel/Frame 071514/0396 →
SECURITY INTEREST Recorded Oct 3, 2022
From: SPACEIQ LLC; TEEM TECHNOLOGIES LLC
To: GOLDMAN SACHS PRIVATE MIDDLE MARKET CREDIT II LLC
Reel/Frame 061294/0644 →
RELEASE OF SECURITY INTEREST Recorded Sep 30, 2022
From: GOLDMAN SACHS BDC, INC., AS COLLATERAL AGENT
To: TEEM TECHNOLOGIES LLC
Reel/Frame 061277/0552 →
RELEASE OF SECURITY INTEREST Recorded Jul 7, 2021
From: CRESTLINE DIRECT FINANCE, L.P.
To: TEEM TECHNOLOGIES LLC
Reel/Frame 056778/0654 →
GRANT OF SECURITY INTEREST IN PATENT RIGHTS Recorded Jul 1, 2021
From: TEEM TECHNOLOGIES LLC
To: GOLDMAN SACHS BDC, INC., AS COLLATERAL AGENT
Reel/Frame 056806/0049 →
SECURITY INTEREST Recorded Jan 24, 2020
From: TEEM TECHNOLOGIES LLC
To: CRESTLINE DIRECT FINANCE, L.P., AS COLLATERAL AGENT
Reel/Frame 051614/0806 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 22, 2020
From: WEWORK COMPANIES LLC
To: TEEM TECHNOLOGIES LLC
Reel/Frame 051582/0643 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 22, 2020
From: THE WE COMPANY MC LLC
To: WEWORK COMPANIES LLC
Reel/Frame 051582/0553 →
RELEASE OF SECURITY INTEREST IN CERTAIN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (050724/0631) Recorded Jan 10, 2020
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: TEEM TECHNOLOGIES LLC
Reel/Frame 051563/0042 →
MERGER AND CHANGE OF NAME Recorded Jan 10, 2020
From: WEWORK COMPANIES INC.; THE WE COMPANY MC LLC
To: THE WE COMPANY MC LLC
Reel/Frame 051477/0649 →
RELEASE OF SECURITY INTEREST IN CERTAIN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (050724/0643) Recorded Jan 10, 2020
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: TEEM TECHNOLOGIES LLC
Reel/Frame 051733/0556 →
SECURITY INTEREST (LETTER OF CREDIT) Recorded Oct 15, 2019
From: WEWORK COMPANIES LLC; MEETUP LLC; CONDUCTOR LLC; EUCLID LLC; TEEM TECHNOLOGIES LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 050724/0643 →
SECURITY INTEREST (REVOLVER) Recorded Oct 15, 2019
From: WEWORK COMPANIES LLC; MEETUP LLC; CONDUCTOR LLC; EUCLID LLC; TEEM TECHNOLOGIES LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 050724/0631 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 17, 2019
From: TEEM TECHNOLOGIES, INC.
To: WEWORK COMPANIES INC.
Reel/Frame 049784/0337 →
CORRECTIVE ASSIGNMENT TO CORRECT THE STATE/COUNTRY OF THE RECEIVING PARTY FROM UGANDA PREVIOUSLY RECORDED ON REEL 041556 FRAME 0254. ASSIGNOR(S) HEREBY CONFIRMS THE STATE/COUNTRY OF THE RECEIVING PARTY SHOULD CORRECTLY READ UTAH. Recorded Mar 17, 2017
From: ENDER LABS, INC.
To: TEEM TECHNOLOGIES, INC.
Reel/Frame 042035/0625 →
CHANGE OF NAME Recorded Jan 30, 2017
From: ENDER LABS, INC.
To: TEEM TECHNOLOGIES, INC.
Reel/Frame 041556/0254 →
CHANGE OF NAME Recorded Oct 17, 2016
From: ENDER LABS INC.
To: TEEM TECHNOLOGIES, INC.
Reel/Frame 040383/0329 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 6, 2016
From: ADAMSON, DAL; ROSS, RON; HOLMQUIST, ZACH; REIS, JOE; MYERS, KEN; GREGERSEN, DYLAN
To: ENDER LABS, INC. D/B/A EVENTBOARD
Reel/Frame 038819/0396 →
Continuity (1)
Provisional Application 62236889 · Oct 3, 2015
Cited By (4)
US 12,314,876 US 12,373,745 US 12,511,296 US 12,579,488