IP Library Granted Patent US 11,930,012
Granted Patent B2
US 11,930,012 · App. 17/982,686 · Granted Mar 12, 2024

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

Inventors: Jean-Philippe Paul Cormier (Ottawa, CA); Thomas Leonard Trevor Plestid (Ottawa, CA); Ian Simpson (Ottawa, CA); Arun Munje (Ottawa, CA)
Assignee: BlackBerry Limited
H04L63/10H04W12/06H04W12/12H04W28/18H04W48/06H04W60/00H04W76/19H04W8/245H04W80/00
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 11,930,012
App. No.
17/982,686
Granted
Mar 12, 2024
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 (32)

1. A method, comprising:

sending, from a mobile device to a node of a wireless network, a request for activation of a data session;

receiving, at the mobile device, a message in response to the request for activation of the data session, wherein the message comprises a rejection of the request for activation of the data session and a cause code, a retry configuration is associated with the cause code, the retry configuration is configured by the wireless network and the retry configuration indicates that a data session retry mechanism is to be disabled; and

disabling, by the mobile device, a further request for activation of the data session with the node in response to determining that the retry configuration indicates that the data session retry mechanism is to be disabled.

2. The method of claim 1 , further comprising:

receiving a second retry configuration associated with the cause code indicating that the data session retry mechanism is to be enabled.

3. The method of claim 1 , wherein the request for activation of the data session is sent after an attachment procedure between the mobile device and the wireless network.

4. The method of claim 1 , wherein a second cause code is configured to be associated with a first carrier of the wireless network and a second retry configuration.

5. The method of claim 4 , wherein a third cause code is configured to be associated with a second carrier of the wireless network and a third retry configuration.

6. The method of claim 4 , wherein a plurality of cause codes are configured to be associated with a plurality of carriers of the wireless network and a plurality of retry mechanism flags indicating whether a data session retry mechanism is to be disabled.

7. A mobile device, comprising:

at least one processor;

one or more non-transitory computer-readable storage media coupled to the at least one processor and storing programming instructions for execution by the at least one processor, wherein the programming instructions, when executed, cause the mobile device to perform operations comprising:

sending, to a node of a wireless network, a request for activation of a data session;

receiving a message in response to the request for activation of the data session, wherein the message comprises a rejection of the request for activation of the data session and a cause code, a retry configuration is associated with the cause code, the retry configuration is configured by the wireless network and the retry configuration indicates that a data session retry mechanism is to be disabled; and

disabling a further request for activation of the data session with the node in response to determining that the retry configuration indicates that the data session retry mechanism is to be disabled.

8. The mobile device of claim 7 , wherein the operations further comprise:

receiving a second retry configuration associated with the cause code indicating that the data session retry mechanism is to be enabled.

9. The mobile device of claim 7 , wherein the request for activation of the data session is sent after an attachment procedure between the mobile device and the wireless network.

10. The mobile device of claim 7 , wherein a second cause code is configured to be associated with a first carrier of the wireless network and a second retry configuration.

11. The mobile device of claim 10 , wherein a third cause code is configured to be associated with a second carrier of the wireless network and a third retry configuration.

12. The mobile device of claim 10 , wherein a plurality of cause codes are configured to be associated with a plurality of carriers of the wireless network and a plurality of retry mechanism flags indicating whether a data session retry mechanism is to be disabled.

13. A non-transitory computer-readable medium containing instructions which, when executed, cause a computing device to perform operations comprising:

sending, from a mobile device to a node of a wireless network, a request for activation of a data session; and

receiving, at the mobile device, a message in response to the request for activation of the data session, wherein the message comprises a rejection of the request for activation of the data session and a cause code, a retry configuration is associated with the cause code, the retry configuration is configured by the wireless network and the retry configuration indicates that a data session retry mechanism is to be disabled; and

disabling, by the mobile device, a further request for activation of the data session with the node in response to determining that the retry configuration indicates that the data session retry mechanism is to be disabled.

14. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise:

receiving a second retry configuration associated with the cause code indicating that the data session retry mechanism is to be enabled.

15. The non-transitory computer-readable medium of claim 13 , wherein the request for activation of the data session is sent after an attachment procedure between the mobile device and the wireless network.

16. The non-transitory computer-readable medium of claim 13 , wherein a second cause code is configured to be associated with a first carrier of the wireless network and a second retry configuration.

17. The non-transitory computer-readable medium of claim 16 , wherein a third cause code is configured to be associated with a second carrier of the wireless network and a third retry configuration.

18. The non-transitory computer-readable medium of claim 16 , wherein a plurality of cause codes are configured to be associated with a plurality of carriers of the wireless network and a plurality of retry mechanism flags indicating whether a data session retry mechanism is to be disabled.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2023
From: CORMIER, JEAN-PHILIPPE
To: RESEARCH IN MOTION LIMITED
Reel/Frame 062904/0775 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2023
From: MUNJE, ARUN; PLESTID, THOMAS LEONARD TREVOR
To: RESEARCH IN MOTION LIMITED
Reel/Frame 062904/0816 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2023
From: SIMPSON, IAN
To: RESEARCH IN MOTION LIMITED
Reel/Frame 062904/0877 →
CHANGE OF NAME Recorded Mar 7, 2023
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 062974/0073 →
Continuity (8)
Continuation 17173086 · Feb 10, 2021
Continuation 16596046 · Oct 8, 2019
Continuation 15852270 · Dec 22, 2017
Continuation 14666048 · Mar 23, 2015
Continuation 13950803 · Jul 25, 2013
Continuation 12480569 · Jun 8, 2009
Continuation 10981864 · Nov 5, 2004
Related Publication 20230060898A1 · Mar 2, 2023