# US 2024/0004840 A1 · Automatic file format conversion system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0004840 A1
- Document ID: US20240004840A1
- Status: Published application
- Kind: A1
- Application number: 18/343,160
- Filed: 2023-06-28
- Published: 2024-01-04
- Earliest claimed: 2022-06-29
- Assignees: State Farm Mutual Automobile Insurance Company
- Applicants: State Farm Mutual Automobile Insurance Company
- Inventors: Shrenik Vora; Kenneth Albin; Santhosh Thangavelu; Kranthi Poladi; Sneha Vemula; Sivaraj Bathran
- Web page: https://patentgrep.com/patent/US20240004840A1

## CPC

- G06F 16/1794: {Details of file format conversion}
- G06F 11/0775: {Content or structure details of the error report, e.g. specific table structure, specific error fields}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A computer-implemented conversion engine can automatically determine source file formats of a set of source files, and invoke corresponding file converters to convert the source files into output files that are formatted according to the same target file format. If an individual source file is larger than a file size threshold, the conversion engine can divide the source file into smaller component files, separately convert the individual component files into the target file format, and assemble the converted component files into an output file that corresponds to the source file.

## Claims

### Claim 1

A computer-implemented method, comprising:
determining, by at least one processor, one or more source file formats of source files in a source directory;
identifying, by the at least one processor, one or more file converters configured to convert files of the one or more source file formats into a target file format;
converting, by the at least one processor, and using the one or more file converters, the source files into corresponding output files that are formatted according to the target file format; and
storing, by the at least one processor, the corresponding output files in a destination directory.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein converting a particular source file into a corresponding output file comprises:
determining, by the at least one processor, that a size of the particular source file exceeds a file size threshold;
dividing, by the at least one processor, the particular source file into component files that have sizes less than or equal to the file size threshold;
converting, by the at least one processor, and using a file converter associated with a source file format of the particular source file, the component files into converted component files formatted according to the target file format; and
assembling, by the at least one processor, the converted component files into the corresponding output file.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2, wherein the at least one processor converts different component files substantially simultaneously via parallel processing.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the at least one processor converts different source files substantially simultaneously via parallel processing.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein the at least one processor comprises different processors of different computing devices, and the different processors of different computing devices convert different source files substantially simultaneously.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, further comprising validating, by the at least one processor, an output file that corresponds to a particular source file, wherein validating the output file includes determining that the output file and the particular source file contain a same number of records.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, wherein the particular source file is a mainframe file, and the at least one processor determines a number of records in the particular source file based on a control file associated with the mainframe file.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, further comprising:
determining, by the at least one processor, that all of the source files in the source directory have been converted into the corresponding output files in the destination directory; and
sending, by the at least one processor, a notification to at least one destination, the notification indicating that conversion operations associated with the source directory are complete.

### Claim 9 (depends on 8)

The computer-implemented method of claim 8, wherein the notification includes at least one of:
an indication that the conversion operations are complete,
at least a portion of an error log identifying errors that occurred during conversion of the source files into the corresponding output files, or
a preview of records in the corresponding output files.

### Claim 10 (depends on 9)

The computer-implemented method of claim 9, wherein the at least one processor omits the preview of the records from the notification based on configuration data indicating that the source files contain sensitive data.

### Claim 11

One or more computing devices, comprising:
at least one processor;
memory storing computer-executable instructions associated with a conversion engine that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
identifying, based on configuration data:
a source directory;
a destination directory; and
a target file format;
determining one or more source file formats of source files in the source directory;
identifying one or more file converters configured to convert files of the one or more source file formats into the target file format;
converting, using the one or more file converters, the source files into corresponding output files formatted according to the target file format; and
storing the corresponding output files in the destination directory.

### Claim 12 (depends on 11)

