IP Library › Granted Patent US 12,437,304
Granted Patent B2
US 12,437,304 · App. 17/702,480 · Granted Oct 7, 2025

Intelligent coordination of transaction processing in a multi-device network

Inventors: Puneetha Polasa (Telangana, IN); Bhagya Lakshmi Sudha Lavanya Mallidi (Hyderabad, IN); Udaya Kumar Raju Ratnakaram (Hyderabad, IN); Sandeep Kumar Chauhan (Hyderabad, IN)
Assignee: Bank of America Corporation
G06Q20/405G06Q20/4014G06Q20/409
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,437,304
App. No.
17/702,480
Granted
Oct 7, 2025
Kind
B2
Abstract

Rules and triggers for initiating and generating transactions can be dynamically and automatically created by a computing device based on learning behaviors for a knowledgebase. This knowledgebase may be created by storing historical transaction information for devices within a particular network such as an Internet of Things (IoT) network where devices are interconnected and capable of processing data and instructions. Such a network may be associated with a user or location or organization, and may conform to a specific communication protocol.

Claims (91)

1. A method for automatically initiating transactions through a network, the method comprising:

receiving, by an authorized computing device in a multi-device private network of a networked computing system and from a first computing device, a request to join the multi-device private network;

determining, by the authorized computing device and based on receiving, from the first computing device, a token unique to the multi-device private network, that the first computing device is approved to join the multi-device private network;

transmitting, by the authorized computing device and to the first computing device, communication and network protocol information enabling the first computing device to communicate with other devices in the multi-device private network;

updating a device registry to add the first computing device to a plurality of computing devices within the multi-device private network;

detecting, by the authorized computing device, a change in processing load associated with at least one computing device of the plurality of computing devices within the multi-device private network;

in response to the detecting, transmitting, to each computing device of the plurality of computing devices within the multi-device private network, a signal including a polling request for data about each computing device of the plurality of computing devices within the multi-device private network;

receiving, in response to the polling request, data about each computing device of the plurality of computing devices;

based on the data about each computing device of the plurality of computing devices, removing, from the device registry, a second computing device of the plurality of computing devices within the multi-device private network;

transmitting, to each remaining computing device of the plurality of computing devices within the multi-device private network, updated membership data of the remaining computing devices of the plurality of computing devices within the multi-device private network;

detecting, by the networked computing system, a plurality of transactions initiated by one or more computing devices of the remaining computing devices of the plurality of computing devices within the multi-device private network, the multi-device private network providing access to a wide area network, wherein the networked computing system is configured to manage electronic transactions initiated by the one or more computing devices of the remaining computing devices of the plurality of computing devices in the multi-device private network;

storing, by the networked computing system, transaction attributes for the plurality of transactions in a transaction history database, the transaction attributes including one or more of: a cost, a quantity of a product, a date, or a device identifier;

automatically generating, by the networked computing system, a transaction triggering event, including:

determining, based on sensor data received from computing devices of the remaining computing devices of the plurality of computing devices within the multi-device private network, a pattern of behavior from the plurality of transactions stored in the transaction history database, including identifying a recurring type of transaction for a particular product;

upon determining the pattern of behavior:

identifying one or more common transaction attributes between the plurality of transactions; and

defining a transaction triggering condition requiring the identified one or more common transaction attributes; and

implementing, by the networked computing system, the transaction triggering event, wherein the transaction triggering event is configured to cause the authorized computing device in the multi-device private network to generate, without user input and prior to transaction authorization, a transaction for purchasing a product upon the transaction triggering condition defined in the transaction triggering event being satisfied, wherein implementing the transaction triggering event includes:

causing a computing device of the one or more computing devices of the remaining computing devices of the plurality of computing devices in the multi-device private network to monitor for the transaction triggering condition defined in the transaction triggering event; and

causing a new transaction for purchasing the product to be generated, without user input, in response to determining that the transaction triggering condition has been met.

2. The method of claim 1 , further comprising:

performing transaction authorization for the new transaction after the new transaction has been generated based on the transaction triggering event.

3. The method of claim 1 , further comprising:

transmitting a notification to a user after generating the new transaction, the notification indicating that the transaction triggering condition defined in the transaction triggering event has been met, and requesting a confirmation from the user to process the generated new transaction.

