| Predicate |
Object |
| assignee |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_487e7b1c2ce1d091482c5372f9d5149b |
| classificationCPCInventive |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F21-629
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/G06F21-105
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-4433
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-64715
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-4353
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04L63-126
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-4431
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/H04N21-2351
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F21-121 |
| 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_e8a69c7f42f7ab4b9794450909490678
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_d07e05e9c4df1033bf55152da6c2f2a0
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_b8cbea4db9845f325608f6de5c750bf3
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_c2c758309cfb382e9f5ac7cae3f733f3
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_b0e5aac90c838cf92ee56fc4cd94ef7c |
| publicationDate |
2015-06-18-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| publicationNumber |
AU-2013338059-A1 |
| titleOfInvention |
METHOD INCLUDING CHALLENGE-RESPONSE SYSTEM TO SECURELY AUTHENTICATE SOFTWARE APPLICATION PROGRAM INTERFACES (APLs) |
| 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 |