Technology validation and ownership

• US 11,943,369 B2
• Filed: 08/09/2017
• Issued: 03/26/2024
• Est. Priority Date: 08/09/2016
• Status: Active Grant

• Current Assignee: Software Integrity Group Incorporated
• Original Assignee: Synopsys Incorporated
• Inventors: Varpiola, Mikko Einari, Shinners, Craig E.
• Primary Examiner(s): Pearson, David J
• Application Number:
  US16/324,422
• Publication Number:
  US 20190182053A1
• Time in Patent Office: 2,421 Days
• CPC Class Codes: G06F 21/16 Program or content traceability, e.g. by watermarking
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: G06Q 50/184 Intellectual property management
• CPC Class Codes: H04L 9/0861 Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/3236 using cryptographic hash functions
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

A method comprising receiving a plurality of signatures representing one or more proprietary files from a vendor generated without disclosure of the proprietary files, each signature corresponding to a segment of a proprietary file. The method further comprising and validating each of the plurality of the signatures, to ensure that the signatures are the proprietary code of the vendor. The method further comprises adding the plurality of the signatures to a global database, the global database used to compare the proprietary data of the vendor to other technology data and taking various action based on the results of the comparison.

Claims

1. A method comprising:

receiving one or more proprietary files from a vendor;

generating, by a signature generator embedded in one or more electronic design automation (EDA) tools, one or more signatures, wherein a signature corresponds to a segment of a proprietary file of the one or more proprietary files, wherein the proprietary file of the one or more proprietary files comprises hardware description language code;

validating each of the signatures to ensure that the signatures are owned by the vendor;

comparing a signature of the one or more signatures with existing signatures;

in response to determining that the signature is not unique and a conflict exists within the vendor based on the comparison, storing a relation between the signature and an existing signature, wherein the relation reflects an ownership relationship between the proprietary file and the vendor;

identifying, in response to determining that the signature is not unique, at least one of leakage, misappropriation, appropriation, or contamination of the one or more proprietary files with one or more of proprietary files from another vendor, and open source files.

2. The method of claim 1, wherein the proprietary file further comprises a netlist file.

3. The method of claim 1, further comprising:

utilizing a blockchain code to create a public ledger in a distributed database, to record the signatures.

4. The method of claim 1, further comprising:

adding the signature to a global database, wherein the global database is used to compare the proprietary data of the vendor to other technology data;

processing and generating open source content of a repository of HDL; and

utilizing the global database to identify free and open source software (FOSS) incorporated into the proprietary files of the vendor.

5. The method of claim 1, further comprising:

utilizing the global database to identify a leakage of the proprietary file or a portion of the proprietary file, the leakage indicating a presence of the proprietary file or the portion of the proprietary file in one of;

public domain data, free and open source (FOSS) data, and other vendors'"'"' proprietary data.

6. The method of claim 1, further comprising:

notifying a particular vendor when the signature indicates that one or more submitted proprietary files of the particular vendor are registered to another entity.

7. The method of claim 6, further comprising:

resolving conflict between one or more signatures and other data in the global database.

8. The method of claim 7, wherein resolving conflict comprises one or more of:

identifying co-ownership, identifying licensing, acquisition, and priority.

9. The method of claim 1, further comprising:

enabling tracking of where the proprietary code is used, based on the signatures; and

to alert the vendor when a policy violation is detected.

10. The method of claim 1, further comprising:

tracking and providing a proof of authorship, and chain of ownership, based on the signatures that are resistant to code modifications and alterations.

11. A technology and ownership validation system comprising:

a signature generator embedded in one or more electronic design automation (EDA) tools, the signature generator configured to generate one or more signatures corresponding to one or more proprietary files received from a vendor;

a signature validator configured to receive the one or more signatures, wherein each signature corresponds to a segment of a proprietary file of the one or more proprietary files, wherein the proprietary file of one or more proprietary files comprises hardware description language code, wherein the signature validator is further configured to compare a signature of the one or more signatures with existing signatures and validate each of the signatures to ensure that the signatures are owned by the vendor;

in response to determining that the signature is not unique and a conflict exists within the vendor based on the comparison, storing a relation between the signature and an existing signature, wherein the relation reflects an ownership relationship between the proprietary file and the vendor; and

a memory including a global database to store the signatures, the global database used to compare the proprietary files of the vendor to other technology data and identify, in response to determining that the signature is not unique, at least one of leakage, misappropriation, appropriation, or contamination of the one or more proprietary files with one or more of proprietary files from another vendor, and open source files.

12. The system of claim 11, wherein the proprietary file further comprises a netlist file.

13. The system of claim 11, further comprising:

a blockchain generator to create a blockchain transaction for each of the signatures, the blockchain serving as a public ledger of the signatures in a distributed database.

14. The system of claim 11, further comprising:

a signature matcher to identify free and open source software (FOSS) incorporated into the proprietary files of the vendor using the signatures in the global database.

15. The system of claim 11, further comprising:

a signature matcher to identify leakage of the proprietary file, indicating presence of the proprietary files in one of;

public domain data, free and open source (FOSS) data, and other vendors'"'"' proprietary data.

16. The system of claim 15, further comprising:

an alert system to notify a particular vendor when the signature indicates that one or more submitted proprietary files of the particular vendor are registered to another entity.

17. The system of claim 16:

wherein the signature validator is further configured to resolve conflict between one or more signatures and other data in the global database, by one of;

identifying co-ownership, identifying licensing, acquisition, and priority.

18. The system of claim 11, wherein

the global database is used to enable tracking of where the proprietary code is used, based on the signatures;

and wherein the system is further comprising an alert system to alert the vendor when a policy violation is detected.

19. A system to provide technology and ownership validation of files, the system comprising:

a processing device configured to execute;

one or more electronic design automation (EDA) tools available to a vendor as a vendor system configured to enable a vendor to generate unique signatures locally for proprietary files, without disclosing the proprietary files to another, wherein a proprietary file of the one or more proprietary files comprises hardware description language code; and

a signature validator configured to receive the unique signatures from the tool, compare a signature of the plurality of signatures with existing signatures and validate each of the plurality of signatures to ensure that the signatures are owned by the vendor, in response to determining that the signature is not unique and a conflict exists within the vendor based on the comparison, storing a relation between the signature and an existing signature, wherein the relation reflects an ownership relationship between the proprietary file and the vendor; and

a memory coupled to the processing device, the memory comprising a global database to store the unique signatures and metadata, the global database used to identify, in response to determining that the signature is not unique, at least one of leakage, misappropriation, appropriation, or contamination of the proprietary files with one or more of proprietary files from another vendor, and open source files.

20. The system of claim 19, wherein the proprietary file further comprises a netlist file.