Reliance server for electronic transaction system

• US 8,032,743 B2
• Filed: 08/31/2001
• Issued: 10/04/2011
• Est. Priority Date: 12/13/1996
• Status: Expired due to Fees

• Current Assignee: Certco
• Original Assignee: Certco
• Inventors: Asay, Alan, Turner, Paul A., Sudia, Frank W., Ankney, Richard
• Primary Examiner(s): Pyzocha, Michael
• Assistant Examiner(s): CALLAHAN, PAUL E
• Application Number:
  US09/943,086
• Publication Number:
  US 20020062438A1
• Time in Patent Office: 3,686 Days
• Field of Search: 380/282, 380/30, 380/277, 705/67, 705/71, 705/76, 705/70, 705/142, 713/156, 713/169, 713/175, 713/176, 713/180
• US Class Current: 713/156
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G07F 7/08 by coded identity card or credit card or other personal identification means without personal verification means G07F7/02
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 9/3268 using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

A method of managing reliance in an electronic transaction system includes a certification authority issuing a primary certificate to a subscriber and forwarding to a reliance server, information about the issued primary certificate. The reliance server maintains the forwarded information about issued primary certificate. The subscriber forms a transaction and then provides the transaction to a relying party. The transaction includes the primary certificate or a reference thereto. The relying party sends to the reliance server a request for assurance based on the transaction received from the subscriber. The reliance server determines whether to provide the requested assurance based on the information about the issued primary certificate and on the requested assurance. Based on the determining, the reliance server issues to the relying party a secondary certificate providing the assurance to the relying party.

Claims

1. A method of managing reliance in an electronic transaction system, the method comprising:

obtaining electronic signals representing subscriber assurance of an attribute of a subscriber to the system, the subscriber assurance issued by a certification authority hardware mechanism;

obtaining electronic signals representing a request for transactional financial assurance and recourse, the transaction financial assurance and recourse being with respect to electronic infrastructure used in or with a transaction involving the subscriber, and the transactional financial assurance being other than a digital signature of the electronic infrastructure or the electronic signals representing subscriber assurance, the request including a value of the transaction financial assurance and recourse requested;

determining whether to provide the requested transactional financial assurance and recourse based on at least the subscriber assurance and whether the requested transaction financial assurance value exceeds or is below a reliance limit associated with the electronic signals representing subscriber assurance; and

, depending on the determining,

issuing electronic signals representing the requested transactional financial assurance and recourse to a relying party hardware mechanism; and

tracking cumulative liability associated with the electronic signals representing subscriber assurance, wherein determining whether the requested transaction financial assurance value exceeds or is below the reliance limit includes determining whether the requested transaction financial assurance value causes the cumulative liability to exceed or be below an acceptable reliance limit in excess of the reliance limit.

2. The method of claim 1, wherein the subscriber assurance comprises (a) an identification assurance of the identity of the subscriber, or (b) an authorization assurance of authorization of the subscriber, or (c) both (a) and (b).

3. The method of claim 1, wherein the subscriber assurance comprises electronic signals representing a certificate.

4. The method of claim 1, wherein the determining is based also on information provided by the relying party.

5. The method of claim 1, wherein the request for transactional financial assurance and recourse comes from the relying party.

6. The method of claim 1, wherein the request for transactional financial assurance and recourse includes a request for a guarantee of an aspect of the transaction and comprising:

validating information in the request for transactional financial assurance and recourse to determine whether to provide the guarantee for the aspect of the transaction; and

sending electronic signals representing an indication of whether the aspect of the transaction will be guaranteed.

7. The method of claim 1, wherein the electronic signals representing the subscriber assurance comprise electronic signals representing a time-based certificate specifying a stated reliance limit and the method comprises obtaining electronic signals representing an actual reliance limit for the certificate, the actual reliance limit being different from the stated reliance limit.

8. The method of claim 1, wherein the electronic infrastructure Comprises electronic signals representing a certificate and the transactional financial assurance and recourse with respect to electronic infrastructure comprises an assurance selected from the following:

assurance regarding the authenticity of the certificate, assurance regarding the accuracy of the certificate, or assurance regarding the validity of the certificate.

