System and method for determining that a maximum number of IP sessions have been established

• US 8,315,162 B2
• Filed: 10/13/2006
• Issued: 11/20/2012
• Est. Priority Date: 08/24/2006
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Wirtanen, Jeff, Kim, Jin, Islam, M. Khaledul, Plestid, Trevor
• Primary Examiner(s): Bost, Dwayne
• Assistant Examiner(s): STERNBANE, LAURENCE J
• Application Number:
  US11/549,390
• Publication Number:
  US 20080049741A1
• Time in Patent Office: 2,230 Days
• Field of Search: 370/351
• US Class Current: 370/230
• CPC Class Codes: H04W 48/14 using user query or user detection
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

Systems and methods for determining that a maximum number of IP sessions have been established are provided. There are instances when the mobile device transmits a request to the wireless network. According to an aspect, in the event that the maximum number of IP sessions is already established for the mobile device, the wireless network transmits a response indicating that the request cannot be fulfilled. The mobile device determines based on the response that the maximum number of IP sessions is already established, which allows the mobile device to determine the maximum number of IP sessions that can be supported so that IP sessions can be managed accordingly.

Claims

1. A method in a mobile device comprising:

transmitting a request for a new Internet Protocol (IP) session;

receiving in response to the request an indication that the request cannot be fulfilled because a maximum number of IP sessions is already established for the mobile device in a network area;

after receipt of the indication, the mobile device avoiding transmitting any request for a new IP session while the maximum number of IP sessions is established for the mobile device in the network area.

2. The method of claim 1 wherein:

transmitting the request comprises transmitting a plurality of requests in an attempt to establish simultaneous IP sessions;

receiving the indication comprises receiving responses to the plurality of requests; and

the method further comprises determining the maximum number of IP sessions supported on the basis of the attempts to establish IP sessions and the responses to such attempts.

3. The method of claim 2 wherein determining the maximum number of IP sessions supported further comprises:

establishing a default value for the maximum number of IP sessions supported based on capabilities of the wireless network.

4. The method of claim 2 wherein determining the maximum number of IP sessions supported further comprises:

performing a count of how many simultaneous IP sessions have been established.

5. The method of claim 4 wherein determining the maximum number of IP sessions supported further comprises:

upon receiving a defined response to an attempt to establish the IP session, setting the number of IP sessions supported to the count of how many simultaneous IP sessions have been established.

6. The method of claim 5 wherein the defined response is one of:

a PDP activate reject response with a cause code 26;

a service option temporarily out of order response with a cause code of 34;

a PDP activate reject response with a cause code 38;

a PDP activate reject response with a cause code 101;

a response requesting the deactivation of another existing context;

a response requesting the release of radio bearer associated with another existing context; and

a response specifically configured to indicate that there are no more PDP contexts available.

7. The method of claim 1 further comprising:

for previously visited network areas, maintaining history information indicating the maximum number of IP sessions supported by each network area; and

upon moving to a new network area, if the new network area is listed in the history information, looking up the maximum number of IP sessions supported by the new network area in the history information, and otherwise, determining the maximum number of IP sessions supported by the new network area.

8. The method of claim 7 wherein the history information is maintained for network areas to a granularity of PLMN.

9. The method of claim 7 wherein the history information is maintained for network areas to a granularity of PLMN and LAC (local area code).

10. The method of claim 7 wherein the history information is maintained for network areas to a granularity of Routing Area Code (RAC) and Radio Network Controller Identifier (RNC Id).

11. The method of claim 1 further comprising:

for each of a plurality of network areas, storing information identifying a maximum number of IP sessions supported for the mobile device in the network area; and

prior to changing network areas from a first network area to a second network area in which fewer IP sessions are supported than in the first network area, the mobile device preemptively deactivating at least one selected IP session.

12. The method of claim 1 wherein receiving the indication comprises:

receiving a cause code indicating that the request cannot be fulfilled because the maximum number of IP sessions is already established.

13. The method of claim 12 wherein the cause code has a cause value of 102 indicating that the maximum number of IP sessions is already activated.

14. The method of claim 12 wherein:

the request is an Activate PDP context request for requesting a new PDP context to be established; and

the response is an Activate PDP context reject for rejecting the Activate PDP context request.

15. The method of claim 12 wherein:

the request is a PDP context service request for requesting service for an existing PDP context; and

the response is a service reject for rejecting the PDP context service request.

16. The method of claim 12 wherein:

the request is an Activate PDP context request for requesting a new PDP context to be established; and

the response is an MT PDP Deactivate Request for deactivating an existing PDP context.

17. The method of claim 1 wherein each IP session is part of a respective PDP context.

18. The method of claim 1 further comprising:

the mobile device actively managing allocation of IP sessions where there are fewer IP sessions than there are device functions that need IP sessions, with regard to the maximum number of IP sessions supported.

19. The method of claim 18 wherein the IP sessions are PDP contexts.

