Managing Connection Retries Due To Access Class Barring

Abstract

In some implementations, a method includes receiving a connection request from a user application. A service request is sent to a radio resource control (RRC) module. An indication of failure of or a rejection to the service request due to access class barring is received from the RRC module. A retry of the user application connection request is prevented until expiration of an access-class-barring timer of the RRC module that resulted in the access class barring.

What is claimed is: 
     
         1 . A method, comprising:
 generating, by a mobile device, a service request, in response to a connection request from a user application;   receiving, by the mobile device, an indication of failure of or a rejection to the service request due to access class barring; and   in response to the indication of failure or the rejection:
 determining an access-class-barring timer of a radio resource control (RRC) module of the mobile device, wherein the access-class-barring timer results in the access class barring; 
 aligning a retry timer of the user application to the access-class-barring timer of the RRC module; and 
 preventing a retry of the connection request until expiration of the retry timer. 
   
     
     
         2 . The method of  claim 1 , wherein aligning the retry timer of the user application to the access-class-barring timer of the RRC module comprises:
 determining a timeout value for the access-class-barring timer; and   setting the expiration of the retry timer to the timeout value.   
     
     
         3 . The method of  claim 2 , wherein the indication of failure of or a rejection to the service request comprises the timeout value for the access-class-barring timer. 
     
     
         4 . The method of  claim 1 , wherein preventing the retry of the service request comprises:
 in response to expiration of the retry timer, automatically triggering a retry of the connection request.   
     
     
         5 . The method of  claim 1 , wherein the user application comprises at least one of a data application, a short messaging service (SMS) application, or a voice application. 
     
     
         6 . The method of  claim 1 , further comprising:
 determining a type of mobile originating (MO) traffic for the user application generating the connection request; and   indicating the type of MO traffic to the RRC module, wherein the access class barring is based on the type of MO traffic.   
     
     
         7 . The method of  claim 1 , wherein the access-class-barring timer comprises at least one of T303, T305, or T306. 
     
     
         8 . A mobile device, comprising:
 one or more processors configured to:
 generate a service request in response to a connection request from a user application; 
 receive an indication of failure of or a rejection to the service request due to access class barring; and 
 in response to the indication of failure or the rejection:
 determine an access-class-barring timer of a radio resource control (RRC) module of the mobile device, wherein the access-class-barring timer results in the access class barring; 
 align a retry timer of the user application to the access-class-barring timer of the RRC module; and 
 prevent a retry of the connection request until expiration of the retry timer. 
 
   
     
     
         9 . The mobile device of  claim 8 , wherein aligning the retry timer of the user application to the access-class-barring timer of the RRC module comprises:
 determining a timeout value for the access-class-barring timer; and   setting the expiration of the retry timer to the timeout value.   
     
     
         10 . The mobile device of  claim 9 , wherein the indication of failure of or a rejection to the service request comprises the timeout value for the access-class-barring timer. 
     
     
         11 . The mobile device of  claim 8 , wherein preventing the retry of the service request comprises:
 in response to expiration of the retry timer, automatically triggering a retry of the connection request.   
     
     
         12 . The mobile device of  claim 8 , wherein the user application comprises at least one of a data application, a short messaging service (SMS) application, or a voice application. 
     
     
         13 . The mobile device of  claim 8 , wherein the one or more processors are further configured to:
 determine a type of mobile originating (MO) traffic for the user application generating the connection request; and   indicate the type of MO traffic to the RRC module, wherein the access class barring is based on the type of MO traffic.   
     
     
         14 . The mobile device of  claim 8 , wherein the access-class-barring timer comprises at least one of T303, T305, or T306. 
     
     
         15 . A non-transitory computer-readable medium storing computer instructions, that when executed by one or more hardware processors, cause a computing device to perform operations comprising:
 generating, by the computing device, a service request, in response to a connection request from a user application;   receiving, by the computing device, an indication of failure of or a rejection to the service request due to access class barring; and   in response to the indication of failure or the rejection:
 determining an access-class-barring timer of a radio resource control (RRC) module of the computing device, wherein the access-class-barring timer results in the access class barring; 
 aligning a retry timer of the user application to the access-class-barring timer of the RRC module; and 
 preventing a retry of the connection request until expiration of the retry timer. 
   
     
     
         16 . The non-transitory computer-readable medium of  claim 15 , wherein aligning the retry timer of the user application to the access-class-barring timer of the RRC module comprises:
 determining a timeout value for the access-class-barring timer; and   setting the expiration of the retry timer to the timeout value.   
     
     
         17 . The non-transitory computer-readable medium of  claim 16 , wherein the indication of failure of or a rejection to the service request comprises the timeout value for the access-class-barring timer. 
     
     
         18 . The non-transitory computer-readable medium of  claim 15 , wherein preventing the retry of the service request comprises:
 in response to expiration of the retry timer, automatically triggering a retry of the connection request.   
     
     
         19 . The non-transitory computer-readable medium of  claim 15 , wherein the user application comprises at least one of a data application, a short messaging service (SMS) application, or a voice application. 
     
     
         20 . The non-transitory computer-readable medium of  claim 15 , wherein the operations further comprise:
 determining a type of mobile originating (MO) traffic for the user application generating the connection request; and   indicating the type of MO traffic to the RRC module, wherein the access class barring is based on the type of MO traffic.