METHODS AND APPARATUS TO MAKE OPEN MARKET HANDSETS (C.S0023-D OR C.S0065-B COMPLAINT) BACKWARD COMPATIBLE WITH OLD RUIM CARDS

• US 20110287752A1
• Filed: 02/25/2011
• Published: 11/24/2011
• Est. Priority Date: 05/20/2010
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Duggal, Nakul, SAHU, DEBESH KUMAR, Du, Zhimin, Veerepalli, Sivaramakrishna
• Granted Patent: US 8,903,367 B2
• Time in Patent Office: Days
• US Class Current: 455/418
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

A method and apparatus for enabling backward compatibility in open market handsets (OMH) is provided. The method may include determining a type of an identity module based on one or more internal parameters of the identity module, and obtaining one or more credentials based at least in part on the determined the type identity module.

Claims

1. A method of communications for a device, comprising:

determining a type of an identity module based on one or more internal parameters of the identity module; and

obtaining one or more credentials based at least in part on the determined the type identity module.

2. The method of claim 1, further comprising:

detecting a change in the identity module, wherein the change is either adding of a new identity module to the device, or changing the type of the identity module in the device; and

enabling the device using the one or more internal parameters and the one or more obtained credentials.

3. The method of claim 1, wherein the one or more internal parameters comprise at least one of:

a state of a service, or a configuration parameter.

4. The method of claim 1, wherein the one or more credentials comprise at least one of:

open market handset (OMH) credentials, or 3G packet data (3GPD) credentials.

5. The method of claim 1, wherein the identity module comprises a mobile country code (MCC) and a mobile network code (MNC), and wherein the obtaining further comprises using the MCC and MNC to determine the one or more credentials.

6. The method of claim 1, wherein the obtaining further comprises:

determining the one or more credentials are stored in nonvolatile (NV) memory of the device; and

accessing the one or more credentials stored in the NV memory of the device.

7. The method of claim 1, wherein the obtaining further comprises:

determining at least one of;

one or more provisioning parameters or the one or more credentials are available from a server; and

accessing the at least one of the one or more provisioning parameters or the one or more credentials from the server.

8. The method of claim 1, wherein the obtaining further comprises:

obtaining a dynamic profile for an application based on the one or more internal parameters of the identity module, wherein the dynamic profile includes one or more parameters different than the one or more internal parameters.

9. The method of claim 1, further comprising:

generating a virtual identification module based on the one or more internal parameters of the identity module and the obtained one or more credentials.

10. The method of claim 1, further comprising:

detecting that the identity module has been connected to the device; and

determining that the type of the identity module is a legacy identity module.

11. The method of claim 10, wherein the identity module comprises either a removable user identify module (RUIM) or a CDMA subscriber identity module (CSIM), wherein a legacy identity module comprises a RUIM not compatible with a C.S0023-D standard, or a CSIM not compatible with a C.S0065-A standard.

12. The method of claim 1, wherein the one or more internal parameters comprise at least one of:

an n15 element in a CST table of RUIM;

n35 element in a CST table of CSIM;

or

an EF_SIPUPPext element.

13. The method of claim 12, further comprising:

determining that the EF_SIPUPPext element is faulty when at least one of;

the EF_SIPUPPext element is not present;

or

14. At least one processor configured to provide backward compatibility, comprising:

a first module for determining a type of an identity module based on one or more internal parameters of the identity module; and

a second module for obtaining one or more credentials based at least in part on the determined the type identity module.

15. A computer program product, comprising:

a computer-readable medium comprising;

a first set of codes for causing a computer to determine a type of an identity module based on one or more internal parameters of the identity module; and

a second set of codes for causing the computer to obtain one or more credentials based at least in part on the determined the type identity module.

16. An apparatus, comprising:

means for determining a type of an identity module based on one or more internal parameters of the identity module; and

means for obtaining one or more credentials based at least in part on the determined the type identity module.

17. The apparatus of claim 16, further comprising:

means for detecting a change in the identity module, wherein the change is either adding of a new identity module to the device, or changing the type of the identity module in the device; and

means for enabling the device using the one or more internal parameters and the one or more obtained credentials.

18. The apparatus of claim 16, wherein the one or more internal parameters comprise at least one of:

a state of a service, or a configuration parameter.

19. The apparatus of claim 16, wherein the one or more credentials comprise at least

one of:

OMH credentials, or 3G packet data (3GPD) credentials.

