US 11,917,026 B2
Dynamic mapping and integration via a meta-model definitional platform
Laurence Karl Grey, San Ramon, CA (US); and Brian Mark Sparling, Fremont, CA (US)
Assigned to Mutara, Inc., San Ramon, CA (US)
Filed by Mutara, Inc., San Ramon, CA (US)
Filed on Jan. 25, 2022, as Appl. No. 17/584,373.
Claims priority of provisional application 63/251,480, filed on Oct. 1, 2021.
Claims priority of provisional application 63/142,975, filed on Jan. 28, 2021.
Prior Publication US 2022/0239759 A1, Jul. 28, 2022
Int. Cl. H04L 67/00 (2022.01); G06F 16/25 (2019.01); G06F 16/22 (2019.01); G06F 16/178 (2019.01)
CPC H04L 67/34 (2013.01) [G06F 16/1794 (2019.01); G06F 16/2291 (2019.01); G06F 16/258 (2019.01)] 19 Claims
OG exemplary drawing
 
1. A computer implemented method for dynamic mapping and integration between one or more software applications via a meta-model definitional application platform, comprising: receiving from a target server, system, database, or computing device an at least one input data object or request;
transforming the at least one input data object or request into a single normalized and encrypted dataset;
loading from a source server, system, database, or computing device an at least one meaningful data object from the meta-model definitional application platform into a memory, the at least one meaningful data object including one or more integration type definitions and one or more target specific structural mapping definitions for enabling a dynamic mapping of the at least one input data object or request from an input JSON datatype associated with a first software application to a target datatype associated with a second software application, the at least one meaningful data object being configured to perform actions in the meta-model application platform including reporting and analytics;
via an at least one processor coupled to the memory:
identifying, via a queue service manager, an integration type definition of the at least one input data object or request from among the one or more integration type definitions included in the at least one meaningful data object;
loading, based on the identified integration type definition, a target specific structural mapping definition from among the one or more target specific structural mapping definitions included in the at least one meaningful data object;
pre-processing the at least one input data object or request comprising:
decrypting the single normalized and encrypted dataset produced from the at least one input data object or request;
converting data in the received at least one input data object or request to an appropriate data type for storage; and
creating one or more default values for non-existent data in the at least one input data object or request to comply with the loaded target specific structural mapping definition;
transforming, in sequence, the pre-processed at least one input data object or request, comprising:
identifying one or more distinct data elements and their associated values in the pre-processed at least one input data object or request; and
mapping the one or more identified distinct data elements according to the target specific structural mapping definition;
generating an at least one output data object; and
transmitting the at least one output data object from the source server, system, database, or computing device into the target server, system, database, or computing device.