36.331 RELEASE 8 PDF

Categories : Science

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: Kajilkree Shakacage
Country: Jordan
Language: English (Spanish)
Genre: Relationship
Published (Last): 24 October 2017
Pages: 190
PDF File Size: 9.19 Mb
ePub File Size: 18.26 Mb
ISBN: 731-1-35793-981-3
Downloads: 49047
Price: Free* [*Free Regsitration Required]
Uploader: Mooguktilar

If the UE support full capability of Rel 13 and a lot of band combination.

Also it would be a good idea to check these information first before you test anything on Measurement, InterRAT. 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.

As a result, interpreting the contents of the message has become pretty complicated. Sometimes UE information says ‘Supported’ but in rleease does not working correct. Why we need to worry about the size limitation of RRC message? Sometimes UE information does not mention something ‘supported’ but seems to work. Since the message is too long and too complicated, 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.


But the size increase by FGI was minor. Relese a result, I see much more issues related to ‘lack of capability’ or ‘mismatch between UE capability report and real implementation’. The more you know of the contents the more you telease 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

Following is how UE Capability Enquiry works. Followings are some of common items you’d better check. So I would split the message into a couple of categories as shown below and post separate repease 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.

The process is very simple as shown below. With this, Network can force UE to send the only capability information that are necessary to the current Network. So I recommend you to check before troubleshoot especially for radio stack issue.

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. Very high level view of UE Capability Information message structure is shown below. It informs on all the details of its capabilities. In some case, we spend pretty much time and effort 36.3331 troubleshoot something which is not supported by UE.

How long the message can repease

What would be the solution for handling this kind of too over-sized message? The real explosion of the size came out with the support of Carrier Aggregation. This list would get longer as the technology evolves. Network request UE to send capability information.


The current several hundred different combination is not with 3CC CA. Followings are some of rellease complete message example for UE Capability Information message. 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. However, as higher carrier aggregation i.

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

Followings are not directly related to UE Capability, but sometimes we see various issues caused by these message correlation. Take this as a guideline but don’t trust too much.

Another possible solution seemingly better solution would be to limit the scope of the information relewse UE report in UE Capability Information message.

But I would suggest you to understand at least on how to interprete the contents of the highlighted items. I want to show how this message has expanded as LTE evolves in following table. I am not aware if there is any explicit size limit reoease any RRC message.

The Enquiry item is configured very simple.