System and method for managing digital interactions

• US 8,170,957 B2
• Filed: 08/08/2008
• Issued: 05/01/2012
• Est. Priority Date: 08/08/2007
• Status: Active Grant

• Current Assignee: Smartpoints Technology Incorporated
• Original Assignee: Sinart Points Technology Incorporated
• Inventors: Richard, Philippe
• Primary Examiner(s): Hewitt, II, Calvin L
• Assistant Examiner(s): Huang, Tsan-Yu J
• Application Number:
  US12/189,135
• Publication Number:
  US 20090150297A1
• Time in Patent Office: 1,362 Days
• Field of Search: 713/185, 713/200, 705/51
• US Class Current: 705/76
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 50/188 Electronic negotiation

Abstract

A system for managing digital interactions comprising an identity module for creating an identity, wherein the identity includes a unique identifier associated with a first party and a plurality of proposed terms for a relationship with a second party; and a relationship module, in communication with the identity module, for receiving and evaluating the plurality of proposed terms, including accepting or rejecting the plurality of proposed terms and, if accepted, for allowing the first party to communicate with the second party in accordance with the plurality of proposed terms.

Claims

1. A method for managing digital interactions comprising:

receiving a digital vector at a receiving Relationship Nexus Agent, resident on a machine, via a negotiated traversal path formed through a network of other Relationship Nexus Agents, the received digital vector being associated with a plurality of terms for a relationship between a requester endpoint and a recipient endpoint and having the property of being authenticated using secure digital keys that are usable only by the requester and the recipient under agreed terms;

authenticating the received digital vector via the receiving Relationship Nexus Agent using the secure digital keys; and

relaying the digital vector from the receiving Relationship Nexus Agent to a role associated with the recipient;

wherein the secure digital keys are exchanged and the agreed terms are determined via a process comprising;

establishing an ephemeral secure channel between the requester and the recipient via a process comprising;

preparing a channel request package, wherein the requester selects requester credentials to disclose, selects recipient credentials to require of the recipient, and selects proposed attributes of a channel between the requester and the recipient, and wherein the requester credentials selected, the recipient credentials selected, and the proposed attributes selected are included by a requesting Relationship Nexus Agent, resident on a machine, in the channel request package;

creating a first requester created random key pair by the requesting Relationship Nexus Agent;

sending the channel request package from the requester by the requesting Relationship Nexus Agent;

receiving the channel request package at the recipient by the receiving Relationship Nexus Agent;

creating a first recipient created random key pair; and

establishing a secure communication channel via an ephemeral key exchange using the first requester created random key pair and the first recipient created random key pair; and

establishing the agreed terms and the secure digital keys by the requesting and receiving Relationship Nexus Agents, the establishing comprising;

reviewing, at the recipient, terms proposed by the requester;

sending a response to the requester through the ephemeral secure channel by the receiving Relationship Nexus Agent, the response comprising one of an acceptance of the proposed terms and counter-proposed terms for the relationship;

receiving, at the requester, the response from the recipient;

sending from the requester, through the ephemeral secure channel, one of an acceptance of the counter-proposed terms and a revised proposed terms for the relationship;

creating a second requester created random key pair;

transmitting to the recipient, through the ephemeral secure channel one key of the second requester created random key pair;

creating a second recipient created random key pair; and

transmitting to the requester, through the ephemeral secure channel one key of the second recipient created random key pair.

2. The method for managing digital interactions of claim 1, wherein none of the secure digital keys are contained within the digital vector.

3. The method for managing digital interactions of claim 1, wherein the relationship between the requester endpoint and the recipient endpoint provides relationship based encryption.

4. The method for managing digital interactions of claim 1, wherein the relationship between the requester endpoint and the recipient party endpoint provides embedded usage control.

5. The method for managing digital interactions of claim 1, wherein the relationship between the requester endpoint and the recipient party endpoint provides rights management.

6. The method for managing digital interactions of claim 1, wherein the relationship between the requester endpoint and the recipient party endpoint provides access location control.

9. The method for managing digital interactions of claim 1, wherein the recipient verifies the channel request package using an electronic signature of the requester'"'"'s domain.

10. The method for managing digital interactions of claim 1, wherein the requester and recipient exchange keys using the Diffie-Hellman protocol.

11. The method for managing digital interactions of claim 1, wherein the agreed terms restrict information access permission based upon a context under which access is sought.

12. The method for managing digital interactions of claim 1, wherein the context comprises physical location.

13. The method for managing digital interactions of claim 1, wherein the context comprises a secure token.

14. The method for managing digital interactions of claim 11, wherein the context comprises the sending party'"'"'s domain.

15. The method for managing digital interactions of claim 11, wherein the context comprises a role.

7. A method for managing digital interactions comprising:

receiving a message at a receiving Relationship Nexus Agent, resident on a machine, via a negotiated traversal path formed through a network of other Relationship Nexus Agents, wherein the message is associated with a plurality of terms for a relationship between a requester endpoint and a recipient endpoint and having the property of being authenticated using secure digital keys that are usable only by the requester and the recipient under agreed terms;

authenticating the received message via the receiving Relationship Nexus Agent using the secure digital keys; and

relaying the message from the receiving Relationship Nexus Agent to a role associated with the recipient;

wherein the secure digital keys are exchanged and the agreed terms are determined via a process comprising;

establishing an ephemeral secure channel between the requester and the recipient via a process comprising;

preparing a channel request package, wherein the requester selects requester credentials to disclose, selects recipient credentials to require of the recipient, and selects proposed attributes of a channel between the requester and the recipient, and wherein the requester credentials selected, the recipient credentials selected, and the proposed attributes selected are included by a requesting Relationship Nexus Agent, resident on a machine, in the channel request package;

creating a first requester created random key pair by the requesting Relationship Nexus Agent;

sending the channel request package from the requester by the requesting Relationship Nexus Agent;

receiving the channel request package at the recipient by the receiving Relationship Nexus Agent;

verifying, at the recipient by the receiving Relationship Nexus Agent, the channel request package using an electronic signature of the requester'"'"'s domain;

creating a first recipient created random key pair; and

establishing a secure communication channel according to the Diffie-Hellman protocol using the first requester created random key pair and the first recipient created random key pair and

establishing the agreed terms and exchanging keys by the requesting and receiving Relationship Nexus Agents, the establishing comprising;

reviewing, at the recipient, terms proposed by the requester;

sending a response to the requester through the ephemeral secure channel by the receiving Relationship Nexus Agent, the response comprising one of an acceptance of the proposed terms and counter-proposed terms for the relationship;

receiving, at the requester, the response from the recipient;

sending from the requester, through the ephemeral secure channel, one of an acceptance of the counter-proposed terms and a revised proposed terms for the relationship;

creating a second requester created random key pair;

transmitting to the recipient, through the ephemeral secure channel one key of the second requester created random key pair;

creating a second recipient created random key pair; and

transmitting to the requester, through the ephemeral secure channel one key of the second recipient created random key pair;

wherein the secure digital keys utilize an asymmetric cryptographic algorithm, and wherein the relationship between the requester endpoint and recipient endpoint provides rights management and embedded usage control.

8. The method for managing digital interactions of claim 7, wherein none of the secure digital keys are contained within the digital vector.

16. The method for managing digital interactions of claim 7, wherein identities of the requester and recipient are made part of the relationship between the requester endpoint and the recipient endpoint.

17. The method for managing digital interactions of claim 7, wherein the relationship between the requester endpoint and recipient endpoint establishes security of communication between the endpoints.

18. The method for managing digital interactions of claim 7, wherein each of the endpoints manages its own keys.