Method and apparatus for binding subscriber authentication and device authentication in communication systems

• US 9,385,862 B2
• Filed: 06/15/2011
• Issued: 07/05/2016
• Est. Priority Date: 06/16/2010
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Escott, Adrian Edward, Palanigounder, Anand
• Primary Examiner(s): Kim, Jung
• Assistant Examiner(s): NGUYEN, NGOC THACH D
• Application Number:
  US13/161,336
• Publication Number:
  US 20110314287A1
• Time in Patent Office: 1,847 Days
• Field of Search: 713/171
• US Class Current: 1/1
• CPC Class Codes: H04L 2463/061 applying further key derivation, e.g. deriving traffic keys from a pair-wise master key cryptographic mechanisms or cryptographic arrangements for generation of secret information including derivation or calculation of cryptographic keys or passwords H04L9/0861
• CPC Class Codes: H04L 2463/082 applying multi-factor authentication cryptographic mechanisms or cryptographic arrangements including means for verifying the identity or authority of a user of the system or for message authentication H04L9/32
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 9/0816 Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
• CPC Class Codes: H04L 9/0838 Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these network architectures or network communication protocols for key exchange in a packet data network H04L63/061
• 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/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04L 9/3271 using challenge-response
• CPC Class Codes: H04L 9/3273 for mutual authentication network architectures or network communication protocols for achieving mutual authentication in a packet data network H04L63/0869
• CPC Class Codes: H04W 12/041 Key generation or derivation
• CPC Class Codes: H04W 12/0433 Key management protocols
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

An authentication method is provided between a device (e.g., a client device or access terminal) and a network entity. A removable storage device may be coupled to the device and stores a subscriber-specific key that may be used for subscriber authentication. A secure storage device may be coupled to the device and stores a device-specific key used for device authentication. Subscriber authentication may be performed between the device and a network entity. Device authentication may also be performed of the device with the network entity. A security key may then be generated that binds the subscriber authentication and the device authentication. The security key may be used to secure communications between the device and a serving network.

Claims

1. A method operational in a device, comprising:

performing subscriber authentication with a network entity based on a subscriber authentication key;

performing device authentication of the device with the network entity to obtain device authentication data, wherein the device authentication data is obtained based on a challenge received by the device and on a device identity or credential, the device authentication data incorporating at least a portion of the challenge and wherein the device authentication data includes an encrypted parameter derived from a device temporary key, a network nonce and a device nonce;

generating a security key based on the subscriber authentication key and at least a portion of the device authentication data to bind the subscriber authentication and the device authentication; and

using the security key to secure communications between the device and a serving network.

2. The method of claim 1, wherein subscriber authentication is performed by a first authentication server that is part of the network entity, and device authentication is performed by a second authentication server that is part of the network entity.

3. The method of claim 1, wherein device authentication is performed by:

receiving data from the network entity that is encrypted with a public key of the device;

using a corresponding private key to decrypt the encrypted data; and

subsequently proving to the network entity that the device has knowledge of the data.

4. The method of claim 1, further comprising:

sending an attach request from the device to the network entity, the attach request including an indication that the device is capable of device authentication.

5. The method of claim 1, wherein device authentication is secured by at least one key generated during the subscriber authentication.

6. The method of claim 1, wherein subscriber authentication and device authentication are concurrently performed in message exchanges in which subscriber authentication and device authentication are combined.

7. The method of claim 1, wherein subscriber authentication is performed in an earlier and separate security exchange from the device authentication.

8. The method of claim 1, wherein the security key is generated as a function of at least a first key obtained from subscriber authentication and a second key obtained from device authentication.

9. The method of claim 1, wherein the device is a relay node that appears as an access terminal to the network entity and appears as a network device to one or more access terminals.

10. The method of claim 1, wherein the security key is separately generated by the device and the network entity.

11. The method of claim 1, further comprising:

provisioning a subscriber-specific key as part of a service agreement, where the subscriber-specific key is used for the subscriber authentication; and

provisioning a device-specific key in the device during manufacturing, where the device-specific key is used for the device authentication.

12. The method of claim 1, wherein the device authentication is performed subsequent to, or concurrently with, the subscriber authentication.

13. The method of claim 1, wherein the challenge includes an identifier and the method further includes:

