US 12,265,859 B2
Computing architecture for optimally executing service requests based on node ability and interest configuration
Ganeshprasad Giridharasharma Kumble, Karnataka (IN); Karthik Balasubramanian, Karnataka (IN); and Anantha Chathanur Raman Krishnan, Princeton, NJ (US)
Assigned to ANANTHA CHATHANUR RAMAN KRISHNAN, Princeton, NJ (US)
Appl. No. 17/257,778
Filed by Ganeshprasad Giridharasharma Kumble, Karnataka (IN); Karthik Balasubramanian, Karnataka (IN); and Anantha Chathanur Raman Krishnan, Princeton, NJ (US)
PCT Filed Jul. 5, 2019, PCT No. PCT/IB2019/055751
§ 371(c)(1), (2) Date Jan. 4, 2021,
PCT Pub. No. WO2020/008427, PCT Pub. Date Jan. 9, 2020.
Claims priority of application No. 201811025043 (IN), filed on Jul. 5, 2018; application No. 201811025044 (IN), filed on Jul. 5, 2018; and application No. 201811025045 (IN), filed on Jul. 5, 2018.
Prior Publication US 2022/0138020 A1, May 5, 2022
Int. Cl. G06F 9/50 (2006.01)
CPC G06F 9/5083 (2013.01) [G06F 9/5044 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A system for executing a plurality of service requests (SRs) from corresponding plurality of user computing devices, said system comprising:
a distributed compute (DC) that forms part of a distributed network, said DC having at least one processor that executes one or more routines stored in an operatively coupled memory to enable receipt of the plurality of service requests in an interaction pool; and
a system state manager (SSM) that, based on at least one common attribute of each SR in the interaction pool, identifies a compute node from one or more available compute nodes comprised in the distributed compute that has an ability and an interest list configuration to execute said respective SR, and transmits said respective SR to said identified compute node for execution, wherein said interest list configuration indicates an asset class of service requests that said identified compute node is configured to execute, and wherein said DC is operatively and communicatively coupled with a distributed storage (DS), said DS being configured to store a super state structure (SSS) representing metadata associated with said SR or output of said execution of said SR by said identified compute node, wherein said SSS represents information indicative of identity of the SR, an interaction vector pertaining to the SR, method of execution of the SR, and cause/intent behind the SR, said cause/intent at least including depiction of why the SR was executed.