3GPP TS V (). 2. Release 8. Keywords. UMTS, radio. 3GPP. Postal address. 3GPP support office address. Route des. Radio Resource Control (RRC); Protocol specification (3GPP TS version Release 11) Ocr ABBYY FineReader Ppi Release 8. 2. 3GPP TS V (). Keywords UMTS, radio. 3GPP Postal address 3GPP support office address Route des Lucioles – Sophia.
|Published (Last):||27 August 2006|
|PDF File Size:||13.19 Mb|
|ePub File Size:||9.95 Mb|
|Price:||Free* [*Free Regsitration Required]|
Feature Group Indicators (FGI bits) in LTE – Rel. 8, Rel. 9 and Rel. 10 – Techplayon
The root cause relexse a kind of message buffer overflow, meaning that the size of the incoming signaling message hit the size of memory allocated to store the message. I want to show how this message has expanded as LTE evolves in following table. Very high level view of UE Capability Information message structure is shown below. How long the message can be?
Feature Group Indicators (FGI bits) in LTE – Rel. 8, Rel. 9 and Rel. 10
We haven’t even 36.331 of this for most of the case, but we start worrying about size limitation of RRC message as UE Capability Information message gets almost exploded in terms of message length size. In some case, we spend pretty much time and effort to troubleshoot something which is not supported by UE.
So I recommend you to check before troubleshoot especially for radio stack issue.
The Enquiry item is configured very simple. Another possible solution seemingly better solution would be to limit the scope of the information 36.3311 UE report in UE Capability Information message. Followings are some of common items you’d better check. One brutal solution would be to reserve super-large message buffer size and ensure 366.331 your ASN decoder works properly for such a super large tree structure. UE reports the information to NW as requested.
Network request UE to send capability information. As a result, interpreting the contents of the message has become pretty complicated.
However, as higher carrier aggregation i. Releas is how UE Capability Enquiry works. The current several hundred different combination is not with 3CC CA. But I would suggest you to understand at least on how to interprete the contents of the highlighted items. When LTE first came out, this process was very simple, but as LTE evolves the information that are required gets larger and complicated.
With this, Network can force UE to send the only capability information that are necessary to the current Network. I am not aware if there is any explicit size limit for any RRC message. Followings are not directly related to UE Capability, but sometimes we see releaee issues caused by these message correlation. The more you know of the contents the more you can understand about the UE and the better position you are at for troubleshooting. Take this as a guideline but don’t trust too much.
Sometimes UE information does not mention releasd ‘supported’ but seems to work. The real explosion of the size came out with the support of Carrier Aggregation.
As a result, I see much more issues related to ‘lack of capability’ or ‘mismatch between UE capability report and real implementation’. Why we need to worry about the size limitation of RRC message?
It informs on all the details of its capabilities. Followings are some of the complete message example for UE Capability Information message. If the UE support full capability of Rel 13 and a lot of band combination. Sometimes UE information says ‘Supported’ but in reality does not working correct. Since the message is too long and too complicated, it would be tricky to describe all of releaae contents in the single page.
This list would get longer as the technology evolves. But the size increase by FGI was minor. So I would split the message into a couple of categories as shown below and post separate pages for each of the categories. Also it would releasd a good idea to check these information first before you test anything on Measurement, InterRAT. What would be the solution for handling this kind of too over-sized message?
The process is very simple 3.6331 shown below. Followings are list of topics that will be dealt with in this page releade a few other pages that are related to UE capability Information.