receiving a command from the network entity that includes the identifier; and

generating additional security keys based on the security key and the identifier.

14. The method of claim 1, wherein the device authentication is performed subsequent to the subscriber authentication.

15. The method of claim 1, wherein the subscriber authentication is performed based on a subscriber authentication key obtained using a subscriber identity or key stored with the device.

16. A device, comprising:

a communication interface; and

a processing circuit coupled to the communication interface, the processing circuit adapted to;

perform subscriber authentication with a network entity based on a subscriber authentication key;

perform device authentication of the device with the network entity to obtain device authentication data, wherein the device authentication data is obtained based on a challenge received by the device and on a device identity or credential, the device authentication data incorporating at least a portion of the challenge and wherein the device authentication data includes an encrypted parameter derived from a device temporary key, a network nonce and a device nonce;

generate a security key based on the subscriber authentication key and at least a portion of the device authentication data to bind the subscriber authentication and the device authentication; and

use the security key to secure communications between the device and a serving network.

17. The device of claim 16, wherein device authentication is based on a challenge-response exchange between the device and the network entity.

18. The device of claim 16, wherein device authentication is performed by:

receiving data from the network entity that is encrypted with a public key of the device;

using a corresponding private key to decrypt the encrypted data; and

subsequently proving to the network entity that the device has knowledge of the data.

19. The device of claim 16, further comprising:

sending an attach request from the device to the network entity, the attach request including an indication that the device is capable of device authentication.

20. The device of claim 16, wherein device authentication is secured by at least one key generated during the subscriber authentication.

21. The device of claim 16, wherein subscriber authentication and device authentication are concurrently performed in combined message exchanges in which subscriber authentication and device authentication are combined.

22. The device of claim 16, wherein subscriber authentication is performed in an earlier and separate security exchange from the device authentication.

23. The device of claim 16, wherein the security key is generated as a function of at least a first key obtained from subscriber authentication and a second key obtained from device authentication.

24. The device of claim 16, wherein the device is a relay node that appears as an access terminal to the network entity and appears as a network device to one or more access terminals.

25. The device of claim 16, further comprising:

a removable storage device coupled to the processing circuit and storing a subscriber-specific key used for the subscriber authentication; and

a secure storage device coupled to the processing circuit and storing a device-specific key used for the device authentication.

26. A device, comprising:

means for performing subscriber authentication with a network entity based on a subscriber authentication key;

means for performing device authentication of the device with the network entity to obtain device authentication data, wherein the device authentication data is obtained based on a challenge received by the device and on a device identity or credential, the device authentication data incorporating at least a portion of the challenge and wherein the device authentication data includes an encrypted parameter derived from a device temporary key, a network nonce and a device nonce;

means for generating a security key based on the subscriber authentication key and at least a portion of the device authentication data to bind the subscriber authentication and the device authentication; and

means for using the security key to secure communications between the device and a serving network.

27. The device of claim 26, further comprising:

means for storing a subscriber-specific key used for the subscriber authentication; and

means for storing a device-specific key used for the device authentication.

28. A non-transitory processor-readable medium comprising instructions operational on a device, which when executed by a processor causes the processor to:

perform subscriber authentication with a network entity based on a subscriber authentication key;

perform device authentication of the device with the network entity to obtain device authentication data, wherein the device authentication data is obtained based on a challenge received by the device and on a device identity or credential, the device authentication data incorporating at least a portion of the challenge and wherein the device authentication data includes an encrypted parameter derived from a device temporary key, a network nonce and a device nonce;

generate a security key based on the subscriber authentication key and at least a portion of the device authentication data to bind the subscriber authentication and the device authentication; and

use the security key to secure communications between the device and a serving network.

29. A method operational in a network entity, comprising:

performing subscriber authentication with a device based on a subscriber authentication key;

performing device authentication of the device to obtain device authentication data, wherein the device authentication data is obtained based on a challenge sent to the device and on a device identity or credential, the device authentication data incorporating at least a portion of the challenge and wherein the device authentication data includes an encrypted parameter derived from a device temporary key, a network nonce and a device nonce;

generating a security key based on the subscriber authentication key and at least a portion of the device authentication data to bind the subscriber authentication and the device authentication; and

using the security key to secure communications between the network entity and the device.

