Inferring meeting expense via a meeting expense and verification controller

US12229730B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12229730-B2
Application numberUS-202117180604-A
CountryUS
Kind codeB2
Filing dateFeb 19, 2021
Priority dateFeb 19, 2021
Publication dateFeb 18, 2025
Grant dateFeb 18, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

This disclosure describes techniques that enable a Meeting Expense and Verification (MEV) controller to infer the meeting expense of a proposed meeting. The MEV controller may analyze a meeting request to identify meeting attendees, and in doing so, determine the meeting expense. In response to the meeting expense being greater than a predetermined meeting expense threshold, the MEV controller may suspend the meeting request.

First claim

Opening claim text (preview).

What is claimed: 1. A system, comprising: one or more processors; and memory coupled to the one or more processors, the memory including one or more modules that are executable by the one or more processors to perform operations to infer a meeting expense for a proposed meeting, calculate an actual meeting expense for an actual meeting, and recommend a change in meeting format, the operations to infer a meeting expense comprising: intercepting, from a scheduler device, a meeting request for a proposed meeting of in-person meeting attendees at a first meeting location, wherein the first meeting location is a geolocation; inferring a meeting expense for the proposed meeting based at least in part on the meeting request, wherein an inferring of the meeting expense includes: determining time lost due to travel of the in-person meeting attendees to the first meeting location that contributes to lost work time (LWT) values of the in-person meeting attendees, the determining the time lost being performed at least using one or more trained machine-learning algorithms to infer a start location of each individual in-person meeting attendee, the machine-learning algorithms having been trained on historical calendar data of the each individual in-person meeting attendee and environmental factors that historically impact meeting at the first meeting location; and in response to the inferred meeting expense being greater than a predetermined meeting expense threshold, suspending the meeting request, and the operations to calculate an actual meeting expense for an actual meeting comprising: for in-person meeting attendees attending the actual meeting at a meeting site: interacting with sensors located at the meeting site to capture sensor data that includes video from the in-person meeting attendees during the meeting; analyzing the sensor data, including comparing the sensor data to biometric profile data of the in-person meeting attendees, to identify in-person meeting attendees based on the comparison; and determining an actual expense of the identified in-person meeting attendees based on their respective LWT values; for virtual meeting attendees attending the meeting virtually via a virtual meeting platform: interacting with the virtual meeting platform to capture attendance data that comprises Internet Protocol (IP) addresses associated with the virtual meeting attendees; identifying the virtual meeting attendees from the IP addresses in the attendance data; determining, based on historical profile data of the virtual meeting attendees identified in the attendance data, an expense of setting up the virtual meeting at a second meeting location for the virtual meeting attendees that contributes to LWT values of the virtual meeting attendees; and determining an actual expense of the virtual meeting attendees based on their respective LWT values; and calculating the actual meeting expense by aggregating the actual expense of the in-person meeting attendees and the actual expense of the virtual meeting attendees; and the operations to recommend a change in meeting format comprising: sensing virtual meeting connectivity of the virtual meeting attendees to the actual meeting; receiving telemetry data that indicates Quality of Service (QOS) of the virtual meeting connectivity; and recommending a change in meeting format from a virtual meeting to an in-person meeting for at least a subset of the virtual meeting attendees based on the telemetry data indicating that virtual meeting connectivity for the at least a subset of the virtual meeting attendees is below a predetermined QoS threshold. 2. The system of claim 1 , wherein the one or more modules are further executable by the one or more processors to: retrieve, from an enterprise server, the biometric profile data associated with individual in-person meeting attendees. 3. The system of claim 1 , wherein the proposed meeting is scheduled to occur at a proposed meeting time, and wherein the one or more modules are further executable by the one or more processors to: retrieve, from an enterprise server, an individual profile associated with a particular in-person meeting attendee of the proposed meeting; determine an individual LWT value associated with the particular in-person meeting attendee at the proposed meeting time; and in response to the individual LWT value being greater than the predetermined meeting expense threshold, determine an alternate meeting time to replace the proposed meeting time, based at least in part on the individual LWT value. 4. The system of claim 3 , wherein the one or more modules are further executable by the one or more processors to: retrieve, from the enterprise server, historical device usage data associated with the particular in-person meeting attendee over a predetermined time interval; analyze the historical device usage data to assign an effective worktime value to workday time increments; and generate a data profile for the particular in-person meeting attendee, based at least in part on the worktime value assigned to the workday time increments, wherein to determine the alternate meeting time is further based at least in part on the data profile. 5. The system of claim 4 , wherein the one or more modules are further executable by the one or more processors to: determine the alternate meeting time to occur during a workday time increment with an assigned worktime value that is less than or equal to remaining workday time increments. 6. The system of claim 1 , wherein the one or more modules are further executable by the one or more processors to: retrieve, from an enterprise server, a meeting attendee profile associated with a particular in-person meeting attendee of the proposed meeting; determine an expense projection associated with the particular in-person meeting attendee at a proposed meeting time of the proposed meeting; and based on the expense projection being greater than the predetermined meeting expense threshold, identify an alternate meeting attendee to attend the proposed meeting in place of the particular in-person meeting attendee. 7. The system of claim 6 , wherein the one or more modules are further executable by the one or more processors to: analyze the meeting attendee profile to identify a plurality of supervised individuals that report to the particular in-person meeting attendee; and determine an alternate expense projection for individual ones of the plurality of supervised individuals, wherein the alternate meeting attendee corresponds to one of the plurality of supervised individuals, based at least in part on the alternate expense projection. 8. The system of claim 1 , wherein the one or more modules are further executable by the one or more processors to: retrieve, from an enterprise server, a meeting attendee profile associated with a particular in-person meeting attendee of the proposed meeting; parse the meeting request to identify a meeting subject-matter; analyze the meeting attendee profile to identify a workgroup related to the meeting subject-matter; and identify a plurality of members of the workgroup to attend the proposed meeting as alternate meeting attendees, based at least in part on the meeting subject-matter. 9. The system of claim 8 , wherein the one or more modules are further executable by the one or more processors to: determine an alternate expense projection for individual ones of the plurality of members, and wherein, the alternate meeting attendee corresponds to one of the plurality of members, based at least in part on the alternate expense projection. 10. The system of claim 1 , wherein the environmental factors include at

Assignees

Inventors

Classifications

  • Calendar-based scheduling for persons or groups · CPC title

  • Price estimation or determination · CPC title

  • Physics · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12229730B2 cover?
This disclosure describes techniques that enable a Meeting Expense and Verification (MEV) controller to infer the meeting expense of a proposed meeting. The MEV controller may analyze a meeting request to identify meeting attendees, and in doing so, determine the meeting expense. In response to the meeting expense being greater than a predetermined meeting expense threshold, the MEV controller …
Who is the assignee on this patent?
T Mobile Usa Inc
What technology area does this patent fall under?
Primary CPC classification G06Q10/1093. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 18 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 10 related publications on this page (citations in our corpus or others sharing the same primary CPC).