| Predicate |
Object |
| assignee |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_bfa3571ebbdfb47cadbd2b9092758bf8 |
| classificationCPCInventive |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F21-105
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-4433
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F21-57
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F21-10
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-2351
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F21-629
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-4431
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-64715
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F21-121
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04L63-126
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-4353 |
| classificationIPCInventive |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G06F21-12 |
| filingDate |
2013-10-29-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| inventor |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_69b257993d6ede9003304168bf53ef89
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_efc96e68e98c9196fc499531d48ccb63
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_3dfcdc2f5ce629c8bf93bf632ecf1eb1
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_a80bf797993e90892ed1504a3ab1e9d2
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_faa474b1bb6e341135eb66d0082b8ec5 |
| publicationDate |
2014-05-08-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| publicationNumber |
CA-2899385-A1 |
| titleOfInvention |
Handshaking protocol for secure transfer of data |
| abstract |
A system for securely authenticating software Application Program Interfaces (APIs) includes a handshake protocol that is provided to validate whether the parties involved are licensed to use the system which includes rights to Intellectual Property (IP) and corresponding obligations. The handshake is a Challenge-Response protocol that includes several steps. First, a Claimant sends a request to a Verifier requesting access to a function through an API. The Verifier reacts to the request by outputting a Challenge that is sent to the Claimant. The Challenge is also retained by the Verifier for use in its internal calculation to verify the Claimant's response. The Claimant next processes the Challenge using components under the license, known as Hook IP, and issues a Response to the Verifier. The Verifier compares the possibly-correct Candidate Response from the Claimant to the known-correct Target Response and if a match occurs the Verifier allows the Claimant access to the API. |
| priorityDate |
2012-10-29-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| type |
http://data.epo.org/linked-data/def/patent/Publication |