Lauro joined Award Solutions in 2008, bringing over ten years of experience in the wireless telecommunication industry working with mobile cellular, broadband and satellite communications. Has a thorough knowledge and understanding of all standardized radio transmission technologies (i.e.: GSM, GPRS, EDGE, WCDMA, HSxPA, HSPA+,IS-95, cdma 1xRTT, 1xEV-DO) and non-standardized technologies (i.e.: Flash OFDM, I-Burst, etc.) as well as and their migration path to 4G and beyond (LTE and WiMAX).
Lauro has co-authored four different telecommunication books, has published 18 international refereed journal papers and over 30 international conference papers, all of them results of research in the wireless telecommunication area. Additionally, has presented over 20 different wireless related courses nationally and internationally to a diverse class of clients. Lauro has a thorough knowledge of mathematical analysis and hands-on experience on wireless and traffic engineering design, including Design, Planning, Performance & Optimization as well as computer simulation of mobile wireless networks. Through research and computer simulation techniques has helped a large base of clients (carriers, vendors, new start up companies) develop optimum technological solutions.
Currently, Lauro is one of the instructors at Award Solutions. His current focus is UMTS, HSPA/HSPA+ and LTE. He is also involved in the development of cutting edge training on optimization courses for LTE operators in the USA.
Lauro holds a Ph.D. in electrical engineering (EE) from King's College London, UK (the University of London), a MSc. In EE. and a B.EE from the National Polytechnic Institute, Mexico, all of them with specialty in telecommunications.
Often time while doing a drive test the RRC collection released gets logged by our data collection tools and later, while debugging our drive tests we see, RRC connection Release. Many times we wonder why we received that message. Is it because we finished our 500 GB file download? Did we unintentionally press a button and we ended the call? What happened?
There are many cases where and when the UE receives an RRC connection release:
a) Going to idle mode: In this case, the UE will receive an RRC connection release from the eNodeB due to the expiration of the inactivity timer (in most networks configured to approximately 10 seconds).
Release Cause: Other
b) Drop Call - > RLC Failure: When the number of retransmissions at the RLC layer in the Downlink direction reaches its maximum value given by the parameter MaxRetxThreshold, the eNodeB releases the context and sends an RRC connection release to the UE.
Release Cause: Other.
c) Drop Call - > RRC Connection Reestablishment Reject: Either because the feature is not adopted or because a race condition occurred in which the case just presented happened first, the eNodeB responds with a RRC connection reestablishment reject to the UE.
d) Tracking Area Update: During a successful tracking area update, the eNodeB will send an RRC connection release to the UE after sending a tracking area update message (from the MME) when no new GUTI is allocated or after the tracking area update complete message is received from the UE, if it received a new GUTI.
e) During Detach: Either during normal detach or abnormal detach, both by an UE initiated detach or network initiated detach, the UE receives an RRC connection Release from the network. Elements in the Network that may cause a detach message sent from the MME to the UE are:
Release Cause: Other or Normal.
Given the above, the RRC connection release message is caused by many reasons. Before arriving to a conclusion just by analyzing a simple UE logfile, a cell trace or MME trace analysis is required to arrive to sounded conclusions.
nice information, but if we increase the MaxRetxThreshold and hope during mobility the radiolink will change better is it a good solution to do?.