Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
DETAILED ACTION
This is a reply to the application filed on 05/27/2025, in which, claim(s) 1-20 are pending. Claim(s) 1, 9 and 14 are independent.
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 05/27/2025, has been reviewed. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the examiner is considering the information disclosure statement.
Drawings
The drawings filed on 05/27/2025 are accepted by The Examiner.
Double Patenting
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 claims at issue 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); and 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 a nonstatutory double patenting ground provided the reference application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The USPTO internet Web site contains terminal disclaimer forms which may be used. Please visit http://www.uspto.gov/forms/. The filing date of the application will determine what form 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 http://www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp.
Claims 1-20 are non-provisionally rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over:
Claims 1-20 of Patent 12,333,006.
Although the conflicting claims are not identical, they are not patentably distinct from each other because claims 1-20 are anticipated by claims 1-20 of Patent 12,333,006.
Instant Application 19/219,503
Patent US 12,333,006 B2
Claim 1. A method comprising:
obtaining, via communications hardware of a threat manager, a piece of data;
determining, by a threat identification engine of the threat manager, that the piece of data is a threat; assigning, by a threat priority engine of the threat manager, a weight to the threat;
causing, by a remediation engine of the threat manager and based on the determination and the weight of the threat, execution of a threat remediation action, by:
generating an emergency remediation statement without human intervention using a trained generative artificial intelligence (GAI) model,
causing automatic publication of the emergency remediation statement on one or more online sources, generating, after the publication of the emergency remediation statement, a threat notification, and
causing display of the threat notification to an entity associated with the threat manager, wherein the threat notification comprises instructions for generating a supplemental remediation statement to supplement the emergency remediation statement;
receiving, via the communications hardware, the supplemental remediation statement; and causing, by the remediation engine, publication of the supplemental remediation statement on the one or more online sources on which the emergency remediation statement was published.
Claim 1. A method comprising:
obtaining, via communications hardware of a threat manager, a piece of data;
determining, by a threat identification engine of the threat manager, that the piece of data is a threat; and
causing, by a remediation engine of the threat manager and based on the determination, execution of a threat remediation action, wherein the threat remediation action comprises publishing an emergency remediation statement addressing the threat and transmitting a takedown request to remove the threat from a threat source, wherein causing execution of the threat remediation action further comprises: generating, by the remediation engine, the takedown request without human intervention using a generative artificial intelligence (GAI) model, wherein the takedown request is generated in addition to the emergency remediation statement and the takedown request indicates (i) a primary takedown target that is the piece of data that comprises deepfake content that is adverse to an entity associated with the threat manager, and the threat source is a third-party content-sharing website, and (ii) one or more secondary takedown targets comprising other pieces of data identified using a threat fingerprint generated, by the threat identification engine, using at least the piece of data; and automatically transmitting, by the communications hardware, the takedown request to the threat source from which the piece of data is obtained.
Claim 3. The method of claim 2, wherein causing execution of the threat remediation action further comprises: generating, by the remediation engine, the emergency remediation statement without human intervention using a trained generative artificial intelligence (GAI) model; and
causing, by the remediation engine, automatic publication of the emergency remediation statement on one or more online sources.
Claim 7. The method of claim 3, wherein causing execution of the threat remediation action further comprises: generating, by the remediation engine and after the publication of the emergency remediation statement, a threat notification; and
causing, by the remediation engine, display of the threat notification to an entity associated with the threat manager, wherein the threat notification comprises instructions for generating a supplemental remediation statement to supplement the emergency remediation statement.
Claim 8. The method of claim 7, further comprising:
receiving, via communications hardware, the supplemental remediation statement; and automatically causing, by the remediation engine, publication of the supplemental remediation statement on the one or more online sources on which the emergency remediation statement was published.
Allowable Subject Matter
Claims 1-20 would be allowable if the Applicant overcomes double patenting rejection issued in this office action by filing a valid electronic Terminal Disclaimer.
Independent Claim(s) and their respective dependent claims would be allowable over prior arts since the prior arts taken individually or in combination fails to particular discloses, fairly suggest or render obvious the following italic limitations:
In claims 1, 9 and 14:
“causing, by a remediation engine of the threat manager and based on the determination and the weight of the threat, execution of a threat remediation action, by:
causing display of the threat notification to an entity associated with the threat manager, wherein the threat notification comprises instructions for generating a supplemental remediation statement to supplement the emergency remediation statement;
causing, by the remediation engine, publication of the supplemental remediation statement on the one or more online sources on which the emergency remediation statement was published” in combination with other limitations recited as specified in the independent claim(s).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHENG-FENG HUANG whose telephone number is (571)272-6186. The examiner can normally be reached Monday-Friday: 9 am - 5 pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Eleni A Shiferaw can be reached at (571) 272-3867. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/CHENG-FENG HUANG/Primary Examiner, Art Unit 2497
Prosecution Insights