Machine to machine data aggregator

• US 10,275,476 B2
• Filed: 12/22/2014
• Issued: 04/30/2019
• Est. Priority Date: 12/22/2014
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Dubois, Jean F., Moran, Patrick J.
• Primary Examiner(s): Le, Miranda
• Application Number:
  US14/579,307
• Publication Number:
  US 20160179849A1
• Time in Patent Office: 1,590 Days
• Field of Search: 707803
• CPC Class Codes: G06F 16/211 Schema design and management

Abstract

A computer system may include data aggregator logic configured to ingest a data item from a data source via an aggregation socket, wherein the aggregation socket is configured to ingest data items of a particular data type; identify a schema associated with the aggregation socket; convert the data item into a common data format using the identified schema; store the converted data item in a common data format storage associated with the computer device; and provide the stored data item to a data utilization system. The computer system may further maintain and record provenance and reputation models associated with data items stored in the common data format storage.

Claims

1. A method comprising:

generating, by a computer device, a plurality of schemas, wherein particular ones of the plurality of schemas convert data items of particular data types into a common data format;

associating, by the computer device, particular ones of the plurality of schemas with particular ones of a plurality of aggregation sockets, wherein different ones of the plurality of aggregation sockets are configured to ingest data items of different data types;

ingesting, by the computer device, a data item from a data source via an aggregation socket, of the plurality of aggregation sockets, wherein the aggregation socket is configured to ingest data items of a particular data type;

identifying, by the computer device, a schema, of the plurality of schemas, associated with the aggregation socket;

converting, by the computer device, the data item into a common data format using the identified schema;

storing, by the computer device, the converted data item in a common data format storage associated with the computer device;

providing, by the computer device, the stored data item to a data utilization system;

sending, by the computer device, an indication to a provenance engine that the data item has been stored in the common data format storage;

generating, by the provenance engine, a provenance record for the stored data item, in response to receiving the indication that the data item has been stored in the common data format storage, wherein the provenance record stores information identifying each event that includes accessing or modifying the stored data item, and wherein the provenance record is stored separately from the common data format storage;

detecting an event that includes accessing or modifying the stored data item;

sending, to the provenance engine, an alert that the stored data items has been accessed or modified, in response to detecting the event;

generating, by the provenance engine, a provenance event record in the generated provenance record in response to the detected event;

storing, by the provenance engine, one or more provenance parameters associated with the detected event in the generated provenance record;

determining a reputation score associated with the data source;

assigning the determined reputation score to the stored data item;

determining that a particular entity, associated with a particular reputation score, has requested to access or modify the stored data item; and

modifying the reputation score associated with the data source based on the particular reputation score associated with the particular entity.

2. The method of claim 1, further comprising:

ingesting another data item from another data source via another aggregation socket, of the plurality of aggregation sockets, wherein the other aggregation socket is configured to ingest data items of another data type that is different from the particular data type;

identifying another schema, of the plurality of schemas, associated with the other aggregation socket;

converting the other data item into the common data format using the other identified schema; and

storing the converted other data item in the common data format storage.

3. The method of claim 1, further comprising:

identifying a data processing module associated with the identified schema; and

processing the data item using the identified data processing module.

4. The method of claim 3, wherein the data processing module includes a Resource Description Framework tagging module, and wherein processing the data item using the identified data processing module includes:

adding one or more Resource Description Framework tags to the stored data item based on the identified schema.

5. The method of claim 1, wherein the one or more provenance parameters include at least one of:

information identifying a type of event associated with the detected event;

information identifying an entity accessing or modifying the stored data item;

information identifying a time and date associated with the event;

information identifying a physical or network location associated with the event;

information identifying a cause of the event;

or

information identifying a system state associated with the event.

6. The method of claim 1, wherein storing the converted data item in the common data format storage includes:

storing the converted data item in a compact binary format.

7. The method of claim 1, further comprising:

associating a field of use with the identified schema;

associating an originating entity with the identified schema; and

associating the aggregation socket with the identified schema.

8. A computer system comprising:

one or more memory devices storing instructions; and

one or more processors configured to execute the instructions to;

generate a plurality of schemas, wherein particular ones of the plurality of schemas convert data items of particular data types into a common data format;

associate particular ones of the plurality of schemas with particular ones of a plurality of aggregation sockets, wherein different ones of the plurality of aggregation sockets are configured to ingest data items of different data types;

ingest a data item from a data source via an aggregation socket, of the plurality of aggregation sockets, wherein the aggregation socket is configured to ingest data items of a particular data type;

identify a schema, of the plurality of schemas, associated with the aggregation socket;

convert the data item into a common data format using the identified schema;

store the converted data item in a common data format storage associated with the computer system;

provide the stored data item to a data utilization system;

send an indication to a provenance engine that the data item has been stored in the common data format storage;

generate a provenance record for the stored data item, in response to receiving the indication that the data item has been stored in the common data format storage, wherein the provenance record stores information identifying each event that includes accessing or modifying the stored data item, and wherein the provenance record is stored separately from the common data format storage;

detect an event that includes accessing or modifying the stored data item based on receiving an alert that the stored data item has been accessed or modified;

generate a provenance event record in the generated provenance record in response to the detected event;

store one or more provenance parameters associated with the detected event in the generated provenance record;

determine a reputation score associated with the data source;

assign the determined reputation score to the stored data item;

determine that a particular entity, associated with a particular reputation score, has requested to access or modify the stored data item; and

modify the reputation score associated with the data source based on the particular reputation score associated with the particular entity.

9. The computer system of claim 8, wherein the one or more processors are further configured to:

ingest another data item from another data source via another aggregation socket, of the plurality of aggregation sockets, wherein the other aggregation socket is configured to ingest data items of another data type that is different from the particular data type;

identify another schema, of the plurality of schemas, associated with the other aggregation socket;

convert the other data item into the common data format using the other identified schema; and

store the converted other data item in the common data format storage.

10. The computer system of claim 8, wherein the one or more processors are further configured to:

identify a data processing module associated with the identified schema; and

process the data item using the identified data processing module.

11. The computer system of claim 10, wherein the data processing module includes a Resource Description Framework tagging module, and wherein, when processing the data item using the identified data processing module, the one or more processors are further configured to:

add one or more Resource Description Framework tags to the stored data item based on the identified schema.

12. The computer system of claim 8, wherein the one or more provenance parameters include at least one of:

information identifying a type of event associated with the detected event;

information identifying an entity accessing or modifying the stored data item;

information identifying a time and date associated with the event;

information identifying information identifying a physical or network location associated with the event;

information identifying a cause of the event;

or

information identifying a system state associated with the event.

13. The computer system of claim 8, wherein the one or more processors are further configured to:

associate a field of use with the identified schema;

associate an originating entity with the identified schema; and

associate the aggregation socket with the identified schema.

14. The computer system of claim 8, wherein, when storing the converted data item in the common data format storage, the one or more processors are further configured to:

store the converted data item in a compact binary format.

15. One or more non-transitory computer-readable memory devices storing instructions executable by one or more processors, the one or more non-transitory computer-readable memory devices comprising:

one or more instructions to generate a plurality of schemas, wherein particular ones of the plurality of schemas convert data items of particular data types into a common data format;

one or more instructions to associate particular ones of the plurality of schemas with particular ones of a plurality of aggregation sockets, wherein different ones of the plurality of aggregation sockets are configured to ingest data items of different data types;

one or more instructions to ingest a data item from a data source via an aggregation socket, of the plurality of aggregation sockets, wherein the aggregation socket is configured to ingest data items of a particular data type;

one or more instructions to identify a schema, of the plurality of schemas, associated with the aggregation socket;

one or more instructions to convert the data item into a common data format using the identified schema;

one or more instructions to store the converted data item in a common data format storage;

one or more instructions to provide the stored data item to a data utilization system;

one or more instructions to send an indication to a provenance engine that the data item has been stored in the common data format storage;

one or more instructions to generate, by the provenance engine, a provenance record for the stored data item, in response to receiving the indication that the data item has been stored in the common data format storage, wherein the provenance record stores information identifying each event that includes accessing or modifying the stored data item, and wherein the provenance record is stored separately from the common data format storage;

one or more instructions to detect an event that includes accessing or modifying the stored data item;

one or more instructions to send, to the provenance engine, an alert that the stored data items has been accessed or modified, in response to detecting the event that includes accessing or modifying the stored data item;

one or more instructions to generate, by the provenance engine, a provenance event record in the generated provenance record in response to the detected event;

one or more instructions to store, by the provenance engine, one or more provenance parameters associated with the detected event in the generated provenance record;

one or more instructions to determine a reputation score associated with the data source;

one or more instructions to assign the determined reputation score to the stored data item;

one or more instructions to determine that a particular entity, associated with a particular reputation score, has requested to access or modify the stored data item; and

one or more instructions to modify the reputation score associated with the data source based on the particular reputation score associated with the particular entity.

16. The one or more non-transitory computer-readable memory devices of claim 15, wherein the one or more provenance parameters include at least one of:

information identifying a type of event associated with the detected event;

information identifying an entity accessing or modifying the stored data item;

information identifying a time and date associated with the event;

information identifying a physical or network location associated with the event;

information identifying a cause of the event;

or

information identifying a system state associated with the event.

17. The one or more non-transitory computer-readable memory devices of claim 15, further comprising:

one or more instructions to associating a field of use with the identified schema;

one or more instructions to associating an originating entity with the identified schema; and

one or more instructions to associating the aggregation socket with the identified schema.

18. The one or more non-transitory computer-readable memory devices of claim 15, further comprising:

one or more instructions to ingest another data item from another data source via another aggregation socket, of the plurality of aggregation sockets, wherein the other aggregation socket is configured to ingest data items of another data type that is different from the particular data types;

one or more instructions to identify another schema, of the plurality of schemas, associated with the other aggregation socket;

one or more instructions to convert the other data item into the common data format using the other identified other schema; and

one or more instructions to store the converted other data item in the common data format storage.

19. The one or more non-transitory computer-readable memory devices of claim 18, further comprising:

one or more instructions to identify a data processing module associated with the identified other schema; and

one or more instructions to process the data item using the identified data processing module.

20. The one or more non-transitory computer-readable memory devices of claim 19, wherein the data processing module includes a Resource Description Framework tagging module, and wherein the one or more instructions to process the data item using the identified data processing module further include:

one or more instructions to add one or more Resource Description Framework tags to the stored data item based on the identified schema.