Method for Processing Data Associated with Session Management and Mobility Management

1. A method of processing data in a communication system, the method performed by a user equipment (UE) and comprising: receiving a deactivate bearer context request message; deleting a bearer context identified by a bearer identity in the deactivate bearer context request message; if a cause code in the deactivate bearer context request message indicates that reactivation is requested, stopping a session management back-off timer associated with a previously-established data connection if the session management back-off timer is running, wherein the session management back-off timer is a timer starting if a session management back-off time value is received at the UE, and wherein the previously-established data connection is associated with an access point name (APN); and re-initiating a packet data network (PDN) connectivity procedure for the APN after stopping the session management back-off timer.

2. The method of claim 1 , further comprising: after deleting the bearer context, transmitting a deactivate bearer context accept message.

3. The method of claim 1 , wherein the cause code is set to ‘39’, which indicates the reactivation is requested.

4. The method of claim 1 , wherein the session management back-off time value is included in a bearer resource modification reject message, and the UE does not transmit an additional request for a bearer resource modification while the session management back-off timer is running.

5. The method of claim 4 , wherein the bearer resource modification reject message includes a cause code which is set to ‘26’, which indicates ‘insufficient resources’.

6. The method of claim 1 , wherein the session management back-off time value is included in a bearer resource allocation reject message, and the UE does not transmit an additional request for the bearer resource allocation while the session management back-off timer is running.

7. The method of claim 6 , wherein the bearer resource allocation reject message includes a cause code which is set to ‘26’, which indicates ‘insufficient resources’.

8. A user equipment (UE) in a communication system, the UE comprising: a radio frequency unit; and a processor coupled to the radio frequency unit and configured to: receive a deactivate bearer context request message, delete a bearer context identified by a bearer identity in the deactivate bearer context request message, if a cause code in the deactivate bearer context request message indicates that reactivation is requested, stop a session management back-off timer associated with a previously-established data connection if the session management back-off timer is running, wherein the session management back-off timer is a timer starting if a session management back-off time value is received at the UE, and wherein the previously-established data connection is associated with an access point name (APN), and re-initiate, a packet data network (PDN) connectivity procedure for the APN after stopping the session management back-off timer.

9. The UE of claim 8 , wherein the processor is further configured to transmit a deactivate bearer context accept message after deleting the bearer context.

10. The UE of claim 8 , wherein the cause code is set to ‘39’, which indicates the reactivation is requested.

11. The UE of claim 8 , wherein the session management back-off time value is included in a bearer resource modification reject message, and the UE does not transmit an additional request for a bearer resource modification while the session management back-off timer is running.

12. The UE of claim 11 , wherein the bearer resource modification reject message includes a cause code which is set to ‘26’, which indicates ‘insufficient resources’.

13. The UE of claim 8 , wherein the session management back-off time value is included in a bearer resource allocation reject message, and the UE does not transmit an additional request for the bearer resource allocation while the session management back-off timer is running.

14. The UE of claim 13 , wherein the bearer resource allocation reject message includes a cause code which is set to ‘26’, Which indicates ‘insufficient resources’.