20. The apparatus of claim 16, wherein the identity module comprises a mobile country code (MCC) and a mobile network code (MNC), and wherein the means for obtaining further comprises using the MCC and MNC to determine the one or more credentials.

21. The apparatus of claim 16, wherein the means for obtaining further comprise:

means for determining the one or more credentials are stored in nonvolatile (NV) memory of the device; and

means for accessing the one or more credentials stored in the NV memory of the device.

22. The apparatus of claim 16, wherein the means for obtaining further comprise:

means for determining at least one of;

one or more provisioning parameters or the one or more credentials are available from a server; and

means for accessing the at least one of the one or more provisioning parameters or the one or more credentials from the server.

23. The apparatus of claim 16, wherein the means for obtaining further comprise:

means for obtaining a dynamic profile for an application based on the one or more internal parameters of the identity module, wherein the dynamic profile includes one or more parameters different than the one or more internal parameters.

24. The apparatus of claim 16, further comprising:

means for generating a virtual identification module based on the one or more internal parameters of the identity module and the obtained one or more credentials.

25. The method of claim 16, further comprising:

means for detecting that the identity module has been connected to the device; and

means for determining that the type of the identity module is a legacy identity module.

26. The apparatus of claim 25, wherein the identity module comprises either a removable user identify module (RUIM) or a CDMA subscriber identity module (CSIM), wherein a legacy identity module comprises a RUIM not compatible with a C.S0023-D standard, or a CSIM not compatible with a C.S0065-A standard.

27. The apparatus of claim 16, wherein the one or more internal parameters comprise at least one of:

an n15 element in a CST table of RUIM;

n35 element in a CST table of CSIM;

or

an EF_SIPUPPext element.

28. The apparatus of claim 27, further comprising:

means for determining that the EF_SIPUPPext element is faulty when at least one of;

the EF_SIPUPPext element is not present;

or

the EF_SIPUPPext element is not properly configured.

29. An apparatus for enabling backward compatibility, comprising:

a compatibility module operable for;

determining a type of an identity module based on one or more internal parameters of the identity module; and

obtaining one or more credentials based at least in part on the determined the type identity module.

30. The apparatus of claim 29, wherein the compatibility module is further operable for:

detecting a change in the identity module, wherein the change is either adding of a new identity module to the device, or changing the type of the identity module in the device; and

enabling the device using the one or more internal parameters and the one or more obtained credentials.

31. The apparatus of claim 29, wherein the one or more internal parameters comprise at least one of:

a state of a service, or a configuration parameter.

32. The apparatus of claim 29, wherein the one or more credentials comprise at least one of:

OMH credentials, or 3G packet data (3GPD) credentials.

33. The apparatus of claim 29, wherein the identity module comprises a mobile country code (MCC) and a mobile network code (MNC), and wherein the compatibility module is further operable for using the MCC and MNC to determine the one or more credentials.

34. The apparatus of claim 29, wherein the compatibility module is further operable for:

determining the one or more credentials are stored in nonvolatile (NV) memory of the device; and

accessing the one or more credentials stored in the NV memory of the device.

35. The apparatus of claim 29, wherein the compatibility module is further operable for:

determining at least one of the one or more provisioning parameters or the one or more credentials are available from a server; and

accessing the at least one of the one or more provisioning parameters or the one or more credentials from the server.

36. The apparatus of claim 29, wherein the compatibility module is further operable for:

obtaining a dynamic profile for an application based on the one or more internal parameters of the identity module, wherein the dynamic profile includes one or more parameters different than the one or more internal parameters.

37. The apparatus of claim 29, wherein the compatibility module is further operable for:

generating a virtual identification module based on the one or more internal parameters of the identity module and the obtained one or more credentials.

38. The apparatus of claim 29, wherein the compatibility module is further operable for:

detecting that the identity module has been connected to the device; and

determining that the type of the identity module is a legacy identity module.

39. The apparatus of claim 38, wherein the identity module comprises either a removable user identify module (RUIM) or a CDMA subscriber identity module (CSIM), and wherein a legacy identity module comprises a RUIM not compatible with a C.S0023-D standard, or a CSIM not compatible with a C.S0065-A standard.

40. The apparatus of claim 29, wherein the one or more internal parameters comprise at least one of:

an n15 element in a CST table of RUIM;

n35 element in a CST table of CSIM;

or

an EF_SIPUPPext element.

41. The apparatus of claim 40, wherein the compatibility module is further operable for:

determining that the EF_SIPUPPext element is faulty when at least one of;

the EF_SIPUPPext element is not present;

or

the EF_SIPUPPext element is not properly configured.