Data loader and mapper tool

Patent metadata

Field	Value
Publication number	US-10248736-B1
Application number	US-201615269602-A
Country	US
Kind code	B1
Filing date	Sep 19, 2016
Priority date	Sep 19, 2016
Publication date	Apr 2, 2019
Grant date	Apr 2, 2019

Abstract

A method of managing data in a telecommunication network data structure is disclosed. The method comprises receiving, by a translation application executing on a telecommunication network computer system, a request to translate source data stored in a source data structure to a target data structure; identifying, by way of information stored in a taxonomy repository, a data store key within the source data; a category of an element of the source data; inferring, by way of information stored in the taxonomy repository a relationship between the data store key and the element; converting, by the translation application, a format of the data store key to a format of a target data store key, and a format of the element to a format of a target element. The method further comprises storing, by the translation application, the target data store key and the target element in the target data structure.

First claim

The invention claimed is:

1. A telecommunication network computer system for converting source data in a source data structure to target data in a target data structure, where the source data structure and target data structure are arbitrarily selected from a plurality of at least fifty different data structures, comprising:
a memory;
a processor; and
a program stored in the memory that, when executed by the processor causes the processor to:
receive a request to translate source data in a source data structure to target data in a target data structure, the source data comprising one or more source tables stored in the source data structure, the one or more source tables comprising a data store key and a first element, wherein the source data structure is different from the target data structure; and
automatically generate data store keys and inter-field relationships from the source data structure by further causing the processor to:
based on information stored in a taxonomy repository:
identify the data store key comprises key information;
identify a category of the first element;
identify a relationship between the data store key and the first element in the one or more source tables;

convert a format of the data store key to a format of a target data store key, wherein when the processor converts the format of the data store key to the format of the target data store key, the program causes the processor to:
identify a structure of the target data store key based on information in the taxonomy repository, the taxonomy repository defining a key structure compatible with the target data structure; and
change a structure of the data store key to the structure of the target data store key;

convert a format of the first element to a format of a target element; and
store the target data store key and the target element in the target data structure.

2. The system of claim 1 , the program, when executed further causes the processor to:
receive a request to translate second source data in a second source data structure to the target data structure, the second source data structure different from the source data structure;
identify that a redundant element in the second source data structure is in the target data structure; and
refrain from translating the redundant element in the target data structure.

3. The system of claim 1 , wherein the taxonomy repository comprises information about the source data structure and the target data structure corresponding to one selected from the group consisting of: a type of data, a format of data, a location of data, and a category of data.

4. The system of claim 1 , wherein when the processor converts the format of the data store key to the format of the target data store key and converts the format of the first element to the format of the target element, the program further causes the processor to:
convert source data comprising the data store key and the first element to data to a generic format; and
convert the data in the generic format to the format of the target data store key and the target element.

5. The system of claim 1 , wherein when the processor converts the format of the first element to the format of the target element the program causes the processor to:
identify the format of the target element based on information in the taxonomy repository, the taxonomy repository defining:
a location for the target element in the target data structure, and
a format of the target element based on a format of data stored in a column or row comprising the location for the target element within the target data structure; and

change the format of the first element to the format of the target element defined in the taxonomy repository,
wherein the format of the target element is at least one selected from the group consisting of: integer number; decimal number; long data; long raw data; and text.

6. The system of claim 1 , wherein when the processor stores the target data store key the program causes the processor to:
identify a location for the target element based on information in the taxonomy repository, the taxonomy repository defining a column or row of data in the target data structure comprising data corresponding to the category of the first element; and
store a copy of the first element at the location.

7. A telecommunication network computer system for converting source data in a source data structure to target data in a target data structure, where the source data structure and target data structure are arbitrarily selected from a plurality of at least fifty different data structures, comprising:
a memory;
a processor; and
a program stored in the memory that, when executed by the processor causes the processor to:
receive a request to translate data from a source data structure to a target data structure, the source data structure comprising a first table of data and a second table of data;
infer relationships among fields by further causing the processor to:
access a taxonomy repository related to a database of a telecommunications entity and identify a relationship between elements in the source data structure based on information in the taxonomy repository;
access the taxonomy repository and identify a category of a column of data in the first table and a category of a column of data in the second table;

determine the categories of data are the same;
compare data in the column of data in the first table and in the column of data in the second table;
based on the comparison, determine that duplicate elements are present between the column of data in the first table and the column of data in the second table;
determine the first table comprises the data store of record based on information in the taxonomy repository; and
translate the first table of data and the second table of data to the target data structure, translating one instance of the duplicate elements in the target data structure from the first table, wherein when the processor translates the first table of data and the second table of data to the target data structure, the program causes the processor to:
identify a location to copy an element of the first table based on information in the taxonomy repository, the taxonomy repository defining:
a location for the target element in the target data structure, and
a format of the target element based on a format of data stored in a column or row comprising the location for the target element within the target data structure; and

change the format of the element to the format of the target element defined in the taxonomy repository.

8. The system of claim 7 , wherein when the processor accesses the taxonomy repository and identifies the relationship between elements in the source data structure, the program causes the processor to:
identify, based on information in the taxonomy repository, a column of data in the first table as comprising a data store key; and
identify, based on information in the taxonomy repository, a relationship between the data store key and a second column of data in the first table of data.

9. The system of claim 7 , wherein when the processor accesses the taxonomy repository and identifies the relationship between elements in the source data structure, the program causes the processor to:
based on information in the taxonomy repository,
identify a column of data in the first table as comprising a foreign data store key,
identify child data corresponding to the foreign data store key, the child data in a third table in the source data structure.

10. The system of claim 9 , wherein when the processor translates the first table of data and the second table of data, t

Assignees

• Sprint Communications Co Lp

Inventors

• Carroll Roberta M
• Floyd Jr Carter Wayne
• Hoskins Steven A
• Samson Kenneth W

Classifications

• H04L67/1095 Primary

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• G06F16/211

  Schema design and management · CPC title

• G06F16/258

  Data format conversion from or to a database · CPC title

• G06F16/957 Primary

  Browsing optimisation, e.g. caching or content distillation · CPC title