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):||28 January 2013|
|PDF File Size:||11.97 Mb|
|ePub File Size:||19.82 Mb|
|Price:||Free* [*Free Regsitration Required]|
Take this as a guideline but don’t trust too much. Sometimes UE information does not mention something ‘supported’ but seems to work. One brutal solution would be to reserve super-large message buffer size and ensure that your ASN decoder works properly for such a super large tree structure. Also it would be a good idea to check these information first before you test anything on Measurement, InterRAT.
I want to show how this message has expanded as LTE evolves in following table. Sometimes UE information says ‘Supported’ but in reality does not working correct. The process is very simple as shown below.
Following is how UE Capability Enquiry works.
What would be the solution for handling this kind of too over-sized message? When LTE first came out, this process was very simple, but as LTE evolves the information that are required gets felease and reelease.
The Enquiry item is configured very simple. How long the message can be? But the size increase by FGI was minor. Why we need to worry about the size limitation of RRC message? We haven’t even thought 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.
Feature Group Indicators (FGI bits) in LTE – Rel. 8, Rel. 9 and Rel. 10 – Techplayon
I am not aware if there is any explicit size limit for any RRC message. So I recommend you to check before troubleshoot especially for radio stack issue. Network request UE to send capability information.
Since the message is too long and too complicated, it would be tricky to describe all of the contents in the single page. With this, Network can force UE to send the only capability information that are necessary to the current Network.
It informs on all the details of its capabilities.
Feature Group Indicators (FGI bits) in LTE – Rel. 8, Rel. 9 and Rel. 10
The real explosion of the size came out with the support of Carrier Aggregation. The current several hundred different combination is not with 3CC CA. If the UE support full capability of Rel 13 and a lot of band combination. The root cause was 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.
Another possible solution seemingly better solution would be to limit the scope of the reoease that UE report in UE Capability Information message.
Followings are some of common items you’d better check. Followings are not directly related to UE Capability, but sometimes we see various issues caused by these message correlation.
In some case, we spend pretty much time and effort to troubleshoot something which is not supported by UE. Followings releasr some of the complete message example for UE Capability Information message. As a result, interpreting the contents of the message has become pretty complicated.
UE reports the information to NW as requested. So I would split the message into a couple of categories as shown below and post separate pages for each of the categories. Releasw, as higher carrier aggregation i. Very high level view of UE Capability Information message structure is shown below.
The more you know of the contents the more you can understand about the UE and the better position you are at for troubleshooting. 63.331
This list would get longer as the technology evolves. But I would suggest 3.6331 to understand at least on how to interprete the contents of the highlighted items.