DETAILED ACTION
Summary
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
This is a first Office Action on the merits.
Claims 1-20 are currently pending.
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 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 filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual 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/apply/applying-online/eterminal-disclaimer.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-18 of U.S. Patent No. 12,482,333. Although the claims at issue are not identical, they are not patentably distinct from each other because the claims of the patent effectively “anticipate” the limitations of the instant application.
The following chart illustrates limitation correspondence between claim sets.
Claim 1:
A computing platform comprising:
at least one processor;
a communication interface communicatively coupled to the at least one processor; and
memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:
apply anomaly detection logic to information indicating potentially anomalous activity at one or more automated teller machines (ATMs), wherein the anomaly detection logic includes one or more rules that are used to identify one or more anomalies;
output, based on applying the anomaly detection logic, one or more anomaly codes, wherein the one or more anomaly codes correspond to the one or more anomalies;
trend the one or more anomalies based on the one or more anomaly codes and using statistical analysis;
identify one or more actions to resolve the one or more anomalies based on the trending;
automatically execute the one or more actions by sending commands to the one or more ATMs affected by the one or more anomalies, that when received by the one or more affected ATMs, direct the one or more affected ATMs to execute the one or more actions;
generate an anomaly report, wherein the anomaly report comprises the one or more anomalies, the trending, and the one or more actions; and
send, to an enterprise computing device, the anomaly report and one or more commands directing the enterprise computing device to display the anomaly report, wherein sending the one or more commands directing the enterprise computing device to display the anomaly report causes the enterprise computing device to display the anomaly report.
Claim 12:
A method comprising:
at a computing platform comprising at least one processor, a communication interface, and memory:
applying anomaly detection logic to information indicating potentially anomalous activity at one or more automated teller machines (ATMs), wherein the anomaly detection logic includes one or more rules that are used to identify one or more anomalies;
outputting, based on applying the anomaly detection logic, one or more anomaly codes, wherein the one or more anomaly codes correspond to the one or more anomalies;
trending the one or more anomalies based on the one or more anomaly codes and using statistical analysis;
identifying one or more actions to resolve the one or more anomalies based on the trending;
automatically executing the one or more actions by sending commands to the one or more ATMs affected by the one or more anomalies, that when received by the one or more affected ATMs, direct the one or more affected ATMs to execute the one or more actions;
generating an anomaly report, wherein the anomaly report comprises the one or more anomalies, the trending, and the one or more actions; and
sending, to an enterprise computing device, the anomaly report and one or more commands directing the enterprise computing device to display the anomaly report, wherein sending the one or more commands directing the enterprise computing device to display the anomaly report causes the enterprise computing device to display the anomaly report.
Claim 20:
One or more non-transitory computer-readable storing instructions that, when executed by a computing platform comprising at least one processor, a communication interface, and memory, cause the computing platform to:
apply anomaly detection logic to information indicating potentially anomalous activity at one or more automated teller machines (ATMs), wherein the anomaly detection logic includes one or more rules that are used to identify one or more anomalies;
output, based on applying the anomaly detection logic, one or more anomaly codes,
wherein the one or more anomaly codes correspond to the one or more anomalies;
trend the one or more anomalies based on the one or more anomaly codes and using statistical analysis;
identify one or more actions to resolve the one or more anomalies based on the trending;
automatically execute the one or more actions by sending commands to the one or more ATMs affected by the one or more anomalies, that when received by the one or more affected ATMs, direct the one or more affected ATMs to execute the one or more actions;
generate an anomaly report, wherein the anomaly report comprises the one or more anomalies, the trending, and the one or more actions; and
send, to an enterprise computing device, the anomaly report and one or more commands directing the enterprise computing device to display the anomaly report, wherein sending the one or more commands directing the enterprise computing device to display the anomaly report causes the enterprise computing device to display the anomaly report.
Claim 1:
A computing platform comprising:
at least one processor;
a communication interface communicatively coupled to the at least one processor; and
memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:
receive information related to one or more automated teller machines (ATMs) indicating potentially anomalous activity at the one or more ATMs;
preprocess the information to remove one or more false positives from the information;
apply anomaly detection logic to the preprocessed information, wherein the anomaly detection logic includes one or more rules that are used to identify one or more anomalies;
output, based on applying the anomaly detection logic, one or more anomaly codes, wherein the one or more anomaly codes correspond to the one or more anomalies;
trend the one or more anomalies based on the one or more anomaly codes and using statistical analysis;
identify one or more actions to resolve the one or more anomalies based on the trending;
automatically execute the one or more actions by sending commands to the one or more ATMs affected by the one or more anomalies, that when received by the one or more affected ATMs, direct the one or more affected ATMs to execute the one or more actions;
generate an anomaly report, wherein the anomaly report comprises the one or more anomalies, the trending, and the one or more actions; and
send, to an enterprise computing device, the anomaly report and one or more commands directing the enterprise computing device to display the anomaly report, wherein sending the one or more commands directing the enterprise computing device to display the anomaly report causes the enterprise computing device to display the anomaly report.
Claim 11:
A method comprising: at a computing platform comprising at least one processor, a communication interface, and memory:
receiving information related to one or more automated teller machines (ATMs) indicating potentially anomalous activity at the one or more ATMs;
preprocessing the information to remove one or more false positives from the information;
applying anomaly detection logic to the preprocessed information, wherein the anomaly detection logic includes one or more rules that are used to identify one or more anomalies;
outputting, based on applying the anomaly detection logic, one or more anomaly codes, wherein the one or more anomaly codes correspond to the one or more anomalies;
trending the one or more anomalies based on the one or more anomaly codes and using statistical analysis; identifying one or more actions to resolve the one or more anomalies based on the trending;
automatically executing the one or more actions by sending commands to the one or more ATMs affected by the one or more anomalies, that when received by the one or more affected ATMs, direct the one or more affected ATMs to execute the one or more actions;
generating an anomaly report, wherein the anomaly report comprises the one or more anomalies, the trending, and the one or more actions; and sending, to an enterprise computing device, the anomaly report and one or more commands directing the enterprise computing device to display the anomaly report, wherein sending the one or more commands directing the enterprise computing device to display the anomaly report causes the enterprise computing device to display the anomaly report.
Claim 18:
One or more non-transitory computer-readable medium storing instructions that, when executed by a computing platform comprising at least one processor, a communication interface, and memory, cause the computing platform to:
receive information related to one or more automated teller machines (ATMs) indicating potentially anomalous activity at the one or more ATMs; preprocess the information to remove one or more false positives from the information;
apply anomaly detection logic to the preprocessed information, wherein the anomaly detection logic includes one or more rules that are used to identify one or more anomalies;
output, based on applying the anomaly detection logic, one or more anomaly codes,
wherein the one or more anomaly codes correspond to the one or more anomalies; trend the one or more anomalies based on the one or more anomaly codes and using statistical analysis;
identify one or more actions to resolve the one or more anomalies based on the trending;
automatically execute the one or more actions by sending commands to the one or more ATMs affected by the one or more anomalies, that when received by the one or more affected ATMs, direct the one or more affected ATMs to execute the one or more actions;
generate an anomaly report, wherein the anomaly report comprises the one or more anomalies, the trending, and the one or more actions; and send, to an enterprise computing device, the anomaly report and one or more commands directing the enterprise computing device to display the anomaly report, wherein sending the one or more commands directing the enterprise computing device to display the anomaly report causes the enterprise computing device to display the anomaly report.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to LAURA A GUDORF whose telephone number is (571)270-7607. If the Examiner cannot be reached by telephone, she can be reached through the following e-mail address: laura.gudorf@uspto.gov. The examiner can normally be reached on M-F 6:00-4:00 PM.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Michael Lee, can be reached at telephone number (571)272-2398. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from Patent Center. Status information for published applications may be obtained from Patent Center. Status information for unpublished applications is available through Patent Center for authorized users only. Should you have questions about access to Patent Center, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free).
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) Form at https://www.uspto.gov/patents/uspto-automated- interview-request-air-form.
/LAURA A GUDORF/Primary Examiner, Art Unit 2876