DETAILED ACTION
Double Patenting
1. The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp.
Claims 1, 4, 8, 11, 15 and 17 are rejected under the judicially created doctrine of obviousness-type double patenting as being unpatentable over claims 1, 8 and 15 of U.S. Patent No. 11,671,272. When claims in the pending application are broader than the ones in the patent, the broad claims in the pending application are rejected under obviousness type double patenting over previously patented narrow claims, In re Van Ornum and Stang, 214 USPQ 761.
Limitations of the present invention and corresponding U.S. Patent No. 11,671,272 are listed in the following table.
Instant Application: 18/943,214
U.S. Patent No. 11,671,272
1. A method comprising: receiving, by a client device, a request to create a meeting invitation for a meeting and an identification of a suggested application for the meeting; generating a meeting link for the meeting, the meeting link comprising information to connect to the meeting and information identifying the suggested application; creating a meeting invitation based on the request and the meeting link; and transmitting the meeting invitation to one or more invitees to the meeting.
1. A method comprising: receiving, by a video conference provider, a request to schedule a video conference, where the request comprises meeting information and information associated with a suggested application; generating, by the video conference provider a meeting link, the meeting link based on the meeting information and the information associated with the suggested application; and transmitting, by the video conference provider and to one or more client devices, the meeting link, the meeting link configured to cause a video conferencing application to be executed, and the video conferencing application to launch the suggested application.
4. The method of claim 1, further comprising receiving meeting information for the meeting, and wherein generating the meeting link comprises transmitting the meeting information and an identification of the suggested application to a remote server and receiving the meeting link from the remote server.
1. A method comprising: receiving, by a video conference provider, a request to schedule a video conference, where the request comprises meeting information and information associated with a suggested application; generating, by the video conference provider a meeting link, the meeting link based on the meeting information and the information associated with the suggested application; and transmitting, by the video conference provider and to one or more client devices, the meeting link, the meeting link configured to cause a video conferencing application to be executed, and the video conferencing application to launch the suggested application.
8. A system comprising: a non-transitory computer-readable medium; and one or more processors communicatively coupled to the non-transitory computer-readable medium, the processor configured to execute processor-executable instructions stored in the non-transitory computer-readable medium to: receive, by a client device, a request to create a meeting invitation for a meeting and an identification of a suggested application for the meeting; generate a meeting link for the meeting, the meeting link comprising information to connect to the meeting and information identifying the suggested application; create a meeting invitation based on the request and the meeting link; and transmit the meeting invitation to one or more invitees to the meeting.
15. A system comprising: a non-transitory computer-readable medium; and a processor communicatively coupled to the non-transitory computer-readable medium, the processor configured to execute processor-executable instructions stored in the non-transitory computer-readable medium to: receive, by a video conference provider, a request to schedule a video conference, where the request comprises meeting information and information associated with a suggested application; generate, by the video conference provider, a meeting link, the meeting link based on the meeting information and the information associated with the suggested application; and transmit, by the video conference provider, and to one or more client devices, the meeting link, the meeting link configured to cause a video conferencing application to be executed, and the video conferencing application to launch the suggested application.
11. The system of claim 8, wherein the one or more processors configured to execute further processor-executable instructions stored in the non-transitory computer-readable medium to receive meeting information for the meeting, and wherein generating the meeting link comprises transmitting the meeting information and an identification of the suggested application to a remote server and receiving the meeting link from the remote server.
15. A system comprising: a non-transitory computer-readable medium; and a processor communicatively coupled to the non-transitory computer-readable medium, the processor configured to execute processor-executable instructions stored in the non-transitory computer-readable medium to: receive, by a video conference provider, a request to schedule a video conference, where the request comprises meeting information and information associated with a suggested application; generate, by the video conference provider, a meeting link, the meeting link based on the meeting information and the information associated with the suggested application; and transmit, by the video conference provider, and to one or more client devices, the meeting link, the meeting link configured to cause a video conferencing application to be executed, and the video conferencing application to launch the suggested application.
15. A non-transitory computer-readable medium comprising processor-readable instructions configured to be executed by one or more processors, that when executed cause the one or more processors to: receive, by a client device, a request to create a meeting invitation for a meeting and an identification of a suggested application for the meeting; generate a meeting link for the meeting, the meeting link comprising information to connect to the meeting and information identifying the suggested application; create a meeting invitation based on the request and the meeting link; and transmit the meeting invitation to one or more invitees to the meeting.
8. A non-transitory computer-readable medium comprising processor-readable instructions configured to be executed by a processor, that when executed cause the processor to: receive, by a video conference provider, a request to schedule a video conference, where the request comprises meeting information and information associated with a suggested application; generate, by the video conference provider, a meeting link, the meeting link based on the meeting information and the information associated with the suggested application; and transmit, by the video conference provider, and to one or more client devices, the meeting link, the meeting link configured to cause a video conferencing application to be executed, and the video conferencing application to launch the suggested application.
17. The non-transitory computer-readable medium of claim 15, further comprising processor-executable instructions configured to be executed by one or more processors, that when executed cause the one or more processors to receive meeting information for the meeting, and wherein generating the meeting link comprises transmitting the meeting information and an identification of the suggested application to a remote server and receiving the meeting link from the remote server.
8. A non-transitory computer-readable medium comprising processor-readable instructions configured to be executed by a processor, that when executed cause the processor to: receive, by a video conference provider, a request to schedule a video conference, where the request comprises meeting information and information associated with a suggested application; generate, by the video conference provider, a meeting link, the meeting link based on the meeting information and the information associated with the suggested application; and transmit, by the video conference provider, and to one or more client devices, the meeting link, the meeting link configured to cause a video conferencing application to be executed, and the video conferencing application to launch the suggested application.
Claim Rejections - 35 USC § 102
2. The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
3. Claims 1, 8 and 15 are rejected under 35 U.S.C. § 102(a)(2) as being anticipated by DeRosa et al, U.S. Patent Application Publication No. 2015/0163066 (hereinafter DeRosa).
Regarding claim 1, DeRosa discloses a method (from paragraph 0004, see method) comprising:
receiving, by a client device, a request to create a meeting invitation for a meeting (from paragraph 0031, see meeting scheduling function) and an identification of a suggested application (from paragraph 0032, see insert UNICC application-related instructions) for the meeting;
generating a meeting link for the meeting, the meeting link comprising information (from paragraph 0032, see meeting information) to connect to the meeting and information identifying the suggested application (from paragraph 0032, see The UNICC application-related instruction message(s) may include a brief introduction of the UNICC service feature, a web link (e.g., a Universal Resource Locator or URL) to download the UNICC mobile client and an authentication code for the user to activate its UNICC mobile client);
creating a meeting invitation (from paragraph 0033, see meeting invitation) based on the request and the meeting link; and
transmitting the meeting invitation to one or more invitees (from paragraph 0033, see all participants, including internal users and/or external users (via associated external messaging systems) to the meeting.
Regarding claim 8, DeRosa discloses a system (from paragraph 0004, see system) comprising:
a non-transitory computer-readable medium; and
one or more processors communicatively coupled to the non-transitory computer-readable medium, the processor configured to execute processor-executable instructions stored in the non-transitory computer-readable medium to:
receive, by a client device, a request to create a meeting invitation for a meeting (from paragraph 0031, see meeting scheduling function) and an identification of a suggested application (from paragraph 0032, see insert UNICC application-related instructions) for the meeting;
generate a meeting link for the meeting, the meeting link comprising information (from paragraph 0032, see meeting information) to connect to the meeting and information (from paragraph 0032, see The UNICC application-related instruction message(s) may include a brief introduction of the UNICC service feature, a web link (e.g., a Universal Resource Locator or URL) to download the UNICC mobile client and an authentication code for the user to activate its UNICC mobile client) identifying the suggested application;
create a meeting invitation (from paragraph 0033, see meeting invitation) based on the request and the meeting link; and
transmit the meeting invitation to one or more invitees (from paragraph 0033, see all participants, including internal users and/or external users (via associated external messaging systems) to the meeting.
Regarding claim 15, DeRosa discloses a non-transitory computer-readable medium (from paragraph 0004, see non-transitory computer-readable medium) comprising processor-readable instructions configured to be executed by one or more processors, that when executed cause the one or more processors to:
receive, by a client device, a request to create a meeting invitation for a meeting (from paragraph 0031, see meeting scheduling function) and an identification of a suggested application (from paragraph 0032, see insert UNICC application-related instructions) for the meeting;
generate a meeting link for the meeting, the meeting link comprising information (from paragraph 0032, see meeting information) to connect to the meeting and information (from paragraph 0032, see The UNICC application-related instruction message(s) may include a brief introduction of the UNICC service feature, a web link (e.g., a Universal Resource Locator or URL) to download the UNICC mobile client and an authentication code for the user to activate its UNICC mobile client) identifying the suggested application;
create a meeting invitation (from paragraph 0033, see meeting invitation) based on the request and the meeting link; and
transmit the meeting invitation to one or more invitees (from paragraph 0033, see all participants, including internal users and/or external users (via associated external messaging systems) to the meeting.
Allowable Subject Matter
4. Claims 2-7, 9-14 and 16-20 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
Conclusion
5. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Olisa Anwah whose telephone number is 571-272-7533. The examiner can normally be reached from Monday to Friday 8.30 AM to 6 PM.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Carolyn Edwards can be reached on 571-270-7136. The fax phone numbers for the organization where this application or proceeding is assigned are 571-273-8300 for regular communications and 571-273-8300 for After Final communications.
Any inquiry of a general nature or relating to the status of this application or proceeding should be directed to the receptionist whose telephone number is 571-272-2600.
Olisa Anwah
Patent Examiner
August 9, 2026
/OLISA ANWAH/Primary Examiner, Art Unit 2692
Prosecution Insights