Site Loader

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: Vuzshura Aragami
Country: Brazil
Language: English (Spanish)
Genre: Life
Published (Last): 11 March 2004
Pages: 166
PDF File Size: 5.43 Mb
ePub File Size: 14.29 Mb
ISBN: 821-2-94524-418-8
Downloads: 64688
Price: Free* [*Free Regsitration Required]
Uploader: Arashinris

Followings are list of topics 36.33 will be dealt with in this page or a few other pages that are related to UE capability Information. Also it would be a good idea to check these information first before you test anything on Measurement, InterRAT.

Delease would be the solution relwase handling this kind of too over-sized message? UE eelease the information to NW as requested. Followings are not directly related to UE Capability, but sometimes we see various issues caused by these message correlation.

We haven’t even releaze 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. The real explosion of the size came out with the support of Carrier Aggregation.

Since the message is too long and too complicated, it would be tricky to describe all of the contents in the single page. As a result, interpreting the contents of the message has become pretty complicated. I want to show how this message has expanded as LTE evolves in following table. This list would get longer as the technology evolves. If the UE support full capability of Rel 13 and a lot of band combination.

  IEC 60099 1 PDF

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. The process is very simple as shown below.

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

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? Network request UE to send capability information. It informs on all the details of its capabilities. But I would suggest you to understand at least on how to interprete the contents of the highlighted items.

So I would split the message into a couple of categories as shown below and post separate pages for each of the categories.

Followings are some of the complete message example for UE Capability Information message. The Enquiry item is configured very simple. As a result, I see much more issues related to ‘lack of capability’ or ‘mismatch between UE capability report and real implementation’. Take this as a guideline but don’t relaese too much. Following is how UE Capability Enquiry works. So I recommend you to check before troubleshoot especially for radio stack issue. Very high level view of UE Capability Information message structure is shown below.


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. How long the message can be?

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

With this, Network can force UE to send the only capability information that are necessary to the current Network. However, as higher carrier aggregation i.

The current several hundred different combination is not with 3CC CA. Sometimes UE information says ‘Supported’ relase in reality does not working correct. 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 the size increase by FGI was minor.

I am not aware if there is any explicit size limit for any RRC message. 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 rdlease store the message.

Another possible solution seemingly better solution would be to limit the scope of the reelase that UE report in UE Capability Information message. Sometimes UE information does not mention something ‘supported’ but seems to work.