DETAILED ACTION
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 .
Claims 1-16 are pending in this application.
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 08/04/2025. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered 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 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-16 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-4, 6, 9-11 and 13-15 of U.S. Patent No. US 12,437,086 B2. Although the claims at issue are not identical, they are not patentably distinct from each other because claims 1-4, 6, 9-11 and 13-15 of U.S. Patent No. US 12,437,086 B2 contains every element of claims 1-16 of the instant application and thus anticipate the claims of the instant application (see Claim Comparison Table below).
Instant Application 19/289,816
US 12,437,086 B2
1. A system for resource event device removal, the system comprising:
a network location associated with a resource recipient, wherein the network location includes a data repository that stores resource event credentials associated with one or more resource event devices held by a resource provider and issued by a resource holding entity; and
a computing platform controlled by the resource holding entity and including a memory and at least one computing processing device in communication with the memory, wherein the memory stores instructions that are executable by one or more of the at least one computing processing devices and are configured to:
receive an input from the resource provider that indicates a desire to remove at least a portion of the resource event credentials from the network location associated with the resource recipient;
in response to receiving the input, determine an intent of the resource provider in providing the input, wherein the intent is to replace the resource event device with another resource event device; determine that the other resource event device is associated with a different resource holding entity as the resource event device; and in response to determining the intent, perform an action associated with the determined intent, wherein the action comprises:
determine resource provider-specific parameters for continuing use of the resource event device, present, to the resource provider, an input option to (i) accept the parameters for continuing use of the resource event device, or (ii) decline the parameters and remove the resource event credentials associated with the resource event device from the data repository;
in response to the resource provider providing a second input that accepts the parameters for continuing use of the resource event device, reconfiguring at least one resource events based on the accepted parameters; and in response to the resource provider providing the second
input that declines the parameters for continuing the recurring resource event, communicate a message to the resource provider that initiates removal of the resource event credentials associated with the resource event device from the data repository.
1. A system for resource event device removal, the system comprising:
a network location associated with a resource recipient, wherein the network location includes a data repository that stores resource event credentials associated with one or more resource event devices held by a resource provider and issued by a resource holding entity; and
a computing platform controlled by the resource holding entity and including a memory and at least one computing processing device in communication with the memory, wherein the memory stores instructions that are executable by one or more of the at least one computing processing devices and are configured to:
receive an input from the resource provider that indicates a desire to remove at least a portion of the resource event credentials from the network location associated with the resource recipient;
in response to receiving the input, determine an intent of the resource provider in providing the input; and in response to determining the intent, perform an action associated with the determined intent, wherein the action comprises communicating a first message to the resource recipient that indicates the intent of the resource provider to cancel the recurring resource event; in response to communicating the first message to the resource recipient, receiving a response message from the resource recipient that provides parameters for continuing the recurring resource event; presenting, to the resource provider, an input option to (i) accept the parameters for continuing the recurring resource event, or (ii) decline the parameters and cancel the recurring resource event;
in response to the resource provider providing a second input that accepts the parameters for continuing the recurring resource event, communicating a second message to the resource provider that indicates acceptance of the parameters by the resource provider, and in response to the resource provider providing the second input that declines the parameters for continuing the recurring resource event, communicating a third message to the resource provider that indicates declination of the parameters by the resource provider and initiates removal, from the data repository, of the resource event credentials associated with the at least one of the one or more resource event devices.
2. The system of claim 1, wherein the instructions configured to determine the intent of the resource provider are further configured to:
implement artificial intelligence (AI) to analyze historical data associated with the resource provider to identify at least one possible intent of the resource provider;
present one or more queries to the resource provider that are configured to confirm the possible intent; and
receive responses to the one or more queries that confirm the possible intent as the intent of the resource provider.
2. The system of claim 1, wherein the instructions configured to determine the intent of the resource provider are further configured to:
implement artificial intelligence (AI) to analyze historical data associated with the resource provider to identify at least one possible intent of the resource provider,
present one or more queries to the resource provider that are configured to confirm the possible intent, and
receive responses to the one or more queries that confirm the possible intent as the intent of the resource provider.
3. The system of claim 2, wherein the instructions configured to determine the intent of the resource provider are further configured to: receive responses to the one or more queries that fail to confirm the possible intent as the intent of the resource provider; and in response to the responses to the one or more queries that fail to confirm the possible intent, iteratively, perform further analysis of the historical data, and continually present additional queries until responses to the additional queries confirm the intent of the resource provider.
3. The system of claim 2, wherein the instructions configured to determine the intent of the resource provider are further configured to: receive responses to the one or more queries that fail to confirm the possible intent as the intent of the resource provider, and in response to the responses to the one or more queries that fail to confirm the possible intent, iteratively, perform further analysis of the historical data, and continually present additional queries until responses to the additional queries confirm the intent of the resource provider.
4. The system of claim 1, wherein the instructions configured to determine the intent of the resource provider are further configured to determine that the resource provider intends to cancel a recurring resource event conducted between the resource provider and the resource recipient that uses the resource event credentials associated with at least one of the one or more resource event devices.
4. The system of claim 1, wherein the instructions configured to determine the intent of the resource provider are further configured to determine that the resource provider intends to cancel a recurring resource event conducted between the resource provider and the resource recipient that uses the resource event credentials associated with at least one of the one or more resource event devices.
8. The system of claim 1, wherein the instructions configured to determine the intent of the resource provider are further configured to determine that the other resource event device is associated with a same resource holding entity as the resource event device, and wherein the instructions configured to perform the action further define the action as including: receiving a third input from the resource provider that selects the other resource event device from amongst one or more other resource event devices; and communicating a message to the resource recipient that initiates replacement of the resource event credentials associated with the resource event device with other resource event credentials associated with the selected other resource event device.
6. The system of claim 5, wherein the instructions configured to determine the intent of the resource provider are further configured to determine that the other resource event device is associated with a same resource holding entity as the resource event device, and wherein the instructions configured to perform the action further define the action as including: receiving a third input from the resource provider that selects the other resource event device from amongst one or more other resource event devices, and communicating a message to the resource recipient that initiates replacement of the resource event credentials associated with the resource event device with other resource event credentials associated with the selected other resource event device.
9. A computer-implemented method for removing a resource event device from a network location, the computer-implemented method is executed by one or more computer processing devices and comprises:
receiving an input from a resource provider that indicates a desire to remove, from a data repository at a network location, at least a portion of resource event credentials associated with at least one resource event device held by the resource provider;
in response to receiving the input, determine an intent of the resource provider in providing the input, wherein the intent is to replace the resource event device with another resource event device; determine that the other resource event device is associated with a different resource holding entity as the resource event device; and in response to determining the intent, perform an action associated with the determined intent, wherein the action comprises: determine resource provider-specific parameters for continuing use of the resource event device,
present, to the resource provider, an input option to (i) accept the parameters for continuing use of the resource event device, or (ii) decline the parameters and remove the resource event credentials associated with the resource event device from the data repository; in response to the resource provider providing a second input that accepts the parameters for continuing use of the resource event device, reconfiguring at least one resource events based on the accepted parameters; and in response to the resource provider providing the second input that declines the parameters for continuing the recurring resource event,
communicate a message to the resource provider that initiates removal of the resource event credentials associated with the resource event device from the data repository.
9. A computer-implemented method for removing a resource event device from a network location, the computer-implemented method is executed by one or more computer processing devices and comprises:
receiving an input from a resource provider that indicates a desire to remove, from a data repository at a network location, at least a portion of resource event credentials associated with at least one resource event device held by the resource provider;
in response to receiving the input, determining an intent of the resource provider in providing the input; and in response to determining the intent,
performing an action associated with the determined intent; determining that the resource provider intends to cancel a recurring resource event conducted between the resource provider and the resource recipient using the resource event credentials associated with at least one of the one or more resource event devices, and wherein performing the action further comprises: communicating a first message to the resource recipient that indicates the intent of the resource provider to cancel the recurring resource event; in response to communicating the first message to the resource recipient, receiving a response message from the resource recipient that provides parameters for continuing the recurring resource event; presenting, to the resource provider, an input option to (i) accept the parameters for continuing the recurring resource event, or (ii) decline the parameters and cancel the recurring resource event; in response to the resource provider providing a second input that accepts the parameters for continuing the recurring resource event, communicating a second message to the resource provider that indicates acceptance of the parameters by the resource provider, and in response to the resource provider providing the second input that declines the parameters for continuing the recurring resource event,
communicating a third message to the resource provider that indicates declination of the parameters by the resource provider and initiates removal, from the data repository, of the resource event credentials associated with the at least one of the one or more resource event devices.
10. The computer-implemented method of claim 9, determining the intent of the resource provider further comprises: implementing artificial intelligence (AI) to analyze historical data associated with the resource provider to identify at least one possible intent of the resource provider; presenting one or more queries to the resource provider that are configured to confirm the possible intent; and either, receiving responses to the one or more queries that seek to confirm the possible intent as the intent of the resource provider; or receiving responses to the one or more queries that fail to confirm the possible intent as the intent of the resource provider; in response to the receiving the responses to the one or more queries that fail to confirm the possible intent iteratively: analyzing the historical data further to identify further possible intent; and continually presenting additional queries that seek to confirm the further possible intent until responses to the additional queries confirm the further possible intent as the intent of the resource provider.
10. The computer-implemented method of claim 9, determining the intent of the resource provider further comprises: implementing artificial intelligence (AI) to analyze historical data associated with the resource provider to identify at least one possible intent of the resource provider; presenting one or more queries to the resource provider that are configured to confirm the possible intent, and either, receiving responses to the one or more queries that seek to confirm the possible intent as the intent of the resource provider; or receiving responses to the one or more queries that fail to confirm the possible intent as the intent of the resource provider; in response to the receiving the responses to the one or more queries that fail to confirm the possible intent iteratively: analyzing the historical data further to identify further possible intent; and continually presenting additional queries that seek to confirm the further possible intent until responses to the additional queries confirm the further possible intent as the intent of the resource provider.
12. The computer-implemented method of claim 9, wherein determining the intent of the resource provider further comprises: determining that the resource provider intends to replace the resource event device with another resource event device; and determining that the other resource event device is associated with a same resource holding entity as the resource event device, and wherein performing the action further comprises: receiving a third input from the resource provider that selects the other resource event device from amongst one or more other resource event devices; and communicating a message to the resource recipient that initiates replacement of the resource event credentials associated with the resource event device with other resource event credentials associated with the selected other resource event device.
11. The computer-implemented method of claim 9, wherein determining the intent of the resource provider further comprises: determining that the resource provider intends to replace the resource event device with another resource event device; and determining that the other resource event device is associated with a same resource holding entity as the resource event device, and wherein performing the action further comprises: receiving a second input from the resource provider that selects the other resource event device from amongst one or more other resource event devices, and communicating a message to the resource recipient that initiates replacement of the resource event credentials associated with the resource event device with other resource event credentials associated with the selected other resource event device.
13. A computer program product comprising: a non-transitory computer-readable medium comprising:
a first set of codes for causing a computer to receive an input from a resource provider that indicates a desire to remove, from a data repository at a network location, at least a portion of resource event credentials associated with at least one resource event device held by the resource provider;
a second set of codes for causing a computer to, in response to receiving the input, determine an intent of the resource provider in providing the input, wherein the intent is to replace the resource event device with another resource event device; a third set of codes for causing a computer to determine that the other resource event device is associated with a different resource holding entity as the resource event device; and a fourth set of codes for causing a computer to, in response to determining the intent, perform an action associated with the determined intent, wherein the action comprises: determine resource provider-specific parameters for continuing use of the resource event device, present, to the resource provider, an input option to (i) accept the parameters for continuing use of the resource event device, or (ii) decline the parameters and remove the resource event credentials associated with the resource event device from the data repository; in response to the resource provider providing a second input that accepts the parameters for continuing use of the resource event device, reconfiguring at least one resource events based on the accepted parameters; and
in response to the resource provider providing the second input that declines the parameters for continuing the recurring resource event, communicate a message to the resource provider that initiates removal of the resource event credentials associated with the resource event device from the data repository.
13. A computer program product comprising: a non-transitory computer-readable medium comprising:
a first set of codes for causing a first computer to receive an input from a resource provider that indicates a desire to remove, from a data repository at a network location, at least a portion of resource event credentials associated with at least one resource event device held by the resource provider;
a second set of codes for causing a second computer to determine that the resource provider intends to cancel a recurring resource event conducted between the resource provider and the resource recipient using the resource event credentials associated with at least one of the one or more resource event devices; and a third set of codes for causing a third computer to: communicate a first message to the resource recipient that indicates the intent of the resource provider to cancel the recurring resource event, in response to communicating the first message to the resource recipient, receive a response message from the resource recipient that provides parameters for continuing the recurring resource event, present, to the resource provider, an input option to (i) accept the parameters for continuing the recurring resource event, or (ii) decline the parameters and cancel the recurring resource event, either:
in response to the resource provider providing a second input that accepts the parameters for continuing the recurring resource event, communicate a second message to the resource provider that indicates acceptance of the parameters by the resource provider, or in response to the resource provider providing the second input that declines the parameters for continuing the recurring resource event, communicating a third message to the resource provider that indicates declination of the parameters by the resource provider and initiates removal, from the data repository, of the resource event credentials associated with the at least one of the one or more resource event devices.
14. The computer program product of claim 13, wherein the fourth set of codes are further configured to cause the computer to: implement artificial intelligence (AI) to analyze historical data associated with the resource provider to identify at least one possible intent of the resource provider; present one or more queries to the resource provider that are configured to confirm the possible intent; and either: receive responses to the one or more queries that seek to confirm the possible intent as the intent of the resource provider; or receive responses to the one or more queries that fail to confirm the possible intent as the intent of the resource provider, in response to the receiving the responses to the one or more queries that fail to confirm the possible intent iteratively: analyze the historical data further to identify further possible intent; and continually present additional queries that seek to confirm the further possible intent until responses to the additional queries confirm the further possible intent as the intent of the resource provider.
14. The computer program product of claim 13, wherein the third set of codes are further configured to cause the third computer to: implement artificial intelligence (AI) to analyze historical data associated with the resource provider to identify at least one possible intent of the resource provider, present one or more queries to the resource provider that are configured to confirm the possible intent, and either: receive responses to the one or more queries that seek to confirm the possible intent as the intent of the resource provider, or receive responses to the one or more queries that fail to confirm the possible intent as the intent of the resource provider, in response to the receiving the responses to the one or more queries that fail to confirm the possible intent iteratively: analyze the historical data further to identify further possible intent, and continually present additional queries that seek to confirm the further possible intent until responses to the additional queries confirm the further possible intent as the intent of the resource provider.
16. The computer program product of claim 13, wherein the second set of codes are further configured to: determine that (i) the resource provider intends to replace the resource event device with another resource event device, and (ii) the other resource event device is associated with a same resource holding entity as the resource event device; and wherein the third set of codes are further configured to cause the computer to: receive a third input from the resource provider that selects the other resource event device from amongst one or more other resource event devices; and communicate a message to the resource recipient that initiates replacement of the resource event credentials associated with the resource event device with other resource event credentials associated with the selected other resource event device.
15. The computer program product of claim 13, wherein the second set of codes are further configured to: determine that (i) the resource provider intends to replace the resource event device with another resource event device, and (ii) the other resource event device is associated with a same resource holding entity as the resource event device, and wherein the third set of codes are further configured to cause the third computer to: receive the second input from the resource provider that selects the other resource event device from amongst one or more other resource event devices, and communicate a message to the resource recipient that initiates replacement of the resource event credentials associated with the resource event device with other resource event credentials associated with the selected other resource event device.
Moreover, limitations of claims 5-7, 11 and 15 of instant application contains in claims 1, 9 and 13 of U.S. Patent No. US 12,437,086 B2. Thus, rejected with similar rationale as above.
Allowable Subject Matter
Claims 1-16 would be allowed when a proper Terminal Disclaimer is submitted to revolve the above double patenting rejection.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Jin et al. (US 9,392,309 B2) teaches entitlement management module may cancel a subscription in response to a failure of recurring payment (e.g., a bad credit card). In this instance, entitlement management module 430 may update an end time for time window with a current date (i.e., subscription cancelled immediately) (herein, cancelling a subscription is referred to as “intent”) -e.g., see, col. 8, lines 38-58 of Jin.
Holm et al. (US 2021/0319092 A1) teaches adding or removing authorized access credentials from a permission database; an administrator utilizing an access control platform may remove unused permissions, infrequently used permissions, or may reclassify permissions from the permissions database. -e.g., see, [0041] of Holm.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SUMAN DEBNATH whose telephone number is (571)270-1256. The examiner can normally be reached Mon-Fri; 9:00am-5:00pm.
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, Farid Homayounmehr can be reached at 571-272-3739. 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.
SUMAN DEBNATH
Patent Examiner
Art Unit 2495
/S.D/ Examiner, Art Unit 2495
/FARID HOMAYOUNMEHR/ Supervisory Patent Examiner, Art Unit 2495
Prosecution Insights