4. The method of claim 2 , wherein performing the transaction authorization includes authorizing the new transaction based on one or more user defined transaction rules.

5. The method of claim 4 , further comprising:

upon determining that the new transaction is not authorized, automatically modifying, by the networked computing system, at least one parameter of the new transaction.

6. The method of claim 4 , further comprising:

upon determining that the new transaction is not authorized based on the one or more user defined transaction rules, transmitting the new transaction to a user for authorization.

7. The method of claim 1 , wherein the one or more common transaction attributes includes the date, and wherein the date is defined as a particular day of week or a particular day of month.

8. The method of claim 1 , wherein the plurality of transactions includes at least three separate transactions, and wherein determining the pattern of behavior from the plurality of transactions includes:

determining that the at least three separate transactions are separated by a same amount of time; and

determining that the at least three separate transactions include a purchase for a particular product.

9. The method of claim 1 , wherein the transaction attributes include a network communication security protocol.

10. A transaction processing apparatus in a multi-device private network comprising:

a processor; and

memory storing computer-readable instructions that, when executed, cause the transaction processing apparatus to:

receive, by an authorized computing device in the multi-device private network and from a first computing device, a request to join the multi-device private network;

determine, by the authorized computing device and based on receiving, from the first computing device, a token unique to the multi-device private network, that the first computing device is approved to join the multi-device private network;

transmit, by the authorized computing device and to the first computing device, communication and network protocol information enabling the first computing device to communicate with other devices in the multi-device private network;

update a device registry to add the first computing device to a plurality of computing devices within the multi-device private network;

detect, by the authorized computing device, a change in processing load associated with at least one computing device of the plurality of computing devices within the multi-device private network;

in response to the detecting, transmit, to each computing device of the plurality of computing devices within the multi-device private network, a signal including a polling request for data about each computing device of the plurality of computing devices within the multi-device private network;

receive, in response to the polling request, data about each computing device of the plurality of computing devices;

based on the data about each computing device of the plurality of computing devices, remove, from the device registry, a second computing device of the plurality of computing devices within the multi-device private network;

transmit, to each remaining computing device of the plurality of computing devices within the multi-device private network, updated membership data of the remaining computing devices of the plurality of computing devices within the multi-device private network;

detect a plurality of transactions initiated by one or more computing devices of the remaining computing devices of the plurality of computing devices within the multi-device private network, the multi-device private network providing access to a wide area network, wherein the transaction processing apparatus is configured to manage electronic transaction processing for the one or more computing devices of the remaining computing devices of the plurality of computing devices in the multi-device private network;

store transaction attributes for the plurality of transactions in a transaction history database, the transaction attributes including one or more of: a cost, a quantity of a product, a date, or a device identifier;

automatically generate a transaction triggering event, including:

determining, based on sensor data received from computing devices of the remaining computing devices of the plurality of computing devices within the multi-device private network, a pattern of behavior from the plurality of transactions stored in the transaction history database, including identifying a recurring type of transaction for a particular product;

upon determining the pattern of behavior:

identifying one or more common transaction attributes between the plurality of transactions; and

defining a transaction triggering condition requiring the identified one or more common transaction attributes; and

implement the transaction triggering event, wherein the transaction triggering event is configured to cause the authorized computing device in the multi-device private network to generate, without user input and prior to transaction authorization, a transaction for purchasing a product upon the transaction triggering condition defined in the transaction triggering event being satisfied, wherein implementing the transaction triggering event includes:

causing a computing device of the one or more computing devices of the remaining computing devices of the plurality of computing devices in the multi-device private network to monitor for the transaction triggering condition defined in the transaction triggering event; and

causing a new transaction for purchasing the product to be generated, without user input, in response to determining that the transaction triggering condition has been met.

11. The transaction processing apparatus of claim 10 , wherein the computer-readable instructions, when executed, further cause the transaction processing apparatus to:

perform transaction authorization for the new transaction after the new transaction has been generated based on the transaction triggering event.

12. The transaction processing apparatus of claim 10 , wherein the computer-readable instructions, when executed, further cause the transaction processing apparatus to:

transmit a notification to a user after generating the new transaction, the notification indicating that the transaction triggering condition defined in the transaction triggering event have been met, and requesting a confirmation from the user to process the generated new transaction.

