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.

Author: Kajilabar Dotaur
Country: Libya
Language: English (Spanish)
Genre: Automotive
Published (Last): 22 June 2011
Pages: 124
PDF File Size: 13.99 Mb
ePub File Size: 14.83 Mb
ISBN: 583-4-86777-307-7
Downloads: 21941
Price: Free* [*Free Regsitration Required]
Uploader: Nalabar

3GPP TS (1 of 18) – E-UTRA RRC

The current several hundred different combination is not with 3CC Reease. Followings are some of common items you’d better check. I want to show how this message has expanded as LTE evolves in following table. What would be the solution for handling this kind of too over-sized message? However, as higher carrier aggregation i. Take this as a guideline but don’t trust too much. 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.

If the UE gelease full capability of Rel 13 and a lot of band combination. We haven’t even thought of this for most of the case, but we start relfase about size limitation of RRC message as UE Capability Information message gets almost exploded in terms of message length size. Another possible solution seemingly better solution would be to limit the scope of the information that UE report in UE Capability Information message.


Feature Group Indicators (FGI bits) in LTE – Rel. 8, Rel. 9 and Rel. 10 – Techplayon

Sometimes UE information says ‘Supported’ but in reality does not working correct. Very high level view of UE Capability Information message structure is shown below. Sometimes UE information does not mention something ‘supported’ but seems to work.

When LTE first came out, this process was very simple, but as LTE evolves the information that are required gets larger and complicated. Followings are some of the complete message example for UE Capability Information message.

I am not aware if there is any explicit size limit for any RRC message.

But the size increase by FGI was minor. The process is very simple as shown below. 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.

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. Why we need to worry about the size limitation of RRC message? Since the message is too long and too complicated, it would be tricky to describe all of the contents reease the single page. 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. UE reports the information to NW as requested.

Also it would be a good idea to check these information first before you test anything on Measurement, InterRAT. In some case, we spend pretty much time and effort to troubleshoot something which is not supported by UE.


So I would split the message into a couple of categories as shown below and post separate pages for each of the categories. Network request UE to send capability information. This list would get longer as the technology evolves.

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 not directly related to UE Releaze, but sometimes we see various issues caused by these message correlation. With this, Network can force UE to send the only capability information that are necessary to the current Network. As a result, Releqse see much more issues related to ‘lack of capability’ or ‘mismatch between UE capability report and real implementation’.

It informs on all the details of its capabilities. As a result, interpreting the contents of releaze message has become pretty complicated. So I recommend you to check before troubleshoot especially for radio stack issue.

Following is how UE Capability Enquiry works. How long the message can be?

But I would suggest you to understand at least on how to interprete the contents of the highlighted items. The Enquiry item is configured very simple.