The one or more computing devices of claim 11, wherein the configuration data indicates a file size threshold, and the operations further comprise:
identifying one or more large source files in the source directory that have sizes that exceed the file size threshold;
converting the one or more large source files by individually dividing the one or more large source files into component files that have sizes less than or equal to the file size threshold;
converting, using the one or more file converters associated with source file formats of the one or more large source files, the component files into converted component files formatted according to the target file format; and
assembling the converted component files into one or more large output files that correspond to the one or more large source files.

### Claim 13 (depends on 11)

The one or more computing devices of claim 11, wherein the operations further comprise validating an output file that corresponds to a particular source file, by determining that the output file and the particular source file contain a same number of records.

### Claim 14 (depends on 11)

The one or more computing devices of claim 11, wherein the configuration data indicates a destination for a notification, wherein the operations further comprise sending the notification to the destination upon completion of conversion of the source files into the corresponding output files.

### Claim 15 (depends on 14)

The one or more computing devices of claim 14, wherein the operations further comprise:
including, in the notification, a preview of records in the corresponding output files based on a first indication in the configuration data that the source files include sensitive data, or
omitting, from the notification, the preview of the records based on a second indication in the configuration data that the source files do not include sensitive data.

### Claim 16

One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by at least one processor, cause the at least one processor to perform operations comprising:
identifying, based on configuration data:
a source directory;
a destination directory; and
a target file format;
determining one or more source file formats of source files in the source directory;
identifying one or more file converters configured to convert files of the one or more source file formats into the target file format;
converting, using the one or more file converters, the source files into corresponding output files formatted according to the target file format; and
storing the corresponding output files in the destination directory.

### Claim 17 (depends on 16)

The one or more non-transitory computer-readable media of claim 16, wherein the configuration data indicates a file size threshold, and the operations further comprise:
identifying one or more large source files in the source directory that have sizes that exceed the file size threshold;
converting the one or more large source files by individually dividing the one or more large source files into component files that have sizes less than or equal to the file size threshold;
converting, using the one or more file converters associated with source file formats of the one or more large source files, the component files into converted component files formatted according to the target file format; and
assembling the converted component files into one or more large output files that correspond to the one or more large source files.

### Claim 18 (depends on 16)

The one or more non-transitory computer-readable media of claim 16, wherein the operations further comprise validating an output file that corresponds to a particular source file, by determining that the output file and the particular source file contain a same number of records.

### Claim 19 (depends on 16)

The one or more non-transitory computer-readable media of claim 16, wherein the configuration data indicates a destination for a notification, wherein the operations further comprise sending the notification to the destination upon completion of conversion of the source files into the corresponding output files.

### Claim 20 (depends on 19)

The one or more non-transitory computer-readable media of claim 19, wherein the operations further comprise:
including, in the notification, a preview of records in the corresponding output files based on a first indication in the configuration data that the source files include sensitive data, or
omitting, from the notification, the preview of the records based on a second indication in the configuration data that the source files do not include sensitive data.

### Claim 21

A computing system, comprising:
selection means for selecting source files in a source directory;
identification means for identifying source file formats of the source files;
conversion means for converting the source files from the source file formats into corresponding output files of a target file format; and
storage means for storing the corresponding output files in a destination directory.

### Claim 22 (depends on 21)

The computing system of claim 21, wherein the conversion means comprises means for:
dividing large source files, of the source files, that exceed a file size threshold into smaller component files that have sizes less than or equal to the file size threshold;
converting the smaller component files into converted component files of the target file format; and
assembling the converted component files into output files that correspond to the large source files.

### Claim 23 (depends on 21)

The computing system of claim 21, further comprising validation means for validating that the source files and the corresponding output files contain a same number of records.

### Claim 24 (depends on 21)

The computing system of claim 21, further comprising notification means for sending a notification to at least one destination, the notification including at least one of:
an indication that conversions of the source files into the corresponding output files are complete,
at least a portion of an error log identifying errors that occurred during conversion of the source files into the corresponding output files, or
a preview of records in the corresponding output files.
