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