What happens when I remove UE intentionally while Downloading and Uploading data from & to N/w.

Question

We are frequently getting the below error when trying to downloading svn data from jenkins. Issue will get resolved when we restart jenkins slave node.
Any idea what is the root cause?

org.tmatesoft.svn.core.SVNException [1]: svn: E175002: OPTIONS /svn/repo/trunk failed    
Caused by: java.io.IOException: 
Remote call on channel failed  at hudson.remoting.Channel.call(Channel.java:760)  at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173)  
... 36 more Caused by: java.lang.NoClassDefFoundError: hudson/remoting/RemoteClassLoader$RemoteIClassLoader  at   
hudson.remoting.RemoteClassLoader.export(RemoteClassLoader.java:657)  at hudson.remoting.UserRequest.
(UserRequest.java:70)  at hudson.remoting.Channel.call(Channel.java:750)  ... 37 more     

Answer 1

This is the scenario like UE is moving to no coverage area or removing UE battery when data in DL and UL running.

In this case eNB will do DL /UL scheduling to UE through Pdcch till eNB declare RLF for the UE . UE will not send any harq ack/nack or will not send any data in UL so eNB will not get any response from UE and make UE as RLF. After RLF enb will remove the UE context and will send the UE context release request to mme . MME will release the UE context and will update UE state to ECM IDLE.

Comments

Veer please correct me if my understanding is not correct.
- Timer  T310 is started once the RLF is detected and it stopped when the rrc re-establishment procedure started.
- eNodeB does not release the context immediately . eNodeB release the context only after the expiry of Timer T310.

---

Yes eNB  does not release context immediately but RLF detection at enb in UL is implementation dependent.