![]() ![]() So I recommend you to check before troubleshoot (especially for radio stack issue). In some case, we spend pretty much time and effort to troubleshoot something which is not supported by UE. Try to get the high level understandings of UE capability information message and refer to following pages for the details. ![]() So I would split the message into a couple of categories as shown below and post separate pages for each of the categories. ![]() Since the message is too long and too complicated, it would be tricky to describe all of the contents in the single page. But I would suggest you to understand at least on how to interprete the contents of the highlighted items. The more you know of the contents the more you can understand about the UE and the better position you are at for troubleshooting. Very high level view of UE Capability Information message structure is shown below. High Level Structure of UE Capability Information UE-CapabilityRequest ::= SEQUENCE (SIZE (1.maxRAT-Capabilities)) OF RAT-Type Refer to 36.331 5.6.3.3 Reception of the UECapabilityEnquiry by the UE in the latest spec if you want to know on the details of the information in the message. ![]() I want to show how this message has expanded as LTE evolves in following table. As a result, interpreting the contents of the message has become pretty complicated. When LTE first came out, this process was very simple, but as LTE evolves the information that are required gets larger and complicated. UE reports the information to NW as requested Network sends UECapabilityEnquiry and UE replied with UECapabilityInformation. The process is very simple as shown below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |