Automatic generation of certificate of origin (COO) for software systems

1. A system, comprising:

at least one computing device, comprising one or more processors, a memory, and a storage storing computer executable code, wherein the computer executable code, when executed at the one or more processors, is configured to:

process a plurality of source modules to generate a plurality of binary modules corresponding to the source modules, wherein each source module has at least one source file and a control file comprising a certificate of origin (COO) of the source module, and each binary module generated from each source module has at least one binary file corresponding to the at least one source file and a copy of the control file;

combine the binary files of each of the binary modules to generate an executable file; and

generate a COO file for the executable file based on the control files from the source modules or the binary modules by:

for each of the source modules, determining whether an identifier of the source module is present in a standard reference COO file, wherein the standard reference COO file has a list of identifiers of a plurality of modules and COO information corresponding to the plurality of modules;

when the identifier of one of the source modules is present in the standard reference COO file, retrieving the COO information corresponding to the identifier from the standard reference COO file as COO information of the one of the source modules;

when the identifier of the one of the source modules is not present in the standard reference COO file, retrieving the COO information of the one of the source modules from the corresponding control file of the one of the source modules; and

generating the COO file by combining the retrieved COO information of all of the source modules.

2. The system of claim 1 , wherein the COO of each source module comprises at least one origin and at least one license of the corresponding source module.

3. The system of claim 1 , wherein at least one of the source modules has a plurality of the source files having the same origin.

4. The system of claim 1 , wherein the executable file is a software image file or a firmware image file.

5. The system of claim 1 , wherein the computer executable code comprises:

a compiling module configured to process the plurality of source modules to generate the plurality of binary modules corresponding to the source modules;

a linker module configured to combine the binary files of each of the binary modules to generate the executable file; and

a control file processing module configured to generate the COO file for the executable file based on the control files from the source modules or the binary modules.

6. The system of claim 1 , wherein the standard reference COO file is stored in the storage.

7. The system of claim 1 , wherein the identifier of each source module is a name of the source module.

8. The system of claim 1 , wherein the at least one source file of the source modules is programmed in a customized programming language, or a set of automation scripts.

9. A method of generating a certificate of origin (COO) for a software or firmware, comprising:

processing, at an automatic COO generating application being executed at one or more processors of at least one computing device, a plurality of source modules to generate a plurality of binary modules corresponding to the source modules, wherein each source module has at least one source file and a control file comprising a COO of the source module, and each binary module generated from each source module has at least one binary file corresponding to the at least one source file and a copy of the control file;

combining, by the executed automatic COO generating application, the binary files of each of the binary modules to generate an executable file; and

generating, by the executed automatic COO generating application, a COO file for the executable file based on the control files from the source modules or the binary modules, comprising:

for each of the source modules, determining whether an identifier of the source module is present in a standard reference COO file, wherein the standard reference COO file has a list of identifiers of a plurality of modules and COO information corresponding to the plurality of modules;

when the identifier of one of the source modules is present in the standard reference COO file, retrieving the COO information corresponding to the identifier from the standard reference COO file as COO information of the one of the source modules;

when the identifier of the one of the source modules is not present in the standard reference COO file, retrieving the COO information of the one of the source modules from the corresponding control file of the one of the source modules; and

generate the COO file by combining the retrieved COO information of all of the source modules.

10. The method of claim 9 , wherein the COO of each source module comprises at least one origin and at least one license of the corresponding source module, and the executable file is a software image file or a firmware image file.

11. The method of claim 9 , wherein at least one of the source modules has a plurality of the source files having the same origin.

12. The method of claim 9 , wherein the automatic COO generating application comprises:

a compiling module configured to process the plurality of source modules to generate the plurality of binary modules corresponding to the source modules;

a linker module configured to combine the binary files of each of the binary modules to generate the executable file; and

a control file processing module configured to generate the COO file for the executable file based on the control files from the source modules or the binary modules.

13. The method of claim 9 , wherein the identifier of each source module is the name of the source module.

14. A non-transitory computer readable medium storing computer executable code, wherein the code, when executed at one or more processors of at least one computing device, is configured to:

process a plurality of source modules to generate a plurality of binary modules corresponding to the source modules, wherein each source module has at least one source file and a control file comprising a certificate of origin (COO) of the source module, and each binary module generated from each source module has at least one binary file corresponding to the at least one source file and a copy of the control file;

combine the binary files of each of the binary modules to generate an executable file; and

generate a COO file for the executable file based on the control files from the source modules or the binary modules by:

for each of the source modules, determining whether an identifier of the source module is present in a standard reference COO file, wherein the standard reference COO file has a list of identifiers of a plurality of modules and COO information corresponding to the plurality of modules;

when the identifier of one of the source modules is present in the standard reference COO file, retrieving the COO information corresponding to the identifier from the standard reference COO file as COO information of the one of the source modules;

when the identifier of the one of the source modules is not present in the standard reference COO file, retrieving the COO information of the one of the source modules from the corresponding control file of the one of the source modules; and

generate the COO file by combining the retrieved COO information of all of the source modules.

15. The non-transitory computer readable medium of claim 14 , wherein the COO of each source module comprises at least one origin and at least one license of the corresponding source module, and the executable file is a software image file or a firmware image file.

16. The non-transitory computer readable medium of claim 14 , wherein at least one of the source modules has a plurality of the source files having the same origin.

17. The non-transitory computer readable medium of claim 14 , wherein the code comprises:

a compiling module configured to process the plurality of source modules to generate the plurality of binary modules corresponding to the source modules;

a linker module configured to combine the binary files of each of the binary modules to generate the executable file; and

a control file processing module configured to generate the COO file for the executable file based on the control files from the source modules or the binary modules.

18. The non-transitory computer readable medium of claim 14 , wherein the identifier of each source module is the name of the source module.

19. The method of claim 9 , wherein the at least one source file of the source modules is programmed in a customized programming language, or a set of automation scripts.

20. The non-transitory computer readable medium of claim 14 , wherein the at least one source file of the source modules is programmed in a customized programming language, or a set of automation scripts.