US 11,943,369 B2
Technology validation and ownership
Mikko Einari Varpiola, Los Gatos, CA (US); and Craig E. Shinners, San Jose, CA (US)
Assigned to Synopsys, Inc., Sunnyvale, CA (US)
Appl. No. 16/324,422
Filed by Synopsys, Inc., Mountain View, CA (US)
PCT Filed Aug. 9, 2017, PCT No. PCT/US2017/046176
§ 371(c)(1), (2) Date Feb. 8, 2019,
PCT Pub. No. WO2018/031703, PCT Pub. Date Feb. 15, 2018.
Claims priority of provisional application 62/372,723, filed on Aug. 9, 2016.
Prior Publication US 2019/0182053 A1, Jun. 13, 2019
Int. Cl. G06F 21/16 (2013.01); G06Q 50/18 (2012.01); H04L 9/08 (2006.01); H04L 9/32 (2006.01); H04L 9/00 (2022.01)
CPC H04L 9/3247 (2013.01) [G06F 21/16 (2013.01); G06Q 50/184 (2013.01); H04L 9/0861 (2013.01); H04L 9/3236 (2013.01); H04L 9/3239 (2013.01); G06Q 2220/00 (2013.01); H04L 9/50 (2022.05)] 20 Claims
OG exemplary drawing
 
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.