20. The method of claim 19 further comprising the mobile device determining information identifying the number of PDP contexts supported by:

the mobile device attempting to establish PDP contexts, and receiving responses to such attempts; and

on the basis of the attempts to establish PDP contexts, and the responses to such attempts, the mobile device establishing the number of PDP contexts supported.

21. The method of claim 19 further comprising the mobile device determining information identifying the number of PDP contexts supported by:

the mobile device receiving the information from a given network area.

22. The method of claim 19 wherein the mobile device is pre-configured with information identifying the number of PDP contexts supported.

23. The method of claim 19 further comprising:

the mobile device determining information identifying the number of PDP contexts supported by performing a database query.

24. The method of claim 1 wherein the indication that the request cannot be fulfilled because a maximum number of IP sessions is already established comprises an indication that the request cannot be fulfilled because a maximum number of IP sessions is already established for the mobile device.

25. The method of claim 1 further comprising determining the maximum number of IP sessions supported for the mobile device based on the indication.

26. The method of claim 25 further comprising managing IP sessions based on the maximum number of IP sessions supported for the mobile device.

27. The method of claim 26 further comprising:

accepting a request from an application for establishing a new IP session;

wherein managing IP sessions comprises determining whether to request the new IP session from the wireless network based on the maximum number of IP sessions supported.

28. The method of claim 26 further comprising:

prioritizing IP sessions;

wherein managing IP sessions comprises maintaining IP sessions of higher priority ahead of IP sessions of lower priority when IP sessions are restricted by the maximum number of IP sessions supported.

29. The method of claim 26, wherein managing IP sessions based on the maximum number of IP sessions supported comprises:

having established the number of IP sessions supported, actively managing allocation of IP sessions where there are fewer IP sessions than there are device functions that need IP sessions, with regard to the number of IP sessions supported.

30. The method of claim 29 wherein actively managing the allocation of IP sessions comprises:

prioritizing device functions, and allocating the IP sessions by priority.

31. The method of claim 29 wherein actively managing the allocation of IP sessions comprises:

after changing network areas from a first network area to a second network area in which fewer IP sessions are supported than in the first network area, selectively determining which device functions are to be allocated the IP sessions in the second network area, and establishing these if not already established and deactivating others if not already deactivated.

32. A non-transitory computer readable medium having computer executable instructions stored thereon that, when executed by a processor on a mobile device, cause the mobile device to perform:

transmitting a request for a new Internet Protocol (IP) session;

receiving in response to the request an indication that the request cannot be fulfilled because a maximum number of IP sessions is already established for the mobile device in a network area;

after receipt of the indication, the mobile device avoiding transmitting any request for a new IP session while the maximum number of IP sessions is established for the mobile device in the network area.

33. The non-transitory computer readable medium of claim 32 wherein the instructions, when executed by the processor, further cause the mobile device to perform:

actively managing allocation of IP sessions where there are fewer IP sessions than there are device functions that need IP sessions, with regard to the maximum number of IP sessions supported.

34. The non-transitory computer readable medium of claim 32 wherein the indication that the request cannot be fulfilled because a maximum number of IP sessions is already established comprises an indication that the request cannot be fulfilled because a maximum number of IP sessions is already established for the mobile device.

35. The non-transitory computer readable medium of claim 32 wherein the non-transitory computer readable medium comprises memory or a storage device.

36. A mobile device comprising:

a wireless access radio configured to communicate with a wireless network; and

an IP session management function configured to;

transmit a request for a new Internet Protocol (IP) session;

receive in response to the request an indication that the request cannot be fulfilled because a maximum number of IP sessions is already established for the mobile device in a network area;

after receipt of the indication, cause the mobile device to avoid transmitting any request for a new IP session while the maximum number of IP sessions is established for the mobile device in the network area.

37. The mobile device of claim 36 wherein the IP session management function is further configured to:

actively manage allocation of IP sessions where there are fewer IP sessions than there are device functions that need IP sessions, with regard to the maximum number of IP sessions supported.

38. The mobile device of claim 37 wherein the IP sessions are PDP contexts.

39. The mobile device of claim 38 wherein the IP session management function is further configured to determine information identifying the number of PDP contexts supported by:

attempting to establish PDP contexts, and receiving responses to such attempts; and

on the basis of the attempts to establish PDP contexts, and the responses to such attempts, establishing the number of PDP contexts supported.

40. The mobile device of claim 38 wherein the IP session management function is further configured to determine information identifying the number of PDP contexts supported by receiving the information from a given network area.

41. The mobile device of claim 38 wherein the mobile device is pre-configured with information identifying the number of PDP contexts supported.

42. The mobile device of claim 38 wherein the IP session management function is further configured to:

determine information identifying the number of PDP contexts supported by performing a database query.

43. The mobile device of claim 36 wherein the indication that the request cannot be fulfilled because a maximum number of IP sessions is already established comprises an indication that the request cannot be fulfilled because a maximum number of IP sessions is already established for the mobile device.

