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