13. The transaction processing apparatus of claim 11 , wherein performing the transaction authorization includes authorizing the new transaction based on one or more user defined transaction rules.

14. The transaction processing apparatus of claim 13 , wherein the computer-readable instructions, when executed, further cause the transaction processing apparatus to:

upon determining that the new transaction is not authorized, automatically modifying at least one parameter of the new transaction.

15. The transaction processing apparatus of claim 13 , wherein the computer-readable instructions, when executed, further cause the transaction processing apparatus to:

upon determining that the new transaction is not authorized based on the one or more user defined transaction rules, transmit the new transaction to a user for authorization.

16. A non-transitory computer-readable medium storing computer-readable instructions that, when executed, cause a transaction processing apparatus in a multi-device private network to:

receive, by an authorized computing device in the multi-device private network and from a first computing device, a request to join the multi-device private network;

determine, by the authorized computing device and based on receiving, from the first computing device, a token unique to the multi-device private network, that the first computing device is approved to join the multi-device private network;

transmit, by the authorized computing device and to the first computing device, communication and network protocol information enabling the first computing device to communicate with other devices in the multi-device private network;

update a device registry to add the first computing device to a plurality of computing devices within the multi-device private network;

detect, by the authorized computing device, a change in processing load associated with at least one computing device of the plurality of computing devices within the multi-device private network;

in response to the detecting, transmit, to each computing device of the plurality of computing devices within the multi-device private network, a signal including a polling request for data about each computing device of the plurality of computing devices within the multi-device private network;

receive, in response to the polling request, data about each computing device of the plurality of computing devices;

based on the data about each computing device of the plurality of computing devices, remove, from the device registry, a second computing device of the plurality of computing devices within the multi-device private network;

transmit, to each remaining computing device of the plurality of computing devices within the multi-device private network, updated membership data of the remaining computing devices of the plurality of computing devices within the multi-device private network;

detect a plurality of transactions initiated by one or more computing devices of the remaining computing devices of the plurality of computing devices within a multi-device private network, the multi-device private network providing access to a wide area network;

store transaction attributes for the plurality of transactions in a transaction history database, the transaction attributes including one or more of: a cost, a quantity of a product, a date, or a device identifier;

generate a transaction triggering event, including:

determining, based on sensor data received from computing devices of the remaining computing devices of the plurality of computing devices within the multi-device private network, a pattern of behavior from the plurality of transactions stored in the transaction history database;

upon determining the pattern of behavior:

identifying one or more common transaction attributes between the plurality of transactions; and

defining a transaction triggering condition requiring the identified one or more common transaction attributes; and

implement the transaction triggering event, wherein the transaction triggering event is configured to cause the authorized computing device in the multi-device private network to generate, without user input, a transaction for purchasing a product upon the transaction triggering condition defined in the transaction triggering event being satisfied.

17. The non-transitory computer-readable medium of claim 16 , wherein the computer-readable instructions, when executed, further cause the transaction processing apparatus to:

determine that the transaction triggering condition defined in the transaction triggering event have been met; and

generate a new transaction for the one or more devices in the multi-device private network.

18. The non-transitory computer-readable medium of claim 17 , wherein the computer-readable instructions, when executed, further cause the transaction processing apparatus to:

transmit a notification to a user after generating the new transaction, the notification indicating that the transaction triggering condition defined in the transaction triggering event have been met, and requesting a confirmation from the user to process the generated new transaction.

19. The non-transitory computer-readable medium of claim 17 , wherein the computer-readable instructions, when executed, further cause the transaction processing apparatus to authorize the new transaction based on one or more user defined transaction rules.

20. The non-transitory computer-readable medium of claim 19 , wherein the computer-readable instructions, when executed, further cause the transaction processing apparatus to:

upon determining that the new transaction is not authorized, modifying at least one parameter of the new transaction.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 23, 2022
From: POLASA, PUNEETHA; LAKSHMI SUDHA LAVANYA MALLIDI, BHAGYA; RATNAKARAM, UDAYA KUMAR RAJU; CHAUHAN, SANDEEP KUMAR
To: BANK OF AMERICA CORPORATION
Reel/Frame 059381/0427 →
Continuity (1)
Related Publication 20230316289A1 · Oct 5, 2023
References Cited (45)
US 9398336B2 · Markley et al. · 2016 [cited by applicant]
US 10826684B1 · Winter et al. · 2020 [cited by applicant]
US 11227325B1 · Baral et al. · 2022 [cited by applicant]
US 11397950B2 · Manjunath · 2022 [cited by examiner]
US 20070204314A1 · Hasek et al. · 2007 [cited by applicant]
US 20140074575A1 · Rappoport · 2014 [cited by examiner]
US 20150019342A1 · Gupta · 2015 [cited by applicant]
US 20160092872A1 · Prakash et al. · 2016 [cited by applicant]
US 20160269330A1 · McEvoy et al. · 2016 [cited by applicant]
US 20160292010A1 · Maesono · 2016 [cited by applicant]
US 20170293901A1 · Savla · 2017 [cited by applicant]
US 20180158043A1 · Noëet al. · 2018 [cited by applicant]
US 20180322430A1 · Guha et al. · 2018 [cited by applicant]
US 20180330349A1 · Uhr et al. · 2018 [cited by applicant]
US 20190026716A1 · Anbukkarasu et al. · 2019 [cited by applicant]
US 20190362076A1 · Wang et al. · 2019 [cited by applicant]
US 20200167337A1 · Kurian et al. · 2020 [cited by applicant]
US 20200226566A1 · Wang · 2020 [cited by applicant]
US 20210065170A1 · Shriver · 2021 [cited by applicant]
US 20210065171A1 · Pliasunov · 2021 [cited by applicant]
US 20210065291A1 · Gaivironsky et al. · 2021 [cited by applicant]
US 20210078847A1 · Marten · 2021 [cited by applicant]
US 20210097523A1 · Phillips · 2021 [cited by examiner]
US 20210174269A1 · Lee et al. · 2021 [cited by applicant]
US 20210201313A1 · Kumawat et al. · 2021 [cited by applicant]
US 20210287279A1 · Taffer · 2021 [cited by examiner]
CN 1836228A · 2006 [cited by applicant]
CN 101868032B · 2010 [cited by applicant]
CN 108880797B · 2021 [cited by applicant]
CN 109347666B · 2021 [cited by applicant]
CN 114037438A · 2022 [cited by applicant]
WO 8909443A1 · 1989 [cited by applicant]
WO 2021174968A1 · 2021 [cited by applicant]
Mar. 30, 2023—(US) Non-Final Office Action—U.S. Appl. No. 17/702,492. [cited by applicant]
Nov. 9, 2023—(US) Non-Final Office Action—U.S. Appl. No. 17/702,460. [cited by applicant]
Dominique Guinard, “Interacting with the SOA-Based Internet of Things . . . Web Services”, 2010, IEEE Transactions on Services Computing, vol. 3, No. 3, pp. 223-235. (Year: 2010). [cited by applicant]
Xiaolin Jia, “RFID Technology and Its Applications in Internet of Things (IOT)”, 2012, School of Information Science and Technology, Chengdun, China, pp. 1292-1285. (Year: 2012). [cited by applicant]
Sep. 20, 2023—(US) Final Office Action—U.S. Appl. No. 17/702,492. [cited by applicant]
Mar. 11, 2024—(US) Non-Final Office Action—U.S. Appl. No. 17/702,492. [cited by applicant]
May 22, 2024—(US) Final Office Action—U.S. Appl. No. 17/702,460. [cited by applicant]
Aug. 20, 2024—(US) Final Office Action—U.S. Appl. No. 17/702,492. [cited by applicant]
Sep. 29, 2024—(US) Non-Final Office Action—U.S. Appl. No. 17/702,460. [cited by applicant]
Daeil Kwon, “IoT-Based Prognostic and Systems Health Management for Industrial Applications,” 2016, IEEE Access, pp. 3659-3670. [cited by applicant]
Samaresh Bera, “Software-Defined Network for Internet of Things A Survey,” 2017, IEEE Internet of Things Journal, vol. 4, No. 6, Dec. 2017, pp. 1994-2008. [cited by applicant]
Apr. 10, 2025—(US) Final Office Action—U.S. Appl. No. 17/702,460. [cited by applicant]