44. The mobile device of claim 36 wherein the IP session management function is further configured to:

transmit the request for the new IP session by transmitting a plurality of requests in an attempt to establish simultaneous IP sessions;

receive the indication by receiving responses to the plurality of requests; and

determine the maximum number of IP sessions supported on the basis of the attempts to establish IP sessions and the responses to such attempts.

45. The mobile device of claim 44 wherein the IP session management function is further configured to determine the maximum number of IP sessions supported by establishing a default value for the maximum number of IP sessions supported based on capabilities of the wireless network.

46. The mobile device of claim 44 wherein the IP session management function is further configured to determine the maximum number of IP sessions supported by performing a count of how many simultaneous IP sessions have been established.

47. The mobile device of claim 46 wherein the IP session management function is further configured to determine the maximum number of IP sessions supported by:

upon receiving a defined response to an attempt to establish the IP session, setting the number of IP sessions supported to the count of how many simultaneous IP sessions have been established.

48. The mobile device of claim 47 wherein the defined response is one of:

a PDP activate reject response with a cause code 26;

a service option temporarily out of order response with a cause code of 34;

a PDP activate reject response with a cause code 38;

a PDP activate reject response with a cause code 101;

a response requesting the deactivation of another existing context;

a response requesting the release of radio bearer associated with another existing context; and

a response specifically configured to indicate that there are no more PDP contexts available.

49. The mobile device of claim 36 wherein the IP session management function is further configured to:

for previously visited network areas, maintain history information indicating the maximum number of IP sessions supported by each network area; and

upon moving to a new network area, if the new network area is listed in the history information, look up the maximum number of IP sessions supported by the new network area in the history information, and otherwise, determine the maximum number of IP sessions supported by the new network area.

50. The mobile device of claim 49 wherein the history information is maintained for network areas to a granularity of PLMN.

51. The mobile device of claim 49 wherein the history information is maintained for network areas to a granularity of PLMN and LAC (local area code).

52. The mobile device of claim 49 wherein the history information is maintained for network areas to a granularity of Routing Area Code (RAC) and Radio Network Controller Identifier (RNC Id).

53. The mobile device of claim 36 wherein the IP session management function is further configured to:

for each of a plurality of network areas, store information identifying a maximum number of IP sessions supported for the mobile device in the network area; and

prior to changing network areas from a first network area to a second network area in which fewer IP sessions are supported than in the first network area, preemptively deactivate at least one selected IP session.

54. The mobile device of claim 36 wherein the IP session management function is configured to receive the indication by:

receiving a cause code indicating that the request cannot be fulfilled because the maximum number of IP sessions is already established.

55. The mobile device of claim 54 wherein the cause code has a cause value of 102 indicating that the maximum number of IP sessions is already activated.

56. The mobile device of claim 54 wherein:

the request is an Activate PDP context request for requesting a new PDP context to be established; and

the response is an Activate PDP context reject for rejecting the Activate PDP context request.

57. The mobile device of claim 54 wherein:

the request is a PDP context service request for requesting service for an existing PDP context; and

the response is a service reject for rejecting the PDP context service request.

58. The mobile device of claim 54 wherein:

the request is an Activate PDP context request for requesting a new PDP context to be established; and

the response is an MT PDP Deactivate Request for deactivating an existing PDP context.

59. The mobile device of claim 36 wherein each IP session is part of a respective PDP context.

60. The mobile device of claim 36 wherein the IP session management function is further configured to determine the maximum number of IP sessions supported for the mobile device based on the indication.

61. The mobile device of claim 60 wherein the IP session management function is further configured to manage IP sessions based on the maximum number of IP sessions supported for the mobile device.

62. The mobile device of claim 61 wherein the IP session management function is further configured to:

accept a request from an application for establishing a new IP session; and

manage the IP sessions by determining whether to request the new IP session from the wireless network based on the maximum number of IP sessions supported.

63. The mobile device of claim 61 wherein the IP session management function is further configured to:

prioritize IP sessions; and

manage the IP sessions by maintaining IP sessions of higher priority ahead of IP sessions of lower priority when IP sessions are restricted by the maximum number of IP sessions supported.

64. The mobile device of claim 61 wherein the IP session management function is configured to manage the IP sessions based on the maximum number of IP sessions by:

having established the number of IP sessions supported, actively managing allocation of IP sessions where there are fewer IP sessions than there are device functions that need IP sessions, with regard to the number of IP sessions supported.

65. The mobile device of claim 64 wherein the IP session management function is configured to actively manage the allocation of IP sessions by prioritizing device functions, and allocating the IP sessions by priority.

66. The mobile device of claim 64 wherein the IP session management function is configured to actively manage the allocation of IP sessions by:

after changing network areas from a first network area to a second network area in which fewer IP sessions are supported than in the first network area, selectively determining which device functions are to be allocated the IP sessions in the second network area, and establishing these if not already established and deactivating others if not already deactivated.