IP Library Granted Patent US 12,652,183
Granted Patent B2
US 12,652,183 · App. 18/348,310 · Granted Jun 9, 2026

Auto-generated collaborative components for collaboration object

Inventors: Shiraz J. Cupala (Snohomish, WA); Daniel Gabriel Zarzar (Austin, TX); Daniel P. Costenaro (Kirkland, WA)
Assignee: Microsoft Technology Licensing, LLC
H04L12/1818H04L12/1831
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 12,652,183
App. No.
18/348,310
Granted
Jun 9, 2026
Kind
B2
Abstract

Systems and methods for generating a collaboration object are provided. In particular, a computing device may detect an intent to generate a meeting invitation for a meeting by a meeting organizer via a first application, provide a meeting invitation template including one or more collaborative components, receive a first set of collaborative components, cause the meeting invitation to be sent to at least one invitee via the first application, in response to causing the meeting invitation to be sent to at least one invitee, generate the collaboration object associated with the meeting based on the first set of collaborative components, determine one or more additional collaborative components from the plurality of collaborative components that are relevant to the meeting, and update the collaboration object to include the one or more additional collaborative components.

Claims (68)

1 . A method for generating a collaboration object, the method comprising:

detecting an indication to generate a meeting invitation for a meeting by a meeting organizer via a first application;

generating, by the first application, the meeting invitation based on a meeting invitation template to include a selected collaborative component, the collaborative component providing functionality for concurrent multi-user interaction in near-real time;

causing the meeting invitation to be sent to at least one invitee via the first application;

in response to causing the meeting invitation to be sent to at least one invitee, generating the collaboration object associated with the meeting based on the selected collaborative component; and

as a result of a change to the collaboration object by the at least one invitee via a second application, displaying, in near real-time, the change within the meeting invitation via the first application.

2 . The method of claim 1 , wherein generating the meeting invitation comprises updating the meeting invitation template to populate the selected collaborative component for receiving content.

3 . The method of claim 1 , wherein the collaboration object comprises pointers to the selected collaborative component, an additional collaborative component associated with the collaboration object after generation of the meeting invite, and content associated with the meeting.

4 . The method of claim 3 , wherein the additional collaborative component is determined from a plurality of collaborative components based on temporal factors and/or contextual factors using a generative machine learning model.

5 . The method of claim 4 , wherein the temporal factors include whether the determination of the additional collaborative component is being made before, during, or after the meeting, and the contextual factors include a type of application or a type of the meeting.

6 . The method of claim 3 , wherein the additional collaborative component is determined from a plurality of collaborative components based on relevance to the meeting using a heuristic technique.

7 . The method of claim 5 , wherein using the generative machine learning model includes:

determining one or more contents that have been shared between the meeting organizer and the at least one invitee that are relevant to the meeting; and

determining the additional collaborative component from the plurality of collaborative components based on the one or more contents.

8 . The method of claim 1 , further comprising:

receiving an indication to join the meeting via a third application;

determining a second set of collaborative components that are deemed relevant based on temporal factors and/or contextual factors;

retrieving the second set of collaborative components and metadata from the collaboration object; and

rendering a collaborative user experience (UX) comprising the second set of collaborative components based on the metadata via the third application,

wherein the temporal factors include whether the determination of the second set of collaborative components to be retrieved are being made before, during, or after the meeting, and the contextual factors include a type of application or a type of the meeting.

9 . The method of claim 8 , further comprising:

receiving user input to the second set of collaborative components by a first participant at a first user device;

automatically causing the user input to the second set of collaborative components to be reflected in near real-time at a second user device associated with a second participant; and

persisting the collaboration object to enable concurrent multi-user interaction with the second set of collaborative components after the collaboration.

10 . The method of claim 8 , further comprising:

detecting content shared by a second participant during the collaboration; and

automatically causing the shared content to be associated with the collaboration object.

11 . A computing device for generating a collaboration object, the computing device comprising:

a processor; and

a memory having a plurality of instructions stored thereon that, when executed by the processor, causes the computing device to:

