IP Library Granted Patent US 8,989,709
Granted Patent B2
US 8,989,709 · App. 13/950,803 · Granted Mar 24, 2015

Customization of data session retry mechanism in a wireless packet data service network

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,989,709
App. No.
13/950,803
Granted
Mar 24, 2015
Kind
B2
Abstract

In one embodiment, a method is provided for customization of a mobile communications device's data session retry mechanism in a wireless packet data service network. The mobile communication device requests activation of a data session with a node via the wireless network and receives a reject message via the wireless network in response to the request for activation of the data session, the reject message including a cause code. If the cause code corresponds to a no-retry behavior of the data session retry mechanism of the mobile communication device, the mobile communications device no longer requesting activation of a data session with the node.

Claims (24)

1. A method in a mobile communications device operable in a wireless network, the method comprising:

requesting activation of a data session with a node via the wireless network;

receiving a reject message via the wireless network in response to the request for activation of the data session, the reject message comprising a cause code; and

if the cause code corresponds to a no-retry behavior of the data session retry mechanism of the mobile device, the mobile communications device no longer requesting activation of a data session with the node, wherein the correspondence of the cause code to the no-retry behaviour is at least partly dependent on a carrier that the device is attached to.

2. The method of claim 1 , further comprising checking whether the cause code received in the reject message corresponds to the no-retry behaviour.

3. The method of claim 1 , further comprising continuing to no longer request activation of a data session until the retry mechanism is re-activated.

4. The method of claim 1 , further comprising the mobile communications device continuing to request activation of a data session with the node if the cause code corresponds to a retry behaviour.

5. The method of claim 4 , further comprising checking whether the cause code received in the reject message corresponds to the retry behaviour.

6. The method of claim 1 , wherein the mobile communications device includes a list of cause codes that correspond to no-retry behaviour.

7. The method of claim 1 , wherein the mobile communications device includes a list of cause codes that correspond to retry behaviour.

8. The method of claim 1 , wherein the method is performed after attaching via the wireless network.

9. A mobile communications device operable in a wireless network, comprising:

a microprocessor operably coupled to a communication subsystem and to a memory;

a module operable to request activation of a data session with a node via the wireless network;

a module operable to receive a reject message via the wireless network in response to the request for activation of the data session, the reject message comprising a cause code; and

a data session retry module operable, if the cause code corresponds to a no-retry behavior, to no longer request activation of a data session with the node, the correspondence of the cause code to the no-retry behaviour being at least partly dependent on a carrier that the device is attached to;

wherein the modules comprise one of hardware, firmware and software stored in the memory.

10. The mobile communication device of claim 9 , further comprising a module operable to check whether the cause code received in the reject message corresponds to the no-retry behaviour.

11. The mobile communication device of claim 9 , wherein the data session retry module continues to no longer request activation of a data session until the retry mechanism is re-activated.

12. The mobile communication device of claim 9 , wherein the data session retry module continues to request activation of a data session with the node if the cause code corresponds to a retry behaviour.

13. The mobile communication device of claim 12 , further comprising a module operable to check whether the cause code received in the reject message corresponds to the retry behaviour.

14. The mobile communication device of claim 9 , further comprising a list of cause codes that correspond to no-retry behaviour stored in the memory.

15. The mobile communication device of claim 9 , further comprising a list of cause codes that correspond to retry behaviour.

16. The mobile communication device of claim 9 , further comprising a module operable to attach via the wireless network.

Assignments (2)
CHANGE OF NAME Recorded Oct 20, 2014
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 034016/0738 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 11, 2013
From: CORMIER, JEAN-PHILIPPE; PLESTID, THOMAS LEONARD TREVOR; SIMPSON, IAN; MUNJE, ARUN
To: BLACKBERRY LIMITED
Reel/Frame 031387/0288 →