System and method for constraint resolution

• US 7,779,257 B2
• Filed: 12/06/2005
• Issued: 08/17/2010
• Est. Priority Date: 12/07/2004
• Status: Expired due to Fees

• Current Assignee: Meizu Technology Company Limited
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Kudla, Caroline, Cuadrado, Javier Esplugas, Preist, Christopher William, Trastour, David
• Primary Examiner(s): Zand; Kambiz
• Assistant Examiner(s): Shaifer Harriman; Dant B
• Application Number:
  US11/294,604
• Publication Number:
  US 20060155996A1
• Time in Patent Office: 1,715 Days
• Field of Search: None
• US Class Current: 713/169
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload

Abstract

A method of determining the compatibility of respective information associated with at least two parties is described. The method comprises: a first and second party each expressing their respective information in an agreed format; processing the information according to a two-phase double-encryption process, in which the first party encrypts their information under a personalized first-phase procedure and sends the results to the second party and the second party encrypts their information under a personalized first-phase procedure and sends the results to the first party, the second party encrypting the encrypted information received from the first party under a personalized second-phase procedure to produce a double-encrypted result and the first party encrypting the encrypted information received from the second party under a personalized second-phase procedure to produce a double-encrypted result, the first- and second-phase procedures being chosen such that a given element of information will always yield the same unique double-encrypted result regardless of which party it originates from; and comparing each party'"'"'s double-encrypted information to determine the compatibility of the information of each party.

Claims

1. A method of determining a compatibility of at least a first party and a second party, each of said parties comprising at least one computer processor, the method comprising:

sending, with the first party, encrypted constraints enforced by the first party to the second party, each said constraint enforced by the first party having been separately encrypted under a first-phase procedure personalized to the first party;

sending, with the second party, encrypted constraints enforced by the second party, each said constraint enforced by the second party having been separately encrypted under a first-phase procedure personalized to the second party;

separately encrypting, with the second party, each of the encrypted constraints enforced by the first party under a second-phase procedure personalized to the second party to produce a first set of double-encrypted constraints;

separately encrypting, with the first party, each of the encrypted constraints enforced by the second party under a second-phase procedure personalized to the first party to produce a second set of double-encrypted constraints; and

determining whether said first party may establish a communication link with said second party based on a comparison of the first set of double-encrypted constraints with the second set of double-encrypted constraints.

2. A method according to claim 1, wherein the first and second parties are each allocated a key unique to that party, such that the first-phase and second-phase encryption procedures are personalised through the use by each party of the unique key.

3. A method according to claim 1, wherein each said constraint comprises a constraint title.

4. A method according to claim 3, wherein the constraint title is used to identify each double-encrypted constraint in determining the compatibility of the constraints enforced by the first and second parties.

5. A method according to claim 1, wherein under the first-phase procedure each party assigns a unique label to the constraints being encrypted.

6. A method according to claim 1, wherein determination of whether said first party may establish a communication link with said second party comprises indicating whether any conflicts exist between said constraints enforced by said first party and said constraints enforced by said second party.

7. A method according to claim 1, wherein determination of whether said first party may establish a communication link with said second party comprises indicating which constraints are compatible with each other.

8. A method according to claim 1, wherein determination of whether said first party may establish a communication link with said second party comprises identifying that all said constraints are compatible with each other.

9. A method of securely comparing constraints enforced by at least a first party and a second party, each of said parties comprising at least one computer processor, the method comprising:

sending, with the first party, encrypted constraints enforced by the first party to the second party, each said constraint enforced by the first party having been separately encrypted under a first-phase procedure personalized to the first party;

sending, with the second party, encrypted constraints enforced by the second party, each said constraint enforced by the second party having been separately encrypted under a first-phase procedure personalized to the second party;

separately encrypting, with the second party, each of the encrypted constraints enforced by the first party under a second-phase procedure personalized to the second party to produce a first set of double-encrypted constraints;