30. The method of claim 29, wherein device authentication includes:

receiving a certificate from the device;

verifying the certificate associated with the device has not been revoked.

31. The method of claim 29, further comprising:

receiving an attach request from the device, the attach request including an indication that the device is capable of device authentication.

32. The method of claim 29, wherein device authentication is secured by at least one key generated during the subscriber authentication.

33. The method of claim 29, wherein subscriber authentication and device authentication are concurrently performed in combined message exchanges in which subscriber authentication and device authentication are combined.

34. The method of claim 29, wherein subscriber authentication is performed in an earlier and separate security exchange from the device authentication.

35. The method of claim 29, wherein the security key is generated as a function of at least a first key obtained from subscriber authentication and a second key obtained from device authentication.

36. The method of claim 29, wherein the security key is separately generated by the device and the network entity.

37. The method of claim 29, further comprising:

obtaining a subscriber-specific key as part of a service agreement, the subscriber-specific key used for the subscriber authentication; and

obtaining a device-specific key for the device, the device-specific key used for the device authentication.

38. The method of claim 29, wherein the device authentication is performed subsequent to, or concurrently with, the subscriber authentication.

39. The method of claim 29, wherein the challenge includes an identifier and the method further includes:

transmitting a command to the device that includes the identifier; and

receiving additional security keys generated by the device based on the security key and the identifier.

40. The method of claim 29, wherein the subscriber authentication is performed based on a subscriber authentication key obtained using a subscriber identity or key stored with the device.

41. A network entity, comprising:

a communication interface; and

a processing circuit coupled to the communication interface, the processing circuit adapted to;

perform subscriber authentication with a device based on a subscriber authentication key;

perform device authentication of the device to obtain device authentication data, wherein the device authentication data is obtained based on a challenge sent to the device and on a device identity or credential, the device authentication data incorporating at least a portion of the challenge and wherein the device authentication data includes an encrypted parameter derived from a device temporary key, a network nonce and a device nonce;

generate a security key based on the subscriber authentication key and at least a portion of the device authentication data to bind the subscriber authentication and the device authentication; and

use the security key to secure communications between the network entity and the device.

42. The network entity of claim 41, wherein the processing circuit is further adapted to:

receive an attach request from the device, the attach request including an indication that the device is capable of device authentication.

43. The network entity of claim 41, wherein device authentication is secured by at least one key generated during the subscriber authentication.

44. The network entity of claim 41, wherein subscriber authentication and device authentication are concurrently performed in combined message exchanges in which subscriber authentication and device authentication are combined.

45. The network entity of claim 41, wherein subscriber authentication is performed in an earlier and separate security exchange from the device authentication.

46. The network entity of claim 41, wherein the security key is generated as a function of at least a first key obtained from subscriber authentication and a second key obtained from device authentication.

47. The network entity of claim 41, further comprising:

obtaining a subscriber-specific key as part of a service agreement, the subscriber-specific key used for the subscriber authentication; and

obtaining a device-specific key for the device, the device-specific key used for the device authentication.

48. A network entity, comprising

means for performing subscriber authentication with a device based on a subscriber authentication key;

means for performing device authentication of the device to obtain device authentication data, wherein the device authentication data is obtained based on a challenge sent to the device and on a device identity or credential, the device authentication data incorporating at least a portion of the challenge and wherein the device authentication data includes an encrypted parameter derived from a device temporary key, a network nonce and a device nonce;

means for a security key based on the subscriber authentication key and at least a portion of the device authentication data to bind the subscriber authentication and the device authentication; and

means for using the security key to secure communications between the network entity and the device.

49. A non-transitory processor-readable medium comprising instructions operational on a network entity, which when executed by a processor causes the processor to:

perform subscriber authentication with a device based on a subscriber authentication key;

perform device authentication of the device to obtain device authentication data, wherein the device authentication data is obtained based on a challenge sent to the device and on a device identity or credential, the device authentication data incorporating at least a portion of the challenge and wherein the device authentication data includes an encrypted parameter derived from a device temporary key, a network nonce and a device nonce;

generate a security key based on the subscriber authentication key and at least a portion of the device authentication data to bind the subscriber authentication and the device authentication; and

use the security key to secure communications between the network entity and the device.