# US 12,182,162 B2 · Attribute sharing platform for data processing systems > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,182,162 B2 - Document ID: US12182162B2 - Status: Granted - Kind: B2 - Application number: 18/490,194 - Filed: 2023-10-19 - Published: 2024-02-08 - Granted: 2024-12-31 - Earliest claimed: 2018-05-31 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Saurabh Gupte - Web page: https://patentgrep.com/patent/US12182162B2 ## CPC - H04L 67/1091: {Interfacing with client-server systems or between P2P systems} - G06F 8/315: {Object-oriented languages} - G06F 9/543: {User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]} - G06F 16/24573: {using data annotations, e.g. user-defined metadata} - G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor - G06Q 10/0637: Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract A device may receive information for an attribute to include in a shared attribute library. The information may include an attribute identifier, data variables needed to compute a value of the attribute, and source code for computing the value of the attribute. The source code may be written in a first programming language. The device may receive a first request to compute the value of the attribute based on a first set of data variables from a first type of data application and a second request to compute the value of the attribute based on a second set of data variables from a second type of data application that is different than the first type of data application. The device may select a computing server, which may execute the first programming language, to compute the value of the attribute based on the first and second sets of data variables. ## Claims ### Claim 1 A first device, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to: identify, based on a map of attributes mapped to a plurality of second devices, and based on a particular programming language, of a plurality of programming languages associated with an attribute related to a set of data associated with an application, a second device of the plurality of second devices configured to compute a value of the attribute, wherein the plurality of second devices are associated with the plurality of programming languages; transmit, based on the map of attributes, a request including data associated with the attribute and the set of data; receive, from the second device, a computed value of the attribute; and transmit the computed value of the attribute as an input for the application. ### Claim 2 (depends on 1) The first device of claim 1, wherein the one or more processors are further configured to: validate, based on verifying that the set of data includes one or more data variables used to compute the value of the attribute, the request. ### Claim 3 (depends on 1) The first device of claim 1, wherein the second device is associated with the particular programming language, and wherein a third device of the plurality of second devices is associated with another programming language of the plurality of programming languages. ### Claim 4 (depends on 1) The first device of claim 1, wherein the one or more processors are further configured to: identify the second device based on identifying that the particular programming language is associated with the second device. ### Claim 5 (depends on 1) The first device of claim 1, wherein the request is generated based on a trigger event. ### Claim 6 (depends on 1) The first device of claim 1, wherein the application is configured to operate based on a trigger that includes at least one of: a time-based trigger, an application programming interface (API) call, an event trigger, or a throughput trigger. ### Claim 7 (depends on 1) The first device of claim 1, wherein the application is associated with at least one of: a batch application, a streaming application, or an application programming interface (API) based application. ### Claim 8 A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a first device, cause the first device to: identify, based on a map of attributes mapped to a plurality of second devices, and based on a particular programming language, of a plurality of programming languages associated with an attribute related to a set of data associated with an application, a second device of the plurality of second devices configured to compute a value of the attribute, wherein the plurality of second devices are associated with the plurality of programming languages; transmit, based on the map of attributes, a request including data associated with the attribute and the set of data; receive, from the second device, a computed value of the attribute; and transmit the computed value of the attribute as an input for the application. ### Claim 9 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein the one or more instructions further cause the first device to: validate, based on verifying that the set of data includes one or more data variables used to compute the value of the attribute, the request. ### Claim 10 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein the second device is associated with the particular programming language, and wherein a third device of the plurality of second devices is associated with another programming language of the plurality of programming languages. ### Claim 11 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein the one or more instructions further cause the first device to: identify the second device based on identifying that the particular programming language is associated with the second device. ### Claim 12 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein the request is generated based on a trigger event. ### Claim 13 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein the application is configured to operate based on a trigger that includes at least one of: a time-based trigger, an application programming interface (API) call, an event trigger, or a throughput trigger. ### Claim 14 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein the application is associated with at least one of: a batch application, a streaming application, or an application programming interface (API) based application. ### Claim 15 A method, comprising: identifying, by a first device, based on a map of attributes mapped to a plurality of second devices, and based on a particular programming language, of a plurality of programming languages associated with an attribute related to a set of data associated with an application, a second device of the plurality of second devices configured to compute a value of the attribute, wherein the plurality of second devices are associated with the plurality of programming languages; transmitting, by the first device and based on the map of attributes, a request including data associated with the attribute and the set of data; receiving, from the second device, a computed value of the attribute; and transmitting, by the first device, the computed value of the attribute as an input for the application. ### Claim 16 (depends on 15) The method of claim 15, further comprising: validating, based on verifying that the set of data includes one or more data variables used to compute the value of the attribute, the request. ### Claim 17 (depends on 15) The method of claim 15, wherein the second device is associated with the particular programming language, and wherein a third device of the plurality of second devices is associated with another programming language of the plurality of programming languages. ### Claim 18 (depends on 15) The method of claim 15, further comprising: identifying the second device based on identifying that the particular programming language is associated with the second device. ### Claim 19 (depends on 15) The method of claim 15, wherein the request is generated based on a trigger event. ### Claim 20 (depends on 15) The method of claim 15, wherein the application is configured to operate based on a trigger that includes at least one of: a time-based trigger, an application programming interface (API) call, an event trigger, or a throughput trigger.