detect an indication to generate a meeting invitation for a meeting by a meeting organizer via a first application;

generating the meeting invitation based on a meeting invitation template to include a selected first set of collaborative components from a plurality of collaborative components, wherein each collaborative component of the plurality of collaborative components provides functionality for concurrent multi-user interaction in near real-time;

cause the meeting invitation to be sent to at least one invitee via the first application;

in response to the meeting invitation being sent to at least one invitee, generate the collaboration object associated with the meeting based on the first set of collaborative components; and

as a result of a change to the collaboration object by the at least one invitee via a second application, displaying, in near real-time, the change within the meeting invitation via the first application.

12 . The computing device of claim 11 , wherein the collaboration object comprises pointers to the first set of collaborative components, additional collaborative components, and its content associated with the meeting.

13 . The computing device of claim 11 , wherein the one or more additional collaborative components are determined from the plurality of collaborative components by using a generative machine learning model to:

determine one or more contents that have been shared between the meeting organizer and the at least one invitee that are relevant to the meeting; and

determine the one or more additional collaborative components from the plurality of collaborative components based on the one or more contents.

14 . The computing device of claim 11 , wherein the one or more additional collaborative components are determined from the plurality of collaborative components by using a generative machine learning model includes to:

determine one or more additional collaborative components that are relevant to the meeting based on temporal factors and/or contextual factors,

wherein the temporal factors include whether the determination of the one or more additional collaborative components are being made before, during, or after the meeting, and the contextual factors include a type of application, a type of the meeting, or shared contents between the meeting organizer and the at least one invitee.

15 . The computing device of claim 11 , further comprising instructions stored thereon that, when executed by the processor, causes the computing device to:

receive an indication to join the meeting via a third application;

determine a second set of collaborative components that are deemed relevant based on temporal factors and/or contextual factors;

retrieve the second set of collaborative components and metadata from the collaboration object; and

render a collaborative user experience (UX) comprising the second set of collaborative components based on the metadata via the third application,

wherein the temporal factors include whether the determination of the second set of collaborative components to be retrieved are being made before, during, or after the meeting, and the contextual factors include a type of application or a type of the meeting.

16 . The computing device of claim 15 , further comprising instructions stored thereon that, when executed by the processor, causes the computing device to:

receive user input to the second set of collaborative components by a first participant at a first user device;

automatically cause the user input to the second set of collaborative components to be reflected in near real-time at a second user device associated with a second participant; and

persist the collaboration object to enable concurrent multi-user interaction with the second set of collaborative components after the collaboration.

17 . The computing device of claim 15 , further comprising instructions stored thereon that, when executed by the processor, causes the computing device to:

detect content shared by a second participant during the collaboration; and

automatically cause the shared content to be associated with the collaboration object.

18 . A non-transitory computer-readable medium storing instructions for generating a collaboration object, the instructions when executed by one or more processors of a computing device, cause the computing device to perform a method comprising:

detecting an indication to generate a meeting invitation for a meeting via a first application;

generating the meeting invitation based on the meeting invitation template to include one or more collaborative components selected from a plurality of collaborative components, wherein each collaborative component of the plurality of collaborative components provides functionality for concurrent multi-user interaction via the collaborative component and is dynamically updated in near real-time with changes before, during, and after the meeting;

causing the meeting invitation to be sent to at least one invitee via the first application;

in response to the meeting invitation being sent to at least one invitee, generating the collaboration object associated with the meeting based on the one or more selected collaborative components; and

as a result of a change to the collaboration object by the at least one invitee via a second application, displaying, in near real-time, the change within the meeting invitation via the first application.

19 . The non-transitory computer-readable medium of claim 18 , wherein the instructions when executed by the one or more processors further cause the computing device to perform the method comprising:

receiving an indication to join the meeting via a third application;

determining one or more collaborative components that are deemed relevant based on temporal factors and/or contextual factors;

retrieving the one or more relevant collaborative components and metadata from the collaboration object; and

rendering a collaborative user experience (UX) comprising the one or more relevant collaborative components based on the metadata via the third application,

