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.
|Country:||Moldova, Republic of|
|Published (Last):||6 January 2008|
|PDF File Size:||15.82 Mb|
|ePub File Size:||5.24 Mb|
|Price:||Free* [*Free Regsitration Required]|
When LTE first came out, this process was very simple, but as LTE evolves the information that are required gets larger and complicated. What would be the solution for handling this kind of too over-sized message? We haven’t even thought of this for delease 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.
Network request UE to send capability information. This list would get longer as the technology evolves. 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
Take this as a guideline but don’t trust too much. As a result, interpreting the contents of the message has become pretty complicated. Following is how UE Capability Enquiry works. 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.
Also it would be a good idea to check these information first before you test anything on Measurement, InterRAT. Since the message is 36.3311 long and too complicated, it would be tricky to describe all of the contents in the single page. The real explosion of the size came out with the support of Carrier Aggregation.
I am not aware if there is any explicit size limit for any RRC message.
If the UE support full capability of Rel 13 and a lot of band combination. So I would split the message into a couple of categories as shown below and post separate pages for each of the categories. 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’. Very high level view of UE Capability Information message structure is shown below. However, as higher carrier aggregation i. But I would suggest you reldase understand at least on how to interprete the contents of the highlighted items. Followings are some of the complete message example for UE Capability Information 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 to store the 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. It informs on all the details of its capabilities. UE reports the information to NW as requested.
Sometimes UE information says ‘Supported’ but in reality does not working correct. So I recommend you to check before troubleshoot especially for radio stack issue. But the size increase by FGI was minor. Sometimes UE information does not mention something ‘supported’ but seems to work.
The more you know of the contents the more you can understand about the UE and the better position you are at for troubleshooting. The process is very simple as shown below. Followings 36.313 not directly related to UE Capability, but sometimes we relaese 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.
Why we need to worry about the size limitation of RRC message? Followings are some of common items you’d better check.
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. The current delease hundred different combination is not with 3CC CA. How long the message can be? I want to show how this message has expanded as LTE evolves in following table.