Suspending a connection in a wireless communication system
An evolved Node B (eNB) includes a memory and at least one hardware processor communicatively coupled with the memory and configured to: determine to suspend an established radio resource control (RRC) connection with a user equipment (UE), where suspension causes the established RRC connection to be a suspended RRC connection that disables user plane data communications between the UE and the eNB; in response to a determination to suspend the established RRC connection, store RRC connection data related to the established RRC connection; and transmit, to the UE, an RRC connection suspend command instructing the UE to store the RRC connection data and suspend the established RRC connection.
1. An evolved Node B (eNB), comprising:
a memory; and
at least one hardware processor communicatively coupled with the memory and configured to:
determine to suspend an established radio resource control (RRC) connection with a user equipment (UE), wherein suspension causes the established RRC connection to be a suspended RRC connection that disables user plane data communications between the UE and the eNB;
in response to a determination to suspend the established RRC connection, store RRC connection data related to the established RRC connection; and
transmit, to the UE, an RRC connection suspend command instructing the UE to store the RRC connection data and suspend the established RRC connection.
2. The eNB of claim 1 , wherein the determination to suspend the established RRC connection is based on one or more of:
expiry of a network inactivity timer; or
receiving an indication from the UE indicating that the UE expects no more data.
3. The eNB of claim 1 , wherein the at least one hardware processor is further configured to:
send, to a mobility management entity (MME), a message indicating the suspension of the established RRC connection, wherein the message causes the MME to store the RRC connection data related to the established RRC connection.
4. The eNB of claim 1 , wherein the at least one hardware processor is further configured to mark the RRC connection data to indicate the suspension of the established RRC connection.
5. The eNB of claim 1 , wherein the RRC connection data comprises data representing one or more of:
the configuration of radio bearers in the established RRC connection;
security parameters relating to the established RRC connection;
temporary cell identifiers;
medium access control (MAC) configuration; or
Physical Layer configuration.
6. The eNB of claim 1 , wherein the at least one hardware processor is further configured to:
receive, from the UE, an RRC connection resumption request to resume the suspended RRC connection; and
send, to the UE, an RRC connection resumption message including updates to the RRC connection data.
7. The eNB of claim 6 , wherein the at least one hardware processor is further configured to:
send, to an MME, a user plane resume message indicting resumption of the suspended RRC connection.
8. A tangible, non-transitory computer-readable medium containing instructions which, when executed, cause an evolved Node B (eNB) to perform operations comprising:
determining to suspend an established radio resource control (RRC) connection with a user equipment (UE), wherein suspension causes the established RRC connection to be a suspended RRC connection that disables user plane data communications between the UE and the eNB;
in response to the determining, storing RRC connection data related to the established RRC connection; and
transmitting, to the UE, an RRC connection suspend command instructing the UE to store the RRC connection data and suspend the established RRC connection.
9. The tangible, non-transitory computer-readable medium of claim 8 , wherein determining to suspend the established RRC connection is based on one or more of:
expiry of a network inactivity timer; or
receiving an indication from the UE indicating that the UE expects no more data.
10. The tangible, non-transitory computer-readable medium of claim 8 , wherein the operations further comprise:
sending, to a mobility management entity (MME), a message indicating the suspension of the established RRC connection, wherein the message causes the MME to store the RRC connection data related to the established RRC connection.
11. The tangible, non-transitory computer-readable medium of claim 8 , wherein the operations further comprise marking the RRC connection data to indicate the suspension of the established RRC connection.
12. The tangible, non-transitory computer-readable medium of claim 8 , wherein the RRC connection data comprises data representing one or more of:
the configuration of radio bearers in the established RRC connection;
security parameters relating to the established RRC connection;
temporary cell identifiers;
medium access control (MAC) configuration; or
Physical Layer configuration.
13. The tangible, non-transitory computer-readable medium of claim 8 , wherein the operations further comprise:
receiving, from the UE, an RRC connection resumption request to resume the suspended RRC connection; and
sending, to the UE, an RRC connection resumption message including updates to the RRC connection data.
14. The tangible, non-transitory computer-readable medium of claim 13 , wherein the operations further comprise:
sending, to an MME, a user plane resume message indicting resumption of the suspended RRC connection.
15. A user equipment (UE), comprising:
a memory; and
at least one hardware processor communicatively coupled with the memory and configured to:
receive, from an evolved Node B (eNB), a radio resource control (RRC) connection suspend command instructing the UE to suspend an established RRC connection, wherein suspension causes the established RRC connection to be a suspended RRC connection that disables user plane data communications between the UE and the eNB; and
in response to reception of the RRC connection suspend command, store RRC connection data related to the established RRC connection and suspend the established RRC connection.
16. The UE of claim 15 , wherein the at least one hardware processor is further configured to send an indication to the eNB indicating that the UE expects no more data.
17. The UE of claim 15 , wherein the at least one hardware processor is further configured to mark the RRC connection data to indicate the suspension of the established RRC connection.
18. The UE of claim 15 , wherein the RRC connection data comprises data representing one or more of:
the configuration of radio bearers in the established RRC connection;
security parameters relating to the established RRC connection;
temporary cell identifiers;
medium access control (MAC) configuration; or
Physical Layer configuration.
19. The UE of claim 15 , wherein the at least one hardware processor is further configured to:
send, to the eNB, an RRC connection resumption request to resume the suspended RRC connection; and
receive, from the eNB, an RRC connection resumption message including updates to the RRC connection data.
20. The UE of claim 19 , wherein the RRC connection resumption request is sent using a random access channel.