Methods and apparatus for enabling fallback to a second data service based on the presence of fallback conditions associated with establishment of a data context with a first data service

• US 9,185,730 B2
• Filed: 06/04/2012
• Issued: 11/10/2015
• Est. Priority Date: 06/09/2011
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Zhao, Suli, Balasubramanian, Srinivasan, Payyappilly, Ajith Tom
• Primary Examiner(s): Kizou, Hassan
• Assistant Examiner(s): NGUYEN, TOAN D
• Application Number:
  US13/488,298
• Publication Number:
  US 20120314562A1
• Time in Patent Office: 1,254 Days
• Field of Search: 370/216, 370/328, 370/329, 370/331, 370/338, 370/341, 370/348, 370/312, 455/63.1, 455/422.1, 455/434, 455/436, 455/453
• US Class Current: 1/1
• CPC Class Codes: H04W 24/08 Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

Aspects disclosed herein relate to enabling fallback to a second data service based on whether one or more fallback conditions are present before or during establishing a data context with a first data service. In one example, a UE may be configured to determine whether one or more fallback conditions are present before or during establishing a data session with a first data service. The UE may be further configured to prohibit further attempts to establish a data context to access the first data service based on the determination of the presence of at least one of the one or more fallback conditions. Some aspects disclosed herein relate to enabling fallback to a HRPD data service based on whether one or more fallback conditions are present before or during establishing a data context with an eHRPD data service.

Claims

1. A method of wireless communications, comprising:

determining whether one or more fallback conditions are present before or during establishing a data session with a first data service via a first data system; and

prohibiting further attempts to establish a data context to access the first data service via the first data system based on the determination of the presence of at least one of the one or more fallback conditions;

wherein one of the one or more fallback conditions indicates an occurrence of a hard fallback failure or an occurrence of a soft fallback failure;

wherein when the one of the one or more fallback conditions indicates the occurrence of the hard fallback failure, the first data service comprises an evolved high rate packet data (eHRPD) service, and the hard fallback failure comprises an authentication failure; and

wherein when the one or more fallback conditions indicates the occurrence of the soft fallback failure, the first data service comprises the eHRPD service, and the soft fallback failure comprises a link control protocol (LCP) negotiation procedure failure.

2. The method of claim 1, wherein one of the one or more fallback conditions indicates a number of soft fallback failures that can occur prior to prohibiting the attempt to establish the data context to access the first data service.

3. The method of claim 1, wherein one of the one or more fallback conditions indicates that the occurrence of the hard fallback failure is to be treated as the occurrence of the soft fallback failure.

4. The method of claim 1, wherein one of the one or more fallback conditions indicates occurrence of a failure of at least one access point name (APN) associated with a packet data network (PDN) connection attempt.

5. The method of claim 1, wherein one of the one or more fallback conditions indicates that a user equipment (UE) is prohibited from attempting to establish the data context to access the first data service when the UE is being supported by a roaming network.

6. The method of claim 1, wherein one of the one or more fallback conditions indicates that a user equipment (UE) is prohibited from attempting to establish the data context to access the first data service when a value is set in an application profile associated with the UE.

7. The method of claim 1, further comprising:

establishing a data session with a second data service via a second data system; and

determining whether to reattempt to establish a data context to access the first data service via the first data system based on one or more first data service reconnection triggers.

8. The method of claim 7, wherein one of the first data service reconnection triggers comprises expiration of a retry timer.

9. The method of claim 7, wherein one of the first data service reconnection triggers comprises detection of an event occurrence.

10. The method of claim 9, wherein detection of the event occurrence further comprises determining that the data session with the second data service is closed and a new data session is being proposed.

11. The method of claim 9, further comprising moving to long term evolution (LTE) network and wherein detection of the event occurrence further comprises determining that a successful authentication to the LTE network has been performed based on an LTE system attach procedure.

12. The method of claim 11, further comprising using a LTE tunnel to pre-register with the second data service.

13. The method of claim 12, further comprising reattempting to establish a data context to access the first data service over the LTE tunnel.

14. The method of claim 11, further comprising reattempting to establish a data context to access the first data service prior to expiration of a retry timer.

15. The method of claim 11, further comprising:

detecting that a UE has moved to a location that includes coverage based on a common access network associated with the first data service and the second data service; and

reattempting to establish a data context to access the first data service based on the detection.

16. The method of claim 9, wherein detection of the event occurrence further comprises determining that a power cycle has been completed.

17. The method of claim 7, wherein the second data service is a high rate packet data (HRPD) service.

18. The method of claim 1, wherein the determining and the prohibiting are performed by a UE.

19. An apparatus for communications, comprising:

means for determining whether one or more fallback conditions are present before or during establishing a data session with a first data service via a first data system; and

means for prohibiting further attempts to establish a data context to access the first data service via the first data system based on the determination of the presence of at least one of the one or more fallback conditions;

wherein one of the one or more fallback conditions indicates an occurrence of a hard fallback failure or an occurrence of a soft fallback failure;

wherein when the one of the one or more fallback conditions indicates the occurrence of the hard fallback failure, the first data service comprises an evolved high rate packet data (eHRPD) service, and the hard fallback failure comprises an authentication failure; and

wherein when the one or more fallback conditions indicates the occurrence of the soft fallback failure, the first data service comprises the eHRPD service, and the soft fallback failure comprises a link control protocol (LCP) negotiation procedure failure.

20. The apparatus of claim 19, wherein one of the one or more fallback conditions indicates a number of soft fallback failures that can occur prior to prohibiting the attempt to establish the data context to access the first data service.

21. The apparatus of claim 19, wherein one of the one or more fallback conditions indicates that the occurrence of the hard fallback failure is to be treated as the occurrence of the soft fallback failure.

22. The apparatus of claim 19, wherein one of the one or more fallback conditions indicates occurrence of a failure of at least one access point name (APN) associated with a packet data network (PDN) connection attempt.

23. The apparatus of claim 19, wherein one of the one or more fallback conditions indicates that a user equipment (UE) is prohibited from attempting to establish the data context to access the first data service when the UE is being supported by a roaming network.

24. The apparatus of claim 19, wherein one of the one or more fallback conditions indicates that a user equipment (UE) is prohibited from attempting to establish the data context to access the first data service when a value is set in an application profile associated with the UE.

25. The apparatus of claim 19, further comprising:

means for establishing a data session with a second data service via a second data system; and

means for determining whether to reattempt to establish a data context to access the first data service via the first data system based on one or more first data service reconnection triggers.

26. The apparatus of claim 25, wherein one of the first data service reconnection triggers comprises expiration of a retry timer.

27. The apparatus of claim 25, wherein one of the first data service reconnection triggers comprises detection of an event occurrence.

28. The apparatus of claim 27, wherein detection of the event occurrence further comprises determining that the data session with the second data service is closed and a new data session is being proposed.

29. The apparatus of claim 27, further comprising moving to long term evolution (LTE) network and wherein detection of the event occurrence further comprises determining that a successful authentication to the LTE network has been performed based on an LTE system attach procedure.

30. The apparatus of claim 29, further comprising means for using a LTE tunnel to pre-register with the second data service.

31. The apparatus of claim 30, further comprising means for reattempting to establish a data context to access the first data service over the LTE tunnel.

32. The apparatus of claim 29, further comprising means for reattempting to establish a data context to access the first data service prior to expiration of a retry timer.

33. The apparatus of claim 29, further comprising:

means for detecting that a UE has moved to a location that includes coverage based on a common access network associated with the first data service and the second data service; and

means for reattempting to establish a data context to access the first data service based on the detection.

34. The apparatus of claim 27, wherein detection of the event occurrence further comprises determining that a power cycle has been completed.

35. The apparatus of claim 25, wherein the second data service is a high rate packet data (HRPD) service.

36. The apparatus of claim 19, wherein the means for determining and the means for prohibiting are included in a UE.

37. A device for communications, comprising:

a memory;

a processor coupled to the memory; and

a data service access module coupled to at least one of the memory or the processor, and configured to;