wherein the temporal factors include whether the determination of the one or more relevant collaborative components to be retrieved are being made before, during, or after the meeting, and the contextual factors include a type of application or a type of the meeting.

20 . The non-transitory computer-readable medium of claim 18 , wherein the plurality of collaborative components includes at least one of an agenda collaborative component, a note collaborative component, or an action item collaborative component.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 24, 2023
From: CUPALA, SHIRAZ J.; ZARZAR, DANIEL GABRIEL; COSTENARO, DANIEL P.
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 064363/0046 →
Continuity (2)
Continuation In Part 18144538 · May 8, 2023
Related Publication 20240380626A1 · Nov 14, 2024
References Cited (76)
US 6952660B1 · Matheson · 2005 [cited by applicant]
US 7386535B1 · Kalucha et al. · 2008 [cited by applicant]
US 7958453B1 · Taing · 2011 [cited by applicant]
US 8769012B1 · Shah et al. · 2014 [cited by applicant]
US 9983759B1 · Dhawan et al. · 2018 [cited by applicant]
US 10389769B2 · Gudipaty · 2019 [cited by examiner]
US 11030585B2 · Nelson et al. · 2021 [cited by applicant]
US 11240278B1 · Wang et al. · 2022 [cited by applicant]
US 11501057B2 · Laborczfalvi · 2022 [cited by examiner]
US 11689379B2 · Daredia · 2023 [cited by examiner]
US 11824670B2 · Jin · 2023 [cited by examiner]
US 20030036941A1 · Leska et al. · 2003 [cited by applicant]
US 20030135565A1 · Estrada · 2003 [cited by applicant]
US 20050097440A1 · Lusk et al. · 2005 [cited by applicant]
US 20060010197A1 · Ovenden · 2006 [cited by applicant]
US 20060026502A1 · Dutta · 2006 [cited by applicant]
US 20060242154A1 · Rawat et al. · 2006 [cited by applicant]
US 20060242639A1 · Manion et al. · 2006 [cited by applicant]
US 20090006982A1 · Curtis et al. · 2009 [cited by applicant]
US 20090083637A1 · Skakkebaek et al. · 2009 [cited by applicant]
US 20090222741A1 · Shaw et al. · 2009 [cited by applicant]
US 20110010332A1 · Vasudevan et al. · 2011 [cited by applicant]
US 20110302506A1 · Noyes et al. · 2011 [cited by applicant]
US 20130091205A1 · Kotler et al. · 2013 [cited by applicant]
US 20130191896A1 · Adderly et al. · 2013 [cited by applicant]
US 20140066044A1 · Ramnani et al. · 2014 [cited by applicant]
US 20140082522A1 · Gunderson et al. · 2014 [cited by applicant]
US 20140129639A1 · Burge · 2014 [cited by applicant]
US 20140280463A1 · Hunter et al. · 2014 [cited by applicant]
US 20140310345A1 · Megiddo et al. · 2014 [cited by applicant]
US 20150135094A1 · Donneau-golencer et al. · 2015 [cited by applicant]
US 20150149929A1 · Shepherd et al. · 2015 [cited by applicant]
US 20150156153A1 · Deselaers et al. · 2015 [cited by applicant]
US 20160112476A1 · Gudipaty · 2016 [cited by applicant]
US 20160342571A1 · Voss et al. · 2016 [cited by applicant]
US 20170076046A1 · Barnes et al. · 2017 [cited by applicant]
US 20170163752A1 · Kaledhonkar et al. · 2017 [cited by applicant]
US 20170279859A1 · Pogorelik · 2017 [cited by applicant]
US 20170315974A1 · Kong et al. · 2017 [cited by applicant]
US 20170364866A1 · Steplyk et al. · 2017 [cited by applicant]
US 20180131731A1 · Jones et al. · 2018 [cited by applicant]
US 20180203577A1 · Astavans et al. · 2018 [cited by applicant]
US 20180260790A1 · Connolly · 2018 [cited by examiner]
US 20180336520A1 · Davis et al. · 2018 [cited by applicant]
US 20180337963A1 · Faulkner et al. · 2018 [cited by applicant]
US 20190065450A1 · Bhogal et al. · 2019 [cited by applicant]
US 20190108492A1 · Nelson et al. · 2019 [cited by applicant]
US 20190288968A1 · Chilakamarri et al. · 2019 [cited by applicant]
US 20190312742A1 · Albrecht · 2019 [cited by applicant]
US 20200076634A1 · Akolkar et al. · 2020 [cited by applicant]
US 20200410457A1 · Sexauer et al. · 2020 [cited by applicant]
US 20210168177A1 · Henderson · 2021 [cited by examiner]
US 20210241865A1 · Bhattacharya et al. · 2021 [cited by applicant]
US 20220261760A1 · Cupala et al. · 2022 [cited by applicant]
US 20220263675A1 · Cupala et al. · 2022 [cited by applicant]
US 20230155851A1 · Cupala et al. · 2023 [cited by applicant]
US 20240378566A1 · Cupala · 2024 [cited by applicant]
Notice of Allowance mailed on Jul. 10, 2024, in U.S. Appl. No. 18/154,514, 08 pages. [cited by applicant]
Non-Final Office Action mailed on Mar. 21, 2024, in U.S. Appl. No. 18/154,514, 10 pages. [cited by applicant]
Notice of Allowance mailed on Dec. 18, 2023, in U.S. Appl. No. 17/179,186, 9 pages. [cited by applicant]
“Final Office Action Issued in U.S. Appl. No. 17/179,151”, Mailed Date: Apr. 3, 2023, 26 Pages. [cited by applicant]
“Non Final Office Action Issued in U.S. Appl. No. 17/179,151”, Mailed Date: Dec. 22, 2022, 23 Pages. [cited by applicant]
“Final Office Action Issued in U.S. Appl. No. 17/179,186”, Mailed Date: Mar. 25, 2022, 20 Pages. [cited by applicant]
“Non Final Office Action Issued in U.S. Appl. No. 17/179,186”, Mailed Date: Oct. 1, 2021, 17 Pages. [cited by applicant]
“Notice of Allowance Issued in U.S. Appl. No. 17/179,186”, Mailed Date: Oct. 13, 2022, 16 Pages. [cited by applicant]
Bendel, et al., “WatchMyPhone—Providing Developer Support for Shared User Interface Objects in Collaborative Mobile Applications”, In proceedings of 2012 IEEE International Conference on Pervasive Computing and Communic… [cited by applicant]
“International Search Report and Written Opinion Issued in PCT Application No. PCT/US22/013810”, Mailed Date: Mar. 25, 2022, 12 Pages. [cited by applicant]
“International Search Report and Written Opinion Issued in PCT Application No. PCT/US22/013812”, Mailed Date: Mar. 28, 2022, 12 Pages. [cited by applicant]
“Non Final Office Action Issued in U.S. Appl. No. 17/179,186”, Mailed Date: May 26, 2023, 23 Pages. [cited by applicant]
“Notice of Allowance Issued in U.S. Appl. No. 17/179,151”, Mailed Date: Jul. 31, 2023, 16 Pages. [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/US2024/027329, Jul. 19, 2024, 17 pages. [cited by applicant]
Non-Final Office Action mailed on Aug. 1, 2024, in U.S. Appl. No. 18/144,538, 27 pages. [cited by applicant]
Cho, et al., “Suggestion for Collaboration-Based UI/UX Development Model through Risk Analysis”, Journal of Information Processing Systems, vol. 16, Issue 6, Dec. 31, 2020, pp. 1372-1390. [cited by applicant]
Nguyen, et al., “User Experience in Collaborative Extended Reality: Overview Study”, Virtual Reality and Augmented Reality, Oct. 27, 2020, pp. 41-70. [cited by applicant]
Notice of Allowance mailed on Apr. 15, 2025, in U.S. Appl. No. 18/527,633, 19 pages. [cited by applicant]
International Preliminary Report on Patentability (Chapter I) received for PCT Application No. PCT/US2024/027329, Mailed on Nov. 20, 2025, 12 Pages. [cited by applicant]