Method for updating secret shared data in a wireless communication system

• US 6,243,811 B1
• Filed: 07/31/1998
• Issued: 06/05/2001
• Est. Priority Date: 07/31/1998
• Status: Expired due to Term

• Current Assignee: Alcatel-Lucent USA, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Patel, Sarvar
• Primary Examiner(s): Peeso, Thomas R.
• Application Number:
  US09/127,768
• Time in Patent Office: 1,040 Days
• Field of Search: 713/167, 713/161, 713/169, 713/171, 380/268, 380/278, 380/283
• US Class Current: 713/167
• CPC Class Codes: H04L 2209/80 Wireless
• CPC Class Codes: H04L 9/0844 with user authentication or key authentication, e.g. ElGamal, MTI, MQV-Menezes-Qu-Vanstone protocol or Diffie-Hellman protocols using implicitly-certified keys
• CPC Class Codes: H04L 9/0891 Revocation or update of secret information, e.g. encryption key update or rekeying
• CPC Class Codes: H04L 9/3271 using challenge-response
• CPC Class Codes: H04W 12/06 Authentication

Abstract

In the method for updating secret shared data (SSD) in a wireless communication system, a first party outputs a first random number as a first challenge wherein the first party is one of a network and a mobile. A second party generates a second random number in response to the first challenge. The second party is the mobile if the first party is the network, and the second party is the network if the first party is the mobile. The second party generates a first challenge response by performing a keyed cryptographic function (KCF) on the first challenge and the second random number using a secondary key, which is not the SSD and is derived from a root key. The second party then transfers the second random number, as a second challenge, and the first challenge response to the first party. The first party verifies the second party based on the first and second challenges and the first challenge response, generates a second challenge response by performing the KCF on the second challenge using the secondary key, and transfers the second challenge response to the second party. The second party verifies the first party based on the second challenge and the second challenge response. Both parties respectively establish the SSD based on the first and second challenges.

Claims

1. A method for updating secret shared data (SSD) at a first party in a wireless communication system, comprising:

(a) receiving a random number from a second party as a first challenge, said first challenge being a global challenge from said second party;

(b) generating a second random number in response to said first challenge;

(c) generating a first challenge response by performing a keyed cryptographic function (KCF) on said first challenge and said second random number using a secondary key;

(d) transferring said second random number, as a second challenge, and said first challenge response to said second party;

(e) receiving a second challenge response from said second party, said second challenge response being a result of performing said KCF on said second challenge using said secondary key;

(f) verifying said second party based on said second challenge and said second challenge response; and

(g) establishing said SSD based on said first and second challenges.

2. The method of claim 1, wherein said first party is a network and said second party is a mobile.

3. The method of claim 2, further comprising:

(h) transferring an update SSD request to said mobile; and

wherein

said step (a) receives said first challenge in response to said update SSD request.

4. The method of claim 1, wherein said step (c) generates said first challenge response by performing said KCF on said first challenge, said second challenge, and an identifier for said first party using said secondary key.

5. The method of claim 1, wherein said step (c) generates said first challenge response by performing said KCF on said first challenge, said second challenge and type data using said secondary key, said type data indicating an update SSD protocol is being performed by said first and second parties.

6. The method of claim 1, wherein said step (c) generates said first challenge response by performing said KCF on said first challenge, said second challenge, an identifier for said first party and type data using said secondary key, said type data indicating an update SSD protocol is being performed by said first and second parties.

7. The method of claim 1, wherein said first party is a mobile and said second party is a network.

8. The method of claim 7, further comprising:

(k) incrementing a count value in response to said first challenge; and

wherein

said step (c) generates said first challenge response by performing said KCF on said first challenge, said second challenge, and said count value using said secondary key;

said step (d) transfers said second challenge, said first challenge response, and said count value from said mobile to said network.

9. The method of claim 1, wherein said secondary key is derived from a root key.

10. The method of claim 1, wherein said secondary key is not a secret shared data.

11. A method for updating secret shared data (SSD) at a first party in a wireless communication system, comprising:

(a) globally outputting a random number as a first challenge to a second party;

(b) receiving a second random number, as a second challenge, and a first challenge response from said second party, said first challenge response being a result of a keyed cryptographic function (KCF) on said first challenge and said second random number using a secondary key;

(c) verifying said second party based on said first and second challenges and said first challenge response; and

(d) establishing said SSD based on said first and second challenges.

12. The method of claim 11, wherein said first party is a mobile and said second party is a network.

13. The method of claim 12, further comprising:

(e) receiving an update SSD request from said network; and

wherein

said step (a) outputs said first challenge in response to said update SSD request.

14. The method of claim 11, wherein said first party is a network and said second party is a mobile.

15. The method of claim 11, further comprising:

(e) generating a second challenge response by performing said KCF on said second challenge using said secondary key; and

(h) transferring said second challenge response to said second party.

16. The method of claim 15, wherein said step (e) generates said second challenge response by performing said KCF on said second challenge and an identifier for said first party using said secondary key.

17. The method of claim 15, wherein said step (e) generates said second challenge response by performing said KCF on said second challenge and type data using said secondary key, said type data indicating an update SSD protocol is being performed by said first and second parties.

18. The method of claim 15, wherein said step (e) generates said second challenge response by performing said KCF on said second challenge, an identifier for said first party and type data using said secondary key, said type data indicating an update SSD protocol is being performed by said first and second parties.

19. The method of claim 11, wherein

said first party is said network and said second party is a mobile.

20. The method of claim 19, wherein

said step (b) receives said second challenge, a count value and said first challenge response from said mobile, said first challenge response being a result of performing said KCF on said first challenge, said second challenge, and said count value using said secondary key;

and

said step (e) verifies said mobile based on said first challenge, said second challenge, said first challenge response, and said count;

value.

21. The method of claim 11, wherein said secondary key is derived from a root key.

22. The method of claim 11, wherein said secondary key is not a secret shared data.