# US 10,455,480 B2 · Customization of data session retry mechanism in a wireless packet data service network > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,455,480 B2 - Document ID: US10455480B2 - Status: Granted - Kind: B2 - Application number: 15/852,270 - Filed: 2017-12-22 - Published: 2018-05-03 - Granted: 2019-10-22 - Earliest claimed: 2004-11-05 - Assignees: BlackBerry Limited - Applicants: BlackBerry Limited - Inventors: Jean-Philippe Paul Cormier; Thomas Leonard Trevor Plestid; Ian Simpson; Arun Munje - Web page: https://patentgrep.com/patent/US10455480B2 ## CPC - H04L 63/10: {for controlling access to devices or network resources} - H04W 12/06: Authentication - H04W 12/12: Detection or prevention of fraud - H04W 12/122: Counter-measures against attacks; Protection against rogue devices - H04W 28/18: Negotiating wireless communication parameters - H04W 48/06: based on traffic conditions - H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration - H04W 60/001: {Registration rejection or failure} - H04W 76/19: Connection re-establishment - H04W 8/245: {from a network towards a terminal} - H04W 80/00: Wireless network protocols or protocol adaptations to wireless operation - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## 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 ### Claim 1 A method, comprising: after an attempt by a mobile communications device to make its presence known has been accepted by a carrier of a wireless network: receiving, at the mobile communications device and from the wireless network, a retry configuration associated with a cause code, the retry configuration indicating whether a data session retry mechanism is to be disabled; in response to sending a request for a data session with a node, receiving, at the mobile communications device, a message comprising a rejection of the request for activation of the data session, the message comprising the cause code, wherein the data session allows data exchange with packets via the wireless network; and in response to the retry configuration associated with the cause code indicating that the data session retry mechanism is to be disabled, disabling, by the mobile communications device, a second request for activation of the data session with the node, wherein the retry configuration is configured by the carrier of the wireless network. ### Claim 2 (depends on 1) 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; and in response to the second retry configuration associated with the cause code indicating that the data session retry mechanism is to be enabled, enabling, by the mobile communications device, a third request for activation of the data session with the node. ### Claim 3 (depends on 1) The method of claim 1, wherein the mobile communications device making its presence known comprises performing an attachment procedure. ### Claim 4 (depends on 1) The method of claim 1, wherein the retry configuration associated with the cause code is stored in a cause code resource file at the mobile communications device, and the cause code resource file stores a second retry configuration associated with a second cause code configured by the carrier. ### Claim 5 (depends on 4) The method of claim 4, wherein the cause code resource file stores a third retry configuration associated with the cause code configured by a second carrier of the wireless network. ### Claim 6 (depends on 1) The method of claim 1, wherein the wireless network comprises at least one of a General Packet Radio Service (GPRS) network, an Enhanced Data Rates for Global System for Mobile Communications (GSM) Evolution (EDGE) network, a 3rd Generation (3G) network, an Integrated Digital Enhanced Network (IDEN), or a Code Division Multiple Access (CDMA) network. ### Claim 7 (depends on 1) The method of claim 1, wherein activation of the data session includes activation of a packet data protocol (PDP) context. ### Claim 8 A mobile communications device, comprising: a memory; and at least one hardware processor communicatively coupled with the memory and configured to perform a method comprising: after an attempt by a mobile communications device to make its presence known has been accepted by a carrier of a wireless network: receiving, at the mobile communications device and from the wireless network, a retry configuration associated with a cause code, the retry configuration indicating whether a data session retry mechanism is to be disabled; in response to sending a request for a data session with a node, receiving, at the mobile communications device, a reject message comprising a rejection of the request for activation of the data session, the message comprising the cause code, wherein the data session allows data exchange with packets via the wireless network; and in response to the retry configuration associated with the cause code indicating that the data session retry mechanism is to be disabled, disabling, by the mobile communications device, a second request for activation of the data session with the node, wherein the retry configuration is configured by the carrier of the wireless network. ### Claim 9 (depends on 8) The mobile communications device of claim 8, wherein the method further comprises: receiving a second retry configuration associated with the cause code indicating that the data session retry mechanism is to be enabled; and in response to the second retry configuration associated with the cause code indicating that the data session retry mechanism is to be enabled, enabling, by the mobile communications device, a third request for activation of the data session with the node. ### Claim 10 (depends on 4) The method of claim 4, wherein the cause code resource file indicates an association among a plurality of carriers, a plurality of cause codes, and a plurality of retry mechanism flags indicating whether a data session retry mechanism is to be disabled. ### Claim 11 (depends on 10) The method of claim 10, further comprises: comparing the cause code in the message with the retry configuration in the cause code resource file stored at the mobile communications device; and determining the retry configuration associated with the cause code indicating that the data session retry mechanism is to be disabled by determining that the cause code in the message matches the cause code associated with the retry configuration in the cause code resource file that indicates the data session retry mechanism is to be disabled. ### Claim 12 (depends on 8) The mobile communications device of claim 8, wherein the retry configuration associated with the cause code is stored in a cause code resource file at the mobile communications device, and the cause code resource file stores a second retry configuration associated with a second cause code configured by the carrier. ### Claim 13 (depends on 12) The mobile communications device of claim 12, wherein the cause code resource file stores a third retry configuration associated with the cause code configured by a second carrier of the wireless network. ### Claim 14 (depends on 8) The mobile communications device of claim 8, wherein the wireless network comprises at least one of a General Packet Radio Service (GPRS) network, an Enhanced Data Rates for Global System for Mobile Communications (GSM) Evolution (EDGE) network, a 3rd Generation (3G) network, an Integrated Digital Enhanced Network (IDEN), or a Code Division Multiple Access (CDMA) network. ### Claim 15 (depends on 8) The mobile communications device of claim 8, wherein activation of the data session includes activation of a packet data protocol (PDP) context. ### Claim 16 A non-transitory computer-readable medium containing instructions which, when executed, cause a mobile communications device to perform operations comprising: after an attempt by a mobile communications device to make its presence known has been accepted by a carrier of a wireless network: receiving, at the mobile communications device and from the wireless network, a retry configuration associated with a cause code, the retry configuration indicating whether a data session retry mechanism is to be disabled; in response to sending a request for a data session with a node, receiving, at the mobile communications device, a message comprising a rejections of the request for activation of the data session, the message comprising the cause code, wherein the data session allows data exchange with packets via the wireless network; and in response to the retry configuration associated with the cause code indicating that the data session retry mechanism is to be disabled, disabling, by the mobile communications device, a second request for activation of the data session with the node, wherein the retry configuration is configured by the carrier of the wireless network. ### Claim 17 (depends on 16) The non-transitory computer-readable medium of claim 16, 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; and in response to the second retry configuration associated with the cause code indicating that the data session retry mechanism is to be enabled, enabling, by the mobile communications device, a third request for activation of the data session with the node. ### Claim 18 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the retry configuration associated with the cause code is stored in a cause code resource file at the mobile communications device, and the cause code resource file stores a second retry configuration associated with a second cause code configured by the carrier. ### Claim 19 (depends on 18) The non-transitory computer-readable medium of claim 18, wherein the cause code resource file stores a third retry configuration associated with the cause code configured by a second carrier of the wireless network. ### Claim 20 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the wireless network comprises at least one of a General Packet Radio Service (GPRS) network, an Enhanced Data Rates for Global System for Mobile Communications (GSM) Evolution (EDGE) network, a 3rd Generation (3G) network, an Integrated Digital Enhanced Network (IDEN), or a Code Division Multiple Access (CDMA) network.