# US 12,007,960 B2 · Methods make web and business application data access agnostic to schema variations and migrations > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,007,960 B2 - Document ID: US12007960B2 - Status: Granted - Kind: B2 - Application number: 17/726,781 - Filed: 2022-04-22 - Published: 2023-10-26 - Granted: 2024-06-11 - Earliest claimed: 2022-04-22 - Assignees: Dell Products L.P. - Applicants: Dell Products L.P. - Inventors: Ching-Yun Chao; Steve Petrucci - Web page: https://patentgrep.com/patent/US12007960B2 ## CPC - G06F 16/211: {Schema design and management} - G06F 16/258: {Data format conversion from or to a database} - G06F 16/284: {Relational databases} - G06F 16/86: {Mapping to a database} - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - G06Q 10/10: Office automation; Time management - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - 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 system, method, and computer-readable medium are disclosed for performing a data schema mapping operation. The data schema mapping operation includes receiving product information from a product supplier, the product information comprising a first document corresponding to a first data schema, the first data schema comprising an unspecified JavaScript Object Notation (JSON) schema; identifying a plurality of components within the first document corresponding to the first data schema, the plurality of components comprising JSON data elements; identifying a second plurality of components corresponding to a second data schema, the second data schema comprising a defined data schema, the second data schema being associated with a data center services provider, at least some of the second plurality of components being associated with a relational database; and, mapping a component of the document corresponding to the first data schema to a component corresponding to the second data schema. ## Claims ### Claim 1 A computer-implementable method for performing a data content mapping operation, comprising: receiving product information from a product supplier, the product information comprising a first document corresponding to a first data schema, the first data schema comprising an unspecified JavaScript Object Notation (JSON) schema, the unspecified JSON schema comprising a data schema having an undefined format, the undefined format being undefined by a recipient of a document conforming to the unspecified JSON schema; identifying a plurality of components within the first document corresponding to the first data schema, the plurality of components comprising JSON data elements, the identifying comprising constructing a node path representation of the plurality of components within the first document; identifying a second plurality of components corresponding to a second data schema, the second data schema comprising a defined data schema, the second data schema being associated with a services provider, the defined data schema comprising a data schema conforming to a defined format, the defined format being prescribed by the service provider, at least some of the second plurality of components being associated with a relational database; and, mapping a component of the document corresponding to the first data schema to a component corresponding to the second data schema. ### Claim 2 (depends on 1) The method of claim 1, wherein: the identifying the plurality of components within the first document comprises identifying a structure of the first document. ### Claim 3 (depends on 2) The method of claim 2, wherein: the node path representation comprises identified node paths and node types; and, the identified node paths and node types are used to generate an associated document node path listing for the first document. ### Claim 4 (depends on 3) The method of claim 3, further comprising: identifying parent nodes and leaf nodes within the node path using the node path representation of the plurality of components within the first document. ### Claim 5 (depends on 4) The method of claim 4, further comprising: replacing each of the leaf nodes with a respective link in the parent nodes. ### Claim 6 (depends on 1) The method of claim 1, further comprising: receiving a second document from the product supplier; determining whether the second document conforms to the first data schema; identifying differences between the first document and the second document; and mapping a component of the document corresponding to an identified difference of the first data schema of the second document to a component corresponding to the second data schema. ### Claim 7 A system comprising: a processor; a data bus coupled to the processor; and a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for: receiving product information from a product supplier, the product information comprising a first document corresponding to a first data schema, the first data schema comprising a unspecified JavaScript Object Notation (JSON) schema, the unspecified JSON schema comprising a data schema having an undefined format, the undefined format being undefined by a recipient of a document conforming to the unspecified JSON schema; identifying a plurality of components within the first document corresponding to the first data schema, the plurality of components comprising JSON data elements, the identifying comprising constructing a node path representation of the plurality of components within the first document; identifying a second plurality of components corresponding to a second data schema, the second data schema comprising a defined data schema, the second data schema being associated with a services provider, the defined data schema comprising a data schema conforming to a defined format, the defined format being prescribed by the service provider, at least some of the second plurality of components being associated with a relational database; and, mapping a component of the document corresponding to the first data schema to a component corresponding to the second data schema. ### Claim 8 (depends on 7) The system of claim 7, wherein: the identifying the plurality of components within the first document comprises identifying a structure of the first document. ### Claim 9 (depends on 8) The system of claim 8, wherein: the node path representation comprises identified node paths and node types; and, the identified node paths and node types are used to generate an associated document node path listing for the first document. ### Claim 10 (depends on 9) The system of claim 9, wherein the instructions executable by the processor are further configured for: identifying parent nodes and leaf nodes within the node path using the node path representation of the plurality of components within the first document. ### Claim 11 (depends on 10) The system of claim 10, wherein the instructions executable by the processor are further configured for: replacing each of the leaf nodes with a respective link in the parent nodes. ### Claim 12 (depends on 7) The system of claim 7, wherein the instructions executable by the processor are further configured for: receiving a second document from the product supplier; determining whether the second document conforms to the first data schema; identifying differences between the first document and the second document; and mapping a component of the document corresponding to an identified difference of the first data schema of the second document to a component corresponding to the second data schema. ### Claim 13 A non-transitory, computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for: receiving product information from a product supplier, the product information comprising a first document corresponding to a first data schema, the first data schema comprising an unspecified JavaScript Object Notation (JSON) schema, the unspecified JSON schema comprising a data schema having an undefined format, the undefined format being undefined by a recipient of a document conforming to the unspecified JSON schema; identifying a plurality of components within the first document corresponding to the first data schema, the plurality of components comprising JSON data elements, the identifying comprising constructing a node path representation of the plurality of components within the first document; identifying a second plurality of components corresponding to a second data schema, the second data schema comprising a defined data schema, the second data schema being associated with a services provider, the defined data schema comprising a data schema conforming to a defined format, the defined format being prescribed by the service provider, at least some of the second plurality of components being associated with a relational database; and, mapping a component of the document corresponding to the first data schema to a component corresponding to the second data schema. ### Claim 14 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein: the identifying the plurality of components within the first document comprises identifying a structure of the first document. ### Claim 15 (depends on 14) The non-transitory, computer-readable storage medium of claim 14, wherein: the node path representation comprises identified node paths and node types; and, the identified node paths and node types are used to generate an associated document node path listing for the first document. ### Claim 16 (depends on 15) The non-transitory, computer-readable storage medium of claim 15, wherein the computer executable instructions are further configured for: identifying parent nodes and leaf nodes within the node path using the node path representation of the plurality of components within the first document. ### Claim 17 (depends on 16) The non-transitory, computer-readable storage medium of claim 16, wherein the computer executable instructions are further configured for: replacing each of the leaf nodes with a respective link in the parent nodes. ### Claim 18 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein the computer executable instructions are further configured for: receiving a second document from the product supplier; determining whether the second document conforms to the first data schema; identifying differences between the first document and the second document; and mapping a component of the document corresponding to an identified difference of the first data schema of the second document to a component corresponding to the second data schema. ### Claim 19 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein: the computer executable instructions are deployable to a client system from a server system at a remote location. ### Claim 20 (depends on 13) The non-transitory, computer-readable storage medium of claim 13, wherein: the computer executable instructions are provided by a service provider to a user on an on-demand basis.