Reestablishing a mobile device radio resource control connection

1. Non-transitory computer-readable media having computer-executable instructions embodied thereon that, when executed, enable a computing device to perform a method for reestablishing a mobile device RRC connection based on eNodeB messaging, the method comprising:

receiving at a first eNodeB an RRC connection reestablishment request for a mobile device, wherein the mobile device maintains an RRC_Connected state upon sending the RRC connection reestablishment request until the mobile device RRC connection is reestablished via eNodeB messaging that excludes initial security activation of the mobile device;

determining that the RRC connection reestablishment request requires mobile device context data that is unavailable at the first eNodeB;

communicating via the first eNodeB an initial mobile device service request message to an MME based on determining that the RRC connection reestablishment request requires context data that is unavailable at the first eNodeB; and

upon communicating the initial mobile device service request message, receiving the mobile device context data in order to reestablish the mobile device RRC connection.

2. The media of claim 1 , wherein the RRC connection reestablishment request for the mobile device is generated as a result of a radio link failure at the mobile device.

3. The media of claim 1 , wherein the mobile device maintains an RRC_Connected state upon generating the RRC connection reestablishment request at the start of a T311 timer until the mobile device RRC connection is reestablished via eNodeB messaging prior to the expiration of the T311 such that the mobile device does not return to an RRC_Idle state.

4. The media of claim 1 , wherein upon determining that the RRC connection reestablishment request requires the mobile device context data that is unavailable at the first eNodeB, the first eNodeB does not communicate an RRC connection reestablishment rejection message.

5. The media of claim 1 , wherein the initial mobile device service request message is a NAS message communicated from the mobile device via the eNodeB to the MME.

6. The media of claim 1 , wherein the MME identifies the mobile device context is available on a second eNodeB that releases the mobile device context based on a request from the MME.

7. The media of claim 1 , wherein the initial security activation comprises bidirectional authentication between the mobile device and the MME.

8. The media of claim 7 , wherein the bidirectional authentication of the mobile device comprises one or more selected from the following:

an RRC:DL Information Transfer+NAS:Authentication Request;

the RRC:UL Information Transfer+NAS:Authentication Response;

the RRC:DL Information Transfer+NAS:Security Mode Command; and

the RRC:UL Information Transfer+NAS:Security Mode Complete.

9. The media of claim 1 , wherein the mobile device context data is received from a second eNodeB via the MME.

10. The media of claim 1 , further comprising:

receiving at the first eNodeB a mobile device context data setup request;

forwarding the mobile device context data setup request to the mobile device;

receiving mobile device capabilities from the mobile device; and

reconfiguring the mobile device RRC connection via a reconfiguration connection message.

11. Non-transitory computer-readable media having computer-executable instructions embodied thereon that, when executed, enable a computing device to perform a method for reestablishing a mobile device RRC connection based on eNodeB messaging the method comprising:

receiving an initial mobile device service request message via a first eNodeB based on the first eNodeB receiving an RRC connection reestablishment request from a mobile device, wherein mobile device context data is unavailable at the first eNodeB;

upon receiving the initial mobile device service request message, identifying the mobile device context data on a second eNodeB;

requesting release of the mobile device context data from the second eNodeB, wherein the mobile device maintains an RRC_Connected state upon sending the RRC connection reestablishment request until the mobile device RRC connection is reestablished via eNodeB messaging that excludes initial security activation of the mobile device; and

communicating to the first eNodeB the mobile device context data in order to reestablish the mobile device RRC connection.

12. The media of claim 11 , wherein identifying the mobile device context data on the second eNodeB utilizes an S-TMSI of the mobile device.

13. The media of claim 11 , wherein release of the mobile device context data from the second eNodeB further comprises release of one or more mobile device-associated logical connections with the second eNodeB.

14. The media of claim 11 , wherein reestablishing the mobile device RRC connection further comprises:

communicating an initial context setup request;

receiving mobile device capability information indication; and

upon completion of an RRC connection reconfiguration of the mobile device, receiving an initial context setup response.

15. The media of claim 11 , wherein reestablishing the mobile device RRC connection excludes an initial security activation of the mobile device.

16. The media of claim 15 , wherein excluding the initial security activation is based on a determination of prior authentication of the mobile device with the second eNodeB.

17. The media of claim 16 , wherein the determination of prior authentication is based at least in part on release of the mobile device context data from the second eNodeB.

18. A system for reestablishing a mobile device RRC connection based on eNodeB messaging, the system comprising:

a first eNodeB configured for:

(1) receiving an RRC connection reestablishment request for the mobile device;

(2) determining that the RRC connection reestablishment request requires mobile device context data that is unavailable at the first eNodeB;

(3) communicating via the first eNodeB an initial mobile device service request message based on determining that the RRC connection reestablishment request requires context data that is unavailable at the first eNodeB; and

(4) upon communicating the initial mobile device service request message, receiving the mobile device context data in order to reestablish the mobile device RRC connection

an MME configured for:

(1) receiving the initial mobile device service request message via the first eNodeB based on the first eNodeB receiving the RRC connection reestablishment request from a mobile device, wherein the mobile device context data is unavailable at the first eNodeB;

(2) upon receiving the initial mobile device service request message, identifying the mobile device context data on a second eNodeB;

(3) requesting release of the mobile device context data from the second eNodeB, wherein the mobile device maintains an RRC_Connected state upon sending the RRC connection reestablishment request until the mobile device RRC connection is reestablished via eNodeB messaging that excludes initial security activation of the mobile device; and

(4) communicating to the first eNodeB the mobile device context data in order to reestablish the mobile device RRC connection.

19. The system of claim 18 , further comprising:

the mobile device configured for:

(1) generating the RRC connection reestablishment request; and

(2) reestablishing the mobile device RRC connection of the mobile device based on the mobile device context data from the first eNodeB, wherein the first eNodeB received the mobile device context data from the second eNodeB via the MME.

20. The system of claim 18 , further comprising:

the second eNodeB configured for:

(1) receiving a request to release the mobile device context data based on the MME identifying the mobile device context data on the second eNodeB; and

(2) releasing the mobile device context data to the MME in order to reestablish the mobile device RRC connection.