# US 10,771,308 B2 · Request processing system using a combining engine > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,771,308 B2 - Document ID: US10771308B2 - Status: Granted - Kind: B2 - Application number: 16/533,523 - Filed: 2019-08-06 - Published: 2019-11-28 - Granted: 2020-09-08 - Earliest claimed: 2017-11-29 - Assignees: Bank of America Corporation - Applicants: Bank of America Corporation - Inventors: Manu J. Kurian; Saritha P. Vrittamani; Jeff T. Burch - Web page: https://patentgrep.com/patent/US10771308B2 ## CPC - H04L 67/566: Grouping or aggregating service requests, e.g. for unified processing - H04L 65/60: Network streaming of media packets - H04L 67/567: Integrating service provisioning from a plurality of service providers - H04L 69/12: Protocol engines - H04L 41/0836: {to enhance reliability, e.g. reduce downtime} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A system includes a request processing system which enables the system to fulfill data requests by grouping and combining requested data elements, while conserving computing resources and increasing security of the requested data elements associated during storage and transmission over a network. The system is configured to identify one or more groups of data elements associated with one or more identifiers, each data element in a group associated with a component of an identifier. The system combines each of the one or more groups of data elements based on a unique association between the components of each identifier. The system subsequently removes the sub-wrappers from the data elements in the one or more groups of data elements, and sends the combined one or more groups of data elements to relevant requestors. ## Claims ### Claim 1 A system for fulfilling data requests, comprising: one or more interfaces operable to receive a plurality of data elements, the plurality of data elements comprising at least: a first data element in response to a first sub-request, the first data element encapsulated in a first sub-wrapper; and a second data element in response to a second sub-request, the second data element encapsulated in a second sub-wrapper; a memory operable to store the received plurality of data elements; and one or more processors communicatively coupled to the memory and operable to: upon determining that the first sub-wrapper and the second sub-wrapper are associated with a first identifier, combine the encapsulated first data element and the encapsulated second data element; remove the first sub-wrapper from the first data element and the second sub-wrapper from the second data element; and send the combined first data element and the second data element to a first requestor in response to a first request; wherein: the one or more interfaces are further operable to receive a third data element in response to a third sub-request, the third data element encapsulated in a third sub-wrapper; the third sub-wrapper is associated with a second identifier that is different from the first identifier; and the third sub-wrapper is not combined with the first data element and the second data element because the second identifier is different from the first identifier. ### Claim 2 (depends on 1) The system of claim 1, wherein the first sub-wrapper is associated with a first component of the first identifier, and the second sub-wrapper is associated with a second component of the first identifier. ### Claim 3 (depends on 2) The system of claim 2, wherein the first component of the first identifier is uniquely associated with the second component of the first identifier. ### Claim 4 (depends on 3) The system of claim 3, wherein the encapsulated first data element and the encapsulated second data element are combined based on the unique association between the first component and the second component of the first identifier. ### Claim 5 A method for fulfilling data requests, comprising: receiving, at an interface, a plurality of data elements, the plurality of data elements comprising at least: a first data element in response to a first sub-request, the first data element encapsulated in a first sub-wrapper; a second data element in response to a second sub-request, the second data element encapsulated in a second sub-wrapper; and a third data element in response to a third sub-request, the third data element encapsulated in a third sub-wrapper, wherein the third sub-wrapper is associated with a second identifier that is different from a first identifier, and the third sub-wrapper is not combined with the first data element and the second data element because the second identifier is different from the first identifier; upon determining that the first sub-wrapper and the second sub-wrapper are associated with the first identifier, combining the encapsulated first data element and the encapsulated second data element; removing, by the processor, the first sub-wrapper from the first data element and the second sub-wrapper from the second data element; sending, by the processor, the combined first data element and the second data element to a first requestor in response to a first request. ### Claim 6 (depends on 5) The method of claim 5, wherein the first sub-wrapper is associated with a first component of the first identifier; and the second sub-wrapper is associated with a second component of the first identifier. ### Claim 7 (depends on 6) The method of claim 6, wherein the first component of the first identifier is uniquely associated with the second component of the first identifier. ### Claim 8 (depends on 7) The method of claim 7, wherein the encapsulated first data element and the encapsulated second data element are combined based on the unique association between the first component and the second component of the first identifier. ### Claim 9 A method for grouping data elements, comprising: receiving, at an interface, a plurality of data elements from a plurality of data repositories, each data element encapsulated in a sub-wrapper associated with a component of an identifier; identifying, by a processor, a first subset of the plurality of data elements, each data element of the first subset encapsulated in a sub-wrapper associated with a component of a first identifier; combining, by the processor, the first subset of data elements based on the components of the first identifier; removing, by the processor, the sub-wrappers encapsulating the first subset of data elements; sending, by the processor, the combined first subset of data elements to a first requestor; identifying, by the processor, a second subset of the plurality of data elements, each data element of the second subset encapsulated in a sub-wrapper associated with a component of a second identifier; and determining, by the processor, that the second identifier is different from the first identifier; and determining, by the processor, not to combine the second subset of the plurality of data elements with the first subset of data elements because the second identifier is different from the first identifier. ### Claim 10 (depends on 9) The method of claim 9, wherein: each component of the first identifier is uniquely associated with one or more neighboring components of the first identifier, and each sub-wrapper encapsulating a data element of the first subset of data elements is uniquely associated with one or more neighboring sub-wrappers.