36.331 RELEASE 8 PDF

Categories : Personal Growth

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: Arashishakar Mazular
Country: Djibouti
Language: English (Spanish)
Genre: Marketing
Published (Last): 9 May 2014
Pages: 226
PDF File Size: 1.30 Mb
ePub File Size: 13.62 Mb
ISBN: 265-7-63916-854-3
Downloads: 3157
Price: Free* [*Free Regsitration Required]
Uploader: Vudolar

However, as higher carrier aggregation i.

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

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

Take this as a guideline but don’t trust too much. As a result, I see much more issues related to ‘lack of capability’ or ‘mismatch between UE capability report and real implementation’. But the size increase by FGI was minor. Following is how UE Capability Enquiry works. 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. The Enquiry item is configured very simple. I am not aware releasf there is any explicit size limit for any RRC message. As a result, interpreting the contents of the message has become pretty complicated.

  ISO 7886-2 PDF

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.

When LTE first came out, this process was very simple, but as LTE evolves the information that are required gets larger and complicated.

It informs on all the details of its capabilities. Followings are not directly related to UE Capability, but sometimes we see various issues caused by releasee message correlation. 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 releade in terms of message length size.

So I recommend you to check before troubleshoot especially for radio stack issue. Sometimes UE information says ‘Supported’ but in reality releaes not working correct.

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

Followings are some of common items you’d better check. Followings reldase 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. Network request UE to send capability information.

Followings are some of the complete message example for UE Capability Information message. 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. In rleease case, we spend 88 much time and effort to troubleshoot something which is not supported by UE.


The more you know of the contents the more you can understand about the UE and the better position you are at for troubleshooting. So I would split the message into a couple of categories as shown below and post separate pages for each of the 63.331. How long the message can be? What would be the solution for handling this kind of too over-sized message?

The process is very simple as shown below. This list would get longer as the technology evolves. Since the message is too long and too complicated, it would be tricky to describe all of the contents in the single page. If the UE support full capability of Rel 13 and a lot of band combination. Why we need to worry about the size limitation of RRC message? The real rwlease of the size came out with the support of Carrier Aggregation. Very high level view of UE Capability Information message structure is shown below.

The current several hundred different combination is not with 3CC CA.