9. A computer program product, embodied in a non-transitory computer-readable storage media, comprising instructions for causing a computer to effect a method of managing reliance in an electronic transaction system, the method comprising:

receiving electronic signals representing a transaction associated with a subscriber, the transaction including information regarding at least one attribute of that subscriber;

creating a reliance request message specifying at least one aspect of the transaction upon which a relying party intends to rely; and

causing electronic signals representing the reliance request message to be sent to a reliance server requesting a transactional financial assurance and recourse for the aspect of the transaction upon which the relying party intends to rely, the transactional financial assurance and recourse including transactional financial assurance and recourse with respect to electronic infrastructure used in or with the transaction and the transactional financial assurance and recourse being other than a digital signature of the electronic infrastructure, the request including a value of the requested transaction financial assurance and recourse for comparison with a reliance limit associated with the aspect of the transaction.

10. The computer program product of claim 9, wherein the method further comprises:

receiving electronic signals representing a transactional financial assurance and recourse from the reliance server; and

continuing the transaction with the subscriber based on information in the transactional financial assurance and recourse.

11. The computer program product of claim 9, wherein the electronic signals representing the transactional financial assurance and recourse are received in response to the sending of the reliance request message.

12. The computer program product of claim 9, wherein the information regarding at least one attribute of the subscriber comprises (a) an identification assurance of the identity of the subscriber, or (b) an authorization assurance of authorization of the subscriber, or (c) both (a) and (b).

13. The computer program product of claim 9, wherein the reliance request message comes from the relying party.

14. The computer program product of claim 9, wherein the electronic infrastructure comprises electronic signals representing a certificate and the transactional financial assurance and recourse with respect to electronic infrastructure comprises an assurance selected from the following:

assurance regarding the authenticity of the certificate, assurance regarding the accuracy of the certificate, or assurance regarding the validity of the certificate.

15. A computer program product, embodied in a non-transitory computer-readable storage media, comprising instructions for causing a computer to effect a method of managing reliance in an electronic transaction system, the method comprising:

receiving electronic signals representing a reliance request message, the message specifying an aspect of a transaction upon which a relying party intends to rely, requesting assurance for the aspect of the transaction, and including a value of the assurance requested;

determining whether to provide transactional financial assurance and recourse with respect to electronic infrastructure used in or with the transaction based on the reliance request message and whether the value of the assurance exceeds or is below a reliance limit associated with the aspect of the transaction, the transactional financial assurance and recourse being other than a digital signature of the electronic infrastructure; and

generating electronic signals representing an indication of whether transactional financial assurance and recourse is available.

16. The computer program product of claim 15, wherein the method further comprises:

receiving electronic signals representing the transactional financial assurance and recourse; and

continuing the transaction based on information in the transactional financial assurance and recourse.

17. The computer program product of claim 15, wherein the reliance request message comes from the relying party.

18. The computer program product of claim 15, wherein the reliance request message includes certificate information derived from the transaction.

19. The computer program product of claim 15, wherein the determining whether to provide the transactional financial assurance and recourse further comprises determining the status of a certificate associated with the transaction.

20. The computer program product of claim 15, wherein the reliance request message includes a request for a guarantee of an aspect of the transaction and the method comprises:

validating information in the reliance request message to determine whether to provide the guarantee for the aspect of the transaction; and

sending electronic signals representing an indication of whether the aspect of the transaction will be guaranteed.

21. The computer program product of claim 15, wherein the determining involves using electronic signals representing a time-based certificate specifying a stated reliance limit and the method comprises obtaining electronic signals representing an actual reliance limit for the certificate, the actual reliance limit being different from the stated reliance limit.

22. The computer program product of claim 15, wherein the electronic infrastructure comprises electronic signals representing a certificate and the transactional financial assurance and recourse with respect to electronic infrastructure comprises an assurance selected from the following:

assurance regarding the authenticity of the certificate, assurance regarding the accuracy of the certificate, or assurance regarding the validity of the certificate.

23. The computer program product of claim 15, wherein the method further comprises tracking cumulative liability associated with the aspect of the transaction, wherein determining whether the assurance value exceeds or is below the reliance limit includes determining whether the assurance value causes a cumulative liability to exceed an acceptable reliance limit in excess of the reliance limit.