determine whether one or more fallback conditions are present before or during establishing a data session with a first data service via a first data system; and

prohibit further attempts to establish a data context to access the first data service via the first data system based on the determination of the presence of at least one of the one or more fallback conditions;

wherein one of the one or more fallback conditions indicates an occurrence of a hard fallback failure or an occurrence of a soft fallback failure;

wherein when the one of the one or more fallback conditions indicates the occurrence of the hard fallback failure, the first data service comprises an evolved high rate packet data (eHRPD) service, and the hard fallback failure comprises an authentication failure; and

wherein when the one or more fallback conditions indicates the occurrence of the soft fallback failure, the first data service comprises the eHRPD service, and the soft fallback failure comprises a link control protocol (LCP) negotiation procedure failure.

38. The apparatus of claim 37, wherein one of the one or more fallback conditions indicates a number of soft fallback failures that can occur prior to prohibiting the attempt to establish the data context to access the first data service.

39. The apparatus of claim 37, wherein one of the one or more fallback conditions indicates that the occurrence of the hard fallback failure is to be treated as the occurrence of the soft fallback failure.

40. The apparatus of claim 37, wherein one of the one or more fallback conditions indicates occurrence of a failure of at least one access point name (APN) associated with a packet data network (PDN) connection attempt.

41. The apparatus of claim 37, wherein one of the one or more fallback conditions indicates that the apparatus is prohibited from attempting to establish the data context to access the first data service when the apparatus is being supported by a roaming network.

42. The apparatus of claim 37, wherein one of the one or more fallback conditions indicates that the apparatus is prohibited from attempting to establish the data context to access the first data service when a value is set in an application profile associated with the apparatus.

43. The apparatus of claim 37, wherein data service access module is further configured to:

establish a data session with a second data service via a second data system; and

determine whether to reattempt to establish a data context to access the first data service via the first data system based on one or more first data service reconnection triggers.

44. The apparatus of claim 43, wherein one of the first data service reconnection triggers comprises expiration of a retry timer.

45. The apparatus of claim 43, wherein one of the first data service reconnection triggers comprises detection of an event occurrence.

46. The apparatus of claim 45, wherein data service access module is further configured to determine that the data session with the second data service is closed and a new data session is being proposed.

47. The apparatus of claim 45, further comprising moving to long term evolution (LTE) network and wherein the data service access module is further configured to determine that a successful authentication to the LTE network has been performed based on an LTE system attach procedure.

48. The apparatus of claim 47, wherein the data service access module is further configured to use a LTE tunnel to pre-register with the second data service.

49. The apparatus of claim 48, wherein the data service access module is further configured to reattempt to establish a data context to access the first data service over the LTE tunnel.

50. The apparatus of claim 47, wherein the data service access module is further configured to reattempt to establish a data context to access the first data service prior to expiration of a retry timer.

51. The apparatus of claim 47, wherein the data service access module is further configured to:

detect that the apparatus has moved to a location that includes coverage based on a common access network associated with the first data service and the second data service; and

reattempt to establish a data context to access the first data service based on the detection.

52. The apparatus of claim 45, wherein the data service access module is further configured to determine that a power cycle has been completed.

53. The apparatus of claim 43, wherein the second data service is a high rate packet data (HRPD) service.

54. A non-transitory computer-readable medium storing computer executable code for wireless communication, comprising code for:

determining whether one or more fallback conditions are present before or during establishing a data session with a first data service via a first data system; and

prohibiting further attempts to establish a data context to access the first data service via the first data system based on the determination of the presence of at least one of the one or more fallback conditions;

wherein one of the one or more fallback conditions indicates an occurrence of a hard fallback failure or an occurrence of a soft fallback failure;

wherein when the one of the one or more fallback conditions indicates the occurrence of the hard fallback failure, the first data service comprises an evolved high rate packet data (eHRPD) service, and the hard fallback failure comprises an authentication failure; and

wherein when the one or more fallback conditions indicates the occurrence of the soft fallback failure, the first data service comprises the eHRPD service, and the soft fallback failure comprises a link control protocol (LCP) negotiation procedure failure.