Canonical model for product development

Patent metadata

Field	Value
Publication number	US-12020207-B2
Application number	US-202017071074-A
Country	US
Kind code	B2
Filing date	Oct 15, 2020
Priority date	Oct 15, 2019
Publication date	Jun 25, 2024
Grant date	Jun 25, 2024

Abstract

Methods and systems disclosed herein describe a canonical model that sets forth a standardized schema that represents data entities and their relationships as a logical data structure across multiple business units. A schema validator module may validate application-specific schema against the canonical module. Additionally, legacy and/or existing applications may be upgraded, through a transformation module, to comply with the canonical model. The transformation module may transform application-specific data and/or information to the standardized schema, and vice versa, to ensure that legacy and/or existing applications may communicate with applications and/or processing engines that comply with the standardized schema.

First claim

What is claimed is:

1. A method comprising:
receiving, at a computing device, one or more inputs, wherein the one or more inputs are in a first format;
validating the first format of the one or more inputs to determine whether the one or more inputs comply with a schema defined by a canonical model;
transforming the first format of the one or more inputs into a second format based on a determination that the first format of the one or more inputs does not comply with the schema;
generating a request using the one or more inputs in the second format, wherein the request comprises a serialized format of the one or more inputs;
transmitting, to a processing engine, the request;
receiving a response from the processing engine, wherein the response comprises one or more outputs;
converting the one or more outputs into the second format by deserializing the response;
transforming the one or more outputs from the second format to the first format; and
generating a product by merging the one or more inputs and the one or more outputs.

2. The method of claim 1 , further comprising:
decompressing the one or more inputs prior to validating the first format of the one or more inputs to determine whether the one or more inputs comply with the schema defined by the canonical model.

3. The method of claim 1 , wherein validating the first format of the one or more inputs further comprises:
determining whether the one or more inputs comply with a version of the schema defined by the canonical model.

4. The method of claim 1 , wherein transforming the first format of the one or more inputs into the second format further comprises:
mapping, using a configuration file, a first input of the one or more inputs to an input associated with the second format.

5. The method of claim 1 , wherein the first format comprises an application-specific schema.

6. The method of claim 1 , wherein the second format comprises a format associated with a target application.

7. The method of claim 1 , wherein the request further comprises at least one of:
a content type;
a content encoding;
a source application identifier; or
a target application identifier.

8. The method of claim 1 , further comprising:
validating the request prior to transmitting the request to the processing engine.

9. The method of claim 1 , wherein transforming the one or more outputs from the second format to the first format further comprises:
mapping a first output of the one or more outputs to an output associated with the first format, the first output mapped to the output using a configuration file and previously stored mapping information.

10. The method of claim 1 , wherein the one or more outputs comprise a product offering generated from one or more data objects associated with the canonical model.

11. A system comprising:
a computing device in communication with a server, the computing device is configured to:
receive one or more inputs, wherein the one or more inputs are in a first format;
validate the first format of the one or more inputs to determine whether the one or more inputs comply with a schema defined by a canonical model;
transform the first format of the one or more inputs into a second format based on a determination that the first format of the one or more inputs does not comply with the schema;
generate a request using the one or more inputs in the second format, wherein the request comprises a serialized format of the one or more inputs;
transmit the request to a server;
receive a response from the server, wherein the response comprises one or more outputs;
convert the one or more outputs into the second format by deserializing the response;

transform the one or more outputs from the second format to the first format; and
generate a product by merging the one or more inputs and the one or more outputs.

12. The system of claim 11 , wherein the server comprises a plurality of services, wherein one of the plurality of services receives the request and generates the response.

13. The system of claim 11 , wherein the server comprises a database, wherein the response is generated using the database.

14. The system of claim 11 , wherein the computing device is further configured to receive a configuration file that defines one or more parameters for determining whether the one or more inputs comply with the schema defined by the canonical model.

15. The system of claim 14 , wherein the configuration file is received via a push from a second server.

16. The system of claim 11 , wherein the product comprises at least one of: an insurance policy or an insurance quote.

17. A non-transitory computer-readable medium comprising instructions, that when executed by one or more processors, cause a computing device to:
receive one or more inputs, wherein the one or more inputs are in a first format wherein the first format comprises an application-specific schema;
validate the first format of the one or more inputs to determine whether the one or more inputs comply with a schema defined by a canonical model;
transform the first format of the one or more inputs into a second format based on a determination that the first format of the one or more inputs does not comply with the schema by mapping a first input of the one or more inputs to an input associated with the second format using a configuration file, wherein the second format comports with the canonical model;
generate a request using the one or more inputs in the second format, wherein the request comprises one or more of a content type, a content encoding, a source application identifier, a target application, identifier, or a serialized format of the one or more inputs;
transmit the request to a server;
receive a response from the server, wherein the response comprises one or more outputs;
convert the one or more outputs into the second format by deserializing the response;
transform the one or more outputs from the second format to the first format by mapping a first output of the one or more outputs to an output associated with the first format using the configuration file; and
generate a product by merging the one or more inputs and the one or more outputs.

18. The non-transitory computer readable medium of claim 17 , wherein the server comprises one or more processing engines.

19. The non-transitory computer readable medium of claim 17 , wherein the instructions further cause the computing device to:
decompress the one or more inputs prior to validating the first format of the one or more inputs to determine whether the one or more inputs comply with the schema defined by the canonical model.

20. The non-transitory computer readable medium of claim 17 , wherein the one or more outputs comprise a product offering generated from one or more data objects associated with the canonical model.

Assignees

• Allstate Insurance Co

Inventors

• Yang Kevin
• Kamble Hruday
• Gupta Avinash

Classifications

• Y10S707/99941

  Database schema or data structure · CPC title

• G06Q40/08

  Insurance · CPC title

• G06F16/212

  with details for data modelling support · CPC title

• G06F16/258

  Data format conversion from or to a database · CPC title

• G06Q10/101 Primary

  Collaborative creation, e.g. joint development of products or services · CPC title