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.

Author: Mikabar Nikokree
Country: Central African Republic
Language: English (Spanish)
Genre: Politics
Published (Last): 17 January 2012
Pages: 472
PDF File Size: 3.51 Mb
ePub File Size: 20.57 Mb
ISBN: 950-8-56792-767-7
Downloads: 18959
Price: Free* [*Free Regsitration Required]
Uploader: Kajishicage

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. The current several hundred different combination is not with 3CC CA.

Another possible solution seemingly better solution would be to limit reoease 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

It informs on all the details of its capabilities. 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 3.6331 in terms of message length size. If the UE support full capability of Rel 13 and a lot of band combination.

This list would get longer as the technology evolves.

So I recommend you to check before troubleshoot especially for radio stack issue. As a result, interpreting the contents of the message has become pretty complicated. The Enquiry item is configured very simple.


Why we need to worry about the size limitation of RRC message? Followings are not directly related to UE Capability, but sometimes we see various 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.

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

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. I want to show how this message has expanded as LTE evolves in following table. As a result, I see much more issues related to ‘lack of capability’ or ‘mismatch 3.6331 UE capability report and real implementation’.

So I would split the message into a couple of categories as shown below and post rflease pages for each of the categories. I am not aware if there is any explicit size limit for any RRC message. What would be the erlease for handling this kind of too over-sized message?

But I would suggest you to understand at least on how to interprete the contents of the highlighted items.

Since the message is too long and too complicated, it would be tricky to describe all of the contents in the single page. Sometimes UE information does not mention something ‘supported’ but seems to work.

Followings are some of the complete message example for UE Capability Information message. The real explosion of the size came out with the support of Carrier Aggregation. Network request UE to send capability information. The process is very simple as shown below. However, as higher carrier aggregation i. 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.


With this, Network can force UE to send the only capability information that are necessary to the current Network. In some case, we spend pretty much time and effort to troubleshoot something which is not supported by UE. Take this as a guideline but don’t trust too much. Very high level view of UE Capability Information message structure is shown below. Sometimes UE information says ‘Supported’ but in reality does not working correct. Followings are some of common items you’d better check.

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? Following is how UE Capability Enquiry works. UE reports the information to NW as requested. But the size increase by FGI was minor.