P
US10098066B2ActiveUtilityPatentIndex 46

Auxiliary back-off to avoid battery and network resource depletion in variable network conditions

Assignee: MICROSOFT TECHNOLOGY LICENSING LLCPriority: Jun 27, 2016Filed: Jun 27, 2016Granted: Oct 9, 2018
Est. expiryJun 27, 2036(~10 yrs left)· nominal 20-yr term from priority
Inventors:YADAV MAHESHJUNG TAEHWANRAO SRINIVASA
H04W 52/0229H04W 76/18H04W 48/06H04W 4/12H04M 1/72583H04M 1/72469Y02D30/70
46
PatentIndex Score
1
Cited by
32
References
20
Claims

Abstract

The embodiments of the disclosure include methods and apparatus that provide back-off procedures for avoiding device/network resource depletion in bad network conditions. A device user may selectively enable an auxiliary back-off procedure that extends the time between network service requests. For example, the auxiliary back-off procedure may be used if the device determines an attach request is unsuccessful when a reject message is received from the network and the reject message indicates a reject cause for which the device has no defined back-off to follow. The auxiliary back-off procedure may be also be used if the device determines that a service request is unsuccessful when the service request is ignored, i.e. no response is received from the network, or, when a service request reject is received from the network and the reject message indicates a reject cause for which the device has no defined back-off to follow.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
       1. A device comprising:
 one or more processors; and, 
 memory in communication with the one or more processors, the memory comprising program instructions, that when executed, causes the one or more processors to control the device to: 
 transmit a service request to a network; 
 determine that the service request has been unsuccessful based on an event; 
 determine if a first back-off procedure is defined for the event; 
 and, if the first back-off procedure is not defined for the event;
 determine if a second back-off procedure is enabled; and, 
 perform the second back-off procedure if the second back-off procedure is enabled. 
 
 
     
     
       2. The device of  claim 1 , wherein the service request comprises a first service request and the program instructions further cause the one or more processors to control the device to initiate one or more second service requests if the second back-off procedure is not enabled. 
     
     
       3. The device of  claim 1 , wherein the event comprises receiving a reject message including an indication of a reject cause. 
     
     
       4. The device of  claim 3 , wherein the program instructions further cause the one or more processors to determine if a first back-off procedure is defined for the event by controlling the device to:
 determine if the indication of the reject cause is defined as associated with the first back-off procedure. 
 
     
     
       5. The device of  claim 4 , wherein the program instructions further cause the one or more processors to determine if a first back-off procedure is defined for the event by controlling the device to:
 determine, in response to a determination that the indication of the reject cause is associated with the first back-off procedure, if the reject cause is an excepted reject cause; 
 and, if the reject cause is an excepted reject cause:
 determine if the second back-off procedure is enabled; 
 perform at least a portion of the first back-off procedure; and, 
 perform the second back-off procedure if the second back-off procedure is enabled. 
 
 
     
     
       6. The device of  claim 1 , wherein the event comprises the network ignoring the service request. 
     
     
       7. The device of  claim 1 , wherein the program instructions further cause the one or more processors to control the device to receive input from a user interface that enables or disables the second back-off procedure. 
     
     
       8. The device of  claim 1 , wherein the service request comprises a first service request and the program instructions further cause the one or more processors to perform the second back-off procedure by controlling the device to:
 increment a counter; 
 determine if the counter is set to a maximum attempt value; 
 activate a timer if the counter is set to the maximum attempt value; and, 
 back-off from sending any second service request until the timer expires. 
 
     
     
       9. The device of  claim 1 , wherein the service request comprises a first service request and the program instructions further cause the one or more processors to perform the second back-off procedure by controlling the device to:
 increment a counter; 
 determine if the counter is set to a maximum attempt value; and, 
 initiate a second service request if the counter is not set to the maximum attempt value. 
 
     
     
       10. A method comprising:
 transmitting a service request to a network; 
 determining that the service request has been unsuccessful based on an event; 
 determining if a first back-off procedure is defined for the event; 
 and, if the first back-off procedure is not defined for the event:
 determining if a second back-off procedure is enabled; and, 
 performing the second back-off procedure if the second back-off procedure is enabled. 
 
 
     
     
       11. The method of  claim 10 , wherein the service request comprises a first service request and the method further comprises initiating one or more second service requests if the second back off procedure is not enabled. 
     
     
       12. The method of  claim 10 , wherein the event comprises receiving a reject message including an indication of a reject cause. 
     
     
       13. The method of  claim 12 , wherein the determining if a first back-off procedure is defined for the event comprises:
 determining if the indication of the reject cause is defined as associated with the first back-off procedure. 
 
     
     
       14. The method of  claim 13 , wherein the determining if a first back-off procedure is defined for the event further comprises:
 determining, in response to a determination that the indication of the reject cause is associated with the first back-off procedure, if the reject cause is an excepted reject cause; 
 and, if the reject cause is an excepted reject cause:
 determining if the second back-off procedure is enabled; 
 performing at least a portion of the first back-off procedure; and, 
 performing the second back-off procedure if the second back-off procedure is enabled. 
 
 
     
     
       15. The device of  claim 10 , wherein the event comprises the network ignoring the service request. 
     
     
       16. The method of  claim 10 , wherein the method further comprises receiving input from a user interface that enables or disables the second back-off procedure. 
     
     
       17. A device comprising:
 a user interface; 
 one or more processors in communication with the user interface; and,
 memory in communication with the one or more processors, the memory comprising program instructions, that when executed, causes the one or more processors to control the device to: 
 receive input at the user interface, the input enabling an auxiliary back-off procedure; 
 send a service request to a network; 
 determine that the service request has been unsuccessful based on an event; 
 determine whether a defined back-off procedure is configured for the event; 
 determine, in response to defined back-off procedure not being configured for the event, whether the auxiliary back-off procedure is enabled; and, 
 perform, in response to a determination that the auxiliary back-off is enabled, the auxiliary back-off procedure. 
 
 
     
     
       18. The device of  claim 17 , wherein the program instructions cause the one or more processors to control the device to determine that the service request has been unsuccessful by determining that a reject message indicating a reject cause was received in response to the service request. 
     
     
       19. The device of  claim 18 , wherein the program instructions further causes the one or more processors to determine whether a defined back-off procedure is configured for the event by controlling the device to determine if the reject cause is defined as associated with a defined back-off procedure. 
     
     
       20. The device of  claim 19 , wherein the program instructions further causes the one or more processors to determine if the indication of the reject cause is associated with a defined back-off procedure by controlling the device to:
 determine, in response to a determination that the indication of the reject cause is associated with the defined back-off procedure, if the reject cause is an excepted defined reject cause; 
 and, if the reject cause is an excepted defined reject cause:
 determine if the auxiliary back-off procedure is enabled; 
 perform at least a portion of the defined back-off procedure; and, 
 perform the auxiliary back-off procedure if the auxiliary back-off procedure is enabled.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.