WO 2018/031703
`
`PCT/US2017/046176
`
`CLAIMS
`
`We claim:
`
`1.
`
`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 the proprietary file;
`
`validating each of the plurality of signatures, to ensure that the signatures are the
`
`proprietary files of the vendor; and
`
`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.
`
`2.
`
`The method of claim 1, wherein the proprietary file comprises one of
`
`software source code, Hardware Design Language (HDL), hardware description, and
`
`scripting language.
`
`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:
`
`utilizing the global database to identify free and open source software (FOSS)
`
`incorporated into the proprietary files of the vendor.
`
`34
`
`
`
`PCT/US2017/046176
`
`CLAIMS
`
`We claim:
`
`1.
`
`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 the proprietary file;
`
`validating each of the plurality of signatures, to ensure that the signatures are the
`
`proprietary files of the vendor; and
`
`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.
`
`2.
`
`The method of claim 1, wherein the proprietary file comprises one of
`
`software source code, Hardware Design Language (HDL), hardware description, and
`
`scripting language.
`
`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:
`
`utilizing the global database to identify free and open source software (FOSS)
`
`incorporated into the proprietary files of the vendor.
`
`34
`
`
`
`WO 2018/031703
`
`PCT/US2017/046176
`
`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.
`
`35
`
`
`
`WO 2018/031703
`
`PCT/US2017/046176
`
`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 validator comprising:
`
`a communication system to receive 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;
`
`a signature validator to validate each of the plurality of signatures, to
`
`ensure that each of the signatures are the proprietary files of the
`
`vendor; and
`
`a memory including a global database to store the plurality of the signatures, the
`
`global database used to compare the proprietary files of the vendor to other technology
`
`data.
`
`12.
`
`The system of claim 11, wherein the proprietary file comprises at least one
`
`of software source code, software object code, Hardware Design Language (HDL), a
`
`hardware description language, and scripting language.
`
`13.
`
`The system of claim 11, further comprising:
`
`36
`
`
`
`WO 2018/031703
`
`PCT/US2017/046176
`
`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, further comprising:
`
`the signature validator 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.
`
`37
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
