Transforming data into data entities

Patent metadata

Field	Value
Publication number	US-2025200076-A1
Application number	US-202318538123-A
Country	US
Kind code	A1
Filing date	Dec 13, 2023
Priority date	Dec 13, 2023
Publication date	Jun 19, 2025
Grant date	—

Abstract

In some implementations, a data management system may obtain, via a data interlocutor, a set of data intended for inclusion in a database, wherein the set of data is associated with at least one data type, wherein the set of data comprises at least one data value. The data management system may generate, via the data interlocutor, a set of data entities based on the set of data and a set of security metadata associated with the set of data, wherein the set of data entities comprises a data entity associated with a data value of the at least one data value, the data entity comprising transaction authorization information associated with the data value. The data management system may output, via the data interlocutor, the set of data entities for inclusion in the database.

First claim

1 . A system for transforming data into data entities, the system comprising:
one or more memories; and one or more processors, communicatively coupled to the one or more memories, configured to:
obtain, via a data interlocutor, a set of data intended for inclusion in a database, wherein the set of data is associated with at least one data type, wherein the set of data comprises at least one data value, and wherein the data interlocutor is particular to the at least one data type;
obtain, via the data interlocutor, a set of security metadata associated with the set of data, the set of security metadata comprising at least one subset of metadata associated with the at least one data value;
generate, via the data interlocutor, a set of data entities based on the set of data and the set of security metadata, wherein the set of data entities comprises a data entity associated with a data value of the at least one data value, the data entity comprising transaction authorization information associated with the data value; and
output, via the data interlocutor, the set of data entities for inclusion in the database.

2 . The system of claim 1 , wherein the one or more processors are further configured to:
encrypt, based on the at least one data type, the set of data entities prior to outputting the set of data entities.

3 . The system of claim 1 , wherein the data entity comprises a data object.

4 . The system of claim 1 , wherein the transaction authorization information indicates at least one of an authorized transaction type associated with the data value, an authorized transaction party associated with the data value, or an authorized user associated with the data value.

5 . (canceled)

6 . The system of claim 1 , wherein the data interlocutor comprises an application programming interface.

7 . The system of claim 1 , wherein the data interlocutor comprises an agent component of an application, wherein at least one component of the application is instantiated on a source device associated with the set of data.

8 . The system of claim 1 , wherein the data interlocutor is a component of a data storage system including the database.

9 . The system of claim 1 , wherein the one or more processors are further configured to:
obtain a request for the data value; obtain, from the database, the data entity associated with the data value; extract the data value from the data entity; and output the data value.

10 . A method of transforming data into data entities, the method comprising:
obtaining, via a data interlocutor, a set of data intended for inclusion in a database, wherein the set of data is associated with at least one data type, wherein the set of data comprises at least one data value, and wherein the data interlocutor is particular to the at least one data type; generating, via the data interlocutor, a set of data entities based on the set of data and a set of security metadata associated with the set of data, wherein the set of data entities comprises a data entity associated with a data value of the at least one data value, the data entity comprising transaction authorization information associated with the data value; and outputting, via the data interlocutor, the set of data entities for inclusion in the database.

11 . The method of claim 10 , further comprising encrypting the set of data entities prior to outputting the set of data entities.

12 . The method of claim 10 , wherein the data entity comprises a data object.

13 . The method of claim 10 , wherein the transaction authorization information indicates at least one of an authorized transaction type associated with the data value, an authorized transaction party associated with the data value, or an authorized user associated with the data value.

14 . The method of claim 10 , further comprising:
obtaining a request for the data value; obtaining, from the database, the data entity associated with the data value; extracting the data value from the data entity; and outputting the data value.

15 . 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 device, cause the device to:
obtain, via a data interlocutor, a set of data intended for inclusion in a database, wherein the set of data is associated with at least one data type, wherein the set of data comprises at least one data value, and wherein the data interlocutor is particular to the at least one data type;
generate, via the data interlocutor, a set of data entities based on the set of data and a set of security metadata associated with the set of data, wherein the set of data entities comprises a data entity associated with a data value of the at least one data value, the data entity comprising transaction authorization information associated with the data value; and
output, via the data interlocutor, the set of data entities for inclusion in the database.

16 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the device to encrypt the set of data entities prior to outputting the set of data entities.

17 . The non-transitory computer-readable medium of claim 15 , wherein the transaction authorization information indicates at least one of an authorized transaction type associated with the data value, an authorized transaction party associated with the data value, or an authorized user associated with the data value.

18 . (canceled)

19 . The non-transitory computer-readable medium of claim 15 , wherein the data interlocutor comprises at least one of an application programming interface, an agent component of an application, or a component of a data storage system including the database.

20 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the device to:
obtain a request for the data value; obtain, from the database, the data entity associated with the data value; extract the data value from the data entity; and output the data value.

21 . The system of claim 1 , wherein each data type, of a plurality of data types, has a different corresponding data interlocutor.

22 . The system of claim 1 , wherein the one or more processors are further configured to:
generate, via another data interlocutor, another set of data entities based on another set of data intended for inclusion in a database, wherein the other set of data is associated with a particular data type that is different from the at least one data type, and wherein the other data interlocutor is particular to the particular data type.

Assignees

• Capital One Services Llc

Inventors

• Ivaturi Ravi K
• Ceesay Ebrima N

Classifications

• G06F21/6218

  to a system of files or objects, e.g. local or distributed file system or database · CPC title

• G06F9/466

  Transaction processing · CPC title

• G06F16/24573

  using data annotations, e.g. user-defined metadata · CPC title

• G06F16/288 Primary

  Entity relationship models · CPC title