separately encrypting, with the first party, each of the encrypted constraints enforced by the second party under a second-phase procedure personalized to the first party to produce a second set of double-encrypted constraints; and

the first-phase and second-phase procedures being chosen such that a given element of information will always yield the same unique double-encrypted result regardless of which party it originates from; and

determining whether said constraints enforced by each of said first and second parties allow said first party to establish a communication link with said second party according to a degree to which said first set of double-encrypted constraints is similar to said second set of double-encrypted constraints.

10. A method according to claim 9, wherein each said constraint comprises a constraint title.

11. A method according to claim 10, wherein the constraint title is used to identify each double-encrypted constraint in determining the compatibility of the constraints enforced by the first and second parties.

12. A method according to claim 9, wherein determination of the compatibility of information comprises indicating whether any conflicts exist between said constraints enforced by said first party and said constraints enforced by said second party.

13. A method according to claim 9, wherein determination of the compatibility of the constraints enforced by said first and second parties comprises indicating which constraints are compatible with each other.

14. A method according to claim 9, wherein determination of the compatibility of the constraints enforced by said first and second parties comprises identifying that all said constraints are compatible with each other.

15. A method according to claim 9, wherein the results of the determination of the compatibility of the constraints enforced by said first and second parties are used to determine if a link may be formed between the first and second parties.

16. A method according to claim 9, wherein under the first-phase procedure the first party assigns a unique label to its encrypted information.

17. A method according to claim 9, wherein the first party is allocated a key unique to the first party, such that the first-phase and second-phase encryption procedures are personalised through the use by the first party of the unique key.

18. A method of establishing communication between a first computing device and a second computing device in accordance with first and second sets of constraints enforced by said first and second computing devices, respectively, said method comprising:

said first computing device providing an encrypted version of said first set of constraints to said second computing device together with an unencrypted set of constraint titles associated with said first set of constraints;

said second computing device providing an encrypted version of said second set of constraints to said first computing device together with an unencrypted set of constraint titles associated with said second set of constraints;

said first computing device encrypting said encrypted version of said second set of constraints to produce a double-encrypted version of said second set of constraints;

said second computing device encrypting said encrypted version of said first set of constraints to produce a double-encrypted version of said first set of constraints; and

generating in each of said first and second computing devices a governing set of constraints for a link between said first and second computing devices based on identified matches between said double-encrypted versions of said first and second sets of constraints and said unencrypted sets of titles associated with said first and second sets of constraints.

21. The method of claim 18, in which an encryption process used by said first computing device to encrypt said constraints is functionally different than an encryption process used by said second computing device.

22. The method of claim 18, in which an encryption process performed by said first computing device is functionally equivalent to an encryption process performed by said second computing device.

23. The method of claim 18, in which said encryption process performed by said first computing device uses a key separate from a key used by said encryption process performed by said second computing device.

24. The method of claim 18, further comprising:

determining that none of said double-encrypted constraints enforced by said first computing device is equal to any of said double-encrypted constraints enforced by said second computing device; and

changing one or more of said constraints;

updating said double-encrypted versions of said first and second sets of constraints; and

reattempting to generate said set of governing constraints.

25. The method of claim 18, further comprising:

determining that none of said double-encrypted constraints enforced by said first computing device is equal to any of said double-encrypted constraints enforced by said second computing device; and

said first computing device negotiating directly with said second computing devices to at least partially generate said set of governing constraints.

26. The method of claim 18, further comprising:

determining that none of said double-encrypted constraints enforced by said first computing device is equal to any of said double-encrypted constraints enforced by said second computing device; and

preventing said first computing device from establishing a link with said second computing device.

27. The method of claim 18, in which each said constraint comprises a constraint title defined by an ontology agreed upon between said first and second computing devices.

19. The method of 18, in which said first computing device uses an encryption key separate from said encryption key used by said second computing device.

20. The method of claim 19, in which said keys are randomly generated.